Changes

ASL-AsteriskNG is the next generation app_rpt client based on the KG7QIN's port to Asterisk 1.8.

ASL-AsteriskNG is the next generation app_rpt client based on the KG7QIN's port to Asterisk 1.8.

== Current Status ==

== Current Status ==

WIP.  app_rpt does run.  This is the code that powers the PTTLink phone portal and powered (powers?) the AllStarLink phone portal.  Refer to the issues section in the repo and the README for more information.

WIP.  app_rpt does run.  This is the code that powers the PTTLink phone portal and powered (powers?) the AllStarLink phone portal.  Refer to the issues section in the repo and the README for more information.

== Downloads ==

== Downloads ==

===Github===

===Github===

You can download the source on GitHub at https://www.github.com/pttlink/ASL-AsteriskNG

You can download the source on GitHub at https://www.github.com/pttlink/ASL-AsteriskNG

===Using setup.sh script===

===Using setup.sh script===

To automatically build and install the port and all associated files:

To automatically build and install the port and all associated files:

<pre>

<pre>

With advice of and some help from Jim, I was able to successfully get app_rpt working within Asterisk 1.8 with some notable issues including: channel drivers were still in a bad state and were prone to crashing or didn't work at all.

With advice of and some help from Jim, I was able to successfully get app_rpt working within Asterisk 1.8 with some notable issues including: channel drivers were still in a bad state and were prone to crashing or didn't work at all.

The code then sat for a few months on my laptop's hard drive as other things became a priority.  Since I didn't want to see the work I'd done go to waste, I opened up a GitHub Repo and made an announcement to the app_rpt-users mailing list about the code's availability.  You can see this announcement here: http://lists.keekles.org/pipermail/app_rpt-users/2016-April/014958.html.

The code then sat for a few months on my laptop's hard drive as other things became a priority.  Since I didn't want to see the work I'd done go to waste, I opened up a GitHub Repo and made an announcement to the app_rpt-users mailing list about the port and availability of the source code.  You can see this announcement here: http://lists.keekles.org/pipermail/app_rpt-users/2016-April/014958.html.

Since then I've done some updates to the app_rpt code and associated modules, mainly porting the changes between the version of app_rpt that I based the port off of and what the current version is/was.  This code does work but it is very much alpha quality.  I also added some extra tidbits to the code to aid with debugging that will need to be removed at some point.  These are in the form of some additional C macros for printing debug information that were/are used to determine flow control as the code was being ported.

Since then I've done some updates to the app_rpt code and associated modules, mainly porting the changes between the version of app_rpt that I based the port off of and what the current version is/was.  This code does work but it is very much alpha quality.  I also added some extra tidbits to the code to aid with debugging that will need to be removed at some point.  These are in the form of some additional C macros for printing debug information that were/are used to determine flow control as the code was being ported.

I am excited that this version of app_rpt is continuing to mature and become a viable client for use by the amateur radio community.

I am excited that this version of app_rpt is continuing to mature and become a viable client for use by the amateur radio community.