Have a look at the so-called "outbound" draft: http://www.ietf.org/internet-drafts/draft-ietf-sip-outbound-08.txt
When you register with TCP, the TCP connection is kept-up with some kind of keepalive (see section 4.4. Detecting Flow Failure). With UDP, you can keepalive the connection with STUN or, though not recommended, you can keep the NAT-binding alive with frequent re-registration. Regards, Attila -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ivar Sent: 20 April 2007 09:26 To: [email protected] Subject: [Sip-implementors] REGISTRATION TCP Hi, Googling, seeing rfc 3261 seems i miss some thing .... How register method over TCP acts ? Does register contact binding must hold reference to TCP connection what made register ? If not then how then you never can connect LAN SIP device over TCP and UDP won't work too because phone haven't sent packet out. If registration keeps connection and all request to that SIP device will be sent through that connection i get how that will work. unknown UA 1 -> invite -> proxy, proxy will reuse registration TCP connection -> UA 2 Any comments very welcome. _______________________________________________ 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
