Date   

Re: Analog_Bridge, one-way audio from DMR to ASL

Mike Zingman - N4IRR
 

Here is what  I suspect (of course I could be wrong).  USRP uses UDP as its transport. 

If you are using DVSM, you set the mobile client to talk to AB on a single port.  This setting in AB (where TX and RX ports are the same) tells AB to use an enhanced protocol to talk to the client.  This enhancement is used to keep the NAT traversal path open to the client. The  trick is that AB  will send keep alive packets back to DVSM to tell the router/firewall that the NAT connection should be maintained.  As long as the keep alive packets are sent often enough the router will maintain the connection.

If you are using ASL as your USRP client to AB, you are using two ports  (TX and RX).  AB does not try to tell ASL to keep the  connection open (since ASL would not understand the keep alives).  So, if you are using ASL on a different machine than AB and there is a NAT between them, you will have problems.

Any of the above make sense?


Re: AMBE server use with md380-emu :D

EA4GAX - Sergio
 

Thank you egain, work perfect!!!


Re: Analog_Bridge, one-way audio from DMR to ASL

Patrick Perdue
 

3138495, but not sure that it matters.

I have it working in both directions on my VPS, where Analog_Bridge is connecting to a remote AMBE server. The problem with that setup is Analog_Bridge likes to stop passing audio after a while, which is why I'm trying to set DVSwitch up locally on a Pi, and have it connect to a remote USRP/ASL, rather than using DVSwitch on the VPS, and relying on a remote AMBEserver.

The Raspberry Pi is behind NAT with incoming UDP port 34001, but nothing from ASL ever makes it to my Analog_Bridge. Outbound traffic from DMR to ASL works fine.


On 11/17/2019 2:31 PM, Brad NK8J wrote:

What is your dmr id number. I had mine original 1139899 and had to upgrade it to the 3146521 to make mine work

On Sun, Nov 17, 2019, 9:10 AM Patrick Perdue <patrick@...> wrote:
Hmm...

That doesn't make sense to me, because then the TX and RX ports match on
both MMDVM_Bridge and Analog_Bridge. TX should go to RX of the other,
which is how it is by default.

I did try it, which caused nothing to pass in either direction.


On 11/17/2019 8:16 AM, Brad N8PC wrote:
> in your Analog_Bridge.ini file turn your txPort and rxPort around.
>
> txPort =31100
> rxPort=31103
>
>
>
> On 11/17/2019 12:45 AM, Patrick Perdue wrote:
>> Hi:
>> In moving my DVSwitch to a local Raspberry Pi 4 rather than running
>> it on the VPS, connecting to a remote AMBEserver, I'm running into a
>> problem.
>>
>> I now have audio going from DMR to USRP, but not the other way. It is
>> bi-directional when running DVSwitch on the VPS.
>>
>> Looking at the logs for Analog_Bridge, it doesn't appear to get audio
>> from ASL, as there is nothing in the log when there is a transmission
>> from Allstar.
>>
>>
>> In rpt.conf, I have:
>>
>> rxchannel = USRP/0.0.0.0:34001:32001; GNU Radio interface USRP
>>
>> In Analog_Bridge.ini:
>>
>> [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)
>> [USRP]
>> address = xlx.borris.me                     ; IP address of USRP
>> partner (Allstar/Asterisk or another Analog_Bridge)
>> txPort = 32001                          ; Transmit USRP frames on
>> this port
>> rxPort = 34001                          ; Listen for USRP frames on
>> this port
>>
>>
>> In DVSwitch.ini:
>>
>> [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
>>
>>
>> Here is a full log from Analog_Bridge. During this period, there were
>> several Allstar transmissions, but they didn't make it to the log.
>> Only DMR is seen.
>>
>>
>> I: 2019-11-17 05:23:55.512 Analog Bridge Version 1.4.1 Mon Nov 11
>> 19:06:12 UTC 2019
>> I: 2019-11-17 05:23:55.513 Copyright (C) 2018 DVSwitch, INAD.
>> I: 2019-11-17 05:23:55.513 Created by Mike N4IRR and Steve N4IRS
>> I: 2019-11-17 05:23:55.513 Analog Bridge comes with ABSOLUTELY NO
>> WARRANTY
>> I: 2019-11-17 05:23:55.513
>> I: 2019-11-17 05:23:55.513 This software is for use on amateur radio
>> networks only,
>> I: 2019-11-17 05:23:55.513 it is to be used for educational purposes
>> only. Its use on
>> I: 2019-11-17 05:23:55.513 commercial networks is strictly prohibited.
>> I: 2019-11-17 05:23:55.513
>> I: 2019-11-17 05:23:55.513 Analog Bridge is starting
>> M: 2019-11-17 05:23:55.513 Setting [GENERAL] logLevel -> 2
>> M: 2019-11-17 05:23:55.513 Setting [GENERAL] subscriberFile ->
>> /var/lib/dvswitch/subscriber_ids.csv
>> M: 2019-11-17 05:23:55.513 Setting [GENERAL] exportMetadata -> true
>> M: 2019-11-17 05:23:55.514 Setting [GENERAL] decoderFallBack -> true
>> M: 2019-11-17 05:23:55.514 Setting [GENERAL] useEmulator -> false
>> M: 2019-11-17 05:23:55.514 Setting [GENERAL] emulatorAddress ->
>> 127.0.0.1:2470
>> M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] address -> 127.0.0.1
>> M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] txPort -> 31103
>> M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] rxPort -> 31100
>> M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] ambeMode -> DMR
>> M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] minTxTimeMS -> 2500
>> M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] gatewayDmrId -> 3138495
>> M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] repeaterID -> 3154444
>> M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] txTg -> 31679
>> M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] txTs -> 2
>> M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] colorCode -> 1
>> M: 2019-11-17 05:23:55.514 Setting [USRP] address -> xlx.borris.me
>> M: 2019-11-17 05:23:55.514 Setting [USRP] txPort -> 32001
>> M: 2019-11-17 05:23:55.514 Setting [USRP] rxPort -> 34001
>> M: 2019-11-17 05:23:55.514 Setting [USRP] usrpAudio -> AUDIO_UNITY
>> M: 2019-11-17 05:23:55.515 Setting [USRP] usrpGain -> 1.10
>> M: 2019-11-17 05:23:55.515 Setting [USRP] tlvAudio -> AUDIO_UNITY
>> M: 2019-11-17 05:23:55.515 Setting [USRP] tlvGain -> 0.35
>> M: 2019-11-17 05:23:55.515 Setting [DV3000] address -> 127.0.0.1
>> M: 2019-11-17 05:23:55.515 Setting [DV3000] rxPort -> 2460
>> I: 2019-11-17 05:23:55.515 Open UDP listener on 127.0.0.1:31100
>> I: 2019-11-17 05:23:55.515 Open USRP on xlx.borris.me:32001
>> M: 2019-11-17 05:23:55.515 Connecting to DV3000 hardware......
>> M: 2019-11-17 05:23:55.535 Begin DV3000 decode
>> I: 2019-11-17 05:23:55.930 Subscriber IDs loaded: 146120
>> I: 2019-11-17 05:23:55.930 Default extended metadata <KE4DYI>
>> I: 2019-11-17 05:23:55.931 Using hardware AMBE vocoder
>> I: 2019-11-17 05:23:55.934 Connected to USRP xlx.borris.me:32001
>> I: 2019-11-17 05:23:55.935 Starting TLV --> Analog_Bridge (decoder)
>> --> USRP thread
>> I: 2019-11-17 05:23:55.935 Starting USRP --> Analog_Bridge (encoder)
>> -> TLV thread
>> I: 2019-11-17 05:24:06.913 Begin TX: src=3138495 rpt=0 dst=31679
>> slot=2 cc=0 call=KE4DYI
>> I: 2019-11-17 05:24:39.132 Begin TX: src=3138495 rpt=0 dst=31679
>> slot=2 cc=0 call=KE4DYI
>> I: 2019-11-17 05:24:58.271 Signal 2 received, exiting Analog_Bridge
>>
>> What am I missing here?
>>
>> Thanks and 73
>>
>> de
>>
>> KE4DYI
>>
>>
>>
>>
>
>
>




