Welcome to DVSwitch

Or why not when you run the script to change TG’s just write the new
talkgroup to a text file since you have it already? No need to pull it
from anywhere. Then just read the Text file into your webpage.



Jeff Lehman, KC8QCH

E-mail: kc8qch@gmail.com

http://kc8qch.dx.am
Hamshack Hotline: 4218



Webmaster

Hamilton County ARPSC

http://www.hamcoarpsc.org

E-mail: hamcoarpsc@gmail.com

Phone: 513-452-6480



Allstar 47374 Administrator

World Wide Amateur Radio Guild

http://www.theguildglobal.org

E-Mail: kc8qch@theguildglobal.net



*From:* main@DVSwitch.groups.io <main@DVSwitch.groups.io> *On Behalf
Of *Steve N4IRS
*Sent:* Thursday, November 15, 2018 20:49
*To:* main@DVSwitch.groups.io
*Subject:* Re: [DVSwitch] ASL to DMR Bridge...reading talkgroups



My short off the top of my head answer. If you know what TG you
started on and tracked the changes, you know where you are.

Pseudo code:
Start the bridge
Send AB/MB to TG 9
Echo 9 to text file
From this point on, any change to the TG goes through the script and
the text file contains the current TG.

No matter where you go, there you are.

As I said, Mike and I have been talking about Metadata. AB exchanges
Metadata across the USRP channel. That is how a Transcoder sends
Metadata across the transcoder. MB1 <-> AB1 <-> AB2 <-MB2> There is a
need to be able to get metadata from MB1 to MB2 That data is passed
across the USRP channel (The connection between AB1 and AB2) The ASL
USRP channel drive does not send or receive Matadata. We are
discussing strategies to add Metadata to ASL without modifing the USRP
channel driver. Think AMI.

73, Steve N4IRS

On 11/15/18 8:32 PM, Michael Weaver - AC2VK wrote:

I was going to post the same question today. So +1 for this. A way
to query what the current talkgroup is.

Or why not when you run the script to change TG’s just write the new
talkgroup to a text file since you have it already? No need to pull it
from anywhere. Then just read the Text file into your webpage.

 

Jeff Lehman, KC8QCH

E-mail: kc8qch@gmail.com

http://kc8qch.dx.am
Hamshack Hotline: 4218

 

Webmaster

Hamilton County ARPSC

http://www.hamcoarpsc.org

E-mail: hamcoarpsc@gmail.com

Phone: 513-452-6480

 

Allstar 47374 Administrator

World Wide Amateur Radio Guild

http://www.theguildglobal.org

E-Mail: kc8qch@theguildglobal.net

 

*From:* main@DVSwitch.groups.io <main@DVSwitch.groups.io> *On Behalf
Of *Steve N4IRS
*Sent:* Thursday, November 15, 2018 20:49
*To:* main@DVSwitch.groups.io
*Subject:* Re: [DVSwitch] ASL to DMR Bridge...reading talkgroups

 

My short off the top of my head answer. If you know what TG you
started on and tracked the changes, you know where you are.

Pseudo code:
Start the bridge
Send AB/MB to TG 9
Echo 9 to text file
From this point on, any change to the TG goes through the script and
the text file contains the current TG.

No matter where you go, there you are.

As I said, Mike and I have been talking about Metadata. AB exchanges
Metadata across the USRP channel. That is how a Transcoder sends
Metadata across the transcoder. MB1 <-> AB1 <-> AB2 <-MB2> There is a
need to be able to get metadata from MB1 to MB2 That data is passed
across the USRP channel (The connection between AB1 and AB2) The ASL
USRP channel drive does not send or receive Matadata. We are
discussing strategies to add Metadata to ASL without modifing the USRP
channel driver. Think AMI.

73, Steve N4IRS

On 11/15/18 8:32 PM, Michael Weaver - AC2VK wrote:

I was going to post the same question today. So +1 for this. A way
to query what the current talkgroup is.

 

My short off the top of my head answer. If you know what TG you started on and tracked the changes, you know where you are.

Pseudo code:
Start the bridge
Send AB/MB to TG 9
Echo 9 to text file
From this point on, any change to the TG goes through the script and the text file contains the current TG.

