Summary:ASTERISK-11231: Hangup request recieved on q931 but asterisk does not hangup the channel
Reporter:Khurram Dar (khurramdar)Labels:
Date Opened:2008-01-14 01:52:39.000-0600Date Closed:2011-06-07 14:02:43
Versions:Frequency of
Environment:Attachments:( 0) case-1.txt
( 1) case-2.txt
( 2) case-3.txt
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.


We have an Asterisk based VAS setup. We use an 8 PRI Sangoma A104 card.

We use:
CentOS 5   v2.6.18-8.el5
wanpipe    v3.2..1
libpri     v1.4.3
zaptel     v1.4.7.1
asterisk   v1.4.16.2
Comments:By: Joshua C. Colp (jcolp) 2008-01-14 08:33:27.000-0600

Please provide logs so Matt can take a look at this.

By: Matthew Fredrickson (mattf) 2008-02-18 14:35:51.000-0600

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.

By: Jason Parker (jparker) 2008-03-27 15:29:30

Closing per comment from mattf.