Hi, Actually rfc 3261 describes all ...
But in general SIP client opens connection sends request, keeps connection alive at least while it gets response. But it's good idea to keep connection alive for ever(sending CRLF at some interval), why ? Because most client are behind NAT and server never can establish connection back to client. 2) Could each subscriber's SIP register and calls share a TCP If destination is same, you should always reuse connection. Just imagine that TCP is tunnel but no like session SMTP. 3) To receive calls you always need to register. jc.huang wrote: > Hi All, > > I want to know how to implement TCP connections in SIP, are there some > documents describe them? I saw some people in the mailist ever discussed > it, but I don't know their conclusions? > I wanna know, > 1) SIP client and server use one TCP connection or several separate TCP > connections for sending or receiving SIP messages during a transaction > procedure, i.e. sending REQUEST uses a TCP connection, and close it, and > then create another TCP connection for sending RESPONSE? > 2) Could each subscriber's SIP register and calls share a TCP > connection? i.e., after a successful registration, SIP client will go > on to keep the TCP connection for subsequent calls until de-registration? > 3) If 2) yes, how about re-register process? if a TCP connection is > maintained between SIP client and server, is re-register not needed yet > because we could check TCP status? > > please tell me your opinions or implemations about it. > > Thanks and Regards, > > JC > > > > _______________________________________________ > 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
