Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use one MediaHandler per Session #7

Closed
josephfrazier opened this issue Apr 30, 2014 · 2 comments
Closed

Use one MediaHandler per Session #7

josephfrazier opened this issue Apr 30, 2014 · 2 comments
Milestone

Comments

@josephfrazier
Copy link
Contributor

Having a single handler per session (instead of a separate handler for each early dialog) provides at least two benefits:

  1. Reusing the same media for multiple early dialogs would be easier to do automatically, without the application needing to know anything about it.
  2. 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).
@wakamoleguy wakamoleguy added this to the 0.8.0 milestone Nov 24, 2014
@olivermt
Copy link

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.

@egreenmachine
Copy link
Collaborator

This is fixed in 0.8.0.

jvdownie pushed a commit to netsapiens/SIP.js that referenced this issue Oct 10, 2017
prlanzarin added a commit to prlanzarin/SIP.js that referenced this issue Jul 2, 2019
Add support for multiple registrations within the same UA
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants