DEVICE_STATE(device) and DEVSTATE(device)

Synopsis

Get or Set a device state
Introduced in Asterisk 1.6 as DEVICE_STATE(), with a backport available for 1.4.

Description

The DEVICE_STATE function can be used to retrieve the device state from any device state provider.
For example:

 NoOp(SIP/mypeer has state ${DEVSTATE(SIP/mypeer)})
 NoOp(Conference number 1234 has state ${DEVSTATE(MeetMe:1234)})

The DEVSTATE function can also be used to set custom device state from the dialplan. The "Custom:" prefix must be used.
For example:

 Set(DEVSTATE(Custom:lamp1)=BUSY)
 Set(DEVSTATE(Custom:lamp2)=NOT_INUSE)

You can subscribe to the status of a custom device state using a hint in the dialplan:

 exten => 1234,hint,Custom:lamp1

The possible values for both uses of this function are:

 UNKNOWN | NOT_INUSE | INUSE | BUSY | INVALID | UNAVAILABLE | RINGING | RINGINUSE | ONHOLD

Troubleshooting

• Make sure you know what will happen after an Asterisk restart! It might be necessary to use a .call file (or the Asterisk manager API) to call the DevState application right after Asterisk has started to ensure correct LED status. Note that, before doing so, you might also have to reboot or initialize the phones in question so that they can renew their SIP subscription of the extension that is used to monitor the devicestate; for example SIP NOTIFY could be used for that purpose (see sip_notify.conf).

See also

• Asterisk func HINT: New HINT() function in Asterisk 1.6
• Asterisk func EXTENSION_STATE: New EXTENSION_STATE() function in Asterisk 1.6
• Backport for Asterisk 1.4
• Extstate() function for 1.4, get extension state instead of device
• Asterisk cmd BristuffDevstate
• Asterisk SLA
• Mini How-To: Blog entry by the author