If there is a stale indication in the challenge sent to Linksys and
there is no retry -> it is Linksys's fault; If there is not "stale"
indication in the reply -> opensips's fault.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 29.05.2014 14:09, Alexander Mustafin wrote:
Hi, Bogdan. Thanks for reply.
You’re right! But now, I’ve seen «Failed» status on Linksys, and it
trying to re-authenticate over and over. Maybe, this problem related
with other reasons. I will sniffing traffic…
Best regards,
Alexander Mustafin
[email protected] <mailto:[email protected]>
29 мая 2014 г., в 16:51, Bogdan-Andrei Iancu <[email protected]
<mailto:[email protected]>> написал(а):
Hi Alexander,
"Stale nonce" is not an error actually - it means the nonce is no
more valid . This may happen because:
- it is expired
- it was reused by UAC for more than one auth
If OpenSIPS detects such a case, it sends a new challenge with a new
nonce (and state indicator) - the UAC must simply re-authenticate
with no problem
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 29.05.2014 13:34, Alexander Mustafin wrote:
Hello!
I’ve many problems with registered user. Their registrations
periodically failed with error: «Stale nonce».
Why this happens? Buggy clients (I use Linksys and Cisco adapters)?
What I need to do? If I increase this time, or disable check_nonce -
is this very dangerous?
Now, I’m use default value: modparam("auth", "nonce_expire", 30).
Best regards,
Alexander Mustafin
[email protected] <mailto:[email protected]>
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
