On 8/4/09, Brian Thompson <[email protected]> wrote: > > Hello, > > We currently have a scenario where a large percentage of inbound > calls on a telco PRI are intended for professors who aren't currently > in their offices/at their desks. > > My question is, is anyone actively using the Asterisk "RLT" (Release > Link Trunking) feature to bounce these sorts of calls back to the > telco? The idea being to forward the call to their mobile phone without > tying up two of the PRI channels (one inbound and one outbound) > for the duration of the call. > > If so, any caveats pertaining to the combination of RLT and Asterisk > that I should be aware of before attempting to build such a system? > > Thanks, > Brian
Hello, We have set up several systems using TBCT(Two B-Channel Transfer), which is the NI2 protocol version of RLT(which is for DMS100 only). As long as the carrier supports it(which is always the biggest problem in our experience), the actual functionality works great with Asterisk. Some things to keep in mind: - Your carrier will bill you for the time on the off-circuit legs of the call, and will send you a PRI message when the call hangs up. Asterisk throws up a warning for this event and ignores it(not logged in any way). - With RLT(on DMS100) you can only do RLT with calls that come in to your circuit, whereas TBCT on NI2 can work for inbound or outbound initiated calls. Setup is fairly easy for these, just set zapata.conf facilityenable=yes and transfer=yes and upon a native bridge on the same trunk group the calls will be released to the carrier and free up those two lines. MATT--- _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2009 - October 13 - 15 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
