Bryan I will let you lead the way lets start a software development side and lets start testing different combinations of things together and share it with the group.. The only way to learn is via failure.. The problem that i see through handling everything through mailing lists is the attachment issues.. How are you suppose to share your work openly and easily searchable.. I like email but to me it seems kinda of an older solution to a huge problem.. Loren Tedford (KC9ZHV) Phone: Fax: Email: lorentedford@gmail.com Email: KC9ZHV@KC9ZHV.com http://www.lorentedford.com http://www.kc9zhv.com http://forum.kc9zhv.com http://hub.kc9zhv.com http://Ltcraft.net <http://ltcraft.net/> On Mon, Jul 11, 2016 at 3:20 PM, Bryan Fields <bryan@bryanfields.net> wrote:

No forums please. I think github has plenty and if we need a mailing list I'm happy to setup another one.

On July 11, 2016 4:05:03 PM EDT, Loren Tedford <lorentedford@gmail.com> wrote:

...

I can try to put together a forum if you think we need it I am willing to host it just to get the project started but I want to make it clear we hand everything back over to the opensource community from the beginning!

As far as storage not a problem here..

Loren Tedford (KC9ZHV) Phone: Fax: Email: lorentedford@gmail.com Email: KC9ZHV@KC9ZHV.com http://www.lorentedford.com http://www.kc9zhv.com http://forum.kc9zhv.com http://hub.kc9zhv.com http://Ltcraft.net <http://ltcraft.net/>

On Mon, Jul 11, 2016 at 3:01 PM, Steve Wright <info@meshnetworks.co.nz> wrote:

...

On 12/07/16 07:05, Steve Zingman <szingman@msgstor.com> wrote:

...

There have been discussion as to how to move forward. The people involved are the people that will do the work. We can not be "left behind" and the tools needed are available. app_rpt is Open Source, Asterisk is Open Source. The concepts and methods used by app_rpt are readily apparent. They can be re-created. [....] On 7/11/2016 2:33 PM, Loren Tedford wrote:

...

Now where do we begin? I know absolutely nothing about coding however I do know if we don't do some thing fast we will be left behind and the tools others may have had available to port their stuff through may not be available for us..

Where do we join this group?

Set it up. _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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.

-- Bryan Fields 727-409-1194 http://bryanfields.net

_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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.

Git hub cost on an individual users space i have a daca center environment why use git hub Loren Tedford (KC9ZHV) Phone:618-553-0806 Fax: 1-618-551-2755 Email: lorentedford@gmail.com Email: KC9ZHV@KC9ZHV.com http://www.lorentedford.com http://www.kc9zhv.com http://forum.kc9zhv.com http://hub.kc9zhv.com http://Ltcraft.net <http://ltcraft.net/> On Mon, Jul 11, 2016 at 3:37 PM, Bryan Fields <bryan@bryanfields.net> wrote:

Have you looked into github?

It's got almost everything needed, and Steve uses it now along with thousands of,other projects.

On July 11, 2016 4:25:06 PM EDT, Loren Tedford <lorentedford@gmail.com> wrote:

...

Bryan I will let you lead the way lets start a software development side and lets start testing different combinations of things together and share it with the group.. The only way to learn is via failure..

The problem that i see through handling everything through mailing lists is the attachment issues.. How are you suppose to share your work openly and easily searchable..

I like email but to me it seems kinda of an older solution to a huge problem..

Loren Tedford (KC9ZHV) Phone: Fax: Email: lorentedford@gmail.com Email: KC9ZHV@KC9ZHV.com http://www.lorentedford.com http://www.kc9zhv.com http://forum.kc9zhv.com http://hub.kc9zhv.com http://Ltcraft.net <http://ltcraft.net/>

On Mon, Jul 11, 2016 at 3:20 PM, Bryan Fields <bryan@bryanfields.net> wrote:

...

No forums please. I think github has plenty and if we need a mailing list I'm happy to setup another one.

On July 11, 2016 4:05:03 PM EDT, Loren Tedford <lorentedford@gmail.com> wrote:

...

I can try to put together a forum if you think we need it I am willing to host it just to get the project started but I want to make it clear we hand everything back over to the opensource community from the beginning!

As far as storage not a problem here..

Loren Tedford (KC9ZHV) Phone: Fax: Email: lorentedford@gmail.com Email: KC9ZHV@KC9ZHV.com http://www.lorentedford.com http://www.kc9zhv.com http://forum.kc9zhv.com http://hub.kc9zhv.com http://Ltcraft.net <http://ltcraft.net/>

On Mon, Jul 11, 2016 at 3:01 PM, Steve Wright <info@meshnetworks.co.nz> wrote:

...

On 12/07/16 07:05, Steve Zingman <szingman@msgstor.com> wrote:

...

There have been discussion as to how to move forward. The people involved are the people that will do the work. We can not be "left behind" and the tools needed are available. app_rpt is Open Source, Asterisk is Open Source. The concepts and methods used by app_rpt are readily apparent. They can be re-created. [....] On 7/11/2016 2:33 PM, Loren Tedford wrote:

...

Now where do we begin? I know absolutely nothing about coding however I do know if we don't do some thing fast we will be left behind and the tools others may have had available to port their stuff through may not be available for us..

Where do we join this group?

Set it up. _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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.

-- Bryan Fields 727-409-1194 http://bryanfields.net

_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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.

-- Bryan Fields 727-409-1194 http://bryanfields.net

_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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.

I think we need a BBS system. I have some extra DID'S we can use.... On Jul 11, 2016 4:20 PM, "Bryan Fields" <bryan@bryanfields.net> wrote:

No forums please. I think github has plenty and if we need a mailing list I'm happy to setup another one.

On July 11, 2016 4:05:03 PM EDT, Loren Tedford <lorentedford@gmail.com> wrote:

...

I can try to put together a forum if you think we need it I am willing to host it just to get the project started but I want to make it clear we hand everything back over to the opensource community from the beginning!

As far as storage not a problem here..

Loren Tedford (KC9ZHV) Phone: Fax: Email: lorentedford@gmail.com Email: KC9ZHV@KC9ZHV.com http://www.lorentedford.com http://www.kc9zhv.com http://forum.kc9zhv.com http://hub.kc9zhv.com http://Ltcraft.net <http://ltcraft.net/>

On Mon, Jul 11, 2016 at 3:01 PM, Steve Wright <info@meshnetworks.co.nz> wrote:

...

On 12/07/16 07:05, Steve Zingman <szingman@msgstor.com> wrote:

...

There have been discussion as to how to move forward. The people involved are the people that will do the work. We can not be "left behind" and the tools needed are available. app_rpt is Open Source, Asterisk is Open Source. The concepts and methods used by app_rpt are readily apparent. They can be re-created. [....] On 7/11/2016 2:33 PM, Loren Tedford wrote:

...

Now where do we begin? I know absolutely nothing about coding however I do know if we don't do some thing fast we will be left behind and the tools others may have had available to port their stuff through may not be available for us..

Where do we join this group?

Set it up. _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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.

-- Bryan Fields 727-409-1194 http://bryanfields.net

_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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.

Sorry to revive an old thread, but take a look at this: https://github.com/KG7QIN/AllStarLink-Asterisk-1.8 -Stacy On 7/11/2016 2:33 PM, Scott Zimmerman wrote:

Loren et. all:

There is already a forum present that can be utilized as needed: AllStarNode.com

I quickly threw this together a few years ago. It was intended to be used exactly how you were describing. It never really took off, however.

You are more than welcome to join. If you do, drop me an e-mail and I'll make you a super admin, so you can change things as you see fit.

Scott

Scott Zimmerman Amateur Radio Call N3XCC 474 Barnett Road Boswell, PA 15531

On 7/11/2016 4:05 PM, Loren Tedford wrote:

...

I can try to put together a forum if you think we need it I am willing to host it just to get the project started but I want to make it clear we hand everything back over to the opensource community from the beginning!

As far as storage not a problem here..

Loren Tedford (KC9ZHV) Phone: Fax: Email: lorentedford@gmail.com <mailto:lorentedford@gmail.com> Email: KC9ZHV@KC9ZHV.com <mailto:KC9ZHV@KC9ZHV.com> http://www.lorentedford.com <http://www.lorentedford.com/> http://www.kc9zhv.com <http://www.kc9zhv.com/> http://forum.kc9zhv.com <http://forum.kc9zhv.com/> http://hub.kc9zhv.com <http://hub.kc9zhv.com/> http://Ltcraft.net<http://ltcraft.net/>

