Map the relationships first
An endpoint defines call-related behavior such as codecs and the incoming dialplan context. An auth object supplies authentication settings. An Address of Record, or AOR, represents how Asterisk can contact an endpoint. A transport defines a signaling listener or connection transport. These objects cooperate but solve different problems.
Outbound registration is a separate relationship: it tells another registrar where Asterisk can be reached. It does not automatically create an endpoint, an incoming call identity rule or a safe dialplan.
Logical configuration relationships, not a complete pjsip.conf. An outbound trunk can use a separate outbound-auth relationship.
Build a configuration inventory
For each phone, record the endpoint name, auth reference, AOR reference and context. For each trunk, also record how incoming requests are matched and whether outbound registration is required. Keep credentials outside shared troubleshooting notes.
An object can exist in a file yet fail to load because of a syntax error, unsupported setting or unresolved relationship. Check what the running engine actually loaded instead of assuming a saved file is active.
Inspect before changing
Use pjsip show endpoints to see endpoint state, then inspect the relevant endpoint and AOR. A contact address answers where requests may be sent; a successful qualify response indicates a response to that probe, not a complete successful business call.
If the endpoint exists but calls fail, follow the incoming context and dialed extension. If it does not exist, investigate configuration loading first. This ordering prevents routing edits from obscuring a configuration problem.
pjsip show endpoints
pjsip show endpoint 2101
pjsip show aor 2101
pjsip show contactsApply with the right lifecycle
Some changes can be reloaded; transport changes can require a restart depending on configuration and support. Schedule disruptive work and consult the exact version's reference. In FreePBX, use its supported interface and apply mechanism rather than editing generated files directly.
Watch the explanation
Starts with an extension-not-found error, then builds a small context and follows its priorities in the Asterisk console. A concrete introduction to how an incoming channel finds dialplan instructions.
Read applicability and editorial notes →Watch this video here
Historical 2014 tutorial. Contexts and priorities remain relevant; the chan_sip endpoint commands do not apply to Asterisk 22. Review used the available transcript and primary references; audio and screen readability remain unverified.
The player loads only when you choose Watch here. Playback uses YouTube’s privacy-enhanced embed; YouTube processes playback data.
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.