I put a call into full hold. Then call sipxConferenceJoin to add it to a conference. It succeeds. But the call is in held state, and I want to unhold it. However after calling sipxCallUnhold it goes to bridged state, so local mic/speaker are not engaged. Subsequent calls to sipxCallUnhold do nothing.
What is the correct behaviour? I didn't find it in sipxtapi.h or in the sipxcalllib/doc manual. Shouldn't that call after sipxCallUnhold be in CONNECTED state instead of BRIDGED? I think sipxtapi doesn't go to CONNECTED state from BRIDGED as you can see from the log even though you can see LOCAL_START::AUDIO event. After REMOTE_START::AUDIO it goes correctly to BRIDGED. But after LOCAL_START::AUDIO it should proceed to CONNECTED. log: HELD::CAUSE_NORMAL EVENT_CATEGORY_MEDIA::LOCAL_STOP::AUDIO::CAUSE_HOLD EVENT_CATEGORY_MEDIA::REMOTE_STOP::AUDIO::CAUSE_HOLD sipxConferenceJoin - Call joined the conference 1 sipxCallUnhold EVENT_CATEGORY_MEDIA::REMOTE_START::AUDIO::CAUSE_NORMAL BRIDGED::CAUSE_NORMAL EVENT_CATEGORY_MEDIA::LOCAL_START::AUDIO::CAUSE_NORMAL _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