On Mon, Jul 11, 2016 at 3:01 PM, Steve Wright <info@meshnetworks.co.nz <mailto:info@meshnetworks.co.nz>> wrote:

On 12/07/16 07:05, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:

There have been discussion as to how to move forward. The people involved are the people that will do the work. We can not be "left behind" and the tools needed are available. app_rpt is Open Source, Asterisk is Open Source. The concepts and methods used by app_rpt are readily apparent. They can be re-created. [....] On 7/11/2016 2:33 PM, Loren Tedford wrote:

Now where do we begin? I know absolutely nothing about coding however I do know if we don't do some thing fast we will be left behind and the tools others may have had available to port their stuff through may not be available for us..

Where do we join this group?

Set it up. _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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.

No security patches, if I remember correctly. There are some tweaks to the IAX2 protocol in the 1.4 version of Asterisk, that needed to be done here for backwards compatibility. If I remember correctly, it deals with the call token for the denial of service problems IAX2 has without it. This is very rough code, and while it does work, some parts are in need or work. I started on this last year, October, and got to where you see it in less than a month. Most of the pieces were already there with 1.8 (this is the last version that the app_rpt code appeared before Digium completely dropped it), but due to to a change in the base code, app_rpt did not work without a mod to (the base code). There were other changes too that needed to be done to bring the version of app_rpt forward to a more recent revision than what sits in the repository. It required going through the entire app_rpt and modules which were ported and updating the calls to functions and variables used. I've successfully used this with AllStar and connecting to node 2560 of the WIN system. Echolink has a problem with DTMF (see issues), but it is a start. I'd love to have other contribute to this. It was done as an intermediate version to bridge the gap to a newer version of Asterisk. -Stacy KG7QIN On 9/9/2016 12:36 PM, Loren Tedford wrote:

Wow This is cool!! I can't wait to play and see how it works!

Great job!! We needed development! Is their by chance any security patches of the whole iax2 issues does anyone know?

Loren Tedford (KC9ZHV) Phone: Fax: Email: lorentedford@gmail.com <mailto:lorentedford@gmail.com> Email: KC9ZHV@KC9ZHV.com <mailto:KC9ZHV@KC9ZHV.com> http://www.lorentedford.com <http://www.lorentedford.com/> http://www.kc9zhv.com <http://www.kc9zhv.com/> http://forum.kc9zhv.com <http://forum.kc9zhv.com/> http://hub.kc9zhv.com <http://hub.kc9zhv.com/> http://Ltcraft.net<http://ltcraft.net/> http://voipham.com

On Fri, Sep 9, 2016 at 2:06 PM, Stacy <kg7qin@arrl.net <mailto:kg7qin@arrl.net>> wrote:

Sorry to revive an old thread, but take a look at this: https://github.com/KG7QIN/AllStarLink-Asterisk-1.8 <https://github.com/KG7QIN/AllStarLink-Asterisk-1.8>

-Stacy

On 7/11/2016 2:33 PM, Scott Zimmerman wrote:

Loren et. all:

There is already a forum present that can be utilized as needed: AllStarNode.com

I quickly threw this together a few years ago. It was intended to be used exactly how you were describing. It never really took off, however.

You are more than welcome to join. If you do, drop me an e-mail and I'll make you a super admin, so you can change things as you see fit.

Scott

Scott Zimmerman Amateur Radio Call N3XCC 474 Barnett Road Boswell, PA 15531

On 7/11/2016 4:05 PM, Loren Tedford wrote:

I can try to put together a forum if you think we need it I am willing to host it just to get the project started but I want to make it clear we hand everything back over to the opensource community from the beginning!

As far as storage not a problem here..

Loren Tedford (KC9ZHV) Phone: Fax: Email: lorentedford@gmail.com <mailto:lorentedford@gmail.com> <mailto:lorentedford@gmail.com <mailto:lorentedford@gmail.com>> Email: KC9ZHV@KC9ZHV.com <mailto:KC9ZHV@KC9ZHV.com <mailto:KC9ZHV@KC9ZHV.com>> http://www.lorentedford.com <http://www.lorentedford.com/> http://www.kc9zhv.com <http://www.kc9zhv.com/> http://forum.kc9zhv.com <http://forum.kc9zhv.com/> http://hub.kc9zhv.com <http://hub.kc9zhv.com/> http://Ltcraft.net<http://ltcraft.net/ <http://ltcraft.net/>>

On Mon, Jul 11, 2016 at 3:01 PM, Steve Wright <info@meshnetworks.co.nz <mailto:info@meshnetworks.co.nz> <mailto:info@meshnetworks.co.nz <mailto:info@meshnetworks.co.nz>>> wrote:

On 12/07/16 07:05, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com> <mailto:szingman@msgstor.com <mailto:szingman@msgstor.com>>> wrote:

There have been discussion as to how to move forward. The people involved are the people that will do the work. We can not be "left behind" and the tools needed are available. app_rpt is Open Source, Asterisk is Open Source. The concepts and methods used by app_rpt are readily apparent. They can be re-created. [....] On 7/11/2016 2:33 PM, Loren Tedford wrote:

Now where do we begin? I know absolutely nothing about coding however I do know if we don't do some thing fast we will be left behind and the tools others may have had available to port their stuff through may not be available for us..

Where do we join this group?

Set it up. _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org <mailto:App_rpt-users@ohnosec.org> <mailto:App_rpt-users@ohnosec.org <mailto:App_rpt-users@ohnosec.org>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users>

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.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@ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users>

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.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@ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users>

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.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@ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users>

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.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.

Yes, he does. He helped me with some of the problems I was having with app_rpt and making calls. There are still some quirks there, but without Jim's advice on it, I would have had an even harder time. -Stacy On 9/9/2016 1:22 PM, Jim Duuuude wrote:

Just in case any one didn't know that already, I REALLY LOVE OPEN SOURCE!!

Jim, WB6NIL

------------------------------------------------------------------------ *From:* app_rpt-users-bounces@ohnosec.org <app_rpt-users-bounces@ohnosec.org> on behalf of Stacy <kg7qin@arrl.net> *Sent:* Friday, September 9, 2016 1:03 PM *To:* Loren Tedford *Cc:* app_rpt mailing list *Subject:* Re: [App_rpt-users] toy throwing time?

No security patches, if I remember correctly.

There are some tweaks to the IAX2 protocol in the 1.4 version of Asterisk, that needed to be done here for backwards compatibility. If I remember correctly, it deals with the call token for the denial of service problems IAX2 has without it.

This is very rough code, and while it does work, some parts are in need or work. I started on this last year, October, and got to where you see it in less than a month. Most of the pieces were already there with 1.8 (this is the last version that the app_rpt code appeared before Digium completely dropped it), but due to to a change in the base code, app_rpt did not work without a mod to (the base code).

There were other changes too that needed to be done to bring the version of app_rpt forward to a more recent revision than what sits in the repository. It required going through the entire app_rpt and modules which were ported and updating the calls to functions and variables used.

I've successfully used this with AllStar and connecting to node 2560 of the WIN system. Echolink has a problem with DTMF (see issues), but it is a start.

I'd love to have other contribute to this. It was done as an intermediate version to bridge the gap to a newer version of Asterisk.

-Stacy

KG7QIN

On 9/9/2016 12:36 PM, Loren Tedford wrote:

...

Wow This is cool!! I can't wait to play and see how it works!

Great job!! We needed development! Is their by chance any security patches of the whole iax2 issues does anyone know?

Loren Tedford (KC9ZHV) Phone: Fax: Email: lorentedford@gmail.com <mailto:lorentedford@gmail.com> Email: KC9ZHV@KC9ZHV.com <mailto:KC9ZHV@KC9ZHV.com> http://www.lorentedford.com <http://www.lorentedford.com/> http://www.kc9zhv.com <http://www.kc9zhv.com/> http://forum.kc9zhv.com <http://forum.kc9zhv.com/> http://hub.kc9zhv.com <http://hub.kc9zhv.com/> http://Ltcraft.net<http://ltcraft.net/> http://voipham.com

