[Freeswitch-users] HANGUP_CAUSE after bridge in outbound ESL

[Diego Toro]

Hi, check originate_disposition variable

http://wiki.freeswitch.org/wiki/Extension_Status_Example
http://wiki.freeswitch.org/wiki/Variable_originate_disposition

Diego Toro

http://voipensando.blogspot.com/

--- On Tue, 3/1/11, Steven Ayre <steveayre at gmail.com> wrote:

From: Steven Ayre <steveayre at gmail.com>
Subject: Re: [Freeswitch-users] HANGUP_CAUSE after bridge in outbound ESL
To: "FreeSWITCH Users Help" <freeswitch-users at lists.freeswitch.org>
Date: Tuesday, March 1, 2011, 4:08 AM

The correct way is to use events. You can register for just the hangup event.

-Steve


On 28 February 2011 22:43, Dmitry Sytchev <kbdfck at gmail.com> wrote:
> Hi All
>
> What is correct method to get bridge status after execute("bridge") in ESL?
> I have inbound call that gets bridged to SIP endpoint. I need to know
> whether it was ORIGINATOR_CANCEL or BUSY or something else, but if I use
> sync, seems I can't determine ORIGINATOR_CANCEL status, because it is set on
> a-leg which is destroyed first after hangup.
>
> Is there a way to get bridge status without messing with events and event
> source filtering by channel uuid or event type?
>
> --
> Best regards,
>
> Dmitry Sytchev,
> IT Engineer
>
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at 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 at lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20110301/aa7d3fa8/attachment-0001.html