asterisk users - Nov 2004 - FXO module in TDM400P (UK, BT) - Hangup detection failing

Hi,

I'm a UK-based * newbie with a BT line on a PIII 2GHz 1Gb Fedora Core 2  
linux box, fully patched up, experiencing a little difficulty with *  
(both CVS V1-0 and yesterday's CVS HEAD). I've been through the  
archives and even popped on to freenode/#asterisk for a while, but no  
firm resolution presented itself. Last relevant post appears to have an  
unresolved cliffhanger:  
http://lists.digium.com/pipermail/asterisk-users/2004-September/ 
061518.html

I had an X100P as my PSTN link and that was working fine for taking and  
making calls, but of course no caller ID (Plenty of "Didn't finish  
Caller-ID spill.  Cancelling" and that's about it).

Needing CID for my application, I procured an FXO module for my TDM400P  
which already had one FXS module in it (also working fine, happily  
shoving and receiving CID info around between my SIP soft phones and  
the Zyxel SIP hardphone).

The wcfxs module is correctly installed with opermode=uk (dmesg  
confirms this), and polarity CID detection works a treat. Call routing  
is fine and, naturally, none of the SIP stuff has broken :-)

HOWEVER, the FXO module isn't detecting remote party clear down events.

Two example cases:

Zap/4-1 (the FXO module on the TDM400P) detects ring because someone is  
dialling my BT line. My dialplan displays CID info to console for  
debugging and then dials my SIP softphone (SIP/stripes), SIP hardphone  
(SIP/zyxel) and Zap hardphone (Zap/1-1).

1/ If the incoming party clears down before one of the internal  
extensions answers, they continue to ring (* hasn't logged the remote  
hang up event on Zap/4-1) and dead air is heard should they  
subsequently answer.

2/ If the incoming party stays on long enough for voicemail to kick in,  
then I get a recording comprising their message, pop/click, 2secs  
silence, 5secs solid tone, pop/click, followed by dead air (and silence  
detection is the only thing stopping the message hitting the 120 second  
maximum message length ceiling)

Both of these cases are consistent with how I understand * to work  
should the channel not notice Zap/4-1 going down - bully for me, bummer  
for operational use ;-)


Speaking with the ever-so helpful folk on freenode/#asterisk, I've  
tried loopstart signalling (nice idea - failed miserably where remote  
clear down made * think that the remote party was trying to transfer  
calls - lots of MOH messages and 's' priority of the context invoked);  
I've tried tweaking indications.conf to make *'s notion of
'busy' for
my line match what is being heard as the tone, but that hasn't worked  
and incoming calls still stay 'connected' until the voicemail's
silence
detection cuts them off.

I can live with voice messages being 9 seconds longer than they need to  
be; I can't, though, live with incoming callers that hangup before  
anything answers still resulting in the internal extensions being  
signalled.

I don't have a lighted keypad, but have seen a deflection on a  
multimeter across A/B wire to suggest that the phone company are  
signalling remote clear down with a polarity reversal.  I'm told  
(again, kind folk on irc) that BT do use supervised disconnects and so  
I am doing the right thing using fxs_ks signalling.

I guess my question is: does anyone have polarity reversal hangup  
detection working on a BT line with an fxo module in a TDM400P?

If so - your direction would be most greatly appreciated.   I've posted  
slightly censored versions of my config to http://ermy.net/senast/, in  
case that might help.


Many thanks in advance,

Mark/

--
// if it doesn't go woof when you light it, you ain't dun it right.

Hi Mark,
Are you based in Hastings by any chance (Senlac and all that)? I have similar
problems with the voicemail but not with users dialing in with extensions
ringing. I do have a problem that "zap show channel" shows the Zap
line as OffHook after a call and it never goes back to OnHook and asterisk gets
confused about channel status.

R's
Ian





From: StrUK
Sent: Tue 02/11/2004 22:58
To: asterisk-users@lists.digium.com
Subject: [Asterisk-Users] FXO module in TDM400P (UK, BT) - Hangup detection
failing


Hi,

I'm a UK-based * newbie with a BT line on a PIII 2GHz 1Gb Fedora Core 2  
linux box, fully patched up, experiencing a little difficulty with *  
(both CVS V1-0 and yesterday's CVS HEAD). I've been through the  
archives and even popped on to freenode/#asterisk for a while, but no  
firm resolution presented itself. Last relevant post appears to have an  
unresolved cliffhanger:  
http://lists.digium.com/pipermail/asterisk-users/2004-September/ 
061518.html

I had an X100P as my PSTN link and that was working fine for taking and  
making calls, but of course no caller ID (Plenty of "Didn't finish  
Caller-ID spill.  Cancelling" and that's about it).

Needing CID for my application, I procured an FXO module for my TDM400P  
which already had one FXS module in it (also working fine, happily  
shoving and receiving CID info around between my SIP soft phones and  
the Zyxel SIP hardphone).

The wcfxs module is correctly installed with opermode=uk (dmesg  
confirms this), and polarity CID detection works a treat. Call routing  
is fine and, naturally, none of the SIP stuff has broken :-)

HOWEVER, the FXO module isn't detecting remote party clear down events.

Two example cases:

Zap/4-1 (the FXO module on the TDM400P) detects ring because someone is  
dialling my BT line. My dialplan displays CID info to console for  
debugging and then dials my SIP softphone (SIP/stripes), SIP hardphone  
(SIP/zyxel) and Zap hardphone (Zap/1-1).

1/ If the incoming party clears down before one of the internal  
extensions answers, they continue to ring (* hasn't logged the remote  
hang up event on Zap/4-1) and dead air is heard should they  
subsequently answer.

2/ If the incoming party stays on long enough for voicemail to kick in,  
then I get a recording comprising their message, pop/click, 2secs  
silence, 5secs solid tone, pop/click, followed by dead air (and silence  
detection is the only thing stopping the message hitting the 120 second  
maximum message length ceiling)

Both of these cases are consistent with how I understand * to work  
should the channel not notice Zap/4-1 going down - bully for me, bummer  
for operational use ;-)


