<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Craig<div><br></div><div>Thanks for getting back to me. When I do a "ps ax | grep media-" on my OpenSIPS / MediaProxy dispatcher server, it shows that media-dispatcher is NOT running. I thought that was because media-dispatcher process tried to start but aborted when it couldn't locate "dispatcher.sock" in /var/run/mediaproxy.</div><div><br></div><div>Because my OpennSIPS config loads the mediaproxy.so module w/the "modparam("mediaproxy", "mediaproxy_socket", "var/run/mediaproxy/dispatcher.sock") set in the OpenSIPS config file, I thought OpenSIPS created the dispatcher.sock. Or do I have it backwards - does MediaProxy's media-dispatcher process create dispatcher.sock?</div><div><br></div><div>As for rights, I have to confess that I haven't paid attention to rights. I followed instructions from the MediaProxy documentation on installing MediaProxy using the Debian respository. The instructions didn't mention setting rights for MediaProxy processes. I did install MediaProxy via a sudo user account. I also made sure that I copied all of the included MediaProxy certificates into the directory specified in the [TLS] section of MediaProxy's config.ini file. </div><div><br></div><div>But I'm not sure which process creates "dispatcher.sock" so I don't know whether the rights are configured correctly. When I do a "ls -l /var/run/mediaproxy/" i got</div><div><br></div><div>drwxr-xr-x 2 root root 160 Jul 20 19:38 tls</div><div><br></div><div><span style="font-size: 12pt;">(I see I was sloppy and used "dispatcher.sock" and "dispatcher.socket" in my post. I double-checked my OpenSIPS and MediaProxy config files and I did use "dispatcher.sock" in both. Sorry about that.)</span></div><div><br></div><div>Regards</div><div><br></div><div>Gary<br><br><div><hr id="stopSpelling">Date: Mon, 21 Jul 2014 09:30:51 +0800<br>From: craig.a.guy@gmail.com<br>To: users@lists.opensips.org<br>Subject: Re: [OpenSIPS-Users] OpenSIPS + MediaProxy: "dispatcher.socket" not being created<br><br><div dir="ltr">Do you have mediaproxy-dispatcher running? Also does the relevant process have rights to create the dispatcher.sock?</div><div class="ecxgmail_extra"><br><br><div class="ecxgmail_quote">On 21 July 2014 09:22, Gary Patton <span dir="ltr"><<a href="mailto:gpatton.public@outlook.com" target="_blank">gpatton.public@outlook.com</a>></span> wrote:<br>
<blockquote class="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex;">
<div><div dir="ltr">
<div dir="ltr">Hi all. OpenSIPS 1.11.1 and MediaProxy 2.6.1. </div><div dir="ltr"><br></div><div dir="ltr">My OpenSIPS creates the opensips.sock just fine. I don't believe my OpenSIPS is creating the "dispatcher.sock" properly or at all. After I do a "/etc/init.d/opensips restart" command, I look in the /var/run/mediaproxy/ directory and I never see the "dispatcher.socket" in there.<br>
<div><br></div><div>Here's one of the error message lines from my opensips.log:</div><div><span style="font-size:12pt;"><br></span></div><div><span style="font-size:12pt;">></span></div><div>><span style="font-size:12pt;">Jul 20 19:44:50 opensips1 /usr/local/opensips_proxy/sbin/opensips[9476]: ERROR:mediaproxy:mediaproxy_connect: failed to connect to /var/run/mediaproxy/dispatcher.sock: No such file or directory</span></div>
<div>></div><div><br></div><div>The strange thing is that I always get a</div><div><br></div><div>INFO:core:daemonize: pre-daemon process exiting with -0</div><div><br></div><div>and my SIP softphones register with no problems and I can make calls.</div>
<div><br></div><div>Any direction on what to look for, research, or reconfigure would be appreciated. Thanks.</div><div><br></div><div>Regards</div><div><br></div><div>Gary</div><div><br></div><div><span style="font-size:12pt;">=====</span></div>
<div><br></div><div>From my opensips_residential_01.cfg file:</div><div><br></div><div><div>#### MI_DATAGRAM module</div><div>loadmodule "mi_datagram.so"</div><div>modparam("mi_datagram", "socket_name", "/var/run/opensips/opensips.sock")</div>
</div><div><div><br></div><div>#####NAT modules</div><div><div>loadmodule "nat_traversal.so"</div><div>modparam("nat_traversal", "keepalive_interval", 90)</div><div>modparam("nat_traversal", "keepalive_method", "OPTIONS")</div>
</div><div><br></div><div>loadmodule "mediaproxy.so"</div><div>modparam("mediaproxy", "disable", 0)</div><div>modparam("mediaproxy", "mediaproxy_socket", "/var/run/mediaproxy/dispatcher.sock") # CUSTOMIZE ME</div>
</div><div>modparam("mediaproxy", "mediaproxy_timeout", 500)</div><div><br></div><div><div>####### Routing Logic ########</div><div><br></div><div># main request routing logic</div><div><br></div><div>
route{</div><div><br></div><div> if (!mf_process_maxfwd_header("10")) {</div><div> sl_send_reply("483","Too Many Hops");</div><div> exit;</div><div> }</div>
<div><br></div><div> if (method==INVITE && !has_totag()) {</div><div> # We can also use a specific media relay if we need to</div><div> #$avp(media_relay) = "1.2.3.4";</div>
<div> engage_media_proxy();</div><div> }</div><div><br></div><div> if (client_nat_test ("3")) {</div><div> fix_contact();</div><div> }</div><div><br></div><div>
if ((method=="REGISTER" || method=="SUBSCRIBE" ||</div><div> (method=="INVITE" && !has_totag())) && client_nat_test("3")) {</div><div> nat_keepalive();</div>
<div> }</div><div>ETC, ETC.</div></div><div><br></div></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></div>
<br>_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users</div></div> </div></body>
</html>