Hi, In your zap/dahdi config file, set those to no
facilityenable = no transfer = no Those variable need to be set in order to enable 2BCT. Or, you could try to leave asterisk in the path by recording the conversation. Jimmy > -----Original Message----- > From: [email protected] > Sent: Mon, 12 Apr 2010 22:07:17 -0400 > To: [email protected] > Subject: RE: [on-asterisk] Native ZAP bridge fails on PRI between two > channels > > > > > Sorry for the spam but I am trying to get to the bottom of this. > > Still looking further into bugs posted on Digium tracker and I am coming > close to TBCT also know as 2BCT and RLT. I think LibPRI generates some > sort of request for RLT on the PRI and since we have not requested that > service from Bell Canada then it fails. > > Facility (98): > > Message not compatible with call state or message type nonexistent or not > implemented. > And Facility (98) error check in /usr/src/libpri/pri_facility.c points me > to error messages related to RLT and AOC-E. > > Specially this part of it: > Facility (len=22, codeset=0) [ 0x91, 0xA1, 0x11, 0x02, 0x01, 0x06, 0x06, > 0x07, '*', 0x86, 'H', 0xCE, 0x15, 0x00, 0x08, '0', 0x03, 0x02, 0x01, 0x03 > ] > > Stephan, I know you used to play with RLT and Bell. Have you faced this > before? > > Am I on the right track at all :-) > > Regards, > Bruce > > >> From: [email protected] >> To: [email protected]; [email protected] >> Date: Mon, 12 Apr 2010 18:27:35 -0400 >> Subject: RE: [on-asterisk] Native ZAP bridge fails on PRI between two >> channels >> >> >> I can further confirm that if inbound is through PRI and outbound is >> through analogue line the ZAP or vice versa the native bridge works just >> fine. So, I doubt it's a function problem. >> >> >> >> Are there any PRI debug gurus out there who can decipher the lingo in >> the debug I posted in my initial post or the following? >> >> >> >> >> >> **************************************** >> >>>> -- Zap/2-1 answered Zap/1-1 >>>> -- Native bridging Zap/1-1 and Zap/2-1 >>>> >>>>> Protocol Discriminator: Q.931 (8) len=27 >>>>> Call Ref: len= 2 (reference 96/0x60) (Originator) >>>>> Message type: FACILITY (98) >>>>> [1c 14 91 a1 11 02 01 06 06 07 2a 86 48 ce 15 00 08 30 03 02 01 61] >>>>> Facility (len=22, codeset=0) [ 0x91, 0xA1, 0x11, 0x02, 0x01, 0x06, >>>>> 0x06, 0x07, '*', 0x86, 'H', 0xCE, 0x15, 0x00, 0x08, '0', 0x03, 0x02, >>>>> 0x01, 'a' ] >>>>> >>>> PROTOCOL 11 >>>> A1 0011 (CONTEXT SPECIFIC [1]) >>>> 02 0001 06 (INTEGER: 6) >>>> 06 0007 2A 86 48 CE 15 00 08 (OBJECTIDENTIFIER: 2a 86 48 ce 15 00 08) >>>> 30 0003 (SEQUENCE) >>>> 02 0001 61 (INTEGER: 97) >>>> < Protocol Discriminator: Q.931 (8) len=9 >>>> < Call Ref: len= 2 (reference 96/0x60) (Terminator) >>>> < Message type: DISCONNECT (69) >> *********************************************************************** >> >> >> >> Thanks, >> >> Bruce >> >> >> >> >> >> >>> Date: Mon, 12 Apr 2010 14:26:36 -0400 >>> From: [email protected] >>> To: [email protected] >>> Subject: Re: [on-asterisk] Native ZAP bridge fails on PRI between two >>> channels >>> >>> What does the incoming callerID look like, and do you just send that >>> out >>> unmodified? Try to change it do something else just for testing >>> purposes. >>> >>> >>> On 4/11/2010 5:56 PM, Bruce N wrote: >>>> Hi Guys, >>>> >>>> I am calling out to 416-999-1111 on Channel 1 of PRI and sending the >>>> call to a context that then dials 416-999-2222 on Channel 2 of PRI. >>>> When the two channels are going to be ZAP native bridged, both >>>> channels hangup and CLI show PRI cause (16). >>>> >>>> Asterisk Verbose (Channel 1 already connected to party): >>>> >>>> -- Requested transfer capability: 0x00 - SPEECH >>>> -- Called g0/4169992222 >>>> -- Zap/2-1 is proceeding passing it to Zap/1-1 >>>> -- Zap/2-1 is ringing >>>> -- Zap/2-1 answered Zap/1-1 >>>> -- Native bridging Zap/1-1 and Zap/2-1 >>>> -- Channel 0/1, span 1 got hangup request, cause 16 >>>> -- Hungup 'Zap/2-1' >>>> == Spawn extension (zap-bridge, s, 8) exited non-zero on 'Zap/1-1' >>>> -- Hungup 'Zap/1-1' >>>> >>>> Here is PRI debug, starting just before Channel two is connected until >>>> both channels are disconnected (maybe FACILITY 98 is of interest?!): >>>> >>>> >>>> < Message type: CONNECT (7) >>>> q931.c:3626 q931_receive: call 32865 on channel 2 enters state 10 >>>> (Active) >>>> >>>>> Protocol Discriminator: Q.931 (8) len=5 >>>>> Call Ref: len= 2 (reference 97/0x61) (Originator) >>>>> Message type: CONNECT ACKNOWLEDGE (15) >>>>> >>>> -- Zap/2-1 answered Zap/1-1 >>>> -- Native bridging Zap/1-1 and Zap/2-1 >>>> >>>>> Protocol Discriminator: Q.931 (8) len=27 >>>>> Call Ref: len= 2 (reference 96/0x60) (Originator) >>>>> Message type: FACILITY (98) >>>>> [1c 14 91 a1 11 02 01 06 06 07 2a 86 48 ce 15 00 08 30 03 02 01 61] >>>>> Facility (len=22, codeset=0) [ 0x91, 0xA1, 0x11, 0x02, 0x01, 0x06, >>>>> 0x06, 0x07, '*', 0x86, 'H', 0xCE, 0x15, 0x00, 0x08, '0', 0x03, 0x02, >>>>> 0x01, 'a' ] >>>>> >>>> PROTOCOL 11 >>>> A1 0011 (CONTEXT SPECIFIC [1]) >>>> 02 0001 06 (INTEGER: 6) >>>> 06 0007 2A 86 48 CE 15 00 08 (OBJECTIDENTIFIER: 2a 86 48 ce 15 00 08) >>>> 30 0003 (SEQUENCE) >>>> 02 0001 61 (INTEGER: 97) >>>> < Protocol Discriminator: Q.931 (8) len=9 >>>> < Call Ref: len= 2 (reference 96/0x60) (Terminator) > >>>> >>>> >>>> System Info: >>>> Bell Canada PRI >>>> Asterisk 1.4.21.2 >>>> Lib PRI 1.4.10 >>>> >>>> Dialplan is as simple as this after first channel has already picked >>>> up: >>>> >>>> [bridge-calls] >>>> >>>> exten => s,1,Playback(beep) >>>> exten => s,n,Dial(ZAP/g0/${destNumb}) >>>> >>>> >>>> Thanks, >>>> Bruce > _________________________________________________________________ > Hotmail & Messenger are available on your phone. Try now. > http://go.microsoft.com/?linkid=9724461 ____________________________________________________________ GET FREE SMILEYS FOR YOUR IM & EMAIL - Learn more at http://www.inbox.com/smileys Works with AIM®, MSN® Messenger, Yahoo!® Messenger, ICQ®, Google Talk™ and most webmails --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
