On Dec 24, 2018, at 12:41, Mike Besemer <mwbesemer@cox.net> wrote:
No disrespect intended here either, but this is something that has bothered me since I first put my toe into the ASL realm.
I spent several years writing Technical Orders for the U.S. Air Force. It was mind-numbing work at times and I was responsible not only to write the documentation, but to verify every single step. I was extremely experienced with the processes I was documenting and that was a great blessing – but it was also a curse. It was very difficult to verify – line by line – process which I not only knew from rote, but which I developed myself from scratch. We went through many iterations of changes and had individuals from all experience levels verify the tasks before we signed off on them. Needless to say, the process took a lot of time and effort.
That being said, one the tasks were documented, the quality of our maintenance skyrocketed and the necessity for maintenance personnel to have to rely on the development team for guidance dropped like a stone.
This is a philosophy I still carry with me today. I work in a one-deep position and am responsible for servicing over 1500 personnel, with my primary customers being full colonels and Lt Colonels. I don’t have time to take care of all of them personally and the Colonels usually don't have time to wait for me to help them. It keep afloat, I've fully documented all of my processes and published them to a SharePoint which all my customers have access to. Each process is tested and revised as needed to make sure each of them is 'Colonel-proof. It has taken me years to fully document and test everything, but I've been given raving reviews of my work and the number of urgent phone calls and emails has dropped into the noise, allowing me to concentrate on day-to-day work.
ASL needs to do the same. The documentation that is available is scattered, often does not provide step by step directions, and is sometimes outdated. Yes, it would take a lot of time to update and test all the processes, but once that was done the developers would have time to concentrate on revisions and enhancements. It's just a matter of philosophies changing.
Anyway, that's my 2-cents worth.
Merry Christmas,
Mike
WM4B
From: App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org] On Behalf Of Mike
Sent: Monday, December 24, 2018 1:48 PM
To: app_rpt-users@lists.allstarlink.org
Subject: Re: [App_rpt-users] Neophyte user
Let me say this, and please know that I am not picking at anyone. No disrespect intended.
Running a Open Source Asterisk Server, before you make radios as phone extensions,
requires skill and knowledge of Linux operating system,
And the Open source Asterisk Telephony System,
Some, not all know something of programming and or shell scripts.
Some, not all taking this to task also have no electronics knowledge,
Some, not all know something of radio repeater systems. Function and terminology.
So, if anyone thinks, when they can't check at least half of those boxes above, that this is just going to be easy when you may not know of the terminology alone to ask the right questions... think again.
Many volunteers put this together. I too can complain about the lack of GREAT documentation but know that it is all work in progress and someone has to take their free time to bring that to you. I have taken time to contribute to the wiki but find it very messy from the structure of it to find anything, let alone add to it.
To fill-in the gaps, we have this email posting board to help each other. And admins and authors read and reply also.
If you are not going to use it to get help and understanding when you first run into a problem, it then becomes your fault that you don't or can't understand your issues.
Personally, I don't have all the answers but nobody has the answers to questions that are not asked.
But ask your question.
Include the version of software you are working with,
Include the hardware you are applying it to since a Pi is much different than a PC. And a HF remote base is quite different than a repeater.
AND/OR include the method of COR/PTT usb radio type interface etc.
The better you include this info and any 'outside the norm things' you are doing,
the more and better the answers you are likely to receive. I don't like spending the next 6 emails just to find those things to give you a accurate answer and likely, I will not reply. (I may not be alone)
I often give bad answers because it was not clear to me what you have or what you are doing with your issue.
Anyway, know that I feel your pain and frustration, that's why I spend time paying attention to the mail board and I have better things that can be done also.
The only stupid question is the one you don't ask. Everyone here knows it is not always so easy. That's why we are here.
Also know I have always said, "if it works out of the box, you learn nothing". How do you grow/create your own with that ? You might as well pay someone to fix it for you when it's broke or want to create something out of the ordinary.
All that said, it has been my personal recommendation for many years that if you are a total newb to all of this, to create your server and one node that works with dahdi-pseudo channel driver and get network connectivity and understand the command structures before you proceed to add radio/external ports. Take that for what it is worth in your circumstance. Most folks make it harder on themselves to take this all in, by trying to do it all at once. And when there is a issue in the end, it becomes hard for anyone to figure out at what level the issue is.
My hope is that many of you get in depth with how all this works and provide the next level of 'cool stuff' going forward.
...mike/kb8jnm
On 12/23/2018 10:04 PM, Pierre Martel wrote:
I wonder why I was able to make allstarlink work out right of the box.
Must be cause I was reading the docs and almost all of the post in the mailling list.
I did ask a few question. But those were very specific if my memory is right...
Le dim. 23 déc. 2018 à 21:14, Serge Bérubé <ve2abc@ve2abc.com> a écrit :
I had the very same results, after 11 tryes , I get results… well I had to discover( guess) many things and learn the linux slang…
May I help you ? PM me at ve2abc at ve2abc dot com…
Best Regards, Serge
De : App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org] De la part de Mike
Envoyé : 23 décembre 2018 10:08
À : app_rpt-users@lists.allstarlink.org
Objet : Re: [App_rpt-users] Neophyte user
You might start with a specific question and if you wish to provide a statement,
make it the version of software you are questioning and the hardware you are applying it to.
You might include what you have accomplished and working so we know where you are.
That's the best way I know to get help. Ask the group but don't leave them in the blind to 'make guesses' to what you have or want.
...mike/kb8jnm
On 12/23/2018 8:30 AM, AD2TM wrote:
Over the past year I have been unsuccessful at getting an installation to Allstar Asterisk to function. I even tried the, excuse me, Ham VOIP version and did not have any luck with that either. I have tried the X86 version and the Raspberry version. Yes I installed the X86 version on an old Dell laptop. The Pi version was on a Pi 3, with a 16GB card.
Is there or can someone create a step by step guide for installation? Do not say all you have to do is follow the setup script. That did not work for me.
The material on the website is very confusing to me.
I only want to set up a simple remote base. I have the RMK URI. The radio I am using is a Motorola CDM1500 LS.
73
Tom AD2TM
_______________________________________________
App_rpt-users mailing list
App_rpt-users@lists.allstarlink.org
http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
Garanti sans virus. www.avast.com
_______________________________________________
App_rpt-users mailing list
App_rpt-users@lists.allstarlink.org
http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
_______________________________________________
App_rpt-users mailing list
App_rpt-users@lists.allstarlink.org
http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
_______________________________________________
App_rpt-users mailing list
App_rpt-users@lists.allstarlink.org
http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
