Date   

Re: How to configure a ASL server

Steve N4IRS
 

José,
The 1999 stanza is the private node that us used to connect Analog_Bridge to AllStarLink. It does not have to be 1999, nor for that matter does it have to be a private node.
If for example you have a public node
[2222]
rxchannel = Radio/usb0 ; Assuming a radio connected via a USB radio interface

And you have a echolink connection (echolink.conf)
[el0]
node = 3215555 ; The EL node number
astnode = 2222 ; Connect EL to node 2222

When someone on EL connects to 3215555 they are on ASL 2222

Now you want to ADD a node for Analog_Bridge.
[1999]
rxchannel = USRP/127.0.0.1:34001:32001; GNU Radio interface USRP

Make sense?

This is the first draft of the ASL <-> DMR how to document.
<https://docs.google.com/document/d/1eN50Csr29eAprBu7eKA0Bfa2XUcsXw5iktY1Ey-Qjkg/edit?usp=sharing>

73, Steve N4IRS


On 06/08/2018 10:06 PM, TG9AOR wrote:
Excellent document. Thank you so much. As you may or may not recall, I followed Kv4S's how to guide, it in turn made reference to another how to guide on setting up the allstar node. It differs somewhat when looking into the manual setup section.Now, considering that I have echolink connected on that allstar node, do I still need to insert the 1999 stanza into de rpt.conf? 

73
--
José Roberto Ruíz García Salas
TG9AOR


Re: How to configure a ASL server

TG9AOR
 

I am able to see more detailed explanation on the section "Transcode one digital format to another", I believe you are referring to this? It is very helpful. 
--
José Roberto Ruíz García Salas
TG9AOR


How to configure a ASL server

TG9AOR
 

Excellent document. Thank you so much. As you may or may not recall, I followed Kv4S's how to guide, it in turn made reference to another how to guide on setting up the allstar node. It differs somewhat when looking into the manual setup section.Now, considering that I have echolink connected on that allstar node, do I still need to insert the 1999 stanza into de rpt.conf? 

73
--
José Roberto Ruíz García Salas
TG9AOR


Network Watchdog cutting off feed to YSFReflector

TG9AOR
 

I noticed that sporadically my DMR transmissions on TG704 would not make it 100% into YSFreflector. Log output below:

I: 2018-06-09 00:36:31.144 YSF, Narrow transmit (72 bit)
M: 2018-06-09 00:37:16.444 DMR Slot 2, received network end of voice transmission, 45.5 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-09 00:37:16.444 YSF, TX state = OFF
M: 2018-06-09 00:37:20.323 DMR Slot 2, received network voice header from HK4CZE to TG 704
M: 2018-06-09 00:37:20.323 YSF, TX state = ON
I: 2018-06-09 00:37:20.324 YSF, Begin TX: src=7320002 rpt=0 dst=704 slot=2 cc=0 metadata=HK4CZE

I: 2018-06-09 00:37:20.690 YSF, Narrow transmit (72 bit)
M: 2018-06-09 00:37:22.237 DMR Slot 2, network watchdog has expired, 1.3 seconds, 81% packet loss, BER: 0.0%
E: 2018-06-09 00:38:11.082 DMR, Connection to the master has timed out, retrying connection
M: 2018-06-09 00:38:11.082 DMR, Closing DMR Network
M: 2018-06-09 00:38:11.082 DMR, Opening DMR Network
M: 2018-06-09 00:38:21.334 DMR, Logged into the master successfully
M: 2018-06-09 00:38:30.490 DMR Slot 2, received network voice header from HK4CZE to TG 704
M: 2018-06-09 00:38:30.490 YSF, TX state = ON
I: 2018-06-09 00:38:30.490 YSF, Begin TX: src=7320002 rpt=0 dst=704 slot=2 cc=0 metadata=HK4CZE

