subject:"\[asterisk\-users\] IAX UNREACHABLE \: Ignoring bindport\/bindaddr on reload"

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

2016-08-30 Thread Vitor Mazuco

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 <vitor.maz...@gmail.com>:
> 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" <supp...@telium.ca>
> 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-
> From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-
> boun...@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 <supp...@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-boun...@lists.digium.com
>> [mailto:asterisk-users-boun...@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.maz...@gmail.com>:
>>> I just see  warning?
>>>
>>>
>>> 2016-08-29 11:30 GMT-03:00, Telium Technical Support
>>> <supp...@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-boun...@lists.digium.com
>>>> [mailto:asterisk-users-boun...@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
>>>> tcp0  0 0.0.0.0:20000.0.0.0:*
>>>> OUÇA   2050/asterisk
>>>> tcp0  0 0.0.0.0:53380.0.0.0:*
>>>> OUÇA   2050/asterisk
>>>> udp0

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

2016-08-29 Thread Vitor Mazuco

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" <supp...@telium.ca>
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-
From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-
boun...@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 <supp...@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-boun...@lists.digium.com
> [mailto:asterisk-users-boun...@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.maz...@gmail.com>:
>> I just see  warning?
>>
>>
>> 2016-08-29 11:30 GMT-03:00, Telium Technical Support <supp...@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-boun...@lists.digium.com
>>> [mailto:asterisk-users-boun...@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
>>> tcp0  0 0.0.0.0:20000.0.0.0:*
>>> OUÇA   2050/asterisk
>>> tcp0  0 0.0.0.0:53380.0.0.0:*
>>> OUÇA   2050/asterisk
>>> udp0  0 0.0.0.0:38180   0.0.0.0:*
>>>  2050/asterisk
>>> udp0  0 0.0.0.0:45200.0.0.0:*
>>>  2050/asterisk
>>> udp0  0 0.0.0.0:46590.0.0.0:*
>>>  2050/asterisk
>>> udp0  0 0.0.0.0:27270.0.0.0:*
>>>  2050/asterisk
>>> udp0  0 0.0.0.0:50000.0.0.0:*
>>>  2050/asterisk
>>> udp0  0 0.0.0.0:50890.0.0.0:*
>>>  2050/asterisk
>>> unix  2  [ ACC ] STREAM OUVINDO   484
>>> 2050/asterisk   /var/run/aster

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

2016-08-29 Thread 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-boun...@lists.digium.com 
[mailto:asterisk-users-boun...@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 <supp...@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-boun...@lists.digium.com
> [mailto:asterisk-users-boun...@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.maz...@gmail.com>:
>> I just see  warning?
>>
>>
>> 2016-08-29 11:30 GMT-03:00, Telium Technical Support <supp...@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-boun...@lists.digium.com
>>> [mailto:asterisk-users-boun...@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
>>> tcp0  0 0.0.0.0:20000.0.0.0:*
>>> OUÇA   2050/asterisk
>>> tcp0  0 0.0.0.0:53380.0.0.0:*
>>> OUÇA   2050/asterisk
>>> udp0  0 0.0.0.0:38180   0.0.0.0:*
>>>  2050/asterisk
>>> udp0  0 0.0.0.0:45200.0.0.0:*
>>>  2050/asterisk
>>> udp0  0 0.0.0.0:46590.0.0.0:*
>>>  2050/asterisk
>>> udp0  0 0.0.0.0:27270.0.0.0:*
>>>  2050/asterisk
>>> udp0  0 0.0.0.0:50000.0.0.0:*
>>>  2050/asterisk
>>> udp0  0 0.0.0.0:50890.0.0.0:*
>>>  2050/asterisk
>>> unix  2  [ ACC ] STREAM OUVINDO   484
>>> 2050/asterisk   /var/run/asterisk/asterisk.ctl
>>> unix  2  [ ] DGRAM116862050/asterisk
>>>
>>> 2016-08-26 19:21 GMT-03:00, Telium Technical Support <supp...@telium.ca>:
>>>> Could y

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

2016-08-29 Thread 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 <supp...@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-boun...@lists.digium.com
> [mailto:asterisk-users-boun...@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.maz...@gmail.com>:
>> I just see  warning?
>>
>>
>> 2016-08-29 11:30 GMT-03:00, Telium Technical Support <supp...@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-boun...@lists.digium.com
>>> [mailto:asterisk-users-boun...@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
>>> tcp0  0 0.0.0.0:20000.0.0.0:*
>>> OUÇA   2050/asterisk
>>> tcp0  0 0.0.0.0:53380.0.0.0:*
>>> OUÇA   2050/asterisk
>>> udp0  0 0.0.0.0:38180   0.0.0.0:*
>>>  2050/asterisk
>>> udp0  0 0.0.0.0:45200.0.0.0:*
>>>  2050/asterisk
>>> udp0  0 0.0.0.0:46590.0.0.0:*
>>>  2050/asterisk
>>> udp0  0 0.0.0.0:27270.0.0.0:*
>>>  2050/asterisk
>>> udp0  0 0.0.0.0:50000.0.0.0:*
>>>  2050/asterisk
>>> udp0  0 0.0.0.0:50890.0.0.0:*
>>>  2050/asterisk
>>> unix  2  [ ACC ] STREAM OUVINDO   484
>>> 2050/asterisk   /var/run/asterisk/asterisk.ctl
>>> unix  2  [ ] DGRAM116862050/asterisk
>>>
>>> 2016-08-26 19:21 GMT-03:00, Telium Technical Support <supp...@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
>&g

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

2016-08-29 Thread 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-boun...@lists.digium.com 
[mailto:asterisk-users-boun...@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.maz...@gmail.com>:
> I just see  warning?
>
>
> 2016-08-29 11:30 GMT-03:00, Telium Technical Support <supp...@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-boun...@lists.digium.com
>> [mailto:asterisk-users-boun...@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
>> tcp0  0 0.0.0.0:20000.0.0.0:*
>> OUÇA   2050/asterisk
>> tcp0  0 0.0.0.0:53380.0.0.0:*
>> OUÇA   2050/asterisk
>> udp0  0 0.0.0.0:38180   0.0.0.0:*
>>  2050/asterisk
>> udp0  0 0.0.0.0:45200.0.0.0:*
>>  2050/asterisk
>> udp0  0 0.0.0.0:46590.0.0.0:*
>>  2050/asterisk
>> udp0  0 0.0.0.0:27270.0.0.0:*
>>  2050/asterisk
>> udp0  0 0.0.0.0:50000.0.0.0:*
>>  2050/asterisk
>> udp0  0 0.0.0.0:50890.0.0.0:*
>>  2050/asterisk
>> unix  2  [ ACC ] STREAM OUVINDO   484
>> 2050/asterisk   /var/run/asterisk/asterisk.ctl
>> unix  2  [ ] DGRAM116862050/asterisk
>>
>> 2016-08-26 19:21 GMT-03:00, Telium Technical Support <supp...@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
>>>
>>
>> --
>> _
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>
>> Join the Asterisk Community at

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

2016-08-29 Thread Vitor Mazuco

Sorry,

I just see warning.



2016-08-29 11:40 GMT-03:00, Vitor Mazuco <vitor.maz...@gmail.com>:
> I just see  warning?
>
>
> 2016-08-29 11:30 GMT-03:00, Telium Technical Support <supp...@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-boun...@lists.digium.com
>> [mailto:asterisk-users-boun...@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
>> tcp0  0 0.0.0.0:20000.0.0.0:*
>> OUÇA   2050/asterisk
>> tcp0  0 0.0.0.0:53380.0.0.0:*
>> OUÇA   2050/asterisk
>> udp0  0 0.0.0.0:38180   0.0.0.0:*
>>  2050/asterisk
>> udp0  0 0.0.0.0:45200.0.0.0:*
>>  2050/asterisk
>> udp0  0 0.0.0.0:46590.0.0.0:*
>>  2050/asterisk
>> udp0  0 0.0.0.0:27270.0.0.0:*
>>  2050/asterisk
>> udp0  0 0.0.0.0:50000.0.0.0:*
>>  2050/asterisk
>> udp0  0 0.0.0.0:50890.0.0.0:*
>>  2050/asterisk
>> unix  2  [ ACC ] STREAM OUVINDO   484
>> 2050/asterisk   /var/run/asterisk/asterisk.ctl
>> unix  2  [ ] DGRAM116862050/asterisk
>>
>> 2016-08-26 19:21 GMT-03:00, Telium Technical Support <supp...@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
>>>
>>
>> --
>> _
>> -- 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
>>
>>
>> --
>> _

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

2016-08-29 Thread Vitor Mazuco

I just see  warning?


2016-08-29 11:30 GMT-03:00, Telium Technical Support <supp...@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-boun...@lists.digium.com
> [mailto:asterisk-users-boun...@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
> tcp0  0 0.0.0.0:20000.0.0.0:*
> OUÇA   2050/asterisk
> tcp0  0 0.0.0.0:53380.0.0.0:*
> OUÇA   2050/asterisk
> udp0  0 0.0.0.0:38180   0.0.0.0:*
>  2050/asterisk
> udp0  0 0.0.0.0:45200.0.0.0:*
>  2050/asterisk
> udp0  0 0.0.0.0:46590.0.0.0:*
>  2050/asterisk
> udp0  0 0.0.0.0:27270.0.0.0:*
>  2050/asterisk
> udp0  0 0.0.0.0:50000.0.0.0:*
>  2050/asterisk
> udp0  0 0.0.0.0:50890.0.0.0:*
>  2050/asterisk
> unix  2  [ ACC ] STREAM OUVINDO   484
> 2050/asterisk   /var/run/asterisk/asterisk.ctl
> unix  2  [ ] DGRAM116862050/asterisk
>
> 2016-08-26 19:21 GMT-03:00, Telium Technical Support <supp...@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
>>
>
> --
> _
> -- 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
>
>
> --
> _
> -- 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

-- 
_

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

2016-08-29 Thread 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-boun...@lists.digium.com 
[mailto:asterisk-users-boun...@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
tcp0  0 0.0.0.0:20000.0.0.0:*
OUÇA   2050/asterisk
tcp0  0 0.0.0.0:53380.0.0.0:*
OUÇA   2050/asterisk
udp0  0 0.0.0.0:38180   0.0.0.0:*
 2050/asterisk
udp0  0 0.0.0.0:45200.0.0.0:*
 2050/asterisk
udp0  0 0.0.0.0:46590.0.0.0:*
 2050/asterisk
udp0  0 0.0.0.0:27270.0.0.0:*
 2050/asterisk
udp0  0 0.0.0.0:50000.0.0.0:*
 2050/asterisk
udp0  0 0.0.0.0:50890.0.0.0:*
 2050/asterisk
unix  2  [ ACC ] STREAM OUVINDO   484
2050/asterisk   /var/run/asterisk/asterisk.ctl
unix  2  [ ] DGRAM116862050/asterisk

2016-08-26 19:21 GMT-03:00, Telium Technical Support <supp...@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
>

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


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

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

2016-08-29 Thread Vitor Mazuco

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
tcp0  0 0.0.0.0:20000.0.0.0:*
OUÇA   2050/asterisk
tcp0  0 0.0.0.0:53380.0.0.0:*
OUÇA   2050/asterisk
udp0  0 0.0.0.0:38180   0.0.0.0:*
 2050/asterisk
udp0  0 0.0.0.0:45200.0.0.0:*
 2050/asterisk
udp0  0 0.0.0.0:46590.0.0.0:*
 2050/asterisk
udp0  0 0.0.0.0:27270.0.0.0:*
 2050/asterisk
udp0  0 0.0.0.0:50000.0.0.0:*
 2050/asterisk
udp0  0 0.0.0.0:50890.0.0.0:*
 2050/asterisk
unix  2  [ ACC ] STREAM OUVINDO   484
2050/asterisk   /var/run/asterisk/asterisk.ctl
unix  2  [ ] DGRAM116862050/asterisk

2016-08-26 19:21 GMT-03:00, Telium Technical Support :
> 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
>

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

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

2016-08-26 Thread Telium Technical Support

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

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

2016-08-26 Thread Vitor Mazuco

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 :
> On Fri, 2016-08-26 at 10:12 -0300, Vitor Mazuco wrote:
>
>> bindaddr = all
>
> Try:
>
> bindaddr=0.0.0.0
>
>
>
>
> --
> _
> -- 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
>

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

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

2016-08-26 Thread Frank Vanoni

On Fri, 2016-08-26 at 10:12 -0300, Vitor Mazuco wrote:

> bindaddr = all

Try:

bindaddr=0.0.0.0




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

[asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

2016-08-26 Thread Vitor Mazuco

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/UsernameHost   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]
bindport=4659
bindaddr = all
disallow=all
allow=ulaw;alaw
;Contas para os servidores das filiais.
;;
[prote1-prote2]
secret= password
username=prote1-prote2
host=192.168.25.26
type=friend
context=ramais
qualify=yes
trunk=yes
auth = md5
;;


SERVER 2

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


How can I fix it?


Thanks.

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

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

Re: [asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

[asterisk-users] IAX UNREACHABLE : Ignoring bindport/bindaddr on reload

13 matches

Site Navigation

Mail list logo

Footer information