This is a list of new features in Enswitch 3.15. It is not exhaustive; some enhancements are too minor to list. A full list of features is also available.

Highlights of 3.15

  • The new web interface is now the default. The old web interface is still available as an option.
  • New routing engine for text messages, allowing inbound text messages to be routed independently of calls.
  • Each peer can have a separate pricing table, allowing pricing from multiple carriers to independently loaded.
  • XMPP/Jabber based presence and messaging.
  • Ticket system for providing support to customers.

Telephony

  • Asterisk 13 is the default for new installations.
  • Time periods can be one-off with a start and end date and time.
  • IP address whitelists can be set per customer, as well as per telephone line.
  • Alerts can be sent for failed SIP registrations.
  • Alerts can be sent for callers hanging up in a hunt group or queue.
  • Calls do not enter queues if no destinations are registered.
  • Calls can be sent to remote SIP URIs via TCP.
  • Call spy can be done in any call direction.
  • Music on hold can be shared with customers.
  • Multiple customers can use the same parking slot simultaneously.
  • Queue events have been updated to the latest format for QueueMetrics compatibility.
  • The maximum voicemail duration can be set per rate plan.
  • Database performance improvements for systems with large numbers of routes.
  • Database performance improvements for systems that heavily use busy lamps (BLF).

Web interface and administration

  • The switch user box can be sorted alphabetically or by most recently used.
  • Transactions can be bulk changed.
  • Bulk changing telephone lines includes password and allowed IP addresses.
  • Each number has a setting to allow everyone in the customer to use it as a callerid.
  • Location callerid can be set to original.
  • Normal users can update the shortcut routing of numbers.
  • Call recordings can be downloaded directly from the call history page.
  • Remotely archived CDRs can have notes attached.
  • People can be imported and exported from/to .csv files.
  • Sounds can be played on the web using a built-in audio player.
  • Editing rate plans shows the effective maximum values inherited from the parent.
  • Call history reports for telephone lines can exclude missed calls from hunt groups, page groups, and queues.
  • Roles can be copied without having to manually re-create their settings.
  • Reports are no longer automatically run when first loading their page, improving database performance.

Billing and payments

  • Invoices can group features by type.
  • If a customer's credit card payment is refused for an invoice, and they then update their credit card details, payment can be automatically retried.

Clients

  • The Windows client has reached version 1.0, and is considered stable.
  • The Android client can handle telephone numbers in other apps.

APIs

  • The old SOAP and numbers APIs have been removed as the JSON API includes their functions.
  • Normal users can control their calls using the JSON API.

System management

  • The system owner can put the system in maintenance mode, where users see a warning message that the system is undergoing maintenance when they log into the web interface. The system owner can optionally lock normal users out of the web interface and JSON API.
  • Encrypted connections to MySQL are supported.
  • Galera cluster is supported.
  • Corosync and pacemaker are used by default for failover in new installations. Existing systems using heartbeat are not affected.
  • System configuration settings can have notes attached.
  • Crontabs are stored in /etc/cron.d for new installations. Existing systems are not affected.