Date   

Re: P25 Gateway <---> allstar

Steve N4IRS
 

Analog_Bridge.ini?

On 05/16/2018 06:41 PM, Jeff Carrier wrote:
Here is dvswitch.ini

; MMDVM_Bridge configuration file.
;   This file should be placed along side of MMDVM_Bridge or it can be
;   supplied as a path on the MMDVM_BRIDGE environment variable.

; Configure the Quantar Repeater Partner
; Note that the TX and RX ports are already reversed for MMDVM_Bridge <--> Quantar_Bridge
[QUANTAR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 34103                  ; Port to send AMBE TLV frames to (export)
RXPort = 34100                  ; Port to listen on (import)
quantarPort = 1994              ; HDLC frames To/From the Quantar repeater
logLevel = 2                    ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
debug = 0                       ; Debug 0 = off, 1 = on (adds lots of additional messages)
logFilePath = /var/log/Quantar_Bridge.log

; Configure the DMR Partner
; Audio format is AMBE 72 bit
[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

; Configure the D-Star Partner
; Audio format is AMBE 48 bit (DSAMBE)
[DSTAR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 32100                  ; Port to send AMBE TLV frames to (export)
RXPort = 32103                  ; Port to listen on (import)
FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
ExportTG = 9                    ; Which TG to export
Slot = 2                        ; Export slot

; Configure the NXDN Partner
; Audio format is AMBE 72 bit
[NXDN]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 33100                  ; Port to send AMBE TLV frames to (export)
RXPort = 33103                  ; Port to listen on (import)
FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
NXDNFallbackID  = 12345         ; Use this ID when the input DMR ID is not found in the database
Translate = 1234=4321           ; Translate NXDN TG < -- > DMR TG (bidirectional)
Slot = 2                        ; Export slot

; Configure the P25 Partner
; Audio format is IMBE 88 bit
[P25]
Address = 10.1.2.245             ; Address to send AMBE TLV frames to (export)
TXPort = 34100                  ; Port to send AMBE TLV frames to (export)
RXPort = 34103                  ; Port to listen on (import)
;Slot = 2                        ; Export slot

; Configure the Yaesu Fusion Partner
; Audio format is AMBE 72 bit
; Audio format is IMBE 88 bit
[YSF]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 35100                  ; Port to send AMBE TLV frames to (export)
RXPort = 35103                  ; Port to listen on (import)
FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
ExportTG = 1234                 ; Which TG to export
Slot = 2                        ; Export slot


and here is mmdvm_bridge.ini

[General]
Callsign=K0JSC
Id=310815
Timeout=180
Duplex=2
ModeHang=20
RFModeHang=20
NetModeHang=20
Display=None
Daemon=0

[Info]
RXFrequency=222340000
TXFrequency=224940000
Power=1
Latitude=41.7333
Longitude=-50.3999
Height=0
Location=Iceberg, North Atlantic
Description=MMDVM_Bridge

[Log]
# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
DisplayLevel=1
FileLevel=2
FilePath=/var/log/mmdvm
FileRoot=MMDVM_Bridge

[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat
Time=24

[NXDN Id Lookup]
File=/var/lib/mmdvm/NXDN.csv
Time=24

[Modem]
Port=/dev/null
RSSIMappingFile=RSSI.dat
Trace=0
Debug=0

[D-Star]
Enable=0
Module=C
SelfOnly=0
AckReply=1
AckTime=750
ErrorReply=1
RemoteGateway=0
ModeHang=0

[DMR]
Enable=0
Beacons=0
BeaconInterval=60
BeaconDuration=3
ColorCode=1
SelfOnly=0
EmbeddedLCOnly=1
DumpTAData=0
CallHang=0
TXHang=0
ModeHang=0

[System Fusion]
Enable=0
LowDeviation=0
SelfOnly=0
RemoteGateway=0
ModeHang=0

[P25]
Enable=1
NAC=293
SelfOnly=0
OverrideUIDCheck=0
RemoteGateway=1
ModeHang=20

[NXDN]
Enable=0
RAN=1
SelfOnly=0
RemoteGateway=0
ModeHang=0
Id=12345

[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
ModeHang=0
Debug=0

[DMR Network]
Enable=0
Address=127.0.0.1
Port=62031
Jitter=360
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
ModeHang=0
Debug=0

[System Fusion Network]
Enable=0
LocalAddress=0
LocalPort=3200
GatewayAddress=127.0.0.1
GatewayPort=42000
ModeHang=0
Debug=0

[P25 Network]
Enable=1
GatewayAddress=10.1.2.245
GatewayPort=42020
LocalPort=32010
ModeHang=0
Debug=0

[NXDN Network]
Enable=0
#LocalAddress=127.0.0.1
ModeHang=0
Debug=0
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020


On Wed, May 16, 2018 at 4:38 PM, Steve N4IRS <szingman@...> wrote:
DVSwitch.ini is the file that manages the ports and addresses used by MMDVM_Bridge to export and import data from a Partner. In this case Analog_Bridge.
It's hard to troubleshoot your error without seeing the relevent sections of DVSwitch.ini and Analog_Bridge.ini.

On 05/16/2018 05:44 PM, Jeff Carrier wrote:
I feel like I may be getting closer with AllStarLink <---> Analog_Bridge <---> MMDVM_Bridge <---> P25Gateway <--> P25Reflector  (i'm also trying to figure out where dvswitch.ini figures into this)

My problem is MMDVM_Bridge now reports this on analog traffic...

 
M: 2018-05-16 21:34:45.070 P25 packet received from an invalid source, 10.1.2.245 != 10.1.2.245 and/or 42020 != 55100
M: 2018-05-16 21:34:45.085 P25 packet received from an invalid source, 10.1.2.245 != 10.1.2.245 and/or 42020 != 55100
M: 2018-05-16 21:34:45.090 P25 packet received from an invalid source, 10.1.2.245 != 10.1.2.245 and/or 42020 != 55100
M: 2018-05-16 21:34:48.984 P25, received network transmission from K0JSC to TG 10209
M: 2018-05-16 21:34:50.968 P25, network end of transmission, 2.3 seconds, 0% packet loss

Do the ports in AMBE_AUDIO, 
 




Re: P25 Gateway <---> allstar

Jeff Carrier
 

Here is dvswitch.ini

; MMDVM_Bridge configuration file.
;   This file should be placed along side of MMDVM_Bridge or it can be
;   supplied as a path on the MMDVM_BRIDGE environment variable.

; Configure the Quantar Repeater Partner
; Note that the TX and RX ports are already reversed for MMDVM_Bridge <--> Quantar_Bridge
[QUANTAR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 34103                  ; Port to send AMBE TLV frames to (export)
RXPort = 34100                  ; Port to listen on (import)
quantarPort = 1994              ; HDLC frames To/From the Quantar repeater
logLevel = 2                    ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
debug = 0                       ; Debug 0 = off, 1 = on (adds lots of additional messages)
logFilePath = /var/log/Quantar_Bridge.log

; Configure the DMR Partner
; Audio format is AMBE 72 bit
[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

; Configure the D-Star Partner
; Audio format is AMBE 48 bit (DSAMBE)
[DSTAR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 32100                  ; Port to send AMBE TLV frames to (export)
RXPort = 32103                  ; Port to listen on (import)
FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
ExportTG = 9                    ; Which TG to export
Slot = 2                        ; Export slot

; Configure the NXDN Partner
; Audio format is AMBE 72 bit
[NXDN]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 33100                  ; Port to send AMBE TLV frames to (export)
RXPort = 33103                  ; Port to listen on (import)
FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
NXDNFallbackID  = 12345         ; Use this ID when the input DMR ID is not found in the database
Translate = 1234=4321           ; Translate NXDN TG < -- > DMR TG (bidirectional)
Slot = 2                        ; Export slot

; Configure the P25 Partner
; Audio format is IMBE 88 bit
[P25]
Address = 10.1.2.245             ; Address to send AMBE TLV frames to (export)
TXPort = 34100                  ; Port to send AMBE TLV frames to (export)
RXPort = 34103                  ; Port to listen on (import)
;Slot = 2                        ; Export slot

; Configure the Yaesu Fusion Partner
; Audio format is AMBE 72 bit
; Audio format is IMBE 88 bit
[YSF]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 35100                  ; Port to send AMBE TLV frames to (export)
RXPort = 35103                  ; Port to listen on (import)
FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
ExportTG = 1234                 ; Which TG to export
Slot = 2                        ; Export slot


and here is mmdvm_bridge.ini

[General]
Callsign=K0JSC
Id=310815
Timeout=180
Duplex=2
ModeHang=20
RFModeHang=20
NetModeHang=20
Display=None
Daemon=0

[Info]
RXFrequency=222340000
TXFrequency=224940000
Power=1
Latitude=41.7333
Longitude=-50.3999
Height=0
Location=Iceberg, North Atlantic
Description=MMDVM_Bridge

[Log]
# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
DisplayLevel=1
FileLevel=2
FilePath=/var/log/mmdvm
FileRoot=MMDVM_Bridge

[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat
Time=24

[NXDN Id Lookup]
File=/var/lib/mmdvm/NXDN.csv
Time=24

[Modem]
Port=/dev/null
RSSIMappingFile=RSSI.dat
Trace=0
Debug=0

[D-Star]
Enable=0
Module=C
SelfOnly=0
AckReply=1
AckTime=750
ErrorReply=1
RemoteGateway=0
ModeHang=0

[DMR]
Enable=0
Beacons=0
BeaconInterval=60
BeaconDuration=3
ColorCode=1
SelfOnly=0
EmbeddedLCOnly=1
DumpTAData=0
CallHang=0
TXHang=0
ModeHang=0

[System Fusion]
Enable=0
LowDeviation=0
SelfOnly=0
RemoteGateway=0
ModeHang=0

[P25]
Enable=1
NAC=293
SelfOnly=0
OverrideUIDCheck=0
RemoteGateway=1
ModeHang=20

[NXDN]
Enable=0
RAN=1
SelfOnly=0
RemoteGateway=0
ModeHang=0
Id=12345

[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
ModeHang=0
Debug=0

[DMR Network]
Enable=0
Address=127.0.0.1
Port=62031
Jitter=360
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
ModeHang=0
Debug=0

[System Fusion Network]
Enable=0
LocalAddress=0
LocalPort=3200
GatewayAddress=127.0.0.1
GatewayPort=42000
ModeHang=0
Debug=0

[P25 Network]
Enable=1
GatewayAddress=10.1.2.245
GatewayPort=42020
LocalPort=32010
ModeHang=0
Debug=0

[NXDN Network]
Enable=0
#LocalAddress=127.0.0.1
ModeHang=0
Debug=0
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020


On Wed, May 16, 2018 at 4:38 PM, Steve N4IRS <szingman@...> wrote:
DVSwitch.ini is the file that manages the ports and addresses used by MMDVM_Bridge to export and import data from a Partner. In this case Analog_Bridge.
It's hard to troubleshoot your error without seeing the relevent sections of DVSwitch.ini and Analog_Bridge.ini.

On 05/16/2018 05:44 PM, Jeff Carrier wrote:
I feel like I may be getting closer with AllStarLink <---> Analog_Bridge <---> MMDVM_Bridge <---> P25Gateway <--> P25Reflector  (i'm also trying to figure out where dvswitch.ini figures into this)

My problem is MMDVM_Bridge now reports this on analog traffic...

 
M: 2018-05-16 21:34:45.070 P25 packet received from an invalid source, 10.1.2.245 != 10.1.2.245 and/or 42020 != 55100
M: 2018-05-16 21:34:45.085 P25 packet received from an invalid source, 10.1.2.245 != 10.1.2.245 and/or 42020 != 55100
M: 2018-05-16 21:34:45.090 P25 packet received from an invalid source, 10.1.2.245 != 10.1.2.245 and/or 42020 != 55100
M: 2018-05-16 21:34:48.984 P25, received network transmission from K0JSC to TG 10209
M: 2018-05-16 21:34:50.968 P25, network end of transmission, 2.3 seconds, 0% packet loss

Do the ports in AMBE_AUDIO, 
 



Re: P25 Gateway <---> allstar

Steve N4IRS
 

DVSwitch.ini is the file that manages the ports and addresses used by MMDVM_Bridge to export and import data from a Partner. In this case Analog_Bridge.
It's hard to troubleshoot your error without seeing the relevent sections of DVSwitch.ini and Analog_Bridge.ini.

On 05/16/2018 05:44 PM, Jeff Carrier wrote:
I feel like I may be getting closer with AllStarLink <---> Analog_Bridge <---> MMDVM_Bridge <---> P25Gateway <--> P25Reflector  (i'm also trying to figure out where dvswitch.ini figures into this)

My problem is MMDVM_Bridge now reports this on analog traffic...

 
M: 2018-05-16 21:34:45.070 P25 packet received from an invalid source, 10.1.2.245 != 10.1.2.245 and/or 42020 != 55100
M: 2018-05-16 21:34:45.085 P25 packet received from an invalid source, 10.1.2.245 != 10.1.2.245 and/or 42020 != 55100
M: 2018-05-16 21:34:45.090 P25 packet received from an invalid source, 10.1.2.245 != 10.1.2.245 and/or 42020 != 55100
M: 2018-05-16 21:34:48.984 P25, received network transmission from K0JSC to TG 10209
M: 2018-05-16 21:34:50.968 P25, network end of transmission, 2.3 seconds, 0% packet loss

Do the ports in AMBE_AUDIO, 
 


P25 Gateway <---> allstar

Jeff Carrier
 

I feel like I may be getting closer with AllStarLink <---> Analog_Bridge <---> MMDVM_Bridge <---> P25Gateway <--> P25Reflector  (i'm also trying to figure out where dvswitch.ini figures into this)

My problem is MMDVM_Bridge now reports this on analog traffic...

 
M: 2018-05-16 21:34:45.070 P25 packet received from an invalid source, 10.1.2.245 != 10.1.2.245 and/or 42020 != 55100
M: 2018-05-16 21:34:45.085 P25 packet received from an invalid source, 10.1.2.245 != 10.1.2.245 and/or 42020 != 55100
M: 2018-05-16 21:34:45.090 P25 packet received from an invalid source, 10.1.2.245 != 10.1.2.245 and/or 42020 != 55100
M: 2018-05-16 21:34:48.984 P25, received network transmission from K0JSC to TG 10209
M: 2018-05-16 21:34:50.968 P25, network end of transmission, 2.3 seconds, 0% packet loss

Do the ports in AMBE_AUDIO, 
 


Re: DMR to AllStar Bridge

Steve N4IRS
 

All the DVSwitch programs are installed in /opt
/opt/Analog_Bridge
/opt MMDVM_Bridge
/opt/...

On 5/16/2018 12:16 PM, Russell Thomas, KV4S wrote:
Ok, I started over from scratch with AWS. I think i was loading the wrong images previously I loaded the Ubuntu 16.04 and that was the key.

I installed the ASL and the DVSwitch. 

All appears to have installed correctly this time.

What are my next steps. I tried some searches but I can't find where the .ini files are located.

On Tue, May 15, 2018 at 8:06 PM Alec J Wasserman <alec.wasserman@...> wrote:
i followed the instructions on here   https://wiki.allstarlink.org/wiki/ASL_FAQ  and I made Allstar work on Google Cloud last night  Wasnt too hard.


Re: DMR to AllStar Bridge

 

Ok, I started over from scratch with AWS. I think i was loading the wrong images previously I loaded the Ubuntu 16.04 and that was the key.

I installed the ASL and the DVSwitch. 

All appears to have installed correctly this time.

What are my next steps. I tried some searches but I can't find where the .ini files are located.

On Tue, May 15, 2018 at 8:06 PM Alec J Wasserman <alec.wasserman@...> wrote:
i followed the instructions on here   https://wiki.allstarlink.org/wiki/ASL_FAQ  and I made Allstar work on Google Cloud last night  Wasnt too hard.


Re: DMR to AllStar Bridge

Alec-N1AJW
 

i followed the instructions on here   https://wiki.allstarlink.org/wiki/ASL_FAQ  and I made Allstar work on Google Cloud last night  Wasnt too hard.


Re: DMR to AllStar Bridge

Steve N4IRS
 

The install script is Debian based. HAMVOIP is ARCH. I doubt it works.

On 05/15/2018 03:12 PM, Russell Thomas wrote:
Ok after some more digging I'm pretty sure I can use the ras pi that my current node is running on which is a HAMVOIP image.

i'm running the instructions I got from this page:

It appears to have downloaded the files 


[root@mynode-xxxx tmp]# wget http://dvswitch.org/install-dvswitch-repo
Resolving dvswitch.org (dvswitch.org)... 44.103.32.18
Connecting to dvswitch.org (dvswitch.org)|44.103.32.18|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 610
Saving to: 'install-dvswitch-repo'

install-dvswitch-re 100%[===================>]     610  --.-KB/s    in 0s

2018-05-15 13:52:34 (18.6 MB/s) - 'install-dvswitch-repo' saved [610/610]

[root@mynode-xxxx tmp]# chmod +x install-dvswitch-repo
[root@mynode-xxxx tmp]# ./install-dvswitch-repo
./install-dvswitch-repo: line 12: cd: /etc/apt/sources.list.d: No such file or directory

checking it again:

[root@mynode-xxxx tmp]# dir
install-dvswitch-repo
iplog.txt
randommsg.gsm
rpt_extnodes
sess_0hr3a226i8nv8tamjanrjjjkl1
sess_o9bvk7fad53j4e3llfnjoitck0
sess_r8uka1a6jhd38tk3pu0m8f2gd1
systemd-private-2687e0800c094fa099d28f32cef3222a-systemd-timesyncd.service-YODPcR
[root@mynode-xxxx tmp]# chmod +x install-dvswitch-repo
[root@mynode-xxxx tmp]# ./install-dvswitch-repo
./install-dvswitch-repo: line 12: cd: /etc/apt/sources.list.d: No such file or directory

On Mon, May 14, 2018 at 9:23 AM Steve N4IRS <szingman@...> wrote:
Russell,
Your first step will be to get the AllStarLink (ASL) node running. I believe it's possible on AWS. The biggest challenge is DAHDI Which requires the kernel headers.
I suggest you get the kernel headers installed and theninstall ASL from <https://wiki.allstarlink.org/wiki/ASL_FAQ>

73, Steve N4IRS 

On 05/14/2018 10:14 AM, Russell Thomas wrote:
Steve,

Thanks for the response!
I'm starting to investigate a cloud host is there anything your recommend as far as linux goes.

this is where i'm starting:

If this looks good what are the install steps?

73,
Russell Thomas, KV4S

Cell: 205.202.1701
DMR: 3101393
D-Star: KV4S
AllStar: 47923
EchoLink: KV4S-L
HamShackHotline: 4225
Web: http://KV4S.com

On Mon, May 14, 2018 at 6:05 AM Steve N4IRS <szingman@...> wrote:
Russell,
AllStarLink can be bridged to a DMR TG. I can't say if the HAMVOIP version supports what is needed since it is closed source.
In general this is how it will look I am going to assume you want to connect to BrandMeister. This is a simple bridge, the components will change is you need more features.

BM <-> MMDVM_Bridge <-> Analog_Bridge <-> AllStarLink.

This can run on the same host as the AllStarLink node or on a separate host if the HAMVOIP node can not handle it.

73, Steve N4IRS
 

On 05/13/2018 02:03 PM, Russell Thomas wrote:
Hello, I'm new to the DVSwitch group.

I was told there was a software only option do do what i'm trying to
do and link and existing DMR talk group to an existing AllStar node.

Can anyone provide details on how to accomplish this?

I'm running VOIP on my AllStar node am I able to use this RasPi or do
I need to get another one dedicated to the linking?

I'm pretty much lost on the rest.

Thanks for any help and assitance. Enjoy seeing so much interest in
the cutting edge :)

73,
Russell Thomas, KV4S

Cell: 205.202.1701
DMR: 3101393
D-Star: KV4S
AllStar: 47923
EchoLink: KV4S-L
HamShackHotline: 4225
Web: http://KV4S.com




Re: DMR to AllStar Bridge

 

Ok after some more digging I'm pretty sure I can use the ras pi that my current node is running on which is a HAMVOIP image.

i'm running the instructions I got from this page:

It appears to have downloaded the files 


[root@mynode-xxxx tmp]# wget http://dvswitch.org/install-dvswitch-repo
Resolving dvswitch.org (dvswitch.org)... 44.103.32.18
Connecting to dvswitch.org (dvswitch.org)|44.103.32.18|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 610
Saving to: 'install-dvswitch-repo'

install-dvswitch-re 100%[===================>]     610  --.-KB/s    in 0s

2018-05-15 13:52:34 (18.6 MB/s) - 'install-dvswitch-repo' saved [610/610]

[root@mynode-xxxx tmp]# chmod +x install-dvswitch-repo
[root@mynode-xxxx tmp]# ./install-dvswitch-repo
./install-dvswitch-repo: line 12: cd: /etc/apt/sources.list.d: No such file or directory

checking it again:

[root@mynode-xxxx tmp]# dir
install-dvswitch-repo
iplog.txt
randommsg.gsm
rpt_extnodes
sess_0hr3a226i8nv8tamjanrjjjkl1
sess_o9bvk7fad53j4e3llfnjoitck0
sess_r8uka1a6jhd38tk3pu0m8f2gd1
systemd-private-2687e0800c094fa099d28f32cef3222a-systemd-timesyncd.service-YODPcR
[root@mynode-xxxx tmp]# chmod +x install-dvswitch-repo
[root@mynode-xxxx tmp]# ./install-dvswitch-repo
./install-dvswitch-repo: line 12: cd: /etc/apt/sources.list.d: No such file or directory


On Mon, May 14, 2018 at 9:23 AM Steve N4IRS <szingman@...> wrote:
Russell,
Your first step will be to get the AllStarLink (ASL) node running. I believe it's possible on AWS. The biggest challenge is DAHDI Which requires the kernel headers.
I suggest you get the kernel headers installed and theninstall ASL from <https://wiki.allstarlink.org/wiki/ASL_FAQ>

73, Steve N4IRS 

On 05/14/2018 10:14 AM, Russell Thomas wrote:
Steve,

Thanks for the response!
I'm starting to investigate a cloud host is there anything your recommend as far as linux goes.

this is where i'm starting:

If this looks good what are the install steps?

73,
Russell Thomas, KV4S

Cell: 205.202.1701
DMR: 3101393
D-Star: KV4S
AllStar: 47923
EchoLink: KV4S-L
HamShackHotline: 4225
Web: http://KV4S.com

On Mon, May 14, 2018 at 6:05 AM Steve N4IRS <szingman@...> wrote:
Russell,
AllStarLink can be bridged to a DMR TG. I can't say if the HAMVOIP version supports what is needed since it is closed source.
In general this is how it will look I am going to assume you want to connect to BrandMeister. This is a simple bridge, the components will change is you need more features.

BM <-> MMDVM_Bridge <-> Analog_Bridge <-> AllStarLink.

This can run on the same host as the AllStarLink node or on a separate host if the HAMVOIP node can not handle it.

73, Steve N4IRS
 

On 05/13/2018 02:03 PM, Russell Thomas wrote:
Hello, I'm new to the DVSwitch group.

I was told there was a software only option do do what i'm trying to
do and link and existing DMR talk group to an existing AllStar node.

Can anyone provide details on how to accomplish this?

I'm running VOIP on my AllStar node am I able to use this RasPi or do
I need to get another one dedicated to the linking?

I'm pretty much lost on the rest.

Thanks for any help and assitance. Enjoy seeing so much interest in
the cutting edge :)

73,
Russell Thomas, KV4S

Cell: 205.202.1701
DMR: 3101393
D-Star: KV4S
AllStar: 47923
EchoLink: KV4S-L
HamShackHotline: 4225
Web: http://KV4S.com



Re: A brief how to, please

TG9AOR
 

Thank you, Steve, for your reply. I am interested in bridging  my Echolink node and BM DMRTG704. I would like to know if I would be able to link the conference created by your software to another node apart from mine (ie Node 654905). This would bridge the analog and digital system currently in place in Guatemala together.

Once I am able to get that going I would then be interested in looking at the NXDN reflector, but that is for later.

You guys have inspired me to learn Python, as G4KLX inspired me to learn Linux. All good examples, I thank you for that, as many others have stated in their posts.


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


Re: A brief how to, please

Michael Rickey (AF6FB)
 

That explains it. I was looking there, but I guess the install script doesn't put anything there. I'll give it another try after I get home.



Michael Rickey - AF6FB
949-298-0529 (voice, sms, allo, duo)




Re: A brief how to, please

Steve N4IRS
 

your problem is fixed.
apt-get update
apt-get install analog-bridge

All applications and config files are installed in /opt as in /opt/Analog_Bridge

On 05/14/2018 07:19 PM, Michael Rickey (AF6FB) wrote:
I'm having problems with this as well.

The only place I've found that talks about installing anything is the post you mentioned. I'm able to get through the first part, when I run "apt-get install analog_bridge" I get the error "analog_bridge: Depends: libsoundio-dev but it is not installable".

Also, what folder are the config files in?

I'm running on Raspian Stretch

Thanks in advance,
Michael AF6FB


Re: A brief how to, please

Michael Rickey (AF6FB)
 

I'm having problems with this as well.

The only place I've found that talks about installing anything is the post you mentioned. I'm able to get through the first part, when I run "apt-get install analog_bridge" I get the error "analog_bridge: Depends: libsoundio-dev but it is not installable".

Also, what folder are the config files in?

I'm running on Raspian Stretch

Thanks in advance,
Michael AF6FB


Re: A brief how to, please

Steve N4IRS
 

José,
Yes, to say the least the documentation has not kept up with the programs. My repository for Analog_Bridge was also behind. I have updated that. The install is using Debian apt and the instructions are here:
<https://dvswitch.groups.io/g/main/topic/updated_dvswitch_repository/18971786?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,18971786>

Can you give us a better idea of what you are trying to do and we can help you get the right software.

73, Steve N4IRS

On 05/14/2018 04:30 PM, TG9AOR wrote:
I am almost done reading all 240+ messages in this forum, while doing that I noticed a rough draft in the files section on how to set up Analog Bridge (wiki is empty) After setting up Analog Bridge.ARM and dmrlink as per the document, it then pointed me to the files that now live under the "Retired" folder /dmrlink/Retired(if I recall) but I was not able to conduct any more testing, but noticing these files were no longer in use left me practically at the starting point again.


If I want to make my own network, and  link my DVMega MMDVM and be able to listen to BrandMeister and Echolink and Allstar, what repos do I need to clone?

I have noticed some commands from N4IRS regarding git and the branches but since they were in response to other threads I just want to be sure what to download. I would then proceed to look over at the config files to fill in the blanks, and then post a question if I get stuck.

I have an Rpi3 with a DV3000u for this project.

Thanks for taking the time to read my post.

José Roberto Ruíz García Salas TG9AOR


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


A brief how to, please

TG9AOR
 

I am almost done reading all 240+ messages in this forum, while doing that I noticed a rough draft in the files section on how to set up Analog Bridge (wiki is empty) After setting up Analog Bridge.ARM and dmrlink as per the document, it then pointed me to the files that now live under the "Retired" folder /dmrlink/Retired(if I recall) but I was not able to conduct any more testing, but noticing these files were no longer in use left me practically at the starting point again.


If I want to make my own network, and  link my DVMega MMDVM and be able to listen to BrandMeister and Echolink and Allstar, what repos do I need to clone?

I have noticed some commands from N4IRS regarding git and the branches but since they were in response to other threads I just want to be sure what to download. I would then proceed to look over at the config files to fill in the blanks, and then post a question if I get stuck.

I have an Rpi3 with a DV3000u for this project.

Thanks for taking the time to read my post.

José Roberto Ruíz García Salas TG9AOR


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


Re: DMR to AllStar Bridge

Steve N4IRS
 

Russell,
Your first step will be to get the AllStarLink (ASL) node running. I believe it's possible on AWS. The biggest challenge is DAHDI Which requires the kernel headers.
I suggest you get the kernel headers installed and theninstall ASL from <https://wiki.allstarlink.org/wiki/ASL_FAQ>

73, Steve N4IRS 

On 05/14/2018 10:14 AM, Russell Thomas wrote:
Steve,

Thanks for the response!
I'm starting to investigate a cloud host is there anything your recommend as far as linux goes.

this is where i'm starting:

If this looks good what are the install steps?

73,
Russell Thomas, KV4S

Cell: 205.202.1701
DMR: 3101393
D-Star: KV4S
AllStar: 47923
EchoLink: KV4S-L
HamShackHotline: 4225
Web: http://KV4S.com

On Mon, May 14, 2018 at 6:05 AM Steve N4IRS <szingman@...> wrote:
Russell,
AllStarLink can be bridged to a DMR TG. I can't say if the HAMVOIP version supports what is needed since it is closed source.
In general this is how it will look I am going to assume you want to connect to BrandMeister. This is a simple bridge, the components will change is you need more features.

BM <-> MMDVM_Bridge <-> Analog_Bridge <-> AllStarLink.

This can run on the same host as the AllStarLink node or on a separate host if the HAMVOIP node can not handle it.

73, Steve N4IRS
 

On 05/13/2018 02:03 PM, Russell Thomas wrote:
Hello, I'm new to the DVSwitch group.

I was told there was a software only option do do what i'm trying to
do and link and existing DMR talk group to an existing AllStar node.

Can anyone provide details on how to accomplish this?

I'm running VOIP on my AllStar node am I able to use this RasPi or do
I need to get another one dedicated to the linking?

I'm pretty much lost on the rest.

Thanks for any help and assitance. Enjoy seeing so much interest in
the cutting edge :)

73,
Russell Thomas, KV4S

Cell: 205.202.1701
DMR: 3101393
D-Star: KV4S
AllStar: 47923
EchoLink: KV4S-L
HamShackHotline: 4225
Web: http://KV4S.com



Re: DMR to AllStar Bridge

 

Steve,

Thanks for the response!
I'm starting to investigate a cloud host is there anything your recommend as far as linux goes.

this is where i'm starting:

If this looks good what are the install steps?

73,
Russell Thomas, KV4S

Cell: 205.202.1701
DMR: 3101393
D-Star: KV4S
AllStar: 47923
EchoLink: KV4S-L
HamShackHotline: 4225
Web: http://KV4S.com


On Mon, May 14, 2018 at 6:05 AM Steve N4IRS <szingman@...> wrote:
Russell,
AllStarLink can be bridged to a DMR TG. I can't say if the HAMVOIP version supports what is needed since it is closed source.
In general this is how it will look I am going to assume you want to connect to BrandMeister. This is a simple bridge, the components will change is you need more features.

BM <-> MMDVM_Bridge <-> Analog_Bridge <-> AllStarLink.

This can run on the same host as the AllStarLink node or on a separate host if the HAMVOIP node can not handle it.

73, Steve N4IRS
 

On 05/13/2018 02:03 PM, Russell Thomas wrote:
Hello, I'm new to the DVSwitch group.

I was told there was a software only option do do what i'm trying to
do and link and existing DMR talk group to an existing AllStar node.

Can anyone provide details on how to accomplish this?

I'm running VOIP on my AllStar node am I able to use this RasPi or do
I need to get another one dedicated to the linking?

I'm pretty much lost on the rest.

Thanks for any help and assitance. Enjoy seeing so much interest in
the cutting edge :)

73,
Russell Thomas, KV4S

Cell: 205.202.1701
DMR: 3101393
D-Star: KV4S
AllStar: 47923
EchoLink: KV4S-L
HamShackHotline: 4225
Web: http://KV4S.com


Re: DMR to AllStar Bridge

Steve N4IRS
 

Russell,
AllStarLink can be bridged to a DMR TG. I can't say if the HAMVOIP version supports what is needed since it is closed source.
In general this is how it will look I am going to assume you want to connect to BrandMeister. This is a simple bridge, the components will change is you need more features.

BM <-> MMDVM_Bridge <-> Analog_Bridge <-> AllStarLink.

This can run on the same host as the AllStarLink node or on a separate host if the HAMVOIP node can not handle it.

73, Steve N4IRS
 

On 05/13/2018 02:03 PM, Russell Thomas wrote:
Hello, I'm new to the DVSwitch group.

I was told there was a software only option do do what i'm trying to
do and link and existing DMR talk group to an existing AllStar node.

Can anyone provide details on how to accomplish this?

I'm running VOIP on my AllStar node am I able to use this RasPi or do
I need to get another one dedicated to the linking?

I'm pretty much lost on the rest.

Thanks for any help and assitance. Enjoy seeing so much interest in
the cutting edge :)

73,
Russell Thomas, KV4S

Cell: 205.202.1701
DMR: 3101393
D-Star: KV4S
AllStar: 47923
EchoLink: KV4S-L
HamShackHotline: 4225
Web: http://KV4S.com


DMR to AllStar Bridge

 

Hello, I'm new to the DVSwitch group.

I was told there was a software only option do do what i'm trying to
do and link and existing DMR talk group to an existing AllStar node.

Can anyone provide details on how to accomplish this?

I'm running VOIP on my AllStar node am I able to use this RasPi or do
I need to get another one dedicated to the linking?

I'm pretty much lost on the rest.

Thanks for any help and assitance. Enjoy seeing so much interest in
the cutting edge :)

73,
Russell Thomas, KV4S

Cell: 205.202.1701
DMR: 3101393
D-Star: KV4S
AllStar: 47923
EchoLink: KV4S-L
HamShackHotline: 4225
Web: http://KV4S.com


Re: I found a NWDR AMBE board in my pile of Pi stuff

Steve N4IRS
 

You could use it if you wanted to bridge AllStarLink to your P25Reflector Or to bridge a Quantar in P25 mode to AllStarlink.

On 05/13/2018 12:29 PM, Mike AE4ML wrote:
This board has been sitting for a while in the box just gathering dust. I pulled it out and found some docs on a AMBE server with Pi 3.
Thats up and running. what can I do with this now ?
I have multiple Quantar repeaters running P25. I'm just trying to see where this board ( i.e. server ) would come into play.


Mike AE4ML

7861 - 7880 of 9083