Date   

Re: TG Listing in DVSwitch

Tom Corcoran
 

Hello Mike,
to do this, do I use "./dvswitch.sh collectProcessPushDataFiles"? Do I just enter file name at end of this command? Is it necessary to enter the destination directory in DVSM (if there is one)"

tnx ... 
Tom VE3NY


Re: Brandmeister to XLX

Steve N4IRS
 

Download from github.

On 12/13/2019 6:53 AM, Tom Corcoran wrote:
Ernie,

can i do apt-get update/upgrade for latest MMDVM_Bridge ... or must I download from github?

tnx ... Tom VE3NY


Re: TG Listing in DVSwitch

Mike Zingman - N4IRR
 

Jay,

You can upload any DMR database to the DVSM app by using the dvswitch.sh script.  The script has several commands that will aid you in this process including the download of the database from the internet, processing of that data into a form compatible with DVSM and upload of the processed file to the app.  

As to you desire to customize the database.  You can change it any way you want before you upload it.  One of the best way to customize it is to place your favorite talk groups in the first 10 locations of the file.  These first 10 locations are used as the "long press" dial macros you use on the keypad.  So, if you want your TG to be number five, place it in the fifth location and when you long press the 5 key on the keyboard it will automatically dial your favorite TG.

Hope this helps,
Mike N4IRR


Re: Brandmeister to XLX

Tom Corcoran
 

Ernie,

can i do apt-get update/upgrade for latest MMDVM_Bridge ... or must I download from github?

tnx ... Tom VE3NY


TG Listing in DVSwitch

Jay Mazure
 


Hello all,

I am new to DV Switch.   I installed the ap on my Samsung S7 and have a VM running Ubuntu.     Everything is working fine,  however I find the TG Listing 
awkward to be used.   As well I would like the option to add a TG if possible as well as making simple a simple TG list of what I mostly use.


I see these two items in Ubuntu for TGList:
1.  /usr/local/sbin/TGListUPdate.sh

2.. /var/liv/mmdvm/TGList.txt

For example I wanted to add TG5156 for the Philippines.   I thought it would be something simple like editing and making the change in the TGlist.txt file,   but that didn't work.  

Any help or advice greatly appreciated.  If this is being worked on else where or has been discussed elsewhere please advise.

73's
Jay Mazure / WT8K
DMR 3132283


Re: Hytera DMR Gateway

Chris K7AZ
 

Hi Jake, I am still following.  
Will try zero as you suggest.  
Was there a link to the video?

When I go to use transcoder after a several day unused period, I find I have to reboot the ASL system.  Have you heard of similiar ?   This is running on a VM platform.  

Thanks,
Chris K7AZ 



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Jake Litwin <litwinjwi@...>
Date: 12/9/19 20:43 (GMT-08:00)
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Hytera DMR Gateway

Hi Chris,

Not sure if you're still following this thread. Great video on this! I had a similar problem but found the solution. It's been working nicely.

DMRGateway.ini


[General]

Timeout=0  <----- Changed to Zero

 


Re: Hytera DMR Gateway

Jake Litwin
 

Hi Chris,

Not sure if you're still following this thread. Great video on this! I had a similar problem but found the solution. It's been working nicely.

DMRGateway.ini


[General]

Timeout=0  <----- Changed to Zero

 


Re: ASL Analog_Bridge and dvswitch.sh #analog_bridge

Steve N4IRS
 

Ed,
Not as of today, but it is planned for SOON.

Steve N4IRS

On 12/9/2019 12:56 PM, Ed W8VT wrote:
When changing digital modes via dvswitch.sh is there a way to set the audio levels for each mode. Not using DVSM with this installation.

Ed W8VT


ASL Analog_Bridge and dvswitch.sh #analog_bridge

Ed W8VT
 

When changing digital modes via dvswitch.sh is there a way to set the audio levels for each mode. Not using DVSM with this installation.

Ed W8VT


Re: Linking dmrlink and HBlink3 #dmrlink #hblink

Cort N0MJS <n0mjs@...>
 

Correct – that error is an “error" because I wrote the code that calls it one. It has been observed many times and isn’t an issue. I’ve suspected it has something to do with XNL/XCMP, but am not sure. I could have just as easily put it at the “WARNING” level instead, but wanted to see those pop out at me when they flew by, so put it at the error level.

