On Wed, 2009-12-02 at 13:14 +0530, hanifa.mohammed wrote: > "However, a UA MUST be prepared for the public GRUU to change from a > previous one, since the > persistence property is not guaranteed with complete certainty." > > So, even for a refresh-REGISTER, the public GRUU may be different. In > that case, for all > existing sessions that uses the previous Public GRUU, UA must send > target-refresh request, to update > the contact. > > Wont the registrar keep the old public GRUU as valid till the user > de-registers?
There is no guarantee of anything. The safest course of action is the target-refresh that you describe. (Conveniently, if the UA sends a target-refresh request, its previous GRUU contact need no longer be valid for the request to succeed.) But if you expect GRUU changes to happen very infrequently, and are not very concerned about reliability, the UA can simply use the GRUU for all future requests. Currently active calls might fail, but new ones will succeed. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
