¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. DINAH
  2. Messages
Expanded Topics Messages Polls
Date
FW: [arm-allstar] MAJOR HamVoIP UPDATE 1.7.0-01 RELEASED

 

-----Original Message-----
From: ARM-allstar <arm-allstar-bounces@...> On Behalf Of "David
McGough via ARM-allstar"
Sent: December 25, 2021 3:17 PM
To: arm-allstar@...
Cc: David McGough <kb4fxc@...>
Subject: [arm-allstar] MAJOR HamVoIP UPDATE 1.7.0-01 RELEASED


Hi Everyone!


After about 1.5 years worth of development effort, I have just released a
MAJOR upgrade to the hamvoip-asterisk package. This package includes the
Asterisk/app_rpt software, which is the software that drives AllStar.

This is the biggest upgrade in at least a decade, with about 15,000 lines of
changed software!!

For hot-spot, repeater and node radio users, the most visible change will be
improved performance over the older software--meaning fewer crashes and
fewer audio pops and clicks.

Hub users still running older software will notice major stability
improvements. This software is currently in use on ALL the worlds biggest
AllStar hubs.

NOTE that if you're a user of Zoiper, DVSwitch Mobile, IAXRPT or other IAX
client software, these clients may NO LONGER CONNECT without a minor
configuration change on the HamVoIP node. As of this software release, the
IAX2 protocol has "call tokens" ENABLED. This is a VERY IMPORTANT security
mechanism, which classically was always forced off in the AllStar software.
This is now changed. To allow connections from software not supporting call
tokens, simply modify the iax.conf file incoming stanza.
For example:

; iax.conf
[iaxphone]
requirecalltoken=no


The whole list of changes is HUGE. Some of the highlights are:


* app_rpt module -- Massive refactoring of code. Complete overhaul of
internal data structures and statistical reporting code, including
the AMI interface. Old highly problematic "remote base" code
completely removed (a new remote base system is coming). Major
changes in process threads and priority, using work queues for
low-priority processing.

* Echolink driver -- The longstanding "garbled audio" issue is fixed!
Module unload and reload functions now work. Overall stability
greatly improved. Echolink node "can't connect" issues common
after the client software was just launched are fixed.

* VOTER channel driver -- Major AMI performance improvements. stability
improvements, including resolving some memory corruption bugs
and mutex issues.

* Many, many areas of the core asterisk code, including IAX2 and Dahdi --
Major stability improvements.

*** Please see a partial partial release comments list at the URL, below.
These are many of the changes since the last major
hamvoip-asterisk package release on June 01, 2020. Note that the
gaps in revisions are where I left out long/complex descriptions
of algorithm changes---these are too detailed to be relevant to
the general user.





MERRY CHRISTMAS!

73, David KB4FXC


_______________________________________________

ARM-allstar mailing list
ARM-allstar@...


Visit the BBB and RPi2/3/4 web page -

Can I use the DINAH to connect my G90 to a Raspberry Pi to run FT8?

 

Hello all,

I have a DINAH that I no longer use because I bought a Shari.

Can I use the DINAH to connect a XIEGU G90 to a raspberry pi to run FT8?

Thanks for any assistance and 73

Terry
KE8GXK?
Kenwood TMV-71 Data Port Woes

 

¿ªÔÆÌåÓý

Or rather, the connector on the cable is delicate!

?

I don¡¯t yet have a Dinah, but I have been running audio into the data port on my Kenwood TMV-71A for about a year, with great results. I actually have low bass, full range audio on FM simplex now.

?

But, be very very careful with those round connectors! I¡¯ve inadvertently damaged a couple, simply by moving things under the desk that tugged on the cable, causing it to come out of that data port on just enough of an angle to bend something. To the naked eye, I can¡¯t tell any difference, but it¡¯s just enough that the connector won¡¯t fully seat in the port now. Very frustrating!

?

I popped the cover off my radio to see if there was perhaps something connected to the back panel that may have shifted, but nope. Those connectors are in little blocks firmly attached to the board.

?

The next cable, and the Dinah when I get it, will both be taped down, to the desk, and cable taped to the wall at a few points along its length, to hopefully stop this from happening again.

?

