Re: Doubt related to URI parameters in remote-URI.

Vineet,
 
If remote target URI has transport parameter, you should send it using
the specified transport as per RFC3263.
The transport specified in Via sent-protocol transport should be set
accordingly.
 
-Rockson
   
________________________________

From: [email protected] [mailto:[email protected]] On Behalf Of
Vineet Gupta
Sent: Wednesday, October 01, 2008 12:55 AM
To: [email protected]
Subject: Re: [Sip] Doubt related to URI parameters in remote-URI.


Hi, 

I understand that the below questions might appear naive. However, I
would really appreciate opinion(s) on this, as this is required for my
design.

Regards,
Vineet.


On Wed, Sep 24, 2008 at 7:48 PM, Vineet Gupta <[email protected]>
wrote:


	Hi, 

	I have very basic doubt related to URI parameters present in
remote-contact URI (i.e. top-most Route URI or Remote Contact URI).

	Case 1: The remote-URI contains URI parameters like
transport=TCP and comp=sigcomp once INVITE dialog is established.
	a) Is it mandatory for all the requests within the dialog to
have transport=TCP and comp=sigcomp in the via header, there forcing
compression and TCP transport for any connection within the dialog.
	b) Can I send some request within the same dialog by retaining
these parameter in the request-URI, but not them copying them onto the
via header, thereby sending the request uncompressed and on UDP.

	Case 2:  The remote-URI does not contain any URI parameters.
	a) Can any request within the dialog be sent with any parameters
like transport=tcp;comp=sigcomp by putting them in via header
irrespective of the way first request within the dialog (Ofcourse,
keeping the capabilities of remote in mind) ?

	In general, do the parameters in the remote URI have any binding
on requests within the dialog?


	Regards,
	Vineet.

_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email protected] for questions on current sip
Use [email protected] for new developments on the application of sip