Hi Marian,
Christian de Balorre wrote: Hello, I am struggling with rtpproxy and I would like some help, because the documentation is rather scarce to be honest. I am running ser on an OpenBSD 3.3 box, with one internal interface (192.168.x.x) and a public interface (62.x.x.x). I am not sure wether I have to force rtpproxy to listen to a specific interface or not.
I launch rtpproxy rather basically with ./rtpproxy -s /var/run/rtpproxy.sock Then I launch ser, it spawns some process and then run into race condition (see ps -aux below) Here is log file :
Feb 2 15:34:28 cdg8-ser1 ser: WARNING: could not read from /dev/random (5) Feb 2 15:34:28 cdg8-ser1 ./ser[20970]: ERROR: send_rtpp_command: can't connect to RTP proxy Feb 2 15:34:28 cdg8-ser1 ./ser[32404]: ERROR: send_rtpp_command: can't connect to RTP proxy Feb 2 15:34:28 cdg8-ser1 ./ser[32404]: WARNING: rtpp_test: can't get version of the RTP proxy Feb 2 15:34:28 cdg8-ser1 ./ser[32404]: WARNING: rtpp_test: support for RTP proxyhas been disabled temporarily Feb 2 15:34:28 cdg8-ser1 ./ser[20970]: WARNING: rtpp_test: can't get version of the RTP proxy Feb 2 15:34:28 cdg8-ser1 ./ser[20970]: WARNING: rtpp_test: support for RTP proxyhas been disabled temporarily Feb 2 15:34:28 cdg8-ser1 ./ser[147]: ERROR: send_rtpp_command: can't connect to RTP proxy ...
Since you are using as communication between SER and RTPPROXY UNIX sockets, your error has nothing to do with the used interfaces. Most probably it's a problem of permissions on the UNIX socket file - like SER has no permission to write on the file.
Best regards, Marian
You know that I'm running both SER and rtpproxy as user root, but still get the same error. What could it be ? And also look at the socket permisions ...
srwxr-xr-x 1 root root 0 Feb 4 17:42 /var/run/rtpproxy.sock
Regards,
Lucas