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

Merge or update the fork with upstream 0.15.x line #22

Open
prlanzarin opened this issue Jan 15, 2020 · 0 comments
Open

Merge or update the fork with upstream 0.15.x line #22

prlanzarin opened this issue Jan 15, 2020 · 0 comments

Comments

@prlanzarin
Copy link
Member

prlanzarin commented Jan 15, 2020

Don't know if a merge is warranted or even possible. It might be easier to just switch to 0.15.x cold turkey, port over the RegisterContext changes and try to make it work over WS in Node.js.
Things to watch for:

  • Make sure we can do multiple alias REGISTER requests within a single UA.
  • Make sure there are no regressions with the INFO nicst transactions state acceptance.

If we make it work with 0.15.x over WS, I suggest dropping the UDP and TCP transports and rely on Kamailio to do the transport protocol conversion. We might keep our 0.7.x fork as a dev dependency to use the UDP/TCP transports to ease development, but that won't be recommended in order to maintain behavioural parity between dev and prod environments.

@prlanzarin prlanzarin changed the title Merge the fork with upstream 0.15.x line Merge or update the fork with upstream 0.15.x line Jan 15, 2020
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

1 participant