Interpret the status in context
An unavailable indication can relate to missing contacts or a failed reachability probe. It is not a complete root-cause statement. Record the endpoint, AOR and contact state from the running Asterisk instance.
Logical configuration relationships, not a complete pjsip.conf. An outbound trunk can use a separate outbound-auth relationship.
Inspect relationships
Use read-only CLI inspection to confirm the endpoint references the expected AOR and auth objects. If the endpoint itself is absent, review configuration loading and parser errors first. If it exists without a contact, investigate phone registration or the configured static destination.
If a contact exists but qualify fails, examine the probe's destination and whether the peer supports and answers the request under its policy. A network path or changed NAT mapping may be involved.
Compare a real call
A qualify result is one observation. Test an authorized internal call and inspect its specific request/response flow. Avoid declaring all service healthy solely because a probe receives a response.
Repair the demonstrated layer
Correct object references, registration or reachability according to the evidence. Do not set a large contact allowance or turn off qualification simply to change the displayed label. Confirm recovery after the phone renews or restarts and verify two-way audio separately.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- IETF RFC 3261 — SIP, including linked updates ↗
- IETF RFC 3550 — RTP and RTCP ↗
- Asterisk res_pjsip configuration ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.