Table of Contents (click to expand)
Hangs up a channel, with an optional cause code supplied.
<action application="hangup" data="USER_BUSY"/>
If you use hangup after a bridge, FreeSWITCH™ overrides the cause with the cause received from the bridge application. You can avoid this using sip_ignore_remote_cause=true
These tips have been shared by Bao Nguyen
Did you see the
BYE sent by FreeSWITCH™ towards the caller, and its 200 OK response? If yes, then it's the problem with your ITSP or the caller cell provider.
hangup_after_bridge variable is also worth checking when FreeSWITCH™ didn't hang up the A leg when B is terminated.