Any inputs would be highly appreciated. Regards, Senthil
From: Senthil Pandian Sent: Monday, January 02, 2017 5:03 PM To: 'sip-implementors@lists.cs.columbia.edu' Subject: Routing logic at network when multiple clients co-exist on same device Hello all, Happy new year to everyone!! I have a question on implementation of RFC 3841. According to this spec, when we have 2 clients registered with different feature tags, one matching the incoming request's specification would be picked and contact with higher strength would be picked when both clients are registered with same/ overlapping feature tags. However, it has given some room for confusion (thanks to the Example section) and I thought it would be better to get this clarified here. Let me describe the issue with 2 cases. Case 1: 2 contacts having different feature tags from same user C1: F1; F2; q=1.0 C2: F3; F4; F5; q=0.5 Question: Can a request with Accept-Contact=F3;require be routed to C1? While I do NOT expect this to happen, I see a possibility of few implementations doing this way because C1 has not explicitly mentioned F3=FALSE so it could be considered for routing, as per RFC 3841. Case 2: 2 contacts having overlapping feature tags from same user C1: F1; F2; q=1.0 C2: F1; F3; F4; q=1.0 Question: Can a request with Accept-Contact=F1; F3; require be routed to C2 on priority? This is another variant of case 1 and C1 could be assumed to be supporting F3 as well as C1 has not explicitly stated F3=FALSE. In other words, is it safe to assume that missing feature tag can be interpreted as 'feature tag=FALSE'? Practically, it would be impossible for any client to know all the capabilities of the network and explicitly mention the unsupported features as FALSE. Thanks in advance and please throw some light on this. Regards, Senthil "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be privileged. If you are not the intended recipient. you are hereby notified that any review. re-transmission. conversion to hard copy. copying. circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient. please notify the sender immediately by return email. and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment." _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
