IAX UNREACHABLE : Ignoring Bindport/bindaddr On Reload

Home » Asterisk Users » IAX UNREACHABLE : Ignoring Bindport/bindaddr On Reload
Asterisk Users 12 Comments

Hi to everybody,

My IAX is not working, When I type reload IAX it returns me:

AsteriskSlave*CLI> iax2 reload
== Parsing ‘/etc/asterisk/iax.conf’: Found
== Parsing ‘/etc/asterisk/users.conf’: Found
[Aug 26 10:05:04] NOTICE[18078]: chan_iax2.c:13546 set_config:
Ignoring bindport on reload
[Aug 26 10:05:04] NOTICE[18078]: chan_iax2.c:13610 set_config:
Ignoring bindaddr on reload

And the peers is not working:

Name/Username Host Mask
Port Status Description prote1-prote2/p 192.168.25.26 (S)
255.255.255.255 4569 (T) UNREACHABLE
1 iax2 peers [0 online, 1 offline, 0 unmonitored]

See my both iax.conf

SERVER 1
[General]
bindportF59
bindaddr = all disallow=all allow=ulaw;alaw
;Contas para os servidores das filiais.
;;
[prote1-prote2]
secret= password username=prote1-prote2
host2.168.25.26
type=friend context=ramais qualify=yes trunk=yes auth = md5
;;

SERVER 2

[General]
bindportF59
bindaddr=all disallow=all allow=ulaw;alaw
;Contas para os servidores das filiais.
;;
[prote1-prote2]
secret= password username=prote1-prote2
host2.168.25.25
type=friend context=ramais qualify=yes trunk=yes auth = md5
;;
;;

How can I fix it?

Thanks.

