[arm-allstar] ARM-allstar Digest, Vol 56, Issue 24

w7jca w7jca at yahoo.com
Mon Jan 14 14:05:01 EST 2019


Thanks for the info but I still cannot get the phone to register. Can someone please provide the stanza that I need to setup? I am kinda new to asterisk and probably doing something wrong. Any help would really be appreciated.


Sent via the Samsung Galaxy, an AT&T 4G LTE smartphone
-------- Original message --------From: arm-allstar-request at hamvoip.org Date: 1/11/19  4:57 PM  (GMT-08:00) To: arm-allstar at hamvoip.org Subject: ARM-allstar Digest, Vol 56, Issue 24 
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: One of two USB URIs dropping off (Justin Reed)
   2. Re: Important dtmf command - hamvoip repeater (Dennis Ramos)
   3. Re: One of two USB URIs dropping off (Randy Neals)
   4. Controlling CTCSS from COS (LaRoy McCann)
   5. Re: SIP telephone (Danny K5CG)
   6. Re: SIP telephone (Doug Crompton)


----------------------------------------------------------------------

Message: 1
Date: Fri, 11 Jan 2019 13:56:37 -0600
From: Justin Reed <celltech161 at gmail.com>
To: Randy Neals <randy at neals.ca>
Cc: ARM Allstar <arm-allstar at hamvoip.org>, Doug Crompton
	<wa3dsp at gmail.com>
Subject: Re: [arm-allstar] One of two USB URIs dropping off
Message-ID: <C7ABC5B4-EC29-458F-9C2F-28FFBAB3BFE5 at gmail.com>
Content-Type: text/plain;	charset=utf-8

It?s possible. The Pi 3B+ by itself is pushing the upper limit of micro USB?s continuous current handling capability. It?s going to be interesting to see how they address this in the next gen which we assume will be even more hungry.

Sent from my iPhone

