Don’t know when it happened, sometime between 19.2 and 22, but asterisk will not bind to multiple IP’s anymore, only the first one. Spent ages checking firewall on a new install, only to find it’s asterisk.
Are all the interfaces on different subnets ?
what does netstat -ln |grep 4569 have to say ?
Just tested 1.4.22 in the lab here and it working as expected
udp 0 0 87.X.1XX.2XX:4569 0.0.0.0:*
udp 0 0 192.168.10.161:4569 0.0.0.0:*
udp 0 0 192.168.10.160:4569 0.0.0.0:*
I can register to all addresses and make calls.
Ian
No they’re all on the same subnet. I’m wondering if my iax.conf file isn’t compliant with .22, Either that or there’s something odd with the PIX 515 setup. 19.2 works fine.
Regards
so
You have multiple interfaces set as say 192.168.1.2, 192.168.1.3 , 192.168.1.4
Correct ?
I think you may have a basic network issue that affects linux, that being if you have multiple interfaces on the same subnet, all addresses appear as they are correct but in realty all traffic is via the first interface for all addresses.
Have google, you will many threads on the subject, Its one of the great elephant traps in Linux that isny in many other OS’s.
Ian
Yes that’s right, I have 1 real interface and 3 virtual. I would agree with your comments, apart from the fact that it’s been running as expected for 18 months now.
Its only that I’ve just installed 4 new servers that I thought I’d use the latest version of asterisk. As I said, if I install 19.2 using the same config files it works, it doesn’t with .22
With .22 remote PBX’s show server as unreachable. Fire up 19.2 and they come on-line immediately.
When I have a spare second I’ll try to debug what’s happening. Os’s are mixture of RHEL and Centos
Regards
Well its not a Asterisk issue, Nothing the release notes.
As the output above is from a system running 2 real and 1 virtual and works as expected. Its been upgraded from .18 to .22 current The issue I describe is when using multiple real interfaces as with virtual they all will be routed from the same mac address.
What does netstat show ? and how have you defined the interfaces ?
Ian
Well, back on this old chesnut
Netstat reports
udp 0 0 192.168.2.51:4569 0.0.0.0:*
udp 0 0 192.168.2.209:4569 0.0.0.0:*
udp 0 0 192.168.2.208:4569 0.0.0.0:*
Regsitration is fine, iax2 show peers show’s the peer is unreachable
iax.conf
;
[general]
bindport=4569
bindaddr = 192.168.2.208
bindaddr = 192.168.2.209
bindaddr = 192.168.2.51
I’ve tried this on MANY other locations, and the result is the same
i have to say? as on 1.4.26 it binds as expected.
But dont forget its the first thats the default.
When using alias IP addreses I never set the real interface as one that its bound to.
Even going back to 1.2 it still works as per the release notes and samples. IE the first defined interface is the default
This is from 1.2.24
bindadd=internalip
bindadd=externalip
1229/1229 192.168.XX.11X (D) 255.255.255.255 4569 OK (4 ms)
peer_out/se 193.XXX.XXX.98 (S) 255.255.255.255 4569 UNREACHABLE
bindadd=externalip
bindadd=internalip
1229/1229 192.168.XX.11X (D) 255.255.255.255 4569 UNREACHABLE
peer_out/se 193.XXX.XXX.98 (S) 255.255.255.255 4569 OK (32 ms)
bindaddr=0.0.0.0
1229/1229 192.168.XX.11X (D) 255.255.255.255 4569 OK (4 ms)
peer_out/se 193.XXX.XXX.98 (S) 255.255.255.255 4569 OK (36 ms)
Ian