On Fri, Sep 9, 2016 at 2:06 PM, Stacy <kg7qin@arrl.net <mailto:kg7qin@arrl.net>> wrote:

Sorry to revive an old thread, but take a look at this: https://github.com/KG7QIN/AllStarLink-Asterisk-1.8 <https://github.com/KG7QIN/AllStarLink-Asterisk-1.8>

-Stacy

On 7/11/2016 2:33 PM, Scott Zimmerman wrote:

Loren et. all:

There is already a forum present that can be utilized as needed: AllStarNode.com

I quickly threw this together a few years ago. It was intended to be used exactly how you were describing. It never really took off, however.

You are more than welcome to join. If you do, drop me an e-mail and I'll make you a super admin, so you can change things as you see fit.

Scott

Scott Zimmerman Amateur Radio Call N3XCC 474 Barnett Road Boswell, PA 15531

On 7/11/2016 4:05 PM, Loren Tedford wrote:

I can try to put together a forum if you think we need it I am willing to host it just to get the project started but I want to make it clear we hand everything back over to the opensource community from the beginning!

As far as storage not a problem here..

Loren Tedford (KC9ZHV) Phone: Fax: Email: lorentedford@gmail.com <mailto:lorentedford@gmail.com> <mailto:lorentedford@gmail.com <mailto:lorentedford@gmail.com>> Email: KC9ZHV@KC9ZHV.com <mailto:KC9ZHV@KC9ZHV.com <mailto:KC9ZHV@KC9ZHV.com>> http://www.lorentedford.com <http://www.lorentedford.com/> http://www.kc9zhv.com <http://www.kc9zhv.com/> http://forum.kc9zhv.com <http://forum.kc9zhv.com/> http://hub.kc9zhv.com <http://hub.kc9zhv.com/> http://Ltcraft.net<http://ltcraft.net/ <http://ltcraft.net/>>

On Mon, Jul 11, 2016 at 3:01 PM, Steve Wright <info@meshnetworks.co.nz <mailto:info@meshnetworks.co.nz> <mailto:info@meshnetworks.co.nz <mailto:info@meshnetworks.co.nz>>> wrote:

On 12/07/16 07:05, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com> <mailto:szingman@msgstor.com <mailto:szingman@msgstor.com>>> wrote:

There have been discussion as to how to move forward. The people involved are the people that will do the work. We can not be "left behind" and the tools needed are available. app_rpt is Open Source, Asterisk is Open Source. The concepts and methods used by app_rpt are readily apparent. They can be re-created. [....] On 7/11/2016 2:33 PM, Loren Tedford wrote:

Now where do we begin? I know absolutely nothing about coding however I do know if we don't do some thing fast we will be left behind and the tools others may have had available to port their stuff through may not be available for us..

Where do we join this group?

Set it up. _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org <mailto:App_rpt-users@ohnosec.org> <mailto:App_rpt-users@ohnosec.org <mailto:App_rpt-users@ohnosec.org>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users>

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.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@ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users>

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.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@ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users>

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.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@ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users>

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.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.

