Adding to what Dale said:
Even in 3gpp, a registration failure should not cause a deregistration.
Rather, state should be the same as if you hadn't done it at all.
So as long as you eventually get it right before the registration
succeeds you should not have a problem.
Of course, if you waited too long, and the registration times out
between your failed attempt and a successful one, then you would see a
problem. But I doubt that is your case - it would be a huge coincidence.
More likely the registrar is broken and is unregistering you when your
renewal fails.
Thanks,
Paul
WORLEY, Dale R (Dale) wrote:
> ________________________________________
> From: [email protected]
> [[email protected]] On Behalf Of Vivek Singla
> [[email protected]]
>
> 1) Should the Register renewal have the empty nonce. I think it should have
> the same nonce as the INVITE.
>
> 2) Should the call be dropped after 401 for the registration renewal? I am
> thinking since the Register renewal did eventually got the 200OK, may be MTA
> should have kept the call alive.
> _______________________________________________
>
> 1) The renewal can use any nonce it prefers. In many systems, the nonces
> time out much quicker than the time between successive registration renewals,
> so there isn't a lot to be gained by keeping the nonce around for
> registrations alone.
>
> 2) Your example is 3GPP, and it has a number of perversions. But in ordinary
> SIP, it would be considered an error for a UA to drop a call because its
> registration failed. Indeed, registration and making outgoing calls are
> entirely independent processes.
>
> Dale
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
