SIP Register - 401 Unauthorized

[rjb]

I've been using broadvoice for just under a year with no problems (expect for their outages). A couple of days ago I noticed that my service wasn't working. Turns out that my SPA-3K is failing to register. Poking around with a softphone shows that the SIP Register request is getting "401 Unauthorized" back. I've checked my auth / password settings from the BV account page and everything looks ok.

I've made no changes to my settings. I'm on comcast cable internet. My normal setup is a Sipura SPA-3000 behind a Linksys WRT54G router. I have UDP ports 5060, 5061 and 16384 - 16482 forwarded to the SPA3k.

My account appears to be fine (I've had no nasty emails from BV, and there's no sign of problems on my account page). I've tried contacting BV support by email and phone with no luck. Was wondering if there's anything else I can try.

[mberlant]

You should try removing the manual forwarding of ports from your router. I have done dozens of installations with this (or the GS) router, and have never needed to forward ports in order to make a SIP ATA work.

[dpoon]

I am also a Broadvoice subscriber with a Sipura 3000 whose relay started clicking on and off occasionally since December. There was one day when the service stopped working altogether; a packet sniff revealed that SIP registration was failing because their proxy was returning "401 Unauthorized" errors. After speaking to Broadvoice tech support, I found that they had changed the password on my VOIP account! Configuring the Sipura with the new password made it work again, but then I found that the relay has been clicking and dropping calls intermittently since then.

Today I finally had the time to do some troubleshooting. A packet sniff revealed that the Sipura was getting some Success and some Unauthorized responses to the registration requests. All of the successful requests came from UDP port 5060; all of the failed ones from port 5061. I deduced that the port 5061 requests were due to the VoIP2 interface. Configuring the PSTN Line not to register seems to have solved the problem; time will tell. (In the Sipura Web interface, logged in as admin, in the "PSTN Line" tab, set "Register" to "no".) I don't know how my Registration option got misconfigured in the first place. Probably accidental.

My guess is that Broadvoice has been cracking down on simulaneous usage of accounts by multiple devices, first by disabling my account by changing the password, then by denying my VoIP2 interface registrations, causing problems in both cases.

[mberlant]

BroadVoice has never permitted more than one device to be used at a time with any of their accounts. Each side of your SPA-3000 (Line 1 and PSTN Line) is a separate device in this context. Consider yourself lucky that all they did was change your password to wake you up to this violation.