Hello,
I am trying to do a performance test of OpenSER (1.3.0) with TLS using SIPP as the UAS/UAC.
The TLS authentication seems to work and the calls are stablished and then terminated (SIPP default scenario). However, I am receiving the following error message from OpenSER:
Feb 19 12:58:40 [12709] ERROR:core:_tls_read: something wrong in SSL: Feb 19 12:58:40 [12709] ERROR:core:tcp_read_req: failed to read
What do these messages mean? Can I ignored them?
The SIP command I am using is:
sipp -s 100 -sn uac 192.168.1.10:5061 -t ln -tls_cert 101-cert.pem -tls_key 101-privkey.pem
The TLS configuration I am using in my openser.cfg file is:
disable_tls = no listen = tls:192.168.1.10:5061 tls_verify_server = 1 tls_verify_client = 1 tls_require_client_certificate = 1 tls_method = SSLv23 tls_certificate = "/openser/etc/openser/tls/proxy/proxy-cert.pem" tls_private_key = "/openser/etc/openser/tls/proxy/proxy-privkey.pem" tls_ca_list = "/openser/etc/openser/tls/proxy/proxy-calist.pem"
I will appreciate any help about this matter.
Thanks, JB
_________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Hi John,
The error: Feb 19 12:58:40 [12709] ERROR:core:_tls_read: something wrong in SSL:
comes from the SSL_read() function - this returns error, but the err code is not identified - so we cannot say what the problem is.
Maybe I will add some extension to the log statement in order to print the error code.
Regards, Bogdan
John Barry wrote:
Hello,
I am trying to do a performance test of OpenSER (1.3.0) with TLS using SIPP as the UAS/UAC.
The TLS authentication seems to work and the calls are stablished and then terminated (SIPP default scenario). However, I am receiving the following error message from OpenSER:
Feb 19 12:58:40 [12709] ERROR:core:_tls_read: something wrong in SSL: Feb 19 12:58:40 [12709] ERROR:core:tcp_read_req: failed to read
What do these messages mean? Can I ignored them?
The SIP command I am using is:
sipp -s 100 -sn uac 192.168.1.10:5061 -t ln -tls_cert 101-cert.pem -tls_key 101-privkey.pem
The TLS configuration I am using in my openser.cfg file is:
disable_tls = no listen = tls:192.168.1.10:5061 tls_verify_server = 1 tls_verify_client = 1 tls_require_client_certificate = 1 tls_method = SSLv23 tls_certificate = "/openser/etc/openser/tls/proxy/proxy-cert.pem" tls_private_key = "/openser/etc/openser/tls/proxy/proxy-privkey.pem" tls_ca_list = "/openser/etc/openser/tls/proxy/proxy-calist.pem"
I will appreciate any help about this matter.
Thanks, JB
Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ _______________________________________________ Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
Hello Bogdan,
Could you give me any additional advice/suggestion about how to solve this problem? I have been trying with different TLS configurations but I am getting the same error.
Have you seen this problem before?
Thanks for your help, JB
Bogdan-Andrei Iancu wrote:
Hi John,
The error: Feb 19 12:58:40 [12709] ERROR:core:_tls_read: something wrong in SSL:
comes from the SSL_read() function - this returns error, but the err code is not identified - so we cannot say what the problem is.
Maybe I will add some extension to the log statement in order to print the error code.
Regards, Bogdan
John Barry wrote:
Hello,
I am trying to do a performance test of OpenSER (1.3.0) with TLS using SIPP as the UAS/UAC.
The TLS authentication seems to work and the calls are stablished and then terminated (SIPP default scenario). However, I am receiving the following error message from OpenSER:
Feb 19 12:58:40 [12709] ERROR:core:_tls_read: something wrong in SSL: Feb 19 12:58:40 [12709] ERROR:core:tcp_read_req: failed to read
What do these messages mean? Can I ignored them?
The SIP command I am using is:
sipp -s 100 -sn uac 192.168.1.10:5061 -t ln -tls_cert 101-cert.pem -tls_key 101-privkey.pem
The TLS configuration I am using in my openser.cfg file is:
disable_tls = no listen = tls:192.168.1.10:5061 tls_verify_server = 1 tls_verify_client = 1 tls_require_client_certificate = 1 tls_method = SSLv23 tls_certificate = "/openser/etc/openser/tls/proxy/proxy-cert.pem" tls_private_key = "/openser/etc/openser/tls/proxy/proxy-privkey.pem" tls_ca_list = "/openser/etc/openser/tls/proxy/proxy-calist.pem"
I will appreciate any help about this matter.
Thanks, JB
Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ _______________________________________________ Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
Hi John,
I just committed on SVN a small patch to print the error code - this will provide some information about the error. Just in case, I attached the patch.
Regards, Bogdan
JB74 wrote:
Hello Bogdan,
Could you give me any additional advice/suggestion about how to solve this problem? I have been trying with different TLS configurations but I am getting the same error.
Have you seen this problem before?
Thanks for your help, JB
Bogdan-Andrei Iancu wrote:
Hi John,
The error: Feb 19 12:58:40 [12709] ERROR:core:_tls_read: something wrong in SSL:
comes from the SSL_read() function - this returns error, but the err code is not identified - so we cannot say what the problem is.
Maybe I will add some extension to the log statement in order to print the error code.
Regards, Bogdan
John Barry wrote:
Hello,
I am trying to do a performance test of OpenSER (1.3.0) with TLS using SIPP as the UAS/UAC.
The TLS authentication seems to work and the calls are stablished and then terminated (SIPP default scenario). However, I am receiving the following error message from OpenSER:
Feb 19 12:58:40 [12709] ERROR:core:_tls_read: something wrong in SSL: Feb 19 12:58:40 [12709] ERROR:core:tcp_read_req: failed to read
What do these messages mean? Can I ignored them?
The SIP command I am using is:
sipp -s 100 -sn uac 192.168.1.10:5061 -t ln -tls_cert 101-cert.pem -tls_key 101-privkey.pem
The TLS configuration I am using in my openser.cfg file is:
disable_tls = no listen = tls:192.168.1.10:5061 tls_verify_server = 1 tls_verify_client = 1 tls_require_client_certificate = 1 tls_method = SSLv23 tls_certificate = "/openser/etc/openser/tls/proxy/proxy-cert.pem" tls_private_key = "/openser/etc/openser/tls/proxy/proxy-privkey.pem" tls_ca_list = "/openser/etc/openser/tls/proxy/proxy-calist.pem"
I will appreciate any help about this matter.
Thanks, JB
Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ _______________________________________________ Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
Index: tls/tls_server.c =================================================================== --- tls/tls_server.c (revision 3747) +++ tls/tls_server.c (working copy) @@ -505,7 +505,7 @@ return 0; default: - LM_ERR("something wrong in SSL:\n"); + LM_ERR("something wrong in SSL: %d\n",err); c->state = S_CONN_BAD; tls_print_errstack(); return -1;
-
Bogdan-Andrei Iancu -
JB74 -
John Barry