[Asterisk-java-users] Backward compatibility and startup performance of DefaultAsteriskManager in Asterisk-Java 1.2 (was: ANNOUNCEMENT: Asterisk-Java 0.2-rc1 released)

[Stefan R. <sr...@re...>]

Thanks for your feedback.

On Thu, 2005-09-01 at 14:53 +0300, Jan Ekholm wrote:
> Seems to work just fine for me. The only thing so far that has bitten me is 
> the change from Channel.getExtension() to Channel.get???().getExtension().

Oh yes, it is not nice to just remove those methods ;)
I readded these methods for 0.2, now there are shortcuts for
- Channel.getCurrentExtension().getContext()
- Channel.getCurrentExtension().getExtension()
- Channel.getCurrentExtension().getPriority()
Besides backward compatibility, thats probably handy if you are not
interested in the channel's extension history.

> I do notice a significantly longer connect/startup time, but I haven't tried to 
> track it down yet, could well be something I do that's not necessary anymore.

This is due to the way the queue initialization works now. I fixed
Asterisk 1.2 to send a QueueStatusComplete event which Asterisk-Java now
waits for and that was not send by Asterisk 1.0.x. So when using
Asterisk-Java with Asterisk 1.0.x you will run into a timeout (default
is 5 seconds).
If you don't need queue information you can get around that with
Asterisk 1.0.x by setting skipQueues to true in DefaultAsteriskManager.

> I also see a lot of fun functionality that's only available in the 1.2 version 
> of Asterisk, maybe I should get someone to upgrade our internal development 
> server. :)

Yes that will be worth it. Asterisk 1.2 includes several nice
enhancements to the Manager API.

=Stefan