We continue to improve and expand the feature set available in our cloud PBX platform, and we are excited to announce the release of the phone.systems™ version 2.9. The latest version introduces the following enhancements:
• Company Directory - Internal Contacts in phone.systems™ and my.call.center are now provisioned by the call.center™ application and are automatically updated/synchronized. To achieve this functionality, the following changes have been made to various components:
a) Improved Internal Contact form. Contact numbers and additional Contact information fields have been added to the Internal Contact form.
*Contact numbers will be used when calling a contact from the call.center™ company directory
b) Improved call.center™ integration into phone.systems™. A new call.center™ contact method has been implemented, which is automatically created and assigned to all devices belonging to the contact. The UI for managing devices has also been redesigned.
Devices are now grouped under the call.center™ contact method and separated by their activation status. In addition, it is no longer required to create a dedicated SIP account for each call.center™ device, as this can be replaced with the automatically created call.center™ contact method. Additional SIP accounts can be added to each call.center™ device as needed.
The call.center™ contact method can be used directly with Ring Groups and Queues.
This contact method’s relation to the various services is also displayed in the new call.center™ UI within phone.systems™:
c) The call.center™ softphone will soon be updated to support the phone.systems™ company directory and the new call.center™ contact method.
• CLI Rules - A new feature to override the Source Caller Name and Destination Number has been implemented in the following services / objects:
a) Inbound Trunk;
b) Phone Number object;
c) Ring Group object;
d) Queue object.
This functionality allows flexible Caller Name configurations and may be used to differentiate SIP calls received from phone.systems™. A common use case is the ability to identify from which DID (Phone number) or Queue the call is coming.
• Email contact method verification and status - Email contact methods have been improved to support email verification. All newly added email contact methods will have to be verified by the recipient in order to receive emails from phone.systems™. This will prevent invalid emails from appearing on the system.
Additionally, emails that are sent from phone.systems™ will contain an unsubscribe link so that the email owner may be easily removed from phone.systems™ notifications without contacting their system administrator. The emails can be re-verified if needed, and the current status of that contact method is reflected in the UI.
The following statuses are available:
a) Pending verification;
b) Verification expired;
• Multiple emails for Email Delivery Method – The Email Delivery Method has been improved to support multiple email destinations. This feature allows several email destinations to receive the same notification or call-recording by using a single Email Delivery Method.
In addition to the above-mentioned improvements, a new design for Queue configuration forms and the Settings icons has been implemented. Important Success notifications have been reinstituted, and a Delete form for Tabs has been added to help locate lost objects in the workspace. Performance improvements have been made to enable faster loading of Delivery and Contact methods for large accounts. Also, all emails sent from phone.systems™ will now use the stylized HTML template.
We now have a video on how to configure a call.center™ softphone in phone.systems™, which is available here.
As always, your feedback, comments and questions are welcome at email@example.com.