Displaying 1 result from an estimated 1 matches for "hangupextension".
2007 Mar 29
0
DISCONNECT 41 hangup problem on PRI
...ension...
The CDR is not correct of course and does not match the time of the
"release complete" you see above.
It's very strange behavior because asterisk mentions the
-- Channel 0/22, span 1 got hangup request
-- Channel 0/22, span 1 got hangup
at the right time in the logs but the hangupextension is not triggered
until the global timelimit is reached...? Apparently this only happens
when DISCONNECT 41 is the hangupcause...
Why would asterisk send an ISDN RELEASE COMPLETE frame and then not
hangup the call ?
We are using asterisk 1.4.2 btw. I have also tried svn version of
asterisk and zap...