Liberty Communication Platform - Create a New Extension

WARNING

Administering a PBX without appropriate telecoms knowledge and training could break the system. Do not attempt to configure your PBX unless you know exactly what you are doing!

The PBX at the heart of the Liberty Communications Platform is a Mitel Openscape Business. This configuration guide is with respect to that system.

Create a New IP (or SIP) Extension

1. Purpose

This engineer/admin guide covers creating a new IP (or SIP) extension in OpenScape Business, validating licensing, applying CLIP (outbound CLI) to meet carrier rules, and enabling UC Suite voicemail where required.

2. Prerequisites

  • Admin access to the OpenScape Business WBM (web interface).
  • PBX management IP/hostname and administrator credentials.
  • Provisioning info: extension (call number), DDI (if applicable), display name, and endpoint type (System IP vs SIP).
  • UC requirements (if any): voicemail/UC Suite access + voicemail email address if message delivery is needed.

3. Check system licensing (always first)

If the correct license is not available, the extension will be created but will not register and/or licensed features (e.g., UC/voicemail) will not function.

Path: License Management → License Status

  • IP User Licenses available (for IP or SIP phones/clients).
  • UC / Voicemail licenses available (only if required for the user).

4. Log into the PBX

  1. Open a web browser.
  2. Browse to: https://<PBX-IP>
  3. Sign in using administrator credentials.

5. Create the new extension

Navigation: Setup → Telephones → Subscribers→ IP Telephones

Note: Fill in the last free line in the table (view can be set to 100 per page for navigation at bottom right)

  1. Add Station – Navigate pages to the last configured extension and select an empty row
  2. Enter the required fields:
    • First Name
    • Last Name
    • Display (This is the name shown on the phone screen 14 Characters Max)
    • CallNo (station Internal Extension Number)
    • DDI: direct dial number (if applicable)
    • Station Type: IP Subscriber (or the relevant SIP/Client type)
    • Class of Service (select valid class, default will be international)
    • Call Pickup (select required call pickup group)
  3. Select Apply.

Engineer note: Ensure Station Type matches the handset/client (e.g., IP Subscriber for Unify system phones; SIP type for SIP endpoints). A mismatch is a common cause of non-registration.

6. Set CLIP (Caller Line Identification Presentation)

Set CLIP to ensure the correct outbound CLI is presented (main DDI or user DDI). If CLIP is wrong/blank, calls may present the internal extension and may fail depending on carrier rules.

Navigation: Setup → Telephones → Subscribers→ IP Telephones

  • Find your extension in the table and click the pencil icon next to it to edit
  • Set Outgoing CLIP Number (e.g., 01224XXXXXX).
  • Example: Extension 225 → Display number = Main DDI or User DDI.

Note: If CLIP is not set correctly, outbound calls may show an internal number and some carriers may reject calls.

7. Configure voicemail / UC (optional)

  • Confirm the user has an appropriate UC/Voicemail license assigned.
  • Navigation: Applications → UC Suite
  • Search for the user by Name or Extension.
  • Set voicemail Password, add email address (Edit user for Change password option) and (if required) voicemail-to-email settings (expand Communications and set options within VM Notification menu option), then save/assign to the extension.

8. Verification checklist

  • Place an internal test call to and from the extension.
  • Place an external outbound test call and confirm the displayed CLI/CLIP is correct.
  • If voicemail enabled: leave a test message and confirm retrieval/delivery.

9. Troubleshooting

  • Extension will not register: re-check licensing (IP/SIP/UC), confirm station type matches the endpoint, and verify credentials/provisioning for the device.
  • Wrong caller ID on outbound calls: verify CLIP settings under the station record and confirm the correct outbound number is entered.
  • Outbound call fails: confirm CLIP is valid for the trunk/carrier and that the user has permission/class of service to dial externally.

10. Notes

  • Keep extension numbering and naming consistent with site standards.
  • Where a user has a dedicated DDI, confirm inbound routing is already in place.
  • Record any changes made (extension, DDI, CLIP) in your service log/ticket.