On Tue, Jul 14, 2009 at 2:14 PM, Weaver, Eric <eweaver@meetingone.com>wrote:
Using api uuid_park 81b65478-70b9-11de-bf26-b962186102f7 before terminating the NC session works, the call is not disconnected.
Once that is done, I do not receive DTMF and cannot play prompts to the caller, they seem to be in limbo. I can uuid_kill the call but I need to get dtmf and play prompts to them. Perhaps Park is not where I need to put these calls ?
To get a call out of park you need to bridge to it or transfer it to another extension. If you have an extension you can just uuid_transfer the parked call's uuid. If you have an existing call's uuid you can use uuid_bridge to bridge the two together. Could you remind me of the application you're building? Just curious what the big picture is. -MC
*From:* freeswitch-users-bounces@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *On Behalf Of *Michael Collins *Sent:* Tuesday, July 14, 2009 11:12 AM *To:* freeswitch-users@lists.freeswitch.org *Subject:* Re: [Freeswitch-users] Preventing disconnect on event_sockte close
On Tue, Jul 14, 2009 at 9:59 AM, Weaver, Eric <eweaver@meetingone.com> wrote:
Tried it using FreeSWITCH Version 1.0.4pre9 (14036M) and the following steps
Start netcat
netcat -v -l -p 14000
place call, socket is connected via dial plan, enter the following.
connect\n\n
sendmsg
call-command: execute
execute-app-name: answer\n\n
sendmsg
call-command: execute
execute-app-name: playback
execute-app-arg: /home/eweaver/holdmusic.wav
<when wave file is done playing>
sendmsg
call-command: execute
execute-app-name: park
Try this: api uuid_park <uuid>
You'll need to capture the uuid at some point and store it. For testing I just manually copied and pasted it to/from the console screen. -MC
Console window displays this message:
2009-07-14 10:42:29.245833 [ERR] switch_ivr.c:654 Cannot park channels that are under control already.
at this point, ^C in the netcat window. Call is disconnected.
Need to be able to park these calls so they can then be handled from an inbound event socket connection.
eric
*From:* freeswitch-users-bounces@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *On Behalf Of *Michael Collins *Sent:* Monday, July 13, 2009 7:08 PM *To:* freeswitch-users@lists.freeswitch.org *Subject:* Re: [Freeswitch-users] Preventing disconnect on event_sockte close
I don't know if this will work for you but I just tested this scenario with uuid_park. After parking the call I disconnected the socket and the call continued. I did the same thing with uuid_transfer. After the transfer I disconnected the socket and the call continued.
How are you handling the call and how is the socket getting disconnected?
-MC
On Mon, Jul 13, 2009 at 4:35 PM, Weaver, Eric <eweaver@meetingone.com> wrote:
Using mod_event_socket in outbound mode, is there any to prevent a call from being disconnected when the outbound socket is closed ? I would like to handle the initial inbound call using outbound but after the disposition of the call is determined, close the socket and have that call managed using an inbound socket instead.
Eric Weaver
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org