Hello all,
there is some implementation towards these extensions done by SER folks in the past (quite some long time ago, when gruu was a draft), some notes in the readme: http://kamailio.org/docs/modules/stable/modules_s/registrar.html#sip.instanc...
Now, I don't how much the specs in the draft were changed by the time of becoming rfc (I haven't read neither these drafts nor rfcs). The inconvenience is that we have two implementations for usrloc/registrar at this moment, but for next release (i mean 3.3) could be a nice task and pleasant work for the volunteers here to merge the two implementations and update with outbound/gruu. Just announce it when the works starts so there is no duplicated effort :-)
To answer to the initial question, this rfc (in the subject) is not in my todo, but that may change before 3.3 (decision to be made when I have time to read the rfcs and can assert properly usability), although I hope it will not be the case to code it myself because someone else will do it...
Cheers, Daniel
On 10/10/11 10:36 PM, Iñaki Baz Castillo wrote:
2011/10/10 Alfred E. Heggestadaeh@db.org:
what is the relationship between gruu and outbound ? GRUU (RFC 5627) has a normative reference to Outbound (RFC 5626), probably because of +sip.instance. Outbound has an informative reference to GRUU spec.
IMHO Outbound is a real need (since NAT and TCP clients do exist), while GRUU is a cool feature, but not a requirement for the core protocol.