On Mon, 2009-04-13 at 10:49 -0400, Paul Kyzivat wrote: > Its been quite awhile and my memory may be getting a little fuzzy on > this, but... > > As I recall there are some very subtle points about this. There are > cases where someone other than the UA doing the registering may need the > gruu. So the UA that registers its contact may not support GRUU, the > gruu need be allocated so others can use it. For instance, if some other > UA registers the same AOR, and does support gruu, it will get back all > the contacts, and should get back gruus for all of them. Similarly, any > who subscribe to the reg event package.
You're correct. It was explicitly designed that the registrar would create a GRUU even if the UA registering did not support GRUU. In particular, this GRUU would be visible in reg events for the AoR in question, which allows *other* UAs that want to know the GRUU of the registering UA to find it. (E.g., the sipX open-source PBX takes advantage of this.) Dale _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [email protected] for questions on current sip Use [email protected] for new developments on the application of sip