And remember folks....... *Standard disclaimer applies:* This product is meant for educational purposes only. Any resemblance to real persons, living or dead is purely coincidental. Void where prohibited. Some assembly required. List each check separately by bank number. Batteries not included. Contents may settle during shipment. Use only as directed. No other warranty expressed or implied. Do not use while operating a motor vehicle or heavy equipment. Postage will be paid by addressee. Subject to CAB approval. This is not an offer to sell securities. Apply only to affected area. May be too intense for some viewers. Do not stamp. Use other side for additional listings. For recreational use only. Do not disturb. All models over 18 years of age. If condition persists, consult your physician. No user-serviceable parts inside. Freshest if eaten before date on carton. Subject to change without notice. Times approximate. Simulated picture. No postage necessary if mailed in the United States. Breaking seal constitutes acceptance of agreement. For off-road use only. As seen on TV. One size fits all. Many suitcases look alike. Contains a substantial amount of non-tobacco ingredients. Colors may, in time, fade. We have sent the forms which seem right for you. Slippery when wet. For office use only. Not affiliated with the American Red Cross. Drop in any mailbox. Edited for television. Keep cool. Process promptly. Post office will not deliver without postage. List was current at time of printing. Return to sender, no forwarding order on file, unable to forward. Not responsible for direct, indirect, incidental or consequential damages resulting from any defect, error or failure to perform. At participating locations only. Not the Beatles. Penalty for private use. See label for sequence. Substantial penalty for early withdrawal. Do not write below this line. Falling rock. Lost ticket pays maximum rate. Your canceled check is your receipt. Add toner. Place stamp here. Avoid contact with skin. Sanitized for your protection. Be sure each item is properly endorsed. Sign here without admitting guilt. Slightly higher west of the Mississippi. Employees and their families are not eligible. Beware of dog. Contestants have been briefed on some questions before the show. Limited time offer, call now to ensure prompt delivery. You must be present to win. No passes accepted for this engagement. No purchase necessary. Processed at location stamped in code at top of carton. Shading within a garment may occur. Use only in a well-ventilated are. Keep away from fire or flames. Replace with same type. Approved for veterans. Booths for two or more. Check here if tax deductible. Some equipment shown is optional. Price does not include taxes. No Canadian coins. Not recommended for children. Prerecorded for this time zone. Reproduction strictly prohibited. No solicitors. No alcohol, dogs or horses. No anchovies unless otherwise specified. Restaurant package, not for resale. List at least two alternate dates. First pull up, then pull down. Call toll free before digging. Driver does not carry cash. Some of the trademarks mentioned in this product appear for identification purposes only. Record additional transactions on back of previous stub. UNIX is a registered trademark of AT&T. Do not fold, spindle or mutilate. No transfers issued until the bus comes to a complete stop. Package sold by weight, not volume. Your mileage may vary. This article does not reflect the thoughts or opinions of either myself, my company, my friends, or my cat. Don't quote me on that. Don't quote me on anything. All rights reserved. You may distribute this article freely but you may not make a profit from it. Terms are subject to change without notice. Illustrations are slightly enlarged to show detail. Any resemblance to actual persons, living or dead, is unintentional and purely coincidental. Do not remove this disclaimer under penalty of law. Hand wash only, tumble dry on low heat. Do not bend, fold, mutilate, or spindle. No substitutions allowed. For a limited time only. This article is void where prohibited, taxed, or otherwise restricted. Use of this article in a manner not in conformance with labeling may be a violation of Federal, State, or Local Laws, Statutes, or Regulations and may or may not subject the user to maximum enforcement under these laws, statutes, or regulations. *Caveat emptor. Article is provided "as is" without any warranties. Reader assumes full responsibility. An equal opportunity article. No shoes, no shirt, no service.* Quantities are limited while supplies last. If any defects are discovered, do not attempt to read them yourself, but return to an authorized service center. Read at your own risk. Parental advisory -- explicit lyrics -- text may contain explicit materials some readers may find objectionable, parental guidance is advised. Keep away from sunlight. Keep away from pets and small children. Limit one-per-family please. No money down. No purchase necessary. You need not be present to win. Some assembly required. Batteries not included. Instructions are included. Action figures sold separately. No preservatives added. Slippery when wet. Safety goggles may be required during use. Sealed for your protection, do not read if safety seal is broken. Not liable for damages arising from use or misuse. For external use only. If rash, irritation, redness, or swelling develops, discontinue reading. Read only with proper ventilation. Avoid extreme temperatures and store in a cool dry place. Keep away from open flames. Avoid contact with eyes and skin and avoid inhaling fumes. Do not puncture, incinerate, or store above 120 degrees Fahrenheit. Do not place near a flammable or magnetic source. Smoking this article could be hazardous to your health. The best safeguard, second only to abstinence, is the use of a condom. No salt, MSG, artificial color or flavoring added. If ingested, do not induce vomiting, and if symptoms persist, consult a physician. Articles are ribbed for your pleasure. Possible penalties for early withdrawal. Offer valid only at participating sites. Slightly higher west of the Rockies. Allow four to six weeks for delivery. Disclaimer does not cover misuse, accident, lightning, flood, tornado, tsunami, volcanic eruption, earthquake, hurricanes and other Acts of God, neglect, damage from improper reading, incorrect line voltage, improper or unauthorized reading, broken antenna or marred cabinet, missing or altered serial numbers, electromagnetic radiation from nuclear blasts, sonic boom vibrations, customer adjustments that are not covered in this list, and incidents owing to an airplane crash, ship sinking or taking on water, motor vehicle crashing, dropping the item, falling rocks, leaky roof, broken glass, mud slides, forest fire, or projectile (which can include, but not be limited to, arrows, bullets, shot, BB's, shrapnel, lasers, napalm, torpedoes, or emissions of X-rays, Alpha, Beta and Gamma rays, knives, stones, etc.). Please consult your physician if unforeseen side effects develop. Non-fatal if swallowed. Proven effective in laboratory experiments. Other restrictions may apply. *This supersedes all previous notices.* *No electrons were harmed in the making of this disclaimer.It has quite sadly become painfully necessary to "Officially" and publicly state that this release is *NOT* an "Official" Allstar release. It has not been sanctioned by me or the Allstar network. It is something that this person is doing completely independently.I am not in any way trying to infer that there is anything "right" or "wrong", or anything elseabout it, merely that is in an independent operation and I/we are not in any way responsiblefor its contents and/or use.* *Have a nice day.* *__________________*__________________________________________ ________________________ -- Thanks in Advance Bob, WØNQX Kansas City Metro Area http://drsm0ke.net http://byrg.net http://sm0kenet.net Quis custodiet ipsos custodes? -- On Fri, Sep 9, 2016 at 3:24 PM, Stacy <kg7qin@arrl.net> wrote:

Yes, he does. He helped me with some of the problems I was having with app_rpt and making calls. There are still some quirks there, but without Jim's advice on it, I would have had an even harder time.

-Stacy

On 9/9/2016 1:22 PM, Jim Duuuude wrote:

Just in case any one didn't know that already, I REALLY LOVE OPEN SOURCE!!

Jim, WB6NIL

------------------------------ *From:* app_rpt-users-bounces@ohnosec.org <app_rpt-users-bounces@ ohnosec.org> <app_rpt-users-bounces@ohnosec.org> on behalf of Stacy <kg7qin@arrl.net> <kg7qin@arrl.net> *Sent:* Friday, September 9, 2016 1:03 PM *To:* Loren Tedford *Cc:* app_rpt mailing list *Subject:* Re: [App_rpt-users] toy throwing time?

No security patches, if I remember correctly.

There are some tweaks to the IAX2 protocol in the 1.4 version of Asterisk, that needed to be done here for backwards compatibility. If I remember correctly, it deals with the call token for the denial of service problems IAX2 has without it.

This is very rough code, and while it does work, some parts are in need or work. I started on this last year, October, and got to where you see it in less than a month. Most of the pieces were already there with 1.8 (this is the last version that the app_rpt code appeared before Digium completely dropped it), but due to to a change in the base code, app_rpt did not work without a mod to (the base code).

There were other changes too that needed to be done to bring the version of app_rpt forward to a more recent revision than what sits in the repository. It required going through the entire app_rpt and modules which were ported and updating the calls to functions and variables used.

I've successfully used this with AllStar and connecting to node 2560 of the WIN system. Echolink has a problem with DTMF (see issues), but it is a start.

I'd love to have other contribute to this. It was done as an intermediate version to bridge the gap to a newer version of Asterisk.

-Stacy

KG7QIN

On 9/9/2016 12:36 PM, Loren Tedford wrote:

Wow This is cool!! I can't wait to play and see how it works!

Great job!! We needed development! Is their by chance any security patches of the whole iax2 issues does anyone know?

Loren Tedford (KC9ZHV) Phone: Fax: Email: lorentedford@gmail.com Email: KC9ZHV@KC9ZHV.com http://www.lorentedford.com http://www.kc9zhv.com http://forum.kc9zhv.com http://hub.kc9zhv.com http://Ltcraft.net <http://ltcraft.net/> http://voipham.com

On Fri, Sep 9, 2016 at 2:06 PM, Stacy <kg7qin@arrl.net> wrote:

...

Sorry to revive an old thread, but take a look at this: https://github.com/KG7QIN/AllStarLink-Asterisk-1.8

-Stacy

On 7/11/2016 2:33 PM, Scott Zimmerman wrote:

...

Loren et. all:

There is already a forum present that can be utilized as needed: AllStarNode.com

I quickly threw this together a few years ago. It was intended to be used exactly how you were describing. It never really took off, however.

You are more than welcome to join. If you do, drop me an e-mail and I'll make you a super admin, so you can change things as you see fit.

Scott

Scott Zimmerman Amateur Radio Call N3XCC 474 Barnett Road Boswell, PA 15531

On 7/11/2016 4:05 PM, Loren Tedford wrote:

...

I can try to put together a forum if you think we need it I am willing to host it just to get the project started but I want to make it clear we hand everything back over to the opensource community from the beginning!

As far as storage not a problem here..

Loren Tedford (KC9ZHV) Phone: Fax: Email: lorentedford@gmail.com <mailto:lorentedford@gmail.com> Email: KC9ZHV@KC9ZHV.com <mailto:KC9ZHV@KC9ZHV.com> http://www.lorentedford.com <http://www.lorentedford.com/> http://www.kc9zhv.com <http://www.kc9zhv.com/> http://forum.kc9zhv.com <http://forum.kc9zhv.com/> http://hub.kc9zhv.com <http://hub.kc9zhv.com/> http://Ltcraft.net<http://ltcraft.net/>

On Mon, Jul 11, 2016 at 3:01 PM, Steve Wright <info@meshnetworks.co.nz <mailto:info@meshnetworks.co.nz>> wrote:

On 12/07/16 07:05, Steve Zingman <szingman@msgstor.com <mailto: szingman@msgstor.com>> wrote:

There have been discussion as to how to move forward. The people involved are the people that will do the work. We can not be "left behind" and the tools needed are available. app_rpt is Open Source, Asterisk is Open Source. The concepts and methods used by app_rpt are readily apparent. They can be re-created. [....] On 7/11/2016 2:33 PM, Loren Tedford wrote:

Now where do we begin? I know absolutely nothing about coding however I do know if we don't do some thing fast we will be left behind and the tools others may have had available to port their stuff through may not be available for us..

Where do we join this group?

Set it up. _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mai lman/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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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.

Bob, You forgot all the additional restriction that the State of California puts on everything. :) Also, I had posted this to the list a while ago. I did not want the code to be left stagnant/lost, and some people seemed to be interested. The only thing with open source, is that it takes a lot of time and effort to move forward. Both Jim Dixon and Steve Rodgers put a lot of work into the parts that are used for the AllStar Network. (app_rpt is one example of the work done). I had an inkling for starting a port for a long time, and my initial attempts were not met with success (the DAHDI driver and a newer Linux kernel). At first, I didn't have a lot of time to put into this. It was only when I had started my transition/retirement from my previous job last October (20 years activey duty Navy, retired 1 Dec 15), that I had the free time to start on a project like this. I have since started a new job, so I do not have all the free time I one did to work on it. One of the reasons why put it in a Github repository and posted the announcement here several months ago, was because I feel there is a desire to move things forward. I saw this old thread today when cleaning up my inbox and decided to re-post the link to it. You are right, this isn't an official release-- yet. As with any major step forward, testing will be required. The only way to accomplish that is for the code to be picked up, used, poked at and fixed. This is a lot for one person to do, especially since there are parts I can't test right now. App_rpt will run, take/make calls and do its thing. Does it have bugs? Hell yes. But is it is start. And as Jim said before, he loves open source. That being said, the only person who can officially sanction this is Jim himself (see copyright in the headers of all the app_rpt and related module source code), and even he released it under the GPL. Unless this plain crashes any of the pieces of the AllStar network, nobody will likely know you are running it. I don't recommend trying to run it as a production node yet, but it still needs to be run in the environment it will be used in to test it out and shake the bugs out. -Stacy KG7QIN On 9/9/2016 2:29 PM, Bob Brown - WØNQX wrote:

And remember folks.......

*Standard disclaimer applies:*

This product is meant for educational purposes only. Any resemblance to real persons, living or dead is purely coincidental. Void where prohibited. Some assembly required. List each check separately by bank number. Batteries not included. Contents may settle during shipment. Use only as directed. No other warranty expressed or implied. Do not use while operating a motor vehicle or heavy equipment. Postage will be paid by addressee. Subject to CAB approval. This is not an offer to sell securities. Apply only to affected area. May be too intense for some viewers. Do not stamp. Use other side for additional listings. For recreational use only. Do not disturb. All models over 18 years of age. If condition persists, consult your physician. No user-serviceable parts inside. Freshest if eaten before date on carton. Subject to change without notice. Times approximate. Simulated picture. No postage necessary if mailed in the United States. Breaking seal constitutes acceptance of agreement. For off-road use only. As seen on TV. One size fits all. Many suitcases look alike. Contains a substantial amount of non-tobacco ingredients. Colors may, in time, fade. We have sent the forms which seem right for you. Slippery when wet. For office use only. Not affiliated with the American Red Cross. Drop in any mailbox. Edited for television. Keep cool. Process promptly. Post office will not deliver without postage. List was current at time of printing. Return to sender, no forwarding order on file, unable to forward. Not responsible for direct, indirect, incidental or consequential damages resulting from any defect, error or failure to perform. At participating locations only. Not the Beatles. Penalty for private use. See label for sequence. Substantial penalty for early withdrawal. Do not write below this line. Falling rock. Lost ticket pays maximum rate. Your canceled check is your receipt. Add toner. Place stamp here. Avoid contact with skin. Sanitized for your protection. Be sure each item is properly endorsed. Sign here without admitting guilt. Slightly higher west of the Mississippi. Employees and their families are not eligible. Beware of dog. Contestants have been briefed on some questions before the show. Limited time offer, call now to ensure prompt delivery. You must be present to win. No passes accepted for this engagement. No purchase necessary. Processed at location stamped in code at top of carton. Shading within a garment may occur. Use only in a well-ventilated are. Keep away from fire or flames. Replace with same type. Approved for veterans. Booths for two or more. Check here if tax deductible. Some equipment shown is optional. Price does not include taxes. No Canadian coins. Not recommended for children. Prerecorded for this time zone. Reproduction strictly prohibited. No solicitors. No alcohol, dogs or horses. No anchovies unless otherwise specified. Restaurant package, not for resale. List at least two alternate dates. First pull up, then pull down.

Call toll free before digging. Driver does not carry cash. Some of the trademarks mentioned in this product appear for identification purposes only. Record additional transactions on back of previous stub. UNIX is a registered trademark of AT&T. Do not fold, spindle or mutilate. No transfers issued until the bus comes to a complete stop. Package sold by weight, not volume. Your mileage may vary. This article does not reflect the thoughts or opinions of either myself, my company, my friends, or my cat. Don't quote me on that. Don't quote me on anything. All rights reserved. You may distribute this article freely but you may not make a profit from it. Terms are subject to change without notice. Illustrations are slightly enlarged to show detail. Any resemblance to actual persons, living or dead, is unintentional and purely coincidental. Do not remove this disclaimer under penalty of law. Hand wash only, tumble dry on low heat. Do not bend, fold, mutilate, or spindle. No substitutions allowed. For a limited time only. This article is void where prohibited, taxed, or otherwise restricted. Use of this article in a manner not in conformance with labeling may be a violation of Federal, State, or Local Laws, Statutes, or Regulations and may or may not subject the user to maximum enforcement under these laws, statutes, or regulations.

*Caveat emptor. Article is provided "as is" without any warranties. Reader assumes full responsibility. An equal opportunity article. No shoes, no shirt, no service.*