I: 2018-06-09 00:38:30.786 YSF, Narrow transmit (72 bit)
M: 2018-06-09 00:38:31.246 DMR Talker Alias (Data Format 1, Received 6/8 char): 'HK4CZE'
M: 2018-06-09 00:38:31.835 DMR Talker Alias (Data Format 1, Received 8/8 char): 'HK4CZE  '
M: 2018-06-09 00:39:32.360 DMR Slot 2, network watchdog has expired, 61.7 seconds, 1% packet loss, BER: 0.0%
M: 2018-06-09 00:39:32.402 YSF, received network data from TG0AA      to ALL        at TG0AA
I: 2018-06-09 00:39:32.402 YSF, Lookup call TG0AA returned id 7040018 -> 7040018
M: 2018-06-09 00:39:32.407 DMR, TX state = ON
I: 2018-06-09 00:39:32.407 DMR, Begin TX: src=7040018 rpt=0 dst=704 slot=2 cc=0 metadata=TG0AA
M: 2018-06-09 00:39:35.605 YSF, network watchdog has expired, 1.8 seconds, 0% packet loss, BER: 7.9%
M: 2018-06-09 00:39:35.605 DMR, TX state = OFF
E: 2018-06-09 00:40:21.427 DMR, Connection to the master has timed out, retrying connection
M: 2018-06-09 00:40:21.427 DMR, Closing DMR Network
M: 2018-06-09 00:40:21.427 DMR, Opening DMR Network
M: 2018-06-09 00:40:31.687 DMR, Logged into the master successfully
 
 
Data center is located in Seattle, WA. xlxd interlink to XLX502 does not have any issues, XLX502 located in Guatemala.
 
How do I get Mr. watchdog in control?
 
 
73 de TG9AOR

--
José Roberto Ruíz García Salas
TG9AOR


Re: New member, few questions regarding hblink/hb_bridge/hb_confbridge

Corey Dean N3FE <n3fe@...>
 

If you have each client have a different connection setup you could use conf bridge and manage this quite easily.


On Jun 8, 2018, at 3:14 PM, Colby Ross W1BSB <colbypr@...> wrote:

That's what I thought. Thanks Steve. So at this time if repeat were off there would be no way to define a list of talk groups that would be repeated to other clients which was kind of what I thought. 

Colby

On Fri, Jun 8, 2018, 15:12 Steve N4IRS <szingman@...> wrote:
If two clients are connected to the same Master and repeat is turned on, all traffic will pass between the two clients.
If two clients are connected to different Master and repeat is turned on, only the TGs defined in hb_confbridge will pass between the two clients.




On 6/8/2018 2:28 PM, Colby Ross W1BSB wrote:
There is not. I didn't want every talk group being repeated, only ones that were defined.

Colby


Re: "Blocked" Message on Brandmeister

Steve N4IRS
 

I: 2018-06-08 19:08:24.977 DMR Network Parameters
I: 2018-06-08 19:08:24.977     Address: 104.236.174.109
I: 2018-06-08 19:08:24.977     Port: 55555
I: 2018-06-08 19:08:24.977     Local: 62032
I: 2018-06-08 19:08:24.977     Jitter: 360ms
I: 2018-06-08 19:08:24.977     Slot 1: disabled
I: 2018-06-08 19:08:24.977     Slot 2: enabled
I: 2018-06-08 19:08:24.977     Mode Hang: 3s
I: 2018-06-08 19:08:24.977     Options: StartRef=4649;RelinkTime=0;UserLink=1
I: 2018-06-08 19:08:24.977 Info Parameters
I: 2018-06-08 19:08:24.978     Callsign: N4IRS
I: 2018-06-08 19:08:24.978     RX Frequency: 222340000Hz
I: 2018-06-08 19:08:24.978     TX Frequency: 224940000Hz
I: 2018-06-08 19:08:24.978     Power: 1W
I: 2018-06-08 19:08:24.978     Latitude: 41.733299deg N
I: 2018-06-08 19:08:24.978     Longitude: -50.399899deg E
I: 2018-06-08 19:08:24.978     Height: 0m
I: 2018-06-08 19:08:24.978     Location: "Iceberg, North Atlantic"
I: 2018-06-08 19:08:24.978     Description: "MMDVM_Bridge"
I: 2018-06-08 19:08:24.978     URL: "https://groups.io/g/DVSwitch"
M: 2018-06-08 19:08:24.978 DMR, Opening DMR Network
I: 2018-06-08 19:08:24.978 RSSI
I: 2018-06-08 19:08:24.978     Mapping File: RSSI.dat
W: 2018-06-08 19:08:24.978 Cannot open the RSSI data file - RSSI.dat
I: 2018-06-08 19:08:24.978 DMR Id Lookups
I: 2018-06-08 19:08:24.978     File: /var/lib/mmdvm/DMRIds.dat
I: 2018-06-08 19:08:24.978     Reload: 24 hours
I: 2018-06-08 19:08:25.062 Loaded 57133 Ids to the DMR callsign lookup table
I: 2018-06-08 19:08:25.062 DMR RF Parameters
I: 2018-06-08 19:08:25.062 Started the DMR Id lookup reload thread
I: 2018-06-08 19:08:25.062     Id: 3112138
I: 2018-06-08 19:08:25.062     Color Code: 1
I: 2018-06-08 19:08:25.062     Self Only: no
I: 2018-06-08 19:08:25.062     Embedded LC Only: yes
I: 2018-06-08 19:08:25.062     Dump Talker Alias Data: no
I: 2018-06-08 19:08:25.062     Prefixes: 0
I: 2018-06-08 19:08:25.062     Call Hang: 3s
I: 2018-06-08 19:08:25.063     TX Hang: 3s
I: 2018-06-08 19:08:25.063     Mode Hang: 10s
M: 2018-06-08 19:08:25.063 DMR, Opening INI file: DVSwitch.ini
M: 2018-06-08 19:08:25.063 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2018-06-08 19:08:25.063 DMR, Setting [DMR] TXPort -> 31100
M: 2018-06-08 19:08:25.063 DMR, Setting [DMR] RXPort -> 31103
M: 2018-06-08 19:08:25.063 DMR, Setting [DMR] Slot -> 1
M: 2018-06-08 19:08:25.063 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
M: 2018-06-08 19:08:25.063 MMDVM_Bridge-20180526 is running
D: 2018-06-08 19:08:35.153 DMR, Sending authorisation
D: 2018-06-08 19:08:35.245 DMR, Sending configuration
D: 2018-06-08 19:08:35.337 DMR, Sending options
M: 2018-06-08 19:08:35.429 DMR, Logged into the master successfully
M: 2018-06-08 19:09:26.536 DMR Slot 2, received network voice header from 4649 to TG 9
M: 2018-06-08 19:09:33.274 DMR Slot 2, received network end of voice transmission, 6.6 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-08 19:23:50.143 DMR Slot 2, received network late entry from WB9PZM to TG 9
D: 2018-06-08 19:23:51.145 DMR Slot 2, lost audio for 408ms filling in
D: 2018-06-08 19:23:51.553 DMR Slot 2, lost audio for 408ms filling in
D: 2018-06-08 19:23:51.962 DMR Slot 2, lost audio for 409ms filling in
M: 2018-06-08 19:23:52.237 DMR Slot 2, network watchdog has expired, 2.2 seconds, 50% packet loss, BER: 0.0%

As you can see, I connected to the Master at 19:08Z and the last traffic I saw was at 19:23Z As of right now, (19:51Z) I'm still connected. I think there may be a keep alive being missed. Are there any firewall rules involved?

73, Steve N4IRS

On 6/8/2018 3:03 PM, Mike Swiatkowski via Groups.Io wrote:
attached...


Re: New member, few questions regarding hblink/hb_bridge/hb_confbridge

Colby Ross W1BSB
 

In my testing with repeat off even if using the bridged talkgroup the other clients on the same master don't hear it which is what I was looking for. Thanks again for the help. 

Cokby

On Fri, Jun 8, 2018, 15:16 Steve N4IRS <szingman@...> wrote:
repeat only controls traffic passing within a Master. It does not effect traffic passing through the conf_bridge. At least I think so.

On 6/8/2018 3:14 PM, Colby Ross W1BSB wrote:
That's what I thought. Thanks Steve. So at this time if repeat were off there would be no way to define a list of talk groups that would be repeated to other clients which was kind of what I thought. 

Colby

On Fri, Jun 8, 2018, 15:12 Steve N4IRS <szingman@...> wrote:
If two clients are connected to the same Master and repeat is turned on, all traffic will pass between the two clients.
If two clients are connected to different Master and repeat is turned on, only the TGs defined in hb_confbridge will pass between the two clients.




On 6/8/2018 2:28 PM, Colby Ross W1BSB wrote:
There is not. I didn't want every talk group being repeated, only ones that were defined.

Colby



Re: New member, few questions regarding hblink/hb_bridge/hb_confbridge

Steve N4IRS
 

repeat only controls traffic passing within a Master. It does not effect traffic passing through the conf_bridge. At least I think so.

On 6/8/2018 3:14 PM, Colby Ross W1BSB wrote:
That's what I thought. Thanks Steve. So at this time if repeat were off there would be no way to define a list of talk groups that would be repeated to other clients which was kind of what I thought. 

Colby

On Fri, Jun 8, 2018, 15:12 Steve N4IRS <szingman@...> wrote:
If two clients are connected to the same Master and repeat is turned on, all traffic will pass between the two clients.
If two clients are connected to different Master and repeat is turned on, only the TGs defined in hb_confbridge will pass between the two clients.




On 6/8/2018 2:28 PM, Colby Ross W1BSB wrote:
There is not. I didn't want every talk group being repeated, only ones that were defined.

Colby



Re: New member, few questions regarding hblink/hb_bridge/hb_confbridge

Colby Ross W1BSB
 

That's what I thought. Thanks Steve. So at this time if repeat were off there would be no way to define a list of talk groups that would be repeated to other clients which was kind of what I thought. 

Colby

On Fri, Jun 8, 2018, 15:12 Steve N4IRS <szingman@...> wrote:
If two clients are connected to the same Master and repeat is turned on, all traffic will pass between the two clients.
If two clients are connected to different Master and repeat is turned on, only the TGs defined in hb_confbridge will pass between the two clients.




On 6/8/2018 2:28 PM, Colby Ross W1BSB wrote:
There is not. I didn't want every talk group being repeated, only ones that were defined.

Colby


Re: New member, few questions regarding hblink/hb_bridge/hb_confbridge

Steve N4IRS
 

If two clients are connected to the same Master and repeat is turned on, all traffic will pass between the two clients.
If two clients are connected to different Master and repeat is turned on, only the TGs defined in hb_confbridge will pass between the two clients.




On 6/8/2018 2:28 PM, Colby Ross W1BSB wrote:
There is not. I didn't want every talk group being repeated, only ones that were defined.

Colby


Re: "Blocked" Message on Brandmeister

Mike, AA9VI
 

attached...


Re: DMR to ASL audio level

Steve N4IRS
 

Funny you should ask. While trying to write the documentation for this we realized that the names and comments need fixing. For now, here is the info:

aslAudio = AUDIO_UNITY ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
agcGain = -20 ; Gain (in db) of the AGC filter
dmrAudio = AUDIO_UNITY ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.35 ; Gain factor of audio from ASL (0.0-1.0)

aslAudio is the level from DMR to ASL you can use the following:
AUDIO_UNITY No change in level from in to out
AUDIO_USE_GAIN Allow change in level up or down
agcGain is misleading, when used with AUDIO_USE_GAIN it is a number from 0.0 to 10.0 A number less then 1.0 is a reduction in level A number greater then 1 is a multiplier.
.75 is 75 percent of AUDIO_UNITY
5.0 is 5 times AUDIO_UNITY.

Steve

On 6/8/2018 2:49 PM, Greg Hovland wrote:
Thank you. One last question.
To adjust the DMR to ASL, can I use AUDIO_USE_GAIN? If so, which number would I adjust? I only see an option for agcGain. I need to increase my audio from DRM to AllStar.


Re: DMR to ASL audio level

Greg Hovland
 

Thank you. One last question.
To adjust the DMR to ASL, can I use AUDIO_USE_GAIN? If so, which number would I adjust? I only see an option for agcGain. I need to increase my audio from DRM to AllStar.


Re: DMR to ASL audio level

Steve N4IRS
 

No,
Just restart Analog_Bridge
systemctl restart analog_bridge

On 6/8/2018 2:43 PM, Greg Hovland wrote:
If I make changes to the audio levels, do I need to reboot the system?


Re: DMR to ASL audio level

Greg Hovland
 

If I make changes to the audio levels, do I need to reboot the system?


Re: New member, few questions regarding hblink/hb_bridge/hb_confbridge

Colby Ross W1BSB
 

There is not. I didn't want every talk group being repeated, only ones that were defined.

Colby


Re: New member, few questions regarding hblink/hb_bridge/hb_confbridge

Peter M0NWI
 

Colby,

Is there not a,repeat = Y in the hblink ini file?

73,
Peter

Sent from Outlook
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Colby Ross W1BSB <colbypr@...>
Sent: 08 June 2018 19:22:49
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] New member, few questions regarding hblink/hb_bridge/hb_confbridge
 
Ok, so I've been playing around with hb_confbridge and I think I understand how the bridging portion works now.  I set up 2 masters and had a working bridge between them.  For this example, we have Master 1, Master 2, Client 1, and Client 2.  I connected Client 1 to Master 1, and Client 2 to Master 2. I set up a bridge on talkgroup 555.  Client 1 transmits on TG555 and Client 2 on Master 2 can hear this. 