Re: AMBE server use with md380-emu :D

EA4GAX - Sergio
 

On Sun, Nov 17, 2019 at 11:29 AM, Steve N4IRS wrote:
Yes,
The UDP listener port is set in /lib/systemd/system/md380-emu.service
ExecStart=/opt/md380-emu/md380-emu -S 2470
Ok Steve, Thank you


Re: How many instances of MMDVM_Bridge, Analog_Bridge and md380-emu can work on the same machine at the same time?

EA4GAX - Sergio
 

Hi all
I´m interresting this cuestion, I´ll follow this topic.


Re: Analog_Bridge, one-way audio from DMR to ASL

Brad NK8J <bradnk8j@...>
 

What is your dmr id number. I had mine original 1139899 and had to upgrade it to the 3146521 to make mine work


On Sun, Nov 17, 2019, 9:10 AM Patrick Perdue <patrick@...> wrote:
Hmm...

That doesn't make sense to me, because then the TX and RX ports match on
both MMDVM_Bridge and Analog_Bridge. TX should go to RX of the other,
which is how it is by default.

I did try it, which caused nothing to pass in either direction.


On 11/17/2019 8:16 AM, Brad N8PC wrote:
> in your Analog_Bridge.ini file turn your txPort and rxPort around.
>
> txPort =31100
> rxPort=31103
>
>
>
> On 11/17/2019 12:45 AM, Patrick Perdue wrote:
>> Hi:
>> In moving my DVSwitch to a local Raspberry Pi 4 rather than running
>> it on the VPS, connecting to a remote AMBEserver, I'm running into a
>> problem.
>>
>> I now have audio going from DMR to USRP, but not the other way. It is
>> bi-directional when running DVSwitch on the VPS.
>>
>> Looking at the logs for Analog_Bridge, it doesn't appear to get audio
>> from ASL, as there is nothing in the log when there is a transmission
>> from Allstar.
>>
>>
>> In rpt.conf, I have:
>>
>> rxchannel = USRP/0.0.0.0:34001:32001; GNU Radio interface USRP
>>
>> In Analog_Bridge.ini:
>>
>> [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)
>> [USRP]
>> address = xlx.borris.me                     ; IP address of USRP
>> partner (Allstar/Asterisk or another Analog_Bridge)
>> txPort = 32001                          ; Transmit USRP frames on
>> this port
>> rxPort = 34001                          ; Listen for USRP frames on
>> this port
>>
>>
>> In DVSwitch.ini:
>>
>> [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
>>
>>
>> Here is a full log from Analog_Bridge. During this period, there were
>> several Allstar transmissions, but they didn't make it to the log.
>> Only DMR is seen.
>>
>>
>> I: 2019-11-17 05:23:55.512 Analog Bridge Version 1.4.1 Mon Nov 11
>> 19:06:12 UTC 2019
>> I: 2019-11-17 05:23:55.513 Copyright (C) 2018 DVSwitch, INAD.
>> I: 2019-11-17 05:23:55.513 Created by Mike N4IRR and Steve N4IRS
>> I: 2019-11-17 05:23:55.513 Analog Bridge comes with ABSOLUTELY NO
>> WARRANTY
>> I: 2019-11-17 05:23:55.513
>> I: 2019-11-17 05:23:55.513 This software is for use on amateur radio
>> networks only,
>> I: 2019-11-17 05:23:55.513 it is to be used for educational purposes
>> only. Its use on
>> I: 2019-11-17 05:23:55.513 commercial networks is strictly prohibited.
>> I: 2019-11-17 05:23:55.513
>> I: 2019-11-17 05:23:55.513 Analog Bridge is starting
>> M: 2019-11-17 05:23:55.513 Setting [GENERAL] logLevel -> 2
>> M: 2019-11-17 05:23:55.513 Setting [GENERAL] subscriberFile ->
>> /var/lib/dvswitch/subscriber_ids.csv
>> M: 2019-11-17 05:23:55.513 Setting [GENERAL] exportMetadata -> true
>> M: 2019-11-17 05:23:55.514 Setting [GENERAL] decoderFallBack -> true
>> M: 2019-11-17 05:23:55.514 Setting [GENERAL] useEmulator -> false
>> M: 2019-11-17 05:23:55.514 Setting [GENERAL] emulatorAddress ->
>> 127.0.0.1:2470
>> M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] address -> 127.0.0.1
>> M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] txPort -> 31103
>> M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] rxPort -> 31100
>> M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] ambeMode -> DMR
>> M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] minTxTimeMS -> 2500
>> M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] gatewayDmrId -> 3138495
>> M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] repeaterID -> 3154444
>> M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] txTg -> 31679
>> M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] txTs -> 2
>> M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] colorCode -> 1
>> M: 2019-11-17 05:23:55.514 Setting [USRP] address -> xlx.borris.me
>> M: 2019-11-17 05:23:55.514 Setting [USRP] txPort -> 32001
>> M: 2019-11-17 05:23:55.514 Setting [USRP] rxPort -> 34001
>> M: 2019-11-17 05:23:55.514 Setting [USRP] usrpAudio -> AUDIO_UNITY
>> M: 2019-11-17 05:23:55.515 Setting [USRP] usrpGain -> 1.10
>> M: 2019-11-17 05:23:55.515 Setting [USRP] tlvAudio -> AUDIO_UNITY
>> M: 2019-11-17 05:23:55.515 Setting [USRP] tlvGain -> 0.35
>> M: 2019-11-17 05:23:55.515 Setting [DV3000] address -> 127.0.0.1
>> M: 2019-11-17 05:23:55.515 Setting [DV3000] rxPort -> 2460
>> I: 2019-11-17 05:23:55.515 Open UDP listener on 127.0.0.1:31100
>> I: 2019-11-17 05:23:55.515 Open USRP on xlx.borris.me:32001
>> M: 2019-11-17 05:23:55.515 Connecting to DV3000 hardware......
>> M: 2019-11-17 05:23:55.535 Begin DV3000 decode
>> I: 2019-11-17 05:23:55.930 Subscriber IDs loaded: 146120
>> I: 2019-11-17 05:23:55.930 Default extended metadata <KE4DYI>
>> I: 2019-11-17 05:23:55.931 Using hardware AMBE vocoder
>> I: 2019-11-17 05:23:55.934 Connected to USRP xlx.borris.me:32001
>> I: 2019-11-17 05:23:55.935 Starting TLV --> Analog_Bridge (decoder)
>> --> USRP thread
>> I: 2019-11-17 05:23:55.935 Starting USRP --> Analog_Bridge (encoder)
>> -> TLV thread
>> I: 2019-11-17 05:24:06.913 Begin TX: src=3138495 rpt=0 dst=31679
>> slot=2 cc=0 call=KE4DYI
>> I: 2019-11-17 05:24:39.132 Begin TX: src=3138495 rpt=0 dst=31679
>> slot=2 cc=0 call=KE4DYI
>> I: 2019-11-17 05:24:58.271 Signal 2 received, exiting Analog_Bridge
>>
>> What am I missing here?
>>
>> Thanks and 73
>>
>> de
>>
>> KE4DYI
>>
>>
>>
>>
>
>
>




