Date   

Re: Setting up a YSFn <--> ASL bridge

Doug - W4DBG
 

Your Gateway address and port need to be


On Mon, Jun 10, 2019 at 5:52 AM Tom Corcoran <tcorcoran@...> wrote:
All,

I have tried to follow the logic of setting up this instance in the cloud but not having any luck. I have a working ASL<=>DMR bridge. The following are my MMDVM_Bridge.ini, Analog_Bridge.ini and DVSwitch.ini files. In my example, I am trying to reach YSF 77353. Any suggestions??
--
Tom VE3NY

*** MMDVM_Bridge.ini

[System Fusion]
Enable=1

[System Fusion Network]
Enable=1
LocalAddress=0
LocalPort=3200
GatewayAddress=96.47.95.121   ;ysfreflector.dvswitch.org
GatewayPort=42001
Debug=0

*** Analog_Bridge.ini

[AMBE_AUDIO]
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 31103                ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31100                       ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = YSFN                         ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2000                      ; Minimum time in MS for hang delay
gatewayDmrId = 3023284                  ; ID to use when transmitting from Analog_Bridge
repeaterID = 302328401                  ; ID of source repeater
txTg = 77353                            ; TG to use for all frames received from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames received 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 toASLPort equal to the other instance fromASLPort (crossover)
[USRP]
server = 127.0.0.1                      ; IP address of Allstar/Asterisk
toASLPort = 32001                       ; Analog_Bridge <-- ASL
fromASLPort = 34001                     ; Analog_Bridge --> ASL
aslAudio = AUDIO_USE_Gain               ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
agcGain = 3                             ; Gain (in db) of the AGC filter
dmrAudio = AUDIO_USE_GAIN               ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.25                          ; Gain factor of audio from ASL (0.0-1.0)

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



--
Doug Gooden
troytrojan@...


Re: Setting up a YSFn <--> ASL bridge

Tom Corcoran
 

All,

I have tried to follow the logic of setting up this instance in the cloud but not having any luck. I have a working ASL<=>DMR bridge. The following are my MMDVM_Bridge.ini, Analog_Bridge.ini and DVSwitch.ini files. In my example, I am trying to reach YSF 77353. Any suggestions??
--
Tom VE3NY

*** MMDVM_Bridge.ini

[System Fusion]
Enable=1

[System Fusion Network]
Enable=1
LocalAddress=0
LocalPort=3200
GatewayAddress=96.47.95.121   ;ysfreflector.dvswitch.org
GatewayPort=42001
Debug=0

*** Analog_Bridge.ini

[AMBE_AUDIO]
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 31103                ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31100                       ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = YSFN                         ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2000                      ; Minimum time in MS for hang delay
gatewayDmrId = 3023284                  ; ID to use when transmitting from Analog_Bridge
repeaterID = 302328401                  ; ID of source repeater
txTg = 77353                            ; TG to use for all frames received from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames received 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 toASLPort equal to the other instance fromASLPort (crossover)
[USRP]
server = 127.0.0.1                      ; IP address of Allstar/Asterisk
toASLPort = 32001                       ; Analog_Bridge <-- ASL
fromASLPort = 34001                     ; Analog_Bridge --> ASL
aslAudio = AUDIO_USE_Gain               ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
agcGain = 3                             ; Gain (in db) of the AGC filter
dmrAudio = AUDIO_USE_GAIN               ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.25                          ; Gain factor of audio from ASL (0.0-1.0)

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


Re: New Moderator

Doug - W4DBG
 

Steve is an excellent resource and does a great job explaining things. You have a good one. 

73,

Doug
W4DBG 



On Sat, Jun 8, 2019 at 7:54 PM Steve KC1AWV <smiller@...> wrote:
Thank you Steve and Mike! I will continue to do my best helping out here.

Some information about me, for those that are interested:

By day, I am the Sr. Systems Administrator for a national non-profit organization. Most of my duties involve maintaining a few hundred servers, many networks, all the way down to the staff level of about 550 users. Been doing that job for about 11 years now (wow!)
My amateur radio activities include ARES, digital networks, and experimenting with new modes of communication using amateur radio. I am also the system administrator for ERDN.net - the East Rockingham Digital Net - which provides digital network capabilities for East Rockingham ARES, in New Hampshire

I will try to provide support here in the group as best I can. During the day, I do monitor the DVSwitch group, and I read all the messages coming in. If you have questions, feel free to ask!

73 de Steve KC1AWV

--
Doug Gooden
troytrojan@...


Re: New Moderator

Steve KC1AWV
 

