Date   

Re: Help install DVSwitch in server Debian 8 64 bits for error.

Steve KC1AWV
 

Here's my full output, sorry for the length, but I wanted to get everything.

vagrant@debian-8:/srv/DVSwitch-System-Builder$ sudo sh ./DVSwitch-System-Builder.sh
--2019-03-31 16:03:02--  http://dvswitch.org/install-dvswitch-repo
Resolving dvswitch.org (dvswitch.org)... 44.103.32.18
Connecting to dvswitch.org (dvswitch.org)|44.103.32.18|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 782
Saving to: ‘install-dvswitch-repo’

install-dvswitch-repo                              100%[==================================================================================================================>]     782  --.-KB/s   in 0s

2019-03-31 16:03:02 (55.2 MB/s) - ‘install-dvswitch-repo’ saved [782/782]

--2019-03-31 16:03:02--  http://dvswitch.org/ASL_Repository/dvswitch.list
Resolving dvswitch.org (dvswitch.org)... 44.103.32.18
Connecting to dvswitch.org (dvswitch.org)|44.103.32.18|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 92
Saving to: ‘dvswitch.list’

dvswitch.list                                      100%[==================================================================================================================>]      92  --.-KB/s   in 0s

2019-03-31 16:03:02 (6.38 MB/s) - ‘dvswitch.list’ saved [92/92]

--2019-03-31 16:03:02--  http://dvswitch.org/ASL_Repository/dvswitch.gpg.key
Resolving dvswitch.org (dvswitch.org)... 44.103.32.18
Connecting to dvswitch.org (dvswitch.org)|44.103.32.18|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1678 (1.6K) [application/pgp-keys]
Saving to: ‘STDOUT’

-                                                  100%[==================================================================================================================>]   1.64K  --.-KB/s   in 0s

2019-03-31 16:03:02 (103 MB/s) - written to stdout [1678/1678]

OK
Get:1 http://dvswitch.org stretch InRelease [4,806 B]
Get:2 http://dvswitch.org stretch/hamradio amd64 Packages [5,126 B]
Hit http://security.debian.org jessie/updates InRelease
Hit http://security.debian.org jessie/updates/main Sources
Hit http://security.debian.org jessie/updates/main amd64 Packages
Hit http://security.debian.org jessie/updates/main Translation-en
Ign http://dvswitch.org stretch/hamradio Translation-en_US
Ign http://dvswitch.org stretch/hamradio Translation-en
Ign http://httpredir.debian.org jessie InRelease
Hit http://httpredir.debian.org jessie Release.gpg
Hit http://httpredir.debian.org jessie Release
Hit http://httpredir.debian.org jessie/main Sources
Hit http://httpredir.debian.org jessie/main amd64 Packages
Hit http://httpredir.debian.org jessie/main Translation-en
Fetched 9,932 B in 28s (351 B/s)
Reading package lists... Done
Installed repositories:
http://dvswitch.org/ASL_Repository/stretch/hamradio
http://httpredir.debian.org/debian/jessie/main
httpredir.debian.org
http://security.debian.org/jessie/updates/main
Hit http://dvswitch.org stretch InRelease
Ign http://httpredir.debian.org jessie InRelease
Hit http://dvswitch.org stretch/hamradio amd64 Packages
Hit http://security.debian.org jessie/updates InRelease
Hit http://httpredir.debian.org jessie Release.gpg
Hit http://security.debian.org jessie/updates/main Sources
Hit http://httpredir.debian.org jessie Release
Hit http://httpredir.debian.org jessie/main Sources
Hit http://security.debian.org jessie/updates/main amd64 Packages
Hit http://httpredir.debian.org jessie/main amd64 Packages
Hit http://security.debian.org jessie/updates/main Translation-en
Ign http://dvswitch.org stretch/hamradio Translation-en_US
Ign http://dvswitch.org stretch/hamradio Translation-en
Hit http://httpredir.debian.org jessie/main Translation-en
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  git git-man liberror-perl rsync
Suggested packages:
  git-daemon-run git-daemon-sysvinit git-doc git-el git-email git-gui gitk gitweb git-arch git-cvs git-mediawiki git-svn
The following NEW packages will be installed:
  git git-core git-man liberror-perl rsync
0 upgraded, 5 newly installed, 0 to remove and 1 not upgraded.
Need to get 5,392 kB of archives.
After this operation, 24.7 MB of additional disk space will be used.
Get:1 http://security.debian.org/ jessie/updates/main git-man all 1:2.1.4-2.1+deb8u7 [1,269 kB]
Get:2 http://httpredir.debian.org/debian/ jessie/main liberror-perl all 0.17-1.1 [22.4 kB]
Get:3 http://security.debian.org/ jessie/updates/main git amd64 1:2.1.4-2.1+deb8u7 [3,709 kB]
Get:4 http://security.debian.org/ jessie/updates/main git-core all 1:2.1.4-2.1+deb8u7 [1,504 B]
Get:5 http://security.debian.org/ jessie/updates/main rsync amd64 3.1.1-3+deb8u2 [390 kB]
Fetched 5,392 kB in 1s (4,152 kB/s)
Selecting previously unselected package liberror-perl.
(Reading database ... 32039 files and directories currently installed.)
Preparing to unpack .../liberror-perl_0.17-1.1_all.deb ...
Unpacking liberror-perl (0.17-1.1) ...
Selecting previously unselected package git-man.
Preparing to unpack .../git-man_1%3a2.1.4-2.1+deb8u7_all.deb ...
Unpacking git-man (1:2.1.4-2.1+deb8u7) ...
Selecting previously unselected package git.
Preparing to unpack .../git_1%3a2.1.4-2.1+deb8u7_amd64.deb ...
Unpacking git (1:2.1.4-2.1+deb8u7) ...
Selecting previously unselected package git-core.
Preparing to unpack .../git-core_1%3a2.1.4-2.1+deb8u7_all.deb ...
Unpacking git-core (1:2.1.4-2.1+deb8u7) ...
Selecting previously unselected package rsync.
Preparing to unpack .../rsync_3.1.1-3+deb8u2_amd64.deb ...
Unpacking rsync (3.1.1-3+deb8u2) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for systemd (215-17+deb8u11) ...
Setting up liberror-perl (0.17-1.1) ...
Setting up git-man (1:2.1.4-2.1+deb8u7) ...
Setting up git (1:2.1.4-2.1+deb8u7) ...
Setting up git-core (1:2.1.4-2.1+deb8u7) ...
Setting up rsync (3.1.1-3+deb8u2) ...
Processing triggers for systemd (215-17+deb8u11) ...
Reading package lists... Done
Building dependency tree
Reading state information... Done
curl is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  g++-4.9 libstdc++-4.9-dev
Suggested packages:
  g++-multilib g++-4.9-multilib gcc-4.9-doc libstdc++6-4.9-dbg libstdc++-4.9-doc
The following NEW packages will be installed:
  g++ g++-4.9 libstdc++-4.9-dev
0 upgraded, 3 newly installed, 0 to remove and 1 not upgraded.
Need to get 18.7 MB of archives.
After this operation, 42.1 MB of additional disk space will be used.
Get:1 http://security.debian.org/ jessie/updates/main libstdc++-4.9-dev amd64 4.9.2-10+deb8u2 [1,118 kB]
Get:2 http://httpredir.debian.org/debian/ jessie/main g++ amd64 4:4.9.2-2 [1,530 B]
Get:3 http://security.debian.org/ jessie/updates/main g++-4.9 amd64 4.9.2-10+deb8u2 [17.6 MB]
Fetched 18.7 MB in 2s (8,217 kB/s)
Selecting previously unselected package libstdc++-4.9-dev:amd64.
(Reading database ... 32845 files and directories currently installed.)
Preparing to unpack .../libstdc++-4.9-dev_4.9.2-10+deb8u2_amd64.deb ...
Unpacking libstdc++-4.9-dev:amd64 (4.9.2-10+deb8u2) ...
Selecting previously unselected package g++-4.9.
Preparing to unpack .../g++-4.9_4.9.2-10+deb8u2_amd64.deb ...
Unpacking g++-4.9 (4.9.2-10+deb8u2) ...
Selecting previously unselected package g++.
Preparing to unpack .../g++_4%3a4.9.2-2_amd64.deb ...
Unpacking g++ (4:4.9.2-2) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up libstdc++-4.9-dev:amd64 (4.9.2-10+deb8u2) ...
Setting up g++-4.9 (4.9.2-10+deb8u2) ...
Setting up g++ (4:4.9.2-2) ...
update-alternatives: using /usr/bin/g++ to provide /usr/bin/c++ (c++) in auto mode
Reading package lists... Done
Building dependency tree
Reading state information... Done
make is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  analog-bridge binfmt-support dvswitch-base libasound2 libasound2-data libflac8 libogg0 libsndfile1 libvorbis0a libvorbisenc2 md380-emu mmdvm-bridge qemu-user-static
Suggested packages:
  libasound2-plugins alsa-utils
The following NEW packages will be installed:
  analog-bridge binfmt-support dvswitch dvswitch-base libasound2 libasound2-data libflac8 libogg0 libsndfile1 libvorbis0a libvorbisenc2 md380-emu mmdvm-bridge qemu-user-static
0 upgraded, 14 newly installed, 0 to remove and 1 not upgraded.
Need to get 12.7 MB of archives.
After this operation, 85.3 MB of additional disk space will be used.
Get:1 http://dvswitch.org/ASL_Repository/ stretch/hamradio dvswitch-base all 1.01-20180420-11 [1,616 kB]
Get:2 http://security.debian.org/ jessie/updates/main libsndfile1 amd64 1.0.25-9.1+deb8u4 [216 kB]
Get:3 http://httpredir.debian.org/debian/ jessie/main libasound2-data all 1.0.28-1 [64.8 kB]
Get:4 http://security.debian.org/ jessie/updates/main qemu-user-static amd64 1:2.1+dfsg-12+deb8u10 [8,232 kB]
Get:5 http://httpredir.debian.org/debian/ jessie/main libasound2 amd64 1.0.28-1 [374 kB]
Get:6 http://httpredir.debian.org/debian/ jessie/main libogg0 amd64 1.3.2-1 [19.9 kB]
Get:7 http://httpredir.debian.org/debian/ jessie/main libflac8 amd64 1.3.0-3 [89.3 kB]
Get:8 http://httpredir.debian.org/debian/ jessie/main libvorbis0a amd64 1.3.4-2+deb8u1 [92.5 kB]
Get:9 http://httpredir.debian.org/debian/ jessie/main libvorbisenc2 amd64 1.3.4-2+deb8u1 [77.8 kB]
Get:10 http://dvswitch.org/ASL_Repository/ stretch/hamradio analog-bridge amd64 1.1-20180424-11 [155 kB]
Get:11 http://httpredir.debian.org/debian/ jessie/main binfmt-support amd64 2.1.5-1 [58.2 kB]
Get:12 http://dvswitch.org/ASL_Repository/ stretch/hamradio dvswitch all 1.01-20180420-3 [2,144 B]
Get:13 http://dvswitch.org/ASL_Repository/ stretch/hamradio md380-emu amd64 1.1-20180424-5 [687 kB]
Get:14 http://dvswitch.org/ASL_Repository/ stretch/hamradio mmdvm-bridge amd64 1.1-20180424-5 [1,055 kB]
Fetched 12.7 MB in 1s (8,125 kB/s)
Selecting previously unselected package libasound2-data.
(Reading database ... 33635 files and directories currently installed.)
Preparing to unpack .../libasound2-data_1.0.28-1_all.deb ...
Unpacking libasound2-data (1.0.28-1) ...
Selecting previously unselected package libasound2:amd64.
Preparing to unpack .../libasound2_1.0.28-1_amd64.deb ...
Unpacking libasound2:amd64 (1.0.28-1) ...
Selecting previously unselected package libogg0:amd64.
Preparing to unpack .../libogg0_1.3.2-1_amd64.deb ...
Unpacking libogg0:amd64 (1.3.2-1) ...
Selecting previously unselected package libflac8:amd64.
Preparing to unpack .../libflac8_1.3.0-3_amd64.deb ...
Unpacking libflac8:amd64 (1.3.0-3) ...
Selecting previously unselected package libvorbis0a:amd64.
Preparing to unpack .../libvorbis0a_1.3.4-2+deb8u1_amd64.deb ...
Unpacking libvorbis0a:amd64 (1.3.4-2+deb8u1) ...
Selecting previously unselected package libvorbisenc2:amd64.
Preparing to unpack .../libvorbisenc2_1.3.4-2+deb8u1_amd64.deb ...
Unpacking libvorbisenc2:amd64 (1.3.4-2+deb8u1) ...
Selecting previously unselected package libsndfile1:amd64.
Preparing to unpack .../libsndfile1_1.0.25-9.1+deb8u4_amd64.deb ...
Unpacking libsndfile1:amd64 (1.0.25-9.1+deb8u4) ...
Selecting previously unselected package dvswitch-base.
Preparing to unpack .../dvswitch-base_1.01-20180420-11_all.deb ...
Unpacking dvswitch-base (1.01-20180420-11) ...
Selecting previously unselected package analog-bridge.
Preparing to unpack .../analog-bridge_1.1-20180424-11_amd64.deb ...
Unpacking analog-bridge (1.1-20180424-11) ...
Selecting previously unselected package binfmt-support.
Preparing to unpack .../binfmt-support_2.1.5-1_amd64.deb ...
Unpacking binfmt-support (2.1.5-1) ...
Selecting previously unselected package dvswitch.
Preparing to unpack .../dvswitch_1.01-20180420-3_all.deb ...
Unpacking dvswitch (1.01-20180420-3) ...
Selecting previously unselected package qemu-user-static.
Preparing to unpack .../qemu-user-static_1%3a2.1+dfsg-12+deb8u10_amd64.deb ...
Unpacking qemu-user-static (1:2.1+dfsg-12+deb8u10) ...
Selecting previously unselected package md380-emu.
Preparing to unpack .../md380-emu_1.1-20180424-5_amd64.deb ...
Unpacking md380-emu (1.1-20180424-5) ...
Selecting previously unselected package mmdvm-bridge.
Preparing to unpack .../mmdvm-bridge_1.1-20180424-5_amd64.deb ...
Unpacking mmdvm-bridge (1.1-20180424-5) ...
Processing triggers for systemd (215-17+deb8u11) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up libasound2-data (1.0.28-1) ...
Setting up libasound2:amd64 (1.0.28-1) ...
Setting up libogg0:amd64 (1.3.2-1) ...
Setting up libflac8:amd64 (1.3.0-3) ...
Setting up libvorbis0a:amd64 (1.3.4-2+deb8u1) ...
Setting up libvorbisenc2:amd64 (1.3.4-2+deb8u1) ...
Setting up libsndfile1:amd64 (1.0.25-9.1+deb8u4) ...
Setting up dvswitch-base (1.01-20180420-11) ...
dpkg: error processing package dvswitch-base (--configure):
 subprocess installed post-installation script returned error exit status 8
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
Setting up binfmt-support (2.1.5-1) ...
Setting up dvswitch (1.01-20180420-3) ...
Setting up qemu-user-static (1:2.1+dfsg-12+deb8u10) ...
Setting up md380-emu (1.1-20180424-5) ...
Created symlink from /etc/systemd/system/multi-user.target.wants/md380-emu.service to /lib/systemd/system/md380-emu.service.
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
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Processing triggers for systemd (215-17+deb8u11) ...
Errors were encountered while processing:
 dvswitch-base
 analog-bridge
 mmdvm-bridge
