Date   

Re: NXDN connections and terms

Mike KB8JNM
 

Thanks

I have had a couple of NXDN ID's for a while. Just getting to it.

I understood the meaning/use of the fallback id but can it be any alfa-numeric.

So, is there any significance to a RAN of 1... is it like 'ALL' in meaning ?

I am also wondering if there is a registry of NXDN relectors. I put a reflector up in experiment and connect to it from dmr2nxdn on pi-star after I edit my NXDNHostsLocal.txt to insert myself but also see the ip to nxcore in the reflector cfg, but see no value in that connection from the reflector.  But I also should not assume it works like the YSF of the same (both g4klx). Perhaps beyond the scope of this board.

So I'm guessing I'm missing something or still pretty dumb on it. Both perhaps.


On 1/6/2019 4:27 PM, Steve N4IRS wrote:
No, you need the Gateway.

[NXDN]
RAN=1        ; Radio Access Number (Think Color Code)
Id=12345     ; This is your Repeater NXDN ID. NXDN IDs max out at 5 digits so you can not use your DMR ID. You can register at <https://www.radioid.net>

NXDNFallbackID  = 12345    Since you are bridging and have a DMR ID coming in The bridge will attempt to find a call sign that matches the DMR ID. If found it will then attempt to find a NXDN ID that matches the callsign. if found that will be the NXDN ID used otherwise, it will insert the fallback ID.

Steve N4IRS

On 1/6/19 4:15 PM, Mike KB8JNM wrote:
Should DVSwitch be able to directly (native) connect to a NXDN reflector without adding a gateway or other interface ?
Looking at the settings, some of them need some definition.

Not being familure with NXDN it begs... What is RAN ?
and what is the purpose of the id=12345 or what id is this ?
[NXDN]
Enable=0
RAN=1
Id=12345

What phams can be used in the NXDN fallbackid. Guessing anything could be used like UNguest to spot it in a dashboard or log file.
NXDNFallbackID  = 12345         ; Use this ID when the input DMR ID is not found in the database

Get me started....HI HI


Re: NXDN connections and terms

Steve N4IRS
 

No, you need the Gateway.

[NXDN]
RAN=1        ; Radio Access Number (Think Color Code)
Id=12345     ; This is your Repeater NXDN ID. NXDN IDs max out at 5 digits so you can not use your DMR ID. You can register at <https://www.radioid.net>

NXDNFallbackID  = 12345    Since you are bridging and have a DMR ID coming in The bridge will attempt to find a call sign that matches the DMR ID. If found it will then attempt to find a NXDN ID that matches the callsign. if found that will be the NXDN ID used otherwise, it will insert the fallback ID.

Steve N4IRS

On 1/6/19 4:15 PM, Mike KB8JNM wrote:
Should DVSwitch be able to directly (native) connect to a NXDN reflector without adding a gateway or other interface ?
Looking at the settings, some of them need some definition.

Not being familure with NXDN it begs... What is RAN ?
and what is the purpose of the id=12345 or what id is this ?
[NXDN]
Enable=0
RAN=1
Id=12345

What phams can be used in the NXDN fallbackid. Guessing anything could be used like UNguest to spot it in a dashboard or log file.
NXDNFallbackID  = 12345         ; Use this ID when the input DMR ID is not found in the database

Get me started....HI HI


Re: NXDN connections and terms

Michael KD5DFB
 

I believe it uses a gateway and reflector like P25. 

RAN (Random Access Number) is similar to a CTCSS encode for analog systems. It unlocks the squelch on the repeater while you transmit to permit access to the repeater. There are 63 codes.

On Sun, Jan 6, 2019, 15:15 Mike KB8JNM <groupio@... wrote:
Should DVSwitch be able to directly (native) connect to a NXDN reflector without adding a gateway or other interface ?
Looking at the settings, some of them need some definition.

Not being familure with NXDN it begs... What is RAN ?
and what is the purpose of the id=12345 or what id is this ?
[NXDN]
Enable=0
RAN=1
Id=12345

What phams can be used in the NXDN fallbackid. Guessing anything could be used like UNguest to spot it in a dashboard or log file.
NXDNFallbackID  = 12345         ; Use this ID when the input DMR ID is not found in the database

Get me started....HI HI


NXDN connections and terms

Mike KB8JNM
 

Should DVSwitch be able to directly (native) connect to a NXDN reflector without adding a gateway or other interface ?
Looking at the settings, some of them need some definition.

Not being familure with NXDN it begs... What is RAN ?
and what is the purpose of the id=12345 or what id is this ?
[NXDN]
Enable=0
RAN=1
Id=12345

