[Serusers] Response is OK, but nonce is stale?
Jan Janak
jan at iptel.org
Tue Oct 5 12:29:32 CEST 2004
I am not aware of such problems with Sipura, but it is possible
(especially if it works with other devices).
Jan.
On 04-10 17:09, AJ Grinnell wrote:
> Do sipura spa-2000s have problems with nonces then? I can have my
> sipura register for one cycle, then not again untill reboot. It seems
> to be holding onto the stale nonce. I tried to use a Grandstream
> BT100, and it seemed to work ok. I have noticed that with both
> devices, I am seeing at least 5 register requests every time, and all
> five are being authenticated just fine via radius. Any thoughts
>
>
> On Mon, 4 Oct 2004 03:03:05 +0200, Jan Janak <jan at iptel.org> wrote:
> > Nonces have limited validity (1 minute by default). If the UA tries to use
> > credentials with an expired nonce, it gets 401 or 407 back and the
> > digest challenge would contain stale=true parameter. It basically
> > means that the username and password was OK, but the nonce had expired.
> > The user agent is supposed to send a new request with updated nonce
> > (sent by the server in 401 or 407) without asking user for the username
> > and password again.
> >
> > Jan.
> >
> > On 28-09 12:56, AJ Grinnell wrote:
> > > Getting closer here to making SER and Radius work together, but what
> > > does Response is OK, but nonce is stale
> > > mean. Why is it stale, and how can i freshen it?
> > >
> > > _______________________________________________
> > > Serusers mailing list
> > > serusers at lists.iptel.org
> > > http://lists.iptel.org/mailman/listinfo/serusers
> >
>
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
More information about the sr-users
mailing list