asterisk users - Jul 2008 - Problems with IAX on heartbeat provided ip address

Hi!

I'm trying to build an HA system using heartbeat for failover. 
Everything works fine with SIP, but I cannot connect my IAX phone to 
the asterisk server using the managed IP address. Here is the 
configuration of the server (asterisk and the IP address are up, 'ip 
addr' and 'netstat' output):

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast 
qlen 1000
    link/ether 52:54:00:51:3b:e2 brd ff:ff:ff:ff:ff:ff
    inet 10.241.85.80/24 brd 10.241.85.255 scope global eth0
    inet 10.241.85.201/24 brd 10.241.85.255 scope global secondary 
eth0:0
    inet6 fe80::5054:ff:fe51:3be2/64 scope link
       valid_lft forever preferred_lft forever

tcp        0      0 0.0.0.0:5038            0.0.0.0:*               
LISTEN      28144/asterisk
tcp        0      0 0.0.0.0:2000            0.0.0.0:*               
LISTEN      28144/asterisk
udp        0      0 0.0.0.0:2727            0.0.0.0:*                           
28144/asterisk
udp        0      0 0.0.0.0:4520            0.0.0.0:*                           
28144/asterisk
udp        0      0 0.0.0.0:5060            0.0.0.0:*                           
28144/asterisk
udp        0      0 0.0.0.0:4569            0.0.0.0:*                           
28144/asterisk

Attaching wireshark shows that the IAX phone never receives any response 
from the asterisk server to its 'REGREQ'.

The IAX connection works fine as soon as I connect to '10.241.85.80' 
instead of '10.241.85.201'. There are no firewall rules in place 
(iptables is not even installed).

Any ideas? Does someone know of any relevant bugs in asterisk 1.4.17?

Cheers,
	Florian

-- 
DI Florian Hackenberger
florian at hackenberger.at
www.hackenberger.at

Florian Hackenberger wrote:
> Hi!
>
> I'm trying to build an HA system using heartbeat for failover. 
> Everything works fine with SIP, but I cannot connect my IAX phone to 
> the asterisk server using the managed IP address.
I've had a similar issue with HA, although in my case SIP wouldn't 
register either.  In my case, it was fixed by including one 
bindaddr=x.x.x.x statement in the [general] section of iax.ocnf per IP 
address that the machine could respond on.