This is a list of new features in Enswitch 3.14. It is not exhaustive; some enhancements are too minor to list. A full list of features is also available.
Highlights of 3.14
- A complete re-write of inter-machine messaging, allowing much higher scalability and monitoring of events throughout the cluster.
- Greater control over allowed SIP registrations.
- SIP advice of charge.
- Call recording on demand.
- Experimental WebRTC support.
- Messages between machines in the cluster are sent through a highly scalable and flexible message daemon. This allows any machine in the cluster, and allowed external machines, to monitor events throughout the cluster. This will also allow many new features in future versions.
- The default fax server is changed to SpanDSP, and is enabled by default.
- When using Authorize.net, credit cards are stored on Authorize.net's servers only.
- Inbound calls can be restricted to allowed source IP addresses.
- Telephone lines can be set to automatically detect the source IP address on first registration, then only allow registration from that IP address.
- Customers can be alerted if the IP address a handset registers from changes.
- Handsets can be limited by user agent.
- The audit log can be searched.
Web interface and administration
- The web interface shows whether voicemails have been listened to and whether faxes have been read.
- Users' names can be changed and all their features updated in one action.
- Bulk changing telephone lines allows changing many more fields.
- Telephone lines can be quickly bulk added to hunt groups, page groups, pickup groups, and queues.
- Speed dials can be bulk uploaded.
- Record groups have a report showing all features using that record group.
- The system owner or reseller is notified when a customer deletes a number.
- The system owner can add a file of numbers to the system.
- Rate plans can limit the maximum concurrent calls and destinations for the bulk dialer, conferences, hunt groups, page groups, and queues.
- Rate plan reports can include or exclude taxes.
- WebRTC is supported for outbound calls on an experimental basis.
- External numbers that customers own, such as mobile numbers, can be configured as outbound callerids.
- Customers can choose which inbound group to add ported numbers to.
- Callerid can be selected by feature prefix.
- Numbers and feature codes can set a distinctive ring tone for calls routing through them.
- When a call is picked up, the callerid of the picked up call is shown.
- The recipient hears a beep on SIP transfer.
- The control panel allows calls to be transferred to any number.
- Call recording can be started and stopped on demand using DTMF.
- Call recording can optionally play a regular beep to remind users that the call is being recorded.
- Queue callback can be limited by class of service.
- Different reasons for exiting a queue, such as maximum hold time, maximum queued calls, no agents logged in, or the caller pressing *, can route the call to different places.
- Queue position announcements can be limited to a maximum position.
- The fax header can be set to the customer name, or blank.
- Sound files can be uploaded in .mp3 format.
- Custom handset models can be provisioned.
Call routing and billing
- Advice of charge (AOC) is sent to SIP handsets.
- Call profit margins can be specified as absolute amounts as well as percentages.
- Customers' call limits can be ignored when calling emergency numbers.
- Different Asterisk machines can be assigned different weightings for call routing.
- Calls routed through remote access obey regions.
- Asterisk machines can be completely disabled for a given region.
- Calls can be routed with NAT handling disabled.
- Customers are notified for successful credit card payments.
- The system owner or reseller is notified when a customer's balance is low.
- There are more options controlling the appearance of invoices, and whether zero-cost transactions and calls are shown.
Integration with other systems
- The message daemon (see above) allows external machines to connect via websocket and receive events from all machines in the cluster.
- Cluster events can be sent to an external machine via HTTP.
- Customers can have events related to their calls sent to an external machine via HTTP.
- Queue events can be sent to an external machine via HTTP.
- Kamailio 5.0 is installed on new installations.
- Systemd is fully supported.
- Devuan GNU+Linux is supported.
- Old audit logs, CDRs, invoices, missed calls, statistics, and transactions can be automatically cleaned up.