> On Jan 11, 2019, at 1:48 PM, Randy Neals <randy at neals.ca> wrote:
> 
> 
> I added a USB thumb drive for backing up the Pi when I reinstalled/rebuilt.
> 
> Making a leap here, but possibly the USB Flash drive is drawing enough extra load, along with two DML URIs to exceed 5VDC capability of RPI USB power capability.
> 
> Will remove USB flash and reboot.
> 
> Randy
> 
>> On Fri, Jan 11, 2019 at 2:04 PM Randy Neals <randy at neals.ca> wrote:
>> Thanks to both..
>> 
>> Are you familiar with any Pi/Linux debug for power or  USB?
>> 
>> Something I could send to a terminal or file to provide some clues?
>> 
>>> On Fri, Jan 11, 2019 at 12:34 PM "Doug Crompton via ARM-allstar" <arm-allstar at hamvoip.org> wrote:
>>> I would agree with that but he did say he tried a different supply.
>>> 
>>> 
>>> *73 Doug*
>>> 
>>> *WA3DSP*
>>> 
>>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>> 
>>> On Fri, Jan 11, 2019 at 12:00 PM Justin Reed <celltech161 at gmail.com> wrote:
>>> 
>>> > I?m going to take a stab and suggest that your Pi power supply is
>>> > under-sized for two fobs. You?ll need a minimum of 3000 mAh at 5.1 VDC. Any
>>> > time I see random issues with a Pi it?s power supply related 100% of the
>>> > time, every time.
>>> >
>>> > Sent from my iPhone
>>> >
>>> > > On Jan 11, 2019, at 10:40 AM, Doug Crompton via ARM-allstar <
>>> > arm-allstar at hamvoip.org> wrote:
>>> > >
>>> > > Randy,
>>> > >
>>> > >   I run very few if any Pi's here with more than one USB FOB so I have
>>> > > never experienced that but I know many others are using multiple ports.
>>> > > Have you tried a different Pi? What error messages are you getting in the
>>> > > client when this happens?
>>> > >
>>> > >
>>> > > *73 Doug*
>>> > >
>>> > > *WA3DSP*
>>> > >
>>> > > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>> > >
>>> > > On Fri, Jan 11, 2019 at 10:08 AM "Randy Neals via ARM-allstar" <
>>> > > arm-allstar at hamvoip.org> wrote:
>>> > >
>>> > >> Hi All,
>>> > >>
>>> > >> I have a fresh HamVoip install on a RPi3.
>>> > >> I started with one node configured, then plugged in a second USB URI and
>>> > >> configured the second node.
>>> > >>
>>> > >> After about 15-20 minutes, one of the two USB URIs will stop working.
>>> > >> (It could be either one, not consistent) ie: Heartbeat led stops
>>> > blinking
>>> > >> on URI.
>>> > >>
>>> > >> I've tried a couple of different power supplies on the RPi.
>>> > >> Same results.
>>> > >>
>>> > >> I've verified my config files.
>>> > >> I'm using usb / usb1 as the reference names for each node.
>>> > >>
>>> > >> I've done the simpleusb-tune-menu and wrote the config.
>>> > >> Verified that the simple usb files have the USB hardware address.
>>> > >>
>>> > >> It feel like this is a USB subsystem issue in the Rpi/Linux.
>>> > >> Not really sure what I might do next to test/isolate.
>>> > >>
>>> > >> [root at VE3RTR etc]# lsusb
>>> > >>
>>> > >> Bus 001 Device 006: ID 18a5:0251 Verbatim, Ltd
>>> > >>
>>> > >> Bus 001 Device 005: ID 0d8c:013a C-Media Electronics, Inc.
>>> > >>
>>> > >> Bus 001 Device 004: ID 0d8c:013a C-Media Electronics, Inc.
>>> > >>
>>> > >> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
>>> > SMSC9512/9514
>>> > >> Fast Ethernet Adapter
>>> > >>
>>> > >> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
>>> > >>
>>> > >> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> > >>
>>> > >>
>>> > >> simpleusb_tune_usb.conf
>>> > >>
>>> > >> [usb]
>>> > >>
>>> > >> ; name=usb
>>> > >>
>>> > >> ; devicenum=1
>>> > >>
>>> > >> devstr=1-1.3:1.0
>>> > >>
>>> > >> rxmixerset=140
>>> > >>
>>> > >> txmixaset=290
>>> > >>
>>> > >> txmixbset=0
>>> > >>
>>> > >>
>>> > >> simpleusb_tune_usb1.conf
>>> > >>
>>> > >> [usb1]
>>> > >>
>>> > >> ; name=usb1
>>> > >>
>>> > >> ; devicenum=0
>>> > >>
>>> > >> devstr=1-1.2:1.0
>>> > >>
>>> > >> rxmixerset=140
>>> > >>
>>> > >> txmixaset=290
>>> > >>
>>> > >> txmixbset=0
>>> > >>
>>> > >> Thanks,
>>> > >> Randy W3RWN
>>> > >> _______________________________________________
>>> > >>
>>> > >> 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
>> -- 
>> Sent from mobile.
> -- 
> Sent from mobile.


------------------------------

Message: 2
Date: Fri, 11 Jan 2019 19:56:52 +0000
From: Dennis Ramos <m0tfg at dx1mk.org>
To: ARM Allstar <arm-allstar at hamvoip.org>, "\"Doug Crompton via
	ARM-allstar\"" <arm-allstar at hamvoip.org>
Cc: Doug Crompton <wa3dsp at gmail.com>
Subject: Re: [arm-allstar] Important dtmf command - hamvoip repeater
Message-ID: <8C336840-798E-4765-B8E8-760D002A366C at dx1mk.org>
Content-Type: text/plain; charset=utf-8

Doug first of all thank you very for your never ending support. 

I have some question about remote dtmf commands. 

Let's say I have two nodes, node 22222 and node 44444, they have different public ip - different locations, and they are permanent link together by adding *3.... On rpt.conf.

