PBXes (http://www1.pbxes.com/forum/index.php)
- English (http://www1.pbxes.com/forum/board.php?boardid=16)
-- Terminal Equipment (http://www1.pbxes.com/forum/board.php?boardid=21)
--- RE: Sip Authentication Failure (http://www1.pbxes.com/forum/threadid.php?threadid=1364501114)


Posted by skyii on 28.03.2013 at 22:05:

Sip Authentication Failure

Hi,
We have 2 Cisco SPA525G2 (1 wifi & 1 Lan) and 1 SPA942 connected on 3 differents extentions.
For about a 3 weeks now, the phones often lose the registration and have difficulties to reconnect with an error (Sip Authentication Fail). When i unplug and replug the phone or wait for the next registration it register again..
This is not a router problem because the phones are connected to pbxes from differents internet access in different countries.
If you have any idea...
Thanks for your help.
Luc


Posted by fsaunier on 08.04.2013 at 11:29:

RE: Sip Authentication Failure

Hi,

I have a similar problem.

As of today, I can no longer register to my extension #1505 using my ATA (cisco SPA112). On the pbxes status page, my extension is marked as online, although it isn't. I have deleted the extension and recreated it with a new password -- it was immediately seen as online by pbxes although it wasn't. I have created a new extension (#1200) and the ATA fails to register to it. That new extension, however, is correctly seen as being offline on the status page. The ATA does have access to the internet, as it does connect directly to the trunk.

I can connect to my sipdroid extension without any issue.

This has happened after I tried to switch from www3 to www1 after I read on the forum it could possibly help solve a betamax-related issue, which it didn't. I switched back to www3, and since then my ATA can no longer register.

Any help/suggestion welcome.

Kind regards,
Fred

UPDATE:
After maybe 2 hours, the status page shows extension 1505 as offline, which is on par with its current state. The ATA still cannot register though :o(

2ND UPDATE:
I checked the ATA again, after maybe 4 or 5 hours, to find it connected. I did nothing in the interval, leaving the ATA trying to register on and on endlessly. I'm glad it now works, but at the same time am a bit frustrated I don't know what happened and why it couldn't register earlier.

Powered by: Burning Board Lite 1.0.2 © 2001-2004 WoltLab GmbH
English translation by Satelk