Date   

Re: Multiple private nodes connected to different talkgroups

 

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?


Re: Multiple private nodes connected to different talkgroups

Steve N4IRS
 

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?


Re: ASL to DMR Bridge...changing talkgroups

 

is it possible to make this work with Allmon2 vs DTMF?


On Tue, Nov 13, 2018 at 4:08 PM Michael Weaver <mchlwvr614@...> wrote:
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')


Multiple private nodes connected to different talkgroups

 

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?


Re: ASL to DMR Bridge...changing talkgroups

Steve N4IRS
 

Neil,
The purpose of this list it to exchange information. Moving information exchange off list defeats that purpose.

Steve N4IRS

On 11/14/2018 11:08 AM, Neil k8it wrote:
Could you please send me off list your python program and your modifying extensions . Conf. Thank you
73 Neil k8it
K8it@...


On Nov 13, 2018, at 5:08 PM, Michael Weaver <mchlwvr614@...> wrote:

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')


Re: ASL to DMR Bridge...changing talkgroups

Neil k8it
 

Could you please send me off list your python program and your modifying extensions . Conf. Thank you
73 Neil k8it

On Nov 13, 2018, at 5:08 PM, Michael Weaver <mchlwvr614@...> wrote:

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')


Re: ASL to DMR Bridge...changing talkgroups

Michael Weaver - AC2VK
 

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')


Re: ASL to DMR Bridge...changing talkgroups

Mike KB8JNM
 

I don't know if you were directing this to me Mike/KB8JNM or not

Your message is to the dvswitch main group @ goups.io

---

Ports do not have to be 'any certain port number' except:

to not conflict with any port number in use &

to match the port number where it is handshaking TO or FROM.

If you look at the HOW2, there is a nice graphic showing the digital flow of ports for dmr to asl.


I use (analog_bridge.ini)

fromDMRPort = 31100                 
toDMRPort = 31103 


It must match the port number it interfaces with in

dvswitch.ini

TXPort = 31100                  ; Port to send AMBE TLV frames to (export)
RXPort = 31103                  ; Port to listen on (import)


The port number you use are up to you. But they must match where they are going to or coming from without conflict.

All modes/formats would be they same.

...mike/kb8jnm


On 11/13/2018 12:14 AM, Gregory Heinrichs wrote:
hi Mike, i just wanted to confirm that the port 31000 is in reference to fromDMRPort, so i should change the script to 31100 correct? Below is from my ini.
[AMBE_AUDIO]
server = 127.0.0.1                
fromDMRPort = 31100                
toDMRPort = 31103
.
.
.


Re: ASL to DMR Bridge...changing talkgroups

Gregory Heinrichs
 

hi Mike, i just wanted to confirm that the port 31000 is in reference to fromDMRPort, so i should change the script to 31100 correct? Below is from my ini.
[AMBE_AUDIO]
server = 127.0.0.1                
fromDMRPort = 31100                
toDMRPort = 31103
.
.
.


Re: ASL to DMR Bridge...changing talkgroups

Gregory Heinrichs
 

hi Mike, i just wanted to confirm that the port 31000 is in reference to fromDMRPort, so i should change the script to 31100 correct? Below is from my ini.
[AMBE_AUDIO]
server = 127.0.0.1                
fromDMRPort = 31100                
toDMRPort = 31103
.
.
.


Re: Bridging a P25Reflector and a YSFReflector?

Mike, KI0IK
 

Thanks for the replies.  I'll give MMDVM_Bridge a go and see if I can get it working with my setup.  I'll checkout MMDVM_CM too.  

Thanks
Mike

On Sat, Nov 10, 2018 at 9:33 AM Steve N4IRS <szingman@...> wrote:
That is intended to be used on a hotspot or repeater.
For reflector to reflector, MMDVM_Bridge will do that quite simply. No transcode required.

Steve N4IRS

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Alec-N1AJW <alec.wasserman@...>
Sent: Saturday, November 10, 2018 10:27:07 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Bridging a P25Reflector and a YSFReflector?
 
there's a ysf wide to p25 bridge made by Andy iin Chile.  Juribeparada. I have never tried that one.     https://github.com/juribeparada/MMDVM_CM


Re: DMR -> P25 issue

Steve N4IRS
 

Andy,
Thanks for the clarification.

Steve N4IRS

On 11/11/18 5:38 AM, andrew144500@... wrote:
So,
here is a little more information about what is/was going on. 
On October 4 a change to MMDVMHost was pushed to github. The change effected P25. https://github.com/g4klx/MMDVMHost/commit/85bc8357aa1967d692901addd6ebefd89a8f32f6
When Andy at Pi-Star updated the binaries for Pi-Star, he rolled in the changes. Those changes broke P25 RF. When the problem was reported to Pi-Star, Andy reverted to a older version of MMDVMHost.
Here is his announcement: https://forum.pistar.uk/viewtopic.php?f=23&p=4003&sid=ffb1861eab2e15bd078550a906388b6b#p4003

If you are running Pi-Star, updating should fix the issue. If you compile your own MMDVMHost, revert to the above commit.

A little more, more information... 
Actually, we never reverted back to the older version.
We rewrote the broken P25 part of MMDVM host and pushed that out
through the pistar updates, then offered the changes up to MMDVM
and made Jon aware of the problem. 😀
Regards A. 


Re: DMR -> P25 issue

andrew (callsign)
 

So,
here is a little more information about what is/was going on. 
On October 4 a change to MMDVMHost was pushed to github. The change effected P25. https://github.com/g4klx/MMDVMHost/commit/85bc8357aa1967d692901addd6ebefd89a8f32f6
When Andy at Pi-Star updated the binaries for Pi-Star, he rolled in the changes. Those changes broke P25 RF. When the problem was reported to Pi-Star, Andy reverted to a older version of MMDVMHost.
Here is his announcement: https://forum.pistar.uk/viewtopic.php?f=23&p=4003&sid=ffb1861eab2e15bd078550a906388b6b#p4003

If you are running Pi-Star, updating should fix the issue. If you compile your own MMDVMHost, revert to the above commit.

A little more, more information... 
Actually, we never reverted back to the older version.
We rewrote the broken P25 part of MMDVM host and pushed that out
through the pistar updates, then offered the changes up to MMDVM
and made Jon aware of the problem. 😀
Regards A. 


Re: Bridging a P25Reflector and a YSFReflector?

Steve N4IRS
 

That is intended to be used on a hotspot or repeater.
For reflector to reflector, MMDVM_Bridge will do that quite simply. No transcode required.

Steve N4IRS

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Alec-N1AJW <alec.wasserman@...>
Sent: Saturday, November 10, 2018 10:27:07 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Bridging a P25Reflector and a YSFReflector?
 
there's a ysf wide to p25 bridge made by Andy iin Chile.  Juribeparada. I have never tried that one.     https://github.com/juribeparada/MMDVM_CM


Re: Bridging a P25Reflector and a YSFReflector?

Alec-N1AJW
 

there's a ysf wide to p25 bridge made by Andy iin Chile.  Juribeparada. I have never tried that one.     https://github.com/juribeparada/MMDVM_CM


Re: DMR -> P25 issue

Steve N4IRS
 

So,
here is a little more information about what is/was going on. 
On October 4 a change to MMDVMHost was pushed to github. The change effected P25. https://github.com/g4klx/MMDVMHost/commit/85bc8357aa1967d692901addd6ebefd89a8f32f6
When Andy at Pi-Star updated the binaries for Pi-Star, he rolled in the changes. Those changes broke P25 RF. When the problem was reported to Pi-Star, Andy reverted to a older version of MMDVMHost.
Here is his announcement: https://forum.pistar.uk/viewtopic.php?f=23&p=4003&sid=ffb1861eab2e15bd078550a906388b6b#p4003

If you are running Pi-Star, updating should fix the issue. If you compile your own MMDVMHost, revert to the above commit.

73, Steve N4IRS 


Re: DMR -> P25 issue

va3czk@...
 

FYI.  

This issue is resolved now after last night Pi Star update. 

73' va3czk


Re: DMR -> P25 issue

David Griffith NZ6D
 

Sorry guys. Didn't look at the recipient's...



Sent from my Verizon, Samsung Galaxy smartphone

-------- Original message --------
From: "David Griffith NZ6D via Groups.Io" <nz6d@...>
Date: 11/9/18 7:48 PM (GMT-07:00)
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR -> P25 issue

PS.. I am in Albuquerque New Mexico now so I don't really have access. Helping my Dad....



Sent from my Verizon, Samsung Galaxy smartphone

-------- Original message --------
From: va3czk@...
Date: 11/9/18 10:06 AM (GMT-07:00)
To: main@DVSwitch.groups.io
Subject: [DVSwitch] DMR -> P25 issue

Does anyone else experiencing an issue with the transcoding from P25 to DMR ?

Not sure what have changed but since yesterday DMR ↔ P25 on our bridge is acting up. P25 -> DMR works well, however DMR ->25 is not getting through the digital squelch on the radio. When I manually open the squelch/monitor I can hear everything fine. (P25 to P25 on same TG is working fine)
The bridge has been working seamlessly ever since it was set up several months ago.

Thanks Jerry va3czk


Re: DMR -> P25 issue

David Griffith NZ6D
 

PS.. I am in Albuquerque New Mexico now so I don't really have access. Helping my Dad....



Sent from my Verizon, Samsung Galaxy smartphone

-------- Original message --------
From: va3czk@...
Date: 11/9/18 10:06 AM (GMT-07:00)
To: main@DVSwitch.groups.io
Subject: [DVSwitch] DMR -> P25 issue

Does anyone else experiencing an issue with the transcoding from P25 to DMR ?

Not sure what have changed but since yesterday DMR ↔ P25 on our bridge is acting up. P25 -> DMR works well, however DMR ->25 is not getting through the digital squelch on the radio. When I manually open the squelch/monitor I can hear everything fine. (P25 to P25 on same TG is working fine)
The bridge has been working seamlessly ever since it was set up several months ago.

Thanks Jerry va3czk


Re: DMR -> P25 issue

David Griffith NZ6D
 

Hi Jerry. Yes we have had some same issues. Nothing changed In our config and it just stopped working. We are looking at the logs and configs. Did you find d anything? 
Dave NZ6D



Sent from my Verizon, Samsung Galaxy smartphone

-------- Original message --------
From: va3czk@...
Date: 11/9/18 10:06 AM (GMT-07:00)
To: main@DVSwitch.groups.io
Subject: [DVSwitch] DMR -> P25 issue

Does anyone else experiencing an issue with the transcoding from P25 to DMR ?

Not sure what have changed but since yesterday DMR ↔ P25 on our bridge is acting up. P25 -> DMR works well, however DMR ->25 is not getting through the digital squelch on the radio. When I manually open the squelch/monitor I can hear everything fine. (P25 to P25 on same TG is working fine)
The bridge has been working seamlessly ever since it was set up several months ago.

Thanks Jerry va3czk

7401 - 7420 of 9801