Re: [OpenSIPS-Users] RTP Proxy Problem - No Way Audio (RTP Traces Within)
Hi, Nick!
From your traces, I can see that the RTPProxy session is properly
established (you have both an offer and an answer). But on the media
level, all I can see is that Asterisk (the callee) is sending RTP to
caller, but the caller doesn't send anything. Also, this is what
RTPProxy indicates (RTP stats: 86 in from callee, 0 in from caller).
Most likely you should checkwhere is the NAT Box trying to sendRTP.
Best regards,
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 03/15/2013 02:00 AM, Nick Khamis wrote:
Hello Everyone,
I am having problem getting RTP packets flowing smoothly. The setup is
NAT Box (192.168.2.1) - OpenSIPS/RTPProxy (192.168.2.5) - Asterisk
(192.168.2.10)
I know that media is reaching the boxes since I see:
OpenSIPS (192.168.2.5)
0.00 192.168.2.10 - 192.168.2.5 UDP 214 Source port: 24454
Destination port: 20198
0.99 192.168.2.5 - 81.201.85.45 UDP 214 Source port: 39810
Destination port: 13272
0.017956 192.168.2.10 - 192.168.2.5 UDP 214 Source port: 24454
Destination port: 20198
0.018028 192.168.2.5 - 81.201.85.45 UDP 214 Source port: 39810
Destination port: 13272
0.037760 192.168.2.10 - 192.168.2.5 UDP 214 Source port: 24454
Destination port: 20198
0.037814 192.168.2.5 - 81.201.85.45 UDP 214 Source port: 39810
Destination port: 13272
Asterisk CLI (192.168.2.10)
Sent RTP P2P packet to 192.168.2.5:20198 (type 00, len 000160)
Sent RTP P2P packet to 192.168.2.5:20198 (type 00, len 000160)
Sent RTP P2P packet to 192.168.2.5:20198 (type 00, len 000160)
Sent RTP P2P packet to 192.168.2.5:20198 (type 00, len 000160)
Sent RTP P2P packet to 192.168.2.5:20198 (type 00, len 000160)
Sent RTP P2P packet to 192.168.2.5:20198 (type 00, len 000160)
Sent RTP P2P packet to 192.168.2.5:20198 (type 00, len 000160)
RTPProxy Messages:
INFO:handle_command: new session
KN74JOEJTRFDVOR3PEH7I5XGBA@81.201.85.45, tag 86219;1 requested, type
strong
INFO:handle_command: new session on a port 20198 created, tag 86219;1
INFO:handle_command: pre-filling caller's address with 81.201.85.45:13272
INFO:handle_command: lookup on ports 20198/39810, session timer restarted
INFO:handle_command: pre-filling callee's address with 192.168.2.10:24454
INFO:handle_delete: forcefully deleting session 1 on ports 20198/39810
INFO:remove_session: RTP stats: 86 in from callee, 0 in from caller,
86 relayed, 0 dropped
INFO:remove_session: RTCP stats: 0 in from callee, 0 in from caller, 0
relayed, 0 dropped
INFO:remove_session: session on ports 20198/39810 is cleaned up
It says 86 in from callee but we do not even have incoming audio. I'm
pretty sure it's rtpproxy_offer/answer issue so bellow is my
configuration:
route[1] {
xlog(Start Call Route For: [ fu=$fu/ tu=$tu /ru=$ru/
ci=$ci]\n);
if (has_body(application/sdp)) {
xlog(Has SDP: $fu\n);
rtpproxy_offer();
}
}
onreply_route[1] {
xlog(Reply Route 1: [ fu=$fu/ tu=$tu /ru=$ru/ ci=$ci]\n);
if (has_body(application/sdp)) {
xlog(Answering RTP Proxy: $fu\n);
rtpproxy_answer();
}
}
Your help is greatly appreciated,
Nick.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] RTP Proxy Problem - No Way Audio (RTP Traces Within)
Hello Everyone,
I am having problem getting RTP packets flowing smoothly. The setup is
NAT Box (192.168.2.1) - OpenSIPS/RTPProxy (192.168.2.5) - Asterisk
(192.168.2.10)
I know that media is reaching the boxes since I see:
OpenSIPS (192.168.2.5)
0.00 192.168.2.10 - 192.168.2.5 UDP 214 Source port: 24454
Destination port: 20198
0.99 192.168.2.5 - 81.201.85.45 UDP 214 Source port: 39810
Destination port: 13272
0.017956 192.168.2.10 - 192.168.2.5 UDP 214 Source port: 24454
Destination port: 20198
0.018028 192.168.2.5 - 81.201.85.45 UDP 214 Source port: 39810
Destination port: 13272
0.037760 192.168.2.10 - 192.168.2.5 UDP 214 Source port: 24454
Destination port: 20198
0.037814 192.168.2.5 - 81.201.85.45 UDP 214 Source port: 39810
Destination port: 13272
Asterisk CLI (192.168.2.10)
Sent RTP P2P packet to 192.168.2.5:20198 (type 00, len 000160)
Sent RTP P2P packet to 192.168.2.5:20198 (type 00, len 000160)
Sent RTP P2P packet to 192.168.2.5:20198 (type 00, len 000160)
Sent RTP P2P packet to 192.168.2.5:20198 (type 00, len 000160)
Sent RTP P2P packet to 192.168.2.5:20198 (type 00, len 000160)
Sent RTP P2P packet to 192.168.2.5:20198 (type 00, len 000160)
Sent RTP P2P packet to 192.168.2.5:20198 (type 00, len 000160)
RTPProxy Messages:
INFO:handle_command: new session
KN74JOEJTRFDVOR3PEH7I5XGBA@81.201.85.45, tag 86219;1 requested, type
strong
INFO:handle_command: new session on a port 20198 created, tag 86219;1
INFO:handle_command: pre-filling caller's address with 81.201.85.45:13272
INFO:handle_command: lookup on ports 20198/39810, session timer restarted
INFO:handle_command: pre-filling callee's address with 192.168.2.10:24454
INFO:handle_delete: forcefully deleting session 1 on ports 20198/39810
INFO:remove_session: RTP stats: 86 in from callee, 0 in from caller,
86 relayed, 0 dropped
INFO:remove_session: RTCP stats: 0 in from callee, 0 in from caller, 0
relayed, 0 dropped
INFO:remove_session: session on ports 20198/39810 is cleaned up
It says 86 in from callee but we do not even have incoming audio. I'm
pretty sure it's rtpproxy_offer/answer issue so bellow is my
configuration:
route[1] {
xlog(Start Call Route For: [ fu=$fu/ tu=$tu /ru=$ru/
ci=$ci]\n);
if (has_body(application/sdp)) {
xlog(Has SDP: $fu\n);
rtpproxy_offer();
}
}
onreply_route[1] {
xlog(Reply Route 1: [ fu=$fu/ tu=$tu /ru=$ru/ ci=$ci]\n);
if (has_body(application/sdp)) {
xlog(Answering RTP Proxy: $fu\n);
rtpproxy_answer();
}
}
Your help is greatly appreciated,
Nick.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] RTP Proxy problem
Dear all,
I had to use both flags IE and EI in rtpproxy_offer and rtpproxy_anwser.
Now it's working fine.
Thanks a lot
On 18 December 2012 13:39, Patrick Wakano pwak...@gmail.com wrote:
I have configured a scenario very similar to yours and I had to use both
the flags 'e' and 'i' accordingly to indicate the direction of the
message when calling rtpproxy_offer() or rtpproxy_answer().
I think, in your case, for INVITEs going to PSTN GW, you have to use the
flags ei, and for 200OK of this dialog use flags ie. For INVITEs coming
from the PSTN GW, you have to use flags ie and for 200Ok of this dialog
use flags ei.
If that doesn't work try to change the 'e' and 'i' order.
On Fri, Dec 14, 2012 at 12:54 PM, Răzvan Crainea raz...@opensips.orgwrote:
Hi, Wesley!
How exactly have you used the E/I flags? Have you tried to combine them
rtpproxy(ie) or rtpproxy(ei)? Taking a look in the Rtpproxy code, it's
kind of awkward how these flags are handled.
Best regards,
Razvan Crainea
OpenSIPS Core Developerhttp://www.opensips-solutions.com
On 12/14/2012 01:59 PM, Wesley Volcov wrote:
Hey Guys,
Some ideas?
Regards,
Wesley Volcov
On 11 December 2012 11:35, Wesley Volcov wesleyvol...@gmail.com wrote:
Dear all,
I could fix the rtpproxy problem, it was a compilation problem.
But now, I'm having a audio problem.
Let me explain:
I have a Opensips with 2 IP addres, a public one (200.0.0.1) and a
private one (10.0.0.1).
The orignation endppint is in the private network (IP TEL), the PSTN
gateway is in the public network.
I receive a call from the IP TEL and send it to the gateway.
In the INVITE that the Opensips sends to the PSTN gateway, I see the
Public IP in the CIN parameter, but in the 200 OK that the Opensips sends
to the TEL IP I see the public IP to, and call goes to one way audio.
The Opensips should send the private IP in the 200OK to the IP TEL.
RTPPROXY run command: /usr/local/bin/rtpproxy -l 200.0.0.1 10.0.0.1 -s
udp:127.0.0.1 7890 -F -m 1 -M 2 -d DBUG
Opensips:
if (is_method(INVITE)){
rtpproxy_offer(,200.0.0.1);
}
onreply_route [ONREPLY] {
rtpproxy_answer(,10.0.0.1);
}
I've tried some parametes in the rtpproxy like FW, I, E, but I had the
same result.
I'am missing some thing?
Please, help me guys.
Thanks a lot
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Wesley Volcov
Email: wesleyvol...@gmail.com
Messenger: vol...@live.com
Skype: wesley.volcov
Mobile: +55 11 7999-7444
Website: http://volcov.blogspot.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] RTP Proxy problem
I have configured a scenario very similar to yours and I had to use both
the flags 'e' and 'i' accordingly to indicate the direction of the
message when calling rtpproxy_offer() or rtpproxy_answer().
I think, in your case, for INVITEs going to PSTN GW, you have to use the
flags ei, and for 200OK of this dialog use flags ie. For INVITEs coming
from the PSTN GW, you have to use flags ie and for 200Ok of this dialog
use flags ei.
If that doesn't work try to change the 'e' and 'i' order.
On Fri, Dec 14, 2012 at 12:54 PM, Răzvan Crainea raz...@opensips.orgwrote:
Hi, Wesley!
How exactly have you used the E/I flags? Have you tried to combine them
rtpproxy(ie) or rtpproxy(ei)? Taking a look in the Rtpproxy code, it's
kind of awkward how these flags are handled.
Best regards,
Razvan Crainea
OpenSIPS Core Developerhttp://www.opensips-solutions.com
On 12/14/2012 01:59 PM, Wesley Volcov wrote:
Hey Guys,
Some ideas?
Regards,
Wesley Volcov
On 11 December 2012 11:35, Wesley Volcov wesleyvol...@gmail.com wrote:
Dear all,
I could fix the rtpproxy problem, it was a compilation problem.
But now, I'm having a audio problem.
Let me explain:
I have a Opensips with 2 IP addres, a public one (200.0.0.1) and a
private one (10.0.0.1).
The orignation endppint is in the private network (IP TEL), the PSTN
gateway is in the public network.
I receive a call from the IP TEL and send it to the gateway.
In the INVITE that the Opensips sends to the PSTN gateway, I see the
Public IP in the CIN parameter, but in the 200 OK that the Opensips sends
to the TEL IP I see the public IP to, and call goes to one way audio.
The Opensips should send the private IP in the 200OK to the IP TEL.
RTPPROXY run command: /usr/local/bin/rtpproxy -l 200.0.0.1 10.0.0.1 -s
udp:127.0.0.1 7890 -F -m 1 -M 2 -d DBUG
Opensips:
if (is_method(INVITE)){
rtpproxy_offer(,200.0.0.1);
}
onreply_route [ONREPLY] {
rtpproxy_answer(,10.0.0.1);
}
I've tried some parametes in the rtpproxy like FW, I, E, but I had the
same result.
I'am missing some thing?
Please, help me guys.
Thanks a lot
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] RTP Proxy problem
Hey Guys,
Some ideas?
Regards,
Wesley Volcov
On 11 December 2012 11:35, Wesley Volcov wesleyvol...@gmail.com wrote:
Dear all,
I could fix the rtpproxy problem, it was a compilation problem.
But now, I'm having a audio problem.
Let me explain:
I have a Opensips with 2 IP addres, a public one (200.0.0.1) and a private
one (10.0.0.1).
The orignation endppint is in the private network (IP TEL), the PSTN
gateway is in the public network.
I receive a call from the IP TEL and send it to the gateway.
In the INVITE that the Opensips sends to the PSTN gateway, I see the
Public IP in the CIN parameter, but in the 200 OK that the Opensips sends
to the TEL IP I see the public IP to, and call goes to one way audio.
The Opensips should send the private IP in the 200OK to the IP TEL.
RTPPROXY run command: /usr/local/bin/rtpproxy -l 200.0.0.1 10.0.0.1 -s
udp:127.0.0.1
7890 -F -m 1 -M 2 -d DBUG
Opensips:
if (is_method(INVITE)){
rtpproxy_offer(,200.0.0.1);
}
onreply_route [ONREPLY] {
rtpproxy_answer(,10.0.0.1);
}
I've tried some parametes in the rtpproxy like FW, I, E, but I had the
same result.
I'am missing some thing?
Please, help me guys.
Thanks a lot
On 1 December 2012 03:05, SamyGo govoi...@gmail.com wrote:
Hi,
The issue is with the command you are using to start RTPproxy. Missing a
: between 127.0.0.1 and 7890. So now you may not see RTPproxy on netstat
output.
Regards,
Sammy
On Dec 1, 2012 12:30 AM, Răzvan Crainea raz...@opensips.org wrote:
Hi, Wesley!
Have you tried tracing the communication opensips has with rtpproxy
(listen with ngrep on port 7890). Are you sure rtpproxy is bound on the
correct IP and port (check with netstat -ulpn | grep rtpproxy). Have you
tried enabling rtpproxy debugging to see if something reaches the server
(start rtpproxy with -d DBUG).
Regards,
Razvan Crainea
OpenSIPS Core Developerhttp://www.opensips-solutions.com
On 11/30/2012 08:06 PM, Wesley Volcov wrote:
Dear all,
I've tried to downgrade the opensips version, and use the nathelper
module, but I still see the error.
RTPPROXY run command: /usr/local/bin/rtpproxy -l public_ip -s udp:127.0.0.1
7890 -F -m 1 -M 2
Opensips configuration: modparam(nathelper, rtpproxy_sock, udp:
127.0.0.1:7890)
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10695]:
ERROR:nathelper:send_rtpp_command: can't send command to a RTP proxy
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10699]:
ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not
respond, disable it
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10707]:
ERROR:nathelper:send_rtpp_command: can't send command to a RTP proxy
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10679]:
ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not
respond, disable it
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10682]:
ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not
respond, disable it
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10678]:
ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not
respond, disable it
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10684]:
ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not
respond, disable it
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10686]:
ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not
respond, disable it
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10687]:
ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not
respond, disable it
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10690]:
ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not
respond, disable it
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10691]:
ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not
respond, disable it
Am I missing some thing?
Please, helpe me.
Regards,
Wesley Volcov
On 29 November 2012 08:28, Wesley Volcov wesleyvol...@gmail.comwrote:
Dear Răzvan,
*
*
Thanks you for helping me!
I changed the modparam to: modparam(rtpproxy, rtpproxy_sock, udp:
127.0.0.1:7890)
And the rtpproxy run command: /usr/local/bin/rtpproxy -lpublic_ip -s
udp:127.0.0.1 7890 -F -m 1 -M 2
And I still see this:
Nov 29 08:25:42 opensips /usr/local/sbin/opensips[5996]:
WARNING:rtpproxy:rtpp_test: support for RTP proxy udp:127.0.0.1:7890
has been disabled temporarily
Nov 29 08:25:42 opensips /usr/local/sbin/opensips[5994]:
WARNING:rtpproxy:rtpp_test: can't get version of the RTP proxy
Any idea?
Regards,
Wesley Volcov
On 28 November 2012 16:02, Răzvan Crainea raz...@opensips.org wrote:
Hi, Wesley!
The idea is that RTPProxy is listening only on localhost, whereas
OpenSIPS tries to connect to a different IP (rather than 127.0.0.1). You
should either allow RTPProxy to listen on that IP (change the -s
Re: [OpenSIPS-Users] RTP Proxy problem
You need to check version compatibility. I use Kamailio-315 and rtpproxy110, and they work fine. Austin On Wed, Nov 28, 2012 at 6:55 PM, Wesley Volcov wesleyvol...@gmail.comwrote: Dear all, I'm having problems with my Opensips + RTP Proxy instalation. Opensips version: 1.7.2-notls RTP Proxy version: 1.2.1 Start RTP Proxy command: /usr/local/bin/rtpproxy -l ip_address -s udp:127.0.0.1 7890 -F -m 1 -M 2 Opensips configuration for RTP Proxy: modparam(rtpproxy, rtpproxy_sock, udp:localhost:7890) When I start the Opensips service, it logs this message: Nov 28 10:56:10 opensips /usr/local/sbin/opensips[2687]: WARNING:rtpproxy:rtpp_test: can't get version of the RTP proxy Nov 28 10:56:10 opensips /usr/local/sbin/opensips[2687]: WARNING:rtpproxy:rtpp_test: support for RTP proxy udp:ip_address:7890 has been disabled temporarily What could it be? Please, help me! Regards -- Wesley Volcov Email: wesleyvol...@gmail.com Messenger: vol...@live.com Skype: wesley.volcov Mobile: +55 11 7999-7444 Website: http://volcov.blogspot.com ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] RTP Proxy problem
Hi, Wesley!
How exactly have you used the E/I flags? Have you tried to combine them
rtpproxy(ie) or rtpproxy(ei)? Taking a look in the Rtpproxy code,
it's kind of awkward how these flags are handled.
Best regards,
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 12/14/2012 01:59 PM, Wesley Volcov wrote:
Hey Guys,
Some ideas?
Regards,
Wesley Volcov
On 11 December 2012 11:35, Wesley Volcov wesleyvol...@gmail.com
mailto:wesleyvol...@gmail.com wrote:
Dear all,
I could fix the rtpproxy problem, it was a compilation problem.
But now, I'm having a audio problem.
Let me explain:
I have a Opensips with 2 IP addres, a public one (200.0.0.1) and a
private one (10.0.0.1).
The orignation endppint is in the private network (IP TEL), the
PSTN gateway is in the public network.
I receive a call from the IP TEL and send it to the gateway.
In the INVITE that the Opensips sends to the PSTN gateway, I see
the Public IP in the CIN parameter, but in the 200 OK that the
Opensips sends to the TEL IP I see the public IP to, and call goes
to one way audio.
The Opensips should send the private IP in the 200OK to the IP TEL.
RTPPROXY run command: /usr/local/bin/rtpproxy -l 200.0.0.1
10.0.0.1 -s udp:127.0.0.1 7890 tel:127.0.0.1%207890 -F -m 1
-M 2 -d DBUG
Opensips:
if (is_method(INVITE)){
rtpproxy_offer(,200.0.0.1);
}
onreply_route [ONREPLY] {
rtpproxy_answer(,10.0.0.1);
}
I've tried some parametes in the rtpproxy like FW, I, E, but I had
the same result.
I'am missing some thing?
Please, help me guys.
Thanks a lot
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] RTP Proxy problem
Dear all,
I could fix the rtpproxy problem, it was a compilation problem.
But now, I'm having a audio problem.
Let me explain:
I have a Opensips with 2 IP addres, a public one (200.0.0.1) and a private
one (10.0.0.1).
The orignation endppint is in the private network (IP TEL), the PSTN
gateway is in the public network.
I receive a call from the IP TEL and send it to the gateway.
In the INVITE that the Opensips sends to the PSTN gateway, I see the Public
IP in the CIN parameter, but in the 200 OK that the Opensips sends to the
TEL IP I see the public IP to, and call goes to one way audio.
The Opensips should send the private IP in the 200OK to the IP TEL.
RTPPROXY run command: /usr/local/bin/rtpproxy -l 200.0.0.1 10.0.0.1 -s
udp:127.0.0.1 7890 -F -m 1 -M 2 -d DBUG
Opensips:
if (is_method(INVITE)){
rtpproxy_offer(,200.0.0.1);
}
onreply_route [ONREPLY] {
rtpproxy_answer(,10.0.0.1);
}
I've tried some parametes in the rtpproxy like FW, I, E, but I had the same
result.
I'am missing some thing?
Please, help me guys.
Thanks a lot
On 1 December 2012 03:05, SamyGo govoi...@gmail.com wrote:
Hi,
The issue is with the command you are using to start RTPproxy. Missing a :
between 127.0.0.1 and 7890. So now you may not see RTPproxy on netstat
output.
Regards,
Sammy
On Dec 1, 2012 12:30 AM, Răzvan Crainea raz...@opensips.org wrote:
Hi, Wesley!
Have you tried tracing the communication opensips has with rtpproxy
(listen with ngrep on port 7890). Are you sure rtpproxy is bound on the
correct IP and port (check with netstat -ulpn | grep rtpproxy). Have you
tried enabling rtpproxy debugging to see if something reaches the server
(start rtpproxy with -d DBUG).
Regards,
Razvan Crainea
OpenSIPS Core Developerhttp://www.opensips-solutions.com
On 11/30/2012 08:06 PM, Wesley Volcov wrote:
Dear all,
I've tried to downgrade the opensips version, and use the nathelper
module, but I still see the error.
RTPPROXY run command: /usr/local/bin/rtpproxy -l public_ip -s udp:127.0.0.1
7890 -F -m 1 -M 2
Opensips configuration: modparam(nathelper, rtpproxy_sock, udp:
127.0.0.1:7890)
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10695]:
ERROR:nathelper:send_rtpp_command: can't send command to a RTP proxy
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10699]:
ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not
respond, disable it
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10707]:
ERROR:nathelper:send_rtpp_command: can't send command to a RTP proxy
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10679]:
ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not
respond, disable it
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10682]:
ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not
respond, disable it
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10678]:
ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not
respond, disable it
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10684]:
ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not
respond, disable it
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10686]:
ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not
respond, disable it
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10687]:
ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not
respond, disable it
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10690]:
ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not
respond, disable it
Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10691]:
ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not
respond, disable it
Am I missing some thing?
Please, helpe me.
Regards,
Wesley Volcov
On 29 November 2012 08:28, Wesley Volcov wesleyvol...@gmail.com wrote:
Dear Răzvan,
*
*
Thanks you for helping me!
I changed the modparam to: modparam(rtpproxy, rtpproxy_sock, udp:
127.0.0.1:7890)
And the rtpproxy run command: /usr/local/bin/rtpproxy -lpublic_ip -s
udp:127.0.0.1 7890 -F -m 1 -M 2
And I still see this:
Nov 29 08:25:42 opensips /usr/local/sbin/opensips[5996]:
WARNING:rtpproxy:rtpp_test: support for RTP proxy udp:127.0.0.1:7890
has been disabled temporarily
Nov 29 08:25:42 opensips /usr/local/sbin/opensips[5994]:
WARNING:rtpproxy:rtpp_test: can't get version of the RTP proxy
Any idea?
Regards,
Wesley Volcov
On 28 November 2012 16:02, Răzvan Crainea raz...@opensips.org wrote:
Hi, Wesley!
The idea is that RTPProxy is listening only on localhost, whereas
OpenSIPS tries to connect to a different IP (rather than 127.0.0.1). You
should either allow RTPProxy to listen on that IP (change the -s parameter,
but this is not recommended because of security issues) or configure
OpenSIPS to connect using 127.0.0.1.
Are you using the DB to provision
Re: [OpenSIPS-Users] RTP Proxy problem
Dear all, I've tried to downgrade the opensips version, and use the nathelper module, but I still see the error. RTPPROXY run command: /usr/local/bin/rtpproxy -l public_ip -s udp:127.0.0.1 7890 -F -m 1 -M 2 Opensips configuration: modparam(nathelper, rtpproxy_sock, udp: 127.0.0.1:7890) Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10695]: ERROR:nathelper:send_rtpp_command: can't send command to a RTP proxy Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10699]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10707]: ERROR:nathelper:send_rtpp_command: can't send command to a RTP proxy Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10679]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10682]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10678]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10684]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10686]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10687]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10690]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10691]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not respond, disable it Am I missing some thing? Please, helpe me. Regards, Wesley Volcov On 29 November 2012 08:28, Wesley Volcov wesleyvol...@gmail.com wrote: Dear Răzvan, * * Thanks you for helping me! I changed the modparam to: modparam(rtpproxy, rtpproxy_sock, udp: 127.0.0.1:7890) And the rtpproxy run command: /usr/local/bin/rtpproxy -lpublic_ip -s udp:127.0.0.1 7890 -F -m 1 -M 2 And I still see this: Nov 29 08:25:42 opensips /usr/local/sbin/opensips[5996]: WARNING:rtpproxy:rtpp_test: support for RTP proxy udp:127.0.0.1:7890 has been disabled temporarily Nov 29 08:25:42 opensips /usr/local/sbin/opensips[5994]: WARNING:rtpproxy:rtpp_test: can't get version of the RTP proxy Any idea? Regards, Wesley Volcov On 28 November 2012 16:02, Răzvan Crainea raz...@opensips.org wrote: Hi, Wesley! The idea is that RTPProxy is listening only on localhost, whereas OpenSIPS tries to connect to a different IP (rather than 127.0.0.1). You should either allow RTPProxy to listen on that IP (change the -s parameter, but this is not recommended because of security issues) or configure OpenSIPS to connect using 127.0.0.1. Are you using the DB to provision the RTPProxy sockets? Because if you do, there is no need of the rtpproxy_sock modparam, you should change the IP directly in the database. Regards, Razvan Crainea OpenSIPS Core Developerhttp://www.opensips-solutions.com On 11/28/2012 05:53 PM, Wesley Volcov wrote: Dear Răzvan, * * I tried to change the modparam configuration, to the ip_addres, and also the rtpproxy listen addres to localhost, and it still the same problem. Regards, Wesley Volcov On 28 November 2012 12:31, Răzvan Crainea raz...@opensips.org wrote: Hi, Wesley! I see that your modparam contains the localhost ip, however, the OpenSIPS warning contains the ip_address. Is this ip_address 127.0.0.1? Because if it is not, then it means that the rtpproxy_sock is set to a different value - either by overwriting the parameter, or by using the DB provisioning mode. Most likely it doesn't work because OpenSIPS is trying to connect to rtpproxy on a public IP, whereas RTPProxy only listens on localhost. Regards, Razvan Crainea OpenSIPS Core Developerhttp://www.opensips-solutions.com On 11/28/2012 02:25 PM, Wesley Volcov wrote: Dear all, I'm having problems with my Opensips + RTP Proxy instalation. Opensips version: 1.7.2-notls RTP Proxy version: 1.2.1 Start RTP Proxy command: /usr/local/bin/rtpproxy -l ip_address -s udp:127.0.0.1 7890 127.0.0.1%207890 -F -m 1 -M 2 Opensips configuration for RTP Proxy: modparam(rtpproxy, rtpproxy_sock, udp:localhost:7890) When I start the Opensips service, it logs this message: Nov 28 10:56:10 opensips /usr/local/sbin/opensips[2687]: WARNING:rtpproxy:rtpp_test: can't get version of the RTP proxy Nov 28 10:56:10 opensips /usr/local/sbin/opensips[2687]: WARNING:rtpproxy:rtpp_test: support for RTP proxy udp:ip_address:7890 has been disabled temporarily What could it be? Please, help me! Regards -- Wesley Volcov Email:
Re: [OpenSIPS-Users] RTP Proxy problem
Hi, Wesley! Have you tried tracing the communication opensips has with rtpproxy (listen with ngrep on port 7890). Are you sure rtpproxy is bound on the correct IP and port (check with netstat -ulpn | grep rtpproxy). Have you tried enabling rtpproxy debugging to see if something reaches the server (start rtpproxy with -d DBUG). Regards, Razvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 11/30/2012 08:06 PM, Wesley Volcov wrote: Dear all, I've tried to downgrade the opensips version, and use the nathelper module, but I still see the error. RTPPROXY run command: /usr/local/bin/rtpproxy -l public_ip -s udp:127.0.0.1 7890 -F -m 1 -M 2 Opensips configuration: modparam(nathelper, rtpproxy_sock, udp:127.0.0.1:7890 http://127.0.0.1:7890) Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10695]: ERROR:nathelper:send_rtpp_command: can't send command to a RTP proxy Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10699]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 http://127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10707]: ERROR:nathelper:send_rtpp_command: can't send command to a RTP proxy Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10679]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 http://127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10682]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 http://127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10678]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 http://127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10684]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 http://127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10686]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 http://127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10687]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 http://127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10690]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 http://127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10691]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 http://127.0.0.1:7890 does not respond, disable it Am I missing some thing? Please, helpe me. Regards, Wesley Volcov On 29 November 2012 08:28, Wesley Volcov wesleyvol...@gmail.com mailto:wesleyvol...@gmail.com wrote: Dear Răzvan, * * Thanks you for helping me! I changed the modparam to: modparam(rtpproxy, rtpproxy_sock, udp:127.0.0.1:7890 http://127.0.0.1:7890) And the rtpproxy run command: /usr/local/bin/rtpproxy -lpublic_ip -s udp:127.0.0.1 7890 tel:127.0.0.1%207890 -F -m 1 -M 2 And I still see this: Nov 29 08:25:42 opensips /usr/local/sbin/opensips[5996]: WARNING:rtpproxy:rtpp_test: support for RTP proxy udp:127.0.0.1:7890 http://127.0.0.1:7890 has been disabled temporarily Nov 29 08:25:42 opensips /usr/local/sbin/opensips[5994]: WARNING:rtpproxy:rtpp_test: can't get version of the RTP proxy Any idea? Regards, Wesley Volcov On 28 November 2012 16:02, Răzvan Crainea raz...@opensips.org mailto:raz...@opensips.org wrote: Hi, Wesley! The idea is that RTPProxy is listening only on localhost, whereas OpenSIPS tries to connect to a different IP (rather than 127.0.0.1). You should either allow RTPProxy to listen on that IP (change the -s parameter, but this is not recommended because of security issues) or configure OpenSIPS to connect using 127.0.0.1. Are you using the DB to provision the RTPProxy sockets? Because if you do, there is no need of the rtpproxy_sock modparam, you should change the IP directly in the database. Regards, Razvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 11/28/2012 05:53 PM, Wesley Volcov wrote: Dear Răzvan, * * I tried to change the modparam configuration, to the ip_addres, and also the rtpproxy listen addres to localhost, and it still the same problem. Regards, Wesley Volcov On 28 November 2012 12:31, Răzvan Crainea raz...@opensips.org mailto:raz...@opensips.org wrote: Hi, Wesley! I see that your modparam contains the localhost ip, however, the OpenSIPS warning contains the ip_address. Is this ip_address 127.0.0.1? Because if it is not, then it means that the rtpproxy_sock is set to a
Re: [OpenSIPS-Users] RTP Proxy problem
Hi, The issue is with the command you are using to start RTPproxy. Missing a : between 127.0.0.1 and 7890. So now you may not see RTPproxy on netstat output. Regards, Sammy On Dec 1, 2012 12:30 AM, Răzvan Crainea raz...@opensips.org wrote: Hi, Wesley! Have you tried tracing the communication opensips has with rtpproxy (listen with ngrep on port 7890). Are you sure rtpproxy is bound on the correct IP and port (check with netstat -ulpn | grep rtpproxy). Have you tried enabling rtpproxy debugging to see if something reaches the server (start rtpproxy with -d DBUG). Regards, Razvan Crainea OpenSIPS Core Developerhttp://www.opensips-solutions.com On 11/30/2012 08:06 PM, Wesley Volcov wrote: Dear all, I've tried to downgrade the opensips version, and use the nathelper module, but I still see the error. RTPPROXY run command: /usr/local/bin/rtpproxy -l public_ip -s udp:127.0.0.1 7890 -F -m 1 -M 2 Opensips configuration: modparam(nathelper, rtpproxy_sock, udp: 127.0.0.1:7890) Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10695]: ERROR:nathelper:send_rtpp_command: can't send command to a RTP proxy Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10699]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10707]: ERROR:nathelper:send_rtpp_command: can't send command to a RTP proxy Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10679]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10682]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10678]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10684]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10686]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10687]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10690]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not respond, disable it Nov 30 17:05:25 localhost /usr/local/sbin/opensips[10691]: ERROR:nathelper:send_rtpp_command: proxy udp:127.0.0.1:7890 does not respond, disable it Am I missing some thing? Please, helpe me. Regards, Wesley Volcov On 29 November 2012 08:28, Wesley Volcov wesleyvol...@gmail.com wrote: Dear Răzvan, * * Thanks you for helping me! I changed the modparam to: modparam(rtpproxy, rtpproxy_sock, udp: 127.0.0.1:7890) And the rtpproxy run command: /usr/local/bin/rtpproxy -lpublic_ip -s udp:127.0.0.1 7890 -F -m 1 -M 2 And I still see this: Nov 29 08:25:42 opensips /usr/local/sbin/opensips[5996]: WARNING:rtpproxy:rtpp_test: support for RTP proxy udp:127.0.0.1:7890 has been disabled temporarily Nov 29 08:25:42 opensips /usr/local/sbin/opensips[5994]: WARNING:rtpproxy:rtpp_test: can't get version of the RTP proxy Any idea? Regards, Wesley Volcov On 28 November 2012 16:02, Răzvan Crainea raz...@opensips.org wrote: Hi, Wesley! The idea is that RTPProxy is listening only on localhost, whereas OpenSIPS tries to connect to a different IP (rather than 127.0.0.1). You should either allow RTPProxy to listen on that IP (change the -s parameter, but this is not recommended because of security issues) or configure OpenSIPS to connect using 127.0.0.1. Are you using the DB to provision the RTPProxy sockets? Because if you do, there is no need of the rtpproxy_sock modparam, you should change the IP directly in the database. Regards, Razvan Crainea OpenSIPS Core Developerhttp://www.opensips-solutions.com On 11/28/2012 05:53 PM, Wesley Volcov wrote: Dear Răzvan, * * I tried to change the modparam configuration, to the ip_addres, and also the rtpproxy listen addres to localhost, and it still the same problem. Regards, Wesley Volcov On 28 November 2012 12:31, Răzvan Crainea raz...@opensips.org wrote: Hi, Wesley! I see that your modparam contains the localhost ip, however, the OpenSIPS warning contains the ip_address. Is this ip_address 127.0.0.1? Because if it is not, then it means that the rtpproxy_sock is set to a different value - either by overwriting the parameter, or by using the DB provisioning mode. Most likely it doesn't work because OpenSIPS is trying to connect to rtpproxy on a public IP, whereas RTPProxy only listens on localhost. Regards, Razvan Crainea OpenSIPS Core Developerhttp://www.opensips-solutions.com On 11/28/2012 02:25 PM, Wesley Volcov wrote: Dear all, I'm
Re: [OpenSIPS-Users] RTP Proxy problem
Dear Răzvan, * * Thanks you for helping me! I changed the modparam to: modparam(rtpproxy, rtpproxy_sock, udp: 127.0.0.1:7890) And the rtpproxy run command: /usr/local/bin/rtpproxy -lpublic_ip -s udp:127.0.0.1 7890 -F -m 1 -M 2 And I still see this: Nov 29 08:25:42 opensips /usr/local/sbin/opensips[5996]: WARNING:rtpproxy:rtpp_test: support for RTP proxy udp:127.0.0.1:7890 has been disabled temporarily Nov 29 08:25:42 opensips /usr/local/sbin/opensips[5994]: WARNING:rtpproxy:rtpp_test: can't get version of the RTP proxy Any idea? Regards, Wesley Volcov On 28 November 2012 16:02, Răzvan Crainea raz...@opensips.org wrote: Hi, Wesley! The idea is that RTPProxy is listening only on localhost, whereas OpenSIPS tries to connect to a different IP (rather than 127.0.0.1). You should either allow RTPProxy to listen on that IP (change the -s parameter, but this is not recommended because of security issues) or configure OpenSIPS to connect using 127.0.0.1. Are you using the DB to provision the RTPProxy sockets? Because if you do, there is no need of the rtpproxy_sock modparam, you should change the IP directly in the database. Regards, Razvan Crainea OpenSIPS Core Developerhttp://www.opensips-solutions.com On 11/28/2012 05:53 PM, Wesley Volcov wrote: Dear Răzvan, * * I tried to change the modparam configuration, to the ip_addres, and also the rtpproxy listen addres to localhost, and it still the same problem. Regards, Wesley Volcov On 28 November 2012 12:31, Răzvan Crainea raz...@opensips.org wrote: Hi, Wesley! I see that your modparam contains the localhost ip, however, the OpenSIPS warning contains the ip_address. Is this ip_address 127.0.0.1? Because if it is not, then it means that the rtpproxy_sock is set to a different value - either by overwriting the parameter, or by using the DB provisioning mode. Most likely it doesn't work because OpenSIPS is trying to connect to rtpproxy on a public IP, whereas RTPProxy only listens on localhost. Regards, Razvan Crainea OpenSIPS Core Developerhttp://www.opensips-solutions.com On 11/28/2012 02:25 PM, Wesley Volcov wrote: Dear all, I'm having problems with my Opensips + RTP Proxy instalation. Opensips version: 1.7.2-notls RTP Proxy version: 1.2.1 Start RTP Proxy command: /usr/local/bin/rtpproxy -l ip_address -s udp:127.0.0.1 7890 127.0.0.1%207890 -F -m 1 -M 2 Opensips configuration for RTP Proxy: modparam(rtpproxy, rtpproxy_sock, udp:localhost:7890) When I start the Opensips service, it logs this message: Nov 28 10:56:10 opensips /usr/local/sbin/opensips[2687]: WARNING:rtpproxy:rtpp_test: can't get version of the RTP proxy Nov 28 10:56:10 opensips /usr/local/sbin/opensips[2687]: WARNING:rtpproxy:rtpp_test: support for RTP proxy udp:ip_address:7890 has been disabled temporarily What could it be? Please, help me! Regards -- Wesley Volcov Email: wesleyvol...@gmail.com Messenger: vol...@live.com Skype: wesley.volcov Mobile: +55 11 7999-7444 %2B55%2011%207999-7444 Website: http://volcov.blogspot.com ___ Users mailing listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Wesley Volcov Email: wesleyvol...@gmail.com Messenger: vol...@live.com Skype: wesley.volcov Mobile: +55 11 7999-7444 Website: http://volcov.blogspot.com ___ Users mailing listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Wesley Volcov Email: wesleyvol...@gmail.com Messenger: vol...@live.com Skype: wesley.volcov Mobile: +55 11 7999-7444 Website: http://volcov.blogspot.com ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] RTP Proxy problem
Dear all, I'm having problems with my Opensips + RTP Proxy instalation. Opensips version: 1.7.2-notls RTP Proxy version: 1.2.1 Start RTP Proxy command: /usr/local/bin/rtpproxy -l ip_address -s udp:127.0.0.1 7890 -F -m 1 -M 2 Opensips configuration for RTP Proxy: modparam(rtpproxy, rtpproxy_sock, udp:localhost:7890) When I start the Opensips service, it logs this message: Nov 28 10:56:10 opensips /usr/local/sbin/opensips[2687]: WARNING:rtpproxy:rtpp_test: can't get version of the RTP proxy Nov 28 10:56:10 opensips /usr/local/sbin/opensips[2687]: WARNING:rtpproxy:rtpp_test: support for RTP proxy udp:ip_address:7890 has been disabled temporarily What could it be? Please, help me! Regards -- Wesley Volcov Email: wesleyvol...@gmail.com Messenger: vol...@live.com Skype: wesley.volcov Mobile: +55 11 7999-7444 Website: http://volcov.blogspot.com ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] RTP Proxy problem
Hi, Wesley! I see that your modparam contains the localhost ip, however, the OpenSIPS warning contains the ip_address. Is this ip_address 127.0.0.1? Because if it is not, then it means that the rtpproxy_sock is set to a different value - either by overwriting the parameter, or by using the DB provisioning mode. Most likely it doesn't work because OpenSIPS is trying to connect to rtpproxy on a public IP, whereas RTPProxy only listens on localhost. Regards, Razvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 11/28/2012 02:25 PM, Wesley Volcov wrote: Dear all, I'm having problems with my Opensips + RTP Proxy instalation. Opensips version: 1.7.2-notls RTP Proxy version: 1.2.1 Start RTP Proxy command: /usr/local/bin/rtpproxy -l ip_address -s udp:127.0.0.1 7890 -F -m 1 -M 2 Opensips configuration for RTP Proxy: modparam(rtpproxy, rtpproxy_sock, udp:localhost:7890) When I start the Opensips service, it logs this message: Nov 28 10:56:10 opensips /usr/local/sbin/opensips[2687]: WARNING:rtpproxy:rtpp_test: can't get version of the RTP proxy Nov 28 10:56:10 opensips /usr/local/sbin/opensips[2687]: WARNING:rtpproxy:rtpp_test: support for RTP proxy udp:ip_address:7890 has been disabled temporarily What could it be? Please, help me! Regards -- Wesley Volcov Email: wesleyvol...@gmail.com mailto:wesleyvol...@gmail.com Messenger: vol...@live.com mailto:vol...@live.com Skype: wesley.volcov Mobile: +55 11 7999-7444 Website: http://volcov.blogspot.com ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] RTP Proxy problem
Dear Răzvan, * * I tried to change the modparam configuration, to the ip_addres, and also the rtpproxy listen addres to localhost, and it still the same problem. Regards, Wesley Volcov On 28 November 2012 12:31, Răzvan Crainea raz...@opensips.org wrote: Hi, Wesley! I see that your modparam contains the localhost ip, however, the OpenSIPS warning contains the ip_address. Is this ip_address 127.0.0.1? Because if it is not, then it means that the rtpproxy_sock is set to a different value - either by overwriting the parameter, or by using the DB provisioning mode. Most likely it doesn't work because OpenSIPS is trying to connect to rtpproxy on a public IP, whereas RTPProxy only listens on localhost. Regards, Razvan Crainea OpenSIPS Core Developerhttp://www.opensips-solutions.com On 11/28/2012 02:25 PM, Wesley Volcov wrote: Dear all, I'm having problems with my Opensips + RTP Proxy instalation. Opensips version: 1.7.2-notls RTP Proxy version: 1.2.1 Start RTP Proxy command: /usr/local/bin/rtpproxy -l ip_address -s udp:127.0.0.1 7890 -F -m 1 -M 2 Opensips configuration for RTP Proxy: modparam(rtpproxy, rtpproxy_sock, udp:localhost:7890) When I start the Opensips service, it logs this message: Nov 28 10:56:10 opensips /usr/local/sbin/opensips[2687]: WARNING:rtpproxy:rtpp_test: can't get version of the RTP proxy Nov 28 10:56:10 opensips /usr/local/sbin/opensips[2687]: WARNING:rtpproxy:rtpp_test: support for RTP proxy udp:ip_address:7890 has been disabled temporarily What could it be? Please, help me! Regards -- Wesley Volcov Email: wesleyvol...@gmail.com Messenger: vol...@live.com Skype: wesley.volcov Mobile: +55 11 7999-7444 Website: http://volcov.blogspot.com ___ Users mailing listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Wesley Volcov Email: wesleyvol...@gmail.com Messenger: vol...@live.com Skype: wesley.volcov Mobile: +55 11 7999-7444 Website: http://volcov.blogspot.com ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] RTP Proxy problem
Hi, Wesley! The idea is that RTPProxy is listening only on localhost, whereas OpenSIPS tries to connect to a different IP (rather than 127.0.0.1). You should either allow RTPProxy to listen on that IP (change the -s parameter, but this is not recommended because of security issues) or configure OpenSIPS to connect using 127.0.0.1. Are you using the DB to provision the RTPProxy sockets? Because if you do, there is no need of the rtpproxy_sock modparam, you should change the IP directly in the database. Regards, Razvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 11/28/2012 05:53 PM, Wesley Volcov wrote: Dear Răzvan, * * I tried to change the modparam configuration, to the ip_addres, and also the rtpproxy listen addres to localhost, and it still the same problem. Regards, Wesley Volcov On 28 November 2012 12:31, Răzvan Crainea raz...@opensips.org mailto:raz...@opensips.org wrote: Hi, Wesley! I see that your modparam contains the localhost ip, however, the OpenSIPS warning contains the ip_address. Is this ip_address 127.0.0.1? Because if it is not, then it means that the rtpproxy_sock is set to a different value - either by overwriting the parameter, or by using the DB provisioning mode. Most likely it doesn't work because OpenSIPS is trying to connect to rtpproxy on a public IP, whereas RTPProxy only listens on localhost. Regards, Razvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 11/28/2012 02:25 PM, Wesley Volcov wrote: Dear all, I'm having problems with my Opensips + RTP Proxy instalation. Opensips version: 1.7.2-notls RTP Proxy version: 1.2.1 Start RTP Proxy command: /usr/local/bin/rtpproxy -l ip_address -s udp:127.0.0.1 7890 tel:127.0.0.1%207890 -F -m 1 -M 2 Opensips configuration for RTP Proxy: modparam(rtpproxy, rtpproxy_sock, udp:localhost:7890) When I start the Opensips service, it logs this message: Nov 28 10:56:10 opensips /usr/local/sbin/opensips[2687]: WARNING:rtpproxy:rtpp_test: can't get version of the RTP proxy Nov 28 10:56:10 opensips /usr/local/sbin/opensips[2687]: WARNING:rtpproxy:rtpp_test: support for RTP proxy udp:ip_address:7890 has been disabled temporarily What could it be? Please, help me! Regards -- Wesley Volcov Email: wesleyvol...@gmail.com mailto:wesleyvol...@gmail.com Messenger: vol...@live.com mailto:vol...@live.com Skype: wesley.volcov Mobile: +55 11 7999-7444 tel:%2B55%2011%207999-7444 Website: http://volcov.blogspot.com ___ Users mailing list Users@lists.opensips.org mailto:Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org mailto:Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Wesley Volcov Email: wesleyvol...@gmail.com mailto:wesleyvol...@gmail.com Messenger: vol...@live.com mailto:vol...@live.com Skype: wesley.volcov Mobile: +55 11 7999-7444 Website: http://volcov.blogspot.com ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
