Skip to content
Phone Guides

Diagnose Asterisk PJSIP registration failures

Identify which device is registering to which service. A phone registering to Asterisk and Asterisk registering to a carrier use different objects and status views. Start with the failing direction rather than changing every account.

Source-reviewed, 19 October 2026. Prepared from the cited documentation. Commands have not been independently tested by Phone Guides. Scope: Asterisk 22/PJSIP; account names below are illustrative.

Establish the expected relationship

For a phone, record its server address, transport, authentication identity and the intended endpoint/AOR. For an outbound trunk registration, record the carrier's registrar, client identity and selected outbound authentication object. A trunk using source-address authentication may not require registration at all.

Use the upstream PJSIP object relationships and outbound registration guide to separate those responsibilities.

Inspect loaded state

At the Asterisk CLI, choose the relevant objects:


pjsip show endpoint 6001
pjsip show aor 6001
pjsip show contacts
pjsip show registrations

Substitute actual names. The final command reports Asterisk's outbound registrations, not a list of locally registered phones. If an expected object is absent, check module/startup errors, file includes or database ownership before diagnosing its password.

Compare the loaded object with the intended source. An edited file is not evidence that a rejected configuration was applied. Use files, CLI and reloads for ownership and change handling.

Follow one exchange

Observation Next question
No request reaches the intended service Is the address, port, transport and route correct?
An authentication challenge arrives Does an authenticated retry follow?
Retry is rejected Do identity, realm, secret and peer requirements match?
Registration succeeds but contact is unusable Is the recorded destination reachable through the actual network path?
Contact repeatedly disappears What do expiry, refresh attempts and later responses show?

One challenge is a normal part of some authentication exchanges. Diagnose from the sequence and final result. The official PJSIP troubleshooting guide provides specific failure examples.

Capture one bounded attempt

First record the object state and the direction being tested. For a phone, inspect its endpoint, AOR and contacts. For a carrier registration, inspect the named outbound registration and its reported state. The latter has Registered, Rejected, Unregistered and Stopped states; Unregistered alone does not prove an authentication fault because it can also mean the attempt has not started or has timed out.

When a message sequence is needed, enable the PJSIP logger for one controlled reproduction and turn it off immediately afterwards:


pjsip set logger on
pjsip set logger off

Run the first command, reproduce one attempt and record its time, then run the second. For a carrier registration, inspect its loaded state and named object:


pjsip show registrations
pjsip show registration carrier-registration

For a phone, use pjsip show endpoint 6001, pjsip show aor 6001 and pjsip show contacts. Check whether an AoR is associated and whether the expected contact appears. If an inbound registration reaches Asterisk but is rejected, verify that the registrar module and AoR loaded, max_contacts is configured, and its limit matches the intended number of simultaneous contacts. Do not raise the limit or enable replacement until that is the observed failure and the device policy permits it.

Treat SIP traces as sensitive operational data. Keep them private, retain only the short exchange needed to identify request direction, final response and timing, then redact authentication headers, account names, addresses and phone numbers before sharing. The troubleshooting guide recommends CLI logging for diagnosis; it does not make a trace safe for public posting.

Captured result Next check
No outbound REGISTER and no loaded registration object Check configuration load errors, type=registration, and the server_uri and client_uri formats
Outbound status is Rejected Read the final registrar response and the matching registration/auth settings before changing credentials
Phone REGISTER is rejected before a contact appears Check endpoint identification, authentication, AoR loading, registrar module and contact limits
Phone contact appears but calls cannot reach it Compare the bound contact and transport with the actual reachable network path
Challenge then authenticated retry succeeds Authentication exchange is working; continue with contact expiry and reachability if the symptom remains

Use the official outbound registration status reference for the loaded state and named-registration details. A retry stopped by a permanent failure or retry limit needs the documented configuration correction and retry policy; repeatedly unregistering an object does not establish the cause.

Keep security and reachability separate

For TLS, establish name/trust validity before analysing later account behaviour. Preserve certificate verification. If traffic is absent, inspect the intended network path rather than disabling authentication or exposing additional services.

Record exact response direction and account identity privately. A carrier rejecting an outbound request is a different boundary from Asterisk rejecting a phone. Redact secrets and authentication material from any shared trace.

Confirm the repair

Change one justified setting and repeat registration. Check the resulting contact or outbound registration state, then separately check an authorised call, two-way audio and hangup. Registration success does not establish routing permissions or the media path.

Use register two phones for the example local accounts and first troubleshooting checks for bounded logging. Keep the previous configuration available for reversal.

Return to Asterisk documentation.