A subscription is not a registration
REGISTER tells a location service where an address can currently be reached. SUBSCRIBE asks to receive changes for an event package. NOTIFY carries the resulting state information. A phone can register successfully while its busy-lamp field remains wrong because the separate event subscription failed. The Event header identifies the package, while Subscription-State describes whether a subscription is pending, active or terminated. Event-package definitions determine the body format and what the state means; a presence document and a dialog-state document are not interchangeable.
Inspect a stale indicator
Capture the initial SUBSCRIBE, its response, the associated NOTIFY and subsequent refreshes. Read expiry values and any termination reason. Check that the monitored identity belongs to the intended tenant and that the subscriber is authorized to observe it. A successful SUBSCRIBE response alone does not prove the phone received or understood the notification body. Follow the NOTIFY transaction too. If the phone displays yesterday's state, investigate refresh failure, a transport reconnect and whether an initial full state was delivered after reconnection.
Design for scale and privacy
Subscriptions multiply with monitored keys: a receptionist monitoring many extensions creates a different workload from a phone with one line key. Estimate both refresh traffic and change-driven notifications before rolling out large BLF templates. Avoid exposing presence or call state to arbitrary authenticated users. Limit the observed resources and event packages to the operator's actual role. During troubleshooting, record the package, target identity and state transitions; redact personal identifiers before sharing a trace. Use event state to explain indicators, not as proof of end-to-end media health.
Watch the explanation
Learn how the X5U’s second display becomes a working directory rather than a list of unexplained buttons. The demonstration searches a company directory, moves between programmed key pages, transfers a caller and contrasts private hold with a shared parking slot. That makes it useful for staff moving between departments or answering calls for colleagues.
Read applicability and editorial notes →Watch this video here
Modern Telecom configuration for a particular customer. Directory contents, key colors, parking slots and dialing rules follow that customer’s template. Review used the available transcript and primary references; audio and screen readability remain unverified.
The player loads only when you choose Watch here. Playback uses YouTube’s privacy-enhanced embed; YouTube processes playback data.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.