What phams can be used in the NXDN fallbackid. Guessing anything could be used like UNguest to spot it in a dashboard or log file.
NXDNFallbackID  = 12345         ; Use this ID when the input DMR ID is not found in the database

Get me started....HI HI


HBlink and DMRlink questions.

Jamie R. Cid <jay@...>
 

Hey All,

So a few questions on HBlink and DMRlink.

1. Can echo (aka parrot) be used with private call also or just group call?
2. Can HBlink and DMRlink pass DATA and Private calls internally?
3. More specifically can DMRlink pass data between internal IPSC endpoints such as 2 Motorola IPSC Trbo repeaters directly connected?

Thanks All and Happy New Year!!


Re: IAXRPT DVSwitch (Unable to Register/Connect)

ke0key@...
 

Thank you for the information. I found that one said "iaxrpt" in iax.rpt and said "iax-rpt" in extensions.conf files. So I changed one to match the other and it fixed the issue.
--
James (KE0KEY)
Founder/Administrator
Global DX System
www.globaldxsystem.com


Re: IAXRPT DVSwitch (Unable to Register/Connect)

Mike KB8JNM
 

To be sure we are not chasing fairy dust,

could you post your iax.conf and extentions.conf entries (mask password) ...just the needed stanza's.

...mike/kb8jnm

On 1/6/2019 1:21 PM, ke0key@... wrote:
I have installed the new version of IAXRPT DVSwitch on my Android phone. I have entered all of the configuration information correctly and it matches the information in my iax.rpt file.

When I go to Register or Connect to my Allstar Node, it will not let me. I am getting the "Not Registered" error.

Also, I have installed the IAXRPT for Windows on my desktop and entered the same information and it will let me log in to my node just fine.

Can someone please tell me what the difference is between the Windows version and the Android version that will prevent me from using the mobile version?

Thanks,
James (KE0KEY)
Global DX System
www.globaldxsystem.com


Re: IAXRPT DVSwitch (Unable to Register/Connect)

Steve N4IRS
 

James,

The entries for DVSwitch Mobile is slightly different from the entries used for Windows IAXRPT. You can find the correct entries at <https://dvswitch.groups.io/g/Mobile/wiki/AllStarLink-setup-for-DVSwitch-Mobile>
I suggest you join the DVSwitch mobile subgroup at <https://dvswitch.groups.io/g/Mobile>

73, Steve N4IRS

On 1/6/19 1:21 PM, ke0key@... wrote:
I have installed the new version of IAXRPT DVSwitch on my Android phone. I have entered all of the configuration information correctly and it matches the information in my iax.rpt file.

When I go to Register or Connect to my Allstar Node, it will not let me. I am getting the "Not Registered" error.

Also, I have installed the IAXRPT for Windows on my desktop and entered the same information and it will let me log in to my node just fine.

Can someone please tell me what the difference is between the Windows version and the Android version that will prevent me from using the mobile version?

Thanks,
James (KE0KEY)
Global DX System
www.globaldxsystem.com


IAXRPT DVSwitch (Unable to Register/Connect)

ke0key@...
 

I have installed the new version of IAXRPT DVSwitch on my Android phone. I have entered all of the configuration information correctly and it matches the information in my iax.rpt file.

When I go to Register or Connect to my Allstar Node, it will not let me. I am getting the "Not Registered" error.

Also, I have installed the IAXRPT for Windows on my desktop and entered the same information and it will let me log in to my node just fine.

Can someone please tell me what the difference is between the Windows version and the Android version that will prevent me from using the mobile version?

Thanks,
James (KE0KEY)
Global DX System
www.globaldxsystem.com


Re: HB Bridge <-> MMDVM_Bridge <-> P25gateway

Steve N4IRS
 

No, the problem is that HB_Bridge is AMBE and P25 is IMBE. You need a transcoder in between.


On 1/5/19 9:56 PM, KD5DFB wrote:
If I have HB_Bridge connected to MMDVM_bridge and P25gateway shouldn't traffic flow both ways? So if I key up on P25 it should go thru MMDVM_bridge and to HB_Bridge and vise versus 

HB Bridge <-> MMDVM_Bridge <-> P25gateway

Or does it just go out the ports defined in the dvswitch.ini??


HB Bridge <-> MMDVM_Bridge <-> P25gateway

Michael KD5DFB
 

If I have HB_Bridge connected to MMDVM_bridge and P25gateway shouldn't traffic flow both ways? So if I key up on P25 it should go thru MMDVM_bridge and to HB_Bridge and vise versus 

HB Bridge <-> MMDVM_Bridge <-> P25gateway

Or does it just go out the ports defined in the dvswitch.ini??


Re: MMDVM_Bridge.ini

Steve N4IRS
 

yep

On 1/5/19 9:51 PM, KD5DFB wrote:
Okay, I see it now. It is like the txport and rxport in the dvswitch.ini

On Sat, Jan 5, 2019 at 8:48 PM Steve N4IRS <szingman@...> wrote:
In P25 it is used to communicate with P25Gateway. In DMR it is used if you are using DMRGateway to communicate. Otherwise it is not used for DMR.

On 1/5/19 9:44 PM, KD5DFB wrote:
What is the purpose of the local ports in the MMDVM_Bridge.ini

[DMR Network]
Enable=1
Address=127.0.0.1
Port=54000
Jitter=360
#Local=62032
Password=s3cr37w0rd
Slot1=0
Slot2=1
Debug=1

[P25 Network]
Enable=1
GatewayAddress=127.0.0.1
GatewayPort=42020
LocalPort=32010
Debug=0
 



Re: MMDVM_Bridge.ini

Michael KD5DFB
 

Okay, I see it now. It is like the txport and rxport in the dvswitch.ini

On Sat, Jan 5, 2019 at 8:48 PM Steve N4IRS <szingman@...> wrote:
In P25 it is used to communicate with P25Gateway. In DMR it is used if you are using DMRGateway to communicate. Otherwise it is not used for DMR.

On 1/5/19 9:44 PM, KD5DFB wrote:
What is the purpose of the local ports in the MMDVM_Bridge.ini

[DMR Network]
Enable=1
Address=127.0.0.1
Port=54000
Jitter=360
#Local=62032
Password=s3cr37w0rd
Slot1=0
Slot2=1
Debug=1

[P25 Network]
Enable=1
GatewayAddress=127.0.0.1
GatewayPort=42020
LocalPort=32010
Debug=0
 


Re: MMDVM_Bridge.ini

Steve N4IRS
 

In P25 it is used to communicate with P25Gateway. In DMR it is used if you are using DMRGateway to communicate. Otherwise it is not used for DMR.

On 1/5/19 9:44 PM, KD5DFB wrote:
What is the purpose of the local ports in the MMDVM_Bridge.ini

[DMR Network]
Enable=1
Address=127.0.0.1
Port=54000
Jitter=360
#Local=62032
Password=s3cr37w0rd
Slot1=0
Slot2=1
Debug=1

[P25 Network]
Enable=1
GatewayAddress=127.0.0.1
GatewayPort=42020
LocalPort=32010
Debug=0
 


MMDVM_Bridge.ini

Michael KD5DFB
 

What is the purpose of the local ports in the MMDVM_Bridge.ini

[DMR Network]
Enable=1
Address=127.0.0.1
Port=54000
Jitter=360
#Local=62032
Password=s3cr37w0rd
Slot1=0
Slot2=1
Debug=1

[P25 Network]
Enable=1
GatewayAddress=127.0.0.1
GatewayPort=42020
LocalPort=32010
Debug=0
 


Re: Allstarlink to Echolink showing an error??

Corey Dean N3FE <n3fe@...>
 

I understand but this issue is with allstar and not dvswitch.  I have the same problem and was not able to get it resolved either.  As stated before it is a question for the allstar group, not dvswitch.

On Sat, Jan 5, 2019 at 8:31 AM <jeff@...> wrote:
I can make and receive all Echolink connects inbound and outbound from the node, i continually see this error each time an outbound connection is attempted.
I was just wondering what it is and how to  fix it, it gives an error code of (467) I am guessing it is a IP Address for node number not found error but again it connects..


Re: Allstarlink to Echolink showing an error??

Mike KB8JNM
 

Check your Db servers in the conf file

These work well for me

server1=naeast.echolink.org
server2=nasouth.echolink.org
server3=servers.echolink.org

...mike/kb8jnm

On 1/5/2019 8:31 AM, jeff@... wrote:
I can make and receive all Echolink connects inbound and outbound from the node, i continually see this error each time an outbound connection is attempted.
I was just wondering what it is and how to  fix it, it gives an error code of (467) I am guessing it is a IP Address for node number not found error but again it connects..


Re: Allstarlink to Echolink showing an error??

Jeff Wood
 

I can make and receive all Echolink connects inbound and outbound from the node, i continually see this error each time an outbound connection is attempted.
I was just wondering what it is and how to  fix it, it gives an error code of (467) I am guessing it is a IP Address for node number not found error but again it connects..


Re: DMR<-->P25 Now only one way Audio

Steve N4IRS
 

Put the gateway in debug and verify it is getting data from the reflector

Also I think there is a debug setting in p25 network of mmdvm_bridge.

Sent via smoke signal (Verizon)

On Jan 4, 2019 6:07 PM, Ian Tulley <ian@...> wrote:
Not that I can see Steve, 

Here is the startup,

I: 2019-01-04 23:04:19.346 MMDVM_Bridge:
I: 2019-01-04 23:04:19.346 Portions Copyright (C) 2018 DVSwitch, INAD.
I: 2019-01-04 23:04:19.346 Hacks by Mike N4IRR and Steve N4IRS
I: 2019-01-04 23:04:19.346 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I: 2019-01-04 23:04:19.346 This software is for use on amateur radio networks only,
I: 2019-01-04 23:04:19.346 it is to be used for educational purposes only. Its use on
I: 2019-01-04 23:04:19.346 commercial networks is strictly prohibited.
I: 2019-01-04 23:04:19.346 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2019-01-04 23:04:19.346 MMDVM_Bridge-20180423 is starting
M: 2019-01-04 23:04:19.346 Built 15:47:01 May 30 2018 (GitID #9cdea41)
I: 2019-01-04 23:04:19.346 General Parameters
I: 2019-01-04 23:04:19.347     Callsign: VK2RHK
I: 2019-01-04 23:04:19.347     Id: 505204
I: 2019-01-04 23:04:19.347     Duplex: no
I: 2019-01-04 23:04:19.347     Timeout: 180s
I: 2019-01-04 23:04:19.347     D-Star: disabled
I: 2019-01-04 23:04:19.347     DMR: enabled
I: 2019-01-04 23:04:19.347     YSF: disabled
I: 2019-01-04 23:04:19.347     P25: enabled
I: 2019-01-04 23:04:19.347     NXDN: disabled
I: 2019-01-04 23:04:19.347 Modem Parameters
I: 2019-01-04 23:04:19.347     Port: /dev/null
I: 2019-01-04 23:04:19.347     RX Invert: no
I: 2019-01-04 23:04:19.347     TX Invert: no
I: 2019-01-04 23:04:19.347     PTT Invert: no
I: 2019-01-04 23:04:19.347     TX Delay: 100ms
I: 2019-01-04 23:04:19.347     RX Offset: 0Hz
I: 2019-01-04 23:04:19.347     TX Offset: 0Hz
I: 2019-01-04 23:04:19.347     RX DC Offset: 0
I: 2019-01-04 23:04:19.347     TX DC Offset: 0
I: 2019-01-04 23:04:19.347     RF Level: 100.0%
I: 2019-01-04 23:04:19.347     DMR Delay: 0 (0.0ms)
I: 2019-01-04 23:04:19.347     RX Level: 50.0%
I: 2019-01-04 23:04:19.348     CW Id TX Level: 50.0%
I: 2019-01-04 23:04:19.348     D-Star TX Level: 50.0%
I: 2019-01-04 23:04:19.348     DMR TX Level: 50.0%
I: 2019-01-04 23:04:19.348     YSF TX Level: 50.0%
I: 2019-01-04 23:04:19.348     P25 TX Level: 50.0%
I: 2019-01-04 23:04:19.348     NXDN TX Level: 50.0%
I: 2019-01-04 23:04:19.348     RX Frequency: 222340000Hz (222340000Hz)
I: 2019-01-04 23:04:19.348     TX Frequency: 224940000Hz (224940000Hz)
M: 2019-01-04 23:04:19.348 Opening the MMDVM
I: 2019-01-04 23:04:19.348 Display Parameters
I: 2019-01-04 23:04:19.348     Type:
I: 2019-01-04 23:04:19.348 DMR Network Parameters
I: 2019-01-04 23:04:19.348     Address: vkbm.repeaters.info
I: 2019-01-04 23:04:19.348     Port: 62031
I: 2019-01-04 23:04:19.348     Local: 62032
I: 2019-01-04 23:04:19.348     Jitter: 360ms
I: 2019-01-04 23:04:19.348     Slot 1: enabled
I: 2019-01-04 23:04:19.348     Slot 2: enabled
I: 2019-01-04 23:04:19.348     Mode Hang: 3s
I: 2019-01-04 23:04:19.350 Info Parameters
I: 2019-01-04 23:04:19.350     Callsign: VK2RHK
I: 2019-01-04 23:04:19.350     RX Frequency: 222340000Hz
I: 2019-01-04 23:04:19.350     TX Frequency: 224940000Hz
I: 2019-01-04 23:04:19.350     Power: 1W
I: 2019-01-04 23:04:19.350     Latitude: -33.182800deg N
I: 2019-01-04 23:04:19.350     Longitude: -151.494095deg E
I: 2019-01-04 23:04:19.350     Height: 0m
I: 2019-01-04 23:04:19.350     Location: "Central Coast, NSW-AU"
I: 2019-01-04 23:04:19.350     Description: "50525 MMDVM_Bridge"
I: 2019-01-04 23:04:19.350     URL: "http:tg50525.repeaters.info"
M: 2019-01-04 23:04:19.350 DMR, Opening DMR Network
I: 2019-01-04 23:04:19.350 P25 Network Parameters
I: 2019-01-04 23:04:19.350     Gateway Address: 127.0.0.1
I: 2019-01-04 23:04:19.351     Gateway Port: 42020
I: 2019-01-04 23:04:19.351     Local Port: 32010
I: 2019-01-04 23:04:19.351     Mode Hang: 3s
M: 2019-01-04 23:04:19.351 P25, Opening INI file: DVSwitch.ini
M: 2019-01-04 23:04:19.351 P25, Setting [P25] Address -> 127.0.0.1
M: 2019-01-04 23:04:19.351 P25, Setting [P25] TXPort -> 34100
M: 2019-01-04 23:04:19.351 P25, Setting [P25] RXPort -> 34103
M: 2019-01-04 23:04:19.351 P25, Setting [P25] Slot -> 2
M: 2019-01-04 23:04:19.351 P25, Transmitting on 127.0.0.1:34100 and listening on port 34103.  Result = 1
M: 2019-01-04 23:04:19.351 Opening P25 network connection
I: 2019-01-04 23:04:19.351 RSSI
I: 2019-01-04 23:04:19.351     Mapping File: RSSI.dat
W: 2019-01-04 23:04:19.352 Cannot open the RSSI data file - RSSI.dat
I: 2019-01-04 23:04:19.352 DMR Id Lookups
I: 2019-01-04 23:04:19.352     File: /var/lib/mmdvm/DMRIds.dat
I: 2019-01-04 23:04:19.352     Reload: 24 hours
I: 2019-01-04 23:04:19.486 Loaded 120478 Ids to the DMR callsign lookup table
I: 2019-01-04 23:04:19.486 DMR RF Parameters
I: 2019-01-04 23:04:19.486     Id: 505204
I: 2019-01-04 23:04:19.486     Color Code: 1
I: 2019-01-04 23:04:19.487     Self Only: no
I: 2019-01-04 23:04:19.487     Embedded LC Only: yes
I: 2019-01-04 23:04:19.487     Dump Talker Alias Data: no
I: 2019-01-04 23:04:19.487     Prefixes: 0
I: 2019-01-04 23:04:19.487     Call Hang: 3s
I: 2019-01-04 23:04:19.487     TX Hang: 3s
I: 2019-01-04 23:04:19.487     Mode Hang: 10s
M: 2019-01-04 23:04:19.487 DMR, Opening INI file: DVSwitch.ini
M: 2019-01-04 23:04:19.487 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2019-01-04 23:04:19.487 DMR, Setting [DMR] TXPort -> 31100
M: 2019-01-04 23:04:19.487 DMR, Setting [DMR] RXPort -> 31103
M: 2019-01-04 23:04:19.487 DMR, Setting [DMR] Slot -> 2
M: 2019-01-04 23:04:19.487 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
I: 2019-01-04 23:04:19.487 P25 RF Parameters
I: 2019-01-04 23:04:19.487     Id: 505204
I: 2019-01-04 23:04:19.488     NAC: $293
I: 2019-01-04 23:04:19.488     UID Override: no
I: 2019-01-04 23:04:19.488     Self Only: no
I: 2019-01-04 23:04:19.488     Remote Gateway: no
I: 2019-01-04 23:04:19.488     Mode Hang: 10s
M: 2019-01-04 23:04:19.488 MMDVM_Bridge-20180423 is running
I: 2019-01-04 23:04:19.488 Started the DMR Id lookup reload thread
D: 2019-01-04 23:04:29.495 DMR, Sending authorisation
D: 2019-01-04 23:04:29.501 DMR, Sending configuration
M: 2019-01-04 23:04:29.506 DMR, Logged into the master successfully

And I did a PTT after this so as you can see nothing showing up for P25 but after that I did a PTT from DMR and this is what I get.

M: 2019-01-04 23:06:34.130 DMR Slot 2, received network voice header from VK2HK to TG 50525
M: 2019-01-04 23:06:34.636 P25, TX state = ON
I: 2019-01-04 23:06:34.636 P25, Begin TX: src=5052110 rpt=505204 dst=50525 slot=2 cc=1

M: 2019-01-04 23:06:34.805 DMR Talker Alias (Data Format 1, Received 6/22 char): 'VK2HK '
M: 2019-01-04 23:06:35.288 DMR Slot 2, received network end of voice transmission, 1.2 seconds, 0% packet loss, BER: 0.2%
M: 2019-01-04 23:06:35.293 P25, TX state = OFF



------------------
Regards
Ian (VK2HK)




On 5 Jan 2019, at 9:49 am, Steve N4IRS <szingman@...> wrote:

Then the problem is at MMDVM_Bridge. Absolutely nothing in the MMDVM_Bridge log when you TX on P25 through the reflector? Nothing strange in the startup of MMDVM_Bridge?

On 1/4/19 5:43 PM, Ian Tulley wrote:
Hi Steve, well that’s the problem, when I PTT of P25, I can see myself on the Reflector, but nothing on mmdvm_bridge log or and of the analog_bridge logs ??

------------------
Regards
Ian (VK2HK)




On 5 Jan 2019, at 9:20 am, Steve N4IRS <szingman@...> wrote:

Follow the data in the logs from program to program. Do you see the data in the log for MMDVM_Bridge? if yes, move on to analog_bridge. Same question. rinse repeat.

On 1/4/19 4:52 PM, Ian Tulley wrote:
Hi all, I recently had active a DMR <--> P25 Bridge with the help of Steve. There was an issue with setting up the audio due to some problem associated with md380-emu, but it was fixed and the bridge worked great and after some tweaking the audio and audio levels in both directions just worked. I have been monitoring for a couple of days and found last night that I only had audio from DMR to P25 but not in the reverse direction. This morning I have been trying hard to solve this issue but just cannot find out why.
This is on a VPS and I am running the P25Reflector/Gateway/Bridge plus NXDN Reflector and YSF Reflector all off the same server, but when the bridge was working all of this was running at the same time.
This is what I have done so far, so any further suggestions would be welcome.

Checked status of all services to make sure all running and yes all OK
Set both P25Reflector and P25Gateway into Debug mode and monitored the output but nothing found.
restarted all services but again no difference.
stoped md30-emu
stopped mmdvm_bridge
stopped analog_bridge_p25 and analog_bridge_dmr
restarted all services manually in seperate windows so I could monitor the output to the screen.

Results I am getting, 
If I key up on the P25 radio, I get nothing coming to any of the screen outputs, but can hear myself via another connected P25 Hotspot so I know the reflector is working OK
If I key up on DMR I can see all 3 screen outputs and can hear myself out of the P25 Radio.

Anyone have any idea where to start to look for this issue.

Ian (VK2HK)
 




Re: DMR<-->P25 Now only one way Audio

Ian Tulley
 

Not that I can see Steve, 

Here is the startup,

I: 2019-01-04 23:04:19.346 MMDVM_Bridge:
I: 2019-01-04 23:04:19.346 Portions Copyright (C) 2018 DVSwitch, INAD.
I: 2019-01-04 23:04:19.346 Hacks by Mike N4IRR and Steve N4IRS
I: 2019-01-04 23:04:19.346 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I: 2019-01-04 23:04:19.346 This software is for use on amateur radio networks only,
I: 2019-01-04 23:04:19.346 it is to be used for educational purposes only. Its use on
I: 2019-01-04 23:04:19.346 commercial networks is strictly prohibited.
I: 2019-01-04 23:04:19.346 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2019-01-04 23:04:19.346 MMDVM_Bridge-20180423 is starting
M: 2019-01-04 23:04:19.346 Built 15:47:01 May 30 2018 (GitID #9cdea41)
I: 2019-01-04 23:04:19.346 General Parameters
I: 2019-01-04 23:04:19.347     Callsign: VK2RHK
I: 2019-01-04 23:04:19.347     Id: 505204
I: 2019-01-04 23:04:19.347     Duplex: no
I: 2019-01-04 23:04:19.347     Timeout: 180s
I: 2019-01-04 23:04:19.347     D-Star: disabled
I: 2019-01-04 23:04:19.347     DMR: enabled
I: 2019-01-04 23:04:19.347     YSF: disabled
I: 2019-01-04 23:04:19.347     P25: enabled
I: 2019-01-04 23:04:19.347     NXDN: disabled
I: 2019-01-04 23:04:19.347 Modem Parameters
I: 2019-01-04 23:04:19.347     Port: /dev/null
I: 2019-01-04 23:04:19.347     RX Invert: no
I: 2019-01-04 23:04:19.347     TX Invert: no
I: 2019-01-04 23:04:19.347     PTT Invert: no
I: 2019-01-04 23:04:19.347     TX Delay: 100ms
I: 2019-01-04 23:04:19.347     RX Offset: 0Hz
I: 2019-01-04 23:04:19.347     TX Offset: 0Hz
I: 2019-01-04 23:04:19.347     RX DC Offset: 0
I: 2019-01-04 23:04:19.347     TX DC Offset: 0
I: 2019-01-04 23:04:19.347     RF Level: 100.0%
I: 2019-01-04 23:04:19.347     DMR Delay: 0 (0.0ms)
I: 2019-01-04 23:04:19.347     RX Level: 50.0%
I: 2019-01-04 23:04:19.348     CW Id TX Level: 50.0%
I: 2019-01-04 23:04:19.348     D-Star TX Level: 50.0%
I: 2019-01-04 23:04:19.348     DMR TX Level: 50.0%
I: 2019-01-04 23:04:19.348     YSF TX Level: 50.0%
I: 2019-01-04 23:04:19.348     P25 TX Level: 50.0%
I: 2019-01-04 23:04:19.348     NXDN TX Level: 50.0%
I: 2019-01-04 23:04:19.348     RX Frequency: 222340000Hz (222340000Hz)
I: 2019-01-04 23:04:19.348     TX Frequency: 224940000Hz (224940000Hz)
M: 2019-01-04 23:04:19.348 Opening the MMDVM
I: 2019-01-04 23:04:19.348 Display Parameters
I: 2019-01-04 23:04:19.348     Type:
I: 2019-01-04 23:04:19.348 DMR Network Parameters
I: 2019-01-04 23:04:19.348     Address: vkbm.repeaters.info
I: 2019-01-04 23:04:19.348     Port: 62031
I: 2019-01-04 23:04:19.348     Local: 62032
I: 2019-01-04 23:04:19.348     Jitter: 360ms
I: 2019-01-04 23:04:19.348     Slot 1: enabled
I: 2019-01-04 23:04:19.348     Slot 2: enabled
I: 2019-01-04 23:04:19.348     Mode Hang: 3s
I: 2019-01-04 23:04:19.350 Info Parameters
I: 2019-01-04 23:04:19.350     Callsign: VK2RHK
I: 2019-01-04 23:04:19.350     RX Frequency: 222340000Hz
I: 2019-01-04 23:04:19.350     TX Frequency: 224940000Hz
I: 2019-01-04 23:04:19.350     Power: 1W
I: 2019-01-04 23:04:19.350     Latitude: -33.182800deg N
I: 2019-01-04 23:04:19.350     Longitude: -151.494095deg E
I: 2019-01-04 23:04:19.350     Height: 0m
I: 2019-01-04 23:04:19.350     Location: "Central Coast, NSW-AU"
I: 2019-01-04 23:04:19.350     Description: "50525 MMDVM_Bridge"
I: 2019-01-04 23:04:19.350     URL: "http:tg50525.repeaters.info"
M: 2019-01-04 23:04:19.350 DMR, Opening DMR Network
I: 2019-01-04 23:04:19.350 P25 Network Parameters
I: 2019-01-04 23:04:19.350     Gateway Address: 127.0.0.1
I: 2019-01-04 23:04:19.351     Gateway Port: 42020
I: 2019-01-04 23:04:19.351     Local Port: 32010
I: 2019-01-04 23:04:19.351     Mode Hang: 3s
M: 2019-01-04 23:04:19.351 P25, Opening INI file: DVSwitch.ini
M: 2019-01-04 23:04:19.351 P25, Setting [P25] Address -> 127.0.0.1
M: 2019-01-04 23:04:19.351 P25, Setting [P25] TXPort -> 34100
M: 2019-01-04 23:04:19.351 P25, Setting [P25] RXPort -> 34103
M: 2019-01-04 23:04:19.351 P25, Setting [P25] Slot -> 2
M: 2019-01-04 23:04:19.351 P25, Transmitting on 127.0.0.1:34100 and listening on port 34103.  Result = 1
M: 2019-01-04 23:04:19.351 Opening P25 network connection
I: 2019-01-04 23:04:19.351 RSSI
I: 2019-01-04 23:04:19.351     Mapping File: RSSI.dat
W: 2019-01-04 23:04:19.352 Cannot open the RSSI data file - RSSI.dat
I: 2019-01-04 23:04:19.352 DMR Id Lookups
I: 2019-01-04 23:04:19.352     File: /var/lib/mmdvm/DMRIds.dat
I: 2019-01-04 23:04:19.352     Reload: 24 hours
I: 2019-01-04 23:04:19.486 Loaded 120478 Ids to the DMR callsign lookup table
I: 2019-01-04 23:04:19.486 DMR RF Parameters
I: 2019-01-04 23:04:19.486     Id: 505204
I: 2019-01-04 23:04:19.486     Color Code: 1
I: 2019-01-04 23:04:19.487     Self Only: no
I: 2019-01-04 23:04:19.487     Embedded LC Only: yes
I: 2019-01-04 23:04:19.487     Dump Talker Alias Data: no
I: 2019-01-04 23:04:19.487     Prefixes: 0
I: 2019-01-04 23:04:19.487     Call Hang: 3s
I: 2019-01-04 23:04:19.487     TX Hang: 3s
I: 2019-01-04 23:04:19.487     Mode Hang: 10s
M: 2019-01-04 23:04:19.487 DMR, Opening INI file: DVSwitch.ini
M: 2019-01-04 23:04:19.487 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2019-01-04 23:04:19.487 DMR, Setting [DMR] TXPort -> 31100
M: 2019-01-04 23:04:19.487 DMR, Setting [DMR] RXPort -> 31103
M: 2019-01-04 23:04:19.487 DMR, Setting [DMR] Slot -> 2
M: 2019-01-04 23:04:19.487 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
I: 2019-01-04 23:04:19.487 P25 RF Parameters
I: 2019-01-04 23:04:19.487     Id: 505204
I: 2019-01-04 23:04:19.488     NAC: $293
I: 2019-01-04 23:04:19.488     UID Override: no
I: 2019-01-04 23:04:19.488     Self Only: no
I: 2019-01-04 23:04:19.488     Remote Gateway: no
I: 2019-01-04 23:04:19.488     Mode Hang: 10s
M: 2019-01-04 23:04:19.488 MMDVM_Bridge-20180423 is running
I: 2019-01-04 23:04:19.488 Started the DMR Id lookup reload thread
D: 2019-01-04 23:04:29.495 DMR, Sending authorisation
D: 2019-01-04 23:04:29.501 DMR, Sending configuration
M: 2019-01-04 23:04:29.506 DMR, Logged into the master successfully

And I did a PTT after this so as you can see nothing showing up for P25 but after that I did a PTT from DMR and this is what I get.

M: 2019-01-04 23:06:34.130 DMR Slot 2, received network voice header from VK2HK to TG 50525
M: 2019-01-04 23:06:34.636 P25, TX state = ON
I: 2019-01-04 23:06:34.636 P25, Begin TX: src=5052110 rpt=505204 dst=50525 slot=2 cc=1

M: 2019-01-04 23:06:34.805 DMR Talker Alias (Data Format 1, Received 6/22 char): 'VK2HK '
M: 2019-01-04 23:06:35.288 DMR Slot 2, received network end of voice transmission, 1.2 seconds, 0% packet loss, BER: 0.2%
M: 2019-01-04 23:06:35.293 P25, TX state = OFF



------------------
Regards
Ian (VK2HK)




On 5 Jan 2019, at 9:49 am, Steve N4IRS <szingman@...> wrote:

Then the problem is at MMDVM_Bridge. Absolutely nothing in the MMDVM_Bridge log when you TX on P25 through the reflector? Nothing strange in the startup of MMDVM_Bridge?

On 1/4/19 5:43 PM, Ian Tulley wrote:
Hi Steve, well that’s the problem, when I PTT of P25, I can see myself on the Reflector, but nothing on mmdvm_bridge log or and of the analog_bridge logs ??

------------------
Regards
Ian (VK2HK)




On 5 Jan 2019, at 9:20 am, Steve N4IRS <szingman@...> wrote:

Follow the data in the logs from program to program. Do you see the data in the log for MMDVM_Bridge? if yes, move on to analog_bridge. Same question. rinse repeat.

On 1/4/19 4:52 PM, Ian Tulley wrote:
Hi all, I recently had active a DMR <--> P25 Bridge with the help of Steve. There was an issue with setting up the audio due to some problem associated with md380-emu, but it was fixed and the bridge worked great and after some tweaking the audio and audio levels in both directions just worked. I have been monitoring for a couple of days and found last night that I only had audio from DMR to P25 but not in the reverse direction. This morning I have been trying hard to solve this issue but just cannot find out why.
This is on a VPS and I am running the P25Reflector/Gateway/Bridge plus NXDN Reflector and YSF Reflector all off the same server, but when the bridge was working all of this was running at the same time.
This is what I have done so far, so any further suggestions would be welcome.

Checked status of all services to make sure all running and yes all OK
Set both P25Reflector and P25Gateway into Debug mode and monitored the output but nothing found.
restarted all services but again no difference.
stoped md30-emu
stopped mmdvm_bridge
stopped analog_bridge_p25 and analog_bridge_dmr
restarted all services manually in seperate windows so I could monitor the output to the screen.

Results I am getting, 
If I key up on the P25 radio, I get nothing coming to any of the screen outputs, but can hear myself via another connected P25 Hotspot so I know the reflector is working OK
If I key up on DMR I can see all 3 screen outputs and can hear myself out of the P25 Radio.

Anyone have any idea where to start to look for this issue.

Ian (VK2HK)
 




7161 - 7180 of 9925