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

Asterisk PJSIPRegister or PJSIPUnregister fails, targets the wrong object or has no lasting effect

Trace action authority, completed inventory, exact object identity, conflicting unregister semantics, SIP exchange, event vocabulary and later refresh state before repeating control.

Reviewed 2026-10-23Current branch-23 PJSIPShowRegistrationsOutbound, OutboundRegistrationDetail, AuthDetail, PJSIPRegister, PJSIPUnregister, Registry and res_pjsip_outbound_registration references plus outbound-registration, troubleshooting and AMI guidance were reviewed October 20, 2026. The reviewed action documentation and configuration guide differ on whether a manually unregistered object stops future attempts or later re-registers from its last expiration, so installed-branch behavior must be observed. Installed release, loaded module, manager action inventory, permissions, event delivery, object population, timer state, persistent configuration, resolver, transport, registrar response and call behavior remain deployment specific. No PBX, module, manager account, session, registration object, auth object, credential, REGISTER exchange, DNS result, timer, provider binding, packet, media stream or live call was inspected or testedAdvancedDocumentation based · not lab tested

Freeze one control attempt and its expected transition

Record node, release, module, manager identity and permissions, action, exact Registration value, correlation value, pre-action completed detail, immediate response, SIP exchange, Registry events, post-action completed detail and observation beyond the earlier refresh boundary. Redact credentials and protected auth fields.

Classify the first mismatch: action absent; permission denied; list incomplete; object absent or wrong; action rejected; no SIP request; registrar rejection; state changed then reverted; observer missed an event; or registration changed but the separate call path did not.

Prove action availability and manager authority

Confirm the installed branch exposes the action and res_pjsip_outbound_registration is loaded. Verify the manager identity can execute the action and receive the required command and system events through its protected connection.

A connected manager socket is not authorization. Current branch-23 documentation is not proof that an older distribution exposes the same action, fields or behavior.

Resolve the object from a completed list

Require OutboundRegistrationDetailComplete, then match ObjectName exactly. Compare client and server URIs, proxy, transport, auth reference, status, retry controls and NextReg. Do not stop parsing when one target row appears because associated auth rows and terminal counters remain part of the transaction.

Do not substitute *all for an unresolved name. A FreePBX trunk label, SIP username and registration object name can differ.

Test the documented unregister disagreement safely

The action page says unregister stops later attempts; the configuration guide says manual unregister can re-register from the prior expiration. Preserve both statements and test only one authorized object on the installed branch.

Observe the unregister request and response when present, a fresh list, any Registry event and state beyond the old refresh boundary. Do not interpret temporary silence as proof that retries are disabled.

Keep action, event, detail and packet evidence distinct

An AMI success shows request acceptance, not registrar success. Registry can emit Registered, Unregistered, Rejected or Failed; OutboundRegistrationDetail documents Registered, Unregistered or Rejected; CLI guidance also describes Stopped. Retain producer and timestamp.

If no packet follows acceptance, investigate object and runtime state. If a request receives no response, investigate destination and transport. If it is rejected, follow authentication, registrar policy and exact response.

Correct the first divergence and retest one object

Correct only the proven boundary: release, module, AMI permission, parser, object name, configuration ownership, proxy, transport, authentication, retry policy or registrar requirement. Repeat one action, complete the list, observe the next scheduled refresh and verify unrelated objects.

Do not build an automatic action loop that defeats retry policy or provider limits. Registration is not proof of inbound routing, outbound calling or media. No PBX, manager session, registration, packet, provider binding, media stream or live call was inspected or tested.

Do not infer state from an accepted control response

The AMI list diagnostic correlates control, Registry, SIP and completed-list evidence.

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 Asterisk branch-23 PJSIPShowRegistrationsOutbound, OutboundRegistrationDetail, AuthDetail, PJSIPRegister, PJSIPUnregister, Registry and outbound-registration documentation was reviewed October 23, 2026. The action page and configuration guide still differ on post-unregister scheduling, so installed-branch behavior must be observed. No PBX, module, manager account, session, registration object, auth object, credential, event stream, SIP exchange, DNS answer, timer, provider binding, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP outbound-registration inventory: completion, state and secret boundaries

Collect the complete outbound-registration event list, preserve each status vocabulary and prevent associated authentication secrets from escaping.

Read guide →
Guide · Current branch-23 PJSIPShowRegistrationsOutbound, OutboundRegistrationDetail, AuthDetail, PJSIPRegister, PJSIPUnregister, Registry and res_pjsip_outbound_registration references plus outbound-registration, troubleshooting and AMI guidance were reviewed October 20, 2026. The reviewed action documentation and configuration guide differ on whether a manually unregistered object stops future attempts or later re-registers from its last expiration, so installed-branch behavior must be observed. Installed release, loaded module, manager action inventory, permissions, event delivery, object population, timer state, persistent configuration, resolver, transport, registrar response and call behavior remain deployment specific. No PBX, module, manager account, session, registration object, auth object, credential, REGISTER exchange, DNS result, timer, provider binding, packet, media stream or live call was inspected or tested

Asterisk PJSIPRegister and PJSIPUnregister: runtime control with state proof

Control one loaded outbound-registration object without confusing action acceptance, unregister semantics, later retry state, provider binding or call readiness.

Read guide →
Troubleshooting · Current branch-23 PJSIPShowRegistrationsOutbound, OutboundRegistrationDetail, AuthDetail, PJSIPRegister, PJSIPUnregister, Registry and res_pjsip_outbound_registration references plus outbound-registration, troubleshooting and AMI guidance were reviewed October 20, 2026. The reviewed action documentation and configuration guide differ on whether a manually unregistered object stops future attempts or later re-registers from its last expiration, so installed-branch behavior must be observed. Installed release, loaded module, manager action inventory, permissions, event delivery, object population, timer state, persistent configuration, resolver, transport, registrar response and call behavior remain deployment specific. No PBX, module, manager account, session, registration object, auth object, credential, REGISTER exchange, DNS result, timer, provider binding, packet, media stream or live call was inspected or tested

Asterisk outbound registration is rejected, stopped or has no scheduled retry

Separate loaded-object state, detail and Registry vocabularies, retry classification, NextReg and runtime controls before forcing another REGISTER.

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 →
Guide · Asterisk 22 LTS

Asterisk outbound registration: what it proves

Distinguish a carrier registration from endpoint configuration and successful incoming or outgoing calls.

Read guide →
Guide · Wireshark 4.x / current upstream tool documentation; inspect installed versions

VoIP packet-capture methodology

Select interfaces, time windows and paired capture points that distinguish network loss from missing evidence.

Read guide →
Troubleshooting · Current Asterisk branch-23 PJSIPShowRegistrationsOutbound, OutboundRegistrationDetail, AuthDetail, PJSIPRegister, PJSIPUnregister, Registry and outbound-registration documentation was reviewed October 23, 2026. The action page and configuration guide still differ on post-unregister scheduling, so installed-branch behavior must be observed. No PBX, module, manager account, session, registration object, auth object, credential, event stream, SIP exchange, DNS answer, timer, provider binding, packet, media stream or live call was inspected or tested

Asterisk AMI outbound-registration list is missing, stale, miscounted or exposes secrets

Find the first failure across action availability, event-list completion, correlation, status counting, timer interpretation and authentication redaction.

Read guide →