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

• Major re-write of the Android client, with new user interface, notifications for voicemails and faxes, and control of call routing for numbers and telephone lines.
• Optional support for Kamailio 3.1 instead of OpenSIPS. Both will be supported, with OpenSIPS being the default.
• All sound files are shipped in G.722, G.711 μ-law, and G.729.
• Calls to peers can be sent through a proxy, such as the local OpenSIPS.
• Customers are emailed if their credit card payment fails. If configured, customer support is copied on these emails.
• Outbound faxes can be saved and viewed on the web interface.
• Queued SMSs can be viewed on the web interface.
• All passwords can be validated against regular expressions to ensure the desired level of security.
• The actions menus, such as make a call, remember the numbers users entered for the next time they use the same menu.
• The rate plan routing exceptions and classes of service have been combined into a new routes link at the bottom of the edit rate plan page. These are simpler and more powerful, and don't require a routing exception for each sub-route configured on the system.
• The list rate plans and list rate plan routes pages are paginated.
• Each rate plan can control whether inter-customer internal calls are free. There is a new setting for this on the rate plan features page.
• Each rate plan can control whether speed dials are provisioned. There is a new setting for this on the rate plan features page.
• Each rate plan can have a minimum invoice amount. There is a new setting for this on the rate plan fees for features page.
• Viewing all telephone lines in the customer can be controlled separately in the role settings.
• Missed calls to telephones can be viewed on the web and Android client (with notifications), and email notifications of missed calls can be sent.
• Each customer can set a default callerid that is used for new telephone lines (unless overridden), making management of callerids over large numbers of handsets easier.
• Telephone lines have a setting to control the maximum number calls to and from them.
• Many telephone settings can be bulk changed for all telephones in a customer using a new bulk change link at the bottom of the list telephone lines page.
• If a telephone line has multiple registrations, all are displayed on the edit telephone page.
• A new feature prefix type to call a telephone line directly.
• The time and source IP address of the last provisioning request are logged in the database and displayed on the edit telephone page.
• When provisioning multiple lines to one telephone, the suffix can optionally be an absolute position rather than relative.
• If telephone lines or remote access accounts are configured to pass the submitted callerid, this is sent in the telephone line's or remote access account's dial plan.
• Busy lamps (BLF) can optionally be allowed between customers. This is useful for institutional customers who use sub-customers for different departments.
• Hunt groups and page groups can have a delay set between calling each telephone line, and busy lamps can have a random delay, to avoid overwhelming NAT devices with SIP packets.
• Page groups, by default, only allow one concurrent call, and do not ring the original caller. Both of these can be changed by configuration setting.
• The max/minmessage columns in the mailboxes table have been replaced with max/minsecs as Asterisk 1.4 is no longer supported. This prevents harmless warnings on the Asterisk console.
• Patterns for pattern menus can be imported/exported from/to CSV files.
• The active calls report shows system owner users which Asterisk machine each call is on, and allows sorting by this.
• The XML API has an action to get all data the client might be interested in a single request.