From: "P Sudarshanakrishnan-A14377" <[EMAIL PROTECTED]> Assuming A registers contacts A1, A2. When a network entity initiates a notification I am not sure if there is a possibility that it indicates different attributes (say rejected for A1 and probation for A2) for the individual contacts A1 & A2.
Assuming both registrations are done in one REGISTER message, they either both succeed or both fail. But even then, there is no requirement that the registrar treat them identically. For instance, the registrar may return different expires values for different contacts. If there is a probation process, the two contacts may be treated differently by it. Etc. And there is (as far as I know) no reason that the reg events may not report the registration of A1 and the registration of A2 in separate events (although they would be closely-spaced): First "no contacts", then "A1 registered", and then "A1 registered, A2 registered". If the device register the same expires value for A1 and A2 and intends to keep them both registered with appropriate refreshes I don't see why the server would need to indicate different states for those contacts ever. Any use cases? If the question is "Is there something the UA can do to ensure that the states of A1 and A2 are always the same?" the answer is "No." If the question is "Can the registrar assume that A1 and A2 will always have the same state because it knows the UA will be carefully attempt to keep them the same?" the answer is "No, because some UA will inevitably do something that desynchronizes the states of A1 and A2." You really have to handle the states of A1 and A2 individually. Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
