Hello, it's me again, I noticed then these steps: 1) dial 2 calls bgapi originate {ignore_early_media=true}sofia/gateway/agent_gateway/2500 &park() bgapi originate {ignore_early_media=true}sofia/gateway/g2/2501 &park() 2) bridge them bgapi uuid_transfer f0c0db16-f00f-4b0b-8a00-d3b108d121b2 intercept:a85fd47e-051f-42ea-987e-f4e090c7ae78,park inline 3) put the 2nd call on hold: uuid_hold a85fd47e-051f-42ea-987e-f4e090c7ae78 4) hangup the 2nd call uuid_kill a85fd47e-051f-42ea-987e-f4e090c7ae78 cause the 1st call to be hanged up as well. I want it to be parked in this situation. When I set the [park_after_bridge=true] var in dialstring, it works just like I want it to. Is setting this variable the proper way of accomplishing it - keeping channel alive when the other leg put on hold hangs up? Thanks, Maciej Aniserowicz -- View this message in context: http://n2.nabble.com/When-leg-on-hold-hangs-up-another-leg-is-hanged-up-too-... Sent from the freeswitch-users mailing list archive at Nabble.com.