Hi Steven,

Are you sure your dispatcher and relay daemons are running ?
use "ps aux | grep media" and see if they are actually running as background 
processes

btw look of it your dispatcher doesn't seems to be running. if it was, it'll 
create the socket file given in the config.
 

    On Monday, 24 September 2018, 6:07:15 PM GMT+5:30, Steven Platt 
<[email protected]> wrote:  
 
 Greetings, 
I am having difficulty getting OpensSIPS to connect to MediaProxy for the 
purpose of bridging media of clients behind NAT, and hope the community has 
advice on how to resolve. 
I have installed MediaProxy from the Debian Jessie repository, and updated the 
config.ini file to disable TLS, Radius, etc - and set the dispatcher and relay 
IP to the public IP of my opensips server. I have mediaproxy and opensips 
installed to the same server with a direct public IP. 
Currently, it looks as though opensips correctly detects the client is behind 
NAT and tried to invoke mediaproxy. The calls seem to fail when opensips goes 
to connect to mediaproxy using the designated socket. Although mediaproxy 
service is running - it does not create the socket. 
Opensips version = 2.3.5
--------------------------------------------------------
cat /var/log/opensips.log shows | tail 
root@[my-server]:~# cat /var/log/opensips.log | tailSep 21 19:08:59 [my-server] 
/usr/sbin/opensips[16080]: INFO:core:probe_max_sock_buff: using snd buffer of 
416 kbSep 21 19:08:59 [my-server] /usr/sbin/opensips[16080]: 
INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 61Sep 21 
19:09:21 [my-server] /usr/sbin/opensips[16081]: 
ERROR:mediaproxy:mediaproxy_connect: failed to connect to 
/var/run/mediaproxy/dispatcher.sock: No such file or directorySep 21 19:09:21 
[my-server] /usr/sbin/opensips[16081]: new branch at 
sip:1000@[client-outside-nat-ip]:44180;rinstance=4050910af32f1c09;transport=TCPSep
 21 19:09:21 [my-server] /usr/sbin/opensips[16081]: 
INFO:core:probe_max_sock_buff: using snd buffer of 416 kbSep 21 19:09:21 
[my-server] /usr/sbin/opensips[16081]: INFO:core:init_sock_keepalive: TCP 
keepalive enabled on socket 63Sep 21 19:13:34 [my-server] 
/usr/sbin/opensips[16081]: ERROR:mediaproxy:mediaproxy_connect: failed to 
connect to /var/run/mediaproxy/dispatcher.sock: No such file or directorySep 21 
19:13:34 [my-server] /usr/sbin/opensips[16081]: new branch at 
sip:1000@[client-outside-nat-ip]:44180;rinstance=4050910af32f1c09;transport=TCPSep
 21 19:13:34 [my-server] /usr/sbin/opensips[16081]: 
INFO:core:probe_max_sock_buff: using snd buffer of 416 kbSep 21 19:13:34 
[my-server] /usr/sbin/opensips[16081]: INFO:core:init_sock_keepalive: TCP 
keepalive enabled on socket 63
--------------------------------------------------------  

/etc/init.d/mediaproxy-relay and mediaproxy-dispatcher start does not give any 
error, and returns OK status for MediaProxy. 
The opensips module config for MediaProxy is: 
#### Media Proxy moduleloadmodule "mediaproxy.so"modparam("mediaproxy", 
"mediaproxy_socket", 
"/var/run/mediaproxy/dispatcher.sock")modparam("mediaproxy", 
"mediaproxy_timeout", 500)modparam("mediaproxy", "signaling_ip_avp", 
"$avp(nat_ip)")modparam("mediaproxy", "media_relay_avp", 
"$avp(media_relay)")modparam("mediaproxy", "ice_candidate", 
"low-priority")modparam("mediaproxy", "ice_candidate_avp", 
"$avp(ice_candidate)")
The MediaProxy config.ini set the socket to this as well: 
[Dispatcher]; Local socket on which to communicate with OpenSIPS. The OpenSIPS 
mediaproxy; module should be configured to connect to this socket. If a 
relative path,; /var/run/mediaproxy will be prepended. Default value is 
dispatcher.sock.;socket_path = dispatcher.sock
Any advice for this would be much appreciated. I have tried to resolve and find 
configuration examples for a few hours now. 
_______________________________________________
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