Now my dvswitch mobile is connected to node 44444 and i would like to send a command from dvswitch mobile to 22222 via node 44444. Is it posble? How?


Thanks in advance

73

De dennis/m0tfg 


On 10 January 2019 23:28:27 GMT, "Doug Crompton via ARM-allstar" <arm-allstar at hamvoip.org> wrote:
>Dennis,
>
>This depends on what you want to secure. Most use it as it stands. What
>is it you want to secure? Only local users can control your system via
>DTMF. Usually you usually should not change the common
>connect/disconnect
>commands because they are well known but you can if you need to. Just
>look
>through the functions stanza in rpt.conf and see what functions you may
>NOT
>want users to have the ability to access. You can either make the DTMF
>code
>different or comment out the command altogether. Just remember that
>changing DTMF is not really secure as someone could figure it out.
>
>You can make commands to your server very secure by using codes out of
>the
>DTMF range. So for instance
>
>A1= some command
>
>Could be
>
>E1= some command
>
>In this case your could only exercise this command via SSH or Supermon
>login.
>
>
>*73 Doug*
>
>*WA3DSP*
>
>*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>On Thu, Jan 10, 2019 at 5:50 PM "Dennis Ramos via ARM-allstar" <
>arm-allstar at hamvoip.org> wrote:
>
>> Hello Guys, I just wonder what are the important dtmf commands that
>MUST
>> need to edit/change from default for securing the hamvoip or
>allstarlink
>> repeater.
>>
>> Cheers
>>
>> De Dennis/m0tfg
>>
>> Sent from my iPad
>> _______________________________________________
>>
>> 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: Fri, 11 Jan 2019 16:45:02 -0500
From: Randy Neals <randy at neals.ca>
To: Justin Reed <celltech161 at gmail.com>
Cc: ARM Allstar <arm-allstar at hamvoip.org>, Doug Crompton
	<wa3dsp at gmail.com>
Subject: Re: [arm-allstar] One of two USB URIs dropping off
Message-ID:
	<CAHDTD7pfBBpn3qRQWiwNtuRc+9vKK258bj32ht7Uwi6vjfqY3Q at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

My ?remote-hands? Ham friend made a trip up the hill to the transmitter
building, powered down the Pi, pulled the 32 GB Thumb Drive and powered the
Pi back up.

I?ll report back to list what the results are in a few hours. (It was
between 10 minutes and 2 hours to fail previously)

*If this solves the problem, I will be shocked. (No pun intended).  But
certainly appreciative of the collective list wisdom.

Randy, W3RWN

On Fri, Jan 11, 2019 at 2:56 PM Justin Reed <celltech161 at gmail.com> wrote:

> It?s possible. The Pi 3B+ by itself is pushing the upper limit of micro
> USB?s continuous current handling capability. It?s going to be interesting
> to see how they address this in the next gen which we assume will be even
> more hungry.
>
> Sent from my iPhone
>
> On Jan 11, 2019, at 1:48 PM, Randy Neals <randy at neals.ca> wrote:
>
>
> I added a USB thumb drive for backing up the Pi when I reinstalled/rebuilt.
>
> Making a leap here, but possibly the USB Flash drive is drawing enough
> extra load, along with two DML URIs to exceed 5VDC capability of RPI USB
> power capability.
>
> Will remove USB flash and reboot.
>
> Randy
>
> On Fri, Jan 11, 2019 at 2:04 PM Randy Neals <randy at neals.ca> wrote:
>
>> Thanks to both..
>>
>> Are you familiar with any Pi/Linux debug for power or  USB?
>>
>> Something I could send to a terminal or file to provide some clues?
>>
>> On Fri, Jan 11, 2019 at 12:34 PM "Doug Crompton via ARM-allstar" <
>> arm-allstar at hamvoip.org> wrote:
>>
>>> I would agree with that but he did say he tried a different supply.
>>>
>>>
>>> *73 Doug*
>>>
>>> *WA3DSP*
>>>
>>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>>
>>> On Fri, Jan 11, 2019 at 12:00 PM Justin Reed <celltech161 at gmail.com>
>>> wrote:
>>>
>>> > I?m going to take a stab and suggest that your Pi power supply is
>>> > under-sized for two fobs. You?ll need a minimum of 3000 mAh at 5.1
>>> VDC. Any
>>> > time I see random issues with a Pi it?s power supply related 100% of
>>> the
>>> > time, every time.
>>> >
>>> > Sent from my iPhone
>>> >
>>> > > On Jan 11, 2019, at 10:40 AM, Doug Crompton via ARM-allstar <
>>> > arm-allstar at hamvoip.org> wrote:
>>> > >
>>> > > Randy,
>>> > >
>>> > >   I run very few if any Pi's here with more than one USB FOB so I
>>> have
>>> > > never experienced that but I know many others are using multiple
>>> ports.
>>> > > Have you tried a different Pi? What error messages are you getting
>>> in the
>>> > > client when this happens?
>>> > >
>>> > >
>>> > > *73 Doug*
>>> > >
>>> > > *WA3DSP*
>>> > >
>>> > > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio
>>> >*
>>> > >
>>> > > On Fri, Jan 11, 2019 at 10:08 AM "Randy Neals via ARM-allstar" <
>>> > > arm-allstar at hamvoip.org> wrote:
>>> > >
>>> > >> Hi All,
>>> > >>
>>> > >> I have a fresh HamVoip install on a RPi3.
>>> > >> I started with one node configured, then plugged in a second USB
>>> URI and
>>> > >> configured the second node.
>>> > >>
>>> > >> After about 15-20 minutes, one of the two USB URIs will stop
>>> working.
>>> > >> (It could be either one, not consistent) ie: Heartbeat led stops
>>> > blinking
>>> > >> on URI.
>>> > >>
>>> > >> I've tried a couple of different power supplies on the RPi.
>>> > >> Same results.
>>> > >>
>>> > >> I've verified my config files.
>>> > >> I'm using usb / usb1 as the reference names for each node.
>>> > >>
>>> > >> I've done the simpleusb-tune-menu and wrote the config.
>>> > >> Verified that the simple usb files have the USB hardware address.
>>> > >>
>>> > >> It feel like this is a USB subsystem issue in the Rpi/Linux.
>>> > >> Not really sure what I might do next to test/isolate.
>>> > >>
>>> > >> [root at VE3RTR etc]# lsusb
>>> > >>
>>> > >> Bus 001 Device 006: ID 18a5:0251 Verbatim, Ltd
>>> > >>
>>> > >> Bus 001 Device 005: ID 0d8c:013a C-Media Electronics, Inc.
>>> > >>
>>> > >> Bus 001 Device 004: ID 0d8c:013a C-Media Electronics, Inc.
>>> > >>
>>> > >> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
>>> > SMSC9512/9514
>>> > >> Fast Ethernet Adapter
>>> > >>
>>> > >> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
>>> SMC9514 Hub
>>> > >>
>>> > >> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> > >>
>>> > >>
>>> > >> simpleusb_tune_usb.conf
>>> > >>
>>> > >> [usb]
>>> > >>
>>> > >> ; name=usb
>>> > >>
>>> > >> ; devicenum=1
>>> > >>
>>> > >> devstr=1-1.3:1.0
>>> > >>
>>> > >> rxmixerset=140
>>> > >>
>>> > >> txmixaset=290
>>> > >>
>>> > >> txmixbset=0
>>> > >>
>>> > >>
>>> > >> simpleusb_tune_usb1.conf
>>> > >>
>>> > >> [usb1]
>>> > >>
>>> > >> ; name=usb1
>>> > >>
>>> > >> ; devicenum=0
>>> > >>
>>> > >> devstr=1-1.2:1.0
>>> > >>
>>> > >> rxmixerset=140
>>> > >>
>>> > >> txmixaset=290
>>> > >>
>>> > >> txmixbset=0
>>> > >>
>>> > >> Thanks,
>>> > >> Randy W3RWN
>>> > >> _______________________________________________
>>> > >>
>>> > >> 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
>>
>> --
>> Sent from mobile.
>>
> --
> Sent from mobile.
>
> --
Sent from mobile.


------------------------------

Message: 4
Date: Fri, 11 Jan 2019 15:43:33 -0600
From: LaRoy McCann <laroy.mccann at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: [arm-allstar] Controlling CTCSS from COS
Message-ID:
	<CAF6L7xYmaatzxRbKSavzd5pD-dyBC96q_8rKUrkdW0_-n48o2w at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

I have a location with 1 repeater and 1 rf link and no internet. These are
controlled from the same hamnoip controller with 2 dmk uri's.

I want to control the link CTCSS based on the repeater COS so I don't get
the link transmit id coming across all the other repeaters that are linked
thru this rf link.  I really don't want to hardwire from the repeater to
the link.  I would like to control a GPIO bit on the link uri based on the
COS of the repeater.

I'm sure there are several ways to do this.  I saw the txctcss function but
that looks like it only works on a single node, no option to give a node
number.  I am now looking at the COS_annunciate.sh script which I think
would work using the events subsystem.  I am wondering does this process
fast enough to reliably control the CTCSS?

Does anyone have any better ways to do this?

Thanks,

LaRoy - K5TW


------------------------------

Message: 5
Date: Fri, 11 Jan 2019 14:39:27 -0800 (PST)
From: Danny K5CG <k5cg at hamoperator.org>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] SIP telephone
Message-ID:
	<1442679839.387031.1547246367685.JavaMail.zimbra at siminiuk.com>
Content-Type: text/plain; charset=utf-8

John,

I just installed a Grandstream GXP1625 the other day and had similar issues.

The key for me was to enable the SIP module...
nano /etc/asterisk.modules.conf

Change
noload=chan_sip.so
-to-
load=chan_sip.so

Then Restart Asterisk...
astres.sh

You need a stanza in sip.conf and extensions.conf for the SIP phone.

When it registers you can also see it here...
asterisk -rvv

NODE#*CLI> sip show users
Username                   Secret           Accountcode      Def.Context      ACL  NAT
1000                       <secret>                          internal         No   RFC3581

Your Username and Default Context will be specific to your configuration.

Danny
K5CG



------------------------------

Message: 6
Date: Fri, 11 Jan 2019 19:56:52 -0500
From: Doug Crompton <wa3dsp at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] SIP telephone
Message-ID:
	<CAMp6vstUsq3qFvB1G9+_CoycJL4jZSN_ezCRz6qVe5vP7AstkQ at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

Actually all you need to do is put a semicolon before the noload commenting
it out.

Also be aware that sip (port 5060) is VERY insecure so don't port forward
it without some firewall'ing. You will get hammered with login requests. In
your case if it is just local on your LAN you would not need to do that.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Fri, Jan 11, 2019 at 6:06 PM "Danny K5CG via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> John,
>
> I just installed a Grandstream GXP1625 the other day and had similar
> issues.
>
> The key for me was to enable the SIP module...
> nano /etc/asterisk.modules.conf
>
> Change
> noload=chan_sip.so
> -to-
> load=chan_sip.so
>
> Then Restart Asterisk...
> astres.sh
>
> You need a stanza in sip.conf and extensions.conf for the SIP phone.
>
> When it registers you can also see it here...
> asterisk -rvv
>
> NODE#*CLI> sip show users
> Username                   Secret           Accountcode      Def.Context
>     ACL  NAT
> 1000                       <secret>                          internal
>    No   RFC3581
>
> Your Username and Default Context will be specific to your configuration.
>
> Danny
> K5CG
>
> _______________________________________________
>
> 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 56, Issue 24
*******************************************


More information about the ARM-allstar mailing list