You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the reconnectMedia will only send ReInvite with "sendrecv" in SDP, but if the call is on hold, we cannot use reconnectMedia API to recover it since if client send ReInvite with "sendrecv", call will resume.
But if we don't send ReInvite at all when call is on hold, if other party hangup call, client cannot receive the BYE from server.
So we need to add an API or exten reconnectMedia API to send out ReInvite with "sendonly" so that we can keep the hold state and also we can receive BYE from server.
Related to bug ticket: FIJI-29843
The text was updated successfully, but these errors were encountered:
But if we don't send ReInvite at all when call is on hold, if other party hangup call, client cannot receive the BYE from server.
As I tested, when the call is on hold, if other party hangup call, phone client CAN receive the BYE from server. However, there is about 5 seconds delay. I mean the BYE message is received 5 seconds after the other party hangup.
Currently the reconnectMedia will only send ReInvite with "sendrecv" in SDP, but if the call is on hold, we cannot use reconnectMedia API to recover it since if client send ReInvite with "sendrecv", call will resume.
But if we don't send ReInvite at all when call is on hold, if other party hangup call, client cannot receive the BYE from server.
So we need to add an API or exten reconnectMedia API to send out ReInvite with "sendonly" so that we can keep the hold state and also we can receive BYE from server.
Related to bug ticket: FIJI-29843
The text was updated successfully, but these errors were encountered: