reSIProcate

Mailing Lists

Source Code

Google Search:



< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [reSIProcate] WSS with Repro

Turns out there was a client issue, once I fixed that I was still having problems. I am using a wildecard cert and had to change from using just exarionetworks.com to proxy.exarionetworks.com.


On Wed, Jun 12, 2013 at 11:58 AM, Nathan Stratton <nathan@xxxxxxxxxxxx> wrote:
I am trying to setup WSS with repro, but running into the following error:

 DEBUG | 20130612-165353.313 | repro | RESIP:TRANSPORT | 140133416277760 | TcpBaseTransport.cxx:167 | Received TCP connection from: [ V4 75.148.206.241:41554 WSS target domain=unspecified mFlowKey=0 ] as fd=33
DEBUG | 20130612-165353.313 | repro | RESIP:TRANSPORT | 140133416277760 | ConnectionManager.cxx:88 | Could not find a connection for [ V4 75.148.206.241:41554 WSS target domain=unspecified mFlowKey=0 ]
DEBUG | 20130612-165353.313 | repro | RESIP:TRANSPORT | 140133416277760 | ConnectionBase.cxx:61 | ConnectionBase::ConnectionBase, who: [ V4 75.148.206.241:41554 WSS target domain=unspecified mFlowKey=0 ] 0x7f73480008c0
DEBUG | 20130612-165353.313 | repro | RESIP:TRANSPORT | 140133416277760 | ConnectionBase.cxx:74 | No compression library available: 0x7f73480008c0
INFO | 20130612-165353.313 | repro | RESIP:TRANSPORT | 140133416277760 | Connection.cxx:38 | Connection::Connection: new connection created to who: [ V4 75.148.206.241:41554 WSS target domain=unspecified mFlowKey=33 ]
INFO | 20130612-165353.313 | repro | RESIP:TRANSPORT | 140133416277760 | ssl/TlsConnection.cxx:42 | Creating TLS connection for domain exarionetworks.com [ V4 75.148.206.241:41554 WSS target domain=unspecified mFlowKey=0 ] on 33
DEBUG | 20130612-165353.313 | repro | RESIP:TRANSPORT | 140133416277760 | ssl/TlsConnection.cxx:49 | Trying to form TLS connection - acting as server
DEBUG | 20130612-165353.313 | repro | RESIP:TRANSPORT | 140133416277760 | ssl/TlsConnection.cxx:82 | Not expecting client certificate
DEBUG | 20130612-165353.337 | repro | RESIP:TRANSPORT | 140133416277760 | ConnectionBase.cxx:879 | Creating buffer for CONN_BASE: 0x7f73480008c0 [ V4 75.148.206.241:41554 WSS target domain=unspecified mFlowKey=33 ]
INFO | 20130612-165353.337 | repro | RESIP:TRANSPORT | 140133416277760 | ssl/TlsConnection.cxx:150 | TLS handshake starting (Server mode)
INFO | 20130612-165353.337 | repro | RESIP:TRANSPORT | 140133416277760 | ssl/TlsConnection.cxx:161 | TLS connected
ERR | 20130612-165353.337 | repro | RESIP:TRANSPORT | 140133416277760 | ssl/TlsConnection.cxx:219 | TLS handshake failed 
ERR | 20130612-165353.337 | repro | RESIP:TRANSPORT | 140133416277760 | ssl/TlsConnection.cxx:233 | error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number
ERR | 20130612-165353.337 | repro | RESIP:TRANSPORT | 140133416277760 | ssl/TlsConnection.cxx:235 | Error code = 336130315 file=s3_pkt.c line=348
DEBUG | 20130612-165353.337 | repro | RESIP:TRANSPORT | 140133416277760 | Connection.cxx:393 | Closing connection bytesRead=-1
DEBUG | 20130612-165353.337 | repro | RESIP:TRANSPORT | 140133416277760 | ConnectionBase.cxx:104 | ConnectionBase::~ConnectionBase 0x7f73480008c0
DEBUG | 20130612-165353.337 | repro | RESIP:TRANSPORT | 140133416277760 | TcpBaseTransport.cxx:263 | Processing write for [ V4 75.148.206.241:41554 WSS target domain=unspecified mFlowKey=33 ]
DEBUG | 20130612-165353.337 | repro | RESIP:TRANSPORT | 140133416277760 | ConnectionManager.cxx:71 | fd 33 does not exist.
DEBUG | 20130612-165353.337 | repro | RESIP:TRANSPORT | 140133416277760 | ConnectionManager.cxx:88 | Could not find a connection for [ V4 75.148.206.241:41554 WSS target domain=unspecified mFlowKey=33 ]
DEBUG | 20130612-165353.337 | repro | RESIP:TRANSPORT | 140133416277760 | TcpBaseTransport.cxx:290 | Failed to create/get connection: [ V4 75.148.206.241:41554 WSS target domain=unspecified mFlowKey=33 ]

Should I see the TLS messages or should they be WSS? I have been searching on the "error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number" error and I found someting saying it may be openssl 1.0.1c, but upgrading to 1.0.1e did not fix that issue.

My certs load fine and my config looks like:

Transport1Interface = 204.117.64.103:5060
Transport1Type = UDP
Transport1RecordRouteUri = auto
Transport2Interface = 204.117.64.103:5060
Transport2Type = TCP
Transport2RecordRouteUri = auto
Transport3Interface = 204.117.64.103:8060
Transport3Type = WSS
Transport3RecordRouteUri = auto
Transport3TlsDomain = exarionetworks.com
Transport3TlsClientVerification = None
Transport3RecordRouteUri = sip:exarionetworks.com;transport=WSS
HttpAdminPassword = ********
ForceRecordRouting = true
#EnumSuffixes = e164.arpa, sip5060.net, e164.org
ClientNatDetectionMode = AUTO
DisableAuth = false
LogLevel = DEBUG
EnableIPv6 = false
ConfigPath = /etc/repro/
HttpPort = 80
EnableFlowTokens = true
CertificatePath = /etc/repro/certs



--
><>
Nathan Stratton                                               Founder, CTO Exario Networks, Inc.
nathan at robotics.net                                     nathan at exarionetworks.com
http://www.robotics.net                                   http://www.exarionetworks.com/

Building the WebRTC solutions today that your customers will demand tomorrow.



--
><>
Nathan Stratton                                               Founder, CTO Exario Networks, Inc.
nathan at robotics.net                                     nathan at exarionetworks.com
http://www.robotics.net                                   http://www.exarionetworks.com/

Building the WebRTC solutions today that your customers will demand tomorrow.