[JeffJ]

My SPA9k is experiencing VoIP registration issues. For unknown reason, line 1 registration to VoIP provider stops at any given time.

My setup consist of having the SPA9k, SPA400, and 2 SPA941's at my location. Off premise from 2 locations there are 2 SPA941's connected to the SPA9k via VPN tunnel using Linksys WRV200 routers at all locations.

During any time period of 1-5 days, the SPA9k will loose registration and VoIP calls stop. PSTN calls via the SPA400 and between extensions continue to work. Rebooting the WRV200 only (SPA9k location) initiates registration again without restarting the SPA9k. When experiencing this issue, broadband connection was not lost, internet traffic flows fine, and VoIP provider having no outages. Replaced router and after a few days problem is back.

The SPA9000 admin guide states "

When using the SPA9000 behind a firewall or router, make sure that the following ports are not blocked: SIP ports—By default, UDP port 5060 and 5061 -
RTP ports—16384 to 16482 Also disable SPI if this function exists on your firewall. "

QOS is enabled for UDP 5060 & 5061 but I have no option for RTP & SPI on this router.

Using syslog, the PDF attatched shows events that take place but I am not familiar enough to interpret.

Suggestions very much welcomed...... router issue/quality, or SPA9k setting?

[humba3]

Looking at the traces I cannot find an obvious reason why the SPA9000 doesn't accept the registration response.. it matches the REGISTER request in both instances. You might wanna look at wireshark traces, too, to make sure there's not some difference you cannot see in syslog.

[JeffJ]

humba3,

Thanks for suggesting Wireshark/Wincap....got it downloaded. I will work to figure out how to pickup the UDP,RTP, and Sip info off the SPA and router. Fortunately todays outage happened 45min after close of business.

Other than dealing with this issue I am quite pleased with the LVS system. Stays up for weeks at a time without rebooting!

[humba3]

I will work to figure out how to pickup the UDP,RTP, and Sip info off the SPA and router.

You'll need switches with SPAN ports / mirroring or a hub (the switch is definitely preferable). Since it's a registration issue, I think it'll suffice if you just look at the SIP traffic. In the syslog, both registration replies (note that in both cases Telix accepts the registration) look the same (with the obious differences in cseq, tags and callid) but there most be some underlying issue, or your SPA9000 has an intermittent hiccup (if that's the case, it'll be a real bitch to resolve.. I hope you got your equipment from a registered Linksys LVS partner - or are one yourself as regular users and even regular Linksys VARs don't get any support on the SPA product line).

[mcannon-gso]

Originally Posted by JeffJ

My SPA9k is experiencing VoIP registration issues. For unknown reason, line 1 registration to VoIP provider stops at any given time.

My setup consist of having the SPA9k, SPA400, and 2 SPA941's at my location. Off premise from 2 locations there are 2 SPA941's connected to the SPA9k via VPN tunnel using Linksys WRV200 routers at all locations.

During any time period of 1-5 days, the SPA9k will loose registration and VoIP calls stop. PSTN calls via the SPA400 and between extensions continue to work. Rebooting the WRV200 only (SPA9k location) initiates registration again without restarting the SPA9k. When experiencing this issue, broadband connection was not lost, internet traffic flows fine, and VoIP provider having no outages. Replaced router and after a few days problem is back.

The SPA9000 admin guide states "

When using the SPA9000 behind a firewall or router, make sure that the following ports are not blocked: SIP ports—By default, UDP port 5060 and 5061 -
RTP ports—16384 to 16482 Also disable SPI if this function exists on your firewall. "

QOS is enabled for UDP 5060 & 5061 but I have no option for RTP & SPI on this router.

Using syslog, the PDF attatched shows events that take place but I am not familiar enough to interpret.

Suggestions very much welcomed...... router issue/quality, or SPA9k setting?

Jeff,

Have you resolved this issue? I am running a PAP2T device on a WRV200 and am experiencing the same issues..

If you have found the resolution, would you please post your findings/

Thank you in advance...

--Mike

[JeffJ]

Originally Posted by mcannon-gso

Jeff,

Have you resolved this issue? I am running a PAP2T device on a WRV200 and am experiencing the same issues..

If you have found the resolution, would you please post your findings/

Thank you in advance...

--Mike

Mike,

Sorry for the delay!

I have added another voip carrier to compare registration issues. Teliax is my main carrier for our dnis and picked up another local tn through Inphonex. Weird thing though...... all has stayed up for nearly 5 days and today I disabled Inphonex line on the SPA9000 this mornging and off course I check the system this evening, registration on line 1 through Teliax dropped again.

Humba3 has the best suggestion of monitoring the sip traffic but that is above my skill level at this time. Linksys had me turn on NAT though I am using an IP for the proxy.

[snoopho]

I am having registration errors to. I have the Linkysy spa9000 and a spa941 and i am using VONAGE. I just got off the phone with them and they said they dont support the spa 9000 or 941 and would not give me a proxy server add. do I have to use theirs, Do I need a different Voip Porvider???

How Can I get this phone to register.

Thanks
snoop

[humba3]

While figuring out the proxy/registrar and outbound proxy isn't too hard if you have some of their equipment (just trace the network traffic), getting the password will be tricky - I guess you could always read the RFC on how the auth header is constructed and see if there's a way to reverse engineer it (it might just be a simple base64 which is easy to reverse) and once you have that, you're golden. There's nothing preventing Vonage from blocking devices they don't like though.. your Linksys devices will report the firmware revision so Vonage could check that and only allow devices that report a vonage firmware.

I haven't seen much on Vonage but I guess using google, you'll find more information. This is more the forum to deal with provider independent technical problems.