[asterisk-dev] Asterisk Support for as-feature-event package

[Olle E. Johansson]

> 
>> Currently we have no DND or forward states on extensions... You could
>> potentially connect this to custom states to have maximum flexibility.
> 
> I think this would be a good feature to have.  It could be something like chan_sip registering new device state providers for other sorts of states.  I think it would be best to try to not introduce logic that tries to mesh this in with normal device states.  Having it as its own state type would be neat, though.
> 
> exten => foo,hint,SIP-dnd:mypeer
> 
> Call forward state is a bit more complicated, since there is custom meta data associated with a call forward.  It's not just a state.
> 
> If anyone wanted to work on this, let's be sure to review the design on this list before you go off and code it to make sure we've got good agreement on the approach.

Why limit it to SIP? We're still building a multiprotocol PBX, right?

We need to come up with a state that matches XMPP and SIP presence - there's a generic IETF guideline for this that I forgot the name for.  The only object in Asterisk we can match it to is the voicemail accounts, lacking a user concept  - hint: my old AUM code....

/O