| Summary: | ASTERISK-02189: wcfxs not detecting incoming calls | ||
| Reporter: | Ryan Courtnage (rcourtna) | Labels: | |
| Date Opened: | 2004-08-04 20:42:11 | Date Closed: | 2008-06-07 10:44:29 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) zapata.conf | |
| Description: | zaptel from CVS-HEAD has this problem. 2004-08-02 zaptel is fine. I suspect the "polarity reversal detection" bug fixes are causing this. I have a tdm400p with fxo modules. To duplicate: - Call from PSTN, and * detects (Starting simple switch on 'Zap/1-1'). - Have dialplan Answer the call, or answer it by ringing a SIP phone - Make the PSTN side hang up 1st, and wait until Asterisk detects this (Hungup 'Zap/1-1') The next incoming call from PSTN to Zap/1 will not be detected. 'restart now' at the CLI corrects the problem for the next call. ****** ADDITIONAL INFORMATION ****** zaptel.conf: loadzone = us defaultzone=us zapata.conf is attached. Asterisk CVS - 2004.06.29 | ||
| Comments: | By: twisted (twisted) 2004-08-04 23:41:05 there have been changes made to cvs after 06/29/04... please update to current and see if your problem still exists. By: egnarf (egnarf) 2004-08-05 04:00:19 I got bit by the same thing myself. In my case it began when zaptel detected a loss of battery. When battery was restored, it kept printing the "BATTERY on" message, but never actually set the battery-variable. The following patch seems to have fixed it for me: --- wcfxs.c 3 Aug 2004 18:36:07 -0000 1.80 +++ wcfxs.c 5 Aug 2004 08:42:35 -0000 @@ -1448,6 +1448,7 @@ #else zt_hooksig(&wc->chans[card], ZT_RXSIG_OFFHOOK); #endif + wc->mod.fxo.battery[card] = 1; wc->mod.fxo.nobatttimer[card] = 0; wc->mod.fxo.battdebounce[card] = BATT_DEBOUNCE; } else if (wc->mod.fxo.battery[card]) By: Dorian Gray (dorian) 2004-08-05 12:49:38 I have been having what seems the same problem as rcourtna -- I get this: Module 3: Installed -- AUTO FXO (FCC mode) Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules) Registered tone zone 0 (United States / North America) 50576934 Polarity reversed (0 -> 1) and then the first incoming call gives this: 50606889 Polarity reversed (1 -> -1) 50608370 Polarity reversed (-1 -> 1) and then after that the fxo would never again see activity from the pstn until wcfxs module was unloaded/reloaded; but the patch supplied by egnarf appears to have remedied this. thank you! By: Mark Spencer (markster) 2004-08-05 16:49:27 I inadvertantly removed a critical line of code while merging the last patch. I apologize for the problem, it's now fixed in CVS. If you have any more trouble just feel free to reopen! By: Digium Subversion (svnbot) 2008-06-07 10:44:28 Repository: dahdi Revision: 448 U trunk/wcfxs.c U trunk/wctdm.c ------------------------------------------------------------------------ r448 | markster | 2008-06-07 10:44:27 -0500 (Sat, 07 Jun 2008) | 2 lines Restore inadvertantly removed line of code (bug ASTERISK-2189) ------------------------------------------------------------------------ http://svn.digium.com/view/dahdi?view=rev&revision=448 | ||