On 5/28/13 10:09 AM, Kumarasami Parasuraman-QXVB36 wrote: > Hi, > > Is anywhere in the RFC said Processing / generating Request, Request-URI and > To URI should be same.
There is no requirement that they be the same. Typically they start out the same but the R-URI changes as the request is routed toward the destination. So it is quite normal that when the request is received by the UAS that the two are different. > While processing request Request-URI has, sip:domain.com and To URI has, > sip:[email protected]. Is the UAS can reject the request with 403 Forbidden. The UAS can return 403 if it wishes. That is indicative of a policy decision. The policy *could* be based on the To-URI or the From-URI, R-URI, or most anything else. (E.g., there could be a policy "we only accept calls *to* a URI we know", or "we only accept calls *from* URIs on a whitelist".) The "final" R-URI when the request reaches the UAS should identify the UAS itself. Normally a UAS wouldn't honor a request with an R-URI that it knows to be its own. (Though some are lax about this.) Typically a caller won't know the precise URI that identifies the UAS. Instead that is typically inserted by a proxy, based on registration by the UAS. Thanks, Paul > Please clarify me. > > As per the RFC3261(Character Escaping Requirements) , User part is optional > in both Request-URI and To URI. > > 19.1.2 Character Escaping Requirements > > dialog > reg./redir. Contact/ > default Req.-URI To From Contact R-R/Route external > user -- o o o o o o > password -- o o o o o o > host -- m m m m m m > port (1) o - - o o o > user-param ip o o o o o o > method INVITE - - - - - o > maddr-param -- o - - o o o > ttl-param 1 o - - o - o > transp.-param (2) o - - o o o > lr-param -- o - - - o o > other-param -- o o o o o o > headers -- - - - o - o > > Thanks > > Regards, > Parasu > > _______________________________________________ > 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
