Skip to content
Phone Guides

Asterisk device state, hints and BLF

A busy-lamp indication is the end of a chain: Asterisk obtains state, a hint associates a monitored extension with a resource, a phone subscribes, and the phone displays what it understands. Inspect each link before declaring a device supported or unsupported.

Source-reviewed, 20 October 2026. Prepared from the cited documentation. No phone light, presence or pickup path has been independently tested by Phone Guides. Scope: Asterisk 22/PJSIP concepts and a simple endpoint-state hint.

Keep state types distinct

Item What it represents
Device state The state supplied for an Asterisk device/resource
Extension state/hint Association used to represent monitored extension state
Presence A separate presence concept or published user condition
BLF display The phone's presentation of received information
Button action What the phone does when the user presses that button

The official device-state reference notes that the state provider determines the meaning of its states. Do not automatically equate a person being unavailable with one endpoint being in a call. Voicemail message waiting is another distinct notification path.

For PJSIP, the endpoint option device_state_busy_at changes when the channel driver reports BUSY instead of INUSE: it does so when the count of in-use channels for that endpoint reaches or exceeds the configured threshold. This is a threshold for Asterisk's device-state result, not a rule that makes a phone display a particular colour or text. Check the exact Asterisk 22 option description alongside the subscriber's behaviour. A concurrent-call test can distinguish the configured threshold from the phone's display mapping.

Associate an extension with a resource

This original dialplan hint monitors the PJSIP resource for account 6002:


[pg-watch]
exten => 6002,hint,PJSIP/6002

It does not create a voice route to 6002 and does not configure a phone button. Keep the ordinary internal-call route separately.

The subscribing endpoint needs permission to subscribe and a context in which its requested extension is found. In that existing endpoint, subscribe_context=pg-watch selects this example context. Compare the exact endpoint options with the Asterisk 22 reference and avoid overwriting unrelated account settings.

Check subscription requirements

The official PJSIP subscription guide describes the required subscription/event-body modules. A device expecting a particular event or body format needs the corresponding supported path. The source also directs readers to the device manufacturer's manual when those expectations are unclear.

Record exact phone model, firmware, account, monitored identity and button type. A label such as BLF on a reseller page does not establish subscription, display and pickup behaviour against a particular Asterisk configuration.

Inspect before changing display settings

Use core show hints and the installed PJSIP CLI's subscription help to inspect the relevant state and subscriptions. Check the requested extension/context and whether notifications reach the subscriber. Then compare what the phone actually displays.

Symptom Question to ask
No subscription Is the phone requesting the intended identity using a documented event format?
Subscription rejected Are the account, subscription permissions, context and hint correct?
State changes but light does not Is the body/event supported and received by the phone?
Light works but pressing it fails Does the configured button action have a valid permitted route?

Reader checks and evidence limits

For your own endpoint checks, observe idle, ringing, answered and ended calls. Include more than one concurrent call if the intended busy behaviour depends on it. Record Asterisk's state, notification and phone display together rather than interpreting one screenshot as proof of the complete chain.

If the button also performs pickup or transfer, check those permissions separately. Do not widen subscription or calling contexts just to make a light change colour. Preserve the previous hint/account configuration for reversal.

Return to Asterisk documentation.