[OpenSIPS-Users] timeout waiting reply from a RTP proxy / adding strong flag to existing session, new=1/0/0

[nick at uni-petrol.com]

Dear Razvna!

rtpproxy doesn't reply back but still continue working.

After I restart rtpproxy OpenSIPS found rtpproxy:
Apr 28 18:07:25 /usr/sbin/opensips[7765]: INFO:rtpproxy:rtpp_test: rtp 
proxy <udp:<rtpproxy LAN IP>:22222> found, support for it enabled

I will monitor this issues a few days to understand is it one time bug 
or repeating.

Thanks.

On Thu, 28 Apr 2011 17:14:43 +0300, Razvan Crainea wrote:

> Hello Nick,
>
> Take care that RTPProxy -n parameter should be the one configured in
> OpenSIPS. Perhaps you will have to change your OpenSIPS parameter to:
> modparam("rtpproxy", "rtpp_notify_socket", "tcp::9001")
>
> Does RTPProxy die after these errors, or simply doesn't reply back to
> OpenSIPS?
>
> Regards,
> Razvan
>
> On 04/28/2011 04:30 PM, nick at uni-petrol.com [3]wrote:
>
>> Dear All! I have strange problem when using opensips with rtpproxy.
>> After failing call rtpproxy become unavailable while restart it. On
>> OpenSIPS side I have errors: Apr 28 17:20:19 
>> /usr/sbin/opensips[7673]:
>> ERROR:rtpproxy:send_rtpp_command: timeout waiting reply from a RTP
>> proxy Apr 28 17:20:19 /usr/sbin/opensips[7673]:
>> ERROR:rtpproxy:send_rtpp_command: proxy :22222> does not respond,
>> disable it Apr 28 17:20:24 /usr/sbin/opensips[7673]:
>> ERROR:rtpproxy:send_rtpp_command: timeout waiting reply from a RTP
>> proxy Apr 28 17:20:24 /usr/sbin/opensips[7673]:
>> ERROR:rtpproxy:send_rtpp_command: proxy :22222> does not respond,
>> disable it Apr 28 17:20:30 /usr/sbin/opensips[7673]:
>> ERROR:rtpproxy:send_rtpp_command: timeout waiting reply from a RTP
>> proxy Apr 28 17:20:30 /usr/sbin/opensips[7673]:
>> ERROR:rtpproxy:send_rtpp_command: proxy :22222> does not respond,
>> disable it On RTPPROXY side I have errors: Apr 28 17:20:00
>> rtpproxy[1775]: INFO:handle_command: adding strong flag to existing
>> session, new=1/0/0 Apr 28 17:20:00 rtpproxy[1775]:
> INFO:handle_command:
>> lookup on ports 17046/0, session timer restarted Apr 28 17:20:05
>> rtpproxy[1775]: INFO:handle_command: adding strong flag to existing
>> session, new=1/0/0 Apr 28 17:20:05 rtpproxy[1775]:
> INFO:handle_command:
>> lookup on ports 17046/0, session timer restarted Apr 28 17:20:39
>> rtpproxy[1775]: INFO:handle_command: adding strong flag to existing
>> session, new=1/0/0 Apr 28 17:20:39 rtpproxy[1775]:
> INFO:handle_command:
>> lookup on ports 17046/0, session timer restarted rtpproxy run with
>> parameters: /usr/bin/rtpproxy -p /var/run/rtpproxy.pid -u rtpproxy 
>> -l
>> -s udp::22222 -n tcp::9001 -i -t 0xB8 -r /var/spool/rtpproxy -r
>> /var/spool/rtpproxy/recorded -u rtpproxy rtpproxy -m 10000 -M 20000 
>> -d
>> DBUG OpenSIPS configurations:
>>
> 
> ########################################################################
>> loadmodule "rtpproxy.so"
>>
> 
> ########################################################################
>> modparam("rtpproxy", "rtpproxy_sock", "udp::22222")
>> modparam("rtpproxy", "rtpproxy_disable_tout", 10) 
>> modparam("rtpproxy",
>> "rtpproxy_timeout", "1") modparam("rtpproxy", "rtpproxy_autobridge",
> 0)
>> modparam("rtpproxy", "rtpproxy_retr", 5) modparam("rtpproxy",
>> "nortpproxy_str", "a=sdpmangled:yesrn") modparam("rtpproxy",
>> "rtpp_notify_socket", "tcp::22222")
>> _______________________________________________ Users mailing list
>> Users at lists.opensips.org [1]
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users [2]
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org [4]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users [5]