VoIP Mailing List Archives

[support at telium.ca]

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...



--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

Join the Asterisk Community at the 13th AstriCon, September 27-29, 2016
http://www.asterisk.org/community/astricon-user-conference

New to Asterisk? Start here:
https://wiki.asterisk.org/wiki/display/AST/Getting+Started

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users

[support at telium.ca]

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: <LOOPBACK,UP,LOWER_UP> 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: <BROADCAST,MULTICAST> 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: <BROADCAST,MULTICAST,UP,LOWER_UP> 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: <BROADCAST,MULTICAST> 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 <support@telium.ca>:

[support at telium.ca]

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 <vitor.mazuco@gmail.com>:

[support at telium.ca]

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 <support@telium.ca>: