27 Jul
2006
27 Jul
'06
10:58 a.m.
Can you get from the command line the SRV ressolution for mediaproy?
Try
#dig SRV _mediaproxy._tcp.mydomain.com
and check whether you get an answer...if not, there's some problem with DNS.
If you get the right answer, then probably the problem is in the SER
installation, remember to use mhomed=yes in the SER config file to
automatically select the right outbound socket (unless you want to do
it manually...)
I don't thing using two interfaces will affect directly how
proxydispatcher connects to DNS and ther resolved mediaproxies if *you
have the kernel routes properly configured*. Maybe you are trying to
contact a mediaproxy from an interface without connectivity to that
mediaproxy...
Hope it helps,
Samuel.
2006/7/26, Richard C. Thompson <rthompson(a)vir2com.com>om>:
Thanks for the hints! Below is additional info in response.
BTW the code for both the exit ser server and the new server are the same
except for a few things like IP address and such.
The new ser server has two interfaces and two IP addresses, does this mess
things up?
________________________________
Without relevant parts of your config file it's hard to tell....it can be:
*you missed to include the new ser address in the allow statment of the
existent mediaproxies
I included the new ser IP address in the existing mediaproxies
*there's an allow part in the DNS which does not include the new ser as
allowed to query for the _mediaproxy._tcp
I don't have an allow statement in the DNS Zone file. Is this what you are
referring to?
Does the new ser server have to be listed in the zone file?
*the domain statement in the new ser's proxydispatcher is not properly set
I have this in the mediaproxy.ini file
defaultProxy = domain://mydomain.com
*a typo somewhere...
why doesn't this line in mediproxy.ini work either?
defaultProxy =xx.xxx.xxx.xxx:25060 # IP address of one of the mediaproxy
servers
few hints...
sAmuEl.
2006/7/26, Richard C. Thompson < rthompson(a)vir2com.com>gt;:
Hi
Can anyone post a hint so I can figure this out.
I have a ser server using a DNS lookup for my SRV mediaproxy servers.
Everything works fine, and has been for some time.
Now I built a new ser server and want to go to the same mediaproxy servers
but I get the following error
Jul 26 09:47:36 localhost proxydispatcher[31666]: warning: none of the
proxies for domain mydomain.com have responded
Jul 26 09:47:36 localhost proxydispatcher[31666]: error: No mediaproxy
servers found for the default domain.
I have included the new ser IP in the allow config of the mediaproxy
Even if I force the defaultproxy to one of the IP addresses of a mediaproxy
server I get the following error
error: couldn't forward command to 0.0.0.0:25060 (Connection reset by peer)
Any ideas???
Could it be a version issue or maybe the python-mysqld issue, I'm not using
accounting.
Rick
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers