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

URI parameters are not in the same order with original uri #68

Open
sekocelik opened this issue Feb 2, 2023 · 0 comments
Open

URI parameters are not in the same order with original uri #68

sekocelik opened this issue Feb 2, 2023 · 0 comments

Comments

@sekocelik
Copy link

When we try to create a new request we use following

Original URI = "sip:bob@192.168.1.59:45831;rinstance=54d13cbf8a4c07df;transport=UDP"
When we try to create a new request with above uri its pramater order changed and appears as follow
"sip:bob@192.168.1.59:45831;transport=UDP;rinstance=54d13cbf8a4c07df"
This is because when ruri is parsed a predefined record is used and there transport param precedes to other params

:ersip_uri.parse( "sip:bob@192.168.1.59:45831;rinstance=54d13cbf8a4c07df;transport=UDP")
{:ok,
{:uri, :sip,
{:sip_uri, false, {:user, "bob"}, {:ipv4, {192, 168, 1, 59}}, "192.168.1.59",
45831,
%{:transport => {:transport, :udp}, "rinstance" => "54d13cbf8a4c07df"},
%{}}}}

Is it possible to parse uri in the same order as the original uri?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant