On Wed, 2006-07-19 at 10:38 +0530, [EMAIL PROTECTED] wrote: > 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.
RFC 3261 does say (section 10.3 Processing Register Requests): REGISTER requests MUST also be processed atomically, meaning that a particular REGISTER request is either processed completely or not at all. That would argue, I think, for rejecting the request, but there are counter-arguments. As you point out, you do have the opportunity to indicate which bindings worked by only returning those Contacts and not returning the others. I wouldn't do it that way - I'd reject the whole thing if any binding is not acceptable (and put text in the response line and a Warning header explaining why). This is the only way to be sure that the user ends up getting an indication that something is not working. I've also seen too many UAs that try to reregister at wire speed when they get confused about the returned Contacts. An even better solution in this case is to add support for TCP. -- Scott Lawrence tel:+1-781-938-5306;ext=162 or sip:[EMAIL PROTECTED] sipXpbx project coordinator - SIPfoundry http://www.sipfoundry.org/sipX Chief Architect - Pingtel Corp. http://www.pingtel.com/ _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
