Date   

ASL ><DMR /DVswitch Audio jitter - port problem ?

Mike KB8JNM
 
Edited

Well after thinking I had this under wraps, and connecting to a busy TG,
I found it was tx-ing the channel.(got some hate mail)

Scope back trough the docs and files, found a port mismatch.
But, after that, has such terrible audio on rx, not manageable.

It sounds like a port conflict to me but I can't find it.
I had check the tx audio with a friend and herd it back through his phone. Perfect.

So... out of hair on this one for 8 hours or more !
But it sounds really like something else in my network is causing the issue.  ???

[AMBE_AUDIO]
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 31100                     ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31103                       ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2500                      ; Minimum time in MS for hang delay
gatewayDmrId = 3101607                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 310160705                          ; ID of source repeater
txTg = 312                             ; TG to use for all frames received from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames received from Analog_Bridge -> xx_Bridge
colorCode = 1         

-----------------
[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0
-------------
[DMR Network]
Enable=1
Address=3102.repeater.net
Port=62031
Jitter=360
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0
--------------
[1999]
rxchannel = USRP/127.0.0.1:34001:32001

dvswitch.ini
[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31100                  ; Port to send AMBE TLV frames to (export)
RXPort = 31103                  ; Port to listen on (import)
Slot = 2                        ; Export slot


Re: How to configure a ASL server

Alec-N1AJW
 

thank you Steve.


Problem with Allstar to DMR Gateway.

Steve WA0SLL
 

I have built a DMR to Allstar gateway on a Raspberry Pi 3b+ using information from your group, and KV4S.  I can key up my talkgroup on my dmr radio and hear it on the phone portal.  I cannot get the Phone portal to transmit to the DMR.  I see the status change on the Brandmister Dashboard, but it has no audio on the hoseline nor does it key the DMR Repeater.  Any Ideas?


Stephen L. Lechliter
WAØSLL, Amateur Radio General Class
913-596-8038


Re: How to configure a ASL server

Steve N4IRS
 

Alec,
The ASL <-> DMR how to will show you how to add a second node https://docs.google.com/document/d/1eN50Csr29eAprBu7eKA0Bfa2XUcsXw5iktY1Ey-Qjkg/edit?usp=sharing

Steve

On 6/11/2018 12:15 PM, Alec J Wasserman wrote:
do you have a template that has two nodes on it?  i actually want to move my ASL link to my other server with a node.  I looked for a template online for two nodes.  I know very little about ASL to know where to just add 2nd node.  

Alec
N1AJW


Re: How to configure a ASL server

Alec-N1AJW
 

do you have a template that has two nodes on it?  i actually want to move my ASL link to my other server with a node.  I looked for a template online for two nodes.  I know very little about ASL to know where to just add 2nd node.  

Alec
N1AJW


Re: How to configure a ASL server

Mike KB8JNM
 

The advantage is nobody from the outside can connect if that is what is required.
When you want that, then connect it to a public node. You have more choices.
Going to be more node security issues as we move forward with more people with knowledge on how the system works.
Just my half cent.
You gotta do what works for your situation and get along peacefully with your neighbors.


Re: How to configure a ASL server

Steve N4IRS
 

Jeff,
I don't think you are overthinking it at all. I don't make too many outgoing EL connections so it has not been a issue for me. We can look at possibilities to streamline operation. That is the power of ASL.

Steve

On 6/11/2018 9:49 AM, Jeff Lehman, KC8QCH wrote:

Steve, Jose, Et Al,

 

I’ve been mulling this in my head for the last half hour because I like the idea of the concept, but there is one disadvantage I see to connecting echolink to a separate private node vs connecting it directly to the node itself. To make outgoing echolink connections you would need to use the remote command and then dial out. If you are on a different node and need to dial out you would need to set remote twice…

 

So in other words. Public node is 12345. Your private echolink node is 1999. If you are connected to 12345 via say Zoiper or RF, you would need to *41999 – wait for confirmation and then dial *33<Elnodenumber> and then # to exit remote mode.

 

Example 2: Say you care connected to 12345 from 67890. From 67890 you would need to issue *412345 to gain remote mode on 12345 and then *41999 to gain remote mode on your echolink connection. Then *33<elnode number> to dial out. Then # and then # again to close remote modes coming back out. And you need to remember which node you are controlling at the time. Plus if you have telem announcements on….this could get messy quickly.

 

Don’t get me wrong, the idea of having one ASL node and then using multiple private nodes to tie things together to turn features on and off on the fly is pretty cool. But am I just overthinking the private node for EL thing?  I know that it is really no different then tying a DMR bridge in via a private node, but with El, since you can issue dialout commands? I’m probably over thinking this aren’t i?

 

Again this my just my thoughts and 2 cents….Feel  free to ignore me and take what I Have with a grain of salt LOL. I Promise I won’t be offended.

 

   Jeff

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of TG9AOR
Sent: Monday, June 11, 2018 08:48
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] How to configure a ASL server

 

Oh yes it does help. Many thanks.. I could then make 1999 the echolink connection, 1998 the DMR connection, and my node 48270 which is the AllStarlink node may have these added features on to it via CLI and so making it a straight AllStar node or an enhanced AllStar node. I have been reading the AllStar documentation, as well as the AllStar Wiki. I am liking it very much.
--
José Roberto Ruíz García Salas
TG9AOR



Re: How to configure a ASL server

Jeff Lehman, N8ACL
 

Steve, Jose, Et Al,

 

I’ve been mulling this in my head for the last half hour because I like the idea of the concept, but there is one disadvantage I see to connecting echolink to a separate private node vs connecting it directly to the node itself. To make outgoing echolink connections you would need to use the remote command and then dial out. If you are on a different node and need to dial out you would need to set remote twice…

 

So in other words. Public node is 12345. Your private echolink node is 1999. If you are connected to 12345 via say Zoiper or RF, you would need to *41999 – wait for confirmation and then dial *33<Elnodenumber> and then # to exit remote mode.

 

Example 2: Say you care connected to 12345 from 67890. From 67890 you would need to issue *412345 to gain remote mode on 12345 and then *41999 to gain remote mode on your echolink connection. Then *33<elnode number> to dial out. Then # and then # again to close remote modes coming back out. And you need to remember which node you are controlling at the time. Plus if you have telem announcements on….this could get messy quickly.

 

Don’t get me wrong, the idea of having one ASL node and then using multiple private nodes to tie things together to turn features on and off on the fly is pretty cool. But am I just overthinking the private node for EL thing?  I know that it is really no different then tying a DMR bridge in via a private node, but with El, since you can issue dialout commands? I’m probably over thinking this aren’t i?

 

Again this my just my thoughts and 2 cents….Feel  free to ignore me and take what I Have with a grain of salt LOL. I Promise I won’t be offended.

 

   Jeff

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of TG9AOR
Sent: Monday, June 11, 2018 08:48
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] How to configure a ASL server

 

Oh yes it does help. Many thanks.. I could then make 1999 the echolink connection, 1998 the DMR connection, and my node 48270 which is the AllStarlink node may have these added features on to it via CLI and so making it a straight AllStar node or an enhanced AllStar node. I have been reading the AllStar documentation, as well as the AllStar Wiki. I am liking it very much.
--
José Roberto Ruíz García Salas
TG9AOR


Re: How to configure a ASL server

TG9AOR
 

Oh yes it does help. Many thanks.. I could then make 1999 the echolink connection, 1998 the DMR connection, and my node 48270 which is the AllStarlink node may have these added features on to it via CLI and so making it a straight AllStar node or an enhanced AllStar node. I have been reading the AllStar documentation, as well as the AllStar Wiki. I am liking it very much.
--
José Roberto Ruíz García Salas
TG9AOR


Re: Turn on logging and view logs ASL

Steve N4IRS
 

Chris,
The ASL log is in /var/log/asterisk/messages
To enable more verbose logging at he the CLI> prompt:

rpt debug level 0 - 7

7 being the most verbose.


On 06/10/2018 12:07 PM, Chris via Groups.Io wrote:
Could someone point me in the right direction as to turning on all the logging that I can in ASL and where to view those logs.
I have a weird little issue cropping up in my DMR to ASL bridge and would like to be able to chase it down.

Chris
WB4ULK


Re: Connect Fusion repeater to DMR

Paul Nannery KC2VRJ
 

The nice thing with the dr 1x is it is easy to keep analog with the digital modes. But yes it is a dumb repeater


On Sun, Jun 10, 2018, 12:02 PM Chris via Groups.Io <chood73=yahoo.com@groups.io> wrote:
I finally figured it out. The DR1X is just ridiculously dumb and can't connect to anything. You have to use their Yaesu box to even connect to the WiresX rooms and then it's only over RF.

I see what you were saying, you basically install an MMDVM modem on the repeater and let it do the C4FM work. Essentially using the DR1X as a pair of radios. At that point why even use a DR1X? It's a garbage "repeater" anyway.

I am going to talk to the club and see if they just want to put a real repeater up there in place of that thing, since we will need to use a MMDVM modem anyway. At least then, it will have a real front-end on it.

That or they can just let it sit there and talk to itself. lol

Chris
WB4ULK


Turn on logging and view logs ASL

Chris WB4ULK
 

Could someone point me in the right direction as to turning on all the logging that I can in ASL and where to view those logs.
I have a weird little issue cropping up in my DMR to ASL bridge and would like to be able to chase it down.

Chris
WB4ULK


Re: Connect Fusion repeater to DMR

Chris WB4ULK
 

I finally figured it out. The DR1X is just ridiculously dumb and can't connect to anything. You have to use their Yaesu box to even connect to the WiresX rooms and then it's only over RF.

I see what you were saying, you basically install an MMDVM modem on the repeater and let it do the C4FM work. Essentially using the DR1X as a pair of radios. At that point why even use a DR1X? It's a garbage "repeater" anyway.

I am going to talk to the club and see if they just want to put a real repeater up there in place of that thing, since we will need to use a MMDVM modem anyway. At least then, it will have a real front-end on it.

That or they can just let it sit there and talk to itself. lol

Chris
WB4ULK


Re: How to configure a ASL server

Steve N4IRS
 

José,
The point I'm trying to make is that in AllStarLink each node has a node stanza. Within that stanza there is a rxchannel. Each node can have only one rxchannel. At the top of the sample rpt.conf you have a list of the more common ones.

; rxchannel = dahdi/pseudo                        ; No radio (hub)
; rxchannel = SimpleUSB/usb_1999        ; SimpleUSB 
; rxchannel = Pi/1                                           ; Raspberry Pi PiTA 
; rxchannel = Radio/usb_1999       ; USBRadio (DSP) 
; rxchannel = Dahdi/1               ; PCI Quad card 
; rxchannel = Beagle/1                      ; BeagleBoard 
; rxchannel = USRP/127.0.0.1:34001:32001; GNU Radio interface USRP

An ASL server can host more then one node. In the case of Echolink it does not have a rxchannel of it's own. Echolink connects or attaches to a existing node. this is done with the "astnode = 1999" in echolink.cfg
You can build a ASL server with multiple types of nodes. But Echolink can only attach to one node. The node it connects to can be connected to other nodes.

There really is no right way or wrong way to build this other then one node can only have one rxchannel.

The way I build my servers is to assign a node to each type of node. That can be a hub, echolink, usrp etc. By separating everything, I can control how things are connected. for example:
2100 = a hub
1999 = echolink
1998 = DMR
1997 = P25

Nodes 2100 and 1999 use the dahdi/pseudo channel driver
Nodes 1998 and 1997 use the USRP channel driver

Since 2100 is a public node, any AllStarLink node can connect to it You can connect any or all of the other nodes to 2100. You could also decide to connect P25 to Echolink, connect DMR to ASL.
Again, there is no right way and wrong way to build this other then the one rxchannel per node rule.

Hope this helps

Steve

  
 


Re: How to configure a ASL server

TG9AOR
 

Steve:


Here is my echolink.conf
[el0]
call = TG9AOR                           ; Change this!
pwd = 5up3rt1tt4                        ; Change this!
name = BM DMR TG70406                   ; Change this!
qth = Guatemala                         ; Change this!
email = qrz@...                  ; Change this!
node = 540574                           ; Change this!
; Data for EchoLink Status Page
lat = 14.528                            ; Latitude in decimal degrees
lon = -90.454                           ; Longitude in decimal degrees
freq = 0.0                              ; not mandatory Frequency in MHz
tone = 0.0                              ; not mandatory CTCSS Tone (0 for none)
power = 0                               ; 0=0W, 1=1W, 2=4W, 3=9W, 4=16W, 5=25W, 6=36W, 7=49W, 8=64W, 9=81W (Power in Watts)
height = 0                              ; 0=10 1=20 2=40 3=80 4=160 5=320 6=640 7=1280 8=2560 9=5120 (AMSL in Feet)
gain = 0                                ; Gain in db (0-9)
dir = 0                                 ; 0=omni 1=45deg 2=90deg 3=135deg 4=180deg 5=225deg 6=270deg 7=315deg 8=360deg (Direction)
maxstns = 2                             ; Max Stations
rtcptimeout = 10                        ; Max number of missed heartbeats from EL
recfile = /tmp/echolink_recorded.gsm    ;
astnode = 48270                         ; Change this!
context = radio-secure                  ; Default in code is echolink-in
; Max 3 servers
server1 = nasouth.echolink.org
server2 = naeast.echolink.org
server3 = server3.echolink.org
; To deny w6xxx you would add the statement: deny = w6xxx
; To prohibit computer-based connections you would write: permit = *-*
; To allow access to only a select group of callsigns: permit = w6abc,w6def,...
permit = KB2YMD-L,TG9AOR-L,KB2YMD                               ; comma delimited list of callsign, type (-r)
; deny

