Tony Mountifield
2008-Jul-28 08:58 UTC
[asterisk-users] TDM400P FXO not seeing ringing after software update
A customer has an Asterisk box with two TDM400P cards, running A at H 2.8, which has Asterisk 1.2.7.1 and Zaptel 1.2.5. This has been running ok for a while, with only some small issues. They have FXO ports going to analogue POTS (UK standard) lines, and SIP phones for extensions. I just tried updating Zaptel to 1.2.26 and Asterisk to 1.2.30.1, and although the update appeared to go ok, the system would no longer detect incoming calls. It appeared not to see the ringing signal. Outgoing calls over the PSTN lines still worked fine. Does anyone know if there have been changes in the 1.2 series that affects ring detection on the TDM400P FXO ports? Any critical settings in zaptel.conf or zapata.conf? For now, I've had to revert to the original versions, in which ringing once again works fine. Cheers Tony -- Tony Mountifield Work: tony at softins.co.uk - http://www.softins.co.uk Play: tony at mountifield.org - http://tony.mountifield.org
Ira
2008-Jul-28 17:10 UTC
[asterisk-users] TDM400P FXO not seeing ringing after software update
At 01:58 AM 7/28/2008, you wrote:>Does anyone know if there have been changes in the 1.2 series that >affects ring detection on the TDM400P FXO ports? Any critical settings >in zaptel.conf or zapata.conf?Some of us know there were changes because we've experienced the same failure. Ira
Drew Gibson
2008-Jul-28 18:00 UTC
[asterisk-users] TDM400P FXO not seeing ringing after software update
Tony Mountifield wrote:> A customer has an Asterisk box with two TDM400P cards, running A at H 2.8, > which has Asterisk 1.2.7.1 and Zaptel 1.2.5. This has been running ok > for a while, with only some small issues. They have FXO ports going > to analogue POTS (UK standard) lines, and SIP phones for extensions. > > I just tried updating Zaptel to 1.2.26 and Asterisk to 1.2.30.1, and > although the update appeared to go ok, the system would no longer > detect incoming calls. It appeared not to see the ringing signal. > Outgoing calls over the PSTN lines still worked fine. > > Does anyone know if there have been changes in the 1.2 series that > affects ring detection on the TDM400P FXO ports? Any critical settings > in zaptel.conf or zapata.conf? > > For now, I've had to revert to the original versions, in which ringing > once again works fine. > > Cheers > Tony >YES! I have a 4xFXO board in Singapore. Having tried many various settings, etc., I had assumed it was the I18N of the ringtones and signalling. Does anyone know at which rev the issue appeared? regards, Drew -- Drew Gibson Systems Administrator OANDA Corporation www.oanda.com
Drew Gibson
2008-Aug-13 20:23 UTC
[asterisk-users] TDM400P FXO not seeing ringing after software update
Kevin P. Fleming wrote:> Tony Mountifield wrote: > > >> My guess is that 1.2.24 will work, which was at revision 3842 of the tree >> (rev 3741 of wctdm.c). The next change to wctdm.c (rev 4126) looks innocuous >> enough, but the follwing two (revs 4128 and 4132) look likely culprits, >> from looking at the areas of code that they affect. >> > > It is very likely 4128, based on the code it affects and the behavior > that is being reported. Please let us know as soon as you can (anyone > who has this problem), if reverting r4128 from current Zaptel branch 1.2 > SVN solves the problem. > >Did anyone find a fix for this (besides down-grading to 1.2.24)? regards, Drew -- Drew Gibson Systems Administrator OANDA Corporation www.oanda.com
Tony Mountifield
2008-Aug-13 21:24 UTC
[asterisk-users] TDM400P FXO not seeing ringing after software update
In article <48A342A6.8090208 at oanda.com>, Drew Gibson <drew at oanda.com> wrote:> Kevin P. Fleming wrote: > > Tony Mountifield wrote: > > > >> My guess is that 1.2.24 will work, which was at revision 3842 of the tree > >> (rev 3741 of wctdm.c). The next change to wctdm.c (rev 4126) looks innocuous > >> enough, but the follwing two (revs 4128 and 4132) look likely culprits, > >> from looking at the areas of code that they affect. > > > > It is very likely 4128, based on the code it affects and the behavior > > that is being reported. Please let us know as soon as you can (anyone > > who has this problem), if reverting r4128 from current Zaptel branch 1.2 > > SVN solves the problem. > > Did anyone find a fix for this (besides down-grading to 1.2.24)?I believe Russell did apply a fix to the 1.2 branch of zaptel (rev 4442), but I have been too busy with other things to try it out. There has not been a zaptel release since the fix was committed. Cheers Tony -- Tony Mountifield Work: tony at softins.co.uk - http://www.softins.co.uk Play: tony at mountifield.org - http://tony.mountifield.org