On 12/4/13 4:34 PM, Greg Burrow wrote:
> Hello,
>
> After initial registration, the subscribers AOR has a single contact
> binding assigned in the registrar. If the client crashes and then
> recovers, it will re-register and the 200OK will contain the previous
> contact binding along with the new binding.
What you say is true *if* the client uses a different contact for the
new binding. If it uses the old contact again, then not.
> In this case is it recommended for the client to de-register the previous
> binding?
If you have some way to know with certainty that the old binding is
yours, and not for some other UA, then it is ok and perhaps wise to do this.
If you are not certain, then it's a bad idea.
> Can this be done by explicitly listing the old contact binding
> (with exipres=0)
yes.
> or does the de-register need to use contact='*', remove
> all bindings, and force the client to re-register? If the client has a new
> IP address after recovery from a crash (and a new sip.instance value), can
> the old binding still be removed?
If you are using RFC 5626 then things get a little more complex.
Why would you have a new sip.instance value? The whole point is that
those should be stable over time.
Thanks,
Paul
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
