I dont believe that is true. You can use an ephermel port while sending messages on UDP and can expect responses to arrive on the default port/port on which you are listening. You only need to listen on the default ports. The above holds true * as long as you dont include an "rport" parameter (that tells the proxy to record the port on which you sent the request for response routing). * specify a port number other than the default port where you want your response sent. Responses are sent to the IP address/port in the Via header to the default port (so for UDP, responses will be sent to 5060).
Venkatesh On 5/2/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi, > > Yaah even I perceive the same behaviour from the RFC pint of view. > > So basically it boils down to either use the same socket for sending and > listening i.e. 5060 port > > becoz if you are using ephemeral UDP port, then you have to listen for > reponses on same port, which is not what an applciation desired for the > usage of ephemeral port.. because you can use multiple socket for sendign > the request and hence creating multiple ephemeral port which server would > not like to listen to.. > > Cant we have some paramter in Via header, may be "sender-port" which > application set it to ephemeral port, > so that if proxy receives this request, it checks if "sender-port" is > present, it matches it with the UDP source port for firewall related > checks, > otherwise it checks with the sent-by filed. > > For sending responses, behaviour can be same as it is now.. > > Regards, > Udit > > [EMAIL PROTECTED] > Sent by: [EMAIL PROTECTED] > 05/02/2005 03:09 AM > > To > Udit Goyal/C/US/[EMAIL PROTECTED] > cc > [EMAIL PROTECTED], SIP Implementors > <sip-implementors@cs.columbia.edu> > Subject > Re: [Sip-implementors] Fw: Via header > > > Udit, > I was waiting for someone more savvy than me to answer this one but I > will just have to dissapoint. I had a read of relevant section in 3261 and > 3263. > > If the UAC populated the sent-by field with IP address and not a port > that this will result in the UAS processing this to use the default port > for the transport - so for your example over UDP = 5060. The UAC could > have > included the ephemeral port in the sent-by field and regardless - yes, it > needs to listen on it. > > I hope the above is accurate, Wayne. > > Query from Udit: > **************************************** > > Can anybody please comment on this query.. > ----- Forwarded by Udit Goyal/C/US/3Com on 05/01/2005 10:05 PM ----- > > Udit Goyal/C/US/3Com > 04/28/2005 12:15 PM > > To > SIP Implementors, SIP IETF > cc > > Subject > Via header > > Hi, > > Conside a case where UAC uses different UDP sockets for listening and > sending SIP requests, > i.e it is listening on port 5060, but when it sends request, it uses > ephemeral UDP port. > > When this UAC sends INVITE request, it will contain Via header containing > the IP address and port number 5060 in sent-by field > But the UDP source port number will be different (IP address will be same) > as it had used UDP ephemeral port for sending that request. > > Now when proxy receives this request, it will check for IP address, since > it is same it will not add "received" parameter. However, port numbers are > different, should it add "rport" parameter ?? but this is not case of > firewall.. > or proxy only check for port when the IP addresses are different ?? > > Also, it seems that is it necessary for UA to listen on the same socket > from which requests sent ?? > > Regards, > Udit > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@cs.columbia.edu > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > > ********************************************************************** > Any personal or sensitive information contained in this email and > attachments must be handled in accordance with the Victorian Information > Privacy Act 2000, the Health Records Act 2001 or the Privacy Act 1988 > (Commonwealth), as applicable. > > This email, including all attachments, is confidential. If you are not > the > intended recipient, you must not disclose, distribute, copy or use the > information contained in this email or attachments. Any confidentiality > or > privilege is not waived or lost because this email has been sent to you in > error. If you have received it in error, please let us know by reply > email, delete it from your system and destroy any copies. > ********************************************************************** > > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@cs.columbia.edu > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@cs.columbia.edu > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list Sip-implementors@cs.columbia.edu http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
