Asterisk PJSIP configuration objects explained
Treat PJSIP configuration as a set of related objects. A working account needs the right relationships as well as the right username and password. Start by naming each object and the job it performs.
Source-reviewed, 18 October 2026. Prepared from the cited documentation. Examples have not been independently tested by Phone Guides. Scope: direct file-based Asterisk 22/PJSIP configuration. A managed PBX may generate these objects for you.
Read the object map
| Object | Job | Typical relationship |
|---|---|---|
| Transport | Defines a SIP listening/connection transport | Referenced by an endpoint or outbound registration |
| Endpoint | Describes handling of SIP communication for a peer | Refers to authentication and address objects; selects a dialplan context |
| Auth | Supplies authentication settings | Endpoint auth for incoming authentication; outbound_auth for authentication to a peer |
| AOR | Associates an endpoint with reachable locations | Endpoint aors points to one or more AORs |
| Contact | Represents a reachable SIP location | May be learned through registration or configured statically |
| Identify | Associates incoming traffic with an endpoint using configured identification rules | Often used for documented provider source addresses |
| Registration | Makes Asterisk register to a remote registrar | Separate from the endpoint used to handle calls |
These relationships are explained in the upstream configuration sections guide. The names in square brackets identify objects; type= tells Asterisk which kind of object the section defines.
Walk through one relationship
The following is an object-link illustration, not a complete account. It deliberately omits credentials, transport and several choices:
[6001]
type=endpoint
context=pg-internal
auth=6001-auth
aors=6001
[6001-auth]
type=auth
; Authentication settings belong here.
[6001]
type=aor
max_contacts=1
Here the endpoint refers to 6001-auth and the AOR named 6001. PJSIP can have endpoint and AOR objects with the same name because they have different types. Do not give every object the same name just to avoid understanding those references. The next guide supplies a two-account example.
For dynamic phone registration, account identity and AOR naming must agree with the registration request. For provider identification, use the provider's documented addressing/authentication scheme. Do not infer it from whichever source address happened to appear in one trace. Check the relevant module reference for identification rules.
Separate registering phones from registering to a provider
A phone registering to Asterisk causes Asterisk to learn that phone's contact. Asterisk registering to a provider is the opposite role and uses an outbound registration object. The presence of an outbound registration does not create all inbound/outbound call-routing configuration automatically.
The official outbound registration reference is the starting point for the latter case. Keep a checklist of endpoint, authentication, AOR/contact, identification, registration and dialplan requirements rather than treating a registered status as a complete trunk installation.
Inspect relationships in the running system
From the Asterisk CLI:
pjsip show endpoints
pjsip show endpoint 6001
pjsip show aor 6001
pjsip show contacts
pjsip show registrations
Use the command that answers the current question. An empty registrations list can be normal for local phones registering to Asterisk; those phones are inspected through AORs and contacts. A listed contact is not proof of a completed call.
When a referenced object is missing, inspect exact spelling, section type, includes, reload errors and configuration ownership. Review the matching release's sample configurations and module option reference before adding guessed settings.
Continue with registering two phones and internal calls. Return to Asterisk documentation.