Date   

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.


Re: AllStarLink/ASL-Install

Steve KC1AWV
 

Ok, I understand a whole lot more now. I appreciate the insight!

I would like to read your instructions about app_rpt, and continue the "learn by doing" approach to further help others. My experience with asterisk so far has been with corporate phone switching, and I felt that ASL would be an easy pickup...

So, if I read you right, manually compiling the dahdi module, modprobe, and check if it's loaded should help bring asterisk up for Manuel? If I don't have the chance to get to his machine again, I'll try it at home and see if I can type up a block of commands that he can try.

Thanks!


On Wed, Dec 12, 2018 at 11:58 PM JJ Cummings <cummingsj@...> wrote:
That’s what I’m talking about when I reference “unless you are using a URI” in terms of sound “modules” which is just OSS that was deprecated long ago (over 10 years), was marked broken early this year, and has to do with hardware level access to the URI.  If you are not interfacing to a radio then there is no need to hold the Kernel back at all.  Even if there is a need for a URI you can still use ALSA and emulate OSS which I am doing and it works very well... if interested you can look for my instructions on app_rpt.

Maybe I missed part of the thread, I’ll read back through... 



Sent from the iRoad




--
Steve Miller
KC1AWV


Re: AllStarLink/ASL-Install

Manuel Díaz
 

thanks for the info
I am working with an image of my own and has the kernel 4.14.79 and I can not download it from version

with the image ASL_1.01-20180228-armhf-raspbian-stretch-image.img, it works perfectly for me.

but with my own image it does not work.

Greetings.

 

De: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] En nombre de Pierre Martel
Enviado el: miércoles, 12 de diciembre de 2018 19:15
Para: main@dvswitch.groups.io
Asunto: Re: [DVSwitch] AllStarLink/ASL-Install

 

Did you used the raspberry pi image from the wiki??? 

 

 

Cause with this image and the readme I was able to do a node in half an hour using usbradio and another hour to make allmon2 work as I wished. 

 

I would really advise you to use both the readme and image file to rebuild from scratch. It will surely be faster then trying to fix your installation. Then when it works. Back up the sd card image. Then if you wish to install a desktop just do it as a normal command line raspbian. 

 

 

 

Le mer. 12 déc. 2018 12:49 p.m., Stephen Miller <smiller@...> a écrit :

After taking an initial look at the Pi in question, I've noticed that the dahdi pseudo device is not loading, preventing asterisk from starting. lsmod shows no dahdi module installed. The /etc/modules file does show that the module is listed.

dpkg-reconfigure for the dahdi module completes, but there is no module to be loaded.


Re: AllStarLink/ASL-Install

Manuel Díaz
 

thanks for the info
I am working with an image of my own and has the kernel 4.14.79 and I can not download it from version

with the image ASL_1.01-20180228-armhf-raspbian-stretch-image.img, it works perfectly for me.

but with my own image it does not work.

Greetings.

 

De: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] En nombre de Mike KB8JNM
Enviado el: miércoles, 12 de diciembre de 2018 20:35
Para: main@DVSwitch.groups.io
Asunto: Re: [DVSwitch] AllStarLink/ASL-Install

 

uname -r

4.9.80-v7+
Is what I have

What happens with newer kernel is you loose sound support which dahdi needs to compile right.

Not sure what for him to do but the fastest way to the end is to start over with the asl pi stretch image and hold the kernel before updating as the readme states.

http://dvswitch.org/files/ASL_Images/Raspberry_Pi/Stretch/ASL_1.01-20180228-armhf-raspbian-stretch-image.readme

http://dvswitch.org/files/ASL_Images/Raspberry_Pi/Stretch/

http://enhanced.github.io/2018/08/ASL_With_ALSA

 

...mike/kb8jnm

 

On 12/12/2018 2:21 PM, Stephen Miller wrote:

It looks like Manuel is making a system of his own design, including all the digital and analog networking systems into one device. While his implementation is a custom one, a lot of the ideas are solid and should be compatible. The install of ASL onto the Pi with other software shouldn't be an issue, just need to be aware that a custom setup like that will have some issues that will need to be worked out before moving the system from alpha to a beta.

Putting the kernel headers on hold might be a little late for that, since the kernel version that was on the Pi was one that looked newer, I think. The DKMS build flashed by faster than I would have liked. Which kernel runs on the Pi image?


Re: AllStarLink/ASL-Install

Manuel Díaz
 

thanks for the info
I am working with an image of my own and has the kernel 4.14.79 and I can not download it from version

with the image ASL_1.01-20180228-armhf-raspbian-stretch-image.img, it works perfectly for me.

but with my own image it does not work.

Greetings.

 

De: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] En nombre de Pierre Martel
Enviado el: miércoles, 12 de diciembre de 2018 20:41
Para: main@dvswitch.groups.io
Asunto: Re: [DVSwitch] AllStarLink/ASL-Install

 

You are right, he is pulling a specific design. The center part of his design is ASL, and it is the most complicated part to run, when ASL run in a stable way. then he should build on that.. 

 

fixing ASL need some pretty specific know how. and if he updated the kernels he will have some problem as the latest kernel dont have the needed module to run ASL without some addon. recompilation of the kernels and so on... 

 

 

 

Garanti sans virus. www.avast.com

 

Le mer. 12 déc. 2018 à 14:21, Stephen Miller <smiller@...> a écrit :

It looks like Manuel is making a system of his own design, including all the digital and analog networking systems into one device. While his implementation is a custom one, a lot of the ideas are solid and should be compatible. The install of ASL onto the Pi with other software shouldn't be an issue, just need to be aware that a custom setup like that will have some issues that will need to be worked out before moving the system from alpha to a beta.

Putting the kernel headers on hold might be a little late for that, since the kernel version that was on the Pi was one that looked newer, I think. The DKMS build flashed by faster than I would have liked. Which kernel runs on the Pi image?


Re: AllStarLink/ASL-Install

Manuel Díaz
 

thanks for the info
I am working with an image of my own and has the kernel 4.14.79 and I can not download it from version

Greetings.

 

 

De: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] En nombre de Stephen Miller
Enviado el: miércoles, 12 de diciembre de 2018 20:48
Para: main@DVSwitch.groups.io
Asunto: Re: [DVSwitch] AllStarLink/ASL-Install

 

Oh boy, yeah I think the version that's on there was at least 4.14, I think I may have seen 4.17 in there too.

Manuel,

The root cause of asl-menu option 5 not working is that the asterisk service on your Pi is not running.
Diagnosing the cause of asterisk not running showed there was a timeout waiting for "dev-dahdi-pseudo"
The reason for the timeout is that there is supposed to be a dahdi kernel module that loads at boot time, which is not loading.
The module requires an older version of the kernel on the Pi (4.9) because newer kernels do not have sound support, which dahdi needs in order to compile correctly.
The kernel version that I remember seeing installed was at least 4.14.

I agree with Mike KB8JNM, your best bet would be to start over with a new install of Raspbian Stretch, with kernel 4.9. Make sure to follow the directions included with the ASL image, which will prevent Raspbian from upgrading your kernel to an incompatible version.

sudo apt-mark hold raspberrypi-kernel-headers raspberrypi-kernel
sudo apt-get update
sudo apt-get upgrade -y 
sudo reboot


I would start your OS buildout with Allstar first and make sure that works, then add in the other software you want after.

- Steve KC1AWV


Re: AllStarLink/ASL-Install

Manuel Díaz
 

thanks for the info
I am working with an image of my own and has the kernel 4.14.79

with the image ASL_1.01-20180228-armhf-raspbian-stretch-image.img, it works perfectly for me.

but with my own image it does not work.

Greetings.

 

De: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] En nombre de JJ Cummings
Enviado el: jueves, 13 de diciembre de 2018 0:58
Para: main@DVSwitch.groups.io
Asunto: Re: [DVSwitch] AllStarLink/ASL-Install

 

That’s what I’m talking about when I reference “unless you are using a URI” in terms of sound “modules” which is just OSS that was deprecated long ago (over 10 years), was marked broken early this year, and has to do with hardware level access to the URI.  If you are not interfacing to a radio then there is no need to hold the Kernel back at all.  Even if there is a need for a URI you can still use ALSA and emulate OSS which I am doing and it works very well... if interested you can look for my instructions on app_rpt.

 

Maybe I missed part of the thread, I’ll read back through... 

 

 

Sent from the iRoad


On Dec 12, 2018, at 15:59, Stephen Miller <smiller@...> 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.


Re: AllStarLink/ASL-Install

Manuel Díaz
 

thanks for the info
I am working with an image of my own and has the kernel 4.14.79

with the image ASL_1.01-20180228-armhf-raspbian-stretch-image.img, it works perfectly for me.

but with my own image it does not work.

Greetings.

 

De: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] En nombre de Stephen Miller
Enviado el: miércoles, 12 de diciembre de 2018 23:59
Para: main@DVSwitch.groups.io
Asunto: Re: [DVSwitch] AllStarLink/ASL-Install

 

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.


Re: AllStarLink/ASL-Install

Manuel Díaz
 

thanks for the info
I am working with an image of my own and has the kernel 4.14.79

with the image ASL_1.01-20180228-armhf-raspbian-stretch-image.img, it works perfectly for me.

but with my own image it does not work.

Greetings.

 

De: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] En nombre de JJ Cummings
Enviado el: miércoles, 12 de diciembre de 2018 23:23
Para: main@dvswitch.groups.io
Asunto: Re: [DVSwitch] AllStarLink/ASL-Install

 

I disagree with rebuilding and with holding the kernel unless there is a good reason to do so.

 

The only reason to hold the kernel back is if you need to use a URI to interface with a radio.. other wise it's just a dahdi kernel module issue so why not compile from source which is already located on the box since you installed from the repo... then reboot and boom you are running with the latest kernel...

 

the source will be located under /usr/src/asl-dahdi-linux-2.11.1/ 

 

go into that directory as root and type "make install" - as long as this is successful reboot and you will be set with regard to dahdi.

 

On Wed, Dec 12, 2018 at 12:47 PM Stephen Miller <smiller@...> wrote:

Oh boy, yeah I think the version that's on there was at least 4.14, I think I may have seen 4.17 in there too.

Manuel,

The root cause of asl-menu option 5 not working is that the asterisk service on your Pi is not running.
Diagnosing the cause of asterisk not running showed there was a timeout waiting for "dev-dahdi-pseudo"
The reason for the timeout is that there is supposed to be a dahdi kernel module that loads at boot time, which is not loading.
The module requires an older version of the kernel on the Pi (4.9) because newer kernels do not have sound support, which dahdi needs in order to compile correctly.
The kernel version that I remember seeing installed was at least 4.14.

I agree with Mike KB8JNM, your best bet would be to start over with a new install of Raspbian Stretch, with kernel 4.9. Make sure to follow the directions included with the ASL image, which will prevent Raspbian from upgrading your kernel to an incompatible version.

sudo apt-mark hold raspberrypi-kernel-headers raspberrypi-kernel
sudo apt-get update
sudo apt-get upgrade -y 
sudo reboot


I would start your OS buildout with Allstar first and make sure that works, then add in the other software you want after.

- Steve KC1AWV


Re: AllStarLink/ASL-Install

JJ Cummings
 

That’s what I’m talking about when I reference “unless you are using a URI” in terms of sound “modules” which is just OSS that was deprecated long ago (over 10 years), was marked broken early this year, and has to do with hardware level access to the URI.  If you are not interfacing to a radio then there is no need to hold the Kernel back at all.  Even if there is a need for a URI you can still use ALSA and emulate OSS which I am doing and it works very well... if interested you can look for my instructions on app_rpt.

Maybe I missed part of the thread, I’ll read back through... 



Sent from the iRoad

On Dec 12, 2018, at 15:59, Stephen Miller <smiller@...> 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.


Re: AllStarLink/ASL-Install

Steve KC1AWV
 

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.


Re: AllStarLink/ASL-Install

JJ Cummings
 

I disagree with rebuilding and with holding the kernel unless there is a good reason to do so.

The only reason to hold the kernel back is if you need to use a URI to interface with a radio.. other wise it's just a dahdi kernel module issue so why not compile from source which is already located on the box since you installed from the repo... then reboot and boom you are running with the latest kernel...

the source will be located under /usr/src/asl-dahdi-linux-2.11.1/ 

go into that directory as root and type "make install" - as long as this is successful reboot and you will be set with regard to dahdi.

On Wed, Dec 12, 2018 at 12:47 PM Stephen Miller <smiller@...> wrote:
Oh boy, yeah I think the version that's on there was at least 4.14, I think I may have seen 4.17 in there too.

Manuel,

The root cause of asl-menu option 5 not working is that the asterisk service on your Pi is not running.
Diagnosing the cause of asterisk not running showed there was a timeout waiting for "dev-dahdi-pseudo"
The reason for the timeout is that there is supposed to be a dahdi kernel module that loads at boot time, which is not loading.
The module requires an older version of the kernel on the Pi (4.9) because newer kernels do not have sound support, which dahdi needs in order to compile correctly.
The kernel version that I remember seeing installed was at least 4.14.

I agree with Mike KB8JNM, your best bet would be to start over with a new install of Raspbian Stretch, with kernel 4.9. Make sure to follow the directions included with the ASL image, which will prevent Raspbian from upgrading your kernel to an incompatible version.

sudo apt-mark hold raspberrypi-kernel-headers raspberrypi-kernel
sudo apt-get update
sudo apt-get upgrade -y 
sudo reboot

I would start your OS buildout with Allstar first and make sure that works, then add in the other software you want after.

- Steve KC1AWV


Re: AllStarLink/ASL-Install

Steve KC1AWV
 

Oh boy, yeah I think the version that's on there was at least 4.14, I think I may have seen 4.17 in there too.

Manuel,

The root cause of asl-menu option 5 not working is that the asterisk service on your Pi is not running.
Diagnosing the cause of asterisk not running showed there was a timeout waiting for "dev-dahdi-pseudo"
The reason for the timeout is that there is supposed to be a dahdi kernel module that loads at boot time, which is not loading.
The module requires an older version of the kernel on the Pi (4.9) because newer kernels do not have sound support, which dahdi needs in order to compile correctly.
The kernel version that I remember seeing installed was at least 4.14.

I agree with Mike KB8JNM, your best bet would be to start over with a new install of Raspbian Stretch, with kernel 4.9. Make sure to follow the directions included with the ASL image, which will prevent Raspbian from upgrading your kernel to an incompatible version.

sudo apt-mark hold raspberrypi-kernel-headers raspberrypi-kernel
sudo apt-get update
sudo apt-get upgrade -y 
sudo reboot

I would start your OS buildout with Allstar first and make sure that works, then add in the other software you want after.

- Steve KC1AWV


Re: AllStarLink/ASL-Install

Pierre Martel
 

You are right, he is pulling a specific design. The center part of his design is ASL, and it is the most complicated part to run, when ASL run in a stable way. then he should build on that.. 

fixing ASL need some pretty specific know how. and if he updated the kernels he will have some problem as the latest kernel dont have the needed module to run ASL without some addon. recompilation of the kernels and so on... 



Garanti sans virus. www.avast.com


Le mer. 12 déc. 2018 à 14:21, Stephen Miller <smiller@...> a écrit :
It looks like Manuel is making a system of his own design, including all the digital and analog networking systems into one device. While his implementation is a custom one, a lot of the ideas are solid and should be compatible. The install of ASL onto the Pi with other software shouldn't be an issue, just need to be aware that a custom setup like that will have some issues that will need to be worked out before moving the system from alpha to a beta.

Putting the kernel headers on hold might be a little late for that, since the kernel version that was on the Pi was one that looked newer, I think. The DKMS build flashed by faster than I would have liked. Which kernel runs on the Pi image?


Re: AllStarLink/ASL-Install

Mike KB8JNM
 

uname -r

4.9.80-v7+
Is what I have

What happens with newer kernel is you loose sound support which dahdi needs to compile right.

Not sure what for him to do but the fastest way to the end is to start over with the asl pi stretch image and hold the kernel before updating as the readme states.

http://dvswitch.org/files/ASL_Images/Raspberry_Pi/Stretch/ASL_1.01-20180228-armhf-raspbian-stretch-image.readme

http://dvswitch.org/files/ASL_Images/Raspberry_Pi/Stretch/

http://enhanced.github.io/2018/08/ASL_With_ALSA


...mike/kb8jnm


On 12/12/2018 2:21 PM, Stephen Miller wrote:
It looks like Manuel is making a system of his own design, including all the digital and analog networking systems into one device. While his implementation is a custom one, a lot of the ideas are solid and should be compatible. The install of ASL onto the Pi with other software shouldn't be an issue, just need to be aware that a custom setup like that will have some issues that will need to be worked out before moving the system from alpha to a beta.

Putting the kernel headers on hold might be a little late for that, since the kernel version that was on the Pi was one that looked newer, I think. The DKMS build flashed by faster than I would have liked. Which kernel runs on the Pi image?


Re: AllStarLink/ASL-Install

Steve KC1AWV
 

It looks like Manuel is making a system of his own design, including all the digital and analog networking systems into one device. While his implementation is a custom one, a lot of the ideas are solid and should be compatible. The install of ASL onto the Pi with other software shouldn't be an issue, just need to be aware that a custom setup like that will have some issues that will need to be worked out before moving the system from alpha to a beta.

Putting the kernel headers on hold might be a little late for that, since the kernel version that was on the Pi was one that looked newer, I think. The DKMS build flashed by faster than I would have liked. Which kernel runs on the Pi image?

7261 - 7280 of 9820