[Freeswitch-users] hangup cause / sip cause ?
steveayre at gmail.com
Fri Aug 9 16:46:16 UTC 2019
Are you returning from the bridge to the dialplan for further processing?
Perhaps the b-leg fails with NORMAL_TEMPORARY_FAILURE, returns to dialplan,
and then you're hanging the a-leg up with NORMAL_CLEARING when it reaches
the end of the dialplan? Which would mean the Reason header sent on the
a-leg would indicate NORMAL_CLEARING.
On Sat, 3 Aug 2019 at 17:28, morbidus at rx900.org <morbidus at rx900.org> wrote:
> Hi i've wrote some dialplans for billing with this great engine which is
> and i'm also using limits and failover ('manually', without the lcr
> Everything works ok and i'm impressed by its stability and performance !
> But i'm unable to get a 'final' termination cause for the calls as i'm
> used to get with asterisk:
> i'd like to have something like 'answered', 'cancel', 'busy',
> 'congestion', 'chanunavail', and so on
> so i'm writing last_bridge_hangup_cause, bridge_hangup_cause and
> hangup_cause in my cdr
> and in particular when the call goes thru the second or third trunk (when
> using failover)
> i get 'NORMAL_TEMPORARY_FAILURE', 'NORMAL_TEMPORARY_FAILURE',
> and i don't know which one of the three is the actual termination cause :)
> what are you guys using to get 'consistent' tc ?
> The FreeSWITCH project is sponsored by SignalWire https://signalwire.com
> Enhance your FreeSWITCH install with disruptive priced SMS and PSTN
> Build your next product on our scalable cloud platform.
> Join our online community to chat in real time
> Professional FreeSWITCH Services
> sales at freeswitch.com
> Official FreeSWITCH Sites
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the FreeSWITCH-users