VoIP.infoThe independent guide to business communications.
VoIP.info Troubleshooting

Asterisk AMI IdentifyDetail is missing, stale or names the wrong endpoint

Trace endpoint scope, completion framing, Sorcery ownership, hostname expansion, identifier order and the actual inbound request before changing match criteria.

Reviewed 2026-10-21Current branch-23 PJSIPShowEndpoint, IdentifyDetail, EndpointDetail, EndpointDetailComplete, AMI action-index, res_pjsip and endpoint-identifier references plus current configuration-relationship, troubleshooting and AMI guidance were reviewed October 21, 2026. The reviewed branch-23 AMI action index does not document a standalone identify-object list action. The current generated identifier reference explicitly supports hostnames, while the older troubleshooting article still says identify match values cannot be hostnames; this documentation conflict is preserved rather than flattened. Installed release, distributor patches, loaded modules, manager actions and permissions, configuration owner, Sorcery mapping, DNS expansion, identifier order, endpoint policy and inbound request behavior remain deployment specific. No PBX, module, manager account, session, endpoint, identify object, hostname, DNS answer, SIP request, packet, route, media stream or live call was inspected or testedAdvancedDocumentation based · not lab tested

Freeze one endpoint-detail transaction and one request

Record node, release, loaded modules, configuration owner, manager identity and permissions, exact endpoint, ActionID, initial response, associated events and EndpointDetailComplete. Separately retain one authorized inbound request with timestamp, transport, source tuple, Request-URI, relevant headers and the first endpoint-selection or rejection evidence.

Classify the first mismatch: action absent or denied; endpoint absent; transaction incomplete; no associated identify row; object or criteria differ; hostname expansion differs; another identifier wins; or the expected endpoint is selected but a later authentication or routing stage fails.

Do not turn associated detail into an all-identify inventory

The reviewed branch-23 action index documents PJSIPShowEndpoint but no standalone identify-object list action. Its associated detail series ends at EndpointDetailComplete; there is no separate IdentifyDetailComplete contract in that transaction.

Use pjsip show identifies, exact CLI inspection or the authoritative Sorcery owner for node-wide scope. Repeating endpoint-detail actions is not a complete inventory unless endpoint population, node, completion and association are all preserved.

Resolve missing or stale object ownership

Compare ObjectName, Endpoint, EndpointName and every criterion with the authoritative configuration and loaded CLI view. If Realtime, AstDB, memory or a generated PBX layer owns identify objects, prove the correct Sorcery family, node and normal activation path before changing data.

A saved row or GUI record does not prove the queried Asterisk process loaded it. Similar endpoint, trunk and identify labels do not prove association, and editing a generated file can create a temporary mismatch rather than a repair.

Reconcile hostname expansion and versioned fields

If Match contains a hostname, preserve whether SrvLookups is enabled and whether a source port is present. Compare the configured name with the loaded A and AAAA expansion and, where applicable, the documented SIP SRV expansion. A later DNS answer is not evidence that the loaded object refreshed to the same addresses.

Do not apply the older troubleshooting article’s no-hostname sentence blindly: the current generated branch-23 reference explicitly documents hostname behavior. Also verify installed support before relying on MatchRequestUri, whose introduction is maintenance-release specific.

Prove order, eligibility and the actual winner

Record pjsip show identifiers, effective endpoint_identifier_order, the endpoint’s identify_by methods and every overlapping identify object. Within one object, source, header and Request-URI criteria are alternatives. Across mechanisms, an earlier match can prevent a later method from owning the request.

Compare the real source tuple, header and Request-URI with exact loaded criteria. Do not widen a network, add anonymous identification or reorder mechanisms globally merely because an AMI row looks plausible.

Correct the first owner and retest both sides

Correct only the demonstrated source: manager permission, endpoint name, Sorcery mapping, generated configuration, hostname or source-port input, regular expression, identifier order or endpoint policy. Repeat the completed AMI transaction and verify one authorized request plus an unrelated negative request.

Keep selected endpoint, authentication, context, dialplan, SIP result, SDP and media separate. A corrected IdentifyDetail row is not proof of registration, call routing or two-way audio. No PBX, manager session, endpoint, identify object, DNS answer, packet, media stream or live call was inspected or tested.

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.

Continue your research

