[OpenSER-Devel] Can't connect with RtpProxy since 1.3.X

Wed Oct 31 08:49:21 UTC 2007

Hi Iñaki,

i was able to reproduce this...strange, but I did, so you are not the 
only one :D....

I increased the number of openser processes to 10 and indeed, some of 
them reported not to be able to receive reply from the rtpproxy....

I will work on this to see where the problem is....

Regards,
Bogdan

Iñaki Baz Castillo wrote:
> El Tuesday 30 October 2007 17:32:51 Iñaki Baz Castillo escribió:
>   
>> I've tryed the 4 versions in
>>   http://ftp.iptel.org/pub/rtpproxy/daily-snapshots/
>> All of them contain the Extension 20060704.
>>
>> In all of them:
>>   ./configure && make && make install
>>
>> I use Debian Sid with gcc-4.2.
>>
>>
>> *** rtpproxy-0.2_2006-12-11   and   rtpproxy-0.2_2007-02-23
>>
>> I run them in foreground but get no info when starting OpenSer. Fails.
>>
>>
>> ***  rtpproxy-0.2_2007-07-27   and    rtpproxy-0.2_2007-07-28
>>
>> I run them in foreground and when I  start OpenSer, RtpProxy crashes
>> with "segment violation".
>>     
>
>
> I can't understand, now I use now the last CVS version from here:
>   http://www.openser.org/downloads/snapshots/rtpproxy/
>
> I run OpenSer with 
>   children=2
>
> so 7 processes exist:
>
>   ~$ pidof openser
>   6694 6691 6688 6685 6682 6679 6678 6677 6676 6675 6674
>
>
> I do a ngrep of 22222 (the port where RtpProxy listens) and get this:
>
>
> #
> U 2007/10/30 18:03:40.028032 127.0.0.1:56123 -> 127.0.0.1:22222
> 6675_0 V
> #
> U 2007/10/30 18:03:40.028195 127.0.0.1:22222 -> 127.0.0.1:56123
> 6675_0 20040107
>
> #
> U 2007/10/30 18:03:40.028374 127.0.0.1:56123 -> 127.0.0.1:22222
> 6675_1 VF 20050322
> #
> U 2007/10/30 18:03:40.028424 127.0.0.1:22222 -> 127.0.0.1:56123
> 6675_1 1
>
> #
> U 2007/10/30 18:03:40.030609 127.0.0.1:56124 -> 127.0.0.1:22222
> 6676_0 V
> #
> U 2007/10/30 18:03:40.035909 127.0.0.1:56125 -> 127.0.0.1:22222
> 6677_0 V
> #
> U 2007/10/30 18:03:40.037366 127.0.0.1:56126 -> 127.0.0.1:22222
> 6678_0 V
> #
> U 2007/10/30 18:03:40.042299 127.0.0.1:56127 -> 127.0.0.1:22222
> 6685_0 V
> #
> U 2007/10/30 18:03:40.043785 127.0.0.1:56128 -> 127.0.0.1:22222
> 6688_0 V
> #
> U 2007/10/30 18:03:40.044231 127.0.0.1:22222 -> 127.0.0.1:56124
> 6676_0 20040107
>
> #
> U 2007/10/30 18:03:40.044246 127.0.0.1:22222 -> 127.0.0.1:56125
> 6677_0 20040107
>
> #
> U 2007/10/30 18:03:40.044258 127.0.0.1:22222 -> 127.0.0.1:56126
> 6678_0 20040107
>
> #
> U 2007/10/30 18:03:40.044268 127.0.0.1:22222 -> 127.0.0.1:56127
> 6685_0 20040107
>
> #
> U 2007/10/30 18:03:40.044278 127.0.0.1:22222 -> 127.0.0.1:56128
> 6688_0 20040107
>
> #
> U 2007/10/30 18:03:40.051380 127.0.0.1:56128 -> 127.0.0.1:22222
> 6688_1 VF 20050322
> #
> U 2007/10/30 18:03:40.054894 127.0.0.1:22222 -> 127.0.0.1:56128
> 6688_1 1
>
>
>
>
> As you can see there are less replies from RtpProxy than requests from 
> OpenSer.
> In fact:
>
>
> ---------------------------------
> Oct 30 18:03:40 [6676] ERROR:nathelper:send_rtpp_command: can't read reply 
> from a RTP proxy
> Oct 30 18:03:40 [6676] ERROR:nathelper:send_rtpp_command: proxy 
> <udp:127.0.0.1:22222> does not respond, disable it
> Oct 30 18:03:40 [6676] WARNING:nathelper:rtpp_test: can't get version of the 
> RTP proxy
> Oct 30 18:03:40 [6676] WARNING:nathelper:rtpp_test: support for RTP proxy 
> <udp:127.0.0.1:22222> has been disabled temporarily
> Oct 30 18:03:40 [6676] NOTICE:presence:child_init: init_child [2]  pid [6676]
> Oct 30 18:03:40 [6677] ERROR:nathelper:send_rtpp_command: can't read reply 
> from a RTP proxy
> Oct 30 18:03:40 [6677] ERROR:nathelper:send_rtpp_command: proxy 
> <udp:127.0.0.1:22222> does not respond, disable it
> Oct 30 18:03:40 [6677] WARNING:nathelper:rtpp_test: can't get version of the 
> RTP proxy
> Oct 30 18:03:40 [6677] WARNING:nathelper:rtpp_test: support for RTP proxy 
> <udp:127.0.0.1:22222> has been disabled temporarily
> Oct 30 18:03:40 [6677] NOTICE:presence:child_init: init_child [3]  pid [6677]
> Oct 30 18:03:40 [6678] ERROR:nathelper:send_rtpp_command: can't read reply 
> from a RTP proxy
> Oct 30 18:03:40 [6678] ERROR:nathelper:send_rtpp_command: proxy 
> <udp:127.0.0.1:22222> does not respond, disable it
> Oct 30 18:03:40 [6678] WARNING:nathelper:rtpp_test: can't get version of the 
> RTP proxy
> Oct 30 18:03:40 [6678] WARNING:nathelper:rtpp_test: support for RTP proxy 
> <udp:127.0.0.1:22222> has been disabled temporarily
> Oct 30 18:03:40 [6678] NOTICE:presence:child_init: init_child [4]  pid [6678]
> Oct 30 18:03:40 [6685] ERROR:nathelper:send_rtpp_command: can't read reply 
> from a RTP proxy
> Oct 30 18:03:40 [6685] ERROR:nathelper:send_rtpp_command: proxy 
> <udp:127.0.0.1:22222> does not respond, disable it
> Oct 30 18:03:40 [6685] WARNING:nathelper:rtpp_test: can't get version of the 
> RTP proxy
> Oct 30 18:03:40 [6685] WARNING:nathelper:rtpp_test: support for RTP proxy 
> <udp:127.0.0.1:22222> has been disabled temporarily
> Oct 30 18:03:40 [6685] NOTICE:presence:child_init: init_child [5]  pid [6685]
> Oct 30 18:03:40 [6688] INFO:nathelper:rtpp_test: rtp proxy 
> <udp:127.0.0.1:22222> found, support for it enabled
> Oct 30 18:03:40 [6688] NOTICE:presence:child_init: init_child [6]  pid [6688]
> ---------------------------------
>
>
> Note that just the last process (child [6]  pid [6688]) has "rtp proxy found, 
> support for it enabled".
>
>
>
>
> What can I do for this? I've already tryed:
>   modparam("nathelper", "rtpproxy_tout", 4)
> and the same occurs (OpenSer and RtpProxy are in same machine !!).
>
>
> Any help please?
> Maybe a compilation bug?
>
> Thanks.
>
>
>
>   