Speaking with the ever-so helpful folk on freenode/#asterisk, I've  
tried loopstart signalling (nice idea - failed miserably where remote  
clear down made * think that the remote party was trying to transfer  
calls - lots of MOH messages and 's' priority of the context invoked);  
I've tried tweaking indications.conf to make *'s notion of
'busy' for
my line match what is being heard as the tone, but that hasn't worked  
and incoming calls still stay 'connected' until the voicemail's
silence
detection cuts them off.

I can live with voice messages being 9 seconds longer than they need to  
be; I can't, though, live with incoming callers that hangup before  
anything answers still resulting in the internal extensions being  
signalled.

I don't have a lighted keypad, but have seen a deflection on a  
multimeter across A/B wire to suggest that the phone company are  
signalling remote clear down with a polarity reversal.  I'm told  
(again, kind folk on irc) that BT do use supervised disconnects and so  
I am doing the right thing using fxs_ks signalling.

I guess my question is: does anyone have polarity reversal hangup  
detection working on a BT line with an fxo module in a TDM400P?

If so - your direction would be most greatly appreciated.   I've posted  
slightly censored versions of my config to http://ermy.net/senast/, in  
case that might help.


Many thanks in advance,

Mark/

--
// if it doesn't go woof when you light it, you ain't dun it right.

_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

------------------------------------------------------------
Mail was checked for spam by the Freeware Edition of No Spam Today!
The Freeware Edition is free for personal and non-commercial use.
You can remove this notice by purchasing a full license! To order
or to find out more please visit: http://www.no-spam-today.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20041103/005d6955/attachment.htm

On Tue, Nov 02, 2004 at 10:58:39PM +0000, StrUK wrote:
<snip other information> 
> I guess my question is: does anyone have polarity reversal hangup  
> detection working on a BT line with an fxo module in a TDM400P?
Testing with my fxo module shows that it takes about 8 seconds from
pressing hangup on the mobile phone before hangup is detected in
asterisk (maybe this relates to your 9 seconds).  I'm not sure if this
is when the local exchange sends the polarity reversal or if asterisk is
detecting a hangup in some other way.  I have busydetect=no and
callprogress=no so I'm (AFAIK) not using any "fake disconnect
functions"
as per the keypad lights page[1].

If I pick up the phone during the 8 seconds I get a usable dialtone,
which might be worrying if I didn't want people calling certain numbers.
This seems to indicate that the local exchange knows that the mobile has
hungup, as it wouldn't give dialtone in the middle of call.  So perhaps
I dont have polarity reversal hangup detection working, but HTH anyway.

I'm not using the fxo callerid and asterisk is from cvs checkout date
14-Aug-2004 (as downloaded from bri-stuff.0.1.0-RC4a)

my zapata config for the fxo module:

group=1
context=fxo
signalling=fxs_ks
usecallerid=no
callwaitingcallerid=no
threewaycalling=no
cancallforward=no
transfer=no
immediate=no
callwaiting=no
usecallingpres=no
callreturn=no
echocancel=yes
echocancelwhenbridged=no
echotraining=800
rxgain=0.0
txgain=2.0
busydetect=no
callprogress=no
channel=6

[1]
http://www.voip-info.org/tiki-index.php?page=Asterisk%20Disconnect%20Supervision

* Ian D. Wlloughby (Wed Nov 3 07:42:03 CST 2004)
>
> What rev of the TDM board do you have?
Revision C from memory (i'm 200mi away from the house today).  I'll
confirm when I'm back tonight.

If it will help, I can provide symptomatic data for your support call


Cheers,

Mark/

I am based in New Zealand and am experiencing the same problem as referred to in
the post "FXO module in TDM400P (UK, BT) - Hangup detection failing"
from 2 November 2004 i.e. Zap/4 (being the FXO module) not detecting hangup on
the PSTN line if the call is not answered on a PABX extension.



Has anyone managed to find a resolution to the problem?



For information:

Digium TDM400P with FXS on Zap 1 & 2 and FXO on Zap 3 & 4.

CVS-v1-0-01/24/05

Using fxs_ks signalling



Regards



Cameron
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20050306/340bb806/attachment.htm