#299 nat_traversal damaged between r6844 and r6972?

1.6.x
closed-fixed
modules (454)
5
2010-07-12
2010-07-12
Thomas Gelf
No

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

Discussion

  • Thomas Gelf
    Thomas Gelf
    2010-07-12

    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.

     
  • Fixed by commit 7008 - there was a problem with parsing of the "expires" contact param.

    Regards,
    bogdan

     
    • assigned_to: nobody --> bogdan_iancu
    • status: open --> closed-fixed