Jay R. Ashworth wrote: > On Fri, Aug 15, 2008 at 03:03:23PM -0500, Matthew Fredrickson wrote: >> Let me clarify some of this. >> >> Under no circumstances can Asterisk receive a TBCT request. We just >> ignore them. We can initiate them however. >> >> There are different TBCT implementations, dependent on which switch type >> is used, with different restrictions associated with each switch type >> selected. >> >> For true TBCT (on switchtypes of NI2 and 5ESS, AFAIK), you can have any >> combination of inbound and/or outbound channels (one inbound/one >> outbound, two inbound, two outbound) and transfer them to the upstream >> switch. The protocol doesn't care. >> >> For DMS100's version of TBCT, called RLT, one leg *must* be inbound and >> the other *must* be outbound. No other combination is going to work. >> This is explicitly mentioned in the protocol in RLT. > > Ok. > > Just found this in my archive. > > Matt: should I assume that this implies that if my switch is provisioned > for NI2, and my Asterisk is set to DMS, that things aren't going to work > well at all? :-) (Outbound calls, FWIW, seem to work fine like that...)
Probably not. You can obviously try this out, but don't be surprised if this doesn't work. You usually want to have your switchtype (which likewise sets the version of TBCT which is used) set to the same thing that the other end is provisioned to be. Matthew Fredrickson _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users