[arm-allstar] ARM-allstar Digest, Vol 66, Issue 37
Ivan Valentin - KP3IV
kp3iv.ivan at gmail.com
Fri Nov 22 10:56:58 EST 2019
Hi, Carlos KP4CA
Previously I used that Script, But it only works for allstar nodes. It
doesn't work for echolink nodes.
Very grateful, I'll keep looking to see if anything comes up.
73
Ivan KP3IV
-----Original Message-----
From: ARM-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of
arm-allstar-request at hamvoip.org
Sent: Friday, November 22, 2019 12:08 AM
To: arm-allstar at hamvoip.org
Subject: ARM-allstar Digest, Vol 66, Issue 37
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. OpenVPN (Mobile) and Personal VPN Server using Asus router @
home (Travis French)
2. Re: Update V1.6-06 released (Brad Trogdon)
3. Re: Update V1.6-06 released (Brad Trogdon)
4. Yellow Box & I-Phone (Ron Gilson)
5. Ref: Echolink Callsign Identification (Ivan Valentin - KP3IV)
6. Re: Ref: Echolink Callsign Identification (Carlos Minguela)
7. Re: Ref: Echolink Callsign Identification (Doug Crompton)
8. Re: Ref: Echolink Callsign Identification (Mike Sullivan)
----------------------------------------------------------------------
Message: 1
Date: Thu, 21 Nov 2019 18:46:36 +0000
From: Travis French <tfrench at pcb.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: [arm-allstar] OpenVPN (Mobile) and Personal VPN Server using
Asus router @ home
Message-ID: <1B4148B7B9EB4E48A67EBB5324222C73B07257F3 at NYDMS11.pcb.com>
Content-Type: text/plain; charset="utf-8"
Good Afternoon,
I periodically read about people referencing the use of a VPN and from what
I am gathering, this is allowing them to make their mobile node visible so
that it can be connected to. Correct me if I am wrong.
I have OpenVPN capability through my ASUS router at home which works great
already and allows me access to my home network. I guess I am having trouble
even after reading through the OpenVPN documentation on how to set this up
so that my mobile node can use this VPN and instead of seeing my network be
seen by the internet. Again, am I wrong in thinking that this is even
possible?
My questions:
Has anyone down this using the VPN server in their home router?
Do I need to run a different type of VPN server or standalone server on
another pi?
Is setting up a home server a waste of time in lieu of a commercial VPN
service from a performance perspective?
Once set up, can I assume that my mobile node then have a static IP address
that would be my home IP on a different port?
I was wondering is someone could point me to a resource that could help me
answer some of these questions and/or steer me in the direction of a setup
guide?
Thank you in advance,
Travis K2PCB
------------------------------
Message: 2
Date: Thu, 21 Nov 2019 16:44:04 -0500
From: Brad Trogdon <Brad at trogdon.org>
To: arm-allstar at hamvoip.org
Subject: Re: [arm-allstar] Update V1.6-06 released
Message-ID:
<CAKAuT6Zhwz0thG0Odvuyz0xd9gZihwwc0P3rboLx2QtoZkUixQ at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
>
> Question,
>
I recompiled and replaced nptee on two nodes. one is working just fine..
The other will not restart its feed.
I reverted back to the original nptee (same results) When I manually run the
command line it scrolls constantly the below message:
*ezstream: Streaming from standard input*
Also /tmp/status file contains: Could not find "/tmp/outsound/pipe1".
Initial install I had to manually create outsound directory. Now even
when i create it gets deleted.
Any pointers?
-Brad
W4INT
>
> ------------------------------
>
> Message: 7
> Date: Wed, 20 Nov 2019 21:15:23 -0500 (EST)
> From: David McGough <kb4fxc at inttek.net>
> To: "\"Patrick Perdue via ARM-allstar\"" <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] Update V1.6-06 released
> Message-ID:
> <Pine.LNX.4.44.1911202053460.27393-100000 at goliath.inttek.net>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>
> Interesting. While I went ahead and released that code, it hasn't been
> exhaustively tested. Is this problem showing up on RPi (HamVoIP) or a
> VPS?
>
> BTW, I did find one bug after the initial release, which has been
> corrected. The code is here:
>
> https://hamvoip.org/downloads/nptee-v-0.3.tgz
>
> I'll test nptee here carefully in the next few days.
>
> 73, David KB4FXC
>
>
> On Wed, 20 Nov 2019, "Patrick Perdue via ARM-allstar" wrote:
>
> > I've been streaming to two servers using ntpee since last night, and
> > I've discovered an interesting thing.
> >
> > It seems that, every few minutes, now that the stream has been
> > running for a while, there is some kind of buffer under-rungoing on.
> >
> > Using my own icecast server at 64 kbps 8000 hz mp3, I noticed that
> > the stream gets closer and closer to real time as time goes on.
> > Eventually, it hits a certain point, and breaks down, like a really
> > bad time compression algorithm, then recycles again, and all is well for
a while.
> > Sometimes, it seems like the buffer is flushed at the next
> > transmission, but maybe that's coincidence.
> >
> > This happens at the same point in the stream from rpt.app for my
> > broadcastify feed and my icecast mountpoint, taking into account the
> > buffer time of Broadcastify. Thus, I can rule out buffering between
> > my client and the stream itself.
> >
> > Later, when I have time, I'm going to try running something through
> > ntpee with time code to see if it is actually dropping samples.
> >
> >
> > On 11/20/2019 1:11 PM, "Doug Crompton via ARM-allstar" wrote:
> >
> > > An update version 1.6-06 was released today. It includes the
> > > binary
> nptee
> > > (Named Pipe Tee) and a howto at hamvoip.org on its use. This SW
> > > allows multiple streams from Allstar (outstream command in
> > > rpt.conf) to
> external
> > > code such as lame and ezstream. It also decouples the external
> > > program
> from
> > > Allstar so that no interaction exists when restarting or rebooting.
> > >
> > > Also included is a new script called - echolink_permit_deny
> > >
> > > This script allows you to change the permit or deny calls for
> > > Echolink without directly editing the config file. This still
> > > requires an
> Allstar
> > > restart to take effect but makes it easier and less error prone to
> make the
> > > changes. This is one step towards a change In the near future
> > > where the Echolink permits and denies will be defined through the
> > > Asterisk
> database
> > > in a similar way as the ban/allows are now for Allstar. Once it is
> > > done this way the changes will be immediate with no restart required.
> > >
> > > And finally the sleep was updated in astdb.php for up to 1800
> > > random seconds, rather than minutes. This should further ease the
> > > loading on
> the
> > > hosting servers.
> > > _______________________________________________
> > >
> > > 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/4 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/4 web page - http://hamvoip.org
> >
>
>
>
>
------------------------------
Message: 3
Date: Thu, 21 Nov 2019 17:11:10 -0500
From: Brad Trogdon <Brad at trogdon.org>
To: arm-allstar at hamvoip.org
Subject: Re: [arm-allstar] Update V1.6-06 released
Message-ID:
<CAKAuT6aASY2mP15o3b1WT_pGQzccsU6S6X-Dg_fm4O4UxK63yA at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
As always an epiphany strikes the second you select ENTER..
I figured out the issue. for some reason the file was not set correctly..
Updated to 0755 and problems resolved.
Hope my tid-bit may help others.
Have a great day!
-Brad
W4INT
On Thu, Nov 21, 2019 at 4:44 PM Brad Trogdon <Brad at trogdon.org> wrote:
> Question,
>>
>
> I recompiled and replaced nptee on two nodes. one is working just fine..
> The other will not restart its feed.
>
> I reverted back to the original nptee (same results) When I manually
> run the command line it scrolls constantly the below message:
>
> *ezstream: Streaming from standard input*
>
> Also /tmp/status file contains: Could not find "/tmp/outsound/pipe1".
>
> Initial install I had to manually create outsound directory. Now even
> when i create it gets deleted.
>
> Any pointers?
>
> -Brad
> W4INT
>
>>
>> ------------------------------
>>
>> Message: 7
>> Date: Wed, 20 Nov 2019 21:15:23 -0500 (EST)
>> From: David McGough <kb4fxc at inttek.net>
>> To: "\"Patrick Perdue via ARM-allstar\"" <arm-allstar at hamvoip.org>
>> Subject: Re: [arm-allstar] Update V1.6-06 released
>> Message-ID:
>> <Pine.LNX.4.44.1911202053460.27393-100000 at goliath.inttek.net>
>> Content-Type: TEXT/PLAIN; charset=US-ASCII
>>
>>
>> Interesting. While I went ahead and released that code, it hasn't
>> been exhaustively tested. Is this problem showing up on RPi (HamVoIP)
>> or a VPS?
>>
>> BTW, I did find one bug after the initial release, which has been
>> corrected. The code is here:
>>
>> https://hamvoip.org/downloads/nptee-v-0.3.tgz
>>
>> I'll test nptee here carefully in the next few days.
>>
>> 73, David KB4FXC
>>
>>
>> On Wed, 20 Nov 2019, "Patrick Perdue via ARM-allstar" wrote:
>>
>> > I've been streaming to two servers using ntpee since last night,
>> > and I've discovered an interesting thing.
>> >
>> > It seems that, every few minutes, now that the stream has been
>> > running for a while, there is some kind of buffer under-rungoing on.
>> >
>> > Using my own icecast server at 64 kbps 8000 hz mp3, I noticed that
>> > the stream gets closer and closer to real time as time goes on.
>> > Eventually, it hits a certain point, and breaks down, like a really
>> > bad time compression algorithm, then recycles again, and all is
>> > well for a
>> while.
>> > Sometimes, it seems like the buffer is flushed at the next
>> transmission,
>> > but maybe that's coincidence.
>> >
>> > This happens at the same point in the stream from rpt.app for my
>> > broadcastify feed and my icecast mountpoint, taking into account
>> > the buffer time of Broadcastify. Thus, I can rule out buffering
>> > between my client and the stream itself.
>> >
>> > Later, when I have time, I'm going to try running something through
>> > ntpee with time code to see if it is actually dropping samples.
>> >
>> >
>> > On 11/20/2019 1:11 PM, "Doug Crompton via ARM-allstar" wrote:
>> >
>> > > An update version 1.6-06 was released today. It includes the
>> > > binary
>> nptee
>> > > (Named Pipe Tee) and a howto at hamvoip.org on its use. This SW
>> allows
>> > > multiple streams from Allstar (outstream command in rpt.conf) to
>> external
>> > > code such as lame and ezstream. It also decouples the external
>> program from
>> > > Allstar so that no interaction exists when restarting or rebooting.
>> > >
>> > > Also included is a new script called - echolink_permit_deny
>> > >
>> > > This script allows you to change the permit or deny calls for
>> > > Echolink without directly editing the config file. This still
>> > > requires an
>> Allstar
>> > > restart to take effect but makes it easier and less error prone
>> > > to
>> make the
>> > > changes. This is one step towards a change In the near future
>> > > where
>> the
>> > > Echolink permits and denies will be defined through the Asterisk
>> database
>> > > in a similar way as the ban/allows are now for Allstar. Once it
>> > > is
>> done
>> > > this way the changes will be immediate with no restart required.
>> > >
>> > > And finally the sleep was updated in astdb.php for up to 1800
>> > > random seconds, rather than minutes. This should further ease the
>> > > loading on
>> the
>> > > hosting servers.
>> > > _______________________________________________
>> > >
>> > > 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/4 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/4 web page - http://hamvoip.org
>> >
>>
>>
>>
>>
------------------------------
Message: 4
Date: Thu, 21 Nov 2019 20:15:03 -0500
From: Ron Gilson <wa2wwk at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: [arm-allstar] Yellow Box & I-Phone
Message-ID:
<CAG36ZF6v5gnX869=WyanBN9ir6MciDtWn_6N_VyM60W8L9dTPQ at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
I'm using my node with a network cable, which works great. I then change to
iPhone using item 7 then remove the cable. Everything works until I shut
down the node. Not sure how to have the YB come up tethered wirelessly to
the phone on next power-up? I have only the i-phone name and passcode no
other WiFi devices in menu item 7. Have I missed something during set-up?
Once I mount the YB in the car, I'll not have a computer handy to program to
the phone mode. I'm using a power down
board so Pi should be shutting down correctly. 73's Ron
------------------------------
Message: 5
Date: Thu, 21 Nov 2019 21:55:56 -0400
From: "Ivan Valentin - KP3IV" <kp3iv.ivan at gmail.com>
To: <arm-allstar at hamvoip.org>
Subject: [arm-allstar] Ref: Echolink Callsign Identification
Message-ID: <063501d5a0d7$fc3bfbe0$f4b3f3a0$@gmail.com>
Content-Type: text/plain; charset="US-ASCII"
Hi, All
I am the Hamvoip Image in my Raspberry Pi 3B
The system is working very well. I can tell if there is any script or
configuration that can be seen people who connect to the Echolink but
instead of being the number of node to see them that you see the callsign
????
There's something for that please.
Thank you
73
Ivan KP3IV
------------------------------
Message: 6
Date: Fri, 22 Nov 2019 03:29:19 +0000 (UTC)
From: Carlos Minguela <minguela at yahoo.com>
To: Ivan Valentin - KP3IV via ARM-allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] Ref: Echolink Callsign Identification
Message-ID: <1183853435.2505942.1574393359135 at mail.yahoo.com>
Content-Type: text/plain; charset=UTF-8
Hi Ivan:
There is a script wrote by WA3DSP that could help you.? It works for
Allstar, but maybe it works for Echolink.
https://4x5mg.net/2017/10/21/callsigns-instead-node-numbers-allstar/?fbclid=
IwAR319CNZTDWeO4aWZ-Utnv0MYZkwH44pHtJX_WBcqKFUHxQ1MfCRWyfqYC0
73
CarlosKP4CA
______________________________________
Carlos A. Minguela
Visit my Flickr Gallery Photos at:
http://www.flickr.com/photos/minguela/
On Thursday, November 21, 2019, 11:01:03 PM AST, Ivan Valentin - KP3IV
via ARM-allstar <arm-allstar at hamvoip.org> wrote:
Hi, All
I am the Hamvoip Image in my Raspberry Pi 3B
The system is working very well.? I can tell if there is any script or
configuration that can be seen people who connect to the Echolink but
instead of being the number of node to see them that you see the callsign
????
There's something for that please.
Thank you
73
Ivan KP3IV
_______________________________________________
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/4 web page - http://hamvoip.org
------------------------------
Message: 7
Date: Thu, 21 Nov 2019 23:07:22 -0500
From: Doug Crompton <wa3dsp at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] Ref: Echolink Callsign Identification
Message-ID:
<CAMp6vsumwn5kwPoyiKtHntWVyu=bX8+UPMo_Dpsk6Yzt4G141w at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Echolink is identified with lsnodes or supermon. Both are part of the
hamvoip package and detailed in howto's at hamvoip.org
*73 Doug*
*WA3DSP*
*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
On Thu, Nov 21, 2019 at 10:00 PM "Ivan Valentin - KP3IV via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:
> Hi, All
>
>
>
> I am the Hamvoip Image in my Raspberry Pi 3B
>
>
>
> The system is working very well. I can tell if there is any script or
> configuration that can be seen people who connect to the Echolink but
> instead of being the number of node to see them that you see the
> callsign ????
> There's something for that please.
>
>
>
> Thank you
>
> 73
>
> Ivan KP3IV
>
> _______________________________________________
>
> 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/4 web page - http://hamvoip.org
>
------------------------------
Message: 8
Date: Thu, 21 Nov 2019 22:54:57 -0500
From: Mike Sullivan <kn4imu at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] Ref: Echolink Callsign Identification
Message-ID:
<CAKoU=5fbsijr9FF1Wu33jaXc65H2X+QMEGx=cp5ReTzrMWdz+w at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Carlos, he is referring to only the node numbers showing up on echolink in
the description.
Mike
On Thu, Nov 21, 2019 at 22:35 "Carlos Minguela via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:
> Hi Ivan:
> There is a script wrote by WA3DSP that could help you. It works for
> Allstar, but maybe it works for Echolink.
>
> https://4x5mg.net/2017/10/21/callsigns-instead-node-numbers-allstar/?f
> bclid=IwAR319CNZTDWeO4aWZ-Utnv0MYZkwH44pHtJX_WBcqKFUHxQ1MfCRWyfqYC0
> 73
> CarlosKP4CA
>
>
>
>
> ______________________________________
> Carlos A. Minguela
> Visit my Flickr Gallery Photos at:
> http://www.flickr.com/photos/minguela/
>
> On Thursday, November 21, 2019, 11:01:03 PM AST, Ivan Valentin -
> KP3IV via ARM-allstar <arm-allstar at hamvoip.org> wrote:
>
> Hi, All
>
>
>
> I am the Hamvoip Image in my Raspberry Pi 3B
>
>
>
> The system is working very well. I can tell if there is any script or
> configuration that can be seen people who connect to the Echolink but
> instead of being the number of node to see them that you see the
> callsign ????
> There's something for that please.
>
>
>
> Thank you
>
> 73
>
> Ivan KP3IV
>
> _______________________________________________
>
> 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/4 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/4 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 66, Issue 37
*******************************************
More information about the ARM-allstar
mailing list