Date   

DMRlink with no audio passing #dmrlink

ai6bx
 
Edited

I took a few weeks away from this project and am back at it now. As my ultimate goal involved linking DMRlink with HBlink with the corresponding IPSC_Bridge and HB_Bridge, I have stepped back a little to build out the networks on each side ensuring all was healthy there. As I stripped back the bridge interfaces, I may have inadvertently caused another issue as my Motorola repeaters with pointed at masters in the dmrlink.cfg files do not appear to fully connect or pass traffic. I note the following behaviors leading me to this:
* the confbridge.py shows the IP address of the repeater as well as the assigned port number however the network link light on the repeater does not sustain solid but blinks indicating no connection.
* I can ping the repeater from the computer running Dmrlink and IPSC
* when I key the repeater and visually confirm signal and TS activation I do not see the corresponding log information show up that I do when I key a remote repeater connected to a different Motorola Master linked to the peer server in the same config file. 

Expanding on the above, I now have three motorola repeaters showing links to DMRlink with the corresponding master stanzas noted above and I have a successful peer link to an existing motorola repeater functioning as a master with seven other linked repeaters. When a radio keys on one of the repeaters linked to the motorola master I see the radio ID and talk group show up in my dmrlink.py logs. Looking at the moto repeaters coming into my dmrlink system, I see IP addresses and port numbers however I get no audio and I do not see the same information regarding radio ID and TG. I also do not see the reciprocal indication of a connection on the repeater side as the link light continues to flash rather than going solid indicating a solid two way link. Below is the log captured during a test session. The only potential errors I see are related to the Carlsbad link. (ERROR (CARLSBAD) Unknown Message - Type: f0 From: 734566 Packet: f0000b35664a531000)

root@AI6BX-DMR:~# tail -f /tmp/dmrlink.log
INFO (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO (CARLSBAD) Master Registration Packet Received from peer 734566, 69.75.245.178:50009
INFO (RIFF_PEER) Peer List Received from Master: 7 peers in this IPSC
INFO (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO (RIFF_PEER) Peer List Received from Master: 7 peers in this IPSC
INFO (GLAMIS) Master Registration Packet Received from peer 734355, 44.16.15.50:62055
INFO (HB_BRIDGE) Master Registration Packet Received from peer 734440, 166.170.51.21:14225
INFO (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO (CARLSBAD) Master Registration Packet Received from peer 734566, 69.75.245.178:50009
ERROR (CARLSBAD) Unknown Message - Type: f0 From: 734566 Packet: f0000b35664a531000
INFO (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO (GLAMIS) Master Registration Packet Received from peer 734355, 44.16.15.50:62055
INFO (RIFF_PEER) Peer List Received from Master: 7 peers in this IPSC
INFO (HB_BRIDGE) Master Registration Packet Received from peer 734440, 166.170.51.21:14225
INFO (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO (CARLSBAD) Master Registration Packet Received from peer 734566, 69.75.245.178:50009
INFO (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO (GLAMIS) Master Registration Packet Received from peer 734355, 44.16.15.50:62055
ERROR (CARLSBAD) Unknown Message - Type: f0 From: 734566 Packet: f0000b356648531000
INFO (HB_BRIDGE) Master Registration Packet Received from peer 734440, 166.170.51.21:14225
INFO (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO (RIFF_PEER) Peer List Received from Master: 7 peers in this IPSC
INFO (CARLSBAD) Master Registration Packet Received from peer 734566, 69.75.245.178:50009
INFO (RIFF_PEER) Peer List Received from Master: 7 peers in this IPSC
INFO (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO (GLAMIS) Master Registration Packet Received from peer 734355, 44.16.15.50:62055
INFO (HB_BRIDGE) Master Registration Packet Received from peer 734440, 166.170.51.21:14225
INFO (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO (ALL IPSC SYSTEMS) Rule timer loop started
INFO (CARLSBAD) Master Registration Packet Received from peer 734566, 69.75.245.178:50009
ERROR (CARLSBAD) Unknown Message - Type: f0 From: 734566 Packet: f0000b35664a531000
INFO (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO (GLAMIS) Master Registration Packet Received from peer 734355, 44.16.15.50:62055
INFO (HB_BRIDGE) Master Registration Packet Received from peer 734440, 166.170.51.21:14225
INFO (RIFF_PEER) Peer Keep-Alive Missed for 734990, 72.132.16.199:50006
INFO (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO (CARLSBAD) Master Registration Packet Received from peer 734566, 69.75.245.178:50009
INFO (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO (GLAMIS) Master Registration Packet Received from peer 734355, 44.16.15.50:62055
ERROR (CARLSBAD) Unknown Message - Type: f0 From: 734566 Packet: f0000b35664e531000
INFO (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO (HB_BRIDGE) Master Registration Packet Received from peer 734440, 166.170.51.21:14225
INFO (CARLSBAD) Master Registration Packet Received from peer 734566, 69.75.245.178:50009
INFO (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO (RIFF_PEER) Peer List Received from Master: 7 peers in this IPSC
INFO (GLAMIS) Master Registration Packet Received from peer 734355, 44.16.15.50:62055
INFO (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO (HB_BRIDGE) Master Registration Packet Received from peer 734440, 166.170.51.21:14225
INFO (CARLSBAD) Master Registration Packet Received from peer 734566, 69.75.245.178:50009
ERROR (CARLSBAD) Unknown Message - Type: f0 From: 734566 Packet: f0000b35664a531000
INFO (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO (GLAMIS) Master Registration Packet Received from peer 734355, 44.16.15.50:62055
INFO (RIFF_PEER) Registering with Peer 20001, 67.63.96.6:50001
INFO (HB_BRIDGE) Master Registration Packet Received from peer 734440, 166.170.51.21:14225
^C

Following is the master stanza for the Carlsbad repeater:

[CARLSBAD]
ENABLED: True
RADIO_ID: 734566
IP:
PORT: 62036
ALIVE_TIMER: 5
MAX_MISSED: 20
PEER_OPER: True
IPSC_MODE: DIGITAL
TS1_LINK: True
TS2_LINK: True
CSBK_CALL: False
RCM: True
CON_APP: True
XNL_CALL: False
XNL_MASTER: False
DATA_CALL: True
VOICE_CALL: True
MASTER_PEER: True
AUTH_ENABLED: True
AUTH_KEY: AD07911
# Below not used for a Master
# MASTER_IP: 1.2.3.4
# MASTER_PORT: 50000
GROUP_HANGTIME: 5

Here is what my confbridge_rules.py looks like:

BRIDGES = {
    'ALLCALL': [
            {'SYSTEM': 'RIFF_PEER',    'TS': 1, 'TGID': 156,    'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [2,], 'OFF': [9,10]},
            {'SYSTEM': 'GLAMIS',    'TS': 1, 'TGID': 156, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [2,], 'OFF': [9,10]},
            {'SYSTEM': 'CARLSBAD',    'TS': 1, 'TGID': 156, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [2,], 'OFF': [9,10]},
            {'SYSTEM': 'HB_BRIDGE',    'TS': 1, 'TGID': 156, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [2,], 'OFF': [9,10]},
        ],
    'T-TAC': [
            {'SYSTEM': 'RIFF_PEER',    'TS': 2, 'TGID': 71,   'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [3,], 'OFF': [8,10]},
            {'SYSTEM': 'GLAMIS',    'TS': 2, 'TGID': 71,   'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [3,], 'OFF': [8,10]},
            {'SYSTEM': 'CARLSBAD',    'TS': 2, 'TGID': 71,   'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [3,], 'OFF': [8,10]},
            {'SYSTEM': 'HB_BRIDGE',    'TS': 2, 'TGID': 71,   'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [3,], 'OFF': [8,10]},
        ],
    'DARKSTAR': [
            {'SYSTEM': 'RIFF_PEER',    'TS': 2, 'TGID': 77, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [4,], 'OFF': [7,10]},
            {'SYSTEM': 'GLAMIS',    'TS': 2, 'TGID': 77, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [4,], 'OFF': [7,10]},
            {'SYSTEM': 'CARLSBAD',    'TS': 2, 'TGID': 77, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [4,], 'OFF': [7,10]},
            {'SYSTEM': 'HB_BRIDGE',    'TS': 2, 'TGID': 77, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [4,], 'OFF': [7,10]},
        ]
}
 
if __name__ == '__main__':
    from pprint import pprint
    pprint(BRIDGES)


Re: Help after editing rpt.conf. Not sure why?

Steve N4IRS
 

I would say yes you did.
As root:
cd /etc/asterisk
systemctl stop asterisk
asterisk -vcd
watch the screen, see if you can catch what your error is.

Steve N4IRS

On 12/30/19 8:00 PM, Ted Lawrence via Groups.Io wrote:
New here still learning my way around AllStar and DV-Switch . I get the following message after running systemctl status asterisk:

● asterisk.service - Asterisk PBX and telephony daemon

   Loaded: loaded (/lib/systemd/system/asterisk.service; enabled; vendor preset: enabled)

   Active: activating (auto-restart) (Result: exit-code) since Mon 2019-12-30 19:53:48 EST; 8s ago

     Docs: man:asterisk(8)

  Process: 3471 ExecStop=/usr/sbin/asterisk -rx stop now (code=exited, status=1/FAILURE)

  Process: 3441 ExecStart=/usr/sbin/asterisk -g -f -C /etc/asterisk/asterisk.conf (code=exited, status=1/FAILURE)

 Main PID: 3441 (code=exited, status=1/FAILURE)

This occurred in error after editing 
rpt.conf.  I must have made an error somewhere.  Not sure?

Thanks,
Ted KD4EG 



Help after editing rpt.conf. Not sure why?

Ted Lawrence
 

New here still learning my way around AllStar and DV-Switch . I get the following message after running systemctl status asterisk:

● asterisk.service - Asterisk PBX and telephony daemon

   Loaded: loaded (/lib/systemd/system/asterisk.service; enabled; vendor preset: enabled)

   Active: activating (auto-restart) (Result: exit-code) since Mon 2019-12-30 19:53:48 EST; 8s ago

     Docs: man:asterisk(8)

  Process: 3471 ExecStop=/usr/sbin/asterisk -rx stop now (code=exited, status=1/FAILURE)

  Process: 3441 ExecStart=/usr/sbin/asterisk -g -f -C /etc/asterisk/asterisk.conf (code=exited, status=1/FAILURE)

 Main PID: 3441 (code=exited, status=1/FAILURE)

This occurred in error after editing 
rpt.conf.  I must have made an error somewhere.  Not sure?

Thanks,
Ted KD4EG 


Re: DSTAR Registration Questions

Adrian Fewster <vk4tux@...>
 

Ed, You are correct regarding the original DCS reflector Z module, see ;

http://176.10.105.252/dcs_userstatus.htm

The Z module on these should return an echo with CQCQCQ once connected. Try DCS001 to test.

Many DCS entries in the DCS host file system are actually XLX reflectors, which don't support it.


These should work ;


DCS001    dcs001.xreflector.net   
DCS002    dcs002.xreflector.net   
DCS003    dcs003.xreflector.net
DCS004    dcs004.xreflector.net

DCS007    dcs007.xreflector.net   
DCS008    dcs008.xreflector.net   
DCS009    dcs009.xreflector.net

DCS011    dcs011.xreflector.net   
  
DCS015    dcs015.xreflector.net   
DCS016    dcs016.xreflector.net   
DCS017    dcs017.xreflector.net   
DCS018    dcs018.xreflector.net   
DCS019    dcs019.xreflector.net   
DCS021    dcs021.xreflector.net   
DCS022    dcs022.xreflector.net   
DCS023    dcs023.xreflector.net   
DCS024    dcs024.xreflector.net   
DCS025    dcs025.xreflector.net   
DCS026    dcs026.xreflector.net   
DCS027    dcs027.xreflector.net

DCS032    dcs032.xreflector.net   
DCS033    dcs033.xreflector.net
DCS044    dcs044.xreflector.net



On 31/12/19 7:57 am, Ed W8VT wrote:
Well, thought from what I could read that REF001E or any REF with E or DCS with Z were echo reflectors. Connected to them thinking should hear myself repeated back.
Is that not how they work? How would I issue your commands from the CLI of this ircDDBgateway-MMDVM_Bridge-Analog_Bridge-ASL setup?
Got DMR and YSF working without much trouble. DSTAR is becoming quite the educational experience!

Thanks,
Ed W8VT


Re: Getting a Burp Voice Message through ASL <> DMR Bridge #mmdvm_bridge

Ted Lawrence
 

Thanks for the help.  Will make changes and try again. 


Re: DSTAR Registration Questions

Adrian Fewster <vk4tux@...>
 

That's not correct. E is just another reflector module and has no reference to 'echo' Echo is an internal ircddbgateway feature, like 'info' #######I  etc.

and requires the #######E urcall sent. You really need to do it from the dstar radio. If you get ok audio reports from the dstar side, I wouldn't worry about it.

On 31/12/19 7:57 am, Ed W8VT wrote:
Well, thought from what I could read that REF001E or any REF with E or DCS with Z were echo reflectors. Connected to them thinking should hear myself repeated back.
Is that not how they work? How would I issue your commands from the CLI of this ircDDBgateway-MMDVM_Bridge-Analog_Bridge-ASL setup?
Got DMR and YSF working without much trouble. DSTAR is becoming quite the educational experience!

Thanks,
Ed W8VT


Re: DSTAR Registration Questions

Ed W8VT
 

Well, thought from what I could read that REF001E or any REF with E or DCS with Z were echo reflectors. Connected to them thinking should hear myself repeated back.
Is that not how they work? How would I issue your commands from the CLI of this ircDDBgateway-MMDVM_Bridge-Analog_Bridge-ASL setup?
Got DMR and YSF working without much trouble. DSTAR is becoming quite the educational experience!

Thanks,
Ed W8VT


Re: DSTAR Registration Questions

Adrian Fewster <vk4tux@...>
 

Ed, usually the ircddb server needs a transmission from the user on 40000 UDP to then add to database. 'Not found' messages usually cease

after a callsign route is done and the call is registered with it's IP in the ircddb database.

If you don't use callsign routing you can turn off all ircddb server options,  they are not necessary for usual dstar linking practice, within ircddbgateway to function.

If not needed, Disable all 4. They are not required for REF, XRF and DCS linking, CCS7, echo, info etc. The internet usage on the system is dramatically reduced.

Remote 4G modem d-star systems with monthly plan benefit greatly from the ircddb server disabled state keeping internet usage within limits, and startup time is much faster.

Example of disabled (=0) ;

ircddbEnabled=0
ircddbHostname=
ircddbUsername=
ircddbPassword=
ircddbEnabled2=0
ircddbHostname2=
ircddbUsername2=
ircddbPassword2=
ircddbEnabled3=0
ircddbHostname3=
ircddbUsername3=
ircddbPassword3=
ircddbEnabled4=0
ircddbHostname4=
ircddbUsername4=


aprs can also be disabled if not needed.


I run without ircddb enabled constantly.   http://vk4tux.duckdns.org:6080/vnc_auto.html  Running 2 x mmdvms and 2 x dstarrepeater for 4 module operation, ircddb server not needed or desired.



On 31/12/19 7:20 am, Will - W4WWM wrote:

Ed-W8VT

Restart your gateway as the quadnet server has a new IP.  That should clear up the NOT FOUND message.  If not send an email to admins@...


Will / W4WWM


On 12/30/2019 2:44 PM, Ed W8VT wrote:
Steve and Adrian,
Have an update. Keep getting interrupted but here is where we stand right now.
Manually updated the database (./dvswitch.sh update). Guess I should set up a cron job to do this on a regular basis?
Now my call shows rather than the DMR ID. Still get this though when trying to transmit:
M: 2019-12-30 20:23:14: Link command from W8VT   B to REF001 C issued via UR Call by W8VT    M: 2019-12-30 20:23:14: D-Plus reply is OKRWM: 2019-12-30 20:23:14: D-Plus ACK message received from REF001 CM: 2019-12-30 20:23:14: D-Plus link to REF001 C establishedM: 2019-12-30 20:23:15: USER: W8VT     NOT FOUND
Tried the E echo and no response, also called on several reflectors with no response, so get  the feeling no transmit.
Got to head out for now and won't be back until later this evening.
Really appreciate the assistance.

Ed W8VT


Re: DSTAR Registration Questions

Adrian Fewster <vk4tux@...>
 

How are you sending an echo request ? In D-Star #######E should be sent in urcall (#=space), &  ircddbgateway handles this locally, it does not go out beyond.

The ircddbgateway log will just show , eg ;

M: 2019-12-30 21:22:53: Received 5.7 secs of audio from VK4TUX   for echoing


On 31/12/19 6:44 am, Ed W8VT wrote:
Steve and Adrian,
Have an update. Keep getting interrupted but here is where we stand right now.
Manually updated the database (./dvswitch.sh update). Guess I should set up a cron job to do this on a regular basis?
Now my call shows rather than the DMR ID. Still get this though when trying to transmit:
M: 2019-12-30 20:23:14: Link command from W8VT   B to REF001 C issued via UR Call by W8VT    M: 2019-12-30 20:23:14: D-Plus reply is OKRWM: 2019-12-30 20:23:14: D-Plus ACK message received from REF001 CM: 2019-12-30 20:23:14: D-Plus link to REF001 C establishedM: 2019-12-30 20:23:15: USER: W8VT     NOT FOUND
Tried the E echo and no response, also called on several reflectors with no response, so get  the feeling no transmit.
Got to head out for now and won't be back until later this evening.
Really appreciate the assistance.

Ed W8VT


Re: DSTAR Registration Questions

Will - W4WWM <w4wwm@...>
 

Ed-W8VT

Restart your gateway as the quadnet server has a new IP.  That should clear up the NOT FOUND message.  If not send an email to admins@...


Will / W4WWM


On 12/30/2019 2:44 PM, Ed W8VT wrote:
Steve and Adrian,
Have an update. Keep getting interrupted but here is where we stand right now.
Manually updated the database (./dvswitch.sh update). Guess I should set up a cron job to do this on a regular basis?
Now my call shows rather than the DMR ID. Still get this though when trying to transmit:
M: 2019-12-30 20:23:14: Link command from W8VT   B to REF001 C issued via UR Call by W8VT    M: 2019-12-30 20:23:14: D-Plus reply is OKRWM: 2019-12-30 20:23:14: D-Plus ACK message received from REF001 CM: 2019-12-30 20:23:14: D-Plus link to REF001 C establishedM: 2019-12-30 20:23:15: USER: W8VT     NOT FOUND
Tried the E echo and no response, also called on several reflectors with no response, so get  the feeling no transmit.
Got to head out for now and won't be back until later this evening.
Really appreciate the assistance.

Ed W8VT


Re: DSTAR Registration Questions

Ed W8VT
 

Steve and Adrian,
Have an update. Keep getting interrupted but here is where we stand right now.
Manually updated the database (./dvswitch.sh update). Guess I should set up a cron job to do this on a regular basis?
Now my call shows rather than the DMR ID. Still get this though when trying to transmit:
M: 2019-12-30 20:23:14: Link command from W8VT   B to REF001 C issued via UR Call by W8VT    M: 2019-12-30 20:23:14: D-Plus reply is OKRWM: 2019-12-30 20:23:14: D-Plus ACK message received from REF001 CM: 2019-12-30 20:23:14: D-Plus link to REF001 C establishedM: 2019-12-30 20:23:15: USER: W8VT     NOT FOUND
Tried the E echo and no response, also called on several reflectors with no response, so get  the feeling no transmit.
Got to head out for now and won't be back until later this evening.
Really appreciate the assistance.

Ed W8VT


Re: Getting a Burp Voice Message through ASL <> DMR Bridge #mmdvm_bridge

Steve N4IRS
 

increase minTxTimeMS to between 2500 and 3000 in the [AMBE_Audio] stanza of Analog_Bridge.ini

On 12/30/19 3:06 PM, Jeff Lehman, N8ACL via Groups.Io wrote:

the message is probably "blocked" in a female voice. this means that your bridge has been blocked for an hour for too many keyups in a certain amount of time.

One thing that I found is to increase your tx timer. That might help to eliminate that. I don't have access to my system right this second, so I don't remember what a good setting is, but that will help. Maybe someone can suggest a good value.

Jeff

On 12/30/19 3:02 PM, Ted Lawrence via Groups.Io wrote:
Hi Folks!

I have 2 nodes running.   Node 505501 ASL<>DMR DV-Switch Bridge on one Raspberry Pi and Stand alone Node 505500 Raspberry Pi remote base UHF.

When the two nodes are linked,  I get what sounds like a  short voice message that sound line the word " burped " after the remote base courtesy tone. This happens when the remote base receives a siginal.   Can someone explain ? How do I stop this message behavior?

Sincerely,
Ted KD4EG
-- 
Jeff Lehman, N8ACL
E-mail: N8ACL@...
Hamshack Hotline: 4218

Webmaster
Hamilton County ARPSC
http://www.hamcoarpsc.org
E-mail: info@...
Phone: 513-452-6480


Re: Getting a Burp Voice Message through ASL <> DMR Bridge #mmdvm_bridge

Jeff Lehman, N8ACL
 

the message is probably "blocked" in a female voice. this means that your bridge has been blocked for an hour for too many keyups in a certain amount of time.

One thing that I found is to increase your tx timer. That might help to eliminate that. I don't have access to my system right this second, so I don't remember what a good setting is, but that will help. Maybe someone can suggest a good value.

Jeff

On 12/30/19 3:02 PM, Ted Lawrence via Groups.Io wrote:
Hi Folks!

I have 2 nodes running.   Node 505501 ASL<>DMR DV-Switch Bridge on one Raspberry Pi and Stand alone Node 505500 Raspberry Pi remote base UHF.

When the two nodes are linked,  I get what sounds like a  short voice message that sound line the word " burped " after the remote base courtesy tone. This happens when the remote base receives a siginal.   Can someone explain ? How do I stop this message behavior?

Sincerely,
Ted KD4EG
-- 
Jeff Lehman, N8ACL
E-mail: N8ACL@...
Hamshack Hotline: 4218

Webmaster
Hamilton County ARPSC
http://www.hamcoarpsc.org
E-mail: info@...
Phone: 513-452-6480


Getting a Burp Voice Message through ASL <> DMR Bridge #mmdvm_bridge

Ted Lawrence
 

Hi Folks!

I have 2 nodes running.   Node 505501 ASL<>DMR DV-Switch Bridge on one Raspberry Pi and Stand alone Node 505500 Raspberry Pi remote base UHF.

When the two nodes are linked,  I get what sounds like a  short voice message that sound line the word " burped " after the remote base courtesy tone. This happens when the remote base receives a siginal.   Can someone explain ? How do I stop this message behavior?

Sincerely,
Ted KD4EG


Re: DSTAR Registration Questions

Ed W8VT
 

Steve,
Well, think we may have found part of the problem, /var/lib/dvswitch/subscriber_ids.csv is an empty file, 0 bytes.
; The metadata below is used when ASL is the source since it does not have any concept of digital modesgatewayDmrId = 3154009                        ; ID to use when transmitting from Analog_BridgerepeaterID = 315400902                          ; ID of source repeatertxTg = 313938                                ; TG to use for all frames sent from Analog_Bridge -> xx_BridgetxTs = 2                                ; Slot to use for frames sent from Analog_Bridge -> xx_BridgecolorCode = 7                           ; Color Code to assign DMR frames
Above is what was being used in the original DMR Bridge.
Still mystified as to where this in the analog_bridge log is coming from:
I: 2019-12-30 17:00:54.887 Begin TX: src=3154017 rpt=0 dst=9 slot=2 cc=0 call=W8VT
Ed


Re: DSTAR Registration Questions

Adrian Fewster <vk4tux@...>
 

The system should be using it's DMR database to find and send W8VT to ircddbgateway ? ;

; Metadata management
exportMetadata = true                   ; Export metadata to USRP partner (transcode setups require this)
subscriberFile = /path/subscriber_ids.csv   ; DMR ID to callsign lookup data


You may have to check path and content of subscriber_ids.csv ? in ini's ?


On 31/12/19 1:55 am, Ed W8VT wrote:
Can now connect and receive fine. Listened to a lot  traffic on REF001C. Tried echo and apparently no transmit, Shows my call as connected in tje log and on their dashboard. When I attempt to transmit, this is via iaxRPT ASL and the bridge, I see this in the ircddbgateway log:
M: 2019-12-30 01:33:05: USER: 3154009  NOT FOUND
3154009 is one of my DMR IDs. I swear at one point in this adventure when I keyed saw my call and public IP listed as  unknown.

Another real mystery is this from the analog_bridge log:
I: 2019-12-30 15:16:58.435 Begin TX: src=3154017 rpt=0 dst=9 slot=2 cc=0 call=W8VT
315017 is my other DMR ID. Have no idea where this coming from. Have searched MMDVM_bridge.ini, analog_bridge.ini and dvswitch.ini. Think at one point may have tried it somewhere as a test but can not find it anywhere now.

The bridge is currently operational on DMR and can also be switched to YSF. Works great on these modes.

Ed W8VT
Still befuddled


Re: DSTAR Registration Questions

Steve N4IRS
 

Ed,
For D-Star transmit, MMDVM_Bridge is going to need to resolve your DMR ID to call sign.
Let's start with Analog_Bridge. What do you have for these?
[GENERAL]

; Metadata management
subscriberFile =
/var/lib/dvswitch/subscriber_ids.csv   ; DMR ID to callsign lookup data
exportMetadata = true                   ; Export metadata to USRP partner (transcode setups require this)

; Information for xx_Bridge (Where xx is MMDVM, Quantar, HB, IPSC)
[AMBE_AUDIO]
gatewayDmrId = 0                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 0                          ; ID of source repeater


Let's verify AB can resolve your call sign

grep 3154009 /var/lib/dvswitch/subscriber_ids.csv

Steve



On 12/30/19 10:55 AM, Ed W8VT wrote:
Can now connect and receive fine. Listened to a lot  traffic on REF001C. Tried echo and apparently no transmit, Shows my call as connected in tje log and on their dashboard. When I attempt to transmit, this is via iaxRPT ASL and the bridge, I see this in the ircddbgateway log:
M: 2019-12-30 01:33:05: USER: 3154009  NOT FOUND
3154009 is one of my DMR IDs. I swear at one point in this adventure when I keyed saw my call and public IP listed as  unknown.

Another real mystery is this from the analog_bridge log:
I: 2019-12-30 15:16:58.435 Begin TX: src=3154017 rpt=0 dst=9 slot=2 cc=0 call=W8VT
315017 is my other DMR ID. Have no idea where this coming from. Have searched MMDVM_bridge.ini, analog_bridge.ini and dvswitch.ini. Think at one point may have tried it somewhere as a test but can not find it anywhere now.

The bridge is currently operational on DMR and can also be switched to YSF. Works great on these modes.

Ed W8VT
Still befuddled


Re: DSTAR Registration Questions

Ed W8VT
 

Can now connect and receive fine. Listened to a lot  traffic on REF001C. Tried echo and apparently no transmit, Shows my call as connected in tje log and on their dashboard. When I attempt to transmit, this is via iaxRPT ASL and the bridge, I see this in the ircddbgateway log:
M: 2019-12-30 01:33:05: USER: 3154009  NOT FOUND
3154009 is one of my DMR IDs. I swear at one point in this adventure when I keyed saw my call and public IP listed as  unknown.

Another real mystery is this from the analog_bridge log:
I: 2019-12-30 15:16:58.435 Begin TX: src=3154017 rpt=0 dst=9 slot=2 cc=0 call=W8VT
315017 is my other DMR ID. Have no idea where this coming from. Have searched MMDVM_bridge.ini, analog_bridge.ini and dvswitch.ini. Think at one point may have tried it somewhere as a test but can not find it anywhere now.

The bridge is currently operational on DMR and can also be switched to YSF. Works great on these modes.

Ed W8VT
Still befuddled


Re: DSTAR Registration Questions

Adrian Fewster <vk4tux@...>
 

The ircddbgateway log will indicate the nature of any issues, if you post it here, if so.



On 30/12/19 11:16 am, Ed W8VT wrote:
Thanks Adrian. Now that I know the registration looks OK, we'll do some more experimentation.

Really appreciate the assistance.

Ed W8VT


Re: DSTAR Registration Questions

Ed W8VT
 

Thanks Adrian. Now that I know the registration looks OK, we'll do some more experimentation.

Really appreciate the assistance.

Ed W8VT

3581 - 3600 of 9203