; Remote text commands thru netcat:
; o.conip <IPaddress>    (request a connect)  ===============>I have tried this by issuing nc -u 127.0.0.1 32767 and then at the prompt issuing the o.conip xxx.xxx.xx.xxx but I do not get a reply or NAK and Echolink does not connect to the IP requested. What is the proper command syntax for this? Thanks.
; o.dconip <IPaddress>   (request a disconnect)
; o.rec                  (turn on/off recording)
ipaddr = 127.0.0.1
port = 32767
#includeifexists custom/echolink.conf

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


Re: "Blocked" Message on Brandmeister

Steve N4IRS
 

Well,
Then I don't know what to tell ya.

On 06/09/2018 07:33 PM, Mike Swiatkowski via Groups.Io wrote:
Not that I know of....


Re: "Blocked" Message on Brandmeister

Mike, AA9VI
 

Not that I know of....


ASL (or DMR) to YSF #brandmeister

Jon KM8V
 

Hi there. The DMR <-> ASL gateway is running great.

I'm reading https://dvswitch.groups.io/g/main/wiki/Bridge-DMR-to-YSF-Narrow and wondering if it's possible to easily add a connection from ASL -> a YSF reflector, and if so, does it require a dongle or can it be done completely in software?

Thanks & 73 de KM8V


Re: How to configure a ASL server

TG9AOR
 

On Fri, Jun 8, 2018 at 07:48 pm, Steve N4IRS wrote:
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
I requested and used my node for the echolink connection (48270), it works, it connects immediately upon starting the asterisk service.
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
My node is 540570(EL). Does my ASL Node accept connections from other ASL nodes? Will they in turn go out on my EL connection?

Now you want to ADD a node for Analog_Bridge. [1999] rxchannel = USRP/127.0.0.1:34001:32001; GNU Radio interface USRP
This is under 48270(the [1999] rxchannel = USRP, and it is using the USRP channel driver. I set up 48270 as a hub(no radio)
Make sense?
I interpreted the 1999 is the ON/OFF switch that will allow DMR to enter the Allstar network or viceversa, and you activate it with the AllStar CLI.

Thanks.

 

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

 On Fri, Jun 8, 2018 at 07:48 pm, Steve N4IRS wrote:
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

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


Re: Repeater ID can not be the same as subscriber ID

Chris Andrist, KC7WSU
 

Looks like I forgot to tell Analog_Bridge which ini to look at. All is working now.

Regards,

Chris Andrist, KC7WSU
DMR-UTAH

On Jun 8, 2018, at 9:19 PM, Steve N4IRS <szingman@...> wrote:

Chris,
I just pasted your AMBE_AUDIO stanza into a test Analog_Bridge.ini I did not get the error. Could you please post the complete startup from Analog_bridge.

Thanks, Steve

On 06/08/2018 11:08 PM, Chris Andrist, KC7WSU wrote:

I: 2018-06-09 03:08:10.164 Analog Bridge Version 1.1 Wed May 30 09:44:39 EDT 2018
I: 2018-06-09 03:08:10.164 Copyright (C) 2018 DVSwitch, INAD.
I: 2018-06-09 03:08:10.164 Created by Mike N4IRR and Steve N4IRS
I: 2018-06-09 03:08:10.164 Analog Bridge comes with ABSOLUTELY NO WARRANTY
I: 2018-06-09 03:08:10.164
I: 2018-06-09 03:08:10.164 This software is for use on amateur radio networks only,
I: 2018-06-09 03:08:10.164 it is to be used for educational purposes only. Its use on
I: 2018-06-09 03:08:10.164 commercial networks is strictly prohibited.
I: 2018-06-09 03:08:10.164
I: 2018-06-09 03:08:10.164 Analog Bridge is starting
F: 2018-06-09 03:08:10.165 Repeater ID can not be the same as subscriber ID




Here is the info from my Analog_Bridge.ini

; Information for xx_Bridges (Where xx is MMDVM, HB, IPSC)
[AMBE_AUDIO]
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 31000                     ; AMBE frames from xx_Bridge (should match "toGatewayPor$
toDMRPort = 31003                       ; AMBE frames from xx_Bridge (should match "fromGatewayP$
ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2000                      ; Minimum time in MS for hang delay
gatewayDmrId = 3149010                  ; ID to use when transmitting from Analog_Bridge
repeaterID = 314905                     ; ID of source repeater
txTg = 31490                            ; TG to use for all frames received from Analog_Bridge -$
txTs = 1                                ; Slot to use for frames received from Analog_Bridge -> $
colorCode = 1                           ; Color Code to assign DMR frames


gatewayDmrId and repeaterID are not the same, not sure why I am getting this.

Regards,

Chris Andrist, KC7WSU
DMR-UTAH

8341 - 8360 of 9925