Jonathan,
A minor remark about the temporary GRUU algorithm in A.2: if the UAC is
using outbound and registers 2 Contacts under the same AoR and instance-id,
the algorithm in A.2 currently cannot distinguish between those contacts
(since the temporary GRUU only contains an index which resolves to an
AoR+instance combination). Therefore, if the Contacts URIs are different
(for example: different user part) the proxy is not able to reproduce the
correct URI when rewriting the request URI.
Concretely: when a UAC registers e.g.
Contact: <sip:[EMAIL PROTECTED]>
;+sip.instance="<urn:uuid:0C67446E-F1A1-11D9-94D3-000A95A0E128>"
;reg-id=1Contact: <sip:[EMAIL PROTECTED]>
;+sip.instance="<urn:uuid:0C67446E-F1A1-11D9-94D3-000A95A0E128>"
;reg-id=2the proxy returns two distinct temporary GRUUs. However,
regardless of which temporary GRUU the UA chooses to use, the proxy cannot
determine whether to rewrite to "callee-001" or "callee-002"
This can easily be remedied, e.g. by including the reg-id in the mapping
Regards,
Jeroen
_______________________________________________
Sip mailing list https://www1.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