- Vladimir Toncar (Kerio)
We published Kerio Operator 2.2.0 Beta 3 this morning. The most interesting change in this beta is the Salesforce.com integration that supports click-to-dial from the Salesforce interface and can also search for the remote party's phone number of an active call in Salesforce.com's contacts, accounts, and leads.
This is the complete change log:
Kerio Operator engine
* Added a mini-application for Salesforce.com integration.
+ Added configurable SIP expiry timeouts.
+ Added support for phone firmware updates in the new auto-provisioning system.
+ Added support for setting logo images in the new auto-provisioning system.
+ Automatic provisioning now supports Yealink/Well phones T41P, T42G, T46G.
+ Automatic provisioning now supports Grandstream GXP models 1100, 1105, 1160, 1165, 1400, 1405, 1450, 2100, 2110, 2120, 2124v2, 3140, 3175.
+ Automatic provisioning supports Cisco SPA8000.
+ Upgraded DAHDI drivers to version 126.96.36.199 for improved compatibility with newer Digium cards.
- Fixed the recording of audio messages via the PBX service (default extension 86).
- Fixed the warning about un-commited write transaction.
- Fixed a bug in Asterisk where SIP registration timeout values could be sometimes ignored.
- Other minor bug-fixes.
Kerio Operator administration
+ The screen "Users" now displays information about voice mail usage.
+ Finished the implementation of notifications in the new auto-provisioning system
+ Added option to erase all local voice mail data for a user.
+ Added support for SSL certificates with a password.
- Improvements in the remote storage configuration.
- Unified naming of buttons (always use "Edit..." instead of "Change..." etc.)
- Display "View.." instead of "Edit..." on buttons for auditor-level access.
- Fixed entering of external numbers that start with the "+" sign.
[Updated on: Fri, 18 October 2013 11:14]
Kerio discussion forums are intended for open communication between forum
members and may contain information and material posted by members which may
be useful in learning about Kerio products. The discussion forums are not
intended to provide technical support for any specific product. Any
information implied or expressed in the discussion forums is that of the
posting member. Kerio is in no way responsible for the information posted in
the forums, or its accuracy. Kerio employees may participate in the
discussions, but their postings do not represent an offical position of the
company on any issues raised or discussed. Kerio reserves the right to
monitor and maintain the forums to promote free and accurate exchange of