<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Stacy,<div><br></div><div>I have heard contradictory stories about who came up with the new registration server idea but the bottom line is no one but you cares. I can't tell you how many ideas I have come up with and either didn't implement them because I didn't have the time, the money, or the skills to actually see the project through to the end. I am not sure why you are trying to take away from Rob and Adam's thunder. The new registration server has been up now for almost 5 months and has an almost 100% uptime. The older system wasn't even close. Even Hamvoip stopped complaining about the allstarlink registration server not working properly once the new one was implemented. </div><div>I am hearing no criticism about the new system or frankly the board of Allstarlink from anyone but you all.</div><div><br></div><div>I know you have hurt feelings toward the board of directors of Allstarlink, you never got along with them, and didn't see eye to eye but it is time to just move on. Without choosing sides, sometimes certain people just don't have compatible personalities. <br></div><div><br></div><div>You all have been publicly criticizing the board of directors for a long time. It is no secret that you haven't agreed with them and also don't respect them. I know you were upset when they implemented Community versus mailman. You started it up again after they switched to Community. The very fact that Community is really active and we can go months before seeing a post on the mailing list shows that the users like Community better. Your actions were undermining the board. It should have been no surprise to you when they cutover to the new registration server behind your back. </div><div><br></div><div>Whether you want to admit it or not, you retaliating by deleting the Github, setting up PTTlink after you new full well the new registration server was stable, attempting to switch Jim Dixon's callsign away from Allstarlink with the FCC, not giving back control over Jim Dixon's Class C Ip addresses and keeping it for your PTTlink network, sending out emails to all the Allstarlink volunteers saying that they have been fired and you are somehow the new board, shows that they made the correct decision by not telling you in advance. </div><div><br></div><div>At this point, I really don't know what you are fighting for. Are you just fighting now because your feelings were hurt? From my standpoint, the board of directors have done a good job. Under their governance, Allstarlink Inc was granted 5013c status, they were able to secure the rights to Allstarlink from Jim Dixon's heir to them, they implemented a new registration server that is stable, there has been a 15% growth in Allstarlink in the last quarter, and they released the first new client in years. </div><div><br></div><div>I am sorry for you that it ended this way but it really is time for you to just move on.</div><div><br></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 22, 2021 at 10:59 PM Stacy via App_rpt-users <<a href="mailto:app_rpt-users@lists.keekles.org">app_rpt-users@lists.keekles.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div>
<p>The story behind the latest posting from Rob Vella KK9ROB,
regarding the "ASL Registration Code" post. Posted here to be a
matter of record. <br>
</p>
<p>--------------------------<br>
</p>
<p>The concept for the new registration was originally the idea of
Jason Kendall VE3YCA, however Jason was not able to spare cycles
to work on the new code as his job and life keeps him gainfully
employed. Around September 2020, when Rob joined in a discussion
on development with several of us, registration came up as well as
the desire to replace the Asterisk 13 based registration servers,
since they were still running a hack that was done to chan_iax by
me (with Tom Hayward KD7LXL doing a minor initial mod that led to
the start of the complete hack).<br>
</p>
<p>On 11 September 2020, Rob sent me a DM asking about ASL
registration and said "I've done a fair bit of socket programming
for a work project. You think it would be a worthwhile venture to
try to code an IAX server? I was thinking about it earlier.
Sniffed some packets, got a familiar with the registration flow.
It's only a few packets that are sent and looks pretty
straightforward."</p>
<p>"It should be fairly straightforward to do so. There's only 5-7
total packets to do a registration"</p>
<p> I told him he could and that there was an RFC for the protocol.</p>
<p>Then on 13 September from Rob:<br>
"won't be able to make the morning meeting but wanted to let you
know that I was successful in getting an IAX server setup. have
the full registration flow working (without verifying password,
just the packets) through UDP. going to work more on it tomorrow
to get is authenticating against real data."<br>
<br>
<img src="cid:1790466d8777601061b1" alt="" width="814" height="198"></p>
<p>"just need to do some refactoring. assuming that it's going to
hit an HTTP endpoint for registration, as Jason expressed, so i
setup something really basic to just authenticate or reject. i'll
be implementing that packet tomorrow."<br>
<br>
"so far it's super fast. less than 15ms to do a full registration.
excited to see where it goes."</p>
<p>(of course there is more, like on 15 September the DM about "i
implemented client functionality, so as a validation measure, i
could literally forward the reaffic back out to a real reg server"
or the reply by me asking if this was in pyton "no. its in NodeJS.
send the hate. lol"<br>
</p>
<p><br>
</p>
<p> Jason and Rob did quite a bit of testing on systems that were
setup just for this purpose. Rob even requested and was provided
the packet captures from the live registration servers and said it
helped a lot.<br>
</p>
<p>Rob's front end was talking to the back end API that Jason wrote
in Python. In fact, both pieces of code still exist in the now
pttlink registration servers and were running on the ASL servers.
Unfortunately, there was a bug in the IAXjs code that had to be
addressed, and Jason was able to do a work around to fix it.<br>
</p>
<p><br>
</p>
<p>And for the record: Jason actually published an updated version
of the Python code about 3-4 months ago here:
<a href="https://github.com/apprpt-central" target="_blank">https://github.com/apprpt-central</a><br>
<br>
<a href="https://github.com/Apprpt-Central/pyIAX-Register" target="_blank">https://github.com/Apprpt-Central/pyIAX-Register</a></p>
<p><br>
</p>
<p><br>
</p>
</div>
_______________________________________________<br>
App_rpt-users mailing list<br>
<a href="mailto:App_rpt-users@lists.keekles.org" target="_blank">App_rpt-users@lists.keekles.org</a><br>
<a href="http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users" rel="noreferrer" target="_blank">http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
<br>
To unsubscribe from this list please visit <a href="http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users" rel="noreferrer" target="_blank">http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
Unsubscribe posts to the list will result in public shaming. <br>
</blockquote></div>