Thank you for your time, patience and effort... I really appreciate it... Correct me if I am wrong mediaproxy.dispatcher.RelayFactory starting on 25060 --- this the port where mediaproxy-relay will connect and it uses TLS
mediaproxy.dispatcher.ManagementControlFactory starting on 25061 --- this the management port and it uses TCP I have set the value in my config.ini for mediaproxy Dispatcher = 172.16.100.20:25060 Can you please enlighten me more on how to do a network capture what tools/utilities/commands do I need to use and what to look for. Can wireshark do this? I am still exploring the Linux OS by the way I am using Fedora Core 10. Dan Pascu wrote: > > > On 29 Sep 2009, at 03:47, bay2x1 wrote: > >> >> I have corrected the wrong port assigned in (25061) in the relay >> section on >> my configuration. I have set the value for dispatcher = >> 172.16.100.20 (ip >> of my dispatcher) -- leaving the port blank. I have already check the >> version both are version 2.3.4. I am still stuck in the same >> error: A TLS >> packet with unexpected length was received. > > This error is usually seen when one side speaks only TCP while the > other speaks TLS. However since the relay and dispatcher only have > code to speak TLS between them there must be something else you do > wrong. A network capture may help you shed some light on what is going > wrong. Are you sure it doesn't still try to connect to the dispatcher > management port that is configured to use TCP? > >> >> >> The only problem I see is that I cant establish the TCP part for the >> TLS >> connection. Again I have checked the versions of both mediaproxy >> relay and >> dispatcher to be the same 2.3.4 version. >> >> Sep 29 08:44:15 ws20 media-dispatcher[14419]: Main loop terminated. >> Sep 29 08:44:15 ws20 media-dispatcher[14481]: Log opened. >> Sep 29 08:44:15 ws20 media-dispatcher[14481]: warning: startSyslog >> is being >> deprecated and will be removed in 1.2.0. Use the start_syslog function >> instead. >> Sep 29 08:44:15 ws20 media-dispatcher[14481]: Starting MediaProxy >> Dispatcher >> 2.3.4 >> >> Sep 29 08:44:32 ws17 media-relay[4007]: Main loop terminated. >> Sep 29 08:44:36 ws17 media-relay[4261]: Log opened. >> Sep 29 08:44:36 ws17 media-relay[4261]: warning: startSyslog is being >> deprecated and will be removed in 1.2.0. Use the start_syslog function >> instead. >> Sep 29 08:44:36 ws17 media-relay[4261]: Starting MediaProxy Relay >> 2.3.4 >> Sep 29 08:44:37 ws17 media-relay[4261]: Set resource limit for >> maximum open >> file descriptors to 11000 >> >> Is there a command to check what version of mediaproxy i am using? > > You can check in syslog. As seen above both print their version on > startup. Otherwise both can be run with --version to print their > version. > > -- > Dan > > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > ----- http://opensips.blogspot.com http://opensips.blogspot.com -- View this message in context: http://n2.nabble.com/Error-A-TLS-packet-with-unexpected-length-was-received-tp3415244p3752801.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
