<div dir="ltr">Not true. I'm running RTP proxy behind NAT without problems.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 2, 2013 at 3:22 PM, Sergey Okhapkin <span dir="ltr"><<a href="mailto:sos@sokhapkin.dyndns.org" target="_blank">sos@sokhapkin.dyndns.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">That might not work. Substituting of advertise IP address is not enough. NAT<br>
router could mangle IP port too.<br>
<br>
Once again - RTP proxy must run on a public IP address. There are no<br>
workarounds.<br>
<div class="HOEnZb"><div class="h5"><br>
On Tuesday 02 July 2013 12:16:40 arun Jayaprakash wrote:<br>
> ...also<br>
><br>
> listen=udp:<a href="http://10.164.62.166:5060" target="_blank">10.164.62.166:5060</a> advertise 54.235.xx.xx:5060<br>
><br>
><br>
><br>
> ________________________________<br>
> From: Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>><br>
> To: arun Jayaprakash <<a href="mailto:jayaprakasharun@yahoo.com">jayaprakasharun@yahoo.com</a>>; Kamailio (SER) - Users<br>
> Mailing List <<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>> Sent: Tuesday, July 2, 2013<br>
> 12:41 PM<br>
> Subject: Re: [SR-Users] Issue with RTP proxy....<br>
><br>
><br>
><br>
><br>
><br>
> On 7/2/13 7:01 PM, arun Jayaprakash wrote:<br>
><br>
> Can you please give me some pointers as to how to apply this patch, I have<br>
> never done one in the past. Thank you.<br>
><br>
> I guess you can find good tutorials online on how to use patch tool or<br>
> understand patching mechanisms.<br>
><br>
> Or if it is ok, just take the whole rtpproxy sources from the githug<br>
> repository and compile/install it.<br>
><br>
> Cheers,<br>
> Daniel<br>
><br>
> >Regards,<br>
> >Arun<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> >________________________________<br>
> ><br>
> > From: Sergey Okhapkin <<a href="mailto:sos@sokhapkin.dyndns.org">sos@sokhapkin.dyndns.org</a>><br>
> ><br>
> >To: arun Jayaprakash <<a href="mailto:jayaprakasharun@yahoo.com">jayaprakasharun@yahoo.com</a>>; Kamailio (SER) - Users<br>
> >Mailing List <<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>> Sent: Tuesday, July 2, 2013<br>
> >11:49 AM<br>
> >Subject: Re: [SR-Users] Issue with RTP proxy....<br>
> ><br>
> ><br>
> >How else?<br>
> ><br>
> >On Tuesday 02 July 2013 09:44:48 arun Jayaprakash wrote:<br>
> >> Daniel, so you are saying that the machine running<br>
><br>
> RTP proxy should not be a<br>
><br>
> >> natted one but should have its own public IP?<br>
> >><br>
> >> Thanks,<br>
> >> Arun<br>
> >><br>
> >><br>
> >><br>
> >><br>
> >> ________________________________<br>
> >><br>
> >> From: Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>><br>
> >><br>
> >> To: Kamailio (SER) - Users Mailing List <<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>><br>
> >> Sent: Tuesday, July 2, 2013 10:53 AM<br>
> >> Subject: Re: [SR-Users] Issue with RTP proxy....<br>
> >><br>
> >> On 7/2/13 5:11 PM, David | StyleFlare wrote:<br>
> >> > Daniel,<br>
> >> ><br>
> >> > I am confused, I thought that patch is not<br>
><br>
> really needed?<br>
><br>
> >> Indeed, the patch is not really needed when you have<br>
><br>
> a single instance<br>
><br>
> >> of rtpproxy and know its public ip. But when you deal<br>
><br>
> with many<br>
><br>
> >> rtpproxies, then you cannot deal from config. Also,<br>
><br>
> for bridging<br>
><br>
> >> networks is not possible from config.<br>
> >><br>
> >> With the patch, the config of kamailio stays as usual<br>
><br>
> all the time.<br>
><br>
> >> Cheers,<br>
> >> Daniel<br>
> >><br>
> >> > On Ec2 you should be able to bind to the Local<br>
><br>
> IP and then pass the<br>
><br>
> >> > External IP to rtp-manage.<br>
> >> ><br>
> >> > Am I missing something here?<br>
> >> ><br>
> >> > Should effectively be the same thing.<br>
> >> ><br>
> >> > On 7/2/13 10:50 AM, Fred Posner wrote:<br>
> >> >> This is awesome... did it say which version<br>
><br>
> of RTP Proxy or did I<br>
><br>
> >> >> just not RTFM well enough?<br>
> >> >><br>
> >> >> Fred Posner | Team Forrest / LOD<br>
> >> >> direct: 503-914-0999 | fax: 954-472-2896<br>
> >> >><br>
> >> >> On 07/02/2013 10:17 AM, Daniel-Constantin<br>
><br>
> Mierla wrote:<br>
> >> >>> Hello,<br>
> >> >>><br>
> >> >>> have you re-installed rtpproxy from<br>
><br>
> sources after applying the patch I<br>
><br>
> >> >>> provided the link to?<br>
> >> >>><br>
> >> >>> Cheers,<br>
> >> >>> Daniel<br>
> >> >>><br>
> >> >>> On 7/2/13 3:33 PM, arun Jayaprakash<br>
><br>
> wrote:<br>
> >> >>>> Hi Daniel, I get this error:<br>
> >> >>>><br>
> >> >>>> rtpproxy -F -l 10.164.62.166 -A<br>
><br>
> 54.x.x.x -s udp:<a href="http://127.0.0.1:7722" target="_blank">127.0.0.1:7722</a><br>
><br>
> >> >>>> rtpproxy: invalid option -- 'A'<br>
> >> >>>> usage: rtpproxy [-2fvFiPa] [-l<br>
><br>
> addr1[/addr2]] [-6 addr1[/addr2]]<br>
><br>
> >> >>>> [-s path]<br>
> >> >>>><br>
> >> >>>> [-t tos] [-r rdir [-S sdir]]<br>
><br>
> [-T ttl] [-L nfiles] [-m<br>
><br>
> >> >>>> port_min]<br>
> >> >>>><br>
> >> >>>> [-M port_max] [-u<br>
><br>
> uname[:gname]] [-n timeout_socket] [-d<br>
><br>
> >> >>>> log_level[:log_facility]]<br>
><br>
><br>
> -----------------------------------------------------------------------<br>
> >> >>>> -<br>
> >> >>>><br>
> >> >>>> *From:* Daniel-Constantin Mierla<br>
><br>
> <<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>><br>
><br>
> >> >>>> *To:* arun Jayaprakash <<a href="mailto:jayaprakasharun@yahoo.com">jayaprakasharun@yahoo.com</a>>; Kamailio (SER) -<br>
> >> >>>> Users Mailing List <<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>><br>
> >> >>>> *Sent:* Tuesday, July 2, 2013 2:39<br>
><br>
> AM<br>
><br>
> >> >>>> *Subject:* Re: [SR-Users] Issue with<br>
><br>
> RTP proxy....<br>
><br>
> >> >>>> Hello,<br>
> >> >>>><br>
> >> >>>> On 7/1/13 5:48 PM, arun Jayaprakash<br>
><br>
> wrote:<br>
> >> >>>>> Hello, I have enabled RTP proxy<br>
><br>
> on my machine (ec2 instance) by<br>
><br>
> >> >>>>> running the following script:<br>
> >> >>>>><br>
> >> >>>>> rtpproxy -F -l mypublicip -s udp:localhost:7722<br>
> >> >>>>><br>
> >> >>>>> but I keep getting this error.<br>
><br>
> The phones ring but there is no audio:<br>
> >> >>>>> 3(4144) ERROR: rtpproxy<br>
><br>
> [rtpproxy.c:2647]: force_rtp_proxy():<br>
> >> >>>>> incorrect port 0 in reply from<br>
><br>
> rtp proxy<br>
><br>
> >> >>>>> can someone let me know what<br>
><br>
> this error means?<br>
><br>
> >> >>>> you cannot get rtpproxy listening on<br>
><br>
> the ec2 public ip, which does not<br>
><br>
> >> >>>> exist on the network interface.<br>
> >> >>>><br>
> >> >>>> You will have to use a patched<br>
><br>
> rtpproxy, that adds advertising address<br>
><br>
> >> >>>> support. I had such patch for my own<br>
><br>
> usage, now I polished it a bit<br>
><br>
> >> >>>> and push it to github:<br>
> >> >>>><br>
> >> >>>> -<br>
> >> >>>> <a href="https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0" target="_blank">https://github.com/miconda/rtpproxy/commit/41f6d9d9084a6fad52a6483a0</a><br>
> >> >>>> 593<br>
> >> >>>> d4b25e0de8ca<br>
> >> >>>><br>
> >> >>>><br>
> >> >>>> Give it a try, hope I haven't broken<br>
><br>
> it with last polishing, if does<br>
><br>
> >> >>>> not work let me know.<br>
> >> >>>><br>
> >> >>>> You should be able to apply it to<br>
><br>
> latest rtpproxy stable release. Once<br>
><br>
> >> >>>> you compile and install, then run<br>
><br>
> rtpproxy with:<br>
> >> >>>> rtpproxy -F -l localip -A publicip<br>
><br>
> -s udp:localhost:7722<br>
><br>
> >> >>>> Cheers,<br>
> >> >>>> Daniel<br>
><br>
> _______________________________________________<br>
><br>
> >> >>> SIP Express Router (SER) and Kamailio<br>
><br>
> (OpenSER) - sr-users mailing list<br>
><br>
> >> >>> <a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
> >> >>> <a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
><br>
> _______________________________________________<br>
><br>
> >> >> SIP Express Router (SER) and Kamailio<br>
><br>
> (OpenSER) - sr-users mailing list<br>
><br>
> >> >> <a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
> >> >> <a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
> >> ><br>
> >> > _______________________________________________<br>
> >> > SIP Express Router (SER) and Kamailio (OpenSER)<br>
><br>
> - sr-users mailing list<br>
><br>
> >> > <a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
> >> > <a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
> ><br>
> >_______________________________________________<br>
><br>
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
> <a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
> <a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br>
_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Carlos<div><a href="http://caruizdiaz.com" target="_blank">http://caruizdiaz.com</a></div><div>+595981146623</div>
</div>