However, and I think this is likely by design, if I connect Client 2 to Master 1, where Client 1 is also connected, and Client 1 transmits over TG555, Client 2 does not hear it.  This is kind of what I'm looking for, a way to define what talk groups are passed to the other clients without repeating all of it.  I'm figuring that the software isn't likely designed to do this, but maybe it is and I'm just missing it?

73

Colby W1BSB


Re: New member, few questions regarding hblink/hb_bridge/hb_confbridge

Colby Ross W1BSB
 

Ok, so I've been playing around with hb_confbridge and I think I understand how the bridging portion works now.  I set up 2 masters and had a working bridge between them.  For this example, we have Master 1, Master 2, Client 1, and Client 2.  I connected Client 1 to Master 1, and Client 2 to Master 2. I set up a bridge on talkgroup 555.  Client 1 transmits on TG555 and Client 2 on Master 2 can hear this. 

However, and I think this is likely by design, if I connect Client 2 to Master 1, where Client 1 is also connected, and Client 1 transmits over TG555, Client 2 does not hear it.  This is kind of what I'm looking for, a way to define what talk groups are passed to the other clients without repeating all of it.  I'm figuring that the software isn't likely designed to do this, but maybe it is and I'm just missing it?

73

Colby W1BSB


locked Bug found and fixed.

Steve N4IRS
 
Edited

In this topic we will announce bugfixes. Some fixes are minor and some are more important. (Duh! Thanks Captain Obvious)
We will post the issue and how to resolve. I am going to lock this thread so that only the announcements get posted. I think this will help someone looking for a answer. If this turns out to not be the case I'll try something else.

Here is the first of...
There is a bug in the netcheck service. The service is intended to signal to other services that the network is configured and operational.
It was always reporting the net was available. It is now fixed.
To fix on your bridge:
apt-get update
apt-get upgrade

73, Steve N4IRS


Re: DTMF

Corey Dean N3FE <n3fe@...>
 

This is what I was referring to.  Sorry I should have read everything before responding.   My bad...

Corey n3fe


On Jun 8, 2018, at 10:38 AM, Steve N4IRS <szingman@...> wrote:

If you set the telemdefault = 2 you will not hear the connect and disconnect after a short time until it is triggered by a command.

telemdefault = 1                        ; 0 = telemetry output off
                                        ; 1 = telemetry output on (default = 1)
                                        ; 2 = timed telemetry output on command execution and for a short time thereafter.


On 6/8/2018 10:33 AM, WillieB wrote:

If you bridge to a DMR ID instead of a TG, then it shouldn’t matter at all whether you leave telemetry on or off. The only issue with it I’ve ran into, is if you are on a node with a lot of connecting/disconnecting then while it’s announcing you can’t transmit. You have to wait until it’s finished. It gets irritating fast lol…

 

Now what I would be interested in, is if we can get it to pass DTMF and leave telemetry on but only for our node. In other words I don’t want to hear when other nodes have disconnecting/connecting nodes.

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Friday, June 8, 2018 10:26 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DTMF

 

Well, there is one report. Turning off telemetry is recommenced but not mandatory. If the TG the bridge is on does not care or wants to here the messages, go ahead and turn telemetry on. I guess I need to be more clear in the how-to.

Thanks, Steve

On 6/8/2018 10:21 AM, WillieB wrote:

Doesn’t work for me, but I’ll say that since it’s recommended to turn off all telemetry anyway, it’s not the best solution even if it did work.

 

I installed allmon2, and I also setup Zoiper with an iax connection. I most always use allmon2 since I can visually see when it connects and when it doesn’t.

 

-Will

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Jeff Lehman, KC8QCH
Sent: Friday, June 8, 2018 10:18 AM
To: main@DVSwitch.groups.io
Subject: [DVSwitch] DTMF

 

Hi Steve Et al,

      Will the bridges pass DTMF? Let’s say I setup an ASL<--> DMR Bridge and I want to control the ASL node. Will the bridge pass the DTMF to do that?

 

       Just thinking my way through a possible project, but I was wondering if this worked. It’s not a deal breaker, just would mean I need to think of something else 😊

 

  Jeff

 

Jeff Lehman, KC8QCH

Email: kc8qch@...

 

Webmaster

Hamilton County ARPSC

http://www.hamcoarpsc.org

Email: hamcoarpsc@...

 

Allstar Node 47374 Administrator

The Guild/IRN

http://theguildglobal.org

 

 


7641 - 7660 of 9203