[OpenSIPS-Users] Removing INVITE Contact from Reply (2.1.5)

mwb mwbazdarich at yahoo.com
Tue Apr 20 18:15:02 EST 2021


 Solved / Follow-up:We found that $ds was being populated in a previous route by way of an $rU assignment. Once we moved that assignment to an area specifically for "scenario #1" (sending the call on to an LNP provider) we found that $ds no longer had the INVITE RURI info populated and thus we could respond only with the URIs that we added in via branch adds.

    On Tuesday, April 20, 2021, 01:05:14 AM PDT, mwb <mwbazdarich at yahoo.com> wrote:  
 
 Hello,I posed a questions a few months ago and received some helpful advice from a user here but I'm having an issue implementing it properly.
We have a redirect server using OpenSIPS 2.1.5 that does LNP dipping with a little bit of routing as well. 
There are two scenarios:
1. There is No RN/NPDI in the RURI (so the redirect server sends a LNP request to an external LNP server
2. The INVITE has RN/NPDI in the RURI so no LNP dip is dispatched.
In the second scenario we do a few operations and generate URIs to embed in a 302 reply using the send_reply function in a . The issue we are running into is that it appears the $ds variable is being populated with the INVITE Request URI (RN and/or NPDI) info and it is being sent as the "top" Contact header in the 302 response. 
I have tried a few different things, including "remove_branch(0)" but they don't seem to be able to clobber the value in the $ds variable. It also seems impossible to use $ds as an LVALUE to try and overwrite it (this is consistent with the documentation which says it is not r/w).
Is there a way to:
1. Clobber the $ds variable?2. Preclude the $ds variable from being inserted as a Contact header in the reply?3. Keep the $ds variable from being populated when the initial INVITE is received.
Thanks!  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210420/219fc82a/attachment-0001.html>


More information about the Users mailing list