[Home]

Summary:DAHLIN-00213: Dahdi got hangup, cause 100
Reporter:nquesada (nquesada)Labels:
Date Opened:2010-09-24 15:53:33Date Closed:2010-10-15 16:02:34
Priority:MinorRegression?No
Status:Closed/CompleteComponents:General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:
I have a Digium 210 conected one port with cisco 5300 an the other port with a channelbank orion E1 GSM gateway


calls hung up with    cause 100


-- Accepting call from '' to '00XXXXXXXXX' on channel 1/31, span 1
   -- Executing [00XXXXXXXXX@from-CISCO:1] Dial("DAHDI/31-1", "DAHDI/R2/e00XXXXXXXXX") in new stack
-- Making new call for cref 32788
   -- Requested transfer capability: 0x00 - SPEECH

> DL-DATA request
> Protocol Discriminator: Q.931 (8)  len=36
> TEI=0 Call Ref: len= 2 (reference 20/0x14) (Sent from originator)
> Message Type: SETUP (5)
TEI=0 Transmitting N(S)=35, window is open V(A)=35 K=7

> Protocol Discriminator: Q.931 (8)  len=36
> TEI=0 Call Ref: len= 2 (reference 20/0x14) (Sent from originator)
> Message Type: SETUP (5)
> [04 03 80 90 a3]
> Bearer Capability (len= 5) [ Ext: 1  Coding-Std: 0  Info transfer capability: Speech (0)
>                              Ext: 1  Trans mode/rate: 64kbps, circuit-mode (16)
>                                User information layer 1: A-Law (35)
> [18 04 e9 82 83 8b]
> Channel ID (len= 6) [ Ext: 1  IntID: Explicit  Other(PRI)  Spare: 0  Exclusive  Dchan: 0
>                       ChanSel: As indicated in following octets
>                       Ext: 1  DS1 Identifier: 2  
>                       Ext: 1  Coding: 0  Number Specified  Channel Type: 3
>                       Ext: 1  Channel: 11 Type: NET]
> [6c 02 21 81]
> Calling Number (len= 4) [ Ext: 0  TON: National Number (2)  NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1)
>                           Presentation: Presentation permitted, user number passed network screening (1)  '' ]
> [70 0e a1 30 30 35 30 35 38 39 33 36 31 30 30 38]
> Called Number (len=16) [ Ext: 1  TON: National Number (2)  NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1)  '00XXXXXXXXX' ]
q931.c:5289 q931_setup: Call 32788 enters state 1 (Call Initiated).  Hold state: Idle
   -- Called R2/e00XXXXXXXXX

< Protocol Discriminator: Q.931 (8)  len=9
< TEI=0 Call Ref: len= 2 (reference 20/0x14) (Sent to originator)
< Message Type: RELEASE COMPLETE (90)
< [08 02 84 e4]
< Cause (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0)  Spare: 0  Location: Public network serving the remote user (4)
<                  Ext: 1  Cause: Invalid information element contents (100), class = Protocol Error (e.g. unknown message) (6) ]
Received message for call 0x9ce3478 on 0xb7da3950 TEI/SAPI 0/0, call->pri is 0xb7da3950 TEI/SAPI 0/0
-- Processing IE 8 (cs0, Cause)
q931.c:7716 post_handle_q931_message: Call 32788 enters state 0 (Null).  Hold state: Idle
   -- Channel 2/11, span 2 got hangup, cause 100
q931_hangup: other hangup
NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Null, peerstate Null, hold-state Idle
NEW_HANGUP DEBUG: Destroying the call, ourstate Null, peerstate Null, hold-state Idle
   -- Hungup 'DAHDI/42-1'
 == Everyone is busy/congested at this time (1:0/0/1)
   -- Auto fallthrough, channel 'DAHDI/31-1' status is 'CHANUNAVAIL'
   -- Hungup 'DAHDI/31-1'

****** ADDITIONAL INFORMATION ******


group=1
switchtype=euroisdn
signalling=pri_cpe
echocancel=yes
context=from-cisco
channel => 1-15 , 17-31

group=2
switchtype=euroisdn
echocancel=yes
signalling=pri_net
context=to-channelbank
channel => 32-46 , 48-62

span=1,1,0,ccs,hdb3
bchan=1-15,17-31
dchan=16
echocanceller=mg2,1-15,17-31

span=2,0,0,ccs,hdb3,crc4
bchan=32-46,48-62
dchan=47
echocanceller=mg2,32-46,48-62
CENTos 5.2
ASterisk 1.6.2
libpri-1.4.11.3
DAHDI Tools Version - 2.4.0
DAHDI Version: 2.4.0
Echo Canceller(s): MG2
Configuration
SPAN 1: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 2: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
Comments:By: Shaun Ruffell (sruffell) 2010-09-24 18:26:43

Could you add some information about why specifically you think this is a bug in DAHDI?
By: nquesada (nquesada) 2010-09-24 19:53:28

i was two problems one fixed issue id=18030, and the other is it , but im not sure that it is a compatibility problem with digium and orion E1 gsm gateway.
By: Shaun Ruffell (sruffell) 2010-10-15 16:02:34

Open this back up if you think there is a specific problem in the drivers.  Otherwise, I recommend using asterisk-users mailing list if your looking for general support.