[Asterisk-Dev] PRI Q.921 problem (zapata.conf
andzaptel.confconfigurations )
Matt
mattl at xgforce.com
Thu Jul 14 15:53:03 MST 2005
did that suggested change in zapata.conf but still got this when we test dial. seams the switch and * unable to establish communication in q921 dialog so it is repeating several times below.
< [ 02 01 7f ]
< Unnumbered frame:
< SAPI: 00 C/R: 1 EA: 0
< TEI: 000 EA: 1
< M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data
-- Got SABME from network peer.
Sending Unnumbered Acknowledgement
> [ 02 01 73 ]
> Unnumbered frame:
> SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
> M3: 3 P/F: 1 M2: 0 11: 3 [ UA (unnumbered acknowledgement) ]
> 0 bytes of data
-- Restarting T203 counter
-- Restarting T203 counter
< [ 02 01 7f ]
< Unnumbered frame:
< SAPI: 00 C/R: 1 EA: 0
< TEI: 000 EA: 1
< M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data
-- Got SABME from network peer.
Sending Unnumbered Acknowledgement
> [ 02 01 73 ]
> Unnumbered frame:
> SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
> M3: 3 P/F: 1 M2: 0 11: 3 [ UA (unnumbered acknowledgement) ]
> 0 bytes of data
-- Restarting T203 counter
-- Restarting T203 counter
< [ 02 01 7f ]
< Unnumbered frame:
< SAPI: 00 C/R: 1 EA: 0
< TEI: 000 EA: 1
< M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data
-- Got SABME from network peer.
Sending Unnumbered Acknowledgement
> [ 02 01 73 ]
> Unnumbered frame:
> SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
> M3: 3 P/F: 1 M2: 0 11: 3 [ UA (unnumbered acknowledgement) ]
> 0 bytes of data
-- Restarting T203 counter
-- Restarting T203 counter
< [ 02 01 7f ]
< Unnumbered frame:
< SAPI: 00 C/R: 1 EA: 0
< TEI: 000 EA: 1
< M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data
-- Got SABME from network peer.
Sending Unnumbered Acknowledgement
> [ 02 01 73 ]
> Unnumbered frame:
> SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
> M3: 3 P/F: 1 M2: 0 11: 3 [ UA (unnumbered acknowledgement) ]
> 0 bytes of data
-- Restarting T203 counter
-- Restarting T203 counter
< [ 02 01 7f ]
< Unnumbered frame:
< SAPI: 00 C/R: 1 EA: 0
< TEI: 000 EA: 1
< M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data
-- Got SABME from network peer.
Sending Unnumbered Acknowledgement
> [ 02 01 73 ]
> Unnumbered frame:
> SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
> M3: 3 P/F: 1 M2: 0 11: 3 [ UA (unnumbered acknowledgement) ]
> 0 bytes of data
-- Restarting T203 counter
-- Restarting T203 counter
< [ 02 01 7f ]
< Unnumbered frame:
< SAPI: 00 C/R: 1 EA: 0
< TEI: 000 EA: 1
< M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data
-- Got SABME from network peer.
Sending Unnumbered Acknowledgement
> [ 02 01 73 ]
> Unnumbered frame:
> SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
> M3: 3 P/F: 1 M2: 0 11: 3 [ UA (unnumbered acknowledgement) ]
> 0 bytes of data
-- Restarting T203 counter
-- Restarting T203 counter
< [ 02 01 7f ]
< Unnumbered frame:
< SAPI: 00 C/R: 1 EA: 0
< TEI: 000 EA: 1
< M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data
-- Got SABME from network peer.
Sending Unnumbered Acknowledgement
> [ 02 01 73 ]
> Unnumbered frame:
> SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
> M3: 3 P/F: 1 M2: 0 11: 3 [ UA (unnumbered acknowledgement) ]
> 0 bytes of data
-- Restarting T203 counter
-- Restarting T203 counter
< [ 02 01 7f ]
< Unnumbered frame:
< SAPI: 00 C/R: 1 EA: 0
< TEI: 000 EA: 1
< M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data
-- Got SABME from network peer.
Sending Unnumbered Acknowledgement
> [ 02 01 73 ]
> Unnumbered frame:
> SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
> M3: 3 P/F: 1 M2: 0 11: 3 [ UA (unnumbered acknowledgement) ]
> 0 bytes of data
-- Restarting T203 counter
-- Restarting T203 counter
< [ 02 01 7f ]
< Unnumbered frame:
< SAPI: 00 C/R: 1 EA: 0
< TEI: 000 EA: 1
< M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data
-- Got SABME from network peer.
NEW_HANGUP DEBUG: Calling q931_hang-up, ourstate Call Initiated, peerstate Overlap sending
> Protocol Discriminator: Q.931 (8) len=9
> Call Ref: len= 2 (reference 2/0x2) (Originator)
> Message type: DISCONNECT (69)
> [08 02 81 90]
> Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: Private network serving the local user (1)
> Ext: 1 Cause: Normal Clearing (16), class = Normal Event (1) ]
Destroying call '1691f517-14837c46 at 192.168.1.100'
This last q931 part is when we hang up. The q921 SABME part not sure what that means.
Best Regards
From: Dpto. Técnico.
To: Asterisk Developers Mailing List
Sent: Thursday, July 14, 2005 9:21 AM
Subject: Re: [Asterisk-Dev] PRI Q.921 problem (zapata.conf andzaptel.confconfigurations )
In zapata.conf try to change:
channel => 1-15
channel => 17-31
for:
channel =>1-15,17-31
regards
----- Original Message -----
From: Matt
To: Asterisk Developers Mailing List
Sent: Thursday, July 14, 2005 1:20 PM
Subject: Re: [Asterisk-Dev] PRI Q.921 problem (zapata.conf and zaptel.confconfigurations )
zaptel.conf:
only 1st span is connected and used for testing.
span=1,1,0,ccs,hdb3
span=2,0,0,ccs,hdb3
span=3,0,0,ccs,hdb3
span=4,0,0,ccs,hdb3
bchan=1-15
dchan=16
bchan=17-31
loadzone = us
defaultzone=us
zapata.conf:
[trunkgroups]
trunkgroup => 1,16
spanmap => 1,1,1
[channels]
language=en
context=default
switchtype=euroisdn
overlapdial=yes
usecallerid=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
rxgain=0.0
txgain=0.0
group=1
immediate=no
busycount=6
musiconhold=default
context=default
callerid="M100" <(666) 888-8888>
channel => 1-15
channel => 17-31
----- Original Message -----
From: Dpto. Técnico.
To: Asterisk Developers Mailing List
Sent: Thursday, July 14, 2005 3:59 AM
Subject: Re: [Asterisk-Dev] PRI Q.921 problem
Can you put the zapata.conf and zaptel.conf configurations file?
Regards.
----- Original Message -----
From: Matt
To: Asterisk-Users at lists.digium.com
Cc: Asterisk Developers Mailing List
Sent: Thursday, July 14, 2005 10:55 AM
Subject: [Asterisk-Dev] PRI Q.921 problem
hi guys:
we are having Q.921 DLPI problem when trying to establish ISDN layer 2 connection with the E1 switch of the telecom carrier, the carrier switch is unable to establish layer 2 link with our * server with a quad E1 card,
Here is a trace provided by telecom.
U -> N DL_RELEASE_IND
U <- N (PRA_PROTOCOL_CONFIG)
U <- N DL_ESTABLISH_REQ
look like this DL_RELEASE_IND is part of Q.921, but i don't see this in libPRI, is the LIBPRI implementation missing the DLPI part of the Q.921? I also found some free code of Q.921 Q931 on the net, Linux and FreeBSD seams also contains this DLPI in their isdn drivers.
reading the libpri code, it tells it is doing the ua only, no DLPI, shall we add DLPI or we can tell teleco to only use ua layer 2 link establishment?
Any hint of help is greatly appreciated.
Matt
------------------------------------------------------------------------
_______________________________________________
Asterisk-Dev mailing list
Asterisk-Dev at lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
--------------------------------------------------------------------------
_______________________________________________
Asterisk-Dev mailing list
Asterisk-Dev at lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
----------------------------------------------------------------------------
_______________________________________________
Asterisk-Dev mailing list
Asterisk-Dev at lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
------------------------------------------------------------------------------
_______________________________________________
Asterisk-Dev mailing list
Asterisk-Dev at lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20050714/c87515b2/attachment.htm
More information about the asterisk-dev
mailing list