Date   

Re: YSF to P25 always return fallbackID

Michael BD7MQB
 

I was using the script from
https://github.com/DVSwitch/DVSwitch-System-Builder/blob/master/Directories/usr/local/sbin/DMRIDUpdateBM.sh,
it pulled IDs from radioed.net

$/etc/cron.daily# vi DMRIDUpdateBM
# Generate new file
curl 'https://www.radioid.net/static/users.csv' 2>/dev/null | sed -e
's/[[:space:]]\+/ /g' > ${DMRIDFILE}

the format of this Id file is
$ head /var/lib/mmdvm/DMRIds.dat
Radio ID,Callsign,Name,City,State,Country,Remarks
1023001,VE3THW,Wayne Edward,Toronto,Ontario,Canada,DMR
1023002,VA3ECM,Mathieu Goulet,Ottawa-Hull,Quebec,Canada,CCS7


while the one from http://registry.dstar.su/dmr/DMRIds.php is
# Call ID Call Alias
2 LW1EOI Luis Mario
24001 SM6TKT Claes

there are different.

so i pull off the second one and give it a try, and it works!
may be you should update the script of DVSwitch-System-Builder?

because all service(p25gateway, p25reflector, etc..) are sharing the
same DMRIds, I wonder which format of DMDIds.dat will serve them all.

Tnx


On Sat, Dec 15, 2018 at 9:12 AM Steve N4IRS <szingman@msgstor.com> wrote:

Check the script and make sure it is pulling from here:
<http://registry.dstar.su/dmr/DMRIds.php>

On 12/14/18 8:03 PM, lazy walker wrote:
Yep but i think it’s fresh because the cron job just download it 2 hours ago :)

$ /var/lib/mmdvm# ls -l
total 12704
-rw-r--r-- 1 root root 6348707 Dec 15 06:26 DMRIds.dat
-rw-r--r-- 1 root root 6343785 Dec 15 06:25 DMRIds.dat.151218

On Dec 15, 2018, at 08:57, Steve N4IRS <szingman@msgstor.com> wrote:

Looks right. I will do some local testing this week. You might try to removed the datafile and download a fresh copy.

Steve

On 12/14/18 7:52 PM, lazy walker wrote:
Here is mine >
I: 2018-12-14 16:28:19.781 DMR Id Lookups
I: 2018-12-14 16:28:19.781 File: /var/lib/mmdvm/DMRIds.dat
I: 2018-12-14 16:28:19.781 Reload: 24 hours
I: 2018-12-14 16:28:19.874 Loaded 116072 Ids to the DMR callsign lookup table
I: 2018-12-14 16:28:19.874 YSF RF Parameters

On Sat, Dec 15, 2018 at 8:43 AM Steve N4IRS <szingman@msgstor.com> wrote:
Check when MMDVM_Bridge starts up. You should see this in the log:
I: 2018-12-02 11:33:12.161 DMR Id Lookups
I: 2018-12-02 11:33:12.161 File: /var/lib/mmdvm/DMRIds.dat
I: 2018-12-02 11:33:12.161 Reload: 24 hours
I: 2018-12-02 11:33:12.690 Loaded 117442 Ids to the DMR callsign lookup table
I: 2018-12-02 11:33:12.690 P25 RF Parameters
I: 2018-12-02 11:33:12.690 Started the DMR Id lookup reload thread

I bolded the 2 important entries. Check yours.

Steve N4IRS


On 12/14/18 7:33 PM, lazy walker wrote:

Hi Steve,
Yes i'm pretty sure we have the DmrId.dat file right :

grep BD7MQB /var/lib/mmdvm/DMRIds.dat
4607133,BD7MQB,Michael Changzhi Cai,Shenzhen/Guangdong,Hu Nan Guang
Dong Guang Xi,China,DMR


On Sat, Dec 15, 2018 at 12:18 AM Steve N4IRS <szingman@msgstor.com> wrote:

Please check MMDVM_Bridge.ini for:
[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat

Make sure that points to a valid ID file
Then make sure it contains a ID:
grep BD7MQB /var/lib/mmdvm/DMRIds.dat

Steve N4IRS

On 12/14/2018 10:37 AM, lazy walker wrote:

I: 2018-12-14 15:27:35.370 YSF, Lookup call BD7MQB returned id 0 -> 1234567










Re: YSF to P25 always return fallbackID

Steve N4IRS
 

Check the script and make sure it is pulling from here:
<http://registry.dstar.su/dmr/DMRIds.php>

On 12/14/18 8:03 PM, lazy walker wrote:
Yep but i think it’s fresh because the cron job just download it 2 hours ago :)

$ /var/lib/mmdvm# ls -l
total 12704
-rw-r--r-- 1 root root 6348707 Dec 15 06:26 DMRIds.dat
-rw-r--r-- 1 root root 6343785 Dec 15 06:25 DMRIds.dat.151218

On Dec 15, 2018, at 08:57, Steve N4IRS <szingman@msgstor.com> wrote:

Looks right. I will do some local testing this week. You might try to removed the datafile and download a fresh copy.

Steve

On 12/14/18 7:52 PM, lazy walker wrote:
Here is mine >
I: 2018-12-14 16:28:19.781 DMR Id Lookups
I: 2018-12-14 16:28:19.781 File: /var/lib/mmdvm/DMRIds.dat
I: 2018-12-14 16:28:19.781 Reload: 24 hours
I: 2018-12-14 16:28:19.874 Loaded 116072 Ids to the DMR callsign lookup table
I: 2018-12-14 16:28:19.874 YSF RF Parameters

On Sat, Dec 15, 2018 at 8:43 AM Steve N4IRS <szingman@msgstor.com> wrote:
Check when MMDVM_Bridge starts up. You should see this in the log:
I: 2018-12-02 11:33:12.161 DMR Id Lookups
I: 2018-12-02 11:33:12.161 File: /var/lib/mmdvm/DMRIds.dat
I: 2018-12-02 11:33:12.161 Reload: 24 hours
I: 2018-12-02 11:33:12.690 Loaded 117442 Ids to the DMR callsign lookup table
I: 2018-12-02 11:33:12.690 P25 RF Parameters
I: 2018-12-02 11:33:12.690 Started the DMR Id lookup reload thread

I bolded the 2 important entries. Check yours.

Steve N4IRS


On 12/14/18 7:33 PM, lazy walker wrote:

Hi Steve,
Yes i'm pretty sure we have the DmrId.dat file right :

grep BD7MQB /var/lib/mmdvm/DMRIds.dat
4607133,BD7MQB,Michael Changzhi Cai,Shenzhen/Guangdong,Hu Nan Guang
Dong Guang Xi,China,DMR


On Sat, Dec 15, 2018 at 12:18 AM Steve N4IRS <szingman@msgstor.com> wrote:

Please check MMDVM_Bridge.ini for:
[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat

Make sure that points to a valid ID file
Then make sure it contains a ID:
grep BD7MQB /var/lib/mmdvm/DMRIds.dat

Steve N4IRS

On 12/14/2018 10:37 AM, lazy walker wrote:

I: 2018-12-14 15:27:35.370 YSF, Lookup call BD7MQB returned id 0 -> 1234567







Re: YSF to P25 always return fallbackID

Michael BD7MQB
 

Yep but i think it’s fresh because the cron job just download it 2 hours ago :)

$ /var/lib/mmdvm# ls -l
total 12704
-rw-r--r-- 1 root root 6348707 Dec 15 06:26 DMRIds.dat
-rw-r--r-- 1 root root 6343785 Dec 15 06:25 DMRIds.dat.151218

On Dec 15, 2018, at 08:57, Steve N4IRS <szingman@msgstor.com> wrote:

Looks right. I will do some local testing this week. You might try to removed the datafile and download a fresh copy.

Steve

On 12/14/18 7:52 PM, lazy walker wrote:
Here is mine >
I: 2018-12-14 16:28:19.781 DMR Id Lookups
I: 2018-12-14 16:28:19.781 File: /var/lib/mmdvm/DMRIds.dat
I: 2018-12-14 16:28:19.781 Reload: 24 hours
I: 2018-12-14 16:28:19.874 Loaded 116072 Ids to the DMR callsign lookup table
I: 2018-12-14 16:28:19.874 YSF RF Parameters

On Sat, Dec 15, 2018 at 8:43 AM Steve N4IRS <szingman@msgstor.com> wrote:
Check when MMDVM_Bridge starts up. You should see this in the log:
I: 2018-12-02 11:33:12.161 DMR Id Lookups
I: 2018-12-02 11:33:12.161 File: /var/lib/mmdvm/DMRIds.dat
I: 2018-12-02 11:33:12.161 Reload: 24 hours
I: 2018-12-02 11:33:12.690 Loaded 117442 Ids to the DMR callsign lookup table
I: 2018-12-02 11:33:12.690 P25 RF Parameters
I: 2018-12-02 11:33:12.690 Started the DMR Id lookup reload thread

I bolded the 2 important entries. Check yours.

Steve N4IRS


On 12/14/18 7:33 PM, lazy walker wrote:

Hi Steve,
Yes i'm pretty sure we have the DmrId.dat file right :

grep BD7MQB /var/lib/mmdvm/DMRIds.dat
4607133,BD7MQB,Michael Changzhi Cai,Shenzhen/Guangdong,Hu Nan Guang
Dong Guang Xi,China,DMR


On Sat, Dec 15, 2018 at 12:18 AM Steve N4IRS <szingman@msgstor.com> wrote:

Please check MMDVM_Bridge.ini for:
[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat

Make sure that points to a valid ID file
Then make sure it contains a ID:
grep BD7MQB /var/lib/mmdvm/DMRIds.dat

Steve N4IRS

On 12/14/2018 10:37 AM, lazy walker wrote:

I: 2018-12-14 15:27:35.370 YSF, Lookup call BD7MQB returned id 0 -> 1234567








Re: YSF to P25 always return fallbackID

Steve N4IRS
 

Looks right. I will do some local testing this week. You might try to removed the datafile and download a fresh copy.

Steve

On 12/14/18 7:52 PM, lazy walker wrote:
Here is mine >
I: 2018-12-14 16:28:19.781 DMR Id Lookups
I: 2018-12-14 16:28:19.781 File: /var/lib/mmdvm/DMRIds.dat
I: 2018-12-14 16:28:19.781 Reload: 24 hours
I: 2018-12-14 16:28:19.874 Loaded 116072 Ids to the DMR callsign lookup table
I: 2018-12-14 16:28:19.874 YSF RF Parameters

On Sat, Dec 15, 2018 at 8:43 AM Steve N4IRS <szingman@msgstor.com> wrote:
Check when MMDVM_Bridge starts up. You should see this in the log:
I: 2018-12-02 11:33:12.161 DMR Id Lookups
I: 2018-12-02 11:33:12.161 File: /var/lib/mmdvm/DMRIds.dat
I: 2018-12-02 11:33:12.161 Reload: 24 hours
I: 2018-12-02 11:33:12.690 Loaded 117442 Ids to the DMR callsign lookup table
I: 2018-12-02 11:33:12.690 P25 RF Parameters
I: 2018-12-02 11:33:12.690 Started the DMR Id lookup reload thread

I bolded the 2 important entries. Check yours.

Steve N4IRS


On 12/14/18 7:33 PM, lazy walker wrote:

Hi Steve,
Yes i'm pretty sure we have the DmrId.dat file right :

grep BD7MQB /var/lib/mmdvm/DMRIds.dat
4607133,BD7MQB,Michael Changzhi Cai,Shenzhen/Guangdong,Hu Nan Guang
Dong Guang Xi,China,DMR


On Sat, Dec 15, 2018 at 12:18 AM Steve N4IRS <szingman@msgstor.com> wrote:

Please check MMDVM_Bridge.ini for:
[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat

Make sure that points to a valid ID file
Then make sure it contains a ID:
grep BD7MQB /var/lib/mmdvm/DMRIds.dat

Steve N4IRS

On 12/14/2018 10:37 AM, lazy walker wrote:

I: 2018-12-14 15:27:35.370 YSF, Lookup call BD7MQB returned id 0 -> 1234567







Re: YSF to P25 always return fallbackID

Michael BD7MQB
 

Here is mine >
I: 2018-12-14 16:28:19.781 DMR Id Lookups
I: 2018-12-14 16:28:19.781 File: /var/lib/mmdvm/DMRIds.dat
I: 2018-12-14 16:28:19.781 Reload: 24 hours
I: 2018-12-14 16:28:19.874 Loaded 116072 Ids to the DMR callsign lookup table
I: 2018-12-14 16:28:19.874 YSF RF Parameters

On Sat, Dec 15, 2018 at 8:43 AM Steve N4IRS <szingman@msgstor.com> wrote:

Check when MMDVM_Bridge starts up. You should see this in the log:
I: 2018-12-02 11:33:12.161 DMR Id Lookups
I: 2018-12-02 11:33:12.161 File: /var/lib/mmdvm/DMRIds.dat
I: 2018-12-02 11:33:12.161 Reload: 24 hours
I: 2018-12-02 11:33:12.690 Loaded 117442 Ids to the DMR callsign lookup table
I: 2018-12-02 11:33:12.690 P25 RF Parameters
I: 2018-12-02 11:33:12.690 Started the DMR Id lookup reload thread

I bolded the 2 important entries. Check yours.

Steve N4IRS


On 12/14/18 7:33 PM, lazy walker wrote:

Hi Steve,
Yes i'm pretty sure we have the DmrId.dat file right :

grep BD7MQB /var/lib/mmdvm/DMRIds.dat
4607133,BD7MQB,Michael Changzhi Cai,Shenzhen/Guangdong,Hu Nan Guang
Dong Guang Xi,China,DMR


On Sat, Dec 15, 2018 at 12:18 AM Steve N4IRS <szingman@msgstor.com> wrote:

Please check MMDVM_Bridge.ini for:
[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat

Make sure that points to a valid ID file
Then make sure it contains a ID:
grep BD7MQB /var/lib/mmdvm/DMRIds.dat

Steve N4IRS

On 12/14/2018 10:37 AM, lazy walker wrote:

I: 2018-12-14 15:27:35.370 YSF, Lookup call BD7MQB returned id 0 -> 1234567







Re: NXDNReflector with DVSwitch

Steve N4IRS
 

Who da thunk it.
Yes, NXDN, D-Star and P25 REQUIRE a gateway.
DMR does not need one.
YSF can use one and it does bring features to the table.

Mike and I have discussed removing the need for P25 and maybe NXDN. We have not decided yet.

Glad I was able to help you get it going.

Steve N4IRS

On 12/14/18 5:20 PM, JJ Cummings wrote:
You are correct sir... I had to undo all of the things that I had monkeyed with to try and make it work before and now it works perfectly!

On Fri, Dec 14, 2018 at 7:50 AM Steve N4IRS <szingman@...> wrote:
If I remember, the defaults in MMDVM_Bridge.ini and the defaults in NXDN_Gateway match up fine.

On 12/14/2018 9:36 AM, JJ Cummings wrote:
So how do I tie NXDNGateway into DVSwitch, I don't even see packets sourcing from DVSwitch toward anything... I'll try it with NXDNGateway in between such as follows and see what happens:

NXDNReflector <-> NXDNGateway <-> DVSwitch etc....

On Fri, Dec 14, 2018 at 7:28 AM Steve N4IRS <szingman@...> wrote:
OK,
Yes it works with YSF. No it does not work with NXDN. You need NXDNGateway.

On 12/14/2018 9:09 AM, JJ Cummings wrote:
I am not, I’m doing what I have with YSFReflector that works.. so 

NXDNReflector <-> DVSwitch <-> Analog_Bridge

Where DVSwitch of course makes the outbound connections to either side etc..

Sent from the iRoad

On Dec 13, 2018, at 23:47, Steve N4IRS <szingman@...> wrote:

Are you running NXDNGateway?




Re: YSF to P25 always return fallbackID

Steve N4IRS
 

Check when MMDVM_Bridge starts up. You should see this in the log:
I: 2018-12-02 11:33:12.161 DMR Id Lookups
I: 2018-12-02 11:33:12.161     File: /var/lib/mmdvm/DMRIds.dat
I: 2018-12-02 11:33:12.161     Reload: 24 hours
I: 2018-12-02 11:33:12.690 Loaded 117442 Ids to the DMR callsign lookup table
I: 2018-12-02 11:33:12.690 P25 RF Parameters
I: 2018-12-02 11:33:12.690 Started the DMR Id lookup reload thread

I bolded the 2 important entries. Check yours.

Steve N4IRS


On 12/14/18 7:33 PM, lazy walker wrote:
Hi Steve,
Yes i'm pretty sure we have the DmrId.dat file right :

      
grep BD7MQB /var/lib/mmdvm/DMRIds.dat
4607133,BD7MQB,Michael Changzhi Cai,Shenzhen/Guangdong,Hu Nan Guang
Dong Guang Xi,China,DMR


On Sat, Dec 15, 2018 at 12:18 AM Steve N4IRS <szingman@...> wrote:
Please check MMDVM_Bridge.ini for:
[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat

Make sure that points to a valid ID file
Then make sure it contains a ID:
grep BD7MQB /var/lib/mmdvm/DMRIds.dat

Steve N4IRS

On 12/14/2018 10:37 AM, lazy walker wrote:

I: 2018-12-14 15:27:35.370 YSF, Lookup call BD7MQB returned id 0 -> 1234567







Re: YSF to P25 always return fallbackID

Michael BD7MQB
 

Hi Steve,
Yes i'm pretty sure we have the DmrId.dat file right :
grep BD7MQB /var/lib/mmdvm/DMRIds.dat
4607133,BD7MQB,Michael Changzhi Cai,Shenzhen/Guangdong,Hu Nan Guang
Dong Guang Xi,China,DMR


On Sat, Dec 15, 2018 at 12:18 AM Steve N4IRS <szingman@msgstor.com> wrote:

Please check MMDVM_Bridge.ini for:
[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat

Make sure that points to a valid ID file
Then make sure it contains a ID:
grep BD7MQB /var/lib/mmdvm/DMRIds.dat

Steve N4IRS

On 12/14/2018 10:37 AM, lazy walker wrote:

I: 2018-12-14 15:27:35.370 YSF, Lookup call BD7MQB returned id 0 -> 1234567




--
http://greatcube.com


Re: NXDNReflector with DVSwitch

JJ Cummings
 

You are correct sir... I had to undo all of the things that I had monkeyed with to try and make it work before and now it works perfectly!


On Fri, Dec 14, 2018 at 7:50 AM Steve N4IRS <szingman@...> wrote:
If I remember, the defaults in MMDVM_Bridge.ini and the defaults in NXDN_Gateway match up fine.

On 12/14/2018 9:36 AM, JJ Cummings wrote:
So how do I tie NXDNGateway into DVSwitch, I don't even see packets sourcing from DVSwitch toward anything... I'll try it with NXDNGateway in between such as follows and see what happens:

NXDNReflector <-> NXDNGateway <-> DVSwitch etc....

On Fri, Dec 14, 2018 at 7:28 AM Steve N4IRS <szingman@...> wrote:
OK,
Yes it works with YSF. No it does not work with NXDN. You need NXDNGateway.

On 12/14/2018 9:09 AM, JJ Cummings wrote:
I am not, I’m doing what I have with YSFReflector that works.. so 

NXDNReflector <-> DVSwitch <-> Analog_Bridge

Where DVSwitch of course makes the outbound connections to either side etc..

Sent from the iRoad

On Dec 13, 2018, at 23:47, Steve N4IRS <szingman@...> wrote:

Are you running NXDNGateway?



Re: YSF to P25 always return fallbackID

Steve N4IRS
 

Please check MMDVM_Bridge.ini for:
[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat

Make sure that points to a valid ID file
Then make sure it contains a ID:
grep BD7MQB /var/lib/mmdvm/DMRIds.dat

Steve N4IRS

On 12/14/2018 10:37 AM, lazy walker wrote:
I: 2018-12-14 15:27:35.370 YSF, Lookup call BD7MQB returned id 0 -> 1234567


YSF to P25 always return fallbackID

Michael BD7MQB
 

Hi, I'm making a ysf-p25 bridge, but it hit fallbackID all the time, below are clips from log and my config

MMDVM_Bridge.log

M: 2018-12-14 15:27:35.370 YSF, received network data from BD7MQB     to ALL        at BD7MQB    

I: 2018-12-14 15:27:35.370 YSF, Lookup call BD7MQB returned id 0 -> 1234567

M: 2018-12-14 15:27:35.370 P25, TX state = ON

I: 2018-12-14 15:27:35.370 P25, Begin TX: src=1234567 rpt=0 dst=1 slot=2 cc=0

 

M: 2018-12-14 15:27:39.589 YSF, received network end of transmission, 4.5 seconds, 0% packet loss, BER: 0.0%

M: 2018-12-14 15:27:39.589 P25, TX state = OFF


DVSwitch.ini

[YSF]

Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)

TXPort = 35100                  ; Port to send AMBE TLV frames to (export)

RXPort = 35103                  ; Port to listen on (import)

FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one

ExportTG = 1                 ; Which TG to export

Slot = 2                        ; Export slot


MMDVM_Bridge.ini

[DMR Id Lookup]

File=/var/lib/mmdvm/DMRIds.dat

Time=24


i can sure that all dmr id are valid and can be found inside DMRIds.dat, any suggestion?
TNX


Re: NXDNReflector with DVSwitch

Steve N4IRS
 

If I remember, the defaults in MMDVM_Bridge.ini and the defaults in NXDN_Gateway match up fine.

On 12/14/2018 9:36 AM, JJ Cummings wrote:
So how do I tie NXDNGateway into DVSwitch, I don't even see packets sourcing from DVSwitch toward anything... I'll try it with NXDNGateway in between such as follows and see what happens:

NXDNReflector <-> NXDNGateway <-> DVSwitch etc....

On Fri, Dec 14, 2018 at 7:28 AM Steve N4IRS <szingman@...> wrote:
OK,
Yes it works with YSF. No it does not work with NXDN. You need NXDNGateway.

On 12/14/2018 9:09 AM, JJ Cummings wrote:
I am not, I’m doing what I have with YSFReflector that works.. so 

NXDNReflector <-> DVSwitch <-> Analog_Bridge

Where DVSwitch of course makes the outbound connections to either side etc..

Sent from the iRoad

On Dec 13, 2018, at 23:47, Steve N4IRS <szingman@...> wrote:

Are you running NXDNGateway?



Re: NXDNReflector with DVSwitch

Steve N4IRS
 

MMDVM_Bridge <-> NXDN_Gateway <-> NXDN Reflector

On 12/14/2018 9:36 AM, JJ Cummings wrote:
So how do I tie NXDNGateway into DVSwitch, I don't even see packets sourcing from DVSwitch toward anything... I'll try it with NXDNGateway in between such as follows and see what happens:

NXDNReflector <-> NXDNGateway <-> DVSwitch etc....

On Fri, Dec 14, 2018 at 7:28 AM Steve N4IRS <szingman@...> wrote:
OK,
Yes it works with YSF. No it does not work with NXDN. You need NXDNGateway.

On 12/14/2018 9:09 AM, JJ Cummings wrote:
I am not, I’m doing what I have with YSFReflector that works.. so 

NXDNReflector <-> DVSwitch <-> Analog_Bridge

Where DVSwitch of course makes the outbound connections to either side etc..

Sent from the iRoad

On Dec 13, 2018, at 23:47, Steve N4IRS <szingman@...> wrote:

Are you running NXDNGateway?



Re: NXDNReflector with DVSwitch

JJ Cummings
 

So how do I tie NXDNGateway into DVSwitch, I don't even see packets sourcing from DVSwitch toward anything... I'll try it with NXDNGateway in between such as follows and see what happens:

NXDNReflector <-> NXDNGateway <-> DVSwitch etc....

On Fri, Dec 14, 2018 at 7:28 AM Steve N4IRS <szingman@...> wrote:
OK,
Yes it works with YSF. No it does not work with NXDN. You need NXDNGateway.

On 12/14/2018 9:09 AM, JJ Cummings wrote:
I am not, I’m doing what I have with YSFReflector that works.. so 

NXDNReflector <-> DVSwitch <-> Analog_Bridge

Where DVSwitch of course makes the outbound connections to either side etc..

Sent from the iRoad

On Dec 13, 2018, at 23:47, Steve N4IRS <szingman@...> wrote:

Are you running NXDNGateway?


Re: NXDNReflector with DVSwitch

Steve N4IRS
 

OK,
Yes it works with YSF. No it does not work with NXDN. You need NXDNGateway.

On 12/14/2018 9:09 AM, JJ Cummings wrote:
I am not, I’m doing what I have with YSFReflector that works.. so 

NXDNReflector <-> DVSwitch <-> Analog_Bridge

Where DVSwitch of course makes the outbound connections to either side etc..

Sent from the iRoad

On Dec 13, 2018, at 23:47, Steve N4IRS <szingman@...> wrote:

Are you running NXDNGateway?


Re: NXDNReflector with DVSwitch

JJ Cummings
 

I am not, I’m doing what I have with YSFReflector that works.. so 

NXDNReflector <-> DVSwitch <-> Analog_Bridge

Where DVSwitch of course makes the outbound connections to either side etc..

Sent from the iRoad

On Dec 13, 2018, at 23:47, Steve N4IRS <szingman@...> wrote:

Are you running NXDNGateway?


Re: NXDNReflector with DVSwitch

Steve N4IRS
 

Are you running NXDNGateway?


NXDNReflector with DVSwitch

JJ Cummings
 

Maybe I am losing my mind (ideally) but I can't seem to get DVSwitch to connect to an instance of NXDNReflector on localhost.  tcpdump against lo shows zero attempted connections when the service starts.  I do have the [NXDN] and [NXDN Network] set to enable and the NXDNReflector is running locally on the same system.. the GatewayPort matches the [Network] Port=41400 in the NXDNReflector.ini configuration.  I am able to connect to the NXDNReflector from an outside host to the given port and I can see that all interfaces are listening on udp:0.0.0.0:41400

I do have YSF also enabled in the same DVSwitch configuration, but have tried to disable it also with the same results, I never see any connection attempts from DVSwitch to NXDNReflector... any ideas or pointers would be appreciated for sure at this point!

N0PKT
JJC


Re: AllStarLink/ASL-Install

Steve KC1AWV
 

Actually Steve, your comments do help me understand better. I kept getting hung up on the process of installing it the package way, and JJ was trying to explain to me that just building from source would be the easiest fix in this situation. Having a set of packages does make it significantly easier to bring up ASL, and provides an intuitive interface for managing the system as asterisk is by no means user friendly at times. Building from source for Manuel is the better option, since he is putting together a major customized system.

I have the opportunity to download a copy of the image that Manuel is working on, and I hope to follow JJ's instructions in order to get ASL working properly. Maybe I can use this to set up a walkthrough of how to build and set up ASL on Raspbian from source, unless someone else has already done so.

On Wed, Dec 12, 2018 at 9:17 PM Steve N4IRS <szingman@...> wrote:
Not much I can add. The last version I built used OSS. I put together some info on channel drivers that did not use OSS. Most of my work was spent moving ASl to a system that did not REQUIRE people to compile ASL. The images and the repository were intended for people to be able to do a simple apt get install or a apt-get upgrade when there were changes. DAHDI has always been a pain in the ass. I spent a lot of time trying to make it easy to upgrade. That is where DKMS came in.

I am no longer involved in ASL development. I know that the dev team for ASL is working to move the repo from DVSwitch to the ASL servers. I hope this happens sooon so that I can start restructure our repo.

Steve N4IRS



Re: AllStarLink/ASL-Install

Steve N4IRS
 

Not much I can add. The last version I built used OSS. I put together some info on channel drivers that did not use OSS. Most of my work was spent moving ASl to a system that did not REQUIRE people to compile ASL. The images and the repository were intended for people to be able to do a simple apt get install or a apt-get upgrade when there were changes. DAHDI has always been a pain in the ass. I spent a lot of time trying to make it easy to upgrade. That is where DKMS came in.

I am no longer involved in ASL development. I know that the dev team for ASL is working to move the repo from DVSwitch to the ASL servers. I hope this happens sooon so that I can start restructure our repo.

Steve N4IRS

On 12/12/18 5:59 PM, Stephen Miller wrote:
The known good instructions from N4IRS state to hold the Raspbian kernel, and from a previous post in this thread it has to do with sound modules that may or may not be present in newer Raspbian kernels, which looks like a dependency for dahdi to compile correctly with DKMS.

Were you able to get ASL installed and configured with a newer Raspbian kernel?

I could be off target there, and think N4IRS could weigh in and edify.

7021 - 7040 of 9595