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

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.

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 a completed state snapshot

Collect the full PJSIPShowRegistrationsOutbound transaction through OutboundRegistrationDetailComplete. Match the exact object, client and server URIs, transport, proxy, auth reference, status, NextReg, retry controls and completion counters. Redact protected auth material.

If the object is absent, investigate configuration ownership, syntax, URI validation and loading. A partial list, dashboard label or missed event is not a completed empty or stopped state.

Preserve the producing status vocabulary

OutboundRegistrationDetail documents Registered, Unregistered and Rejected. The CLI guide also describes Stopped. Registry can report Registered, Unregistered, Rejected or Failed, while the list-complete event counts Registered and NotRegistered.

Do not collapse these into one offline label. Record the source, timestamp and exact value, then correlate the latest state with the last bounded SIP exchange.

Classify temporary, authentication and fatal responses

The outbound-registration guide treats no response, 408, 500, 502, 503, 504 and 600-class responses as temporary. Loaded retry interval and maximum retry count govern later attempts. Authentication rejection, 403 and other fatal responses have separate controls.

Do not loosen intervals merely to create visible traffic. First confirm registrar identity, realm, credentials, account state and response policy; repeated errors can hide a durable fault or trigger upstream protection.

Interpret NextReg with the retry history

NextReg is a point-in-time countdown reported for the loaded object. The Asterisk example shows zero after registrations reached their maximum retry count. Zero is therefore not proof of an immediate attempt, a disabled scheduler or a particular failure cause.

Preserve the last response, retry count, control action, configuration reload, DNS and connection observations. A changed DNS answer alone does not restart a stopped state or close an existing transport.

Use runtime control only after finding the first divergence

PJSIPRegister restarts a loaded object by unregistering first and scheduling from current configuration. PJSIPUnregister has conflicting current documentation about later attempts, so confirm installed behavior and observe beyond the prior refresh boundary.

Do not use *all or a repeated action loop to compensate for a malformed URI, wrong proxy, rejected credentials, exhausted retries or a configuration owner that will regenerate the fault.

Verify registration and calls as separate outcomes

After correction, preserve a new REGISTER exchange, accepted expiration, completed state snapshot and at least one scheduled renewal. Then test inbound routing and outbound calling independently when authorized, including media and release.

A Registered value establishes neither the provider’s DID route nor dialplan, caller identity, codec, RTP or hangup success. No PBX, registration, provider binding, packet, media stream or live call was inspected or tested.

Read stopped behavior against retry and NextReg evidence

The AMI inventory guide preserves the unresolved unregister scheduling conflict and installed-branch 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 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.

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 · Current Asterisk PJSIP transport-selection, DNS API, res_resolver_unbound and outbound-registration documentation plus RFC 3263 and RFC 2782 were reviewed October 8, 2026; no Asterisk or FreePBX host, resolver, nameserver, DNS zone, cache, URI, proxy, registrar, transport, connection, registration, request, failover event, availability, compatibility or call was inspected or tested

Asterisk PJSIP DNS resolution: SRV, TTL and live-state boundaries

Trace a SIP URI through Asterisk's resolver, SRV selection, address family, transport and live registration state without treating a DNS edit as immediate failover.

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 →