I think the most important thing with outbound is that the UA must always maintain the TCP connection for the "flow".
Then for calls arriving at the SIP proxy, the call can be routed to the UA using the "flow". You have to keep the flow alive to receive calls. However this requirement does not stop you from making other SIP TCP connections. You are allowed to make as many as you want as long as you maintain the "flow" connection. Regards, Attila -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ivar Lumi Sent: 28 February 2008 09:29 To: [email protected] Subject: [Sip-implementors] TCP transport. Hi, According rfc 3261 18.1 For reliable transports, the response is normally sent on the connection on which the request was received. Therefore, the client transport MUST be prepared to receive the response on the same connection used to send the request. Under error conditions, the server may attempt to open a new connection to send the response. To handle this case, the transport layer MUST also be prepared to receive an incoming connection on the source IP address from which the request was sent and port number in the "sent-by" field. It also //------------------------------------- Request sending connection must also listen incoming connection on same local end point. From there comes that there can be only 1 connection between 2 SIP devices if both have only 1 IP address and they are listening in 1 port. device 1(192.168.1.10:5060) ------- device 2(192.168.1.10.5060) Or only possibility is to forge sent-by value to listening port and open each connection on it's own port. But this again brakes draft-ietf-sip-outbound-12.txt, if new ports every time, SIP proxy can't detect flow reconnect if connection braked. (If i get right flow is defined by local enpoint,remote endpoint and transport) Do i miss something or there is always 1 connection ? Any comments would be very welcome. Thanks, _______________________________________________ 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