Quantities are limited while supplies last. If any defects are discovered, do not attempt to read them yourself, but return to an authorized service center. Read at your own risk. Parental advisory -- explicit lyrics -- text may contain explicit materials some readers may find objectionable, parental guidance is advised. Keep away from sunlight. Keep away from pets and small children. Limit one-per-family please. No money down. No purchase necessary. You need not be present to win. Some assembly required. Batteries not included. Instructions are included. Action figures sold separately. No preservatives added. Slippery when wet. Safety goggles may be required during use. Sealed for your protection, do not read if safety seal is broken. Not liable for damages arising from use or misuse. For external use only. If rash, irritation, redness, or swelling develops, discontinue reading. Read only with proper ventilation. Avoid extreme temperatures and store in a cool dry place. Keep away from open flames. Avoid contact with eyes and skin and avoid inhaling fumes. Do not puncture, incinerate, or store above 120 degrees Fahrenheit. Do not place near a flammable or magnetic source. Smoking this article could be hazardous to your health. The best safeguard, second only to abstinence, is the use of a condom. No salt, MSG, artificial color or flavoring added. If ingested, do not induce vomiting, and if symptoms persist, consult a physician. Articles are ribbed for your pleasure. Possible penalties for early withdrawal. Offer valid only at participating sites. Slightly higher west of the Rockies. Allow four to six weeks for delivery. Disclaimer does not cover misuse, accident, lightning, flood, tornado, tsunami, volcanic eruption, earthquake, hurricanes and other Acts of God, neglect, damage from improper reading, incorrect line voltage, improper or unauthorized reading, broken antenna or marred cabinet, missing or altered serial numbers, electromagnetic radiation from nuclear blasts, sonic boom vibrations, customer adjustments that are not covered in this list, and incidents owing to an airplane crash, ship sinking or taking on water, motor vehicle crashing, dropping the item, falling rocks, leaky roof, broken glass, mud slides, forest fire, or projectile (which can include, but not be limited to, arrows, bullets, shot, BB's, shrapnel, lasers, napalm, torpedoes, or emissions of X-rays, Alpha, Beta and Gamma rays, knives, stones, etc.). Please consult your physician if unforeseen side effects develop. Non-fatal if swallowed. Proven effective in laboratory experiments. Other restrictions may apply.

*This supersedes all previous notices.*

*No electrons were harmed in the making of this disclaimer.

It has quite sadly become painfully necessary to "Officially" and publicly state that this release is *NOT* an "Official" Allstar release. It has not been sanctioned by me or the Allstar network. It is something that this person is doing completely independently.

I am not in any way trying to infer that there is anything "right" or "wrong", or anything else about it, merely that is in an independent operation and I/we are not in any way responsible for its contents and/or use.*

*Have a nice day.*

*__________________*__________________________________________________________________

-- Thanks in Advance

Bob, WØNQX

Kansas City Metro Area

http://drsm0ke.net http://byrg.net

http://sm0kenet.net <http://sm0kenet.net/>

Quis custodiet ipsos custodes?

--

On Fri, Sep 9, 2016 at 3:24 PM, Stacy <kg7qin@arrl.net <mailto:kg7qin@arrl.net>> wrote:

Yes, he does. He helped me with some of the problems I was having with app_rpt and making calls. There are still some quirks there, but without Jim's advice on it, I would have had an even harder time.

-Stacy

On 9/9/2016 1:22 PM, Jim Duuuude wrote:

...

Just in case any one didn't know that already, I REALLY LOVE OPEN SOURCE!!

Jim, WB6NIL

------------------------------------------------------------------------ *From:* app_rpt-users-bounces@ohnosec.org <mailto:app_rpt-users-bounces@ohnosec.org> <app_rpt-users-bounces@ohnosec.org> <mailto:app_rpt-users-bounces@ohnosec.org> on behalf of Stacy <kg7qin@arrl.net> <mailto:kg7qin@arrl.net> *Sent:* Friday, September 9, 2016 1:03 PM *To:* Loren Tedford *Cc:* app_rpt mailing list *Subject:* Re: [App_rpt-users] toy throwing time?

No security patches, if I remember correctly.

There are some tweaks to the IAX2 protocol in the 1.4 version of Asterisk, that needed to be done here for backwards compatibility. If I remember correctly, it deals with the call token for the denial of service problems IAX2 has without it.

This is very rough code, and while it does work, some parts are in need or work. I started on this last year, October, and got to where you see it in less than a month. Most of the pieces were already there with 1.8 (this is the last version that the app_rpt code appeared before Digium completely dropped it), but due to to a change in the base code, app_rpt did not work without a mod to (the base code).

There were other changes too that needed to be done to bring the version of app_rpt forward to a more recent revision than what sits in the repository. It required going through the entire app_rpt and modules which were ported and updating the calls to functions and variables used.

I've successfully used this with AllStar and connecting to node 2560 of the WIN system. Echolink has a problem with DTMF (see issues), but it is a start.

I'd love to have other contribute to this. It was done as an intermediate version to bridge the gap to a newer version of Asterisk.

-Stacy

KG7QIN

On 9/9/2016 12:36 PM, Loren Tedford wrote:

...

Wow This is cool!! I can't wait to play and see how it works!

Great job!! We needed development! Is their by chance any security patches of the whole iax2 issues does anyone know?

Loren Tedford (KC9ZHV) Phone: Fax: Email: lorentedford@gmail.com <mailto:lorentedford@gmail.com> Email: KC9ZHV@KC9ZHV.com <mailto:KC9ZHV@KC9ZHV.com> http://www.lorentedford.com <http://www.lorentedford.com/> http://www.kc9zhv.com <http://www.kc9zhv.com/> http://forum.kc9zhv.com <http://forum.kc9zhv.com/> http://hub.kc9zhv.com <http://hub.kc9zhv.com/> http://Ltcraft.net<http://ltcraft.net/> http://voipham.com

On Fri, Sep 9, 2016 at 2:06 PM, Stacy <kg7qin@arrl.net <mailto:kg7qin@arrl.net>> wrote:

Sorry to revive an old thread, but take a look at this: https://github.com/KG7QIN/AllStarLink-Asterisk-1.8 <https://github.com/KG7QIN/AllStarLink-Asterisk-1.8>

-Stacy

On 7/11/2016 2:33 PM, Scott Zimmerman wrote:

Loren et. all:

There is already a forum present that can be utilized as needed: AllStarNode.com

I quickly threw this together a few years ago. It was intended to be used exactly how you were describing. It never really took off, however.

You are more than welcome to join. If you do, drop me an e-mail and I'll make you a super admin, so you can change things as you see fit.

Scott

Scott Zimmerman Amateur Radio Call N3XCC 474 Barnett Road Boswell, PA 15531

On 7/11/2016 4:05 PM, Loren Tedford wrote:

I can try to put together a forum if you think we need it I am willing to host it just to get the project started but I want to make it clear we hand everything back over to the opensource community from the beginning!

As far as storage not a problem here..

Loren Tedford (KC9ZHV) Phone: Fax: Email: lorentedford@gmail.com <mailto:lorentedford@gmail.com> <mailto:lorentedford@gmail.com <mailto:lorentedford@gmail.com>> Email: KC9ZHV@KC9ZHV.com <mailto:KC9ZHV@KC9ZHV.com> <mailto:KC9ZHV@KC9ZHV.com <mailto:KC9ZHV@KC9ZHV.com>> http://www.lorentedford.com <http://www.lorentedford.com/> http://www.kc9zhv.com <http://www.kc9zhv.com/> http://forum.kc9zhv.com <http://forum.kc9zhv.com/> http://hub.kc9zhv.com <http://hub.kc9zhv.com/> http://Ltcraft.net<http://ltcraft.net/ <http://ltcraft.net/>>

On Mon, Jul 11, 2016 at 3:01 PM, Steve Wright <info@meshnetworks.co.nz <mailto:info@meshnetworks.co.nz> <mailto:info@meshnetworks.co.nz <mailto:info@meshnetworks.co.nz>>> wrote:

On 12/07/16 07:05, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com> <mailto:szingman@msgstor.com <mailto:szingman@msgstor.com>>> wrote:

There have been discussion as to how to move forward. The people involved are the people that will do the work. We can not be "left behind" and the tools needed are available. app_rpt is Open Source, Asterisk is Open Source. The concepts and methods used by app_rpt are readily apparent. They can be re-created. [....] On 7/11/2016 2:33 PM, Loren Tedford wrote:

Now where do we begin? I know absolutely nothing about coding however I do know if we don't do some thing fast we will be left behind and the tools others may have had available to port their stuff through may not be available for us..

Where do we join this group?

Set it up. _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org <mailto:App_rpt-users@ohnosec.org> <mailto:App_rpt-users@ohnosec.org <mailto:App_rpt-users@ohnosec.org>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users>

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.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@ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users>

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.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@ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users>

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.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@ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users>

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.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@ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users>

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.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.

I generally will stay out of things of this nature, but I'm not so sure why there is a push to move app_rpt to a later version of Asterisk? I see the version of Asterisk that's running app_rpt as purpose built to do what it does, act as a repeater controller and linking system and a few other things. There are some general specific applications in the app_rpt version of Asterisk that I could care less about using, so if it's older code and doesn't have as many features I'm not really missing anything. My production PBX is the place to use those features instead. I can't fault folks for wanting to progress technology, that is afterall what this should be all about, but I guess I don't see the appeal of jumping to a newer version of Asterisk and making app_rpt work with it just because it's newer code. What exactly does it gain for us? Is it the spark and the challenge of doing it is what's driving this? (which I completely understand mind you). 73 and that's my .02 (about all it's worth anyhow!) Stephen K1LNX On Mon, Sep 12, 2016 at 9:49 AM, Steve Zingman <szingman@msgstor.com> wrote:

I thought I recognized this. It's a quote from Duuuude in June 2014

On 9/9/2016 5:29 PM, Bob Brown - WØNQX wrote:

*It has quite sadly become painfully necessary to "Officially" and publicly state that this release is *NOT* an "Official" Allstar release. It has not been sanctioned by me or the Allstar network. It is something that this person is doing completely independently. I am not in any way trying to infer that there is anything "right" or "wrong", or anything else about it, merely that is in an independent operation and I/we are not in any way responsible for its contents and/or use.*

-- "Just say no to world domination"

_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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.

I realize keepng up with the Asterisk code base is a lot to ask, but for one thing it buys you is security. While it is certainly true that "improvements" do introduce new security holes, a more mature and current Asterisk is more likely to have fewer security holes.

Since many nodes face the public internet, it would certainly be catastrophic if a black hat were to have the ability to knock any public facing AllStar node in the world off the air by exploiting a previously undisclosed vulnerability. Combining such an exploit with a router exploit to get to private networks of nodes is a real possibility, and there are LOTS of people around the world, including some big players, that invest heavily in having such a toolset ready for when it would benefit them.

Having what is essentially a static code base makes it easier for those folks. I know that sounds rather paranoid, but just sayin....

I don't refute that. Security is a real threat and something that everyone should keep fingers on, but I really have to ask myself, if I was so concerned about something being attacked why is it on the internet in the first place? If my box were to get owned, I most likely would discover it in a timely manner and take corrective action anyhow, which would probably involve me laughing at it, wiping the drive, and restoring my configs from backup. This is pure hobby to me, not a mission critical production system. It's no excuse to have any insecure software or protocols running on any platform whatsoever, but I know of no single product in existence that has ever been made 100% bullet proof and secure out of the box, so that leads me to wonder what the real threat vector is here besides the "what if" factor. Believe me, as a security conscious guy who locks down his own servers and gear, I totally get it, but I view app_rpt in a different light because it's only existence in life for me is to control a repeater and provide network connectivity to other nodes. All in all, I like things where they are now, and if progress can be made on a newer platform, great, but otherwise the work others have done to this point on it has been phenomenal and I am in 100% support and appreciative of it. 73 Stephen K1LNX On Mon, Sep 12, 2016 at 1:04 PM, Willem Schreuder <willem@prinmath.com> wrote:

On Mon, 12 Sep 2016, Stephen - K1LNX wrote:

What exactly does it gain for us?

...

I realize keepng up with the Asterisk code base is a lot to ask, but for one thing it buys you is security. While it is certainly true that "improvements" do introduce new security holes, a more mature and current Asterisk is more likely to have fewer security holes.

Since many nodes face the public internet, it would certainly be catastrophic if a black hat were to have the ability to knock any public facing AllStar node in the world off the air by exploiting a previously undisclosed vulnerability. Combining such an exploit with a router exploit to get to private networks of nodes is a real possibility, and there are LOTS of people around the world, including some big players, that invest heavily in having such a toolset ready for when it would benefit them.

Having what is essentially a static code base makes it easier for those folks. I know that sounds rather paranoid, but just sayin....

73 -Willem AC0KQ

On Mon, 12 Sep 2016, Stephen - K1LNX wrote:

All in all, I like things where they are now, and if progress can be made on a newer platform, great, but otherwise the work others have done to this point on it has been phenomenal and I am in 100% support and appreciative of it.

I absolutely concur. I am simply arguing that there ARE some tangible benefits to migrating to a newer Asterisk at such time as it should bubble high enough on the list of priorities. It is not unlike the ACID to DIAL migration that happend because it became advantageous, but only then. 73 -Willem

That is true, 1.8 does support IPv6. Some places are already starting to offer you only an IPv6 address with a connection. Mostly mobile hot spots. If we don't want Allstar to become something of the past, we should move up to at least 1.8 so that it supports IPv6. This code really needs someone else's eyes to go over it, it works but I know there are things that need to be fixed. -Stacy KG7QIN On 09/12/2016 03:05 PM, Bryan Fields wrote:

On 9/12/16 5:51 PM, Willem Schreuder wrote:

...

I am simply arguing that there ARE some tangible benefits to migrating to a newer Asterisk Two big things, IPv6 and Multicast are supported in the new version of asterisk.

I'm speaking on IPv6 in ham networks at DCC Saturday (and I've not done my slides yet!). My DCC Paper is up here on IPv6

http://wiki.w9cr.net/images/3/3c/IPv6_in_Amateur_Radio.docx

Hi Everyone, Every time these discussions about upgrading software come up, I re-evaluate the possible gains of a major upgrade. I'll remind everyone of a major hurdle which can't be side-stepped: The AllStar project would continue to be a FORK of Asterisk---not code that becomes part of the Digium distro, like it once was. You ask why?? Well, that's due to Digium's draconian contributor license, which doesn't guarantee the code will remain open source and all developer's must surrender their code ownership to Digium, to do with as they please. So, I guess my question becomes: WHY? ...what glaring issues will a major upgrade resolve? What issues need to be fixed? What -TRULY- known problems are present? Why not just FIX those problems, including back-porting code, if Asterisk needs a patch. As the overall Asterisk project has marched forward, gazillions of features have been added...And gazillions of NEW bugs. Are those features needed for AllStar? For the most part, I would argue probably not. AllStar's primary duty isn't as a phone PBX... One aspect many AllStar users are probably unaware of is that there were major command syntax changes as of Asterisk 1.6.x...One thing this means to the user is that the dialplan syntax in the 1.4.x extensions.conf file isn't compatible with syntax in 1.6.x and later...So, now both styles of dialplans must be supported, the old 1.4.x variety and the new 1.6.x style. Yet more confusion. As for IPV6, yes, native IPV6 compatibility would be nice, but simply NAT mapping IPV6 address space to IPV4 addresses will and does work too. But, this is only part of the problem, it doesn't fix other major issues: All the AllStar registration and node database software must be upgraded to IPV6 as well! THEN, suddenly, none of the IPV6 users can talk to IPV4 users---and, yes, there will be IPV4 address space in use by ISP's for years to come. The IPV4 vs. IPV6 migration problem gets more and more complex to fix, the deeper you dig. ....As another long term solution, the IPV6 code could be back-ported to the 1.4.x chan_iax2, chan_sip. Wouldn't this be easier than a full upgrade?? Anyhow, as a recap, what is broken that needs to be fixed???? IMO, fixing core issues in the CURRENT codebase is much better use of developer's time, since developers are so few and far between. Just my $0.02 73, David KB4FXC On Tue, 13 Sep 2016, Stacy wrote:

That is true, 1.8 does support IPv6. Some places are already starting to offer you only an IPv6 address with a connection. Mostly mobile hot spots.

If we don't want Allstar to become something of the past, we should move up to at least 1.8 so that it supports IPv6.

This code really needs someone else's eyes to go over it, it works but I know there are things that need to be fixed.

-Stacy

KG7QIN

Wow, Ok. There are some good points here, but what we seem to be hitting is one of the major criticisms of ham radio -- any new ideas are met with stiff resistance. Which usually means another fork in the road and the community is further divided. Which is quite funny, since ham radio operators are normally credited with making the advances that everyone else adopts later. Nobody is forcing you to pay attention to this, I'm just some hobbyist who had an idea and is trying to give back to the community. Note that I did most of the work on this back in October, almost a year ago, and afterwards it has sat. I posted about this before, and am doing so again since I see there is some interest. 1.8 does need some minor tweaks to the extensions.conf file generated by the portal to get running. I will try to include the extensions.conf file from my test node, 42088, in the repository for an example. There were just some minor tweaks that were needed to get the portal generated file accepted. As for running NAT, why? One of the points of moving to IPv6 is to get away from using NAT. For building the system, I just put on the repository for this port some simple instructions on the wiki that are needed if you try to run ./configure and make. This assumes that you have all the prerequisites for building asterisk in the first place. You will also need to compile and install the patched version of DAHDI as well before compiling and running asterisk. In addition to the features that were added to 1.8, there are some pretty significant changes to the code base itself. Trying to port the stuff for supporting IPv6 into 1.4 would be more trouble than it is worth. Richard, Welcome to the community. Don't be discouraged by what you are seeing. I invite you to take a look at the code for 1.8.32.3 that I have up on the github repository, poke around in it, and make contributions back. I would love to see this become stable enough for a production environment so that we could then ask for it to be blessed. Just my $.04 cents. :) -Stacy KG7QIN On 09/13/2016 09:39 PM, Richard Bateman wrote:

Hi all,

I'm going to toss my $0.02 in as well and see if it gets me kicked out onto my backside =]

I am a developer with a lot of experience with open source software projects, as well as being a ham radio operator and one of the newest members of this group. I'm very interested in the possibilities that are presented here, but having come from an open source background I have to say that my #1 frustration is that there seems to be no effort to set things up so that people can easily get involved with the code.

Personally I'd be very interested in contributing code; I'd like to think that I could fix some things that are bothering me and maybe that'd help others as well. Naturally the first thing I did was start looking for the codebase and figuring out how to build it.

I still haven't figured out for sure how to build the distribution; that seems to happen under a dark rock somewhere. There are no DIY instructions that I can find. I recently discovered that there is at least one semi-major (ARM-specific) fork of the project which is even worse in this way than this project is and the documentation for both is scattered across the internet and intermixed; I had no idea that half of the documentation I was reading from the hamvoip.org <http://hamvoip.org> group may or may not be relevant to what I'm doing because there isn't really an easy to find single source of any kind of truth or attempt by either group to clarify things.

I realize that I'm a total newcomer walking in and saying "hey you should do this differently", and I absolutely am grateful to everything that has been done, but... subversion? on a closed server? And your documentation site is split from an old drupal site and a new site that I can't find half the time? This feels like it's designed to keep out new developers rather than bring them in.

That is of course an overly harsh characterization, but there are *lots* of open source projects out there these days and since this project was created much better collaboration tools have been created.

Here is what I'd really love to see:

(note that this advice is provided free of charge and guaranteed to be worth what you paid)

1. Move the main code repository to github. If you have devs who don't want to learn how to use git, a) I'm happy to get on the phone with them and walk them through whatever is annoying them and b) github actually supports checking out the master branch via subversion, so you can still use it if you really really want to.

2. Use github wiki for documentation; this way users can submit pull requests to provide documentation on using the code, tips and tricks, etc.

3. Use the github issue system -- I realize that's going to be a pain sometimes, but at least it would provide a place where issues can be filed, answered, and *searched* -- that last is the most important since it means future people with the same issue can find the result.

I can only imagine that the core developers of the project are getting tired of carrying it on their backs for all this time; whether we upgrade to 1.8 or stay with 1.4 or jump straight to 1.13 can we *please* get this set up somewhere that it's easy to get into and contribute? I can't imagine that I'm the only newcomer feeling this frustation -- I'm probably just one of the few who are annoying enough to write you an email about it.

Thank you to all who work on this. I am absolutely ready and willing to help with migration if any of these suggestions (or alternatives to them) are to be implemented.

Respectfully, Richard Bateman a.k.a. taxilian KD7BBC HamStudy.org <http://hamstudy.org>

...

On Sep 13, 2016, at 10:21 PM, David McGough <kb4fxc@inttek.net <mailto:kb4fxc@inttek.net>> wrote:

Hi Everyone,

Every time these discussions about upgrading software come up, I re-evaluate the possible gains of a major upgrade.

I'll remind everyone of a major hurdle which can't be side-stepped: The AllStar project would continue to be a FORK of Asterisk---not code that becomes part of the Digium distro, like it once was. You ask why?? Well, that's due to Digium's draconian contributor license, which doesn't guarantee the code will remain open source and all developer's must surrender their code ownership to Digium, to do with as they please.

So, I guess my question becomes: WHY? ...what glaring issues will a major upgrade resolve? What issues need to be fixed? What -TRULY- known problems are present? Why not just FIX those problems, including back-porting code, if Asterisk needs a patch.

As the overall Asterisk project has marched forward, gazillions of features have been added...And gazillions of NEW bugs. Are those features needed for AllStar? For the most part, I would argue probably not. AllStar's primary duty isn't as a phone PBX...

One aspect many AllStar users are probably unaware of is that there were major command syntax changes as of Asterisk 1.6.x...One thing this means to the user is that the dialplan syntax in the 1.4.x extensions.conf file isn't compatible with syntax in 1.6.x and later...So, now both styles of dialplans must be supported, the old 1.4.x variety and the new 1.6.x style. Yet more confusion.

As for IPV6, yes, native IPV6 compatibility would be nice, but simply NAT mapping IPV6 address space to IPV4 addresses will and does work too. But, this is only part of the problem, it doesn't fix other major issues: All the AllStar registration and node database software must be upgraded to IPV6 as well! THEN, suddenly, none of the IPV6 users can talk to IPV4 users---and, yes, there will be IPV4 address space in use by ISP's for years to come. The IPV4 vs. IPV6 migration problem gets more and more complex to fix, the deeper you dig.

....As another long term solution, the IPV6 code could be back-ported to the 1.4.x chan_iax2, chan_sip. Wouldn't this be easier than a full upgrade??

Anyhow, as a recap, what is broken that needs to be fixed???? IMO, fixing core issues in the CURRENT codebase is much better use of developer's time, since developers are so few and far between.

Just my $0.02

73, David KB4FXC

On Tue, 13 Sep 2016, Stacy wrote:

...

That is true, 1.8 does support IPv6. Some places are already starting to offer you only an IPv6 address with a connection. Mostly mobile hot spots.

If we don't want Allstar to become something of the past, we should move up to at least 1.8 so that it supports IPv6.

This code really needs someone else's eyes to go over it, it works but I know there are things that need to be fixed.

-Stacy

KG7QIN

_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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.

On 9/14/16 3:02 AM, Toussaint OTTAVI wrote:

A NAT rule takes 10 seconds to set up for any network administrator, and it just works.

What if your service provider doesn't give you an IPv4 address? Many service providers only give IPv6 addresses now and use DS-Lite or even nat64. In most cases you do not have the ability to map ports on IPv4. NAT is evil.

Moreover, for those who definitely do not like NAT, there are plenty of 44.x.y.z AMPR IPv4 adresses available to the HAM community.

Most hams cannot announce a subnet via BGP to their service provider. The IP-IP tunnel gateway all flows via one point in San Diego. It's useless for VoIP.

I'm working in IT services for small businesses. I do not use IPv6 at all.

You're doing a disservice for your customers if you do not enable v6 for them. IPv4 run out has made v4 expensive.

I absolutely do not need it, and most of our ISPs here do not provide IPv6 connectivity.

Your provider is deficient. Many are, and the only way to get it fixed is by demanding proper IPv6 deployment.

Moreover, setting up an IPv6 network, and a dual-stack IPv4/IPv6 network, creates far more problems than it solves. For example, I spent dozens of hours last month to track a bug in my firewall's provider firmware, where IPv6 rules conflicted with IPv4 ones.

IMHO, IPv6 is absolutely not a feature I would request and/or enjoy, at least for the next 10 years !

It's this Luddite attitude that has got us into the place we're at now in IPv6.

50% of traffic on mobile networks to the major content providers is now via v6.

We cannot afford to be left behind once again. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

On Wed, Sep 14, 2016 at 2:02 AM, Toussaint OTTAVI <t.ottavi@bc-109.com> wrote:

Le 14/09/2016 à 07:22, Stacy a écrit :

...

As for running NAT, why? One of the points of moving to IPv6 is to get away from using NAT.

A NAT rule takes 10 seconds to set up for any network administrator, and it just works. Moreover, for those who definitely do not like NAT, there are plenty of 44.x.y.z AMPR IPv4 adresses available to the HAM community.

A NAT rule on IPv4 takes a few seconds, but one on IPv6 takes hardware/software that supports it. What was mentioned initially about NAT was NAT64 which requires a NAT gateway to be setup, and is not usually a simple matter of port forwarding.

Le 14/09/2016 à 06:39, Richard Bateman a écrit :

I can only imagine that the core developers of the project are getting tired of carrying it on their backs for all this time; whether we upgrade to 1.8 or stay with 1.4 or jump straight to 1.13 can we *please* get this set up somewhere that it's easy to get into and contribute? I can't imagine that I'm the only newcomer feeling this frustation -- I'm probably just one of the few who are annoying enough to write you an email about it.

You are not ;-) 73 de TK1BI

Security patches for IAX2??? What IAX2 security issue are you referring to (Call Tokens?) ?? Just wondering. 73, David KB4FXC On Fri, 9 Sep 2016, Loren Tedford wrote:

Wow This is cool!! I can't wait to play and see how it works!

Great job!! We needed development! Is their by chance any security patches of the whole iax2 issues does anyone know?

Loren Tedford (KC9ZHV) Phone: Fax: Email: lorentedford@gmail.com Email: KC9ZHV@KC9ZHV.com http://www.lorentedford.com http://www.kc9zhv.com http://forum.kc9zhv.com http://hub.kc9zhv.com http://Ltcraft.net <http://ltcraft.net/> http://voipham.com

On Fri, Sep 9, 2016 at 2:06 PM, Stacy <kg7qin@arrl.net> wrote:

...

Sorry to revive an old thread, but take a look at this: https://github.com/KG7QIN/AllStarLink-Asterisk-1.8

-Stacy

On 7/11/2016 2:33 PM, Scott Zimmerman wrote:

...

Loren et. all:

There is already a forum present that can be utilized as needed: AllStarNode.com

I quickly threw this together a few years ago. It was intended to be used exactly how you were describing. It never really took off, however.

You are more than welcome to join. If you do, drop me an e-mail and I'll make you a super admin, so you can change things as you see fit.

Scott

Scott Zimmerman Amateur Radio Call N3XCC 474 Barnett Road Boswell, PA 15531

On 7/11/2016 4:05 PM, Loren Tedford wrote:

...

I can try to put together a forum if you think we need it I am willing to host it just to get the project started but I want to make it clear we hand everything back over to the opensource community from the beginning!

As far as storage not a problem here..

Loren Tedford (KC9ZHV) Phone: Fax: Email: lorentedford@gmail.com <mailto:lorentedford@gmail.com> Email: KC9ZHV@KC9ZHV.com <mailto:KC9ZHV@KC9ZHV.com> http://www.lorentedford.com <http://www.lorentedford.com/> http://www.kc9zhv.com <http://www.kc9zhv.com/> http://forum.kc9zhv.com <http://forum.kc9zhv.com/> http://hub.kc9zhv.com <http://hub.kc9zhv.com/> http://Ltcraft.net<http://ltcraft.net/>

On Mon, Jul 11, 2016 at 3:01 PM, Steve Wright <info@meshnetworks.co.nz <mailto:info@meshnetworks.co.nz>> wrote:

On 12/07/16 07:05, Steve Zingman <szingman@msgstor.com <mailto: szingman@msgstor.com>> wrote:

There have been discussion as to how to move forward. The people involved are the people that will do the work. We can not be "left behind" and the tools needed are available. app_rpt is Open Source, Asterisk is Open Source. The concepts and methods used by app_rpt are readily apparent. They can be re-created. [....] On 7/11/2016 2:33 PM, Loren Tedford wrote:

Now where do we begin? I know absolutely nothing about coding however I do know if we don't do some thing fast we will be left behind and the tools others may have had available to port their stuff through may not be available for us..

Where do we join this group?

Set it up. _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mai lman/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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mai lman/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.