Date   

How to connect to FCS001 27

IK7VXC Mike
 

Sorry for the noobie question. 
I wish to connect to FCS001 27 but I don't know how to set it up in DVSwitch. Apparently using 176.10.105.218:65000 is not enough. In fact I don't know how to point the reflector to operate on module 27.
Can you please help?
Thank you

IK7VXC Mike


Re: Truncated DMR audio

Danny Lloyd
 

The issue was with the talk group.  The system was using an unnamed 5 digit talk group.  It appears that Brandmeister found out and shut it down.  It works now using a 7 digit talk group.

Danny


Re: Truncated DMR audio

Steve N4IRS
 

What TG are you using?

On 7/15/21 3:59 PM, Danny Lloyd wrote:
I have an allstar link setup with mmdvm bridge (1.63) and analog bridge (1.6.1).  I use thumbdv for the vocoder, all running on a RPI 4.    I am connecting to 3104 master.

Everything has worked great for the past several months.  (No changes or updates)  This morning DMR users reported only hearing the first 1 to 2 seconds of dmr audio from the bridge.  I connected my hotspot to the talk group and sure enough - when someone talks on the analog side, the connected dmr users only hear the first 2 seconds.

The logs for MB and AB indicate that we are transmitting much more voice data than 2 seconds.  There are no errors in those two logs.

I tried a reboot, however, that did not change the operation.  I have though about changing masters to see if that helped.

Anyone else seen anything like this or has a suggestion?

Danny/KB4MDD


Truncated DMR audio

Danny Lloyd
 

I have an allstar link setup with mmdvm bridge (1.63) and analog bridge (1.6.1).  I use thumbdv for the vocoder, all running on a RPI 4.    I am connecting to 3104 master.

Everything has worked great for the past several months.  (No changes or updates)  This morning DMR users reported only hearing the first 1 to 2 seconds of dmr audio from the bridge.  I connected my hotspot to the talk group and sure enough - when someone talks on the analog side, the connected dmr users only hear the first 2 seconds.

The logs for MB and AB indicate that we are transmitting much more voice data than 2 seconds.  There are no errors in those two logs.

I tried a reboot, however, that did not change the operation.  I have though about changing masters to see if that helped.

Anyone else seen anything like this or has a suggestion?

Danny/KB4MDD


Re: System Builder Script where is Asterisk?! #analog_bridge

craig@...
 

On Mon, Jul 12, 2021 at 10:49 AM, Steve N4IRS wrote:
apt install allstar
OMG! You're right! Thanks!!


Re: System Builder Script where is Asterisk?! #analog_bridge

Steve N4IRS
 

You don't have AllStar installed.
apt install allstar

Steve N4IRS

On 7/12/2021 11:22 AM, craig@... wrote:
Thanks for reading this, a simple question, where can I find the IAX, RPT EXTENSIONS files when I use the DVSwitch-System-Builder script, yes, I've looked in etc/asterisk but it doesn't exist.

Thanks, Craig G8PY


System Builder Script where is Asterisk?! #analog_bridge

craig@...
 

Thanks for reading this, a simple question, where can I find the IAX, RPT EXTENSIONS files when I use the DVSwitch-System-Builder script, yes, I've looked in etc/asterisk but it doesn't exist.

Thanks, Craig G8PY


DSTAR TX from ASL comes out as TG 0

Michael Champion Sr
 

When I transmit with my ASL node into Analog_Reflector on DSTAR, the Target is TG 0.

 

But, if I use the DVSW web client it work properly with ‘CQCQCQ via REF001 E’

 

This used to work, did I mess up a config somehow? Or did something change in updates?

 

 

-Michael

 


Re: ASL Using DVSWITCH client on android and Anytone 878 radio #dvs #analog_bridge

Stephen Fairfield
 

I have Analog_Reflector working. Lotsa new "stuff" to configure tho. I have used with the HUC client and also on my analog phone with   dvs mobile. I have not tried it yet with my analog Radio connection from the 878UV to my SHARI node.
Thank you for all your help Steve. You ROCK !!! 73s N1SAF - Steve


Re: ASL Using DVSWITCH client on android and Anytone 878 radio #dvs #analog_bridge

Steve N4IRS
 

On 7/2/21 7:24 AM, Fairfieldsteve@... wrote:
Yes same LAN. Yes I can access from outside localLAN using public address. 
Steve



Re: DVSwitch Client does not receive

Gareth GM0WUR
 

Hi Everyone,

First of all Sorry Steve that this has taken me a while to post. Family medical emergency kept me busy since we were in contact.

Anyway for the benefit of everyone. Thanks to Steve, I can report my DVSwitch Client app is working fully.


After much pondering and trying of things it was discovered that the issues were at the end of the day not related to the DVSwitch Server and ports firewalls etc. That was proven because Steve connected to the server first time and it worked. So that left me with the t320 and the client to look at.

What eventually was discovered was that after putting a SIM card into the t320 and switching off wifi it all started working, Reconnect to the WiFi directly built in to the ISP router - Again it was now working A OK.

It would appear that the issue was that my main WiFi sits behind a couple of Managed network switches and somehow UDP packets were getting blocked on their way back in.

Honestly I'm at a loss to explain it. However a full shutdown and reboot of my network from scratch to make sure all the ARP tables etc etc were flushed and no I'm happy to report the Client on the t320 is working using 4G, WiFi (my main and ISP direct) also it works tethered to my Mobile Phone.

So there you have it...... Thanks again to Steve!

Best Regards,

Gareth GM0WUR


Re: ASL Using DVSWITCH client on android and Anytone 878 radio #dvs #analog_bridge

Fairfieldsteve@...
 

Done restarted AB
Sent email


Re: ASL Using DVSWITCH client on android and Anytone 878 radio #dvs #analog_bridge

Steve N4IRS
 

Set ports to 50001. Send public IP to me at szingman@...

On 7/2/21 7:24 AM, Fairfieldsteve@... wrote:
Yes same LAN. Yes I can access from outside localLAN using public address. 
Steve



Re: ASL Using DVSWITCH client on android and Anytone 878 radio #dvs #analog_bridge

Fairfieldsteve@...
 

Yes same LAN. Yes I can access from outside localLAN using public address. 
Steve


Re: ASL Using DVSWITCH client on android and Anytone 878 radio #dvs #analog_bridge

Steve N4IRS
 

Are you on the same LAN? Is the Server exposed to the outside world?

On 7/1/21 4:51 PM, Fairfieldsteve@... wrote:
Yes same issue
73 
N1saf
Steve


Re: ASL Using DVSWITCH client on android and Anytone 878 radio #dvs #analog_bridge

Fairfieldsteve@...
 

Yes same issue
73 
N1saf
Steve


Re: ASL Using DVSWITCH client on android and Anytone 878 radio #dvs #analog_bridge

Steve N4IRS
 

Have you tried anyother TG or parrot?

On 7/1/21 11:42 AM, Stephen Fairfield wrote:
.I am running the ASL 2.0 on a SHAri rpi4 NODE. It works fine except for one issue:

If I use 50001 tx and receive ports in AB.ini and in the DVSWITCH mobile client config, I can connect to BM ie TG91 and I hear the audio on that TG91 fine on 
my android phone in the DVS client, but not on the Radio.
If I change AB.ini USRP stanza from 50001/50001 to 32001/34001 and in the DVS config on the phone, I hear the audio on that TG91 fine on the Radio, but nothing
in the audio on the DVS phone client.

Here is my AB.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 (analog audio) and
; AMBE_AUDIO (compressed audio).  Analog_Bridge will take everything sent to the USRP port andsystemctl status analog_bridge19
; encode it for transmission on the AMBE_AUDIO port.  The encoder will use the format defined in ambeMode.
; As you might expect, the reverse direction is defined too.
 
; Analog_Bridge supports include files. More on this later...
include = dvsm.macro
; include = asl.macro
 
