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

Asterisk AMI TransportDetail is missing, stale or exposes secrets

Trace endpoint scope, completion framing, object relationships, versioned fields, redaction and runtime transport state before changing listeners or AMI permissions.

Reviewed 2026-10-21Current branch-23 PJSIPShowEndpoint, TransportDetail, EndpointDetail, EndpointDetailComplete, AMI action-index and res_pjsip references plus transport-selection, object-relationship, troubleshooting and AMI guidance were reviewed October 21, 2026. The reviewed action index does not document a standalone PJSIP transport-list action; endpoint-associated TransportDetail is not a complete all-transport inventory. Installed release, linked PJSIP and TLS libraries, loaded modules, manager actions and permissions, configuration owner, transport population, listener state, connection reuse, DNS, certificate validation, selected message path and call behavior remain deployment specific. No PBX, module, manager account, session, endpoint, transport, password, private key, certificate, socket, connection, DNS result, packet, media stream or live call was inspected or testedAdvancedDocumentation based · not lab tested

Freeze one endpoint-detail transaction

Record node, release, loaded modules, configuration owner, manager identity and permissions, exact endpoint name, ActionID, initial response, every associated event and EndpointDetailComplete. Redact protected fields before the record leaves the restricted incident path.

Classify the first mismatch: action absent or denied; endpoint missing; transaction incomplete; endpoint has no explicit association; TransportDetail omitted; object name or field differs; value is loaded but listener or packet path disagrees; or a secret-bearing row escaped its intended boundary.

Do not search for an undocumented all-transport AMI list

The reviewed branch-23 action index documents PJSIPShowEndpoint but no standalone all-transport list action. The single-endpoint action emits associated object detail and ends with EndpointDetailComplete; there is no separate TransportDetailComplete contract in that transaction.

Use the loaded CLI transport inventory or authoritative configuration for fleet scope. Do not send repeated endpoint actions and treat the union as complete unless the endpoint inventory, node, completion and association model are also preserved.

Resolve absent or surprising association

Inspect the exact EndpointDetail transport field and associated TransportDetail object names. An endpoint without an explicit transport can rely on URI-driven compatible selection, so absence of an associated row must not be rewritten as no transport or no listener.

Compare generated and loaded configuration. Similar endpoint, registration and provider labels do not establish ownership. If a FreePBX-managed source generated the object, correct that owner instead of editing a generated file.

Separate stale detail from an unchanged runtime object

Transport configuration is restart-sensitive by default, while allow_reload is an opt-in capability with disruption risk. Compare submitted value, generated file, loaded detail, CLI object, listener and first post-change message. A stale AMI row and an unchanged listener are related but not identical findings.

For external_signaling_hostname, first confirm the installed maintenance release supports the field and that external_signaling_address is not also configured. A hostname row does not prove current DNS resolution, header output or remote acceptance.

Contain password and topology exposure

If Password, sensitive file paths, private addresses or local networks reached a broad log or ticket, stop further collection, restrict access, preserve the minimum incident record and follow the organization’s credential-rotation and incident process. Do not paste another raw row to demonstrate the first leak.

Review manager reachability, TLS, permissions, event filters, client logging and retention. Redaction after central ingestion is too late for every copy already created.

Verify the corrected boundary without claiming a call result

Repeat one authorized endpoint transaction, require EndpointDetailComplete, confirm redaction, then compare the intended transport object with CLI state, exact listener and one bounded SIP message. For TCP or TLS retain connection reuse, certificate presentation and peer verification separately.

A corrected TransportDetail row is not proof of registration, inbound identification, dialplan, SDP, RTP or hangup. No PBX, manager session, endpoint, transport, secret, certificate, socket, 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, TransportDetail, EndpointDetail, EndpointDetailComplete, AMI action-index and res_pjsip references plus transport-selection, object-relationship, troubleshooting and AMI guidance were reviewed October 21, 2026. The reviewed action index does not document a standalone PJSIP transport-list action; endpoint-associated TransportDetail is not a complete all-transport inventory. Installed release, linked PJSIP and TLS libraries, loaded modules, manager actions and permissions, configuration owner, transport population, listener state, connection reuse, DNS, certificate validation, selected message path and call behavior remain deployment specific. No PBX, module, manager account, session, endpoint, transport, password, private key, certificate, socket, connection, DNS result, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP TransportDetail and secret-safe evidence

Read endpoint-associated transport detail without mistaking it for an all-transport inventory, listener proof, selected socket, TLS negotiation or SIP delivery.

Read guide →
Guide · Current branch-23 PJSIPShowEndpoints, PJSIPShowEndpoint, EndpointList, EndpointListComplete, EndpointDetail and EndpointDetailComplete references, PJSIP object guidance, res_pjsip configuration reference and AMI v2 specification were reviewed October 19, 2026. Installed branch, loaded modules, manager action inventory and permissions, configuration owner, endpoint, AoR, auth, transport, identify, contact, device-state provider, active channel, registration, qualification and call behavior remain deployment specific. No PBX, module, manager account, session, endpoint, AoR, auth, transport, identify, contact, channel, registration, qualification exchange, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP endpoint lists and object detail

Use completed endpoint-list and single-endpoint transactions without turning aggregate device state, contact text or active-channel counts into registration or call proof.

Read guide →
Guide · Asterisk branch-23-generated and branch-22-generated ListCommands references plus official AMI syntax, v2 specification, manager-command, change/versioning, permission, module-loader and network-security documentation reviewed October 16, 2026; installed branch and maintenance release, build, package and module set, manager user, read and write authorizations, session mask, action registration, request framing, parameters, target objects, response, related events and service outcome remain deployment specific; no PBX, module, package, manager user, manager session, request, response, event, configuration file, channel, packet, media stream or live call was inspected or tested

Asterisk AMI command inventory and permission evidence

Use ListCommands and the administrator CLI to distinguish the actions visible to one manager user from the actions registered by the running Asterisk instance.

Read guide →
Troubleshooting · Current Asterisk res_pjsip object, transport-selection, troubleshooting and logging documentation plus FreePBX 17 SIP-setting records reviewed October 6, 2026; installed branch, generated configuration, sockets, active sessions and service behavior require runtime verification

Asterisk PJSIP transport change did not take effect

Separate saved configuration, the loaded PJSIP object, the bound listener and the transport selected by each consumer before restarting or changing ports.

Read guide →
Diagnostic · Current Asterisk PJSIP transport-selection, proxy and troubleshooting guidance plus Asterisk 22 res_pjsip and outbound-registration references reviewed October 7, 2026; no Asterisk host, transport, socket, connection, DNS response, proxy, registrar, endpoint, certificate, request, media path, compatibility, availability, price or live call was inspected or tested

Asterisk PJSIP uses the wrong UDP, TCP or TLS transport

Capture one affected request, then separate its URI, DNS target, explicit object, implicit first-valid choice, existing connection and proxy owner before changing transport order.

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 →
Guide · Operational guidance; Asterisk 22 / FreePBX 17 where applicable

Least privilege for PBX users and integrations

Separate the right to register, place calls, administer the PBX and read sensitive data.

Read guide →