[Freeswitch-users] Primary leg hangs up when other leg rejects the call

lakshmanan ganapathy lakindia89 at gmail.com
Wed May 11 15:45:53 MSD 2011


Hi all,
I've also check it against the latest GIT as of today and there is no change
in the behavior. Can someone please tell me why the primary leg is also got
hangup?? and how can I avoid that??


On Tue, May 10, 2011 at 6:04 PM, lakshmanan ganapathy
<lakindia89 at gmail.com>wrote:

> Dear all,
> I'm using Event Inbound Socket. I want to originate a call to the user and
> bridge him with different user.
> So I used the following commands from the telnet.
>
>
> api originate {exec_after_bridge_app=park,ignore_early_media=true}user/1010
> &park()
>
> Content-Type: api/response
> Content-Length: 41
>
> +OK cf9a78a2-7aff-11e0-b732-4f9b0298a6ed
>
> sendmsg cf9a78a2-7aff-11e0-b732-4f9b0298a6ed
> call-command: execute
> execute-app-name: bridge
> execute-app-arg:user/1005
>
> Content-Type: command/reply
> Reply-Text: +OK
>
> The user 1005 rejects the call and I got the response as CALL_REJECTED.
> I expect that primary leg will not hangup and go into park mode. But it got
> hangup.
>
> Since by default hangup_after_bridge will be false, I'm not setting it
> explicitly here.
>
> FreeSwitch logs are here,
> http://pastebin.freeswitch.org/16264
>
> Can someone please tell me what is the problem I've done and how to make
> the primary leg again in park() ??
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20110511/a4bba1c4/attachment.html 


More information about the FreeSWITCH-users mailing list