E: Sub-process /usr/bin/dpkg returned an error code (1)
vagrant@debian-8:/srv/DVSwitch-System-Builder$


Feed From DV_Swithch to YSFReflector drops out when used

N9UMJ
 

Hi All

My feed from the VPS using DV_Switch has been dropping connection every time  the repeater is used. after about 60 seconds +/- of use the feed drops out between the reflector, repeaters and the YSFReflector the reflector and about a minute later it returns. II'm using port 42000 to the ysfreflector dashboard, Is there a timer that needs to be changed ? It has been running for about 6 months with only an occasional drop out and now it is every time, It started a few updates ago around January., Ive checked my configurations and nothing seems to have changed, I have  checked my graphs on digital ocean and the uptime has been solid so I know it's not on their end. My cpu usage and latency are low so I know I've not over taxed the server...Any Ideas of where I might look or have there been others experiencing the same problem that can share their method to resolve the issue?

Thanks
Rick /n9umj


Re: Help install DVSwitch in server Debian 8 64 bits for error.

Steve KC1AWV
 
Edited

Gotcha. I think that the fix you made mention of back in November may help. Purge package, update repo and reinstall. I tried here running the builder script on Debian 8 and I think I got the error to replicate. I'll post output when wipe and try again.


Re: Help install DVSwitch in server Debian 8 64 bits for error.

Steve KC1AWV
 

Another option is to take a look at an ASL thread that mentioned a similar issue. N4IRS gave some tricks to try to fix the issue.

https://dvswitch.groups.io/g/allstarlink/message/351

To fix the problem:
As root:
apt purge dvswitch-base
Say yes to Do you want to continue? [Y/n]

apt-get update
apt-get install dvswitch-base


Re: Help install DVSwitch in server Debian 8 64 bits for error.

Steve N4IRS
 

It's all one repo. I added the DVSwitch stuff to the ASL repo.

On 3/31/19 11:23 AM, Steve KC1AWV wrote:
Could be, I'll see if I can replicate the issue here. Then again, I don't know where the dvswitch-base package came from, other than an ASL repo.


Re: Help install DVSwitch in server Debian 8 64 bits for error.

Steve KC1AWV
 

Could be, I'll see if I can replicate the issue here. Then again, I don't know where the dvswitch-base package came from, other than an ASL repo.


Re: Help install DVSwitch in server Debian 8 64 bits for error.

Mike KB8JNM
 

My first thought was Deb 8 may not have all supporting library for it. But never tried it.

On 3/31/2019 11:17 AM, Steve KC1AWV wrote:
For explanation of exit status 8 - that's an exec format error according to errno. Could be the package you're installing is for the wrong architecture, such as trying to install a package for ARM on an x86.


Re: Help install DVSwitch in server Debian 8 64 bits for error.

Steve KC1AWV
 

For explanation of exit status 8 - that's an exec format error according to errno. Could be the package you're installing is for the wrong architecture, such as trying to install a package for ARM on an x86.


Re: Help install DVSwitch in server Debian 8 64 bits for error.

Steve KC1AWV
 

Need more info. how are you installing DVSwitch? Are you using the DVSwitch-System-Builder script?

Only references to dvswitch-base I can find is in ASL, not DVSwitch.


Help install DVSwitch in server Debian 8 64 bits for error.

EA5GVK Joaquin
 

Help. It report it error when install dvswitch:
Selecting previously unselected package dvswitch-base.
(Reading database ... 42595 files and directories currently installed.)
Preparing to unpack dvswitch-base_1.01-20180420-11_all.deb ...
Unpacking dvswitch-base (1.01-20180420-11) ...
Setting up dvswitch-base (1.01-20180420-11) ...
dpkg: error processing package dvswitch-base (--install):
 subprocess installed post-installation script returned error exit status 8
Errors were encountered while processing:
 dvswitch-base


Quick deploy DVSwitch test box

Steve KC1AWV
 

Hi everyone,

Since I do work testing and developing systems at work, I use vagrant a lot. It helps me build test virtual machines and provision them quickly to test out things. Sometimes, I need to destroy and re-provision those virtual machines in a rapid fashion, so vagrant is the way to go. If you're interested, I've put the vagrantfile and provisioning steps up on github for those interested.

https://github.com/kc1awv/dvswitch-sandbox

You'll need vagrant and virtualbox installed on a machine. Simply git clone the repo, go into the directory and run vagrant up. The system will download a bento Debian 9.6 box and install the DVSwitch programs from the DVSwitch-System-Builder script from Steve N4IRS. I also included a DMRGateway unit file for systemd in there as well.

Do not use this system in production! This is designed as a development box, so play with the configs as you see fit, then copy your configs from the vagrant box to your production system.

Questions and comments are welcomed, and I will do my best to respond as work permits.

Steve KC1AWV


Re: Linking P25 to P25 using two mmdvm's

David BV3UN
 

Hi for DMR to P25 via DVswitch you can reference this blog 
http://blog.927.org/node/1


Re: Linking P25 to P25 using two mmdvm's

Tony Steele
 

Hi

Just to update the group, I managed to get this working perfectly using a MMDVM duplex hotspot (UHF) with a Orange Pi zero and a MMDVM modem pcb attached to a GM360 VHF and Raspberry Pi 2.
I also installed P25 Reflector on a seperate Raspberry Pi 2.
Following the instructions Mike gave above, aside from the issue I had with Raspbian on the Orange Pi Zero (above), everything went fine when I switched to Armbian.
It works very very well, I still have some playing to do, but very impressed so far, the total delay is just under 2 seconds and that includes the internet trip to my house.

A final question Mike if I may, how simple would it be to add in another unit with a seperate Pi and MMDVM hotspot but running DMR? I know this is now getting more complicated, but just thinking ahead a bit, would I need to install something on the third Pi currently running P25reflector to link the DMR to the P25 or is this not possible?

Thank you for all the help, it is very much appreciated.

Regards
Tony.


Re: 1 Way Audio (XLX DMR to ASL)

Steve KC1AWV
 

Thanks, I got one here I run. I'll test and let you know what I find!

On Thu, Mar 28, 2019 at 8:18 AM Daniel L. Srebnick <dan@...> wrote:
Here's hoping you are able to figure it out! If you need an XLX to test with, feel free to use XLX020 E.

73,

Dan

On Thu, 2019-03-28 at 07:43 -0400, Steve KC1AWV wrote:
Ok, unless someone else can provide clues as to what might be happening I may have to lab this and go through the steps again to recreate and solve. I plan on restructuring the system I run here this weekend anyway, so it may be a good chance to write this stuff down for future reference.

On Wed, Mar 27, 2019 at 9:58 PM Daniel L. Srebnick <dan@...> wrote:
Steve:

I changed the repeater id in Analog_Bridge.ini to 1234567 as you suggested. After restarting all the involved processes, my test results were unchanged.

On Wed, 2019-03-27 at 20:48 -0400, Steve KC1AWV wrote:
Daniel,

I've had the same issue myself before. I'm trying to remember exactly what I did to rectify the problem, but it's been a while since the last time I played with the configurations here. One thing that I do want to note is to make sure that you send only a max of a 7 digit DMR ID when going to XLX, your repeater ID has 9 digits. Try setting the repeater ID to something like 1234567 (if you don't have a second DMR ID) and test again. I'm not sure if using that ID is copacetic with every network, but it shouldn't be a problem with XLX since I think it only uses the repeater ID to lookup and display the callsign of the network you're coming in on. Your mileage may vary, caveat emptor, don't forget to turn the lights off before you leave, etc.

I would be very interested in how the test runs with that change.

Steve KC1AWV






--
Steve Miller
KC1AWV


Re: 1 Way Audio (XLX DMR to ASL)

Dan K2IE
 

Here's hoping you are able to figure it out! If you need an XLX to test with, feel free to use XLX020 E.

73,

Dan

On Thu, 2019-03-28 at 07:43 -0400, Steve KC1AWV wrote:
Ok, unless someone else can provide clues as to what might be happening I may have to lab this and go through the steps again to recreate and solve. I plan on restructuring the system I run here this weekend anyway, so it may be a good chance to write this stuff down for future reference.

On Wed, Mar 27, 2019 at 9:58 PM Daniel L. Srebnick <dan@...> wrote:
Steve:

I changed the repeater id in Analog_Bridge.ini to 1234567 as you suggested. After restarting all the involved processes, my test results were unchanged.

On Wed, 2019-03-27 at 20:48 -0400, Steve KC1AWV wrote:
Daniel,

I've had the same issue myself before. I'm trying to remember exactly what I did to rectify the problem, but it's been a while since the last time I played with the configurations here. One thing that I do want to note is to make sure that you send only a max of a 7 digit DMR ID when going to XLX, your repeater ID has 9 digits. Try setting the repeater ID to something like 1234567 (if you don't have a second DMR ID) and test again. I'm not sure if using that ID is copacetic with every network, but it shouldn't be a problem with XLX since I think it only uses the repeater ID to lookup and display the callsign of the network you're coming in on. Your mileage may vary, caveat emptor, don't forget to turn the lights off before you leave, etc.

I would be very interested in how the test runs with that change.

Steve KC1AWV





Re: 1 Way Audio (XLX DMR to ASL)

Steve KC1AWV
 

Ok, unless someone else can provide clues as to what might be happening I may have to lab this and go through the steps again to recreate and solve. I plan on restructuring the system I run here this weekend anyway, so it may be a good chance to write this stuff down for future reference.

On Wed, Mar 27, 2019 at 9:58 PM Daniel L. Srebnick <dan@...> wrote:
Steve:

I changed the repeater id in Analog_Bridge.ini to 1234567 as you suggested. After restarting all the involved processes, my test results were unchanged.

On Wed, 2019-03-27 at 20:48 -0400, Steve KC1AWV wrote:
Daniel,

I've had the same issue myself before. I'm trying to remember exactly what I did to rectify the problem, but it's been a while since the last time I played with the configurations here. One thing that I do want to note is to make sure that you send only a max of a 7 digit DMR ID when going to XLX, your repeater ID has 9 digits. Try setting the repeater ID to something like 1234567 (if you don't have a second DMR ID) and test again. I'm not sure if using that ID is copacetic with every network, but it shouldn't be a problem with XLX since I think it only uses the repeater ID to lookup and display the callsign of the network you're coming in on. Your mileage may vary, caveat emptor, don't forget to turn the lights off before you leave, etc.

I would be very interested in how the test runs with that change.

Steve KC1AWV




--
Steve Miller
KC1AWV


Re: Asterisk Error

K4VL
 

As a matter of fact I bought two new cards. The second I plan on being a clone. 


On Wed, Mar 27, 2019, 7:56 PM Steve KC1AWV <smiller@...> wrote:
Glad to hear it! I would suggest to take an image of the known good card and back it up safely somewhere so you can slap it on a new card if this comes up again. But that might just be the paranoia here talking. :)

Steve KC1AWV

On Wed, Mar 27, 2019 at 7:13 PM K4VL <73dek4vl@...> wrote:
Thanks again for everybody's help. I bought a new SD card and got it reconfigured and working again.

73 de K4VL

Virus-free. www.avg.com

On Wed, Mar 27, 2019 at 4:34 AM Steve N4IRS <szingman@...> wrote:
I would at least run asterisk in the foreground with:
asterisk -vcd

On 3/27/19 5:33 AM, Steve KC1AWV wrote:
If the logs are empty, then it's going to be next to impossible to diagnose the problem. Log files are the single most important thing on a computer, and without them, you're flying blind.

At this point, I'd say back up the configuration files and put them somewhere for reference and start over.

On Tue, Mar 26, 2019, 10:25 PM K4VL <73dek4vl@...> wrote:
The logs appear empty. I event went into the asterisk log folder and opened the event log and it was blank.



--
Steve Miller
KC1AWV


Re: 1 Way Audio (XLX DMR to ASL)

Dan K2IE
 

Steve:

I changed the repeater id in Analog_Bridge.ini to 1234567 as you suggested. After restarting all the involved processes, my test results were unchanged.

On Wed, 2019-03-27 at 20:48 -0400, Steve KC1AWV wrote:
Daniel,

I've had the same issue myself before. I'm trying to remember exactly what I did to rectify the problem, but it's been a while since the last time I played with the configurations here. One thing that I do want to note is to make sure that you send only a max of a 7 digit DMR ID when going to XLX, your repeater ID has 9 digits. Try setting the repeater ID to something like 1234567 (if you don't have a second DMR ID) and test again. I'm not sure if using that ID is copacetic with every network, but it shouldn't be a problem with XLX since I think it only uses the repeater ID to lookup and display the callsign of the network you're coming in on. Your mileage may vary, caveat emptor, don't forget to turn the lights off before you leave, etc.

I would be very interested in how the test runs with that change.

Steve KC1AWV



Re: Asterisk Error

Steve KC1AWV
 

Glad to hear it! I would suggest to take an image of the known good card and back it up safely somewhere so you can slap it on a new card if this comes up again. But that might just be the paranoia here talking. :)

Steve KC1AWV


On Wed, Mar 27, 2019 at 7:13 PM K4VL <73dek4vl@...> wrote:
Thanks again for everybody's help. I bought a new SD card and got it reconfigured and working again.

73 de K4VL

Virus-free. www.avg.com

On Wed, Mar 27, 2019 at 4:34 AM Steve N4IRS <szingman@...> wrote:
I would at least run asterisk in the foreground with:
asterisk -vcd

On 3/27/19 5:33 AM, Steve KC1AWV wrote:
If the logs are empty, then it's going to be next to impossible to diagnose the problem. Log files are the single most important thing on a computer, and without them, you're flying blind.

At this point, I'd say back up the configuration files and put them somewhere for reference and start over.

On Tue, Mar 26, 2019, 10:25 PM K4VL <73dek4vl@...> wrote:
The logs appear empty. I event went into the asterisk log folder and opened the event log and it was blank.



--
Steve Miller
KC1AWV


Re: 1 Way Audio (XLX DMR to ASL)

Steve KC1AWV
 

Daniel,

I've had the same issue myself before. I'm trying to remember exactly what I did to rectify the problem, but it's been a while since the last time I played with the configurations here. One thing that I do want to note is to make sure that you send only a max of a 7 digit DMR ID when going to XLX, your repeater ID has 9 digits. Try setting the repeater ID to something like 1234567 (if you don't have a second DMR ID) and test again. I'm not sure if using that ID is copacetic with every network, but it shouldn't be a problem with XLX since I think it only uses the repeater ID to lookup and display the callsign of the network you're coming in on. Your mileage may vary, caveat emptor, don't forget to turn the lights off before you leave, etc.

I would be very interested in how the test runs with that change.

Steve KC1AWV


On Wed, Mar 27, 2019 at 4:04 PM Daniel L. Srebnick <dan@...> wrote:
Just to clarify the diagram below, the md380-emu hangs off the Analog Bridge...should have used a fixed font.

On Wed, 2019-03-27 at 12:13 -0700, Daniel L. Srebnick wrote:
I am trying to gateway ASL to XLX DMR.  Here is a diagram of what I have implemented.

Cloud Server 1

ASL Asterisk (Pvt Node and Public Node) <===> Analog Bridge <===> MMDVM Bridge <===> DMR Gateway (from github)
                                                                                      ||
                                                                                      ||
                                                                                md380-emu

Cloud Server 2

xlxd based reflector


I can successfully pass audio from the DMR side to the Asterisk side of the connection.  Quality is good.  However, when I try to pass audio from Asterisk to DMR, it sets up the path but there is no audio.  The DMR side times out after about 2 seconds after Analog PTT, the ID number of the gateway shows up on the screen, and that is all.

What should I look at next?

Here are some log snippets from a successful DMR <==> Analog transmission:

MMDVM Bridge:
M: 2019-03-27 19:03:19.379 DMR Slot 2, received network voice header from K2DLS to TG 6
M: 2019-03-27 19:03:23.554 DMR Slot 2, received network end of voice transmission, 4.0 seconds, 0% packet loss, BER: 0.0%

Analog Bridge:

I: 2019-03-27 19:02:34.163 Begin TX: src=3134090 rpt=0 dst=6 slot=2 cc=0
D: 2019-03-27 19:02:37.225 End TX

Here are snippers from the unsuccesful Analog <==> DMR:

MMDVM Bridge:

M: 2019-03-27 19:04:10.405 DMR, TX state = ON
I: 2019-03-27 19:04:10.405 DMR, Begin TX: src=3134090 rpt=313409003 dst=6 slot=2 cc=1 metadata=K2DLS
M: 2019-03-27 19:04:14.262 DMR, TX state = OFF

Analog Bridge:

M: 2019-03-27 19:04:10.403 PTT on
D: 2019-03-27 19:04:14.259 cpu_time_used = 3856, minTxTime = 2000, pttTime = 1553713450403, end = 1553713454259
M: 2019-03-27 19:04:14.259 PTT off (keyed for 3856 ms)

DMR Gateway:

No useful logging for XLX seen after the connect with the level set to 1.

xlxd: Lots of these going from analog to DMR...

Mar 27 14:58:22 somehost xlxd[8847]: WARNING: orphaned DvFramePacket SID 56803 from 1.2.3.4
Mar 27 14:58:23 somehost xlxd[8847]: WARNING: orphaned DvFramePacket SID 56803 from 1.2.3.4
Mar 27 14:58:23 somehost xlxd[8847]: WARNING: orphaned DvFramePacket SID 56803 from 1.2.3.4
Mar 27 14:58:23 somehost xlxd[8847]: WARNING: orphaned DvFramePacket SID 56803 from 1.2.3.4
Mar 27 14:58:23 somehost xlxd[8847]: WARNING: orphaned DvFramePacket SID 56803 from 1.2.3.4

A fellow ham in the local area also had this exact problem.

Suggestions appreciated.

73,

Dan Srebnick
K2DLS



--
Steve Miller
KC1AWV

6221 - 6240 of 9882