No matter where you go, there you are.

As I said, Mike and I have been talking about Metadata. AB exchanges Metadata across the USRP channel. That is how a Transcoder sends Metadata across the transcoder. MB1 <-> AB1 <-> AB2 <-MB2> There is a need to be able to get metadata from MB1 to MB2 That data is passed across the USRP channel (The connection between AB1 and AB2) The ASL USRP channel drive does not send or receive Matadata. We are discussing strategies to add Metadata to ASL without modifing the USRP channel driver. Think AMI.

73, Steve N4IRS

I was going to post the same question today. So +1 for this. A way to query what the current talkgroup is.

I was going to post the same question today. So +1 for this. A way to query what the current talkgroup is.

with the same principal, call a python script, so i can return the talkgroup number to a webpage.

On 11/15/18 4:22 PM, Steve N4IRS wrote:

Define read. Voice feedback? Allison?

On 11/15/18 7:21 PM, Gregory Heinrichs wrote:

I can change the talkgroup via code below, i was wondering it there is a way to read it as well?
[code]
_sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
cmd = struct.pack("BB", 0x05, len(cmd))[0:2] + cmd
# Set the second value below to match the rxPort in the [AMBE_AUDIO] stanza of Analog_Bridge.ini
_sock.sendto(cmd, ('127.0.0.1', 31100))
_sock.close()
[/code]

Define read. Voice feedback? Allison?

On 11/15/18 7:21 PM, Gregory Heinrichs wrote:

I can change the talkgroup via code below, i was wondering it there is a way to read it as well?
[code]
_sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
cmd = struct.pack("BB", 0x05, len(cmd))[0:2] + cmd
# Set the second value below to match the rxPort in the [AMBE_AUDIO] stanza of Analog_Bridge.ini
_sock.sendto(cmd, ('127.0.0.1', 31100))
_sock.close()
[/code]

I can change the talkgroup via code below, i was wondering it there is a way to read it as well?
[code]
_sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
cmd = struct.pack("BB", 0x05, len(cmd))[0:2] + cmd
# Set the second value below to match the rxPort in the [AMBE_AUDIO] stanza of Analog_Bridge.ini
_sock.sendto(cmd, ('127.0.0.1', 31100))
_sock.close()
[/code]

Hello, sorry if I'm possibly mistaken group. Can you tell me the
procedure to activate, if possible, a connection (I suppose using
MMDVM_Bridge) between two XLX (example module B) but using a native
DSTAR protocol, such as DEXTRA or DCS? The comparison is with the old
XRF which for many reasons is no longer advisable to use it.
 
Thank you, 73
David IK5XMK

I didn't get Mike Z's code working out of the box and haven't had time to troubleshoot his yet.  My setup allows you to enter *8711 and then the talkgroup number you want to connect to.  the extenstions.conf will strip off the leading 1 and pass the variable into tg_connect.py.  The python script will read the ini, update txTg, write the ini file(side effect of removing all comments), and restart the analog bridge.  Backup your ini file first!

rpt.conf

871 = autopatchup,context=command_radio,noct=1,farenddisconnect=1,dialtime=20000,quiet=1

extensions.conf

[command_radio]
exten => _1X.,1,SayDigits(${EXTEN:1})
exten => _1X.,n,System(/scripts/tg_connect.py ${EXTEN:1})
exten => _1X.,n,Wait(2)
exten => _1X.,n,Hangup()

tg_connect.py

#!/usr/bin/env python
 
import sys
import socket
import struct
import os

#import parser
from ConfigParser import SafeConfigParser

#store cmd line arg
new_txTg = sys.argv[1]

#strip off first character
#new_txTg = new_txTg[1:]

#read config file
parser = SafeConfigParser()
parser.read('/opt/Analog_Bridge/Analog_Bridge.ini')
print "Existing talkgroup is: " + parser.get('AMBE_AUDIO', 'txTg')
print "Desired talkgroup is: " + new_txTg
 
#set config file
parser.set('AMBE_AUDIO', 'txTg', new_txTg)
 
#writing our configuration file to
with open('/opt/Analog_Bridge/Analog_Bridge.ini', 'wb') as configfile:
    parser.write(configfile)

