The originate creates one leg and connects it to another leg. In this example: {execute_on_answer=start_dtmf,ignore_early_media=true}sofia/gateway/trunk_1/0860216060 8888 Everything up to 8888 creates the A leg. The "8888" is the B leg. -MC On Wed, May 30, 2012 at 9:37 AM, Michael Lutz <mytemike72@gmail.com> wrote:
Hi Michael,
Can you explain a bit more? If you would initiate an outbound call using an originate api call, there is only one leg? How would you specify to listen to the b-leg, other than this?
It might explain some issues I have recognizing (valid) dtmf's...
Regards, Mike.
2012/5/30 Michael Collins <msc@freeswitch.org>:
Make sure that the start_dtmf is on the correct leg. I suggested putting it on the b leg, but this example sets it on the a leg. Try it either way to make sure. -MC
On Wed, May 30, 2012 at 5:08 AM, Michael Lutz <mytemike72@gmail.com> wrote:
If your outbound provider does not support RFC2833 (DTMF via SIP Info messages) you need to explicitly set the outbound leg to 'listen' for DTMF tones using the start_dtmf dialplan command. As you originate, there is no real dialplan, you can set it using the "execute_on_answer"in inside the originate command like:
originate
{execute_on_answer=start_dtmf,ignore_early_media=true}sofia/gateway/trunk_1/0860216060
8888
Regards, Mike.
2012/5/29 Michael Collins <msc@freeswitch.org>:
You may need explicitly to listen for inband DTMFs.Try adding <action application="start_dtmf"> to extension 8888 and retest. -MC
On Thu, May 24, 2012 at 8:27 PM, Chaiyawut Sookplang <chaiyawut.so@gmail.com> wrote:
I want to make an automatic IVR call using originate command. I
issued
command
"originate {ignore_early_media=true}sofia/gateway/trunk_1/0860216060 8888"
and then I found that DTMF from the receiver side couldn't be detected. On the other hand, if I call to extension 8888, IVR and DTMF work fine.