0.0.0.0

Good day, tell me please, can someone of you will come across at least an idea where to look.

In general the problem:
If the asterisk in sip.conf set to play an ip, then everything is OK and no problems. But if you put 0.0.0.0, start weird glitches. Some clients connect without problems, but the rest of the majority can not, receives a time out.

does the server have multiple IP addresses or multiple NICs?

eth0 Link encap:Ethernet HWaddr 00:30:48:F1:B5:DE
inet addr:212.158.161.155 Bcast:212.158.161.255 Mask:255.255.255.0
inet6 addr: fe80::230:48ff:fef1:b5de/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:206506490 errors:0 dropped:0 overruns:0 frame:0
TX packets:161276357 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:103517552676 (96.4 GiB) TX bytes:68098401815 (63.4 GiB)
Memory:faf60000-faf80000

eth0:0 Link encap:Ethernet HWaddr 00:30:48:F1:B5:DE
inet addr:217.23.132.80 Bcast:217.23.132.80 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Memory:faf60000-faf80000

eth0:1 Link encap:Ethernet HWaddr 00:30:48:F1:B5:DE
inet addr:217.23.132.81 Bcast:217.23.132.81 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Memory:faf60000-faf80000

eth0:2 Link encap:Ethernet HWaddr 00:30:48:F1:B5:DE
inet addr:217.23.132.82 Bcast:217.23.132.82 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Memory:faf60000-faf80000

eth0:3 Link encap:Ethernet HWaddr 00:30:48:F1:B5:DE
inet addr:217.23.132.83 Bcast:217.23.132.83 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Memory:faf60000-faf80000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:42425574 errors:0 dropped:0 overruns:0 frame:0
TX packets:42425574 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:97237700587 (90.5 GiB) TX bytes:97237700587 (90.5 GiB)

I guess that means the answer is yes. Appears to have 5 IP addresses.

I have one phisical interace and 4 aliases

i guessed that this is the problem. i will now speculate that some of the extensions and or trunks are being pointed at the secondary IP addresses… which is what causes the problem since the server will listen on those addresses but will always reply from the base address. i have encountered this with high availability clusters with a second, floating IP address. basically you can listen and reply on any one of the addresses on that NIC e.g. in siip.conf

bindaddr=217.23.132.81

would set that address to both listen and reply to SIP requests and handle RTP traffic.

bindaddr=0.0.0.0

will listen on all addresses but only reply from 217.23.132.80

This is something that only VoIP has an issue with as far as I have been able to tell. Other protocols [e.g. http], work fine on any of the added IP addresses.

So basically your choice is to use just the one IP address. The bindaddr=0.0.0.0 does not really mean “listen on all IP addresses” like the documentation suggests. It really means list on all base IP addresses on all NICs.

I want to use only aliesy 217.23.132.82 and 217.23.132.83. How to do it? I want both IP replied.

as far as i know…cannot be done… only one IP address per NIC.