asterisk users - Sep 2005 - TDM400P not detecting hangup and not hanging up

Canuck15,

No, I hadn't played with the gains. But I've now done so and no
difference
unfortunately. Thanks for the suggestion though.

I have discovered that after Asterisk has answered the call and the remote
caller has hung up, if I lift the receiver on a phone connected to the line
(in parallel with Asterisk), Asterisk then DOES instantly hang up.

Would it be reasonable to assume the voltage drop caused by lifting the
receiver causes this? It only happens when I set the BATT_(whatever it was)
in wcfxs.c to 8. If I set it to a lower level, Asterisk won't even answer at
all and so nothing works.

Also possibly relevant: When I disconnect Asterisk completely from the
equation and just answer the remote caller myself, when the remote caller
hangs up the line does not actually drop: Instead I just get a
"disconnect"
(or number unobtainable) tone. Could this be the problem (i.e. there's no
actual voltage drop happening to signal the call has ended)? Or is there
some sort of other change in the line that I wouldn't detect audibly?

Could it be that any inaudible voltage drop might be happening too quickly
for zaptel to detect? What might I change in the source code to see if this
is the case? 

Does nobody else in the UK use these cards? I'm sure that's not the
case. So
if you do use them, please stand up and be counted -- did you have to make
any adjustments or did it just work "out of the box"?

Incidentally, when callprogress=yes, Asterisk goes nuts and keeps detecting
strange things happening: Essentially every time the CLI comes through
(polarity reversal) between rings, asterisk picks up and hangs up (though
not physically - the caller hears ringing).
>This may or may not be related but have you tried adjusting your RX and TX
>gains?  I see both are at the default (0.0) which leads me to believe you
>have not.  Search the Asterisk Wiki for the procedure.
Stevanus,

I think the hanguponpolarity switch is relevant to a patch to to Zaptel that
may or may not have actually been added to the released version. I'm not
sure. However, thanks for pointing this out -- I've tried it too and
didn't
get anywhere.
>I have similar problems like you.
>In the past, I did adjusted my RX and TX gain, but didn't know if it has
>been optimal yet.
>Fxotune is seemed do not working, perhaps caused of my asterisk's
version (
>I use stable v1.0)..
>
>Just curious, is rx and tx gain really a sole setting option here in order
>to make things the way it's meant to be? Or is there others?
>FYI, my tdm04b occasionally don't detect call-in as well as hangup
signal.
>
>I've searched in the wiki and have activated hanguponpolarity swicth. 
>But I don't notice any difference at all.
>
>Any help would be greatly appreciated. (I've asked this in another
thread,
>but got no respon :( )


SUMMARY OF THREAD: hardware=TDM400P 2xFXS, 1xFXO. Location=UK. *ver=1.0.9.
Zaptel 1.0.9.1. Problem: Asterisk does not detect that the remote caller has
hung up and carries on as though nothing has happened.

> Canuck15,
>
> No, I hadn't played with the gains. But I've now done so and no
difference
> unfortunately. Thanks for the suggestion though.
>
> I have discovered that after Asterisk has answered the call and the remote
> caller has hung up, if I lift the receiver on a phone connected to the 
> line
> (in parallel with Asterisk), Asterisk then DOES instantly hang up.
>
> Would it be reasonable to assume the voltage drop caused by lifting the
> receiver causes this? It only happens when I set the BATT_(whatever it 
> was)
> in wcfxs.c to 8. If I set it to a lower level, Asterisk won't even
answer
> at
> all and so nothing works.
>
> Also possibly relevant: When I disconnect Asterisk completely from the
> equation and just answer the remote caller myself, when the remote caller
> hangs up the line does not actually drop: Instead I just get a 
> "disconnect"
> (or number unobtainable) tone. Could this be the problem (i.e. there's
no
> actual voltage drop happening to signal the call has ended)? Or is there
> some sort of other change in the line that I wouldn't detect audibly?
>
> Could it be that any inaudible voltage drop might be happening too quickly
> for zaptel to detect? What might I change in the source code to see if 
> this
> is the case?
>
> Does nobody else in the UK use these cards? I'm sure that's not the
case.
> So
> if you do use them, please stand up and be counted -- did you have to make
> any adjustments or did it just work "out of the box"?
>
> Incidentally, when callprogress=yes, Asterisk goes nuts and keeps 
> detecting
> strange things happening: Essentially every time the CLI comes through
> (polarity reversal) between rings, asterisk picks up and hangs up (though
> not physically - the caller hears ringing).
>
>>This may or may not be related but have you tried adjusting your RX and
TX
>>gains?  I see both are at the default (0.0) which leads me to believe
you
>>have not.  Search the Asterisk Wiki for the procedure.
>
> Stevanus,
>
> I think the hanguponpolarity switch is relevant to a patch to to Zaptel 
> that
> may or may not have actually been added to the released version. I'm
not
> sure. However, thanks for pointing this out -- I've tried it too and 
> didn't
> get anywhere.
>
>>I have similar problems like you.
>>In the past, I did adjusted my RX and TX gain, but didn't know if it
has
>>been optimal yet.
>>Fxotune is seemed do not working, perhaps caused of my asterisk's
version
>>(
>>I use stable v1.0)..
>>
>>Just curious, is rx and tx gain really a sole setting option here in
order
>>to make things the way it's meant to be? Or is there others?
>>FYI, my tdm04b occasionally don't detect call-in as well as hangup
signal.
>>
>>I've searched in the wiki and have activated hanguponpolarity
swicth.
>>But I don't notice any difference at all.
>>
>>Any help would be greatly appreciated. (I've asked this in another
thread,
>>but got no respon :( )
>
>
>
> SUMMARY OF THREAD: hardware=TDM400P 2xFXS, 1xFXO. Location=UK. *ver=1.0.9.
> Zaptel 1.0.9.1. Problem: Asterisk does not detect that the remote caller 
> has
> hung up and carries on as though nothing has happened.
Disconnect Supervision/Hangup Detection has been discussed quite extensively 
on this list. But considering the information you provide and given that you 
tried to play with BATT_THRESH setting, I tend to think that there may be 
other problems. My concern would be the opermode setting of FXO modules.

So I would get a fresh copy of asterisk and zaptel (and would not play with 
BATT_THRESH). I think the default opermode is FCC, so I would change it to 
UK. If it still does not work, I would try hanguponpolarityswitch (perhaps 
your telco provides disconnect supervision). If it still doesn't work, my 
only option would be busydetect.

Hope this helps...