[SR-Users] Setting up TLS between proxy and authentication server

Hello, I am testing TLS communication with Kamailio 3.0.2, and I encounter a strange problem. My setup is like this: Client <-UDP-> Proxy server <- TLS with client certificate authentication -> Authentication server 192.168.24.1 192.168.24.128 192.168.24.129 The two servers are instance of Kamailio 3.0.2 When the client sends a REGISTER, the proxy retransmits the message to the authentication server, which sends back a 401 Unauthorized. But it seems the proxy closes the TLS connexion right after forwarding the REGISTER, and doesn't receive the 401 message. The TLS handshake is OK, and the client certificate is required (I didn't add the verification part yet). The REGISTER message goes through TLS, and is received by the authentication server. Then, the proxy sends a TLS alert (Close-notify), and after that message, the authentication server sends back the 401, and the proxy ignores that message. Could it be caused by a timeout? Is there a way to keep the TLS connection opened? Here are the relevant files (I don't like to send mails of more than 100 lines): authentication server configuration: http://pastebin.com/QBmnNc4e authentication server log: http://pastebin.com/uYdHDG5G proxy server configuration: http://pastebin.com/8WPPJBtM proxy server log: http://pastebin.com/JTwJSKtk I am just testing TLS, so I have tried to remove most of the irrelevant parts. Best regards, Geoffroy ________________________________ Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? du groupe Atos Origin ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.