Any changes in SIP NAT traversal handling between TB K26 beta 52 and 54?

Discussion in 'Tomato Firmware' started by humba, Feb 14, 2011.

  1. humba

    humba Network Guru Member

    Last Thursday I upgraded my router from beta 52 to beta 54. Shortly thereafter, I updated my PBX to the latest release as well.
    Everything came back up and was running fine, but during the night, I lost the registration on two of my sip lines (with the same provider) - the lines never came back up.

    After a bit of looking around, I noted that for that particular provider, when I have STUN active (default setting), the PBX sends out an INVITE with the public IP (the correct one).. and no response ever comes in. If however I disable STUN, the INVITE contains the private IP of the PBX, and everything works out just fine. The thing is.. STUN has been working for more than the last 3 years (using a variety of routers.. first with Linksys standard firmware, then various Tomato releases and more recently Teddy Bear's K26 builds on the RT-16N).

    I already downgraded the PBX software again (thank god I kept a backup of the config prior to upgrading as a downgrade wipes everything) - I guess I'll try downgrading the router firmware next but I was just wondering whether there was some change not mentioned in the release notes that could have something to do with it (at this point I'm looking at all the options - rollback, talk to the PBX makers and IPTSP).
  2. teddy_bear

    teddy_bear Network Guru Member

    Try turning off the SIP helper on the Advanced->Conntrack/Netfilter page.

    SIP helper in all released K2.6 builds is old and buggy - may work with some providers and/or client configurations but not with others etc. The next Tomato USB build will include a major backport of the SIP helper from upstream kernel - hopefully it will resolve some of the problems people experienced. Anyway there's no need to use STUN and the SIP helper at the same time - if the SIP helper is working properly you won't need STUN.
  3. humba

    humba Network Guru Member

    Thanks for your reply.

    I actually rolled back the firmware version to beta 52 in the meantime - and things are the same. So it looks like the IPTSP changed something on their end.. I already have a ticket open but they're taking their sweet time responding. In the meantime I just disabled STUN for this particular IPTSP.
    I also have NAT keepalive turned on anyway (that worked even with the original firmware of the WRT54GL).. STUN is probably overkill but it was on by default when I got the PBX so I kept it on.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice