[asterisk-bugs] [DAHDI-linux 0014633]: Hangup call, but unrequested
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Mar 17 04:19:49 CDT 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=14633
======================================================================
Reported By: igorcarneiro
Assigned To:
======================================================================
Project: DAHDI-linux
Issue ID: 14633
Category: wct4xxp
Reproducibility: random
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 2009-03-09 13:09 CDT
Last Modified: 2009-03-17 04:19 CDT
======================================================================
Summary: Hangup call, but unrequested
Description:
The DAHDI Hangup the call, in the way of the calling .
asterisk -rx 'pri intensive debug span 1'
------------------------------------------------------------------------
[1e 02 84 88]
Progress Indicator (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0:
0 Location: Public network serving the remote user (4)
Ext: 1 Progress Description: Inband information
or appropriate pattern now available. (8) ]
-- Processing IE 30 (cs0, Progress Indicator)
NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Active, peerstate Active
q931.c:3009 q931_disconnect: call 197 on channel 6 enters state 11
(Disconnect Request)
Protocol Discriminator: Q.931 (8) len=9
Call Ref: len= 2 (reference 197/0xC5) (Terminator)
Message type: DISCONNECT (69)
======================================================================
----------------------------------------------------------------------
(0101851) tzafrir (manager) - 2009-03-17 04:19
http://bugs.digium.com/view.php?id=14633#c101851
----------------------------------------------------------------------
Is this issue reproducable? If so: how do you reproduce it?
What is the immediate cause of the hangup?
To see that we probably need debug-level logging of Asterisk:
1. In logger.conf enable the 'full' sample line (or otherwise get 'debug'
logged to some file)
2. If you changed logger.conf: run in the CLI: logger reload
3. in the CLI: core set debug 5
4. What do you see in /var/log/asterisk/full for that event?
Issue History
Date Modified Username Field Change
======================================================================
2009-03-17 04:19 tzafrir Note Added: 0101851
======================================================================
More information about the asterisk-bugs
mailing list