Hello,

I’m using event socket outbound, and have an issue where, after a bridge ends and is terminated by Leg B, Leg A is also terminated.  Here’s the call flow:

1. Call comes in (Leg A), session created, play welcome message.

2. From this session, originate and dial out using api originate

3. After the target answers (Leg B), bridge the 2 calls using api uuid_bridge

4. Leg B hangs up.

5. Leg A will be terminated.

After step 4, Leg A is terminated.  I do not want Leg A to hang up.  I’ve tried setting “hangup_after_bridge=false” prior to the call, and that doesn’t work.

Having said that, I tried a similar test which does not end Leg A’s call after Leg B hangs up, but I can’t use this solution because, functionally, does not accomplish what I want it to do (i.e., I want to perform some actions on Leg B prior to the bridge, like send some DTMF tones, playback some messages, etc).  I did not need to set the “hangup_after_bridge” variable (default should be false anyway).

1. Call comes in (Leg A), session created, play welcome message.

2. From this session, do a bridge by doing an execute bridge.

3. The target answers (Leg B)

4. Leg B hangs up.

5. Leg A will still be active.

Any ideas would be appreciated.  Thanks!

Simon