Re: AMBE server use with md380-emu :D

Steve N4IRS
 

Yes,
The UDP listener port is set in /lib/systemd/system/md380-emu.service
ExecStart=/opt/md380-emu/md380-emu -S 2470

73, Steve N4IRS

On 11/17/19 2:24 PM, EA4GAX - Sergio wrote:
Hi all
It`s possible change defaut port 2470 for ejemplo 2471 or other?
Thank you


Re: AMBE server use with md380-emu :D

EA4GAX - Sergio
 

Hi all
It`s possible change defaut port 2470 for ejemplo 2471 or other?
Thank you


Re: IPSC-bridge Dmrlink and HBlink3: help for how to #dmrlink #best_practices #hblink

ai6bx
 

I am at the same place. I have HBlink up and running and am preparing to install dmrlink to bring my Moto repeaters into the mix. I noted the cautions of considering install options for dmrlink and want to better understand the pros and cons of using mk vs. sh. Are there advantages of one over the other or better facilitation of management down the road of other modules or functionalities are added? 


Re: Analog_Bridge, one-way audio from DMR to ASL

Patrick Perdue
 

Hmm...

That doesn't make sense to me, because then the TX and RX ports match on both MMDVM_Bridge and Analog_Bridge. TX should go to RX of the other, which is how it is by default.

I did try it, which caused nothing to pass in either direction.

On 11/17/2019 8:16 AM, Brad N8PC wrote:
in your Analog_Bridge.ini file turn your txPort and rxPort around.

txPort =31100
rxPort=31103



On 11/17/2019 12:45 AM, Patrick Perdue wrote:
Hi:
In moving my DVSwitch to a local Raspberry Pi 4 rather than running it on the VPS, connecting to a remote AMBEserver, I'm running into a problem.

I now have audio going from DMR to USRP, but not the other way. It is bi-directional when running DVSwitch on the VPS.

Looking at the logs for Analog_Bridge, it doesn't appear to get audio from ASL, as there is nothing in the log when there is a transmission from Allstar.


In rpt.conf, I have:

rxchannel = USRP/0.0.0.0:34001:32001; GNU Radio interface USRP

In Analog_Bridge.ini:

[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)
[USRP]
address = xlx.borris.me                     ; IP address of USRP partner (Allstar/Asterisk or another Analog_Bridge)
txPort = 32001                          ; Transmit USRP frames on this port
rxPort = 34001                          ; Listen for USRP frames on this port


In DVSwitch.ini:

[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


Here is a full log from Analog_Bridge. During this period, there were several Allstar transmissions, but they didn't make it to the log. Only DMR is seen.


I: 2019-11-17 05:23:55.512 Analog Bridge Version 1.4.1 Mon Nov 11 19:06:12 UTC 2019
I: 2019-11-17 05:23:55.513 Copyright (C) 2018 DVSwitch, INAD.
I: 2019-11-17 05:23:55.513 Created by Mike N4IRR and Steve N4IRS
I: 2019-11-17 05:23:55.513 Analog Bridge comes with ABSOLUTELY NO WARRANTY
I: 2019-11-17 05:23:55.513
I: 2019-11-17 05:23:55.513 This software is for use on amateur radio networks only,
I: 2019-11-17 05:23:55.513 it is to be used for educational purposes only. Its use on
I: 2019-11-17 05:23:55.513 commercial networks is strictly prohibited.
I: 2019-11-17 05:23:55.513
I: 2019-11-17 05:23:55.513 Analog Bridge is starting
M: 2019-11-17 05:23:55.513 Setting [GENERAL] logLevel -> 2
M: 2019-11-17 05:23:55.513 Setting [GENERAL] subscriberFile -> /var/lib/dvswitch/subscriber_ids.csv
M: 2019-11-17 05:23:55.513 Setting [GENERAL] exportMetadata -> true
M: 2019-11-17 05:23:55.514 Setting [GENERAL] decoderFallBack -> true
M: 2019-11-17 05:23:55.514 Setting [GENERAL] useEmulator -> false
M: 2019-11-17 05:23:55.514 Setting [GENERAL] emulatorAddress -> 127.0.0.1:2470
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] address -> 127.0.0.1
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] txPort -> 31103
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] rxPort -> 31100
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] ambeMode -> DMR
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] minTxTimeMS -> 2500
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] gatewayDmrId -> 3138495
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] repeaterID -> 3154444
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] txTg -> 31679
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] txTs -> 2
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] colorCode -> 1
M: 2019-11-17 05:23:55.514 Setting [USRP] address -> xlx.borris.me
M: 2019-11-17 05:23:55.514 Setting [USRP] txPort -> 32001
M: 2019-11-17 05:23:55.514 Setting [USRP] rxPort -> 34001
M: 2019-11-17 05:23:55.514 Setting [USRP] usrpAudio -> AUDIO_UNITY
M: 2019-11-17 05:23:55.515 Setting [USRP] usrpGain -> 1.10
M: 2019-11-17 05:23:55.515 Setting [USRP] tlvAudio -> AUDIO_UNITY
M: 2019-11-17 05:23:55.515 Setting [USRP] tlvGain -> 0.35
M: 2019-11-17 05:23:55.515 Setting [DV3000] address -> 127.0.0.1
M: 2019-11-17 05:23:55.515 Setting [DV3000] rxPort -> 2460
I: 2019-11-17 05:23:55.515 Open UDP listener on 127.0.0.1:31100
I: 2019-11-17 05:23:55.515 Open USRP on xlx.borris.me:32001
M: 2019-11-17 05:23:55.515 Connecting to DV3000 hardware......
M: 2019-11-17 05:23:55.535 Begin DV3000 decode
I: 2019-11-17 05:23:55.930 Subscriber IDs loaded: 146120
I: 2019-11-17 05:23:55.930 Default extended metadata <KE4DYI>
I: 2019-11-17 05:23:55.931 Using hardware AMBE vocoder
I: 2019-11-17 05:23:55.934 Connected to USRP xlx.borris.me:32001
I: 2019-11-17 05:23:55.935 Starting TLV --> Analog_Bridge (decoder) --> USRP thread
I: 2019-11-17 05:23:55.935 Starting USRP --> Analog_Bridge (encoder) -> TLV thread
I: 2019-11-17 05:24:06.913 Begin TX: src=3138495 rpt=0 dst=31679 slot=2 cc=0 call=KE4DYI
I: 2019-11-17 05:24:39.132 Begin TX: src=3138495 rpt=0 dst=31679 slot=2 cc=0 call=KE4DYI
I: 2019-11-17 05:24:58.271 Signal 2 received, exiting Analog_Bridge

What am I missing here?

Thanks and 73

de

KE4DYI




Re: Analog_Bridge, one-way audio from DMR to ASL

Brad N8PC
 

in your Analog_Bridge.ini file turn your txPort and rxPort around.

txPort =31100
rxPort=31103

On 11/17/2019 12:45 AM, Patrick Perdue wrote:
Hi:
In moving my DVSwitch to a local Raspberry Pi 4 rather than running it on the VPS, connecting to a remote AMBEserver, I'm running into a problem.

I now have audio going from DMR to USRP, but not the other way. It is bi-directional when running DVSwitch on the VPS.

Looking at the logs for Analog_Bridge, it doesn't appear to get audio from ASL, as there is nothing in the log when there is a transmission from Allstar.


In rpt.conf, I have:

rxchannel = USRP/0.0.0.0:34001:32001; GNU Radio interface USRP

In Analog_Bridge.ini:

[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)
[USRP]
address = xlx.borris.me                     ; IP address of USRP partner (Allstar/Asterisk or another Analog_Bridge)
txPort = 32001                          ; Transmit USRP frames on this port
rxPort = 34001                          ; Listen for USRP frames on this port


In DVSwitch.ini:

[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


Here is a full log from Analog_Bridge. During this period, there were several Allstar transmissions, but they didn't make it to the log. Only DMR is seen.


I: 2019-11-17 05:23:55.512 Analog Bridge Version 1.4.1 Mon Nov 11 19:06:12 UTC 2019
I: 2019-11-17 05:23:55.513 Copyright (C) 2018 DVSwitch, INAD.
I: 2019-11-17 05:23:55.513 Created by Mike N4IRR and Steve N4IRS
I: 2019-11-17 05:23:55.513 Analog Bridge comes with ABSOLUTELY NO WARRANTY
I: 2019-11-17 05:23:55.513
I: 2019-11-17 05:23:55.513 This software is for use on amateur radio networks only,
I: 2019-11-17 05:23:55.513 it is to be used for educational purposes only. Its use on
I: 2019-11-17 05:23:55.513 commercial networks is strictly prohibited.
I: 2019-11-17 05:23:55.513
I: 2019-11-17 05:23:55.513 Analog Bridge is starting
M: 2019-11-17 05:23:55.513 Setting [GENERAL] logLevel -> 2
M: 2019-11-17 05:23:55.513 Setting [GENERAL] subscriberFile -> /var/lib/dvswitch/subscriber_ids.csv
M: 2019-11-17 05:23:55.513 Setting [GENERAL] exportMetadata -> true
M: 2019-11-17 05:23:55.514 Setting [GENERAL] decoderFallBack -> true
M: 2019-11-17 05:23:55.514 Setting [GENERAL] useEmulator -> false
M: 2019-11-17 05:23:55.514 Setting [GENERAL] emulatorAddress -> 127.0.0.1:2470
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] address -> 127.0.0.1
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] txPort -> 31103
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] rxPort -> 31100
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] ambeMode -> DMR
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] minTxTimeMS -> 2500
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] gatewayDmrId -> 3138495
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] repeaterID -> 3154444
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] txTg -> 31679
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] txTs -> 2
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] colorCode -> 1
M: 2019-11-17 05:23:55.514 Setting [USRP] address -> xlx.borris.me
M: 2019-11-17 05:23:55.514 Setting [USRP] txPort -> 32001
M: 2019-11-17 05:23:55.514 Setting [USRP] rxPort -> 34001
M: 2019-11-17 05:23:55.514 Setting [USRP] usrpAudio -> AUDIO_UNITY
M: 2019-11-17 05:23:55.515 Setting [USRP] usrpGain -> 1.10
M: 2019-11-17 05:23:55.515 Setting [USRP] tlvAudio -> AUDIO_UNITY
M: 2019-11-17 05:23:55.515 Setting [USRP] tlvGain -> 0.35
M: 2019-11-17 05:23:55.515 Setting [DV3000] address -> 127.0.0.1
M: 2019-11-17 05:23:55.515 Setting [DV3000] rxPort -> 2460
I: 2019-11-17 05:23:55.515 Open UDP listener on 127.0.0.1:31100
I: 2019-11-17 05:23:55.515 Open USRP on xlx.borris.me:32001
M: 2019-11-17 05:23:55.515 Connecting to DV3000 hardware......
M: 2019-11-17 05:23:55.535 Begin DV3000 decode
I: 2019-11-17 05:23:55.930 Subscriber IDs loaded: 146120
I: 2019-11-17 05:23:55.930 Default extended metadata <KE4DYI>
I: 2019-11-17 05:23:55.931 Using hardware AMBE vocoder
I: 2019-11-17 05:23:55.934 Connected to USRP xlx.borris.me:32001
I: 2019-11-17 05:23:55.935 Starting TLV --> Analog_Bridge (decoder) --> USRP thread
I: 2019-11-17 05:23:55.935 Starting USRP --> Analog_Bridge (encoder) -> TLV thread
I: 2019-11-17 05:24:06.913 Begin TX: src=3138495 rpt=0 dst=31679 slot=2 cc=0 call=KE4DYI
I: 2019-11-17 05:24:39.132 Begin TX: src=3138495 rpt=0 dst=31679 slot=2 cc=0 call=KE4DYI
I: 2019-11-17 05:24:58.271 Signal 2 received, exiting Analog_Bridge

What am I missing here?

Thanks and 73

de

KE4DYI



Re: Analog_Bridge remote control (TLV) commands exposed.

SP2ONG Waldek
 


Ok, thank you for the information


Re: Analog_Bridge, one-way audio from DMR to ASL

Patrick Perdue
 

I forgot to mention that UDP 34001 and 31100 are forwarded through my local NAT to the Pi running DVSwitch.


Analog_Bridge, one-way audio from DMR to ASL

Patrick Perdue
 

Hi:
In moving my DVSwitch to a local Raspberry Pi 4 rather than running it on the VPS, connecting to a remote AMBEserver, I'm running into a problem.

