On Fri, Aug 15, 2008 at 03:03:23PM -0500, Matthew Fredrickson wrote: > 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.
Oddly, I learned about TBCT *from the feature planning guide concerning the DMS100*, to which I had a subscription 10 years or so ago; I don't recall it having a different name or limitations. I can lay my hands on that issue; I will. But, again, I wasn't concerned with whether Asterisk could do anything specific with TBCT, except catch calls sent to me by someone else performing one. Which my original message was pretty clear on. :-) Cheers, -- jra -- Jay R. Ashworth Baylink [EMAIL PROTECTED] Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com '87 e24 St Petersburg FL USA http://photo.imageinc.us +1 727 647 1274 Those who cast the vote decide nothing. Those who count the vote decide everything. -- (Josef Stalin) _______________________________________________ -- 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
