[Serusers] rtpproxy mess

[Marian Dumitru]

Hi Christian,

Please see my inline comments.

Best regards,
Marian

Christian de Balorre wrote:
> Thanks for your answer Marian.
> You are right indeed : if I run ser as root I don't get the errors.  Any
> solution to run rtpproxy as user other than root ?

There is no parameter that will force rtpproxy to do chown by itself; 
So, the only way is to launch rtpproxy as a different user than root.

> 
> Last question about rtpproxy :
> It is running on a xhomed box (2 interfaces) : shall we tell rtproxy
> explicitly what is inbound / outbound interface - if yes how - or can it
> handle the situation automatically ?

Do you want to run rtpproxy in bridging mode (private<->public) ?

> 
> ----- Original Message -----
> From: "Marian Dumitru" <marian.dumitru at voice-sistem.ro>
> To: "Christian de Balorre" <cdebalorre at neotelecoms.com>
> Cc: <serusers at lists.iptel.org>
> Sent: Thursday, February 03, 2005 2:16 PM
> Subject: Re: [Serusers] rtpproxy mess
> 
> 
> 
>>Hi Christian,
>>
>>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
>>
>>
>>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
>>>...
>>>
>>>
>>>And the ps
>>>
>>>USER       PID %CPU %MEM   VSZ   RSS TT   STAT STARTED       TIME
> 
> COMMAND
> 
>>>ser      16586 99.0  0.5  1744  2672 ??  R      3:34PM    6:15.11 ./ser
>>>-P /var/run/ser.pid
>>>root     16613  0.0  0.1   752   272 ??  Ss     3:33PM    0:00.01
>>>./rtpproxy -s /var/run/rtpproxy.sock
>>>
>>>
>>>#./rtpproxy -v
>>>20040107
>>># ./ser -V
>>>version:  0.8.14 (i386/openbsd)
>>>
>>>Nathelper config :
>>>
>>>#-------------- nathelper parameters
>>>modparam("nathelper", "natping_interval", 30)
>>>modparam("nathelper", "ping_nated_only", 1)
>>>modparam("nathelper", "rtpproxy_sock", "/var/run/rtpproxy.sock")
>>>
>>>Could it be that ser running as ser user cannot read the rtpproxy socket
>>>(running as root) ?
>>>
>>>Thanks
>>>
>>>Christian
>>>
>>>
>>>------------------------------------------------------------------------
>>>
>>>_______________________________________________
>>>Serusers mailing list
>>>serusers at lists.iptel.org
>>>http://lists.iptel.org/mailman/listinfo/serusers
>>
>>--
>>Voice System
>>http://www.voice-system.ro
>>
> 
> 
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
> 

-- 
Voice System
http://www.voice-system.ro