Hello, I have enabled RTP proxy on my machine (ec2 instance) by running the following script:
rtpproxy -F -l mypublicip -s udp:localhost:7722
but I keep getting this error. The phones ring but there is no audio:
3(4144) ERROR: rtpproxy [rtpproxy.c:2647]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy
can someone let me know what this error means?
Thank you, Arun
Hello,
On 7/1/13 5:48 PM, arun Jayaprakash wrote:
Hello, I have enabled RTP proxy on my machine (ec2 instance) by running the following script:
rtpproxy -F -l mypublicip -s udp:localhost:7722
but I keep getting this error. The phones ring but there is no audio:
3(4144) ERROR: rtpproxy [rtpproxy.c:2647]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy
can someone let me know what this error means?
you cannot get rtpproxy listening on the ec2 public ip, which does not exist on the network interface.
You will have to use a patched rtpproxy, that adds advertising address support. I had such patch for my own usage, now I polished it a bit and push it to github:
- https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0593d4b25...
Give it a try, hope I haven't broken it with last polishing, if does not work let me know.
You should be able to apply it to latest rtpproxy stable release. Once you compile and install, then run rtpproxy with:
rtpproxy -F -l localip -A publicip -s udp:localhost:7722
Cheers, Daniel
Hi Daniel, I get this error:
rtpproxy -F -l 10.164.62.166 -A 54.x.x.x -s udp:127.0.0.1:7722 rtpproxy: invalid option -- 'A' usage: rtpproxy [-2fvFiPa] [-l addr1[/addr2]] [-6 addr1[/addr2]] [-s path] [-t tos] [-r rdir [-S sdir]] [-T ttl] [-L nfiles] [-m port_min] [-M port_max] [-u uname[:gname]] [-n timeout_socket] [-d log_level[:log_facility]]
________________________________ From: Daniel-Constantin Mierla miconda@gmail.com To: arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 2:39 AM Subject: Re: [SR-Users] Issue with RTP proxy....
Hello,
On 7/1/13 5:48 PM, arun Jayaprakash wrote:
Hello, I have enabled RTP proxy on my machine (ec2 instance) by running the following script:
rtpproxy -F -l mypublicip -s udp:localhost:7722
but I keep getting this error. The phones ring but there is no audio:
3(4144) ERROR: rtpproxy [rtpproxy.c:2647]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy
can someone let me know what this error means?
you cannot get rtpproxy listening on the ec2 public ip, which does not exist on the network interface.
You will have to use a patched rtpproxy, that adds advertising address support. I had such patch for my own usage, now I polished it a bit and push it to github:
- https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0593d4b25...
Give it a try, hope I haven't broken it with last polishing, if does not work let me know.
You should be able to apply it to latest rtpproxy stable release. Once you compile and install, then run rtpproxy with:
rtpproxy -F -l localip -A publicip -s udp:localhost:7722
Cheers, Daniel
Hello,
have you re-installed rtpproxy from sources after applying the patch I provided the link to?
Cheers, Daniel
On 7/2/13 3:33 PM, arun Jayaprakash wrote:
Hi Daniel, I get this error:
rtpproxy -F -l 10.164.62.166 -A 54.x.x.x -s udp:127.0.0.1:7722 rtpproxy: invalid option -- 'A' usage: rtpproxy [-2fvFiPa] [-l addr1[/addr2]] [-6 addr1[/addr2]] [-s path] [-t tos] [-r rdir [-S sdir]] [-T ttl] [-L nfiles] [-m port_min] [-M port_max] [-u uname[:gname]] [-n timeout_socket] [-d log_level[:log_facility]]
*From:* Daniel-Constantin Mierla miconda@gmail.com *To:* arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org *Sent:* Tuesday, July 2, 2013 2:39 AM *Subject:* Re: [SR-Users] Issue with RTP proxy....
Hello,
On 7/1/13 5:48 PM, arun Jayaprakash wrote:
Hello, I have enabled RTP proxy on my machine (ec2 instance) by running the following script:
rtpproxy -F -l mypublicip -s udp:localhost:7722
but I keep getting this error. The phones ring but there is no audio:
3(4144) ERROR: rtpproxy [rtpproxy.c:2647]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy
can someone let me know what this error means?
you cannot get rtpproxy listening on the ec2 public ip, which does not exist on the network interface.
You will have to use a patched rtpproxy, that adds advertising address support. I had such patch for my own usage, now I polished it a bit and push it to github:
https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0593d4b25...
Give it a try, hope I haven't broken it with last polishing, if does not work let me know.
You should be able to apply it to latest rtpproxy stable release. Once you compile and install, then run rtpproxy with:
rtpproxy -F -l localip -A publicip -s udp:localhost:7722
Cheers, Daniel
-- Daniel-Constantin Mierla -http://www.asipto.com http://www.asipto.com/ http://twitter.com/#!/miconda http://twitter.com/#%21/miconda -http://www.linkedin.com/in/miconda
This is awesome... did it say which version of RTP Proxy or did I just not RTFM well enough?
Fred Posner | Team Forrest / LOD direct: 503-914-0999 | fax: 954-472-2896
On 07/02/2013 10:17 AM, Daniel-Constantin Mierla wrote:
Hello,
have you re-installed rtpproxy from sources after applying the patch I provided the link to?
Cheers, Daniel
On 7/2/13 3:33 PM, arun Jayaprakash wrote:
Hi Daniel, I get this error:
rtpproxy -F -l 10.164.62.166 -A 54.x.x.x -s udp:127.0.0.1:7722 rtpproxy: invalid option -- 'A' usage: rtpproxy [-2fvFiPa] [-l addr1[/addr2]] [-6 addr1[/addr2]] [-s path] [-t tos] [-r rdir [-S sdir]] [-T ttl] [-L nfiles] [-m port_min] [-M port_max] [-u uname[:gname]] [-n timeout_socket] [-d log_level[:log_facility]]
*From:* Daniel-Constantin Mierla miconda@gmail.com *To:* arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org *Sent:* Tuesday, July 2, 2013 2:39 AM *Subject:* Re: [SR-Users] Issue with RTP proxy....
Hello,
On 7/1/13 5:48 PM, arun Jayaprakash wrote:
Hello, I have enabled RTP proxy on my machine (ec2 instance) by running the following script:
rtpproxy -F -l mypublicip -s udp:localhost:7722
but I keep getting this error. The phones ring but there is no audio:
3(4144) ERROR: rtpproxy [rtpproxy.c:2647]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy
can someone let me know what this error means?
you cannot get rtpproxy listening on the ec2 public ip, which does not exist on the network interface.
You will have to use a patched rtpproxy, that adds advertising address support. I had such patch for my own usage, now I polished it a bit and push it to github:
https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0593d4b25...
Give it a try, hope I haven't broken it with last polishing, if does not work let me know.
You should be able to apply it to latest rtpproxy stable release. Once you compile and install, then run rtpproxy with:
rtpproxy -F -l localip -A publicip -s udp:localhost:7722
Cheers, Daniel
-- Daniel-Constantin Mierla -http://www.asipto.com http://www.asipto.com/ http://twitter.com/#!/miconda http://twitter.com/#%21/miconda -http://www.linkedin.com/in/miconda
-- Daniel-Constantin Mierla -http://www.asipto.com http://twitter.com/#!/miconda -http://www.linkedin.com/in/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Daniel,
I am confused, I thought that patch is not really needed?
On Ec2 you should be able to bind to the Local IP and then pass the External IP to rtp-manage.
Am I missing something here?
Should effectively be the same thing.
On 7/2/13 10:50 AM, Fred Posner wrote:
This is awesome... did it say which version of RTP Proxy or did I just not RTFM well enough?
Fred Posner | Team Forrest / LOD direct: 503-914-0999 | fax: 954-472-2896
On 07/02/2013 10:17 AM, Daniel-Constantin Mierla wrote:
Hello,
have you re-installed rtpproxy from sources after applying the patch I provided the link to?
Cheers, Daniel
On 7/2/13 3:33 PM, arun Jayaprakash wrote:
Hi Daniel, I get this error:
rtpproxy -F -l 10.164.62.166 -A 54.x.x.x -s udp:127.0.0.1:7722 rtpproxy: invalid option -- 'A' usage: rtpproxy [-2fvFiPa] [-l addr1[/addr2]] [-6 addr1[/addr2]] [-s path] [-t tos] [-r rdir [-S sdir]] [-T ttl] [-L nfiles] [-m port_min] [-M port_max] [-u uname[:gname]] [-n timeout_socket] [-d log_level[:log_facility]]
*From:* Daniel-Constantin Mierla miconda@gmail.com *To:* arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org *Sent:* Tuesday, July 2, 2013 2:39 AM *Subject:* Re: [SR-Users] Issue with RTP proxy....
Hello,
On 7/1/13 5:48 PM, arun Jayaprakash wrote:
Hello, I have enabled RTP proxy on my machine (ec2 instance) by running the following script:
rtpproxy -F -l mypublicip -s udp:localhost:7722
but I keep getting this error. The phones ring but there is no audio:
3(4144) ERROR: rtpproxy [rtpproxy.c:2647]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy
can someone let me know what this error means?
you cannot get rtpproxy listening on the ec2 public ip, which does not exist on the network interface.
You will have to use a patched rtpproxy, that adds advertising address support. I had such patch for my own usage, now I polished it a bit and push it to github:
https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0593d4b25...
Give it a try, hope I haven't broken it with last polishing, if does not work let me know.
You should be able to apply it to latest rtpproxy stable release. Once you compile and install, then run rtpproxy with:
rtpproxy -F -l localip -A publicip -s udp:localhost:7722
Cheers, Daniel
-- Daniel-Constantin Mierla -http://www.asipto.com http://www.asipto.com/ http://twitter.com/#!/miconda http://twitter.com/#%21/miconda -http://www.linkedin.com/in/miconda
-- Daniel-Constantin Mierla -http://www.asipto.com http://twitter.com/#!/miconda -http://www.linkedin.com/in/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On 7/2/13 5:11 PM, David | StyleFlare wrote:
Daniel,
I am confused, I thought that patch is not really needed?
Indeed, the patch is not really needed when you have a single instance of rtpproxy and know its public ip. But when you deal with many rtpproxies, then you cannot deal from config. Also, for bridging networks is not possible from config.
With the patch, the config of kamailio stays as usual all the time.
Cheers, Daniel
On Ec2 you should be able to bind to the Local IP and then pass the External IP to rtp-manage.
Am I missing something here?
Should effectively be the same thing.
On 7/2/13 10:50 AM, Fred Posner wrote:
This is awesome... did it say which version of RTP Proxy or did I just not RTFM well enough?
Fred Posner | Team Forrest / LOD direct: 503-914-0999 | fax: 954-472-2896
On 07/02/2013 10:17 AM, Daniel-Constantin Mierla wrote:
Hello,
have you re-installed rtpproxy from sources after applying the patch I provided the link to?
Cheers, Daniel
On 7/2/13 3:33 PM, arun Jayaprakash wrote:
Hi Daniel, I get this error:
rtpproxy -F -l 10.164.62.166 -A 54.x.x.x -s udp:127.0.0.1:7722 rtpproxy: invalid option -- 'A' usage: rtpproxy [-2fvFiPa] [-l addr1[/addr2]] [-6 addr1[/addr2]] [-s path] [-t tos] [-r rdir [-S sdir]] [-T ttl] [-L nfiles] [-m port_min] [-M port_max] [-u uname[:gname]] [-n timeout_socket] [-d log_level[:log_facility]]
*From:* Daniel-Constantin Mierla miconda@gmail.com *To:* arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org *Sent:* Tuesday, July 2, 2013 2:39 AM *Subject:* Re: [SR-Users] Issue with RTP proxy....
Hello,
On 7/1/13 5:48 PM, arun Jayaprakash wrote:
Hello, I have enabled RTP proxy on my machine (ec2 instance) by running the following script:
rtpproxy -F -l mypublicip -s udp:localhost:7722
but I keep getting this error. The phones ring but there is no audio:
3(4144) ERROR: rtpproxy [rtpproxy.c:2647]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy
can someone let me know what this error means?
you cannot get rtpproxy listening on the ec2 public ip, which does not exist on the network interface.
You will have to use a patched rtpproxy, that adds advertising address support. I had such patch for my own usage, now I polished it a bit and push it to github:
https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0593d4b25...
Give it a try, hope I haven't broken it with last polishing, if does not work let me know.
You should be able to apply it to latest rtpproxy stable release. Once you compile and install, then run rtpproxy with:
rtpproxy -F -l localip -A publicip -s udp:localhost:7722
Cheers, Daniel
-- Daniel-Constantin Mierla -http://www.asipto.com http://www.asipto.com/ http://twitter.com/#!/miconda http://twitter.com/#%21/miconda -http://www.linkedin.com/in/miconda
-- Daniel-Constantin Mierla -http://www.asipto.com http://twitter.com/#!/miconda -http://www.linkedin.com/in/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Daniel, so you are saying that the machine running RTP proxy should not be a natted one but should have its own public IP?
Thanks, Arun
________________________________ From: Daniel-Constantin Mierla miconda@gmail.com To: Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 10:53 AM Subject: Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 5:11 PM, David | StyleFlare wrote:
Daniel,
I am confused, I thought that patch is not really needed?
Indeed, the patch is not really needed when you have a single instance of rtpproxy and know its public ip. But when you deal with many rtpproxies, then you cannot deal from config. Also, for bridging networks is not possible from config.
With the patch, the config of kamailio stays as usual all the time.
Cheers, Daniel
On Ec2 you should be able to bind to the Local IP and then pass the External IP to rtp-manage.
Am I missing something here?
Should effectively be the same thing.
On 7/2/13 10:50 AM, Fred Posner wrote:
This is awesome... did it say which version of RTP Proxy or did I just not RTFM well enough?
Fred Posner | Team Forrest / LOD direct: 503-914-0999 | fax: 954-472-2896
On 07/02/2013 10:17 AM, Daniel-Constantin Mierla wrote:
Hello,
have you re-installed rtpproxy from sources after applying the patch I provided the link to?
Cheers, Daniel
On 7/2/13 3:33 PM, arun Jayaprakash wrote:
Hi Daniel, I get this error:
rtpproxy -F -l 10.164.62.166 -A 54.x.x.x -s udp:127.0.0.1:7722 rtpproxy: invalid option -- 'A' usage: rtpproxy [-2fvFiPa] [-l addr1[/addr2]] [-6 addr1[/addr2]] [-s path] [-t tos] [-r rdir [-S sdir]] [-T ttl] [-L nfiles] [-m port_min] [-M port_max] [-u uname[:gname]] [-n timeout_socket] [-d log_level[:log_facility]]
*From:* Daniel-Constantin Mierla miconda@gmail.com *To:* arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org *Sent:* Tuesday, July 2, 2013 2:39 AM *Subject:* Re: [SR-Users] Issue with RTP proxy....
Hello,
On 7/1/13 5:48 PM, arun Jayaprakash wrote:
Hello, I have enabled RTP proxy on my machine (ec2 instance) by running the following script:
rtpproxy -F -l mypublicip -s udp:localhost:7722
but I keep getting this error. The phones ring but there is no audio:
3(4144) ERROR: rtpproxy [rtpproxy.c:2647]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy
can someone let me know what this error means?
you cannot get rtpproxy listening on the ec2 public ip, which does not exist on the network interface.
You will have to use a patched rtpproxy, that adds advertising address support. I had such patch for my own usage, now I polished it a bit and push it to github:
https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0593d4b25...
Give it a try, hope I haven't broken it with last polishing, if does not work let me know.
You should be able to apply it to latest rtpproxy stable release. Once you compile and install, then run rtpproxy with:
rtpproxy -F -l localip -A publicip -s udp:localhost:7722
Cheers, Daniel
-- Daniel-Constantin Mierla -http://www.asipto.com http://www.asipto.com/ http://twitter.com/#!/miconda http://twitter.com/#%21/miconda -http://www.linkedin.com/in/miconda
-- Daniel-Constantin Mierla -http://www.asipto.com http://twitter.com/#!/miconda -http://www.linkedin.com/in/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
How else?
On Tuesday 02 July 2013 09:44:48 arun Jayaprakash wrote:
Daniel, so you are saying that the machine running RTP proxy should not be a natted one but should have its own public IP?
Thanks, Arun
From: Daniel-Constantin Mierla miconda@gmail.com To: Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 10:53 AM Subject: Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 5:11 PM, David | StyleFlare wrote:
Daniel,
I am confused, I thought that patch is not really needed?
Indeed, the patch is not really needed when you have a single instance of rtpproxy and know its public ip. But when you deal with many rtpproxies, then you cannot deal from config. Also, for bridging networks is not possible from config.
With the patch, the config of kamailio stays as usual all the time.
Cheers, Daniel
On Ec2 you should be able to bind to the Local IP and then pass the External IP to rtp-manage.
Am I missing something here?
Should effectively be the same thing.
On 7/2/13 10:50 AM, Fred Posner wrote:
This is awesome... did it say which version of RTP Proxy or did I just not RTFM well enough?
Fred Posner | Team Forrest / LOD direct: 503-914-0999 | fax: 954-472-2896
On 07/02/2013 10:17 AM, Daniel-Constantin Mierla wrote:
Hello,
have you re-installed rtpproxy from sources after applying the patch I provided the link to?
Cheers, Daniel
On 7/2/13 3:33 PM, arun Jayaprakash wrote:
Hi Daniel, I get this error:
rtpproxy -F -l 10.164.62.166 -A 54.x.x.x -s udp:127.0.0.1:7722 rtpproxy: invalid option -- 'A' usage: rtpproxy [-2fvFiPa] [-l addr1[/addr2]] [-6 addr1[/addr2]] [-s path]
[-t tos] [-r rdir [-S sdir]] [-T ttl] [-L nfiles] [-mport_min]
[-M port_max] [-u uname[:gname]] [-n timeout_socket] [-dlog_level[:log_facility]]
*From:* Daniel-Constantin Mierla miconda@gmail.com *To:* arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org *Sent:* Tuesday, July 2, 2013 2:39 AM *Subject:* Re: [SR-Users] Issue with RTP proxy....
Hello,
On 7/1/13 5:48 PM, arun Jayaprakash wrote:
Hello, I have enabled RTP proxy on my machine (ec2 instance) by running the following script:
rtpproxy -F -l mypublicip -s udp:localhost:7722
but I keep getting this error. The phones ring but there is no audio:
3(4144) ERROR: rtpproxy [rtpproxy.c:2647]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy
can someone let me know what this error means?
you cannot get rtpproxy listening on the ec2 public ip, which does not exist on the network interface.
You will have to use a patched rtpproxy, that adds advertising address support. I had such patch for my own usage, now I polished it a bit and push it to github:
https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0593 d4b25e0de8ca
Give it a try, hope I haven't broken it with last polishing, if does not work let me know.
You should be able to apply it to latest rtpproxy stable release. Once you compile and install, then run rtpproxy with:
rtpproxy -F -l localip -A publicip -s udp:localhost:7722
Cheers, Daniel
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Can you please give me some pointers as to how to apply this patch, I have never done one in the past. Thank you.
Regards, Arun
________________________________ From: Sergey Okhapkin sos@sokhapkin.dyndns.org To: arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 11:49 AM Subject: Re: [SR-Users] Issue with RTP proxy....
How else?
On Tuesday 02 July 2013 09:44:48 arun Jayaprakash wrote:
Daniel, so you are saying that the machine running RTP proxy should not be a natted one but should have its own public IP?
Thanks, Arun
From: Daniel-Constantin Mierla miconda@gmail.com To: Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 10:53 AM Subject: Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 5:11 PM, David | StyleFlare wrote:
Daniel,
I am confused, I thought that patch is not really needed?
Indeed, the patch is not really needed when you have a single instance of rtpproxy and know its public ip. But when you deal with many rtpproxies, then you cannot deal from config. Also, for bridging networks is not possible from config.
With the patch, the config of kamailio stays as usual all the time.
Cheers, Daniel
On Ec2 you should be able to bind to the Local IP and then pass the External IP to rtp-manage.
Am I missing something here?
Should effectively be the same thing.
On 7/2/13 10:50 AM, Fred Posner wrote:
This is awesome... did it say which version of RTP Proxy or did I just not RTFM well enough?
Fred Posner | Team Forrest / LOD direct: 503-914-0999 | fax: 954-472-2896
On 07/02/2013 10:17 AM, Daniel-Constantin Mierla wrote:
Hello,
have you re-installed rtpproxy from sources after applying the patch I provided the link to?
Cheers, Daniel
On 7/2/13 3:33 PM, arun Jayaprakash wrote:
Hi Daniel, I get this error:
rtpproxy -F -l 10.164.62.166 -A 54.x.x.x -s udp:127.0.0.1:7722 rtpproxy: invalid option -- 'A' usage: rtpproxy [-2fvFiPa] [-l addr1[/addr2]] [-6 addr1[/addr2]] [-s path]
[-t tos] [-r rdir [-S sdir]] [-T ttl] [-L nfiles] [-m
port_min]
[-M port_max] [-u uname[:gname]] [-n timeout_socket] [-d
log_level[:log_facility]]
*From:* Daniel-Constantin Mierla miconda@gmail.com *To:* arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org *Sent:* Tuesday, July 2, 2013 2:39 AM *Subject:* Re: [SR-Users] Issue with RTP proxy....
Hello,
On 7/1/13 5:48 PM, arun Jayaprakash wrote:
Hello, I have enabled RTP proxy on my machine (ec2 instance) by running the following script:
rtpproxy -F -l mypublicip -s udp:localhost:7722
but I keep getting this error. The phones ring but there is no audio:
3(4144) ERROR: rtpproxy [rtpproxy.c:2647]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy
can someone let me know what this error means?
you cannot get rtpproxy listening on the ec2 public ip, which does not exist on the network interface.
You will have to use a patched rtpproxy, that adds advertising address support. I had such patch for my own usage, now I polished it a bit and push it to github:
https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0593 d4b25e0de8ca
Give it a try, hope I haven't broken it with last polishing, if does not work let me know.
You should be able to apply it to latest rtpproxy stable release. Once you compile and install, then run rtpproxy with:
rtpproxy -F -l localip -A publicip -s udp:localhost:7722
Cheers, Daniel
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
RTPProxy can run on a natted (i.e., bridged mode) environment without any patches using rtpproxy_offer/answer("ie","IP") etc...
If you are on a public IP just use MediaProxy....
N.
Hi,
rtpproxy needs to bind to an IP that, as well, needs to be bound to a network interface. In case you are dealing with a Kamailio installation behind NAT, you have to instruct rtproxy to advertise an address (public IP) that it doesn't have locally. That's the reason the patch is needed.
Similarly, you have to tell to Kamailio to advertise that public address, reason why the advertised_address [1] and record_route_preset are needed.
[1] http://kamailio.org/dokuwiki/doku.php/core-cookbook:3.0.x#advertised_address [2] http://www.kamailio.org/docs/modules/3.1.x/modules_k/rr.html#id2667590
On Tue, Jul 2, 2013 at 1:05 PM, Nick Khamis symack@gmail.com wrote:
RTPProxy can run on a natted (i.e., bridged mode) environment without any patches using rtpproxy_offer/answer("ie","IP") etc...
If you are on a public IP just use MediaProxy....
N.
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hello,
your links are to old versions, but also mixed.
With latest stable version is easier just to use 'advertise' for listen parameters: - http://www.kamailio.org/wiki/cookbooks/4.0.x/core#listen
That's all, so there is no need for a complex config logic using advertised_address and preset record routing.
Cheers, Daniel
On 7/2/13 7:23 PM, Carlos Ruiz Díaz wrote:
Hi,
rtpproxy needs to bind to an IP that, as well, needs to be bound to a network interface. In case you are dealing with a Kamailio installation behind NAT, you have to instruct rtproxy to advertise an address (public IP) that it doesn't have locally. That's the reason the patch is needed.
Similarly, you have to tell to Kamailio to advertise that public address, reason why the advertised_address [1] and record_route_preset are needed.
[1] http://kamailio.org/dokuwiki/doku.php/core-cookbook:3.0.x#advertised_address [2] http://www.kamailio.org/docs/modules/3.1.x/modules_k/rr.html#id2667590
On Tue, Jul 2, 2013 at 1:05 PM, Nick Khamis <symack@gmail.com mailto:symack@gmail.com> wrote:
RTPProxy can run on a natted (i.e., bridged mode) environment without any patches using rtpproxy_offer/answer("ie","IP") etc... If you are on a public IP just use MediaProxy.... N. _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users-- Carlos http://caruizdiaz.com +595981146623
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On 7/2/13 7:05 PM, Nick Khamis wrote:
RTPProxy can run on a natted (i.e., bridged mode) environment without any patches using rtpproxy_offer/answer("ie","IP") etc...
If you are on a public IP just use MediaProxy....
RTPProxy runs well on the public address, being actually the most common use case, why is needed to use something else for such case?
Cheers, Daniel
Hi Daniel,
this is probably just me, but Google always messes around with the documentation from the early versions of Kamailio to the latest ones when searching. This could confuse the new comers.
Thanks for pointing me out to the right direction.
Carlos
On Tue, Jul 2, 2013 at 1:45 PM, Daniel-Constantin Mierla miconda@gmail.comwrote:
On 7/2/13 7:05 PM, Nick Khamis wrote:
RTPProxy can run on a natted (i.e., bridged mode) environment without any patches using rtpproxy_offer/answer("ie","**IP") etc...
If you are on a public IP just use MediaProxy....
RTPProxy runs well on the public address, being actually the most common use case, why is needed to use something else for such case?
Cheers, Daniel
-- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/**micondahttp://www.linkedin.com/in/miconda
______________________________**_________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**usershttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On 7/2/13 7:01 PM, arun Jayaprakash wrote:
Can you please give me some pointers as to how to apply this patch, I have never done one in the past. Thank you.
I guess you can find good tutorials online on how to use patch tool or understand patching mechanisms.
Or if it is ok, just take the whole rtpproxy sources from the githug repository and compile/install it.
Cheers, Daniel
Regards, Arun
*From:* Sergey Okhapkin sos@sokhapkin.dyndns.org *To:* arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org *Sent:* Tuesday, July 2, 2013 11:49 AM *Subject:* Re: [SR-Users] Issue with RTP proxy....
How else?
On Tuesday 02 July 2013 09:44:48 arun Jayaprakash wrote:
Daniel, so you are saying that the machine running RTP proxy should
not be a
natted one but should have its own public IP?
Thanks, Arun
From: Daniel-Constantin Mierla <miconda@gmail.com
To: Kamailio (SER) - Users Mailing List
<sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org>
Sent: Tuesday, July 2, 2013 10:53 AM Subject: Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 5:11 PM, David | StyleFlare wrote:
Daniel,
I am confused, I thought that patch is not really needed?
Indeed, the patch is not really needed when you have a single instance of rtpproxy and know its public ip. But when you deal with many rtpproxies, then you cannot deal from config. Also, for bridging networks is not possible from config.
With the patch, the config of kamailio stays as usual all the time.
Cheers, Daniel
On Ec2 you should be able to bind to the Local IP and then pass the External IP to rtp-manage.
Am I missing something here?
Should effectively be the same thing.
On 7/2/13 10:50 AM, Fred Posner wrote:
This is awesome... did it say which version of RTP Proxy or did I just not RTFM well enough?
Fred Posner | Team Forrest / LOD direct: 503-914-0999 | fax: 954-472-2896
On 07/02/2013 10:17 AM, Daniel-Constantin Mierla wrote:
Hello,
have you re-installed rtpproxy from sources after applying the
patch I
provided the link to?
Cheers, Daniel
On 7/2/13 3:33 PM, arun Jayaprakash wrote:
Hi Daniel, I get this error:
rtpproxy -F -l 10.164.62.166 -A 54.x.x.x -s udp:127.0.0.1:7722 rtpproxy: invalid option -- 'A' usage: rtpproxy [-2fvFiPa] [-l addr1[/addr2]] [-6 addr1[/addr2]] [-s path]
[-t tos] [-r rdir [-S sdir]] [-T ttl] [-L nfiles] [-mport_min]
[-M port_max] [-u uname[:gname]] [-n timeout_socket] [-dlog_level[:log_facility]]
*From:* Daniel-Constantin Mierla <miconda@gmail.com
*To:* arun Jayaprakash <jayaprakasharun@yahoo.com
mailto:jayaprakasharun@yahoo.com>; Kamailio (SER) -
Users Mailing List <sr-users@lists.sip-router.org
mailto:sr-users@lists.sip-router.org>
*Sent:* Tuesday, July 2, 2013 2:39 AM *Subject:* Re: [SR-Users] Issue with RTP proxy....
Hello,
On 7/1/13 5:48 PM, arun Jayaprakash wrote: > Hello, I have enabled RTP proxy on my machine (ec2 instance) by > running the following script: > > rtpproxy -F -l mypublicip -s udp:localhost:7722 > > but I keep getting this error. The phones ring but there is no
audio:
> > 3(4144) ERROR: rtpproxy [rtpproxy.c:2647]: force_rtp_proxy(): > incorrect port 0 in reply from rtp proxy > > can someone let me know what this error means?
you cannot get rtpproxy listening on the ec2 public ip, which
does not
exist on the network interface.
You will have to use a patched rtpproxy, that adds advertising
address
support. I had such patch for my own usage, now I polished it a bit and push it to github:
https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0593
d4b25e0de8ca
Give it a try, hope I haven't broken it with last polishing, if
does
not work let me know.
You should be able to apply it to latest rtpproxy stable
release. Once
you compile and install, then run rtpproxy with:
rtpproxy -F -l localip -A publicip -s udp:localhost:7722
Cheers, Daniel
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list
sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list
sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list
sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Daniel, I have installed the new version of rtpproxy from GIT. Now I am not getting any errors but I am not getting any audio at all ( not even one way). This is what I have for my modparameters:
modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722") modparam("nathelper", "force_socket", "udp:127.0.0.1:7722")
The output when I make a call is as follows:
acc [acc.c:275]: acc_log_request(): ACC: transaction answered: timestamp=1372791705;method=INVITE;from_tag=SGyhghw.6gAHM4JLDdkhhrNYln22JEYp;to_tag=77761ca6f0df43c1b16d09a958126e09;call_id=9wJWhSfXDQyPKe.h9ZeK38gdg5Yl4msl;code=200;reason=OK;src_user=1002;src_domain=54.x.x.36;src_ip=71.252.x.x;dst_ouser=1001;dst_user=38246571;dst_domain=192.168.1.15
Suggestions? Thanks.
Arun
________________________________ From: Daniel-Constantin Mierla miconda@gmail.com To: arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 12:41 PM Subject: Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 7:01 PM, arun Jayaprakash wrote:
Can you please give me some pointers as to how to apply this patch, I have never done one in the past. Thank you.
I guess you can find good tutorials online on how to use patch tool or understand patching mechanisms.
Or if it is ok, just take the whole rtpproxy sources from the githug repository and compile/install it.
Cheers, Daniel
Regards, Arun
From: Sergey Okhapkin sos@sokhapkin.dyndns.org To: arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 11:49 AM Subject: Re: [SR-Users] Issue with RTP proxy....
How else?
On Tuesday 02 July 2013 09:44:48 arun Jayaprakash wrote:
Daniel, so you are saying that the machine running
RTP proxy should not be a
natted one but should have its own public IP?
Thanks, Arun
From: Daniel-Constantin Mierla miconda@gmail.com To: Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 10:53 AM Subject: Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 5:11 PM, David | StyleFlare wrote:
Daniel,
I am confused, I thought that patch is not
really needed?
Indeed, the patch is not really needed when you have
a single instance
of rtpproxy and know its public ip. But when you deal
with many
rtpproxies, then you cannot deal from config. Also,
for bridging
networks is not possible from config.
With the patch, the config of kamailio stays as usual
all the time.
Cheers, Daniel
On Ec2 you should be able to bind to the Local
IP and then pass the
External IP to rtp-manage.
Am I missing something here?
Should effectively be the same thing.
On 7/2/13 10:50 AM, Fred Posner wrote:
This is awesome... did it say which version
of RTP Proxy or did I
just not RTFM well enough?
Fred Posner | Team Forrest / LOD direct: 503-914-0999 | fax: 954-472-2896
On 07/02/2013 10:17 AM, Daniel-Constantin
Mierla wrote:
Hello,
have you re-installed rtpproxy from
sources after applying the patch I
provided the link to?
Cheers, Daniel
On 7/2/13 3:33 PM, arun Jayaprakash
wrote:
Hi Daniel, I get this error:
rtpproxy -F -l 10.164.62.166 -A
54.x.x.x -s udp:127.0.0.1:7722
rtpproxy: invalid option -- 'A' usage: rtpproxy [-2fvFiPa] [-l
addr1[/addr2]] [-6 addr1[/addr2]]
[-s path]
[-t tos] [-r rdir [-S sdir]]
[-T ttl] [-L nfiles] [-m
port_min]
[-M port_max] [-u
uname[:gname]] [-n timeout_socket] [-d
log_level[:log_facility]]
-----------------------------------------------------------------------
*From:* Daniel-Constantin Mierla
*To:* arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org *Sent:* Tuesday, July 2, 2013 2:39
AM
*Subject:* Re: [SR-Users] Issue with
RTP proxy....
Hello,
On 7/1/13 5:48 PM, arun Jayaprakash
wrote:
> Hello, I have enabled RTP proxy
on my machine (ec2 instance) by
> running the following script: > > rtpproxy -F -l mypublicip -s udp:localhost:7722 > > but I keep getting this error.
The phones ring but there is no audio:
> > 3(4144) ERROR: rtpproxy
[rtpproxy.c:2647]: force_rtp_proxy():
> incorrect port 0 in reply from
rtp proxy
> > can someone let me know what
this error means?
you cannot get rtpproxy listening on
the ec2 public ip, which does not
exist on the network interface.
You will have to use a patched
rtpproxy, that adds advertising address
support. I had such patch for my own
usage, now I polished it a bit
and push it to github:
https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0593 d4b25e0de8ca
Give it a try, hope I haven't broken
it with last polishing, if does
not work let me know.
You should be able to apply it to
latest rtpproxy stable release. Once
you compile and install, then run
rtpproxy with:
rtpproxy -F -l localip -A publicip
-s udp:localhost:7722
Cheers, Daniel
_______________________________________________
SIP Express Router (SER) and Kamailio
(OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio
(OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER)
- sr-users mailing list
sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
...also
listen=udp:10.164.62.166:5060 advertise 54.235.xx.xx:5060
________________________________ From: Daniel-Constantin Mierla miconda@gmail.com To: arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 12:41 PM Subject: Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 7:01 PM, arun Jayaprakash wrote:
Can you please give me some pointers as to how to apply this patch, I have never done one in the past. Thank you.
I guess you can find good tutorials online on how to use patch tool or understand patching mechanisms.
Or if it is ok, just take the whole rtpproxy sources from the githug repository and compile/install it.
Cheers, Daniel
Regards, Arun
From: Sergey Okhapkin sos@sokhapkin.dyndns.org To: arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 11:49 AM Subject: Re: [SR-Users] Issue with RTP proxy....
How else?
On Tuesday 02 July 2013 09:44:48 arun Jayaprakash wrote:
Daniel, so you are saying that the machine running
RTP proxy should not be a
natted one but should have its own public IP?
Thanks, Arun
From: Daniel-Constantin Mierla miconda@gmail.com To: Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 10:53 AM Subject: Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 5:11 PM, David | StyleFlare wrote:
Daniel,
I am confused, I thought that patch is not
really needed?
Indeed, the patch is not really needed when you have
a single instance
of rtpproxy and know its public ip. But when you deal
with many
rtpproxies, then you cannot deal from config. Also,
for bridging
networks is not possible from config.
With the patch, the config of kamailio stays as usual
all the time.
Cheers, Daniel
On Ec2 you should be able to bind to the Local
IP and then pass the
External IP to rtp-manage.
Am I missing something here?
Should effectively be the same thing.
On 7/2/13 10:50 AM, Fred Posner wrote:
This is awesome... did it say which version
of RTP Proxy or did I
just not RTFM well enough?
Fred Posner | Team Forrest / LOD direct: 503-914-0999 | fax: 954-472-2896
On 07/02/2013 10:17 AM, Daniel-Constantin
Mierla wrote:
Hello,
have you re-installed rtpproxy from
sources after applying the patch I
provided the link to?
Cheers, Daniel
On 7/2/13 3:33 PM, arun Jayaprakash
wrote:
Hi Daniel, I get this error:
rtpproxy -F -l 10.164.62.166 -A
54.x.x.x -s udp:127.0.0.1:7722
rtpproxy: invalid option -- 'A' usage: rtpproxy [-2fvFiPa] [-l
addr1[/addr2]] [-6 addr1[/addr2]]
[-s path]
[-t tos] [-r rdir [-S sdir]]
[-T ttl] [-L nfiles] [-m
port_min]
[-M port_max] [-u
uname[:gname]] [-n timeout_socket] [-d
log_level[:log_facility]]
-----------------------------------------------------------------------
*From:* Daniel-Constantin Mierla
*To:* arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org *Sent:* Tuesday, July 2, 2013 2:39
AM
*Subject:* Re: [SR-Users] Issue with
RTP proxy....
Hello,
On 7/1/13 5:48 PM, arun Jayaprakash
wrote:
> Hello, I have enabled RTP proxy
on my machine (ec2 instance) by
> running the following script: > > rtpproxy -F -l mypublicip -s udp:localhost:7722 > > but I keep getting this error.
The phones ring but there is no audio:
> > 3(4144) ERROR: rtpproxy
[rtpproxy.c:2647]: force_rtp_proxy():
> incorrect port 0 in reply from
rtp proxy
> > can someone let me know what
this error means?
you cannot get rtpproxy listening on
the ec2 public ip, which does not
exist on the network interface.
You will have to use a patched
rtpproxy, that adds advertising address
support. I had such patch for my own
usage, now I polished it a bit
and push it to github:
https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0593 d4b25e0de8ca
Give it a try, hope I haven't broken
it with last polishing, if does
not work let me know.
You should be able to apply it to
latest rtpproxy stable release. Once
you compile and install, then run
rtpproxy with:
rtpproxy -F -l localip -A publicip
-s udp:localhost:7722
Cheers, Daniel
_______________________________________________
SIP Express Router (SER) and Kamailio
(OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio
(OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER)
- sr-users mailing list
sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
That might not work. Substituting of advertise IP address is not enough. NAT router could mangle IP port too.
Once again - RTP proxy must run on a public IP address. There are no workarounds.
On Tuesday 02 July 2013 12:16:40 arun Jayaprakash wrote:
...also
listen=udp:10.164.62.166:5060 advertise 54.235.xx.xx:5060
From: Daniel-Constantin Mierla miconda@gmail.com To: arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 12:41 PM Subject: Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 7:01 PM, arun Jayaprakash wrote:
Can you please give me some pointers as to how to apply this patch, I have never done one in the past. Thank you.
I guess you can find good tutorials online on how to use patch tool or understand patching mechanisms.
Or if it is ok, just take the whole rtpproxy sources from the githug repository and compile/install it.
Cheers, Daniel
Regards, Arun
From: Sergey Okhapkin sos@sokhapkin.dyndns.org
To: arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 11:49 AM Subject: Re: [SR-Users] Issue with RTP proxy....
How else?
On Tuesday 02 July 2013 09:44:48 arun Jayaprakash wrote:
Daniel, so you are saying that the machine running
RTP proxy should not be anatted one but should have its own public IP?
Thanks, Arun
From: Daniel-Constantin Mierla miconda@gmail.com
To: Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 10:53 AM Subject: Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 5:11 PM, David | StyleFlare wrote:
Daniel,
I am confused, I thought that patch is not
really needed?Indeed, the patch is not really needed when you have
a single instanceof rtpproxy and know its public ip. But when you deal
with manyrtpproxies, then you cannot deal from config. Also,
for bridgingnetworks is not possible from config.
With the patch, the config of kamailio stays as usual
all the time.Cheers, Daniel
On Ec2 you should be able to bind to the Local
IP and then pass theExternal IP to rtp-manage.
Am I missing something here?
Should effectively be the same thing.
On 7/2/13 10:50 AM, Fred Posner wrote:
This is awesome... did it say which version
of RTP Proxy or did Ijust not RTFM well enough?
Fred Posner | Team Forrest / LOD direct: 503-914-0999 | fax: 954-472-2896
On 07/02/2013 10:17 AM, Daniel-Constantin
Mierla wrote:Hello,
have you re-installed rtpproxy from
sources after applying the patch Iprovided the link to?
Cheers, Daniel
On 7/2/13 3:33 PM, arun Jayaprakash
wrote:> Hi Daniel, I get this error: > > rtpproxy -F -l 10.164.62.166 -A
54.x.x.x -s udp:127.0.0.1:7722> rtpproxy: invalid option -- 'A' > usage: rtpproxy [-2fvFiPa] [-l
addr1[/addr2]] [-6 addr1[/addr2]]> [-s path] > > [-t tos] [-r rdir [-S sdir]]
[-T ttl] [-L nfiles] [-m> port_min] > > [-M port_max] [-u
uname[:gname]] [-n timeout_socket] [-d> log_level[:log_facility]]
> - > > *From:* Daniel-Constantin Mierla
<miconda@gmail.com>> *To:* arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - > Users Mailing List sr-users@lists.sip-router.org > *Sent:* Tuesday, July 2, 2013 2:39
AM> *Subject:* Re: [SR-Users] Issue with
RTP proxy....> Hello, > > On 7/1/13 5:48 PM, arun Jayaprakash
wrote:>> Hello, I have enabled RTP proxy
on my machine (ec2 instance) by>> running the following script: >> >> rtpproxy -F -l mypublicip -s udp:localhost:7722 >> >> but I keep getting this error.
The phones ring but there is no audio:>> 3(4144) ERROR: rtpproxy
[rtpproxy.c:2647]: force_rtp_proxy():>> incorrect port 0 in reply from
rtp proxy>> can someone let me know what
this error means?> you cannot get rtpproxy listening on
the ec2 public ip, which does not> exist on the network interface. > > You will have to use a patched
rtpproxy, that adds advertising address> support. I had such patch for my own
usage, now I polished it a bit> and push it to github: > > - > https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0 > 593 > d4b25e0de8ca > > > Give it a try, hope I haven't broken
it with last polishing, if does> not work let me know. > > You should be able to apply it to
latest rtpproxy stable release. Once> you compile and install, then run
rtpproxy with:> rtpproxy -F -l localip -A publicip
-s udp:localhost:7722> Cheers, > Daniel
_______________________________________________SIP Express Router (SER) and Kamailio
(OpenSER) - sr-users mailing listsr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________SIP Express Router (SER) and Kamailio
(OpenSER) - sr-users mailing listsr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER)
- sr-users mailing listsr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Does that mean that Kamailio can not be installed on an ec2 instance ?
________________________________ From: Sergey Okhapkin sos@sokhapkin.dyndns.org To: arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 2:22 PM Subject: Re: [SR-Users] Issue with RTP proxy....
That might not work. Substituting of advertise IP address is not enough. NAT router could mangle IP port too.
Once again - RTP proxy must run on a public IP address. There are no workarounds.
On Tuesday 02 July 2013 12:16:40 arun Jayaprakash wrote:
...also
listen=udp:10.164.62.166:5060 advertise 54.235.xx.xx:5060
From: Daniel-Constantin Mierla miconda@gmail.com To: arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 12:41 PM Subject: Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 7:01 PM, arun Jayaprakash wrote:
Can you please give me some pointers as to how to apply this patch, I have never done one in the past. Thank you.
I guess you can find good tutorials online on how to use patch tool or understand patching mechanisms.
Or if it is ok, just take the whole rtpproxy sources from the githug repository and compile/install it.
Cheers, Daniel
Regards, Arun
From: Sergey Okhapkin sos@sokhapkin.dyndns.org
To: arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 11:49 AM Subject: Re: [SR-Users] Issue with RTP proxy....
How else?
On Tuesday 02 July 2013 09:44:48 arun Jayaprakash wrote:
Daniel, so you are saying that the machine running
RTP proxy should not be a
natted one but should have its own public IP?
Thanks, Arun
From: Daniel-Constantin Mierla miconda@gmail.com
To: Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 10:53 AM Subject: Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 5:11 PM, David | StyleFlare wrote:
Daniel,
I am confused, I thought that patch is not
really needed?
Indeed, the patch is not really needed when you have
a single instance
of rtpproxy and know its public ip. But when you deal
with many
rtpproxies, then you cannot deal from config. Also,
for bridging
networks is not possible from config.
With the patch, the config of kamailio stays as usual
all the time.
Cheers, Daniel
On Ec2 you should be able to bind to the Local
IP and then pass the
External IP to rtp-manage.
Am I missing something here?
Should effectively be the same thing.
On 7/2/13 10:50 AM, Fred Posner wrote:
This is awesome... did it say which version
of RTP Proxy or did I
just not RTFM well enough?
Fred Posner | Team Forrest / LOD direct: 503-914-0999 | fax: 954-472-2896
On 07/02/2013 10:17 AM, Daniel-Constantin
Mierla wrote:
Hello,
have you re-installed rtpproxy from
sources after applying the patch I
provided the link to?
Cheers, Daniel
On 7/2/13 3:33 PM, arun Jayaprakash
wrote:
> Hi Daniel, I get this error: > > rtpproxy -F -l 10.164.62.166 -A
54.x.x.x -s udp:127.0.0.1:7722
> rtpproxy: invalid option -- 'A' > usage: rtpproxy [-2fvFiPa] [-l
addr1[/addr2]] [-6 addr1[/addr2]]
> [-s path] > > [-t tos] [-r rdir [-S sdir]]
[-T ttl] [-L nfiles] [-m
> port_min] > > [-M port_max] [-u
uname[:gname]] [-n timeout_socket] [-d
> log_level[:log_facility]]
> - > > *From:* Daniel-Constantin Mierla
> *To:* arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - > Users Mailing List sr-users@lists.sip-router.org > *Sent:* Tuesday, July 2, 2013 2:39
AM
> *Subject:* Re: [SR-Users] Issue with
RTP proxy....
> Hello, > > On 7/1/13 5:48 PM, arun Jayaprakash
wrote:
>> Hello, I have enabled RTP proxy
on my machine (ec2 instance) by
>> running the following script: >> >> rtpproxy -F -l mypublicip -s udp:localhost:7722 >> >> but I keep getting this error.
The phones ring but there is no audio:
>> 3(4144) ERROR: rtpproxy
[rtpproxy.c:2647]: force_rtp_proxy():
>> incorrect port 0 in reply from
rtp proxy
>> can someone let me know what
this error means?
> you cannot get rtpproxy listening on
the ec2 public ip, which does not
> exist on the network interface. > > You will have to use a patched
rtpproxy, that adds advertising address
> support. I had such patch for my own
usage, now I polished it a bit
> and push it to github: > > - > https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0 > 593 > d4b25e0de8ca > > > Give it a try, hope I haven't broken
it with last polishing, if does
> not work let me know. > > You should be able to apply it to
latest rtpproxy stable release. Once
> you compile and install, then run
rtpproxy with:
> rtpproxy -F -l localip -A publicip
-s udp:localhost:7722
> Cheers, > Daniel
_______________________________________________
SIP Express Router (SER) and Kamailio
(OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio
(OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER)
- sr-users mailing list
sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Not true. I'm running RTP proxy behind NAT without problems.
On Tue, Jul 2, 2013 at 3:22 PM, Sergey Okhapkin sos@sokhapkin.dyndns.orgwrote:
That might not work. Substituting of advertise IP address is not enough. NAT router could mangle IP port too.
Once again - RTP proxy must run on a public IP address. There are no workarounds.
On Tuesday 02 July 2013 12:16:40 arun Jayaprakash wrote:
...also
listen=udp:10.164.62.166:5060 advertise 54.235.xx.xx:5060
From: Daniel-Constantin Mierla miconda@gmail.com To: arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 12:41 PM Subject: Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 7:01 PM, arun Jayaprakash wrote:
Can you please give me some pointers as to how to apply this patch, I
have
never done one in the past. Thank you.
I guess you can find good tutorials online on how to use patch tool or understand patching mechanisms.
Or if it is ok, just take the whole rtpproxy sources from the githug repository and compile/install it.
Cheers, Daniel
Regards, Arun
From: Sergey Okhapkin sos@sokhapkin.dyndns.org
To: arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) -
Users
Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2,
2013
11:49 AM Subject: Re: [SR-Users] Issue with RTP proxy....
How else?
On Tuesday 02 July 2013 09:44:48 arun Jayaprakash wrote:
Daniel, so you are saying that the machine running
RTP proxy should not be anatted one but should have its own public IP?
Thanks, Arun
From: Daniel-Constantin Mierla miconda@gmail.com
To: Kamailio (SER) - Users Mailing List <
sr-users@lists.sip-router.org>
Sent: Tuesday, July 2, 2013 10:53 AM Subject: Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 5:11 PM, David | StyleFlare wrote:
Daniel,
I am confused, I thought that patch is not
really needed?Indeed, the patch is not really needed when you have
a single instanceof rtpproxy and know its public ip. But when you deal
with manyrtpproxies, then you cannot deal from config. Also,
for bridgingnetworks is not possible from config.
With the patch, the config of kamailio stays as usual
all the time.Cheers, Daniel
On Ec2 you should be able to bind to the Local
IP and then pass theExternal IP to rtp-manage.
Am I missing something here?
Should effectively be the same thing.
On 7/2/13 10:50 AM, Fred Posner wrote:
This is awesome... did it say which version
of RTP Proxy or did Ijust not RTFM well enough?
Fred Posner | Team Forrest / LOD direct: 503-914-0999 | fax: 954-472-2896
On 07/02/2013 10:17 AM, Daniel-Constantin
Mierla wrote:> Hello, > > have you re-installed rtpproxy from
sources after applying the patch I> provided the link to? > > Cheers, > Daniel > > On 7/2/13 3:33 PM, arun Jayaprakash
wrote:>> Hi Daniel, I get this error: >> >> rtpproxy -F -l 10.164.62.166 -A
54.x.x.x -s udp:127.0.0.1:7722>> rtpproxy: invalid option -- 'A' >> usage: rtpproxy [-2fvFiPa] [-l
addr1[/addr2]] [-6 addr1[/addr2]]>> [-s path] >> >> [-t tos] [-r rdir [-S sdir]]
[-T ttl] [-L nfiles] [-m>> port_min] >> >> [-M port_max] [-u
uname[:gname]] [-n timeout_socket] [-d>> log_level[:log_facility]]
>> - >> >> *From:* Daniel-Constantin Mierla
<miconda@gmail.com>>> *To:* arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio
(SER) -
>> Users Mailing List sr-users@lists.sip-router.org >> *Sent:* Tuesday, July 2, 2013 2:39
AM>> *Subject:* Re: [SR-Users] Issue with
RTP proxy....>> Hello, >> >> On 7/1/13 5:48 PM, arun Jayaprakash
wrote:>>> Hello, I have enabled RTP proxy
on my machine (ec2 instance) by>>> running the following script: >>> >>> rtpproxy -F -l mypublicip -s udp:localhost:7722 >>> >>> but I keep getting this error.
The phones ring but there is no audio:>>> 3(4144) ERROR: rtpproxy
[rtpproxy.c:2647]: force_rtp_proxy():>>> incorrect port 0 in reply from
rtp proxy>>> can someone let me know what
this error means?>> you cannot get rtpproxy listening on
the ec2 public ip, which does not>> exist on the network interface. >> >> You will have to use a patched
rtpproxy, that adds advertising address>> support. I had such patch for my own
usage, now I polished it a bit>> and push it to github: >> >> - >>
https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0
>> 593 >> d4b25e0de8ca >> >> >> Give it a try, hope I haven't broken
it with last polishing, if does>> not work let me know. >> >> You should be able to apply it to
latest rtpproxy stable release. Once>> you compile and install, then run
rtpproxy with:>> rtpproxy -F -l localip -A publicip
-s udp:localhost:7722>> Cheers, >> Daniel
_______________________________________________> SIP Express Router (SER) and Kamailio
(OpenSER) - sr-users mailing list> sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________SIP Express Router (SER) and Kamailio
(OpenSER) - sr-users mailing listsr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER)
- sr-users mailing listsr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
That's what I thought, thanks.
________________________________ From: Carlos Ruiz Díaz carlos.ruizdiaz@gmail.com To: Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 2:40 PM Subject: Re: [SR-Users] Issue with RTP proxy....
Not true. I'm running RTP proxy behind NAT without problems.
On Tue, Jul 2, 2013 at 3:22 PM, Sergey Okhapkin sos@sokhapkin.dyndns.org wrote:
That might not work. Substituting of advertise IP address is not enough. NAT
router could mangle IP port too.
Once again - RTP proxy must run on a public IP address. There are no workarounds.
On Tuesday 02 July 2013 12:16:40 arun Jayaprakash wrote:
...also
listen=udp:10.164.62.166:5060 advertise 54.235.xx.xx:5060
From: Daniel-Constantin Mierla miconda@gmail.com To: arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 12:41 PM Subject: Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 7:01 PM, arun Jayaprakash wrote:
Can you please give me some pointers as to how to apply this patch, I have never done one in the past. Thank you.
I guess you can find good tutorials online on how to use patch tool or understand patching mechanisms.
Or if it is ok, just take the whole rtpproxy sources from the githug repository and compile/install it.
Cheers, Daniel
Regards, Arun
From: Sergey Okhapkin sos@sokhapkin.dyndns.org
To: arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 11:49 AM Subject: Re: [SR-Users] Issue with RTP proxy....
How else?
On Tuesday 02 July 2013 09:44:48 arun Jayaprakash wrote:
Daniel, so you are saying that the machine running
RTP proxy should not be a
natted one but should have its own public IP?
Thanks, Arun
From: Daniel-Constantin Mierla miconda@gmail.com
To: Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 10:53 AM Subject: Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 5:11 PM, David | StyleFlare wrote:
Daniel,
I am confused, I thought that patch is not
really needed?
Indeed, the patch is not really needed when you have
a single instance
of rtpproxy and know its public ip. But when you deal
with many
rtpproxies, then you cannot deal from config. Also,
for bridging
networks is not possible from config.
With the patch, the config of kamailio stays as usual
all the time.
Cheers, Daniel
On Ec2 you should be able to bind to the Local
IP and then pass the
External IP to rtp-manage.
Am I missing something here?
Should effectively be the same thing.
On 7/2/13 10:50 AM, Fred Posner wrote:
This is awesome... did it say which version
of RTP Proxy or did I
just not RTFM well enough?
Fred Posner | Team Forrest / LOD direct: 503-914-0999 | fax: 954-472-2896
On 07/02/2013 10:17 AM, Daniel-Constantin
Mierla wrote:
> Hello, > > have you re-installed rtpproxy from
sources after applying the patch I
> provided the link to? > > Cheers, > Daniel > > On 7/2/13 3:33 PM, arun Jayaprakash
wrote:
>> Hi Daniel, I get this error: >> >> rtpproxy -F -l 10.164.62.166 -A
54.x.x.x -s udp:127.0.0.1:7722
>> rtpproxy: invalid option -- 'A' >> usage: rtpproxy [-2fvFiPa] [-l
addr1[/addr2]] [-6 addr1[/addr2]]
>> [-s path] >> >> [-t tos] [-r rdir [-S sdir]]
[-T ttl] [-L nfiles] [-m
>> port_min] >> >> [-M port_max] [-u
uname[:gname]] [-n timeout_socket] [-d
>> log_level[:log_facility]]
>> - >> >> *From:* Daniel-Constantin Mierla
>> *To:* arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - >> Users Mailing List sr-users@lists.sip-router.org >> *Sent:* Tuesday, July 2, 2013 2:39
AM
>> *Subject:* Re: [SR-Users] Issue with
RTP proxy....
>> Hello, >> >> On 7/1/13 5:48 PM, arun Jayaprakash
wrote:
>>> Hello, I have enabled RTP proxy
on my machine (ec2 instance) by
>>> running the following script: >>> >>> rtpproxy -F -l mypublicip -s udp:localhost:7722 >>> >>> but I keep getting this error.
The phones ring but there is no audio:
>>> 3(4144) ERROR: rtpproxy
[rtpproxy.c:2647]: force_rtp_proxy():
>>> incorrect port 0 in reply from
rtp proxy
>>> can someone let me know what
this error means?
>> you cannot get rtpproxy listening on
the ec2 public ip, which does not
>> exist on the network interface. >> >> You will have to use a patched
rtpproxy, that adds advertising address
>> support. I had such patch for my own
usage, now I polished it a bit
>> and push it to github: >> >> - >> https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0 >> 593 >> d4b25e0de8ca >> >> >> Give it a try, hope I haven't broken
it with last polishing, if does
>> not work let me know. >> >> You should be able to apply it to
latest rtpproxy stable release. Once
>> you compile and install, then run
rtpproxy with:
>> rtpproxy -F -l localip -A publicip
-s udp:localhost:7722
>> Cheers, >> Daniel
_______________________________________________
> SIP Express Router (SER) and Kamailio
(OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio
(OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER)
- sr-users mailing list
sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
We've been using RTPProxy behing a Dlink router from hell for 2 years now (SIP ALG mangling and everything). No problems here....
PS Make sure your "C=", and RR are correct. If not, fix them with the proxy.
N.
This is how my sip capture looks. I am making a call from ext 1002 to 1004.
U 2013/07/02 21:13:32.876503 50.84.xxx.yyy:61472 -> 10.164.62.166:5060 SIP/2.0 180 Ringing. Via: SIP/2.0/UDP 54.235.xxx.xxx:5060;branch=z9hG4bKb0be.e57d8ce.0. Via: SIP/2.0/UDP 50.84.xxx.xxx:5065;rport=5065;branch=z9hG4bKPjgBwd-5iRFfSiG7l6NyTlOMaMK5YQIqpZ. Record-Route: sip:54.235.xxx.xxx;lr;nat=yes. Contact: sip:1004@172.10.17.88:61472;rinstance=d9e6974a58dc5882. To: sip:1004@54.235.xxx.xxx:5060;tag=1718096f. From: "1002"sip:1002@54.235.xxx.xxx:5060;tag=ryAGHAFEBqSFh3wr9OXhLqw4TuzvwfE5. Call-ID: yyVVgjCpXJdhzaMpBkVfbopF1UOtRPP-. CSeq: 4600 INVITE. User-Agent: 3CXPhone 6.0.26523.0. Content-Length: 0. .
U 2013/07/02 21:13:32.876798 10.164.62.166:5060 -> 50.84.xxx.xxx:5065 SIP/2.0 180 Ringing. Via: SIP/2.0/UDP 50.84.xxx.xxx:5065;rport=5065;branch=z9hG4bKPjgBwd-5iRFfSiG7l6NyTlOMaMK5YQIqpZ. Record-Route: sip:54.235.xxx.xxx;lr;nat=yes. Contact: sip:1004@172.10.17.88:61472;alias=50.84.xxx.yyy~61472~1;rinstance=d9e6974a58dc5882. To: sip:1004@54.235.xxx.xxx:5060;tag=1718096f. From: "1002"sip:1002@54.235.xxx.xxx:5060;tag=ryAGHAFEBqSFh3wr9OXhLqw4TuzvwfE5. Call-ID: yyVVgjCpXJdhzaMpBkVfbopF1UOtRPP-. CSeq: 4600 INVITE. User-Agent: 3CXPhone 6.0.26523.0. Content-Length: 0. .
U 2013/07/02 21:13:37.185706 50.84.xxx.yyy:61472 -> 10.164.62.166:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 54.235.xxx.xxx:5060;branch=z9hG4bKb0be.e57d8ce.0. Via: SIP/2.0/UDP 50.84.xxx.xxx:5065;rport=5065;branch=z9hG4bKPjgBwd-5iRFfSiG7l6NyTlOMaMK5YQIqpZ. Record-Route: sip:54.235.xxx.xxx;lr;nat=yes. Contact: sip:1004@172.10.17.88:61472;rinstance=d9e6974a58dc5882. To: sip:1004@54.235.xxx.xxx:5060;tag=1718096f. From: "1002"sip:1002@54.235.xxx.xxx:5060;tag=ryAGHAFEBqSFh3wr9OXhLqw4TuzvwfE5. Call-ID: yyVVgjCpXJdhzaMpBkVfbopF1UOtRPP-. CSeq: 4600 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE. Content-Type: application/sdp. Supported: replaces. User-Agent: 3CXPhone 6.0.26523.0. Content-Length: 256. . v=0. o=3cxVCE 201458055 127227570 IN IP4 172.10.17.88. s=3cxVCE Audio Call. c=IN IP4 172.10.17.88. t=0 0. m=audio 40024 RTP/AVP 3 8 0 101. a=rtpmap:3 GSM/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:0 PCMU/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15.
2(10205) NOTICE: acc [acc.c:275]: acc_log_request(): ACC: transaction answered: timestamp=1372799617;method=INVITE;from_tag=ryAGHAFEBqSFh3wr9OXhLqw4TuzvwfE5;to_tag=1718096f;call_id=yyVVgjCpXJdhzaMpBkVfbopF1UOtRPP-;code=200;reason=OK;src_user=1002;src_domain=54.235.xxx.xxx;src_ip=50.84.xxx.xxx;dst_ouser=1004;dst_user=1004;dst_domain=172.10.17.88
U 2013/07/02 21:13:37.196544 10.164.62.166:5060 -> 50.84.xxx.xxx:5065 SIP/2.0 200 OK. Via: SIP/2.0/UDP 50.84.xxx.xxx:5065;rport=5065;branch=z9hG4bKPjgBwd-5iRFfSiG7l6NyTlOMaMK5YQIqpZ. Record-Route: sip:54.235.xxx.xxx;lr;nat=yes. Contact: sip:1004@172.10.17.88:61472;alias=50.84.xxx.yyy~61472~1;rinstance=d9e6974a58dc5882. To: sip:1004@54.235.xxx.xxx:5060;tag=1718096f. From: "1002"sip:1002@54.235.xxx.xxx:5060;tag=ryAGHAFEBqSFh3wr9OXhLqw4TuzvwfE5. Call-ID: yyVVgjCpXJdhzaMpBkVfbopF1UOtRPP-. CSeq: 4600 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE. Content-Type: application/sdp. Supported: replaces. User-Agent: 3CXPhone 6.0.26523.0. Content-Length: 276. . v=0. o=3cxVCE 201458055 127227570 IN IP4 54.235.xxx.xxx. s=3cxVCE Audio Call. c=IN IP4 54.235.xxx.xxx. t=0 0. m=audio 47210 RTP/AVP 3 8 0 101. a=rtpmap:3 GSM/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:0 PCMU/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=nortpproxy:yes.
U 2013/07/02 21:13:37.437809 50.84.xxx.xxx:5065 -> 10.164.62.166:5060 ACK sip:1004@172.10.17.88:61472;alias=50.84.xxx.yyy~61472~1;rinstance=d9e6974a58dc5882 SIP/2.0. Via: SIP/2.0/UDP 50.84.xxx.xxx:5065;rport;branch=z9hG4bKPj7uuAnd60VwkAO19guEfMd-r5rtuCV1xN. Max-Forwards: 70. From: "1002" sip:1002@54.235.xxx.xxx:5060;tag=ryAGHAFEBqSFh3wr9OXhLqw4TuzvwfE5. To: sip:1004@54.235.xxx.xxx:5060;tag=1718096f. Call-ID: yyVVgjCpXJdhzaMpBkVfbopF1UOtRPP-. CSeq: 4600 ACK. Route: sip:54.235.xxx.xxx;lr;nat=yes. Content-Length: 0. .
U 2013/07/02 21:13:37.438072 10.164.62.166:5060 -> 50.84.xxx.yyy:61472 ACK sip:1004@172.10.17.88:61472;rinstance=d9e6974a58dc5882 SIP/2.0. Via: SIP/2.0/UDP 54.235.xxx.xxx:5060;branch=z9hG4bKcydzigwkX. Via: SIP/2.0/UDP 50.84.xxx.xxx:5065;rport=5065;branch=z9hG4bKPj7uuAnd60VwkAO19guEfMd-r5rtuCV1xN. Max-Forwards: 16. From: "1002" sip:1002@54.235.xxx.xxx:5060;tag=ryAGHAFEBqSFh3wr9OXhLqw4TuzvwfE5. To: sip:1004@54.235.xxx.xxx:5060;tag=1718096f. Call-ID: yyVVgjCpXJdhzaMpBkVfbopF1UOtRPP-. CSeq: 4600 ACK. Content-Length: 0. .
U 2013/07/02 21:13:38.157996 50.84.xxx.yyy:61472 -> 10.164.62.166:5060 BYE sip:1002@50.84.xxx.xxx:5065;ob SIP/2.0. Via: SIP/2.0/UDP 172.10.17.88:61472;branch=z9hG4bK-d8754z-8d614214534e5b28-1---d8754z-;rport. Max-Forwards: 70. Route: sip:54.235.xxx.xxx;lr;nat=yes. Contact: sip:1004@172.10.17.88:61472;rinstance=d9e6974a58dc5882. To: "1002"sip:1002@54.235.xxx.xxx:5060;tag=ryAGHAFEBqSFh3wr9OXhLqw4TuzvwfE5. From: sip:1004@54.235.xxx.xxx:5060;tag=1718096f. Call-ID: yyVVgjCpXJdhzaMpBkVfbopF1UOtRPP-. CSeq: 2 BYE. User-Agent: 3CXPhone 6.0.26523.0. Reason: SIP;description="User Hung Up". Content-Length: 0. .
U 2013/07/02 21:13:38.169148 10.164.62.166:5060 -> 50.84.xxx.xxx:5065 BYE sip:1002@50.84.xxx.xxx:5065;ob SIP/2.0. Via: SIP/2.0/UDP 54.235.xxx.xxx:5060;branch=z9hG4bKefa.00cd6586.0. Via: SIP/2.0/UDP 172.10.17.88:61472;received=50.84.xxx.yyy;branch=z9hG4bK-d8754z-8d614214534e5b28-1---d8754z-;rport=61472. Max-Forwards: 16. Contact: sip:1004@172.10.17.88:61472;alias=50.84.xxx.yyy~61472~1;rinstance=d9e6974a58dc5882. To: "1002"sip:1002@54.235.xxx.xxx:5060;tag=ryAGHAFEBqSFh3wr9OXhLqw4TuzvwfE5. From: sip:1004@54.235.xxx.xxx:5060;tag=1718096f. Call-ID: yyVVgjCpXJdhzaMpBkVfbopF1UOtRPP-. CSeq: 2 BYE. User-Agent: 3CXPhone 6.0.26523.0. Reason: SIP;description="User Hung Up". Content-Length: 0. .
3(10206) NOTICE: acc [acc.c:275]: acc_log_request(): ACC: transaction answered: timestamp=1372799618;method=BYE;from_tag=1718096f;to_tag=ryAGHAFEBqSFh3wr9OXhLqw4TuzvwfE5;call_id=yyVVgjCpXJdhzaMpBkVfbopF1UOtRPP-;code=200;reason=OK;src_user=1004;src_domain=54.235.xxx.xxx;src_ip=50.84.xxx.yyy;dst_ouser=1002;dst_user=1002;dst_domain=50.84.xxx.xxx
U 2013/07/02 21:13:38.302085 50.84.xxx.xxx:5065 -> 10.164.62.166:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 54.235.xxx.xxx:5060;received=54.235.xxx.xxx;branch=z9hG4bKefa.00cd6586.0. Via: SIP/2.0/UDP 172.10.17.88:61472;rport=61472;received=50.84.xxx.yyy;branch=z9hG4bK-d8754z-8d614214534e5b28-1---d8754z-. Call-ID: yyVVgjCpXJdhzaMpBkVfbopF1UOtRPP-. From: sip:1004@54.235.xxx.xxx:5060;tag=1718096f. To: "1002" sip:1002@54.235.xxx.xxx:5060;tag=ryAGHAFEBqSFh3wr9OXhLqw4TuzvwfE5. CSeq: 2 BYE. Content-Length: 0. .
U 2013/07/02 21:13:38.302275 10.164.62.166:5060 -> 50.84.xxx.yyy:61472 SIP/2.0 200 OK. Via: SIP/2.0/UDP 172.10.17.88:61472;rport=61472;received=50.84.xxx.yyy;branch=z9hG4bK-d8754z-8d614214534e5b28-1---d8754z-. Call-ID: yyVVgjCpXJdhzaMpBkVfbopF1UOtRPP-. From: sip:1004@54.235.xxx.xxx:5060;tag=1718096f. To: "1002" sip:1002@54.235.xxx.xxx:5060;tag=ryAGHAFEBqSFh3wr9OXhLqw4TuzvwfE5. CSeq: 2 BYE. Content-Length: 0.
________________________________ From: Nick Khamis symack@gmail.com To: arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 3:03 PM Subject: Re: [SR-Users] Issue with RTP proxy....
We've been using RTPProxy behing a Dlink router from hell for 2 years now (SIP ALG mangling and everything). No problems here....
PS Make sure your "C=", and RR are correct. If not, fix them with the proxy.
N.
On 7/2/13 6:44 PM, arun Jayaprakash wrote:
Daniel, so you are saying that the machine running RTP proxy should not be a natted one but should have its own public IP?
RTP proxy can run on a natted system such as ec2, but i can listen only on local ip, not on the public one. The advertised address is used to build the sdp, not listen on it.
Cheers, Daniel
Thanks, Arun
*From:* Daniel-Constantin Mierla miconda@gmail.com *To:* Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org *Sent:* Tuesday, July 2, 2013 10:53 AM *Subject:* Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 5:11 PM, David | StyleFlare wrote:
Daniel,
I am confused, I thought that patch is not really needed?
Indeed, the patch is not really needed when you have a single instance of rtpproxy and know its public ip. But when you deal with many rtpproxies, then you cannot deal from config. Also, for bridging networks is not possible from config.
With the patch, the config of kamailio stays as usual all the time.
Cheers, Daniel
On Ec2 you should be able to bind to the Local IP and then pass the External IP to rtp-manage.
Am I missing something here?
Should effectively be the same thing.
On 7/2/13 10:50 AM, Fred Posner wrote:
This is awesome... did it say which version of RTP Proxy or did I just not RTFM well enough?
Fred Posner | Team Forrest / LOD direct: 503-914-0999 | fax: 954-472-2896
On 07/02/2013 10:17 AM, Daniel-Constantin Mierla wrote:
Hello,
have you re-installed rtpproxy from sources after applying the patch I provided the link to?
Cheers, Daniel
On 7/2/13 3:33 PM, arun Jayaprakash wrote:
Hi Daniel, I get this error:
rtpproxy -F -l 10.164.62.166 -A 54.x.x.x -s udp:127.0.0.1:7722 rtpproxy: invalid option -- 'A' usage: rtpproxy [-2fvFiPa] [-l addr1[/addr2]] [-6 addr1[/addr2]] [-s path] [-t tos] [-r rdir [-S sdir]] [-T ttl] [-L nfiles] [-m port_min] [-M port_max] [-u uname[:gname]] [-n timeout_socket] [-d log_level[:log_facility]]
*From:* Daniel-Constantin Mierla <miconda@gmail.com
*To:* arun Jayaprakash <jayaprakasharun@yahoo.com
mailto:jayaprakasharun@yahoo.com>; Kamailio (SER) -
Users Mailing List <sr-users@lists.sip-router.org
mailto:sr-users@lists.sip-router.org>
*Sent:* Tuesday, July 2, 2013 2:39 AM *Subject:* Re: [SR-Users] Issue with RTP proxy....
Hello,
On 7/1/13 5:48 PM, arun Jayaprakash wrote:
Hello, I have enabled RTP proxy on my machine (ec2 instance) by running the following script:
rtpproxy -F -l mypublicip -s udp:localhost:7722
but I keep getting this error. The phones ring but there is no
audio:
3(4144) ERROR: rtpproxy [rtpproxy.c:2647]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy
can someone let me know what this error means?
you cannot get rtpproxy listening on the ec2 public ip, which
does not
exist on the network interface.
You will have to use a patched rtpproxy, that adds advertising
address
support. I had such patch for my own usage, now I polished it a bit and push it to github:
https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0593d4b25...
Give it a try, hope I haven't broken it with last polishing, if does not work let me know.
You should be able to apply it to latest rtpproxy stable release.
Once
you compile and install, then run rtpproxy with:
rtpproxy -F -l localip -A publicip -s udp:localhost:7722
Cheers, Daniel
-- Daniel-Constantin Mierla -http://www.asipto.com http://www.asipto.com/ http://twitter.com/#!/miconda
http://twitter.com/#%21/micondahttp://twitter.com/#%21/miconda
-- Daniel-Constantin Mierla -http://www.asipto.com http://twitter.com/#!/miconda
http://twitter.com/#%21/miconda-http://www.linkedin.com/in/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list
sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla - http://www.asipto.com http://www.asipto.com/ http://twitter.com/#!/miconda http://twitter.com/#%21/miconda- http://www.linkedin.com/in/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi,
you can also check the RTPProxy replacement from Sipwise:
- https://github.com/sipwise/mediaproxy-ng
It supports working behind NAT with advertised IPs. I've used it on Amazon EC2 myself.
Kind regards, Carsten
2013/7/2 Daniel-Constantin Mierla miconda@gmail.com:
On 7/2/13 6:44 PM, arun Jayaprakash wrote:
Daniel, so you are saying that the machine running RTP proxy should not be a natted one but should have its own public IP?
RTP proxy can run on a natted system such as ec2, but i can listen only on local ip, not on the public one. The advertised address is used to build the sdp, not listen on it.
Cheers, Daniel
Thanks, Arun
From: Daniel-Constantin Mierla miconda@gmail.com To: Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 10:53 AM Subject: Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 5:11 PM, David | StyleFlare wrote:
Daniel,
I am confused, I thought that patch is not really needed?
Indeed, the patch is not really needed when you have a single instance of rtpproxy and know its public ip. But when you deal with many rtpproxies, then you cannot deal from config. Also, for bridging networks is not possible from config.
With the patch, the config of kamailio stays as usual all the time.
Cheers, Daniel
On Ec2 you should be able to bind to the Local IP and then pass the External IP to rtp-manage.
Am I missing something here?
Should effectively be the same thing.
On 7/2/13 10:50 AM, Fred Posner wrote:
This is awesome... did it say which version of RTP Proxy or did I just not RTFM well enough?
Fred Posner | Team Forrest / LOD direct: 503-914-0999 | fax: 954-472-2896
On 07/02/2013 10:17 AM, Daniel-Constantin Mierla wrote:
Hello,
have you re-installed rtpproxy from sources after applying the patch I provided the link to?
Cheers, Daniel
On 7/2/13 3:33 PM, arun Jayaprakash wrote:
Hi Daniel, I get this error:
rtpproxy -F -l 10.164.62.166 -A 54.x.x.x -s udp:127.0.0.1:7722 rtpproxy: invalid option -- 'A' usage: rtpproxy [-2fvFiPa] [-l addr1[/addr2]] [-6 addr1[/addr2]] [-s path] [-t tos] [-r rdir [-S sdir]] [-T ttl] [-L nfiles] [-m port_min] [-M port_max] [-u uname[:gname]] [-n timeout_socket] [-d log_level[:log_facility]]
*From:* Daniel-Constantin Mierla miconda@gmail.com *To:* arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org *Sent:* Tuesday, July 2, 2013 2:39 AM *Subject:* Re: [SR-Users] Issue with RTP proxy....
Hello,
On 7/1/13 5:48 PM, arun Jayaprakash wrote:
Hello, I have enabled RTP proxy on my machine (ec2 instance) by running the following script:
rtpproxy -F -l mypublicip -s udp:localhost:7722
but I keep getting this error. The phones ring but there is no audio:
3(4144) ERROR: rtpproxy [rtpproxy.c:2647]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy
can someone let me know what this error means?
you cannot get rtpproxy listening on the ec2 public ip, which does not exist on the network interface.
You will have to use a patched rtpproxy, that adds advertising address support. I had such patch for my own usage, now I polished it a bit and push it to github:
https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0593d4b25...
Give it a try, hope I haven't broken it with last polishing, if does not work let me know.
You should be able to apply it to latest rtpproxy stable release. Once you compile and install, then run rtpproxy with:
rtpproxy -F -l localip -A publicip -s udp:localhost:7722
Cheers, Daniel
-- Daniel-Constantin Mierla -http://www.asipto.com http://www.asipto.com/ http://twitter.com/#!/miconda http://twitter.com/#%21/miconda -http://www.linkedin.com/in/miconda
-- Daniel-Constantin Mierla -http://www.asipto.com http://twitter.com/#!/miconda -http://www.linkedin.com/in/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Carsten, will I need to remove previously installed version of RTP proxy before installing this version?
Arun
________________________________ From: Carsten Bock carsten@ng-voice.com To: Daniel-Constantin Mierla miconda@gmail.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Cc: arun Jayaprakash jayaprakasharun@yahoo.com Sent: Tuesday, July 2, 2013 12:41 PM Subject: Re: [SR-Users] Issue with RTP proxy....
Hi,
you can also check the RTPProxy replacement from Sipwise:
- https://github.com/sipwise/mediaproxy-ng
It supports working behind NAT with advertised IPs. I've used it on Amazon EC2 myself.
Kind regards, Carsten
2013/7/2 Daniel-Constantin Mierla miconda@gmail.com:
On 7/2/13 6:44 PM, arun Jayaprakash wrote:
Daniel, so you are saying that the machine running RTP proxy should not be a natted one but should have its own public IP?
RTP proxy can run on a natted system such as ec2, but i can listen only on local ip, not on the public one. The advertised address is used to build the sdp, not listen on it.
Cheers, Daniel
Thanks, Arun
From: Daniel-Constantin Mierla miconda@gmail.com To: Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 10:53 AM Subject: Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 5:11 PM, David | StyleFlare wrote:
Daniel,
I am confused, I thought that patch is not really needed?
Indeed, the patch is not really needed when you have a single instance of rtpproxy and know its public ip. But when you deal with many rtpproxies, then you cannot deal from config. Also, for bridging networks is not possible from config.
With the patch, the config of kamailio stays as usual all the time.
Cheers, Daniel
On Ec2 you should be able to bind to the Local IP and then pass the External IP to rtp-manage.
Am I missing something here?
Should effectively be the same thing.
On 7/2/13 10:50 AM, Fred Posner wrote:
This is awesome... did it say which version of RTP Proxy or did I just not RTFM well enough?
Fred Posner | Team Forrest / LOD direct: 503-914-0999 | fax: 954-472-2896
On 07/02/2013 10:17 AM, Daniel-Constantin Mierla wrote:
Hello,
have you re-installed rtpproxy from sources after applying the patch I provided the link to?
Cheers, Daniel
On 7/2/13 3:33 PM, arun Jayaprakash wrote:
Hi Daniel, I get this error:
rtpproxy -F -l 10.164.62.166 -A 54.x.x.x -s udp:127.0.0.1:7722 rtpproxy: invalid option -- 'A' usage: rtpproxy [-2fvFiPa] [-l addr1[/addr2]] [-6 addr1[/addr2]] [-s path] [-t tos] [-r rdir [-S sdir]] [-T ttl] [-L nfiles] [-m port_min] [-M port_max] [-u uname[:gname]] [-n timeout_socket] [-d log_level[:log_facility]]
*From:* Daniel-Constantin Mierla miconda@gmail.com *To:* arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org *Sent:* Tuesday, July 2, 2013 2:39 AM *Subject:* Re: [SR-Users] Issue with RTP proxy....
Hello,
On 7/1/13 5:48 PM, arun Jayaprakash wrote:
Hello, I have enabled RTP proxy on my machine (ec2 instance) by running the following script:
rtpproxy -F -l mypublicip -s udp:localhost:7722
but I keep getting this error. The phones ring but there is no audio:
3(4144) ERROR: rtpproxy [rtpproxy.c:2647]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy
can someone let me know what this error means?
you cannot get rtpproxy listening on the ec2 public ip, which does not exist on the network interface.
You will have to use a patched rtpproxy, that adds advertising address support. I had such patch for my own usage, now I polished it a bit and push it to github:
https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0593d4b25...
Give it a try, hope I haven't broken it with last polishing, if does not work let me know.
You should be able to apply it to latest rtpproxy stable release. Once you compile and install, then run rtpproxy with:
rtpproxy -F -l localip -A publicip -s udp:localhost:7722
Cheers, Daniel
-- Daniel-Constantin Mierla -http://www.asipto.com http://www.asipto.com/ http://twitter.com/#!/miconda http://twitter.com/#%21/miconda -http://www.linkedin.com/in/miconda
-- Daniel-Constantin Mierla -http://www.asipto.com http://twitter.com/#!/miconda -http://www.linkedin.com/in/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Daniel, thank you, I have got it to work on my ec2 instance. I had to open more UDP ports ( opened from 35000 to 65000) and that enabled two way voice communication. Thanks again.
Regards, Arun
________________________________ From: Daniel-Constantin Mierla miconda@gmail.com To: arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 12:39 PM Subject: Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 6:44 PM, arun Jayaprakash wrote:
Daniel, so you are saying that the machine running RTP proxy should not be a natted one but should have its own public IP?
RTP proxy can run on a natted system such as ec2, but i can listen only on local ip, not on the public one. The advertised address is used to build the sdp, not listen on it.
Cheers, Daniel
Thanks, Arun
From: Daniel-Constantin Mierla miconda@gmail.com To: Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, July 2, 2013 10:53 AM Subject: Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 5:11 PM, David | StyleFlare wrote:
Daniel,
I am confused, I thought that patch is not really
needed?
Indeed, the patch is not really needed when you have a
single instance
of rtpproxy and know its public ip. But when you deal with
many
rtpproxies, then you cannot deal from config. Also, for
bridging
networks is not possible from config.
With the patch, the config of kamailio stays as usual all
the time.
Cheers, Daniel
On Ec2 you should be able to bind to the Local IP and
then pass the
External IP to rtp-manage.
Am I missing something here?
Should effectively be the same thing.
On 7/2/13 10:50 AM, Fred Posner wrote:
This is awesome... did it say which version of
RTP Proxy or did I
just not RTFM well enough?
Fred Posner | Team Forrest / LOD direct: 503-914-0999 | fax: 954-472-2896
On 07/02/2013 10:17 AM, Daniel-Constantin Mierla
wrote:
Hello,
have you re-installed rtpproxy from sources
after applying the patch I
provided the link to?
Cheers, Daniel
On 7/2/13 3:33 PM, arun Jayaprakash wrote:
Hi Daniel, I get this error:
rtpproxy -F -l 10.164.62.166 -A 54.x.x.x
-s udp:127.0.0.1:7722
rtpproxy: invalid option -- 'A' usage: rtpproxy [-2fvFiPa] [-l
addr1[/addr2]] [-6 addr1[/addr2]]
[-s path] [-t tos] [-r rdir [-S sdir]] [-T
ttl] [-L nfiles] [-m
port_min] [-M port_max] [-u uname[:gname]]
[-n timeout_socket] [-d
log_level[:log_facility]]
------------------------------------------------------------------------
*From:* Daniel-Constantin Mierla miconda@gmail.com *To:* arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org *Sent:* Tuesday, July 2, 2013 2:39 AM *Subject:* Re: [SR-Users] Issue with RTP
proxy....
Hello,
On 7/1/13 5:48 PM, arun Jayaprakash
wrote:
Hello, I have enabled RTP proxy on my
machine (ec2 instance) by
running the following script:
rtpproxy -F -l mypublicip -s udp:localhost:7722
but I keep getting this error. The
phones ring but there is no audio:
3(4144) ERROR: rtpproxy
[rtpproxy.c:2647]: force_rtp_proxy():
incorrect port 0 in reply from rtp
proxy
can someone let me know what this
error means?
you cannot get rtpproxy listening on the
ec2 public ip, which does not
exist on the network interface.
You will have to use a patched rtpproxy,
that adds advertising address
support. I had such patch for my own
usage, now I polished it a bit
and push it to github:
https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0593d4b25...
Give it a try, hope I haven't broken it
with last polishing, if does
not work let me know.
You should be able to apply it to latest
rtpproxy stable release. Once
you compile and install, then run
rtpproxy with:
rtpproxy -F -l localip -A publicip -s udp:localhost:7722
Cheers, Daniel
-- Daniel-Constantin Mierla
http://www.asipto.com/ http://twitter.com/#!/miconda http://twitter.com/#%21/miconda -http://www.linkedin.com/in/miconda
-- Daniel-Constantin Mierla
http://twitter.com/#!/miconda -http://www.linkedin.com/in/miconda
_______________________________________________
SIP Express Router (SER) and Kamailio
(OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) -
sr-users mailing list
sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) -
sr-users mailing list
sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list
sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi all,
I am trying install module mediaproxy-ng, but, when I built module "kernel-module" I got error: make -C /lib/modules/2.6.32-279.22.1.el6.x86_64/build M=/usr/local/src/mediaproxy_ngcp/mediaproxy-ng-master/kernel-module O=/lib/modules/2.6.32-279.22.1.el6.x86_64/build modules make: *** /lib/modules/2.6.32-279.22.1.el6.x86_64/build: No such file or directory. Stop. make: *** [modules] Error 2
Modules "daemon" and "iptables-extension" built success. How I can fix it.
Brs, Khue Nguyen.
2013/7/3 arun Jayaprakash jayaprakasharun@yahoo.com
Daniel, thank you, I have got it to work on my ec2 instance. I had to open more UDP ports ( opened from 35000 to 65000) and that enabled two way voice communication. Thanks again.
Regards, Arun
*From:* Daniel-Constantin Mierla miconda@gmail.com *To:* arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org *Sent:* Tuesday, July 2, 2013 12:39 PM
*Subject:* Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 6:44 PM, arun Jayaprakash wrote:
Daniel, so you are saying that the machine running RTP proxy should not be a natted one but should have its own public IP?
RTP proxy can run on a natted system such as ec2, but i can listen only on local ip, not on the public one. The advertised address is used to build the sdp, not listen on it.
Cheers, Daniel
Thanks, Arun
*From:* Daniel-Constantin Mierla miconda@gmail.com miconda@gmail.com *To:* Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.orgsr-users@lists.sip-router.org *Sent:* Tuesday, July 2, 2013 10:53 AM *Subject:* Re: [SR-Users] Issue with RTP proxy....
On 7/2/13 5:11 PM, David | StyleFlare wrote:
Daniel,
I am confused, I thought that patch is not really needed?
Indeed, the patch is not really needed when you have a single instance of rtpproxy and know its public ip. But when you deal with many rtpproxies, then you cannot deal from config. Also, for bridging networks is not possible from config.
With the patch, the config of kamailio stays as usual all the time.
Cheers, Daniel
On Ec2 you should be able to bind to the Local IP and then pass the External IP to rtp-manage.
Am I missing something here?
Should effectively be the same thing.
On 7/2/13 10:50 AM, Fred Posner wrote:
This is awesome... did it say which version of RTP Proxy or did I just not RTFM well enough?
Fred Posner | Team Forrest / LOD direct: 503-914-0999 | fax: 954-472-2896
On 07/02/2013 10:17 AM, Daniel-Constantin Mierla wrote:
Hello,
have you re-installed rtpproxy from sources after applying the patch I provided the link to?
Cheers, Daniel
On 7/2/13 3:33 PM, arun Jayaprakash wrote:
Hi Daniel, I get this error:
rtpproxy -F -l 10.164.62.166 -A 54.x.x.x -s udp:127.0.0.1:7722 rtpproxy: invalid option -- 'A' usage: rtpproxy [-2fvFiPa] [-l addr1[/addr2]] [-6 addr1[/addr2]] [-s path] [-t tos] [-r rdir [-S sdir]] [-T ttl] [-L nfiles] [-m port_min] [-M port_max] [-u uname[:gname]] [-n timeout_socket] [-d log_level[:log_facility]]
*From:* Daniel-Constantin Mierla miconda@gmail.com *To:* arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org *Sent:* Tuesday, July 2, 2013 2:39 AM *Subject:* Re: [SR-Users] Issue with RTP proxy....
Hello,
On 7/1/13 5:48 PM, arun Jayaprakash wrote:
Hello, I have enabled RTP proxy on my machine (ec2 instance) by running the following script:
rtpproxy -F -l mypublicip -s udp:localhost:7722
but I keep getting this error. The phones ring but there is no audio:
3(4144) ERROR: rtpproxy [rtpproxy.c:2647]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy
can someone let me know what this error means?
you cannot get rtpproxy listening on the ec2 public ip, which does not exist on the network interface.
You will have to use a patched rtpproxy, that adds advertising address support. I had such patch for my own usage, now I polished it a bit and push it to github:
https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0593d4b25...
Give it a try, hope I haven't broken it with last polishing, if does not work let me know.
You should be able to apply it to latest rtpproxy stable release. Once you compile and install, then run rtpproxy with:
rtpproxy -F -l localip -A publicip -s udp:localhost:7722
Cheers, Daniel
-- Daniel-Constantin Mierla -http://www.asipto.com http://www.asipto.com/ http://twitter.com/#!/miconda http://twitter.com/#%21/miconda -http://www.linkedin.com/in/miconda
-- Daniel-Constantin Mierla -http://www.asipto.com http://twitter.com/#!/miconda -http://www.linkedin.com/in/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi,
On 07/04/2013 09:00 AM, Khue Nguyen Minh wrote:
I am trying install module mediaproxy-ng, but, when I built module "kernel-module" I got error: make -C /lib/modules/2.6.32-279.22.1.el6.x86_64/build M=/usr/local/src/mediaproxy_ngcp/mediaproxy-ng-master/kernel-module O=/lib/modules/2.6.32-279.22.1.el6.x86_64/build modules make: *** /lib/modules/2.6.32-279.22.1.el6.x86_64/build: No such file or directory. Stop. make: *** [modules] Error 2
Modules "daemon" and "iptables-extension" built success. How I can fix it.
You're missing the kernel headers. Having the kernel module is optional (as the daemon falls back to userspace-only mode if it fails to load the kernel module), but it's highly recommended for performance reasons.
Andreas
Hi Andreas,
I' using rtpproxy and I can hear voice but quality is not good. After I changed to mediaproxy-ng, I don't hear anything. I use same config with rtpproxy. Do you guide change config to mediaproxy-ng?
Brs,
2013/7/4 Andreas Granig agranig@sipwise.com
Hi,
On 07/04/2013 09:00 AM, Khue Nguyen Minh wrote:
I am trying install module mediaproxy-ng, but, when I built module "kernel-module" I got error: make -C /lib/modules/2.6.32-279.22.1.**el6.x86_64/build M=/usr/local/src/mediaproxy_**ngcp/mediaproxy-ng-master/**kernel-module O=/lib/modules/2.6.32-279.22.**1.el6.x86_64/build modules make: *** /lib/modules/2.6.32-279.22.1.**el6.x86_64/build: No such file or directory. Stop. make: *** [modules] Error 2
Modules "daemon" and "iptables-extension" built success. How I can fix it.
You're missing the kernel headers. Having the kernel module is optional (as the daemon falls back to userspace-only mode if it fails to load the kernel module), but it's highly recommended for performance reasons.
Andreas
______________________________**_________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**usershttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On 07/04/13 05:21, Khue Nguyen Minh wrote:
Hi Andreas,
I' using rtpproxy and I can hear voice but quality is not good. After I changed to mediaproxy-ng, I don't hear anything. I use same config with rtpproxy. Do you guide change config to mediaproxy-ng?
They're mostly compatible, just make sure you launch mediaproxy-ng with the right options, specifically --listen-udp with the right listening port (I believe the default for the rtpproxy module is 22222) and --ip and --advertised-ip with your address details.
Otherwise, please watch your logs for any helpful information.
cheers
On 7/2/13 4:50 PM, Fred Posner wrote:
This is awesome... did it say which version of RTP Proxy or did I just not RTFM well enough?
The patch on github is to latest git version of rtpproxy (I cloned the git rtpproxy repository from sourceforge to my github).
But it can be easily extracted and applied to the latest stable, iirc that's 1.2.1. It's how I have it running on several deployments (this one is a bit polished, though).
Cheers, Daniel
Fred Posner | Team Forrest / LOD direct: 503-914-0999 | fax: 954-472-2896
On 07/02/2013 10:17 AM, Daniel-Constantin Mierla wrote:
Hello,
have you re-installed rtpproxy from sources after applying the patch I provided the link to?
Cheers, Daniel
On 7/2/13 3:33 PM, arun Jayaprakash wrote:
Hi Daniel, I get this error:
rtpproxy -F -l 10.164.62.166 -A 54.x.x.x -s udp:127.0.0.1:7722 rtpproxy: invalid option -- 'A' usage: rtpproxy [-2fvFiPa] [-l addr1[/addr2]] [-6 addr1[/addr2]] [-s path] [-t tos] [-r rdir [-S sdir]] [-T ttl] [-L nfiles] [-m port_min] [-M port_max] [-u uname[:gname]] [-n timeout_socket] [-d log_level[:log_facility]]
*From:* Daniel-Constantin Mierla miconda@gmail.com *To:* arun Jayaprakash jayaprakasharun@yahoo.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org *Sent:* Tuesday, July 2, 2013 2:39 AM *Subject:* Re: [SR-Users] Issue with RTP proxy....
Hello,
On 7/1/13 5:48 PM, arun Jayaprakash wrote:
Hello, I have enabled RTP proxy on my machine (ec2 instance) by running the following script:
rtpproxy -F -l mypublicip -s udp:localhost:7722
but I keep getting this error. The phones ring but there is no audio:
3(4144) ERROR: rtpproxy [rtpproxy.c:2647]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy
can someone let me know what this error means?
you cannot get rtpproxy listening on the ec2 public ip, which does not exist on the network interface.
You will have to use a patched rtpproxy, that adds advertising address support. I had such patch for my own usage, now I polished it a bit and push it to github:
https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0593d4b25...
Give it a try, hope I haven't broken it with last polishing, if does not work let me know.
You should be able to apply it to latest rtpproxy stable release. Once you compile and install, then run rtpproxy with:
rtpproxy -F -l localip -A publicip -s udp:localhost:7722
Cheers, Daniel
-- Daniel-Constantin Mierla -http://www.asipto.com http://www.asipto.com/ http://twitter.com/#!/miconda http://twitter.com/#%21/miconda -http://www.linkedin.com/in/miconda
-- Daniel-Constantin Mierla -http://www.asipto.com http://twitter.com/#!/miconda -http://www.linkedin.com/in/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-
Andreas Granig -
arun Jayaprakash -
Carlos Ruiz Díaz -
Carsten Bock -
Daniel-Constantin Mierla -
David | StyleFlare -
Fred Posner -
Khue Nguyen Minh -
Nick Khamis -
Richard Fuchs -
Sergey Okhapkin