Per RFC 3261, the registrar would send requests outside of dialog to the registered Contact.
Per RFC 3261 concerning requests within dialog, the called party would send requests within dialog to the originating INVITE's Contact (unless Contact within dialog subsequent refreshed). However since clients typically have NAT concerns, you might want be interested in RFC 3581 and RFC 5626. > -----Original Message----- > From: [email protected] [mailto:sip- > [email protected]] On Behalf Of Guan Xsun > Sent: Wednesday, July 18, 2012 5:44 AM > To: Tarun2 Gupta > Cc: [email protected] > Subject: Re: [Sip-implementors] Does SIP client can use different port > for Register and Invite? > > HI, > Thanks! > But which port does SIP server should send , if there is a request > need > to send to that client? > > 2012/7/18 Tarun2 Gupta <[email protected]> > > > ** > > > > Theoritically yes, protocol imposes no such restrictions on use of > same > > port for **SIP** messages.**** > > > > ** ** > > > > Regards,**** > > > > **Tarun Gupta****** > > > > Aricent**** > > > > ** ** > > > > -----Original Message----- > > From: [email protected] [mailto: > > [email protected]] On Behalf Of Guan > Xsun > > Sent: Wednesday, July 18, 2012 1:39 PM > > To: [email protected] > > Subject: [Sip-implementors] Does **SIP** client can use different > port > > for Register and Invite? > > > > ** ** > > > > Hi,All,**** > > > > Does **SIP** Client can use different port for Register and > Invite?*** > > * > > > > That means a **SIP** client may use a port 5067 to send > **SIP**Register > > **** > > > > message to **SIP** server 5060 port , and use port 5068 port to send > **SIP > > ****** > > > > Register Message to **SIP** server 5060 port .**** _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
