[Home]

Summary:DAHLIN-00083: Hangup call, but unrequested
Reporter:Igor Marques Carneiro da Silva (igorcarneiro)Labels:
Date Opened:2009-03-09 13:09:48Date Closed:2009-09-30 09:25:06
Priority:MajorRegression?No
Status:Closed/CompleteComponents:wct4xxp
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) digiuminfo-srsergio
( 1) full-srsergio
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)
Comments:By: Joshua C. Colp (jcolp) 2009-03-09 16:26:14

Please provide complete console output with this issue, not just a snippet of PRI intensive debug. A general description of the call scenario would also be useful, along with the DAHDI hardware in use and signaling.
By: Igor Marques Carneiro da Silva (igorcarneiro) 2009-03-10 07:32:23

the problem may be
"[Mar  9 15:14:49] VERBOSE[20204] logger.c: -- Restarting T203 timer"
????????????


cat /proc/dahdi/1
Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" (MASTER) HDB3/CCS/CRC4 ClockSource

  1 TE2/0/1/1 Clear (In use)  (EC: MG2)
  2 TE2/0/1/2 Clear (In use)  (EC: MG2)
  3 TE2/0/1/3 Clear (In use)  (EC: MG2)
  4 TE2/0/1/4 Clear (In use)  (EC: MG2)
  5 TE2/0/1/5 Clear (In use)  (EC: MG2)
  6 TE2/0/1/6 Clear (In use)  (EC: MG2)
  7 TE2/0/1/7 Clear (In use)  (EC: MG2)
  8 TE2/0/1/8 Clear (In use)  (EC: MG2)
  9 TE2/0/1/9 Clear (In use)  (EC: MG2)
 10 TE2/0/1/10 Clear (In use)  (EC: MG2)
 11 TE2/0/1/11 Clear (In use)  (EC: MG2)
 12 TE2/0/1/12 Clear (In use)  (EC: MG2)
 13 TE2/0/1/13 Clear (In use)  (EC: MG2)
 14 TE2/0/1/14 Clear (In use)  (EC: MG2)
 15 TE2/0/1/15 Clear (In use)  (EC: MG2)
 16 TE2/0/1/16 HDLCFCS (In use)
 17 TE2/0/1/17 Clear (In use)  (EC: MG2)
 18 TE2/0/1/18 Clear (In use)  (EC: MG2)
 19 TE2/0/1/19 Clear (In use)  (EC: MG2)
 20 TE2/0/1/20 Clear (In use)  (EC: MG2)
 21 TE2/0/1/21 Clear (In use)  (EC: MG2)
 22 TE2/0/1/22 Clear (In use)  (EC MG2)
 23 TE2/0/1/23 Clear (In use)  (EC: MG2)
 24 TE2/0/1/24 Clear (In use)  (EC: MG2)
 25 TE2/0/1/25 Clear (In use)  (EC: MG2)
 26 TE2/0/1/26 Clear (In use)  (EC: MG2)
 27 TE2/0/1/27 Clear (In use)  (EC: MG2)
 28 TE2/0/1/28 Clear (In use)  (EC: MG2)
 29 TE2/0/1/29 Clear (In use)  (EC: MG2)
 30 TE2/0/1/30 Clear (In use)  (EC: MG2)
 31 TE2/0/1/31 Clear (In use)  (EC: MG2)


my /etc/dahdi/system.conf
-----------------------------------------
# Autogenerated by /usr/sbin/dahdi_genconf on Tue Feb 17 08:45:27 2009 -- do not hand edit
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" (MASTER) HDB3/CCS/CRC4 ClockSource
span=1,1,0,ccs,hdb3,crc4
# termtype: te
bchan=1-15,17-31
dchan=16
echocanceller=mg2,1-15,17-31
alaw=1-15
alaw=17-31
# Span 2: TE2/0/2 "T2XXP (PCI) Card 0 Span 2" HDB3/CCS RED
span=2,2,0,ccs,hdb3
# termtype: te
bchan=32-46,48-62
dchan=47
echocanceller=mg2,32-46,48-62
alaw=32-46
alaw=48-62
# Global data
loadzone = us
defaultzone = us



my /etc/dahdi/init.conf
-------------------------------
#DAHDI_DEV_TIMEOUT=10
# Override settings for xpp_fxloader
#XPP_FIRMWARE_DIR=/usr/share/dahdi
#XPP_HOTPLUG_DISABLED=no



my chan_dahdi.conf
-------------------------
[trunkgroups]
[channels]
context=from-pstn
switchtype=euroisdn
pridialplan=unknown
inbanddisconnect=yes
priindication=inband ; Change by Igor
signalling=pri_cpe
usecallerid=yes
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancelwhenbridged=yes
txgain=-1.0
busydetect=no   ; change by Igor
hanguponpolarityswitch=yes
echocancel = 64
group=1
channel => 1-15,17-31
group=2
channel => 32-46,48-62



the verbose log
--------------------------------------------------------------------------
[Mar  9 15:14:49] VERBOSE[20204] logger.c: -- Restarting T203 timer
[Mar  9 15:14:50] VERBOSE[20204] logger.c:
< [ 02 01 ec 48 08 02 00 c5 45 08 02 81 90 ]
[Mar  9 15:14:50] VERBOSE[20204] logger.c:
< Informational frame:
[Mar  9 15:14:50] VERBOSE[20204] logger.c: < SAPI: 00  C/R: 1 EA: 0
<  TEI: 000        EA: 1
[Mar  9 15:14:50] VERBOSE[20204] logger.c: < N(S): 118   0: 0
< N(R): 036   P: 0
< 9 bytes of data
[Mar  9 15:14:50] VERBOSE[20204] logger.c: Handling message for SAPI/TEI=0/0
[Mar  9 15:14:50] VERBOSE[20204] logger.c: -- ACKing all packets from 35 to (but not including) 36
[Mar  9 15:14:50] VERBOSE[20204] logger.c: -- Since there was nothing left, stopping T200 counter
[Mar  9 15:14:50] VERBOSE[20204] logger.c: -- Stopping T203 counter since we got an ACK
[Mar  9 15:14:50] VERBOSE[20204] logger.c: -- Nothing left, starting T203 counter
[Mar  9 15:14:50] VERBOSE[20204] logger.c: < Protocol Discriminator: Q.931 (8)  len=9
[Mar  9 15:14:50] VERBOSE[20204] logger.c: < Call Ref: len= 2 (reference 197/0xC5) (Originator)
[Mar  9 15:14:50] VERBOSE[20204] logger.c: < Message type: DISCONNECT (69)
[Mar  9 15:14:50] VERBOSE[20204] logger.c: < [08 02 81 90]
[Mar  9 15:14:50] VERBOSE[20204] logger.c: < Cause (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0)  Spare: 0  Location: Private network serving the local user (1)
[Mar  9 15:14:50] VERBOSE[20204] logger.c: <                  Ext: 1  Cause: Normal Clearing (16), class = Normal Event (1) ]
[Mar  9 15:14:50] VERBOSE[20204] logger.c: -- Processing IE 8 (cs0, Cause)
[Mar  9 15:14:50] VERBOSE[20204] logger.c: q931.c:3820 q931_receive: call 197 on channel 5 enters state 12 (Disconnect Indication)
[Mar  9 15:14:50] VERBOSE[20204] logger.c: Sending Receiver Ready (119)
[Mar  9 15:14:50] VERBOSE[20204] logger.c:
> [ 02 01 01 ee ]
[Mar  9 15:14:50] VERBOSE[20204] logger.c:
> Supervisory frame:
[Mar  9 15:14:50] VERBOSE[20204] logger.c: > SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
[Mar  9 15:14:50] VERBOSE[20204] logger.c: > Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
> N(R): 119 P/F: 0
> 0 bytes of data
[Mar  9 15:14:50] VERBOSE[20204] logger.c: -- Restarting T203 timer
[Mar  9 15:14:50] VERBOSE[18514] logger.c: NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Disconnect Indication, peerstate Disconnect Request
[Mar  9 15:14:50] VERBOSE[18514] logger.c: q931.c:2961 q931_release: call 197 on channel 5 enters state 19 (Release Request)
[Mar  9 15:14:50] VERBOSE[18514] logger.c:
> [ 00 01 48 ee 08 02 80 c5 4d 08 02 81 90 ]
[Mar  9 15:14:50] VERBOSE[18514] logger.c:
> Informational frame:
[Mar  9 15:14:50] VERBOSE[18514] logger.c: > SAPI: 00  C/R: 0 EA: 0
>  TEI: 000        EA: 1
[Mar  9 15:14:50] VERBOSE[18514] logger.c: > N(S): 036   0: 0
> N(R): 119   P: 0
> 9 bytes of data
[Mar  9 15:14:50] VERBOSE[18514] logger.c: Stopping T_203 timer
[Mar  9 15:14:50] VERBOSE[18514] logger.c: Starting T_200 timer
[Mar  9 15:14:50] VERBOSE[18514] logger.c: -- Restarting T200 timer
[Mar  9 15:14:50] VERBOSE[18514] logger.c: > Protocol Discriminator: Q.931 (8)  len=9
[Mar  9 15:14:50] VERBOSE[18514] logger.c: > Call Ref: len= 2 (reference 197/0xC5) (Terminator)
[Mar  9 15:14:50] VERBOSE[18514] logger.c: > Message type: RELEASE (77)
[Mar  9 15:14:50] VERBOSE[18514] logger.c: > [08 02 81 90]
[Mar  9 15:14:50] VERBOSE[18514] logger.c: > Cause (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0)  Spare: 0  Location: Private network serving the local user (1)
[Mar  9 15:14:50] VERBOSE[18514] logger.c: >                  Ext: 1  Cause: Normal Clearing (16), class = Normal Event (1) ]
[Mar  9 15:14:50] VERBOSE[20204] logger.c:
By: Tzafrir Cohen (tzafrir) 2009-03-17 04:19:49

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?
By: Igor Marques Carneiro da Silva (igorcarneiro) 2009-03-23 06:38:15

if I put debug=5,
my CPU to lake !!!
not possible put debug 5 ....

and, my log-level is full


By: Sergio Serrano (srsergio) 2009-04-02 04:00:15

We have same problem with an TE220P. I attach digiuminfo-srsergio and full-srsergio for your information. The problem occurs after a time. Restart level 2 and after a timer occurs again.
By: Leif Madsen (lmadsen) 2009-09-08 13:57:30

I'd like to ping this issue and verify that the reporters are seeing the same issue with the latest DAHDI.

I request this since this issue hasn't been updated in quite some time.
By: Leif Madsen (lmadsen) 2009-09-08 13:58:34

Additionally, information is required on how to reproduce the issue. Thanks!
By: Leif Madsen (lmadsen) 2009-09-30 09:25:05

I'm closing this issue as it has been waiting on feedback for more than 2 weeks. If the reporter has additional information that can be submitted, than they are welcome to reopen the issue. Thanks!