[OpenSIPS-Users] Info about rtpproxy and opensips working together on different hosts...

[Laszlo]

Hi,


2010/4/20 Roberto Ovani <roberto.ebay at gmail.com>

>  This is what I get in /var/log/syslog at RTPPROXY's host,
> when I get "ERROR:nathelper:force_rtp_proxy_body: incorrect port 0 in reply
> from rtp proxy" at opensips' host :
>
> Apr 20 14:34:45 ate rtpproxy[32664]: DBUG:handle_command: received command
> "1338_6 V"
> Apr 20 14:34:45 ate rtpproxy[32664]: DBUG:doreply: sending reply "1338_6
> 20040107 "
> Apr 20 14:34:45 ate rtpproxy[32664]: DBUG:handle_command: received command
> "1338_7 VF 20050322"
> Apr 20 14:34:45 ate rtpproxy[32664]: DBUG:doreply: sending reply "1338_7 1
> "
> Apr 20 14:34:45 ate rtpproxy[32664]: DBUG:handle_command: received command
> "1338_8 VF 20071116"
> Apr 20 14:34:45 ate rtpproxy[32664]: DBUG:doreply: sending reply "1338_8 1
> "
> Apr 20 14:34:45 ate rtpproxy[32664]: DBUG:handle_command: received command
> "1338_9 VF 20081102"
> Apr 20 14:34:45 ate rtpproxy[32664]: DBUG:doreply: sending reply "1338_9 1
> "
> Apr 20 14:34:45 ate rtpproxy[32664]: DBUG:handle_command: received command
> "1338_10 Uc3,8,0,101 9313C89A-1DD2-11B2-899C-81EF5B6DD5A7 at 192.168.1.22151.68.60.80 49164 4563395591901985372;1"
> Apr 20 14:34:45 ate rtpproxy[32664]: INFO:handle_command: new session
> 9313C89A-1DD2-11B2-899C-81EF5B6DD5A7 at 192.168.1.22, tag
> 4563395591901985372;1 requested, type strong
> Apr 20 14:34:47 ate rtpproxy[32664]: ERR:handle_command: can't create
> listener
> Apr 20 14:34:47 ate rtpproxy[32664]: DBUG:doreply: sending reply "1338_10
> E10 "
> Apr 20 14:34:47 ate rtpproxy[32664]: DBUG:handle_command: received command
> "1338_10 Uc3,8,0,101 9313C89A-1DD2-11B2-899C-81EF5B6DD5A7 at 192.168.1.22151.68.60.80 49164 4563395591901985372;1"
> Apr 20 14:34:47 ate rtpproxy[32664]: INFO:handle_command: new session
> 9313C89A-1DD2-11B2-899C-81EF5B6DD5A7 at 192.168.1.22, tag
> 4563395591901985372;1 requested, type strong
> Apr 20 14:34:48 ate rtpproxy[32664]: ERR:handle_command: can't create
> listener
> Apr 20 14:34:48 ate rtpproxy[32664]: DBUG:doreply: sending reply "1338_10
> E10 "
> Apr 20 14:34:48 ate rtpproxy[32664]: DBUG:handle_command: received command
> "1339_8 D 9313C89A-1DD2-11B2-899C-81EF5B6DD5A7 at 192.168.1.224563395591901985372"
> Apr 20 14:34:48 ate rtpproxy[32664]: INFO:handle_command: delete request
> failed: session 9313C89A-1DD2-11B2-899C-81EF5B6DD5A7 at 192.168.1.22, tags
> 4563395591901985372/NONE not found
> Apr 20 14:34:48 ate rtpproxy[32664]: DBUG:doreply: sending reply "1339_8 E8
> "
> Apr 20 14:34:48 ate rtpproxy[32664]: DBUG:handle_command: received command
> "1339_8 D 9313C89A-1DD2-11B2-899C-81EF5B6DD5A7 at 192.168.1.224563395591901985372"
> Apr 20 14:34:48 ate rtpproxy[32664]: INFO:handle_command: delete request
> failed: session 9313C89A-1DD2-11B2-899C-81EF5B6DD5A7 at 192.168.1.22, tags
> 4563395591901985372/NONE not found
> Apr 20 14:34:48 ate rtpproxy[32664]: DBUG:doreply: sending reply "1339_8 E8
> "
>
>
> Roberto
>
>
>
>
> Il martedì 20/04/10 14.05, Bogdan-Andrei Iancu ha scritto:
>
> Hi Roberto,
>
> start RTPproxy with debugs (in foreground) and check for errors - a 0 port
> returned means some error on the rtpproxy side.
>
> Regards,
> Bogdan
>
> Roberto Ovani wrote:
>
> Hi !
> I logged with xlog to answer to Bogdan's question :
> this is what I can read in syslog:
> Scenario : 1000 at mydomain is trying to call 1002 at mydomain :
>
> /*Apr 20 11:44:58 opensips opensips[32557]: >>>>>>>>>>>>>>>>>>>>>>>
> entering route 6 !!!!! <<<<<<<<<<<<<<<
> Apr 20 11:44:58 opensips opensips[32557]: Method : INVITE --->
> forceRTPproxy !!!!*/
> Apr 20 11:44:58 opensips opensips[32558]: fix nated contact
> */Apr 20 11:44:59 opensips opensips[32557]:
> ERROR:nathelper:force_rtp_proxy_body: incorrect port 0 in reply from rtp
> proxy
> Apr 20 11:44:59 opensips opensips[32557]: new branch at
> sip:1002 at 151.16.40.175:58056;rinstance=0b5635955004021c/*
> Apr 20 11:44:59 opensips opensips[32556]: incoming reply
> Apr 20 11:44:59 opensips opensips[32556]: Qui siamo nella route onreply :
> onreply_route[2]: ovvero nella gestione delle risposte 200OK o
> 183........... !!!!! <<<<<<<<<<
> Apr 20 11:45:00 opensips opensips[32558]: incoming reply
> Apr 20 11:45:00 opensips opensips[32558]: Qui siamo nella route onreply :
> onreply_route[2]: ovvero nella gestione delle risposte 200OK o
> 183........... !!!!! <<<<<<<<<<
>
> I'm a newbie in opensips, so I sometimes lose control of it :(
> any other advice ?
>
> thanks in advance
> Roberto
>
>
>
> Il martedì 20/04/10 11.29, Bogdan-Andrei Iancu ha scritto:
>
> Hi Roberto,
>
> does the error pop up when doing force_rtp_proxy() for the INVITE request
> or for the 200 OK INVITE ?
>
> Regards,
> Bogdan
>
> Roberto Ovani wrote:
>
>
> Hello,
> i have :
>
> 1) one host with opensips installed (opensips.roberto.com) on one public
> ip
> 2) one host with rtpproxy installed (rtpproxy.roberto.com) on another
> public ip
>
> 3) two clients into another LANs...
>
> I forwarded the ports for making all work :
> 1) opensips : 5060 udp (for the registering in sip)
> 2) rtpproxy : 7890 udp (the socket), and the range 10,000 : 20,000 (i
> compiled with this range)
>
> 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 :
> /nathelper:force_rtp_proxy_body: incorrect port 0 in reply from rtp proxy
>
> /and the communication cannot happen correctly...... any advice ? what
> shoul I have to check ?
>
> Roberto
> ------------------------------------------------------------------------
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>
>
>
>
>
>
Hmm, can you run netstat -uap during you calling out for testing?
Do you see established connections or any connections to the remote
rtpproxy?


-Laszlo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20100420/33a292af/attachment.htm