Skip to content

Add an Extension

Create a new SIP extension that a desk phone, softphone (e.g. Bria, Sangoma Connect), or app can register to. Most new extensions on UnifiedBX are PJSIP — chan_sip is legacy.

Before You Start

  • Pick an extension number that doesn't conflict with ring groups, queues, feature codes, or DIDs. UnifiedBX defaults to 1xxx for users.
  • Decide whether the user gets voicemail.
  • Have the user's email address handy if voicemail-to-email will be enabled.

Steps

  1. Go to User Attributes → Extensions.
  2. Click + Quick Create Extension for the streamlined wizard, OR + Add Extension → Add New SIP [chan_pjsip] Extension for full control. The wizard covers 90% of cases.
  3. General Tab — required fields:
    • User Extension — e.g. 1001.
    • Display Name — caller ID name, e.g. Front Desk or Jane Doe.
    • Outbound CID — leave blank to use the route's CID, or set per-extension as "Display Name" <2075551234>.
    • Secret — auto-generated; copy it now (you'll need it on the phone).
    • Email Address — needed for voicemail-to-email.
  4. Voicemail Tab:
    • Enabled — Yes to give the extension a mailbox.
    • Voicemail Password — 4-6 digits the user types at the prompt.
    • Email Address — same as General if you want VM-to-email.
    • Email Attachment — Yes to attach the .wav.
    • Delete Voicemail — Yes deletes from the mailbox after emailing (recommended if attaching).
    • Play CID / Play Envelope — usually defaults are fine.
  5. Advanced Tab (PJSIP technology): defaults are fine for most desk phones. Adjust only if you have a specific reason:
    • DTMF Mode — leave at RFC 4733 (the standard) unless the phone needs Inband or Info.
    • NAT — Force rport, comedia for users behind home NAT (most softphones); No for desk phones on the same LAN as UnifiedBX.
    • Transport — udp for legacy phones, tls for encrypted, wss for browser clients.
    • Codecs — leave at default (ulaw, alaw) unless you have G.722 / G.729 / Opus needs.
  6. Find Me / Follow Me Tab: see Set Up Find Me / Follow Me — usually skipped at extension creation.
  7. Other Tab: Pin Sets, Recording, Class of Service — usually defaults.
  8. Click Submit.
  9. Click Apply Config.

Provision the Phone

  • For Sangoma/Yealink/Polycom phones managed via Endpoint Manager, the extension is auto-provisioned when you map it to a phone (see Endpoint section).
  • For manual provisioning: enter the extension number, secret, and the UnifiedBX FQDN/IP into the phone's SIP account settings.

Verify

asterisk -rx "pjsip show endpoint 1001"

Look for Status: Available (registered) under the contact. Place a test call to and from the extension.

Common Issues

  • Phone says "registration failed." Wrong secret, wrong server FQDN/IP, or firewall blocking SIP from the phone's source IP (check System Admin → Firewall).
  • Extension number already used. UnifiedBX will reject the form. Pick a free number.
  • VM works but emails don't arrive. Check System Admin → Sysadmin → Email Setup — the SMTP postfix relay must be configured.
  • Inbound caller ID is wrong on outbound calls. Outbound CID on the extension is overriding the route. Clear it or set it correctly.
  • PJSIP vs chan_sip mismatch. If a legacy device only supports chan_sip, change technology when creating the extension. Don't mix freely — port conflicts cause silent registration failures.