I now have audio going from DMR to USRP, but not the other way. It is bi-directional when running DVSwitch on the VPS.

Looking at the logs for Analog_Bridge, it doesn't appear to get audio from ASL, as there is nothing in the log when there is a transmission from Allstar.


In rpt.conf, I have:

rxchannel = USRP/0.0.0.0:34001:32001; GNU Radio interface USRP

In Analog_Bridge.ini:

[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)
[USRP]
address = xlx.borris.me                     ; IP address of USRP partner (Allstar/Asterisk or another Analog_Bridge)
txPort = 32001                          ; Transmit USRP frames on this port
rxPort = 34001                          ; Listen for USRP frames on this port


In DVSwitch.ini:

[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


Here is a full log from Analog_Bridge. During this period, there were several Allstar transmissions, but they didn't make it to the log. Only DMR is seen.


I: 2019-11-17 05:23:55.512 Analog Bridge Version 1.4.1 Mon Nov 11 19:06:12 UTC 2019
I: 2019-11-17 05:23:55.513 Copyright (C) 2018 DVSwitch, INAD.
I: 2019-11-17 05:23:55.513 Created by Mike N4IRR and Steve N4IRS
I: 2019-11-17 05:23:55.513 Analog Bridge comes with ABSOLUTELY NO WARRANTY
I: 2019-11-17 05:23:55.513
I: 2019-11-17 05:23:55.513 This software is for use on amateur radio networks only,
I: 2019-11-17 05:23:55.513 it is to be used for educational purposes only. Its use on
I: 2019-11-17 05:23:55.513 commercial networks is strictly prohibited.
I: 2019-11-17 05:23:55.513
I: 2019-11-17 05:23:55.513 Analog Bridge is starting
M: 2019-11-17 05:23:55.513 Setting [GENERAL] logLevel -> 2
M: 2019-11-17 05:23:55.513 Setting [GENERAL] subscriberFile -> /var/lib/dvswitch/subscriber_ids.csv
M: 2019-11-17 05:23:55.513 Setting [GENERAL] exportMetadata -> true
M: 2019-11-17 05:23:55.514 Setting [GENERAL] decoderFallBack -> true
M: 2019-11-17 05:23:55.514 Setting [GENERAL] useEmulator -> false
M: 2019-11-17 05:23:55.514 Setting [GENERAL] emulatorAddress -> 127.0.0.1:2470
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] address -> 127.0.0.1
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] txPort -> 31103
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] rxPort -> 31100
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] ambeMode -> DMR
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] minTxTimeMS -> 2500
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] gatewayDmrId -> 3138495
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] repeaterID -> 3154444
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] txTg -> 31679
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] txTs -> 2
M: 2019-11-17 05:23:55.514 Setting [AMBE_AUDIO] colorCode -> 1
M: 2019-11-17 05:23:55.514 Setting [USRP] address -> xlx.borris.me
M: 2019-11-17 05:23:55.514 Setting [USRP] txPort -> 32001
M: 2019-11-17 05:23:55.514 Setting [USRP] rxPort -> 34001
M: 2019-11-17 05:23:55.514 Setting [USRP] usrpAudio -> AUDIO_UNITY
M: 2019-11-17 05:23:55.515 Setting [USRP] usrpGain -> 1.10
M: 2019-11-17 05:23:55.515 Setting [USRP] tlvAudio -> AUDIO_UNITY
M: 2019-11-17 05:23:55.515 Setting [USRP] tlvGain -> 0.35
M: 2019-11-17 05:23:55.515 Setting [DV3000] address -> 127.0.0.1
M: 2019-11-17 05:23:55.515 Setting [DV3000] rxPort -> 2460
I: 2019-11-17 05:23:55.515 Open UDP listener on 127.0.0.1:31100
I: 2019-11-17 05:23:55.515 Open USRP on xlx.borris.me:32001
M: 2019-11-17 05:23:55.515 Connecting to DV3000 hardware......
M: 2019-11-17 05:23:55.535 Begin DV3000 decode
I: 2019-11-17 05:23:55.930 Subscriber IDs loaded: 146120
I: 2019-11-17 05:23:55.930 Default extended metadata <KE4DYI>
I: 2019-11-17 05:23:55.931 Using hardware AMBE vocoder
I: 2019-11-17 05:23:55.934 Connected to USRP xlx.borris.me:32001
I: 2019-11-17 05:23:55.935 Starting TLV --> Analog_Bridge (decoder) --> USRP thread
I: 2019-11-17 05:23:55.935 Starting USRP --> Analog_Bridge (encoder) -> TLV thread
I: 2019-11-17 05:24:06.913 Begin TX: src=3138495 rpt=0 dst=31679 slot=2 cc=0 call=KE4DYI
I: 2019-11-17 05:24:39.132 Begin TX: src=3138495 rpt=0 dst=31679 slot=2 cc=0 call=KE4DYI
I: 2019-11-17 05:24:58.271 Signal 2 received, exiting Analog_Bridge

What am I missing here?

Thanks and 73

de

KE4DYI


Re: Analog_Bridge remote control (TLV) commands exposed.

Mike Zingman - N4IRR
 
Edited

BTW, when AB executes any macro it exports ABINFO so dvswitch.sh can work with the correct ports.


Re: Analog_Bridge remote control (TLV) commands exposed.

Mike Zingman - N4IRR
 

Set the environment variable ABINFO to the filename of the AB you want to control. Each ABINFO file is in /tmp and named based on the port. 
ABINFO=/tmp/xxxx.xxx ./dvswitch.sx Foo
 


Re: Analog_Bridge remote control (TLV) commands exposed.

SP2ONG Waldek
 

Steve

One more question

I use three Analog_Bridge on my server. How to choose Analog_Bridge to use dvswitch.sh on the selected AB, for example, I would like to change tvlAudio gain

73 Waldek


New file uploaded to main@DVSwitch.groups.io

main@DVSwitch.groups.io Notification <main+notification@...>
 

Hello,

This email message is a notification to let you know that the following files have been uploaded to the Files area of the main@DVSwitch.groups.io group.

Uploaded By: Steve N4IRS <szingman@...>

Description:
USRP_Parrot listens on a UDP port for USRP packets. After end of transmission, USRP_Parrot sends those USRP packets out to a UDP port.

Cheers,
The Groups.io Team


Re: Analog_Bridge stops bridging

Steve N4IRS
 

ASL configures the USRP connection in rpt.conf:
In the node stanza

rxchannel = USRP/127.0.0.1:34001:32001; GNU Radio interface USRP



On 11/16/19 3:02 AM, Patrick Perdue wrote:

I have installed/configured DVSwitch on my Raspberry Pi 4 and pointed it at the local AMBEserver and remote USRP, but it seems that traffic isn't passing. Does ASL's USRP driver only listen on localhost by default? If so, where can I change this in ASL?

Otherwise, what did I break?


On 11/15/2019 5:47 PM, Patrick Perdue via Groups.Io wrote:

The power supply is 4A. Temperature is hanging out around 35 degrees C with active cooling.


On 11/15/2019 4:44 PM, Ernie Gm7kbk wrote:
Check your power supply it needs to be 2 amps or greater. Also Pi do not like the heat. Use cooling fan and heatsinks.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Friday, November 15, 2019 8:43:09 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: [DVSwitch] Analog_Bridge stops bridging
 
Hi:

I have Analog_Bridge and MMDVM_Bridge running on a Debian Stretch VPS.
Analog_Bridge is connected to a remote DV3000 dongle hosted on a
Raspberry Pi at my house. Pings between my house and the

server average 3 ms, with higher spikes. The worst I see is 19 ms, but
that's not at all typical.

Sometimes, after Analog_Bridge has been running for some time, traffic
appears to stop bridging. There is no activity in the log indicating
that it is receiving or transmitting between MMDVM_Bridge and USRP. It
just stops, requiring a restart of A_B, which makes everything work again.

Sometimes, it can run like this for a day or two. Other times, it can
fall over in less than an hour.

I haven't figured out a pattern in the logs. At first, I thought it
might be short keys from Allstar, but it often just drops in the middle
of transmission, and it doesn't seem to matter what side of the bridge
is transmitting at the time. I have tried running it in the console and
as a daemon with the same result. Note: I'm using the version of
Analog_Bridge from the repository. Is this a known, fixed issue in the
latest build from github?

This didn't happen when I was using the md380-emu vocoder, as far as I
can remember. I had Analog_Bridge running solidly with no restarts for a
week.

For a while, I had Analog_Bridge restart four times a day on a Cron, but
that wasn't ideal, as it would sometimes break QSOs, and often, it fell
over between restarts, leaving large gaps of time when the bridge didn't
work if I didn't happen to be around. I haven't yet implemented a macro
so anyone can restart the bridge.

Has anyone else experienced this while using a remotely connected
DV3000? Would it be safer to run DVSwitch and the DV3000 locally, and
have it connect to USRP across the internet rather than having
Analog_Bridge connect to my DV3000 that way?






Re: Analog_Bridge stops bridging

Patrick Perdue
 

Here is a full log. There are no entries when transmissions occur from either side of the bridge.

I could use the IP address rather than DNS for the remote machine, but I know from experience that DNS works, as I am currently using it to connect Analog_Bridge from the VPS to my remote AMBEserver in a somewhat working configuration.


I: 2019-11-16 10:03:22.605 Analog Bridge Version 1.4.1 Mon Nov 11 19:06:12 UTC 2019
I: 2019-11-16 10:03:22.605 Copyright (C) 2018 DVSwitch, INAD.
I: 2019-11-16 10:03:22.605 Created by Mike N4IRR and Steve N4IRS
I: 2019-11-16 10:03:22.605 Analog Bridge comes with ABSOLUTELY NO WARRANTY
I: 2019-11-16 10:03:22.605
I: 2019-11-16 10:03:22.605 This software is for use on amateur radio networks only,
I: 2019-11-16 10:03:22.605 it is to be used for educational purposes only. Its use on
I: 2019-11-16 10:03:22.605 commercial networks is strictly prohibited.
I: 2019-11-16 10:03:22.605
I: 2019-11-16 10:03:22.606 Analog Bridge is starting
M: 2019-11-16 10:03:22.606 Setting [GENERAL] logLevel -> 2
M: 2019-11-16 10:03:22.606 Setting [GENERAL] subscriberFile -> /var/lib/dvswitch/subscriber_ids.csv
M: 2019-11-16 10:03:22.606 Setting [GENERAL] exportMetadata -> true
M: 2019-11-16 10:03:22.606 Setting [GENERAL] decoderFallBack -> true
M: 2019-11-16 10:03:22.606 Setting [GENERAL] useEmulator -> false
M: 2019-11-16 10:03:22.606 Setting [GENERAL] emulatorAddress -> 127.0.0.1:2470
M: 2019-11-16 10:03:22.606 Setting [AMBE_AUDIO] address -> xlx.borris.me
M: 2019-11-16 10:03:22.606 Setting [AMBE_AUDIO] txPort -> 31103
M: 2019-11-16 10:03:22.606 Setting [AMBE_AUDIO] rxPort -> 31100
M: 2019-11-16 10:03:22.606 Setting [AMBE_AUDIO] ambeMode -> DMR
M: 2019-11-16 10:03:22.607 Setting [AMBE_AUDIO] minTxTimeMS -> 2500
M: 2019-11-16 10:03:22.607 Setting [AMBE_AUDIO] gatewayDmrId -> 3138495
M: 2019-11-16 10:03:22.607 Setting [AMBE_AUDIO] repeaterID -> 3154444
M: 2019-11-16 10:03:22.607 Setting [AMBE_AUDIO] txTg -> 31679
M: 2019-11-16 10:03:22.607 Setting [AMBE_AUDIO] txTs -> 2
M: 2019-11-16 10:03:22.607 Setting [AMBE_AUDIO] colorCode -> 1
M: 2019-11-16 10:03:22.607 Setting [USRP] address -> xlx.borris.me
M: 2019-11-16 10:03:22.607 Setting [USRP] txPort -> 32001
M: 2019-11-16 10:03:22.607 Setting [USRP] rxPort -> 34001
M: 2019-11-16 10:03:22.607 Setting [USRP] usrpAudio -> AUDIO_UNITY
M: 2019-11-16 10:03:22.607 Setting [USRP] usrpGain -> 1.10
M: 2019-11-16 10:03:22.607 Setting [USRP] tlvAudio -> AUDIO_USE_BPF
M: 2019-11-16 10:03:22.607 Setting [USRP] tlvGain -> 0.20
M: 2019-11-16 10:03:22.607 Setting [DV3000] address -> 127.0.0.1
M: 2019-11-16 10:03:22.607 Setting [DV3000] rxPort -> 2460
I: 2019-11-16 10:03:22.607 Open UDP listener on xlx.borris.me:31100
I: 2019-11-16 10:03:22.607 Open USRP on xlx.borris.me:32001
M: 2019-11-16 10:03:22.608 Connecting to DV3000 hardware......
M: 2019-11-16 10:03:22.628 Begin DV3000 decode
I: 2019-11-16 10:03:22.981 Subscriber IDs loaded: 146118
I: 2019-11-16 10:03:22.981 Default extended metadata <KE4DYI>
I: 2019-11-16 10:03:22.981 Using hardware AMBE vocoder
I: 2019-11-16 10:03:22.983 Connected to USRP xlx.borris.me:32001
I: 2019-11-16 10:03:22.984 Starting USRP --> Analog_Bridge (encoder) -> TLV thread
I: 2019-11-16 10:03:22.984 Starting TLV --> Analog_Bridge (decoder) --> USRP thread
I: 2019-11-16 10:03:28.692 Signal 2 received, exiting Analog_Bridge

11/16/2019 3:44 AM, Peter M0NWI wrote:

Patrick,

You'll need to give people a little more to go on.  Can you post your config text files, and the output log from when you are trying to transmit?

Most of these type of issues seem to be around IP addresses or ports not being lined up through the pipeline of voice bridges, and packets dropping off the end.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: 16 November 2019 08:02:52
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Analog_Bridge stops bridging
 

I have installed/configured DVSwitch on my Raspberry Pi 4 and pointed it at the local AMBEserver and remote USRP, but it seems that traffic isn't passing. Does ASL's USRP driver only listen on localhost by default? If so, where can I change this in ASL?

Otherwise, what did I break?


On 11/15/2019 5:47 PM, Patrick Perdue via Groups.Io wrote:

The power supply is 4A. Temperature is hanging out around 35 degrees C with active cooling.


On 11/15/2019 4:44 PM, Ernie Gm7kbk wrote:
Check your power supply it needs to be 2 amps or greater. Also Pi do not like the heat. Use cooling fan and heatsinks.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Friday, November 15, 2019 8:43:09 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: [DVSwitch] Analog_Bridge stops bridging
 
Hi:

I have Analog_Bridge and MMDVM_Bridge running on a Debian Stretch VPS.
Analog_Bridge is connected to a remote DV3000 dongle hosted on a
Raspberry Pi at my house. Pings between my house and the

server average 3 ms, with higher spikes. The worst I see is 19 ms, but
that's not at all typical.

Sometimes, after Analog_Bridge has been running for some time, traffic
appears to stop bridging. There is no activity in the log indicating
that it is receiving or transmitting between MMDVM_Bridge and USRP. It
just stops, requiring a restart of A_B, which makes everything work again.

Sometimes, it can run like this for a day or two. Other times, it can
fall over in less than an hour.

I haven't figured out a pattern in the logs. At first, I thought it
might be short keys from Allstar, but it often just drops in the middle
of transmission, and it doesn't seem to matter what side of the bridge
is transmitting at the time. I have tried running it in the console and
as a daemon with the same result. Note: I'm using the version of
Analog_Bridge from the repository. Is this a known, fixed issue in the
latest build from github?

This didn't happen when I was using the md380-emu vocoder, as far as I
can remember. I had Analog_Bridge running solidly with no restarts for a
week.

For a while, I had Analog_Bridge restart four times a day on a Cron, but
that wasn't ideal, as it would sometimes break QSOs, and often, it fell
over between restarts, leaving large gaps of time when the bridge didn't
work if I didn't happen to be around. I haven't yet implemented a macro
so anyone can restart the bridge.

Has anyone else experienced this while using a remotely connected
DV3000? Would it be safer to run DVSwitch and the DV3000 locally, and
have it connect to USRP across the internet rather than having
Analog_Bridge connect to my DV3000 that way?




3861 - 3880 of 9087