[Devel] Re: [Serusers] SSL: connect failed ..Please help

[Klaus Darilion]

looks like minisip uses SSLv3 instead of TLSv1

either change the version in minisip or (open)ser

http://www.voneurope.com/speakers.html

regards
klaus

Ferianto siregar wrote:
> Dear all,
>  
> Thank you very much for you time .
> All, I am sorry. May I ask you again, please..?
>  
> I got error message in minisip command prompt when I tried using TLS 
> (Transport Method = TLS and Ntwork Port = 5061).But, without TLS , I can 
> make a call with minisip. (User`s registration success)
>  
> The error message says :
>  
> A. in client command prompt
>  
> init 6/9: Creating MSip SIP stack
> init 7/9: Connecting GUI to SIP logic
> init 8.2/9: Starting TCP transport worker thread
> init 8.3/9: Starting TLS transport worker thread
> init 9/9: Registering Identities to registrar server
> Registering user didit at 202.95.149.251 <mailto:didit at 202.95.149.251> to 
> proxy 202.95.149.251, requesting domain
>  202.95.149.251
> SipMessageTransport: sendMessage: creating new socket
> *Creating new SSL_CTX
> SSL: connect failed*
> SipMessageTransport: sendMessage: exception thrown!
> SipMessageTransport: sendMessage: creating new socket
> *SSL: connect failed
> *SipMessageTransport: sendMessage: exception thrown!
> SipMessageTransport: sendMessage: creating new socket
> SSL: connect failed
> SipMessageTransport: sendMessage: exception thrown!
> SipMessageTransport: sendMessage: creating new socket
> SSL: connect failed
> SipMessageTransport: sendMessage: exception thrown!
>  
> B. in server terminal
>  
> tls_tcpconn_init: Setting in ACCEPT mode (server)
> 11(5927) tcpconn_add: hashes: 835, 11
> 11(5927) handle_new_connect: new connection: 0x422d88f0 24 flags: 0002
> 11(5927) send2child: to tcp child 0 7(5919), 0x422d88f0
>  7(5919) received n=4 con=0x422d88f0, fd=20
>  7(5919) DBG: io_watch_add(0x80ed320, 20, 2, 0x422d88f0), fd_no=1
>  7(5919) tls_update_fd: New fd is 20
>  7(5919) tls_accept: Error in SSL:
> * 7(5919) tls_error: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong 
> version number*
>  7(5919) DBG: io_watch_del (0x80ed320, 20, 1, 0x10) fd_no=2 called
>  7(5919) releasing con 0x422d88f0, state -2, fd=20, id=11
>  7(5919)  extra_data 0x422e8a08
> 11(5927) handle_tcp_child: reader response= 422d88f0, -2 from 0
> 11(5927) tcpconn_destroy: destroying connection 0x422d88f0, flags 0002
> 11(5927) tls_close: Closing SSL connection
> 11(5927) tls_update_fd: New fd is 24
> 11(5927) tls_shutdown: Shutdown successful
> 11(5927) tls_tcpconn_clean: Entered
> 
> What`s wrong? How to solve the error "SSL3_GET_RECORD:wrong version 
> number" and "SSL: connect failed"?
> Please forgive me for my lack of skill and many questions
> 
> Please tell me if I have shown my openser.cfg file. Thanks
> Thank you for your attention and Have a nice day :)
> Regards,
> 
> Ferianto
> Note:
> 1. I use Redhat 9
> [root at localhost root]# rpm -qa|grep -i ssl
> perl-Crypt-SSLeay-0.45-7
> openssl-devel-0.9.7a-2
> openssl-perl-0.9.7a-2
> openssl-0.9.7a-2
> pyOpenSSL-0.5.1-8
> mod_ssl-2.0.40-21
> openssl096b-0.9.6b-3
> docbook-style-dsssl-1.76-8
> openssl096-0.9.6-15
> [root at localhost root]#
> 
>  
> 
> ------------------------------------------------------------------------
> How low will we go? Check out Yahoo! Messenger’s low PC-to-Phone call 
> rates. 
> <http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com>
> 
> <http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com>
> 
> ------------------------------------------------------------------------
> Do you Yahoo!?
> Get on board. 
> <http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com>You're 
> invited 
> <http://us.rd.yahoo.com/evt=40791/*http://advision.webevents.yahoo.com/mailbeta> 
> to try the new Yahoo! Mail.
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Serusers mailing list
> Serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers