Date   

Re: Controlling DVSwitch from AllStar

 

On 10/11/20 8:25 am, Steve N4IRS wrote:
It was in the first message, but here it is again:

Ahh OK sorry, must have been half asleep when I read your first reply. 
Thanks again.  I'm about to have some fun with my scripting. :) 

--
73 de Tony VK3JED/VK3IRL
http://vkradio.com


Re: Controlling DVSwitch from AllStar

Steve N4IRS
 

dvswitch,sh is installed with MMDVM_Bridge. it's in /opt/MMDVM_Bridge.
No, you can install DVSwitch Server on ASL 1.01. You do not need a second RPi
Yes, you can have python 3.7 and 3.x on the same machine.
As to controlling DVSwitch with voice, if you can run a bash script and pass a parameter, you should be able to control DVSwitch Server.

On 11/9/20 5:24 PM, Neil k8it wrote:

Hi, I have two questions. Where  can I download switch.sh?  Is it included in the package allready released?  Question 2.  With a RPI3 plus, do I need two PI boards to run Allstar 1.0, DVSWITCH, Python 2.7 at the same time? The purpose of Python is to interface with remote USe GPIO.  IT allows me to have a low voltage data bus between a A    LLSTAR node and an Amazon Alexa Echo Dot.  I use the Dot Routine functions to control the bus, allowing voice commands for Allstar.  Now I want to expand it for the digital modes. As I am totatlly blind, the voice control is a huge help. It will also work for mobile users.

From: "Steve N4IRS" <szingman@msgstor.com>
Sent: Monday, November 09, 2020 8:10 AM
To: <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Controlling DVSwitch from AllStar

Tony,
I'm working out a issue with changing TGs now. I hope you have been using dvswitch.sh to control the server. If you have not, you need to be.
dvswitch.sh was built for just this thing in mind. I have to do a updated write up but here is most of it in message form. First, let's make sure you have the private node setup to work best with DVSwitch.
These are the recommended settings you should have. You may have other parameters:

[1XXX]
rxchannel = USRP/127.0.0.1:34001:32001  ; Use the USRP channel driver. Must be enabled in modules.conf
                    ; 127.0.0.1 = IP of the target application
                    ; 34001 = UDP port the target application is listening on
                    ; 32001 = UDP port ASL is listening on

duplex = 0          ; 0 = Half duplex with no telemetry tones or hang time. Ah, but Allison STILL talks!

hangtime = 0        ; squelch tail hang time 0
althangtime = 0     ; longer squelch tail hang time 0

holdofftelem = 1    ; Hold off all telemetry when signal is present on receiver or from connected nodes
                    ; except when an ID needs to be done and there is a signal coming from a connected node.

telemdefault = 0    ; 0 = telemetry output off. Don't send Allison to DMR !!!!!!!!!!!!!!!!! Trust me.

telemdynamic = 0    ; 0 = disallow users to change the local telemetry setting with a COP command,

linktolink = no     ; disables forcing physical half-duplex operation of main repeater while
                    ; still keeping half-duplex semantics (optional)

nounkeyct = 1       ; Set to a 1 to eliminate courtesy tones and associated delays.

totime = 180000     ; transmit time-out time (in ms) (optional, default 3 minutes 180000 ms)

idrecording = |ie   ; id recording or morse string see http://ohnosec.org/drupal/node/87
idtalkover = |ie    ; Talkover ID (optional) default is none see http://ohnosec.org/drupal/node/129

Now, lets add some commands to control the modes from ASL. Add this to your [functions stanza]. I chose 0 as a first character since it's not used in the default ASL.

; mode commands sent via DTMF
00 = cmd, /opt/MMDVM_Bridge/dvswitch.sh ; unused
01 = cmd, /opt/MMDVM_Bridge/dvswitch.sh ; unused
02 = cmd, /opt/MMDVM_Bridge/dvswitch.sh ; unused
03 = cmd, /opt/MMDVM_Bridge/dvswitch.sh tune unlink  ; Unlink from last TG / reflector
04 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode DMR
05 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode DSTAR
06 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode YSF
07 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode P25
08 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode NXDN

To dial a TG number or reflector number, we need to pass a arbitrary number of string to dvswitch.sh

; This nice simple one line function (and dialplan) was written by Mike KB8JNM. It will allow you to pass arbitrary string of digits to a external script for processing.
; We are going to use this to pass a TG or reflector number (DMR, NXDN, P25 YSF) to Analog_Bridge so that you can change the TG you are connected to from the DTMF pad on your analog
; radio. Example: If you dial *093100 (read this as *09 3100) you can tell dvswitch.sh to tune to TG 3100 on the current digital mode.

09=autopatchup,context=tgtune,dialtime=90000,farenddisconnect=1,noct,quiet=1

Add this to extensions.conf This is a work in progress and I will post a update when I'm ready.

[tgtune]
exten = _X.,1,noop ; Wait,1
exten = _X.,n,System(/opt/MMDVM_Bridge/dvswitch.sh mute TLV)
exten = _X.,n,System(/opt/MMDVM_Bridge/dvswitch.sh tune ${EXTEN})
exten = _X.,n,System(/opt/MMDVM_Bridge/dvswitch.sh mute OFF)
exten = _X.,n,Hangup









On 11/8/2020 11:13 PM, Tony Langdon wrote:
I've installed an instance of DVSwitch on my AllStar node, and I've been
able to link it to Brandmeister and select talkgroups from the commend
line.  I'm yet to get it working via AllStar commands.  The USRP
interface is working well.  I have it running on a private node, so I
can isolate the digital gateway from the node, when it's not in use by
disconnecting the private node from my main AllStar node.

In addition to getting the AllStar side working (for future control from
remote stations), I'd also like to be able to link to the other modes -
YSF, P25, etc, again ideally using DTMF comands.

Is there any documentation that I can look up?  I am running ASL and
DVSwitch on a Debian 9 PC.






--
This email has been checked for viruses by AVG.
https://www.avg.com



Re: Controlling DVSwitch from AllStar

Neil k8it
 

Hi, I have two questions. Where can I download switch.sh? Is it included in the package allready released? Question 2. With a RPI3 plus, do I need two PI boards to run Allstar 1.0, DVSWITCH, Python 2.7 at the same time? The purpose of Python is to interface with remote USe GPIO. IT allows me to have a low voltage data bus between a A LLSTAR node and an Amazon Alexa Echo Dot. I use the Dot Routine functions to control the bus, allowing voice commands for Allstar. Now I want to expand it for the digital modes. As I am totatlly blind, the voice control is a huge help. It will also work for mobile users.

From: "Steve N4IRS" <szingman@msgstor.com>
Sent: Monday, November 09, 2020 8:10 AM
To: <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Controlling DVSwitch from AllStar

Tony,
I'm working out a issue with changing TGs now. I hope you have been using dvswitch.sh to control the server. If you have not, you need to be.
dvswitch.sh was built for just this thing in mind. I have to do a updated write up but here is most of it in message form. First, let's make sure you have the private node setup to work best with DVSwitch.
These are the recommended settings you should have. You may have other parameters:

[1XXX]
rxchannel = USRP/127.0.0.1:34001:32001 ; Use the USRP channel driver. Must be enabled in modules.conf
; 127.0.0.1 = IP of the target application
; 34001 = UDP port the target application is listening on
; 32001 = UDP port ASL is listening on

duplex = 0 ; 0 = Half duplex with no telemetry tones or hang time. Ah, but Allison STILL talks!

hangtime = 0 ; squelch tail hang time 0
althangtime = 0 ; longer squelch tail hang time 0

holdofftelem = 1 ; Hold off all telemetry when signal is present on receiver or from connected nodes
; except when an ID needs to be done and there is a signal coming from a connected node.

telemdefault = 0 ; 0 = telemetry output off. Don't send Allison to DMR !!!!!!!!!!!!!!!!! Trust me.

telemdynamic = 0 ; 0 = disallow users to change the local telemetry setting with a COP command,

linktolink = no ; disables forcing physical half-duplex operation of main repeater while
; still keeping half-duplex semantics (optional)

nounkeyct = 1 ; Set to a 1 to eliminate courtesy tones and associated delays.

totime = 180000 ; transmit time-out time (in ms) (optional, default 3 minutes 180000 ms)

idrecording = |ie ; id recording or morse string see http://ohnosec.org/drupal/node/87
idtalkover = |ie ; Talkover ID (optional) default is none see http://ohnosec.org/drupal/node/129

Now, lets add some commands to control the modes from ASL. Add this to your [functions stanza]. I chose 0 as a first character since it's not used in the default ASL.

; mode commands sent via DTMF
00 = cmd, /opt/MMDVM_Bridge/dvswitch.sh ; unused
01 = cmd, /opt/MMDVM_Bridge/dvswitch.sh ; unused
02 = cmd, /opt/MMDVM_Bridge/dvswitch.sh ; unused
03 = cmd, /opt/MMDVM_Bridge/dvswitch.sh tune unlink ; Unlink from last TG / reflector
04 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode DMR
05 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode DSTAR
06 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode YSF
07 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode P25
08 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode NXDN

To dial a TG number or reflector number, we need to pass a arbitrary number of string to dvswitch.sh

; This nice simple one line function (and dialplan) was written by Mike KB8JNM. It will allow you to pass arbitrary string of digits to a external script for processing.
; We are going to use this to pass a TG or reflector number (DMR, NXDN, P25 YSF) to Analog_Bridge so that you can change the TG you are connected to from the DTMF pad on your analog
; radio. Example: If you dial *093100 (read this as *09 3100) you can tell dvswitch.sh to tune to TG 3100 on the current digital mode.

09=autopatchup,context=tgtune,dialtime=90000,farenddisconnect=1,noct,quiet=1

Add this to extensions.conf This is a work in progress and I will post a update when I'm ready.

[tgtune]
exten = _X.,1,noop ; Wait,1
exten = _X.,n,System(/opt/MMDVM_Bridge/dvswitch.sh mute TLV)
exten = _X.,n,System(/opt/MMDVM_Bridge/dvswitch.sh tune ${EXTEN})
exten = _X.,n,System(/opt/MMDVM_Bridge/dvswitch.sh mute OFF)
exten = _X.,n,Hangup









On 11/8/2020 11:13 PM, Tony Langdon wrote:
I've installed an instance of DVSwitch on my AllStar node, and I've been
able to link it to Brandmeister and select talkgroups from the commend
line. I'm yet to get it working via AllStar commands. The USRP
interface is working well. I have it running on a private node, so I
can isolate the digital gateway from the node, when it's not in use by
disconnecting the private node from my main AllStar node.

In addition to getting the AllStar side working (for future control from
remote stations), I'd also like to be able to link to the other modes -
YSF, P25, etc, again ideally using DTMF comands.

Is there any documentation that I can look up? I am running ASL and
DVSwitch on a Debian 9 PC.





--
This email has been checked for viruses by AVG.
https://www.avg.com


Re: Controlling DVSwitch from AllStar

Steve N4IRS
 

It was in the first message, but here it is again:

Now, lets add some commands to control the modes from ASL. Add this to your [functions stanza]. I chose 0 as a first character since it's not used in the default ASL.

; mode commands sent via DTMF
00 = cmd, /opt/MMDVM_Bridge/dvswitch.sh ; unused
01 = cmd, /opt/MMDVM_Bridge/dvswitch.sh ; unused
02 = cmd, /opt/MMDVM_Bridge/dvswitch.sh ; unused
03 = cmd, /opt/MMDVM_Bridge/dvswitch.sh tune unlink  ; Unlink from last TG / reflector
04 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode DMR
05 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode DSTAR
06 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode YSF
07 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode P25
08 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode NXDN

On 11/9/20 4:15 PM, Tony Langdon wrote:
On 10/11/20 12:10 am, Steve N4IRS wrote:
Tony,
I'm working out a issue with changing TGs now. I hope you have been
using dvswitch.sh to control the server. If you have not, you need to be.
dvswitch.sh was built for just this thing in mind. I have to do a
updated write up but here is most of it in message form. First, let's
make sure you have the private node setup to work best with DVSwitch.
These are the recommended settings you should have. You may have other
parameters:
Thanks Steve.  I think I'm pretty close, as I took my AllStar settings
from my working multimode gateway, which I know I turned off all the
telemetry stuff on.  Will take a look at the rest and set it up.

And the other question is how can I add other modes (YSF, etc) to this?


Re: Controlling DVSwitch from AllStar

 

On 10/11/20 12:10 am, Steve N4IRS wrote:
Tony,
I'm working out a issue with changing TGs now. I hope you have been
using dvswitch.sh to control the server. If you have not, you need to be.
dvswitch.sh was built for just this thing in mind. I have to do a
updated write up but here is most of it in message form. First, let's
make sure you have the private node setup to work best with DVSwitch.
These are the recommended settings you should have. You may have other
parameters:

Thanks Steve.  I think I'm pretty close, as I took my AllStar settings
from my working multimode gateway, which I know I turned off all the
telemetry stuff on.  Will take a look at the rest and set it up.

And the other question is how can I add other modes (YSF, etc) to this?

--
73 de Tony VK3JED/VK3IRL
http://vkradio.com


Re: XLX899 <> Allstar 40171

Patrick Perdue
 

If you're using HamVoIP, it's much, much easier to dedicate a second Pi to DVSwitch and connect USRP between them on the LAN. I've done this, and it works well. I also have a couple of ASL 1.01 systems. Once you have ASL up and running, it's a lot easier to integrate DVSwitch on the same hosting machine than with HamVoIP.


On 11/9/2020 1:24 PM, Daren. 2E0LXY. wrote:

Ah OK many thanks for the reply. 
I installed HAMVOIP as it was so much easier than installing the other system. 
I actually can't do the other system after trying so many times I gave up. 
Looks like I may have to lock myself in a padded room and try again! 😂 


Re: XLX899 <> Allstar 40171

Daren. 2E0LXY.
 

Ah OK many thanks for the reply. 
I installed HAMVOIP as it was so much easier than installing the other system. 
I actually can't do the other system after trying so many times I gave up. 
Looks like I may have to lock myself in a padded room and try again! 😂 


Re: Controlling DVSwitch from AllStar

Steve N4IRS
 

Tony,
I'm working out a issue with changing TGs now. I hope you have been using dvswitch.sh to control the server. If you have not, you need to be.
dvswitch.sh was built for just this thing in mind. I have to do a updated write up but here is most of it in message form. First, let's make sure you have the private node setup to work best with DVSwitch.
These are the recommended settings you should have. You may have other parameters:

[1XXX]
rxchannel = USRP/127.0.0.1:34001:32001  ; Use the USRP channel driver. Must be enabled in modules.conf
                    ; 127.0.0.1 = IP of the target application
                    ; 34001 = UDP port the target application is listening on
                    ; 32001 = UDP port ASL is listening on

duplex = 0          ; 0 = Half duplex with no telemetry tones or hang time. Ah, but Allison STILL talks!

hangtime = 0        ; squelch tail hang time 0
althangtime = 0     ; longer squelch tail hang time 0

holdofftelem = 1    ; Hold off all telemetry when signal is present on receiver or from connected nodes
                    ; except when an ID needs to be done and there is a signal coming from a connected node.

telemdefault = 0    ; 0 = telemetry output off. Don't send Allison to DMR !!!!!!!!!!!!!!!!! Trust me.

telemdynamic = 0    ; 0 = disallow users to change the local telemetry setting with a COP command,

linktolink = no     ; disables forcing physical half-duplex operation of main repeater while
                    ; still keeping half-duplex semantics (optional)

nounkeyct = 1       ; Set to a 1 to eliminate courtesy tones and associated delays.

totime = 180000     ; transmit time-out time (in ms) (optional, default 3 minutes 180000 ms)

idrecording = |ie   ; id recording or morse string see http://ohnosec.org/drupal/node/87
idtalkover = |ie    ; Talkover ID (optional) default is none see http://ohnosec.org/drupal/node/129

Now, lets add some commands to control the modes from ASL. Add this to your [functions stanza]. I chose 0 as a first character since it's not used in the default ASL.

; mode commands sent via DTMF
00 = cmd, /opt/MMDVM_Bridge/dvswitch.sh ; unused
01 = cmd, /opt/MMDVM_Bridge/dvswitch.sh ; unused
02 = cmd, /opt/MMDVM_Bridge/dvswitch.sh ; unused
03 = cmd, /opt/MMDVM_Bridge/dvswitch.sh tune unlink  ; Unlink from last TG / reflector
04 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode DMR
05 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode DSTAR
06 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode YSF
07 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode P25
08 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode NXDN

To dial a TG number or reflector number, we need to pass a arbitrary number of string to dvswitch.sh

; This nice simple one line function (and dialplan) was written by Mike KB8JNM. It will allow you to pass arbitrary string of digits to a external script for processing.
; We are going to use this to pass a TG or reflector number (DMR, NXDN, P25 YSF) to Analog_Bridge so that you can change the TG you are connected to from the DTMF pad on your analog
; radio. Example: If you dial *093100 (read this as *09 3100) you can tell dvswitch.sh to tune to TG 3100 on the current digital mode.

09=autopatchup,context=tgtune,dialtime=90000,farenddisconnect=1,noct,quiet=1

Add this to extensions.conf This is a work in progress and I will post a update when I'm ready.

[tgtune]
exten = _X.,1,noop ; Wait,1
exten = _X.,n,System(/opt/MMDVM_Bridge/dvswitch.sh mute TLV)
exten = _X.,n,System(/opt/MMDVM_Bridge/dvswitch.sh tune ${EXTEN})
exten = _X.,n,System(/opt/MMDVM_Bridge/dvswitch.sh mute OFF)
exten = _X.,n,Hangup

On 11/8/2020 11:13 PM, Tony Langdon wrote:
I've installed an instance of DVSwitch on my AllStar node, and I've been
able to link it to Brandmeister and select talkgroups from the commend
line.  I'm yet to get it working via AllStar commands.  The USRP
interface is working well.  I have it running on a private node, so I
can isolate the digital gateway from the node, when it's not in use by
disconnecting the private node from my main AllStar node.

In addition to getting the AllStar side working (for future control from
remote stations), I'd also like to be able to link to the other modes -
YSF, P25, etc, again ideally using DTMF comands.

Is there any documentation that I can look up?  I am running ASL and
DVSwitch on a Debian 9 PC.


Controlling DVSwitch from AllStar

 

I've installed an instance of DVSwitch on my AllStar node, and I've been
able to link it to Brandmeister and select talkgroups from the commend
line.  I'm yet to get it working via AllStar commands.  The USRP
interface is working well.  I have it running on a private node, so I
can isolate the digital gateway from the node, when it's not in use by
disconnecting the private node from my main AllStar node.

In addition to getting the AllStar side working (for future control from
remote stations), I'd also like to be able to link to the other modes -
YSF, P25, etc, again ideally using DTMF comands.

Is there any documentation that I can look up?  I am running ASL and
DVSwitch on a Debian 9 PC.

