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

[Vieri]

--- Tzafrir Cohen <tzafrir.cohen at xorcom.com> wrote:
> >     -- 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?

I think so because if I initiate a call from ext. 4053
(Asterisk) to ext. 7021 (Bosch PBX) via the Alcatel
PRI (ie.: Asterisk---Alcatel---Bosch)  get the same
ALERT message and the Bosch extension keeps ringing
"forever" until the Asterisk caller hangs up.
I get the following:

    -- Zap/1-1 is proceeding passing it to
SIP/4053-b490d478
1 < Protocol Discriminator: Q.931 (8)  len=9
1 < Call Ref: len= 2 (reference 183/0xB7) (Terminator)
1 < Message type: ALERTING (1)
1 < [1e 02 80 82]
1 < Progress Indicator (len= 4) [ Ext: 1  Coding:
CCITT (ITU) standard (0) 0: 0   Location: User (0)
1 <                               Ext: 1  Progress
Description: Called equipment is non-ISDN. (2) ]
1 -- Processing IE 30 (cs0, Progress Indicator)
    -- Zap/1-1 is ringing


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

right. That's what I'm trying to understand.
Which side is the FIRST to say/report that Zap/1-1 is
busy?
Alcatel or Asterisk?

> > 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?

The Asterisk caller does not actively hang up of
course. Asterisk closes the connection and reports
DISCONNECT and then RELEASE because Zap/1-1 was found
to be BUSY.
Why is that?

In the example I gave above where the Asterisk
extension 4053 makes a call to the Bosch extension
7021 via Alcatel, the caller hangs up willingly and I
see this in the log:

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 183/0xB7) (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) ]
    -- Hungup 'Zap/1-1'

Of course this makes sense.

So the bottom line is: why is Zap/1-1 detected as busy
after just 10-15 seconds of ring time and which side
is actually producing this event?

Thanks,

Vieri



      ____________________________________________________________________________________
Luggage? GPS? Comic books? 
Check out fitting gifts for grads at Yahoo! Search
http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs=bz