[asterisk-dev] Issue 16732 - device state change notification over manager

[Tilghman Lesher]

On Wednesday 03 February 2010 14:34:23 Olle E. Johansson wrote:
> 3 feb 2010 kl. 21.29 skrev Tilghman Lesher:
> > On Wednesday 03 February 2010 12:54:38 Russell Bryant wrote:
> >> On 02/03/2010 12:42 PM, Olle E. Johansson wrote:
> >>> https://issues.asterisk.org/view.php?id=16732
> >>>
> >>> Haakon has create a patch for managing the custom device states from
> >>> manager. He's also adding events for device state changes in
> >>> devicestate.c that reports EVERY device state change, not only the
> >>> custom ones.
> >>>
> >>> As this can be quite a few notifications, I've suggested him that we
> >>> add a new class, called DEVICEINFO for these events, so that a manager
> >>> can decide upon configuration of the manager account if he/she/it wants
> >>> these events on the manager interface. :-)
> >>>
> >>> Are you all ok with that addition?
> >>
> >> That configuration option sounds reasonable to me.  That's the best
> >> method that we have for providing coarse configuration about what events
> >> are desired.
> >
> > I'm fine with the general concept, but I think the name should be along
> > the lines of DEVICESTATE or DEVICESTATUS.  DEVICEINFO sounds a bit too
> > generic and could potentially cause confusion with information about SIP
> > peers and other types of information about specific devices.
>
> I though we could possibly include other types of device-messages in
> DEVICEINFO. If we named it DEVICESTATE/US it would be specific only for one
> event, which I felt was a shame.

Given how many events the devicestate API can generate, I don't feel that
limiting only devicestate updates to this event type to be problematic.  What
other events are you considering?  Propose them, and we might be adding
two event types, not just one.

-- 
Tilghman