Date   

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

Patrick Perdue
 

Mike:

I'll probably end up implementing another instance of ASL, but testing that once it's available is easier in the short-term. So, I'll do that, too.


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

Mike Zingman - N4IRR
 

Partick,

I just wanted to say thank you!  I decided to go back and inspect the code for UDP encode and decode to a remote AMBE server.  What I found was that there was an error in the logic that was causing your AB to stop listening for new packets from the remote server.  I have fixed that error and when Steve releases a new build to github, I would love for you to re-test and verify that you no longer have to stop and start your AB instance on regular intervals.

However, the architecture that Steve pointed you at will also work and you may want to implement that anyway.  Your call.

Again, thank you!
Mike N4IRR


Re: I have asl setup in the cloud using debian. Just want to make sure i use the right MMDVM, i think should be using the amd64 hope this is correct before I download.thank you.

Steve N4IRS
 

Debian 8, 9 or 10 should be fine. Let me know of problems so I can test and fix.

Steve

On 11/18/2019 10:48 AM, Tom Corcoran wrote:

Hello Charles,

what modes are using? I have DMR, YSF & P25 up but not luck with NXDN or DStar yet  

Also, I found Debian 9 seemed to be the only version that worked. Your experience?
--
Tom VE3NY



Re: I have asl setup in the cloud using debian. Just want to make sure i use the right MMDVM, i think should be using the amd64 hope this is correct before I download.thank you.

Tom Corcoran
 

Hello Charles,

what modes are using? I have DMR, YSF & P25 up but not luck with NXDN or DStar yet  

Also, I found Debian 9 seemed to be the only version that worked. Your experience?
--
Tom VE3NY


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

Patrick Perdue
 

Sounds reasonable. As I am moving soon, I'll set up an identical private node with a second AMBE dongle in another location, then just switch to that for the duration of downtime.


On 11/17/2019 8:09 PM, Steve N4IRS wrote:
I'm going to suggest a alternative configuration.
Put your public ASL node on your VPS No radio interface needed. Setup a private node at your house. Add AB, MB etc. Setup a full time IAX connection between the 2 nodes.
Done...
 

On 11/17/19 7:43 PM, Mike Zingman - N4IRR wrote:
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: I have asl setup in the cloud using debian. Just want to make sure i use the right MMDVM, i think should be using the amd64 hope this is correct before I download.thank you.

Charles Wiant
 

Thank you


On Nov 17, 2019, at 10:08 PM, Steve N4IRS <szingman@...> wrote:


Yes amd64 is correct.

Sent via smoke signal (AT&T)

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Charles Wiant via Groups.Io <kd8itc@...>
Sent: Sunday, November 17, 2019 10:50:20 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] I have asl setup in the cloud using debian. Just want to make sure i use the right MMDVM, i think should be using the amd64 hope this is correct before I download.thank you.
 

4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u6 (2018-10-08) x86_64 GNU    sorry it has taken so long to get back to you for work has been in the way .thank you for your patience.

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Steve N4IRS
Sent: Monday, November 11, 2019 6:44 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] I have asl setup in the cloud using debian. Just want to make sure i use the right MMDVM, i think should be using the amd64 hope this is correct before I download.thank you.

 

What is the result of uname -a


Re: I have asl setup in the cloud using debian. Just want to make sure i use the right MMDVM, i think should be using the amd64 hope this is correct before I download.thank you.

Steve N4IRS
 

Yes amd64 is correct.

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Charles Wiant via Groups.Io <kd8itc@...>
Sent: Sunday, November 17, 2019 10:50:20 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] I have asl setup in the cloud using debian. Just want to make sure i use the right MMDVM, i think should be using the amd64 hope this is correct before I download.thank you.
 

4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u6 (2018-10-08) x86_64 GNU    sorry it has taken so long to get back to you for work has been in the way .thank you for your patience.

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Steve N4IRS
Sent: Monday, November 11, 2019 6:44 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] I have asl setup in the cloud using debian. Just want to make sure i use the right MMDVM, i think should be using the amd64 hope this is correct before I download.thank you.

 

What is the result of uname -a


Re: I have asl setup in the cloud using debian. Just want to make sure i use the right MMDVM, i think should be using the amd64 hope this is correct before I download.thank you.

Charles Wiant
 

4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u6 (2018-10-08) x86_64 GNU    sorry it has taken so long to get back to you for work has been in the way .thank you for your patience.

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Steve N4IRS
Sent: Monday, November 11, 2019 6:44 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] I have asl setup in the cloud using debian. Just want to make sure i use the right MMDVM, i think should be using the amd64 hope this is correct before I download.thank you.

 

What is the result of uname -a


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

Steve N4IRS
 

I'm going to suggest a alternative configuration.
Put your public ASL node on your VPS No radio interface needed. Setup a private node at your house. Add AB, MB etc. Setup a full time IAX connection between the 2 nodes.
Done...
 

On 11/17/19 7:43 PM, Mike Zingman - N4IRR wrote:
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: 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


3861 - 3880 of 9096