--
73 de Tony VK3JED/VK3IRL
http://vkradio.com


Re: Pass callsigns YSF<>DMR via MMDVM_Bridge #mmdvm_bridge

Steve N4IRS
 

I: 2020-11-08 20:48:44.634 MMDVM_Bridge:
I: 2020-11-08 20:48:44.634 Portions Copyright (C) 2018, 2019, 2020 DVSwitch, INAD.
I: 2020-11-08 20:48:44.634 Hacks by Mike N4IRR and Steve N4IRS
I: 2020-11-08 20:48:44.634 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I: 2020-11-08 20:48:44.634 This software is for use on amateur radio networks only,
I: 2020-11-08 20:48:44.634 it is to be used for educational purposes only. Its use on
I: 2020-11-08 20:48:44.634 commercial networks is strictly prohibited.
I: 2020-11-08 20:48:44.634 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2020-11-08 20:48:44.634 MMDVM_Bridge-20201031_V1.6.0 is starting
M: 2020-11-08 20:48:44.634 Built 15:53:02 Oct 28 2020 (GitID #008e177)


On 11/8/20 5:26 PM, hello@... wrote:
Thanks a lot Steve. I'm super happy now.

Appreciate the help.

Are you a developer of this software? 

73


Re: Pass callsigns YSF<>DMR via MMDVM_Bridge #mmdvm_bridge

@hamzahradio
 

Thanks a lot Steve. I'm super happy now.

Appreciate the help.

Are you a developer of this software? 

73


Re: Pass callsigns YSF<>DMR via MMDVM_Bridge #mmdvm_bridge

Steve N4IRS
 

http://www.pistar.uk/downloads/DMRIds.dat

I suggest you build your bridge with DVSwitch Server so that the files are downloaded daily.

On 11/8/20 4:53 PM, hello@... wrote:
Ah OK, where can I download the new file from?


Re: Pass callsigns YSF<>DMR via MMDVM_Bridge #mmdvm_bridge

@hamzahradio
 

Ah OK, where can I download the new file from?


Re: Pass callsigns YSF<>DMR via MMDVM_Bridge #mmdvm_bridge

Steve N4IRS
 

MB was unable to resolve DMRID 2680070 so it passed it to YSF as a callsign.
If you get the DMR ID from from github, it's not current.

Steve

M: 2020-11-08 21:19:41.225 DMR Slot 2, received network voice header from 2680070 to TG 73583
M: 2020-11-08 21:19:41.226 YSF, TX state = ON
I: 2020-11-08 21:19:41.226 YSF, Begin TX: src=2680070 rpt=0 dst=73583 slot=2 cc=0 metadata=2680070


On 11/8/20 4:22 PM, hello@... wrote:
Just did a tail command of the log, it has the callsign of the person who TX'd CT1ERY, but it just passed through his DMRID to yaesu not the callsign.


M: 2020-11-08 21:19:35.067 YSF, TX state = OFF
M: 2020-11-08 21:19:41.225 DMR Slot 2, received network voice header from 2680070 to TG 73583
M: 2020-11-08 21:19:41.226 YSF, TX state = ON
I: 2020-11-08 21:19:41.226 YSF, Begin TX: src=2680070 rpt=0 dst=73583 slot=2 cc=0 metadata=2680070
I: 2020-11-08 21:19:41.282 YSF, Narrow transmit (72 bit)
M: 2020-11-08 21:19:41.829 DMR Talker Alias (Data Format 1, Received 6/22 char): 'CT1ERY'
M: 2020-11-08 21:19:41.829 DMR Slot 2, Embedded Talker Alias Header
M: 2020-11-08 21:19:41.829 0000:  04 00 6C 43 54 31 45 52 59                         *..lCT1ERY*
M: 2020-11-08 21:19:43.447 DMR Slot 2, received network end of voice transmission, 2.3 seconds, 0% packet loss, BER: 0.0%
M: 2020-11-08 21:19:43.447 YSF, TX state = OFF
 


Re: Pass callsigns YSF<>DMR via MMDVM_Bridge #mmdvm_bridge

@hamzahradio
 

Just did a tail command of the log, it has the callsign of the person who TX'd CT1ERY, but it just passed through his DMRID to yaesu not the callsign.


M: 2020-11-08 21:19:35.067 YSF, TX state = OFF
M: 2020-11-08 21:19:41.225 DMR Slot 2, received network voice header from 2680070 to TG 73583
M: 2020-11-08 21:19:41.226 YSF, TX state = ON
I: 2020-11-08 21:19:41.226 YSF, Begin TX: src=2680070 rpt=0 dst=73583 slot=2 cc=0 metadata=2680070
I: 2020-11-08 21:19:41.282 YSF, Narrow transmit (72 bit)
M: 2020-11-08 21:19:41.829 DMR Talker Alias (Data Format 1, Received 6/22 char): 'CT1ERY'
M: 2020-11-08 21:19:41.829 DMR Slot 2, Embedded Talker Alias Header
M: 2020-11-08 21:19:41.829 0000:  04 00 6C 43 54 31 45 52 59                         *..lCT1ERY*
M: 2020-11-08 21:19:43.447 DMR Slot 2, received network end of voice transmission, 2.3 seconds, 0% packet loss, BER: 0.0%
M: 2020-11-08 21:19:43.447 YSF, TX state = OFF
 


Re: Pass callsigns YSF<>DMR via MMDVM_Bridge #mmdvm_bridge

Steve N4IRS
 

Just copy a section of the log when there is traffic.

On 11/8/20 4:21 PM, hello@... wrote:
Hi, I downloaded the latest DMRIds.dat file from github and it's the mmdvm_bride.ini file is pointing to the right file path.
Do I need to do anything with permissions?

The log at /var/log/mmdvm is really quite long.

Also, appreciate the help Steve!


Re: Pass callsigns YSF<>DMR via MMDVM_Bridge #mmdvm_bridge

@hamzahradio
 

Hi, I downloaded the latest DMRIds.dat file from github and it's the mmdvm_bride.ini file is pointing to the right file path.
Do I need to do anything with permissions?

The log at /var/log/mmdvm is really quite long.

Also, appreciate the help Steve!


Re: Pass callsigns YSF<>DMR via MMDVM_Bridge #mmdvm_bridge

Steve N4IRS
 

Is the user database up to date? Please post MB log when there is traffic.

On 11/8/20 3:52 PM, hello@... wrote:
On the fusion reflector no DMR callsigns are being translated to the callsign, and when someone transmits on the fusion side, it just shows my DMRID on the pistar.
dashboard is here http://18.134.217.115/
TG 73583


Re: Pass callsigns YSF<>DMR via MMDVM_Bridge #mmdvm_bridge

@hamzahradio
 

On the fusion reflector no DMR callsigns are being translated to the callsign, and when someone transmits on the fusion side, it just shows my DMRID on the pistar.
dashboard is here http://18.134.217.115/
TG 73583


Re: DMR<>YSF Bridge - can't hear anything on the DMR side #mmdvm_bridge

@hamzahradio
 

Hi Steve,
I figured out the issue. I was following the guide made by KV4S - https://kv4s.com/2018/05/23/hosting-an-allstar-node-and-an-allstardmr-bridge-in-the-cloud/ - but using dmr<>ysf, I had to verify what’s in DVSwitch.ini matches what you are trying to use in the Analog_bridge.ini like this:
DVSwitch.ini             |       Analog_bridge.ini
[DMR]                    |       [AMBE_AUDIO]
Address = 127.0.0.1      |       server = 127.0.0.1
TXPort = 31100           |       fromDMRPort = 31100
RXPort = 31103           |       toDMRPort = 31103

It's now working.

2501 - 2520 of 9925