[OpenSIPS-Users] SIP URI User Parameters
bogdan at opensips.org
Thu Jun 29 04:38:47 EDT 2017
I understand you add the npdi useraname parameter after performing the
initial do_routing() - if you do it in request or branch route is not
relevant (for RURI changes) as RURI is anyhow a per-branch value.
In failure route, when resuming, you will get the RURI of the winning
branch ( the one which was selected to be sent back to caller), so you
see the npdi param.
So far so good. And now you do use_next_gw() in failure route and you
get "sip:+15555551212 at gw2.com;npdi" directly, without any another npdi
addition ? I'm asking, as use_next_gw() does a full RURI replacement (it
doesn;t care what is the existing RURI).
Could you also do an
xlog("DR ruris are <$(avp(___dr_ruri__)[*])>\n");
right after do_routing() ?
OpenSIPS Founder and Developer
OpenSIPS Bootcamp 2017, Houston, US
On 06/28/2017 11:41 PM, Ben Newlin wrote:
> We have run into an issue with OpenSIPs’ handling of user parameters
> in SIP URIs with Dynamic Routing module. When a parameter is added to
> a SIP URI user part, any subsequent modification of the URI by DR
> module results in the parameter being moved to be a URI parameter.
> For example, starting with $ru of “sip:+15555551212 at gw1.com”, if we
> modify it this way:
> $rU = $rU + “;npdi”;
> then we get a new $ru of “sip:+15555551212;npdi at gw1.com”.
> We send this call out and if it returns an error we want to use the
> next available gateway.
> The Request URI in the failure route is still
> “sip:+15555551212;npdi at gw1.com”.
> Note: this is the case even when the “;npdi” parameter was added in a
> branch route, which I didn’t expect. I thought changes made in a
> branch route were isolated to that branch.
> Now from the failure route when we call use_next_gw the npdi parameter
> is moved and the URI is now “sip:+15555551212 at gw2.com;npdi”. This is
> not correct.
> Is there some other way to properly manipulate SIP URI user parameters
> or is this a bug?
> Ben Newlin
> Users mailing list
> Users at lists.opensips.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users