Varadhan Work <varadhan.w...@gmail.com> writes: > Suppose, > SIP Domain name: *mydomain.org <http://mydomain.org>* > SIP Port: *8060*
> Question is, > If Req-URI received [by the Registrar] without port number on SIP > server listening port 8060 as follows, > > *REGISTER sip:mydomain.org <http://mydomain.org> SIP/2.0* > > a) Can domain name without port number, should be allowed for the same 8060 > port routing ? > and > should be manipulated based on received(socket) port number ? The standards do not truly fix the behavior in this case, because the Registrar that receives the message is allowed considerable latitude regarding what bindings it records and what their meanings are. But in general, Mohit Soni's answer is the best practice: sip:mydomain.org is a different domain from sip:mydomain.org:8060 and the Registrar for sip:mydomain.org:8060 should either reject this message or forward it to sip:mydomain.org. The particular situation where this behavior is needed is if the host mydomain.org has two SIP systems, one listening on port 5060 using domain sip:mydomain.org and one listening on port 8060 using domain sip:mydomain.org:8060. In that situation, the two systems should operate independently, and that requires that both of them are strict about handling REGISTER messages. Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
