Bug#491310: asterisk: Problem not solved by downgrade

Christoph Kling ml at familiekling.de
Sun Aug 3 13:42:58 UTC 2008


Hello,

> > I cannot solve the problem by downgrading to 1.4.20, 1.4.19 or 1.4.18. I
> also
> > tried to downgrade zaptel from 1.4.11 to 1.4.10 - problem remains.
> >
> > The error behaviour is different than Louis-David reported it:
> > - there is no error when starting asterisk
> > - but a Dial(...) on a zap device results in:
> >
> >   -- Channel 0/1, span 1 got hangup, cause 18
> 
> (AST_CAUSE_NO_USER_RESPONSE)
> 
> Could you please provide a pri trace 'pri debug span 1') of the call?
> 

Yes, of course, here it is:


debian*CLI> pri debug span 1
Enabled debugging on span 1
    -- Executing [zap at sip-in:1] Answer("SIP/phi-081d2b38", "") in new stack
    -- Executing [zap at sip-in:2] Dial("SIP/phi-081d2b38", "ZAP/1/zap|120") in new stack
1 -- Making new call for cr 130
    -- Requested transfer capability: 0x00 - SPEECH
1 > Protocol Discriminator: Q.931 (8)  len=46
1 > Call Ref: len= 1 (reference 2/0x2) (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 01 89]
1 > Channel ID (len= 3) [ Ext: 1  IntID: Implicit  Other  Spare: 0  Exclusive  Dchan: 0
1 >                        ChanSel: B1 channel
1                          ]
1 > [28 0f 43 68 72 69 73 74 6f 70 68 20 4b 6c 69 6e 67]
1 > Display (len=15) [ Christoph Kling ]
1 > [6c 05 00 81 70 68 69]
1 > Calling Number (len= 7) [ Ext: 0  TON: Unknown Number Type (0)  NPI: Unknown Number Plan (0)
1 >                           Presentation: Presentation permitted, user number passed network screening (1)  'phi' ]
1 > [70 04 80 7a 61 70]
1 > Called Number (len= 6) [ Ext: 1  TON: Unknown Number Type (0)  NPI: Unknown Number Plan (0)  'zap' ]
1 > [7d 02 91 81]
1 > High-layer compatibilty (len= 4) [ 1 0x91 1 0x81 1  ]
1 q931.c:3637 q931_setup: call 130 on channel 1 enters state 1 (Call Initiated)
    -- Called 1/zap
1 No response to SETUP message
1 NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Call Initiated, peerstate Overlap sending
    -- Channel 0/1, span 1 got hangup, cause 18
1 NEW_HANGUP DEBUG: Destroying the call, ourstate Call Initiated, peerstate Overlap sending
1 NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Call Initiated, peerstate Overlap sending
    -- Hungup 'Zap/1-1'
  == Everyone is busy/congested at this time (1:0/0/1)
    -- Executing [zap at sip-in:3] Congestion("SIP/phi-081d2b38", "5") in new stack
  == Spawn extension (sip-in, zap, 3) exited non-zero on 'SIP/phi-081d2b38'
Really destroying SIP dialog '59548DE8F4F8415EABB4985D6D0C3EBF0xc0a8011e' Method: ACK


> This is clearly a different issue than #491810 . #491810 is about
> Asterisk not starting at all.

Sorry for the confusion.


Regards,

--CK
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 183 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20080803/32295dcf/attachment-0001.pgp 


More information about the Pkg-voip-maintainers mailing list