Ok, will check that.
I subscribe to the call answered event and wait for that before doing
ivr things, I play a prompt then go to get a key response and it just
skips straight past the message sent, no timeout or anything, and
obviously not waiting for the user. The user presses a key and it
doesnt go anywhere due to the program having completed.
On Tue, May 18, 2010 at 10:18 AM, Anthony Minessale
<anthony.miness...@gmail.com> wrote:
> that does not mean if you are in sync mode or async, the reply on the event
> socket initial message after you enter connect does.
> If you are doing ivr type things before you have media established its
> possible it's simply failing.
>
> On Mon, May 17, 2010 at 4:53 PM, Bob Coleman <b...@devassert.com> wrote:
>>
>> I tried specifying async full to confirm it was giving me the same
>> result, and it does.
>>
>> I put break points into our code where it sends a message to fs, in
>> sync mode it waits for the timeout or until the user presses a key,
>> but in async mode it just returns as expected, immediately.
>>
>> I expected it to be in sync mode, as all our inbound calls come thru
>> in this fashion, and work fine.
>>
>> If ignore_early_media=true is used for the originate it obeys the
>> dialplan, and operates in sync mode.
>>
>> On Tue, May 18, 2010 at 9:33 AM, Anthony Minessale
>> <anthony.miness...@gmail.com> wrote:
>> > try actually specifying sync full not just omitting it.
>> > how are you determining that you are ending up in async mode?
>> >
>> > On Mon, May 17, 2010 at 4:15 PM, Bob Coleman <b...@devassert.com> wrote:
>> >>
>> >> Sorry guys. I might not understand myself.
>> >>
>> >> The scenario is I want to make an outbound call(via an inbound socket)
>> >> and connect it back to an outbound socket for processing.
>> >>
>> >> So to test this, I typed into the FreeSWITCH console the originate
>> >> command, just like I would have via the inbound socket. and was able
>> >> to make a call to a mobile phone, and have it connect back to an
>> >> outbound socket, but to my surprise it was now in async mode. I had
>> >> written the outbound socket to be sync, and there was no async command
>> >> in the dialplan that handled the extension I had transfered the call
>> >> too. Once the call is made I am not doing anything else to it via the
>> >> inbound socket, just letting the call run its course through our
>> >> callflow app.
>> >>
>> >> I guess I am wondering if I am doing this the right way, or I have
>> >> missed something and there is an easier way.
>> >>
>> >> Thanks
>> >>
>> >> Bob
>> >>
>> >> On Tue, May 18, 2010 at 3:37 AM, Michael S Collins
>> >> <m...@freeswitch.org>
>> >> wrote:
>> >> > Are you trying to originate from a program with inbound event socket
>> >> > and
>> >> > then and also have the same program handle the other call leg (805)
>> >> > using
>> >> > outbound event socket? Same port? Please clarify like Tony said.
>> >> > -MC
>> >> >
>> >> > Sent from my iPhone
>> >> > On May 17, 2010, at 8:13 AM, Anthony Minessale
>> >> > <anthony.miness...@gmail.com>
>> >> > wrote:
>> >> >
>> >> > I read this like 5 times and I could not understand what you are
>> >> > trying
>> >> > to
>> >> > ask.
>> >> > Could you rephrase with more detail?
>> >> >
>> >> > On Sun, May 16, 2010 at 6:54 PM, Bob Coleman <b...@devassert.com>
>> >> > wrote:
>> >> >>
>> >> >> Hi,
>> >> >>
>> >> >> Is there a reason why an orginate command typed into the freeswitch
>> >> >> console overrides the dialplan socket application(<action
>> >> >> application="socket" data="127.0.0.1:4573 full"/>) with async
>> >> >> eg originate sofia/gateway/????/???? 805
>> >> >>
>> >> >> 805 being the extension the outbound event socket is fired from.
>> >> >>
>> >> >> I have noticed that if the {ignore_early_media=true} is set that it
>> >> >> behaves correctly and does not override with async.
>> >> >>
>> >> >> I am using the 1.6 version source compiled locally on a windows box,
>> >> >> and a extension of 805 setup with the above outbound socket
>> >> >> connection.
>> >> >>
>> >> >> Regards
>> >> >>
>> >> >> Bob
>> >> >>
>> >> >> _______________________________________________
>> >> >> FreeSWITCH-dev mailing list
>> >> >> FreeSWITCH-dev@lists.freeswitch.org
>> >> >> http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
>> >> >>
>> >> >> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
>> >> >> http://www.freeswitch.org
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Anthony Minessale II
>> >> >
>> >> > FreeSWITCH http://www.freeswitch.org/
>> >> > ClueCon http://www.cluecon.com/
>> >> > Twitter: http://twitter.com/FreeSWITCH_wire
>> >> >
>> >> > AIM: anthm
>> >> > MSN:anthony_miness...@hotmail.com
>> >> > GTALK/JABBER/PAYPAL:anthony.miness...@gmail.com
>> >> > IRC: irc.freenode.net #freeswitch
>> >> >
>> >> > FreeSWITCH Developer Conference
>> >> > sip:8...@conference.freeswitch.org
>> >> > googletalk:conf+...@conference.freeswitch.org
>> >> > pstn:+19193869900
>> >> >
>> >> > _______________________________________________
>> >> > FreeSWITCH-dev mailing list
>> >> > FreeSWITCH-dev@lists.freeswitch.org
>> >> > http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
>> >> >
>> >> > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
>> >> > http://www.freeswitch.org
>> >> >
>> >> > _______________________________________________
>> >> > FreeSWITCH-dev mailing list
>> >> > FreeSWITCH-dev@lists.freeswitch.org
>> >> > http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
>> >> >
>> >> > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
>> >> > http://www.freeswitch.org
>> >> >
>> >> >
>> >>
>> >> _______________________________________________
>> >> FreeSWITCH-dev mailing list
>> >> FreeSWITCH-dev@lists.freeswitch.org
>> >> http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
>> >> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
>> >> http://www.freeswitch.org
>> >
>> >
>> >
>> > --
>> > Anthony Minessale II
>> >
>> > FreeSWITCH http://www.freeswitch.org/
>> > ClueCon http://www.cluecon.com/
>> > Twitter: http://twitter.com/FreeSWITCH_wire
>> >
>> > AIM: anthm
>> > MSN:anthony_miness...@hotmail.com
>> > GTALK/JABBER/PAYPAL:anthony.miness...@gmail.com
>> > IRC: irc.freenode.net #freeswitch
>> >
>> > FreeSWITCH Developer Conference
>> > sip:8...@conference.freeswitch.org
>> > googletalk:conf+...@conference.freeswitch.org
>> > pstn:+19193869900
>> >
>> > _______________________________________________
>> > FreeSWITCH-dev mailing list
>> > FreeSWITCH-dev@lists.freeswitch.org
>> > http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
>> > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
>> > http://www.freeswitch.org
>> >
>> >
>>
>> _______________________________________________
>> FreeSWITCH-dev mailing list
>> FreeSWITCH-dev@lists.freeswitch.org
>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
>> http://www.freeswitch.org
>
>
>
> --
> Anthony Minessale II
>
> FreeSWITCH http://www.freeswitch.org/
> ClueCon http://www.cluecon.com/
> Twitter: http://twitter.com/FreeSWITCH_wire
>
> AIM: anthm
> MSN:anthony_miness...@hotmail.com
> GTALK/JABBER/PAYPAL:anthony.miness...@gmail.com
> IRC: irc.freenode.net #freeswitch
>
> FreeSWITCH Developer Conference
> sip:8...@conference.freeswitch.org
> googletalk:conf+...@conference.freeswitch.org
> pstn:+19193869900
>
> _______________________________________________
> FreeSWITCH-dev mailing list
> FreeSWITCH-dev@lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
> http://www.freeswitch.org
>
>
_______________________________________________
FreeSWITCH-dev mailing list
FreeSWITCH-dev@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
http://www.freeswitch.org
