Hi there -- Dan ve4drk from Winnipeg here.

(warning - long email - two logs)

I've been going through Steve's document on the Analog to DMR config and am almost there.  Great/easy write-up too.
Initially, when I did the update, I had one error which apparently was corrected by running the script again.
It had an error on dvswitch-base - but after attempt #2, it went through apparently ok.

(log of the script is as such:
---------------------------------------------------------------------------------------------------

root@aslhub:/etc/asterisk# apt-get install dvswitch -y

Reading package lists... Done

Building dependency tree

Reading state information... Done

The following additional packages will be installed:

  analog-bridge binfmt-support dvswitch-base md380-emu mmdvm-bridge qemu-user-static

The following NEW packages will be installed:

  analog-bridge binfmt-support dvswitch dvswitch-base md380-emu mmdvm-bridge qemu-user-static

0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.

Need to get 12.6 MB of archives.

After this operation, 90.5 MB of additional disk space will be used.

Get:1 http://http.us.debian.org/debian stretch/main amd64 binfmt-support amd64 2.1.6-2 [59.5 kB]

Get:2 http://dvswitch.org/ASL_Repository stretch/hamradio amd64 dvswitch-base all 1.01-20180420-9 [1,623 kB]

Get:3 http://http.us.debian.org/debian stretch/main amd64 qemu-user-static amd64 1:2.8+dfsg-6+deb9u4 [8,985 kB]

Get:4 http://dvswitch.org/ASL_Repository stretch/hamradio amd64 analog-bridge amd64 1.1-20180424-11 [155 kB]

Get:5 http://dvswitch.org/ASL_Repository stretch/hamradio amd64 dvswitch all 1.01-20180420-3 [2,144 B]

Get:6 http://dvswitch.org/ASL_Repository stretch/hamradio amd64 md380-emu amd64 1.1-20180424-5 [687 kB]

Get:7 http://dvswitch.org/ASL_Repository stretch/hamradio amd64 mmdvm-bridge amd64 1.1-20180424-5 [1,055 kB]

Fetched 12.6 MB in 3s (3,611 kB/s)

Selecting previously unselected package dvswitch-base.

(Reading database ... 58727 files and directories currently installed.)

Preparing to unpack .../0-dvswitch-base_1.01-20180420-9_all.deb ...

Unpacking dvswitch-base (1.01-20180420-9) ...

Selecting previously unselected package analog-bridge.

Preparing to unpack .../1-analog-bridge_1.1-20180424-11_amd64.deb ...

Unpacking analog-bridge (1.1-20180424-11) ...

Selecting previously unselected package binfmt-support.

Preparing to unpack .../2-binfmt-support_2.1.6-2_amd64.deb ...

Unpacking binfmt-support (2.1.6-2) ...

Selecting previously unselected package dvswitch.

Preparing to unpack .../3-dvswitch_1.01-20180420-3_all.deb ...

Unpacking dvswitch (1.01-20180420-3) ...

Selecting previously unselected package qemu-user-static.

Preparing to unpack .../4-qemu-user-static_1%3a2.8+dfsg-6+deb9u4_amd64.deb ...

Unpacking qemu-user-static (1:2.8+dfsg-6+deb9u4) ...

Selecting previously unselected package md380-emu.

Preparing to unpack .../5-md380-emu_1.1-20180424-5_amd64.deb ...

Unpacking md380-emu (1.1-20180424-5) ...

Selecting previously unselected package mmdvm-bridge.

Preparing to unpack .../6-mmdvm-bridge_1.1-20180424-5_amd64.deb ...

Unpacking mmdvm-bridge (1.1-20180424-5) ...

Setting up binfmt-support (2.1.6-2) ...

Created symlink /etc/systemd/system/multi-user.target.wants/binfmt-support.service → /lib/systemd/system/binfmt-support.service.

Setting up dvswitch-base (1.01-20180420-9) ...

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

100 21230    0 21230    0     0  18773      0 --:--:--  0:00:01 --:--:-- 18787

dpkg: error processing package dvswitch-base (--configure):

 subprocess installed post-installation script returned error exit status 4

dpkg: dependency problems prevent configuration of mmdvm-bridge:

 mmdvm-bridge depends on dvswitch-base; however:

  Package dvswitch-base is not configured yet.

 

dpkg: error processing package mmdvm-bridge (--configure):

 dependency problems - leaving unconfigured

Setting up dvswitch (1.01-20180420-3) ...

dpkg: dependency problems prevent configuration of analog-bridge:

 analog-bridge depends on dvswitch-base; however:

  Package dvswitch-base is not configured yet.

 

dpkg: error processing package analog-bridge (--configure):

 dependency problems - leaving unconfigured

Processing triggers for systemd (232-25+deb9u4) ...

Setting up qemu-user-static (1:2.8+dfsg-6+deb9u4) ...

Processing triggers for man-db (2.7.6.1-2) ...

Setting up md380-emu (1.1-20180424-5) ...

Created symlink /etc/systemd/system/multi-user.target.wants/md380-emu.service → /lib/systemd/system/md380-emu.service.

Errors were encountered while processing:

 dvswitch-base

 mmdvm-bridge

 analog-bridge

E: Sub-process /usr/bin/dpkg returned an error code (1)

root@aslhub:/etc/asterisk# apt-get install dvswitch -y

Reading package lists... Done

Building dependency tree

Reading state information... Done

dvswitch is already the newest version (1.01-20180420-3).

0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

3 not fully installed or removed.

After this operation, 0 B of additional disk space will be used.

Setting up dvswitch-base (1.01-20180420-9) ...

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

100 21230    0 21230    0     0  13448      0 --:--:--  0:00:01 --:--:-- 13445

Updating /var/lib/mmdvm/XLXHosts.txt ...

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

100  7004  100  7004    0     0   3970      0  0:00:01  0:00:01 --:--:--  3970

Created symlink /etc/systemd/system/network-online.target.wants/systemd-networkd-wait-online.service → /lib/systemd/system/systemd-networkd-wait-online.service.

Created symlink /etc/systemd/system/multi-user.target.wants/netcheck.service → /lib/systemd/system/netcheck.service.

Setting up mmdvm-bridge (1.1-20180424-5) ...

Created symlink /etc/systemd/system/multi-user.target.wants/mmdvm_bridge.service → /lib/systemd/system/mmdvm_bridge.service.

Setting up analog-bridge (1.1-20180424-11) ...

Created symlink /etc/systemd/system/multi-user.target.wants/analog_bridge.service → /lib/systemd/system/analog_bridge.service.

W: APT had planned for dpkg to do more than it reported back (6 vs 10).

   Affected packages: dvswitch-base:amd64
---------------------------------------------------------------------------------------



After that, all was fine for quite some time and all the tests were good until I got to page 10 of the instructions and attempted to run ./MMDVM_Bridge MMDVMBridge.ini
had an error with credentials.
I did find the IP address of the local (Canada) brandmeister server. (we apparently only have one for this country).
I did confirm my password was set properly, yet I get the following:

root@aslhub:/opt/MMDVM_Bridge# ./MMDVM_Bridge MMDVM_Bridge.ini

I: 2018-09-26 21:24:59.240 MMDVM_Bridge:

I: 2018-09-26 21:24:59.240 Portions Copyright (C) 2018 DVSwitch, INAD.

I: 2018-09-26 21:24:59.240 Hacks by Mike N4IRR and Steve N4IRS

I: 2018-09-26 21:24:59.241 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

I: 2018-09-26 21:24:59.245 This software is for use on amateur radio networks only,

I: 2018-09-26 21:24:59.245 it is to be used for educational purposes only. Its use on

I: 2018-09-26 21:24:59.245 commercial networks is strictly prohibited.

I: 2018-09-26 21:24:59.245 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others

M: 2018-09-26 21:24:59.245 MMDVM_Bridge-20180423 is starting

M: 2018-09-26 21:24:59.245 Built 15:47:01 May 30 2018 (GitID #9cdea41)

I: 2018-09-26 21:24:59.245 General Parameters

I: 2018-09-26 21:24:59.245     Callsign: VE4DRK

I: 2018-09-26 21:24:59.245     Id: 302401901

I: 2018-09-26 21:24:59.246     Duplex: no

I: 2018-09-26 21:24:59.246     Timeout: 180s

I: 2018-09-26 21:24:59.246     D-Star: disabled

I: 2018-09-26 21:24:59.246     DMR: enabled

I: 2018-09-26 21:24:59.246     YSF: disabled

I: 2018-09-26 21:24:59.246     P25: disabled

I: 2018-09-26 21:24:59.246     NXDN: disabled

I: 2018-09-26 21:24:59.246 Modem Parameters

I: 2018-09-26 21:24:59.246     Port: /dev/null

I: 2018-09-26 21:24:59.246     RX Invert: no

I: 2018-09-26 21:24:59.247     TX Invert: no

I: 2018-09-26 21:24:59.247     PTT Invert: no

I: 2018-09-26 21:24:59.247     TX Delay: 100ms

I: 2018-09-26 21:24:59.247     RX Offset: 0Hz

I: 2018-09-26 21:24:59.247     TX Offset: 0Hz

I: 2018-09-26 21:24:59.247     RX DC Offset: 0

I: 2018-09-26 21:24:59.247     TX DC Offset: 0

I: 2018-09-26 21:24:59.247     RF Level: 100.0%

I: 2018-09-26 21:24:59.247     DMR Delay: 0 (0.0ms)

I: 2018-09-26 21:24:59.247     RX Level: 50.0%

I: 2018-09-26 21:24:59.247     CW Id TX Level: 50.0%

I: 2018-09-26 21:24:59.247     D-Star TX Level: 50.0%

I: 2018-09-26 21:24:59.247     DMR TX Level: 50.0%

I: 2018-09-26 21:24:59.247     YSF TX Level: 50.0%

I: 2018-09-26 21:24:59.247     P25 TX Level: 50.0%

I: 2018-09-26 21:24:59.247     NXDN TX Level: 50.0%

I: 2018-09-26 21:24:59.247     RX Frequency: 146475000Hz (146475000Hz)

I: 2018-09-26 21:24:59.247     TX Frequency: 146475000Hz (146475000Hz)

M: 2018-09-26 21:24:59.248 Opening the MMDVM

I: 2018-09-26 21:24:59.248 Display Parameters

I: 2018-09-26 21:24:59.248     Type:

I: 2018-09-26 21:24:59.248 DMR Network Parameters

I: 2018-09-26 21:24:59.248     Address: 158.69.203.89

I: 2018-09-26 21:24:59.248     Port: 62031

I: 2018-09-26 21:24:59.248     Local: 62032

I: 2018-09-26 21:24:59.248     Jitter: 360ms

I: 2018-09-26 21:24:59.248     Slot 1: disabled

I: 2018-09-26 21:24:59.248     Slot 2: enabled

I: 2018-09-26 21:24:59.248     Mode Hang: 3s

I: 2018-09-26 21:24:59.249 Info Parameters

I: 2018-09-26 21:24:59.249     Callsign: VE4DRK

I: 2018-09-26 21:24:59.249     RX Frequency: 146475000Hz

I: 2018-09-26 21:24:59.249     TX Frequency: 146475000Hz

I: 2018-09-26 21:24:59.249     Power: 1W

I: 2018-09-26 21:24:59.249     Latitude: 49.836800deg N

I: 2018-09-26 21:24:59.249     Longitude: -97.078140deg E

I: 2018-09-26 21:24:59.250     Height: 0m

I: 2018-09-26 21:24:59.250     Location: "Winnipeg, MB (EN19lu)"

I: 2018-09-26 21:24:59.250     Description: "MMDVM_Bridge"

I: 2018-09-26 21:24:59.250     URL: "https://groups.io/g/DVSwitch"

M: 2018-09-26 21:24:59.250 DMR, Opening DMR Network

I: 2018-09-26 21:24:59.250 RSSI

I: 2018-09-26 21:24:59.250     Mapping File: RSSI.dat

W: 2018-09-26 21:24:59.250 Cannot open the RSSI data file - RSSI.dat

I: 2018-09-26 21:24:59.250 DMR Id Lookups

I: 2018-09-26 21:24:59.250     File: /var/lib/mmdvm/DMRIds.dat

I: 2018-09-26 21:24:59.250     Reload: 24 hours

I: 2018-09-26 21:24:59.431 Loaded 111282 Ids to the DMR callsign lookup table

I: 2018-09-26 21:24:59.432 DMR RF Parameters

I: 2018-09-26 21:24:59.433     Id: 302401901

I: 2018-09-26 21:24:59.433     Color Code: 1

I: 2018-09-26 21:24:59.433     Self Only: no

I: 2018-09-26 21:24:59.433     Embedded LC Only: yes

I: 2018-09-26 21:24:59.433     Dump Talker Alias Data: no

I: 2018-09-26 21:24:59.433     Prefixes: 0

I: 2018-09-26 21:24:59.433     Call Hang: 3s

I: 2018-09-26 21:24:59.433     TX Hang: 3s

I: 2018-09-26 21:24:59.433     Mode Hang: 10s

M: 2018-09-26 21:24:59.433 DMR, Opening INI file: DVSwitch.ini

M: 2018-09-26 21:24:59.434 DMR, Setting [DMR] Address -> 127.0.0.1

M: 2018-09-26 21:24:59.434 DMR, Setting [DMR] TXPort -> 31100

M: 2018-09-26 21:24:59.434 DMR, Setting [DMR] RXPort -> 31103

M: 2018-09-26 21:24:59.434 DMR, Setting [DMR] Slot -> 2

I: 2018-09-26 21:24:59.432 Started the DMR Id lookup reload thread

M: 2018-09-26 21:24:59.437 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1

M: 2018-09-26 21:24:59.437 MMDVM_Bridge-20180423 is running

D: 2018-09-26 21:25:09.466 DMR, Sending authorisation

E: 2018-09-26 21:25:09.504 DMR, Login to the master has failed, retrying network ...

M: 2018-09-26 21:25:09.505 DMR, Closing DMR Network

M: 2018-09-26 21:25:09.505 DMR, Opening DMR Network

D: 2018-09-26 21:25:19.543 DMR, Sending authorisation

E: 2018-09-26 21:25:19.581 DMR, Login to the master has failed, retrying network ...

M: 2018-09-26 21:25:19.581 DMR, Closing DMR Network

M: 2018-09-26 21:25:19.581 DMR, Opening DMR Network

^CM: 2018-09-26 21:25:19.762 Closing the MMDVM

I: 2018-09-26 21:25:20.442 Stopped the DMR Id lookup reload thread

M: 2018-09-26 21:25:20.443 DMR, Closing DMR Network

I: 2018-09-26 21:25:20.443 MMDVM_Bridge-20180423 exited on receipt of SIGINT

Dan,
without looking at your files, I can only say,
check that you are using the appended dmr ID in the right place.
One is your true ID (non appended) and the other id that is a appended ID (if you chose to do it that way)

And I'm guessing you might want to check that your ID is correct as seen at brandmeister.

Look for type errors

Color Code for Canada correct and set ?

That's all I can think of off the top of my head.

Send your mmdvm_bridge.ini and analog_bridge.ini files if you don't find anything.


...mike/kb8jnm

Thanks for the help.  I've pretty much followed the instructions as far as I can tell.
I have specified the dmr id with the 2 digit extension has recommended. I've specified my brandmeister password and verified it.
I did not change any color code - not sure if that matters?
I am having the issue with the MMDVM_Bridge program - and have not progressed to changing/configuring the Analog yet.
Here's my ini file - less pass.  I can't see anything myself.
I'm still hunting. 73, Dan ve4drk

Password=passw0rd

...mike/kb8jnm

I was able to finish the config after fuddling with a few more things  - works well.  Will do further testing which should help with ensuring I have a good grasp of the config.  
Too bad our one and only brandmeister server is on the other side of the country -- the RTT gets an extra +30ms to the hop :-(

WPG -> MTL -> TOR -> MTL ... when will people get on the IX bandwagon?!

I will enjoy learning more about this config.

73, Dan ve4drk

Dan,
I believe it has been said,
If you have issues with the server,
Use any other one that works well for you.
So , it's worth a try if you are having issues.
But re-check periodically as things change.

I have found it is still logical to use the one 'closest to your ISP's HUB/switch', not necessarily the one closest to you if you understand that thinking.

...mike/kb8jnm