2.4.0 forces IAX and SIP bind addresses to 0.0.0.0

The priority of this should be higher. This effects more than port and bind address settings. It also effects available codecs and their selection order. The easiest fix might be to change the include order in sip.conf & iax.conf to put *_general_custom.conf before *_general_additional.conf?

Why have the bindaddr and port specified at all as Asterisk defaults to 0.0.0.0:4569 for iax and 0.0.0.0:5060 for sip if left unspecified.

when you cluster, the default bind 0.0.0.0 does not function. The bind address has to be the cluster floating address.

so has sip.conf changed - it should use the last value set, so if you do:

bindaddr=0.0.0.0
bindaddr=10.100.0.3

It should discard 0.0.0.0 as the bind address and use the new one set. Meaning if you do the same in a subsequent include file, it should have the same result. That is how it has worked in the past unless something has changed?

Here is the parsing code out of the 1.4 branch - it appears to set the value 'blindly' meaning the last one set will take?

    } else if (!strcasecmp(v->name, "bindaddr")) {
      if (!(hp = ast_gethostbyname(v->value, &ahp))) {
        ast_log(LOG_WARNING, "Invalid address: %s\n", v->value);
      } else {
        memcpy(&bindaddr.sin_addr, hp->h_addr, sizeof(bindaddr.sin_addr));
      }

I just ran some test now on 1.2. and 1.4 to check this and it appears to work as it always has. I tested bindaddr setting by resetting it to a different value in sip_general_custom.conf, which comes after the _addtional.conf (for this reason) and then at the CLI 'sip show settings' and it is properly set to the new value. Similarly for codecs you can override the defaults with:

disallow=all ;override all values auto generated in _addtional
allow=g729
allow=gsm
allow=ulaw

As an example, all in the sip_general_custom.conf file, as above. I have not tested this on 1.6 - hopefully it has not changed, if so, then a new ticket should be opened. I'm going to close this for now as worksforme. If you find otherwise in some circumstances I have not covered, then either comment with specifics and we'll re-open, or file a new bug at the specific scenario if it is more of a corner case situation.

p_lindheimer, It doesn't work for me. In sip_general_custom I have set bindaddr=192.168.40.56 and in sip_general_additional I set bindaddr=10.10.10.0 and after restating asterisk with restart gracefully the bind address is 10.10.10.0. So it uses the first address read (set in sip_general_additional) not the last. The same applies for codecs. Distribution PBXinaFlash Asterisk version 1.4.18.1 FreePBX version Core 2.4.0.1 Framework 2.4.0.0.

hmm - I ran it on a pbxinaflash for testing with the above results, although running a slightly older Asterisk version. But the code excerpt above was from the 1.4 latest branch. Please check to make sure you don't have any typos. The way I describe is how sip conf parsing has always worked. Same with codecs, if you use disallow=all it resets the codecs and you should always be able to then set them to your desired codecs.

I just tried it on 1.4.19 and it still works as I describe above.

I think I found the issue. Here is my sip.conf. Note that sip_general_custom comes BEFORE sip_general_additional! How did that happen? See my comment from 18th March. The same is true for iax.conf.

sip.conf ; do not edit this file, this is an auto-generated file by freepbx ; all modifications must be done from the web gui

[general] ; ; enable and force the sip jitterbuffer. If these settings are desired ; they should be set in the sip_general_custom.conf file as this file ; will get overwritten during reloads and upgrades. ; ; jbenable=yes ; jbforce=yes

; These will all be included in the [general] context ; #include sip_general_custom.conf #include sip_general_additional.conf #include sip_nat.conf #include sip_registrations_custom.conf #include sip_registrations.conf

; These should all be expected to come after the [general] context

if you did not change them yourself then you may want to check with the pbxinaflash team to make sure they did not do something. It is not the FreePBX code, you can take a look at svn and view the entire history of that file, it should never have been in that order.

SIP seems OK from my test, but IAX is not. IAX seems to listen on the 0.0.0.0 address AND any other addresses specified in 'iax_general_custom.conf'

When I have no extra bindaddr entries in 'iax_general_custom.conf', IAX seems to listen on the 0.0.0.0 address AS WELL AS the extra addresses.

<snip output of netstta -an |grep 4569> udp 0 0 143.96.128.49:4569 0.0.0.0:* udp 0 0 143.96.128.111:4569 0.0.0.0:* udp 0 0 0.0.0.0:4569 0.0.0.0:* </snip>

Thanks p_lindheimer, What is the consequences of changing both sip.conf and iax.conf? Will FreePBX rewrite them the next time I make a change?

Actually the IAX multi-listen problem shows up on my asterisk-1.4.17 box, but not on my 1.4.18 machines, so maybe this is a bug that has been fixed since 1.4.17??

doing a few tests on iax, it does appear that it binds to multiple addresses when you add them so this may be an issue, at least testing on 1.4.19, I have not checked on 1.2 or anything else.

We'll have to investigate, since I believe the default for iax is to bind to 0.0.0.0:4569 if nothing is specified, we may just remove the setting all together.

Yeah, the real issue with the IAX multi IP bind is not with incoming connections to the extra bind addresses, but with outgoing connections using the wrong address. The reason I use the bindaddr for IAX is to force the source IP for outgoing IAX connections to use the virtual IP and if you have 0.0.0.0 specified, IAX uses the NIC address of the outgoing interface. :(

rolly, why don't you open a new ticket against the iax issue specifically, mainly that it ends up dual homing it. Seems to make sense to take it out of the conf file all together and let it default if not sepcified - I'll just want to bounce it off someone else first.

r5747