asterisk users - Jun 2011 - Re connecting to SIP Provider with virtual IP, from pacemaker cluster

Hi,

If your cluster's virtual IP is using ip aliasing (eg eth0:0), i think 
your problem come from UDP flows, they are, in opposition to TCP flows, 
unconnected, so the IP stack take the shortest route/interface to send 
them, wich is when this is the default route, the real interface and not 
the aliased.

For exemple if you have eth0 the real, eth0:0 the virtual, you can try 
to add in your failback/failover cluster script something like this :

# when the virtual ip come up
ip r a "SIP_PROVIDER_IP" via "GATEWAY_IP" dev eth0:0

# when the virtual ip come down, maybe facultative because the route is 
deleted when the interface fall down
ip r d "SIP_PROVIDER_IP" via "GATEWAY_IP" dev eth0:0

Regards,

C?dric


Le 15/06/11 19:01, asterisk-users-request at lists.digium.com a ?crit
:
> Date: Wed, 15 Jun 2011 17:28:36 +0200
> From:rosenberger at taoweb.at
> Subject: [asterisk-users] connecting to SIP Provider with virtual IP
> 	from	pacemaker cluster
> To:<asterisk-users at lists.digium.com>
> Message-ID:<d265002689c5927864dc1da6ae1f1e0b at taoweb.at>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> Hello !
>
> i am new to this list and asterisk.
>
> I run asterisk 1.4 on a OpenSuSE 11.4. My SIP Provider needs my IP to
> connect the local area number to my IP and also for there firewall.
> I plan to run asterisk in a pacemaker cluster that is not the problem
> and works.
> My problem is the virtual IP from the cluster and the connection to the
> SIP Provider.
> My Server has 2 NIC's one intern to register the VOIP Phone's and
one
> external to register to the SIP Provider.
> If i run asterisk with a virtuail IP configuration i get problems to
> connect to the SIP Provider
> because the ip route uses the real Hardware NIC ip.
> OK this i can solve with setting a sorce IP with ip route. That works
> with ssh an other but not with asterisk.
> tcpdump always show the the ip from the real Hardware device.
> A bindaddr in the SIP conf is first not possible because i had to
> connect from internal and external.
> But when i try a bindaddr on the virtual device tcpdump shows the same
> result that the connection comes
> from the real IP.
>
> maybe some had the same problem an can give me a hint.
>
>
> BR/Torsten

-- 
*C?dric Lemarchand
*

52 avenue de l'Europe
78160 Marly-le-Roi
France

Tel. +33 (0)1 30 08 88 88
Cell. +33 (0)6 37 23 40 93

logo

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20110615/a08a6e65/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo_ixblue.png
Type: image/png
Size: 4832 bytes
Desc: not available
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20110615/a08a6e65/attachment.png>

Hello C?dric
> # when the virtual ip come up
> ip r a "SIP_PROVIDER_IP" via "GATEWAY_IP" dev eth0:0
> 
> # when the virtual ip come down, maybe facultative because the route
> is deleted when the interface fall down
> ip r d "SIP_PROVIDER_IP" via "GATEWAY_IP" dev eth0:0
thank's for your hint. 
i tried it today but connection always come from eth0 and not from the
alias eth0:0

and route -n also shows for Iface eth0 and not eth0:0

BR/Torsten