Refer to Section 10.2.1 in RFC 3261: "The 2xx response to the REGISTER request will contain, in a Contact header field, a complete list of bindings that have been registered for this address-of-record at this registrar."
The registrar will only add those URIs in the Contact headers for 200 OK for which it has been successfully been able to create a AOR binding. As for the differentiation between TCP & UDP, I think it can be done in a way similar to the original INVITE request: Contact:..@<...>;transport=udp If the registrar does not support TCP, it will not add the corresponding CONTACT header in 200 OK. A similar thread for INVITE might help: https://lists.cs.columbia.edu/pipermail/sip-implementors/2004-July/006694.ht ml I hope this helps. Regards, Gaurav -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, July 19, 2006 10:38 AM To: [email protected] Cc: [email protected] Subject: [Sip-implementors] How to reject a binding for REGISTER Hi, If registrar receives a REGISTER request with two Contact headers, and registrar wants to register only one binding, how it can indicate this in the response message (should it omit the Contact header not supported in 200 ok response) One scenario happening is UAC sending two Contact headers with same IP and port but protocol as TCP and UDP, but server does not support TCP, so it want to only create binding for UDP Contact header, so it wants to indicate to UAC that it has created only one binding. Thanks, Udit _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
