[Home]

Summary:ASTERISK-07825: Ability to set hints for non-device related extensions
Reporter:Steven BerkHolz (steveb)Labels:
Date Opened:2006-09-26 12:30:48Date Closed:2011-06-07 14:03:02
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Functions/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Please add (or comment on) the ability to set hints for non-device related extensions.
This would build onto OEJ's device state changes.

Concept:
def: A vitual extension, one that does a feature/function, but not channel related.

Example of setting the hint manually:
I create a vitual extension to do a task, such as day/night mode.
I would like to be able to set the hint status manually in the dialplan.
The purpose of setting this is to be able to have phones subscribe to the status and set a BLF.
Ex. Day mode is pressed, all of the code is run, then the hint is set to InUse so that the light on the phone lights up.


Example of reading the hint status in the dialplan.
Another scenario I am looking at relates to the ability to set the parking slot in 1.4.
I would define parking slots ex. 701 through 709.
I would have another extension (5701) that would have a hint for parking slot 701.(This is doable now)
When the button is pressed on the phone, If the hint is Idle, park the call on slot 701, if the hint is InUse, pickup the call from slot 701.
This way the receptionist can have a string of button that work like most key systems.



















****** ADDITIONAL INFORMATION ******

I am at a loss as to where to start writing this.

I was advised that an agi can query device state, but the day/night mode example has no real channel or device.

My next place to look is where the device states are set in code to see if I can expose that either to the dialplan or an agi.

Please advise.
Comments:By: Russell Bryant (russell) 2006-09-26 14:49:14

Please use the asterisk-dev mailing list for discussion on how to implement a new feature.  Thanks!