[SR-Users] Close TLS connection and Registrar Server (Kamailio V1.4.x)
edson.gomes.leme
edson.gomes.leme at uol.com.br
Sun Apr 11 13:58:13 CEST 2010
Hello,
We are using Kamailio V1.4 with TCP/TLS.
The Kamailio is configured the TCP lifetime to the expire value of the REGISTER by using the tcp_persistent_flag parameter of Kamailio's registrar module. Note: The SIP proxy should not close the TCP connection as it is not capable of opening a new one.
Kamailio tries to open a TLS connection to the client. The Kamailio should use the existing TLS/TCP connection that was established by the client during registration.
We are applying NAT traversal techniques to instruct Kamailio to reuse the established TCP/TLS connection. Example: for each register call fix_nated_register(). For every other request and response call fix_nated_contact().
I have got one SIP phone registered via TLS to kamailio-1.4.X version with Expires = 3600.
phone1: connected via ip1:port1 and Expires = 3600.
Example: After 15 minutes TLS connection is closed.
The SIP Phone opens a new TLS connection and registers via TLS to Kamailio. Thus, we have the following records on the Registrar Server (Kamailio):
phone1: connected via ip1:port1 and Expires = 2700 [3600 – (15 min * 60 s) = 2700].
phone1: connected via ip1:port2 and Expires = 3600.
Is this the desirable behavior? Shouldn’t the Kamailio (Registrar Server) delete the below registry?
phone1: connected via ip1:port1 and Expires = 2700 [3600 – (15 min * 60 s) = 2700].
Best regards!
Edson G. Leme
More information about the sr-users
mailing list