section 16.4, Route Information Preprocessing, takes care of this. regards, ravi.
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of > [EMAIL PROTECTED] > Sent: Saturday, November 30, 2002 4:55 PM > To: [EMAIL PROTECTED] > Subject: [Sip-implementors] 16.5 Determining Request Targets > > > > > Hi, > Section 16.5 of RFC explains determining targets for a request. > This section doesnot consider existence of route header set in > the message. > > If the route headers are present, then the "top-most route will be > the target" instead of the request-URI. > > Therefore we need not go for processing the request-URI or > go for determining contact set or DNS resolution for the request-URI. > > Please clarify. > > regards, > Shrinivas Shetti > Hughes Software Systems Ltd. > http://www.hssworld.com/ > > > > > > > > This message is proprietary to Hughes Software Systems Limited > (HSS) and is > intended solely for the use of the individual to whom it is addressed. It > may contain privileged or confidential information and should not be > circulated or used for any purpose other than for what it is intended. If > you have received this message in error, please notify the originator > immediately. If you are not the intended recipient, you are notified that > you are strictly prohibited from using, copying, altering, or disclosing > the contents of this message. HSS accepts no responsibility for loss or > damage arising from the use of the information transmitted by this email > including damage from virus. > > > _______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