On Dec 9, 2019, at 6:47 AM, area51now via Groups.Io <area51now@...> wrote:

The error message your seeing looks like mine when a trbo peer is connected (below is mine) every thing working fine here

ERROR 2019-12-09 04:42:22,977 (Peer-5-XN TS2) Unknown Message - Type: f0 From: 4770 Packet: f0000012a249531000


Bob
'
KB6LED

Cort Buffington
785-865-7206


Re: Linking dmrlink and HBlink3 #dmrlink #hblink

area51now@...
 

I get the same looking error when a mototrbo repeater is connected as a peer (see below)
all working good here

ERROR 2019-12-09 04:42:22,977 (Peer-5-XN TS2) Unknown Message - Type: f0 From: 4770 Packet: f0000012a249531000

I hope I am not doubling up on this message

Bob

KB6LED

-----Original Message-----
From: ai6bx via Groups.Io <ai6bx.keith@...>
To: main <main@DVSwitch.groups.io>
Sent: Sun, Dec 8, 2019 10:50 pm
Subject: Re: [DVSwitch] Linking dmrlink and HBlink3 #dmrlink #hblink

After taking a few days off, I am coming back into my config files and trying to understand an error message. Following is the log file when confbridge.py is running. Note one of my peers starts and appears to function fine and I am getting an error on the the second client connection attempts, Carlsbad.

root@AI6BX-DMR:/opt/DMRlink# python confbridge.py
INFO 2019-12-08 22:37:39,737 DMRlink 'dmrlink.py' (c) 2013 - 2015 N0MJS & the K0USY Group - SYSTEM STARTING...
INFO 2019-12-08 22:37:40,755 ID ALIAS MAPPER: 'peer_ids.json' successfully downloaded
INFO 2019-12-08 22:37:42,199 ID ALIAS MAPPER: 'subscriber_ids.json' successfully downloaded
INFO 2019-12-08 22:37:42,359 ID ALIAS MAPPER: peer_ids dictionary is available
INFO 2019-12-08 22:37:44,211 ID ALIAS MAPPER: subscriber_ids dictionary is available
INFO 2019-12-08 22:37:44,214 (RIFF_PEER) IPSC Instance Created: 92374, 0.0.0.0:50001
INFO 2019-12-08 22:37:44,215 (RIFF_PEER) Registering with the Master: 47.180.30.199:7000
INFO 2019-12-08 22:37:44,216 (IBEX) IPSC Instance Created: 734379, 0.0.0.0:62055
INFO 2019-12-08 22:37:44,216 (CARLSBAD) IPSC Instance Created: 92002, 0.0.0.0:62031
INFO 2019-12-08 22:37:44,217 (HB_BRIDGE) IPSC Instance Created: 12345, 0.0.0.0:62050
INFO 2019-12-08 22:37:44,218 Bridge configuration file found and imported
INFO 2019-12-08 22:37:44,218 ACL file not found or invalid - all subscriber IDs are valid
INFO 2019-12-08 22:37:44,218 (ALL IPSC SYSTEMS) Rule timer loop started
WARNING 2019-12-08 22:37:44,737 (RIFF_PEER) PeerError: Peer not in peer-list: 734377, 72.132.11.23:1024
WARNING 2019-12-08 22:37:48,515 (RIFF_PEER) PeerError: Peer not in peer-list: 734868, 47.156.178.150:50008
INFO 2019-12-08 22:37:49,216 (RIFF_PEER) Registering with the Master: 47.180.30.199:7000
WARNING 2019-12-08 22:37:49,226 (RIFF_PEER) Registration response (we requested reg) from the Master: 734379, 47.180.30.199:7000 (7 peers)
WARNING 2019-12-08 22:37:50,748 (RIFF_PEER) PeerError: Peer not in peer-list: 734377, 72.132.11.23:1024
INFO 2019-12-08 22:37:51,308 (CARLSBAD) Master Registration Packet Received from peer 734566, 76.81.231.35:50009
ERROR 2019-12-08 22:37:51,323 (CARLSBAD) Unknown Message - Type: f0 From: 734566 Packet: f0000b356600000000
INFO 2019-12-08 22:37:54,216 (RIFF_PEER), No Peer List - Requesting One From the Master
WARNING 2019-12-08 22:37:54,517 (RIFF_PEER) PeerError: Peer not in peer-list: 734868, 47.156.178.150:50008
WARNING 2019-12-08 22:37:56,747 (RIFF_PEER) PeerError: Peer not in peer-list: 734377, 72.132.11.23:1024
INFO 2019-12-08 22:37:59,215 (RIFF_PEER), No Peer List - Requesting One From the Master
WARNING 2019-12-08 22:37:59,270 (RIFF_PEER) PeerError: Peer not in peer-list: 734, 72.132.11.23:7000
INFO 2019-12-08 22:37:59,419 (RIFF_PEER) Peer List Received from Master: 6 peers in this IPSC
INFO 2019-12-08 22:37:59,508 (RIFF_PEER) Peer Registration Request From: 734, 72.132.11.23:7000
INFO 2019-12-08 22:37:59,670 (RIFF_PEER) Peer Registration Request From: 725123, 72.132.11.23:1051
INFO 2019-12-08 22:38:00,041 (RIFF_PEER) Peer Registration Request From: 734555, 162.248.117.53:7000
INFO 2019-12-08 22:38:00,255 (RIFF_PEER) Peer Registration Request From: 734990, 72.132.11.23:50006
WARNING 2019-12-08 22:38:00,525 (RIFF_PEER) PeerError: Peer not in peer-list: 734868, 47.156.178.150:50008
INFO 2019-12-08 22:38:04,215 (RIFF_PEER) Registering with Peer 734555, 162.248.117.53:7000
INFO 2019-12-08 22:38:04,216 (RIFF_PEER) Registering with Peer 734990, 72.132.11.23:50006
INFO 2019-12-08 22:38:04,216 (RIFF_PEER) Registering with Peer 734377, 72.132.11.23:1024
INFO 2019-12-08 22:38:04,216 (RIFF_PEER) Registering with Peer 725123, 72.132.11.23:1051
INFO 2019-12-08 22:38:04,216 (RIFF_PEER) Registering with Peer 734, 72.132.11.23:7000
INFO 2019-12-08 22:38:04,235 (RIFF_PEER) Registration Reply From: 734555, 162.248.117.53:7000
INFO 2019-12-08 22:38:04,242 (RIFF_PEER) Registration Reply From: 734377, 72.132.11.23:1024
INFO 2019-12-08 22:38:04,247 (RIFF_PEER) Registration Reply From: 725123, 72.132.11.23:1051
INFO 2019-12-08 22:38:04,252 (RIFF_PEER) Registration Reply From: 734990, 72.132.11.23:50006
INFO 2019-12-08 22:38:04,264 (RIFF_PEER) Registration Reply From: 734, 72.132.11.23:7000
ERROR 2019-12-08 22:38:06,322 (CARLSBAD) Unknown Message - Type: f0 From: 734566 Packet: f0000b356648531000
WARNING 2019-12-08 22:38:06,523 (RIFF_PEER) PeerError: Peer not in peer-list: 734868, 47.156.178.150:50008
WARNING 2019-12-08 22:38:12,515 (RIFF_PEER) PeerError: Peer not in peer-list: 734868, 47.156.178.150:50008
WARNING 2019-12-08 22:38:13,135 (RIFF_PEER) PeerError: Peer not in peer-list: 20001, 67.63.96.6:1046
INFO 2019-12-08 22:38:13,271 (RIFF_PEER) Peer List Received from Master: 7 peers in this IPSC
INFO 2019-12-08 22:38:13,430 (RIFF_PEER) Peer Registration Request From: 20001, 67.63.96.6:1046
INFO 2019-12-08 22:38:14,216 (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
WARNING 2019-12-08 22:38:18,517 (RIFF_PEER) PeerError: Peer not in peer-list: 734868, 47.156.178.150:50008
INFO 2019-12-08 22:38:19,216 (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO 2019-12-08 22:38:20,322 (RIFF_PEER) Peer List Received from Master: 7 peers in this IPSC
ERROR 2019-12-08 22:38:21,322 (CARLSBAD) Unknown Message - Type: f0 From: 734566 Packet: f0000b35664e531000
INFO 2019-12-08 22:38:24,216 (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
WARNING 2019-12-08 22:38:24,535 (RIFF_PEER) PeerError: Peer not in peer-list: 734868, 47.156.178.150:50008
INFO 2019-12-08 22:38:29,216 (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
WARNING 2019-12-08 22:38:30,690 (RIFF_PEER) PeerError: Peer not in peer-list: 734868, 47.156.178.150:50008
INFO 2019-12-08 22:38:31,421 (RIFF_PEER) Peer List Received from Master: 7 peers in this IPSC
INFO 2019-12-08 22:38:34,216 (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO 2019-12-08 22:38:34,721 (RIFF_PEER) Peer List Received from Master: 7 peers in this IPSC
ERROR 2019-12-08 22:38:36,322 (CARLSBAD) Unknown Message - Type: f0 From: 734566 Packet: f0000b356674531000
WARNING 2019-12-08 22:38:36,518 (RIFF_PEER) PeerError: Peer not in peer-list: 734868, 47.156.178.150:50008
INFO 2019-12-08 22:38:38,120 (RIFF_PEER) Peer List Received from Master: 6 peers in this IPSC
INFO 2019-12-08 22:38:38,121 (RIFF_PEER) Peer De-Registration Requested for: 734377
WARNING 2019-12-08 22:38:38,122 (RIFF_PEER) Peer Deleted (not in new peer list): 734377
INFO 2019-12-08 22:38:39,216 (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
WARNING 2019-12-08 22:38:40,537 (RIFF_PEER) PeerError: Peer not in peer-list: 734377, 72.132.11.23:1024
WARNING 2019-12-08 22:38:42,553 (RIFF_PEER) PeerError: Peer not in peer-list: 734868, 47.156.178.150:50008
INFO 2019-12-08 22:38:44,216 (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO 2019-12-08 22:38:44,219 (ALL IPSC SYSTEMS) Rule timer loop started
INFO 2019-12-08 22:38:44,621 (RIFF_PEER) Peer List Received from Master: 6 peers in this IPSC
INFO 2019-12-08 22:38:44,621 (RIFF_PEER) Peer De-Registration Requested for: 734555
WARNING 2019-12-08 22:38:44,622 (RIFF_PEER) Peer Deleted (not in new peer list): 734555
^CINFO 2019-12-08 22:38:46,238 *** DMRLINK IS TERMINATING WITH SIGNAL 2 ***
INFO 2019-12-08 22:38:46,239 (RIFF_PEER) De-Registering self from the IPSC system
INFO 2019-12-08 22:38:46,239 (CARLSBAD) De-Registering self from the IPSC system
INFO 2019-12-08 22:38:46,239 (IBEX) De-Registering self from the IPSC system
INFO 2019-12-08 22:38:46,240 (HB_BRIDGE) De-Registering self from the IPSC system


Re: Linking dmrlink and HBlink3 #dmrlink #hblink

area51now@...
 

The error message your seeing looks like mine when a trbo peer is connected (below is mine) every thing working fine here

ERROR 2019-12-09 04:42:22,977 (Peer-5-XN TS2) Unknown Message - Type: f0 From: 4770 Packet: f0000012a249531000


Bob
'
KB6LED


Re: Linking dmrlink and HBlink3 #dmrlink #hblink

ai6bx
 

After taking a few days off, I am coming back into my config files and trying to understand an error message. Following is the log file when confbridge.py is running. Note one of my peers starts and appears to function fine and I am getting an error on the the second client connection attempts, Carlsbad.

root@AI6BX-DMR:/opt/DMRlink# python confbridge.py
INFO 2019-12-08 22:37:39,737 DMRlink 'dmrlink.py' (c) 2013 - 2015 N0MJS & the K0USY Group - SYSTEM STARTING...
INFO 2019-12-08 22:37:40,755 ID ALIAS MAPPER: 'peer_ids.json' successfully downloaded
INFO 2019-12-08 22:37:42,199 ID ALIAS MAPPER: 'subscriber_ids.json' successfully downloaded
INFO 2019-12-08 22:37:42,359 ID ALIAS MAPPER: peer_ids dictionary is available
INFO 2019-12-08 22:37:44,211 ID ALIAS MAPPER: subscriber_ids dictionary is available
INFO 2019-12-08 22:37:44,214 (RIFF_PEER) IPSC Instance Created: 92374, 0.0.0.0:50001
INFO 2019-12-08 22:37:44,215 (RIFF_PEER) Registering with the Master: 47.180.30.199:7000
INFO 2019-12-08 22:37:44,216 (IBEX) IPSC Instance Created: 734379, 0.0.0.0:62055
INFO 2019-12-08 22:37:44,216 (CARLSBAD) IPSC Instance Created: 92002, 0.0.0.0:62031
INFO 2019-12-08 22:37:44,217 (HB_BRIDGE) IPSC Instance Created: 12345, 0.0.0.0:62050
INFO 2019-12-08 22:37:44,218 Bridge configuration file found and imported
INFO 2019-12-08 22:37:44,218 ACL file not found or invalid - all subscriber IDs are valid
INFO 2019-12-08 22:37:44,218 (ALL IPSC SYSTEMS) Rule timer loop started
WARNING 2019-12-08 22:37:44,737 (RIFF_PEER) PeerError: Peer not in peer-list: 734377, 72.132.11.23:1024
WARNING 2019-12-08 22:37:48,515 (RIFF_PEER) PeerError: Peer not in peer-list: 734868, 47.156.178.150:50008
INFO 2019-12-08 22:37:49,216 (RIFF_PEER) Registering with the Master: 47.180.30.199:7000
WARNING 2019-12-08 22:37:49,226 (RIFF_PEER) Registration response (we requested reg) from the Master: 734379, 47.180.30.199:7000 (7 peers)
WARNING 2019-12-08 22:37:50,748 (RIFF_PEER) PeerError: Peer not in peer-list: 734377, 72.132.11.23:1024
INFO 2019-12-08 22:37:51,308 (CARLSBAD) Master Registration Packet Received from peer 734566, 76.81.231.35:50009
ERROR 2019-12-08 22:37:51,323 (CARLSBAD) Unknown Message - Type: f0 From: 734566 Packet: f0000b356600000000
INFO 2019-12-08 22:37:54,216 (RIFF_PEER), No Peer List - Requesting One From the Master
WARNING 2019-12-08 22:37:54,517 (RIFF_PEER) PeerError: Peer not in peer-list: 734868, 47.156.178.150:50008
WARNING 2019-12-08 22:37:56,747 (RIFF_PEER) PeerError: Peer not in peer-list: 734377, 72.132.11.23:1024
INFO 2019-12-08 22:37:59,215 (RIFF_PEER), No Peer List - Requesting One From the Master
WARNING 2019-12-08 22:37:59,270 (RIFF_PEER) PeerError: Peer not in peer-list: 734, 72.132.11.23:7000
INFO 2019-12-08 22:37:59,419 (RIFF_PEER) Peer List Received from Master: 6 peers in this IPSC
INFO 2019-12-08 22:37:59,508 (RIFF_PEER) Peer Registration Request From: 734, 72.132.11.23:7000
INFO 2019-12-08 22:37:59,670 (RIFF_PEER) Peer Registration Request From: 725123, 72.132.11.23:1051
INFO 2019-12-08 22:38:00,041 (RIFF_PEER) Peer Registration Request From: 734555, 162.248.117.53:7000
INFO 2019-12-08 22:38:00,255 (RIFF_PEER) Peer Registration Request From: 734990, 72.132.11.23:50006
WARNING 2019-12-08 22:38:00,525 (RIFF_PEER) PeerError: Peer not in peer-list: 734868, 47.156.178.150:50008
INFO 2019-12-08 22:38:04,215 (RIFF_PEER) Registering with Peer 734555, 162.248.117.53:7000
INFO 2019-12-08 22:38:04,216 (RIFF_PEER) Registering with Peer 734990, 72.132.11.23:50006
INFO 2019-12-08 22:38:04,216 (RIFF_PEER) Registering with Peer 734377, 72.132.11.23:1024
INFO 2019-12-08 22:38:04,216 (RIFF_PEER) Registering with Peer 725123, 72.132.11.23:1051
INFO 2019-12-08 22:38:04,216 (RIFF_PEER) Registering with Peer 734, 72.132.11.23:7000
INFO 2019-12-08 22:38:04,235 (RIFF_PEER) Registration Reply From: 734555, 162.248.117.53:7000
INFO 2019-12-08 22:38:04,242 (RIFF_PEER) Registration Reply From: 734377, 72.132.11.23:1024
INFO 2019-12-08 22:38:04,247 (RIFF_PEER) Registration Reply From: 725123, 72.132.11.23:1051
INFO 2019-12-08 22:38:04,252 (RIFF_PEER) Registration Reply From: 734990, 72.132.11.23:50006
INFO 2019-12-08 22:38:04,264 (RIFF_PEER) Registration Reply From: 734, 72.132.11.23:7000
ERROR 2019-12-08 22:38:06,322 (CARLSBAD) Unknown Message - Type: f0 From: 734566 Packet: f0000b356648531000
WARNING 2019-12-08 22:38:06,523 (RIFF_PEER) PeerError: Peer not in peer-list: 734868, 47.156.178.150:50008
WARNING 2019-12-08 22:38:12,515 (RIFF_PEER) PeerError: Peer not in peer-list: 734868, 47.156.178.150:50008
WARNING 2019-12-08 22:38:13,135 (RIFF_PEER) PeerError: Peer not in peer-list: 20001, 67.63.96.6:1046
INFO 2019-12-08 22:38:13,271 (RIFF_PEER) Peer List Received from Master: 7 peers in this IPSC
INFO 2019-12-08 22:38:13,430 (RIFF_PEER) Peer Registration Request From: 20001, 67.63.96.6:1046
INFO 2019-12-08 22:38:14,216 (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
WARNING 2019-12-08 22:38:18,517 (RIFF_PEER) PeerError: Peer not in peer-list: 734868, 47.156.178.150:50008
INFO 2019-12-08 22:38:19,216 (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO 2019-12-08 22:38:20,322 (RIFF_PEER) Peer List Received from Master: 7 peers in this IPSC
ERROR 2019-12-08 22:38:21,322 (CARLSBAD) Unknown Message - Type: f0 From: 734566 Packet: f0000b35664e531000
INFO 2019-12-08 22:38:24,216 (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
WARNING 2019-12-08 22:38:24,535 (RIFF_PEER) PeerError: Peer not in peer-list: 734868, 47.156.178.150:50008
INFO 2019-12-08 22:38:29,216 (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
WARNING 2019-12-08 22:38:30,690 (RIFF_PEER) PeerError: Peer not in peer-list: 734868, 47.156.178.150:50008
INFO 2019-12-08 22:38:31,421 (RIFF_PEER) Peer List Received from Master: 7 peers in this IPSC
INFO 2019-12-08 22:38:34,216 (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO 2019-12-08 22:38:34,721 (RIFF_PEER) Peer List Received from Master: 7 peers in this IPSC
ERROR 2019-12-08 22:38:36,322 (CARLSBAD) Unknown Message - Type: f0 From: 734566 Packet: f0000b356674531000
WARNING 2019-12-08 22:38:36,518 (RIFF_PEER) PeerError: Peer not in peer-list: 734868, 47.156.178.150:50008
INFO 2019-12-08 22:38:38,120 (RIFF_PEER) Peer List Received from Master: 6 peers in this IPSC
INFO 2019-12-08 22:38:38,121 (RIFF_PEER) Peer De-Registration Requested for: 734377
WARNING 2019-12-08 22:38:38,122 (RIFF_PEER) Peer Deleted (not in new peer list): 734377
INFO 2019-12-08 22:38:39,216 (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
WARNING 2019-12-08 22:38:40,537 (RIFF_PEER) PeerError: Peer not in peer-list: 734377, 72.132.11.23:1024
WARNING 2019-12-08 22:38:42,553 (RIFF_PEER) PeerError: Peer not in peer-list: 734868, 47.156.178.150:50008
INFO 2019-12-08 22:38:44,216 (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO 2019-12-08 22:38:44,219 (ALL IPSC SYSTEMS) Rule timer loop started
INFO 2019-12-08 22:38:44,621 (RIFF_PEER) Peer List Received from Master: 6 peers in this IPSC
INFO 2019-12-08 22:38:44,621 (RIFF_PEER) Peer De-Registration Requested for: 734555
WARNING 2019-12-08 22:38:44,622 (RIFF_PEER) Peer Deleted (not in new peer list): 734555
^CINFO 2019-12-08 22:38:46,238 *** DMRLINK IS TERMINATING WITH SIGNAL 2 ***
INFO 2019-12-08 22:38:46,239 (RIFF_PEER) De-Registering self from the IPSC system
INFO 2019-12-08 22:38:46,239 (CARLSBAD) De-Registering self from the IPSC system
INFO 2019-12-08 22:38:46,239 (IBEX) De-Registering self from the IPSC system
INFO 2019-12-08 22:38:46,240 (HB_BRIDGE) De-Registering self from the IPSC system


Re: Linking dmrlink and HBlink3 #dmrlink #hblink

ai6bx
 

Cort,

Do you by chance have any suggestions after the log report of my last post?

thank you,

keith


Re: Bad audio from analog_bridge

Philippe, f5rvx
 

and how to run usrpaudio.py from systemd ?

I created the service "usrpaudio.service" in which I noted:
ExecStart = /opt/Analog_Bridge/./USRPAudio.py -s> / dev / null 2> & 1
User = root

And I get the following errors:
Dec 2 23:47:43 localhost USRPAudio.py [598]: File "/opt/Analog_Bridge/./USRPAudio.py", line 164, in <module>
Dec 2 23:47:43 localhost USRPAudio.py [598]: ch = getch ()
Dec 2 23:47:43 localhost USRPAudio.py [598]: File "/opt/Analog_Bridge/./USRPAudio.py", line 145, in _getch
Dec 2 23:47:43 localhost USRPAudio.py [598]: old_settings = termios.tcgetattr (fd)
Dec 2 23:47:43 localhost USRPAudio.py [598]: termios.error: (25, 'Inappropriate ioctl for device')


Thank you so much.
Philippe

Le 04/12/2019 à 20:33, Steve N4IRS a écrit :

Glad to hear it. That's what usrpaudio.py is for.
You might want to post your command line so others can learn from it.

73, Steve N4IRS

On 12/4/2019 2:31 PM, JF via Groups.Io wrote:
Works perfect with usrpaudio.py thanks!


Re: Bad audio from analog_bridge

Patrick Perdue
 

If you can get raw PCM to stdout, you can pipe that audio to lame, then pipe lame to ezstream. No sound card, virtual or otherwise, required. You could perhaps do this with ffmpeg as well. Going the Darkice and loopback device will work if needed, too. This is how I have streamed output from op25 on a Raspberry Pi.


Re: Bad audio from analog_bridge

JF
 

Ok I see. I did’t work on that part yet but I plan to use darkice as broadcast feed.
 
I think I’ll need to install a virtual sound card and then pipe the audio into darkice.


Re: Bad audio from analog_bridge

Steve N4IRS
 

OK,
I thought you were planning to send the audio to Broadcastify.

Steve

On 12/4/19 10:08 PM, JF via Groups.Io wrote:
Hi Steve, I’m not sure what command line you are talking about.
 
My setup is:
BM<>mmdvm_bridge<>analog_bridge<>usrpaudio.py
 
Here is the command, I run those manually to monitor them.

./MMDVM_Bridge
./Analog_Bridge
./md380-emu
./USRPaudio.py
 
Usrpaudio.py throws a couple of error at launch but it works
 
Actually I run this on a debian virtual machine on my laptop, at the end I plan to run this on aws where there is no sound card so I think I’ll have a another funny troubleshooting weed-end :)


Re: Bad audio from analog_bridge

JF
 

Hi Steve, I’m not sure what command line you are talking about.
 
My setup is:
BM<>mmdvm_bridge<>analog_bridge<>usrpaudio.py
 
Here is the command, I run those manually to monitor them.

./MMDVM_Bridge
./Analog_Bridge
./md380-emu
./USRPaudio.py
 
Usrpaudio.py throws a couple of error at launch but it works
 
Actually I run this on a debian virtual machine on my laptop, at the end I plan to run this on aws where there is no sound card so I think I’ll have a another funny troubleshooting weed-end :)


Re: Bad audio from analog_bridge

Steve N4IRS
 

Glad to hear it. That's what usrpaudio.py is for.
You might want to post your command line so others can learn from it.

73, Steve N4IRS

On 12/4/2019 2:31 PM, JF via Groups.Io wrote:
Works perfect with usrpaudio.py thanks!

4621 - 4640 of 10066