I have found the problem, and of course it's just what I though, it is because of my setup. Now I just need to figure out a fix. The problem is that it can't bind to the IP that I want it to use in the offer/answer. For example if I put in:<br>
<br>relay_ip = 10.251.27.180<br><br>Then it doesn't blow up, but it writes the SDP with a private address not accessible. If I put in:<br><br>relay_ip = <public_ip><br><br>Then it blows up. So is there a way to get media proxy to bind to one address, and offer another?<br>
<br>-dg<br>
<br><br><div class="gmail_quote">On Fri, Oct 16, 2009 at 10:25 AM, Jeff Pyle <span dir="ltr"><<a href="mailto:jpyle@fidelityvoice.com">jpyle@fidelityvoice.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<font face="Tahoma, Verdana, Helvetica, Arial"><span style="font-size: 10pt;">Way to let the smoke out.<br>
<br>
What are you using for a port range in config.ini?<br><font color="#888888">
<br>
<br>
<br>
- Jeff</font><div><div></div><div class="h5"><br>
<br>
<br>
<br>
On 10/16/09 1:21 PM, "Daniel Goepp" <<a href="http://dan@goepp.net" target="_blank">dan@goepp.net</a>> wrote:<br>
<br>
</div></div></span></font><div><div></div><div class="h5"><blockquote><font face="Tahoma, Verdana, Helvetica, Arial"><span style="font-size: 10pt;">Oh and I believe that since media proxy went a little crazy, opensips just failed with:<br>
<br>
Oct 16 17:15:29 ip-10-251-27-180 /usr/local/sbin/opensips[3093]: ERROR:mediaproxy:send_command: did timeout waiting for an answer <br>
<br>
-dg<br>
<br>
<br>
On Fri, Oct 16, 2009 at 10:19 AM, Daniel Goepp <<a href="http://dan@goepp.net" target="_blank">dan@goepp.net</a>> wrote:<br>
</span></font><blockquote><font face="Tahoma, Verdana, Helvetica, Arial"><span style="font-size: 10pt;">That definitely made something happen, as in blow up my relay ;)<br>
<br>
Dispatcher:<br>
debug: Connection to OpenSIPS lost: Connection was closed cleanly.<br>
debug: Issuing "update" command to relay at 127.0.0.1<br>
debug: Connection to OpenSIPS lost: Connection was closed cleanly.<br>
warning: relay failure: Relay at 127.0.0.1 timed out<br>
error: No suitable relay found<br>
warning: relay failure: Relay at 127.0.0.1 timed out<br>
error: No suitable relay found<br>
error: Connection with relay at 127.0.0.1 was lost: TCP connection timed out.<br>
<br>
Relay (spewed constantly):<br>
warning: Cannot use port pair 59128/59129<br>
warning: Cannot use port pair 59130/59131<br>
warning: Cannot use port pair 59132/59133<br>
warning: Cannot use port pair 59134/59135<br>
warning: Cannot use port pair 59136/59137<br>
warning: Cannot use port pair 59138/59139<br>
warning: Cannot use port pair 59140/59141<br>
warning: Cannot use port pair 59142/59143<br>
<br>
I believe this is likely due to the fact that much like the problem I had with opensip, mediaproxy does not like me telling it that it's IP is something other than what it's interface says. I'm digging in deeper now.<br>
<br>
Thanks<br>
<font color="#888888"><br>
-dg<br>
</font><br>
<br>
<br>
On Fri, Oct 16, 2009 at 9:38 AM, Jeff Pyle <<a href="http://jpyle@fidelityvoice.com" target="_blank">jpyle@fidelityvoice.com</a>> wrote:<br>
</span></font><blockquote><font face="Tahoma, Verdana, Helvetica, Arial"><span style="font-size: 10pt;">Dan,<br>
<br>
Are you using the dialog module? I recommend it. If so, you’ll need<br>
somewhere in there before any t_relay():<br>
<br>
create_dialog();<br>
engage_media_proxy();<br>
<br>
This actually switches on Mediaproxy for the call. It uses the dialog<br>
module to track any reinvites, etc.<br>
<br>
<br>
- Jeff<br>
<br>
<br>
<br>
On 10/16/09 12:32 PM, "Daniel Goepp" <<a href="http://dan@goepp.net" target="_blank">dan@goepp.net</a>> wrote:<br>
<br>
> I have finally successfully install and am running media proxy on the same<br>
> server that I am running opensips. I have added to the opensips.cfg the<br>
> mediaproxy module<br>
><br>
> loadmodule "mediaproxy.so"<br>
><br>
> From an example site I tried with these, then commented them out:<br>
> #modparam("mediaproxy", "mediaproxy_socket",<br>
> "/var/run/mediaproxy/dispatcher.sock")<br>
> #modparam("mediaproxy", "mediaproxy_timeout", 500)<br>
> #modparam("mediaproxy", "signaling_ip_avp", "$avp(s:nat_ip)")<br>
> #modparam("mediaproxy", "media_relay_avp", "$avp(s:media_relay)")<br>
><br>
> The SDP on my calls are not getting re-written with the IP of the media. With<br>
> RTP proxy I had to put in the force_rtp_proxy call, but I don't see anything<br>
> similar with media proxy. Any ideas on what I might look at next to get<br>
> opensips to re-write the SDP?<br>
><br>
> Here are the startup commands and output:<br>
><br>
> /usr/local/src# media-dispatcher --no-fork<br>
> Starting MediaProxy Dispatcher 2.3.8<br>
> Twisted is using epollreactor<br>
> mediaproxy.dispatcher.RelayFactory starting on 25060<br>
> mediaproxy.dispatcher.OpenSIPSControlFactory starting on<br>
> "'/var/run/mediaproxy/dispatcher.sock'"<br>
> mediaproxy.dispatcher.ManagementControlFactory starting on 25061<br>
> debug: Connection from relay at 127.0.0.1<br>
> debug: Issuing "sessions" command to relay at 127.0.0.1<br>
><br>
> /etc/mediaproxy# media-relay --no-fork<br>
> Starting MediaProxy Relay 2.3.8<br>
> Set resource limit for maximum open file descriptors to 11000<br>
> gc: collectable <tuple 0xb7c1152c><br>
> gc: collectable <StgDict 0xb7a9c6ac><br>
> gc: collectable <_ctypes.ArrayType 0x8552fc4><br>
> gc: collectable <getset_descriptor 0xb7bd0a0c><br>
> gc: collectable <getset_descriptor 0xb7bd09cc><br>
> gc: collectable <tuple 0xb7f5c61c><br>
> gc: collectable <tuple 0xb7bd0a2c><br>
> gc: collectable <StgDict 0xb7a9c91c><br>
> gc: collectable <_ctypes.ArrayType 0x8554e54><br>
> gc: collectable <getset_descriptor 0xb7bd08ac><br>
> gc: collectable <getset_descriptor 0xb7bd048c><br>
> gc: collectable <tuple 0xb7a632fc><br>
> gc: collectable <getset_descriptor 0xb7bd060c><br>
> gc: collectable <getset_descriptor 0xb7bd0c6c><br>
> /etc/resolv.conf changed, reparsing<br>
> Resolver added ('172.16.0.23', 53) to server list<br>
> <class 'twisted.names.dns.DNSDatagramProtocol'> starting on 21651<br>
> Starting protocol <twisted.names.dns.DNSDatagramProtocol object at 0xb7a2254c><br>
> (Port 21651 Closed)<br>
> Stopping protocol <twisted.names.dns.DNSDatagramProtocol object at 0xb7a2254c><br>
><br>
> Thanks<br>
><br>
> -dg<br>
><br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="http://Users@lists.opensips.org" target="_blank">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>
</span></font></blockquote><font face="Tahoma, Verdana, Helvetica, Arial"><span style="font-size: 10pt;"><br>
</span></font></blockquote><font face="Tahoma, Verdana, Helvetica, Arial"><span style="font-size: 10pt;"><br>
<br>
</span></font></blockquote>
</div></div></div>
<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>
<br></blockquote></div><br>