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 <mico...@gmail.com>
To: arun Jayaprakash <jayaprakasha...@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/41f6d9d9084a6fad52a6483a0593d4b25e0de8ca
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://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
