<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
This is what I get in /var/log/syslog at RTPPROXY's host,<br>
when I get "ERROR:nathelper:force_rtp_proxy_body: incorrect port 0 in
reply from rtp proxy" at opensips' host :<br>
<br>
<small>Apr 20 14:34:45 ate rtpproxy[32664]: DBUG:handle_command:
received command "1338_6 V"<br>
Apr 20 14:34:45 ate rtpproxy[32664]: DBUG:doreply: sending reply
"1338_6 20040107 "<br>
Apr 20 14:34:45 ate rtpproxy[32664]: DBUG:handle_command: received
command "1338_7 VF 20050322"<br>
Apr 20 14:34:45 ate rtpproxy[32664]: DBUG:doreply: sending reply
"1338_7 1 "<br>
Apr 20 14:34:45 ate rtpproxy[32664]: DBUG:handle_command: received
command "1338_8 VF 20071116"<br>
Apr 20 14:34:45 ate rtpproxy[32664]: DBUG:doreply: sending reply
"1338_8 1 "<br>
Apr 20 14:34:45 ate rtpproxy[32664]: DBUG:handle_command: received
command "1338_9 VF 20081102"<br>
Apr 20 14:34:45 ate rtpproxy[32664]: DBUG:doreply: sending reply
"1338_9 1 "<br>
Apr 20 14:34:45 ate rtpproxy[32664]: DBUG:handle_command: received
command "1338_10 Uc3,8,0,101
<a class="moz-txt-link-abbreviated" href="mailto:9313C89A-1DD2-11B2-899C-81EF5B6DD5A7@192.168.1.22">9313C89A-1DD2-11B2-899C-81EF5B6DD5A7@192.168.1.22</a> 151.68.60.80 49164
4563395591901985372;1"<br>
Apr 20 14:34:45 ate rtpproxy[32664]: INFO:handle_command: new session
<a class="moz-txt-link-abbreviated" href="mailto:9313C89A-1DD2-11B2-899C-81EF5B6DD5A7@192.168.1.22">9313C89A-1DD2-11B2-899C-81EF5B6DD5A7@192.168.1.22</a>, tag
4563395591901985372;1 requested, type strong<br>
Apr 20 14:34:47 ate rtpproxy[32664]: ERR:handle_command: can't create
listener<br>
Apr 20 14:34:47 ate rtpproxy[32664]: DBUG:doreply: sending reply
"1338_10 E10 "<br>
Apr 20 14:34:47 ate rtpproxy[32664]: DBUG:handle_command: received
command "1338_10 Uc3,8,0,101
<a class="moz-txt-link-abbreviated" href="mailto:9313C89A-1DD2-11B2-899C-81EF5B6DD5A7@192.168.1.22">9313C89A-1DD2-11B2-899C-81EF5B6DD5A7@192.168.1.22</a> 151.68.60.80 49164
4563395591901985372;1"<br>
Apr 20 14:34:47 ate rtpproxy[32664]: INFO:handle_command: new session
<a class="moz-txt-link-abbreviated" href="mailto:9313C89A-1DD2-11B2-899C-81EF5B6DD5A7@192.168.1.22">9313C89A-1DD2-11B2-899C-81EF5B6DD5A7@192.168.1.22</a>, tag
4563395591901985372;1 requested, type strong<br>
Apr 20 14:34:48 ate rtpproxy[32664]: ERR:handle_command: can't create
listener<br>
Apr 20 14:34:48 ate rtpproxy[32664]: DBUG:doreply: sending reply
"1338_10 E10 "<br>
Apr 20 14:34:48 ate rtpproxy[32664]: DBUG:handle_command: received
command "1339_8 D <a class="moz-txt-link-abbreviated" href="mailto:9313C89A-1DD2-11B2-899C-81EF5B6DD5A7@192.168.1.22">9313C89A-1DD2-11B2-899C-81EF5B6DD5A7@192.168.1.22</a>
4563395591901985372"<br>
Apr 20 14:34:48 ate rtpproxy[32664]: INFO:handle_command: delete
request failed: session
<a class="moz-txt-link-abbreviated" href="mailto:9313C89A-1DD2-11B2-899C-81EF5B6DD5A7@192.168.1.22">9313C89A-1DD2-11B2-899C-81EF5B6DD5A7@192.168.1.22</a>, tags
4563395591901985372/NONE not found<br>
Apr 20 14:34:48 ate rtpproxy[32664]: DBUG:doreply: sending reply
"1339_8 E8 "<br>
Apr 20 14:34:48 ate rtpproxy[32664]: DBUG:handle_command: received
command "1339_8 D <a class="moz-txt-link-abbreviated" href="mailto:9313C89A-1DD2-11B2-899C-81EF5B6DD5A7@192.168.1.22">9313C89A-1DD2-11B2-899C-81EF5B6DD5A7@192.168.1.22</a>
4563395591901985372"<br>
Apr 20 14:34:48 ate rtpproxy[32664]: INFO:handle_command: delete
request failed: session
<a class="moz-txt-link-abbreviated" href="mailto:9313C89A-1DD2-11B2-899C-81EF5B6DD5A7@192.168.1.22">9313C89A-1DD2-11B2-899C-81EF5B6DD5A7@192.168.1.22</a>, tags
4563395591901985372/NONE not found<br>
Apr 20 14:34:48 ate rtpproxy[32664]: DBUG:doreply: sending reply
"1339_8 E8 "</small><br>
<br>
<br>
Roberto<br>
<br>
<br>
<br>
<br>
Il martedì 20/04/10 14.05, Bogdan-Andrei Iancu ha scritto:
<blockquote cite="mid:4BCD988B.60602@voice-system.ro" type="cite">Hi
Roberto,
<br>
<br>
start RTPproxy with debugs (in foreground) and check for errors - a 0
port returned means some error on the rtpproxy side.
<br>
<br>
Regards,
<br>
Bogdan
<br>
<br>
Roberto Ovani wrote:
<br>
<blockquote type="cite">Hi !
<br>
I logged with xlog to answer to Bogdan's question :
<br>
this is what I can read in syslog:
<br>
Scenario : 1000@mydomain is trying to call 1002@mydomain :
<br>
<br>
/*Apr 20 11:44:58 opensips opensips[32557]:
>>>>>>>>>>>>>>>>>>>>>>>
entering route 6 !!!!!
<<<<<<<<<<<<<<<
<br>
Apr 20 11:44:58 opensips opensips[32557]: Method : INVITE --->
forceRTPproxy !!!!*/
<br>
Apr 20 11:44:58 opensips opensips[32558]: fix nated contact
<br>
*/Apr 20 11:44:59 opensips opensips[32557]:
ERROR:nathelper:force_rtp_proxy_body: incorrect port 0 in reply from
rtp proxy
<br>
Apr 20 11:44:59 opensips opensips[32557]: new branch at
<a class="moz-txt-link-freetext" href="sip:1002@151.16.40.175:58056;rinstance=0b5635955004021c/*">sip:1002@151.16.40.175:58056;rinstance=0b5635955004021c/*</a>
<br>
Apr 20 11:44:59 opensips opensips[32556]: incoming reply
<br>
Apr 20 11:44:59 opensips opensips[32556]: Qui siamo nella route onreply
: onreply_route[2]: ovvero nella gestione delle risposte 200OK o
183........... !!!!! <<<<<<<<<<
<br>
Apr 20 11:45:00 opensips opensips[32558]: incoming reply
<br>
Apr 20 11:45:00 opensips opensips[32558]: Qui siamo nella route onreply
: onreply_route[2]: ovvero nella gestione delle risposte 200OK o
183........... !!!!! <<<<<<<<<<
<br>
<br>
I'm a newbie in opensips, so I sometimes lose control of it :(
<br>
any other advice ?
<br>
<br>
thanks in advance
<br>
Roberto
<br>
<br>
<br>
<br>
Il martedì 20/04/10 11.29, Bogdan-Andrei Iancu ha scritto:
<br>
<blockquote type="cite">Hi Roberto,
<br>
<br>
does the error pop up when doing force_rtp_proxy() for the INVITE
request or for the 200 OK INVITE ?
<br>
<br>
Regards,
<br>
Bogdan
<br>
<br>
Roberto Ovani wrote:
<br>
<blockquote type="cite">Hello,
<br>
i have :
<br>
<br>
1) one host with opensips installed (opensips.roberto.com) on one
public ip
<br>
2) one host with rtpproxy installed (rtpproxy.roberto.com) on another
public ip
<br>
<br>
3) two clients into another LANs...
<br>
<br>
I forwarded the ports for making all work :
<br>
1) opensips : 5060 udp (for the registering in sip)
<br>
2) rtpproxy : 7890 udp (the socket), and the range 10,000 : 20,000 (i
compiled with this range)
<br>
<br>
when on sip client wants to call another sip clients (they're both
behind different nats and into different lans), then opensips must
rewrite the sdp so that the rtp flow goes through rtpproxy: in this
moment, opensips logs tell me :
<br>
/nathelper:force_rtp_proxy_body: incorrect port 0 in reply from rtp
proxy
<br>
<br>
/and the communication cannot happen correctly...... any advice ? what
shoul I have to check ?
<br>
<br>
Roberto
<br>
------------------------------------------------------------------------
<br>
<br>
_______________________________________________
<br>
Users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
<br>
</blockquote>
</blockquote>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
</body>
</html>