As you're probably all aware, this site is having problems. Is anybody interested in hosting it? I have a box here I can use if no offers come up but my pipe is not terribly fast. Right now it's running on a virtual server hosted with powervps. The mysql server is running out of resources. It's running on their LINUX WEBMIN POWER-0 $24.95 per month package. The next one would probably be fine but that will cost an extra $20.00 per month. If somebody wants to help out a bit, I should be able to just upgrade the plan. Any takers?

I have a piece of software I found that may help many of you. It's called RegexBuddy and is found at http://www.regexbuddy.com/. It's great for designing the regular expressions to be used in the astpp routes, etc.

Here's a big thank you to those of the community that stepped forward to offer their assistance! We now have 2 more programmers added and you can look to see some really neat stuff in the next release. There's still work for you if you're interested. We need more/better documentation yet as well as a release engineer.

Thanks Again!!!

Hello Everyone!!

I just added HTML::Template support to astpp-admin.cgi. This will be coming to the other scripts and is actually easy to add. This will make it trivial for you to customize the look of your astpp installation. Visit http://html-template.sourceforge.net/ for more information.

The bugtracker will be down tonight for an upgrade. It should be up by Saturday morning.

Well, the svn server move finally happened. Visit the "Downloads" page for details. Everything is the same expect it's now at www.astpp.org instead of aleph.aleph-com.net. Also, as you can see on the right had side of the page, there's an rss feed setup for commits.

I'm currently looking for somebody or even a few people to assist with ASTPP.  Here are the areas that I think need help the worst.

• Release Engineer
  • We need somebody to help coordinate the release activities and write up announcements, etc.
• Documentation
  • While I have put quite a bit of effort into documenting version 1.4, the documentation could always use help.
• User Interface Beautification
  • The user interface (astpp-admin,astpp-users,etc) could certainly use some help.  The person responsible for this would not need to know perl but an understanding of html and an eye for color coordinating, etc. would go a long ways.
• PHP Programmer
  • I have a few ideas that could use a php programmers help:
    • 1.  We currently have a php interface but it is outdated and does not work.  I appreciate if somebody who knows php would have a look at it and tell me what they think.  The original author does not seem to be available any long.
    • 2. Currently, we have a link to/from OSCommerce.  I was thinking about adding at least some of the functionality from astpp-users into an OSCommerce module.  Here there might be some funding available.
• C Programmer
  • I hired a C programmer to write the astpp-authorize.agi and astpp-lcr scripts into asterisk C modules a year or so ago.  As I am not a C coder and this fellow has disappeared, these modules are outdated.   I don't think it would be a vast amount of work to get them working again but any interested party is welcome to look at them.

If you're interested in any of these positions please feel free to email me at darren@aleph-com.net or post comments here.

Just a quick update for everybody.  Version 1.4 release is just around the bend.  I'm getting the last upgrading issues resolved and then the actual release will come out.

I've come up with a technique that will allow the administrator to work with the number that the customer dials.  For example, if you enter the regex pattern "^011" then any number dialed that begins with a 011 will have the 011 stripped off.  Also you will be able to have multiple regex patterns within the field.  This means that you can have something like this "011/" would remove the 011 but "^.......$/1780/0" would add 1780 onto any 7 digit number dialed.  This is somewhat complicated but allows for an incredible amount of flexibility.&nbsp