8 Nov
2005
8 Nov
'05
9:56 a.m.
Dear all,
When we use only one mediaproxy which is on the same machine with SER and disable the
dispatcher, this system works perfectly. But now we want to use the dispatcher on the
machine A with SER(ip:218.97.252.38), and install a mediaproxy on a separater machine
B(ip:218.97.252.40), then mediaproxy just can not start. Call signaling is all OK, but
there is no voice. SDP section of invite message is not changed by the mediaproxy.
The log file on machine A shows that:
Nov 8 16:36:10 b2bua proxydispatcher[5188]: command request
8029CEE9-92A3-4E09-91B5-0F1EE955B343(a)218.97.252.39 218.97.252.39:8000:audio 218.97.252.39
sensates.com remote 203.86.79.190 remote X-Lite=20release=201103a
info=from:38001@sensates.com,to:3801@sensates.com,fromtag:614201966,totag:
Nov 8 16:36:11 b2bua proxydispatcher[5188]: error: couldn't forward command to
218.97.252.40:25060 (Connection refused)
The log file on machine B shows that:
Nov 8 11:46:10 localhost mediaproxy[4082]: mediaproxy started.
Nov 8 11:46:10 localhost mediaproxy[4082]: Listening for commands on local socket is
disabled
Nov 8 11:46:10 localhost mediaproxy[4082]: Mediaproxy error: couldn't create command
socket (Cannot assign requested address).
Nov 8 11:46:10 localhost mediaproxy[4082]: exiting.
Nov 8 11:46:10 localhost proxydispatcher[4085]: proxydispatcher started.
Nov 8 11:46:10 localhost proxydispatcher[4085]: disabled from configuration
Nov 8 11:46:10 localhost proxydispatcher[4085]: exiting.
We set mediaproxy.ini (on machine B) as follow:
[Dispatcher]
start = no
socket = /var/run/proxydispatcher.sock
group = ser
[MediaProxy]
start = yes
socket = None
group = ser
listen = 218.97.252.38:25060
allow = 218.97.252.38
proxyIP = 218.97.252.40
portRange = 35000:65000
TOS = 0xb8
idleTimeout = 60
holdTimeout = 3600
forceClose = 0
accounting = off
Thanks a lot.