Skip to main content

Create and Edit PJSIP Extensions

Use this page to create or edit a phone extension that registers as a PJSIP endpoint. The form works against the tenant currently selected in the top bar.

The screenshots use the Canistracci Oil demo extension 101 Bella Stone. Creating and editing use the same form: a new extension opens with tenant defaults, while an existing extension opens with saved values.

Creating and editing

ActionDescription
CreateOpen Configuration > Extensions and select New PJSIP peer. Fill the required fields and select Save.
EditOpen an existing extension from the Extensions list. Update the required fields and select Save.
DeleteWhen delete permission is available, open the extension and select Delete. Confirm only after checking routing, phones, queues, and other references.

For PJSIP extensions, the endpoint username normally uses the extension number, a hyphen, and the tenant code, such as 101-CANISTRACCI. Press the swapped-arrow icon beside Username to switch the separator from a hyphen to an underscore, for example 101_CANISTRACCI. If custom usernames are enabled in Admin > Settings, you can enter a username that does not follow the generated tenant-code pattern.

Information

Information section for PJSIP extension 101.
Information section for PJSIP extension 101.

Use this section for the extension identity, endpoint credentials, media basics, groups, voicemail message-waiting indication, DND state, and inbound ring timeout.

BlockPurpose
Number and nameNumber is the internal extension number. Name is the display name used in lists, caller ID, and reports.
Description and emergency notesDescription is an administrator note. Emergency notes can be used by emergency routing and notification logic.
SIP stackShows whether the endpoint is using chan_sip or PJSIP. Users with switch permission can change the stack from this form or from the Extensions list.
Username and passwordEndpoint credentials used by the phone or softphone. The default username pattern is the extension number followed by the tenant code.
Codecs and DTMFControls the allowed audio/video codecs and DTMF signaling mode used by the endpoint.
Media and groupsDirect media, call groups, pickup groups, spy groups, and message-waiting options control how the endpoint participates in calls and monitoring.
Voicemail, DND, and timeoutVoicemail MWI, DND, and inbound dial timeout control how incoming calls are presented and how long the extension rings.

Trunk mode

Additional trunk mode options visible after enabling Trunk on a PJSIP extension.
Additional trunk mode options visible after enabling Trunk on a PJSIP extension.

Enable Trunk only when the PJSIP endpoint is another PBX, gateway, or upstream device that should receive calls by dialed number rather than as a single telephone endpoint. A normal phone extension should usually leave this option disabled.

Field or optionEffect
TrunkChanges how calls are sent to the endpoint. With trunk mode disabled, MiRTA PBX dials the PJSIP endpoint contacts as a phone endpoint. With trunk mode enabled, MiRTA PBX sends the called number to the endpoint, or the configured DID override when one is set.
DID NumberAutomatic sends the original called number to the peer. Set to sends the value entered in the DID number field instead, which is useful when the downstream PBX or gateway expects a fixed pilot number or a rewritten DID.
CallerID Number OverrideControls which outbound caller ID values are preserved from the SIP INVITE received from the trunk device. The default behavior can keep both caller ID name and number from the INVITE. The other choices keep only the number, keep only the name, or ignore the INVITE caller ID and use the caller ID configured on the extension.
Emergency CallerID Number OverrideFor emergency routes, Get Emergency CallerID from SIP Invite allows the emergency caller ID sent by the trunk device to pass through. Do not use Emergency CallerID from SIP Invite makes MiRTA PBX replace it with the extension emergency caller ID, or the tenant default emergency caller ID when the extension does not define one.
CallerID Number SourceSelects where inbound trunk caller ID is read from when a specific source is required. Automatic keeps the caller ID parsed by Asterisk. The explicit choices read the From, P-Asserted-Identity, P-Preferred-Identity, or Remote-Party-ID header and use it to set caller ID before routing.

In the dialplan, PJSIP trunk mode affects both direct endpoint dialing and registered-contact dialing. When contacts are used, MiRTA PBX rewrites the PJSIP contact URI user part from the endpoint identity to the dialed number, or to the DID override. If the endpoint is registered on another node, MiRTA PBX sends the call through the configured inter-node SIP trunking module.

NAT Control

NAT Control section for PJSIP extension 101.
NAT Control section for PJSIP extension 101.

Use this section to control endpoint reachability and keepalive behavior for devices behind NAT or with changing network paths.

BlockPurpose
NATDefines how MiRTA PBX treats NAT traversal for the endpoint.
Qualify and qualify frequencyControls whether the PBX checks endpoint reachability and how often checks are sent.
Keep alive and RTP keep aliveSends periodic traffic to keep network mappings open and detect unavailable devices.

Call Settings

Call Settings section for PJSIP extension 101.
Call Settings section for PJSIP extension 101.

Use this section for call behavior that is not specific to inbound or outbound routing.

BlockPurpose
Fax and volumeControls T.38 fax behavior and transmit/receive volume adjustments.
Music on hold and languageSelects media behavior and the preferred language for prompts played to the extension.
Directories and phone booksControls whether the extension appears in dial-by-name directories and phone book generated lists.
Call waiting and autoanswerControls second-call handling and optional automatic answer behavior for supported phones.

Inbound Recording

Inbound Recording section for PJSIP extension 101.
Inbound Recording section for PJSIP extension 101.

Use this section for recording behavior applied to calls received by the extension.

BlockPurpose
Inbound recording policyControls whether inbound calls are recorded and whether recording privacy behavior is enabled.
Recording notificationsWhen enabled, recordings can be mailed and processed according to tenant recording settings.

Outbound Recording

Outbound Recording section for PJSIP extension 101.
Outbound Recording section for PJSIP extension 101.

Use this section for recording and post-processing behavior applied to calls placed by the extension.

BlockPurpose
Always recordControls whether outbound calls from this extension are recorded, unless tenant-wide settings force recording.
Email recording toSends matching recordings to the configured address. Minimum size can suppress very small recordings.
Transcript, summary, sentimentEnables transcript, summary, and sentiment processing when the tenant supports those services.

Security

Security section for PJSIP extension 101.
Security section for PJSIP extension 101.

Use this section to restrict registration, authentication, abuse behavior, cost limits, and outbound availability.

BlockPurpose
Authentication and network filtersControls endpoint trust, allowed IPs, and authentication-related behavior.
Abuse detection and cost limitsLocks or warns on suspicious or excessive usage according to tenant policy.
Outbound destinationsAllows all calls, blocks calls, or applies a destination regex filter.
Lock PIN and max durationAllows the extension to be locked and caps outbound call duration.
Working hoursRestricts outbound calling to the selected weekday condition.

Web User Panel and Switchboard

Web User Panel and Switchboard section for PJSIP extension 101.
Web User Panel and Switchboard section for PJSIP extension 101.

Use this section to enable user-facing web access and related application permissions for the extension.

BlockPurpose
Access togglesEnables the user panel, web phone, switchboard, and optional custom user application.
Web user and passwordSets the login identity and password. If no web user is specified, the endpoint username is used.
Password policy and 2FAControls expiry, forced change, lock state, LDAP use, and two-factor authentication.
Email, profile, and IP filterSets the user email, sends account information, assigns a user profile, and optionally restricts web access by IP.

Outbound Calls

Outbound Calls section for PJSIP extension 101.
Outbound Calls section for PJSIP extension 101.

Use this section to control the caller ID, emergency caller ID, area-code handling, dialing filters, routing profile, and call rate used by outbound calls.

BlockPurpose
External caller IDSets or hides the caller ID number and name sent on outbound calls.
SMS and override caller IDControls SMS caller ID and optional SIP header based caller ID overrides.
Emergency caller IDDefines the emergency number identity and whether empty emergency caller ID warnings are ignored.
Area code and caller ID regexApplies prefixes and caller ID rewrite rules before routing.
Do Not and Only Allow listsApplies tenant call-list restrictions to this extension.
Routing profile and call rateSelects the routing profile, SMS routing profile, and client rate used by calls.

Inbound Calls

Inbound Calls section for PJSIP extension 101.
Inbound Calls section for PJSIP extension 101.

Use this section for inbound caller ID privacy controls.

BlockPurpose
Block inbound caller ID numberPrevents the caller ID number from being shown to this extension.
Block inbound caller ID namePrevents the caller ID name from being shown to this extension.

Find me/Follow me Configuration

Find me/Follow me Configuration section for PJSIP extension 101.
Find me/Follow me Configuration section for PJSIP extension 101.

Use this section to forward calls to an alternate number when find-me/follow-me is enabled.

BlockPurpose
FMFM number and statusSets the external follow-me number and enables or disables the feature.
Condition and dial methodLimits follow-me behavior to a condition and selects how the alternate number is dialed.
Confirmation and messagesRequires answer confirmation and selects confirm/hold messages.
Caller ID and timingControls caller ID presentation, prefixes, delay, and dial timeout for the follow-me call.

Additional Destinations - Active if checked

Additional Destinations - Active if checked section for PJSIP extension 101.
Additional Destinations - Active if checked section for PJSIP extension 101.

Use this section to define failover or conditional routing for calls that do not complete normally.

BlockPurpose
UnconditionalAlways routes calls to the selected destination when enabled.
On no answer, busy, or offlineRoutes calls when the extension does not answer, is busy, or is offline.
On conditionRoutes calls to a selected destination when the chosen condition matches.
Missed call notificationSends email notifications for missed calls, with options to ignore internal or queue-originated calls.

Note

Note section for PJSIP extension 101.
Note section for PJSIP extension 101.

Use this section for administrative classification and free-form notes, then save or delete the extension.

BlockPurpose
Branch and departmentClassifies the extension for reporting and administration.
Reference ID and additional infoStores external references and notes.
Save, delete, and backSave applies changes, Delete removes the extension when allowed, and Back returns to the Extensions list.