<div>I meant the 24th, yes. Could there be any problem with the support to the AT&T maintenance protocol? We have checked the libpri code, in q931.c, and there appears to be a simple response to messages that have the protocol discriminator set to "AT&T maintenance": a copy with a changed byte.</div> <div> </div> <div> if ((h->pd == 0x3) || (h->pd == 0x43)) {<BR> /* This is the weird maintenance stuff. We majorly<BR> KLUDGE this by changing byte 4 from a 0xf (SERVICE)<BR> to a 0x7 (SERVICE ACKNOWLEDGE) */<BR>
h->raw[h->crlen + 2] -= 0x8;<BR> q931_xmit(pri, h, len, 1);<BR> return 0;<BR> }<BR></div> <div>Could there be cases where a more specific response might be needed?</div> <div> </div> <div><BR><B><I>Michael Collins <mcollins@fcnetwork.com></I></B> escreveu:</div> <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">> I've never seen a PRI dchannel on a T1 on a timeslot other than the<BR>> 24th. Are you sure that it's really on channel 23?<BR><BR>I think he meant channel 23 of channels 0~23, aka the 24th channel.<BR>-MC<BR><BR><BR>> <BR>> Matthew Fredrickson<BR>> <BR>> On Mar 20, 2007, at 8:54 AM, Kanelbullar wrote:<BR>> <BR>> > Thanks for your answer,
Bruno. However, the configuration you provided<BR>> > is for an E1 connection and we are using a T1, having channel 23 as D<BR>> > channel.<BR>> ><BR>> > Bruno De Luca <BDELUCA@FGASOFTWARE.COM>escreveu:d-channel is in midle<BR>> >><BR>> >> bchan=1-15,17-31<BR>> >> dchan=16<BR>> >> loadzone = it<BR>> >> defaultzone = it<BR>> >><BR>> >><BR>> >><BR>> >><BR>> >> Kanelbullar wrote:Hi guys,<BR>> >>><BR>> >>> We are experiencing a problem with a T1 PRI connection. After trying<BR>> >>> a number of variations in the configuration files, the behavior is<BR>> >>> always the same: no B channels come up and the D channel doesn't<BR>> >>> appear to be working well. We can see there are AT&T Maintenance<BR>> >>> messages being exchanged by asterisk and the provider, CONNECT and<BR>> >>>
CONNECT ACKNOWLEDGE, but that doesn't appear to be enough to bring<BR>> >>> the D and B channels properly up. Are there any messages missing?<BR>> >>> When we attempt to make a call, we can see the Q.931 SETUP message<BR>> >>> being sent. But shortly after we are getting a LAPD DISC message,<BR>> >>> which ends up originating a Q.931 DISCONNECT message, terminating<BR>> >>> the call.<BR>> >>><BR>> >>> What could be the problem here?<BR>> >>> * Could there be any configuration issue on our side?<BR>> >>> * Does libpri provide complete support to the AT&T Maintenance<BR>> >>> protocol or could this connection be incompatible?<BR>> >>><BR>> >>> Any help would be highly appreciated.<BR>> >>><BR>> >>> Many thanks in advance,<BR>> >>> Paulo<BR>> >>><BR>> >>>
----------------------------------------------------------------<BR>> >>> PS: Configuration files, messages and pri debug snippets follow<BR>> >>><BR>> >>> zaptel.conf<BR>> >>> ----------------<BR>> >>> loadzone = us<BR>> >>> defaultzone=us<BR>> >>> #Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" PRI_T1<BR>> >>> span=1,0,0,esf,b8zs,crc4<BR>> >>> bchan=1-23<BR>> >>> dchan=24<BR>> >>><BR>> >>> zapata.conf<BR>> >>> ----------------<BR>> >>> [channels]<BR>> >>> group = 0<BR>> >>> usecallingpres = yes<BR>> >>> switchtype = national<BR>> >>> context = inbound<BR>> >>> signalling = pri_cpe<BR>> >>> usecallerid = yes<BR>> >>> channel = 1-23<BR>> >>><BR>> >>> messages<BR>> >>>
--------------<BR>> >>> Mar 19 15:32:23 NOTICE[3306] cdr.c: CDR logging disabled, data will<BR>> >>> be lost.<BR>> >>> Mar 19 15:32:23 WARNING[3306] pbx_ael.c: Unable to open<BR>> >>> '/etc/asterisk/extensions.ael': No such file or directory<BR>> >>> Mar 19 15:32:23 WARNING[3306] pbx.c: Requested contexts didn't get<BR>> >>> merged<BR>> >>> Mar 19 15:33:17 WARNING[3322] chan_zap.c: No D-channels available!<BR>> >>> Using Primary channel 24 as D-channel anyway!<BR>> >>> Mar 19 15:33:58 WARNING[3322] chan_zap.c: No D-channels available!<BR>> >>> Using Primary channel 24 as D-channel anyway!<BR>> >>> Mar 19 15:33:58 WARNING[3366] app_dial.c: Unable to forward voice<BR>> >>> [...]<BR>> >>><BR>> >>> pri debug span<BR>> >>> ----------------------<BR>> >>> > [ 00 01 0a 0a 03 01 00 07 01
01 c0 18 01 ac ]<BR>> >>> > Informational frame:<BR>> >>> > SAPI: 00 C/R: 0 EA: 0<BR>> >>> > TEI: 000 EA: 1<BR>> >>> > N(S): 005 0: 0<BR>> >>> > N(R): 005 P: 0<BR>> >>> > 10 bytes of data<BR>> >>> -- Restarting T203 counter<BR>> >>> Stopping T_203 timer<BR>> >>> Starting T_200 timer<BR>> >>> > Protocol Discriminator: AT&T Maintenance (3) len=10<BR>> >>> > Call Ref: len= 1 (reference 0/0x0) (Originator)<BR>> >>> > Message type: CONNECT (7)<BR>> >>> > [01 01 c0]<BR>> >>> > IE: Change Status (len = 3)<BR>> >>> > [18 01 ac]<BR>> >>> > Channel ID (len= 3) [ Ext: 1 IntID: Implicit, PRI Spare: 0,<BR>> >>> Exclusive Dchan: 1<BR>> >>>
> ChanSel: As indicated in following octets<BR>> >>> ]<BR>> >>> (...)<BR>> >>> < [ 02 01 0a 0c 03 01 00 0f 01 01 c0 18 01 ac ]<BR>> >>> < Informational frame:<BR>> >>> < SAPI: 00 C/R: 1 EA: 0<BR>> >>> < TEI: 000 EA: 1<BR>> >>> < N(S): 005 0: 0<BR>> >>> < N(R): 006 P: 0<BR>> >>> < 10 bytes of data<BR>> >>> -- ACKing all packets from 5 to (but not including) 6<BR>> >>> -- Since there was nothing left, stopping T200 counter<BR>> >>> -- Stopping T203 counter
since we got an ACK<BR>> >>> -- Nothing left, starting T203 counter<BR>> >>> < Protocol Discriminator: AT&T Maintenance (3) len=10<BR>> >>> < Call Ref: len= 1 (reference 0/0x0) (Originator)<BR>> >>> < Message type: CONNECT ACKNOWLEDGE (15)<BR>> >>> < [01 01 c0]<BR>> >>> < IE: Change Status (len = 3)<BR>> >>> < [18 01 ac]<BR>> >>> < Channel ID (len= 3) [ Ext: 1 IntID: Implicit, PRI Spare: 0,<BR>> >>> Exclusive Dchan: 1<BR>> >>> < ChanSel: As indicated in following octets<BR>> >>> ]<BR>> >>> (...)<BR>>
>>> > Protocol Discriminator: Q.931 (8) len=40<BR>> >>> > Call Ref: len= 2 (reference 2/0x2) (Originator)<BR>> >>> > Message type: SETUP (5)<BR>> >>> > [04 03 80 90 a2]<BR>> >>> > Bearer Capability (len= 5) [ Ext: 1 Q.931 Std: 0 Info transfer<BR>> >>> capability: Speech (0)<BR>> >>> > Ext: 1 Trans mode/rate: 64kbps,<BR>> >>> circuit-mode (16)<BR>> >>> > Ext: 1 User information layer 1:<BR>> >>> u-Law (34)<BR>> >>> > [18 03 a9 83 82]<BR>>
>>> > Channel ID (len= 5) [ Ext: 1 IntID: Implicit, PRI Spare: 0,<BR>> >>> Exclusive Dchan: 0<BR>> >>> > ChanSel: Reserved<BR>> >>> > Ext: 1 Coding: 0 Number Specified<BR>> >>> Channel Type: 3<BR>> >>> > Ext: 1 Channel: 2 ]<BR>> >>> > [1e 02 80 83]<BR>> >>> > Progress Indicator (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard<BR>> >>> (0) 0: 0 Location: User (0)<BR>> >>>
> Ext: 1 Progress Description:<BR>> >>> Calling equipment is non-ISDN. (3) ]<BR>> >>> > [6c 06 21 80 37 31 30 30]<BR>> >>> > Calling Number (len= 8) [ Ext: 0 TON: National Number (2) NPI:<BR>> >>> ISDN/Telephony Numbering Plan (E.164/E.163) (1)<BR>> >>> > Presentation: Presentation permitted,<BR>> >>> user number not screened (0) '7100' ]<BR>> >>> > [70 0b a1 35 38 35 34 31 39 37 39 39 35]<BR>> >>> > Called Number (len=13) [ Ext: 1 TON: National Number (2) NPI:<BR>> >>> ISDN/Telephony
Numbering Plan (E.164/E.163) (1) '5854197995' ]<BR>> >>> (...)<BR>> >>> < [ 02 01 53 ]<BR>> >>> < Unnumbered frame:<BR>> >>> < SAPI: 00 C/R: 1 EA: 0<BR>> >>> < TEI: 000 EA: 1<BR>> >>> < M3: 2 P/F: 1 M2: 0 11: 3 [ DISC (disconnect) ]<BR>> >>> < 0 bytes of data<BR>> >>> -- Got Disconnect from peer.<BR>> >>> Sending Unnumbered Acknowledgement<BR>> >>> > [ 02 01 73 ]<BR>> >>> > Unnumbered frame:<BR>> >>> > SAPI: 00 C/R: 1 EA: 0<BR>> >>> > TEI: 000 EA: 1<BR>> >>> > M3: 3 P/F: 1 M2: 0 11: 3 [ UA (unnumbered acknowledgement) ]<BR>> >>> > 0 bytes of data<BR>> >>> -- Restarting T203
counter<BR>> >>> > [ 00 01 00 00 08 02 00 02 45 08 02 81 90 ]<BR>> >>> > Informational frame:<BR>> >>> > SAPI: 00 C/R: 0 EA: 0<BR>> >>> > TEI: 000 EA: 1<BR>> >>> > N(S): 000 0: 0<BR>> >>> > N(R): 000 P: 0<BR>> >>> > 9 bytes of data<BR>> >>> Starting T_200 timer<BR>> >>> > Protocol Discriminator: Q.931 (8) len=9<BR>> >>> > Call Ref: len= 2 (reference 2/0x2) (Originator)<BR>> >>> > Message type: DISCONNECT (69)<BR>> >>> > [08 02 81 90]<BR>> >>> > Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0<BR>> >>> Location: Private network serving the local user (1)<BR>> >>>
> Ext: 1 Cause: Unknown (16), class = Normal Event<BR>> >>> (1) ]<BR>> >>> __________________________________________________<BR>> >>> Fale com seus amigos de graça com o novo Yahoo! Messenger<BR>> >>> http://br.messenger.yahoo.com/<BR>> >>> _______________________________________________ --Bandwidth and<BR>> >>> Colocation provided by Easynews.com -- asterisk-users mailing<BR>> >>> list To UNSUBSCRIBE or update options visit:<BR>> >>> http://lists.digium.com/mailman/listinfo/asterisk-users<BR>> >> _______________________________________________<BR>> >> --Bandwidth and Colocation provided by Easynews.com --<BR>> >><BR>> >> asterisk-users mailing list<BR>> >> To UNSUBSCRIBE or update options visit:<BR>> >>
http://lists.digium.com/mailman/listinfo/asterisk-users<BR>> ><BR>> > __________________________________________________<BR>> > Fale com seus amigos de graça com o novo Yahoo! Messenger<BR>> > http://br.messenger.yahoo.com/<BR>> > _______________________________________________<BR>> > --Bandwidth and Colocation provided by Easynews.com --<BR>> ><BR>> > asterisk-users mailing list<BR>> > To UNSUBSCRIBE or update options visit:<BR>> > http://lists.digium.com/mailman/listinfo/asterisk-users<BR>> <BR>> _______________________________________________<BR>> --Bandwidth and Colocation provided by Easynews.com --<BR>> <BR>> asterisk-users mailing list<BR>> To UNSUBSCRIBE or update options visit:<BR>> http://lists.digium.com/mailman/listinfo/asterisk-users<BR>_______________________________________________<BR>--Bandwidth and Colocation provided by Easynews.com --<BR><BR>asterisk-users mailing list<BR>To
UNSUBSCRIBE or update options visit:<BR>http://lists.digium.com/mailman/listinfo/asterisk-users<BR></BLOCKQUOTE><BR><p> __________________________________________________<br>Fale com seus amigos de graça com o novo Yahoo! Messenger <br>http://br.messenger.yahoo.com/