I have an app that conferences several calls together on one CTI port. I have a CTI port with 2 calls conferenced. When this CTI port answers a third call (from a transfer), the terminal connection state goes to HELD. An attempt to conference the third call fails (let's say, due to the conference bridge being full), the app drops that call. So far, everything works correctly. However, the terminal connection state is still in the HELD state, after the third call failed (and the other two are still happily in a conference.) I expected the terminal connection state to be back in ACTIVE state. Is this expected behavior?
Jtapi version is 9.0
No terminal connection doesn't come back to active state. Application should use unhold() API to get the terminal connection to TALKING state.