; 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
exportMetadata = true                   ; Export metadata to USRP partner (transcode setups require this)
transferRootDir = /tmp ; Export database files to USRP partner
subscriberFile = /var/lib/dvswitch/subscriber_ids.csv   ; DMR ID to callsign lookup data
 
; General vocoder setup information
decoderFallBack = true                  ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = true                      ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470        ; IP address and port of the md380 server
 
;pcmPort = 2222 ; UDP port to send to the WebProxy saf
 
; Information for xx_Bridge (Where xx is MMDVM, Quantar, HB, IPSC)
[AMBE_AUDIO]
address = 127.0.0.1                     ; IP address of xx_Bridge
txPort = 31103                          ; Transmit TLV frames to partner on this port
rxPort = 31100                          ; Listen for TLV frames from partner on this port
ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2500                      ; Analog -> Digital 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 = 3172638                  ; ID to use when transmitting from Analog_Bridge 7 digit ID
repeaterID = 317263811                  ; ID of source repeater 7 digit ID plus 2 digit SSID
txTg = 317263                                ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2                                ; 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 information
; There are two typical configurations, ASL and Transcode.  ASL (AllstarLink) is for analog clients connected
; to a digital network.  Transcode is when Analog_Bridge actually points its PCM interfaces back at itself, 
; 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 = 127.0.0.1                     ; IP address of USRP partner (Analog_Reflector, Allstar/Asterisk or another Analog_Bridge)
;txPort = 50001 ; Transmit USRP frames on this port
;rxPort = 50001 ; Listen for USRP frames on this port
txPort = 32001                          ; Transmit USRP frames on this port
rxPort = 34001                          ; Listen for USRP frames on this port
usrpAudio = AUDIO_USE_GAIN              ; Digital -> Analog (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_USE_AGC)
usrpGain = 4.00                         ; Gain factor when usrpAudio = AUDIO_USE_GAIN (0.0 to 5.0) (1.0 = AUDIO_UNITY)
usrpAGC = -20,10,100                    ; Set the agc threshold (db), slope (db) and decay (ms)
tlvAudio = AUDIO_USE_GAIN               ; Analog -> Digital (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
tlvGain = 0.25                          ; Gain factor when tlvAudio = AUDIO_USE_GAIN (0.0 to 5.0) (1.0 = AUDIO_UNITY)
 
[MACROS]
 
; Where the macros are
; xxxx=yyyy
; xxxx is the dial string to match
; yyyy is the command line to execute
 
; xxxx must be preceded by a *
; xxxx can be any string (alphanumeric)
; yyyy is the command to execute
; yyyy will replace xxxx in the dial string
; arguments follow the macro name with a # delimiter
 
; For example using macro "5678" above would look like:
; *5678#9876
 
; Which would invoke:
; echo 9876
 
; 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=false for AMBEServer
[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=false for AMBEServer

Can you please help ?
N1SAF
Steve
 


ASL Using DVSWITCH client on android and Anytone 878 radio #dvs #analog_bridge

Stephen Fairfield
 

.I am running the ASL 2.0 on a SHAri rpi4 NODE. It works fine except for one issue:

If I use 50001 tx and receive ports in AB.ini and in the DVSWITCH mobile client config, I can connect to BM ie TG91 and I hear the audio on that TG91 fine on 
my android phone in the DVS client, but not on the Radio.
If I change AB.ini USRP stanza from 50001/50001 to 32001/34001 and in the DVS config on the phone, I hear the audio on that TG91 fine on the Radio, but nothing
in the audio on the DVS phone client.

Here is my AB.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 (analog audio) and
; AMBE_AUDIO (compressed audio).  Analog_Bridge will take everything sent to the USRP port andsystemctl status analog_bridge19
; encode it for transmission on the AMBE_AUDIO port.  The encoder will use the format defined in ambeMode.
; As you might expect, the reverse direction is defined too.
 
; Analog_Bridge supports include files. More on this later...
include = dvsm.macro
; include = asl.macro
 
; 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
exportMetadata = true                   ; Export metadata to USRP partner (transcode setups require this)
transferRootDir = /tmp ; Export database files to USRP partner
subscriberFile = /var/lib/dvswitch/subscriber_ids.csv   ; DMR ID to callsign lookup data
 
; General vocoder setup information
decoderFallBack = true                  ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = true                      ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470        ; IP address and port of the md380 server
 
;pcmPort = 2222 ; UDP port to send to the WebProxy saf
 
; Information for xx_Bridge (Where xx is MMDVM, Quantar, HB, IPSC)
[AMBE_AUDIO]
address = 127.0.0.1                     ; IP address of xx_Bridge
txPort = 31103                          ; Transmit TLV frames to partner on this port
rxPort = 31100                          ; Listen for TLV frames from partner on this port
ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2500                      ; Analog -> Digital 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 = 3172638                  ; ID to use when transmitting from Analog_Bridge 7 digit ID
repeaterID = 317263811                  ; ID of source repeater 7 digit ID plus 2 digit SSID
txTg = 317263                                ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2                                ; 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 information
; There are two typical configurations, ASL and Transcode.  ASL (AllstarLink) is for analog clients connected
; to a digital network.  Transcode is when Analog_Bridge actually points its PCM interfaces back at itself, 
; 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 = 127.0.0.1                     ; IP address of USRP partner (Analog_Reflector, Allstar/Asterisk or another Analog_Bridge)
;txPort = 50001 ; Transmit USRP frames on this port
;rxPort = 50001 ; Listen for USRP frames on this port
txPort = 32001                          ; Transmit USRP frames on this port
rxPort = 34001                          ; Listen for USRP frames on this port
usrpAudio = AUDIO_USE_GAIN              ; Digital -> Analog (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_USE_AGC)
usrpGain = 4.00                         ; Gain factor when usrpAudio = AUDIO_USE_GAIN (0.0 to 5.0) (1.0 = AUDIO_UNITY)
usrpAGC = -20,10,100                    ; Set the agc threshold (db), slope (db) and decay (ms)
tlvAudio = AUDIO_USE_GAIN               ; Analog -> Digital (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
tlvGain = 0.25                          ; Gain factor when tlvAudio = AUDIO_USE_GAIN (0.0 to 5.0) (1.0 = AUDIO_UNITY)
 
[MACROS]
 
; Where the macros are
; xxxx=yyyy
; xxxx is the dial string to match
; yyyy is the command line to execute
 
; xxxx must be preceded by a *
; xxxx can be any string (alphanumeric)
; yyyy is the command to execute
; yyyy will replace xxxx in the dial string
; arguments follow the macro name with a # delimiter
 
; For example using macro "5678" above would look like:
; *5678#9876
 
; Which would invoke:
; echo 9876
 
; 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=false for AMBEServer
[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=false for AMBEServer

Can you please help ?
N1SAF
Steve
 


Re: DVSwitch Client does not receive

Steve N4IRS
 

Here is a follow up to this.
I was able to connect to his VPS with DVSwitch Mobile. Gareth found a issue with his wifi / LAN configuration. I'll let him explain.
Gareth, to answer your other question, you can share your DVSwitch Server with your father. You will want to add Analog_Reflector.

Steve N4IRS

On 6/30/21 9:56 PM, steelegwds@... wrote:
I'm just adding my current testing results.

Ok in an effort to rule out even the absurd. I've gone and paid for a VPS server for a month just to install DVSwitch - I figured lets try a full Deban server outside my LAN really can't do more than that.

So Installed DV Switch and configured it. No problems there it all fired up first time.

Change the config on my Laptop for the pyUC client set the TX and RX ports correctly (TX 50111, RX 50112) this matches the cloud servers settings in Analog_Bridge.ini - as I said before I noticed that using the same port number for both on the mobile client it never registers but different ports it does register (why I have no idea).

Anyway fire up pyUC and bingo! it works first time no faults. I can watch the DVSwitch Dashboard, connect to Parrot system etc etc all works - Two way audio as expected.

So then we move on to the DVSwitch client, just to rule out every possible glitch I can think of IT wise, I connected my t320 to my next-door neighbours WiFi (yes I had permission) configured the App with the appropriate ports and the IP address of the cloud server. It registered! if I enter talk group numbers and press send, Looking at DVSwitch Dashboard sure enough the talk group changes.

Try to transmit, again DVSwitch Dashboard indicates its receiving me and doing it's thing. But when say Parrot system trys to replay my test transmission, it shows in DVSwitch Dashboard but the Mobile Client App stays totally quiet no sign of live, no messages on screen nothing.... Dead as a Dodo.

So wanting to rule out an issue with the t320, I've now gotten hold of both an older Android Phone and a Nvida Shield Android Tablet - Installed DVSwitch client on them both, settings etc - same test... same results, can TX fine, can control the DVSwitch ok. But receive anything from the DVSwitch = NOPE.

The last test I did showed how totally Bonkers this is - Connected Laptop to DVSwitch in the Cloud via the pyUC via one internet connection, then connected the Mobile Client via another internet connection.... Used the Mobile client to transmit to the Parrot system - again Dashboard showed the TX working. Then when parrot replayed my transmission - The mobile client just sat there an did nothing, but the pyUC Client played out my voice and showed me the appropriate data in it's log window.

Talk about weird ass problem lol, anyone have a suggestion here? Steve I know your busy but is anyone else out there that has any ideas?

Praying for a Miracle.
Gareth GM0WUR


Re: DVSwitch Client does not receive

Steve N4IRS
 

Set the 2 ports to the same value and send me the IP address direct szingman@...

On 6/30/21 9:56 PM, steelegwds@... wrote:
I'm just adding my current testing results.

Ok in an effort to rule out even the absurd. I've gone and paid for a VPS server for a month just to install DVSwitch - I figured lets try a full Deban server outside my LAN really can't do more than that.

So Installed DV Switch and configured it. No problems there it all fired up first time.

Change the config on my Laptop for the pyUC client set the TX and RX ports correctly (TX 50111, RX 50112) this matches the cloud servers settings in Analog_Bridge.ini - as I said before I noticed that using the same port number for both on the mobile client it never registers but different ports it does register (why I have no idea).

Anyway fire up pyUC and bingo! it works first time no faults. I can watch the DVSwitch Dashboard, connect to Parrot system etc etc all works - Two way audio as expected.

So then we move on to the DVSwitch client, just to rule out every possible glitch I can think of IT wise, I connected my t320 to my next-door neighbours WiFi (yes I had permission) configured the App with the appropriate ports and the IP address of the cloud server. It registered! if I enter talk group numbers and press send, Looking at DVSwitch Dashboard sure enough the talk group changes.

Try to transmit, again DVSwitch Dashboard indicates its receiving me and doing it's thing. But when say Parrot system trys to replay my test transmission, it shows in DVSwitch Dashboard but the Mobile Client App stays totally quiet no sign of live, no messages on screen nothing.... Dead as a Dodo.

So wanting to rule out an issue with the t320, I've now gotten hold of both an older Android Phone and a Nvida Shield Android Tablet - Installed DVSwitch client on them both, settings etc - same test... same results, can TX fine, can control the DVSwitch ok. But receive anything from the DVSwitch = NOPE.

The last test I did showed how totally Bonkers this is - Connected Laptop to DVSwitch in the Cloud via the pyUC via one internet connection, then connected the Mobile Client via another internet connection.... Used the Mobile client to transmit to the Parrot system - again Dashboard showed the TX working. Then when parrot replayed my transmission - The mobile client just sat there an did nothing, but the pyUC Client played out my voice and showed me the appropriate data in it's log window.

Talk about weird ass problem lol, anyone have a suggestion here? Steve I know your busy but is anyone else out there that has any ideas?

Praying for a Miracle.
Gareth GM0WUR

321 - 340 of 9891