Guide · Current branch-23 PJSIPShowEndpoint, IdentifyDetail, EndpointDetail, EndpointDetailComplete, AMI action-index, res_pjsip and endpoint-identifier references plus current configuration-relationship, troubleshooting and AMI guidance were reviewed October 21, 2026. The reviewed branch-23 AMI action index does not document a standalone identify-object list action. The current generated identifier reference explicitly supports hostnames, while the older troubleshooting article still says identify match values cannot be hostnames; this documentation conflict is preserved rather than flattened. Installed release, distributor patches, loaded modules, manager actions and permissions, configuration owner, Sorcery mapping, DNS expansion, identifier order, endpoint policy and inbound request behavior remain deployment specific. No PBX, module, manager account, session, endpoint, identify object, hostname, DNS answer, SIP request, packet, route, media stream or live call was inspected or tested

Asterisk AMI PJSIP IdentifyDetail and endpoint-match evidence

Read endpoint-associated identify detail without mistaking loaded criteria for a complete identify inventory, the winning identifier or proof that an inbound request matched.

Read guide →
Guide · Asterisk 22 LTS res_pjsip and endpoint-identifier references, the Asterisk endpoint-identification article and GHSA-qqxj-v78h-hrf9 were reviewed October 8, 2026; no PBX, package, module, configuration, endpoint, identify object, address, DNS answer, request, security event, registration, authentication, route, media path or live call was inspected or tested

Asterisk PJSIP endpoint identification: order, scope and evidence

Control how Asterisk 22 maps an incoming SIP request to an endpoint before authentication and dialplan routing.

Read guide →
Troubleshooting · Asterisk 22 LTS res_pjsip and endpoint-identifier references, the Asterisk endpoint-identification article, current object-relationship and troubleshooting guidance and GHSA-qqxj-v78h-hrf9 were reviewed October 8, 2026; the installed branch, patches, modules, generated configuration, endpoints, identify objects, DNS, provider signaling addresses, proxy path and SIP transactions require runtime verification

Asterisk PJSIP cannot identify an inbound request: endpoint-matching diagnosis

Trace the rejected SIP message through loaded identifier modules, global order, endpoint permissions and exact IP, username, header or request-URI evidence before changing authentication or routing.

Read guide →
Troubleshooting · Asterisk 22 LTS res_pjsip and endpoint-identifier references, the endpoint-identification article, current Asterisk PJSIP guidance and GHSA-qqxj-v78h-hrf9 were reviewed October 8, 2026; adapt the method to the installed patch, provider handoff and PBX management layer

Inbound SIP trunk rejected as an unidentified endpoint

Trace a carrier INVITE from packet source to PJSIP identify object before changing DID routes or authentication.

Read guide →
Guide · Current Asterisk Realtime architecture, PJSIP Realtime tutorial, Sorcery mapping and caching guidance, Realtime schema-management guidance, PJSIP troubleshooting guide, and upstream extconfig and sorcery samples reviewed October 15, 2026; installed Asterisk branch, packaged modules, mapping order, connector, DSN, driver, schema revision, database account, rows, cache policy, reload behavior and PJSIP runtime state remain deployment specific; no host, module, connector, credential, database, schema, row, cache, endpoint, registration, message, packet or live call was inspected or tested

Asterisk PJSIP Realtime: Sorcery mapping, schema and cache boundaries

Map one PJSIP object from Sorcery type and source order through Realtime family, connector, schema row, cache and runtime consumer.

Read guide →
Guide · FreePBX 17 / Debian 12 editorial baseline; Sangoma Asterisk SIP Settings guidance, FreePBX sipsettings release/17.0 source and current Asterisk PJSIP configuration, NAT, transport-selection and Asterisk 22 option references reviewed October 11, 2026; older Sangoma screenshots and field descriptions are semantic guidance rather than an exact map of every installed module build; installed FreePBX, sipsettings and Asterisk versions, saved values, generated files, loaded objects, listeners, firewall, DNS, certificates, endpoints, trunks, registrations, SDP, RTP and calls require local evidence, and no PBX or call was inspected or tested

FreePBX Asterisk SIP Settings: transport, NAT and media boundaries

Map each GUI control to generated PJSIP transport, address, codec, media or TLS state, then prove the loaded listener and call path after activation.

Read guide →