[OpenSIPS-Users] opensips vs rtpproxy

nick at uni-petrol.com nick at uni-petrol.com
Thu Apr 28 17:04:40 CEST 2011


Dear Razvan!

My rtpproxy parameters: rtpproxy_offer("cof");
And I not use rtpproxy_answer() function at all.

Also I use unforce_rtp_proxy(); without parameters.

Unfortunately I can't reproduce such error anymore so can't paste such 
output.
If this errors happens again I will send all information again.

Thanks.

On Thu, 28 Apr 2011 15:32:48 +0300, Razvan Crainea wrote:

> Hello Nick,
>
> I think that before receiving the first command (the one starting 
> with
> 7823_9 LR...) you should have received an Update command (something 
> like
>
> 7823_8 UR...). Can you please paste me that output along with
> rtpproxy_offer/answer parameters?
>
> Regards,
> Razvan
>
> On 04/28/2011 02:34 PM, nick at uni-petrol.com [8]wrote:
>
>> Dear Razvan! There is rtpproxy debug output: DBUG:handle_command:
>> received command "7823_9 LR11788 907979336;2 2098324425;2"
>> ERR:handle_command: command syntax error DBUG:doreply: sending reply
>> "7823_9 E4 As u can see there is some garbage in SIP URI:
> "7495xxxxc109
>> 226220584@" There is another rtpproxy output: DBUG:handle_command:
>> received command "7824_13 UR" ERR:handle_command: command syntax 
>> error
>> DBUG:doreply: sending reply "7824_13 E4 It seems like very cut 
>> string
>> in received commands. I run rtpproxy with follow parameters: 
>> rtpproxy
>> -F -l/-s udp::22222 -n tcp::9001 -d DBUG -i -m 10000 -M 20000 -f 
>> Hope
>> this helps. Thanks. On Wed, 27 Apr 2011 14:54:07 +0300, Razvan 
>> Crainea
>> wrote:
>>
>>> Hello Nick, I will need some debugging information such as the
>>> received commands. Can you please start RTPProxy with debug logging
>>> level (parameter "-d DBUG") and paste me the line starting with
>>> "DBUG:handle_command: received command ... ". Regards, Razvan On
>>> 04/25/2011 10:42 AM, nick at uni-petrol.com [3][3]wrote:
>>>
>>>> Dear All! OS: CentOS 5.6 x86_64 OpenSIPS: trunk 7904 revision RTP
>>>> Rroxy: latest from git I have strange errors and garbage in RTP
>>>> Proxy when parsing information coming from OpenSIPS and calling
>>>> from 2000 at y.y.y.y to 1000 at y.y.y.y through OpenSIPS+RTP Rroxy. RTP
>>>> Rroxy are on different server then OpenSIPS and they connect each
>>>> other through LAN and WAN. On LAN they exchange technical
>>>> information (RTP sock, RTP timeout notify socket) and through WAN
>>>> they exchange information (SIP
>>> &
>>>
>>>> RTP) with SIP clients (UAC & UAS). Both phones (1000 &am> on the
>>> same LAN and go through same NAT router w
>>> x to OpenSIPS WAN IP. Simple schema is: 2000 --> NAT Router -->
>>> OpenSIPS --> NAT
>>>> Router --> 1000 I have following errors in RTP Rroxy : Apr 25
>>>> 11:00:11 rtpproxy[5181]: ERR:handle_command: command syntax error
>>>> Apr 25 11:00:34 rtpproxy[5181]: ERR:handle_command: invalid remote
>>>> address: x.x.x.x70045415: No address associated with hostname
>>> Where
>>>> x.x.x.x is IP of NAT router, and 70045415 some garbage or ports?
>>> In
>>>> OpenSIPS I have error: Apr 25 11:00:34 /usr/sbin/opensips[5634]:
>>>> [REPR02] -----> Reply route 'base-nat-reply' - M=INVITE
>>>> RURI=F=sip:2000 at y.y.y.y T=sip:1000 at 8y.y.y.y IP= ID=345194
>>> r 25 11:00:34 pensips[5634]: [REPR02] NAT-Reply - S=200 D=OK
>>> F=sip:2000 at y.y.y.y
>>>> T=sip:1000 at y.y.y.y IP=x.x.x.x ID=34519459 at z.z.z.z Apr 25 11:00:34
>>>> /usr/sbin/opensips[5634]: [REPR02] rtpproxy_answer() - M=INVITE
>>>> RURI=F=sip:2000 at y.y.y.y T=sip:1000 at 8y.y.y.y IP=x.x.x.x
>>>> ID=34519459 at z.z.z.z Apr 25 11:00:34 /usr/sbin/opensips[5634]:
>>>> ERROR:rtpproxy:force_rtp_proxy_body: incorrect port 0 in rep>>
>>> quote>proxy RTP Proxy running with the following parameters:
>>>> rtpproxy -F -l -s udp::22222 -n tcp::9001 -d DBUG OpenSIPS configu
>>> kquote>
>>> #############################################################
>>>
>>>> loadmodule "
>>> /blockquote>
>>> ###########################################################
>>>
>>>> # modparam("rtpproxy", "rtpproxy_sock", "udp::22222")
>>>> modparam("rtpproxy", "rtpproxy_disable_tout", 1)
>>>> modparam("rtpproxy", "rtpproxy_timeout", "1") modparam("rtpproxy",
>>>> "rtpprox
>>> , 1) dparam("rtpproxy", "rtpproxy_retr", 10) modparam("rtpproxy",
>>>> "rtpp_notify_socket", "tcp::9001") Thanks in advance!
>>>> _______________________________________________ Users mailing list
>>>> Users at lists.opensips.org [1] [1]
>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users [2] [2]
>>> ______________________________________________ Users mailing list
>>> Users at lists.opensips.org [4] [4]
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users [5] [5]
>> _______________________________________________ Users mailing list
>> Users at lists.opensips.org [6]
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users [7]
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org [9]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users [10]




More information about the Users mailing list