Frequently Asked Question

Modules to Remove
Last Updated 12 hours ago

Modules to Remove

Why Unused / Unneeded Modules Are a Risk

Risk Impact
Security surface area – every installed module adds code that could contain vulnerabilities. Hackers have more places to look for an entry point.
Performance drag – background services, licence checks and scheduled jobs run for every module, even if you never use it. CPU, memory and I/O are wasted, which can slow down call processing and the web UI.
Licence & compliance confusion – you may be paying for licences you never use, making audits harder to explain. Unnecessary cost and potential compliance questions.
Maintenance overhead – each module must be patched and kept compatible with the core system. More time spent on updates and a higher chance of incompatibilities.

Removing the modules you don’t need therefore makes your PBX faster, more secure and easier to maintain.


Modules That Can Safely Be Removed

Note: Before you start, back up the system configuration and verify that none of the listed modules are referenced in any custom dial‑plans, APIs or third‑party integrations.
Category Modules
General PBX features Advanced Recovery, Call Accounting, Class of Service, OEM Branding, PBX MFA, PBX SAML, Phone Apps, Sangoma Connect, Appointment Reminder, Broadcast, CallerID Management, Conference Pro, Oracle Connector, Paging Pro, Parking Pro, Queues Pro, Sangoma Property Management, Sangoma Realtime API, Voicemail Notifications, Web Callback
DAHDi / telephony drivers DAHDi Config (only keep if you are using DAHDi)
Routing & limits Extension Routes, Outbound Call Limit
Third‑party integration packs SIPSTATION, VoIPInnovations
Reporting & analytics CDR Reports Pro, Call Recording Report, Pinsets Pro, Queue Reports, Queue Wallboard, Scribe, smsplus, Voicemail Reports
CRM & endpoint tools Customer Relationship Manager, Endpoint Manager
Fax & extra services Fax Configuration Professional

How to Remove the Unused Modules (Step‑by‑Step)

  1. Take a full backup
  • Export the PBX configuration (XML/JSON) and copy the database dump to a safe location.
  • Snapshot the virtual machine or take an image of the physical appliance.
  1. Disable the module first
  • In the web GUI, go to Modules → Installed.
  • Click Disable for each module.
  • Restart the PBX services (or reboot) and confirm the system runs normally for at least 15 minutes.
  1. Uninstall the module
  • After confirming no errors, click Uninstall.
  • The system will remove the module files and any scheduled jobs.
  1. Document the change
  • Record the date, modules removed, and any notes on the process in your change‑log.

Keeping the Remaining Modules Up‑to‑Date

  • Schedule regular updates – at least once a month, run the System Update wizard or use your package manager to fetch the latest module releases.
  • Subscribe to Sangoma security advisories – they announce critical patches for specific modules.
  • Automate health checks – enable the built‑in Module Health monitor; it will alert you when a module is out‑of‑date or failing a licence check.
  • Test updates in a lab – if you have a staging PBX, apply patches there first to confirm compatibility with your custom dial‑plans.
  • Document version numbers – maintain a simple spreadsheet with module name, installed version and date of last update.

By trimming the unused modules and keeping the rest current, you’ll enjoy a leaner, faster and more secure PBX environment. If you need assistance with any of the steps, our support team is happy to help.


This website relies on temporary cookies to function, but no personal data is ever stored in the cookies.
OK
Powered by GEN UK CLEAN GREEN ENERGY

Loading ...