#verify
parser.read('/opt/Analog_Bridge/Analog_Bridge.ini')
print "New talkgroup is: " + parser.get('AMBE_AUDIO', 'txTg')

#restart bridge
os.system('systemctl restart analog_bridge')

very much so, thanks Steve.

Next question, what will these statements look like? 

systemctl enable analog_bridge

systemctl start analog_bridge

because if you copy contents the program has the same name? how does the service know which is which or maybe on linux it doesn't matter?

:/opt/Analog_Bridge$ dir 

Analog_Bridge Analog_Bridge.ini





Can you point me in the right direction for setting up a private node? do I just copy my main node stanza and make it a number like 1999, 1998 ect? Seems like there was one there but i think i overwrote it.

On Wed, Nov 14, 2018 at 10:39 AM Steve N4IRS <szingman@...> wrote:

Russell,
As per usual there is more then one way to do this. He is a simple one:
Create 4 subdirectories:
mkdir MMDVM_Bridge_TG_1234
mkdir  MMDVM_Bridge_TG_9876
mkdir Analog_Bridge_TG_1234
mkdir Analog_Bridge_TG_9876

Copy the contents of /opt/MMDVM_Bridge into the new MMDVM_Bridge directories.
Copy the contents of /opt/Analog_Bridge into the new Analog_Bridge directories.
Setup MMDVM_Bridge_TG_1234 to connect to TG 1234 on BM as normal
Setup Analog_Bridge_TG_1234 to connect to TG 1234 as normal and point it at Private node 1234

The assumption is you used the default port numbers Check your work.
Now come the change, You can not reuse the port numbers you chose for TG 1234 so:
In the MMDVM_Bridge_TG_9876 directory edit DVSwitch.ini to change the port numbers in the [DMR] stanza
Make it easy to see the change
[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 36100                     ; Port to send AMBE TLV frames to (export)
RXPort = 36103                     ; Port to listen on (import)
Slot = 2                                   ; Export slot

In the Analog_Bridge_TG_9876 directory edit Analog_Bridge.ini to change the port numbers in the [AMBE_AUDIO] stanza
Match the ports use in DVSwitch.ini
[AMBE_AUDIO]
address = 127.0.0.1                     ; IP address of xx_Bridge
txPort = 36103                          ; Transmit TLV frames to partner on this port
rxPort = 36100                          ; Listen for TLV frames from partner on this port

As with MMDVM_Bridge <-> Analog_Bridge where you can not reuse the port numbers, It's the same for Analog_Bridge <-> ASL.
In the Analog_Bridge_TG_9876 directory edit Analog_Bridge.ini to change the port numbers in the [USRP] stanza
[USRP]
address = 127.0.0.1                     ; IP address of USRP partner (Allstar/Asterisk or another Analog_Bridge)
txPort = 38001                          ; Transmit USRP frames on this port
rxPort = 39001                          ; Listen for USRP frames on this port

Match the above port numbers for private node 9876 in rpt.conf

Does that help?

73, Steve N4IRS

On 11/14/2018 11:18 AM, Russell, KV4S wrote:

I don't have a lot of experience with private nodes but I've been working on a personal hub that is working fine with DVSwitch.

What I envision is having multiple instances of the DVSwitch (Analog/MMDVM/DVSwitch) with each instance using a different talk group. I would dedicate a private node to the different talk groups then use the main hub (public) to connect to the private nodes on the fly using  Allmon to link up the different private nodes. I would need to move the existing TG from the public hub to a private so by default nothing is linked unless I tell it to in Allmon.

I also do know how to setup multiple instances of DVSwich.

Any guidance on this?

I don't have a lot of experience with private nodes but I've been working on a personal hub that is working fine with DVSwitch.

What I envision is having multiple instances of the DVSwitch (Analog/MMDVM/DVSwitch) with each instance using a different talk group. I would dedicate a private node to the different talk groups then use the main hub (public) to connect to the private nodes on the fly using  Allmon to link up the different private nodes. I would need to move the existing TG from the public hub to a private so by default nothing is linked unless I tell it to in Allmon.

I also do know how to setup multiple instances of DVSwich.

Any guidance on this?