Skip to content
Phone Guides

Asterisk configuration files, CLI and reloads

Inspect the running configuration before editing a file. Asterisk can use different directories, included files or database-backed settings, and a management product may generate files that look hand-editable.

Source-reviewed, 18 October 2026. Prepared from the cited documentation. Commands have not been independently tested by Phone Guides. Scope: Asterisk 22 command and file concepts; paths and access depend on installation.

Know which prompt you are using

From a Linux shell, asterisk -r attaches to the running Asterisk CLI. A shell command such as the following sends one CLI instruction and returns:


asterisk -rx 'core show settings'

Inside the Asterisk CLI, enter just the instruction:


core show settings
core show version
core show help

Do not paste the shell wrapper into the Asterisk prompt. Use help or tab completion to check a command accepted by your build. The upstream CLI syntax and help guide explains the distinction between commands and their arguments. CLI access itself needs permission to reach the control socket.

Map files to jobs

File Job in a direct file-based installation
asterisk.conf Directories and process options
modules.conf Module loading policy
pjsip.conf PJSIP configuration objects, possibly split with includes
extensions.conf Dialplan instructions and includes
rtp.conf RTP resource settings
logger.conf Logging outputs and levels

The directory reference describes configurable locations. /etc/asterisk is a common configuration directory, not proof that it is the one used by your process. Record effective locations from core show settings and the startup configuration.

Read state before making a change

Useful CLI questions include:


module show like pjsip
pjsip show endpoints
pjsip show contacts
dialplan show pg-internal
core show channels

Here pg-internal is the example context used in our call guides. Substitute an existing context if investigating another system. A missing command can mean its module is not loaded; consult help and the startup log rather than assuming a syntax error in the file you just edited.

For an individual setting, use the running module's documentation:


config show help res_pjsip endpoint context
core show application Dial

This keeps option and application help tied to the installed system. The PJSIP relationships guide documents configuration help; its examples should still be compared with the relevant release reference.

Apply one small change

Preserve the previous file and its permissions, note the intended difference, and choose an appropriate maintenance window. After editing a file-based dialplan, dialplan reload reloads the dialplan; use dialplan show to confirm the expected extension and priorities. A successful reload message alone is not a call test.

For PJSIP objects, use the reload procedure accepted by your installation and read the log for rejected options. Transport changes deserve special attention: the upstream transport documentation describes allow_reload and its limitations. Do not assume every listening-address or transport change becomes effective after an ordinary reload. A restart can interrupt service and needs planning.

If a change fails, restore the previous values, apply the necessary reload/restart and read back the object or route again. Avoid repeated broad reloads that make it harder to connect a symptom to a particular edit. For managed PBXs, use the product's configuration application process instead.

Continue with PJSIP configuration or troubleshooting. Return to Asterisk documentation.