I wish radio manufacturers would either use a DB9 or ¨C and this would be a shock! ¨C switch to USB for getting audio, PTT, COS etc. in and out of radios.

I now have no faith in these round connectors, which if I¡¯m not mistaken, go all the way back to the IBM PS/2.

?

OK, rant over.

?

73,

?

Chris

VE3RWJ

?
Re: DINAH and Kenwood Repeater

 

Thank you, It is clear what I need to do to make it work.


On Fri, Oct 1, 2021 at 10:40 AM Dan Keizer <ve4drk@...> wrote:
I've asked our fellow ham who made up the cables to provide the reference information.? I'm attaching a PDF that describes this.
We use this repeater on an allstar node as well.? We've also documented what we are going to use for an APRS connection as well - once I figure out the configuration on the direwolf...

Hope this helps.

73, Dan ve4drk


On Thu, Sep 30, 2021 at 8:52 PM rmatteucci . <rmatteucci@...> wrote:
Dan,
I guess I should have included that I am looking to use the DINAH for Allstar input.? What's still a bit confusing is on the DINAH you have pins for COS, GRND, PTT, which are easy to match but you also have pins for 9600, 1200, and Data IN - I am not sure which they would go to on the TKR-750.? I assume that DATA IN might be TX Audio input and either 9600 or 1200 will be RX Audio Output?? is this correct?
Thanks,
Bob N2TEV

On Wed, Sep 29, 2021 at 3:56 PM Dan Keizer <ve4drk@...> wrote:
We did this with a tkr750 - the specs were:

Diagram on Page 48 is as follows

Pin????? Purpose

7??????? Ground

9??????? TX audio input (voice) Input impedance: 600?

Coupling: AC coupling Deviation: 60% deviation (1kHz 280mVrms ¡À25mV input)

11?????? RX audio output (voice) Output impedance: 1k? or less

Coupling: AC coupling Output level: 360~440mVrms (standard modulation)

16????? PTT - ¡°L¡±: PTT on, ¡°H¡±: PTT off

17????? COS ¨C Squelch control output ¡°L¡±: Busy, ¡°H¡±: Not busy


73, Dan ve4drk


On Wed, Sep 29, 2021 at 2:14 PM rmatteucci . <rmatteucci@...> wrote:
I would like to add Allstar to a Kenwood TKR-750 Repeater that I have access to. ? I am being told that it should be as simple as creating a cable DB-9 to DB-25 so that the pins for RX Audio,? TX Audio, COS, PTT and Ground match up.? Has anyone done this? or does anyone think that this will not work?? Just looking for direction before going forward with this.
Re: DINAH and Kenwood Repeater

 

I've asked our fellow ham who made up the cables to provide the reference information.? I'm attaching a PDF that describes this.
We use this repeater on an allstar node as well.? We've also documented what we are going to use for an APRS connection as well - once I figure out the configuration on the direwolf...

Hope this helps.

73, Dan ve4drk


On Thu, Sep 30, 2021 at 8:52 PM rmatteucci . <rmatteucci@...> wrote:
Dan,
I guess I should have included that I am looking to use the DINAH for Allstar input.? What's still a bit confusing is on the DINAH you have pins for COS, GRND, PTT, which are easy to match but you also have pins for 9600, 1200, and Data IN - I am not sure which they would go to on the TKR-750.? I assume that DATA IN might be TX Audio input and either 9600 or 1200 will be RX Audio Output?? is this correct?
Thanks,
Bob N2TEV

On Wed, Sep 29, 2021 at 3:56 PM Dan Keizer <ve4drk@...> wrote:
We did this with a tkr750 - the specs were:

Diagram on Page 48 is as follows

Pin????? Purpose

7??????? Ground

9??????? TX audio input (voice) Input impedance: 600?

Coupling: AC coupling Deviation: 60% deviation (1kHz 280mVrms ¡À25mV input)

11?????? RX audio output (voice) Output impedance: 1k? or less

Coupling: AC coupling Output level: 360~440mVrms (standard modulation)

16????? PTT - ¡°L¡±: PTT on, ¡°H¡±: PTT off

17????? COS ¨C Squelch control output ¡°L¡±: Busy, ¡°H¡±: Not busy


73, Dan ve4drk


