Thanks again Samuel
I saw the ultramonkey open source stuff and I will look at it. In the mean
time I resolved the issue by setting up the alternate interfaces with a
private IP subnet like 10.0.0.2 - 3 and now there is no routing between the
public IP and private IP interfaces within the same server. I can manage the
'offline' server by ssh'ng into the on line server and then ssh'ng across
the private IP link to the second server. I'll let you know how it goes,
still in development.
Richard C. Thompson
Technology Assurance Director, CCNA
Virtual Communications, LLC
-----Original Message-----
From: samuel [mailto:samu60@gmail.com]
Sent: Thursday, July 27, 2006 11:02 AM
To: RThompson(a)vir2com.com
Cc: serusers(a)iptel.org
Subject: Re: FW: FW: [Serusers] DNS SRV Mediaproxy
It's a really nice setup and quite complex, if you manage to get it
working I would like to know it. You can try to take a look at
heartbeat and
www.ultramonkey.org because you might find useful
programs to monitor both machines and have "same" IP.
I don't know if it can help you but there's a parameter under proc
that controls whether packets should be forwarded from interface to
interface: Execute
#cat sys/net/ipv4/ip_forward
if it returns 1 it means that the kernel is acting as router between
the two interfaces. You can set it to 0 so the two interfaces would be
isolated:
#echo 0 > sys/net/ipv4/ip_forward
I'm afraid I can't help you more.....I don't know much more ;)
Samuel.
2006/7/27, Richard C. Thompson <rthompson(a)vir2com.com>om>:
Thanks Samuel
I now have it working. I found out the proxydispatcher was using eth0
which
had the other IP address on it. The one that SER is
not listening on. Once
I
switched the IP addresses around it started working.
BTW in order to get
SER
to route calls I had to turn mhomed off. Normally I
use bond0 with two
Ethernet interfaces, multihome on and use roundrobin to provide redundancy
but in this case I am trying to set up two SER servers, one as a mirror of
the other for a hot standby. I want to sync the two mysql databases using
the eth1's and have eth0 of the slave with the same IP address on it as
eth0
of the master SER. The interfaces go through a switch
that I can turn the
port off so there should be no conflict, but so far the improved routing
of
Linux has foiled my strategy ie Linux provides a path
through the working
interface, but I'm sure I'll find a way of isolating the interfaces,
mucking
around with iptables and such.
Do you know of anyone who has made this config work?
Thanks again for the help
Rick
-----Original Message-----
From: serusers-bounces(a)lists.iptel.org
[mailto:serusers-bounces@lists.iptel.org] On Behalf Of samuel
Sent: Thursday, July 27, 2006 3:59 AM
To: serusers(a)iptel.org
Subject: Re: FW: [Serusers] DNS SRV Mediaproxy
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
_______________________________________________
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