[App_rpt-users] Allmon/2

Fri Dec 21 04:34:57 UTC 2018

app_rpt have been incorporated in asterisk at version asterisk-0.3.0

the app_rpt.c file was first seen in the app/ directory there... and the
app_rpt.c started with this:

/** @file app_rpt.c
 *
 * Asterisk -- A telephony toolkit for Linux.
 *
 * Radio Repeater program
 *
 * Copyright (C) 2002, Jim Dixon
 *
 * Jim Dixon <jim at lambdatel.com>
 *
 * This program is free software, distributed under the terms of
 * the GNU General Public License
 *
 */

#include <asterisk/lock.h>
#include <asterisk/file.h>
#include <asterisk/logger.h>
#include <asterisk/channel.h>
#include <asterisk/pbx.h>
#include <asterisk/module.h>
#include <asterisk/translate.h>
#include <asterisk/options.h>
 events
this kind of raise question on your memory of events in those days..

Have a great day!

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Garanti
sans virus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Le jeu. 20 déc. 2018 à 13:51, william howell <william-t2 at live.com> a écrit :

> Well, I used the Asterisk software back in the early days (1999-2000) of
> the beginning of Asterisk I still have the first release or so and most
> releases since).....and honestly don't recall Jim Dixon having any major
> say over any portion of Asterisk, specifically app_rpt, back then. I do
> recall several conversations with Mark Spencer and/or his staff back in the
> day (2001-2005) during the early releases of Asterisk pertaining to app_rpt
> and why it wasn't being advanced when the rest of the Asterisk version was
> being released. At that time it was apparent that there was more interest
> in the full-blown PBX portion of Asterisk than there was in the radio
> control portion of the Asterisk software. I never heard of Jim Dixon until
> Asterisk had stated that they were not going to further app_rpt module and
> that anyone thinking of advancing it was free to do so. So base on the
> experience I have with Digium & Asterisk software since its inception I'm
> not sure that even Jim Dixon had any proprietary rights to the source code
> of the app_rpt module than anyone else, other than Mark Spencer, did/does.
>
> I've used Asterisk software since 1999-2000 as it was/is intended for. For
> both PBX systems and as a means to do radio control as I need. I personally
> don't care who has "rights" to it as I will always consider that Mark
> Spencer is the only one that has the rights to recognition for its
> development to begin with. What, if any, disputes among software
> developers, court battles, and/or any other conflicts there may be doesn't
> interest me period as long as the software is and remains open source use
> and that the software is being advanced. As long as advancements are being
> made I will go with those that do the advancements, or, I will move on,
> reinvent the wheel, and write my own code and be done.
>
> Frankly, there is no reason that both HamVoip & AllstarLink can't work
> together, stop the division, settle differences, and open the source code
> the two of you have to all of us that are willing to help advance it. It's
> not like there's going to be tons of money to make off of it as there are
> enough of us that will eventually get tired of the BS, the lack of
> advancement that makes it worth using, and will start our own source code
> that will work for all those wanting to control their repeater/radios.
>
> You must know by now that there are more users, other than Licensed
> Amateur Radio Operators, that have and are obtaining the software and using
> it for linking their repeaters across this nation. So why not decide to
> work together and make it useful for all.
>
> That's my rant for the day, thanks for your input.
>
> Have a great day,
>
> William R Howell, CEO
> Amphibicom, A Division of
> Amphibian Technologies & Solutions
> 20587 State Highway 19 South Suite #13
> Canton, Texas 75103
> Office: 903-287-0069
> Fax: 972-275-6069
>
>
> Consulting, Sales and Services that specialize in the areas of wire &
> wireless communications, EOC (Emergency Operations Center), PEOC (Portable
> Emergency Operation Centers), Dispatch Consoles & Software, Central
> Dispatch Communications Centers, and Call Center Equipment.....
> Installation, Maintenance, and Management.......
>
>
> Where Two-way Radios, Computers, Telephones, Telephone Land Lines, VOIP,
> Hardware & Software all come together........ Working together to make for
> better communications within our communities thru clubs and social
> networking....... A place where Commercial, Public Safety, GMRS, Amateur,
> Marine, Aircraft, and Military operators learn how to coexist together thru
> shared communications....... If it can be done ---- we can do it.....
>
>
>
> ------------------------------
> *From:* App_rpt-users <app_rpt-users-bounces at lists.allstarlink.org> on
> behalf of Marshall Oldham <ke6pcv at cal-net.org>
> *Sent:* Wednesday, December 19, 2018 3:49 PM
> *To:* 'Users of Asterisk app_rpt'
> *Subject:* Re: [App_rpt-users] Allmon/2
>
>
> William,
>
>
>
> If you must know the truth, included in my reply below is a post that was
> made to the app_rpt in October from Kevin Custer.
>
>
>
> This should explain the history and why we have two  outlets or groups.
>
>
>
> 73
>
>
>
> Marshall - ke6pcv
>
>
>
>
>
>
>
>
>
>
>
> *From:* App_rpt-users [mailto:app_rpt-users-bounces at lists.allstarlink.org]
> *On Behalf Of *Kevin Custer
> *Sent:* Wednesday, October 24, 2018 7:03 PM
> *To:* Users of Asterisk app_rpt
> *Subject:* Re: [App_rpt-users] App_rpt-users Digest, Vol 116, Issue 13
>
>
>
> AllStarLink, Inc. is an assembly of people selected to carry out the
> project and vision of Jim Dixon (SK).  Jim is now passed on and was the
> inventor of AllStar Link.  He is also responsible for many aspects of
> Asterisk and mainly wrote the app_rpt software application that makes
> Asterisk capable of being a full blown repeater controller, capable of
> several ports per computer host.  AllStar has always been an open source
> project, as Jim Dixon had no interest in selling it outright, or as a paid
> application.  To say the very least, Jim Dixon was all about open source.
> The AllStar project is protected by GPL,
> <https://www.novell.com/coolsolutions/feature/1532.html> a license that's
> visible when viewing the Source Code of AllStarLink and every derivative of
> it.
>
> The folks at AllStarLink put a lot of time, effort, and money into
> continuing the AllStar Link project.  They are fully responsible for
> vetting new members (making sure they a licensed amateur radio operators),
> issuing node numbers, running servers to allow connections between its
> members, and a website to make it all happen.  AllStarLink provides free
> support via several contact methods.   AllStarLink is (mainly) funded by
> several individuals who regularly donate to it.  In other words, it's
> generally free to the users.  This doesn't mean it's free to maintain.
> There are real monthly costs associated with running it.  I've personally
> carried the monthly fees myself.  I'm not mentioning this for any
> recognition - I'm simply trying to let folks know it's not free to make
> this project available to the amateur public.
>
> Jim Dixon was a brilliant man, but not a easy one to work with.  I had a
> few uncomfortable conversations with Jim myself.  But, you soon learned
> that it was what it was, and you played as he wanted.
>
> The folks at HamVoIP had several ideas of their own and were mostly met
> with resistance from Jim.  That led to Jim making the statement that the
> folks at HamVoIP should fork the project, and do as they please.  That's
> exactly what happened, but there's a catch....
>
> If you fork a project protected by the GPL, you must do one of two things:
> 1 - Use it for your own purposes and NOT distribute or support it publicly.
> 2 - Comply with the GPL and release your changes to the public.
>
> If (and only if) you do the latter, are you allowed to redistribute your
> version of the work.  What does this mean?
>
> It's perfectly legal to fork a Linux project, but, if you are going to
> redistribute a derivative to the general public, you MUST release the
> source code.
>
> NO ONE would have an issue with the HamVoIP project if they simply
> complied, and released the source.   Wouldn't that be the "right" thing to
> do?
>
> HamVoIP does not directly support the project financially, or otherwise.
> They are not responsible for the membership.  In recent months, they are
> quick to take credit for all of AllStar, but they don't really have much to
> do with it.  They even go on to make a very negative public perception of
> all of the folks at AllStarLink.  For example, just go look at their home
> page and read the section on "August 15, 2018".  While the transition of
> making the server stack more reliable and diverse didn't go exactly as
> planned, we're not a bunch of buffoons either.  Personally, attacks like
> this hurt the core of what we're trying to do - continue with a great
> project.  They hurt me and the rest of the team personally - but we're
> supposed to pretend they don't exist.  Bryan has more time (and possibly
> more money) in the AllStar project than anyone else since Jim's passing.
> Maybe now you understand his position more clearly.  AllStarLink is
> responsible for the most of it, but HamVoIP has led people to believe THEY
> are AllStar, but they're not.  And - now you know why.
>
> Kevin Custer W3KKC
> Board Member
> AllStarLink, Inc.
>
>
>
>
> *From:* App_rpt-users [mailto:app_rpt-users-bounces at lists.allstarlink.org]
> *On Behalf Of *william howell
> *Sent:* Wednesday, December 19, 2018 6:59 AM
> *To:* Users of Asterisk app_rpt
> *Subject:* Re: [App_rpt-users] Allmon/2
>
>
>
> For the powers to be or are,
>
>
>
> Who is the "other group" claiming to be developers of Allstar that has and
> is being mentioned and what is the difference between this Allstar here and
> that Allstar there? Are the two not open source and both base source code
> the same?  Why are there apparently two different outlets and not just one
> as there was?
>
>
> Only asking for my benefit and the benefit of others that still, like me,
> may not know.
>
>
>
>
>
> Thank you,
>
>
>
> William R Howell, CEO
> Amphibicom, A Division of
> Amphibian Technologies & Solutions
> 20587 State Highway 19 South Suite #13
> Canton, Texas 75103
> Office: 903-287-0069
> Fax: 972-275-6069
>
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at 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.
>

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Garanti
sans virus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20181220/c72d47e5/attachment.html>