On Wed, Sep 29, 2021 at 2:14 PM rmatteucci . <rmatteucci@...> wrote:
I would like to add Allstar to a Kenwood TKR-750 Repeater that I have access to. ? I am being told that it should be as simple as creating a cable DB-9 to DB-25 so that the pins for RX Audio,? TX Audio, COS, PTT and Ground match up.? Has anyone done this? or does anyone think that this will not work?? Just looking for direction before going forward with this.

Cable APRS to Radios.pdf
Cable APRS to Radios.pdf

Re: DINAH and Kenwood Repeater

 

Dan,
I guess I should have included that I am looking to use the DINAH for Allstar input.? What's still a bit confusing is on the DINAH you have pins for COS, GRND, PTT, which are easy to match but you also have pins for 9600, 1200, and Data IN - I am not sure which they would go to on the TKR-750.? I assume that DATA IN might be TX Audio input and either 9600 or 1200 will be RX Audio Output?? is this correct?
Thanks,
Bob N2TEV


On Wed, Sep 29, 2021 at 3:56 PM Dan Keizer <ve4drk@...> wrote:
We did this with a tkr750 - the specs were:

Diagram on Page 48 is as follows

Pin????? Purpose

7??????? Ground

9??????? TX audio input (voice) Input impedance: 600?

Coupling: AC coupling Deviation: 60% deviation (1kHz 280mVrms ¡À25mV input)

11?????? RX audio output (voice) Output impedance: 1k? or less

Coupling: AC coupling Output level: 360~440mVrms (standard modulation)

16????? PTT - ¡°L¡±: PTT on, ¡°H¡±: PTT off

17????? COS ¨C Squelch control output ¡°L¡±: Busy, ¡°H¡±: Not busy


73, Dan ve4drk


On Wed, Sep 29, 2021 at 2:14 PM rmatteucci . <rmatteucci@...> wrote:
I would like to add Allstar to a Kenwood TKR-750 Repeater that I have access to. ? I am being told that it should be as simple as creating a cable DB-9 to DB-25 so that the pins for RX Audio,? TX Audio, COS, PTT and Ground match up.? Has anyone done this? or does anyone think that this will not work?? Just looking for direction before going forward with this.
Re: DINAH and Kenwood Repeater

 

We did this with a tkr750 - the specs were:

Diagram on Page 48 is as follows

Pin????? Purpose

7??????? Ground

9??????? TX audio input (voice) Input impedance: 600?

Coupling: AC coupling Deviation: 60% deviation (1kHz 280mVrms ¡À25mV input)

11?????? RX audio output (voice) Output impedance: 1k? or less

Coupling: AC coupling Output level: 360~440mVrms (standard modulation)

16????? PTT - ¡°L¡±: PTT on, ¡°H¡±: PTT off

17????? COS ¨C Squelch control output ¡°L¡±: Busy, ¡°H¡±: Not busy


73, Dan ve4drk


On Wed, Sep 29, 2021 at 2:14 PM rmatteucci . <rmatteucci@...> wrote:
I would like to add Allstar to a Kenwood TKR-750 Repeater that I have access to. ? I am being told that it should be as simple as creating a cable DB-9 to DB-25 so that the pins for RX Audio,? TX Audio, COS, PTT and Ground match up.? Has anyone done this? or does anyone think that this will not work?? Just looking for direction before going forward with this.
DINAH and Kenwood Repeater

 

I would like to add Allstar to a Kenwood TKR-750 Repeater that I have access to. ? I am being told that it should be as simple as creating a cable DB-9 to DB-25 so that the pins for RX Audio,? TX Audio, COS, PTT and Ground match up.? Has anyone done this? or does anyone think that this will not work?? Just looking for direction before going forward with this.
DINAH on PI Zero

 

OK I have DINAH working smoothly on a Raspberry PI 3 running direwolf and all is working well.

