Amos Shahar - 2012-06-07

hi,
I'm using rtpproxy 1.2.1 and opensips 1.7.1. I would like to use the rtp timout (-n) function.. other stuff is working good.
the OpenSips Ip is 10.0.10.210
the RTPPROXY IP IS: 10.0.10.220

since the rtpproxy is in cloud (private IP) it was patched with the the rtpproxy patch from
http://opensips-open-sip-server.1449251.n2.nabble.com/attachment/5008062/0/rtpproxy_nat_address_fix.txt

so I'm running the RTPPROXY with the following command:
/usr/local/src/rtpproxy-1.2.1/rtpproxy -n tcp:10.0.10.210:7777 -T 10 -A 107.2.4.26 -F -l 10.0.10.220 -s udp:*:7722 -m 16000 -M 26000 -d DBUG -f -i

the opensips conf is with:
modparam("rtpproxy","rtpproxy_sock","udp:10.0.10.220:7722")
modparam("rtpproxy","rtpp_notify_socket","tcp:10.0.10.210:7777")
…
if (!rtpproxy_answer("n"))
…
if (!rtpproxy_offer("n"))
…

I can see that the RTPProxy identify when there is no RTP but I have a problem with the socket: this log is created when a call comes in:

/usr/local/src/rtpproxy-1.2.1/rtpproxy -n tcp:10.0.10.210:7777 -T 10 -A 107.2.4.26 -F -l 10.0.10.220 -s udp:*:7722 -m 16000 -M 26000 -d DBUG -f -i
INFO:main: rtpproxy started, pid 5820
DBUG:handle_command: received command "20275_9 Uc0,8,101 20510279-3548041261-108065@NY-MSW.mydomain.com 210.137.89.91 59380 NzQ5MDFmNjBjN2VhYjNlM2YyNmQwMGI2ODQwNmViMzA.;1 ;1 10.0.10.210:7777 702.1825308238"
INFO:handle_command: new session 20510279-3548041261-108065@NY-MSW-2.deltathree.com, tag NzQ5MDFmNjBjN2VhYjNlM2YyNmQwMGI2ODQwNmViMzA.;1 requested, type strong
INFO:handle_command: new session on a port 17316 created, tag NzQ5MDFmNjBjN2VhYjNlM2YyNmQwMGI2ODQwNmViMzA.;1
ERR:handle_command: invalid socket name 10.0.10.210:7777

the problem is with the "invalid socket name 10.0.10.210:7777".

any idea what is causing problem?
Thanks
Amos