> Now 1st registration already vanished and for that > registrar send notify message which showing this > Notify is to terminate old registration with > subscription state is terminated reason deactivated > and expire =0. Here sbc sending same notify to > user A and deleting new registration entry from sbc. > Once user A recive this notify it automatically deregister.
If I understand the issue correctly, a race condition is causing ambiguity concerning which registration has been terminated. Including the optional callid attribute within NOTIFY is one way to remove the ambiguity. However if not included, it looks like the client needs to re-register (as indicated within rfc3680 section 3.1 and create another subscription) to remedy the situation. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
