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
I've come across what I believe is an issue when dealing with referring with a call that is on hold. To explain:
I establish an RTCSession to phone A
I place this on hold
I establish a second RTCSession to phone B
I use a refer() action on phone A's RTCSession, populating the replaces optional parameter
Phone B's RTCSession correctly emits an ended (Terminated) event shortly after the referral completes. Phone A waits for exactly 60 seconds before emitting it's ended event. This isn't emitted because there's been a termination, but instead because it's timed out and no longer exists.
If I unhold phone A's RTCSession prior to calling the refer action, then both RTCSessions submit an ended event within a millisecond of each other. Equally if I unhold phone A's RTCSession within refers eventHandler: accepted event, the ended events are submitted correctly.
I have tried flipping the refer around (i.e. Phone A.refer(Phone B)), but I still have the same issue, which suggests to me the ended event isn't correctly emitted for held RTCSessions during a refer action. ended events are emitted should an on hold RTCSession be hung up on.
The text was updated successfully, but these errors were encountered:
I've come across what I believe is an issue when dealing with referring with a call that is on hold. To explain:
I establish an RTCSession to phone A
I place this on hold
I establish a second RTCSession to phone B
I use a refer() action on phone A's RTCSession, populating the
replaces
optional parameterPhone B's RTCSession correctly emits an
ended
(Terminated) event shortly after the referral completes. Phone A waits for exactly 60 seconds before emitting it'sended
event. This isn't emitted because there's been a termination, but instead because it's timed out and no longer exists.If I unhold phone A's RTCSession prior to calling the refer action, then both RTCSessions submit an
ended
event within a millisecond of each other. Equally if I unhold phone A's RTCSession within referseventHandler: accepted
event, theended
events are submitted correctly.I have tried flipping the refer around (i.e. Phone A.refer(Phone B)), but I still have the same issue, which suggests to me the
ended
event isn't correctly emitted for held RTCSessions during a refer action.ended
events are emitted should an on hold RTCSession be hung up on.The text was updated successfully, but these errors were encountered: