January 2021 - App_rpt-users - lists.keekles.org

Moderation?
by Watson Jones 24 Jan '21

24 Jan '21

FYI. ASL is now moderating posts to community. Will pttlink do the same for the mailing lists?

2 1

Posted: Community FAQ - January 2021
by PTTLink Admin 24 Jan '21

24 Jan '21

The PTTLink Team has posted a Community FAQ on the PTTLink mailing list. This FAQ addresses many of the questions that have been asked here and elsewhere. You are invited to review this post at: http://lists.pttlink.org/pipermail/pttlink/2021-January/000007.html

2 1

Voter board/rtcm link connect and disconnect email
by Joe Moskalski 24 Jan '21

24 Jan '21

I figured I would post this question to see if anyone has done this so I am not reinventing the wheel. I have a simulcast system with 5 sites that use voter boards/rtcm's. I would like to know when one of those sites loses connectivity with the host, when it comes back online again and which site it is by email preferably. Is there anyone who has done this or could anyone point me in the right direction to do it myself? Thanks for any help with this in advance!

3 2

New PTTLink Mailing List
by PTTLink Admin 21 Jan '21

21 Jan '21

A new mailing list specific to PTTLink announcements, topics, and discussions to include those of a non-technical nature is now available. for more information please visit: http://lists.pttlink.org/cgi-bin/mailman/listinfo/pttlink The PTTLink Team

4 4

Well well well - the ASL Board shows its colors again
by Stacy 20 Jan '21

20 Jan '21

In case anyone is wondering at the scope of the targeted actions towards me: Here is what my account listed previously for node numbers on the AllStarLink web portal: 2004 2005 2006 2020 41638 42088 42342 48404 2004 <https://www.pttlink.org/portal/nodes.php?call=KG7QIN&id=24916&action=edit> ASL-Testing 2005 <https://www.pttlink.org/portal/nodes.php?call=KG7QIN&id=24922&action=edit> ASL-Testing 2006 <https://www.pttlink.org/portal/nodes.php?call=KG7QIN&id=24925&action=edit> ASL-Testing 2020 <https://www.pttlink.org/portal/nodes.php?call=KG7QIN&id=3127&action=edit> ASL-Testing 41638 <https://www.pttlink.org/portal/nodes.php?call=KG7QIN&id=9108&action=edit> KG7QIN-1 42088 <https://www.pttlink.org/portal/nodes.php?call=KG7QIN&id=9553&action=edit> KG7QIN-2 42342 <https://www.pttlink.org/portal/nodes.php?call=KG7QIN&id=9802&action=edit> KG7QIN-3 48404 <https://www.pttlink.org/portal/nodes.php?call=KG7QIN&id=14943&action=edit> KG7QIN-4 This is what is lists as of now: 41638 <https://www.allstarlink.org/portal/nodes.php?call=KG7QIN&id=9108&action=edit> KG7QIN-1 KG7QIN 41638 only So tell me again if you think the ASL Board and it's minions aren't targeting me? Stacy KG7QIN

7 11

Allstarlink's new registration server
by Steve Jason 18 Jan '21

18 Jan '21

I have to admit, based upon all the rhetoric I had been reading, I was concerned about the new Allstarlink's new registration server. Happily, I feel so much better now. Their new system appears to be working flawlessly for the last two weeks. I see there are consistently over 5100 nodes registered at any one time on their new system. The nodelist and stats page comes up so much faster than the old registration server. I know this may be a controversial statement but I just don't see the point of setting up a separate PTTlink registration server. It adds a lot of unnecessary technical complications for no apparent gain. There are approximately only 50 nodes registering on the PTTlink system at any one time. I suspect a lot of those sites simply have static IP addresses in their configuration files and are none the wiser. They probably don't realize their nodes are not on the allstarlink system. Google Cloud Flare is really robust and has also sorts of backup and failover solutions. My work uses Cloud Flare and all our techs love it. I know there is a lot of hard feelings from the PTTlink group toward the Allstarlink Inc group. If the PTTlink folks want to set up their own separate registration then do it. Nevertheless, it is time for the PTTlink group to do the right thing and frankly grow up. They need to return Jim Dixon's IP ranges and the Allstarlink Git hub page back to Allstarlink Inc. Just because their feelings are hurt doesn't justify stealing the IP address ranges and talking control of the Github. - Shame on the PTTlink group for doing that. They are only punishing the Ham community by this childish and frankly criminal behavior. If they have some justification for stealing the IP addresses and the Github, I would love to hear it. I suspect we will hear crickets.

3 2

posting format
by George Csahanin 12 Jan '21

12 Jan '21

Last year I was removed from this list because I top-posted a reply to something. This was done by someone I had a whole lot of respect for until that point in time. So is that a rule or is top posting now ok here? GeorgeC W2DB 2360 28599

7 7

OT: seeking knowledgeable coder
by Steve L 10 Jan '21

10 Jan '21

Here is something a bit off topic to hopeful break the recent tension: Doug, AD8DP has been working on a project he calls DudeStar. It's open source application for amateur radio operators that allows RX and TX of D-Star, DMR, YSF, NXDN, P25 & M17. Either via a Desktop or Android application over the internet, or you can interface it to an analog rig: http://www.dudetronics.com/index.php/dude-star-radio-project He just recently started adding an IAX client to it. It does support software vocoding for the Digital Voice modes. However the code that is out there to do this for D-Star needs work as it sounds poor. If you know someone with some talent I did write about this in the most recent issue of TAPR's PSR, or you can read here; https://www.qsl.net/kb9mwr/projects/dv/codec/ambe.html Steve, KB9MWR

1 0

PTTLink Community Update - 7 Jan 2021
by PTTLink Admin 08 Jan '21

08 Jan '21

PTTLink Update: It’s been a quick past few days and the group wanted to give an update on some items: Implementation of multi-network app_rpt. Initial efforts have begun to implement multi-network support in app_rpt. The concept our team has is to make use of a what is called a network prefix code associated with groups wanting to run their own networks. PTTLink will be one of the first networks and we expect AllStarLink will follow suit. To help facilitate this we are reserving the first two network prefixes with the first to be assigned to AllStarLink (if they wish to participate) and the second to PTTLink. Methods to publicly request a network prefix will be created using a similar procedure to https://dn42.net. Anyone will be able to request a network prefix using a newly created public GitHub repository (more details below). By doing this on GitHub, all requests, and actions are completely visible to the community at large. There are a number of technical challenges. This includes default network dialing, keeping backward compatibility with the existing networks, selecting a method to dial other networks, and how to securely allow connections from other nodes. We’re hoping to have more details on this in the coming weeks, and look forward to community comments on our recommendations. Open sourcing PTTLink’s registration systems. It’s nearly impossible to add more networks to the Amateur Radio VoIP landscape without giving more tools to groups to build them. As such, we’re putting the final touches on a Python based registration system that is easy to configure and use. This can simplify other interested parties in forming their own networks. Our goal is to foster innovation within our humble corner of the internet and this will hopefully bring us closer. Iterations of new registration tools have been in development for a few months and were already deployed in experimental phases. This new iteration is geared towards general usage as opposed to internal use only. To be fully clear, the project to create this was started independently several months ago before the formation of PTTLink. Only after events that created PTTLink was the decision made by the developer to create the registration system in Python and license its use for the community. New GitHub Based Organization. We believe network agnostic code should not be held by any single network. That has the potential to stifle the innovation we believe in. As such, a new GitHub based organization was created to house all the community code bases associated with the VoIP interconnection of repeaters, this includes the above projects this team is releasing to the amateur radio community.: Please keep an eye on https://GitHub.com/Apprpt-Central for current and future releases. New PTTLink portal. With the implementation of multi-network support on app_rpt, we want interested parties to have the ability to keep the same node number(s) that were originally assigned by AllStarLink (“ASL”) on the PTTLink network. Part of this includes a new management portal for nodes within the PTTLink network. This isn’t a small feat, given the state of the existing codebase. We’ve elected to start from scratch and migrate interested parties. Multi-language node configuration menu. Looking to make the project more accessible to the community, we are implementing multilingual versions for the shell configuration menu, starting with the Spanish language, including a first time configuration menu. As follow ups to our Letter to the community: Regarding not revoking access: We pledge to not remove or modify any post on any mailing list, forum, or otherwise within our control. We believe everyone is entitled to their opinions. However, there will be times we’ll need to end threads, moderate, and maybe forbid someone from posting for periods of time. The process for moderation isn’t something to be decided quickly, and a better, clearer policy with the expectation of having community input will follow. Of course, in the interest of privacy to those involved, requests from individuals regarding their personal information will not be shared with anyone else. A reminder that adding a registration line to your IAX2 config file only signals your intent to have the same node number on PTTLink, all call routing will still remain on the AllStarLink network until the multi-network implementation is added to app_rpt - You should NOT remove any existing registration lines unless you no longer want to register with that network. A little about PTTLink: The PTTLink team is made up of multiple individuals trying to give back to the amateur radio community. We strongly believe in sharing knowledge and helping others get on the air. We have members from multiple countries and look forward to having representation from other nations. Our backgrounds include Internet and computer security, major internet and telecom networking, project management, and web design. Rather than speak of our individual experience and qualifications, the PTTLink team were the developers, administrators, and operations members of the AllStarLink network. During our tenure, AllStarLink moved from a single server to a world wide scalable redundant cluster, systems were redesigned, lines upon lines of backend code were written then debugged and our team provided all user level support. We look forward to working with community members on the development and innovation of interconnecting repeaters, hotspots, and hams all over the world, whether it be via the PTTLink Network or your very own network. Signed, The PTTLink Team

7 9

Netiquette
by PTTLink Admin 07 Jan '21

07 Jan '21

The app_rpt-users mailing list is for the benefit of the ham radio community and all members are required to adhere to the usage guidelines at http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users. The recent discussions on this list are not in the spirit of the guidelines for operational and technical content discussion. The repeated cross posting of publicly available statements from other organizations, spamming, harassment, and the back and forth mudslinging are not the type of lively discission this list is meant for. Users who continue to engage in such action may have their posts placed under moderation for review pending release or banned. If you feel this message is in error, please reach out to helpdesk at pttlink.org <mailto:helpdesk at pttlink.org> to discuss. Respectfully, PTTLink Admin Team

5 4