I am excited to announce the Asterisk has a new (and majorly improved) Asterisk GUI (2.0)

You can find this GUI in svn here:

branches/2.0


The GUI formerly known 'trunk' is now at:

branches/1.0


Installations Instructions can be found at:

http://asterisknow.org/install-related


Along with information on how to get involved:

http://asterisknow.org/gui-news


And last but not least screenshots of the new GUI: (I uploaded a _lot_ from Pari heh)

Thanks for looking!

-bk

It's going to take a while to fill it all in because I'm doing it in free time of my job, but I'm putting up results as I get runs done. You can see the results at http://www.simplified.org/trac/wiki/InterruptCoalescenceTesting as I complete them.

Over the weekend the /var/log partition on the test run server filled up. As a consequence both the routing engine and Asterisk slowed way down. However, neither died, and upon clearing up space, both resumed normal operations. We're now past the 12 million call mark. After 20 million calls I'll switch to the new data set that should allow us to sustain 300-350 calls per second and I'll report again after the 100 million call test job completes.

I've started running some stress tests of both SIP signaling and RTP handling in Asterisk 1.4 and Trunk. In our telecomm routing project we needed a SIP front end to our route selection server and the choice became Asterisk. However, we need to be able to push at least 400-500 calls/second through Asterisk to any given Griffin server. To do this is going to require some work on the Asterisk side of things (as well as a herculean effort on our Griffin development team).

I've been working on a concept over the past several months, which I call "adaptive capabilities". Some of you are already familiar with the original module that started this work, called cdr_adaptive_odbc. The idea behind this is rather simple, but the result is very powerful: instead of relying on database tables to be static representations of what Asterisk designers originally intended, make Asterisk adapt to the layout of a database table.

Read more about distributed presence in this post.

Read more about multiple parking lots in this post.