[Fwd: RTPproxy 1.1 has been released]

[Maxim Sobolev]

Marcus Better wrote:
> Maxim Sobolev wrote:
>> I have made the changes in the trunk version, you can find the patch for
>> 1.1 here:
> 
> Thanks, I applied it to the Debian package in svn, but the setuid thing still 
> doesn't work with SER as I intended, although it seems not to be rtpproxy's 
> fault.
> 
> My ser 2.0 snapshot runs as user ser, group ser, and I've added ser to the 
> rtpproxy group, and made the control socket group-writable, but it still 
> doesn't connect. However if I change the control socket group to "ser", it 
> works. This is not very elegant. Shouldn't the above work?
> 
> Regarding the group-write permissions on the control socket: For this type of 
> scenario the socket should probably be group-writable. Can this be made the 
> default?

Marcus,

You should use umask(1) command to make socket group-writeable. There is 
no need to change rtpproxy itself.

Regards,
-- 
Maksym Sobolyev
Sippy Software, Inc.
Internet Telephony (VoIP) Experts
T/F: +1-646-651-1110
Web: http://www.sippysoft.com