Unfortunately yes, in this situation I am. The firewall is not PAT, but rather a full 1 to 1 NAT. So any request coming in on port 10000 or 10001 will go straight to MP. From a network perspective I know it works as long as the application is aware of what's going on. I'm able to get FreeSWITCH running next to this and it handles the packets fine, but FS has a way to tell it what the external IP is. Trust me, I know I'm fighting an uphill battle here...but I'm trying to do some proof of concept work that would depend on this setup. And at some point I will just admit defeat, I'm just not there yet. I have gone through the source for MP, and it actually doesn't seem like it would be too much to change, but unfortunately I'm no Python expert.<br>
<br>-dg<br>
<br><br><div class="gmail_quote">2009/10/16 Raúl Alexis Betancor Santana <span dir="ltr"><<a href="mailto:rabs@dimension-virtual.com">rabs@dimension-virtual.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Friday 16 October 2009 18:51:12 Daniel Goepp wrote:<br>
> Yes, I do realize that I'm breaking the rules...but that never stopped me<br>
> from trying before. And yes, RTPproxy has the same problem, which is why I<br>
> decided to give media proxy a try to see if I could get it working, same<br>
> problem though as you note. I guess next I'm going to have to get in and<br>
> hack up some code...would seem a straight forward fix though, just have two<br>
> parameters in the config, one to offer and one to bind to.<br>
><br>
> -dg<br>
<br>
</div>Just a question ... are you trying to use mediaproxy on a private IP, but to<br>
announce a public IP? ... that's your goal? .. if yes, it will NEVER run,<br>
mediaproxy/rtpproxy was designed to work on public IP's.<br>
Try to image what will occurs on this situation:<br>
<br>
UAC -> Proxy<br>
MP<br>
<br>
With MP working on a private IP, let say ... 10.10.10.10 behing a NAT<br>
router ... let say 222.222.222.222 with the port range 10.000-20.000<br>
redirected to mediaproxy IP.<br>
Now you setup mediaproxy to announce 222.222.222.222 as it's media-ip and let<br>
it bind to 10.10.10.10 (first of all, as you have seen that's not possible<br>
with current code)<br>
<br>
Now a nat-fixing request cames from the proxy ... and mediaproxy decides to<br>
use 10000:10001 and you send out that on the SDP to your UAC's, so your UAC1<br>
send it's RTP to <a href="http://222.222.222.222:10000" target="_blank">222.222.222.222:10000</a> and your UAC2 should do the same but<br>
to <a href="http://222.222.222.222:10001" target="_blank">222.222.222.222:10001</a>, how do you think that your NAT router would<br>
behalf ? ... wrongly on 99% of times, for sure.<br>
<font color="#888888"><br>
--<br>
Raúl Alexis Betancor Santana<br>
Dimensión Virtual<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br>