12 thoughts on - IAX UNREACHABLE : Ignoring Bindport/bindaddr On Reload

  • Hi, I have already tried to change for bindaddr=0.0.0.0

    but it didn’t worked.

    2016-08-26 11:44 GMT-03:00, Frank Vanoni :

  • Could you post the result of “ip addr” command, and “netstat -anp | grep ast” after the reload?

    I suspect something else is going on here…

  • Hi, see the log below

    root@AsteriskSlave:~# ip addr
    1: lo: mtu 65536 qdisc noqueue state UNKNOWN
    group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
    valid_lft forever preferred_lft forever
    2: p3p1: mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:13:3b:12:02:21 brd ff:ff:ff:ff:ff:ff
    3: p4p1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:e0:4c:44:01:95 brd ff:ff:ff:ff:ff:ff
    inet 192.168.25.25/24 brd 192.168.25.255 scope global p4p1
    valid_lft forever preferred_lft forever
    inet6 2804:7f1:4080:fe45:2e0:4cff:fe44:195/64 scope global dynamic
    valid_lft 86398sec preferred_lft 43198sec
    inet6 fe80::2e0:4cff:fe44:195/64 scope link
    valid_lft forever preferred_lft forever
    4: p5p1: mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 14:dd:a9:82:38:ff brd ff:ff:ff:ff:ff:ff

    and

    root@AsteriskSlave:~# netstat -anp | grep ast tcp 0 0 0.0.0.0:2000 0.0.0.0:*
    OUÇA 2050/asterisk tcp 0 0 0.0.0.0:5338 0.0.0.0:*
    OUÇA 2050/asterisk udp 0 0 0.0.0.0:38180 0.0.0.0:*
    2050/asterisk udp 0 0 0.0.0.0:4520 0.0.0.0:*
    2050/asterisk udp 0 0 0.0.0.0:4659 0.0.0.0:*
    2050/asterisk udp 0 0 0.0.0.0:2727 0.0.0.0:*
    2050/asterisk udp 0 0 0.0.0.0:5000 0.0.0.0:*
    2050/asterisk udp 0 0 0.0.0.0:5089 0.0.0.0:*
    2050/asterisk unix 2 [ ACC ] STREAM OUVINDO 484
    2050/asterisk /var/run/asterisk/asterisk.ctl unix 2 [ ] DGRAM 11686 2050/asterisk

    2016-08-26 19:21 GMT-03:00, Telium Technical Support :
    —

  • This shows that asterisk’s IAX is already bound to all adapters – so that’s good. Symptomatically does your IAX stop working? Or do you just see a warning?

    —–Original Message—–
    From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Vitor Mazuco Sent: Monday, August 29, 2016 8:46 AM
    To: Asterisk Users Mailing List – Non-Commercial Discussion Subject: Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

    Hi, see the log below

    root@AsteriskSlave:~# ip addr
    1: lo: mtu 65536 qdisc noqueue state UNKNOWN
    group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
    valid_lft forever preferred_lft forever
    2: p3p1: mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:13:3b:12:02:21 brd ff:ff:ff:ff:ff:ff
    3: p4p1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:e0:4c:44:01:95 brd ff:ff:ff:ff:ff:ff
    inet 192.168.25.25/24 brd 192.168.25.255 scope global p4p1
    valid_lft forever preferred_lft forever
    inet6 2804:7f1:4080:fe45:2e0:4cff:fe44:195/64 scope global dynamic
    valid_lft 86398sec preferred_lft 43198sec
    inet6 fe80::2e0:4cff:fe44:195/64 scope link
    valid_lft forever preferred_lft forever
    4: p5p1: mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 14:dd:a9:82:38:ff brd ff:ff:ff:ff:ff:ff

    and

    root@AsteriskSlave:~# netstat -anp | grep ast tcp 0 0 0.0.0.0:2000 0.0.0.0:*
    OUÇA 2050/asterisk tcp 0 0 0.0.0.0:5338 0.0.0.0:*
    OUÇA 2050/asterisk udp 0 0 0.0.0.0:38180 0.0.0.0:*
    2050/asterisk udp 0 0 0.0.0.0:4520 0.0.0.0:*
    2050/asterisk udp 0 0 0.0.0.0:4659 0.0.0.0:*
    2050/asterisk udp 0 0 0.0.0.0:2727 0.0.0.0:*
    2050/asterisk udp 0 0 0.0.0.0:5000 0.0.0.0:*
    2050/asterisk udp 0 0 0.0.0.0:5089 0.0.0.0:*
    2050/asterisk unix 2 [ ACC ] STREAM OUVINDO 484
    2050/asterisk /var/run/asterisk/asterisk.ctl unix 2 [ ] DGRAM 11686 2050/asterisk

    2016-08-26 19:21 GMT-03:00, Telium Technical Support :
    —

  • Oh! In that case ignore it.

    Asterisk won’t rebind the adapter if you’ve only changed parameters. The message is misleading

    —–Original Message—–
    From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Vitor Mazuco Sent: Monday, August 29, 2016 10:41 AM
    To: Asterisk Users Mailing List – Non-Commercial Discussion Subject: Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

    Sorry,

    I just see warning.

    2016-08-29 11:40 GMT-03:00, Vitor Mazuco :
    —

  • Hummm, but why It is with that problem?

    I use UCARP, maybe is this the problem?

    2016-08-29 12:17 GMT-03:00, Telium Technical Support :

    —

  • Possibly – I noticed this thread only in the context of an IAX problem. I can’t speak to UCARP

    If you’re trying to my a high availability cluster out of Asterisk servers have a look at http://serverfault.com/questions/733403/high-availability-asterisk-options/733441#733441

    —–Original Message—–
    From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Vitor Mazuco Sent: Monday, August 29, 2016 11:38 AM
    To: Asterisk Users Mailing List – Non-Commercial Discussion Subject: Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

    Hummm, but why It is with that problem?

    I use UCARP, maybe is this the problem?

    2016-08-29 12:17 GMT-03:00, Telium Technical Support :

    —

  • Humm right

    I think the UCARP can be the problem

    It is the problem about sip and rtp ports

    I will remove it and make the tests

    Thanks man

    Em 29/08/2016 14:19, “Telium Technical Support”
    escreveu:

    Possibly – I noticed this thread only in the context of an IAX problem. I
    can’t speak to UCARP

    If you’re trying to my a high availability cluster out of Asterisk servers have a look at http://serverfault.com/questions/733403/high-
    availability-asterisk-options/733441#733441

    —–Original Message—

  • Yes, UCARP is the problem about the sip ports

    It conflict with ports IAX, SIP, RTP, etc.

    Thanks man.

    2016-08-29 21:44 GMT-03:00, Vitor Mazuco :
    —