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

[Tzafrir Cohen]

On Sun, Sep 16, 2007 at 02:38:40AM -0700, Vieri wrote:
> 
> --- 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?

You can probably get an answer to that if you enable and log debug
messages of Asterisk .

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