Craig
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.
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?
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.   
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
drwxr-xr-x 2 root root 160 Jul 20 19:38 tls
(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.)
Regards
Gary

Date: Mon, 21 Jul 2014 09:30:51 +0800
From: [email protected]
To: [email protected]
Subject: Re: [OpenSIPS-Users] OpenSIPS + MediaProxy: "dispatcher.socket" not 
being created

Do you have mediaproxy-dispatcher running? Also does the relevant process have 
rights to create the dispatcher.sock?

On 21 July 2014 09:22, Gary Patton <[email protected]> wrote:







Hi all.  OpenSIPS 1.11.1 and MediaProxy 2.6.1.  
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.


Here's one of the error message lines from my opensips.log:
>>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
>
The strange thing is that I always get a
INFO:core:daemonize: pre-daemon process exiting with -0
and my SIP softphones register with no problems and I can make calls.

Any direction on what to look for, research, or reconfigure would be 
appreciated.  Thanks.
Regards
Gary
=====

>From my opensips_residential_01.cfg file:
#### MI_DATAGRAM moduleloadmodule "mi_datagram.so"modparam("mi_datagram", 
"socket_name", "/var/run/opensips/opensips.sock")

#####NAT modulesloadmodule "nat_traversal.so"modparam("nat_traversal", 
"keepalive_interval", 90)modparam("nat_traversal", "keepalive_method", 
"OPTIONS")

loadmodule "mediaproxy.so"modparam("mediaproxy", "disable", 
0)modparam("mediaproxy", "mediaproxy_socket", 
"/var/run/mediaproxy/dispatcher.sock")  # CUSTOMIZE ME
modparam("mediaproxy", "mediaproxy_timeout", 500)
####### Routing Logic ########
# main request routing logic

route{
        if (!mf_process_maxfwd_header("10")) {                
sl_send_reply("483","Too Many Hops");                exit;        }

        if (method==INVITE && !has_totag()) {                # We can also use 
a specific media relay if we need to                #$avp(media_relay) = 
"1.2.3.4";
                engage_media_proxy();        }
        if (client_nat_test ("3")) {                fix_contact();        }

        if ((method=="REGISTER" || method=="SUBSCRIBE" ||                
(method=="INVITE" && !has_totag())) && client_nat_test("3")) {                
nat_keepalive();
        }ETC, ETC.

                                          

_______________________________________________

Users mailing list

[email protected]

http://lists.opensips.org/cgi-bin/mailman/listinfo/users





_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users                        
                  
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to