[asterisk-users] 2BCT last mile... Hopefully

Matthew Fredrickson creslin at digium.com
Thu Apr 23 12:14:06 CDT 2009


Max Metral wrote:
> Ok, so I’ve made progress on 2BCT (2 B-Channel Transfer).  I’m assuming 
> that the debug info below shows that XO doesn’t have 2BCT enabled on my 
> line, but if anybody can confirm that’ll let me be way more indignant. J

It would appear that the switch doesn't like what you're sending it. 
That means either your switch at the other end is not configured with 
this feature enabled or that your switchtype is set incorrectly for the 
actual switch type that the other end is expecting.

 From the message you are sending to the other side, it would appear 
that you are configured for either 5ESS or national switch type.

Another possiblity (although low in probability) is that it doesn't like 
being sent the transfer message so soon, since it would appear that we 
have not yet received the CONNECT-ACK from the other switch by the time 
we send the transfer request.

You could try inserting a Wait(5) after you Answer() the call in your 
dialplan before Dial()'ing back out to verify that the call is 
completely setup.  Make sure you try explicitly Answer()'ing the call 
first in your dialplan before Wait()'ing or Dial()'ing back out, at 
least until you figure out what the problem is.

Matthew Fredrickson
Digium, Inc.


> 
>  
> 
>     -- Native bridging DAHDI/1-1 and DAHDI/3-1
> 
>  > Protocol Discriminator: Q.931 (8)  len=28
> 
>  > Call Ref: len= 2 (reference 801/0x321) (Terminator)
> 
>  > Message type: FACILITY (98)
> 
>  > [1c 15 91 a1 12 02 01 23 06 07 2a 86 48 ce 15 00 08 30 04 02 02 01 93]
> 
>  > Facility (len=23, codeset=0) [ 0x91, 0xA1, 0x12, 0x02, 0x01, '#', 
> 0x06, 0x07, '*', 0x86, 'H', 0xCE, 0x15, 0x00, 0x08, '0', 0x04, 0x02, 
> 0x02, 0x01, 0x93 ]
> 
> PROTOCOL 11I>
> 
> A1 0012 (CONTEXT SPECIFIC [1])
> 
>   02 0001 23 (INTEGER: 35)
> 
>   06 0007 2A 86 48 CE 15 00 08 (OBJECTIDENTIFIER: 2a 86 48 ce 15 00 08)
> 
>   30 0004 (SEQUENCE)
> 
>     02 0002 01 93 (INTEGER: 403)
> 
> < Protocol Discriminator: Q.931 (8)  len=5
> 
> < Call Ref: len= 2 (reference 801/0x321) (Originator)
> 
> < Message type: CONNECT ACKNOWLEDGE (15)
> 
> q931.c:3705 q931_receive: call 801 on channel 1 enters state 10 (Active)
> 
> < Protocol Discriminator: Q.931 (8)  len=16
> 
> < Call Ref: len= 2 (reference 801/0x321) (Originator)
> 
> < Message type: FACILITY (98)
> 
> < [1c 09 91 a3 06 02 01 23 02 01 00]
> 
> < Facility (len=11, codeset=0) [ 0x91, 0xA3, 0x06, 0x02, 0x01, '#', 
> 0x02, 0x01, 0x00 ]
> 
> PROTOCOL 11I>
> 
> A3 0006 (CONTEXT SPECIFIC [3])
> 
>   02 0001 23 (INTEGER: 35)
> 
>   02 0001 00 (INTEGER: 0)
> 
> -- Processing IE 28 (cs0, Facility)
> 
> Handle Q.932 ROSE return error component
> 
> Unable to handle return result on switchtype 1!
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users




More information about the asterisk-users mailing list