[arm-allstar] arm-allstar Digest, Vol 51, Issue 23
mrnet
mrnet at ix.netcom.com
Sun Aug 12 23:44:47 EDT 2018
Doug,
That is very strange, the iax.conf files are correct 4569 and 4570, matching
what is in the database and the routers match too. These were working before
the update. I wonder where the ports are getting changes in the query that
you are seeing (not saying the update is the problem, it's only the time
stamp for the change)
Thanks,
Jud
N6GYF
-----Original Message-----
From: arm-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of
arm-allstar-request at hamvoip.org
Sent: Sunday, August 12, 2018 7:27 PM
To: arm-allstar at hamvoip.org
Subject: arm-allstar Digest, Vol 51, Issue 23
Send arm-allstar mailing list submissions to
arm-allstar at hamvoip.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
or, via email, send a message with subject or body 'help' to
arm-allstar-request at hamvoip.org
You can reach the person managing the list at
arm-allstar-owner at hamvoip.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of arm-allstar digest..."
Today's Topics:
1. Re: Notice to all hamvoip users (James Hause)
2. Re: Notice to all hamvoip users (Doug Crompton)
3. out/in connection problem after update (mrnet)
4. Re: out/in connection problem after update (Doug Crompton)
5. Moving a node... (Mr. Possum (Bill))
6. Re: out/in connection problem after update (Doug Crompton)
----------------------------------------------------------------------
Message: 1
Date: Sun, 12 Aug 2018 12:05:24 -0500
From: James Hause <hausejd at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] Notice to all hamvoip users
Message-ID:
<CAPoL7-H=7FuuGhH94wyUAf+paQbzH7UhJqFrsNieoBcMR2ygmQ at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Thanks for the information Doug.
I have, what is probably another dumb question, but here it is. Since
hamvoip is going to have it's own servers, as I understand it, then if I go
to the Allstar Active nodes site that I go to now to see what nodes are
active, will I need to check a different site once the new servers are
released?
73, Jim KF5LBT
On Sun, Aug 12, 2018 at 11:45 AM, "Doug Crompton via arm-allstar" <
arm-allstar at hamvoip.org> wrote:
> As of this morning the Allstar group has implemented a new server and
> lookup methodology for registration and node dissemination. Unfortunately
> it does not work as intended and is causing some nodes to not register. As
> of today there are about 400 less nodes registered than yesterday and many
> errors are appearing the data we are seeing.
>
> We apologize for any problems you may be having but we have no control
over
> this and knowing the changes that were to take place cautioned about its
> feasibility to no avail.
>
> The good thing is we have a sound system ready to go very soon to replace
> the servers you are currently using that will be a substantial positive
> step in improving the quality in both speed and accuracy of the Allstar
> system. Since our users are the majority of Allstar nodes and growing we
> take the quality of the Allstar system very seriously.
>
> Hopefully this is not causing you any problems but if it is be assured we
> are doing our best to make it better very soon.
>
> And a friendly reminder - if you are not using the V1.5 image you will not
> be able to take advantage of the services we will offer. Beaglebone Black
> and early Pi images will continue to work but not using the hamvoip
> protocol. These users will be at a big disadvantage. Please upgrade!!!
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
------------------------------
Message: 2
Date: Sun, 12 Aug 2018 13:21:07 -0400
From: Doug Crompton <wa3dsp at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] Notice to all hamvoip users
Message-ID:
<CAMp6vsv-RuA=+vTCgfHqQG3cX9x=gtgF=rWSN=UA+73N6Hqm1Q at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Jim,
Good questions. We will make the best effort to keep the communities
together but unfortunately can only offer code to others. If they decide to
not participate then that is on them. hamvop users will dual register and
also, if they want to, send dual status information. You will also have the
option of using the Allstar file node lookup system that has always been in
place or the hamvoip dns lookup which many are using now. There would be no
reason to use the Allstar lookup services as the hamvoip would have both
databases available with priority to the more accurate and timely hamvoip
ones.
I hope that answers your question for now. We will have much more on this
very soon.
*73 Doug*
*WA3DSP*
*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
On Sun, Aug 12, 2018 at 1:05 PM, "James Hause via arm-allstar" <
arm-allstar at hamvoip.org> wrote:
> Thanks for the information Doug.
> I have, what is probably another dumb question, but here it is. Since
> hamvoip is going to have it's own servers, as I understand it, then if I
go
> to the Allstar Active nodes site that I go to now to see what nodes are
> active, will I need to check a different site once the new servers are
> released?
> 73, Jim KF5LBT
>
> On Sun, Aug 12, 2018 at 11:45 AM, "Doug Crompton via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > As of this morning the Allstar group has implemented a new server and
> > lookup methodology for registration and node dissemination.
Unfortunately
> > it does not work as intended and is causing some nodes to not register.
> As
> > of today there are about 400 less nodes registered than yesterday and
> many
> > errors are appearing the data we are seeing.
> >
> > We apologize for any problems you may be having but we have no control
> over
> > this and knowing the changes that were to take place cautioned about its
> > feasibility to no avail.
> >
> > The good thing is we have a sound system ready to go very soon to
replace
> > the servers you are currently using that will be a substantial positive
> > step in improving the quality in both speed and accuracy of the Allstar
> > system. Since our users are the majority of Allstar nodes and growing we
> > take the quality of the Allstar system very seriously.
> >
> > Hopefully this is not causing you any problems but if it is be assured
we
> > are doing our best to make it better very soon.
> >
> > And a friendly reminder - if you are not using the V1.5 image you will
> not
> > be able to take advantage of the services we will offer. Beaglebone
Black
> > and early Pi images will continue to work but not using the hamvoip
> > protocol. These users will be at a big disadvantage. Please upgrade!!!
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> > _______________________________________________
> >
> > arm-allstar mailing list
> > arm-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> >
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
------------------------------
Message: 3
Date: Sun, 12 Aug 2018 18:35:46 -0700
From: "mrnet" <mrnet at ix.netcom.com>
To: <arm-allstar at hamvoip.org>
Subject: [arm-allstar] out/in connection problem after update
Message-ID: <E1fp1lr-000FSo-G7 at elasmtp-curtail.atl.sa.earthlink.net>
Content-Type: text/plain; charset="us-ascii"
A new problem. After getting the latest update and having the BataDNS loaded
I find I can not connect to any of my nodes and a recently built a third
node with the same build 45697, 48170, 42216. All nodes are on different
networks. Below is the AST Log. I get the same response in any direction. I
can how ever connect to nodes out in the wild such as 45830 and 45479, I
suspect they have not updated there image recently. I don't have any idea
what the slow response is caused by, I have rebooted every thing I have
checked all of the modified code ( BetaDNS) . supermon load across the
board. Etc. 45697 and 48170 were working before the latest update. All of
the DNS look ups in the docs are working.
Any Ideas,
Thanks in advanced
Jud
N6GYF
-- <DAHDI/pseudo-1423563495> Playing 'rpt/connection_failed' (language
'en')
[Aug 12 18:11:18] NOTICE[336] chan_iax2.c: Auto-congesting call due to slow
response
CLI readout from 48170
from node 48170 to node 45697
=========================================================================
Connected to Asterisk 1.4.23-pre.hamvoip-V1.5.3-38-app_rpt-0.327-08/08/2018
currently running on NAZ-BW-HUB (pid = 319)
Verbosity was 3 and is now 4
== Manager 'admin' logged on from 127.0.0.1
== Manager 'admin' logged off from 127.0.0.1
-- Hungup 'DAHDI/pseudo-1308875839'
[Aug 12 18:11:18] NOTICE[336]: chan_iax2.c:4097 __auto_congest:
Auto-congesting call due to slow response
-- Hungup 'IAX2/206.80.215.19:3625-12175'
-- Hungup 'DAHDI/pseudo-796202681'
-- <DAHDI/pseudo-1423563495> Playing 'rpt/node' (language 'en')
-- <DAHDI/pseudo-1423563495> Playing 'digits/4' (language 'en')
-- <DAHDI/pseudo-1423563495> Playing 'digits/5' (language 'en')
-- <DAHDI/pseudo-1423563495> Playing 'digits/6' (language 'en')
-- <DAHDI/pseudo-1423563495> Playing 'digits/9' (language 'en')
-- <DAHDI/pseudo-1423563495> Playing 'digits/7' (language 'en')
-- <DAHDI/pseudo-1423563495> Playing 'rpt/connection_failed' (language
'en')
-- Hungup 'DAHDI/pseudo-1423563495'
NAZ-BW-HUB*CLI>
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
AST log 48170
File: /var/log/asterisk/messages
-----------------------------------------------------------------
[Aug 12 18:04:46] NOTICE[319] dnsmgr.c: Managed DNS entries will be
refreshed every 300 seconds.
[Aug 12 18:04:46] NOTICE[319] cdr.c: CDR simple logging enabled.
[Aug 12 18:04:46] NOTICE[319] loader.c: 119 modules will be loaded.
[Aug 12 18:04:46] ERROR[319] codec_dahdi.c: Failed to open
/dev/dahdi/transcode: No such file or directory
[Aug 12 18:04:46] ERROR[319] chan_voter.c: Unable to load config voter.conf
[Aug 12 18:04:46] NOTICE[319] chan_irlp.c: Unable to load config irlp.conf
[Aug 12 18:04:46] WARNING[319] cdr_odbc.c: cdr_odbc: Unable to load config
for ODBC CDR's: cdr_odbc.conf
[Aug 12 18:04:46] NOTICE[319] pbx_ael.c: Starting AEL load process.
[Aug 12 18:04:46] NOTICE[319] pbx_ael.c: AEL load process: calculated config
file name '/usr/local/hamvoip-asterisk/etc/asterisk/extensions.ael'.
[Aug 12 18:04:46] NOTICE[319] pbx_ael.c: File
/usr/local/hamvoip-asterisk/etc/asterisk/extensions.ael not found; AEL
declining load
[Aug 12 18:04:46] NOTICE[319] chan_usbradio.c: Unable to load config
usbradio.conf
[Aug 12 18:04:46] NOTICE[319] chan_pi.c: Unable to load config pi.conf
[Aug 12 18:04:47] WARNING[319] pbx_spool.c: Unable to create queue directory
/var/spool/asterisk/outgoing -- outgoing spool disabled
[Aug 12 18:04:48] NOTICE[333] app_rpt.c: Normal Repeater Init 48170
[Aug 12 18:04:48] NOTICE[333] app_rpt.c: Normal Repeater Init 1999
[Aug 12 18:06:17] ERROR[348] chan_echolink.c: connect() failed to connect to
the Echolink server server5.echolink.org
[Aug 12 18:06:50] NOTICE[343] chan_iax2.c: Auto-congesting call due to slow
response
[Aug 12 18:11:18] NOTICE[336] chan_iax2.c: Auto-congesting call due to slow
response
Xxxxxxxxxxx end xxxxxxxxxxxx
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
------------------------------
Message: 4
Date: Sun, 12 Aug 2018 21:45:05 -0400
From: Doug Crompton <wa3dsp at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] out/in connection problem after update
Message-ID:
<CAMp6vst_xKs6ji-Qhor1OSDHkZvj_umrqEy44j2S784NVPfqgA at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Jud,
I can assure you this is not an update problem. Perhaps it could be the
problems at Allstar but lets do some checking. The issues you are seeing
point to routing problems.
First here are the reported IP addresses and ports for each node from
Allstar. The ports look strange but maybe you have them set that way? If
not this is an Allstar registration problem.
# dns-query 45697
+OK|radio at 206.80.215.19:14862/45697,206.80.215.19
Shows as iax port 14862
# dns-query 48170
+OK|radio at 63.230.217.89:3525/48170,63.230.217.89
Shows as iax port 3525
# dns-query 42216
+OK|radio at 75.32.108.157:22828/42216,75.32.108.157
shows as iax port 22828
Are these correct? Are these numbers the ports you have set in your
iax.conf bindport= for these nodes?
*73 Doug*
*WA3DSP*
*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
On Sun, Aug 12, 2018 at 9:35 PM, "mrnet via arm-allstar" <
arm-allstar at hamvoip.org> wrote:
> A new problem. After getting the latest update and having the BataDNS
> loaded
> I find I can not connect to any of my nodes and a recently built a third
> node with the same build 45697, 48170, 42216. All nodes are on different
> networks. Below is the AST Log. I get the same response in any direction.
> I
> can how ever connect to nodes out in the wild such as 45830 and 45479, I
> suspect they have not updated there image recently. I don't have any idea
> what the slow response is caused by, I have rebooted every thing I have
> checked all of the modified code ( BetaDNS) . supermon load across the
> board. Etc. 45697 and 48170 were working before the latest update. All of
> the DNS look ups in the docs are working.
>
>
>
> Any Ideas,
>
> Thanks in advanced
>
> Jud
>
> N6GYF
>
>
>
>
>
> -- <DAHDI/pseudo-1423563495> Playing 'rpt/connection_failed' (language
> 'en')
>
>
>
> [Aug 12 18:11:18] NOTICE[336] chan_iax2.c: Auto-congesting call due to
slow
> response
>
>
>
>
>
> CLI readout from 48170
>
>
>
> from node 48170 to node 45697
>
>
>
> =========================================================================
>
> Connected to Asterisk 1.4.23-pre.hamvoip-V1.5.3-38-
> app_rpt-0.327-08/08/2018
> currently running on NAZ-BW-HUB (pid = 319)
>
> Verbosity was 3 and is now 4
>
> == Manager 'admin' logged on from 127.0.0.1
>
> == Manager 'admin' logged off from 127.0.0.1
>
> -- Hungup 'DAHDI/pseudo-1308875839'
>
> [Aug 12 18:11:18] NOTICE[336]: chan_iax2.c:4097 __auto_congest:
> Auto-congesting call due to slow response
>
> -- Hungup 'IAX2/206.80.215.19:3625-12175'
>
> -- Hungup 'DAHDI/pseudo-796202681'
>
> -- <DAHDI/pseudo-1423563495> Playing 'rpt/node' (language 'en')
>
> -- <DAHDI/pseudo-1423563495> Playing 'digits/4' (language 'en')
>
> -- <DAHDI/pseudo-1423563495> Playing 'digits/5' (language 'en')
>
> -- <DAHDI/pseudo-1423563495> Playing 'digits/6' (language 'en')
>
> -- <DAHDI/pseudo-1423563495> Playing 'digits/9' (language 'en')
>
> -- <DAHDI/pseudo-1423563495> Playing 'digits/7' (language 'en')
>
> -- <DAHDI/pseudo-1423563495> Playing 'rpt/connection_failed' (language
> 'en')
>
> -- Hungup 'DAHDI/pseudo-1423563495'
>
> NAZ-BW-HUB*CLI>
>
>
>
>
>
> xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
>
>
> AST log 48170
>
>
>
> File: /var/log/asterisk/messages
>
> -----------------------------------------------------------------
>
> [Aug 12 18:04:46] NOTICE[319] dnsmgr.c: Managed DNS entries will be
> refreshed every 300 seconds.
>
> [Aug 12 18:04:46] NOTICE[319] cdr.c: CDR simple logging enabled.
>
> [Aug 12 18:04:46] NOTICE[319] loader.c: 119 modules will be loaded.
>
> [Aug 12 18:04:46] ERROR[319] codec_dahdi.c: Failed to open
> /dev/dahdi/transcode: No such file or directory
>
> [Aug 12 18:04:46] ERROR[319] chan_voter.c: Unable to load config
voter.conf
>
> [Aug 12 18:04:46] NOTICE[319] chan_irlp.c: Unable to load config irlp.conf
>
> [Aug 12 18:04:46] WARNING[319] cdr_odbc.c: cdr_odbc: Unable to load config
> for ODBC CDR's: cdr_odbc.conf
>
> [Aug 12 18:04:46] NOTICE[319] pbx_ael.c: Starting AEL load process.
>
> [Aug 12 18:04:46] NOTICE[319] pbx_ael.c: AEL load process: calculated
> config
> file name '/usr/local/hamvoip-asterisk/etc/asterisk/extensions.ael'.
>
> [Aug 12 18:04:46] NOTICE[319] pbx_ael.c: File
> /usr/local/hamvoip-asterisk/etc/asterisk/extensions.ael not found; AEL
> declining load
>
> [Aug 12 18:04:46] NOTICE[319] chan_usbradio.c: Unable to load config
> usbradio.conf
>
> [Aug 12 18:04:46] NOTICE[319] chan_pi.c: Unable to load config pi.conf
>
> [Aug 12 18:04:47] WARNING[319] pbx_spool.c: Unable to create queue
> directory
> /var/spool/asterisk/outgoing -- outgoing spool disabled
>
> [Aug 12 18:04:48] NOTICE[333] app_rpt.c: Normal Repeater Init 48170
>
> [Aug 12 18:04:48] NOTICE[333] app_rpt.c: Normal Repeater Init 1999
>
> [Aug 12 18:06:17] ERROR[348] chan_echolink.c: connect() failed to connect
> to
> the Echolink server server5.echolink.org
>
> [Aug 12 18:06:50] NOTICE[343] chan_iax2.c: Auto-congesting call due to
slow
> response
>
> [Aug 12 18:11:18] NOTICE[336] chan_iax2.c: Auto-congesting call due to
slow
> response
>
>
>
>
>
> Xxxxxxxxxxx end xxxxxxxxxxxx
>
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
------------------------------
Message: 5
Date: Mon, 13 Aug 2018 02:23:22 +0000 (UTC)
From: "Mr. Possum (Bill)" <flatpossum1231 at yahoo.com>
To: ARM Allstar <arm-allstar at hamvoip.org>, Doug Crompton
<wa3dsp at gmail.com>
Subject: [arm-allstar] Moving a node...
Message-ID: <1684409074.5804711.1534127002847 at mail.yahoo.com>
Content-Type: text/plain; charset=UTF-8
OK, I THOUGHT I knew what I was doing...? But evidently fate and the tech
gods have different ideas...
I wanted to move a HUB node from one of my nodes at home to a much more
reliable (and faster!) internet connection at a repeater site I have.
First I moved it on allstarlink.org to the right server this evening...
Then I remmed it out on my node at home and restarted asterisk.? I edited
extensions, iax.conf and rpt.conf
Then I added the hub node on the repeater site node and restarted asterisk.?
I edited extensions, iax.conf and rpt.conf
NOW it seems like the hub node isn't working anymore...? I can't make it
connect out and I can't connect INto it either...
I have gone over looking for typos and I can't find any...? (But that
doesn't mean there aren't any...)
So I got busy and slapped an unused node number of mine on the repeater site
node and can get things to connect to it! YAY!? BUT, allstarlink.org doesn't
have any registration data on it...? (throws up my hands in disgust...)? So
the bubble chart isn't working!
Is this an issue related to the new registration nightmare the allstar guys
are still working on or do you think I fat fingered something...
The hub node I moved is 46682 and it should come back with an IP of
50.27.185.63
The hub node I created that "sort of works" is 46903 on the same Ip
address...
I am sort of at an impasse now...? Not sure what's going on...? Any help
would be appreciated!
Bill - N5MBM
------------------------------
Message: 6
Date: Sun, 12 Aug 2018 22:26:21 -0400
From: Doug Crompton <wa3dsp at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] out/in connection problem after update
Message-ID:
<CAMp6vst9Rn+9xUOy09LRKfLT-6AcaocHOZd=zQnDyU1mAbQzDA at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Jud,
In talking to Dave this is most definitely an Allstar problem that they
caused by switching to the supposed better new system. It is failing
miserably and the only answer on their part is to go back to the old
system. If they don't I am afraid you are off the air Allstar wise until
they do or we get our new code going. We are working on doing that ASAP.
The problem is they moved away from old patched code that picked up the
port you advertised at Allstarlink.org. The new software apparently ignores
that. Some routers report wrong ports and the registration server is
picking that up in error rather than using a user defined port at
allstarlink.org.
Our new code will have a fix for that in the registration line. There will
be no need to define it at our end.
Again very sorry for the problem but it is not ours and we did warn then
about it. There are more than 700 nodes currently with bogus data like
yours.
*73 Doug*
*WA3DSP*
*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
On Sun, Aug 12, 2018 at 9:35 PM, "mrnet via arm-allstar" <
arm-allstar at hamvoip.org> wrote:
> A new problem. After getting the latest update and having the BataDNS
> loaded
> I find I can not connect to any of my nodes and a recently built a third
> node with the same build 45697, 48170, 42216. All nodes are on different
> networks. Below is the AST Log. I get the same response in any direction.
> I
> can how ever connect to nodes out in the wild such as 45830 and 45479, I
> suspect they have not updated there image recently. I don't have any idea
> what the slow response is caused by, I have rebooted every thing I have
> checked all of the modified code ( BetaDNS) . supermon load across the
> board. Etc. 45697 and 48170 were working before the latest update. All of
> the DNS look ups in the docs are working.
>
>
>
> Any Ideas,
>
> Thanks in advanced
>
> Jud
>
> N6GYF
>
>
>
>
>
> -- <DAHDI/pseudo-1423563495> Playing 'rpt/connection_failed' (language
> 'en')
>
>
>
> [Aug 12 18:11:18] NOTICE[336] chan_iax2.c: Auto-congesting call due to
slow
> response
>
>
>
>
>
> CLI readout from 48170
>
>
>
> from node 48170 to node 45697
>
>
>
> =========================================================================
>
> Connected to Asterisk 1.4.23-pre.hamvoip-V1.5.3-38-
> app_rpt-0.327-08/08/2018
> currently running on NAZ-BW-HUB (pid = 319)
>
> Verbosity was 3 and is now 4
>
> == Manager 'admin' logged on from 127.0.0.1
>
> == Manager 'admin' logged off from 127.0.0.1
>
> -- Hungup 'DAHDI/pseudo-1308875839'
>
> [Aug 12 18:11:18] NOTICE[336]: chan_iax2.c:4097 __auto_congest:
> Auto-congesting call due to slow response
>
> -- Hungup 'IAX2/206.80.215.19:3625-12175'
>
> -- Hungup 'DAHDI/pseudo-796202681'
>
> -- <DAHDI/pseudo-1423563495> Playing 'rpt/node' (language 'en')
>
> -- <DAHDI/pseudo-1423563495> Playing 'digits/4' (language 'en')
>
> -- <DAHDI/pseudo-1423563495> Playing 'digits/5' (language 'en')
>
> -- <DAHDI/pseudo-1423563495> Playing 'digits/6' (language 'en')
>
> -- <DAHDI/pseudo-1423563495> Playing 'digits/9' (language 'en')
>
> -- <DAHDI/pseudo-1423563495> Playing 'digits/7' (language 'en')
>
> -- <DAHDI/pseudo-1423563495> Playing 'rpt/connection_failed' (language
> 'en')
>
> -- Hungup 'DAHDI/pseudo-1423563495'
>
> NAZ-BW-HUB*CLI>
>
>
>
>
>
> xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
>
>
> AST log 48170
>
>
>
> File: /var/log/asterisk/messages
>
> -----------------------------------------------------------------
>
> [Aug 12 18:04:46] NOTICE[319] dnsmgr.c: Managed DNS entries will be
> refreshed every 300 seconds.
>
> [Aug 12 18:04:46] NOTICE[319] cdr.c: CDR simple logging enabled.
>
> [Aug 12 18:04:46] NOTICE[319] loader.c: 119 modules will be loaded.
>
> [Aug 12 18:04:46] ERROR[319] codec_dahdi.c: Failed to open
> /dev/dahdi/transcode: No such file or directory
>
> [Aug 12 18:04:46] ERROR[319] chan_voter.c: Unable to load config
voter.conf
>
> [Aug 12 18:04:46] NOTICE[319] chan_irlp.c: Unable to load config irlp.conf
>
> [Aug 12 18:04:46] WARNING[319] cdr_odbc.c: cdr_odbc: Unable to load config
> for ODBC CDR's: cdr_odbc.conf
>
> [Aug 12 18:04:46] NOTICE[319] pbx_ael.c: Starting AEL load process.
>
> [Aug 12 18:04:46] NOTICE[319] pbx_ael.c: AEL load process: calculated
> config
> file name '/usr/local/hamvoip-asterisk/etc/asterisk/extensions.ael'.
>
> [Aug 12 18:04:46] NOTICE[319] pbx_ael.c: File
> /usr/local/hamvoip-asterisk/etc/asterisk/extensions.ael not found; AEL
> declining load
>
> [Aug 12 18:04:46] NOTICE[319] chan_usbradio.c: Unable to load config
> usbradio.conf
>
> [Aug 12 18:04:46] NOTICE[319] chan_pi.c: Unable to load config pi.conf
>
> [Aug 12 18:04:47] WARNING[319] pbx_spool.c: Unable to create queue
> directory
> /var/spool/asterisk/outgoing -- outgoing spool disabled
>
> [Aug 12 18:04:48] NOTICE[333] app_rpt.c: Normal Repeater Init 48170
>
> [Aug 12 18:04:48] NOTICE[333] app_rpt.c: Normal Repeater Init 1999
>
> [Aug 12 18:06:17] ERROR[348] chan_echolink.c: connect() failed to connect
> to
> the Echolink server server5.echolink.org
>
> [Aug 12 18:06:50] NOTICE[343] chan_iax2.c: Auto-congesting call due to
slow
> response
>
> [Aug 12 18:11:18] NOTICE[336] chan_iax2.c: Auto-congesting call due to
slow
> response
>
>
>
>
>
> Xxxxxxxxxxx end xxxxxxxxxxxx
>
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
------------------------------
Subject: Digest Footer
_______________________________________________
arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
------------------------------
End of arm-allstar Digest, Vol 51, Issue 23
*******************************************
More information about the arm-allstar
mailing list