Date   

Re: Minor coredump in MMDVM_Bridge when there is a typo in the config

Steve KC1AWV
 

Where's the indication of a core dump?


On Sun, Jun 2, 2019, 10:36 PM David Ranch <dvswitch-groupsio@...> wrote:

Hello Everyone,

David KI6ZHD here and I'm on the final stages of following the https://docs.google.com/document/d/1eN50Csr29eAprBu7eKA0Bfa2XUcsXw5iktY1Ey-Qjkg/edit documentation to bring up a ASL <-> DMR link.  I happened to make a small typo in the MMDVM_Bridge.ini config:

was:
   [DMR Network]
   ddress=3108.repeater.net

should be:

   [DMR Network]
   Address=3108.repeater.net


and when trying to start the MMDVM_Bridge program, it core dumped:
--
[root@ww6bay-asl MMDVM_Bridge]# /opt/MMDVM_Bridge/MMDVM_Bridge /opt/MMDVM_Bridge/MMDVM_Bridge.ini    
I: 2019-06-03 00:10:16.154 MMDVM_Bridge:                                                             
I: 2019-06-03 00:10:16.154 Portions Copyright (C) 2018 DVSwitch, INAD.                               
I: 2019-06-03 00:10:16.154 Hacks by Mike N4IRR and Steve N4IRS                                       
I: 2019-06-03 00:10:16.154 =                         
I: 2019-06-03 00:15:01.292 This software is for use on amateur radio networks only,             
I: 2019-06-03 00:15:01.292 it is to be used for educational purposes only. Its use on           
I: 2019-06-03 00:15:01.292 commercial networks is strictly prohibited.                          
I: 2019-06-03 00:15:01.292 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others          
M: 2019-06-03 00:15:01.292 MMDVM_Bridge-20180423 is starting                                    
M: 2019-06-03 00:15:01.292 Built 19:26:19 Jul 26 2018 (GitID #903ae69)                          
I: 2019-06-03 00:15:01.292 General Parameters                                                   
I: 2019-06-03 00:15:01.292     Callsign: WW6BAY                                                 
I: 2019-06-03 00:15:01.292     Id: 11068301                                                     
I: 2019-06-03 00:15:01.293     Duplex: no                                                       
I: 2019-06-03 00:15:01.293     Timeout: 180s                                                    
I: 2019-06-03 00:15:01.293     D-Star: disabled                                                 
I: 2019-06-03 00:15:01.293     DMR: enabled                                                     
I: 2019-06-03 00:15:01.293     YSF: disabled                                                    
I: 2019-06-03 00:15:01.293     P25: disabled                                                    
I: 2019-06-03 00:15:01.293     NXDN: disabled                                                   
I: 2019-06-03 00:15:01.293 Modem Parameters                                                     
I: 2019-06-03 00:15:01.293     Port: /dev/null                                                  
I: 2019-06-03 00:15:01.293     RX Invert: no                                                    
I: 2019-06-03 00:15:01.293     TX Invert: no                                                    
I: 2019-06-03 00:15:01.293     PTT Invert: no                                                   
I: 2019-06-03 00:15:01.294     TX Delay: 100ms                                                  
I: 2019-06-03 00:15:01.294     RX Offset: 0Hz                                                   
I: 2019-06-03 00:15:01.294     TX Offset: 0Hz                                                   
I: 2019-06-03 00:15:01.294     RX DC Offset: 0                                                  
I: 2019-06-03 00:15:01.294     TX DC Offset: 0                                                  
I: 2019-06-03 00:15:01.294     RF Level: 100.0%                                                 
I: 2019-06-03 00:15:01.294     DMR Delay: 0 (0.0ms)                                             
I: 2019-06-03 00:15:01.294     RX Level: 50.0%                                                  
I: 2019-06-03 00:15:01.295     CW Id TX Level: 50.0%                                            
I: 2019-06-03 00:15:01.295     D-Star TX Level: 50.0%                                           
I: 2019-06-03 00:15:01.295     DMR TX Level: 50.0%                                              
I: 2019-06-03 00:15:01.295     YSF TX Level: 50.0%                                              
I: 2019-06-03 00:15:01.295     P25 TX Level: 50.0%                                              
I: 2019-06-03 00:15:01.295     NXDN TX Level: 50.0%                                             
I: 2019-06-03 00:15:01.295     RX Frequency: 222340000Hz (222340000Hz)                          
I: 2019-06-03 00:15:01.295     TX Frequency: 224940000Hz (224940000Hz)                          
M: 2019-06-03 00:15:01.296 Opening the MMDVM                                                    
I: 2019-06-03 00:15:01.296 Display Parameters                                                   
I: 2019-06-03 00:15:01.296     Type:                                                            
I: 2019-06-03 00:15:01.296 DMR Network Parameters                                               
I: 2019-06-03 00:15:01.296     Address: 3108.repeater.net                                       
I: 2019-06-03 00:15:01.296     Port: 62031                                                      
I: 2019-06-03 00:15:01.296     Local: 62032                                                     
I: 2019-06-03 00:15:01.297     Jitter: 360ms                                                    
I: 2019-06-03 00:15:01.297     Slot 1: disabled                                                 
I: 2019-06-03 00:15:01.297     Slot 2: enabled                                                  
I: 2019-06-03 00:15:01.297     Mode Hang: 3s                                                    
I: 2019-06-03 00:15:01.475 Info Parameters                                                      
I: 2019-06-03 00:15:01.476     Callsign: WW6BAY                                                 
I: 2019-06-03 00:15:01.476     RX Frequency: 222340000Hz                                        
I: 2019-06-03 00:15:01.476     TX Frequency: 224940000Hz                                        
I: 2019-06-03 00:15:01.476     Power: 1W                                                        
I: 2019-06-03 00:15:01.476     Latitude: 41.733299deg N                                         
I: 2019-06-03 00:15:01.476     Longitude: -50.399899deg E                                       
I: 2019-06-03 00:15:01.476     Height: 0m                                                       
I: 2019-06-03 00:15:01.476     Location: "Iceberg, North Atlantic"                              
I: 2019-06-03 00:15:01.476     Description: "MMDVM_Bridge"                                      
I: 2019-06-03 00:15:01.476     URL: "https://groups.io/g/DVSwitch"                              
M: 2019-06-03 00:15:01.476 DMR, Opening DMR Network                                             
I: 2019-06-03 00:15:01.476 RSSI                                                                 
I: 2019-06-03 00:15:01.476     Mapping File: RSSI.dat
W: 2019-06-03 00:15:01.476 Cannot open the RSSI data file - RSSI.dat
I: 2019-06-03 00:15:01.476 DMR Id Lookups
I: 2019-06-03 00:15:01.476     File: /var/lib/mmdvm/DMRIds.dat
I: 2019-06-03 00:15:01.476     Reload: 24 hours
I: 2019-06-03 00:15:01.997 Loaded 96141 Ids to the DMR callsign lookup table
I: 2019-06-03 00:15:01.997 DMR RF Parameters
I: 2019-06-03 00:15:01.997     Id: 11068301
I: 2019-06-03 00:15:01.997     Color Code: 1
I: 2019-06-03 00:15:01.997     Self Only: no
I: 2019-06-03 00:15:01.997     Embedded LC Only: yes
I: 2019-06-03 00:15:01.997     Dump Talker Alias Data: no
I: 2019-06-03 00:15:01.997     Prefixes: 0
I: 2019-06-03 00:15:01.997     Call Hang: 3s
I: 2019-06-03 00:15:01.997     TX Hang: 3s
I: 2019-06-03 00:15:01.997     Mode Hang: 10s
M: 2019-06-03 00:15:01.997 DMR, Opening INI file: DVSwitch.ini
M: 2019-06-03 00:15:01.998 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2019-06-03 00:15:01.998 DMR, Setting [DMR] TXPort -> 31100
M: 2019-06-03 00:15:01.998 DMR, Setting [DMR] RXPort -> 31103
M: 2019-06-03 00:15:01.998 DMR, Setting [DMR] Slot -> 2
M: 2019-06-03 00:15:01.998 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
M: 2019-06-03 00:15:01.998 MMDVM_Bridge-20180423 is running
I: 2019-06-03 00:15:01.998 Started the DMR Id lookup reload thread
D: 2019-06-03 00:15:12.063 DMR, Sending authorisation
D: 2019-06-03 00:15:12.130 DMR, Sending configuration
M: 2019-06-03 00:15:12.196 DMR, Logged into the master successfully
^CM: 2019-06-03 01:05:40.041 Closing the MMDVM
I: 2019-06-03 01:05:40.219 Stopped the DMR Id lookup reload thread
M: 2019-06-03 01:05:40.219 DMR, Closing DMR Network
I: 2019-06-03 01:05:40.219 MMDVM_Bridge-20180423 exited on receipt of SIGINT
--


I thought I'd report the error since a program should ideally never coredump

--David
KI6ZHD


Minor coredump in MMDVM_Bridge when there is a typo in the config

David Ranch
 


Hello Everyone,

David KI6ZHD here and I'm on the final stages of following the https://docs.google.com/document/d/1eN50Csr29eAprBu7eKA0Bfa2XUcsXw5iktY1Ey-Qjkg/edit documentation to bring up a ASL <-> DMR link.  I happened to make a small typo in the MMDVM_Bridge.ini config:

was:
   [DMR Network]
   ddress=3108.repeater.net

should be:

   [DMR Network]
   Address=3108.repeater.net


and when trying to start the MMDVM_Bridge program, it core dumped:
--
[root@ww6bay-asl MMDVM_Bridge]# /opt/MMDVM_Bridge/MMDVM_Bridge /opt/MMDVM_Bridge/MMDVM_Bridge.ini    
I: 2019-06-03 00:10:16.154 MMDVM_Bridge:                                                             
I: 2019-06-03 00:10:16.154 Portions Copyright (C) 2018 DVSwitch, INAD.                               
I: 2019-06-03 00:10:16.154 Hacks by Mike N4IRR and Steve N4IRS                                       
I: 2019-06-03 00:10:16.154 =                         
I: 2019-06-03 00:15:01.292 This software is for use on amateur radio networks only,             
I: 2019-06-03 00:15:01.292 it is to be used for educational purposes only. Its use on           
I: 2019-06-03 00:15:01.292 commercial networks is strictly prohibited.                          
I: 2019-06-03 00:15:01.292 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others          
M: 2019-06-03 00:15:01.292 MMDVM_Bridge-20180423 is starting                                    
M: 2019-06-03 00:15:01.292 Built 19:26:19 Jul 26 2018 (GitID #903ae69)                          
I: 2019-06-03 00:15:01.292 General Parameters                                                   
I: 2019-06-03 00:15:01.292     Callsign: WW6BAY                                                 
I: 2019-06-03 00:15:01.292     Id: 11068301                                                     
I: 2019-06-03 00:15:01.293     Duplex: no                                                       
I: 2019-06-03 00:15:01.293     Timeout: 180s                                                    
I: 2019-06-03 00:15:01.293     D-Star: disabled                                                 
I: 2019-06-03 00:15:01.293     DMR: enabled                                                     
I: 2019-06-03 00:15:01.293     YSF: disabled                                                    
I: 2019-06-03 00:15:01.293     P25: disabled                                                    
I: 2019-06-03 00:15:01.293     NXDN: disabled                                                   
I: 2019-06-03 00:15:01.293 Modem Parameters                                                     
I: 2019-06-03 00:15:01.293     Port: /dev/null                                                  
I: 2019-06-03 00:15:01.293     RX Invert: no                                                    
I: 2019-06-03 00:15:01.293     TX Invert: no                                                    
I: 2019-06-03 00:15:01.293     PTT Invert: no                                                   
I: 2019-06-03 00:15:01.294     TX Delay: 100ms                                                  
I: 2019-06-03 00:15:01.294     RX Offset: 0Hz                                                   
I: 2019-06-03 00:15:01.294     TX Offset: 0Hz                                                   
I: 2019-06-03 00:15:01.294     RX DC Offset: 0                                                  
I: 2019-06-03 00:15:01.294     TX DC Offset: 0                                                  
I: 2019-06-03 00:15:01.294     RF Level: 100.0%                                                 
I: 2019-06-03 00:15:01.294     DMR Delay: 0 (0.0ms)                                             
I: 2019-06-03 00:15:01.294     RX Level: 50.0%                                                  
I: 2019-06-03 00:15:01.295     CW Id TX Level: 50.0%                                            
I: 2019-06-03 00:15:01.295     D-Star TX Level: 50.0%                                           
I: 2019-06-03 00:15:01.295     DMR TX Level: 50.0%                                              
I: 2019-06-03 00:15:01.295     YSF TX Level: 50.0%                                              
I: 2019-06-03 00:15:01.295     P25 TX Level: 50.0%                                              
I: 2019-06-03 00:15:01.295     NXDN TX Level: 50.0%                                             
I: 2019-06-03 00:15:01.295     RX Frequency: 222340000Hz (222340000Hz)                          
I: 2019-06-03 00:15:01.295     TX Frequency: 224940000Hz (224940000Hz)                          
M: 2019-06-03 00:15:01.296 Opening the MMDVM                                                    
I: 2019-06-03 00:15:01.296 Display Parameters                                                   
I: 2019-06-03 00:15:01.296     Type:                                                            
I: 2019-06-03 00:15:01.296 DMR Network Parameters                                               
I: 2019-06-03 00:15:01.296     Address: 3108.repeater.net                                       
I: 2019-06-03 00:15:01.296     Port: 62031                                                      
I: 2019-06-03 00:15:01.296     Local: 62032                                                     
I: 2019-06-03 00:15:01.297     Jitter: 360ms                                                    
I: 2019-06-03 00:15:01.297     Slot 1: disabled                                                 
I: 2019-06-03 00:15:01.297     Slot 2: enabled                                                  
I: 2019-06-03 00:15:01.297     Mode Hang: 3s                                                    
I: 2019-06-03 00:15:01.475 Info Parameters                                                      
I: 2019-06-03 00:15:01.476     Callsign: WW6BAY                                                 
I: 2019-06-03 00:15:01.476     RX Frequency: 222340000Hz                                        
I: 2019-06-03 00:15:01.476     TX Frequency: 224940000Hz                                        
I: 2019-06-03 00:15:01.476     Power: 1W                                                        
I: 2019-06-03 00:15:01.476     Latitude: 41.733299deg N                                         
I: 2019-06-03 00:15:01.476     Longitude: -50.399899deg E                                       
I: 2019-06-03 00:15:01.476     Height: 0m                                                       
I: 2019-06-03 00:15:01.476     Location: "Iceberg, North Atlantic"                              
I: 2019-06-03 00:15:01.476     Description: "MMDVM_Bridge"                                      
I: 2019-06-03 00:15:01.476     URL: "https://groups.io/g/DVSwitch"                              
M: 2019-06-03 00:15:01.476 DMR, Opening DMR Network                                             
I: 2019-06-03 00:15:01.476 RSSI                                                                 
I: 2019-06-03 00:15:01.476     Mapping File: RSSI.dat
W: 2019-06-03 00:15:01.476 Cannot open the RSSI data file - RSSI.dat
I: 2019-06-03 00:15:01.476 DMR Id Lookups
I: 2019-06-03 00:15:01.476     File: /var/lib/mmdvm/DMRIds.dat
I: 2019-06-03 00:15:01.476     Reload: 24 hours
I: 2019-06-03 00:15:01.997 Loaded 96141 Ids to the DMR callsign lookup table
I: 2019-06-03 00:15:01.997 DMR RF Parameters
I: 2019-06-03 00:15:01.997     Id: 11068301
I: 2019-06-03 00:15:01.997     Color Code: 1
I: 2019-06-03 00:15:01.997     Self Only: no
I: 2019-06-03 00:15:01.997     Embedded LC Only: yes
I: 2019-06-03 00:15:01.997     Dump Talker Alias Data: no
I: 2019-06-03 00:15:01.997     Prefixes: 0
I: 2019-06-03 00:15:01.997     Call Hang: 3s
I: 2019-06-03 00:15:01.997     TX Hang: 3s
I: 2019-06-03 00:15:01.997     Mode Hang: 10s
M: 2019-06-03 00:15:01.997 DMR, Opening INI file: DVSwitch.ini
M: 2019-06-03 00:15:01.998 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2019-06-03 00:15:01.998 DMR, Setting [DMR] TXPort -> 31100
M: 2019-06-03 00:15:01.998 DMR, Setting [DMR] RXPort -> 31103
M: 2019-06-03 00:15:01.998 DMR, Setting [DMR] Slot -> 2
M: 2019-06-03 00:15:01.998 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
M: 2019-06-03 00:15:01.998 MMDVM_Bridge-20180423 is running
I: 2019-06-03 00:15:01.998 Started the DMR Id lookup reload thread
D: 2019-06-03 00:15:12.063 DMR, Sending authorisation
D: 2019-06-03 00:15:12.130 DMR, Sending configuration
M: 2019-06-03 00:15:12.196 DMR, Logged into the master successfully
^CM: 2019-06-03 01:05:40.041 Closing the MMDVM
I: 2019-06-03 01:05:40.219 Stopped the DMR Id lookup reload thread
M: 2019-06-03 01:05:40.219 DMR, Closing DMR Network
I: 2019-06-03 01:05:40.219 MMDVM_Bridge-20180423 exited on receipt of SIGINT
--


I thought I'd report the error since a program should ideally never coredump

--David
KI6ZHD


Fusion to dmr and allstar #dmrlink

Raul cruz <rcw3023@...>
 

I'm trying to set up my repeater DR-1x and my wires-x fusion repeater to be linked with the DMR in all star .with my YSF reflector and All Star .I'm running the Dvmini dongle Raspberry Pi 3 currently  the reflector is working with my repeater but have not being able to link with Dmr and all star. Can please someone  help me to how to set up  the dvswitch .so can link the repeater with .
Also the Raspberry is running  Raspian stretch 
Thanks  for any help 
Rcw3023 


Various DmrLink/HBlink questions.

KK4zmg
 

Hi,
I Have Been running HBlink3(x2),DMR_Bridge and DMRlink.

I have them all running in separate docker ubuntu lockers.
            
                                                                                         (Brandmiester)
                                                                                                   |
(Hot Spots MMDVM)----<HBlink3 bridge.py>-----------<Hblink3 bridge.py>-----------<DMR_Bridge>---------------<DMRlink>---------------(moto xpr8300)
                                                                                                                                                                                     \
                                                                                                                                                                                       \--------------------(moto xpr8400)    
I'm running to separate versions of HBlink3 to be able to switch the TG from the hot spots from TG2 to TG1 for everything else.

Question 1, Is it normal to have to do it this way, run each instants in a separate machine/container. It seams like reading the info and the forums that the programs should be able to run on one machine.

Question 2, The moto xpr8300 connects just fine and worked no issues. The moto xpr8400 connects but i get an error
Unknown Message - Type:f0 From:"Repeater number" Packet: f0002fbe1600000000

Any ideas?
Are there better ways of implementing this kind of setup? 

Thanks in advance

Richard
KK4zmg


Re: ALLSTAR to DMR Bridge

Brett KB5YZB
 

Steve, just checking back in; with what you provided can I move to try to install the bridge? I may need your help...But I will try first....:)

Thanks Steve.  


Re: ysf2dmr Network watchdog has expired

Dexter Harroo
 

Thanks for your response, will check ports


On Thu, May 30, 2019 at 11:42 AM Steve KC1AWV <smiller@...> wrote:
The YSF2DMR program is not part of DVSwitch, it is a separate program developed by someone else. Not sure if you'll get much help here for it. However, from previous experience with other network watchdog issues, I would first check to make sure YSF2DMR is not trying to use ports that are in use by other programs.



--
73
9Y4C
Dexter Harroo


Re: ysf2dmr Network watchdog has expired

Steve KC1AWV
 

The YSF2DMR program is not part of DVSwitch, it is a separate program developed by someone else. Not sure if you'll get much help here for it. However, from previous experience with other network watchdog issues, I would first check to make sure YSF2DMR is not trying to use ports that are in use by other programs.


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

Tom Corcoran
 

Hello Steve, just to be clear on all the suggested changes, can you please post your final/working MMDVM_Bridge.ini and Analog_Bridge.ini files
--
tnx so much … Tom VE3NY


Re: YSF/DMR/Allstar #mmdvm_bridge

Steve KC1AWV
 

I am unsure of the terminology used on YSF (I'm still pretty new to that concept) but by room, do you mean reflector?

MMDVM_Bridge.ini

[System Fusion Network]
Enable=0
LocalAddress=0
LocalPort=3200
GatewayAddress=ysfreflector.dvswitch.org <-- this is the address for the Reflector
GatewayPort=42166 <-- this is the port that the Reflector is listening to
Debug=0

That being said, I can go through how I have it set up at ERDN.

First, I am using HBlink3 as the "hub", which performs all the call routing and bridging for me.
Second, I have ASL connected to Analog_Bridge, md380_emu, and MMDVM_Bridge. MMDVM_Bridge connects to HBlink, and Analog_Bridge sends calls to TG2.
Third, I have HBlink connected to Brandmeister as a Peer (for now). This connects calls on the bridge to a TG on Brandmeister that uses my DMR ID.
Fourth, I have YSF2DMR connected to my YSF Reflector, and MMDVM_Bridge. MMDVM_Bridge connects to HBlink and uses TG2.
Fifth, I am working on getting my XLX reflector in the mix to provide D-Star support.

So, those components are running on a few different VMs located on some hardware I have colocated in Chicago. One runs ASL, another XLX and YSFReflector, and a third HBlink3. I separate them out, well, because that's how I do it at work. Each server has its own tasks.
HBlink runs, HBlink of course.
ASL also runs the DVSwitch programs for getting onto the HBlink server.
XLX/YSF also runs the YSF2DMR program for getting onto the HBlink server.

Can these components be run all on one system? Yes. I run them separately so that if one part goes offline, the whole system doesn't go kaput. The most important system for me is the HBlink server, reason being so that even if my ASL, BM or YSF links go offline, others can still connect and work.

It really boils down to your own use case and risk assessment.
Are you setting up a network for your own use and can handle it going offline for any reason possible? Then running it on one system will be fine.
Are you running a network that will be handling multiple users, providing connections for multiple modes, and need a more agile system? Then running components separately would be better.

That's my two cents :)

Steve KC1AWV


ysf2dmr Network watchdog has expired

Dexter Harroo
 

Hi all, I had ysf2dmr successfully running on my system, today I have Network watchdog has expired when transmission is made, can anyone shed some light on this issue hopefully a fix?


YSF/DMR/Allstar #mmdvm_bridge

Mark Johnston
 

What is the best way to bridge all three on one system, or would it be better to split that task? I am trying to bridge a YSF room (my own) with DMR TG, and Allstar Node. I see in the ini file it has DMR settings, but nothing for how to join a specific room on ysf... it would seem... looking at MMDVM_Bridge.ini and DVswitch.ini...

I have successfully bridged DMR and Allstar, so far working very well...


Thanks,

Mark


Low Mic Audio From Android Phone

Rob K7TGU
 

I originally posted this inquiry to the [allstarlink] group, however, it may have been more appropriate to post it here.
 
Is there a means to boost the microphone audio from the phone? Both the DVSwitch transmit and receive levels are at the max. The receive level is acceptable, however, the transmit is not. I've insured the phone mic port is clear along with disabling the noise reduction (Samsung Galaxy S5) and insuring voice call is not checked in DVSwitch. Played around with the transmit level slider reducing the level and saving incrementally and the reverse of that process. The mic audio level does decrease and increase as you might expect, but not to the point where it is acceptable. No complaints of low audio or audio quality with normal phone usage. Any thoughts?
 
Rob


Re: ALLSTAR to DMR Bridge

Brett KB5YZB
 

Steve, thanks for the help on this. so I'm ready to start with your instructions? If so I will give it a try and see if I can make it work tonight. If I run into problems; if I may, call you for guidance at your convenience....


Brett
KB5YZB


Re: “Blocked” from a hotspot?

Mike KB8JNM
 

There is a min tx time in the pistar software under the advanced/dmr if you look for it and know it is the problem.

But I would advise against adjusting parameters from the default unless you clearly know better.

2 or 3 wireless connections (if it's on wireless) and you can have errors from the packet collisions.

Many other network things can create a issue like that and give the appearance of short keying.

On 5/27/2019 1:06 PM, Chris WB4ULK via Groups.Io wrote:
I got a call from a friend last night. He said his buddy was getting the “Blocked” message.
The thing is, the guy is on a hotspot.
You guys ever heard of THAT? 
Is there a delay you can set in PiStar?

I told him it might be his internet connection dropping in and out tripping it, but I have no idea.

Any thoughts?

Chris


Re: “Blocked” from a hotspot?

Chris WB4ULK
 

Yeah, I am suspicious of the dropping connection.
I just wanted to make sure there was no delay setting somewhere in PiStar like in the Bridge software.

Thanks Corey,
Chris


Re: “Blocked” from a hotspot?

Corey Dean N3FE <n3fe@...>
 

That is a BrandMeister thing.  That means the network either detected him looping, key keyed up 5 times quickly, or his connection kept dropping constantly.

It auto in-blocks in a hour.

Corey n3fe

On Mon, May 27, 2019 at 1:06 PM Chris WB4ULK via Groups.Io <chood73=yahoo.com@groups.io> wrote:
I got a call from a friend last night. He said his buddy was getting the “Blocked” message.
The thing is, the guy is on a hotspot.
You guys ever heard of THAT? 
Is there a delay you can set in PiStar?

I told him it might be his internet connection dropping in and out tripping it, but I have no idea.

Any thoughts?

Chris


“Blocked” from a hotspot?

Chris WB4ULK
 

I got a call from a friend last night. He said his buddy was getting the “Blocked” message.
The thing is, the guy is on a hotspot.
You guys ever heard of THAT? 
Is there a delay you can set in PiStar?

I told him it might be his internet connection dropping in and out tripping it, but I have no idea.

Any thoughts?

Chris


Re: Dv switch link

Mike KB8JNM
 

My example was not exactly correct because I have many in my set-up and the context was not paired correctly.

sorry

In extensions.conf

[iax-client]                ; for IAX VIOP clients.           <-------------------    
exten => ${NODE},1,Ringing
exten => ${NODE},n,Wait(3)
exten => ${NODE},n,Answer
exten => ${NODE},n,Set(NODENUM=${CALLERID(number)})
exten => ${NODE},n,Playback(rpt/node|noanswer)
exten => ${NODE},n,SayDigits(${EXTEN})
exten => ${NODE},n,Set(CALLERID(num)=0)
exten => ${NODE},n,Rpt,${NODE}|P|${CALLERID(name)}
exten => ${NODE},n,Hangup
exten => ${NODE},n(hangit),Answer
exten => ${NODE},n(hangit),Wait(1)
exten => ${NODE},n(hangit),Hangup

in iax.conf

[iax-user]                        
type = friend                         ; Notice type here is friend <--------------
context = iax-client                  ; Context to jump to in extensions.conf
auth = md5
secret = pasword*
host = dynamic
disallow = all
allow = ulaw
allow = adpcm
allow = gsm
notransfer = yes

Please note that the callsign will need to be used in the app and will announce the connection when complete using this method.

On 5/27/2019 10:36 AM, Mike KB8JNM wrote:

In extensions.conf

[iax-user]                ; for IAX VIOP clients.               
exten => ${NODE},1,Ringing
exten => ${NODE},n,Wait(3)
exten => ${NODE},n,Answer
exten => ${NODE},n,Set(NODENUM=${CALLERID(number)})
exten => ${NODE},n,Playback(rpt/node|noanswer)
exten => ${NODE},n,SayDigits(${EXTEN})
exten => ${NODE},n,Set(CALLERID(num)=0)
exten => ${NODE},n,Rpt,${NODE}|P|${CALLERID(name)}
exten => ${NODE},n,Hangup
exten => ${NODE},n(hangit),Answer
exten => ${NODE},n(hangit),Wait(1)
exten => ${NODE},n(hangit),Hangup


in iax.conf

[iax-user]                        
type = friend                         ; Notice type here is friend <--------------
context = iax-client                  ; Context to jump to in extensions.conf
auth = md5
secret = pasword*
host = dynamic
disallow = all
allow = ulaw
allow = adpcm
allow = gsm
notransfer = yes

Please note that the callsign will need to be used in the app and will announce the connection when complete using this method.


On 5/27/2019 10:21 AM, Mahefuze Moosa wrote:
I want to get dvswitch to work on my android phone i was told if correct I need to set it up first on my pc which I don't have a clue to do it.
Thank you 

On Mon, 27 May 2019, 15:17 Steve KC1AWV, <smiller@...> wrote:
You'll have to be a little more specific as to what you want to accomplish. There are a lot of docs in the wiki that can get you started.

On Mon, May 27, 2019 at 10:00 AM Mahefuze Moosa <mahefuze@...> wrote:
Hello can anyone give me a link to set this up on my pc before I set it up on my android phone.
Thank you
VU3ZPT


--
Steve Miller
KC1AWV


Re: Dv switch link

Mike KB8JNM
 

In extensions.conf

[iax-user]                ; for IAX VIOP clients.               
exten => ${NODE},1,Ringing
exten => ${NODE},n,Wait(3)
exten => ${NODE},n,Answer
exten => ${NODE},n,Set(NODENUM=${CALLERID(number)})
exten => ${NODE},n,Playback(rpt/node|noanswer)
exten => ${NODE},n,SayDigits(${EXTEN})
exten => ${NODE},n,Set(CALLERID(num)=0)
exten => ${NODE},n,Rpt,${NODE}|P|${CALLERID(name)}
exten => ${NODE},n,Hangup
exten => ${NODE},n(hangit),Answer
exten => ${NODE},n(hangit),Wait(1)
exten => ${NODE},n(hangit),Hangup


in iax.conf

[iax-user]                        
type = friend                         ; Notice type here is friend <--------------
context = iax-client                  ; Context to jump to in extensions.conf
auth = md5
secret = pasword*
host = dynamic
disallow = all
allow = ulaw
allow = adpcm
allow = gsm
notransfer = yes

Please note that the callsign will need to be used in the app and will announce the connection when complete using this method.


On 5/27/2019 10:21 AM, Mahefuze Moosa wrote:
I want to get dvswitch to work on my android phone i was told if correct I need to set it up first on my pc which I don't have a clue to do it.
Thank you 

On Mon, 27 May 2019, 15:17 Steve KC1AWV, <smiller@...> wrote:
You'll have to be a little more specific as to what you want to accomplish. There are a lot of docs in the wiki that can get you started.

On Mon, May 27, 2019 at 10:00 AM Mahefuze Moosa <mahefuze@...> wrote:
Hello can anyone give me a link to set this up on my pc before I set it up on my android phone.
Thank you
VU3ZPT


--
Steve Miller
KC1AWV


Re: Dv switch link

Walter
 

Everything you needed was in this email…

 

<<<<>>>> 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Phil, G7OEA
Sent: Sunday, May 12, 2019 7:05 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Dv switch

 

[Edited Message Follows]

Hi Mayfuse, 
As Steve said you need to set up an allstar node. 

To do this you first need to apply for a node number from allstar link. once you have that you need to create a server on the allstar link page and then associate your node number to that server. 

As this is your first node don't change the iax port that is suggested on the server setup page.  make a note of the iax port node number and node password.

to build the node you will need a raspberry pi, a SD card and an allstar image. Get the allstar image from hamvoip.org and follow the instructions on the download page. you will need win23disk imager to write the  image to the SD card. a link to this is on the hamvoip.org download page.

Once the image is on the SD card  plug the raspberry pi into a monitor and add a keyboard an mouse. 

Follow the setup instructions. you can ignore the usb audio config as your not plugging in a radio. if you only have a Wi-Fi connection you can go back and configure the wi-fi once the wizard has finished.

I would advise you download a program called WinSCP. this will let you edit the config files more easily.  

To configure the raspberry pi to accept connections from DV switch go to https://dvswitch.groups.io/g/Mobile/wiki/AllStarLink-setup-for-DVSwitch-Mobile

You will ned to edit iax.conf and extensions.conf. everything in [iaxclient] goes in the iax.conf file. Add it to the bottom of the file. in extensions.conf you will see NODE=1999. change 1999 for your node number. next scroll to the bottom of extensions.conf and add everything under [iax-client]. save both of these files and restart.

to configure DV Switch enter the following. 

in accounts
host name - ip address of your raspberry pi. 
port - your iax port number
username - 
iaxclient
password - this is whaterver you set "secret" to in iax.conf
caller - ID your callsign
caller number leave blank
node - your node number

put a tick in autoload node

codec type - server selected.

in config if you want to user the up volume key for a ptt button enter the code 24. I you have the free version this wont save but the full app only costs $1.87

It is a great app that does work. I would suggest also reading through the wiki https://wiki.allstarlink.org/wiki/Main_Page

Phil

5821 - 5840 of 9795