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/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://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