[asterisk-bugs] [Asterisk 0011762]: Hangup request recieved on q931 but asterisk does not hangup the channel

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11762 
====================================================================== 
Reported By:                khurramdar
Assigned To:                mattf
====================================================================== 
Project:                    Asterisk
Issue ID:                   11762
Category:                   Channels/chan_zap
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.16.2 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             01-14-2008 01:52 CST
Last Modified:              02-18-2008 14:35 CST
====================================================================== 
Summary:                    Hangup request recieved on q931 but asterisk does
not hangup the channel
Description: 
We have noticed that some times, customer hang-up the channel but asterisk
does not release it and continue serving it hence resulting in mismatch in
cdrs between and us and operator.

In last 15-20 days we are trying to analyze various logs and found
following three situations related to the above problem. I am not sure
whether all of them are related to the same problem or not.

1. in the intense PRI log we have seen that disconnect request recieved on
q931 from operator side but asterisk continue with the calls, after 3 sec
operator again sends release request which gain was ignored by asterisk and
after 40 sec operator again sends the release message which was acknowlgded
by asterisk and confiem to release the channel but actually hangup channel
after 5 minutes

2. in few cases we could not find any hangup request from operator on q931
in the pri intense log even though the caller has actually ended the call

3. last case is a bit different where we have taken the verbose log for
few calls where dial plan (or may be asterisk thread for that call) goes to
sleep. Just to explain this point further, in our dial plan when a call
gets connected to asterisk first it should play welcome prompt and after
that it should call an agi (to check the caller status), welcome prompt is
about 7 sec long hence in normal calls agi gets executed automatically
after 7 sec from the time call gets connected. What we have seen is that
there is gap of around 5 minutes between welcome prompt and when dial plan
call the agi. During this period the caller disconnected the call but
asterisk move to the next level after 5 minutes and continue serving the
channel as if the caller is present.

I am not sure whether they all are inter-related issues or not. Luckily
last night my own call experience the same thing where i disconnected the
call but asterisk didnot released the channel. What i experienced was that
suddenly the call went in silence and after that even though i disconnected
it asterisk never released it. I also experienced after that when i again
tried calling my call gets connected (in asterisk log) but i could not hear
anything.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0011758 Hangup request recieved on q931 but ast...
====================================================================== 

---------------------------------------------------------------------- 
 mattf - 02-18-08 14:35  
---------------------------------------------------------------------- 
PRI protocol problems are something that is handled (at least for Digium
cards) principally through Digium Technical Support.  You may also wait for
someone here to see if anyone can help or attempt to contact your vendor
about this problem. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-18-08 14:35  mattf          Note Added: 0082505                          
======================================================================