... all the normal dialplan handling. Setting CID, options, LCR stuff, billing controls.
-Avi
On Sun, Jun 3, 2012 at 11:40 PM, Michael Collins
<msc@freeswitch.org> wrote:
Let me rephrase...
Since loopback is generally evil and should be avoided wherever possible, what does loopback give you that you can't get from doing a normal dialstring?
-MC
On Sat, Jun 2, 2012 at 11:13 AM, Avi Marcus
<avi@avimarcus.net> wrote:
... because att_xfer seems to require a "sofia/$profile/$destination" directive, and he just wants the call to hit the dialplan.
-Avi
On Fri, Jun 1, 2012 at 8:13 PM, Michael Collins
<msc@freeswitch.org> wrote:
Why do you need to use loopback at all?
-MCOn Fri, Jun 1, 2012 at 3:17 AM, Alex Lake
<alex@digitalmail.com> wrote:
Got a lua script for a B-party "mid-call menu". Is it legitimate to do..
"session:execute("att_xfer", "loopback/"..destnum)"
I've tried it and it seems to start off doing the right things, but my
A-party gets disconnected as soon as the call to the C-Party (the person
I'm transferring the call to) answers the call.
Maybe better to try to orchestrate the entire affair from within the lua
script? (Tricky for a beginner like me!)
Thanks,
Alex