Thank you Steve and Mike! I will continue to do my best helping out here.

Some information about me, for those that are interested:

By day, I am the Sr. Systems Administrator for a national non-profit organization. Most of my duties involve maintaining a few hundred servers, many networks, all the way down to the staff level of about 550 users. Been doing that job for about 11 years now (wow!)
My amateur radio activities include ARES, digital networks, and experimenting with new modes of communication using amateur radio. I am also the system administrator for ERDN.net - the East Rockingham Digital Net - which provides digital network capabilities for East Rockingham ARES, in New Hampshire

I will try to provide support here in the group as best I can. During the day, I do monitor the DVSwitch group, and I read all the messages coming in. If you have questions, feel free to ask!

73 de Steve KC1AWV


New Moderator

Steve N4IRS
 

We have asked Steve, KC1AWV to help us out by taking on moderation duties here on groups.io Steve has been a great help to quite a few of you as he has answered you questions and helped you build what you need with the DVSwitch programs.

73, Steve N4IRS 


DVSwitch programs

Steve N4IRS
 

Now that Hamvention is over and we have had a chance to digest the comments and discussions about the DVSwitch programs. To be clear I mean Analog_Bridge, MMDVM_Bridge and Mobile.
Over the next 6 months we are going to implement a feature freeze on all of the programs. During this period we will be fixing the bugs we know about and any that show up. We  will also work on documentation and howto documents. We want to put some polish on the DVSwitch family.

Along with the bug fixes we will publish a list of "enhancements" we want to add to each programs. The idea here is to put together a coherent list of what should be in the next revision of each of the programs. By creating a list BEFORE the work starts, we hope to streamline the work needed.

For all of the above to happen we need your help. Once we publish the basic list, we welcome comments on the features we missed. This is not to say every idea will be implemented. As I tell teams that have worked for me in the past, "Bring your ideas to the table, and be prepared to defend them"  If you can write documentation, PLEASE do so. We need content for the wiki. It can be a FAQ, a howto, a detailed writeup. If you already have written up something, please publish it on the Wiki. Having info all over the web does no one any good when we have a good place to right here to point people to. All authors will be acknowledged and their work will remain their property.

I expect some other changes coming. All designed to make it easier for people to use the DVSwitch programs.

73, Steve and Mike


Re: Github update

Steve N4IRS
 

You can just replace the executable. Backup the old one first. There will be more updates next week.

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of EA5GVK Joaquin <ea5gvk@...>
Sent: Saturday, June 8, 2019 11:02:42 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Github update
 
Congratulations Steve.
How to update Analog_Bridge and MMDVM_Bridge of our server, which is working?
Many thx.


Re: Github update

Carlos Minguela
 
Edited

Good question of Joaquin.  Do we have to make a fresh new install or it will be a update file?  KP4CA.


Re: Github update

EA5GVK Joaquin
 

Congratulations Steve.
How to update Analog_Bridge and MMDVM_Bridge of our server, which is working?
Many thx.


Re: different streams with mmdvm_bridge...

Heiko DL1BZ
 

hmm, here I use hblink3 too - no ambe_bridge.py exist. In hblink there isn't such ambe_bridge.py too.

73 Heiko, DL1BZ


Re: different streams with mmdvm_bridge...

SP2ONG Waldek
 

Hi Mike,

I don't use HB Bridge. I have use only HBLink3 and in HBLink3 don't exist ambe_bridge.py

https://github.com/n0mjs710/hblink3


Re: different streams with mmdvm_bridge...

Mike Zingman - N4IRR
 

I do not think it is MB, but HB Bridge.  Try to change line 540 in ambe_bridge.py.  Change the 3 to a 1


Re: different streams with mmdvm_bridge...

Chris WB4ULK
 

Phew! I thought I was the only one. Must be normal, as my asl analog bridge does the same thing.
I was waiting to see if anyone else posted. Everything works, but it makes those and I was wondering if I screwed up.

Chris


Re: different streams with mmdvm_bridge...

SP2ONG Waldek
 

Hi,

I confirm the Heiko report.  I have the same "problem" on my on my HBlink with MMDVM_Bridge to YSF reflector. I use the version MMDVM_Bidge i386 which was available before the update MMDVM_Bridge

73 Waldek SP2ONG


different streams with mmdvm_bridge...

Heiko DL1BZ
 

I have a mmdvm_bridge YSF-reflector on one side and hblink on other side. If there is a call initiated (from YSF), there were build more than one stream with different stream_ids:

INFO 2019-06-07 12:20:12,943 (YSF-REF-PEG) *CALL START* STREAM ID: 1750720806 SUB: DM2DK (2629370) PEER: DB0PIB (262929) TGID 70000 (70000), TS 2
DEBUG 2019-06-07 12:20:12,945 (YSF-REF-PEG) Generating TX FULL and EMB LCs for HomeBrew destination: System: DMR-OL-LOKAL, TS: 1, TGID: 70000
INFO 2019-06-07 12:20:12,945 (YSF-REF-PEG) Conference Bridge: LOKAL:TS1#TG70000<->YSF-PEG, Call Bridged to HBP System: DMR-OL-LOKAL TS: 1, TGID: 70000
INFO 2019-06-07 12:20:12,946 (YSF-REF-PEG) *CALL START* STREAM ID: 585735029 SUB: DM2DK (2629370) PEER: DB0PIB (262929) TGID 70000 (70000), TS 2
DEBUG 2019-06-07 12:20:12,947 (YSF-REF-PEG) Generating TX FULL and EMB LCs for HomeBrew destination: System: DMR-OL-LOKAL, TS: 1, TGID: 70000
INFO 2019-06-07 12:20:12,947 (YSF-REF-PEG) Conference Bridge: LOKAL:TS1#TG70000<->YSF-PEG, Call Bridged to HBP System: DMR-OL-LOKAL TS: 1, TGID: 70000
INFO 2019-06-07 12:20:12,948 (YSF-REF-PEG) *CALL START* STREAM ID: 2379084806 SUB: DM2DK (2629370) PEER: DB0PIB (262929) TGID 70000 (70000), TS 2
DEBUG 2019-06-07 12:20:12,950 (YSF-REF-PEG) Generating TX FULL and EMB LCs for HomeBrew destination: System: DMR-OL-LOKAL, TS: 1, TGID: 70000
INFO 2019-06-07 12:20:12,950 (YSF-REF-PEG) Conference Bridge: LOKAL:TS1#TG70000<->YSF-PEG, Call Bridged to HBP System: DMR-OL-LOKAL TS: 1, TGID: 70000

With input only DMR I cannot see this effect. Is it a problem with mmdvm_bridge (I use the newest version) ? If the call ends only one stream was closed.

73 Heiko, DL1BZ


Re: Help with HBlink and Bridge Groups

Carlos Minguela
 

Sorry, I thought that changing the starting file was gonna work but dont.  Here is the screen.  


Re: Help with HBlink and Bridge Groups

Carlos Minguela
 

Thank you.  That is the file that I have to hit.  Thanks!!!!


Re: Help with HBlink and Bridge Groups

Cort N0MJS <n0mjs@...>
 

because the program you need to run for bridging is bridge.py. hblink.py is like a protocol stack. It doesn’t really do much on its own.

On Jun 5, 2019, at 8:35 PM, Carlos Minguela via Groups.Io <minguela@...> wrote:

Hello:

I am trying to configure HBlink for the first time.  Everything is all set and running without Warnings in the log but I noticed that in the log I do not see that the Bridges are made.  I have configured the hb_confbridge_rules.py and everything.  But when the programs start I do not see the TG in the logs.  Attached here is the files and a photo of the log. 

If anybody know how to solve this thanks for your help. <2019-06-05_2124.png><hb_confbridge_rules.py><hblink.cfg>

--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206






Re: Help with HBlink and Bridge Groups

Steve KC1AWV
 

I'm running mobile, so I can't read the config files, but... 

Try running hb_bridge_all.py and see if it works then.

Remember, HBlink is no longer getting support, so you should look at HBlink3 since that's under current development.

Steve KC1AWV

On Wed, Jun 5, 2019, 9:35 PM Carlos Minguela via Groups.Io <minguela=yahoo.com@groups.io> wrote:
Hello:

I am trying to configure HBlink for the first time.  Everything is all set and running without Warnings in the log but I noticed that in the log I do not see that the Bridges are made.  I have configured the hb_confbridge_rules.py and everything.  But when the programs start I do not see the TG in the logs.  Attached here is the files and a photo of the log. 

If anybody know how to solve this thanks for your help.


Help with HBlink and Bridge Groups

Carlos Minguela
 

Hello:

I am trying to configure HBlink for the first time.  Everything is all set and running without Warnings in the log but I noticed that in the log I do not see that the Bridges are made.  I have configured the hb_confbridge_rules.py and everything.  But when the programs start I do not see the TG in the logs.  Attached here is the files and a photo of the log. 

If anybody know how to solve this thanks for your help.

5581 - 5600 of 9595