[asterisk-dev] TBCT from the Asterisk side (this time)
Jay R. Ashworth
jra at baylink.com
Mon Sep 8 10:42:01 CDT 2008
On Mon, Sep 08, 2008 at 11:25:02AM -0400, Donny Kavanagh wrote:
> There really is no 'programming' it, you need facilityenable=yes and
> you need to do your dial w/o asking asterisk to stay in the audio
> path. Asterisk should then decide if it can do the RLT or not. I
> don't know much beyond that as i have not used the implementation in
> quite a while other then to know it works for us at our office. With
> the proper console debugging levels (i dont know which) you should see
> ROSE protocol talk on your console.
Ah. So you're saying that it treats it, very roughly, as the same
situation in which it has to decide whether it can do Native Bridging: if
a call comes in a PRI, and you dial it out the same PRI, and don't
specify anything that would suggest to Asterisk that it needs to keep
listening, then it will tell the switch to transfer it, and wait for both
timeslots to drop, and then move on with life? Got it.
And if you *do* want to stay in the call, you just do *something* that
will cause it to think it needs to.
How far back does that facility go, version wise?
Cheers,
-- jra
--
Jay R. Ashworth Baylink jra at baylink.com
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)
More information about the asterisk-dev
mailing list