What things from the ABE C tree are relevant, Lumenvox upgrade to 7.5 software obviously isn’t, to the underlying AA50 (not GUI specific) software:

– Added ‘C’ option to the MeetMe application to allow a caller to continue in the dialplan when kicked out of the MeetMe.
– Added Taiwan language support to voicemail
– Added ‘trunkmaxsize’ and ’srvlookup’ configuration options for chan_iax2.
– Added two new dialplan functions, DUNDIQUERY and DUNDIRESULT. These functions will allow you to initiate a DUNDi query from the dialplan, find out how many results there are, and access each one.
– Added ENUMQUERY() and ENUMRESULT() dialplan functions to initiate an ENUM lookup from the dialplan and access cached results without doing multiple DNS queries.
– Added the ability to pass arguments to the Dial application when using the DUNDi switch in the dialplan.
– Added DUNDi functionality to set weights for dynamic responses using a global variable or a dialplan function. The SHELL() function would enable external scripts to set weights.
– Added DEVICE_STATE() dialplan functionality for dialplan device state creation and retrieval.
– Added EXTENSION_STATE() dialplan functionality for retrieving the state of any extension

With that in mind, please note that the AA50 software test plan doesn’t test features and functionality outside of the GUI. So, the syncing of the Asterisk componenet of the AA50 to the C.x line of ABE software is more convenient for Digium (we’re not maintaining two wholely separate and unsynched branches) than probably for any AA50 customers.

It’s not practical right now, or in my view of the forseeable future, for me to internally kick off any development to change the way for our downloads portal to operate - see my previous comment. And, considering the way we support the product, I’m afraid to go too deeply, in the AA50 Changelog, into things that changed underneath the GUI; because, for example, our support department isn’t going to help you build a DUNDi cluster of AA50’s using the nifty new DUNDIQUERY functionality - it isn’t in the GUI.

So, my solution is this:
The next time we do a software release for the AA50, I’ll blog about it. If I mention anything about syncing the AA50 Asterisk component to any particular ABE Asterisk component and I don’t mention any specifics, please feel free to comment and ask me for more information.

Cheers.

I appreciate the response and — no offense intended — but that sounds like bureaucracy-speak and excuse making to me. It may be the reason why it happens to not be available presently but is it justification for not making it available some other way and, going forward, consider a cleaner way of including it down the road too?

I just would appreciate the information to be able to make informed upgrade plans. It’s silly that there’s a AA50 ChangeLog where a big item on it is effectively “includes all this other crud and, by the way, we’re not going to tell you exactly what that crud is but if you happen to have a license for this other product you’ll be able to indirectly decipher what those changes are”. Shall I e-mail the support group and see if someone is simply willing to e-mail the ABE ChangeLog to me?

Heck, put it on an HTTP site somewhere or posted it on this blog. AFAIK there’s nothing that prevents me from posting a healthy excerpt of the AA50 ChangeLog somewhere (indeed I did on my blog recently). Could not someone with an ABE license do the same?

In any case, I’m not directly this at you personally. You just happened to be the one I posed the original query to and that replied to me and this is a forum for communicating with the Digium customer base so seems as good as any.

Any further thoughts appreciated,

-jr

Probably slim to none.

Owners of BE can see the BE Changelogs, but not anything to do with the AA50. Owners of the AA50 can see AA50 Changelogs, but nothing to do with BE. Owners of both see, naturally, both.

Our downloads portal doesn’t provide cross entitlement whereby items in one category (ABE owners) may be multi-tagged to allow users in another category (AA50 owners) access. Building such a capability isn’t in the cards.

Cheers.

Indeed the AA50 1.1.0.1 ChangeLog says:

* AA50 has been synchronized to ABE C.1 branch source code

What are the chances of us AA50 users getting access to the ChangeLog for ABE C1.5 so that we have some idea of the specifics of those changes which were incorporated?

-jr

It would indeed eliminate the need for a separate ATA device. I appreciate your asking me about things that aren’t supported on the AA50.

Please appreciate my inability to provide any comment about things that aren’t supported on the AA50.

Cheers.

Most business customers have a fax machine. In order to reliably use that fax machine over VOIP, they need to use the T.38 protocol. Currently, this can be accomplished by using an ATA and ITSP that supports T.38.

I would like to see T.38 fully supported on the AA50, for at least one of the FXS ports. This would eliminate the need for a separate ATA device. Any thoughts on this?

Thanks,

Tristan Rhodes

No announcements for either of those at the present time.

Cheers.

Great work on the many improvements to the AA50! Do you know when these subscription services for the Asterisk Appliance are going to be available?

Configuration Backup Services (planned)
Monitoring and Outage Notification (planned)

Thanks,

Tristan Rhodes

Yup, what you’re seeing in the 1.6 beta is actually an improvement over what’s in the AA50. res_phoneprov was a quick ‘n dirty utility written and used internally at Digium for years that was cleaned up for the AA50. What you see in SVN is an improvement over what’s currently in the AA50. But, without tons of live test time, we, I, didn’t feel comfortable rolling it into the AA50 just yet. But, look for it in the future as we put additional capability into the AA50 with respect to its phone configurations.

Cheers.

I also noted the phone provisioning in the 1.6 beta which I’m guessing is based on what I first saw on the AA50 and is also in the 1.0.1 of AsteriskNOW. I dig up some more docs for it (in LaTeX format, but readable as plain-text too):

http://svn.digium.com/view/asterisk/trunk/doc/tex/phoneprov.tex?revision=98988&view=markup

Is that the same as what’s in the current AA50 release?

Thanks folks,

-jr