I have now built from scratch on PI Zero? (PI3 compiles don't always work o PI Zero)? and I get the following errors:

Audio input device 0 error code -19: No such device
Audio input device 0 error code -77: File descriptor in bad state
Audio input device 0 error code -77: File descriptor in bad state
Could not open /dev/hidraw0 for write, errno=2
ERROR: ?PTT for channel 0 has failed.? See User Guide for troubleshooting tips.
Audio input device 0 error code -77: File descriptor in bad state
Audio input device 0 error code -77: File descriptor in bad state
Audio input device 0 error code -77: File descriptor in bad state
Audio input device 0 error code -77: File descriptor in bad state
Audio input device 0 error code -77: File descriptor in bad state
Audio input device 0 error code -77: File descriptor in bad state
Audio input device 0 error code -77: File descriptor in bad state
Audio input device 0 error code -77: File descriptor in bad state
Terminating after audio input failure.

Direwoilf?is initially finding the DINAH as card 1 device 0.

aplay -l identifies the device.

alsamixer -c 1 can adjust sound level.

Thoughts?

Thanks!
--

73,
AB1PH
Don Rolph
Re: [direwolf] DINAH on PI Zero

 

My thanks to JK and David Ranch.

The dreaded RFI seems to strike again.

I have beads on every line.

I turn the transceiver off.

System is stable. ?beacon triggers at appropriate intervals.

Power up transceiver and these failures occur.

Does not happen with Raspberry PI 3, but it looks like PI Zero is more sensitive.

Ok, now to scratch my head and figure out?how to get enough shielding.

Thanks!



On Fri, Sep 24, 2021 at 3:45 PM David Ranch <direwolf-groupsio@...> wrote:

Hello Don,

OK I have DINAH working smoothly on a Raspberry PI 3 running direwolf and all is working well.

I have now built from scratch on PI Zero? (PI3 compiles don't always work o PI Zero)? and I get the following errors:

Audio input device 0 error code -19: No such device
Audio input device 0 error code -77: File descriptor in bad state
Audio input device 0 error code -77: File descriptor in bad state
Could not open /dev/hidraw0 for write, errno=2
ERROR: ?PTT for channel 0 has failed.? See User Guide for troubleshooting tips.
Audio input device 0 error code -77: File descriptor in bad state
Audio input device 0 error code -77: File descriptor in bad state
Audio input device 0 error code -77: File descriptor in bad state
Audio input device 0 error code -77: File descriptor in bad state
Audio input device 0 error code -77: File descriptor in bad state
Audio input device 0 error code -77: File descriptor in bad state
Audio input device 0 error code -77: File descriptor in bad state
Audio input device 0 error code -77: File descriptor in bad state
Terminating after audio input failure.

These errors smack of RFI interference knocking out the DINAH sound device.? To confirm, once this error pops up, look at the output of "dmesg" and see if you have a USB reset and your soundcard is "re-discovered".? If that's happening, you need to resolve the RFI issue.? Try and and ALL of the following:

?? - Check to confirm the SWR on your antenna is low
?? - Lower the transmit power on your radio as a test
?? - Move the antenna farther away from the Rpi.? Farther the better.
?? - Put ferrites on *all* cables going in/out of the Rpi, the radio (audio cables, power, etc),


--David



--

73,
AB1PH
Don Rolph
Re: Yaesu FT-1500M and Allstarlink

 

G'day Steve,

Thanks for confirming that the connector is the same, I was 99% sure but just like to confirm things.

Installed the Hamvoip image (I had been attempting to install the Allstar image) and followed the KG8MM directions that you linked me to and there are some signs of life in that the the node radio is making announcements and I can trigger announcements from the CLI such as rpt fun 53780 *82 for the time but get the following report at times:

[Sep 14 15:19:48] NOTICE[1316]: chan_iax2.c:7848 registry_rerequest: No secret associated with peer '53780'

Not sure what that means.

Also not able to connect to any other node from the CLI or get any responses to DTMF from the HH to the node radio.

Any and all advice welcome!

73, Steve VK2ARS



----- Original Message -----

To:
<[email protected]>
Cc:

Sent:
Mon, 13 Sep 2021 06:13:25 -0700
Subject:
Re: [DINAH] Yaesu FT-1500M and Allstarlink


The FT-1500 has the standard 6 Pin miniDIN packet data connector so it will work with DINAH.

The setup procedure can be downloaded from the Files section of this group.? It is very detailed and straight forward.??

/g/DINAH/files/HamVOIP-Allstar-Node-Setup-and-Configuration-Guide-by-KG8MM.pdf

The COS LED can be enabled to illuminate when a signal is received.? See this document in the Files section.

/g/DINAH/files/COS%20LED.pdf

Steve - N8AR
Email sent using Optus Webmail
Yaesu FT-1500M and Allstarlink

 

¿ªÔÆÌåÓý

G¡¯day everyone!
?
Can anybody advise if the above radio is compatible with DINAH?
?
I see no reason why it shouldn¡¯t be, but it¡¯s not in the compatible list so I thought I should ask.
?
The plan is to plug it into the DINAH and into a Pi running Allstarlink, are there any really simple walk through setup instructions that I can follow?
?
73, Steve VK2ARS
Re: Yaesu FT-1500M and Allstarlink

 

The FT-1500 has the standard 6 Pin miniDIN packet data connector so it will work with DINAH.

The setup procedure can be downloaded from the Files section of this group.? It is very detailed and straight forward.??

/g/DINAH/files/HamVOIP-Allstar-Node-Setup-and-Configuration-Guide-by-KG8MM.pdf

The COS LED can be enabled to illuminate when a signal is received.? See this document in the Files section.

/g/DINAH/files/COS%20LED.pdf

Steve - N8AR
Re: Hmm when I moved from my IC7000 to my FT817ND the volume control behavior reappeared

 

Perfect!

Will do.

Thanks!


On Fri, Sep 3, 2021 at 11:31 AM N0YWB <n0ywb1@...> wrote:
The following VOIP applications need the COS input to inhibit transmitting when the channel is active: Otherwise cut the JP3 trace to disable COS for most digital mode applications.? See .?
? Includes a Debian LINUX distribution called?
?- a standard protocol from DHS OIC's SAFECOM program
??for radio / resource sovereignty and peer-to-peer




--

73,
AB1PH
Don Rolph
Re: Hmm when I moved from my IC7000 to my FT817ND the volume control behavior reappeared

 

The Allstar VOIP application is the only digital mode that I am aware of that uses the COS input to inhibit transmitting.? COS may also be useful in remotely controlled EchoLink repeaters.? In all other digital modes applications, jumper JP3 in the DINAH interface should be disconnected. This will make the decreasing volume issue go away.
Re: Hmm when I moved from my IC7000 to my FT817ND the volume control behavior reappeared

 

The following VOIP applications need the COS input to inhibit transmitting when the channel is active: Otherwise cut the JP3 trace to disable COS for most digital mode applications.? See .?
? Includes a Debian LINUX distribution called?
?- a standard protocol from DHS OIC's SAFECOM program
??for radio / resource sovereignty and peer-to-peer


Re: Hmm when I moved from my IC7000 to my FT817ND the volume control behavior reappeared

 

I have done further testing:
?
- there are specfici?instructions about configuring Rasperian PI for DINAH and Direwolf
? o?
?
When I remove Pulse audio from my PI, the problem disappears and the system?works on both my IC-7000 and FT817ND.
?
So it appears I can turn this undesired?behavior on and off at will in Rasperian.
?
And the problem is documented to exist in Windows.
?
So it appears that the issue?is not in the application software per se, but in the sound driver system which is default in both Windows and apparently?Rasperian.
?
Now for a voice based system the COS/squelch of incoming?signal is required?otherwise atmospheric?noise will be interpreted as incoming?voice?and lock up the software.? Indeed a have a tailored signalink configuration for Echolink which draws sound from the squelched audio line rather than the 6 pin mini din connection to avoid this problem.
?
And AllStar systems are voice?based systems, and appear to be focused on tailored versions of LINUX which do not have this problem.
?
But digital modes have some form of software squelch/channel busy detect and COS/Squelch is not?needed.? Indeed on HF there is no squelch functionality.
?
And the focus for this?use case is digital modes, not voice.
?
So the question seems to be:
?
- should I work to keep the software clean
?
- should I cut jumper JP3
?
Thoughts?
?
Thanks!
?

On Thu, Sep 2, 2021 at 8:48 PM N8AR <n8ar73@...> wrote:
I would say that the CM108B in DINAH is doing exactly what it should be doing.? Turning down the volume.? Here is my reasoning.

In DINAH, the COS signal from Pin 6 of the miniDIN connector is connected to Pin 48 of the CM108B which is VOLDN (Volume Down).? This is a Schmidt trigger data input with a pullup.? Every time the input goes low, the volume should decrease in "normal souncard" operation using a CM108B driver.? However, using Direwolf, every time your radio squelches ( RF signal to the radio) COS goes low and lowers the volume slightly.? When an RF signal is received by the radio,? it goes high.? In Allstar the functionality of VOLDN is redefined by software so that it is interpreted as a COS input signal.? Apparently, the CM108 driver? used in Direwolf still treats it as a VOLDN command.

Opening JP3 (cutting the trace on the solder bridge jumper) means that the pullup on the CM108B VOLDN input will force the input to be always high so the volume will never be decreased.? ?You can remove the COS input when you are using Direwolf because it always needs to be monitoring the 1200 (or 9600) signal input looking for valid packet data.

Steve - N8AR

?

?


?
--
?
73,
AB1PH
Don Rolph
Re: Hmm when I moved from my IC7000 to my FT817ND the volume control behavior reappeared

 
Edited

I would say that the CM108B in DINAH is doing exactly what it should be doing.? Turning down the volume.? Here is my reasoning.

In DINAH, the COS signal from Pin 6 of the miniDIN connector is connected to Pin 48 of the CM108B which is VOLDN (Volume Down).? This is a Schmidt trigger data input with a pullup.? Every time the input goes low, the volume should decrease in "normal sound card" operation using a CM108B driver.? So, using Direwolf, every time your radio squelches (i.e.no RF signal to the radio) COS goes low and lowers the volume slightly.? When an RF signal is received by the radio,? it goes high.? In Allstar the functionality of VOLDN is redefined by software so that it is interpreted as a COS input signal.? Apparently, the CM108 driver? used in Direwolf still treats it as a VOLDN command.

Opening JP3 (cutting the trace on the solder bridge jumper) means that the pullup on the CM108B VOLDN input will force the input to be always high so the volume will never be decreased.? ?You can remove the COS input when you are using Direwolf because it always needs to be monitoring the 1200 (or 9600) signal input looking for valid packet data.

Steve - N8AR
Re: Hmm when I moved from my IC7000 to my FT817ND the volume control behavior reappeared

 

Hi Don:

It is asserted in the packet/817 world that to use the 817 one needs to disconnect pin 6 on the DIN cable to the 817. They call it a "squelch problem".

SInce the pin 6 input to the DINAH goes to a signal on the CM108/119 called VOLDN, maybe makes sense that the 817 might drive this signal to squelch?

Jeff Marden
N1JCM


On Thu, Sep 2, 2021 at 12:30 PM Don Rolph <don.rolph@...> wrote:
Now I am puzzled.

My configuration:

Raspberry?PI 3 (Direwolf)<->DINAH<->IC7000 worked stably overnight

I am now using:

PI (direwolf) (same system)<-> DINAH (same DINAH) <-> FT817ND

and the speaker volume is now being pushed to zero as on Windows.

It looks like the behavior is nor Windows specific but perhaps is associated with the DINAH system?

Thoughts?

--

73,
AB1PH
Don Rolph
Re: Hmm when I moved from my IC7000 to my FT817ND the volume control behavior reappeared

 

I use a DINAH with direwolf for packet on a Raspberry Pi often with no
problems.

I open jumper plug JP3 on DINAH so that COS is not connected to pin 6 on
the mDin6 cable.

/Basil n7nix

Don Rolph <don.rolph@...> writes:

And I have moved back to the IC7000 and I get the same behavior where an
incoming signal depresses the speaker volume.

I seem stumped but the COS line management seems unstable.

Thoughts?

On Thu, Sep 2, 2021 at 12:30 PM Don Rolph via groups.io <don.rolph=
[email protected]> wrote:

Now I am puzzled.

My configuration:

Raspberry PI 3 (Direwolf)<->DINAH<->IC7000 worked stably overnight

I am now using:

PI (direwolf) (same system)<-> DINAH (same DINAH) <-> FT817ND

and the speaker volume is now being pushed to zero as on Windows.

It looks like the behavior is nor Windows specific but perhaps is
associated with the DINAH system?

Thoughts?
281 - 300 of 430