I haven't resolved this problem. Further exploration revealed that both relay and dispatcher are working. The only problem is during the handshake between dispatcher and relay. The dispatcher is refusing the relay connection. I have downloaded the sample tls certificates from the svn repository because I believe this might resolve the problem still the problem persists. I am correct to say that I am using the correct certificates if my CDRTool on Network and Session section is able to connect to the mediaproxy-dispatcher. I have observed it previously that if I dont have the proper mediaproxy.hostname.com.pem file I encounter this error == Error connecting to tls://hostname.com:25061: (111). With my current CDRTool configuration I am able to connect to media dispatcher properly. I am wondering why I am receiving Error: A TLS packet with unexpected length was received.
bay2x1 wrote: > > I am encountering this error with mediaproxy. Mediaproxy-relay and > Mediaproxy-dispatcher is not on the same machine. > Every time I restart mediaproxy-relay on the other computer I got this log > error on the machine where mediaproxy-dispatcher is running. I have check > both relay and dispatcher have the same version 2.3.4. > > error: Connection with relay at 176.16.100.150 was lost: A TLS packet with > unexpected length was received. > > Everytime I restart dispatcher I get this log warning > > Aug 9 20:42:04 phoenix303 media-dispatcher[10797]: Received SIGTERM, > shutting down. > Aug 9 20:42:04 phoenix303 media-dispatcher[10797]: (Port None Closed) > Aug 9 20:42:04 phoenix303 media-dispatcher[10797]: (Port 25061 Closed) > Aug 9 20:42:04 phoenix303 media-dispatcher[10797]: (Port 25060 Closed) > Aug 9 20:42:04 phoenix303 media-dispatcher[10797]: Connection with relay > at 176.16.100.150 was closed > Aug 9 20:42:04 phoenix303 media-dispatcher[10797]: Main loop terminated. > Aug 9 20:42:05 phoenix303 media-dispatcher[10816]: Log opened. > Aug 9 20:42:05 phoenix303 media-dispatcher[10816]: warning: startSyslog > is being deprecated and will be removed in 1.2.0. Use the start_syslog > function instead. > Aug 9 20:42:05 phoenix303 media-dispatcher[10816]: Starting MediaProxy > Dispatcher 2.3.4 > Aug 9 20:42:05 phoenix303 media-dispatcher[10816]: Twisted is using > epollreactor > Aug 9 20:42:06 phoenix303 media-dispatcher[10816]: > mediaproxy.dispatcher.RelayFactory starting on 25060 > Aug 9 20:42:06 phoenix303 media-dispatcher[10816]: > mediaproxy.dispatcher.OpenSIPSControlFactory starting on > "'/var/run/mediaproxy/dispatcher.sock'" > Aug 9 20:42:06 phoenix303 media-dispatcher[10816]: > mediaproxy.dispatcher.ManagementControlFactory starting on 25 > > > ----- http://opensips.blogspot.com http://opensips.blogspot.com -- View this message in context: http://n2.nabble.com/Error%3A-A-TLS-packet-with-unexpected-length-was-received.-tp3415244p3434560.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
