Date   

Re: M17 to ASL

SP2ONG Waldek
 

Perhaps this would require adding Codec2 support and an M17 mode to Analog_Bridge similar to use md380-emu.
The Codec2 server version is available

https://github.com/ea3ihi/codec2

and it can be used in a similar way as md380-emu via UDP port


Re: Error when using AMBEserver

 

I think you have the same usb stick that I have. Played for hours had no joy . Will only work with ambeserver. When running its got a green Led.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Tony Langdon <vk3jed@...>
Sent: Friday, March 12, 2021 6:28:35 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Error when using AMBEserver
 
I'm now xperimnting with AB talking to the AMBE dongle over USB, but still no joy, even when using the actual /dev/ttyUSBn device name.

On 12/3/21 5:22 pm, Ernie Gm7kbk wrote:
I get the same problem. If I restart the ambeserver with AB running all will work fine for days.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Tony Langdon <vk3jed@...>
Sent: Friday, March 12, 2021 6:04:30 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: [DVSwitch] Error when using AMBEserver
 
While I had a bit of spare time this morning, I decided to do a bit of
troubleshooting to find out why AB was apparently not using my ThumbDV
dongle for D-STAR (distorted audio being an obvious symptom!).

In test mode, I am using AMBEserver on localhost.  Eventually, I plan to
dedicate the AMBEserver to a remote instance of AB running on a VM, so
switching to local USB connection isn't an option.  Also, the AMBEserver
has previously been successfully used with BlueDV running in a local
Windows host.

I restarted AMBEserver, then restarted AB, and when AB attemoted to
connect, I got the following error repeated dozens of times by AMBEserver:

AMBEserver: invalid start byte when reading from the socket, 0x00

The system appears to recognise the AMBE dongle, and I am using a static
symlink (managed by udev rules), because there are multiple USB serial
devices, and using the ttyUSB device name would mean frequent manual
intervention.

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







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


Re: Error when using AMBEserver

 

I'm now xperimnting with AB talking to the AMBE dongle over USB, but still no joy, even when using the actual /dev/ttyUSBn device name.

On 12/3/21 5:22 pm, Ernie Gm7kbk wrote:
I get the same problem. If I restart the ambeserver with AB running all will work fine for days.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Tony Langdon <vk3jed@...>
Sent: Friday, March 12, 2021 6:04:30 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: [DVSwitch] Error when using AMBEserver
 
While I had a bit of spare time this morning, I decided to do a bit of
troubleshooting to find out why AB was apparently not using my ThumbDV
dongle for D-STAR (distorted audio being an obvious symptom!).

In test mode, I am using AMBEserver on localhost.  Eventually, I plan to
dedicate the AMBEserver to a remote instance of AB running on a VM, so
switching to local USB connection isn't an option.  Also, the AMBEserver
has previously been successfully used with BlueDV running in a local
Windows host.

I restarted AMBEserver, then restarted AB, and when AB attemoted to
connect, I got the following error repeated dozens of times by AMBEserver:

AMBEserver: invalid start byte when reading from the socket, 0x00

The system appears to recognise the AMBE dongle, and I am using a static
symlink (managed by udev rules), because there are multiple USB serial
devices, and using the ttyUSB device name would mean frequent manual
intervention.

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







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


Re: Error when using AMBEserver

 

I get the same problem. If I restart the ambeserver with AB running all will work fine for days.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Tony Langdon <vk3jed@...>
Sent: Friday, March 12, 2021 6:04:30 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: [DVSwitch] Error when using AMBEserver
 
While I had a bit of spare time this morning, I decided to do a bit of
troubleshooting to find out why AB was apparently not using my ThumbDV
dongle for D-STAR (distorted audio being an obvious symptom!).

In test mode, I am using AMBEserver on localhost.  Eventually, I plan to
dedicate the AMBEserver to a remote instance of AB running on a VM, so
switching to local USB connection isn't an option.  Also, the AMBEserver
has previously been successfully used with BlueDV running in a local
Windows host.

I restarted AMBEserver, then restarted AB, and when AB attemoted to
connect, I got the following error repeated dozens of times by AMBEserver:

AMBEserver: invalid start byte when reading from the socket, 0x00

The system appears to recognise the AMBE dongle, and I am using a static
symlink (managed by udev rules), because there are multiple USB serial
devices, and using the ttyUSB device name would mean frequent manual
intervention.

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







Error when using AMBEserver

 

While I had a bit of spare time this morning, I decided to do a bit of
troubleshooting to find out why AB was apparently not using my ThumbDV
dongle for D-STAR (distorted audio being an obvious symptom!).

In test mode, I am using AMBEserver on localhost.  Eventually, I plan to
dedicate the AMBEserver to a remote instance of AB running on a VM, so
switching to local USB connection isn't an option.  Also, the AMBEserver
has previously been successfully used with BlueDV running in a local
Windows host.

I restarted AMBEserver, then restarted AB, and when AB attemoted to
connect, I got the following error repeated dozens of times by AMBEserver:

AMBEserver: invalid start byte when reading from the socket, 0x00

The system appears to recognise the AMBE dongle, and I am using a static
symlink (managed by udev rules), because there are multiple USB serial
devices, and using the ttyUSB device name would mean frequent manual
intervention.

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


Re: M17 to ASL

 

Hmm, I'd have thought it better to have Analog_Bridge or an equivalent program to transcode between M17 (Codec2) and PCM.  Doing it via DMR means there's an unnecessary transcoding step, when going from M17 to ASL (i.e. going via AMBE+2), degrading audio quality unnecessarily.  I've built my multimode gateway on the principle of transcoding as few times as possible.  From any digital mode to PCM is only one transcoding operation, between any 2 modes, there is never more than 2 transcoding operations (one source to PCM, then one from PCM to the target codec).  And the release of Analog_Reflector has allowed me to (mostly) preserve metadata across modes.
`

On 12/3/21 8:46 am, Steve KC1AWV wrote:
As of now, there is only one known path to get M17 to ASL, and that is to use M172DMR.

nostar MMDVM_CM fork: https://github.com/nostar/MMDVM_CM

Using M172DMR, you can cross-mode M17 to a DMR talkgroup. Then it's a simple matter of getting that DMR TG to ASL.

If anyone's interested in creating an ASL to M17 bridge, feel free to reach out to me.

Steve KC1AWV


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


Re: M17 to ASL

Steve KC1AWV
 

As of now, there is only one known path to get M17 to ASL, and that is to use M172DMR.

nostar MMDVM_CM fork: https://github.com/nostar/MMDVM_CM

Using M172DMR, you can cross-mode M17 to a DMR talkgroup. Then it's a simple matter of getting that DMR TG to ASL.

If anyone's interested in creating an ASL to M17 bridge, feel free to reach out to me.

Steve KC1AWV


Re: Emulator timed out on encode!

Steve N4IRS
 

Can you receive DMR?
Is the emulator running?
Please show your AB.ini



On 3/11/21 1:56 PM, G4WXN@... wrote:
DVSwitch server connected to BM.

MMDVM_bridge log says that it's logging in correctly.

I have a selfcare account with BM and password set.

When I try to transmit from the client I get this error in the analogue bridge log.

"Emulator timed out on encode!"

After that happens the whole system appears to lock up.

appreciate any help.



--
Derek

G4WXN


Emulator timed out on encode!

G4WXN@...
 
Edited

DVSwitch server connected to BM.

MMDVM_bridge log says that it's logging in correctly.

I have a selfcare account with BM and password set.

When I try to transmit from the client I get this error in the analogue bridge log.

"Emulator timed out on encode!"

After that happens the whole system appears to lock up.

This also happens on DMR plus.

appreciate any help.



--
Derek

G4WXN


Re: MMDVM bridge to YSF portion of XLX server with Allstar

Eric-K6KWB
 

Hi Jeff,
This is the comments I have I hope it helps. Good Luck!
73,
Eric

[YSF]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31100                  ; Port to send AMBE TLV frames to (export) >>>>>> 35100  should match your AB.ini
RXPort = 31103                  ; Port to listen on (import) >>>>> 35103
FallbackID = 3140122            ; In case we can not find a valid DMR id in the database, 
export this one
ExportTG = 31403                 ; Which TG to export
Slot = 1                        ; Export slot

; General vocoder setup information
decoderFallBack = true                 ; Allow software AMBE decoding if a hardware decode
r is not found
useEmulator = false                     ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN  >>>>>>true
/NXDN)
emulatorAddress = 127.0.0.1:2470        ; IP address and port of the md380 server

[AMBE_AUDIO]
address = 3.208.70.29                     ; IP address of xx_Bridge   >>>>>>>>>>> this should match your dvswitch.ini 127.0.0.1
txPort = 35103                          ; Transmit TLV frames to partner on this port   
rxPort = 35100                          ; Listen for TLV frames from partner on this port
ambeMode = YSFN                         ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (enc
ode PCM to this format)
minTxTimeMS = 2000                      ; Minimum time in MS for hang delay (0-10000)

[USRP]
address = rcwacomputer.ddns.net                     ; IP address of USRP partner (Allstar/
Asterisk or another Analog_Bridge)
txPort = 33001                          ; Transmit USRP frames on this port         >>>>>>double check your port from Allstar
rxPort = 35001                          ; Listen for USRP frames on this port       
aslAudio = AUDIO_UNITY               ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE
_GAIN)
agcGain = -20                             ; Gain 1 = Unity Gain 2 = two time the level of 
unity
dmrAudio = AUDIO_USE_GAIN               ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUD
IO_BPF)
dmrGain = 0.15                          ; Gain 1 = Unity Gain .50 = half the level of unit
y


Re: Our ability to support connectivity to TGIF.network

@AndrewVK2HAC
 

What functionality does have "TGIF Prime set up on three different DVSwitch instances" give you???

How do I set it up on my DVSwitch instance? 
I have a Prime TGIF ID & PW.


MMDVM bridge to YSF portion of XLX server with Allstar

Jeff Scoville
 

I have created a new MMDVM_Bridge from an Allstar node USRP to the YSF portion of an XLX reflector.  Audio travels well from YSF side to the Allstar side and even from the Dstar side of the XLX reflector to the Allstar side (because I have transcoding enabled on the XLX server).

However, I cannot get any audio to go from Allstar side to YSF side of XLX reflector, even though it appears that MMDVM_Bridge is handling that stream.  Debug info shown below.

I have ANOTHER YSF Reflector on the same box that is running the MMDVM_Bridge.  All I did was change the destination IP address to it and I can get both YSF to Allstar and Allstar to YSF audio.  So it appears that the only difference is now going to an XLX server (which is not on the same box).  Appreciate any assistance on what I may have configured incorrectly.

By the way, the YSF Reflector on the same box is on port 42000, the XLX reflector YSF is 42001.

Configuration files and debug info:

MMDVM_Bridge_Allstar.ini

[General]
Callsign=AE5ME
Id=3140122
Timeout=180
Duplex=0
 
[Info]
RXFrequency=445000000
TXFrequency=445000000
Power=1
Latitude=41.7333
Longitude=-50.3999
Height=0
Location=Iceberg, North Atlantic
Description=MMDVM_Bridge
URL=https://groups.io/g/DVSwitch
 
[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=/usr/local/bin/DMRIds.dat
Time=24
 
[NXDN Id Lookup]
File=/var/lib/mmdvm/NXDN.csv
Time=24
 
[Modem]
Port=/dev/null
RSSIMappingFile=RSSI.dat
Trace=0

[D-Star]
Enable=0
Module=A
 
[DMR]
Enable=0
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0
 
[System Fusion]
Enable=1
 
[P25]
Enable=0
NAC=293
 
[NXDN]
Enable=0
RAN=1
Id=12345
 
[D-Star Network]
Enable=0
GatewayAddress=54.158.171.153
GatewayPort=20010
LocalPort=20011
Debug=0

[DMR Network]
Enable=0
Address=54.158.171.153
Port=62030
Jitter=360
Local=62032
Password=passw0rd
Slot1=0
Slot2=1
Debug=0
 
[System Fusion Network]
Enable=1
LocalAddress=0
LocalPort=3200
GatewayAddress=54.158.171.153
GatewayPort=42001
Debug=1
 
[P25 Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=42020
LocalPort=32010
ModeHang=0
Debug=0
 
[NXDN Network]
Enable=0
#LocalAddress=127.0.0.1
Debug=0
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020

DVSwitch.ini

; MMDVM_Bridge export / import 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]
logFilePath = /var/log/Quantar_Bridge.log
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)
 
; 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 da
tabase
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 = 127.0.0.1             ; 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 = 1                        ; 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 = 31100                  ; Port to send AMBE TLV frames to (export)
RXPort = 31103                  ; Port to listen on (import)
FallbackID = 3140122            ; In case we can not find a valid DMR id in the database, 
export this one
ExportTG = 31403                 ; Which TG to export
Slot = 1                        ; Export slot

Analog_Bridge_Allstar.ini

; Analog_Bridge configuration file.
;   This file should be placed in either /etc or it can be
;   supplied as a path on the Analog_Bridge command line.
 
; The best way to think of this file, is that there are two main sections, the USRP (analo
g audio) and
; AMBE_AUDIO (encoded audio).  Analog_Bridge will take everything sent to the USRP port an
d
; encode it for transmission on the AMBE_AUDIO port.  The encoder will use the format defi
ned in ambeMode.
; As you might expect, the reverse direction is defined also.
 
 
; General Section describes settings for Analog_Bridge itself.
[GENERAL]
logLevel = 2                            ; Show messages and above 0=No logging, 1=Debug, 2
=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
 
; Metadata management
subscriberFile = /etc/subscriber_ids.csv   ; DMR ID to callsign lookup data
exportMetadata = true                   ; Export metadata to USRP partner (transcode setup
s require this)
 
; General vocoder setup information
decoderFallBack = true                 ; Allow software AMBE decoding if a hardware decode
r is not found
useEmulator = false                     ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN
/NXDN)
emulatorAddress = 127.0.0.1:2470        ; IP address and port of the md380 server
 
; Information for xx_Bridge (Where xx is MMDVM, Quantar, HB, IPSC)

[AMBE_AUDIO]
address = 3.208.70.29                     ; IP address of xx_Bridge
txPort = 35103                          ; Transmit TLV frames to partner on this port
rxPort = 35100                          ; Listen for TLV frames from partner on this port
ambeMode = YSFN                         ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (enc
ode PCM to this format)
minTxTimeMS = 2000                      ; Minimum time in MS for hang delay (0-10000)
 
; The metadata below is used when ASL is the source since it does not have any concept of 
digital modes
gatewayDmrId = 3140122                        ; ID to use when transmitting from Analog_Br
idge
repeaterID = 314012210                          ; ID of source repeater
txTg = 19053                                    ; TG to use for all frames sent from Analo
g_Bridge -> xx_Bridge
txTs = 1                                ; Slot to use for frames sent from Analog_Bridge -
> xx_Bridge
colorCode = 1                           ; Color Code to assign DMR frames
 
; Information for USRP channel driver.  This interface uses PCM to transfer audio informat
ion
; There are two typical configurations, ASL and Transcode.  ASL (AllstarLink) is for analo
g clients connected
; to a digital network.  Transcode is when Analog_Bridge actually points its PCM interface
s at a second Analog_Bridge, 
; causing a TLV <-- (pcm <--> pcm) --> TLV type of architecture.
;   When using ASL, this matches the rpt.conf ASL file with a setting like:
;   rxchannel = usrp/127.0.0.1:34001:32001
;   When Transcoding, make two ini files and set txPort equal to the other instance rxPort
 (crossover).  Launch
;   each instance with its own ini file.

[USRP]
address = rcwacomputer.ddns.net                     ; IP address of USRP partner (Allstar/
Asterisk or another Analog_Bridge)
txPort = 33001                          ; Transmit USRP frames on this port
rxPort = 35001                          ; Listen for USRP frames on this port
aslAudio = AUDIO_UNITY               ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE
_GAIN)
agcGain = -20                             ; Gain 1 = Unity Gain 2 = two time the level of 
unity
dmrAudio = AUDIO_USE_GAIN               ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUD
IO_BPF)
dmrGain = 0.15                          ; Gain 1 = Unity Gain .50 = half the level of unit
y
 
; Information for DV3000 hardware decoder
;   There are two configuration modes: IP (AMBEServer) and serial (direct connect hardware
)
;   Use top server and port if using AMBEServer
;   Use bottom server/port and serial = true if using the DV3000u (thumbdv)
;   Did you run AMBETest4.py before using this?
[DV3000]
;address = 127.0.0.1                     ; IP address of AMBEServer
;rxPort = 2460                           ; Port of AMBEServer
; address = /dev/ttyUSB0                ; Device of DV3000U on this machine
; baud = 460800                         ; Baud rate of the dongle (230400 or 460800)
; serial = true                         ; Use serial=true for direct connect or serial=fal
se for AMBEServer

Analog Bridge log:

I: 2021-03-10 13:01:07.780 Analog Bridge is starting
M: 2021-03-10 13:01:07.781 Setting [GENERAL] logLevel -> 2
M: 2021-03-10 13:01:07.781 Setting [GENERAL] subscriberFile -> /etc/subscriber_ids.csv
M: 2021-03-10 13:01:07.781 Setting [GENERAL] exportMetadata -> true
M: 2021-03-10 13:01:07.781 Setting [GENERAL] decoderFallBack -> true
M: 2021-03-10 13:01:07.781 Setting [GENERAL] useEmulator -> false
M: 2021-03-10 13:01:07.781 Setting [GENERAL] emulatorAddress -> 127.0.0.1:2470
M: 2021-03-10 13:01:07.781 Setting [AMBE_AUDIO] address -> 3.208.70.29
M: 2021-03-10 13:01:07.781 Setting [AMBE_AUDIO] txPort -> 35103
M: 2021-03-10 13:01:07.781 Setting [AMBE_AUDIO] rxPort -> 35100
M: 2021-03-10 13:01:07.781 Setting [AMBE_AUDIO] ambeMode -> YSFN
M: 2021-03-10 13:01:07.781 Setting [AMBE_AUDIO] minTxTimeMS -> 2000
M: 2021-03-10 13:01:07.781 Setting [AMBE_AUDIO] gatewayDmrId -> 3140122
M: 2021-03-10 13:01:07.781 Setting [AMBE_AUDIO] repeaterID -> 314012210
M: 2021-03-10 13:01:07.781 Setting [AMBE_AUDIO] txTg -> 19053
M: 2021-03-10 13:01:07.781 Setting [AMBE_AUDIO] txTs -> 1
M: 2021-03-10 13:01:07.781 Setting [AMBE_AUDIO] colorCode -> 1
M: 2021-03-10 13:01:07.781 Setting [USRP] address -> rcwacomputer.ddns.net
M: 2021-03-10 13:01:07.782 Setting [USRP] txPort -> 33001
M: 2021-03-10 13:01:07.782 Setting [USRP] rxPort -> 35001
M: 2021-03-10 13:01:07.782 Setting [USRP] aslAudio -> AUDIO_UNITY
M: 2021-03-10 13:01:07.782 Setting [USRP] agcGain -> -20
M: 2021-03-10 13:01:07.782 Setting [USRP] dmrAudio -> AUDIO_USE_GAIN
M: 2021-03-10 13:01:07.782 Setting [USRP] dmrGain -> 0.15
W: 2021-03-10 13:01:07.782 ioctl reset error 
W: 2021-03-10 13:01:07.782 ioctl speed error 
W: 2021-03-10 13:01:07.782 ioctl stereo error 
W: 2021-03-10 13:01:07.782 ioctl setfmt error 
M: 2021-03-10 13:01:07.782 Audio In/Out Device: /dev/null
I: 2021-03-10 13:01:07.782 Open UDP listener on 3.208.70.29:35100
I: 2021-03-10 13:01:07.782 Open USRP on rcwacomputer.ddns.net:33001
M: 2021-03-10 13:01:07.782 Connecting to DV3000 hardware......
M: 2021-03-10 13:01:07.782 Connecting to DV3000 hardware......
W: 2021-03-10 13:01:08.797 DV3000 not found at 127.0.0.1:2460
I: 2021-03-10 13:01:08.798 Subscriber IDs loaded: 1
I: 2021-03-10 13:01:08.798 Default extended metadata <3140122>
W: 2021-03-10 13:01:08.798 Using software MBE decoder version 1.2.3
W: 2021-03-10 13:01:08.798 Using software OP25 IMBE/AMBE vocoder
I: 2021-03-10 13:01:08.798 Starting Analog_Bridge --> USRP thread
I: 2021-03-10 13:01:08.801 Open UDP listener on rcwacomputer.ddns.net:35001
I: 2021-03-10 13:01:08.801 Starting USRP --> HB_Bridge thread
I: 2021-03-10 13:01:40.795 Begin TX: src=3140122 rpt=0 dst=31403 slot=1 cc=0
I: 2021-03-10 13:01:46.975 Begin TX: src=3140122 rpt=0 dst=31403 slot=1 cc=0
M: 2021-03-10 13:01:53.325 PTT on
M: 2021-03-10 13:01:59.618 PTT off (keyed for 6293 ms)
I: 2021-03-10 13:08:46.547 Analog Bridge Version 1.1 Wed May 30 09:44:39 EDT 2018
I: 2021-03-10 13:08:46.547 Copyright (C) 2018 DVSwitch, INAD.
I: 2021-03-10 13:08:46.547 Created by Mike N4IRR and Steve N4IRS
I: 2021-03-10 13:08:46.547 Analog Bridge comes with ABSOLUTELY NO WARRANTY
I: 2021-03-10 13:08:46.547 
I: 2021-03-10 13:08:46.547 This software is for use on amateur radio networks only,
I: 2021-03-10 13:08:46.547 it is to be used for educational purposes only. Its use on
I: 2021-03-10 13:08:46.547 commercial networks is strictly prohibited.
I: 2021-03-10 13:08:46.547 
I: 2021-03-10 13:08:46.547 Analog Bridge is starting
M: 2021-03-10 13:08:46.548 Setting [GENERAL] logLevel -> 2
M: 2021-03-10 13:08:46.548 Setting [GENERAL] subscriberFile -> /etc/subscriber_ids.csv
M: 2021-03-10 13:08:46.548 Setting [GENERAL] exportMetadata -> true
M: 2021-03-10 13:08:46.548 Setting [GENERAL] decoderFallBack -> true
M: 2021-03-10 13:08:46.548 Setting [GENERAL] useEmulator -> false
M: 2021-03-10 13:08:46.548 Setting [GENERAL] emulatorAddress -> 127.0.0.1:2470
M: 2021-03-10 13:08:46.548 Setting [AMBE_AUDIO] address -> 3.208.70.29
M: 2021-03-10 13:08:46.548 Setting [AMBE_AUDIO] txPort -> 35103
M: 2021-03-10 13:08:46.548 Setting [AMBE_AUDIO] rxPort -> 35100
M: 2021-03-10 13:08:46.548 Setting [AMBE_AUDIO] ambeMode -> YSFN
M: 2021-03-10 13:08:46.548 Setting [AMBE_AUDIO] minTxTimeMS -> 2000
M: 2021-03-10 13:08:46.548 Setting [AMBE_AUDIO] gatewayDmrId -> 3140122
M: 2021-03-10 13:08:46.548 Setting [AMBE_AUDIO] repeaterID -> 314012210
M: 2021-03-10 13:08:46.548 Setting [AMBE_AUDIO] txTg -> 19053
M: 2021-03-10 13:08:46.549 Setting [AMBE_AUDIO] txTs -> 1
M: 2021-03-10 13:08:46.549 Setting [AMBE_AUDIO] colorCode -> 1
M: 2021-03-10 13:08:46.549 Setting [USRP] address -> rcwacomputer.ddns.net
M: 2021-03-10 13:08:46.549 Setting [USRP] txPort -> 33001
M: 2021-03-10 13:08:46.549 Setting [USRP] rxPort -> 35001
M: 2021-03-10 13:08:46.549 Setting [USRP] aslAudio -> AUDIO_UNITY
M: 2021-03-10 13:08:46.549 Setting [USRP] agcGain -> -20
M: 2021-03-10 13:08:46.549 Setting [USRP] dmrAudio -> AUDIO_USE_GAIN
M: 2021-03-10 13:08:46.549 Setting [USRP] dmrGain -> 0.15
W: 2021-03-10 13:08:46.549 ioctl reset error 
W: 2021-03-10 13:08:46.549 ioctl speed error 
W: 2021-03-10 13:08:46.549 ioctl stereo error 
W: 2021-03-10 13:08:46.550 ioctl setfmt error 
M: 2021-03-10 13:08:46.550 Audio In/Out Device: /dev/null
I: 2021-03-10 13:08:46.550 Open UDP listener on 3.208.70.29:35100
I: 2021-03-10 13:08:46.550 Open USRP on rcwacomputer.ddns.net:33001
M: 2021-03-10 13:08:46.550 Connecting to DV3000 hardware......
W: 2021-03-10 13:08:47.564 DV3000 not found at 127.0.0.1:2460
I: 2021-03-10 13:08:47.566 Subscriber IDs loaded: 1
I: 2021-03-10 13:08:47.566 Default extended metadata <3140122>
W: 2021-03-10 13:08:47.566 Using software MBE decoder version 1.2.3
W: 2021-03-10 13:08:47.566 Using software OP25 IMBE/AMBE vocoder
I: 2021-03-10 13:08:47.569 Open UDP listener on rcwacomputer.ddns.net:35001
I: 2021-03-10 13:08:47.569 Starting USRP --> HB_Bridge thread
M: 2021-03-10 13:08:48.404 PTT on
M: 2021-03-10 13:08:49.593 Short transmission, extend hang time by 811 ms
M: 2021-03-10 13:08:50.435 PTT off (keyed for 2031 ms)
M: 2021-03-10 13:08:52.104 PTT on
M: 2021-03-10 13:08:56.874 PTT off (keyed for 4770 ms)
M: 2021-03-10 13:09:30.304 PTT on
M: 2021-03-10 13:09:32.293 Short transmission, extend hang time by 11 ms
M: 2021-03-10 13:09:32.353 PTT off (keyed for 2049 ms)
M: 2021-03-10 13:10:59.444 PTT on
M: 2021-03-10 13:11:01.556 PTT off (keyed for 2112 ms)

MMDVM_Bridge log:

I: 2021-03-10 18:58:47.207 YSF, received TLV header from 3140122      to ALL
I: 2021-03-10 18:58:47.310 YSF, Narrow transmit (72 bit)
M: 2021-03-10 18:59:13.602 YSF, TX state = OFF
M: 2021-03-10 18:59:13.602 YSF, received TLV end of transmission, 1.0 seconds, BER: 2.4
M: 2021-03-10 18:59:17.187 YSF, TX state = ON
I: 2021-03-10 18:59:17.187 YSF, Begin TX: src=3140122 rpt=314012210 dst=19053 slot=1 cc=1 
metadata=3140122
I: 2021-03-10 18:59:17.187 YSF, received TLV header from 3140122      to ALL
I: 2021-03-10 18:59:17.290 YSF, Narrow transmit (72 bit)
M: 2021-03-10 18:59:23.019 YSF, TX state = OFF
M: 2021-03-10 18:59:23.019 YSF, received TLV end of transmission, 1.0 seconds, BER: 2.4
M: 2021-03-10 18:59:29.127 YSF, TX state = ON
I: 2021-03-10 18:59:29.127 YSF, Begin TX: src=3140122 rpt=314012210 dst=19053 slot=1 cc=1 
metadata=3140122
I: 2021-03-10 18:59:29.127 YSF, received TLV header from 3140122      to ALL
I: 2021-03-10 18:59:29.210 YSF, Narrow transmit (72 bit)
M: 2021-03-10 18:59:38.962 YSF, TX state = OFF
M: 2021-03-10 18:59:38.962 YSF, received TLV end of transmission, 1.0 seconds, BER: 2.4
M: 2021-03-10 18:59:42.629 YSF, TX state = ON
I: 2021-03-10 18:59:42.629 YSF, Begin TX: src=3140122 rpt=314012210 dst=19053 slot=1 cc=1 
metadata=3140122
I: 2021-03-10 18:59:42.629 YSF, received TLV header from 3140122      to ALL
I: 2021-03-10 18:59:42.711 YSF, Narrow transmit (72 bit)
M: 2021-03-10 19:00:23.179 YSF, TX state = OFF
M: 2021-03-10 19:00:23.179 YSF, received TLV end of transmission, 1.0 seconds, BER: 2.4
M: 2021-03-10 19:00:40.626 YSF, TX state = ON
I: 2021-03-10 19:00:40.626 YSF, Begin TX: src=3140122 rpt=314012210 dst=19053 slot=1 cc=1 
metadata=3140122
I: 2021-03-10 19:00:40.626 YSF, received TLV header from 3140122      to ALL
I: 2021-03-10 19:00:40.709 YSF, Narrow transmit (72 bit)
 


Re: Our ability to support connectivity to TGIF.network

Steve N4IRS
 

Support was the problem. It was not automation that required the match when I attempted to create the account. I'll not worry about it for now until it becomes an issue.

Thank, Steve

On 3/9/2021 1:27 PM, Joe, WB3IHY wrote:
I'll be here.  Also, to resolve your registration issue, shooting an email to support@... describing the problem will likely get that taken care of.


Re: Our ability to support connectivity to TGIF.network

David Young
 

Steve,
You can register on the new TGIF server by going to the WEB page:  prime.tgif.network.  There at the top is a link to login or register.  Registering gives you capability to go to self-care and generate a security prime.tgif.password for your DMR ID's (separate password for each DMR ID) which currently you need to access the prime.tgif.network talk groups.  This site is in beta testing until Ty Weaver decides it is ready to replace the existing tgif.network legacy.  Once this happens the current tgif.network DNS name will be reassigned to the new prime.tgif.network IP and the WEB link will then become the same as the legacy which is tgif.network.
Each TG admin on the new server will be able to set the security password for his/her talk group or leave it as the default password:  passw0rd.
We have also been using DVSwitch to bridge talk group 30639 on the prime.tgif.network into our master hblink3 hub and it works fine.  Currently we are using the security password which we put into the MMDVM_Bridge.ini file in the DMR Network stanza.  No problems found doing this, other than you need to be registered and have your own security password to access any talk group on the new server.

Dave
--
Dave WB6DTB


Re: Our ability to support connectivity to TGIF.network

Joe, WB3IHY
 

I'll be here.  Also, to resolve your registration issue, shooting an email to support@... describing the problem will likely get that taken care of.


Re: Our ability to support connectivity to TGIF.network

Steve N4IRS
 

Joe,
Thanks. I may have to call on you if someone has a problem.

Steve

On 3/9/2021 1:22 PM, Joe, WB3IHY wrote:
For what it's worth, I have TGIF Prime set up on three different DVSwitch instances and it works fine on all of them.


Re: Our ability to support connectivity to TGIF.network

Joe, WB3IHY
 

For what it's worth, I have TGIF Prime set up on three different DVSwitch instances and it works fine on all of them.


Re: Monit stopped working, checking DVstick 30 is being used

Jason Turning
 


D-Star is different as each reflector is it's own server. I'm new to playing with D-Star with DVswitch Server, but I've heard that some of the servers are having issues with too many hotspots parked 24/7 which sucks up a lot of bandwidth and resources. So they're blocking people that try to connect with more than one hotspot since the second one will keep trying to connect. So best to only have one connection and then unlink if you're not actively listening. 

Side note, I added the NW Digital vocoder dongle, and what an audio improvement. And D-Star sounds pretty good. I had to redo my D-Star registration as some of the reflectors wouldn't link. I had done D-Star registration before for Peanut, but somehow it was dropped, so perhaps I hadn't completed it properly. Funny that I could still use Peanut and get into some of the D-Star reflectors like REF030C. So if you're having issues connecting you might check your D-Star registration.

Jason - WY7JT


On Sun, Mar 7, 2021 at 11:40 AM David J Taylor via groups.io <david-taylor=blueyonder.co.uk@groups.io> wrote:

One question - how many hotspots/DVswitch can one D-STAR user have on a
single public IP address?


Re: Our ability to support connectivity to TGIF.network

Steve N4IRS
 

It's good to hear they are going to temporarily disable the mandatory password. I'll be able to test until they enable it. As to interaction with server admins, I have had no problem with most. Some were quite helpful during the beta phase of Analog_Reflector. I hope some day to have the same with TGIF.

Steve N4IRS

On 3/9/2021 11:35 AM, Jason Turning wrote:
They're just going to redirect traffic from the legacy server to the new server and temporarily disable the mandatory password of the beta server, so it won't affect users at switch over. I believe they'll eventually want you to set up a password. They're finishing up the TG dashboard which will give TG owners complete control over their TG, and then make the switch. What's neat is as a TG owner you'll be able to do whatever you want as long as it doesn't negatively impact the server. So kind of a libre version of Brandmeister where you only have to be worried about being blocked by the TG owner/admin. No curmudgeon server admins running wild and disrespecting their users like on some other services. 

Jason - WY7JT


Re: Our ability to support connectivity to TGIF.network

Jason Turning
 

They're just going to redirect traffic from the legacy server to the new server and temporarily disable the mandatory password of the beta server, so it won't affect users at switch over. I believe they'll eventually want you to set up a password. They're finishing up the TG dashboard which will give TG owners complete control over their TG, and then make the switch. What's neat is as a TG owner you'll be able to do whatever you want as long as it doesn't negatively impact the server. So kind of a libre version of Brandmeister where you only have to be worried about being blocked by the TG owner/admin. No curmudgeon server admins running wild and disrespecting their users like on some other services. 

Jason - WY7JT

441 - 460 of 9203