either way is fine.
when you hangup up a bridged call the A leg returns to the execute state and since there are no more apps to execute it hangs up (desired default behavior) setting park_after_bridge was designed for your desired result of the call returning to a park state to await further instructions.
The 2nd call can be hanged up manually too, not only from my app by
uuid_kill. I use the uuid_kill scenario just for tests, to see how it
behaves.
--
View this message in context: http://n2.nabble.com/When-leg-on-hold-hangs-up-another-leg-is-hanged-up-too-tp4790809p4791688.html
Sent from the freeswitch-users mailing list archive at Nabble.com.
_______________________________________________
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