RESERVE BOUNTY: Aastra XML SLA (Share "Line" Experience)
I've put some more thought into this application. I think it will work like this, but I would appreciate comments:
Each button can be registered to listen to either a specific channel (ie. Zap/1-1) or groups of trunks (Zap, SIP, IAX). If the buttons are registered for a single channel, they will only display behavior for that channel. If they are registered for blocks of channels, they will behave in a round-robin manner where the first active channel in a group or groups will be assigned to the first button "Line 1", the second to "Line 2" and so on.
When a line that is registered is ringing, a SIP message will be sent to the phone with an encapsulated XML object informing the phone to display a blinking LED. When the call is answered, it will go solid, when "on hold" it will go fast blink. Pushing a button while it actively holds a channel will drop the caller into the parking lot and link that slot number with that button and channel. Users will only be able to put a caller on hold on a channel they have answered, but they will be able to take a call off of hold on any channel that has a held call.
The backend of the application will be a script connected to the Asterisk manager processing all applicable channel requests and sending SIP messages to the phones with XML objects. Metermaid and devstate BLF hint capabilities should not be required.
This application will require the latest 2.2 firmware for support of SIP messages with encapsulated XML. It will only work on the 5i series of phones, but should work on the new 913x and 48x phones that are coming out soon based on newer hardware and support for 5i XML capabilities (according to Aastra).
CAVEOTS: I have no idea what kind of load this is going to place on phones. It should be negligable on the server, however. Certainly, it is going to have some kind of total phone limitations, so will most likely only be suitable for smaller "key system like" systems. I won't know the limitations until it's basically done.
There are a lot of things to work out on the technical and configuration sides, but theoretically everything is possible. I'm putting an ETA of 3-4 weeks for a first release if there is enough support to begin development.
This will be developed under the new Reverse Bounty system, as with the Aastra Away (Presence) capabilities (http://trixbox.org/forums/trixbox-forums/open-discussion/bounty-a...). Under the Reverse Bounty system, "heros" contribute a set amount to get the application immediately, have access to premium support and feature requests, and get memorialized in the forums, documentation and installers.
The reserve bounty will be set at $2400 (8 separate $300 "heros"). Due to the unknowns, I will not accept payment until the application is working and I am able to communicate exactly what the capabilities and limitations of it are, but I would like some general feedback and soft commitments before development begins. Upon meeting the reserve bounty, the application will convert to GPL and be distributed to the community.
As with all applications developed under this model, any "heros" contributing towards previous projects under this model will receive this and all future applications under this model in a priority manner.
And as always, all past, current and future Open Telephony Training Seminar participants will receive priority access to these applications during development and premium support. Sign up now for Vegas in May. It looks like you will get a special treat in addition to expanded Aastra XML applications and training.


Member Since:
2007-01-16