[asterisk-users] Asterisk DIAL() premature timeout on a PRI trunk to legacy PBX

[Tzafrir Cohen]

On Thu, Sep 13, 2007 at 11:55:59PM -0700, Vieri wrote:
> Thank you,
> I did what you mentioned below.
> It seems that I'm getting a hangupcause of 0 which I
> believe is "not defined".
> Is Alcatel the first party that is trying to
> disconnect or is it Asterisk? (Not sure how to
> interpret the debug info I'm posting below)
> 
> Whether it's Alcatel or Asterisk, what could be the
> actual cause? (or where should I start looking?)
> 
> Thanks
> 
> INF-VOIP*CLI> pri debug span 1
> Enabled debugging on span 1
>     -- Executing NoOp("SIP/4053-083189e8", "[ALCATEL TEST] Start") in new stack
>     -- Executing Dial("SIP/4053-083189e8", "Zap/g1/5900") in new stack
> 1 -- Making new call for cr 32781
>     -- Requested transfer capability: 0x00 - SPEECH
> 1 > Protocol Discriminator: Q.931 (8)  len=32
> 1 > Call Ref: len= 2 (reference 13/0xD) (Originator)
> 1 > Message type: SETUP (5)
> 1 > [04 03 80 90 a3]
> 1 > Bearer Capability (len= 5) [ Ext: 1  Q.931 Std: 0  Info transfer capability: Speech (0)
> 1 >                              Ext: 1  Trans mode/rate: 64kbps, circuit-mode (16)
> 1 >                              Ext: 1  User information layer 1: A-Law (35)
> 1 > [18 04 e9 81 83 81]
> 1 > Channel ID (len= 6) [ Ext: 1  IntID: Explicit, PRI Spare: 0, Exclusive Dchan: 0
> 1 >                        ChanSel: Reserved
> 1 >                       Ext: 1  DS1 Identifier: 1
> 1 >                       Ext: 1  Coding: 0   Number Specified   Channel Type: 3
> 1 >                       Ext: 1  Channel: 1 ]
> 1 > [6c 06 21 80 34 30 35 33]
> 1 > Calling Number (len= 8) [ Ext: 0  TON: National Number (2)  NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1)
> 1 >                           Presentation: Presentation permitted, user number not screened (0) '4053' ]
> 1 > [70 05 a1 35 39 30 30]
> 1 > Called Number (len= 7) [ Ext: 1  TON: National Number (2)  NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) '5900' ]
> 1 > [a1]
> 1 > Sending Complete (len= 1)
>     -- Called g1/5900
> 1 < Protocol Discriminator: Q.931 (8)  len=10
> 1 < Call Ref: len= 2 (reference 13/0xD) (Terminator)
> 1 < Message type: CALL PROCEEDING (2)
> 1 < [18 03 a9 83 81]
> 1 < Channel ID (len= 5) [ Ext: 1  IntID: Implicit, PRI Spare: 0, Exclusive Dchan: 0
> 1 <                        ChanSel: Reserved
> 1 <                       Ext: 1  Coding: 0   Number Specified   Channel Type: 3
> 1 <                       Ext: 1  Channel: 1 ]
> 1 -- Processing IE 24 (cs0, Channel Identification)
>     -- Zap/1-1 is proceeding passing it to SIP/4053-083189e8
> 1 < Protocol Discriminator: Q.931 (8)  len=5
> 1 < Call Ref: len= 2 (reference 13/0xD) (Terminator)
> 1 < Message type: ALERTING (1)

This is normal, right?

>     -- Zap/1-1 is ringing
>     -- Zap/1-1 is busy

Huh? why is Zap/1-1 suddenly busy?

> 1 NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Call Delivered, peerstate Call Received
> 1 > Protocol Discriminator: Q.931 (8)  len=9
> 1 > Call Ref: len= 2 (reference 13/0xD) (Originator)
> 1 > Message type: DISCONNECT (69)
> 1 > [08 02 81 90]
> 1 > Cause (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0) 0: 0   Location: Private network serving the local user (1)
> 1 >                  Ext: 1  Cause: Normal Clearing (16), class = Normal Event (1) ]

So your side initiation disconnecting?

-- 
               Tzafrir Cohen       
icq#16849755                    jabber:tzafrir at jabber.org
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com       
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir