[sr-dev] GRUU and publish registration status
Olle E. Johansson
oej at edvina.net
Thu Aug 30 11:15:33 CEST 2012
30 aug 2012 kl. 10:22 skrev Iñaki Baz Castillo <ibc at aliax.net>:
> 2012/8/30 Olle E. Johansson <oej at edvina.net>:
>> Hi!
>>
>> Since we've learned that GRUU's are more or less semi-automatic I have of course a few more questions:
>>
>> - Is the usrloc module aware that a specific contact is using GRUU's
>
> AFAIK that's not "needed". When a request arrives to the proxy having
> ;gr param in the RURI, the proxy extracts the gr value, "decodes" it
> somehow (not need to have such a mapping in a DB) and gets the
> associated binding, so just such a binding would be retrieved form
> usrloc table when calling lookup().
That means that one - knowing the algorithm - can reach all contacts directly, regardless
if they have a gruu or not. Or?
>
>
>> - If so, is that reachable information for the pua-regloc to publish the gruu's?
>
> Note that such a feature would require implementing RFC 5628:
>
> http://tools.ietf.org/html/rfc5628
>
> "Registration Event Package Extension for SIP
> Globally Routable User Agent URIs (GRUUs)"
Yes. But to make it possible and to make it possible to restart kamailio without loosing information, I think we have no other option but to store a gruu flag in usrloc.
Of course, I might be totally wrong :-)
/O
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2307 bytes
Desc: not available
URL: <http://lists.sip-router.org/pipermail/sr-dev/attachments/20120830/015175f3/attachment.bin>
More information about the sr-dev
mailing list