Hi All,
Just confirming when using nathelper, the fix_nated_register function is only used to write corrected contact into to $avp then to database, this function does not actually change the contact in the SIP message when passing through the proxy, correct?
fix_nated_contact is used to actually change the SIP message contact when passing through the proxy. I'm using kamailio 4.2.
Thanks.
JR
That is accurate. The external IP info ends up in the received column/attribute.
On Wed, Feb 08, 2017 at 01:33:56PM -0600, JR Richardson wrote:
Hi All,
Just confirming when using nathelper, the fix_nated_register function is only used to write corrected contact into to $avp then to database, this function does not actually change the contact in the SIP message when passing through the proxy, correct?
fix_nated_contact is used to actually change the SIP message contact when passing through the proxy. I'm using kamailio 4.2.
Thanks.
JR
JR Richardson Engineering for the Masses Chasing the Azeotrope
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On 08/02/2017 20:33, JR Richardson wrote:
Hi All,
Just confirming when using nathelper, the fix_nated_register function is only used to write corrected contact into to $avp then to database, this function does not actually change the contact in the SIP message when passing through the proxy, correct?
fix_nated_contact is used to actually change the SIP message contact when passing through the proxy. I'm using kamailio 4.2.
You should use set_contact_alias() togheter with handle_ruri_alias() instead of fix_nated_contact(). It is safer for devices that are strict on checking r-uri.
Cheers, Daniel
-
Alex Balashov -
Daniel-Constantin Mierla -
JR Richardson