Hi, Anton!
Calling fix_nated_contact() in the on_reply route is the way to do it,
no other work around. Try to make sure the function is actually called
for your reply, perhaps the route is not actual executed for that reply.
You can double check by printing some xlogs "guarding" the
fix_nated_contact() and check if they appear in your logs.
Best regards,
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 4/19/23 15:28, Anton Danilov wrote:
Hello, everyone.
I've faced a strange issue: incorrect port number in the contact
header of 200 Ok reply causes ACK loss and dialog termination.
Here is the UML diagram in svg format (also in the attach):
https://drive.google.com/file/d/1ti5SjpV3H8SM6rHovAbBOL86ZSu9N2x2/view?usp=share_link
I've tried to fix this with the fix_nated_contact() function in the
on_reply route, but it seems like it doesn't work - the port number is
still unchanged.
Is there a way to fix it without manual manipulation with regular expressions?
--
Anton Danilov.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
