[OpenSIPS-Devel] [ opensips-Bugs-3028327 ] nat_traversal damaged between r6844 and r6972?

[Richard Revels]

I haven't checked this since I saw a note about fixing contact mangling on the list but, I found that nat ping was broke when I added a tag to the contact from within the config for register.   No idea when problem started.  

If your config is something like this:

modparam("registrar", "received_avp", "$avp(s:received_uri)")
modparam("registrar", "received_param", "received")
...

route[register-handle]
{
do stuff
$avp(s:received_uri) = $source_uri + ";aparam=regparam";
do stuff
}

Then you can get rid of the problem by not setting the received avp.

Richard

On Jul 12, 2010, at 10:51 AM, SourceForge.net wrote:

> Bugs item #3028327, was opened at 2010-07-12 11:19
> Message generated for change (Comment added) made by thomas_gelf
> You can respond by visiting: 
> https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3028327&group_id=232389
> 
> Please note that this message will contain a full copy of the comment thread,
> including the initial issue submission, for this request,
> not just the latest update.
> Category: modules
> Group: 1.6.x
> Status: Open
> Resolution: None
> Priority: 5
> Private: No
> Submitted By: Thomas Gelf (thomas_gelf)
> Assigned to: Nobody/Anonymous (nobody)
> Summary: nat_traversal damaged between r6844 and r6972?
> 
> Initial Comment:
> I didn't do any deeper investigation on this problem yet, however as of Bogdan's call for bug reports before 1.6.3 here is what I experienced:
> - upgraded from r6844 to r6972
> - noticed problems with some clients not longer "reacheable" most of the time
> - assured with xlog that nat_keepalive() has been called for those clients on their REGISTER requests
> - restarted OpenSIPS to dump keepalive_state_file
> - there has been no entry for those clients (manually checked just two of them)
> Immediately reverted back to r6844 as this happened on a live system with a few thousand users, did no farther testing. Did a quick look to SVN history, but wasn't able to find anything suspicious nat_traversal-related change. Just a wild guess: could it have been caused by the bug fixed in r7008?
> 
> Regards,
> Thomas Gelf
> 
> 
> ----------------------------------------------------------------------
> 
>> Comment By: Thomas Gelf (thomas_gelf)
> Date: 2010-07-12 16:51
> 
> Message:
> Pretty strange - this means the error should have been added somewhere
> between r6947 and r6972. However, there have mostly been changes to pua and
> b2b components, also sst - but I can see nothing related to nat_traversal
> and/or core components/parsing.
> 
> I would really like to stay with nat_traversal, as I consider it being the
> better architectured variant.
> 
> 
> ----------------------------------------------------------------------
> 
> Comment By: Vallimamod Abdullah (vabdulla)
> Date: 2010-07-12 15:41
> 
> Message:
> Got the exact same issue after upgrade to r6947 from r6924. See
> http://opensips-open-sip-server.1449251.n2.nabble.com/Nat-traversing-don-t-work-after-svn-upgrade-td5158840.html#a5158840
> 
> The only way I found to solve it was to drop nat_traversal in favor of the
> nathelper module.
> 
> 
> ----------------------------------------------------------------------
> 
> You can respond by visiting: 
> https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3028327&group_id=232389
> 
> _______________________________________________
> Devel mailing list
> Devel at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/devel