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
Having a single handler per session (instead of a separate handler for each early dialog) provides at least two benefits:
Reusing the same media for multiple early dialogs would be easier to do automatically, without the application needing to know anything about it.
WebRTC.MediaHandler.getRemoteStreams could return the early media streams if available, and the on-call streams otherwise (again, without the application having to dig out the early dialog and its streams).
The text was updated successfully, but these errors were encountered:
We are currently playing with a new MediaHandler per getDescription/setDescription (to get fresh peerConnections for reINVITE scenarios and on-the-fly handling of adding/removing screens).
Will keep you posted on our progress if that is an approach that would be satisfactory for merging into upstream as well.
Having a single handler per session (instead of a separate handler for each early dialog) provides at least two benefits:
The text was updated successfully, but these errors were encountered: