[App_rpt-users] custom node announcement?

[Bryan Fields]

On 11/25/14, 6:57 PM, Bryan D. Boyle wrote:
>>> The link I posted from 2009 said there was a way via the web portal.
>>> 
> It's now almost 2015.  The software has advanced a bit, as well as the
> population using it.  And still a volunteer effort.  And the documentation,
> such as it is, really should be read as a starting point, not canonical in
> many regards.  That's what the usefulness of list archive is for.

I'm using the source, and finding that in there is why I'm asking.  A search
of the archives turned up one post about it from 2009.

If the docs and the source aren't accurate, and the list is not authoritative,
then what is?

>>> If this is not a feature, why is it in the script?
> Because of 'cruft', limited numbers of people maintaining the core because
> they have real jobs.
> 
> if it's not doing what you want, open up vi, delete the lines, save as a
> new file, and mod the crontab to use your new script.  It won't affect the
> net.

I can't change that which I don't control.  That's why I'm asking.  Apparently
that's some kinda offense to people here.


> Options have been publicized (i use KB2EAR's repository) to work around
> issues like this, bought the O'Reilly Asterisk tome for more insight, and
> search voip.net for even more insights.  That's the beauty of open source:
> if something isn't working like you think it should, you can either wait
> for someone to fix it, fix it yourself, or figure out a workaround.

This begs the question, why not have it as an official part of the Allstar
network, the hooks are there, and certainly someone has rsync setup on
allstarlink.org for it.

Heck make the other repository the main one in the allstar source tree that
everyone builds from.  This is what makes Allstar a network vs. app_rpt and
linking to others via IAX.

>>> I'd question which repository is the proper one for the Allstar
>>> network.
>>> 
> Any one that works for you.

Well that's an issue.

I'm asking the network why we don't have this as a network wide standard.  I
don't care which one Allstar uses, but lets get everyone using the same one
across the network.

Hell I'm happy to write up some code and formal docs for it.

>>> Can anyone see how this can be confusing? --
> No, because it's a cooperative effort that, except for the registration
> server, is not controlled by any one person and depends on the system
> operator to manage their own system.

I'm asking about the Allstar network standards.  There is network standards
for audio, authentication, numbers, etc.  This certainly would fall under that
as well.

If you can't see how this is confusing we're failing at marketing Allstar and
to a lesser extent app_rpt.

-- 
Bryan Fields

727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net