<div><div>I attached a graph of traffic on the interface that media-relay uses from the 18th through 20th. Before that we didn't realize it wasn't working and after we stopped it. FYI the interface has a 10Gb internet connection, so graph numbers are not pushing internet limits.</div>
<div>The mediaproxy log compressed from 272MB to 11MB and is at this <a href="http://viper.wideideas.net/mediaproxy.log.gz">link</a>.</div><div><br></div>Thanks for any help.</div><div>Dave</div><div><br><div class="gmail_quote">
On Wed, Oct 20, 2010 at 11:43 PM, Saúl Ibarra Corretgé <span dir="ltr"><<a href="mailto:saul@ag-projects.com" target="_blank">saul@ag-projects.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<div><br>
On 10/20/2010 11:14 PM, Dave Singer wrote:<br>
> I have one server where mediaproxy is having serious problems.<br>
> In the logs I have a lot of:<br>
> media-dispatcher[6067]: error: failed to end dialog: 500 Operation<br>
> failed<br>
<br>
</div>This error is returned by OpenSIPS when MediaProxy calls the dlg_end_dlg<br>
over the MI interface. Do you see anything in the OpenSIPS log?<br>
<div><br>
> and a lot of of the following but much less than the above:<br>
> media-dispatcher[6067]: error: Got `remove' command from OpenSIPS<br>
> for unknown session with call-id `83335711-572b-122e-57ab-0024e869f3a5'<br>
><br>
<br>
</div>Are you using the engage_media_proxy function alone? Are you using<br>
end_media_session by any chance?<br>
<div><br>
> After some preiod of time, from a few minutes to a day or<br>
> so, media-relay appears to start holding open ports that have long gone<br>
> dead.<br>
> After a while it runs out of ports for new calls and opensips sends the<br>
> call on without using mediaproxy.<br>
> Traffic graphs support this conclusion. They also show that it was<br>
> working fine for more than a month then stopped working.<br>
><br>
<br>
</div>Can you please provide some more information/logs on this?<br>
<div><div></div><div><br>
> I'm using<br>
> opensips 1.6.2-notls (x86_64/linux)<br>
> mediaproxy is enacted with engage_media_proxy() with dialog write to<br>
> db on shutdown.<br>
> mediaproxy 2.4.2 (just replaced with 2.4.3 but still getting the<br>
> errors mentioned above in the logs. Haven't seen it run out of ports yet<br>
> but it has only been a few minutes)<br>
> Fedora release 11, kernel 2.6.30.10-105.2.23.fc11.x86_64<br>
><br>
> pertinent opensips.cfg stuff<br>
> modparam("dialog", "dlg_flag", 13)<br>
> # db_mode: 0 - NO_DB, 1 - REALTIME, 2 - DELAYED, 3 - ON SHUTDOWN<br>
> modparam("dialog", "db_mode", 3)<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>
> modparam("mi_datagram", "socket_name", "/tmp/opensips.sock")<br>
> modparam("mi_datagram", "children_count", 4)<br>
><br>
> if (is_method("INVITE")) {<br>
> engage_media_proxy();<br>
> fix_nated_sdp("8","<my hosts ip>"); # topology<br>
> hide the sdp o header.<br>
> }<br>
> pertinent /etc/mediaproxy/config.ini stuff:<br>
> [Dispatcher]<br>
> socket_path = /var/run/mediaproxy-dispatcher.sock<br>
> [OpenSIPS]<br>
> socket_path = /tmp/opensips.sock<br>
><br>
<br>
</div></div>This looks fine.<br>
<br>
<br>
Regards,<br>
<font color="#888888"><br>
--<br>
Saúl Ibarra Corretgé<br>
AG Projects<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto: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>
</font></blockquote></div><br></div>