[arm-allstar] AutoSky, A Skywarn script for hamvoip (Doug Crompton)
Christopher W Fuselier AF5XP
af5xp at yahoo.com
Thu Apr 20 15:41:16 EST 2017
Does the tail message have to be there for AutoSky to work properly?
Christopher W. Fuselier, AF5XP
SARC W5SUL President & Trustee
ARES -- Region 5 Emergency Coordinator Calcasieu Parish
CERT -- Emergency Communications OIC
ARRL Volunteer ExaminerARRL Registered License Instructor
Email: AF5XP at yahoo.com
Cell:337-842-6554
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
-------- Original message --------
From: arm-allstar-request at hamvoip.org
Date: 4/20/17 10:14 AM (GMT-06:00)
To: arm-allstar at hamvoip.org
Subject: arm-allstar Digest, Vol 35, Issue 25
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. Trouble with iaxrpt (pjg)
2. Re: AutoSky, A Skywarn script for hamvoip (Justin Reed)
3. Re: Trouble with iaxrpt (Bryan St Clair)
4. Re: Trouble with iaxrpt (Doug Crompton)
5. Re: AutoSky, A Skywarn script for hamvoip (Doug Crompton)
6. Re: Trouble with iaxrpt (pjg)
7. TTS / Call Signs (Maurice Dake)
8. Re: AutoSky, A Skywarn script for hamvoip (Justin Reed)
9. Re: TTS / Call Signs (Doug Crompton)
10. Re: AutoSky, A Skywarn script for hamvoip (Doug Crompton)
----------------------------------------------------------------------
Message: 1
Date: Wed, 19 Apr 2017 20:11:59 -0400
From: pjg <pjg123 at comcast.net>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: [arm-allstar] Trouble with iaxrpt
Message-ID: <ee9f3b0a-325a-6772-ee2b-ae2dd2375605 at comcast.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi,
I just did a clean install of the new V1.5rc2 image on a RPI 2.
Everything is seams to be working fine. But when I try to connect from
my android or PC using iaxrpt I get a message saying:
chan_iax2.c:6858 register_verify: No registration for peer 'iaxrpt'
(from 192.168.1.167)
If I change the type=user to type=friend in iax.conf file, I am able to
connect ok.
I did a new clean install because I was having the same issue on a
previous install but I thought I might have changed something on the
last install.
Any ideas?
Paul
------------------------------
Message: 2
Date: Wed, 19 Apr 2017 19:11:31 -0500
From: Justin Reed <celltech161 at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] AutoSky, A Skywarn script for hamvoip
Message-ID: <828cad74-6229-d74d-45a8-9e41f4bc7d30 at gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Doug,
Is there any way to disable/enable AutoSky using a DTMF sequence that
doesn't begin with *?
For example, a 4 digit DTMF code like 1234.
I'm not sure how to remove the leading * as a requirement.
Thanks,
Justin
NV8Q
------------------------------
Message: 3
Date: Wed, 19 Apr 2017 17:18:00 -0700
From: Bryan St Clair <bryan at k6cbr.us>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] Trouble with iaxrpt
Message-ID:
<CAH5oE6ZsZ-LmpKb=WTH-QfsB_v8ZLy9b-YEQc72uCz72-5xipA at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
I used myiphone settings for Android. Worked for me.
Just have to uncomment out the lines in extensions.conf and update the
name, as mine was listed as myphone and not myiphone
Connect without issue now. Still use iaxrpt for Windows connections.
On Apr 19, 2017 5:12 PM, pjg via arm-allstar <arm-allstar at hamvoip.org>
wrote:
Hi,
I just did a clean install of the new V1.5rc2 image on a RPI 2. Everything
is seams to be working fine. But when I try to connect from my android or
PC using iaxrpt I get a message saying:
chan_iax2.c:6858 register_verify: No registration for peer 'iaxrpt' (from
192.168.1.167)
If I change the type=user to type=friend in iax.conf file, I am able to
connect ok.
I did a new clean install because I was having the same issue on a previous
install but I thought I might have changed something on the last install.
Any ideas?
Paul
_______________________________________________
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: 4
Date: Thu, 20 Apr 2017 00:49:17 -0400
From: Doug Crompton <wa3dsp at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] Trouble with iaxrpt
Message-ID:
<CAMp6vstMWZ7YAWkyhVrwSAEqt2md0XuKZ=vJnawXUGEOVebfEA at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Paul,
I am not sure why 'user' would not work since this is strictly and incoming
call but if 'friend' works then go with it. It is a little confusing at
times but I suspect it is an authorization problem. Here is a definition of
the type's -
type = [user|peer|friend]: This line tells Asterisk how to interpret
this entity. Users are things
that connect to us, while peers are people we connect to, and a friend is
shorthand for creating a user and a peer with identical information.
The case of incoming calls from the peer, the IP address must match in
order for the invitation to work. This means calls made from either
direction won't work if the peer is unregistered while host=dynamic or if
the host is otherwise not set to the correct IP of the sender.
For entities with 'type=user': Asterisk users handle inbound calls only
(meaning they call Asterisk, Asterisk can't ; call them) and are matched by
their authorization information (authname and secret). Asterisk doesn't
rely on their IP and will accept calls regardless of the host setting as
long as the incoming invite authorizes successfully.
For entities with 'type=friend': Asterisk will create the entity as both a
friend and a peer. Asterisk will accept calls from friends like it would
for users, requiring only that the authorization matches rather than the IP
address. Since it is also a peer, a friend entity can be called as long as
its IP is known to Asterisk. In the case of host=dynamic, this means it is
necessary for the entity to register before Asterisk can call it.
*73 Doug*
*WA3DSP*
*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
On Wed, Apr 19, 2017 at 8:11 PM, "pjg via arm-allstar" <
arm-allstar at hamvoip.org> wrote:
> Hi,
>
> I just did a clean install of the new V1.5rc2 image on a RPI 2. Everything
> is seams to be working fine. But when I try to connect from my android or
> PC using iaxrpt I get a message saying:
>
> chan_iax2.c:6858 register_verify: No registration for peer 'iaxrpt' (from
> 192.168.1.167)
>
> If I change the type=user to type=friend in iax.conf file, I am able to
> connect ok.
>
> I did a new clean install because I was having the same issue on a
> previous install but I thought I might have changed something on the last
> install.
>
> Any ideas?
>
> Paul
>
> _______________________________________________
>
> 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: Thu, 20 Apr 2017 00:59:30 -0400
From: Doug Crompton <wa3dsp at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] AutoSky, A Skywarn script for hamvoip
Message-ID:
<CAMp6vssCqZ87EcZvZ5wHGGiEW4Aiyw0BDH=Czp0mtU0a96nQQQ at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Justin,
The "lead-in" character for Allstar is '*' This can be changed to any
character in rpt.conf BUT whatever it is changed to cannot be part of the
remaining sequence. So you could change it to A or B or C or D on DTMF so
everything would then be preceded by A - A1234 etc. Theoretically you
could change it to say a '%' symbol but then DTMF would not work while you
could command with the client.
So the answer is NO you cannot just type 1234 if that is what the function
is defined as. Also you cannot define codes that are already defined or
within the range of already defined. The 8xx, 9xx are typically user
defined.
*73 Doug*
*WA3DSP*
*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
On Wed, Apr 19, 2017 at 8:11 PM, "Justin Reed via arm-allstar" <
arm-allstar at hamvoip.org> wrote:
> Doug,
> Is there any way to disable/enable AutoSky using a DTMF sequence that
> doesn't begin with *?
> For example, a 4 digit DTMF code like 1234.
>
> I'm not sure how to remove the leading * as a requirement.
>
> Thanks,
> Justin
> NV8Q
>
> _______________________________________________
>
> 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: 6
Date: Thu, 20 Apr 2017 02:17:57 -0400
From: pjg <pjg123 at comcast.net>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] Trouble with iaxrpt
Message-ID: <6b4f9203-6c34-8465-8d57-1e14dd16d92e at comcast.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Doug,
Thanks for the info, I have been looking for that answer about the diff
between the types.
I spent hours trying to figure out what was wrong, I shortened the
iax.conf to only general and iaxrpt sections and then tried every option
I could find listed but could not get type=user to work. I was not sure
that "friend" was as secure as "user".
Thanks again for the great work!!!!
Paul
On 4/20/2017 12:49 AM, "Doug Crompton via arm-allstar" wrote:
> Paul,
>
> I am not sure why 'user' would not work since this is strictly and incoming
> call but if 'friend' works then go with it. It is a little confusing at
> times but I suspect it is an authorization problem. Here is a definition of
> the type's -
>
> type = [user|peer|friend]: This line tells Asterisk how to interpret
> this entity. Users are things
> that connect to us, while peers are people we connect to, and a friend is
> shorthand for creating a user and a peer with identical information.
>
> The case of incoming calls from the peer, the IP address must match in
> order for the invitation to work. This means calls made from either
> direction won't work if the peer is unregistered while host=dynamic or if
> the host is otherwise not set to the correct IP of the sender.
>
> For entities with 'type=user': Asterisk users handle inbound calls only
> (meaning they call Asterisk, Asterisk can't ; call them) and are matched by
> their authorization information (authname and secret). Asterisk doesn't
> rely on their IP and will accept calls regardless of the host setting as
> long as the incoming invite authorizes successfully.
>
> For entities with 'type=friend': Asterisk will create the entity as both a
> friend and a peer. Asterisk will accept calls from friends like it would
> for users, requiring only that the authorization matches rather than the IP
> address. Since it is also a peer, a friend entity can be called as long as
> its IP is known to Asterisk. In the case of host=dynamic, this means it is
> necessary for the entity to register before Asterisk can call it.
>
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
> On Wed, Apr 19, 2017 at 8:11 PM, "pjg via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
>> Hi,
>>
>> I just did a clean install of the new V1.5rc2 image on a RPI 2. Everything
>> is seams to be working fine. But when I try to connect from my android or
>> PC using iaxrpt I get a message saying:
>>
>> chan_iax2.c:6858 register_verify: No registration for peer 'iaxrpt' (from
>> 192.168.1.167)
>>
>> If I change the type=user to type=friend in iax.conf file, I am able to
>> connect ok.
>>
>> I did a new clean install because I was having the same issue on a
>> previous install but I thought I might have changed something on the last
>> install.
>>
>> Any ideas?
>>
>> Paul
>>
>> _______________________________________________
>>
>> 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: 7
Date: Thu, 20 Apr 2017 09:32:40 -0400
From: "Maurice Dake" <k9ee at comcast.net>
To: <arm-allstar at hamvoip.org>
Subject: [arm-allstar] TTS / Call Signs
Message-ID: <6A91948CB324454BA62E542660DF6D54 at MauriceLapTop>
Content-Type: text/plain; charset="iso-8859-1"
To maintain the latest database of Allstar Call Signs do we just have to re-run the write_node_callsign.tar on a routine basis and write it? Is there an automated way to maintain the latest database.
------------------------------
Message: 8
Date: Thu, 20 Apr 2017 09:13:00 -0500
From: Justin Reed <celltech161 at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] AutoSky, A Skywarn script for hamvoip
Message-ID: <0059f1eb-952f-0fdf-c1d3-156f21b08867 at gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Ok, then my next question would be can the enable/disable scripts be
called from within the allmon2 controlpanel.ini.php file?
What would the syntax of that look like?
We had a severe T-storm watch and several warnings last night and the
alerts worked as advertised!
Thanks!
Justin
On 4/19/2017 11:59 PM, "Doug Crompton via arm-allstar" wrote:
> Justin,
>
> The "lead-in" character for Allstar is '*' This can be changed to any
> character in rpt.conf BUT whatever it is changed to cannot be part of the
> remaining sequence. So you could change it to A or B or C or D on DTMF so
> everything would then be preceded by A - A1234 etc. Theoretically you
> could change it to say a '%' symbol but then DTMF would not work while you
> could command with the client.
>
> So the answer is NO you cannot just type 1234 if that is what the function
> is defined as. Also you cannot define codes that are already defined or
> within the range of already defined. The 8xx, 9xx are typically user
> defined.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
> On Wed, Apr 19, 2017 at 8:11 PM, "Justin Reed via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
>> Doug,
>> Is there any way to disable/enable AutoSky using a DTMF sequence that
>> doesn't begin with *?
>> For example, a 4 digit DTMF code like 1234.
>>
>> I'm not sure how to remove the leading * as a requirement.
>>
>> Thanks,
>> Justin
>> NV8Q
>>
>> _______________________________________________
>>
>> 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: 9
Date: Thu, 20 Apr 2017 11:06:52 -0400
From: Doug Crompton <wa3dsp at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] TTS / Call Signs
Message-ID:
<CAMp6vsuGhMnF8fw5Mb0Xj+7Ufa9oW_0mmuyfOkCGsaBcd4RdOw at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Maurice,
Yes, you would need to run it from time to time. Maybe once a month or as
needed. It is not that important as things are not going to break if it is
not updated you just won't have calls vs. nodes numbers for a few new
nodes. You could do this with cron. cron has shortcuts to do that shown
below. Unless you specify the -o option it will not rewrite existing files.
@weekly /etc/asterisk/local/write_node_callsigns or
@monthly /etc/asterisk/local/write_node_callsigns
*73 Doug*
*WA3DSP*
*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
On Thu, Apr 20, 2017 at 9:32 AM, "Maurice Dake via arm-allstar" <
arm-allstar at hamvoip.org> wrote:
> To maintain the latest database of Allstar Call Signs do we just have to
> re-run the write_node_callsign.tar on a routine basis and write it? Is
> there an automated way to maintain the latest database.
> _______________________________________________
>
> 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: 10
Date: Thu, 20 Apr 2017 11:14:28 -0400
From: Doug Crompton <wa3dsp at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] AutoSky, A Skywarn script for hamvoip
Message-ID:
<CAMp6vsvaNcNirb9ccjdNY6CUwGBgrRtxv-jPMJkGq8oefpBeLw at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Yes, create the on and off DTMF functions as described in the howto. Then
add this to the favorites.ini in the /srv/http/supermon directory. You can
use the supermon editor to do this.
label[] = "AutoSky ON"
cmd[] = "rpt fun %node% *880"
label[] = "AutoSky OFF"
cmd[] = "rpt fun %node% *881"
The function numbers 880, 881 would match the ones you setup in your
rpt.conf file functions section to do the commands.
*73 Doug*
*WA3DSP*
*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
On Thu, Apr 20, 2017 at 10:13 AM, "Justin Reed via arm-allstar" <
arm-allstar at hamvoip.org> wrote:
> Ok, then my next question would be can the enable/disable scripts be
> called from within the allmon2 controlpanel.ini.php file?
> What would the syntax of that look like?
>
> We had a severe T-storm watch and several warnings last night and the
> alerts worked as advertised!
>
> Thanks!
> Justin
>
>
> On 4/19/2017 11:59 PM, "Doug Crompton via arm-allstar" wrote:
>
>> Justin,
>>
>> The "lead-in" character for Allstar is '*' This can be changed to any
>> character in rpt.conf BUT whatever it is changed to cannot be part of the
>> remaining sequence. So you could change it to A or B or C or D on DTMF so
>> everything would then be preceded by A - A1234 etc. Theoretically you
>> could change it to say a '%' symbol but then DTMF would not work while you
>> could command with the client.
>>
>> So the answer is NO you cannot just type 1234 if that is what the function
>> is defined as. Also you cannot define codes that are already defined or
>> within the range of already defined. The 8xx, 9xx are typically user
>> defined.
>>
>>
>> *73 Doug*
>>
>> *WA3DSP*
>>
>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>
>> On Wed, Apr 19, 2017 at 8:11 PM, "Justin Reed via arm-allstar" <
>> arm-allstar at hamvoip.org> wrote:
>>
>> Doug,
>>> Is there any way to disable/enable AutoSky using a DTMF sequence that
>>> doesn't begin with *?
>>> For example, a 4 digit DTMF code like 1234.
>>>
>>> I'm not sure how to remove the leading * as a requirement.
>>>
>>> Thanks,
>>> Justin
>>> NV8Q
>>>
>>> _______________________________________________
>>>
>>> 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
>>
>
>
> _______________________________________________
>
> 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 35, Issue 25
*******************************************
More information about the arm-allstar
mailing list