Historique des versions
- Version 9.0.0.10 Released on 2024/11/28
-
Features
Security Notice
We strongly recommend applying this security patch or updating to STARFACE 9.0.1 (as soon as it is available)!
No action is needed for STARFACE Clouds: All affected clouds have already been patched and updated images are available for new clouds.
Important General Notes
Ensure that you do not use self-signed certificates.
Certificates of the type 'self-signed' are no longer accepted and must be replaced if necessary.
STARFACE 8.0 and above strictly require valid certificates for encrypted telephony (for Snom, Yealink, and Gigaset). The definition of valid certificates depends on the manufacturer.
The certificates of the STARFACE Clouds are verified and valid, so no action is required on your part.
The existing (Asterisk) 'Recording' function has been adjusted as part of the OpenAI integration.
The function has been extended with the new parameter 'GUI OPENAIKEY PASSWORDFIELD'.
All modules using this function must be updated to ensure the module continues to work!
Minimum Requirements
Note that when updating STARFACE to version 9, at least 6 GB of free disk space is required, plus twice the size of the backup to be imported.
During the update to STARFACE 9, the memory for STARFACE Clouds will be increased to 4 GB when done via cloud management.
Update/Migration Path
Systems with STARFACE 7.3 or older cannot be directly updated to STARFACE 9. This affects all types (Appliances, VMs &
- Clouds).
Background:
With STARFACE 8.0, the backup and recovery process was revised and a new method for importing and exporting backups introduced.
Backups from versions STARFACE 7.3 (and older) can only be imported into systems with versions STARFACE 8.0 or 8.1.
With STARFACE 9, only backups from versions STARFACE 8.0 or 8.1 can be imported.
Procedure:
Systems with STARFACE 7.3 (and older) must first update to STARFACE 8.0 or 8.1 to create a backup in the new format.
Only with this backup in the new format can an update from STARFACE 8.0 or 8.1 to STARFACE 9 be performed.
The update from STARFACE 8.0 and above to STARFACE 9 can be installed as a normal update via the web interface as usual, and does not require a new installation.
Please perform updates of STARFACE Clouds directly via cloud management in the partner portal.
Before the Update
We recommend archiving call lists, fax lists, voicemails, and call recordings with the 'STARFACE Archiving' module before the update.
We recommend working with fully qualified numbers in all modules.
Please check before installation if the siptrunk.de profile of your provider has been updated.
With STARFACE 9, potential adjustments in modules are necessary. We recommend checking before an update if a current, 9.0-compatible version is available for the modules used. Consult the module partners for information.
After the Update
Existing Gigaset stations N510 and N720 must be manually adjusted after the STARFACE update. A corresponding guide is available in our Knowledge Base.
Please update your STARFACE Apps to the latest version, especially the new STARFACE App for Windows. Older versions of the STARFACE Apps (Windows, MacOS, Android &
- iOS) are not fully compatible with STARFACE 8.1.
If you only use a STARFACE Connect line, ensure that you use the highest routing priority in the settings.
Please check already installed modules for newer versions and update them after the update.
Bugfixes
This patch closes a security vulnerability in the STARFACE system.
Note:
We strongly recommend applying this security patch or updating to STARFACE 9.0.1 (as soon as it is available)!
To protect you and all other customers who have not yet applied the update or hotfix, we are currently unable to disclose further details regarding the specific contents of the security vulnerability.
- Version 8.1.3.3 Released on 2024/11/28
-
Features
Security Notice
We strongly recommend applying this security patch or updating to STARFACE 9.0.1 (as soon as it is available)!
No action is needed for STARFACE Clouds: All affected clouds have already been patched and updated images are available for new clouds.
IMPORTANT GENERAL NOTES
Please ensure that you use only valid certificates for STARFACE 8.0 and higher as self-signed certificates are not accepted. This is particularly important for encrypted telephony with Snom, Yealink, and Gigaset. For Snom, follow the Mozilla standards.
'Let's Encrypt' certificates are considered valid. The verification and exchange of certificates should be done before activating telephone encryption, but can be done before or after the update.
For STARFACE Clouds, no action is needed as their certificates are already verified and valid.
Update/Migration Path
The update from STARFACE 7.0 and higher to STARFACE 8.1 can be installed as a normal update via the web interface as usual and does not require a new installation.
Updates for STARFACE Clouds should be done directly through Cloud Management in the partner portal. This allows you to update directly from STARFACE 6 to STARFACE 8.1.
Virtualized STARFACE installations must be manually reinstalled. Details can be found in our Knowledge Base.
Backups from older versions (e.g., STARFACE 6.7) can also be imported into STARFACE 8.1 as usual.
BEFORE the Update
We recommend archiving the call lists, fax lists, voicemails, and call recordings with the 'STARFACE Archiving' module before the update.
We recommend working with fully qualified phone numbers in all modules.
Please check before installation whether the siptrunk.de-Profil profile of your provider has been updated.
With STARFACE 8.1, potential adjustments in modules may be necessary. We recommend checking whether there is a current, 8.1-compatible version available for the modules used before an update. Please consult the respective module partners for this.
AFTER the Update
Existing Gigaset stations N510 and N720 must be manually adjusted after the STARFACE update. A corresponding guide is available in our Knowledge Base.
Please update your STARFACE apps to the latest version, especially the new STARFACE app for Windows. Older versions of the STARFACE apps (Windows, MacOS, Android &
- iOS) are not fully compatible with STARFACE 8.1
If you use exclusively a STARFACE Connect line, ensure in the settings that you are using the highest routing priority.
Please check already installed modules for newer versions and update them after the update.
Bugfixes
This patch closes a security vulnerability in the STARFACE system.
Note:
We strongly recommend applying this security patch or updating to STARFACE 9.0.1 (as soon as it is available)!
To protect you and all other customers who have not yet applied the update or hotfix, we are currently unable to disclose further details regarding the specific contents of the security vulnerability.
- Version 8.0.0.15 Released on 2024/11/28
-
Features
Security Notice
We strongly recommend applying this security patch or updating to STARFACE 9.0.1 (as soon as it is available)!
No action is needed for STARFACE Clouds: All affected clouds have already been patched and updated images are available for new clouds.
IMPORTANT GENERAL NOTES
Lines without authentication AND whose line names contain a space do not establish calls, e.g. when operating an SBC.
Please make sure that you do not use self-signed certificates. Certificates of type 'self-signed' are no longer accepted and may have to be replaced. STARFACE 8 requires valid certificates for encrypted telephony (for Snom, Yealink, and Gigaset). The definition of valid certificates depends on the manufacturer
- for Snom you can use Mozilla as a guide, for example. Certificates from 'Let's Encrypt' are valid as far as known.
Testing and replacement can be done before or after the update, but definitely before enabling phone encryption. The certificates of the STARFACE Clouds are checked and valid, there is no need for action on your part.
The previous STARFACE App for Windows version 7.3 is still compatible with STARFACE 8.
The new app for Windows (version 8.x) requires STARFACE 8.
Minimum RequirementsPlease note that when updating STARFACE to version 8, the free disk space must be at least 6 GB plus twice the size of the backup to be imported.
Virtualized STARFACE installations require at least 2 GB of RAM.
Update/Migration PathThe update from STARFACE 7.0 and higher to STARFACE 8 can be installed as usual as a normal update via the web interface and does not require a new installation.
Please update STARFACE Clouds directly via the Cloud Management in the Partner Portal. This also allows you to update directly from STARFACE 6 to STARFACE 8.
The update from STARFACE 6 to STARFACE 8 is not possible directly via the admin area: The migration path leads, as before, via STARFACE 7, for which we offer a special module that handles the update procedure for appliances.
Virtualized STARFACE installations have to be reinstalled manually. Details can be found in our Knowledge Base.
Backups from older versions (e.g. STARFACE 6.7) can also be imported into STARFACE 8 as usual.
BEFORE the updateWe recommend archiving the call lists, fax lists, voicemails and call recordings with the module 'STARFACE Archiving' before the update.
We recommend working with fully qualified call numbers in all modules.
Before installation, please check if the siptrunk.de profile of your provider has been updated.
With STARFACE 8, potential adjustments are required for modules. Before updating, we recommend to check whether a current, 8.0-compatible version is available for the modules used. Please contact the respective module partner for more information.
AFTER the updatePlease update your STARFACE Apps to the latest version, this is especially true for the new STARFACE App for Windows. Older versions of the STARFACE Apps (Windows, MacOS, Android &
- iOS) are not fully compatible with STARFACE 8.
If you exclusively use a STARFACE Connect line, make sure in the settings that you use the highest routing priority.
Please check already installed modules for newer versions and update them after the update.
Activated encryptions of Snom phones are automatically deactivated by an update to STARFACE 8 and have to be reset manually in the admin area afterwards.
Bugfixes
This patch closes a security vulnerability in the STARFACE system.
Note:
We strongly recommend applying this security patch or updating to STARFACE 9.0.1 (as soon as it is available)!
To protect you and all other customers who have not yet applied the update or hotfix, we are currently unable to disclose further details regarding the specific contents of the security vulnerability.
- Version 7.3.1.6 Released on 2024/11/28
-
Features
Security Notice
We strongly recommend applying this security patch or updating to STARFACE 9.0.1 (as soon as it is available)!
No action is needed for STARFACE Clouds: All affected clouds have already been patched and updated images are available for new clouds.
Important general notes
Please note that when updating STARFACE to version 7.3, the free disk space is at least 6 GB, plus twice the size of the backup to be imported.
Virtualized STARFACE installations require at least 2 GB of RAM.
The update from STARFACE 6 to STARFACE 7 is not available via a normal update, but requires a special module that handles the update procedure for appliances. Virtualized STARFACE installations have to be reinstalled manually. Details can be found in our Knowledge Base.
The update from STARFACE 7.0 and higher to STARFACE 7.3 can be installed as usual as a normal update via the web interface and does not require a new installation.
Older versions of the STARFACE Apps (Windows, MacOS, Android &
- iOS) are not fully compatible with STARFACE 7.3. Please update your STARFACE Apps to the respective latest version.
We recommend to archive the call lists, fax lists, voicemails and call recordings with the module 'STARFACE Archiving' before the update and to work with fully qualified phone numbers in all modules.
If you use a STARFACE Connect line, please make sure in your settings that you use the highest routing priority.
Before installation, please check if the siptrunk.de profile of your provider has been updated.
With STARFACE 7.3 mandatory adjustments are required for modules. Before updating, we recommend to check whether a current, 7.3-compatible version is available for the modules used. Please contact your module partner for more information.
Important notes on modules
New logging library (Log4j 2.18.0): Custom functions from .class and .jar files must be adapted to the new logging library ('NoSuchMethodError').
Raised ASM level: For loading Java 11 compiled classes.
Better logging in classloader: stacktrace with description why .class and .jar's could not be loaded.
'Tiptel Soundfile' is now called 'Yealink Soundfile': rename the resource, but not the type in the function editor.
Discontinuation: The module 'group specific ringtones' is no longer supported with STARFACE 7.3.0. As an alternative, we recommend the free ringtones module of STARFACE, either in the free variant or the paid one, with extended support for phones.
Bugfixes
This patch closes a security vulnerability in the STARFACE system.
Note:
We strongly recommend applying this security patch or updating to STARFACE 9.0.1 (as soon as it is available)!
To protect you and all other customers who have not yet applied the update or hotfix, we are currently unable to disclose further details regarding the specific contents of the security vulnerability.
- Version 9.0.0.9 Released on 2024/10/29
-
Features
Important General Notes
Ensure that you do not use self-signed certificates.
Certificates of the type 'self-signed' are no longer accepted and must be replaced if necessary.
STARFACE 8.0 and above strictly require valid certificates for encrypted telephony (for Snom, Yealink, and Gigaset). The definition of valid certificates depends on the manufacturer.
The certificates of the STARFACE Clouds are verified and valid, so no action is required on your part.
The existing (Asterisk) 'Recording' function has been adjusted as part of the OpenAI integration.
The function has been extended with the new parameter 'GUI OPENAIKEY PASSWORDFIELD'.
All modules using this function must be updated to ensure the module continues to work!
Minimum Requirements
Note that when updating STARFACE to version 9, at least 6 GB of free disk space is required, plus twice the size of the backup to be imported.
During the update to STARFACE 9, the memory for STARFACE Clouds will be increased to 4 GB when done via cloud management.
Update/Migration Path
Systems with STARFACE 7.3 or older cannot be directly updated to STARFACE 9. This affects all types (Appliances, VMs &
- Clouds).
Background:
With STARFACE 8.0, the backup and recovery process was revised and a new method for importing and exporting backups introduced.
Backups from versions STARFACE 7.3 (and older) can only be imported into systems with versions STARFACE 8.0 or 8.1.
With STARFACE 9, only backups from versions STARFACE 8.0 or 8.1 can be imported.
Procedure:
Systems with STARFACE 7.3 (and older) must first update to STARFACE 8.0 or 8.1 to create a backup in the new format.
Only with this backup in the new format can an update from STARFACE 8.0 or 8.1 to STARFACE 9 be performed.
The update from STARFACE 8.0 and above to STARFACE 9 can be installed as a normal update via the web interface as usual, and does not require a new installation.
Please perform updates of STARFACE Clouds directly via cloud management in the partner portal.
Before the Update
We recommend archiving call lists, fax lists, voicemails, and call recordings with the 'STARFACE Archiving' module before the update.
We recommend working with fully qualified numbers in all modules.
Please check before installation if the siptrunk.de profile of your provider has been updated.
With STARFACE 9, potential adjustments in modules are necessary. We recommend checking before an update if a current, 9.0-compatible version is available for the modules used. Consult the module partners for information.
After the Update
Existing Gigaset stations N510 and N720 must be manually adjusted after the STARFACE update. A corresponding guide is available in our Knowledge Base.
Please update your STARFACE Apps to the latest version, especially the new STARFACE App for Windows. Older versions of the STARFACE Apps (Windows, MacOS, Android &
- iOS) are not fully compatible with STARFACE 8.1.
If you only use a STARFACE Connect line, ensure that you use the highest routing priority in the settings.
Please check already installed modules for newer versions and update them after the update.
Features &
- Improvements
New Outlook Add-In for the New MS Outlook
A new Outlook Add-In has been developed for Microsoft's web-based Outlook.
A new UI in STARFACE is available for setting up the Add-In under 'Server >
- App/Outlook Add-In'.
The new Add-In is available via the Microsoft Store.
The existing Outlook Connector for the ?old? native MS Outlook continues to work. No adjustments are required.
New Admin Login (OAuth-based)
Admins must now log in separately in the Admin area.
The admin login has been technically separated from the web client to switch to OAuth.
External identity providers such as Microsoft Azure AD or Google Identity can be used for admin login.
Single Sign-On and Two-Factor Authentication can be configured for admins.
Standard STARFACE credentials remain valid for both areas.
Configuration is done via the new Admin UI under 'Advanced Settings >
- OAuth-Login'.
Microsoft 365 Support via OAuth / Mail Server with OAuth
Microsoft Mail Services can now integrate via OAuth authentication.
Currently, this is limited to the Microsoft email provider.
Setup is done through the new UI under 'Server >
- Mail Server (with OAuth)'.
The previous connection method remains available with STARFACE 9.
Microsoft Status
Status synchronization between STARFACE and 'Microsoft Presence' can now be set up under 'Advanced Settings >
- Microsoft Presence'.
The status synchronization is currently fixed and not adjustable.
Archiving
The logic of the STARFACE module 'Archiving' has been fully integrated into the PBX.
It can now be configured in the admin area under 'Server >
- Archiving.'
After the update to STARFACE 9:
an existing module configuration for archiving remains active.
the new native configuration remains disabled by default.
There is no automatic migration from a module configuration to the new native configuration.
A change must be manually performed by an administrator of the system.
CSTA Integration
Allows setting up a dedicated TAPI service provider on a central Windows server for integrating third-party applications.
Existing first-party integrations via the client TAPI are not affected.
CSTA driver integration can be done via the Admin UI under 'Advanced Settings >
- CSTA'.
A free CSTA driver is offered as a separate download package in the Knowledge Base.
Phone Pin
STARFACE 9 allows requiring an additional four-digit PIN when logging into a desk phone.
By default, the use of the new PIN is disabled.
Activation of the PIN can be done under 'Phones >
- Security'.
Modules with their own phone PIN logic may cause problems.
Multi-login still allows multiple simultaneous logins on one device but must be activated by the admin for each device in advanced settings.
Users can be informed about the new PIN if the provided module 'STARFACE Telephone PIN Distributor' is activated by the administrator.
XML interfaces have been revised as part of mitigating a security risk. Parameters and validation have been adjusted.
This affects all currently supported STARFACE phones, as well as legacy phones.
AI Module Functions
New module functions for communication with 'OpenAI' AI are now available and are provided by two means:
Local 'Whisper'
Hosted by STARFACE in Europe.
Exclusively available for STARFACE cloud customers.
Functions: Speech-to-Text, Text-to-Speech.
OpenAI
Direct connection to the OpenAI interface.
Data is processed on OpenAI's US servers.
Requires its own OpenAI API key.
Functions: Speech-to-Text, Text-to-Speech, Chat.
Let's Encrypt
STARFACE 8.1's certificate management has been expanded to include the ACME standard.
Server certificates from 'Let's Encrypt' can be requested and integrated directly via the UI 'Server >
- ACME'.
Limitation: This service is only available for STARFACE Appliances and VMs, not for STARFACE Clouds.
Administrators must agree that future changes to Let's Encrypt terms will be accepted automatically.
A system restart is required after the issuance of Let's Encrypt certificates, even after the initial setup.
Firmware Update Notification
From STARFACE 9, administrators receive an email when new firmware is available on the STARFACE Firmware Server.
Receipt of such emails can be disabled in the UI 'Phones >
- Firmwares'.
Mitel 6920w
The Mitel 6920w desk phone can now be used with STARFACE.
Supported features: One-Touch-Provisioning, Call Handling.
Security Updates
Critical: CWE-74 - Apache Derby Databases (CVE-2022-46337)
Critical: 186528 - AlmaLinux 8: Kernel (ALSA-2023:7549)
Critical: 186527 - AlmaLinux 8: kpatch-Patch (ALSA-2023:7554)
Critical: 188014 - AlmaLinux 8: Pixman (ALSA-2024:0131)
Critical: 186293 - AlmaLinux 8: Samba (ALSA-2023:7467)
High: 189912 - AlmaLinux 8: GnuTLS (ALSA-2024:0627)
High: 188010 - AlmaLinux 8: libxml2 (ALSA-2024:0119)
High: 191112 - AlmaLinux 8: PostgreSQL:10 (ALSA-2024:0956)
High: 189114 - AlmaLinux 8: SQLite (ALSA-2024:0253)
High: 191110 - AlmaLinux 8: Unbound (ALSA-2024:0965)
Low: CWE-73 - AlmaLinux 8: curl (CVE-2023-38546)
Maintenance
PostgreSQL updated to version 15.
Asterisk updated to version 20.6.0.
AlmaLinux updated to version 8.10.
Java updated to version 21, which may impact modules with Java code.
Tomcat updated to version 9.0.82.
Prometheus for local monitoring updated to version 2.53.0.
Module System
Modules such as user or group call blocks can no longer interrupt or block outgoing emergency calls.
Call handling events can be used for modules.
Devices
Yealink CP920: Provisioning encryption has been removed. Encryption via Yealink can still be activated.
Manually triggered firmware update processes can now be executed independently of the global auto-update option.
Gigaset N-Series: The setting for GAP handsets has been removed and is enabled by default with firmware version v2.57.
Yealink phones T58W, VP59, CP960, and CP965 have new icons for the STARFACE phone menu.
SNOM phones D385, D717, D735, and D785 have new icons for the STARFACE phone menu.
System
A warning has been added to the address book import process indicating that the import is conducted without validation.
Bugfixes
Devices/Firmware Server
The 'phoneID' in metadata for firmware downloads has been fixed and downloads are now more reliable. [Call#7928670] [Call#7933871] [Call#7933535] [Call#7927702] [Call#7936671] [Call#7942235] [Call#7944245] [Call#7946256] [Call#7937643] [Call#7939346] [Call#7947637]
User information of participants with analog phones is now displayed again. [Call#7913386] [Call#7912961] [Call#7912849] [Call#7923599] [Call#7927584] [Call#7928310] [Call#7932973] [Call#7939892] [Call#7916360] [Call#7916605][Call#7915486] [Call#7920339] [Call#7921159] [Call#7920929] [Call#7925299] [Call#7925878] [Call#7925893] [Call#7926275] [Call#7927401] [Call#7930400]
Auto-provisioning of SNOM desk phones using firmware version 10.1.169.13 has been adjusted to reduce the likelihood of routers autonomously closing open SIP connections. [Call#7915245] [Call#7930314] [Call#7929595] [Call#7932281] [Call#7933304] [Call#7933305] [Call#7933306] [Call#7933307] [Call#7933308] [Call#7933261]
Access to voicemail boxes in the STARFACE phone menu works correctly even after opening an empty voicemail box.
Keys
More than 20 favorites can now be created in the function key editor for the STARFACE App for Windows. [Call#7917787] [Call#7918450] [Call#7917304] [Call#7925332] [Call#7929039] [Call#7935402] [Call#7937004] [Call#7953221] [Call#7869269] [Call#7911692] [Call#7947245] [Call#7928868]
All unsaved changes are retained when a new key is inserted between existing ones.
Backup and Restore
Backups containing files with umlauts are now restored correctly. [Call#7861972] [Call#7301619]
Latest (TLS) encryption algorithms, such as 'Kex,' are supported for backup storage on SFTPs. [Call#7948167] [Call#7948956]
Selection options during backup import are correctly captured and applied again.
iQueue/Groups
Group redirection on timeout now functions as documented. [Call#7866304] [Call#7873297] [Call#7917966]
Calls blind transferred to another iQueue group are handled correctly when the agent of the second group does not answer within the time limit.
Module Functions
Module functions IsResolvedCall and CallPhoneNumber now provide correct values. [Call#7356710] [Call#7649608] [Call#7787439]
Backend
Timer handling has been revised. Scheduled events (e.g., conferences) are executed correctly after a time change, such as daylight saving time changes. [Call#1019750] [Call#7496692]
WEB UI
Applying a user template with an active and empty function key configuration now correctly clears the function keys.
The key configuration UI in user templates has been aligned with user key configuration.
Call Manager/Call List
When a group call is redirected to another user and the call is accepted, the 'Accepted by' field is filled with the accepting user.
Call Handling
A Call2Go no longer rings on the desk phone if the other participant hangs up during an active call.
Address Book and LDAP
Progress display during contact import to the address book is functioning again.
Administration
Translations for notifications when assigning licenses to user accounts have been added and corrected.
The '*' symbol can now be used as a wildcard of any length in the MAC address filter.
The 'messenger' constant name in the 'Address Book > Layout' menu was corrected.
The preflight check for admin-login OAuth configurations now also checks the issuer.
Phone Numbers and Providers
If a location in the emergency configuration is deleted, the associated emergency phone numbers are correctly removed from the database. [Call#7864164]
- Version 8.1.3.2 Released on 2024/07/22
-
Features
- Support of the new appliance Advanced V7
- This version does not include any new features or bug fixes
- No changes have been made to the user interface
- Version 8.1.3.1 Released on 2024/05/27
-
Features
IMPORTANT GENERAL NOTES
Please ensure that you use only valid certificates for STARFACE 8.0 and higher as self-signed certificates are not accepted. This is particularly important for encrypted telephony with Snom, Yealink, and Gigaset. For Snom, follow the Mozilla standards.
'Let's Encrypt' certificates are considered valid. The verification and exchange of certificates should be done before activating telephone encryption, but can be done before or after the update.
For STARFACE Clouds, no action is needed as their certificates are already verified and valid.
Update/Migration Path
- The update from STARFACE 7.0 and higher to STARFACE 8.1 can be installed as a normal update via the web interface as usual and does not require a new installation.
- Updates for STARFACE Clouds should be done directly through Cloud Management in the partner portal. This allows you to update directly from STARFACE 6 to STARFACE 8.1.
- Virtualized STARFACE installations must be manually reinstalled. Details can be found in our Knowledge Base.
- Backups from older versions (e.g., STARFACE 6.7) can also be imported into STARFACE 8.1 as usual.
BEFORE the Update
- We recommend archiving the call lists, fax lists, voicemails, and call recordings with the 'STARFACE Archiving' module before the update.
- We recommend working with fully qualified phone numbers in all modules.
- Please check before installation whether the siptrunk.de-Profil profile of your provider has been updated.
- With STARFACE 8.1, potential adjustments in modules may be necessary. We recommend checking whether there is a current, 8.1-compatible version available for the modules used before an update. Please consult the respective module partners for this.
AFTER the Update
- Existing Gigaset stations N510 and N720 must be manually adjusted after the STARFACE update. A corresponding guide is available in our Knowledge Base.
- Please update your STARFACE apps to the latest version, especially the new STARFACE app for Windows. Older versions of the STARFACE apps (Windows, MacOS, Android & iOS) are not fully compatible with STARFACE 8.1
- If you use exclusively a STARFACE Connect line, ensure in the settings that you are using the highest routing priority.
- Please check already installed modules for newer versions and update them after the update.
Bugfixes
- You can again upload and change audio files in the .wav format through modules.[Forum]
- Version 8.1.3.0 Released on 2024/05/22
-
Features
IMPORTANT GENERAL NOTES
Please ensure that you use only valid certificates for STARFACE 8.0 and higher as self-signed certificates are not accepted. This is particularly important for encrypted telephony with Snom, Yealink, and Gigaset. For Snom, follow the Mozilla standards.
'Let's Encrypt' certificates are considered valid. The verification and exchange of certificates should be done before activating telephone encryption, but can be done before or after the update.
For STARFACE Clouds, no action is needed as their certificates are already verified and valid.
Update/Migration Path
- The update from STARFACE 7.0 and higher to STARFACE 8.1 can be installed as a normal update via the web interface as usual and does not require a new installation.
- Updates for STARFACE Clouds should be done directly through Cloud Management in the partner portal. This allows you to update directly from STARFACE 6 to STARFACE 8.1.
- Virtualized STARFACE installations must be manually reinstalled. Details can be found in our Knowledge Base.
- Backups from older versions (e.g., STARFACE 6.7) can also be imported into STARFACE 8.1 as usual.
BEFORE the Update
- We recommend archiving the call lists, fax lists, voicemails, and call recordings with the 'STARFACE Archiving' module before the update.
- We recommend working with fully qualified phone numbers in all modules.
- Please check before installation whether the siptrunk.de-Profil profile of your provider has been updated.
- With STARFACE 8.1, potential adjustments in modules may be necessary. We recommend checking whether there is a current, 8.1-compatible version available for the modules used before an update. Please consult the respective module partners for this.
AFTER the Update
- Existing Gigaset stations N510 and N720 must be manually adjusted after the STARFACE update. A corresponding guide is available in our Knowledge Base.
- Please update your STARFACE apps to the latest version, especially the new STARFACE app for Windows. Older versions of the STARFACE apps (Windows, MacOS, Android & iOS) are not fully compatible with STARFACE 8.1
- If you use exclusively a STARFACE Connect line, ensure in the settings that you are using the highest routing priority.
- Please check already installed modules for newer versions and update them after the update.
Features & Improvements
- Devices: For users of the Gigaset R700H Protect handset, the alarm feature via DTMF inputs is now supported on the Gigaset N670 and N870 stations.
- Module Designer: The function editor's component library has been expanded with a search field to enhance usability.
Bugfixes
Administration:
- Initial configuration can now be completed successfully even without a connection to the license server.
- Configuration -> Server: The timezone dropdown is adapted to the selected language.
- Phones: Firmware management is now usable even when HTTP is disabled.
- Function Keys: The "Redirect Single Number" button works even when multiple users use it for the same group.
- IFMC: A call initiated via IFMC can be picked up.
- Address Book: Speed dial buttons are saved even if fields 3 and 4 are empty.
- System Link: Absent or busy users are now redirected to the correct drop point.
- Call List: The correct duration of a call is now displayed in the call list when a call is held via the web interface for an inquiry.
- Firmware scheduling errors corrected: The next scheduled time for checking and downloading tasks is now correctly displayed in the local time zone.
- Firmware Server: Scheduling regular tasks such as checking, updating, and downloading firmware can now be more precisely controlled. These tasks are now configurable to reschedule themselves for the next planned time.
- Group Login: The "UserAssignmentsSettingsChangedEvent" is triggered with every user-initiated login or logout from a group.
- Proxy Server Settings: Settings for the proxy server are now consistently applied to outbound web connections.
- Call Handling: The external number of an iQueue is now displayed in the CalledID field for external calls.
- Logged out users are displayed as Not Available during the recording of a voicemail message.
- A UCI call is created when a module initiates a call without a user as the calling party.
- User Template: The error code UUID is no longer shown in error messages related to user templates.
- User Login: User login fails with an error message if permissions are not granted.
- Hold Music: The filter for preselecting .wav files has been improved.
- Devices
- Phones of the SNOM D8 series now use the correct language setting for the date.
- The Yealink T57W now features a keyboard with German layout.
- The LEDs of the audio buttons on SNOM phones D712, D715, D717, D725, D735, D785, D862, and D865 are functional again.
- TAPI: The external number of the IQueue is correctly transmitted in the CalledID field.
- .wav files cannot be uploaded through modules > Know Issue Details
- Version 8.1.2.2 Released on 2024/02/20
-
Features
IMPORTANT GENERAL NOTES
Please ensure that you use only valid certificates for STARFACE 8.0 and higher as self-signed certificates are not accepted. This is particularly important for encrypted telephony with Snom, Yealink, and Gigaset. For Snom, follow the Mozilla standards.
'Let's Encrypt' certificates are considered valid. The verification and exchange of certificates should be done before activating telephone encryption, but can be done before or after the update.
For STARFACE Clouds, no action is needed as their certificates are already verified and valid.
Update/Migration Path
- The update from STARFACE 7.0 and higher to STARFACE 8.1 can be installed as a normal update via the web interface as usual and does not require a new installation.
- Updates for STARFACE Clouds should be done directly through Cloud Management in the partner portal. This allows you to update directly from STARFACE 6 to STARFACE 8.1.
- Virtualized STARFACE installations must be manually reinstalled. Details can be found in our Knowledge Base.
- Backups from older versions (e.g., STARFACE 6.7) can also be imported into STARFACE 8.1 as usual.
BEFORE the Update
- We recommend archiving the call lists, fax lists, voicemails, and call recordings with the 'STARFACE Archiving' module before the update.
- We recommend working with fully qualified phone numbers in all modules.
- Please check before installation whether the siptrunk.de-Profil profile of your provider has been updated.
- With STARFACE 8.1, potential adjustments in modules may be necessary. We recommend checking whether there is a current, 8.1-compatible version available for the modules used before an update. Please consult the respective module partners for this.
AFTER the Update
- Existing Gigaset stations N510 and N720 must be manually adjusted after the STARFACE update. A corresponding guide is available in our Knowledge Base.
- Please update your STARFACE apps to the latest version, especially the new STARFACE app for Windows. Older versions of the STARFACE apps (Windows, MacOS, Android & iOS) are not fully compatible with STARFACE 8.1
- If you use exclusively a STARFACE Connect line, ensure in the settings that you are using the highest routing priority.
- Please check already installed modules for newer versions and update them after the update.
Features & Improvements
Devices
- The DECT base station SNOM M400 is supported as a single-cell system.
- For this device, the firmware version 670B202 is available and is delivered directly with the update.
- Similar to the M900, management via the firmware server is currently not possible.
- Phones from the SNOM D8 series now have a dial button in their phone menu, which allows direct callback from the call lists.
- SNOM: From now on, the missed calls counter resets as soon as you have viewed them in the 'Missed Calls' menu.
- The admin passwords of Gigaset N610, N670, and N870 are now regularly checked.
- The phone SNOM D120 now fully supports the languages German and Dutch via provisioning.
Administration
- In the administration area under 'Phones > Firmwares', the time zone of the telephone system for the timestamps is now displayed.
- In the administration area under 'Groups', the ringing strategy was corrected from 'IQueue' to 'iQueue' in the overview.
Logging
- Logging in the administration area 'Server > Log files > Address book' is now easier to read.
Technology
- Update of the AlmaLinux 8.8 packages
- Update of Asterisk to version 20.5.2
- Update of Tomcat to version 9.0.85
Changes
- The video codec H264 is no longer set as the standard for the STARFACE app for Windows.
- The video codec H264 is removed by this update for all set up STARFACE apps for Windows.
- The codec can be added again via the administration 'Phones' if needed.
- The codec is no longer used by the STARFACE app for Windows from version 8.0 onwards.
- The active codec caused audio problems with the softphone.[Call#7577141] [Call#7567646] [Call#7688975] [Call#7676058] [Call#7642385] [Call#7656620] [Call#7672247]
- In the administration area under 'User > Keys', it is no longer possible to arrange the columns via drag-and-drop. However, moving individual keys between columns remains possible.
Bugfixes
- Provider issues, such as problems with line registration, call transmission, the use of various codecs with some SIPTRUNKS (Connect, Telekom, ecotel, M-Net, Telemaxx) have been fixed.[Call#7914225] [Call#7914523] [Call#7915903] [Call#7917969] [Call#7919928] [Call#7920259] [Call#7925752] [Call#7893551] [Call#7890455] [Call#7913557] [Call#7915183] [Call#7916604] [Call#7918607] [Call#7919636] [Call#7919982] [Call#7919693] [Call#7919602] [Call#7920512] [Call#7919676] [Call#7911256] [Call#7919171] [Call#7919747] [Call#7921305] [Call#7908538] [Call#7904507] [Call#7909135] [Call#7710418] [Call#7912593] [Call#7913311] [Call#7912590] [Call#7912736] [Call#7911997] [Call#7913861] [Call#7913167] [Call#7914183] [Call#7914181] [Call#7914135] [Call#7914231] [Call#7916904] [Call#7917703] [Call#7254069] [Call#7252703] [Call#7156067] [Call#7291700] [Call#7331617] [Call#7812279] [Call#7812485] [Call#7871494]
- When using a French provider, French emergency numbers are reliably dialed and connected.
- The call duration in the call list is now correctly displayed for spontaneous conferences and calls that were held. [Call#7900107] [Call#7561403] [Call#7864636] [Call#7874121]
- When a call is started via iFMC, the caller can be heard again.[Forum] [Call#7909795] [Call#7786073]
- The matching of existing users with Active Directory when activating AD works smoothly.
- Occasionally, an error occurred when restoring cloud services, which meant that the connection did not work again until a restart. This problem has been successfully fixed.
- Mail notifications are now reliably sent to the administrator as soon as phones with default passwords are active. Furthermore, corresponding notices are displayed again in the system status.
- The number of the B-party after a diversion (external) is now signaled in the SIP header in the fields 'PAI' (P-Asserted-Identity) and 'Diversion'.[Call#7785256]
- Phones of the SNOM D8 series now switch to speaker mode by themselves when receiving calls if the group ringing strategy 'Broadcast' is used.
- Button changes via the WebUI are now rolled out only to the selected choice of phones when saving. Previously, the WebUI ignored the selection and the buttons were rolled out to all phones of the user.
The complete list of known issues can be found in our Support Forum.
- Version 8.1.1.1 Released on 2023/12/18
-
Features
- IMPORTANT GENERAL NOTES
- Please ensure that you do not use any self-signed certificates. 'Self-signed' certificates are no longer accepted and must be replaced if necessary. STARFACE 8.0 and higher strictly require valid certificates for encrypted telephony (for Snom, Yealink, and Gigaset). The definition of valid certificates depends on the manufacturer
- for Snom, for example, you can refer to Mozilla standards
- Certificates from 'Let's Encrypt' are known to be valid, for instance. Verification and replacement can be carried out before or after the update, but definitely before activating telephony encryption. The certificates of STARFACE Clouds have been checked and are valid
- there is no action required on your part.
Update/Migration Path
- The update from STARFACE 7.0 and higher to STARFACE 8.1 can be installed as a normal update via the web interface as usual, and does not require a reinstallation.
- Please carry out updates for STARFACE Clouds directly via the Cloud Management in the Partner Portal. This allows you to update directly from STARFACE 6 to STARFACE 8.1.
- The update from STARFACE 6 to STARFACE 8 is not directly possible via the Admin area: The migration path leads, as before, via STARFACE 7, for which we offer a special module that takes over the update procedure for appliances.
- Virtualized STARFACE installations must be manually reinstalled. Details can be found in our Knowledge Base.
- Backups from older versions (e.g., STARFACE 6.7) can also be imported into STARFACE 8.1 as usual.
BEFORE the Update
- We recommend archiving call lists, fax lists, voicemails, and call recordings with the 'STARFACE Archiving' module before the update.
- We recommend working with fully qualified phone numbers in all modules.
- Please check before installation whether the siptrunk.de profile of your provider has been updated.
- Potential adjustments in modules may be necessary with STARFACE 8.1. We recommend checking whether there is a current, 8.1-compatible version available for the modules used before an update. Please consult the respective module partner for this.
AFTER the Update
- Existing Gigaset stations N510 and N720 must be manually adjusted after the STARFACE update. A corresponding guide is available in our Knowledge Base.
- Please update your STARFACE apps to the latest respective version, especially the new STARFACE App for Windows. Older versions of the STARFACE Apps (Windows, MacOS, Android & iOS) are not fully compatible with STARFACE 8.
- If you use exclusively a STARFACE Connect line, make sure in the settings that you are using the highest routing priority.
- Please check already installed modules for newer versions and update them after the update.
- Activated encryptions of Snom phones will be automatically disabled by an update to STARFACE 8 and must be manually reset in the Admin area afterwards.
Security Patches
- Update of the ActiveMQ library to address a security vulnerability (CVE-2023-46604)
- This vulnerability is relevant for configurations with an active system network
- Port 3090 (TCP/UDP) can be reactivated with this patch (does not happen automatically)
- Update of the glibc packages that address CVE-2023-4911 aka Looney Tunables.
- The affected library is also present in the Linux versions we have been using since STARFACE 7.3.
- As a measure to secure your systems, we strongly recommend either updating STARFACE 7.3 and 8.0 to STARFACE 8.1 or installing the corresponding security updates for 7.3 or 8.0.
- Further information on this topic can be found in the News in the Partner Portal
User Templates
- From now on, up to 200 buttons per user template can be stored
- The successful saving and applying of changes is now also visually confirmed
- The Gigaset station N610 is now supported
- SNOM M900: Update to version 650B204
- Introduction of two new user profiles (User + Engineer) for the SNOM web interface
- In the 'firmwares' log, log entries will now use the phone type name instead of the phone type ID
- Update of Asterisk to version 20.5.0
- The login error message in case of connection problems to an Active Directory has been optimized
- New module function: RecordAnnouncementLanguage
- This function allows setting the language of an announcement for a recording
- In the 'Groups' overview, the ringing strategy is now also displayed
- Some text adjustments have been made in the admin interface
Bugfixes
- Devices
- All Gigaset handsets can now be used again for outgoing calls via STARFACE Apps. [Call#7864401] [Call#7865010] [Call#7864846] [Call#7869242] [Call#7871481] [Call#7861372] [Call#7833863] [Call#7839361] [Call#7847161] [Call#7830968] [Call#7848368] [Call#7844315] [Call#7853922] [Call#7854062] [Call#7856142] [Call#7837662] [Call#7830993] [Call#7870912] [Call#7861372] [Call#7866076] [Call#7866269] [Call#7866699] [Call#7866822] [Call#7867108] [Call#7867257] [Call#7867428] [Call#7868712] [Call#7869275] [Call#7869395] [Call#7870957] [Call#7869948] [Call#7871760] [Call#7872465] [Call#7874046] [Call#7897935] [Call#7897934] [Call#7898104] [Call#7899551] [Call#7901000] [Call#7901001]
- A problem with the Yealink encryption settings has been fixed, and they are functioning again. Affected devices: T46U, T53W, T54W, T57W, T58W
- Problems with the provisioning of the Yealink T4x phone series have been resolved
- SNOM D8 series: When the language of the phone is changed, the phone now uses the correct language for the menu
- Multithreading for module functions now works again. [Forum]
- With the function key 'Activate Modules', all modules are now available for selection with each creation
- When creating the function key 'Redirect Numbers', the voicemail box is now selected as the target by default
- The reliability of the status display of provider lines has been improved [Call#7908381]
- Logging in via the web interface is possible again when an Active Directory server hostname without a domain specification has been configured [Call#7911789] [Call#7916149]
- User's private address book entries are deleted as soon as the user account is deleted [Call#7879675]
- A deadlock problem in the address book menu has been resolved
- Occurs rarely when certificates are reloaded simultaneously and connection interruptions for LDAP occur
- A problem in the backup execution has been resolved [Call#7797976]
- The UI of the 'Firmware' page is now always correctly displayed (Phones > Firmware) [Call#7908988][Forum]
- The button 'Import Certificate with Private Key' in the menu 'Server > Webserver' is no longer unnecessarily wrapped in Firefox
- In the administration, in the menus 'Users' and 'Groups', the 'Redirect' tab is now displayed in the user's language instead of the system language
- In the 'Voicemail' window, the 'Group' column can now be sorted
- An administrator can now see their own forwards without having the 'Forward' right
The complete list of known issues can be found in our Support Forum.
- IMPORTANT GENERAL NOTES
- Version 8.1.0.11 Released on 2023/11/15
-
Bugfixes
- Note: We strongly recommend installing this security patch or updating to STARFACE 8.1!
- Update of the ActiveMQ library, to fix a security vulnerability (CVE-2023-46604)
- This security gap is relevant for configurations with an active federation setup
- The port 3090 (TCP/UDP) can be re-enabled with this patch (will not be done automatically)
- All Gigaset handsets can now be used again via STARFACE apps for outgoing calls. [Call#7864401] [Call#7865010] [Call#7864846] [Call#7869242] [Call#7871481] [Call#7861372] [Call#7833863] [Call#7839361] [Call#7847161] [Call#7830968] [Call#7848368] [Call#7844315] [Call#7853922] [Call#7854062] [Call#7856142] [Call#7837662] [Call#7830993] [Call#7870912] [Call#7861372] [Call#7866076] [Call#7866269] [Call#7866699] [Call#7866822] [Call#7867108] [Call#7867257] [Call#7867428] [Call#7868712] [Call#7869275] [Call#7869395] [Call#7870957] [Call#7869948] [Call#7871760] [Call#7872465] [Call#7874046] [Call#7897935] [Call#7897934] [Call#7898104] [Call#7899551] [Call#7901000] [Call#7901001]
- Update of the ActiveMQ library, to fix a security vulnerability (CVE-2023-46604)
- Note: We strongly recommend installing this security patch or updating to STARFACE 8.1!
- Version 8.0.0.14 Released on 2023/11/15
-
Features
- IMPORTANT GENERAL NOTES
- Lines without authentication AND whose line names contain a space do not establish calls, e.g. when operating an SBC.
- Please make sure that you do not use self-signed certificates. Certificates of type 'self-signed' are no longer accepted and may have to be replaced. STARFACE 8 requires valid certificates for encrypted telephony (for Snom, Yealink, and Gigaset). The definition of valid certificates depends on the manufacturer
- for Snom you can use Mozilla as a guide, for example. Certificates from 'Let's Encrypt' are valid as far as known. Testing and replacement can be done before or after the update, but definitely before enabling phone encryption.
- The certificates of the STARFACE Clouds are checked and valid, there is no need for action on your part.
- The previous STARFACE App for Windows version 7.3 is still compatible with STARFACE 8.
- The new app for Windows (version 8.x) requires STARFACE 8.
Minimum Requirements
- Please note that when updating STARFACE to version 8, the free disk space must be at least 6 GB plus twice the size of the backup to be imported.
- Virtualized STARFACE installations require at least 2 GB of RAM.
Update/Migration Path
- The update from STARFACE 7.0 and higher to STARFACE 8 can be installed as usual as a normal update via the web interface and does not require a new installation.
- Please update STARFACE Clouds directly via the Cloud Management in the Partner Portal. This also allows you to update directly from STARFACE 6 to STARFACE 8.
- The update from STARFACE 6 to STARFACE 8 is not possible directly via the admin area: The migration path leads, as before, via STARFACE 7, for which we offer a special module that handles the update procedure for appliances.
- Virtualized STARFACE installations have to be reinstalled manually. Details can be found in our Knowledge Base.
- Backups from older versions (e.g. STARFACE 6.7) can also be imported into STARFACE 8 as usual.
BEFORE the update
- We recommend archiving the call lists, fax lists, voicemails and call recordings with the module 'STARFACE Archiving' before the update.
- We recommend working with fully qualified call numbers in all modules.
- Before installation, please check if the siptrunk.de profile of your provider has been updated.
- With STARFACE 8, potential adjustments are required for modules. Before updating, we recommend to check whether a current, 8.0-compatible version is available for the modules used. Please contact the respective module partner for more information.
AFTER the update
- Please update your STARFACE Apps to the latest version, this is especially true for the new STARFACE App for Windows. Older versions of the STARFACE Apps (Windows, MacOS, Android & iOS) are not fully compatible with STARFACE 8.
- If you exclusively use a STARFACE Connect line, make sure in the settings that you use the highest routing priority.
- Please check already installed modules for newer versions and update them after the update.
- Activated encryptions of Snom phones are automatically deactivated by an update to STARFACE 8 and have to be reset manually in the admin area afterwards.
Bugfixes
- Note: We strongly recommend installing this security patch or updating to STARFACE 8.1!
- Update of the ActiveMQ library, to fix a security vulnerability (CVE-2023-46604)
- This security gap is relevant for configurations with an active federation setup
- The port 3090 (TCP/UDP) can be re-enabled with this patch (will not be done automatically)
- Update of the ActiveMQ library, to fix a security vulnerability (CVE-2023-46604)
- IMPORTANT GENERAL NOTES
- Version 7.3.1.5 Released on 2023/11/15
-
Features
- Important general notes
- Please note that when updating STARFACE to version 7.3, the free disk space is at least 6 GB, plus twice the size of the backup to be imported.
- Virtualized STARFACE installations require at least 2 GB of RAM.
- The update from STARFACE 6 to STARFACE 7 is not available via a normal update, but requires a special module that handles the update procedure for appliances. Virtualized STARFACE installations have to be reinstalled manually. Details can be found in our Knowledge Base.
- The update from STARFACE 7.0 and higher to STARFACE 7.3 can be installed as usual as a normal update via the web interface and does not require a new installation.
- Older versions of the STARFACE Apps (Windows, MacOS, Android & iOS) are not fully compatible with STARFACE 7.3. Please update your STARFACE Apps to the respective latest version.
- We recommend to archive the call lists, fax lists, voicemails and call recordings with the module 'STARFACE Archiving' before the update and to work with fully qualified phone numbers in all modules.
- If you use a STARFACE Connect line, please make sure in your settings that you use the highest routing priority.
- Before installation, please check if the siptrunk.de profile of your provider has been updated.
- With STARFACE 7.3 mandatory adjustments are required for modules. Before updating, we recommend to check whether a current, 7.3-compatible version is available for the modules used. Please contact your module partner for more information.
- New logging library (Log4j 2.18.0): Custom functions from .class and .jar files must be adapted to the new logging library ('NoSuchMethodError').
- Raised ASM level: For loading Java 11 compiled classes.
- Better logging in classloader: stacktrace with description why .class and .jar's could not be loaded.
- 'Tiptel Soundfile' is now called 'Yealink Soundfile': rename the resource, but not the type in the function editor.
- Discontinuation: The module 'group specific ringtones' is no longer supported with STARFACE 7.3.0. As an alternative, we recommend the free ringtones module of STARFACE, either in the free variant or the paid one, with extended support for phones.
Bugfixes
- Note: We strongly recommend installing this security patch or updating to STARFACE 8.1!
- Update of the ActiveMQ library, to fix a security vulnerability (CVE-2023-46604)
- This security gap is relevant for configurations with an active federation setup
- The port 3090 (TCP/UDP) can be re-enabled with this patch (will not be done automatically)
- Update of the ActiveMQ library, to fix a security vulnerability (CVE-2023-46604)
- Important general notes
- Version 7.2.1.5 Released on 2023/11/15
-
Features
- Important Notes:
- When updating STARFACE to 7.2.1, please note that the free disk space should be at least 6 GB.
- Please note that virtualized STARFACE installations require at least 2GB of memory.
- The update from STARFACE 6 to STARFACE 7 is not available via a available update package, but requires a special module that handles the update procedure for appliances. Virtualized STARFACE installations have to be reinstalled manually. For details please refer to our knowledge base.
- The update from STARFACE 7.0 and higher to STARFACE 7.2 can be installed as usual as a normal update via the web interface and does not require a new installation.
- Please update your STARFACE Apps to the respective latest version. Older versions of STARFACE Apps (Windows, MacOS, Android & iOS) are not fully compatible with STRAFACE 7.2.
- We recommend to archive the call lists, fax lists, voicemails and call recordings with the module 'STARFACE Archiving' before the update. You should also work only with fully qualified phone numbers in all modules.
- If you use a STARFACE Connect line, please make sure in your settings that you use the highest routing priority.
- Before installation, please check if the siptrunk.de profile of your provider has been updated.
Bugfixes
- Note: We strongly recommend installing this security patch or updating to STARFACE 8.1!
- Update of the ActiveMQ library, to fix a security vulnerability (CVE-2023-46604)
- This security gap is relevant for configurations with an active federation setup
- The port 3090 (TCP/UDP) can be re-enabled with this patch (will not be done automatically)
- Update of the glibc packages, to fix a security vulnerability (CVE-2023-4911 aka 'Looney Tunables').
- This vulnerability affects a library of the operating system 'AlmaLinux'.
- Update of the ActiveMQ library, to fix a security vulnerability (CVE-2023-46604)
- Important Notes:
- Version 7.1.1.11 Released on 2023/11/15
-
Features
- Important release notes
- In STARFACE 7.1.1, firmware updates for several telephone series were provided .
- According to our customers' feedback this not only fixed bugs for Yealink devices, but also introduced new bugs.
In close collaboration with Yealink, a new firmware has been built and integrated into STARFACE which solves these issues. - This release only updates the firmware for Yealink telephones.
Bugfixes
- Note: We strongly recommend installing this security patch or updating to STARFACE 8.1!
- Update of the ActiveMQ library, to fix a security vulnerability (CVE-2023-46604)
- This security gap is relevant for configurations with an active federation setup
- The port 3090 (TCP/UDP) can be re-enabled with this patch (will not be done automatically)
- Update of the ActiveMQ library, to fix a security vulnerability (CVE-2023-46604)
- Important release notes
- Version 8.0.0.13 Released on 2023/11/02
-
Features
- IMPORTANT GENERAL NOTES
- Lines without authentication AND whose line names contain a space do not establish calls, e.g. when operating an SBC.
- Please make sure that you do not use self-signed certificates. Certificates of type 'self-signed' are no longer accepted and may have to be replaced. STARFACE 8 requires valid certificates for encrypted telephony (for Snom, Yealink, and Gigaset). The definition of valid certificates depends on the manufacturer
- for Snom you can use Mozilla as a guide, for example. Certificates from 'Let's Encrypt' are valid as far as known. Testing and replacement can be done before or after the update, but definitely before enabling phone encryption.
- The certificates of the STARFACE Clouds are checked and valid, there is no need for action on your part.
- The previous STARFACE App for Windows version 7.3 is still compatible with STARFACE 8.
- The new app for Windows (version 8.x) requires STARFACE 8.
Minimum Requirements
- Please note that when updating STARFACE to version 8, the free disk space must be at least 6 GB plus twice the size of the backup to be imported.
- Virtualized STARFACE installations require at least 2 GB of RAM.
Update/Migration Path
- The update from STARFACE 7.0 and higher to STARFACE 8 can be installed as usual as a normal update via the web interface and does not require a new installation.
- Please update STARFACE Clouds directly via the Cloud Management in the Partner Portal. This also allows you to update directly from STARFACE 6 to STARFACE 8.
- The update from STARFACE 6 to STARFACE 8 is not possible directly via the admin area: The migration path leads, as before, via STARFACE 7, for which we offer a special module that handles the update procedure for appliances.
- Virtualized STARFACE installations have to be reinstalled manually. Details can be found in our Knowledge Base.
- Backups from older versions (e.g. STARFACE 6.7) can also be imported into STARFACE 8 as usual.
BEFORE the update
- We recommend archiving the call lists, fax lists, voicemails and call recordings with the module 'STARFACE Archiving' before the update.
- We recommend working with fully qualified call numbers in all modules.
- Before installation, please check if the siptrunk.de profile of your provider has been updated.
- With STARFACE 8, potential adjustments are required for modules. Before updating, we recommend to check whether a current, 8.0-compatible version is available for the modules used. Please contact the respective module partner for more information.
AFTER the update
- Please update your STARFACE Apps to the latest version, this is especially true for the new STARFACE App for Windows. Older versions of the STARFACE Apps (Windows, MacOS, Android & iOS) are not fully compatible with STARFACE 8.
- If you exclusively use a STARFACE Connect line, make sure in the settings that you use the highest routing priority.
- Please check already installed modules for newer versions and update them after the update.
- Activated encryptions of Snom phones are automatically deactivated by an update to STARFACE 8 and have to be reset manually in the admin area afterwards.
Bugfixes
- Update of the glibc packages to solve the security issue CVE-2023-4911, aka Looney Tunables.
- IMPORTANT GENERAL NOTES
- Version 7.3.1.4 Released on 2023/11/02
-
Features
- Important general notes
- Please note that when updating STARFACE to version 7.3, the free disk space is at least 6 GB, plus twice the size of the backup to be imported.
- Virtualized STARFACE installations require at least 2 GB of RAM.
- The update from STARFACE 6 to STARFACE 7 is not available via a normal update, but requires a special module that handles the update procedure for appliances. Virtualized STARFACE installations have to be reinstalled manually. Details can be found in our Knowledge Base.
- The update from STARFACE 7.0 and higher to STARFACE 7.3 can be installed as usual as a normal update via the web interface and does not require a new installation.
- Older versions of the STARFACE Apps (Windows, MacOS, Android & iOS) are not fully compatible with STARFACE 7.3. Please update your STARFACE Apps to the respective latest version.
- We recommend to archive the call lists, fax lists, voicemails and call recordings with the module 'STARFACE Archiving' before the update and to work with fully qualified phone numbers in all modules.
- If you use a STARFACE Connect line, please make sure in your settings that you use the highest routing priority.
- Before installation, please check if the siptrunk.de profile of your provider has been updated.
- With STARFACE 7.3 mandatory adjustments are required for modules. Before updating, we recommend to check whether a current, 7.3-compatible version is available for the modules used. Please contact your module partner for more information.
- New logging library (Log4j 2.18.0): Custom functions from .class and .jar files must be adapted to the new logging library ('NoSuchMethodError').
- Raised ASM level: For loading Java 11 compiled classes.
- Better logging in classloader: stacktrace with description why .class and .jar's could not be loaded.
- 'Tiptel Soundfile' is now called 'Yealink Soundfile': rename the resource, but not the type in the function editor.
- Discontinuation: The module 'group specific ringtones' is no longer supported with STARFACE 7.3.0. As an alternative, we recommend the free ringtones module of STARFACE, either in the free variant or the paid one, with extended support for phones.
Bugfixes
- Update of the glibc packages to solve the security issue CVE-2023-4911, aka Looney Tunables.
- Important general notes
- Version 8.1.0.9 Released on 2023/11/02
-
Features
- IMPORTANT GENERAL NOTES
-
Please make sure that you do not use any self-signed certificates. 'Self-signed' certificates will no longer be accepted and must be replaced if necessary. STARFACE 8.0 and higher strictly require valid certificates for encrypted telephony (for Snom, Yealink, and Gigaset). The definition of valid certificates depends on the manufacturer
- for Snom, you can refer to Mozilla standards, for example
- Certificates from 'Let's Encrypt' are known to be valid as far as known. Verification and exchange can take place before or after the update, but definitely before the activation of telephony encryption. The certificates of STARFACE Clouds have been checked and are valid
- there is no need for action on your part.
Minimum Requirements
-
For STARFACE 8.1, the following appliance types will no longer be supported and have been discontinued. Support for these appliance versions remains for all older, still supported STARFACE versions.
- Compact SIP V1
- Pro V5 + V6
- Advanced V5
- Enterprise V5
- Platinum V5
- Please note that when updating STARFACE to version 8, the free storage space must be at least 6 GB, in addition to twice the size of the backup to be imported.
- Virtualized STARFACE installations require at least 2 GB of RAM.
Update/Migration Path
- The update from STARFACE 7.0 and higher to STARFACE 8.1 can be installed as a normal update via the web interface as usual, and does not require a reinstallation.
- Please carry out updates for STARFACE Clouds directly via the Cloud Management in the Partner Portal. This allows you to update directly from STARFACE 6 to STARFACE 8.1.
- The update from STARFACE 6 to STARFACE 8 is not directly possible via the Admin area: The migration path leads, as before, via STARFACE 7, for which we offer a special module that takes over the update procedure for appliances.
- Virtualized STARFACE installations must be manually reinstalled. Details can be found in our Knowledge Base.
- Backups from older versions (e.g., STARFACE 6.7) can also be imported into STARFACE 8.1 as usual.
BEFORE the Update
- We recommend archiving call lists, fax lists, voicemails, and call recordings with the 'STARFACE Archiving' module before the update.
- We recommend working with fully qualified phone numbers in all modules.
- Please check before installation whether the siptrunk.de profile of your provider has been updated.
- Potential adjustments in modules may be necessary with STARFACE 8.1. We recommend checking whether there is a current, 8.1-compatible version available for the modules used before an update. Please consult the respective module partner for this.
AFTER the Update
- Existing Gigaset stations N510 and N720 must be manually adjusted after the STARFACE update. A corresponding guide is available in our Knowledge Base.
- Please update your STARFACE Apps to the latest respective version, especially the new STARFACE App for Windows. Older versions of the STARFACE Apps (Windows, MacOS, Android & iOS) are not fully compatible with STARFACE 8.
- If you use exclusively a STARFACE Connect line, ensure in the settings that you are using the highest routing priority.
- Please check already installed modules for newer versions and update them after the update.
- Activated encryptions of Snom phones will be automatically disabled by an update to STARFACE 8 and must be manually reset in the Admin area afterwards.
FEATURES & IMPROVEMENTS
Fully revised certificate management- New administrator interface and REST API for managing trusted certificates and server certificates (e.g., installed certificates for webserver and PBX)
- It is now possible to import a complete certificate chain with a private key via the Web UI and use it as a certificate for the webserver.
- The previously distributed Trust Stores have been merged into a new single Trust Store.
- All manually installed certificates must be re-imported via the new API (or the administrator interface) to ensure future-proof storage.
- Management via the file system / SSH will overwrite and delete the corresponding certificates.
- As of STARFACE 8.1, a central firmware server managed by STARFACE will handle the firmwares of all supported phones that are not frozen (Legacy) or discontinued.
- The update automatically deletes firmwares that are no longer needed from the system.
- Each STARFACE pulls the required firmware from this server.
- With the new admin interface 'Phones > Firmwares', automatic downloads and updates of phones can be set and scheduled globally or per phone type.
- New firmware updates can thus be provided independently of releases in the future.
- An active internet connection is strictly required for updates of supported end devices through the firmware server.
- List of currently supported end device types:
- Yealink: T31, T46U, T53, T54, T57, T58W, VP59, CP920, CP925, CP960, CP965
- Snom: D120, D315, D345, D385, D712, D715, D717, D725, D735, D785, D862, D865, PA1
- Grandstream: HT802, HT812, HT814
- Gigaset: N670, N870
- The SNOM M900 is currently not served by the firmware server and the firmware files are for now still part of the server image
- The STARFACE Firmware Server does not manage firmware for Legacy devices. These are delivered with the image of STARFACE 8.1 as usual and will be removed successively with subsequent versions.
- List of currently frozen end device types in Legacy status:
- Yealink: T19P_E2, T21, T23, T27, T29, T40, T40G, T41, T41S, T42, T42S, T46, T46S, T48, T48S, T49, T54S, T58A, T58V
- Snom: 710, 720, 760, 305, 375, 745, 765, MP
- Fanvil: X2, X3, X4, X5, X6, X7
- Gigaset: N510, N720
- BLF function keys on telephone devices can lead to a large number of hints, which could slow down the performance of Asterisk.
- The new dedicated service takes over the processing of these hints and prevents potential performance losses.
- In the default configuration, the Hint service is disabled.
- For call acceptance on the terminal server and in the STARFACE App for MS Teams, the current STARFACE App for Windows or Mac in version 8.1 is strictly required.
- For call acceptance in the STARFACE App for MS Teams, in addition to the desktop app, the current version 8.1 of the STARFACE App for MS Teams is required.
- During the update and backup import, unsupported phone types are removed. Configured phones of these types receive the 'Standard Sip' profile.
- SNOM D862 & D865 are now supported.
- Yealink T46U: Update to version 108.86.150.5
- Yealink T53/T54/T57 series: Update to version 96.86.150.4
- Frozen devices (Legacy status for provisioning process):
- Yealink: T19P_E2, T41S, T42S, T46S, T48S, T54S, T56A, T58A, T58V
- Fanvil: X2, X3, X4, X7
- Gigaset: N510, N720
- Update of the glibc packages that fix CVE-2023-4911 aka Looney Tunables.
- The affected library is also present in the Linux versions we have been using since STARFACE 7.3.
- As a measure to secure your systems, we strongly recommend either updating STARFACE 7.3 and 8.0 to STARFACE 8.1 or installing the corresponding security updates for 7.3 or 8.0.
- More information on this topic can be found in the News in the Partner Portal
- The packages for CPU microcodes have been updated to close the security vulnerabilities CVE-2022-40982 (Intel, Downfall) and CVE-2023-20569 (AMD, Inception).
- The RAM memory management for Tomcat has been optimized to minimize memory usage.
- Asterisk has been updated to version 20.4.0 LTS.
- AlmaLinux has been updated to version 8.8.
- Apache Batik has been updated to version 1.17.
- Jetty has been updated to version 10.0.15.
- Prometheus (local monitoring) has been updated to version 2.45.0 LTS.
- A new log file 'cloud-mgmt.log' has been introduced, in which additional information from the cloud platform will be logged in the future. This log is not displayed in the admin interface but is automatically included in log packages of error reports.
- The 'Email Notifications' permission has been moved to the administration permission as a new subcategory.
- Errors when importing own SSL certificates have been fixed with the new certificate management and can now be easily imported and managed via Admin-UI or API. [Call#7127241] [Call#7123573] [Call#7113734] [Call#6997448] [Call#7134186]
Bugfixes
- WEB UI
- In the call lists of the Web UI, the date format is now displayed based on the set language.
- Details, such as numbers in call lists, can now be highlighted with the mouse in the Web UI and copied with 'Ctrl+C'.
- The button to call a conference in the Web UI is now activated only when the conference has started.
- Unnecessary spaces in the display of a caller's company name from the address book have been removed.
- No additional 'Unknown' call appears anymore during a call with inquiry. [Call#7139858] [Call#7142510] [Call#7142436] [Call#7140094]
- After a call has been transferred, the 'Diversion on Timeout' now functions correctly again. [Call#7155697] [Call#7305030] [Call#7211173] [Call#7362084] [Call#7249294] [Call#7543540]
- For the provider SipCall, the 'Callback' function now has a working audio stream again. [Call#7847055] [Call#7907796]
- An iQueue agent now receives the post-processing time again if the previous call was transferred via inquiry. [Call#7618397]
- Gigaset handsets can now be used again for outgoing calls via STARFACE Apps. [Call#7864401] [Call#7865010] [Call#7864846] [Call#7869242] [Call#7871481] [Call#7861372] [Call#7833863] [Call#7839361] [Call#7847161] [Call#7830968] [Call#7848368] [Call#7844315] [Call#7853922] [Call#7854062] [Call#7856142] [Call#7837662] [Call#7830993] [Call#7870912] [Call#7861372] [Call#7866076] [Call#7866269] [Call#7866699] [Call#7866822] [Call#7867108] [Call#7867257] [Call#7867428] [Call#7868712] [Call#7869275] [Call#7869395] [Call#7870957] [Call#7869948] [Call#7871760] [Call#7872465] [Call#7874046] [Call#7897935] [Call#7897934] [Call#7898104] [Call#7899551] [Call#7901000] [Call#7901001]
- The EXP43 expansion module now works again for the Yealink T46U. The new firmware version 108.86.150.5 is required for this.
- The EXP50 expansion module now works again for the Yealink T53/T54/T57 series. The new firmware version 96.86.150.4 is required for this.
- Problems with provisioning the Yealink T4x phone series have been fixed.
- Changes to the advanced settings for the phone type 'Standard Sip' are now applied again.
- On the Snom M900, firmware updates are now only carried out when necessary (and not every time) if the setting 'Automatically update firmware' is active.
- Paper labels for function keys of SNOM phones can now be created again.
- The log view for SNOM desk phones has been optimized and made more clear.
- Phone numbers in the internal address book are now saved in the normalized, international format after editing.
- The buttons to add and import contacts are now only present if write access for the current directory exists.
- If multiple changes are made in the menu 'Address Book > Layout' one after the other, they are now correctly saved.
- During user import, the external phone number, if available, is now set as the caller ID display.
- Blacklist entries are now correctly displayed in the system status again. [Call#7865620]
- Changes to users are now applied after saving the changes with the 'Apply' button.
- The phone setting for 'Displayed Call Number' is now applied upon first saving.
- The phone setting 'Displayed Call Number' has been supplemented with the option 'primary external phone number'. This is now the default value in new templates and the standard template.
- After editing and deleting configured phones, no errors occur when adding a phone again.
- For the user template 'STARFACE Standard', the setting for 'Displayed Call Number' has been set to 'Retain user settings'.
- In user templates, buttons can no longer be edited if the category is disabled.
- In user templates, buttons can no longer be moved if the category is disabled.
- In user templates, the current settings are now displayed when editing buttons.
- The drag & drop behavior of buttons in user templates has been optimized.
- An error in the permission settings of user templates has been fixed, so that the sub-rights now correctly affect the main right.
- Warning notices in the list of module configurations are now fully available again.
- NetworkManager packages have been updated so that NGN configurations work. [Call#7831669] [Call#7867892]
- In the 'estos' menu, the names of the settings have been expanded to include 'uaCSTA'.
- The button to call a conference was active, even if no phone was assigned to the users.
- Group buttons now again show an active diversion.
- The labels of the function key type 'Phone Menu: Address Book' have been corrected in the button settings of the Windows App v8.
- The counter of voicemail notifications in the client now decreases again after listening to the voicemail. [Call#7225290] [Call#7331598] [Call#7362067][Call#7365092] [Call#7215643] [Call#7505101] [Call#7535262] [Call#7597892][Call#7567898] [Call#7618404]
- An error has been fixed that sporadically prevented the correct processing of voicemails and the sending of voicemail notifications via email. [Call#7154682] [Call#7142994] [Call#7151916] [Call#7153163] [Call#7111225][Call#7130278] [Call#7131944] [Call#7141214] [Call#7194175] [Call#7623605]
- The job for creating backups now uses the internal hard drive as the default storage location by default. Existing divergent configurations are automatically renamed and preserved during the update.
- Incorrect error messages after running a backup job have been removed. [Call#7504397] [Call#7622389] [Call#7868169]
- SMBv2.0 is now considered when mounting Windows Shares. [Call#7104020]
- Incoming calls via the provider Ecotel are now correctly forwarded again. [Call#7865369] [Call#7854319] [Call#7865380] [Call#7865425] [Call#7860715] [Call#7865994] [Call#7864991] [Call#7856531] [Call#7868831] [Call#7869217] [Call#7871105]
- If 'Clip no Screening' is disabled or not supported by the provider, the external phone number of the user is now again signaled for external forwards. [Call#7216576] [Call#7252946] [Call#7249914] [Call#7228625] [Call#7312035]
- Connect numbers now remain when there is a change in the Hardware-ID in Clouds.
The complete list of Known Issues can be found in our Support Forum.
- IMPORTANT GENERAL NOTES
- Version 8.0.0.12 Released on 2023/07/17
-
Features
- IMPORTANT GENERAL NOTES
- Lines without authentication AND whose line names contain a space do not establish calls, e.g. when operating an SBC.
- Please make sure that you do not use self-signed certificates. Certificates of type 'self-signed' are no longer accepted and may have to be replaced. STARFACE 8 requires valid certificates for encrypted telephony (for Snom, Yealink, and Gigaset). The definition of valid certificates depends on the manufacturer
- for Snom you can use Mozilla as a guide, for example. Certificates from 'Let's Encrypt' are valid as far as known. Testing and replacement can be done before or after the update, but definitely before enabling phone encryption.
- The certificates of the STARFACE Clouds are checked and valid, there is no need for action on your part.
- The previous STARFACE App for Windows version 7.3 is still compatible with STARFACE 8.
- The new app for Windows (version 8.x) requires STARFACE 8.
Minimum Requirements
- Please note that when updating STARFACE to version 8, the free disk space must be at least 6 GB plus twice the size of the backup to be imported.
- Virtualized STARFACE installations require at least 2 GB of RAM.
Update/Migration Path
- The update from STARFACE 7.0 and higher to STARFACE 8 can be installed as usual as a normal update via the web interface and does not require a new installation.
- Please update STARFACE Clouds directly via the Cloud Management in the Partner Portal. This also allows you to update directly from STARFACE 6 to STARFACE 8.
- The update from STARFACE 6 to STARFACE 8 is not possible directly via the admin area: The migration path leads, as before, via STARFACE 7, for which we offer a special module that handles the update procedure for appliances.
- Virtualized STARFACE installations have to be reinstalled manually. Details can be found in our Knowledge Base.
- Backups from older versions (e.g. STARFACE 6.7) can also be imported into STARFACE 8 as usual.
BEFORE the update
- We recommend archiving the call lists, fax lists, voicemails and call recordings with the module 'STARFACE Archiving' before the update.
- We recommend working with fully qualified call numbers in all modules.
- Before installation, please check if the siptrunk.de profile of your provider has been updated.
- With STARFACE 8, potential adjustments are required for modules. Before updating, we recommend to check whether a current, 8.0-compatible version is available for the modules used. Please contact the respective module partner for more information.
AFTER the update
- Please update your STARFACE Apps to the latest version, this is especially true for the new STARFACE App for Windows. Older versions of the STARFACE Apps (Windows, MacOS, Android & iOS) are not fully compatible with STARFACE 8.
- If you exclusively use a STARFACE Connect line, make sure in the settings that you use the highest routing priority.
- Please check already installed modules for newer versions and update them after the update.
- Activated encryptions of Snom phones are automatically deactivated by an update to STARFACE 8 and have to be reset manually in the admin area afterwards.
Bugfixes
- The Snom M900 can be used in a multi cell configuration.[Call#7866945] [Call#7867149]
- Lines can be configured with blank spaces in the line name. [dazugehöriges Known Issue]
- IMPORTANT GENERAL NOTES
- Version 8.0.0.11 Released on 2023/05/04
-
Features
- IMPORTANT GENERAL NOTES
- Lines without authentication AND whose line names contain a space do not establish calls, e.g. when operating an SBC.
- Please make sure that you do not use self-signed certificates. Certificates of type 'self-signed' are no longer accepted and may have to be replaced. STARFACE 8 requires valid certificates for encrypted telephony (for Snom, Yealink, and Gigaset). The definition of valid certificates depends on the manufacturer
- for Snom you can use Mozilla as a guide, for example. Certificates from 'Let's Encrypt' are valid as far as known. Testing and replacement can be done before or after the update, but definitely before enabling phone encryption.
- The certificates of the STARFACE Clouds are checked and valid, there is no need for action on your part.
- The previous STARFACE App for Windows version 7.3 is still compatible with STARFACE 8.
- The new app for Windows (version 8.x) requires STARFACE 8.
Minimum Requirements
- Please note that when updating STARFACE to version 8, the free disk space must be at least 6 GB plus twice the size of the backup to be imported.
- Virtualized STARFACE installations require at least 2 GB of RAM.
Update/Migration Path
- The update from STARFACE 7.0 and higher to STARFACE 8 can be installed as usual as a normal update via the web interface and does not require a new installation.
- Please update STARFACE Clouds directly via the Cloud Management in the Partner Portal. This also allows you to update directly from STARFACE 6 to STARFACE 8.
- The update from STARFACE 6 to STARFACE 8 is not possible directly via the admin area: The migration path leads, as before, via STARFACE 7, for which we offer a special module that handles the update procedure for appliances.
- Virtualized STARFACE installations have to be reinstalled manually. Details can be found in our Knowledge Base.
- Backups from older versions (e.g. STARFACE 6.7) can also be imported into STARFACE 8 as usual.
BEFORE the update
- We recommend archiving the call lists, fax lists, voicemails and call recordings with the module 'STARFACE Archiving' before the update.
- We recommend working with fully qualified call numbers in all modules.
- Before installation, please check if the siptrunk.de profile of your provider has been updated.
- With STARFACE 8, potential adjustments are required for modules. Before updating, we recommend to check whether a current, 8.0-compatible version is available for the modules used. Please contact the respective module partner for more information.
AFTER the update
- Please update your STARFACE Apps to the latest version, this is especially true for the new STARFACE App for Windows. Older versions of the STARFACE Apps (Windows, MacOS, Android & iOS) are not fully compatible with STARFACE 8.
- If you exclusively use a STARFACE Connect line, make sure in the settings that you use the highest routing priority.
- Please check already installed modules for newer versions and update them after the update.
- Activated encryptions of Snom phones are automatically deactivated by an update to STARFACE 8 and have to be reset manually in the admin area afterwards.
FEATURES and IMPROVEMENTS
Presence status logic/non-STARFACE XMPP client customization:- All status updates of type 'unavailable' are now ignored in Openfire unless it is the last known session of the user account:
- A user is always online when one or more of his XMPP clients are online.
- A user is offline and 'unavailable' for chat only when no XMPP client is online.
- A user is online as long as the user is logged into the mobile app and the app is active, i.e. the user does not log out or close the app. Caution: If the app moves to the background in iOS, it is considered offline.
- When using non-Starface XMPP clients, changed avatar images are no longer transferred to other clients. The images must now be transferred via the user settings in the web interface or a Starface client.
- Yealink phones now support encrypted auto-provisioning, STARFACE menus, and telephony over SRTP and TLS (SIPS).
- Snom phones now additionally support encrypted auto-provisioning and STARFACE menus and all non-legacy Snom phones support encrypted telephony via SRTP and TLS (SIPS).
- Gigaset N870 and N670 now support encrypted auto-provisioning, STARFACE menus and telephony via SRTP and TLS (SIPS).
- New backup format, for significantly faster backups and restores and more reliable recovery processes in case of failure.
- Backups created with older STARFACE versions are still supported and can be imported as usual.
- Error messages of the backup now appear not only in 'error.log' but also in 'backup.log'.
- New log file 'update.log': The previous logs in '/var/log/starface-update/' are now aggregated and displayed in a log file under '/var/log/starface/update.log.
- New REST interface 'server/backups' for creating, executing and restoring backups as well as for querying the current process status (see 'REST API').
- New: Grandstream HT812 is now supported.
- Gigaset N720: Update to v117
- Yealink T58V/T56A: Update to 58.86.150.1
- Yealink T58W: Update to 150.86.150.2
- Yealink VP59: Update to 91.86.150.2
- Adaptation: On the Snom phones D385, D717, D735 and D785, the STARFACE user picture is now displayed for a logged in user in idle mode.
- Integration of Asterisk realtime architecture, i.e. switching from configuration files to database for SIP peers, for improved handling of SIP reloads and thus relieving the load on the Asterisk and improving overall performance.
- Updating Asterisk to version 16.30.0
- Update Java to version JDK 17 (LTS)
- New endpoint to download a triggered backup: 'GET /server/backups/files/{backupJobId}'. Requires the 'Admin_MISC' permission. The response contains a hex-encoded SHA256 hash which can optionally be used for the restore.
- New endpoint to query the current status of a running backup or restore process 'GET /server/backups/state/{backupJobId}'
- no specific permission required.
- New endpoint to trigger a backup with the submitted configuration 'PUT /server/backups/actions/run'
- requires the 'Admin_MISC' permission.
- New endpoint for triggering a restore process with the submitted backup 'PUT /server/backups/actions/restore'
- requires the 'Admin_MISC' permission. An additional SHA256 hash can be supplied for server-side verification.
- The '/users/{userId}/managedConferences/{conferenceId}' endpoint now returns a 'ForbiddenException' instead of 'UnauthorizedException' for GET/PUT/DELETE if the executing user is not the conference owner or administrator.
- The '/users/{userId}/phonenumberconfig/phonenumbers/delete' endpoint now uses the 'DELETE' method for deletion. The previous POST method has been marked as deprecated.
- New UCI endpoint for module instances: A user with the right permissions can request all configured module instances, subscribe to a selected set, and receive updates as changes occur. The user can also toggle the status of any module instance, whether it is subscribed or not. One of the following two permissions are required for access: 'Administration' and 'Keys'.
- The '/users/{userId}/managedConferences/{conferenceId}' endpoint now returns a 'ForbiddenException' instead of 'UnauthorizedException' for GET/PUT/DELETE if the executing user is not the conference owner or administrator.
- The '/users/{userId}/phonenumberconfig/phonenumbers/delete' endpoint now uses the 'DELETE' method for deletion. The previous POST method has been marked as deprecated.
- A new 'Delete All' button has been added in the Administration system status, which can now be used to delete all messages at once.
- New log file 'status.log': contains information about changes by users in the system status of the administration (e.g. deleting messages).
- The new log file 'update.log' under '/var/log/starface/' aggregates the previous log files in '/var/log/starface-update/' from phase 3 of the STARFACE updates.
- With estos MetaDirectory 5 as an external address book for STARFACE, user-specific read access rights can now be assigned. For the mandatory synchronization of existing user accounts, we recommend using a Microsoft Active Directory. When using email addresses as user IDs, separate email addresses must also be created for groups. Alternatively, the login/account ID can be used.
- Local monitoring of the PBX system was integrated (Prometheus).
- Local monitoring requires SSH access.
Bugfixes
- BUGFIXES
Call List:- Busy forwarding to voicemail box now generates correct entries in the call list after rejecting the call.
- For an accepted group call, the 'Accepted by' field is now filled correctly. [Call#7601947] [Call#7706171] [Call#7779028]
- Group calls are now correctly displayed in the call list if the user has accepted the call via iFMC. [Call#7216027] [Call#7722694]
- The BLFs in the Call Manager of the WEB UI are displayed correctly again.
- Call pickup via star dialing '*8' now only works with the number of the called party.
- Fixed a bug that could cause all other agents in an iQueue to be blocked after one agent accepted a call in certain situations. [Call#7130785]
- The N510 now works again when the PBX is set to 'French'. [Call#7140740] [Call#7131028] [Call#7134799] [Call#7153462]
- The unused call list of the Yealink CP960 has been removed.
- The Snom M900 DECT handsets can now be muted via their menus or by a long press on the '#' key. [CALL#7622417]
- Fixed an error when changing the folder during the creation of a new contact.
- The buttons for importing and adding an entry in the LDAP address book are now no longer visible if the directory is read-only.
- Entries with certain special characters loaded via LDAP are now displayed correctly.
- The menu items 'System Status' and 'STARFACE Neon/Connect' of the administration are now only visible for users with the permission 'Admin_MISC'. [Call#7654656]
- The phone configuration (softphone/SIP account) for a STARFACE app is now also removed when a user account is deleted. This also applies to updates or imports of backups that no longer have assigned softphone configurations.
- Long error messages when configuring the LDAP address book are now correctly displayed in the dialog window again.
- Forwarding destination numbers are now correctly stored in the WEB UI when a voicemail box is selected as destination.
- Redirections are now saved without error message if no voicemail and destination number was specified.
- Error messages for forwarding now correctly display the forwarding type and the affected phone number.
- Missing log files no longer cause the log UI to crash in the 'Server: Log Files'. [Call#7703077] [Call#7783173]
- Changes to function keys can again be saved and transferred to a phone as often as desired.
- Duplicate entries in the line configurations no longer cause errors at system startup.
- The system restart is no longer delayed when connection attempts to the STARFACE Neon API fail. [Call#7725594]
- A user's telephony options 'DND' and 'Call waiting' can now be set properly again via 'PUT /users/
/phoneconfig' if no phone is assigned to the user.
- The Building Block 'SetCaller' is now correctly determined from the call number master again. [Call#7186800]
- For the module function 'CallPhoneNumber', 'caller number' and 'ringing duration' now work correctly again. [Call#7107093] [Call#7180142] [Call#7581660]
- IMPORTANT GENERAL NOTES
- Version 7.3.1.3 Released on 2023/02/09
-
Features
- Important general notes
- Please note that when updating STARFACE to version 7.3, the free disk space is at least 6 GB, plus twice the size of the backup to be imported.
- Virtualized STARFACE installations require at least 2 GB of RAM.
- The update from STARFACE 6 to STARFACE 7 is not available via a normal update, but requires a special module that handles the update procedure for appliances. Virtualized STARFACE installations have to be reinstalled manually. Details can be found in our Knowledge Base.
- The update from STARFACE 7.0 and higher to STARFACE 7.3 can be installed as usual as a normal update via the web interface and does not require a new installation.
- Older versions of the STARFACE Apps (Windows, MacOS, Android & iOS) are not fully compatible with STARFACE 7.3. Please update your STARFACE Apps to the respective latest version.
- We recommend to archive the call lists, fax lists, voicemails and call recordings with the module 'STARFACE Archiving' before the update and to work with fully qualified phone numbers in all modules.
- If you use a STARFACE Connect line, please make sure in your settings that you use the highest routing priority.
- Before installation, please check if the siptrunk.de profile of your provider has been updated.
- With STARFACE 7.3 mandatory adjustments are required for modules. Before updating, we recommend to check whether a current, 7.3-compatible version is available for the modules used. Please contact your module partner for more information.
- New logging library (Log4j 2.18.0): Custom functions from .class and .jar files must be adapted to the new logging library ('NoSuchMethodError').
- Raised ASM level: For loading Java 11 compiled classes.
- Better logging in classloader: stacktrace with description why .class and .jar's could not be loaded.
- 'Tiptel Soundfile' is now called 'Yealink Soundfile': rename the resource, but not the type in the function editor.
- Discontinuation: The module 'group specific ringtones' is no longer supported with STARFACE 7.3.0. As an alternative, we recommend the free ringtones module of STARFACE, either in the free variant or the paid one, with extended support for phones.
- Native integration of estos MetaDirectory: The MetaDirectory from estos is now automatically recognized by STARFACE if configured in STARFACE as an external LDAP address book, and no longer requires any additional configuration adjustments to MetaDirectory. In addition, a more performant search for estos MetaDirectory has been implemented.
- TLS configuration for the LDAP address book: Port 714 is now treated like port 636 and forces 'TLS' instead of 'STARTTLS' as before, i.e. regardless of the settings in the dialog (e.g. with the admin setting 'unencrypted').
- Extension of LDAP configuration for the address book: it is now possible to configure the address book in LDAP without a folder to always search under the base folder.
Bugfixes
- Bugfixes
- Update process: Various bugs have been fixed that caused problems during an update in individual cases. [Call#7567502] [Call#7567710] [Call#7582090] [Call#7582915] [Call#7573878] [Call#7577309] [Call#7581723] [Call#7582686] [Call#7582707] [Call#7567771] [Call#7567956] [Call#7574395] [Call#7574247] [Call#7572243] [Call#7574557] [Call#7570718] [Call#7582686] [Call#7602067] [Call#7580579] [Call#7618371] [Call#7621030] [Call#7618516]
- Dropbox: Scheduled backups can be successfully saved to Dropbox again. [Call#7136748][CALL#7150790][Call#7156726][Call#7141156 ][Call#7164994][Call#7194156][7196095 ][Call#7236630][Call#7416460]
- Keys: Multiple assignements to one function key are now properly saved and won't break the key anymore. [Call#7617501] [Call#7597910] [Call#7688338] [Call#7567931] [Call#7580757] [Call#7597886] [Call#7620401] [Call#7651581]
- iQueue: Fixed some errors when logging in or logging out iQueue agents. [Call#7195632]
- iQueue: For forwarding to an iQueue, the ID display 'Group call forwarding on phone: Name' is now used correctly.
- Snom: Provisioning for Snom 710/720/760 now works correctly again.
- User templates: Upper and lower case in the user/group selection for BLF of the function key editor are now treated the same for sorting.
The complete list of known issues can be found in our Support Forum.
- Important general notes
- Version 7.3.0.10 Released on 2022/11/23
-
Features
- Important general notes
- Please note that when updating STARFACE to version 7.3.0, the free disk space is at least 6 GB, plus twice the size of the backup to be imported.
- Virtualized STARFACE installations require at least 2 GB of RAM.
- The update from STARFACE 6 to STARFACE 7 is not available via a normal update, but requires a special module that handles the update procedure for appliances. Virtualized STARFACE installations have to be reinstalled manually. Details can be found in our Knowledge Base.
- The update from STARFACE 7.0 and higher to STARFACE 7.3 can be installed as usual as a normal update via the web interface and does not require a new installation.
- Older versions of the STARFACE Apps (Windows, MacOS, Android & iOS) are not fully compatible with STARFACE 7.3. Please update your STARFACE Apps to the respective latest version.
- We recommend to archive the call lists, fax lists, voicemails and call recordings with the module 'STARFACE Archiving' before the update and to work with fully qualified phone numbers in all modules.
- If you use a STARFACE Connect line, please make sure in your settings that you use the highest routing priority.
- Before installation, please check if the siptrunk.de profile of your provider has been updated.
- The interface UCI v2, which is marked as deprecated, is finally removed with this STARFACE version, as already announced with STARFACE 7.1.
- With the release of 7.3, appointments for updates to all current STARFACE versions can now be booked via Cloud Management in the Partner Portal. Please update STARFACE Clouds directly via the Partner Portal.
- With STARFACE 7.3 mandatory adjustments are required for modules. Before updating, we recommend to check whether a current, 7.3-compatible version is available for the modules used. Please contact your module partner for more information.
This update contains potential breaking changes for existing modules.
As a module partner, please check your module and adjust it if necessary.- New logging library (Log4j 2.18.0): Custom functions from .class and .jar files must be adapted to the new logging library ('NoSuchMethodError').
- Raised ASM level: For loading Java 11 compiled classes.
- Better logging in classloader: stacktrace with description why .class and .jar's could not be loaded.
- 'Tiptel Soundfile' is now called 'Yealink Soundfile': rename the resource, but not the type in the function editor.
- Discontinuation: The module 'group specific ringtones' is no longer supported with STARFACE 7.3.0. As an alternative, we recommend the ringtones module of STARFACE, either in the free variant or the paid one, with extended support for phones.
Innovations in STARFACE MS Teams Integration
For STARFACE 7.3 there are new versions of the MS Teams App and the STARFACE Teams Module.
The following bugs and features have been fixed or implemented:- Presence status matching between STARFACE and MS Teams for outgoing calls
- Revised presentation of iQueue diagrams and legends
- Search internal function keys & contacts directly via MS Teams integration
- Improved configuration of iFMC settings
- New infrastructure for more stable communication
- Simplified module updates via STARFACE module manager
- New information of who has taken over a group call.
- New option to mark a missed call as 'called back'. This will directly inform other group members if a missed group call has already been answered.
- New comment field for call list entries. Short notes can be stored here centrally for all other group members to see.
- Ability to transfer user-related data such as phone settings, permissions and function keys to multiple user accounts simultaneously.
- New tab 'Templates' in the admin area under 'Users'.
- New dropdown menu in the user create/edit dialog for applying specific templates to the respective user.
- New log 'Users' for storing all events in the context of user templates.
- Standard templates with default settings.
- Configuration of phone settings: Call waiting, missed call email, displayed phone number.
- Permissions configuration: all except admin permissions.
- Configuration of function keys: BLF of users, direct dialing of phone numbers from address books, callback on busy, Park&Orbit, DTMF, Silence and 'Empty key'.
- Updating the following endpoints:
- Gigaset N510 IP PRO: to firmware version v262
- Gigaset N670/N870: to firmware version 2.49.1
- Grandstream HT802, HT812 & HT814: to firmware version 1.0.41.2
- Newly added end devices:
- Yealink T31, T31P, T31G
- Yealink T58W
- Yealink CP925, CP965
- Frozen end devices (Legacy status for the provisioning process):
- Snom Meeting Point
- Snom 710, 720 & 760
- Snom D305, D375, D710, D745 & D765
- Removed end devices (provisioning no longer possible):
- Aastra
- Alcatel business phones (200-800)
- Gigaset DE-Serie (nicht DECT)
- Gigaset Maxwell Basic & Maxwell 3
- Grandstream HT702 & HT704
- Panasonic KX-UT-Serie
- Polycom Soundstation
- Siemens/Unify Open Stage Serie
- Snom 3xx Serie
- Snom 8xx Serie
- Tiptel
- Yealink T20, T22, T26, T28, T32, T38, VP530
- Other changes:
- Gigaset N870/N670: All mobile device data can now be retransmitted using a new button.
- Gigaset N870: MAC addresses can now be managed in the administration area.
- Voice encryption is now supported for the Snom M900.
- For Grandstream devices, an update is now only performed if a newer version is available.
- The 'Accoustic Shield', 'Wi-Fi Security Check' and 'Dialpad on Hold' features were enabled for several Yealink phones.
- With the Snom D-Series, when using 'Click-to-dial' in headset mode, it will only ring on the headset.
- The 'Automatic search of phones' function has been removed.
- Doorline settings are no longer displayed for DECT multi-cell systems.
- Optimization of URLs for doorlines.
- For Patton devices, the web login settings have been removed from the web interface.
- Update of Log4j to version 2.18.0
- Update of Asterisk to version 16.27.0
- Update of AlmaLinux to version 8.6
- Update of OpenJDK to version 11.0.16
- Successful logins via an IP address are no longer excluded from the system in the event of a large number of requests via this IP address.
- Optimization of the performance in the internal communication between Openfire and Tomcat.
- Rest Authentication tokens become invalid when credentials are changed.
- The ringing strategy has been added to the group interfaces.
- New interfaces for user skills have been introduced.
- A new interface for group pickup and caller data visibility has been introduced.
- The server configurations for ECSTA can now be set and retrieved via a dedicated interface.
- The host name at Address Book or Active Directory must now match the host name in the certificate if TLS with validation is enabled.
- The second directory server at Active Directory is now also checked when testing the connection, if it is specified.
- Unknown errors during the connection test for the address book or Active Directory are now displayed directly to the administrator.
- Non-standard ports are now taken into account during the connection test for the address book or Active Directory.
- The module 'free ringtones' has been adapted and added for STARFACE 7.3.0.
Bugfixes
- Bugfixes
Call list display
- Calls initiated in the iOS app using the dialing method 'Callback' now have the correct signaling and correct call list entries.
- In the new display 'accepted from' you are no longer displayed if you have answered the call yourself with multiple end devices configured.
- When a blind transfer comes back to the transferor, the signaling is now correct again.
- iFMC will now stop ringing if the call has already been transferred.
- REST API: The ringing strategy is not changed when a group is modified via the REST API.
- The iQueue report shows the CallerID for all calls again. [Call#7107972]
- iQueue recordings are now only copied to an SMB drive if this is also enabled.
- For newly registered STARFACE Apps for Windows the codec H.264 is set again. [Call#7182259]
- Hyphens in shortcut keys are now removed when saving function keys and thus no longer cause problems with STARFACE apps. [Call#7270223][Call#7221419][Call#7218782][Call#7176541][Call#72409
- The number of hints for user statuses has been optimized to reduce the load on Asterisk.
- Gigaset: The N870 and N670 are now automatically provisioned when the codec is changed in the web interface.
- Gigaset: The N510 IP PRO is now correctly provisioned again. [Call#7140740][Call#7131028][Call#7134799][Call#7153462]
- Yealink: For Yealink phones, lists are limited to 30 entries, otherwise they show an error.
- Yealink: On the Yealink CP960, missing app icons are displayed correctly again.
- Yealink: The phonebook button when forwarding now accesses the STARFACE address book. [Call#6941298] [Call#6928223]
- Yealink: On the Yealink T57W and T58A, the 'Connected' status is now no longer displayed for certain function keys (DND, Forwarding).
- When a phone is offline, a correct error message is now displayed when copying the function keys.
- The STARFACE App for Windows is no longer incorrectly flagged as PushClient.
- In case of multiple lines with the same provider profile, one drop location can now be defined per line. [Call#7133443] [Call#7100698] [Call#6927167] [Call6945250] [Call#6949737] [Call#6970329] [Call#7146375] [Call#7169068]
- The selection of phone number formats in the French interface has been aligned with the German interface. [Call#7139782]
- COR rules can be edited again. [Forum] [Call#7186914] [Call#7187017]
- When deleting a user account, all assigned phone numbers are correctly removed.
- Editing a group is possible again, even if the administrator does not have the permissions for redirections. [Call#7106195] [Call#7135982]
- If you only change the ringing strategy for a group, you will now be prompted to save.
- The correct name for the Gigaset N720 is now used in the admin area under 'Phones > Security'.
- Log messages and their levels have been adjusted to improve the readability of 'starface-database.log'.
- All TLDs are now accepted in e-mail addresses. [Call#7417508]
- In the English localization, the option for phone number display has been changed from 'No display' to 'Number withheld' in the Admin UI system-wide.
- When creating external single numbers, it is no longer possible to store single-digit phone numbers.
- In case the request for a hardware change was not accepted after 7 days, there is now an improved error message.
- The web server ports can no longer be set to ports assigned by the system.
- The update removes address book entries of already deleted users. [Call#6998725]
- The address book is usable again when the address book log level is set to TRACE. [Call#6998810] [Call#6998941] [Call#6996100]
- Speed dials for address book contacts can be set properly again. [Call#7245142] [Call#7211165] [Forum]
- Fixed an address book resolution error when the query took too long, but then there was still a response when the phone had already started ringing.
- The length for names resolved from the address book has been limited to 100 characters.
- Host names for the address book and Active Directory are now better validated.
- Unused LDAP connections are now always reliably closed.
- REST API: POST and PUT for contacts now return the created and changed contact respectively.
- Classes built with Java 11 can now be loaded in the module system. [Call#7165471] [Call#7169105]
- The same time format is now used for conference invitations in all languages. [Call#6945970]
- Conferences can no longer be scheduled for the past.
- The messages why a conference cannot be attended have been improved. Call#6924821]
- If a message was spoken to a voicemail box, all assigned users/groups get correct call list entries. [Call#7172837]
- When removing permissions in the system group, local groups still have the correct user assignments.
- The deletion of groups is now synchronized.
- When editing a provider profile, the French localization has been improved. [Call#7139782]
- Important general notes
- Version 7.2.1.3 Released on 2022/07/06
-
Features
- Important Notes:
- When updating STARFACE to 7.2.1, please note that the free disk space should be at least 6 GB.
- Please note that virtualized STARFACE installations require at least 2GB of memory.
- The update from STARFACE 6 to STARFACE 7 is not available via a available update package, but requires a special module that handles the update procedure for appliances. Virtualized STARFACE installations have to be reinstalled manually. For details please refer to our knowledge base.
- The update from STARFACE 7.0 and higher to STARFACE 7.2 can be installed as usual as a normal update via the web interface and does not require a new installation.
- Please update your STARFACE Apps to the respective latest version. Older versions of STARFACE Apps (Windows, MacOS, Android & iOS) are not fully compatible with STRAFACE 7.2.
- We recommend to archive the call lists, fax lists, voicemails and call recordings with the module 'STARFACE Archiving' before the update. You should also work only with fully qualified phone numbers in all modules.
- If you use a STARFACE Connect line, please make sure in your settings that you use the highest routing priority.
- Before installation, please check if the siptrunk.de profile of your provider has been updated.
- Added a new tab 'estos' for the connection of the estos ECSTA (under 'Admin > Extended Settings').
- The buffer size for STARFACE app events will adapt dynamically. [Call#6996523]
- Added a download button in the tab 'Log Files' under 'Admin > Server'. You can now download locally the complete log file package of your STARFACE.
- New Firmware: Added new firmware version 91.86.150.1 for the Yealink VP59.
- New Firmware: Added new firmware version 73.86.150.1 for the Yealink CP960.
- The free module 'Ringtones' is now available in the STARFACE module library.
Bugfixes
- Fixed Issues: 4
- The phone number of a caller will be correctly shown again in the iQueue of an interconnection. [Call#6928059]
- The automatic login for the STARFACE web interface is working again. [Call#7166258]
- The value for 'Max. connections' can now set to ?1? (under ?Admin > Lines > Lines > Extended?). [Call#7114684]
- When creating a new user, the correct response of type ?application/json' will now be sent. [Board]
- Important Notes:
- Version 7.2.0.5 Released on 2022/05/17
-
Features
- Important Notes:
- When updating STARFACE to 7.2, please note that the free disk space should be at least 5 GB.
- Please note that virtualized STARFACE installations require at least 2GB of memory.
- The update from STARFACE 6 to STARFACE 7 is not available via a available update package, but requires a special module that handles the update procedure for appliances. Virtualized STARFACE installations have to be reinstalled manually. For details please refer to our knowledge base.
- The update from STARFACE 7.0 and higher to STARFACE 7.2 can be installed as usual as a normal update via the web interface and does not require a new installation.
- Older versions of STARFACE Apps (Windows, MacOS, Android & iOS) are not fully compatible with STRAFACE 7.2. Please update your STARFACE Apps to the respective latest version.
- We recommend to archive the call lists, fax lists, voicemails and call recordings with the module 'STARFACE Archiving' before the update and to work with fully qualified phone numbers in all modules.
- If you use a STARFACE Connect line, please make sure in your settings that you use the highest routing priority.
- Before installation, please check if the siptrunk.de profile of your provider has been updated.
- The interface UCI v2, which is marked as deprecated, will be completely removed with the next major STARFACE version, as already announced with STARFACE 7.1.
- Support of NEON Freemium independent of STARFACE Connect (requires the latest client version).
- Global external signaling numbers for users can now be configured and assigned.
- There is a new free variant of the 'Ringtones' module that allows to distinguish between internal/external and individual phone numbers.
- New policies have been introduced for user passwords to increase security. [Call#6974558]
- There are two new phone device types for using estos ProCall as a softphone, for regular and encrypted SIP connections from the STARFACE PBX to the estos ProCall Server.
- The new DECT station SNOM M900 is now supported on STARFACE.
- Login IDs for new users are suggested according to a random pattern.
- If Connect numbers are removed in the Connect service, the change is now applied in the STARFACE PBX.
- On creation of the iQueue statistics report, copying voicemails to shares can now be disabled. [Call#6909801] [Call#6905103]
- When copying the function keys, multiple devices can now be selected.
- A permission can now be assigned for 'Send files'.
- The search fields in the web UI for administration are now reset when switching pages or tabs/panels.
- The message displayed when the installation media is still mounted is now clearer and easier to understand.
- The following devices have been updated:
- Snom D120: to firmware version 10.1.54.13
- Snom D745: to firmware version 10.1.57.14
- Snom D305/D375/D765: to firmware version 10.1.64.14
- Snom D315/D345/D385/D712/D715/D717/D725/D735/D785: to firmware version 10.1.84.17
- Gigaset N670/N870: to firmware version v2.44
- The value for 'OpenFire message buffer size' will now be adapted to the system automatically. [Call#7107443] [Call#6997918] [Call#7109269]
- Log files can now be sent individually to any e-mail address in addition to the option of sending them directly to Support.
- The phone web UI will now no longer get closed when the admin navigates away or closes the admin area web UI.
- The naming of the features 'Group pickup' and 'caller ID display' has been unified.
- The CSV template file for user import is now correctly separated with the selected character (comma or semicolon).
- The text input fields in module settings are now wider.
- System mails now only contain the port information if it differs from the default.
- Asterisk updated to version 16.23.0.
- Linux operating system updated to AlmaLinux 8.5.
- Java updated to OpenJDK 11.
- Java updated to OpenJDK 11.
- Java updated to OpenJDK 11.
Bugfixes
- Fixed Issues: 82
Top 5:
- The SIP field 'CallerID(name)' can be fully used again. [Call#6998101] [Call#7101773] [Call#6999474]
- Notification emails for new voicemails are sent again if the Pre Answere module is enabled. [Call#7103619] [Call#7106114] [Call#7105888] [Call#7106779] [Call#7107078] [Call#7107659] [Call#7112234] [Call#7112935] [Call#7134089]
- With VM installations of STARFACE, both network interfaces can now be fully used again. [Call#7104770] [Call#7111021] [Call#7104171] [Call#7116453] [Call#7126819]
- Call2Go can be used for incoming calls to groups. [Call#6999668] [Call#7109877]
- The update and backup process has been improved. After automatically regenerating certificates, it is now possible to create backups again. [Call#7125170] [Call#7125427] [Call#7107063]
- The expiration date of a temporary license is now displayed.
- The Integration Log of STARFACE has been extended and improved.
- The error message 'This phone cannot be updated if automatic provisioning is disabled. Please contact your administrator!' is now no longer automatically hidden.
- An error message is now no longer displayed when exiting the 'Assign User Licenses' dialog box.
- Proxy settings are now taken into account when sending log files (and the HttpGetValue module function). [Call#6953286] [Call#1023934]
- Uploading GIF files for avatars is no longer possible. [Call#7112607]
- New installations of the STARFACE PBX now use the correct crypto policy.
- An IP address listed on the whitelist can now no longer be added to the blacklist.
- The NGN port is now displayed in the web UI in the same way as the position on the appliances.
- When multiple administrators edit the same user, they are now prompted to reload the user when changes are made.
- The request to change the hardware ID in license management is now handled correctly if it has expired.
- STARFACE now prevents the import of a backup while a backup is already being imported.
- The content of the module password field is now saved correctly when the module configuration is reopened after saving.
- The unhooked window for the logs is completely filled again.
- When adding licenses, an error message now appears in the popup for all mandatory fields that have not been filled in or have been filled in incorrectly.
- The web UI now no longer freezes when the phone is removed during administration.
- The entry in the 'Active Directory Domain' field is now validated and the user is notified if the entry was invalid.
- If the user has not made any changes in the 'Music on hold' settings, the user will no longer be notified that there were changes that should be saved.
- Fixed some issues in the connection settings for the LDAP address book.
- The Compact V1 and V2 appliances are recognized again according to their type after a RAM upgrade.
- During update and backup import, user avatars are now scaled to max. 320 pixels. [Call#6925448]
- The fallback login for the administrator now works again when the Active Directory server is unreachable.
- The WEB UI for 'Admin > Security' is now scrollable again.
- Das Drop Down Menü 'Admin > Benutzer > Rufnummern > Angezeigte Rufnummer' enthält nun alle zuweisbaren Rufnummer des Benutzers und wird scrollbar dargestellt, wenn die Liste der Rufnummern zu lang ist. Weiterhin wird die Liste der Rufnummern nun sortiert dargestellt.
- The width of the 'Login ID' column under 'Admin > Users > License Type Assignment' is now adjusted according to the length of the login IDs (up to max. 13 digits). [Beta-Feedback]
- After changing and saving the skills under 'Admin > User > Skills', the admin now returns to 'Admin > User > Skills'. [Beta-Feedback]
- The error message after failed backup due to unconnected USB media has been improved. [Beta-Feedback]
- When creating a new phone, the server address of STARFACE is now displayed only once. [Beta-Feedback]
- After importing a backup, the network address is now correctly displayed under 'Admin > System Status > System Summary > Network'. [Call#7107019] [Call#7138328] [Call#7141196] [Call#7138300]
- The changed settings under 'Time window for registration of mobile devices' for Gigaset N670/N870 are now saved. [Beta-Feedback]
- GET users/{userId}/phonenumberconfig/phonenumbers/{phoneNumberId} now returns a correct 404-NotFound if the phone number does not exist.
- When importing users as well as creating users via REST, the parent permissions must also be set to assign child permissions.
- User import - in case of errors when setting the avatar (empty file or zero length), the correct error reason is now returned.
- The GET /phonenumbers function now no longer returns numbers of type 'Invalid' if no explicit type was specified.
- The caller's phone number is now displayed correctly again in an iQueue interconnection.
- The phone number and the state of the users, is now displayed correctly in the Call Manager when transferring with *2.
- The external number selected during user creation is now set as the phone number to signal for outgoing calls.
- The web UI of the admin area of STARFACE now closes automatically when the services or STARFACE are restarted.
- Avatars are deleted across the plant network. [Call#6901863]
- The list of assigned phone numbers for iFMC is now displayed sorted. [Beta-Feedback]
- Calls via the 'CallPhoneNumber' module function that are forwarded to voicemail are now included in the voicemail list or the missed calls list entry.
- For call forwarding with consultation, the caller's phone number is now displayed more reliably in the Call Manager. [Call#7103121]
- The iQueue statistic reports scheduled for the second half of the day will now be created at the desired time.
- Sorting of phone numbers is now alphanumeric and takes into account country and area codes (tab: Users, Groups, Phone numbers).
- In the 'Phone numbers' tab, you can now search for the conference entry via text.
- Incoming group calls are now automatically displayed in the call list, provided that 'Update entries automatically' is active under 'Preferences -> Windows -> Call lists'.
- Filters with '&' in the name, now work properly in the call lists.
- Only one call list entry is now generated for parked calls. [Call#7103112]
- The Call Manager now accepts spaces in combination with other special characters e.g. -/() in the phone numbers. [Call#7103005]
- When using external mail servers, it is now correctly indicated that a password has been saved. [Call#7115534]
- After switching to internal mail server, it is no longer possible to edit the settings 'SMTP after POP3' and 'POP3 Server'.
- Several email templates have been corrected and updated.
- When resending an e-mail (missed call) from 'System status -> Reports', the sender is now displayed correctly. [Forum]
- Search for names with two or more digits now returns the correct result.
- It is now possible to import files with duplicate records into the address book. [Call#6996895]
- If multiple users are logged on to one phone, only the general folders of the address book are available for selection.
- Speed dial Numbers from the address book can only be assigned once. [Call#7106410]
- For calls on hold via the STARFACE clients, the user-defined music on hold is now played.
- If a user is using mobile apps but has no active phone/desktop apps assigned, when the push message fails to send, the call is treated as an 'Unavailable'.
- For incoming calls via NGN, all RTP streams are now transmitted correctly.
- When importing IPUIs/IPEIs, the correct IPUIs/IPEIs are imported in case of conflicts (duplicates).
- The Gigaset N670/N870 no longer receives the login information each time an action is performed on the handset.
- The keyboard mode on Yealink phones is now displayed correctly to the settings made on the phone.
- The Yealink T46U now supports three EXP 43 expansion modules.
- The function keys of the Yealink CP960 are correctly provisioned again.
- The display of new voicemails on end devices is now timely. [Call#6993499] [Call#7135019]
- When the Pre Answere module plays the announcement or music and the call is diverted to voicemail, an entry is now displayed in the voicemail list for group members.
- If there are no new voicemails, the correct greeting 'You have no new messages' is now played.
- The direct dial function keys can now also contain spaces in the destination number. [Call#7106389]
- The name of the park and orbit buttons is now changed when the assigned park and orbit parking space is changed.
- When the function key 'Display call number' is created, the key now receives the correct label.
- The naming of the function key 'Activate modules' is now correct.
- When switching the telephone (e.g. from FMC to desk phone), the prompt for saving the function keys no longer appears. [Beta-Feedback]
- The internal processes of call management (call handling) were improved.
- The search in the system reports has been improved.
- The UCI function 'getRedialList()' now returns correct data.
- The SIP line 'Telekom Company Flex' now works properly again. [Call#7160315][Call#7160957]
- In the 'Scheduled Redirection' module, the abbreviations 'Mo Di Mi Do Fr Sa Su' can now be used properly again. [Call#7157777] [Call#7159989] [Call#7160549] [Beta-Feedback]
- Important Notes:
- Version 7.1.1.7 Released on 2021/12/07
-
Features
- Important release notes
- In STARFACE 7.1.1, firmware updates for several telephone series were provided .
- According to our customers' feedback this not only fixed bugs for Yealink devices, but also introduced new bugs.
In close collaboration with Yealink, a new firmware has been built and integrated into STARFACE which solves these issues. - This release only updates the firmware for Yealink telephones.
Bugfixes
- Bugfixes
. In particular following the following bugs have been fixed by Yealink:- Yealink: It was possible to hear participants who were placed on hold. [Forum]
- Yealink: No audio transmission to Headsets attached via EHS adapters. [Call#7112637] [Call#7112941]
- Yealink: Incoming phone calls could not be answered on headsets when using EHS. [Call#7112624]
- Yealink: The display name will not scroll through anymore.
- Important release notes
- Version 7.1.1.6 Released on 2021/11/16
-
Features
- Highlights
- Yealink T46U telephone model is now supported.
- G.722 is now used in Interconnection.
- Firmware updates for many Yealink, Gigaset and Grandstream devices.
- When updating to STARFACE 7.x, please note that the update requires a minimum of 4 GB of free space.
- The Update from STARFACE 6 to STARFACE 7 is not available as a normal update. For appliances we have built a special module which performs an in-place update. Virtual installations need to be re-installed manually. See our Knowledge Base for more information.
- The update from STARFACE 7.0 and higher to STARFACE 7.1.1 can be installed as usual as a normal update via the web interface and does not require a new installation.
- Virtualized STARFACE installations now require at least 2GB RAM.
- We strongly recommend archiving your call lists, fax, voicemails and recorded phone calls as well as only using fully-qualified phone numbers in all modules.
- If you are using STARFACE Connect, please check your Routing settings after the update, as these may have changed.
- Before the installation, please check that your provider's siptrunk.de profile has been updated for STARFACE 7.
- Please note when purchasing new Yealink devices from the T5 series that they will likely be from a new hardware revision with a new chipset. To provision these devices, the new firmware version included in STARFACE 7.1.1 is required!
- After the update of Yealink T5x devices to firmware version 86, these devices cannot be downgraded to v85 or lower due to a manufacturer limitation.
- All partners wanting to use an alarmserver as Tomedo, Tenmo, etc. with Starface 7.1.x.x should note that a manual change of some name fields is required.
Please contact our Support before activating alarmservers on a Starface.
- G.722 is now used in Interconnection.
- It is now possible to track what was last done on the console and when, as the change log is time-stamped.
- Provider A1 Telekom Austria is now supported. (According to A1 SIP Guideline V4.1)
- The log message structure of all phone manufacturers in the Autoprovisioning log have been standardised.
- Yealink: Yealink T46U is now supported.
- Yealink T41S/T42S/T46S/T48S/T53/T54/T57: Update to firmware version 86
- Gigaset N670/N870: Update to firmware version 2.42
- Gigaset N510: Update to firmware version 259.
- Gigaset N720: Update to firmware version 116.
- Grandstream HT802/HT814: Update to firmware version 1.0.31.1.
Bugfixes
- Bugfixes
The following bugs have been fixed:- Fixed: Picking up a call from a group caused the call to be dropped after a few seconds. [Call#6992195] [Call#6995214] [Call#6991260] [Call#7101919] [Call#6993565]
- Fixed: Blind transferring a group call were automatically hung up if the call wasn't picked up within 30 seconds. [Beta]
- Fixed: Call grabbing/pickup via *8 was partially not possible. [Call#7105718] [Call#7107394]
- Fixed: Scheduled conferences did not work via iFMC. [Call#6997605]
- Fixed: Conferences based on an existing call haven't been displayed in the call lists. [Beta]
- Fixed: iFMC showed unknown phone number in Interconnection. [Forum]
- Fixed: Silence (DND) could not be deactivated in some cases. [Forum]
- Fixed: NGN lines did not register after updating from STARFACE 6 to STARFACE 7. [Call#7102489]
- Fixed: Call list showed accepted call also as missed. [Call#7103910]
- Fixed: Caller ID display did not work correctly in some cases. [Call#7102666] [Call#7107177]
- Fixed: Call durations were sometimes different between WebUI and App.
- Fixed: iQueue: The displayed waiting time in the WebUI was sometimes shorter than displayed in the apps.
- Fixed: iQueue: In the call list, accepted calls were sometimes displayed as missed.
- Fixed: Gigaset N670/N870: Bases crashed when trying to record an announcement for a voicemail box. [Call#6994110]
- Fixed: Gigaset N670/N870: Newly created, unconfigured handsets could not be deleted without prior configuration.
- Highlights
- Version 7.1.0.4 Released on 2021/10/04
-
Bugfixes
- Bugfixes
The following bugs have been fixed:- Fixed: Several Siptrunks periodically became unregistered. [Call#7104916] [Call#7104895] [Call#7104881] [Call#7104725] [Call#7104723] [Call#7104980] [Call#7104991] [Call#7104986] [Call#7105020] [Call#7105007] [Call#7105079]
- Fixed: It was possible for duplicate voicemail notification emails to be sent. [Call#7104731] [Call#7104744] [Call#7104909] [Call#7102329]
- Bugfixes
- Version 6.7.3.22 Released on 2021/10/26
-
Bugfixes
- Bugfixes
- Fixed: LDAP/AD connections have not been handled correctly by a pool and might not have been closed. [Call#6954744]
- Fixed: The server-connection to OpenFire as our communication service (UCI) has been stabilized. [Call#6954744]
- Bugfixes
- Version 7.1.0.3 Released on 2021/09/22
-
Features
- Highlights
- The handling of calls in the Mobile Apps has been unified and optimised.
- A new function key has been added with which a targetted redirection can be set for one or more of the user's own phone numbers.
- Busy Lamp Fields are now removed when the linked account has been deleted.
- As previously announced, the UCI 2.0 API has been marked as deprecated and will be removed in a future release.
- Important notes regarding this Release
- When updating to STARFACE 7.1, please note that the update requires a minimum of 4 GB of free space.
- The Update from STARFACE 6 to STARFACE 7 is not available as a normal update. For appliances we have built a special module which performs an in-place update. Virtual installations need to be re-installed manually. See our Knowledge Base for more information.
- The update from STARFACE 7.0 to STARFACE 7.1 can be installed as a normal update via the web-interface. A clean installation is not required when upgrading from STARFACE 7.0.
- Virtualized STARFACE installations now require at least 2GB RAM.
- We strongly recommend archiving your call lists, fax, voicemails and recorded phone calls as well as only using fully-qualified phone numbers in all modules.
- If you are using STARFACE Connect, please check your Routing settings after the update, as these may have changed.
- Before the installation, please check that your provider's siptrunk.de profile has been updated for STARFACE 7.
- As previously announced, the UCI 2.0 API has been marked as deprecated and will be removed in a future release.
- The Patton SN200 is supported as of STARFACE 7.0. It can be integrated via our Patton Wizard. Please refer to the Knowledge Base for more information.
- Support for the following telephones has been discontinued:
- Snom: Meeting Point, D305, D375, D710, D745
- Yealink: CP860, T21P, T23P, T27P/G, T29G, T40P, T40G, T41P, T42G, T46G, T48G, T49G
- Fanvil: X5S, X6
- Panasonic: KX-HDV130, KX-HDV230, KX-HDV330, KX-HDV340
- Security: A vulnerability in the Linux kernel has been closed.
- Security: The library used for the generation of PDF files (for example reports) has been updated and some layouts have been adjusted.
- Security: The Email Server can now be configured to use TLS, STARTLS and unencrypted connections to external systems, and certificate validation can now be enabled.
- Special phone numbers for Switzerland, Austria and Belgium have been updated.
- Apps: The Park & Orbit function key can now be used from within STARFACE for Windows. [Call#6924143]
- Apps: New UCI requests have been added to query iQueue statistics.
- Apps: Starface Mobile Apps (iOS, Android) now use Opus if activated in the STARFACE Administration panel.
- Apps: Call handling in the Mobile Apps has been unified and optimised.
- Added a new permission "Call Recording" which controls the ability to record calls by the user.
- New Function Key: A new function key has been added with which a targetted redirection can be set for one or more of the user's own phone numbers.
- Busy Lamp Fields are now removed when the linked account has been deleted.
- Modules: Licensed modules are now downloaded automatically when a valid license key for the respective module is added to the STARFACE.
- Web UI: Administrators can now define the codecs used by individual Softphone Apps.
- Web UI: The default number of lines displayed for lists has been increased to 20.
- The template for user imports is now a csv file.
- Web-UI: The online Knowledge Base is now also linked when the UI is set to French.
- The default subject of the email sent accompanying a planned conference is now the name of the conference.
- System notification emails now contain the hostname as well as the internal and external ip addresses of the STARFACE. [Call#1060412]
- Links in System notification emails now use HTTPS if HTTPS is activated in the administration panel.
- The error handling for the email server configuration has been improved.
- Error Reports now include a file containing pertinent information regarding the STARFACE installation (Installation type, CPU, RAM, date of first installation and the currrent installed version).
- The formatting of the log contents has been optimized for human readablility.
- The timestamp in the PBX log has been changed to match the timestamps of the other STARFACE logs to improve legibility.
- As previously announced, the UCI 2.0 API has been marked as deprecated and will be removed in a future release.
- Support for the long-outdated calendar entry format vCalendar (*.vcs) has been removed.
- Update of CentOS to Version 8.4
- Update of Asterisk to Version 16.19.0
- Gigaset / Security: For security reasons the administration password is now only provisioned once.
- Gigaset N670/N870: The current and maximum number of handsets which can be registered to the base station is now displayed in the respective configuration panel.
- Gigaset N670/N870: Firmware Update to v2.39.3
Bugfixes
- Bugfixes
The following bugs have been fixed:- Call lists displayed the number forwarding a call instead of the fowarded number. [Call#7103082]
- Security: The security of the AD integration has been improved.
- Fixed: A call could be hung up when transferring after consultation. [Call#6993962] [Call#6990042]
- Fixed: A call initiated via QuickDial key could not be declined.
- Fixed: In some configurations it was impossible to dial a 0800 number with an active line access prefix. [Call#6966834] [Call#6929081]
- Fixed: Calls could not be initiated using the call list entry on a desk phone. [Call#6994397] [Call#6992011] [Call#6996532] [Call#6992050] [Call#6993857] [Call#6994140] [Call#6998266]
- Fixed: Resolving incoming callnumbers did not display a company name, if first and last name had been missing. [Call#7102455]
- Fixed: The group number instead of the agent's information was displayed for incoming transfers and consulation calls. [Call#6989085] [Call#6994525]
- Fixed: It was possible to grab an already-answered phone call. [Call#6994130] [Call#6994245] [Call#6992812] [Call#6996099]
- Fixed: The group number sometimes incorrectly remained in the display number setting after leaving a group. [Call#6964604]
- Fixed: It was only possible to use one Park & Orbit parking lot per user.
- Fixed: The LDAP address book phone number resolution was incorrect with phone numbers signalled with a prefix. [Call#6933910]
- Fixed: LDAP/AD connections have not been handled correctly by a pool and might not have been closed. [Call#6954744]
- Fixed: Apps: No Push notification was sent when sending a Click2Dial call to a Mobile App.
- Fixed: Apps: The call was not always correctly ended when it was declined in the Mobile App for iOS.
- Fixed: Apps: The user state was not always correctly calculated when the user had an iPhone.
- Fixed: Apps: Avatars set via the Apps where not always correctly displayed.
- Fixed: Apps: Unnecessary UCI events were sent when a user logged in to an App.
- Fixed: Apps: The name of a group was not always displayed correctly when a new voicemail message was received. [Call#1069328]
- Fixed: Apps / iQueue: A ringing iQueue call could not always be declined via the UCI.
- Fixed: Apps / REST: The initial password change could reset some user settings.
- Fixed: Apps / REST: It was not possible to add participants to a planned conference if they did not have a telephone number.
- Fixed: REST: Fixed multiple errors in the FunctionKey API.
- Fixed: Module: The authentication in the "StarfaceRestRequest" module function did not work correctly.
- Fixed: Module: Modules were unable to correctly idenfify the phone number after a call was forwarded. [Call#6990819] [Call#6992401] [Call#6995135] [Call#6995005] [Call#6997013] [Call#6995624] [Call#6997309] [Call#6997624] [Call#6996699]
- Fixed: Module: Modules were deleted if the status of the module was checked.
- Fixed: Module: No push notification was generated when the module function "CallUser" was executed.
- Fixed: Module: The module function "CallphoneNumber" did not always signal the correct phone number.
- Fixed: iQueue: Callers were not always correctly prioritised by Priority-Based Routing when prioritising based on the caller number.
- Fixed: iQueue: Skill-Based-Routing did not always call the agents in the expected order. [Call#6971710] [Call#6964443] [Call#6993848]
- Fixed: iQueue: Rules were incorrectly applied when deleting skills.
- Fixed: iQueue: The call was displayed incorrectly when an iQueue call was forwarded to a voicemail box.
- Fixed: iQueue / Web UI: The calculation of average waiting time did not always return the correct result. [Call#6988945]
- Fixed: Internal extensions were not synchronised in the Interconnection. [Call#6904098] [Call#6945481]
- Fixed: Backup Import: It was possible for a backup import to not fully run, if announcements were excluded from the import.
- Fixed: The group number was incorrectly displayed on consultation calls. [Call#6989085] [Call#6994525]
- Fixed: Clouds: A non-existent line was selectable in the emergency call and call routing settings.
- Fixed: Clouds: It was possible to configure incompatible network settings.
- Fixed: The line prefix was ignored when sending a fax. [Call#6991601]
- Fixed: Increased the stability of retrieving a fax from the fax lists.
- Fixed: A port was not correctly applied when configuring an external email server.
- Fixed: Web UI / Security: File uploads were insufficiently validated and the interactions with the UI have been improved.
- Fixed: Web UI: The line status display was not always correct.
- Fixed: Web UI: User entries were not saved, if a redirection was not set to active.
- Fixed: Web UI: External phone numbers were not always displayed in the fully-qualified format.
- Fixed: Web UI: Entering a single character in the redirection target input field started a search.
- Fixed: Web UI: Updating a display filter did not work as expected.
- Fixed: Web UI: The error message was not clear enough when creating a duplicate Quickdial key.
- Fixed: Web UI: The password field in the user settings panel was not applied correctly.
- Fixed: Web UI: The hostname was not displayed in the information popup when changing network settings.
- Fixed: Web UI: The error messages displayed when required fields were left empty while configuring a backup schedule to SFTP and Windows Share targets have been corrected.
- Fixed: Web UI: Calls can no longer be forwarded to invalid users.
- Fixed: Web UI: The error messages in the network configuration did not cover all scenarios.
- Fixed: Web UI: The HTTPS redirection can now only be activated, if HTTP is active.
- Fixed: Web UI: Fixed miscellaneous minor display errors.
- Fixed: Web UI: Phone number selection for conference participants was not intuitive.
- Fixed: Web UI: Searching for a telephone number containing non-numeric characters did not always return the expected result.
- Fixed: Web UI: It was possible for an error to occur when creating a new SIP telephone profile.
- Fixed: Web UI: The "Test" option in the mail server configuration only used the previously saved values.
- Fixed: Web UI: The validation of Login-ID, name and surname did not work as expected with regards to minimum and maximum input length.
- Fixed: Web UI: Clicking an upload buttons caused all pending uploads within a form to be submitted.
- Fixed: Web UI: An unecessary warning was occasionally displayed when switching between tabs in the administration panel.
- Fixed: Web-UI: The phone number entry field now once again permits the entry of special characters. [Call#7103005]
- Fixed: Redirections activated with target "voicemail box" by default for users without a voicemail box.
- Fixed: The maximum number of backups to be stored on a Dropbox account was not properly applied. [Call#6964919]
- Fixed: Email addresses were incorrectly validated in multiple parts of the web ui (validation is now done according to RFC).
- Fixed: Call signalling was incorrect during ad-hoc conferences.
- Fixed: The NTP service is no longer active when the system time is set manually.
- Fixed: A held call was incorrectly displayed as forwarded.
- Fixed: Not all calls were taken into account when the current calls were displayed.
- Fixed: Some special characters were incorrectly encoded in emails sent by the STARFACE.
- Fixed: An incorrect error message was displayed when the license server was unable to be reached.
- Fixed: Error messages in the fax list were incorrect.
- Fixed: The server-connection to OpenFire as our communication service (UCI) has been stabilized. [Call#6954744]
- Fixed: Asterisk: The error message "Unable to determine asterisk version" will no longer appear in the respective logs.
- Fixed: Some email jobs were not logged to the "mail" log.
- Fixed: The address book category "job_tilte" has been corrected to "job_title". [Call#1073860]
- Fixed: All group members received "CONNECTED" UCI events when a call to a ring-all group was answered.
- Fixed: Deutsche Telekom: Special Action Codes were transmitted incorrectly. [Call#6971479] [Call#6979720] [Call#6984217]
- Fixed: New voicemail notifications did not always contain the caller's name.
- Fixed: The system resources for the Openfire service were not always correctly calculated.
- Fixed: Telephone names were limited to 14 characters.
- Fixed: Yealink: The OK-Button triggered an "Unknown URL" error message in the telephone menus.
- Fixed: Yealink: There was no "Back" button in the telephone menus. [Call#6953232]
- Fixed: Gigaset N670/N870: It was possible to enter more than 10 characters in the IPUI field.
- Fixed: Fanvil: The default tone scheme was "USA" and is now "Germany". [Call#6934319]
- Answering an incoming conference invite call generated by a planned conference on an iFMC device hangs up the call immediately.
- Duplicate call list entries can be generated when an iQueue agent answers incoming calls on a Mobile App.
- In rare cases, it is possible for calls with anonymous external participants to not be displayed in the call list.
- Highlights
- Version 7.0.2.1 Released on 2021/06/22
-
Features
- Important notes regarding this Release
- When updating to STARFACE 7.0, please note that the update requires a minimum of 4 GB of free space.
- The Update from STARFACE 6 to STARFACE 7 is not available as a normal update. For appliances we have built a special module which performs an in-place update. Virtual installations need to be re-installed manually. See our Knowledge Base for more information.
- Virtualized STARFACE installations now require at least 2GB RAM.
- We strongly recommend archiving your call lists, fax, voicemails and recorded phone calls as well as only using fully-qualified phone numbers in all modules.
- If you are using STARFACE Connect, please check your Routing settings after the update, as these may have changed.
- Before the installation, please check that your provider's siptrunk.de profile has been updated for STARFACE 7.
- The UCI versions 2.0, 2.1 and 2.2 will be marked as DEPRECATED in an upcoming release and completely removed at a later date.
- Additional security filters have been added to prevent novel attacks.
- Gigaset N670/N870: Firmware update to Version 2.39.1.
Bugfixes
- Bugfixes
The following errata have been fixed.- Fixed: In some system configurations, it was possible for phone calls via encrypted SIP providers to be cancelled immediately after they were connected.
- Fixed: In some system configurations, it was possible for phone calls which were placed on ISDN BRI telephone devices to not be dialled correctly. [Call#6992339] [Call#6993533] [Call#6993299] [Call#6993322]
- Fixed: Apps / REST: BLFAccountID error messages were ambiguous.
- Fixed: Open HTTP/HTTPS connections were sometimes not correctly closed.
- Fixed: Gigaset N670/N870: Gigaset-Bases crashed on voicemail message playback. [Call#6988005] [Call#6990136]
- Fixed: Gigaset N670/N870: It was not possible to register new Gigaset base stations.
- Important notes regarding this Release
- Version 7.0.1.8 Released on 2021/05/17
-
Features
- Highlights
- Added Support for encrypted STARFACE Connect.
- Telekom CompanyFlex Complete Unencrypted (NGN), Telekom CompanyFlex Complete Encrypted (NGN) and Telekom CompanyFlex Pure are now supported.
- Important notes regarding this Release
- When updating to STARFACE 7.0, please note that the update requires a minimum of 4 GB of free space.
- The Update from STARFACE 6 to STARFACE 7 is not available as a normal update. For appliances we have built a special module which performs an in-place update. Virtual installations need to be re-installed manually. See our Knowledge Base for more information.
- STARFACE 7 is incompatible with the following EOL Appliances: Light v1, Light v2, Light v3, Pro v1, Pro v2, Enterprise v1, Enterprise v2, Advanced v1.
- Virtualized STARFACE installations now require at least 2GB RAM.
- We strongly recommend archiving your call lists, fax, voicemails and recorded phone calls as well as only using fully-qualified phone numbers in all modules.
- If you are using STARFACE Connect, please check your Routing settings after the update, as these may have changed.
- Before the installation, please check that your provider's siptrunk.de profile has been updated for STARFACE 7.
- The Firefox setting 'network.http.sendRefererHeader' must be set to its default value "2". Other values may cause problems in the administration panel and the iQueue Widget.
- Older versions of the UCC and Mobile Clients are not fully compatible with STARFACE 7. Please update them together with your STARFACE PBX.
- The STARFACE Push infrastructure for the mobile apps has been overhauled for STARFACE 7. You may need to change your Firewall settings to reflect this change. The host for the push servers has been changed and is now "push-cluster.starface.de", and the IP addresses have also changed to 37.120.181.70, 46.38.248.58 und 46.38.248.91. Whitelisting TCP traffic to port 443 for these hosts is required.
Bugfixes
- Bugfixes
The following bugs were fixed.- Fixed: Users of type "User Light" cannot use the address book. [Call#6989191] [Call#6988908]
- Fixed: The Asterisk "full" log files were not deleted correctly.
- Fixed: The system partition is created with a size of max. 50GB. [https://support.starface.de/forum/showthread.php?8972-Starface-7-0-0-19-gr%F6%DFe-nur-50-GB]
- Fixed: Ringing of non-existent calls to mobile clients (ghost calls) when the call has already been rejected.
- Fixed: In some cases, calls could not be transferred with Yealink phones.
- Known Issues
- Highlights
- Version 7.0.0.19 Released on 2021/04/20
-
Features
- Highlights
- STARFACE 7 is the latest release for STARFACE telephone systems, bringing new technologies to your STARFACE PBX! Many of the underlying systems and techologies have been updated and reworked, in particular the operating system and the Asterisk SIP Server, upon which our Call-Handling logic is built. The new STARFACE 7 is vastly superior, safer and is more future-proof than any other previous version!
- Important notes regarding this Release
- When updating to STARFACE 7.0, please note that the update requires a minimum of 4 GB of free space.
- STARFACE 7 is not available as a normal update. For appliances we have built a special module which performs an in-place update. Virtual installations need to be re-installed manually. See our Knowledge Base for more information.
- STARFACE 7 is incompatible with the following EOL Appliances: Light v1, Light v2, Light v3, Pro v1, Pro v2, Enterprise v1, Enterprise v2, Advanced v1.
- Virtualized STARFACE installations now require at least 2GB RAM.
- We strongly recommend archiving your call lists, fax, voicemails and recorded phone calls as well as only using fully-qualified phone numbers in all modules.
- If you are using STARFACE Connect, please check your Routing settings after the update, as these may have changed.
- Before the installation, please check that your provider's sipcheck.com profile has been updated for STARFACE 7.
- Older versions of the UCC and Mobile Clients are not fully compatible with STARFACE 7. Please update them together with your STARFACE PBX.
- The STARFACE Push infrastructure for the mobile apps has been overhauled for STARFACE 7. You may need to change your Firewall settings to reflect this change. The host for the push servers has been changed and is now "push-cluster.starface.de", and the IP addresses have also changed to 37.120.181.70, 46.38.248.58 und 46.38.248.91. Whitelisting TCP traffic to port 443 for these hosts is required.
- New features
In addition to the update of fundamental system components and the introduction of many new features, the following changes have been made to the system:- Address book folders can now be emptied and deleted.
- New module function "DeactivateModuleInstance" to deactivate the current module instance.
- The last 5 days of the Asterisk system log are now included in the logfiles when they are submitted to STARFACE Support.
- Improved error handling when the internal number area is exhausted. [Call#6913807]
- The administration panel can now be resized.
- The default Logging level for the autoprovisioning log is now Debug, not Trace. [Call#6956081]
- Data protection: A user's voicemail boxes are now deleted with the user.
- Dropbox backups larger than 150MB are now possible.
- The DNS-tree continues to be searched even when a DNS server returns "no such name" for a request (fixes in particular an error produced by Windows Server 2012 name servers).[Call#6954541] [Call#6966855] [Call#6966926] [Call#6966402] [Call#6967083]
- The email notification sent when the storage is close to being full now contains the directory listing sorted by size.
- Searching for telephone numbers is now significantly faster. [Call#1078324]
- A STARFACE server license can now be added to the system before importing a backup during the initial configuration of the system.
- Fanvil: Do not disturb status of the logged-in user is now displayed on the telephone.
- Yealink: Firmware update to version 85 for CP960, T41S, T42S, T46S, T48S, T53, T53W, T54W, T56A, T57W, T58A, T58A with camera and VP59.
- Gigaset N510: Firmware update to version 258. [Call#6945489] [Call#6949826] [Call#6950198] [Call#6958371] [Call#6958993] [Call#6969532] [Call#6972955]
- Gigaset N670/N870: Firmware update to Version 2.39.0.
- Gigaset N670/N870: Added support for the "Integrator" role (requires additional license which can be purchased seperately from Gigaset).
- Gigaset N720: SL800H PRO and S700H PRO handsets can now be used with Gigaset N720 DECT systems.
- Snom: The "right" button now displays system notifications, as intended by Snom.
- New Module: Upload of root-certificate for encrypted Active Directory/LDAPS services.
- The distribution of internal system resources has been optimized.
- Push for Mobile Clients: The contents of chat messages is now encrypted and sent inside the Push Notification.
- REST: All endpoints now use 401 and 403 responses where appropriate.
- REST: Automatic assignment of UCC-Premium and Terminal-Server permissions can now be deactivated.
- REST: Added new endpoints /server/restart and /server/shutdown to aid with system management.
- REST: New endpoints for configurinng the system time and timezone.
- REST: The default permission schema can now be optionally applied when changing the user license-type (User to User-Light and vice-versa).
- The default permission scheme can now be applied when changing the user license type (User to User Light and vice-versa).
- Security: Added support for TLS 1.3.
- Security: STARFACE only supports TLS 1.2 and higher.
- Security: Disabling weak TLS 1.2 ciphers.
- SIP INVITEs to DeutschlandLAN SIP-Trunks now contain the SIP-server name instead of its IP-Address. [Call#6958402] [Call#6958873] [Call#6961758] [Call#6963014] [Call#6961512]
- STARFACE NEON video meetings can now be scheduled and joined from the Web interface.
- Support of SMB3.
- When sending log files to STARFACE Support, the settings for internal resource usage are now also sent.
- The STARFACE UCC and Mobile Clients have been rebranded to STARFACE Apps.
- Special phone numbers for France have been updated.
- The root password for appliances and virtualized installations now be set in the initial configuration wizard.
- UCC Clients
Bugfixes
- Bugfixes
- Fixed: After a reboot, conference reminder emails were not sent for about 15 minutes.
- Fixed: Allowed requests per IP raised from 500 to 1000 per 20s. [Call#6960059]
- Fixed: CA-Certificates uploaded by the customer for encrypted AD/LDAPS were not persisted through updates and backup imports.
- Fixed: Chat messages belonging to deleted users were only deleted from the server after 90 days. [Call#6937058]
- Fixed: Call lists were not written directly after ending a call
- Fixed: Call Lists showed an incorrect caller number if "call waiting" was deactivated. [Call#6934051] [Call#6939358] [Call#6911688]
- Fixed: Chat status was displayed in the UCC Clients when the permission to set one was not assigned to the user.
- Fixed: Change of line number in logging window was not always applied.
- Fixed: Click2Dial was signaling iFMC number.
- Fixed: Conference invitations: The auto-generated calendar entry did not have an end-time.
- Fixed: Control codes are not possible on direct dial keys. [Call#6902690] [Call#1060302] [Call#6910466]
- Fixed: Display error when expanding "Exit code" in the line area.
- Fixed: Display error when notifying unsaved changes in groups.
- Fixed: Display error in the web interface when trying to make a call repeatedly without a phone via BLF or speed dial.
- Fixed: Display error for "Disconnect attachment" button in attachment group settings.
- Fixed: Display error with diacritic characters in conference invitations. [Call#6924378]
- Fixed: Emails were not sent if one of the recipients had an invalid email address.
- Fixed: Error when setting the call displays.
- Fixed: Error in signaling in system network.
- Fixed: Error when sending fax.
- Fixed: Error in the Mail2Fax function. [Call#1075326]
- Fixed: Error in the phone number search in the administration panel.
- Fixed: Faulty signaling when redirecting to a voicemail box.
- Fixed: "grabcall" was not displayed on the telephone when picking up an incoming call.
- Fixed: Incoming calls to a group member were not picked up via the Star-Dial *8 if the phone call was delivered directly to the user.
- Fixed: Invalid entries in personal call list filters were not discarded.
- Fixed: It was possible for an undeleteable call manager entry to be generated if the user attempted to join an inactive conference.
- Fixed: It was possible for users of type "User Light" to be named as conference moderators.
- Fixed: It was possible to assign one more UCC Premium right than was actually available.
- Fixed: It was not possible to import users via CSV file if this file's extension was in upper-case. [Call#6959718]
- Fixed: It was possible for a user to own a softphone despite not having the UCC-Premium permission. [Call#6931534] [Call#6939595]
- Fixed: It was not possible to start a phone call from a UCC Client with a Mobile Client for iPhone if it was in the background (CTI).
- Fixed: iQueue agent does not get post-processing time after grabbing.
- Fixed: iQueue was not available if the internal and external phone numbers were identical. [Call#1067406]
- Fixed: iQueue call list entry was missing when the call was answered with an iFMC device.
- Fixed: iQueue evaluation could keep missed calls as answered under certain circumstances when no agent had rung.
- Fixed: LDAP connections were not correctly closed.
- Fixed: Licenses for UCC Premium, Terminal Server and the integration with Microsoft Teams were not active while the server license registration was not yet confirmed.
- Fixed: License dialog remained open when trying to use an active license of another system.
- Fixed: Logging: Auto-update when viewing logs in faded out window did not work if it was already selected before.
- Fixed: Long lists in license management could not be scrolled.
- Fixed: Managed conferences continued to call participants who missed the conference, even after the conference had finished.
- Fixed: Missing upper limit for entries per page in address book.
- Fixed: Missing error handling if a backup file was too large for uploading to Dropbox. [Call#6952044]
- Fixed: Mobile Clients would ring if registered on multiple systems.
- Fixed: Module function GetCallState mandatorily required a user.
- Fixed: Navigation error when taking over function keys in the web interface.
- Fixed: Only one redirection was displayed in the web interface.
- Fixed: Path pass in module function UnzipFile.
- Fixed: Phone calls were incorrectly signally when started or answered via a TAPI client.
- Fixed: Push notifications were sent to an iPhone when the user did not have the UCC-Premium permission. [Call#6931534] [Call#6939595]
- Fixed: Redundant STARFACE PBX sent duplicate mails. [Call#6934315] [Call#6941828]
- Fixed: Repeating managed conferences were not removed when a user was deleted.
- Fixed: REST: Fixed a security vulnerability in the REST API.
- Fixed: REST: BLF could be created for non-existent user.
- Fixed: REST: Error in the naming of address book blocks. [Call#6946313] [Call#6951806]
- Fixed: REST: The phone type was not specified. [Call#6967376]
- Fixed: REST: query for a non-existent mailbox returned an error.
- Fixed: REST: Numerous bug fixes in the REST interface.
- Fixed: Security: Active Directory settings now default to "TLS with certificate validation".
- Fixed: SIP video codecs may not be listed first.
- Fixed: Starface Cloud: phones are configured to use the NTP server directly. Please make sure port 123 is open for your 1st configured NTP server.
- Fixed: Subscribers with special characters in their phone number (e.g. brackets) could not be invited to a conference. [Call#6940202]
- Fixed: Some Swiss special phone numbers were not included. [Call#1076764]
- Fixed: The caller id was not always updated correctly when transferring a call after consultation via the call manager in the web interface.
- Fixed: The last digit of 5-digit phone names was unintentionally clipped.
- Fixed: The module function SetForwardForAccount did not work.
- Fixed: The module system no longer crashes if the class InvocationInfo was used in multithreaded situations. [Call#6932672]
- Fixed: The name of a quick-dial key was overwritten if a user from the address book was selected.
- Fixed: The permission "Show call forwarding targets" did not work in all cases (e.g. was not respected by the UCC Clients for administrator accounts). [Call#6927969]
- Fixed: The pcap network trace in the administration panel "Diagnotics" could be unintentionally interrupted. [Call#6902432]
- Fixed: The signalling number was not automatically set when adding the first external number to a user.
- Fixed: The system update email notification only contained the external system address.
- Fixed: The update progress appeared to stall in step 2 when the web interface was opened via HTTPS. [Call#6919729]
- Fixed: The Web interface was not reloaded when the display language of a user was changed.
- Fixed: Telephones: Address book entries containing diactrics (umlauts) were not searchable.
- Fixed: A typographic error in the fax cover sheet was fixed.
- Fixed: Update process could not be started successfully from setup dialog.
- Fixed: Users remained logged in when their Login-ID was changed.
- Fixed: WEB-UI and UCC behave differently with "Display chat status" permission. [Call#6935168]
- Fixed: Yealink T57W: Power keys 28 and 29 not usable. [Call#6934302] [Call#6934206] [#6937130] [Call#6977937] [Call#6949910] [Call#6974595] [Call#6978237]
- Fixed: Yealink: A telephone-specific redirection could be activated by pressing the "Transfer" key without an active call.
- Fixed: Snom telephones remained unregistered after they were edited in the administration panel.
- Fixed: Gigaset N870/N670: No error handling if an IPUI is used multiple times.
- Fixed: Gigaset N870/N670: Accessing the address book via a handset did not work on some cloud systems.
- Fixed: Fanvil X5/X6/X7: DND status was not updated when DND was activated via function key.
- Fixed: Fanvil X2/X3/X4: The STARFACE Menu had excessively long loading times.
- Fixed: Panasonic: DHCP was active after the device was autoprovisioned. [Call#6935379]
- Fixed: Outbound calls were sometimes listed as inbound. [Call#6963063][Call#6908033][Call#6936002][Call#6935888][Call#6948959][Call#6931320]
- Fixed: The module designer did not mark all functions with problems.
- Fixed: An incorrect avatar was sometimes displayed after a call was picked up.
- Fixed: A CCBS (Call Completion to Busy Subscriber) attempt was sometimes unable to be stopped.
- Fixed: It was not possible to pick up an iQueue call if an instance of the Pre-Answer module was set up to intercept calls to the iQueue number. [Call#6902621]
- Fixed: Call2Go called the telephone which triggered the Call2Go request.
- Fixed: The CCBS progress bar was not displayed in the STARFACE App for Windows.
- Fixed: Inviting a participant to an ad-hoc telephone conference would sometimes end the conference call.
- Fixed: Die UCI method UciQueueRequests.getQueueCalls() now also returns connected iQueue calls.
- Fixed: CallerIds set by modules were not applied to phone calls when the module instance was executed in the "on outgoing calls per used line" call stage.
- Fixed: The parameter "Ringing Duration" was not respected when set in the module function CallPhoneNumber. [https://support.starface.de/forum/showthread.php?8789-STARFACE-7-0-0-2-CallPhoneNumber-gt-Ringing-duration-wird-ignoriert]
- Fixed: It was not possible to forward an inbound call to voicemail.
- Fixed: The Security Advisor whitelist entry for the Cloud Reverse Proxy was sometimes removed when a phone device was deleted (only applies to STARFACE Clouds). [Call#6962969]
- Fixed: It was not possible to answer some incoming calls on the STARFACE App for iOS.
- Fixed: Module instances were erroneously deactivated if a hardware change was detected. [Call#6985215]
- Fixed: Only the first ten lines were displayed in the line configuration area of the administration panel.
- Fixed: Miscellaneous layout issues in the Web-UI were fixed.
- Known Issues
- Highlights
- Version 6.7.3.20 Released on 2021/02/08
-
Features
- Highlights
- A security issue inside the operating system was fixed.(CVE-2021-3156)
- Highlights
- Version 6.7.3.11 Released on 2020/09/14
-
Features
- Highlights
- This Service Release adds support for LDAPS (LDAP over SSL) for address book access and user authentication.
- Preparation for STARFACE NEON Video Meetings: This release is the minimum required version for STARFACE NEON Video Meetings to work as soon as STARFACE NEON will be officially release.
- The Fanvil X7 phone model is now supported.
- Important Information about this Release
- When updating to STARFACE 6.7.3, please note that the update requires a minimum of 4 GB of free space.
- The following appliances will be considered "End of Life" by STARFACE as of 30 September 2020: Light v1, Light v2, Light v3, Pro v1, Pro v2, Enterprise v1, Enterprise v2, Advanced v1. They will not be supported by STARFACE any more. Furthermore, software version STARFACE 7 (expected in Q1 2021) will not run on several of these appliances.
- The entire OpenStage series of Unify will be considered "End of Life" by STARFACE as of 1 January 2021. The phones will continue to be autoprovisioned, however STARFACE will no longer support or maintain these devices from this date onwards.
- We recommend reducing the size of the call data record with the module "STARFACE Archivierung", and to ensure that fully-qualified phone numbers are used in all module configurations.
- If you are using STARFACE Connect, please check the line routing settings to ensure that it is using the highest routing priority.
- Before you install you should check if your provider profile has been updated on SIPCHECK.COM.
- It is necessary to use the latest version of the UCC client in combination with the latest version of the telephony system.
- New Features
- Fanvil: The Fanvil X7 phone model is now supported.
- Fanvil: New MAC address range added to ensure compatibility with future Fanvil phones.
- Fanvil: Do Not Disturb (DND) is now displayed on the phone's screen.
- Fanvil: Users can now perform an attended transfer by pressing the BLF key of a user when a call is held and another call is active. [Call#6920236]
- Improved audio stability for SIP trunks (e.g. DeutschlandLAN), transfers, and Clients, by updating strictrtp. [Call#6948149] [Call#6941909] [Call#6935182] [Call#6941943] [Call#6948278] [Call#6937018] [Call#6944414 ] [Call#6950487] [Call#6956092]
- Integration into Microsoft Teams: A new permission is added to allow or disallow users the use of the integration into Microsoft Teams.
- Country codes from the lines are now provided for Gigaset N870/N670 [Call#6936247]
- Logfiles can now be sent to STARFACE Support even if no users has the permission "admin_mail" assigned.
- Modules: Always show XML-RPC endpoint in module designer.
- REST: Adding users via REST does not require a licenseType anymore.
- STARFACE NEON preparation: New permission to allow or disallow the use of STARFACE NEON Video Chats on a per-user basis (becomes available when STARFACE NEON becomes available). The permission will be assigned to all users by default. Furthermore, STARFACE NEON will register with STARFACE NEON servers when activated and exchanges keys for authentication. STARFACE NEON is not yet officially available, but this release will be required to use it when it will become available.
- Support for LDAPS (LDAP over SSL) for address book access.
- Support for LDAPS (LDAP over SSL) for user authentication via Active Directory.
- Users with User Light license cannot be assigned administrator permissions in the user creation screen in order to prevent confusion.
- Snom: Standard output device when used with UCC Client is now the handset.
- Snom: New background image for Snom D785. [Call#6948040] [Call#6955487] [Call#6958958]
- Cloud systems: SIP Settings in Network tab are available again, after they had been greyed out in earlier versions.
- The error report form does not require a strict date format any more.
- Module "Archivierung": Field "Number of days" is now a text input field. It is not necessary any more to choose from a predefined list of values.
- UCC Clients
Bugfixes
- Bugfixes
- Fixed: A warning sign was shown in the administration area for UCC Clients and Mobile Clients that were disconnected during an update.
- Fixed: Gigaset N720: Umlauts in address book entries were displayed incorrectly. [Call#6945318]
- Fixed: Gigaset N870/N670: Address book was not accessible on cloud systems with long names. [Call#6959094]
- Fixed: Module functions for setting redirections (Redirect.setredirectsetting and SetForwardForAccount) did not work. [Call#6954872]
- Fixed: Module Zeitgesteuerte Umleitung: Module now works with French localisation.
- Fixed: Redundancy Module did not work because synchronization failed. [Call#6955076] [Call#6956322]
- Fixed: Snom D785: The button for ad-hoc conference calls was missing. [Call#6955687]
- Fixed: Yealink T58A/VP59: The displayed showed keys for the local address book and call list, while the phone was supposed to use server-side address book and call lists.
- Call Lists: Call listed in wrong direction when picked up from lock screen of Mobile Client for iPhone.
- Module system: Class InvocationInfo was not threadsafe and could crash. [Call#6932672]
- Known Issues
- The German language package for the Snom D120 is not currently available.
- Highlights
- Version 6.7.2.2 Released on 2020/07/01
-
Features
- Highlights
- This Service Release splits the "Pickup" permission into caller visibility during ringing and busy phase.
- Some changes have been made to improve the experience with Snom phones and cloud systems.
- Important Information about this Release
- When updating to STARFACE 6.7.2, please note that the update requires a minimum of 4 GB of free space.
- The following Snom phones will be considered "End of Life" by STARFACE as of 30 June 2020: 710, 720, 760, D710. They will continue to be autoprovisioned, however STARFACE will no longer support or maintain these devices from this date onwards.
- The following Gigaset PRO phones will be considered "End of Life" by STARFACE as of 30 June 2020: DE310 IP PRO, DE410 IP PRO, DE700 IP PRO, DE900 IP PRO. They will continue to be autoprovisioned, however STARFACE will no longer support or maintain these devices from this date onwards.
- The following appliances will be considered "End of Life" by STARFACE as of 30 September 2020: Light v1, Light v2, Light v3, Pro v1, Pro v2, Enterprise v1, Enterprise v2, Advanced v1. They will not be supported by STARFACE any more. Furthermore, software version STARFACE 7 (expected at the end of 2020) will not run on several of these appliances.
- We recommend reducing the size of the call data record with the module "STARFACE Archivierung", and to ensure that fully-qualified phone numbers are used in all module configurations.
- If you are using STARFACE Connect, please check the line routing settings to ensure that it is using the highest routing priority.
- Before you install you should check if your provider profile has been updated on SIPCHECK.COM.
- It is necessary to use the latest version of the UCC Client in combination with the latest version of the telephony system.
- New Features
- Pickup permission split into caller visibility during ringing and busy phase.
- Mobile Client for iPhone: Send encrypted call data with push message in order to comply with Apple's new Push Service rules.
- Cloud: Some network settings cannot be changed for cloud systems in order to prevent misconfiguration
- Fanvil: SIP credentials will be provisioned only once. For all further provisionings, the phones must be enabled first in the admin panel.
- Snom 715: Firmware update to 10.1.51.12.
- Snom 725: Firmware update to 10.1.51.12.
- Snom D120: Firmware update to 10.1.51.12.
- Snom D305: Firmware update to 10.1.51.12.
- Snom D315: Firmware update to 10.1.51.12.
- Snom D345: Firmware update to 10.1.51.12.
- Snom D375: Firmware update to 10.1.51.12.
- Snom D385: Firmware update to 10.1.51.12.
- Snom D712: Firmware update to 10.1.51.12.
- Snom D717: Firmware update to 10.1.51.12.
- Snom D735: Firmware update to 10.1.51.12.
- Snom D745: Firmware update to 10.1.51.12.
- Snom D765: Firmware update to 10.1.51.12.
- Snom D785: Firmware update to 10.1.51.12.
- Snom: The web login is only provisioned once to the phone.
- Yealink: The web login is only provisioned once to the phone.
- UCC Clients
Bugfixes
- Bugfixes
- Fixed: Could not start chat with internal user from address book. [Call#6933408]
- Fixed: In a rare case, a call was not displayed in the call data records. [Call#6944122]
- Fixed: Medium-severity bug in jQuery. [Call#6951147] [CVE-2019-11358]
- Fixed: Mobile Client for iPhone signals call from oneself if used as the only phone for the user.
- Fixed: Snom: NTP service did not work with cloud systems.
- Fixed: Snom: Voicemail key did not work with cloud systems.
- Known Issues
- Yealink phones T58A and VP59 will display icons for the phone's address book and call lists. We will remove these icons with an upcoming release.
- The German language package for the Snom D120 is not currently available.
- Highlights
- Version 6.7.1.23 Released on 2020/05/12
-
Features
- Highlights
- This Service Release fixes a bug in version 6.7.1.20 that prevented Snom phones to work after an update in some cases.
- Important Information about this Release
- When updating to STARFACE 6.7.1, please note that the update requires a minimum of 4 GB of free space.
- We recommend reducing the size of the call data record with the module "STARFACE Archivierung", and to ensure that fully-qualified phone numbers are used in all module configurations.
- If you are using STARFACE Connect, please check the line routing settings to ensure that it is using the highest routing priority.
- Before you install you should check if your provider profile has been updated on SIPCHECK.COM.
- It is necessary to use the latest version of the UCC client in combination with the latest version of the telephony system.
Bugfixes
- Bugfixes
- Fixed: In version 6.7.1.20, a certificate-related bug prevented Snom phones to work after an update in some cases.
- Known Issues
- The German language package for the Snom D120 is not currently available.
- Highlights
- Version 6.7.1.20 Released on 2020/03/11
-
Features
- Highlights
- This Service Release further improves the handling of SIP passwords and the telephones' web-interface passwords. In the course of the Yealink security gap in the auto-provisioning service, we have further optimized in this regards.
- The new STARFACE Compact SIP appliance is now supported.
- VM-Server licenses are not longer lost when the virtual hardware is changed.
- Gigaset N670: The Gigaset N670 Single-Cell-DECT-System is now supported.
- Yealink VP59: The Yealink VP59 is now supported.
- Permissions: The automatic assignment of the UCC-Premium permission can now be deactivated.
- Permissions: The automatic assignment of the Terminal-Server permission can now be deactivated.
- Module function: Chat messages can now be sent from modules to users.
- User Light: Users with the license type "User Light" can now no longer log in to the web interface, the UCC Clients and the REST interface in accordance with the product definition. See below for more information.
- Important Information about this Release
- When updating to STARFACE 6.7.1, please note that the update requires a minimum of 4 GB of free space.
- The UCC Client for Windows will no longer support Windows 7 from 31 December 2019. From 1 January 2020, we will only be providing support and maintenance for the UCC Client for Windows if it is run on Windows 8 or newer (or the respective Windows Server version (from Windows Server 2012 or newer)).
- Please note that we have combined two permissions regarding the visibility of caller IDs to a single permission. Please check if any change of configuration is necessary. Further information can be found here.
- We recommend reducing the size of the call data record with the module "STARFACE Archivierung", and to ensure that fully-qualified phone numbers are used in all module configurations.
- If you are using STARFACE Connect, please check the line routing settings to ensure that it is using the highest routing priority.
- Before you install you should check if your provider profile has been updated on SIPCHECK.COM.
- It is necessary to use the latest version of the UCC client in combination with the latest version of the telephony system
- New Features
- Snom & Yealink: Improved STARFACE update mechanism prevents the loss of configuration settings on the device during a phone's update: After a firmware update as a result of a STARFACE update, Snom and Yealink phones can receive their SIP and phone menu passwords as often as they want within a period of 20 minutes.
- A new button in the Phone menu allows the generation and transmission of new SIP passwords for all phones.
- Phone list: Re-transfer SIP and Admin credentials from the context menu.
- Snom & Yealink: Provisioning timeframe for SIP and phone menu passwords introduced. After initial configuration of a phone, SIP and phone menu passwords are no longer provisioned. The STARFACE administration interface allows you to enable transmission for a 20-minute window.
- Faster detection of unavailable phones after a timeout of 60 seconds. Does not work in all scenarios for Snom devices.
- Snom & Yealink: For security reasons, administration passwords are only transferred once.
- Yealink and Snom: The password set in STARFACE for the web interface of the phones is only transmitted to the phones once. It is only retransmitted after a new change.
- Yealink: The VAR user in the phone web interface has been disabled for security reasons.
- User Light: Users with the license type "User Light" can now no longer log in to the web interface, the UCC Clients and the REST interface in accordance with the product definition.
- User Light: The license type is now displayed in relevant sections of the Administration Panel.
- User Light: A Wizard will aid the initial assignment of User Light licenses to the correct users after the update.
- User must now change their password on their first login.
- The phone numbers of external telephone conference participants are now detected more accurately when line prefixes and provider service features are used.
- Chat messages can now be sent from modules to users.
- The STARFACE will now check for new updates during the night of Monday to Tuesday.
- The external number in the user import demo file is now fomatted correctly [Call#6901188] [Call#6917591] [Call#6931936] [Call#6933836]
- The email containing new user credentials can now be deactivated.
- The amount of iQueue groups in use is now sent to our license server. This is needed to allow iQueue licenses to be rented via "STARFACE 365".
- The setting "seperate download and update" is now correctly persisted. [Call#6932477]
- Gigaset N670: The Gigaset N670 Single-Cell-DECT-System is now supported.
- Gigaset N870: Firmware-Update to Version 2.23.0.
- Gigaset N870: It is now possible to use more than one N870 DECT Manager on one STARFACE PBX.
- Gigaset N870: Call lists and the address book can now be accessed from the centre button on handsets.
- The HttpGetValue function now respects proxy settings in the server configuration.
- The message displayed when insufficient licenses are available has had new values added to it (User Light, deactivated users, users without a license type assigned to them).
- Patton Smartnodes are now provisioned with the correct CID-Format.
- Permissions: The automatic assignment of the UCC-Premium permission can now be deactivated.
- Permissions: The automatic assignment of the Terminal-Server permission can now be deactivated.
- REST: The entire REST request is now logged when the restfull-interface log is set to TRACE.
- REST: New endpoints for PBX licenses have been added.
- REST: New endpoints for web server settings have been added.
- REST: A new endpoint has been added to configure the system default language.
- REST: A new endpoint has been added to request the server version.
- REST: The YAML file now contains read-only annotations for respective fields.
- Security: STARFACE now will only install signed packages. [Call#6927643]
- When users are deactivated due to missing licenses, at least three administrators will remain active which have the ability to add licenses to the system.
- Snom D712: Firmware update to 8.9.3.60.
- Snom D785: New background image.
- Snom Telephones: Firmware updated to 10.1.42.14 for all devices currently provisioned with the Version 10 firmware. [Call#6926118]
- The new STARFACE Compact SIP appliance is now supported.
- Updates are now downloaded via HTTPS. [Call#6927643]
- VM-Server licenses are not longer lost when the virtual hardware is changed.
- Yealink VP59: The Yealink VP59 is now supported.
- Yealink T41S, T42S, T46S, T48S: Firmware update to 66.84.150.6
- Yealink T54W: Firmware update to 96.84.150.8
- Yealink T57W: Firmware update to 97.84.150.5
- UCC Clients
Bugfixes
- Fixed: Changing a user's language did not change the language of voice prompts and announcements.
- Fixed: Calls from a Mobile Client for Android could not be forwarded in the UCC Client for Windows.
- Fixed: An incorrect announcement was played when attempting to log off from telephone without the appropriate permission.
- Fixed: Users deactivated due to insufficient licensing were only fully reactivated after a server restart when licenses were added to the system.
- Fixed: The primary external numbers of users were not always updated when deleting a line.
- Fixed: Corrected a bad link to the manual in the login screen. [Call#6933166]
- Fixed: Fanvil X2: EHS was deactivated in the provisioning profile. [Call#6926764] [Call#6930459]
- Fixed: Some errors logged during the initial STARFACE database configuration were fixed.
- Fixed: Users with spaces in their surname could not be added to planned conferences. [Call#6922699]
- Fixed: Gigaset N870: It was possible for the device firmware to be updated when this was not necessary.
- Fixed: iQueue-Widget: Calls which entered the iQueue multiple times were sometimes counted as unanswered multiple times.
- Fixed: iQueue-Widget: Timestamps were formatted incorrectly in the French localisation.
- Fixed: Conference: The hyperlink in the email to external participants to the web view did not work correctly.
- Fixed: It was possible for users to be unable to delete conferences in the web interface.
- Fixed: Line configurations are no longer url-encoded to restore compatiblility with some providers (for example M-Net). [Call#6936384] [Call#6936654] [Call#6938716]
- Fixed: Module system: The default value for the date selection was in a past year.
- Fixed: When running a manual backup job, the backup file offered for download was incomplete when its size exceeded a certain limit.
- Fixed: Snom D725, D785, D120, D385, D717 and D735 had some issues with encrypted phone calls which were fixed.
- Fixed: REST: The name displayed on telephones was not updated when a user's name was changed via the REST Api.
- Fixed: REST: The conference language did not have a valid default value.
- Fixed: REST: If the value "E-mail on missed calls" was changed via REST, an incorrect value was returned when this setting was queried.
- Fixed: It was possible for extremely large backups (> 4GB) to not import properly on small storage media that should have enough space. [Call#6935482]
- Fixed: RAID error notifications were nto displayed in the System Status panel in some hardware configurations.
- Fixed: The version when splitting the download and update of a STARFACE system update was not always the pre-downloaded version expected by the administrator. [Call#6915883]
- Fixed: Redirections could be set via telephone keys without the respective permission.
- Fixed: Missed calls were not displayed in the call lists when the called user did not have a telephone assigned to them. [Call#6938813]
- Fixed: Voicemails: The alphabetic sorting was not applied to every entry in the voicemail list.
- Fixed: Yealink T48G/S, T57W: Missed calls were not displayed. [Call#6925142]
- Fixed: Yealink T56/T58: The STARFACE menus would disappear if additional widgets were added to the display.
- Fixed: Yealink: The notification tone on new voicemail messages was not intended to play and has been deactivated.
- Known Issues
- The German language package for the Snom D120 is not currently available.
- Highlights
- Version 6.7.0.24 Released on 2019/11/27
-
Features
- Highlights
- This Service Release fixes several bugs.
- Please note before installing this update
- The update to STARFACE 6.7 requires up to 4 GB of free storage.
- The UCC Client for Windows will no longer support Windows 7 from 31 December 2019. From 1 January 2020, we will only be providing support and maintenance for the UCC Client for Windows if it is run on Windows 8 or newer (or the respective Windows Server version (from Windows Server 2012 or newer)).
- We recommend reducing the size of the call data record with the module "STARFACE Archivierung", and to ensure that fully-qualified phone numbers are used in all module configurations.
- If you are using STARFACE Connect, please check the line routing settings to ensure that it is using the highest routing priority.
- Please make sure that you are using the most recent version of the UCC Clients after updating your STARFACE to this version.
- A separation of pickup permissions is planned for a future release (planned Q1/2020) and is not part of this release.
- Improvements
- Push Notifications now contain the CallID of a call (but still not personal data).
Bugfixes
- Bugfixes
- Some lines properties were erroneously url-encoded in configuration files, which caused compatibility issues with some line providers. (e.g. M-net). [Call#6936384] [Call#6936654] [Call#6938716]
- REST: Assigning a phone number to a phone did not work.
- REST: Phone assignments to users did not work when using a client generated from the API definition.
- REST: Assigning a phone assignments to oneself required admin permissions.
- Known Issues
- The German localization is temporarily not available for Snom D120.
- Encryption is currently disabled on Snom D120, D385, D717, D735, and D785.
- Highlights
- Version 6.7.0.22 Released on 2019/09/05
-
Features
- Highlights
- This is a Service Release that contains several bugfixes.
- Please note before installing this update
- The update to STARFACE 6.7 requires up to 4 GB of free storage.
- All STARFACE products with a release date before 30 September 2016 are transitioning to End-Of-Life status on 31 July 2019. This includes STARFACE versions 6.3 and older, as well as any anciliary products released before this date. From 1 August 2019 we will only be offering support and maintenance for STARFACE versions 6.4.0 and newer, and all anciliary products released after 30 September 2016.
- The UCC Client for Windows will no longer support Windows 7 from 31 December 2019. From 1 January 2020, we will only be providing support and maintenance for the UCC Client for Windows if it is run on Windows 8 or newer (or the respective Windows Server version (from Windows Server 2012 or newer)).
- We recommend reducing the size of the call data record with the module "STARFACE Archivierung", and to ensure that fully-qualified phone numbers are used in all module configurations.
- If you are using STARFACE Connect, please check the line routing settings to ensure that it is using the highest routing priority.
- Before you install you should check if your provider profile has been updated on SIPCHECK.COM.
- New Features
- Gigaset N720: Firmware updated to version 113.
- Gigaset N510: Firmware updated to version 250.
Bugfixes
- Bugfixes
- Gigaset N870: Handsets could become disconnected from the base station when new handsets were registered.
- Gigaset N510: Base stations delivered with firmware version 248 were not fully compatible with STARFACE.
- Lines could not be created or saved if the user name or authuser contained the "@" symbol.
- The STARFACE could not, in some configurations, connect to SFTP services to transfer files and backups.
- In some cases, a call could not be picked from another user. [Call#6934937] [Call#6933899][Call#6935180][Call#6934484][Call#6935179][Call#6934875][Call#6934457][Call#6934164][Call#6935473]
- Known Issues
- The German localization is temporarily not available for Snom D120.
- Encryption is currently disabled on Snom D785 and D725.
- Highlights
- Version 6.7.0.18 Released on 2019/07/25
-
Features
- Please note before installing this update
- STARFACEs that have already been updated to version 6.7.0.X will be contacted separately by e-mail.Further information can be found in the knowledgebase
- The update to STARFACE 6.7 requires up to 4 GB of free storage.
- All STARFACE products with a release date before 30 September 2016 are transitioning to End-Of-Life status on 31 July 2019. This includes STARFACE versions 6.3 and older, as well as any anciliary products released before this date. From 1 August 2019 we will only be offering support and maintenance for STARFACE versions 6.4.0 and newer, and all anciliary products released after 30 September 2016.
- The UCC Client for Windows will no longer support Windows 7 from 31 December 2019. From 1 January 2020, we will only be providing support and maintenance for the UCC Client for Windows if it is run on Windows 8 or newer (or the respective Windows Server version (from Windows Server 2012 or newer)).
- Please note that we have combined two permissions regarding the visibility of caller IDs to a single permission. Please check if any change of configuration is necessary. Further information can be found here (German).
- We recommend reducing the size of the call data record with the module "STARFACE Archivierung", and to ensure that fully-qualified phone numbers are used in all module configurations.
- If you are using STARFACE Connect, please check the line routing settings to ensure that it is using the highest routing priority.
- Before you install you should check if your provider profile has been updated on siptrunk.de.
- It is necessary to use the latest version of the UCC client in combination with the latest version of the telephony system
- Known Issue: Encryption is currently disabled on Snom D785 and D725.
Bugfixes
- Bugfixes
- There were problems with the update server, so the update was not possible in some cases.
- Please note before installing this update
- Version 6.7.0.17 Released on 2019/07/23
-
Features
- Highlights
- Group-Based Call Pickup Rules
- Security Improvements
- Many new phones integrated
- Please note before installing this update
- The update to STARFACE 6.7 requires up to 4 GB of free storage.
- All STARFACE products with a release date before 30 September 2016 are transitioning to End-Of-Life status on 31 July 2019. This includes STARFACE versions 6.3 and older, as well as any anciliary products released before this date. From 1 August 2019 we will only be offering support and maintenance for STARFACE versions 6.4.0 and newer, and all anciliary products released after 30 September 2016.
- The UCC Client for Windows will no longer support Windows 7 from 31 December 2019. From 1 January 2020, we will only be providing support and maintenance for the UCC Client for Windows if it is run on Windows 8 or newer (or the respective Windows Server version (from Windows Server 2012 or newer)).
- We recommend reducing the size of the call data record with the module "STARFACE Archivierung", and to ensure that fully-qualified phone numbers are used in all module configurations.
- If you are using STARFACE Connect, please check the line routing settings to ensure that it is using the highest routing priority.
- Before you install you should check if your provider profile has been updated on SIPCHECK.COM.
- It is necessary to use the latest version of the UCC client in combination with the latest version of the telephony system>
- Known Issue: Encryption is currently disabled on Snom D785 and D725.
- New Features
- The administration panel now shows an activity indicator when saving changes to phone numbers and lines.
- The P-Asserted-Identity now conforms to RFC-3261 when forwarding a call if the username contains an @ symbol
- The Gigaset Maxwell C is now supported.
- The Snom D120 is now supported.
- The Snom D385 is now supported.
- The Snom D717 is now supported.
- The Snom D735 is now supported.
- The Yealink T53 is now supported.
- The Yealink T53W is now supported.
- The Yealink T54W is now supported.
- The Yealink T57W is now supported.
- The redundant Groups "Password" setting has been removed.
- Login attempts to the web interface with invalid credentials now return the HTTP reponse 401 instead of 200.
- Gigaset N870: Firmware updated to version 16
- Gigaset N870: Handsets can now be assigned to users before they are provisioned for the first time.
- Gigaset N870: A long press on the buttons below the screen of a handset grants access to the STARFACE address book.
- Gigaset N870: Miscellaneous improvements to cloud autoprovisioning
- Group-Based Call Pickup Rules
- Group-Based Caller Display Rules
- REST-API: The version of the API documentation is now synchronized with the server version.
- REST-API: The YAML API documentation of the REST API can now be downloaded from within the administration panel.
- Security: The cipher RC4 has been removed.
- Security: DH Key-Length has been increased to 4096.
- Security: The email sent to new users now contains a suggestion for the user to change their password after logging in for the first time.
- Security: Security update of the installed Ghostscript application.
- Security: SSH key-length increased to 4096 on new installations.
- Security: TCP Timestamps have been deactivated to mask the server uptime.
- Security: TLS 1.0 is now disabled for SIP (Port 5061), XMPP (Port 5222) and HTTP (Port 443). These sockets now require at least TLS 1.1.
- Security: Additional HTTP Security Headers are now used.
- Snom D785: LED-Settings fixed
- Snom D785: Firmware update to version 10.1.37.11
- Improved availability of the Mobile Client for iPhone by adjusting the SIP-Expiry values
- UCC Clients
Bugfixes
- Bugfixes
- It was possible for the incorrect calls to be listed in the call list [Call#6924425]
- A STARFACE Connect lines were not saved correctly if an analogue or ISDN line was configured
- Unanswered calls were sometimes displayed as an active call in the UCC Client [Call#6920223]
- It was possible for phone number assignments to become corrupted when the standard rule for a phone number was changed from SoftwareFax to SoftwareFax2Mail
- The module "Gruppenspezifische Klingeltöne" sometimes did not play the correct ringtone after an update to STARFACE 6.6 [Call#6920517]
- The "ISDN: Timeout" setting was not considered when dialling (Austria). [Call#6920698]
- Call Waiting did not work on the Mobile Clients.
- Archiving call list data with the module "STARFACE Archivierung" did not close SFTP connections. [Call#6918110]
- The wrong error message was played when a user attempted to log off from a telephone without the permission to do so.
- Adding a new participant to a finished conference call removed all other participants.
- beroNet-Gateways: The status indicator in the line configuration did not always display the correct line status.
- BLF keys created via a REST request did not always show the correct telephone state of the user on the creating user's telephone
- The panel "Edit Function Keys" was too small after pressing cancel.
- Using the symbol "@" in SIP usernames caused all lines to become deregisterd.
- External participants could not join a telephone conference if no external phone number was assigned to the conference service.
- Importing signed certificates failed.
- In some cases the email texts sent when a user was changed was displayed incorrectly
- The Die Info-Is on the login page did not work.
- Telephones were not provisioned with the user account when assigned to a user via the REST API.
- It was not possible to let a user be called on an external number when creating a planned conference
- It was not possible to enter certain symbols when creating a new web-server certificate.
- The call loop detection did not always catch forwarded calls.
- Gigaset N870: The pagination in the handset management panel did not work.
- Gigaset N870: The field for adding new handsets is now easier to find.
- Gigaset N870: The button to start a registration window did not work correctly.
- Gigaset N870: The separator dropdown for the import file has been removed, as it is not needed.
- iFMC was activated for all phone numbers when the user's iFMC settings were changed in the STARFACE UCC Clients and Mobile Clients. [Call#6924433]
- In rare cases, answered iQueue calls would continue to ring [Call#6913925]
- In some cases, a warning about unsaved changes was displayed when none were made.
- iQueue: The redirection on time-out was not triggered when the music on hold was deactivated.
- iQueue: In some cases the iQueue Widget was displayed incorrectly.
- Memo an mich: Emails were sent in English when the server system language was French.
- It was possible for group numbers to become assigned to users under certain circumstances.
- The module Call-Through used the incorrect announcement files, which could lead to mistakes by the user. [Call#6921758]
- Music on Hold configurations assigned to users did not work after a backup import.
- REST-API: A more accurate error message is given when requesting a non-existent user.
- REST-API: It was not possible to specify which telephone should be assigned to a user when calling the endport AssignPhone.
- REST-API: The HTTP status code 200 was sent when an attempt to copy function keys to a telephone failed.
- REST-API: It was not possible to specify which telephone should be called when starting a telephone conference.
- REST-API: A telephone asigned to a user was not set as the user's primary phone device when it was their first phone.
- REST-API: It was possible to create duplicate keys.
- REST-API: An error occurred when calling GetManagedConference if the user was a moderator but not the organiser.
- REST-API: Conference: The phone number for external users did not only allow digits.
- REST-API: Updating a conference via PutManagedConference duplicated the participants
- REST-API: Participants received a PIN of "-1" when a conference was created or edited.
- REST-API: A POST to /functionkeysets/{fkSetId}/ returned a null-object.
- REST-API: It was possible to set permissions for groups
- REST-API: Phone number assignments to modules were not returned when calling GET on the /phonenumbers endpoint.
- Porting phone numbers to a second line without saving between line creation and number porting caused phone numbers to be duplicated. [Call#6923122]
- In rare cases, it was possible for calls to be displayed as ringing or active in the UCC Clients when they were answered elsewhere. [Call#6920223]
- Yealink CP860 was not provisioned with a firmware.
- Known Issues
- German language ist temporary not available for Snom D120.
- Highlights
- Version 6.6.0.20 Released on 2019/04/02
-
Features
- Highlights
- Phone numbers can now easily be ported to the "STARFACE Connect" line
- Yealink telephones were updated to Firmware version 83/84.
- Important information about this release
- The update to STARFACE 6.6 requires up to 4 GB of free storage.
- We recommend reducing the size of the call data record with the module "STARFACE Archivierung", and to ensure that fully-qualified phone numbers are used in all module configurations.
- If you are using STARFACE Connect, please check the line routing settings to ensure that it is using the highest routing priority.
- Before you install you should check if your provider profile has been updated on SIPCHECK.COM.
- Security enhancement: Yealink phones with a standard phone password will show a warning sign as a reminder to change the password.
- Improvements
- Phone numbers can now easily be ported to the "STARFACE Connect" line.
- Yealink telephones of series T4xS and T5x are updated to Firmware version 84.
- The iQueue Widget now contains an additional counter, which counts all calls that were not answered and also never rung
- Yealink telephones of series T2x and T4xG/p are updated to Firmware version 83.
- The Yealink T40G is now supported.
- The Yealink T58A (new hardware revision) is now supported.
- The Yealink T58A with Camera (new hardware revision) is now supported.
- Gigaset N870: The provisioning on STARFACE Clouds has been improved. You can find more details at knowledge.starface.de.
- Gigaset N870: Firmware update to Version 16
- Gigaset N870: The display of handsets in the Web-Interface has been improved.
- Gigaset N870: The seperator selection dropdown has been removed, as the import does not require a character separated list.
- Gigaset N870: Improved the process for handset account creation.
- The Panasonic KX-HDV340 is now supported.
- UCC Clients
- The releease notes for the UCC Client for Windows can be found here.
Bugfixes
- Bugfixes
- Adding participants to a finished conference would remove all other participants from the managed conference.
- Gigaset N870: Navigating between pages within the handset index did not work.
- Gigaset N870: The button to start Registration Mode did not work as expected.
- REST-API: The email sent when updating a conference via REST contained "-1" for the conference PIN.
- Die Info-Is on the login page did not work.
- It was not possible to use special characters such as "-" and "&" in some fields when creating a new webserver TLS certificate.
- Importing signed TLS certificates silently failed.
- Gigaset N870: An error was fixed that could occur when registering handsets.
- Highlights
- Version 6.6.0.10 Released on 2019/01/17
-
Features
- Highlights
- Telephone numbers and number blocks can now be moved from one line to another.
- Fanvil X2 to X6 Series devices are now supported and can be autoprovisioned.
- The Gigaset N870 Multicell DECT System is now supported and can be autoprovisioned and configured within the STARFACE webinterface.
- Conferences can now be configured within the UCC Clients.
- Function Keys can now be configured within the UCC Clients.
- Please note before installing this update
- The update to STARFACE 6.6 requires up to 4 GB of free storage.
- We recommend reducing the size of the call data record with the module "STARFACE Archivierung", and to ensure that fully-qualified phone numbers are used in all module configurations.
- If you are using STARFACE Connect, please check the line routing settings to ensure that it is using the highest routing priority.
- The Firefox configuration setting "network.http.sendRefererHeader" must be set to the default value "2". Alternate settings can cause problems when working with the administration panel and the iQueue widget.
- Before you install you should check if your provider profile has been updated on SIPCHECK.COM.
- Manual line configurations will be lost during the update. Please save your manual line configurations and insert them again after the update.
- New Features
- The Gigaset N870 Multicell DECT System is now supported and autoprovisioned, and can be configured within the STARFACE webinterface.
- Fanvil X2 to X6 Series devices are now supported and can be autoprovisioned.
- The Java Runtime has been updated to version 8u192.
- Telephone numbers and number blocks can now be moved from one line to another.
- The value "dtmfmode" can now be configured in line profiles.
- The CentOS distribution has been updated to version 6.10.
- The firmware 10.1.20.0 for Snom D785 has been integrated.
- Added a new endpoint to the REST API which allows reading and setting of permissions for users.
- Added a new endpoint to the REST API which allows the creation and management of conferences.
- Added a new endpoint to the REST API which allows the configuration of voicemail boxes.
- Added a new endpoint to the REST API which allows the configuration of groups.
- Added a new property "local" to the "account" REST API entity, which flags the account as a local or federation account.
- Added a new property "type" to the "account" REST API entity, which contains the type of account (USER, GROUP, REMOTE_USER, REMOTE_GROUP).
- Added a new property "assignedServiceId" to the "phonenumber" REST API entity, which denotes the service assigned to the telephone number.
- Changed the log level of the REST API to "INFO".
- UCC Clients
Bugfixes
- Bugfixes
- It was possible for a function key id to be displayed in the re-dial menu of Yealink telephones. [Call#1063641]
- Groups were unavailable when a telephone line (FXS/ISDN) was assigned to more than one agent. [Call#6912735]
- Under certain circumstances, it was possible for not all callers to be displayed in the iQueue widget. [Call#6910498]
- It was possible to cause outgoing calls of other users to be ended by dialling *8 for a random call pickup. [Call#6912379]
- It was possible for the visibility of an interconnection to be one-way only. [Call#6911470]
- It was possible to import empty address book contacts via CSV.
- Some STARFACE Connect phone numbers were not imported correctly.
- The instant messaging history of a user was not cleared when the user was deleted. [Call#6910513]
- Variables in conference invitations were always replaced by the English text if the "Default" text was selected.
- Under certain circumstances it was possible for finished conferences to not be marked as finished.
- A group created directly after creating a group with an external phone number was also assigned that external telephone number.
- It was not possible to assign a user to a group in the "logged off" state.
- Changes to telephone profiles were only applied when saved a second time.
- The web administration panels of Snom 320 and 360 devices could not be reached. [Call#6905476]
- Snom 320 devices were only provisioned in English. [Call#6905812] [Call#6905476]
- Sent faxes were occasionally not displayed in the fax list. [Call#6904302]
- E-Mails were not sent after completing the initial configuration.
- It was possible for manual dialplan settings in the line configuration to not contain the line id persisted via the database.
- The connection to the Openfire component was lost when saving changes to users and groups in rare circumstances. [Call#1059652]
- Changes to telephones restricted solely to upper/lower case characters were not saved correctly.
- Some keys were not displayed during an active call on Snom 760 devices.
- Some French translations were incorrect.
- The REST endpoint for avatars did not work as intended.
- It was possible to create unique function keys multiple times via the REST API.
- Under very rare circumstances, user licenses were incorrectly handled.
- In extremely rare circumstances it was possible for a call to not be placed to an analogue device. [Call#1057015] [Call#6914545]
- Function keys were copied to all telephones belonging to a user, instead of just the device selected.
- The resolution of caller names from the internal address book has been improved significantly.
- It was possible for the creation of an NGN provider account to fail.
- DTMF signals were not always registered correctly
- SIP lines would sometimes not register when the host IP address behind a DNS name changed
- Calls were incorrectly hung up if they were parked too frequently
- In rare circumstances, it was possible for an incoming call to be sent to the wrong extension
- NGN accounts could not be saved for some provider profiles
- Known Issues Gigaset N870
- It is currently not possible to use the N870 with cloud systems.
- A reboot or manual provisioning request via the N870 web interface is required after a factory reset or role change.
- The contacts telephone key is currently undefined.
- The Umlaut "ü" in the "SF-Menü" softkey label is displayed incorrectly for German users.
- Devices switch to speakerphone when retrieving voicemails.
- Devices switch to speakerphone when receiving CTI calls.
- Registering multiple handsets simultaneously will frequently fail.
- Known Issues Fanvil
- The Call-List and Contact Search keys are not linked to the STARFACE service.
- Some line breaks are not displayed correctly.
- A reboot is required after the device is autoprovisioned.
- Some resources are incorrectly translated.
- The "Park and Orbit" function key does not work.
- Miscellaneous known issues when displaying new voicemail messages
- The re-dial key is not linked to the Call-List.
- Some display issues were noted when using a quickdial key to initiate a call.
- Navigating in the STARFACE-Menu is not fully implemented.
- The telephone does not register the removal of the device from a user.
- Known Issues REST API for Conferences
- The permissions for the creation and alteration of conferences are not respected for some actions.
- It is not possible to edit a managed conference if an internal participant is using a phone number that isn't their primary internal number.
- Highlights
- Version 6.5.1.9 Released on 2018/09/20
-
Features
- Please note before installing this update
- The update to STARFACE 6.5.1 requires up to 4 GB of free storage.
- >We recommend reducing the size of the call data record with the module "STARFACE Archivierung", and to ensure that fully-qualified phone numbers are used in all module configurations.
- The Firefox configuration setting "network.http.sendRefererHeader" must be set to the default value "2". Alternate settings can cause problems when working with the administration panel and the iQueue widget.
- Before you install you should check if your provider profile has been updated on SIPCHECK.COM.
- Improvements
- The redial menu on Yealink telephones T19P-E2, T21P-E2, T23G, T27G, T29G, T40G, T41G, T42G, T46G, T48G no longer displays an incorrect label for function keys. [Call#1063641]
- UCC Clients
Bugfixes
- Bugfixes
- It was possible for the XMPP-Server to be unable to start after an update, if a great number of empty address book entries had been imported. [Call#6910619] [Call#6910171] [Call#6910089] [Call#6910354]
- The PostgreSQL-Logs in the STARFACE Error-Report were incomplete.
- Telephone numbers assigned via the REST API were not displayed in the web interface.
- The settings for manual telephone profiles erroneously displayed "%nbsp
- " in the canreinvite field.
- It was not possible to reach the web interface if the HTTP(S) ports of the request was forwarded from a different port by the router [Call#691028] [Call#1078771]
- The daily SIPCHECK.COM update restarted the NGN network interface(s) and stopped existing connections. [Call#6904017] [Call#6907284]
- A simulated ringback tone was played on Yealink telephones [Call#6903479] [Call#6905586]
- Please note before installing this update
- Version 6.5.1.5 Released on 2018/08/14
-
Features
- Please note before installing this update
- The update to STARFACE 6.5.1 requires up to 4 GB of free storage.
- We recommend reducing the size of the call data record with the module "STARFACE Archivierung", and to ensure that fully-qualified phone numbers are used in all module configurations.
- Please note that SIPTRUNK.DE is yet to be updated for STARFACE 6.5.1.
- The Firefox configuration setting "network.http.sendRefererHeader" must be set to the default value "2". Alternate settings can cause problems when working with the administration panel and the iQueue widget.
- Before you install you should check if your providers Profile has been updated on siptrunk.de.
- New Features
- The ModCall module is now localized to French.
- Voicemail announcements are now always played in the caller's language if this is known and no longer in the system default language.
- The Call Monitoring announcements are now always played in the user's language, if known.
- STARFACE Connect now supports routing calls to national landlines and mobile numbers, not only for Germany.
- Instant Messages are now synchronized immediately between chat clients.
- Improved French localization.
- UCC Clients
Bugfixes
- Bugfixes
- It is no longer possible to place an anonymous call to an emergency number. Anonymous emergency calls could lead to a slower response from emergency services due to longer caller identification procedures.
- It was possible for the activation of a Quickdial function key to trigger an infinite loop.
- Fixed a bug that broke the export of recorded group calls.[Call#6901721]
- The conversion of recorded audio files in the module Modcall occasionally failed.
- It was possible for the saving of the line configuration to take much longer that necessary. [Call#6902692]
- The agent intermission timer did not trigger when an iQueue call was placed on hold and resumed.
- It was possible for new users to not be able to click the button "Keys" in the web interface.
- The module Zeitgesteuerte Umleitung attempted to signal the internal phone number of a user when externally redirecting the call.
- A new user's telephones were not provisioned when the account was created.
- Missed calls would continue to be displayed to a user that had been removed from the group.
- Certain telephones would signal busy to an iQueue call after 120 seconds, regardless of the maximum waiting duration set in the iQueue.
- It was possible to access the web interface via certain ports even if these were not open.[Call#1078771]
- Some 0900 (premium rate numbers in Germany) numbers could not be called.[Call#6900700]
- The Stardial *5 would only deactivate redirections.
- It was not possible to assign provider action codes to quickdial keys which contained two or more subsequent special characters.
- The update of SIP provider profiles did not use an HTTP Proxy if one was configured. [Call#:1076366]
- The key "DSS Key" on Yealink T48G telephones is once again labelled "Show More".
- It was not possible to assign multiple phone numbers to a user or group when creating it.
- The Cross-Site-Request-Forgery protection for the Administration Panel has been improved.
- The Administration Panel would accept web server ports higher than 65535.
- It was possible for no audio to be transmitted in rare circumstances when using a HFO SIP line.
- 110 was not prioritized correctly if assigned to a remote user as an internal phone number in an interconnection.
- The name of the called party in the Call Manager was not resolved if the address book entry contained a line prefix in their phone number.
- It was possible to create a new without an internal phone number.
- It was possible for BLFs to become hidden when entering a phone number to start an inquiry call.
- The "information i" in the administration panel for voicemail box announcements did not open the correct page in the STARFACE Knowledge Base.
- It was possible to type letters in the time selection fields for the call statistics export.
- HTML Tags were displayed in certain UI elements.
- Telephone numbers in Address book entries were not formatted properly when a line prefix was included.
- The user search field did not display the expected result when selecting users for a managed conference.
- The search field did not return the complete list of module instances when creating an "activate module" function key.
- Incoming calls were listed without a dialling prefix in the call list when a Music on Hold was played by the module "Ansage vor Melden"
- Under specific circumstances, user accounts were not fully synchronized across an interconnection
- After replacing the network interface, the replacement was sometimes not detected
- The combination of GetCaller() and SetCaller() could cause issues when used on an iMFC call
- Two of the files in an Error Report were incomplete
- The device names were missing in the French email concerning insecure passwords
- Additional error report information was not sent if the content of the "Date" field was invalid
- Please note before installing this update
- Version 6.5.0.30 Released on 2018/05/17
-
Features
- The Highlights of this Version
- UCC-Clients for Windows and Mac: Screen-sharing is now enabled. The contents of a display can now be shared with other people.
- UCC-Clients for Windows and Mac: Remote control of a computer is now implemented. The other call party can now control the mouse and keyboard when this is activated.
- Invitations to external telephone conference participants no longer carry the STARFACE branding.
- The Yealink telephones T58V, T58A, T56A have been integrated.
- The Snom telephone D785 has been integrated.
- Please note before installing this update
- The update to STARFACE 6.5 requires up to 4 GB of free storage.
- We recommend reducing the size of the call data record with the module "STARFACE Archivierung", and to ensure that fully-qualified phone numbers are used in all module configurations.
- The module "Gruppen Anzeige" will transition to "End of Life" status as of 31 March 2018 and will thus no longer be on sale from the date of this beta release. STARFACE will no longer offer support for this module, neither will we maintain it going forwards. The module's functionality can be reproduced using the configuration panel under Phones/ID Display by setting "Callee name" as the first Display Element for "Default call signaling on phone for groups: Name".
- Polycom Conference telephones (Soundstation 5000, 6000, 7000) are considered "End of Life" by STARFACE as of 31 March 2018. They will continue to be autoprovisioned, however STARFACE will no longer support or maintain these devices from this date onwards.
- The telephone Gigaset Maxwell 10 is no longer supported by STARFACE as of 31 March 2018. It will no longer be auto-provisioned or supported by STARFACE.
- The module "ModCall" has changed. It might be possible that you will have to reconfigure the module after successfully updating your STARFACE
- New Features
STARFACE PBX/General Functions- The Yealink Telephones CP920 and CP960 are now supported.
- Yealink telephonee now display DND on the telephone's display.
- Provider Action Codes can now be sent to ISDN and analogue PSTN lines.
STARFACE PBX/General Improvements- The German version of the Error Report generation panel now contains a link to the support case creation form
- The Knowledge Base link for backup schedule creation now sends the user to the correct edition of the support article.
- SHA256 is now used to create Asterisk certificates.
- The autoprovisioning of Patton SN44xx Gateways is now similar to that of the SN41xx Gateways.
- CentOS has been updated to version 6.9.
- Java has been updated to version 8u152
- UCC Clients
Bugfixes
- Bugfixes
- Fixed a bug that caused the phone number in the header of the redirection options of the telephone menu to be displayed incorrectly.
- Fixed a bug that caused the wrong host to be written to the register-line for STARFACE Connect lines after a system update.
- Fixed a bug that caused callers which were redirected from an iQueue to a voicemail box by an agent to be displayed as connected for every agent in the iQueue Widget when connected to the voicemail box.
- Fixed a bug that could cause no notification to be sent in the case of a failed backup under certain circumstances.
- Fixed a bug that allowed a UCC Client to attempt a login before all of the system components were initialized.
- Fixed a bug that caused some of the phone numbers on STARFACE PBXs in Switzerland between 100 and 199 to be incorrectly assigned .
- Fixed a bug that could lead to issues when placing phone calls for users of the same phone model who were in a group.
- Fixed a bug that could make it be impossible to deactivate the suppression of a caller id.
- Fixed a bug that prevented outgoing calls when using the SIP provider "Peoplefone" if the caller id was suppressed via CLIR.
- Fixed a bug that caused some TLS certificates to be declined by some browsers.
- Fixed a bug that could lead to some internal phone numbers becoming unassignable.
- Fixed a bug that could cause UCC Premium and UCC Terminal Server licenses to be deactivated after a confirmed hardware change request.
- Fixed a bug that could cause customized function keys on Snom telephones to be labelled incorrectly.
- Fixed a bug in the REST-API which caused a returned field type to be labelled "PHONENUMER" when calling the "RedirectDestination" endpoint. The field type is now correctly labelled "PHONENUMBER" for read and write API calls.
- Fixed a bug that prevented the download of images to Yealink telephones when a forced HTTPS redirection was active.
- Fixed a bug that caused the BLF keys to display an incorrect state on Yealink T21 and T23 telephones.
- Fixed a bug that prevented the immediate use of profiles updated via SIPTRUNK.DE
- Fixed a bug that could potentially cause multiple calls to be initiated when dialling from a UCC Client
- Fixed a bug that could cause timeouts to occur when calling operating system functions on the STARFACE
- Fixed a bug that could cause some system processes to be initialized with a lower priority than required
- Fixed a bug that made it impossible to delete system notifications regarding unsent emails
- Fixed a bug where call in the iQueue widget were incorrectly marked as missed. This also fixed certain problems with follow-up time
- Fixed a bug where special characters int the address book were not displayed correctly
- Fixed a bug where the module component "EmailGet" returned an empty body element for (text/plain) emails
- Fixed a rare bug where autoprovisioning on the Gradstream HT-802 did not work properly
- Fixed a bug that caused the voicemailbox to send too many E-Mails for missed calls
- Fixed a bug where the function keys could not be used while the module "Rufsperre-Modul" was active
- Fixed a bug where call list entries without phone numbers were generated
- Fixed a bug where the export of CDR data did not work for the module "Gruppenbezogener Mitschnitt"
- Miscellaneous minor bugfixes
- The Highlights of this Version
- Version 6.4.3.34 Released on 2018/01/26
-
Features
- Release
- This release is a bugfix release which fixes several bugs that appeared in version 6.4.3.
- Please read this before installing the update
- Please note that for the proper operation of the STARFACE some ports must not be blocked. This especially refers to automatic updating of the SIP line profiles. For more information, please visit: https://knowledge.starface.de/pages/viewpage.action?pageId=6128345
- Please note that the update will download a significant amount of data.
- Should you be updating a STARFACE PRO v2 appliance, please ensure that there is at least 2.5GB of storage available.
- We strongly recommend reducing the size of the call data record with the module "STARFACE Archivierung", as well as ensuring that fully-qualified phone numbers are used in modules.
- General
- The OpenStage phones OpenStage 15, OpenStage 40, OpenStage 60 have received a firmware update to version V3R5.8.0
Bugfixes
- Bugfixes
- Fixed an issue where using special characters ("%", "&", "\") in passwords could cause problems.
- Fixed a bug where the UCC Client for Mac did not display names for external numbers in the call history.
- Fixed a bug that caused the UCC Client for Mac to open an older version of the manuel in the help menu
- Fixed an issue where a second call in the UCC Client for Mac did not knock, but rang despite an ongoing call
- Fixed a bug where the moduluser did not have write access to generated mount points of module components.
- Fixed an issue where some NGN ports were no longer able to be registered.
- Fixed a bug where the DNS resolution did not always work correctly.
- Fixed a bug that prevented the module info text to be correctly displayed.
- Fixed a rare bug that caused the module "redundancy" to fail with the 6.4.3 update.
- Fixed a bug that caused root-code in modules to not be excecuted properly after an import.
- Fixed a bug that prevented the sending of provider action codes ("#", "*") via ISDN or analog.
Note: The CALL-IDs of the individual bugfixes can be found in the corresponding release notes in the forum.
- Release
- Version 6.4.3.28 Released on 2017/12/04
-
Features
- Security Release
- This Security Release fixes a major security vulnerability in the STARFACE REST API. We recommend to update you STARFACE PBX immediately. All 6.4.3 releases up to 6.4.3.27 are affected. Installations on versions 6.4.2 or older are not affected.
- Please read this before installing the update
- Due to extensive changes, the current version of the STARFACE Mobile Client for iPhone is only compatible with a STARFACE PBX 6.4.3 and higher. We provide a legacy client to maintain compatibility with STARFACE PBXs on releases between 6.3 and 6.4.2. ATTENTION: The legacy version of the App will not be maintained. We strongly recommend that you keep your STARFACE PBX up to date and install the latest version of the app.
- Please note that the update will download a significant amount of data.
- Should you be updating a STARFACE PRO v2 appliance, please ensure that there is at least 2.5GB of storage available.
- We strongly recommend reducing the size of the call data record with the module "STARFACE Archivierung", as well as ensuring that fully-qualified phone numbers are used in modules.
Bugfixes
- Bugfixes
- Fixed a security vulnerability in the STARFACE REST API.
- Fixed a bug that caused the Snom PA1 Public Address System to malfunction. [Call#1076071]
- Security Release
- Version 6.4.3.27 Released on 2017/11/29
-
Features
- This release is a bugfix release which fixes several bugs that appeared in version 6.4.3.
- Panasonic devices have been discontinued and will no longer be supported. Currently deployed phones will continue to work, but will not be maintained or supported. This does not apply to the following devices: We continue to support the Panasonic devices KX-HDV 130, KX-HDV 230, KX-HDV 330 and KX-TGP 600.
- Please read this before installing the update
- Due to extensive changes, the current version of the STARFACE Mobile Client for iPhone is only compatible with a STARFACE PBX 6.4.3 and higher. We provide a legacy client to maintain compatibility with STARFACE PBXs on releases between 6.3 and 6.4.2. ATTENTION: The legacy version of the App will not be maintained. We strongly recommend that you keep your STARFACE PBX up to date and install the latest version of the app.
- Please note that the update will download a significant amount of data.
- Should you be updating a STARFACE PRO v2 appliance, please ensure that there is at least 2.5GB of storage available.
- We strongly recommend reducing the size of the call data record with the module "STARFACE Archivierung", as well as ensuring that fully-qualified phone numbers are used in modules.
Bugfixes
- Bugfixes
- Fixed a bug that caused some DNS servers to misinterprete a request, leading to problems with lines.
- Fixed a bug that caused the Gigaset N720 to ignore Click2Dial and calls initiated by UCC Clients.
- Fixed a bug that caused shares/SMBs to not be accessible.
- Fixed a bug that caused sytems with a large number of connected UCC Client to become slow.
- Fixed a bug that caused the log file system-scripts.log to grow indefinitely.
- Fixed a bug that caused a RAID Controller error message when there was no error.
- Version 6.4.3.26 Released on 2017/11/16
-
Features
- Release Highlights
- New provider profile: "Telekom DeutschlandLAN SIP-Trunk". We recommend using a LANCOM router.
Developer Comment: STARFACE now natively supports Deutsche Telekom's DeutschlandLAN SIP-Trunk. However, we continue to recommend using a LANCOM router from Deutsche Telekom when using this SIP Trunk. Alterations to the SIP parameters of Deutsche Telekom's service will be published immediately or at the next opportunity to Deutsche Telekom's LANCOM routers, should these be necessary. This means that you will always be up to date with the latest sip profile for your DeutschlandLAN SIP-Trunk connection. As we are not proactively informed of changes to the platform, any changes on our end can only be done after the fact, which would mean a certain amount of downtime for the customer. - System status: New tab "Diagnosis" with the option to create and download TCP-Dumps from the Administration Interface
- Calls to iOS UCC Mobile Clients now send push notifications
- The communication between the STARFACE and Snom Telephones is now encrypted
- UCC Client for Windows: Instant messages can now be sent to offline users
- UCC Client for Windows: A new "expert configuration mode" has been added, which contains seldom used settings
Developer Comment: We have noticed that some settings are used rarely. These settings overloaded the Settings menu, which made building an intuitive configuration panel difficult. We therefore moved rare used and complex settings and to a separate "Expert Mode", to make the more commonly configured settings easier and simpler to find and set - UCC Client for Windows: iFMC can now be configured in the UCC Client
- New provider profile: "Telekom DeutschlandLAN SIP-Trunk". We recommend using a LANCOM router.
Please read this before installing the update
- Due to extensive changes, the current version of the STARFACE Mobile Client for iPhone is only compatible with a STARFACE PBX 6.4.3 and higher. We will provide a legacy client to maintain compatibility with STARFACE PBXs on releases between 6.3 and 6.4.2. ATTENTION: The legacy version of the App will not be maintained. We strongly recommend that you keep your STARFACE PBX up to date and install the latest version of the App.
- Please note that the update will download a significant amount of data.
- Should you be updating a STARFACE PRO v2 appliance, please ensure that there is at least 2.5GB of storage available.
- We strongly recommend reducing the size of the call data record with the module "STARFACE Archivierung", as well as ensuring that fully-qualified phone numbers are used in modules.
- UCC Clients
- New Features
- Added a new neutral phone number prefix, to avoid manipulation of the signaled number when using CLIP NoScreening and SIP lines.
- The STARFACE can now resolve SRV DNS Records for SIP Provider Profiles
- System status: New tab "Diagnosis" with the option to create and download TCP-Dumps from the Administration Interface
- Instant Messaging: Messages to offline users are now delivered when they next log in (Offline Messaging)
- Email Templates are now updated centrally by STARFACE.
- The encryption of traffic between the STARFACE server and its telephones can be toggled
- The first three administrator accounts can log in after importing a backup with more than three users on a newly installed STARFACE
- New SIP Provider: Ecotel has been integrated
- New Provider profile for LANCOM Routers, which can be used to connect to the Deutsche Telekom DeutschlandLAN SIP-Trunk
- New Integration: Snom D710
- New Integration: Snom D712
- New Integration: Grandstream HT 814
- Improvements
- The user import template now contains an demo entry
- Onboarding emails are now sent to administrators of newly installed systems
- Telephone Conference participants now hear the same announcements regardless of how they logged in
- The system performance when a large number of UCC Clients are logged in has been improved
- Performance: Various improvements for WebUI navigation
- Usability: It is no longer possible to add more LDAP directories if all of the directories on the LDAP are in use
- LDAP: Added two search methods "precise" and "fast", to allow address book resolution from large databases in an acceptable timeframe
- Provider profiles which were downloaded from SIPTRUNK.DE without being tested by the platform are no longer marked as "Verified"
- Provider profiles downloaded from SIPTRUNK.DE are now used immediately
- Provider profiles previously downloaded from SIPTRUNK.DE which are still available on the service are marked as "verified" in the profile selection dropdown
- A system notification is now sent if the SIPTRUNK.DE provider profile download should fail
- SIPTRUNK.DE: The data transfer is now encrypted via HTTPS
- Modules can once again be run with root-level permissions after they have been signed in the partner portal
- New Module Function: ExecuteAsRoot allows signed scripts to be run with root-level permissions
- New Provider Profile: "Telekom DeutschlandLAN IP Start"
- Improved usability: The provider profile "DeutschlandLAN IP Voice/Data S" has been renamed as "Telekom DeutschlandLAN IP Voice Data (S/M/L)"
- Improved usability: The provider profile "Telekom DeutschlandLAN SIP-Trunk (Pooling)" has been renamed as "Telekom DeutschlandLAN SIP-Trunk"
- The permission "Instant Messaging" now controls the ability of the user to initiate a chat session
Developer Comment: This only affects starting a chat session. Users without this permission can still receive and answer chat messages - Provider Action Codes containing the characters "#" and "*" can now be assigned to quick dial function keys
- Improved the consistency of system notifications
- The replacement text for the conference invitation variable CALL_PARTICIPANT_INFO has been improved
- A copied provider profile is now used immediately
- The name of the column "Call number" has been renamed "Call Number/Name
- The heading for the announcement configuration for voicemail boxes is now labelled "On Timeout / Always Redirections"
- The handling of telephone numbers containing the DTMF characters * and # has been improved
- There is now a "back" button on the last step of the backup restore wizard
- The selection of a CLIP NoScreening prefix has been moved from the line extended settings to the provider configuration (setting "Caller ID Outgoing"). This is to ensure that the correct signaling type is used
Developer Comment: The signaling number prefix is now set correctly by the STARFACE. This made the drop-down in the line extended settings superfluous and avoids bad configurations. This setting can be changed in the provider profile if needed "
- The setting "No Screening" has been renamed to "CLIP No Screening"
- The display settings on Yealink T4x telephones can now be accessed without an administrator password
- New Firmware for Yealink T4xS devices (81.150.4) that fixes issues with the STARFACE telephone menu
- Yealink devices with new MAC addresses are now supported
- New Firmware for Grandstream HT 802 (1.0.3.2)
Bugfixes
- General
- Fixed a bug that prevented the creation of a backup copy of a provider profile when updated by SIPTRUNK.DE
- Fixed a bug that caused the UCI event newVoicemailListEntry to not be sent if a group call was redirected to a user voicemail box
- Fixed a bug that caused the Doorline stream to not be transmitted via the UCI until the call was answered
- Fixed a bug that caused user redirections to not be removed when the user was deleted
- Fixed a bug that caused the contents of the TextInput field to be replaced if a file with the same name was uploaded to the module instance
- Fixed a bug through which a bad input to break the navigation when creating a backup
- Fixed a bug that caused the "address book" permission to not be applied to the telephone menus
- Fixed a bug that caused the wrong default value to be applied when configuring a new addressbook block
- Fixed a bug that caused the phone numbers of interconnection users to not be added to the internal addressbook
- Fixed a bug that allowed an administrator to configure a group redirection for a user without the permission to configure group redirections
- Fixed a bug that caused call list entries of anonymous calls to have inconsistent names
- Fixed a bug that caused call list entries for held and resumed iQueue calls to be listed under "Outgoing"
- Fixed a bug that caused the sender number in the transmission report to be empty, even when it was set by the sending user
- Fixed a bug that caused the checkbox "ignore internal calls" in the module "Zeitgesteuerte Umleitung" to not work
- Fixed a bug that caused a malfunction of the speed-dial function key if the target number was entered with an external dialing prefix
- Fixed a bug that could prevent the synchronization of group BLF statuses across an interconnection
- Fixed a bug that caused the "telephone number" dropdown to be disabled when adding a new participant to a planned conference
- Fixed a bug that caused an empty line to be inserted when moving a user's BLFs in the administration panel
- Fixed a bug that caused special characters in address book import CSV files to be converted to underscores "_"
- Fixed a bug affecting the caller id when the signaling type "RFC 3325"
- Fixed a bug that caused the duration of answered calls to be incorrectly calculated
- Fixed a bug that caused a call to an iFMC device to not be hung up when the call was answered internally
- Fixed a bug that made it impossible to transfer a consultation call if the target of the transfer answered the call on their iFMC device
- Fixed a bug that caused some calls to be unintentionally signaled as "anonymous"
- Fixed a bug that could cause the name of the answering agent to be listed in the iQueue widget call log
- Fixed a bug preventing the recreation or editing of a group which had previously been deleted
- Fixed a bug that prevented outgoing calls via the SIP provider "Toplink"
- Fixed a but that caused the custom URL feature in the call manager to no longer work
- Fixed a bug that could stop calls being placed or transferred using BLF function keys
- Fixed a bug that caused the agent intermission time to be incorrectly calculated if the agent performed a consultation call
- Fixed a bug that could lead to internal numbers being unassignable after the creation of an internal number block
- Fixed a bug that caused answered iQueue calls to be listed as missed
- Fixed a bug that could cause high server load when searching for a telephone account
- Fixed a bug that caused module numbers to be improperly sorted
- Fixed a bug that could cause the name of the caller to be incorrectly displayed
- Fixed a bug that could, in rare cases, cause the caller-id to be incorrectly signaled on international calls
- Fixed a bug that could, in rare cases, make it impossible to add a new participant to a planned conference
- Fixed a bug that could, in rare cases, cause a click2dial call to be instantly forwarded to the deposit
- Fixed a bug that could, in rare cases, lead to the wrong phone number being added to a missed call notification email
- Fixed a bug that could, in rare cases, make a backup from a very old version of STARFACE to be incompatible to the new version
- Fixed a bug that could, in rare cases, cause individual call list entries to not be displayed in the UCC Clients
- Fixed a bug that could, in rare cases, cause a group call which was forwarded via CFU (always) to generate a missed call, even though the call was answered
- Fixed a bug that could, in rare cases, cause the international dialing code to be set to "0"
- Fixed a bug that could, in rare cases, cause user update via REST to fail
- Fixed a bug that could, in rare cases, lead to not all options being available when creating a new Music on Hold theme
- Fixed a bug that could, in rare cases, cause an interconnection to no longer work due to an internal number block of infinite length
- Fixed a bug that could, in rare cases, make an internal number block uneditable
- Miscellaneous minor fixes
- Telephones
- Fixed a bug that could, in rare cases, prevent a complete provisioning of Yealink Telephones
- Fixed a bug, that caused the text displayed when recording announcements on Snom telephones to be confusing
- Fixed a bug that caused the backlight of Yealink telephones to be continuously activate
- Fixed a bug that caused a redirection to voicemailbox to be incorrectly set
- Fixed a bug that caused the Opus codec to be erroneously enabled for Yealink telephones
- Fixed a bug that caused Doorline feeds to not be displayed on Yealink T48S devices
- Fixed a bug that prevented the playback of voicemail messages on Yelaink T4xS devices
- Release Highlights
- Version 6.4.2.24 Released on 2017/10/18
-
Features
- STARFACE Release 6.4.2.24
- New Yealink devices with the new MAC Address ranges are now supported by our auto-provisioning.
- Fixed a bug that prevented the authentication of the module function "AcquireAuthToken" to the server.
Please read this before installing the update
- Please note that the update will download a significant amount of data.
- Should you be updating a STARFACE PRO v2 appliance, please ensure that there is at least 2.5GB of storage available.
- We strongly recommend reducing the size of the call data record with the module "STARFACE Archivierung", as well as ensuring that fully-qualified phone numbers are used in modules.
- STARFACE Release 6.4.2.24
- Version 6.4.2.23 Released on 2017/10/05
-
Features
- STARFACE Release 6.4.2.23
- The "RTP Bleed Bug", which was found in an underlying component of the STARFACE PBX, has been completely fixed. For further information, please refer to rtpbleed.com.
- Fix: It was possible for calls via STARFACE Connect to be interrupted under rare circumstances.
Please read this before installing the update
- Please note that the update will download a significant amount of data.
- Should you be updating a STARFACE PRO v2 appliance, please ensure that there is at least 2.5GB of storage available.
- We strongly recommend reducing the size of the call data record with the module "STARFACE Archivierung", as well as ensuring that fully-qualified phone numbers are used in modules.
Bugfixes
- Fixed the RTP Bleed Bug completely
- Fixed the STARFACE Connect Bug
- STARFACE Release 6.4.2.23
- Version 6.4.2.21 Released on 2017/09/13
-
Features
- STARFACE Security Release fixes security vulnerability
This security release fixes the "RTP Bleed Bug" which was found in an underlying component of the STARFACE PBX. We strongly encourage you to install this security release. For further information please refer to RTP Bleed Bug.
Please read this before installing the update- Please note that the update will download a significant amount of data.
- Should you be updating a STARFACE PRO v2 appliance, please ensure that there is at least 2.5GB of storage available.
- We strongly recommend reducing the size of the call data record with the module "STARFACE Archivierung", as well as ensuring that fully-qualified phone numbers are used in modules.
Bugfixes
- Fixed the RTP Bleed Bug.
- STARFACE Security Release fixes security vulnerability
- Version 6.4.2.20 Released on 2017/07/21
-
Features
- Integration of Yealink devices T48S, T46S, T42S and T41S
The change compared to the prior version is the integration of the Yealink devices T48S, T46S, T42S and T41S.
Please note: It is not possible to retrieve voicemails with this version. This feature will be shipped with the next major release.
Please read this before installing the update- Please note that the update will download a significant amount of data.
- Should you be updating a STARFACE PRO v2 appliance, please ensure that there is at least 2.5GB of storage available.
- We strongly recommend reducing the size of the call data record with the module "STARFACE Archivierung", as well as ensuring that fully-qualified phone numbers are used in modules.
- Integration of Yealink devices T48S, T46S, T42S and T41S
- Version 6.4.2.19 Released on 2017/07/06
-
Features
- STARFACE PBX/General Improvements
- New authentication mechanisms
- Improved handling of passwords
- Important Note
- Please update any UCC Clients for Windows, Mac and Android as some client versions are incompatible with the new version
- For the clients to be able to update automatically, please activate "Use SSL" in each client prior to the server update.
- Please note that the update will download a significant amount of data.
- Should you be updating a STARFACE PRO v2 appliance, please ensure that there is at least 2.5GB of storage available.
- We strongly recommend reducing the size of the call data record with the module "STARFACE Archivierung", as well as ensuring that fully-qualified phone numbers are used in modules.
- UCC Clients
Bugfixes
- Bugfixes
- Fixed: It was possible for the line configuration panel to become inaccessible in very rare circumstances [Call#1067517]
- Fixed: It was possible for a backup import to fail due to a misconfigured line [Call#1062495]
- Fixed: Internal calls to external numbers of users were incorrectly routed if the dialled number was an international extension [Call#1067280]
- Fixed: Contact Headers in the register line of the sip.conf were incorrectly configured if the respective SIP line belonged to a different country [Call#1069071]
- STARFACE PBX/General Improvements
- Version 6.4.2.12 Released on 2017/05/10
-
Features
- STARFACE Security Release fixes additional vulnerability - Update strongly encouraged for PBX Interconnections
Following a blackmail threat, STARFACE gained knowledge of an additional security vulnerability in version 6.4 during forensic analysis. This vulnerability could possibly be exploited actively in the near future. The vulnerability affects telephony systems that are interconnected.
Therefore, we published a security release that closes the aforementioned vulnerability.
We strongly encourage you to install the security release and take the following general steps:
- Please ensure that your firewall opens port 3090 only when several STARFACE telephony systems are interconnected with each other
- Please operate a STARFACE Interconnection of several PBXes in a VPN, as recommended
Furthermore, we continue to strongly recommend the following general security measures:- Please create a backup of your STARFACE telephony systems immediately. Save this backup to an external drive. Ensure that backups are created regularly in the future.
- Install the security release that matches your STARFACE version. Customers on versions 6.4.0 and 6.4.1 may update to the latest version of 6.4.2 without an update contract.
- Change all passwords on your STARFACE telephony system precautiously.
We kindly ask you to update your cloud machines by yourself, if deemed necessary.
- STARFACE Security Release fixes additional vulnerability - Update strongly encouraged for PBX Interconnections
- Version 6.4.2.11 Released on 2017/05/08
-
Features
- STARFACE Security Release fixes vulnerability - Update strongly encouraged
In the context of a blackmail threat, STARFACE gained knowledge of a security vulnerability in versions 6.1, 6.2, 6.3 and 6.4. This vulnerability could possibly be exploited actively in the near future. Therefore, we published a security release that closes the aforementioned vulnerability.
We strongly encourage you to take the following steps immediately:
- Please create a backup of your STARFACE telephony systems immediately. Save this backup to an external drive. Ensure that backups are created regularly in the future.
- Install the security release that matches your STARFACE version. Customers on versions 6.4.0 and 6.4.1 may update to the latest version of 6.4.2 without an update contract.
- Change all passwords on your STARFACE telephony system precautiously.
In addition to these measures, we will start automatic updates of cloud-based telephony systems within the contractual maintenance windows.
After installing this security release, several modules might cease to work properly, because the module function ?Execute? was modified.
- STARFACE Security Release fixes vulnerability - Update strongly encouraged
- Version 6.3.0.25 Released on 2017/05/08
-
Features
- STARFACE Security Release fixes vulnerability - Update strongly encouraged
In the context of a blackmail threat, STARFACE gained knowledge of a security vulnerability in versions 6.1, 6.2, 6.3 and 6.4. This vulnerability could possibly be exploited actively in the near future. Therefore, we published a security release that closes the aforementioned vulnerability.
We strongly encourage you to take the following steps immediately:
- Please create a backup of your STARFACE telephony systems immediately. Save this backup to an external drive. Ensure that backups are created regularly in the future.
- Install the security release that matches your STARFACE version. Customers on versions 6.4.0 and 6.4.1 may update to the latest version of 6.4.2 without an update contract.
- Change all passwords on your STARFACE telephony system precautiously.
In addition to these measures, we will start automatic updates of cloud-based telephony systems within the contractual maintenance windows.
After installing this security release, several modules might cease to work properly, because the module function ?Execute? was modified.
- STARFACE Security Release fixes vulnerability - Update strongly encouraged
- Version 6.2.0.18 Released on 2017/05/08
-
Features
- STARFACE Security Release fixes vulnerability - Update strongly encouraged
In the context of a blackmail threat, STARFACE gained knowledge of a security vulnerability in versions 6.1, 6.2, 6.3 and 6.4. This vulnerability could possibly be exploited actively in the near future. Therefore, we published a security release that closes the aforementioned vulnerability.
We strongly encourage you to take the following steps immediately:
- Please create a backup of your STARFACE telephony systems immediately. Save this backup to an external drive. Ensure that backups are created regularly in the future.
- Install the security release that matches your STARFACE version. Customers on versions 6.4.0 and 6.4.1 may update to the latest version of 6.4.2 without an update contract.
- Change all passwords on your STARFACE telephony system precautiously.
In addition to these measures, we will start automatic updates of cloud-based telephony systems within the contractual maintenance windows.
After installing this security release, several modules might cease to work properly, because the module function ?Execute? was modified.
- STARFACE Security Release fixes vulnerability - Update strongly encouraged
- Version 6.1.0.2 Released on 2017/05/08
-
Features
- STARFACE Security Release fixes vulnerability - Update strongly encouraged
In the context of a blackmail threat, STARFACE gained knowledge of a security vulnerability in versions 6.1, 6.2, 6.3 and 6.4. This vulnerability could possibly be exploited actively in the near future. Therefore, we published a security release that closes the aforementioned vulnerability.
We strongly encourage you to take the following steps immediately:
- Please create a backup of your STARFACE telephony systems immediately. Save this backup to an external drive. Ensure that backups are created regularly in the future.
- Install the security release that matches your STARFACE version. Customers on versions 6.4.0 and 6.4.1 may update to the latest version of 6.4.2 without an update contract.
- Change all passwords on your STARFACE telephony system precautiously.
In addition to these measures, we will start automatic updates of cloud-based telephony systems within the contractual maintenance windows.
After installing this security release, several modules might cease to work properly, because the module function ?Execute? was modified.
- STARFACE Security Release fixes vulnerability - Update strongly encouraged
- Version 6.4.2.10 Released on 2017/04/20
-
Features
- The Highlights of this Version
- Provider profiles which have been tested by SIPTRUNK.DE are now labelled "verified" in the line selection dropdown
- The Panasonic HDV 330 is now supported
- It is now possible to search for combinations of first and family names in the address book
- Emergeny call improvements: Emergency calls will now be correctly routed if a line prefix is configured and the emergency number is configured without the dialling prefix
- Emergeny call improvements: It is now no longer possible to assign emergency numbers as internal phone numbers
- The contact search via function key now also searches the description of the key in addition to the assigned user name
- The sending of logs to STARFACE or email addresses has been redesigned
- UCC Client for Mac: It is now possible to mute the microphone while in a call
- UCC Client for Windows: Chat: A new chat window now displays the chat history of the last two days
- UCC Client for Windows: Chat: It is now possible to continue a conversation on other devices in the UCC Client
- UCC Client for Windows: Chat: Persistent group chats are now supported
- UCC Client for Windows: Faxes can now be sent via the Windows context menu ("Send to...")
- Please read this before installing the update
- All products with a release date prior to 31 March 2015 are discontinued as of 31 March 2017. STARFACE Versions 5.8 and older are affected. From 31 March onwards, we shall offer support and provide maintenance for STARFACE version 6.0 and newer and all products released after 31 March 2015
- Please note that the update will download a significant amount of data.
- Should you be updating a STARFACE PRO v2 appliance, please ensure that there is at least 2.5GB of storage available.
- We strongly recommend reducing the size of the call data record with the module "STARFACE Archivierung", as well as ensuring that fully-qualified phone numbers are used in modules.
- New Features
STARFACE PBX/General New Features- Provider profiles which have been tested by SIPTRUNK.DE are now labelled "verified" in the line selection dropdown
- An error notification is now displayed in the System Status area if the internal mail server cannot send emails due to low storage capacity
- The Feature Code *4 deactivates the Asterisk feature code detection for 10 seconds. This can be used to send DMTF codes with stars ( * ) to the other party, for example to authenticate with a telephone conference system or Doorline.
- A module function has been added to read the function keys of a user via the REST API
- New provider profile: Swisscom Smart Business Connect
- Provider Profile configuration: added an Extension Field to the profile manager
- Provider Profile configuration: TCP can now be set as the transport protocol for SIP providers
- The status of SIP line registrations is now monitored as will be restored if needed
- A new endpoint for the REST API has been added: Read phone numbers assigned to users ( GET )
- Provider action codes can now be added to a quick dial key
- The Support log now shows the execution of module functions
- The Grandstream HT802-Adapter is now supported
- Countries with multiple exit codes are now supported
- The Panasonic HDV 330 is now supported
- Video calls are now supported for iQueue and Call-Hunting groups
- It is now possible to optimize the video transmission for Yealink VCS and T49 devices via the maxcalibrate option
STARFACE PBX/General Improvements- It is now possible to search for combinations of first and last name in the address book
- The system version is now checked before moving a licence. This is to improve version compatibility
- Filenames are now checked for unsupported characters prior to being uploaded, in order to prevent future issues
- The user import feature now supports fully-qualified telephone numbers in the CSV file
- Emergeny call improvements: Emergency calls will now be correctly routed if a line prefix is configured and the emergency number is configured without the dialling prefix
- Emergeny call improvements: It is now no longer possible to assign configured emergency numbers as internal phone numbers
- All external phone numbers are now displayed including country code and local area code in all areas of the Web Interface
- It is now possible to configure the format of incoming caller ids in the administration area, as some providers format them differently
- Users deactivated due to expired or cancelled licences are now greyed out and can no longer be configured. Individual users can, however, be deleted
- Log level settings now persist through restarts and system updates
- No system status notification when profiles are updated via SIPTRUNK.DE
- The time-out duration before an update is aborted has been extended to account for slower internet speeds
- The sending of logs to STARFACE or email addresses has been redesigned
- It is now possible for line configurations belonging to multiple provider profiles to use the same SIP Domain
- Module Designer: getCaller() now also returns the caller id of the original caller for iFMC calls
- A new firmware package has been added for the Panasonic HDV-X30-Series (105)
- A new firmware package has been added for the Gigaset N510 (240)
- A new firmware package has been addded for the Gigaset N720 (102)
- Panasonic HDV-Series and TGP600: Speakerphone mode has been enabled for Click2Dial
- Patton Smartnode Gateways: A new firmware package has been included which improves performance and device stability in high-load scenarios
- The telephone search via Patton has been improved
- The permission "Provider Action Codes" no longer requires the parent category "Administration"
- It is now possible to sort call lists, fax lists and voicemail lists by name in the Web Interface
- The Support log now shows the call routing rules used
- Redirections now supports line prefixes in the destination field
- Additional protections against Click-Jacking attacks have been added
- It is now possible to configure the Web Server and Telephone conference links independently
- XML-RPC-Interface for the iQueue: HTTP-Response Encoding has been changed to UTF-8 geändert and the charset-definition is now sent in the Content-Type Header
- Yealink T49: Increased the resolution of video calls
- UCC Clients
Bugfixes
- Bugfixes
- Fixed: It was possible for a mismatch to occur in the Account/Port assignment for Patton Smartnode SN4424/SN4432
- Fixed: Refresh events for the Fax List were not being sent via the XML-RPC interface
- Fixed: It was possible for all UCC Clients to lose the connection to the STARFACE under a high system load [Call#1059652]
- Fixed: It was not possible to dial provider action codes on ISDN telephones [Call#1063783]
- Fixed: Interconnection/Interconnection Routing: It was possble to create routing rules with overlapping activation windows
- Fixed: The creation of very large (more than 4 digits) number blocks took an excessively long time to process
- Fixed: It was not possible to accept calls and broker held calls in the call manager if "Call Waiting" was active
- Fixed: The caller id signalling was inconsistent if a dialling prefix was active [Call#1057904]
- Fixed: It was possible for telephones to not update their display if a user was removed from the telephone in the administration area
- Fixed: The ISDN line usage statistics were empty [Call#:1060103]
- Fixed: It was possible for backups to become very large, as they could contain previous backups that could not be delivered to the backup location
- Fixed: Chat no longer worked after changing the XMPP domain
- Fixed: Group BLFs would signal "busy" when one group member was on the phone [Call#1054061]
- Fixed: It was not possible for a user to save their signalling number if the respective phone number was assigned to multiple lines
- Fixed: It was possible for the status of BLF to not be synchronized across an interconnection [Call#1048096] [Call#1048733]
- Fixed: It was possible for Call Manager to show incorrect data when forwarding a call to a group via a BLF
- Fixed: It was possble for the CallerID to be signalled incorrectly after a call transfer [Call#1043822]
- Fixed: The deactivation of the phone number normalization would not always work as expected [Call#1059245]
- Fixed: A user could find their "users" address book entry added to their own private address book [Call#1053011]
- Fixed: Removed irrelevant events from the Error log
- Fixed: Only one caller could record a message on a voicemail box at any one time.
- Fixed: It was possible for the call to drop for an external caller when transferred
- Fixed: An incorrect CallerID was signalled when performing an attended transfer via a Softphone and the Web Interface [Call#1058554]
- Fixed: The wrong error message was returned when setting an invalid call forward via function key
- Fixed: The wrong participant name was displayed in group chats when AD authentication was active [Call#1057520]
- Fixed: Faxes shall no longer appear in the call lists
- Fixed: It was possible for an error to occur when performing a call pickup when an iQueue call started to ring [Call#1049542]
- Fixed: Fixed various errors which occurred while shutting down the Webserver
- Fixed: It was possible for the initial start time for an instance of STARFACE Archivierung to be set to a future date when a new year began [Call#1062934]
- Fixed: The format of incoming caller ids was erroneous when the exit code was not " 00 "
- Fixed: A call could be routed to an incorrect deposit if more than two lines with the same provider profile were active [Call#1053055]
- Fixed: Scheduled Conference: DTMF menu options did not require an asterisk ( * ) to be activated [Call#1055259]
- Fixed: The call would drop if picked up via the stardial " *8 " from an iQueue after entering an IVR [Call#1063617]
- Fixed: The JDBC driver required for the "GetConnection" Module component was missing
- Fixed: In certain circumstances it was possible for the connection detail graphs in the statistics summary to display the wrong data [Call#1055791]
- Fixed: The system internal UUID of a group service module was displayed instead of its name [Call#1052544]
- Fixed: It was not possible to accept a call via iFMC when using the option "Confirm answering calls by keypress"
- Fixed: An iFMC device was not set as the primary telephone device when all SIP devices were unassigned
- Fixed: Corrected an issue which prevented the user from resetting the row count in the function key editor
- Fixed: User-specific voicemail announcements were not played after a call passed through a "Call-Hunting-Hotline" module instance [Call#1031699]
- Fixed: Fixed an issue which prevented a custom ringtone being played via the "Klingeltöne" module
- Fixed: iQueue Widget: The called position number did not change when the caller moved up the queue [Call#1054336]
- Fixed: iQueue Widget: Missed calls were attributed to the iQueue despite being forwarded by the module "Zeitgesteuerte Umleitung"
- Fixed: iQueue Widget: Fixed an issue which caused a transferred call to remain next to the original agent [Call#1060314]
- Fixed: iQueue displayed calls answered via iFMC as "missed" [Call#1055513]
- Fixed: iQueue: It was sporadically possible for the maximum length of the iQueue to not be applied
- Fixed: iQueue: Improved the display of missed calls in the iQueue Widget
- Fixed: Certain configurations of the module "Ansage vor Melden" could cause the caller number to not be displayed [Call#:1060573]
- Fixed: It was not possible to initiate an ad-hoc conference call via the feature code *3 in calls to groups
- Fixed: Fixed an issue when searching for LDAP contacts with certain special characters
- Fixed: Fixed an issue which caused some provider profiles to be displayed more than once if the local product description did not match the description on SIPTRUNK.DE
- Fixed: Line Configuration: Selecting a country would not change the country code
- Fixed: The email notification for new voicemail messages contained the wrong phone number if the module Gruppenanzeige was in use [Call#1056958]
- Fixed: It was possible for the notification "Invalid Login" to be displayed when using Firefox
- Fixed: It was not possible to set group redirections with the module function Redirect.setRedirectSetting
- Fixed: The missed call notification should no longer contain the user's own phone number when a call was answered via iFMC [Call#1055616]
- Fixed: Module "Call-in-Conference": Leaving the field "Länge der Raumnummer" empty would prevent users from entering the conference
- Fixed: Fixed an issue which prevented the module "Chefsekretärin" from working correctly in STARFACE 6.4
- Fixed: The module "Gruppenanzeige" should no longer signal an extra " 0 "
- Fixed: Module Voicemailabfrage: Fixed an issue which could prevent the caller from logging in to their voicemail box [Call#1059312]
- Fixed: Module Designer: Log messages were limited to 1024 characters
- Fixed: It was possible for modules to be executed on the standby system when using the "STARFACE Redundanz" module
- Fixed: It was possible for the message waiting indication on telephones and in the UCC Clients to signal nonexistant messages [Call#1057548]
- Fixed: It was possible for a user to not be available for usage after executing a user import via CSV file [Call#1060694]
- Fixed: Telephone numbers in the web interface are no longer clickable in Microsoft Edge
- Fixed: The Patton Smartnode 4118 4xFXS/4xFXO was detected and provisioned as an 8xFXS
- Fixed: Fixed an issue which could lead to problems when the same subscriber number was assigned to multiple local area codes
- Fixed: It was possible for backup imports to fail in rare circumstances
- Fixed: Outgoing calls on Spanish lines would occasionally fail to be dialled
- Fixed: Fixed a problem which could occur when a call was placed to a ring all group after being processed by an "Ansage vor Melden" instance and answered on an iFMC device [Call#1059889]
- Fixed: Provider Profiles: The Auth line was not updated when the domain was changed from an empty entry to a valid domain
- Fixed: Provider Profiles: Removed deprecated, non-existant or duplicate options for the property "insecure"
- Fixed: Provider Profiles: The option "never" for the property "progressinband" appeared more than once in the dropdown
- Fixed: It was sometimes not possible to send a provider action code to the pstn [Call#1062345]
- Fixed: Fixed a typo in the display "harddrive full"
- Fixed: REST-API: Fixed an issue preventing the creation of user and group BLFs
- Fixed: It was not possible to enter non-standard exit codes in the global line configuration of the STARFACE [Call#1056775]
- Fixed: The return value of the UCI function placeCallbackCall did not match the type of the UUID parameter
- Fixed: It was possible for CCBS to create duplicate call list entries [Call#1054945]
- Fixed: iFMC calls displayed the user's own external number
- Fixed: When an IVR was redirected to itself, the voice menu did not start from the beginning. Instead, the call was hung up
- Fixed: It was possible for the signalled number to show the external number of an internal caller [Call#1060312]
- Fixed: STARFACE Connect: Changes to the local area code of the line were not updated in the STARFACE
- Fixed: Fixed an issue which caused phone calls via Deutsche Telekom lines to become disconnected after a certain amount of time
- Fixed: The managed telephone conference required a PIN entry when answering the conference invitation on an iFMC device [Call#1052656]
- Fixed: A UCI Terminalserver licence was automatically granted to the administrator created during the initial configuration of the STARFACE [Call#1058792]
- Fixed: A UCI CDR event was not sent for missed group calls. The call lists in the UCC Clients will now refresh automatically when a missed group call occurs
- Fixed: Fixed an issue which caused the UCI to generate high system load when logging in or out of a group via the groupsettings options [Call#1042820]
- Fixed: The company name was not being displayed when redirecting to a username [Call#1059930]
- Fixed: It was possible for the update process to STARFACE 6.4 to fail in rare cases [Call#1059904]
- Fixed: The validation error messages when creating custom call list filters were incomplete
- Fixed: The call data export also included line usage statistics
- Fixed: It was possible for a licence expiry warning to be sent when moving the licence to a different appliance
- Fixed: The XML Function keys did not work on Panasonic devices
- Fixed: Yealink T2X Series: Firmware updates were not being deployed
- Fixed: A counter field would increment in the module designer if the user switched between timers
- Fixed: Two system status notifications were not being displayed
- Fixed: 0800 (freephone) numbers were normalized when a dialling prefix was active
- Fixed: A new version of the Struts framework was included to fix a critical security issue (CVE-2017-5638)
- Fixed: iQueue Widget: Fixed an issue which prevented the generation of missed call entries if the call never rang for an agent (beta feedback)
- Fixed: iQueue Widget: It was possible for the caller amount display to not be reset at midnight (beta feedback)
- Fixed: It was not possible to have more than two systems active in an interconnection (beta feedback)
- Fixed: The module function GetCaller() returned the wrong value for accountid for external calls (beta feedback)
- Fixed: Special characters were displayed as HTML encoded values in system logs (beta feedback)
- Fixed: A call which was answered on an iFMC device counted as a "missed" call (beta feedback)
- Fixed: Calls in the USA were signalled incorrectly (beta feedback)
- The Highlights of this Version
- Version 6.4.1.12 Released on 2017/03/15
-
Features
- Security Release: Fixed security issue in Apache Struts (CVE-2017-5638)
- Systems on versions 6.0 to 6.3 are not affected by the security issue
- Systems on versions 6.4.0 and 6.4.1 should upgrade to this security release (the update from 6.4.0 and 6.4.1 does not require an update contract)
Bugfixes
- Security Release: Fixed security issue in Apache Struts (CVE-2017-5638)
- Version 6.4.1.11 Released on 2016/12/08
-
Features
- The Highlights of this version
- This release focuses on quality improvements and bug fixes
- A new checkbox has been added for the line "STARFACE Connect", which sets whether or not the line is used for call routing
- System-internal external phone numbers are now displayed in the canonic format (+xx yyy zzzzzzzz) in the relevant parts of the UI
- REST-API: The user-telephone relationship can now be configured for the REST API and via a module element
- REST-API: The user configuration can be read from a module element via the REST-API
- UCC Client for Mac: Calendar appointments now automatically apply the "absent" chat status
- UCC Client for Mac: It is now possible to configure an automatic status change on inactivity
- Please read this before installing the update
- The field Configuration -> Extended Settings -> XMPP -> Domain must contain the STARFACE's IP address or the fully qualified host name as used in the clients.
- It is now possible to update directly to 6.4.1
- the required step to 6.2 when updating from 6.1 or lower is no longer necessary.
- Please note that the update will download a significant amount of data.
- Should you be updating a STARFACE PRO v2 appliance, please ensure that there is at least 2.5GB of storage available.
- We strongly recommend reducing the size of the call data record with the module "STARFACE Archivierung", as well as ensuring that fully-qualified phone numbers are used in modules.
- Improvements
STARFACE PBX/General Improvements- The behaviour of the notification LEDs on Snom telephones now follow the manufacturer's specification.
- The line configuration panel no longer displays the international and local area codes above the configured lines as these fields were made redundant.
- The call lists can now be accessed directly via the four-way button on Yealink telephones
- The field "AgentID" is now accessible via the XML-RPC interface of the iQueue
- The module function getCaller() is now able to deliver the externalNumber of the caller
- Video calls between Yealink telephones now have a higher resolution
- Manually transmitted Error Reports from the STARFACE now contain the licence key to enable a faster turnaround for trouble-shooting
- Picture-Clip for SnomD375
- The "number display" fields have been removed from the Caller-ID Display configuration to avoid misconfigurations
- UCI: It is now possible to search for function keys using the accountId
- Digium ISDN card 1TE436BF is now supported
- Digium ISDN card B434 is now supported
- Improved the reliability of the SIP line status display
- The update process requires less space on the storage drive, as each packet is deleted after its successful installation
- The number display when forwarding calls via ISDN has been improved
- The German language labels for the Snom D3xx and D7xx telephones have been improved
- The German language labels for the Yealink T4x telephones have been improved
- The address book query time-out has been increased to improve the resolution of phone numbers from very large address books
- UCC Clients
Bugfixes
- Bugfixes
- Fixed: The address book would sometimes show the wrong information when the STARFACE was in an interconnection [Call#1051056]
- Fixed: It was possible for users to lose their telephone numbers when the internal number blocks were changed.
- Fixed: The interconnection would sometimes not synchronize after disconnecting, deleting and reconnecting the location
- Fixed: Resolved a conflict between the permissions "uci_autoprovisioning" and "phone_login" [Call#1043899]
- Fixed: A call to a group was signalled incorrectly after an attended transfer
- Fixed: Avatars were not being displayed for some telephone models.
- Fixed: It was possible for users to be sporadically locked out of the web interface [Call#1038367]
- Fixed: The checkbox "Send error report" did not have any effect
- Fixed: It was possible for automatic blacklisting to be incorrectly deactivated for some STARFACE Cloud Instances
- Fixed: The Error Log contained some events which were not describing errors (for example "The Park and Orbit function key can only be used in BLINKING state.")
- Fixed: The module "Chefsekretärin" would signal the module's internal number to the callee.
- Fixed: The telephone number search in LDAP directories was too fuzzy.
- Fixed: Repeatedly performing backups while in an interconnection caused the backup size to increase rapidly.
- Fixed: A timing issue caused a database restore to fail in one case.
- Fixed: The German language localization of some menu labels on Yealink T48 and T49 devices was incomplete.
- Fixed: The "help" hyperlink in the conference invitation email was pointing at the wrong Knowledge Base article.
- Fixed: It was possible for the REST-API to return an empty result when under extremely high load.
- Fixed: The creation of large number blocks and the assignment of numbers belonging to large number blocks could take an abnormally long time to complete.
- Fixed: It was possible for an interconnection to not restore connectivity after deleting and restoring a location.
- Fixed: It was possible for faxes to be declined if the provider offered T.38
- Fixed: Whitespace in fax numbers would cause the transmission to fail.
- Fixed: File Upload in Modules: The existing uploaded file was not replaced when uploading a new file with the same name
- Fixed: It was possible for function keys to not be displayed on Yealink telephones if their labels contained illegal special characters.
- Fixed: An error would sporadically occur when a group redirection was active and displayed on a Gigaset telephone.
- Fixed: In rare cases it was possible for the voicemail list to contain entries with a broken file link.
- Fixed: iQueue: It was possible for a caller to be declined while their call remained in the system if all agents were DND
- Fixed: The iQueue-Reporting did not contain an entry when external callers were picked up from the Queue [Call#1049414]
- Fixed: It was possible for an iQueue to only deliver incoming calls to a single agent. [Call#: 1056220]
- Fixed: The module version roll-back was not always successful when a server update failed. [Call#1056103 ]
- Fixed: A personal redirection was able to affect cross-server group calls in an interconnection
- Fixed: Provider Profile "sipconnect"/"qscconnect": The Contact-Header in the REGISTER was not in the e.164-Format
- Fixed: Editing Provider Profiles: Saving and applying changes did not work properly
- Fixed: Caller number signalling on iFMC devices via an interconnection was not working as intended [Call#1050938]
- Fixed: It was possible for a group phone number selected as the signalling number to be displayed as the primary external number of a user
- Fixed: STARFACE Connect: The local area prefix was not updated properly when changed.
- Fixed: No exception was thrown when unnecessary data was supplied to a UCI Redirect.
- Fixed: It was possible for transfers across an interconnection to be declined when the call had been forwarded multiple times.
- Fixed: Voicemails were not correctly displayed after the caller had been forwarded after an Ansage vor Melden was played [Call#1050126]
- Fixed: The total waiting time was not being correctly calculated when a caller had hung up. [Call#1058555]
- Fixed: It was possible for call completion on busy (CCBS) to trigger additional calls
- Fixed: Legacy snom devices were not being correctly provisioned
- Fixed: It was possible for callers to be signalled with the wrong number when a dialling prefix was set [Call#1057904]
- Fixed: It was possible for the browser to freeze when activating a licence
- Fixed: It was possible for a wrong caller id to be signalled when performing an inquiry call via the UCC Softphone and the Webinterface Call Manager [Call#1058554]
- Fixed: getCallerID() returned the internalNumber and externalNumber of the callee, not the caller when the function was called when an iFMC call was dialled
- Fixed: It was possible for no number to be signalled [Call#1060573]
- Fixed: The missed call notification was not working correctly when an iFMC device was active [Call#1055616]
- Fixed: It was possible for the Message Waiting Indication on telephones and in the UCC Client to signal an incorrect number of new Voicemail messages [Call#1057548]
- Fixed: Resolved an issue involving an "invalid permissions" notification when opening faxes [Call#1059591]
- Fixed: It was possible for incoming calls to phone numbers which belonged to multiple local area codes to be routed incorrectly
- Fixed: Resolved an issue which caused the signalled caller number to display the user's own internal phone number instead of the caller's number
- Fixed: STARFACE Connect: It was possible for the line to not register properly after importing a backup
- Fixed: The call data export also contained line usage data
- Fixed: The Yealink T49G did not have a STARFACE wallpaper
- Fixed: Panasonic KX Series: Empty Function Keys not provisioned properly
- The Highlights of this version
- Version 6.4.0.11 Released on 2016/10/20
-
Features
- The Highlights of this version
- Configure multiple external number blocks with different prefixes to a single line
- Configure multiple internal number blocks
- REST API: endpoints and module functions for user data, iFMC and redirections
- Provider-specific star-dials can now be dialled, to control provider-side features
- UCC Client for Windows: "Away" state during outlook meetings is now applied to chat status
- UCC Client für Windows: Configure redirections
- Please read this before installing the update
- The field Configuration -> Extended Settings -> XMPP -> Domain must contain the STARFACE's IP address or the fully qualified host name as used in the clients.
- In order to upgrade to version 6.4 from version 6.1 or older, it is necessary to upgrade to versions 6.2 oder 6.3 first and subsequently upgrade to version 6.4.
- Please note that the update will download a significant amount of data.
- Should you be updating a STARFACE PRO v2 appliance, please ensure that there is at least 2.5GB of storage available.
- We strongly recommend reducing the size of the call data record with the module "STARFACE Archivierung", as well as ensuring that fully-qualified phone numbers are used in modules.
- New Features
STARFACE PBX/General New Features- Interconnection: Phone calls will now be dialled via an external line if the internal network connection goes down
- Additional information can now be included when sending logfiles to the STARFACE Support
- The login-screen of the web interface now includes links to the user and administrator manuals as well as the STARFACE KnowledgeBase
- New statistics export: It is now possible to export the line usage as a CSV file
- New permission: It is now possible to assign a permission to users to control provider-side features
- The administrators are now warned if telephones are using insecure telephone administration passwords
- It is now possible to send asterisks (*) in dialled numbers, in order to control provider-side features
- Snom D745 are now supported
- Yealink T40 are now supported
- Improvements
STARFACE PBX/General Improvements- It is now possible to see how many UCC Premium licences have been used [Call#1038987]
- The automated SIP-Password update process has been improved
- Autoprovisioning: Improved the reliablity of the autoprovisioning process and its logging
- CSV-files for user-imports now support the German standard formatting in Microsoft Excel (semi-colon as separator)
- It is now possible to select user-names and address book entries as redirection targets
- Email notifications for incoming faxes now include the name of the sender
- Conference invitations can now be configured to automatically include the message that the STARFACE will call the participant
- The email notification on missed calls now also includes the external number
- The collection of important / special rate phone numbers has been expanded significantly
- The administrator is now warned of unsaved changes to provider profiles
- Input/Output-Streams belonging to module functions are now correctly closed when the module execution ends
- It is no longer possible to configure redirections and call deflection in the telephone configuration of Yealink telephones, in order to avoid conflicts with server-side configurations
- The module "Archivierung" now sends emails in the system default language
- Module configuration details and module logs are now included in the STARFACE Error Report
- New Firmware: Grandstream HT702
- New Firmware: Grandstream HT704
- New Firmware: Panasonic HDV 330
- It is now possible to select an SMB-encryption method in STARFACE modules
- The automatic telephone restart after a server update is now staggered (50 telephones per minute)
- Unterschiedbarkeit zwischen Nummer und Funktionstaste in Modulen
- The update server now includes a Java 8 runtime
- Improved compatibility with less secure customer certificates in internal networks (no security risk)
- The usability of the address book has been improved by automatically formatting telephone numbers correctly
- The timing of separately downloaded updates has been improved
- The autoprovisioning mechanism has been improved
- Voicemail recordings now wait for 5 seconds of silence before being automatically ended
- The web interface now automatically updates when voicemails are deleted or moved via a telephone
- The Yealink T27 now reacts quicker when a user logout is cancelled
- The documentation of the module "Klingeltöne" has been improved
- All locations in the WebUI where a telephone number is assigned now show the entire number, including country and area codes
- UCC Clients
Bugfixes
- Bugfixes
- Fixed: Certain 0800 prefixed special rate numbers were not included for some countries
- Fixed: It was possible for the outgoing signalling number to not be transmitted [Call#1055957]
- Fixed: It was possible for the address book to create an erroneous entry after clicking "save" or "apply", which would lead to errors in the data entry area [Call#: 1056746]
- Fixed: Address book: It was possible to save an empty address book entry
- Fixed: Addressbook configuration: An "Apply" Button has been added
- Fixed: Fixed an issue which could prevent the creation of newly configured voicemail boxes
- Fixed: Interconnection: The search field in the list of interconnected systems did not work
- Fixed: It was possible for placing calls to phone numbers previously assigned to deleted module instances to lead to an error
- Fixed: Fixed an issue which caused a wrong average waiting time for the iQueue to be displayed [Call#1051643]
- Fixed: It was possible for an Attended Transfer on a telephone to cause the wrong caller number to be shown to the C-participant
- Fixed: It was possible for a server backup to only be saved locally on the STARFACE installation instead of being copied to a Windows Share
- Fixed: Fixed an issue which prevented the creation of call data records when an incoming call was put on hold
- Fixed: The password field for external mail servers was not being emptied when its contents was deleted and then saved
- Fixed: Some permissions were not being correctly assigned when importing users from a CSV file [Call#1051777]
- Fixed: A blind transfer of a call to an external party via interconnection routing which had been previously transferred via attended transfer across an interconnection would be declined by the CoR Routing
- Fixed: It was possible for executing Call2Go to an iFMC device to signal the primary internal number as the CLIP on the iFMC device
- Fixed: Call2Go was not generating a UCI call (only a SIP-Call)
- Fixed: The Call-Hunting-Group was not working correctly when called after an "Ansage vor Melden" module instance [Call#1053347]
- Fixed: Callmanager: A declined consultation call would incorrectly signal "busy"
- Fixed: Deflecting an incoming call from an O2 ISDN line to an external number via HFO would cause the following error: "Recovery on timer expiry"
- Fixed: It was possible for the Clip-No-Screening-Präfix "+" to also remove sequences of zeros which occurred within the dialled number
- Fixed: The Diversion-Header was not correctly set for CFU
- Fixed: It was possible for repeated redirections of iQueue calls to iQueues to fail [Call#1052785]
- Fixed: The settings for the configuration of an external mail server would persist in the server logs, even after deactivating the external mail server
- Fixed: It was possible for the telephone numbers of external conference participants to not be resolved from the address book [Call#1040891]
- Fixed: Phone numbers in the call list of Yealink telephones were not being correctly displayed when an instance of "Ansage vor Melden" was involved [Call#1040770]
- Fixed: Fax lists: Sorting the fax list by caller number did not work as intended
- Fixed: Fax numbers were not being correctly resolved from the address book in the transmission report [Call#1044025]
- Fixed: It was possible for the WebInterface to hang after changing the address book source from LDAP to the internal address book
- Fixed: The module component CallPhoneNumber threw an error if CalledParticipationInfo was not set
- Fixed: The module component IsChannelOpen threw an error if no call was available when the function was called
- Fixed: Fixed a bug in the function UcpFmcPhoneRequests
- Fixed: It was possible for a call placed on hold to be hung up when transferred [Call#1041036]
- Fixed: Scheduled conference: Moderator permissions were not being correctly granted [Call#1045385]
- Fixed: Only one number was available when the subscriber number was assigned to different local and international prefixes [Call#1050816]
- Fixed: Multiple error messages were displayed when attempting to save invalid active times for an iFMC device
- Fixed: Deleting a provider attached to a line without clicking "save" could lead to a defective connection in the database
- Fixed: Internal calls to an iQueue which were initiated via a "click2dial" command were signalled as "click2dial:{number of the iQueue}" in the iQueue-Widget
- Fixed: The deposit would jump to "none" if no number was entered
- Fixed: The caller indication in the iQueue-Widget would only count to 1000 [Call#: 1052499]
- Fixed: No fmcPhonesChangedEvent was fired when settings were changed via the UCI
- Fixed: There was no ringing tone when calling some SIP providers
- Fixed: There was no hangup when recording a voicemail after navigating through an IVR [Call#1045779]
- Fixed: No UCI-MWI event for group voicemails was fired if the user was logged out of the group
- Fixed: It was, under certain circumstances, not possible to assign a telephone number to a module [Call#1054002]
- Fixed: It was possible for non-admins to receive the error message "Login denied" when using a cookie to log in to the web interface [Call#1043059]
- Fixed: The module "Ansage vor Melden" caused two contradictory CDR entries when calling a group
- Fixed: The module "Ansage vor Melden" would place a second call if the call was declined or hung up immediately when "Music on Hold instead of ringing tone" was enabled
- Fixed: The module "Call-Hunting Hotline" always displayed the caller information, even when the "display number" was defined
- Fixed: The module "IVR" hung up the call when an attended transfer was performed
- Fixed: The module "IVR-Einstufig" only allowed one digit for the selection of the call destination
- Fixed: The module "Zeitgesteuerte Umleitung" could cause complications when performing consultation calls
- Fixed: Modul "Zeitgesteuerte Umleitung": Park/Halten/Blind Transfer und Grab-Voicemailbox ging
- Fixed: The module "Zeitgesteuerte Umleitung" could cause errors when parking calls, placing calls as well as performing blind and attended transfers
- Fixed: It was possible for modules to block phone numbers assigned as a call service if the entry point of the module was changed
- Fixed: Module Creator: Return Value for GetSignalNumberForUser() contained the local prefix of the STARFACE and not the signalling number [Call#1050611]
- Fixed: The module function CallPhoneNumber returned the wrong result [Call#1047626]
- Fixed: The module function GetCallerSignallingNumber() returned a different value to STARFACE 5.8
- Fixed: Module system: onAllIncomingCallToUser and onAllIncomingCallToGroup had inappropriate entry points
- Fixed: It was possible for the wrong music on hold class to be played when the module "Ansage vor Melden" was active [Call#1046553]
- Fixed: After changing the MSN of an internal ISDN line, it was possible for the old MSN to be called on the line
- Fixed: It was not possible for the Panasonic TGP600 to call a voicemail box
- Fixed: The PhoneBusinessObject allowed duplicate numbers when calling saveFcmPhone
- Fixed: Plus-Prefixed-number were hard-coded to display as "00xx" phone numbers in the conference display
- Fixed: It was possible for pop-up windows to close when using the function key editor
- Fixed: Provider profile configuration and sip/qscconnect: leaving the field "fromdomain" caused calls to be declined
- Fixed: Revoking the permission "redirect groups" only blocked affected function keys after the first usage after the change
- Fixed: Rest: The Unhandled Exception Mapper delivered the HTML Error Page in the Response Body
- Fixed: Routing/COR-Regel: "24" as a bound for the timeframe was not evaluated as a full hour
- Fixed: Call list entries were not being created when the call was redirected to an IVR and then sent to a user's voicemail box
- Fixed: Safari: The voicemail player in the Web-UI did not work
- Fixed: A connection error could appear in rare cases when logging in to the UCI
- Fixed: It was possible in very rare cases to hijack the session Seltener Fall des Session Hijackings unter seltenen Bedingungen
- Fixed: Snom 821: It was not possible to configure the virtual keypad in FW 8.7.5.35
- Fixed: The available storage check was not performed when checking for module updates
- Fixed: The language settings were not applied when importing a backup
- Fixed: Corrected the behaviour when performing a call deflection [Call#1053283]
- Fixed: The call display settings did not have any effect when an external dialling prefix was active [Call#1053627]
- Fixed: UCI with Smack 4: Openfire was not advertising DIGEST-MD5 as mech
- Fixed: Time-out redirection: The web-interface showed 120 seconds while 0 seconds was published by the UCI
- Fixed: It was possible to create invalid SIP-URIs by changing the Caller-ID Display setting. This led to calls being unable to be answered in the UCC Clients [Call#1055354]
- Fixed: It was not possible to update modules while the "separate download and installation" checkbox was selected
- Fixed: The Struts libraries have been updated
- Fixed: The validation of the area code failed after changing the international code
- Fixed: It was possible for there to be a delay in creating the audio channel when initiating an iFMC call [Call#1036573]
- Fixed: The maximum voicemail recording duration was only 10 minutes when it was set to "30 minutes" in the administration panel
- Fixed: It was possible to the Voicemail box to forward calls under certain circumstances [Call#1047357]
- Fixed: It was possible for voicemail messages to sporadically not appear in the web interface and UCC Client call lists [Call#1047935]
- Fixed: WebGUI: Active time-out redirections were displayed instead of the "always" redirection on function keys [Call#1054144]
- Fixed: It was possible for the Web interface to end the session [Call#1038367]
- Fixed: Web-Interface: Dropdown selections did not jump to the first relevant entry when pressing a key
- Fixed: The Webserver address was always included in the conference invitation, even when it was excluded [Call#1044794]
- Fixed: An active call redirection caused "missed call" email notifications to be sent regardless of whether the call was answered or not [Call#1053671]
- Fixed: Whitelist-Eintries with the expiry time "never" were overwritten
- Fixed: Yealink EXP40: Attempting to provision "empty keys" prevented the provisioning of the device [Call#1032234]
- Fixed: Yealink T2X: It was possible for the keys to be transferred in the wrong order in rare cases
- Fixed: Yealink T49: Searching in the address book always returned the entire address book
- Fixed: Yealinks used "#" as a "send key" by default. This has been disabled
- Fixed: Additional address book data fields "phoneX" were not interpreted as phone numbers
- Fixed: UCC Client for Windows: Number recognition for the format (+49) 721 12345-67 was not working correctly [Call#1058319]
- Fixed: UCC Client for Windows: Fixed an issue which caused McAfee Antivirus to block the Outlook-Connector-Fehler
- Fixed: UCC Client for Windows: The Address book synchronisation of the Outlook connector in the global address list was very slow [Call#1053141]
- Fixed: UCC Client for Windows: It was possible for the client to continue to show information after logging out
- Fixed: UCC Client for Windows: Fixed an error which could occur when changing the server
- Fixed: UCC Client for Windows: Fixed the ordering of context menu entries when in a call with an external party
- Fixed: UCC Client for Mac: It was possible for the Chat History to not display any entries
- Fixed: STARFACE Connect: A changed area prefix was not propagated properly
- Fixed: It was possible for a call deflection of an anonymous caller to fail [Call#1057034]
- Fixed: It was possible for the module "Gruppenanzeige" to manipulate the caller id display multiple times [Call#1053646]
- Fixed: It was possible for voicemail messages to only be displayed on the day after they were recorded [Call#1051437]
- Fixed: It was possible for a caller to be declined and the channel stay open if the called user was in an iQueue and had server-side DND active
- The Highlights of this version
- Version 6.3.0.24 Released on 2016/08/23
-
Features
- Please note:
-
This is a service release. If you are not affected by the listed issues, we recommend waiting for the upcoming major release
- Improvements
- DTMF-Tones generated by Sirrix-cards are now louder.
- Attention: It is no longer possible to set a separate Openfire/XMPP Domain.
Bugfixes
- Bugfixes
- Fixed: In very rare circumstances, it was possible for appliances to crash due to incompatibilities between ISDN cards.
- Fixed: It was possible for incorrect data to be written to the database when reactivating Skill Based Routing and Priority Based Routing.
- Fixed: It was not possible to use email addresses as the username for SIP provider accounts.
- Fixed: Fixed an issue which led to digits being deleted from dialled phone numbers from certain local area codes.
- Fixed: Correct erroneous provider profiles which had an incorrectly configured signalling format.
- Fixed: LEDs of Snom phones for missed calls failed to work.
- Fixed: iQueue configuration: Skill Based Routing was not being applied until a service or server restart.
- Fixed: Numbers which were entered in a specific format into the address book were not able to be called from the address book.
- Fixed: DTMF tones were not being correctly transmitted for some providers.
- Fixed: UCC Client for Windows: An error would sporadically occur while sharing files
- Fixed: UCC Client for Windows: Group chats would sometimes not be closed properly.
- Solved Support-Calls
- Solved Support-Call: [6.0.1.11] No DTMF transmission since the last update [Call#: 1040519]
- Solved Support-Calls: [6.0.2.11] The iQueue audio file export includes previously exported files [Call#1043514]
- Solved Support-Calls: [6.2.0.17] The FunctionKeyManager does not start after an update [Call#: 1055781]
- Please note:
- Version 5.8.2.7 Released on 2016/08/03
-
Bugfixes
- Resolves volume of DTMF tones too low with Sirrix cards
- Version 6.3.0.19 Released on 2016/07/20
-
Features
- Main Features of this Version
- iQueue: Priority-based Routing
- iQueue: Skill-based Routing
- UCC Clients for Windows and Mac: Chat History
- UCC Client for Windows: It is now possible to configure an automatic away-status based on inactivity, screen lock and screen saver
- Please take note of the following advice before installing the update:
- Please note that the update will download approximately 1.2 GB of data.
- If you are updating a STARFACE Pro v2 appliance, please note that update requires 2.5 GB of available storage.
- We recommend that you archive the call data records with the module "STARFACE Archivierung", and that you ensure that fully-qualified telephone numbers are used in all modules.
- If the STARFACE UCC Client for Windows is to be installed via the MSI package, the .NET Framework 4.5 must be installed first.
- Should you be updating from a STARFACE version older than 5.5, the STARFACE needs to be updated to 5.5 or 5.8 before updating to STARFACE 6.3
- New Features
- It is now possible to copy existing line configuration profiles
- iQueue: Priority-based Routing
- iQueue: Skill-based Routing
- STARFACE Connect: The list of valid mobile phone numbers is now periodically refreshed, so that the routing rules for mobile phone numbers are applied correctly
- The status of SIP lines is now monitored by the PBX and the PBX will now periodically attempt to re-register unregistered lines
- UCI: A method for requesting the Avatar Hash for a Jabber-ID/Login-ID has been added
- Telephones: The Snom D305 is now supported
- Telephones: The Snom D315 is now supported
- Telephones: The Snom D345 is now supported
- Telephones: The Yealink CP860 Conference phone is now supported
- Update: It is now possible to separately download and install server updates
- Update: It is now possible to view server updates without an update contract
- Chat: The "instant messaging" permission is now used.
- Improvements
- Automatically refreshing the address book is no longer optional
- The Snom telephone menu has been updated
- The Openfire has been updated
- The formatting of dialled numbers is now dependent on the country selected in the global line configuration (for example when dialling numbers within the USA, Australia, Poland, Spain etc.)
- The retrieval of the CallerID via the module system has been improved
- It is once again possible to auto-provision recently bought Openstage telephones
- The display of the line status in the administration panel is now refreshed more frequently after adding or editing a line
- The resolution of fax senders can now be configured via a database key
- The codec G.722 has been added to the default profiles for supported telephones
- It is no longer possible for the module "STARFACE Archivierung" to run while a backup is being created
- The module "STARFACE Archivierung" now also offers the option to export data via sFTP
- New Firmware: snom 360 (End-of-Life)
- New Firmware: Yealink T41
- New Firmware: Yealink T42
- New Firmware: Yealink T46
- New Firmware: Yealink T48
- A new column for the called number has been added to the call lists
- A new caller-ID scenario has been added for returning blind transfers
- The user permission "Instant Messaging" is now set to "active" when updating to this or higher versions, so that chat continues to work
- CCBS will now only perform the ringback when DND has been disabled
- Snom 360 now activate DND on the server
- System status: The support-log is now shown by default
- System status: Notifications are now sorted by timestamp (newest first)
- The text of the button to sign up for STARFACE Connect now reads "Get Information"
- It is now possible to request the current server timezone via the UCI method getTimeZoneId()
- The support log is now easier to read
- The error message displayed when locked out of the WebUI by the traffic filter has been improved
- The web interface now instantly displays new voicemail annoucements in the drop-downs
- Yealink T4x-Series: The Navigation buttons now open the STARFACE telephone menu
- UCC Clients
- End of Life
- The following telephones have been declared "End of Life" by the manufacturers, and are thus also no longer supported and maintained by STARFACE (though they continue to work in the current state):
- Alcatel IP 200
- Alcatel IP 600
- Alcatel IP 800
- Snom 300
- Snom 320
- Snom 360
- Snom 370
- Snom 820
- Snom 821
- Snom 870
- Snom Vision
- Tiptel IP28XS
- Tiptel IP280
- Tiptel IP282
- Tiptel IP284
- Tiptel IP286
- Tiptel T3110
- Tiptel T3120
- Tiptel T3130
- Yealink T20
- Yealink T22
- Yealink T26
- Yealink T28
- Yealink T32
- Yealink T38
Bugfixes
- Bugfixes
- Fixed: Address book: The paging would break when viewing an address book sourced from an LDAP
- Fixed: Altering a provider profile would not update all affected lines
- Fixed: The called number was not included in the support log when a call to a group was picked up (grabbed)
- Fixed: Interconnection Routing: the "delete" button would not delete rules when multiple entries were selected
- Fixed: It was not possible to sign in when the password contained umlauts
- Fixed: It was possible for the MWI counter to erroneously display numbers of voicemail messages above 1000
- Fixed: It was possible for the module "STARFACE Archivierung" to also archive and delete custom voicemail announcements [Call#1043770]
- Fixed: The iQueue call recording export would also included recordings from past days [Call#1043514]
- Fixed: The selection box for windows share security settings was positioned too far to the left
- Fixed: The backup protocol was not being correctly written [Call#1051996]
- Fixed: The check-boxes regarding interconnection permissions were not being set correctly
- Fixed: The routing priority settings for STARFACE Connect were not being correctly applied when the routing strategy "line" was selected [Call#1051936]
- Fixed: The primary internal phone number was always logged as the called number for internal calls [Call#1039207]
- Fixed: The order of the connected locations in the Interconnection tab was incorrect when sorted by "Status" and "External No."
- Fixed: It was possible for a BLF function key to not change from grey to green when a group became available
- Fixed: It was possible for BLF function keys to not perform the expected action when assigned to a Snom 370
- Fixed: It was possible for a call to continue to include a doorline-URL after removing the doorline functionality from the calling phone
- Fixed: Caller-ID settings were not always being applied on incoming external calls
- Fixed: The Cepstral-voices for text-to-speech were incorrect [Call#1049050]
- Fixed: It was possible for the check-boxes for group numbers to overwrite other settings in rare circumstances
- Fixed: The DND-display on the Snom 360 did not work
- Fixed: The DND-display on the Snom 370 did not work
- Fixed: The password entry fields for various modules now correctly mask passwords
- Fixed: The fallback-routing for interconnections was not always being correctly applied
- Fixed: Some tooltips for method descriptions in the UCI 3.0 have been corrected
- Fixed: Group numbers were not being correctly signalled after answering a call [Call#1047689]
- Fixed: The call list entries for grabbed calls were incorrect [Call#1042833]
- Fixed: The order of function keys in the automatically generated function key label PDF for Snom telephones was incorrect
- Fixed: The call list entry for group calls in conjunction with the module "Gruppenanzeige" was incorrect [Call#1040090]
- Fixed: It was not possible to add an iFMC device under certain circumstances [Call#1052359]
- Fixed: The language of the iFMC-announcement when a group was called did not correspond to the user's language setting
- Fixed: It was possible for internal faxes to not be displayed in the incoming fax list
- Fixed: iQueue recordings were only being exported to an SMB share if the checkbox for sending iQueue reports was active
- Fixed: It was possible for the module "IVR einstufig" to be incorrectly considered incompatible to the current STARFACE version [Call#1051497]
- Fixed: The online help text for the module "Voicemailabfrage" was corrected
- Fixed: LDAP: It was not possible to resolve names from entries formatted according to E.123
- Fixed: The module "Mail2Fax" incorrectly parsed email addresses with case sensitivity activated [Call#1044214]
- Fixed: It was not possible for system emails to be sent if the mail server rejected a TLS connection [Call#1053724]
- Fixed: It was not possible for the module "Ansage vor Melden" to be activated after the module "Zeitgesteuerte Rufumleitung" [Call#1042021]
- Fixed: The module "Ansage vor Melden" caused two contradictory CDR entries to be generated
- Fixed: Modul "Gruppenspezifische Klingeltöne": The title of the tab "Ring Tones" has been corrected
- Fixed: Modul Creator: The return value for GetSignalNumberForUser() contained the area code of the server and not the signalling number [Call#1050611]
- Fixed: It was not possible for modules on interconnected locations to be called without using a location prefix [Call#1038753]
- Fixed: It was possible for the connection to all SIP peers to be lost after updating to STARFACE 6.2 / the FunctionKeyManager was sometimes not being started on system boot [Call#1051356]
- Fixed: It was possible for the external number of a conference participant to be not displayed in the call manager when the line prefix was not defined and the routing strategy "static" was selected
- Fixed: Park&Orbit: It was possible for the signalled number of the caller to change when picking up the call from a park and orbit position
- Fixed: Provider profile M-Net: Fixed a typo regarding the G-729 codec
- Fixed: Removed a vulnerability in the Gigaset XML interface [Call#1048944]
- Fixed: It was possible for the tomcat log in /var/log/tomcat6/catalina.out to write multiple empty lines to the log
- Fixed: It was possible for Snom telephones to become deregistered after transferring keys if the provisioning security setting was deactivated
- Fixed: It was possible for the System status to not display the CPU status
- Fixed: System status: The system overview would load very slowly
- Fixed: It was possible for a user to not be able to transfer a telephone call which was delivered via an attended transfer
- Fixed: A typo in the logging of the module "Zeitgesteuerte Umleitung" was fixed [Call#1047178]
- Fixed: A typo in the System-Email for call monitoring was fixed
- Fixed: A typo in the notification after updating the server was fixed
- Fixed: It was possible for transferred calls to generate incorrect call list entries
- Fixed: It was possible for UCC-Premium licences to not be assigned to a user after importing a backup
- Fixed: The UCI SoftPhoneNatType included the value "NAT = yes"
- Fixed: The UCI-Function placeCallWithPhone did not use the passed Call-ID
- Fixed: Calls to unavailable call-hunting groups were not being routed correctly [Call#1049618]
- Fixed: The navigation keys on the Snom 760 were not working correctly while navigating the call lists
- Fixed: It was possible to provoke a system crash while using the module function "TextToSpeech"
- Fixed: The setting "nat=force_rport,comedia" is now used instead of "nat=yes"
- Fixed: It was not possible for voicemail emails to be sent if the contact had multiple phone numbers in the address book [Call#1053687]
- Fixed: It was possible for a user to no longer be able to be reached if a module instance that was assigned to the user as a number rule was deleted
- Fixed: A register line was written to the sip.conf when the provider profile contained the setting "host=dynamic"
- Fixed: Yealink EXP40: Provisioning "empty keys" prevented the provisioning of the device [Call#1032234]
- Fixed: Yealink T2X: It was very rarely possible for key to be provisioned in the wrong order when using an expansion pad
- Fixed: Yealink T49: A doorline feed was not displayed after answering the call
- Closed Support Tickets
- Closed Support Ticket: [5.8.2.4] Weiterleitung Gruppe mit Warteschlange funktioniert nicht [Call#1049942]
- Closed Support Ticket: [6.0.0.2] Netzwerkprobleme bei Gigaset DE-Serie [Call#1027703]
- Closed Support Ticket: [6.0.0.7] Nummern des deaktiviertem Moduls Chefsekretärin nicht mehr erreichbar [Call#1038614]
- Closed Support Ticket: [6.0.2.11] Adressbuch: Extended Pperation bei LDAP-Abfrage [Call#1044945]
- Closed Support Ticket: [6.0.2.11] Angezeigte Nummer bei externen Weiterleitungen anpassbar machen [Call#1037458]
- Closed Support Ticket: [6.0.2.11] Anlagenverbund - Bestimmte Rufnummern seit Update nicht erreichbar [Call#1045564]
- Closed Support Ticket: [6.0.2.11] Asterisk startet sporadisch neu [Call#1047934]
- Closed Support Ticket: [6.0.2.11] Cloud: Probleme mit Telefonen [Call#1044054]
- Closed Support Ticket: [6.0.2.11] Cloud: Verzögerung bei der Sprachübertragung [Call#1047584]
- Closed Support Ticket: [6.0.2.11] Faxmanager hängt sich gelegentlich auf [Call#1048469]
- Closed Support Ticket: [6.0.2.11] Gerät am internen S0 kann nicht ausgehend telefonieren [Call#1043738]
- Closed Support Ticket: [6.0.2.11] iFMC wird nach zeitgesteuerter Umleitung nicht gerufen [Call#1044069]
- Closed Support Ticket: [6.0.2.11] iQueue: gesonderte Betrachtung des DND-Status [Call#1044520]
- Closed Support Ticket: [6.0.2.11] Keine Verbindung mit SIP-Provider [Call#1046253]
- Closed Support Ticket: [6.0.2.11] Mailbox funktioniert nach Benutzerimport nicht [Call#1045154]
- Closed Support Ticket: [6.0.2.11] Modul Klingeltöne (v84) funktioniert nicht [Call#1043812]
- Closed Support Ticket: [6.0.2.11] MWI-Anzeige an Yealink T46G deaktivieren [Call#1044970]
- Closed Support Ticket: [6.0.2.11] Rufnummernsignalisierung bei Anruf auf Gruppe und anschließendes Weitervermitteln [Call#1046582]
- Closed Support Ticket: [6.0.2.11] Signalisierungstyp RFC3325 schickt falsche CLIP (B statt A) an iFMC [Call#1044079]
- Closed Support Ticket: [6.1.0.0] Adressbuchsuche findet keine vollständigen Namen [Call#1047948]
- Closed Support Ticket: [6.1.0.0] Anlage hängt sich sporadisch auf [Call#1050243]
- Closed Support Ticket: [6.1.0.0] Auswertung der iQueue unpraktisch [Call#1048883]
- Closed Support Ticket: [6.1.0.0] Bei externen Anrufen wird falsche Caller-ID übermittelt [Call#1052114]
- Closed Support Ticket: [6.1.0.0] Benutzer in Gruppe inaktiv: keine E-Mail-Benachrichtigungen [Call#1049618]
- Closed Support Ticket: [6.1.0.0] Faxversand nicht möglich [Call#: 1050251]
- Closed Support Ticket: [6.1.0.0] iQueue Wartemusik startet nach Zwischenansagen neu [Call#1050531]
- Closed Support Ticket: [6.1.0.0] Openstage-Telefone werden mit externer IP-provisioniert [Call#1055077]
- Closed Support Ticket: [6.1.0.0] Probleme mit der CDR-Exportdatei [Call#1049263]
- Closed Support Ticket: [6.1.0.0] Rückfrage funktioniert nicht nach IVR [Call#1048040]
- Closed Support Ticket: [6.1.0.1] Anlage muss öfter neugestartet werden, da nicht erreichbar [Call#1051325]
- Closed Support Ticket: [6.1.0.1] Anlegen mehrerer Leitungen mit gleichem Benutzername/Auth-User [Call#1049572]
- Closed Support Ticket: [6.1.0.1] Ausgehende Telefonie nach Update nicht möglich [Call#1050052]
- Closed Support Ticket: [6.1.0.1] E-Mail Benachrichtigungen werden an alle Benutzer versendet, bei denen dies eingestellt ist [Call#1050432]
- Closed Support Ticket: [6.1.0.1] Extremer Festplattenspeicherverbrauch [Call#1052496]
- Closed Support Ticket: [6.1.0.1] Fehler bei Click2Dial über iFMC mit Amtsholung [Call#1050181]
- Closed Support Ticket: [6.1.0.1] Kein Picken von externen Gesprächen per BLF möglich [Call#1051303]
- Closed Support Ticket: [6.1.0.1] Keine Kennwortänderung über die Weboberfläche möglich [Inhalt Call#: 1050765]
- Closed Support Ticket: [6.1.0.1] Nicht angenommene ausgehende Anrufe werden nach 45 Sekunden beendet [Call#1050989]
- Closed Support Ticket: [6.1.0.1] Ruflisten fehlerhaft [Call#1051628]
- Closed Support Ticket: [6.1.0.1] Telefone provisionieren sich nicht mit hinterlegtem Firmenlogo mit Firmenlogo-Modul [Call#1050407]
- Closed Support Ticket: [6.1] Gruppen ohne Klingelton [Call#1052015]
- Closed Support Ticket: [6.1] UCI-Schnittstelle: die intern vergebene CallID ändert sich nach Beendigung des Gesprächs [Call#1051624]
- Closed Support Ticket: [6.2.0.14 / v86] Modul "Memo an mich": Datumsformat und Dauer in Email nicht gemäß Konfiguration [Call#1052048]
- Closed Support Ticket: [6.2.0.14] Adressbucheintrag lässt sich aus UCC Client heraus nicht anlegen [Call#1051978]
- Closed Support Ticket: [6.2.0.14] Anlage zeigt sporadisch falsche Avatar-Bilder auf dem Telefon an [Call#1052833]
- Closed Support Ticket: [6.2.0.14] Diversion Header für Colt in England [Call#1053762]
- Closed Support Ticket: [6.2.0.14] Kein Freiton [Call#1053198]
- Closed Support Ticket: [6.2.0.14] Unterschiedliches Verhalten im REST-Adressbuch [Call#1052556]
- Closed Support Ticket: [6.2.0.14] Update auf 6.2.0.15 schlägt fehl [Call#1054037]
- Closed Support Ticket: [6.2.0.15] Anmeldung sporadisch nicht möglich [Call#1054922]
- Closed Support Ticket: [6.2.0.15] ISDN-Aussetzer / Ausfall nach Zuschalten von NTBAs [Call#1054299]
- Closed Support Ticket: [allgemein] DynDNS bei "Verwendete Serveradresse" in Telefonprofilen nicht verfügbar [Call#1043706]
- Closed Support Ticket: [IVR v54, 6.2.0.14] IVR einstufig ist nicht kompatibel zu Systemversion [Call#1052894] [Call#1052765] [Call#1051497]
- Closed Support Ticket: Anlage booted nicht ohne USB-Stick: GRUB auf Installationsmedium installiert [Call#1052985]
- Closed Support Ticket: Dropbox oauth2-App funktioniert nicht und gibt die Fehlermeldung aus: "frozen, pending review." [Call#1053135]
- Main Features of this Version
- Version 6.2.0.17 Released on 2016/07/13
-
Features
- This is a Service Release. Please refer to the "Bugfixes" section. If you are not affected by the fixed bugs, we recommend waiting for the next major release, which will be released shortly.
Bugfixes
- Fixed: Line "STARFACE Connect" did not re-register after losing registration
- Fixed: Busy lamp fields on Snom 370 stopped working
- Fixed: Newly purchased Openstage phone could not be autoprovisioned
- Version 6.2.0.15 Released on 2016/05/25
-
Features
- Main Features of this Version
- This Service Release contains the following bugfixes and improvements.
- Please take note of the following advice before installing the update:
- If you are updating a STARFACE Pro v2, please note that there must be at least 2.5 GB of free storage space available.
- If you are updating from STARFACE 5.8 or older, we strongly recommmend reducing the size of the call-list database with the STARFACE Archivierung module and using the fully-qualified format to ensure that modules, redirects etc. continue to work.
- If the STARFACE UCC Client for Windows is to be installed via the MSI package, the .NET Framework 4.5 must be installed first.
- Should you be updating from a STARFACE version older than 5.5, the STARFACE needs to be updated to 5.5 or 5.8 before updating to STARFACE 6.2
- Improvements
STARFACE PBX/General Improvements- Logging settings for the REST and LDAP interfaces adjusted (debug and trace)
- Progressinband=no is now sent instead of Progressinband=never in order to improve compatiblility with more providers
Bugfixes
- Bugfixes
- Fixed: Polycom conference phones were not being autoprovisioned
- Fixed: Backup to Dropbox required confirmation key on the first step of the wizard
- Fixed: Services were not being properly restarted after writing the time zone during the initial configuration
- Fixed: Various Emails contained variable names instead of texts
- Fixed: The iQueue report did not contain the caller number for each call
- Fixed: Module 'Memo an mich': The date format and duration in the email were not being properly localized
- Fixed: Module Designer: the variable returned by the function GetCallUUID() was not able to be used
- Fixed: The Tomcat was writing blocks of empty lines to the Catalina log
- Fixed: Cloud systems were not recognizing special characters in user names
- Main Features of this Version
- Version 6.2.0.14 Released on 2016/04/12
-
Features
- Main Features of this Version
- STARFACE Connect: The built-in SIP trunk for your STARFACE!
- The integration in Microsoft Office now includes more information and STARFACE features (only with the UCC Client for Windows)
- Chat is now integrated into the UCC Client for Mac
- Additional chat features in the UCC Client for Windows
- New and improved system emails with a fresh look and design
- Please take note of the following advice before installing the update:
- All products released before 31 March 2014 have been discontinued. STARFACE 5.7 and older are now considered End of Life. Only STARFACE versions newer than 5.7 and products released after 31 March 2014 will be supported and maintained.
- Please note that approx. 1.2 GB of data is being downloaded during the update.
- If you are updating a STARFACE Pro v2, please note that there must be at least 2.5 GB of free storage space available.
- If you are updating from STARFACE 5.8 or older, we strongly recommmend reducing the size of the call-list database with the STARFACE Archivierung module and using the fully-qualified format to ensure the modules continue to work.
- If the STARFACE UCC Client for Windows is to be installed via the MSI package, the .NET Framework 4.5 must be installed first.
- Should you be updating from a STARFACE version older than 5.6, the STARFACE needs to be updated to 5.6 or 5.8 before updating to STARFACE 6.2
- New Features
STARFACE PBX/General New Features- A message is shown in the System Monitor should a telephone attempt to autoprovision its SIP credentials a second time and this is blocked by the STARFACE for security reasons.
- A message is shown in the System Monitor if an email was unable to be sent. You have the option of re-sending the email directly from the System Monitor.
- The check for the available storage which is run when starting an update will now warn at a more realistic level.
- System-generated emails now have a more modern design and the text has been improved.
- Support for the Yealink T49 (Firmware 51.80.150.1).
- Encryption support of data sent to and received from providers (TLS/SRTP)
- It is now possible to record Voicemail-box announcements and change the Voicemail-box Password via a telephone.
- STARFACE UCC Client for Windows
- Chat notifications now open a pop-up window.
- Chat presence messages can now be stored for re-use.
- Group chat sessions in the UCC Client for Windows can now be started via a group BLF, or with all internal participants of a telephone conference.
- The destination directory for received files can now be configured.
- Microsoft Office for Windows now receives information and contains STARFACE functions.
- Support for Plantronics headsets: APU-75, Blackwire 200 Series, Blackwire 300 Series, Blackwire 400 Series, Blackwire 500 Series, Blackwire 600 series, Blackwire 700 Series, Calisto 600 Series, Calisto 800 Series, Calisto 240, Clarity 340, CS50/60-USB, DA45, DA70, DA80, Entera USB, MDA200 Audio Switcher, Savi 400 Series, Savi 700 Series, Savi Office, Voyager Edge UC, Voyager Focus UC, Voyager Legend UC, Voyager Pro UC
STARFACE UCC Client für Mac- Chat is now integrated into the UCC Client for Mac
- Import configuration from file
Improvements
STARFACE PBX/General Improvements- Time zones and Summer/Winter time settings were added and/or updated where necessary
- It is now possible to reset all call-display changes with one click
- The call monitoring announcement is now played for both call parties
- It is now possible to execute multiple module instances in series
- Telephones which have already been provisioned and have an autoprovisioning URL which differs from the standard URL set by the STARFACE, will now be correctly provisioned when they send a Multicast provisioning request
- Quickdials defined in a user's private address book are no longer available to other users
- The description of the module 'Gruppenbezogener Mitschnitt' has been improved
- The Support log is now more legible
- The security of the Openfire server has been increased
- Fax2Mail numbers are no longer displayed in the Web Interface where they are not needed
- Improved the formatting and encoding of the call list export files
- The amount of users that a group with the ringing strategy "Ring All" can address has been increased significantly
- Modified description in System Status: Number of further logged-in users
- The English text of the conference invitation has been corrected
- It is now possible to delete notifications in the System Monitor
- The module 'Redundanz' will now send a notification to the administrators and users, requesting that they restart their telephones
- Module function CallPhonenumber always signals "unknown" for unknown callers
- New firmware for the Gigaset DE310 (End-of-Life-Firmware)
- New firmware for the Gigaset DE410 (End-of-Life-Firmware)
- New firmware for the Gigaset DE700 (End-of-Life-Firmware)
- New firmware for the Gigaset DE900 (End-of-Life-Firmware)
- New firmware for the Gigaset N510
- New firmware for the Panasonic KX-HDV-130
- New firmware for the Panasonic KX-HDV-230
- New firmware for the Snom 870 (8.7.5.39)
- New firmware for the Yealink T48G (35.80.150.1)
- Panasonic HDV: Function keys are now populated from top to bottom
- Panasonic HDV: Function key labels can now contain up to 20 characters (up from 10)
- The Web Interface now lists the CSV entries which contain errors found when importing users
- The import of large amounts of users has been accelerated
- STARFACE Connect: The built-in SIP trunk for STARFACE has been implemented
- The display language of the STARFACE is now provisioned to the following Yealink telephones: T41P, T42G, T46G, T48G
- A new UCI event "receiveGlobalLineConfigChange" is now fired when an interconnection number block changes
- Redirections and DND status is now configured by the server for the following Yealink telephones: T19, T21, T23, T27, T29, T41, T42, T46, T48
- Improved call list entries, in particular in the case of transferred calls
- The German language translation of the Yealink T4X devices has been improved
- Improved the control of planned conferences
- The fax watchdog will no longer trigger error messages while an update is in progress
- Update to Java 8
- STARFACE UCC Client for Windows
- The client is now less susceptible to network issues
- It is now possible to configure the priority of the UCC CLient compared to other chat clients
STARFACE UCC Client for Mac- Improve cursor's colour in text fields
- The recent called numbers can now be removed from the GUI
Bugfixes
- Bugfixes
- Fixed: 'Execute Backup and apply settings' applied the changes after creating the backup
- Fixed: It was possible to 'Export call records' without selecting a user
- Fixed: [6.0.1.13] It was possible for Call2Go to not work in conjunction with the module "Chef-Sekretärin" if the ringing strategy was assigned to a user's primary phone number [Call# 1043225]
- Fixed: It was possible for a caller to be kept in the iQueue for multiple seconds before being connected to an agent [Call# 1037634]
- Fixed: Altering the call display element 'Default call signaling on phone for groups: Name' did not have any effect
- Fixed: It was possible for the STARFACE Archivierung module to export double entries [Call# 1044428]
- Fixed: It was not possible to record a voicemail announcement via the administration panel if the telephone was assigned to the user via the *77 stardial [Call# 1045585]
- Fixed: It was possible for system generated emails to contain the string 'null compatibility'
- Fixed: The time-zone set at the initial configuration was not applied immediately
- Fixed: The voicemail box would always play the same message if the total amount of saved voicemails exceeded 1,000
- Fixed: The selection box created by the DateTimeInput GUI component for the year was too small
- Fixed: It was possible for a nonsensical message to be displayed when creating a new redirection function key
- Fixed: The CLIP displayed on iFMC devices was always +49, independent of the selected CLIP prefix
- Fixed: It was, under certain circumstances, not possible to reassign a DAHDI-device belonging to an analogue line
- Fixed: It was possible for the telephone to continue to ring after an incoming call was grabbed and hung up
- Fixed: There was a double space between the first name and second name in some system generated emails
- Fixed: The dropdown selections were cut off when selecting the expiry date for blacklist and whitelist entries
- Fixed: It was sporadically not possible to answer a transferred iQueue call [Call# 1043365]
- Fixed: Some telephones were being displayed more than once in the results list of the telephone search
- Fixed: Emails for subsequent planned conferences were being sent when the previous conference was scheduled to start [Call# 1044702]
- Fixed: It was possible for a fax to be hung up if a concurrent inquiry call ended during the fax transmission [Call# 1042726]
- Fixed: Fax lists: The column "Own number" was empty
- Fixed: Call on hold is lost during transfer [Call #1041036]
- Fixed: Cannot save recordings with special characters in the file name [Call# 1020861]
- Fixed: Gigaset - CCBS (call completion on busy) was not being displayed on the telephone [Call# 1036666]
- Fixed: Gigaset: No DTMF tones to doorline when other call is being held [Call# 1036745]
- Fixed: It was possible for a voicemail list entry to be displayed multiple times, and for more than one notification email to be sent
- Fixed: Gruppenspezifische Klingeltöne was not being executed when a call from an iQueue was ringing [Call# 1042374]
- Fixed: High load due to call-data records [Call# 1049856]
- Fixed: It was possible to use non-permissable hostnames
- Fixed: The default selections for users and groups in the "export call records" and "statistics" tabs of the Statistics area of the administration panel were different
- Fixed: Entering "1" in the iQueue configuration option for 'Auto-logout idle agents - Number of unanswered calls' would log agents out of the iQueue when they answered a call [Call# 1043427]
- Fixed: The name of the user which answered a group call was not listed in the group call record export [Call# 1043513]
- Fixed: iQueue mit parallel ringing strategy: telephones belonging to agents that did not answer a call would continue to ring for up to 2 seconds after the call was answered [Call# 1044520]
- Fixed: Putting a conference on hold would make it impossible to administer the conference from the call manager
- Fixed: It was possible for an LDAP request to return an empty contact
- Fixed: It was possible for a user to not be able to access their voicemail directly after importing the user via csv [Call# 1045154]
- Fixed: Notifications in the System Monitor were being deleted when the server was updated
- Fixed: It was not possible to run the 'Ansage vor Melden' module in a series of modules
- Fixed: Module 'Chef-Sekretärin': A wildcard in the Blacklist caused the Whitelist to not be processed [Call# 1037324]
- Fixed: Module 'IVR einstufig': The call was not stopped if it was hung up [Call# 1044877]
- Fixed: Modules with the entry point 'on all incoming calls' were being executed on outgoing calls to iFMC devices
- Fixed: Module 'Ansage vor Melden' was preventing the execution of the module 'Klingeltöne'
- Fixed: Module Designer: It was possible to move categories as if they were normal module functions
- Fixed: Calling back from a group call with an activated line prefix after activating the redundancy module would cause the wrong number to be dialled
- Fixed: The agent intermission timer was not being restarted if the agent picked up a call in the iQueue before their intermission timer expired
- Fixed: It was sometimes not possible to immediately use a newly created telephone profile
- Fixed: It was possible for the presence of a virtual network interface (eth0:0) to cause a boot loop (fixeth)
- Fixed: QSC extended connect: If the called participant did not have an assigned telephone the call would be automatically redialled
- Fixed: The call duration when dialling the stardial *9 was not being displayed in the call manager
- Fixed: Phone numbers were not being resolved if the address book entry contained specific special characters [Call# 1041654]
- Fixed: CCBS: No incoming call was signalled to the CCBS initiator in the call manager when the ringback was executed
- Fixed: Security issue in glibc system library
- Fixed: An inconsistency was fixed, where a line prefix was displayed for normal calls, but not for conference calls
- Fixed: The signalling for the C-participant was incorrect after completion of an attended transfer from an external caller
- Fixed: It was, under certain circumstances, possible for two callers to be connected erroneously
- Fixed: It was possible for all of the function keys on the Tiptel 3120 to display red, light up and not react to user input
- Fixed: In certain situations, audio was not being transmitted in both directions when using a Snom D375
- Fixef: UCC Client for Mac: Clicking on Dock icon does nothing
- Fixed: UCC Client for Mac: It was not possible to set the ringtone audio device if this option was deactivated in a previous version
- Fixed: UCC Client for Mac: The ring-tone preview was not using the correct audio output device
- Fixed: UCC Client for Mac: Fixed a typo in the context menu of the function keys
- Fixed: UCC Client for Mac: High memory load when using the doorline feature
- Fixed: UCC Client for Mac: Error messages when closing the UCC Client under OS X 10.9
- Fixed: UCC Client for Mac: Call, fax and voicemail lists cannot be sorted by phone number
- Fixed: UCC Client for Mac: Entries in context menus of the list windows stopped working under OS X 10.9
- Fixed: UCC Client for Mac: Sound input device occasionally not refreshed after changing the standard input device
- Fixed: UCC Client for Mac: Client freezes when scrolling function keys
- Fixed: UCC Client for Mac: Redirection display erroneous [Call# 1050480]]
- Fixed: UCC Client for Mac: Call Manager not displayed after restarting the client
- Fixed: UCC Client for Windows: The address book in the UCC CLient was not loading if the password was not saved on login
- Fixed: UCC Client for Windows: A called that was picked via a telephone BLF was signalled to TAPI as an outgoing call
- Fixed: UCC Client for Windows: A minimized undocked pane was not usable after restarting the client
- Fixed: UCC Client for Windows: Fixed an error when dialling links with an HTML encoded '+'
- Fixed: UCC Client for Windows: The Outlook Connector was not retrieving all folders from the address book
- Fixed: UCC Client for Windows: The Outlook Connector was only retrieving mobile phone numbers from the global address book
- Fixed: UCC Client for Windows: The Outlook Connector became unresponsive if the global address book contained more than 1000 entries
- Fixed: UCC Client for Windows: Fixed issues when brokering calls and performing inquiry calls while in a telephone conference
- Fixed: UCC Client for Windows: A Call Pickup had to be confirmed by sending an additional incoming call [Call# 1048246]
- Fixed: UCC Client for Windows: Software distribution requires administrator's permissions [Call# 1047602]
- Fixed: UCC Client for Windows: TAPI-Applications would sometimes show an outgoing call with duration '0 seconds'
- Fixed: UCC Client for Windows: It was not possible to dial a number from chat via a hotkey [Call# 1046561]
- Fixed: A redirection to an external number would fail when the routing rule "line" was selected if the caller was not signalling a display number
- Fixed: It was possible for an incorrect redirection to be activated under certain circumstances if a redirection to a phone number was defined via the UCI
- Fixed: Server updates would sometimes not fully complete, and the STARFACE would need to be restarted manually
- Fixed: Pre-update warnings regarding the versions are not shown during initial configuration.
- Fixed: Listening to a Voicemail message on a telephone would open an empty call manager
- Fixed: Voicemail messages were not being displayed correctly
- Fixed: Dialling from the address book with an iFMC device while a line prefix was active would fail [Call# 1043136]
- Fixed: The WebUI of the Snom 320 was not accessible via HTTPS with Firefox 41.0a2
- Fixed: Concurrent execution of the modules 'IVR', 'zeitgesteuerter Umleitung' and the iQueue caused significant problems [Call# 1045182]
- Fixed: Updated glibc to newest version
- Closed Support Tickets
- Closed Support Ticket: [5.0.0.14] User können nicht gelöscht werden [Call# 1047525]
- Closed Support Ticket: [5.7.0.7] Modul 'Blacklist': Wildcard in der Blacklist überschreibt Whitelist [Call# 1024955]
- Closed Support Ticket: [5.8.0.13] Appliance bleibt stehen [Call# 1045714]
- Closed Support Ticket: [5.8.0.15 / v57] Modul Speeddial: Anlagenverbundstauglichkeit [Call# 1040302]
- Closed Support Ticket: [5.8.0.15] [6.0.2.11] Es verschwinden Nummern, Umleitungsverhalten nicht konsitent zur Benutzeroberfläche [Call# 1045189]
- Closed Support Ticket: [5.8.0.X] Update von Firmware für Tiptel 3110 / 3120 [Call# 1028837]
- Closed Support Ticket: [5.8.2.0] Teilweise weiterhin Echo auf ISDN-Leitung der STARFACE Compact [Call# 1033805]
- Closed Support Ticket: [5.8.2.2] Compact: Asterisk stürzt ab - watchdog greift ein [Call# 1033544]
- Closed Support Ticket: [5.8.2.2] Wählen über Telefonhistorie nach Click2Dial funktioniert nicht [Call# 1041498]
- Closed Support Ticket: [5.8.2.2] Yealink T46: Umleitungen an Endgeräten verhindern [Call# 1045003]
- Closed Support Ticket: [5.8.2.4] AGI nicht verfügbar [Call# 1045912]
- Closed Support Ticket: [5.8.2.4] Analog-Smartnodes (SN 44xx) signalisieren CLIP nur jedes zweite mal [Call# 1042287]
- Closed Support Ticket: [5.8.2.4] Archivierung sendet Fehlermails [Call# 1044043]
- Closed Support Ticket: [5.8.2.4] Telefone hängen sich beim Booten auf [Call# 1041928]
- Closed Support Ticket: [5.8.2.4] Weiterleitung nach extern über Provider schlägt fehl [Call# 1043408]
- Closed Support Ticket: [6.0.0.5] Fehler bei Namensauflösung bei Ruf einer Gruppe mit 'Ansage vor Melden' [Call# 1035684]
- Closed Support Ticket: [6.0.0.5] Weitergeleitete Rufe bleiben im Callmanager hängen [Call# 1035734]
- Closed Support Ticket: [6.0.0.7] Kein Freiton, obwohl im TCP Dump dieser zu hören ist [Call# 1037401]
- Closed Support Ticket: [6.0.0.7] Outlook Connector soll für die Namensauflösung auch das globale Exchange-Adressbuch verwenden [Call# 1037438]
- Closed Support Ticket: [6.0.1.12] Popup-Fenster des Outlook Connectors öffnet sich nicht [Call# 1040216]
- Closed Support Ticket: [6.0.1.12] Telefon klingelt bei Anruf auf Gruppe nicht [Call# 1040372]
- Closed Support Ticket: [6.0.1.12] übertragung der BLFs als Admin nicht mehr anstoßbar [Call# 1034134]
- Closed Support Ticket: [6.0.1.13] Anlagenabsturz [Call# 1047907]
- Closed Support Ticket: [6.0.1.13] Call Picking via BLF nicht möglich [Call# 1037748]
- Closed Support Ticket: [6.0.1.13] Externe Nummer nicht erreichbar [Call# 1042782]
- Closed Support Ticket: [6.0.1.13] ISDN-Leitung nach Update von 5.7.0.7 auf 6.0.1.13 nicht stabil [Call# 1041688]
- Closed Support Ticket: [6.0.1.13] Rufnummerauflösung ausgehend greift nicht [Call# 1041565]
- Closed Support Ticket: [6.0.1.13] SIP-Gerät klingelt nicht bei jedem User mit [Call# 1041554]
- Closed Support Ticket: [6.0.1.13] Spontane Konferenz bricht zusammen [Call# 1037925]
- Closed Support Ticket: [6.0.1.13] Voicemaileintrag in Liste existiert nicht [Call# 1035287]
- Closed Support Ticket: [6.0.2.11 Rufnummern von Voicemails im Mac-Client werden nicht mehr aufgelöst [Call# 1043279]
- Closed Support Ticket: [6.0.2.11] Anlage startet sporadisch neu [Call# 1046920]
- Closed Support Ticket: [6.0.2.11] Anlagenverbund - Benutzer kann sich bei der Gruppe nicht an-/abmelden [Call# 1047640]
- Closed Support Ticket: [6.0.2.11] Anlagenverbund: Rufnummer des anderen Standorts signalisieren [Call# 1046049]
- Closed Support Ticket: [6.0.2.11] Anrufe der iQueue werden nicht zugestellt [Call# 1043936]
- Closed Support Ticket: [6.0.2.11] Anrufe landen nach Update auf Abwurfplatz [Call# 1043461]
- Closed Support Ticket: [6.0.2.11] Backup kann wegen zu wenig RAM nicht eingespielt werden [Call# 1044781]
- Closed Support Ticket: [6.0.2.11] Benutzer einer Gruppe klingelt nicht mit [Call# 1044801]
- Closed Support Ticket: [6.0.2.11] Besetztlampenstatus-Update funktioniert nicht [Call# 1043361]
- Closed Support Ticket: [6.0.2.11] Beta-Release verfügbar ohne 'Activate Beta-Modul' [Call# 1045530]
- Closed Support Ticket: [6.0.2.11] COR-Routing funktioniert nach Update nicht mehr [Call# 1043782]
- Closed Support Ticket: [6.0.2.11] Ein weitergeleiteter iQueue-Anruf kann nicht angenommen werden [Call# 1043365]
- Closed Support Ticket: [6.0.2.11] Eingehende Anrufe nach Update nicht mehr möglich [Call# 1045668]
- Closed Support Ticket: [6.0.2.11] Falsche CLIP bei iFMC-Ruf [Call# 1044247]
- Closed Support Ticket: [6.0.2.11] Hauptnummer nicht erreichbar [Call# 1045389]
- Closed Support Ticket: [6.0.2.11] iQueue - Gespräche können nicht angenommen werden [Call# 1046800]
- Closed Support Ticket: [6.0.2.11] iQueue: Anrufer hört Wartemusik trotz Gesprächsannahme [Call# 1042883]
- Closed Support Ticket: [6.0.2.11] iQueue: Call-Picks nicht möglich [Call#: 1043485]
- Closed Support Ticket: [6.0.2.11] iQueue: Schlussansage wird nicht abgespielt [Call# 1046993]
- Closed Support Ticket: [6.0.2.11] Java Exception bei selbst erstelltem Modul [Call# 1045676]
- Closed Support Ticket: [6.0.2.11] Nach Update werden die Default- statt der benutzerdefinierten Mailboxansagen abgespielt [Call# 1044434]
- Closed Support Ticket: [6.0.2.11] Namensauflösung fehlerhaft [Call# 1044663]
- Closed Support Ticket: [6.0.2.11] Probleme mit Rufnummer und AccountID im Anlagenverbund [Call#: 1046003]
- Closed Support Ticket: [6.0.2.11] Providerprofil TeleData RFC3325 signalisert bei CLIP No Screening B-Teilnehmernummer an iFMC [Call# 1044079]
- Closed Support Ticket: [6.0.2.11] Rufliste nach Tranfer zeigt interne Nummer [Call# 1043762]
- Closed Support Ticket: [6.0.2.11] UCC Client für Mac: Fehlermeldung verhindert Abmelden des Rechners [Call# 1043590]
- Closed Support Ticket: [6.0.2.11] UCC Client für Windows setzt Audio-Einstellungen nach Beenden zurück [Call# 1045261]
- Closed Support Ticket: [6.0.2.11] Voicemailnachrichten werden in der Weboberfläche nicht angezeigt [Call# 1045058]
- Closed Support Ticket: [6.0.2.11] Zeitgesteuerte Umleitung bei Gruppe greift nicht, wenn es nach Modul 'Ansage vor Melden' geschaltet ist [Call# 1043758]
- Closed Support Ticket: [6.0.2.11] Zeitgesteuerte Umleitungen werden nur mit Immer-Umleitungen angezeigt [Call# 1044279]
- Closed Support Ticket: [6.0.2.11] Error message: No Configfile has been loaded [Call# 1046464]
- Closed Support Ticket: [6.0.2.11] The wrong name was signaled to remote users [Call# 1044821]
- Closed Support Ticket: [6.0.2.11] Artifacts were produced when playing back audio of recordings [Call# 1043185]
- Closed Support Ticket: [6.0.2.11] DTMF letters are not transmitted [Call# 1047883]
- Closed Support Ticket: [6.0.2.11] No ringing tone when transferring to external numbers [Call# 1049218]
- Closed Support Ticket: [6.0.9.7] Absendernummer in Faxliste falsch [Call# 1045378]
- Closed Support Ticket: [6.0.9.7] Call-Hunting-Hotline Modul funktioniert nicht [Call# 1045865]
- Closed Support Ticket: [6.0.9.7] Intern ISDN wählen über Sirrix-Karte funktioniert nach Update auf Beta-Version nicht mehr [Call# 1046456]
- Closed Support Ticket: [6.0.9.7] Kein Klingeln bei ausgehender Telefonie [Call# 1045612 ]
- Closed Support Ticket: [6.0.9.7] Kein Ton im Provider-NGN bei zeitgesteuerter Umleitung nach extern [Call# 1045679]
- Closed Support Ticket: [6.0.9.7] N510-Provisionierung nicht möglich [Call# 1045803]
- Closed Support Ticket: [6.1.0.0] Fehler in der ID-Anzeige bei Umleitung [Call# 1046860]
- Closed Support Ticket: [6.1.0.0] Probleme mit Bootstick bei 6.1.0.0 ISO! [Call# 1046999]
- Closed Support Ticket: [6.1.0.0] Call-data records often show STARFACE [Call# 1048890]
- Closed Support Ticket: [6.1.0.0] Problems with network interface card on Enterprise appliance [Call# 1049463]
- Closed Support Ticket: [6.1.0.0] UCC Client für Windows: Anbdingung des Adressbuch [Call# 1047097]
- Closed Support Ticket: [6.1.0.0] UCC Client für Windows: Anmeldung an UCC Client als Admin nicht möglich, wenn AD aktiv [Call# 1047385]
- Closed Support Ticket: [6.1.0.0] Update to 6.2 Beta fails [Call# 1049525]
- Closed Support Ticket: [6.1.0.0] Voicemail-Symbol: Unendlich viele Nachrichten [Call# 1047057]
- Closed Support Ticket: [6.1.0.0] STARFACE Menu not working on Tiptel 286 [Call# 1049592]
- Closed Support Ticket: [6.1.0.0] Hylafax crashes [Call# 1049208]
- Closed Support Ticket: [6.1.0.0] External callers are connected on attended transfer [Call# 1045152]
- Closed Support Ticket: [6.1.0.1] Busy redirects does not work for groups [Call# 1050176]
- Closed Support Ticket: [6.1.0.1] Gigaset N510 - Mailbox number changes suddenly [Call# 1049965]
- Closed Support Ticket: [6.1.0.1] Number signalled without regional and country codes [Call# 1050981]
- Closed Support Ticket: [6.1.0.1] UCC Client for Windows: Outlook contacts from public folder cannot be retrieved [Call# 1047897]
- Closed Support Ticket: [6.1.0.1] XMPP Server not available after update [Call# 1050324]
- Closed Support Ticket: [iOS App 1.8.2] Meldung 'Timeout' bei Voicemail Abruf [Call# 1037881]
- Closed Support Ticket: [Tiptel 286] Frage nach Anzahl der möglichen Beistellmodule [Call# 1043778]
- Main Features of this Version
- Version 5.8.2.6 Released on 2016/03/07
-
Features
- Bugfix Release: Contains the bugfixes for two security issues: OpenSSL library / DROWN attack (CVE-2016-0800) and glibc (CVE-2015-7547)
Bugfixes
- Fixed security issue in OpenSSL library (DROWN attack, CVE-2016-0800)
- Version 5.7.0.14 Released on 2016/03/07
-
Bugfixes
- Fixed security issue in OpenSSL library (DROWN attack, CVE-2016-0800)
- Version 5.7.0.13 Released on 2016/02/24
-
Features
- Adjusted the storage check performed when starting an update
- Do not allow caller ID "anonymous" in HFO provider profile
- New firmware for Yealink T46G: 28.71.150.17
Bugfixes
- Fixed a critical vulnerability in glibc library (CVE-2015-7547)
- Several additional bugfixes
- Version 6.1.0.1 Released on 2016/02/23
-
Features
- Adjusted the storage check performed when starting an update
Bugfixes
- Fixed a critical vulnerability in glibc library (CVE-2015-7547)
- Version 6.0.2.13 Released on 2016/02/23
-
Features
- Adjusted the storage check performed when starting an update
Bugfixes
- Fixed a critical vulnerability in glibc library (CVE-2015-7547)
- Version 5.8.2.5 Released on 2016/02/23
-
Features
- Adjusted the storage check performed when starting an update
Bugfixes
- Fixed a critical vulnerability in glibc library (CVE-2015-7547)
- Version 6.1.0.0 Released on 2015/12/15
-
Features
- Main Features of this Version
- Improvements for the Deutsche Telekom ALL-IP SIP profile
- The address book has been added to the UCC Clients
- The new System Status Monitor offers an in-depth view of the telephone system for monitoring the system and troubleshooting
- Caller-IDs can now be configured on a case-by-case basis
- Please take note of the following advice before installing the update:
- We strongly recommend all users of the STARFACE PRO v2 appliance paying extra attention to the free disk space, which should be a at least 2GB when upgrading.
- We strongly recommend using the 'STARFACE Archivierung' module to reduce the size of the caller lists if you are updating from STARFACE Version 5.x or lower.
- The installation of the update can take up to 2 hours, depending on the installed hardware and/or system resources and the amount of data contained in the database.
- MP3 files are no longer permitted as custom ringtones and notification alerts for the UCC Client for Windows. Please convert these to WAV files to retain compatibility with the client. Any existing MP3 files need to be converted.
- The .NET framework 4.5 must be installed before installing the UCC Client for Windows via the MSI package.
- When upgrading from a version older than 5.6, it is necessary to update to version 5.6 or 5.8 prior to upgrading to version 6.1.
- When upgrading from a version older than 6.0, please note that STARFACE 6.1 uses fully qualified formatting for telephone numbers. Please check your COR rules and, if necessary, format them accordingly. For example, a rule set in STARFACE 5 that routes German telephone numbers starting with "01" needs to be changed to "00491"
- If any of the following settings have been altered, please redo them after updating as they will be over-written: 'authuser' in the line configuration, the register line, or the 'host' setting for an M-net provider profile.
- New Features
STARFACE PBX/General new features- The status of the system can now be monitored in the System Status tab of the Administration panel. This can be used to monitor the system and perform trouble-shooting and analysis of issues. It is composed of Reports, System Summary, Utilization and Log Data.
- The preferred number display format (International, National, Subscriber) on telephones, the UCC Clients und in the WebGUI
- The function of a telephone number is now displayed as an icon in the configuration menu for telephones. Ringing can now only be enabled and disabled for user and group telephone numbers
- The UCC Client for Mac has been optically improved, can now be docked into a single window and has has new functions added
- The configuration option 'maximum connections' for lines now restricts the amount of simultaneous calls on the line.
- The display of caller-ids can now be individually configured with various elements such as caller name, caller number, called number and free-text fields
- The Panasonic KX-HDV 130 is now supported
- The Panasonic KX-HDV 230 is now supported
- The Panasonic KX-TGP 600 is now supported
- The snom D375 is now supported
- The snom D715 is now supported
- The snom D725 is now supported
- The snom D765 is now supported
- The Yealink T19P_E2 is now supported
- The Yealink T21P_E2 is now supported
- The Yealink T23P/G is now supported
- The Yealink T27P is now supported
- The Yealink T29G is now supported
- STARFACE UCC Client for Windows
- Integration of the STARFACE Address Book in the UCC Client, including search, detail view, editing and creation of contacts, contacts are now matched when dialing in the quick access bar and call manager
- The UCC Client for Windows is now also available in French
- Optional feature: Display internal phone numbers on BLF key
STARFACE UCC Client for Mac- The UI panels of the UCC Client for Mac can now be docked into a single Window
- A Quick Access Bar has been added
- Integration of the STARFACE Address Book in the UCC Client, including search, detail view, contacts are now matched when dialing in the quick access bar and call manager
Improvements:
STARFACE PBX/General improvements- An alternative Echo Cancellation method (AEC) is now available for STARFACE Compact appliances
- New language files for snom telephones have been added
- The Echo Cancellation type is now selectable (oslec/aec)
- The entry field for MAC address entry is now properly in focus
- The initial configuration of the server can now be performed solely with the keyboard instead of with a mouse
- The ability to setting the Caller-ID (TSI) for faxes is now possible where permitted by the manufacturer, instead of being restricted to the default value.
- Numbers entered as DTMF tones are once again displayed instead of being masked
- The primary internal number and avatar of each user are now integrated into the address book
- Conferences: The Webserver address can now also be saved when https:// is affixed
- Module: IVR mehrstufig: The time-out can now be configured
- Module execution is now also logged in the full-log (Asterisk log)
- A new firmware for the Gigaset N510 has been integrated (Revision 228)
- A new firmware for the snom 300, 320 and 370 telephones has been integrated (Revision 8.7.5.31)
- A new firmware for the snom 700 and 800 Series has been integrated (Revision 8.7.5.11)
- New firmwares for the Yealink T2x series have been integrated
- A new firmware for the Yealink T41 has been integrated (Revision 36.73.150.1)
- A new firmware for the Yealink T42 has been integrated (Revision 29.73.150.1)
- A new firmware for the Yealink T46 has been integrated (Revision 28.73.150.2), and this telephone has had doorline functionality added
- Upgrade of the underlying operating system to CentOS 6.7
- The integration of an LDAP address book has been improved
- The provisioning of NTP-Servers to telephones has been improved
- The order of operations when autoprovisioning devices after a system restart has been optimized
- STARFACE UCC Client for Windows
- Outlook-Integration: Display of names resolved from the Outlook Connector.
- Outlook and address book contacts are now displayed when searching in the Quick Access Bar and Call Manager
- Name resolving from a global exchange address book
- Simplified integration of a Microsoft Exchange server
- Name resolving from public contact folders
- Double-clicking on a Call List entry with a voicemail attached will now start a telephone call instead of playing the voicemail message
- The internal telephone number can now be optionally displayed on a Busy Lamp Field
- Telephone numbers from lists can now be copied to the clipboard
- Call Lists can now be refreshed manually
- Browser windows opened on incoming call can now be closed automatically upon handing up the call
- A menu entry for packaging support-relevant files as a zip-archive has been added
- Sennheiser devices have been integrated
- Call-brokering in Grutzeck Software is now supported
- Reverse-Lookup and name resolving from a global address book
- Outlook Connector: Der Connector now reads telephone numbers from the subject line of an email
- Outlook Connector: Support of Outlook 2016
- Call Grabbing now instantly accepts the call on the primary phone device
- It is now possible to choose if the UCC Client for Windows receives all chat messages exclusively, all installed chat clients receive all chat messages, or an other installed chat client should be preferred when delivering chat messages
- Mouse-over animations in the Quick Access Bar have been improved
- Searching for contacts in the Quick Access Bar has been improved
STARFACE UCC Client for Mac- Improved call list display
- Improved Voicemail list display
- Improved Fax list display
- Improved the redirection window/li>
- The special dialing rules for domestic phone calls in Luxembourg and Liechtenstein are now considered
- Names are now resolved from the 'recently dialled numbers' list
- It is now possible to start an E-Mail and open a Website from the detailled contact view
- Improved headset support
- Filters, selected folders and the selected time period now persist in the list-windows
- The ringing tone can now be configured
- The display of redirections in the redirection pane has been improved
- MacOS X 10.11 ('El Capitan') is now supported
Bugfixes
- Bugfixes
- Fixed: The '%' symbol can once again be used to place variables in the subject line of the conference invitation email [Call# 1044588]
- Fixed: Admin-Phone Numbers: Sorting telephone numbers by user-name was not sorting the telephone numbers correctly
- Fixed: Address Book: It was possible for the address book to prevent the opening of the call list
- Fixed: Interconnection: Two call-eggs would appear when a call that was forwarded across an interconnection was returned due to unavailability of the target user
- Fixed: It was not possible to complete the recording of voicemail announcements with the UCC Client's softphone [Call#1037758]
- Fixed: Conference participants called by the system will no longer incorrectly be asked to enter a PIN
- Fixed: The system backup via sFTP failed if the maximum amount of copies was exceeded
- Fixed: Backup Configuration: The checkbox 'Complete Backup' no longer incorrectly fails to also activate its subordinate check-boxes
- Fixed: A beep will now be correctly played when a call is transferred via the call manager
- Fixed: It was possible for a user without an external phone number to be assigned a group number as their primary internal phone number
- Fixed: It was possible for user data to be changed via the address book [Call#1043712]
- Fixed: It was possible for BLF keys to be duplicated on creation[Call#1041428]
- Fixed: It was possible for function keys to be displayed twice
- Fixed: Performing a call-pickup shall no longer incorrectly flag the initially called agent for 'least recent'
- Fixed: The caller-ID displayed on the telephone was being incorrectly updated to that of the iQueue when a call was answered by an agent
- Fixed: A CCBS-Call would continue to ring on the telephone after declining it via the call manager
- Fixed: It was not possible to decline a CCBS ringback
- Fixed: It was possible for the size of the file nohup.out to increase excessively
- Fixed: An issue regarding the display of a Doorline feed for group members was fixed
- Fixed: The ringing volume of a snom 370 would fluctuate
- Fixed: It was not possible to export data via SMB to a Mac
- Fixed: It was possible for the 'next' button to disappear when creating a new backup schedule
- Fixed: Fax list CSV-Export: Some columns of the fax list contained the wrong data when exporting as a CSV file
- Fixed: Fax list CSV-Export: The wrong character encoding (ISO-8859-1) was being used when exporting the fax journal as a CSV file
- Fixed: Using semi-colons in passwords had unintended consequences
- Fixed: The variable "isAnonymous" of the module function GetCaller() always returned false for outgoing calls
- Fixed: It was possible for the 'telephone-based URL' function key to not work as intended
- Fixed: It was not possible to join a planned conference via the handset button after it had started
- Fixed: A group without a phone number could cause an update to fail
- Fixed: A user without the 'login' permission was not shown an error message when the permission was revoked while they were logged in
- Fixed: Anonymous calls were sometime being displayed incorrectly
- Fixed: It was not possible to hang up a call that was initiated via the call manager while the 'click2dial' call was still ringing
- Fixed: IPA-Profile: Removed erroneous settings from the IPA provider profile
- Fixed: iQueue: Fixed a minor cosmetic bug in the iQueue widget
- Fixed: iQueue: The signalliing of a call in the iQueue widget was incorrect after resuming a call that was placed on hold
- Fixed: It was not possible to start a conference if its start time was more than 10 minutes ago
- Fixed: The line setting "authuser" was not being processed correctly
- Fixed: Deleting an active iQueue agent caused the iQueue widget to display incorrect information
- Fixed: Call Brokering with an IPC turret would sometimes not work [Call#1036065]
- Fixed: It was possible to create multiple telephones with the same SIP Account name
- Fixed: It was not possible to configure a multiple-device ISDN connection on a second card
- Fixed: Module Creator: Umlauts were not encoding properly when contained in a module variable [Call# 1042600]
- Fixed: Fixed an exploit which allowed the password protection of modules to be circumvented
- Fixed: The MWI on telephones was not being resetted when a voicemail message was deleted elsewhere
- Fixed: N510: The name of a user was not being displayed if more than 4 handsets were assigned to a Gigaset N510 base station [Call#1029640]
- Fixed: The initial caller was not being displayed in the call lists after an attended transfer
- Fixed: The name/IP address of the telephone system was not included in automatically generated email notifications
- Fixed: SIP Provider passwords which included a backslash did not allow the server to authenticate with the provider
- Fixed: The Patton Smartnode 4118 was not being autoprovisioned
- Fixed: Proxy settings: It was possible to use the special characters '#' and '$' in the username and password of the HTTP Proxy settings
- Fixed: iQueue: It was, under certain conditions, not possible to transfer a call between iQueues
- Fixed: The 'record' button on some telephones was not working [Call#1035172]
- Fixed: Call lists: Custom filters for the call lists were not being correctly applied
- Fixed: Server/Network/Proxy Settings: The password for the HTTP proxy settings was not masked
- Fixed: It was possible for telephones to get caught in a registration/deregistration loop in Asterisk 11.20
- Fixed: The NTP settings were not being provisioned to the snom 370
- Fixed: It was not possible to sort the mailboxes by name
- Fixed: The sorting of ended conferences was incorrect
- Fixed: It was not possible to have more than 512 telephone number to telephone connections per user
- Fixed: The time-out when dialing over an Austrian ISDN line was incorrectly set
- Fixed: It was possible for a call transferred via the *2 command to bounce back to the original party [Call# 1044939]
- Fixed: Two time-zones were giving the wrong time difference to Yealink telephones
- Fixed: [UCC Client for Windows] The caller name was not resolved if the number was not known to the Outlook Connector call protocol
- Fixed: [UCC Client for Windows] CallTo-Links now work as intended in Windows 10
- Fixed: [UCC Client for Windows] The wrong number was signalled to TAPI after the execution of an 'Ansage vor Melden' module
- Fixed: [UCC Client for Windows] Under certain circumstances it was possible for the UCC Client for Windows to not play its ringing tone on an incoming call [Call#1041945]
- Fixed: [UCC Client for Windows] It was possible for the windows to flicker when run on a terminal server
- Fixed: [UCC Client for Windows] It was possible for audio to not be transferred when the client was run on a device with multiple local IP addresses
- Fixed: [UCC Client for Windows] A tooltip in the 'call direction' column of the call list was incorrect
- Fixed: [UCC Client for Windows] Call list entries were occasionally not being retrieved correctly
- Fixed: [UCC Client for Windows] It was possible for the UCC Client for Windows to crash when installed on a terminal server [Call#1043355]
- Fixed: [UCC Client for Windows] It was possible for certain server permissions to cause the redirection and call list panels to be empty [Call#1043110]
- Fixed: [UCC Client for Windows] It was not always possible to distribute the UCC Client for Windows via a group policy
- Fixed: [UCC Client for Windows] The configuration in the audio settings for Bluetooth audio devices did not persist through a restart of the UCC Client for Windows
- Fixed: [UCC Client for Windows] Fixed an issue which caused the Outlook Connector to fail to connect [Call#1042699]
- Fixed: [UCC Client for Windows] A chat status message would disappear on restarting the UCC Client for Windows [Call#1044279]
- Fixed: [UCC Client for MacOS] The UCC Client for Mac would prevent the system from shutting down under certain circumstances
- Fixed: [UCC Client for MacOS] Fixed an issue which prevented call-pickup via the dropdown menu [Call#1044275]
- Closed Support Tickets
- [5.0.8.4] Closed Support Ticket: Umleitung bei Yealink T46 führt mit QSC zu Problemen [Call# 1043498]
- [5.7.0.7] Closed Support Ticket: Anzeige der Historie auf einem Yealink T42G mit Tag 'JTag' [Call# 1025895]
- [5.8.2.2] Closed Support Ticket: Wenn die Hostadresse des Providers auf Black- und Whitelist ist, greift die Blacklist [Call# 1042209]
- [5.8.2.2] Closed Support Ticket: Umleitungen an Endgeräten bei Yealink T46 verhindern [Call# 1045003]
- [5.8.2.2] Closed Support Ticket: Nach Update kein Einloggen auf GUI der Cloud mehr möglich [Call# 1043439]
- [5.8.2.4] Closed Support Ticket: Archivierung sendet Fehlermails [Call# 1044043]
- [5.8.2.4] Closed Support Ticket: Analog-Gateways (Patton SmartNode SN 44xx) signalisieren CLIP nur jedes zweite Mal [Call#1042287]
- [5.8.2.4] Closed Support Ticket: Fehlende Amtsholungs-Null bei Wahl über T46G-Telefonhistorie [Call# 1040903]
- [5.8.2.4] Closed Support Ticket: Manuelle Leitungskonfiguration funktioniert nicht [Call# 1043220]
- [5.8.2.4] Closed Support Ticket: Unautorisierte Anrufe ins Ausland [Call# 1042757]
- [5.8.2.4] Closed Support Ticket: Verbund mit aktiver Amtsholung verändert die Rufnummernsignalisierung [Call# 1042410]
- [6.0.0.2] Closed Support Ticket: Fehlerhaftes Klingelverhalten bei gleichzeitiger Anmeldung in iQueue [Call# 1035044]
- [6.0.0.2] Closed Support Ticket: "Aktive Anrufe" im Admin-Bereich wird falsch gezählt [Call#1034974]
- [6.0.0.7] Closed Support Ticket: Callhunting-Gruppe mit AvM ruft nur den ersten Agenten [Call# 1037229]
- [6.0.0.7] Closed Support Ticket: Fehlfunktion der 'Einzelne Rufnummer umleiten'-Taste nach Änderungen der betreffenden Gruppe [Call# 1039522]
- [6.0.0.7] Closed Support Ticket: Konferenzeinstellungen: Webserveradresse nicht mit HTTPS einstellbar [Call# 1039450]
- [6.0.1.13 || 6.0.1.44] Closed Support Ticket: 'Ansage vor Melden'-Call am UCC-Client nicht annehmbar [Call# 1043053]
- [6.0.1.13] Closed Support Ticket: Attended Transfer gibt ankommenden Ruf weiter [Call# 1041986]
- [6.0.1.13] Closed Support Ticket: Call Picking via BLF nicht möglich [Call# 1037748]
- [6.0.1.13] Closed Support Ticket: COR-Regel routet falsch [Call# 1042967]
- [6.0.1.13] Closed Support Ticket: Eingehende Faxe werden in Rufliste gezeigt [Call# 1042725]
- [6.0.1.13] Closed Support Ticket: Erster Agent verpasst den Anrufer und alle Agenten klingeln anschließend [Call# 1042667]
- [6.0.1.13] Closed Support Ticket: Faxe lassen sich nicht öffnen [Call# 1042719]
- [6.0.1.13] Closed Support Ticket: Im Modulsystem wird externe Caller ID als interne Caller ID ausgegeben [Call# 1043078]
- [6.0.1.13] Closed Support Ticket: Fehlerverhalten bei iFMC Ruf über Gruppe [Call# 1042652]
- [6.0.1.13] Closed Support Ticket: Gesprächsannahme nach iQueue verzögert [Call# 1042262]
- [6.0.1.13] Closed Support Ticket: Ghostcalls in der iQueue [Call# 1041730]
- [6.0.1.13] Closed Support Ticket: Gruppenweiterleitung greift nach Deaktivieren weiterhin [Call# 1040473]
- [6.0.1.13] Closed Support Ticket: iFMC Gerät klingelt nur wenige Sekunden [Call# 1043120]
- [6.0.1.13] Closed Support Ticket: Mehrere Benutzer klingeln bei Anruf auf Gruppe nicht [Call# 1042542]
- [6.0.1.13] Closed Support Ticket: Modul Gruppen Anzeige: CallerID wird nicht gesetzt [Call# 1041281]
- [6.0.1.13] Closed Support Ticket: Outlook-Connector hat keine Verbindung [Call# 1042699]
- [6.0.1.13] Closed Support Ticket: Patton SN4412 Signalisiert keine CallerID von SmartNode zum Endgerät [Call# 1041317]
- [6.0.1.13] Closed Support Ticket: UCC Client verliert Verbindung [Call# 1043401]
- [6.0.1.13] Closed Support Ticket: UCC Client aktualisiert Rufliste in seiner UI nicht [Call# 1042094]
- [6.0.1.13] Closed Support Ticket: Voicemails werden in der Weboberfläche und im Mac Client nicht angezeigt [Call# 1042503]
- [6.0.2.11] Closed Support Ticket: Anrufe der iQueue-Warteschlange werden nicht zugestellt [Call# 1043936]
- [6.0.2.11] Closed Support Ticket: Autoprovisionierung für Yealink auf 'Accept SIP Trust Server Only' setzen [Call# 1043503]
- [6.0.2.11] Closed Support Ticket: Benutzername und Telefonname wird in Yealink-Telefonen angezeigt [Call# 1043524]
- [6.0.2.11] Closed Support Ticket: Beta-Release verfügbar ohne ?Activate Beta?-Modul [Call#1045530]
- [6.0.2.11] Closed Support Ticket: Eingehende Anrufe nach Update nicht mehr möglich [Call#1045668]
- [6.0.2.11] Closed Support Ticket: Email 'Verpasster Anruf' wird trotz Rufannahme verschickt [Call# 1043525]
- [6.0.2.11] Closed Support Ticket: Hauptnummer nicht erreichbar [Call#1045389]
- [6.0.2.11] Closed Support Ticket: iQueue: Anrufer hört Wartemusik trotz Gesprächsannahme [Call#1042883]
- [6.0.2.11] Closed Support Ticket: Java Exception bei selbst erstelltem Modul [Call#1045676]
- [6.0.2.11] Closed Support Ticket: Email 'Verpasster Anruf' wird trotz Rufannahme verschickt [Call# 1043525]
- [6.0.2.11] Closed Support Ticket: Probleme bei >1.000 User in AD Base DN [Call# 1044180]
- [6.0.2.11] Closed Support Ticket: Leitungen nach Update nicht verfügbar [Call# 1043233] [Call# 1043254] [Call# 1043235]
- [6.0.2.11] Closed Support Ticket: Mehrfach-Signalisierung von Calls in TAPI [Call# 1043755]
- [6.0.2.11] Closed Support Ticket: Modul 'Modul' in der Library [Call# 1043329]
- [6.0.2.11] Closed Support Ticket: Nach Update werden Default- statt Custom-Mailboxansagen abgespielt [Call#1044434]
- [6.0.2.11] Closed Support Ticket: Namensauflösung im UCC Client fehlerhaft [Call#1044663]
- [6.0.2.11] Closed Support Ticket: Ruflisten im UCC Client nach Neustart nicht abrufbar [Call# 1043110]
- [6.0.2.11] Closed Support Ticket: Rufliste zeigt nach Tranfer die interne Nummer an [Call#1043762]
- [6.0.2.11] Closed Support Ticket: Rufnummer, die auf anderen Anlage im Verbund eine Account ID ist, führt zu Problemen im Anruf [Call#: 1046003]
- [6.0.2.11] Closed Support Ticket: Rufnummernanzeige nach zeitüberschreitender Umleitung [Call# 1044447]
- [6.0.2.11] Closed Support Ticket: TAPI Event in unterschiedlichem Format [Call# 1044025]
- [6.0.2.11] Closed Support Ticket: UCC Client für Mac: Fehlermeldung verhindert Abmelden des Rechners [Call#1043590]
- [6.0.2.11] Closed Support Ticket: Voicemailnachrichten werden in der Weboberfläche nicht angezeigt [Call#1045058]
- [6.0.2.11] Closed Support Ticket: Zeitgesteuerte Umleitungen werden nur dann am BLF angezeigt, wenn auch eine dauerhafte Umleitung aktiviert ist [Call#1044279]
- [6.0.9.7] Closed Support Ticket: Bei zeitgesteuerter Umleitung nach extern im HFO NGN ist beidseitig kein Ton zu hören [Call#1045679]
- [IVR-Mehrstufig v53] Closed Support Ticket: IVR mehrstufig: Timeout nicht frei einstellbar [Call# 1043724]
- Closed Support Ticket: [Call# 1040212]
- Main Features of this Version
- Version 6.0.2.11 Released on 2015/09/08
-
Features
- Attention: STARFACE 6.0 uses fully qualified formatting for telephone numbers. Please check your COR rules and, if necessary, format them accordingly. For example, a rule set in STARFACE 5 that routes German telephone numbers starting with "01" needs to be changed to "00491"
- Attention: Please use fully qualified formatting for telephone numbers in modules which react to (or dial) external telephone numbers.
- New firmware for the Yealink T48G
- Customized iQueue announcements can now be uploaded
- NGN is now monitored by the watchdog
- LBR Routing has been introduced. Dialled numbers are expanded according to the location of the system as defined in the administration panel. The procedure for selecting the outgoing line is the same as with CoR Rules
- The TSI of fax machines is displayed as the caller number in the fax list
- Fax numbers are now resolved from the address book
- New Provider profile: M-net
- New provider profile: easybell
- The address of the WebUI is now showed in the browser tab and/or title bar
Bugfixes
- Modules: Fixed a bug in the module "Gruppenanzeige"
- Modules: Fixed a bug in the module "Rückrufbitte per E-Mail"
- Modules: Fixed a bug in the module "Rückrufbitte per E-Mail"
- Modules: Fixed a bug in the module "Rückrufbitte per E-Mail"
- Modules: Fixed a bug in the module "Zeitgesteuerte Umleitung"
- Modules: Fixed a bug in the module "IVR-einstufig"
- Modules: Fixed a bug in the module "Call-Through"
- Modules: Fixed a bug in the module "Benutzerbezogene Rufsperre"
- Modules: Fixed a bug in the module "CallHunting"
- Modules: Fixed a bug in the module "Ansage vor Melden"
- Modules: Fixed a bug in the module "Archivierung"
- Modules: Fixed a bug in the module function "External CallerID"
- Modules: Fixed a bug in the Module Creator
- Modules: Fixed a bug in the module function Voicemail()
- Modules: The module function CallPhoneNumber was not able to initiate an external call if a line prefix was active
- Modules: the module functions isGroup and isUser both returned "true" for an iQueue
- Modules: the encoding of CallerIDs after an executed Ansage vor Melden module was fixed
- Modules: Modules using the entry-point 'on all incoming calls' were not always executed
- iQueue: it was possible for agent intermission to be activated when the setting was disabled in the iQueue configuration
- iQueue: transferring a call within the iQueue granted agent intermission
- iQueue: Agents were not being called via an interconnection after the interconnection was re-connected
- iQueue: Fixed an error for iQueue running with default settings
- iQueue: The caller on the second position was connected before the first
- iQueue: A call will no longer ring for an agent that has already declined the call
- iQueue: It was not possible to transfer a call from one iQueue to another
- iQueue: Fixed an issue that caused an agent to not be called under specific circumstances
- iQueue: The call manager would disappear on picked iQueue calls
- iQueue: Fixed an issue that caused agents to continue to ring after a call was connected
- iQueue: Fixed an issue that caused the iQueue Widget to be empty if it was opened while a call was ringing
- iQueue: Call Monitoring recordings were sometimes being sent to agents
- iQueue: Fixed a counter and empty call lists
- iQueue: The maximum waiting time of the iQueue was not being calculated correctly
- iQueue: Improved the behaviour of iFMC in conjunction with the iQueue
- iQueue: Agent intermission is now correctly assigned when accepting a call with an iFMC device
- iQueue: Updating the agent status during the agent intermission has been improved
- iQueue: Picked calls are now shown next to the correct agent
- iQueue: The iQueue configuration panel has been improved
- iQueue Report: Call duration of calls placed on hold was not being calculated correctly
- iQueue Report: Transfers to iQueue agents were not taken into account
- iQueue Report: Report files were being sent when the tick box was not activated
- iQueue Report: Call Duration was displayed incorrectly
- iQueue Report: Call duration after a call transfer was still counted as connected
- iQueue Report: Transferred calls were not being counted as "answered"
- iQueue Report: Fixed an error on call pick-up
- iQueue Report: External callers were counted as internal callers under certain circumstances
- iQueue Report: Fixed an issue which could cause non-agents to be included in the report
- iQueue Report: Picked calls are no longer listed as "missed" in the call list
- iQueue Report: The sending of the iQueue Report has been improved
- UCI: Fixed a bug in the function getCallState
- UCI: Executing getVoicemailList without a folder limitation returned no result
- UCI: A call on hold was hung up immediately under certain circumstances
- UUCI: Information about the call was erroneous after an attended transfer
- UCI: Improved various functions after feedback from partners
- Conference: "Call" symbol was not working after a manual start
- Conference: Invitation Email was not being sent
- Conference: The conference call will no longer disrupt active calls
- Incoming callers were being connected under certain circumstances
- Reduced the system load when resolving phone numbers from large address books
- Improved compatibility with Firefox 40 and higher
- The wrong deposit was sometimes being selected in multiline configurations
- Erroneous entries for the maximum permitted connections per line are now ignored
- The Fax Journal (PDF) contained double entries
- Call duration was missing in the call list statistics
- Changes to function keys were not applied if one or more keys were invalid
- Emergency Calls were not routed correctly via the interconnection in certain circumstances
- Fax list entries could not be deleted
- Improvements to the Dutch translation made
- A fax modem answered group calls made to remote group members
- Fixed an issue which prevented the Stardial *010 (deactivate redirection-always) from working
- Special characters are no longer permitted in SIP-passwords
- Fixed an error in the assignment of users to groups
- Fixed an issue which prevented the export of system backups via SFTP to Macs
- CallerID was not set when calling a voicemail box
- The display of calls to groups in the call lists has been standardized
- Corrected an error in the display of transferred calls in the call list
- corrected an issue that prevented the creation of call list entries on incoming external calls
- Spaces are no longer removed when creating server certificates
- Fixed an issue which caused outgoing calls to sometimes be labelled as group calls
- The original call is now being hung up after using the star code ** (call2go)
- Fixed errors in the MWI-Status
- Newly created users were not being called after being assigned to a group
- The name of the group was not changed in the call list and call manager after re-naming the group
- Insecure encryption methods for Asterisk were disabled
- Improved the behaviour of the call-hunting group after the execution of a Zeitgesteuerte Umleitung
- Fixed an issue that caused all of a user's telephones to ring if they logged on to a group while an incoming call was ringing in the group
- Corrected an error that occurred on the initial configuration of an iFMC device
- Outgoing calls were displayed as incoming calls under certain circumstances
- Fixed an issue when iFMC was used in conjunction with a voicemail recording
- Fixed an issue that prevented the deletion of group calls from the call lists
- Removed weak SSL cyphers
- Fixed an issue which caused the system to restart frequently after an update
- fixed an issue which caused the iFMC devices of other group members to continue to ring after the call was answered internally
- Fixed an issue which allowed the Stardial *8 to also affect outgoing calls
- Added an online help button for "edit Voicemail box"
- Adjusted the PAI-Domain in the provider profile "Telekom Call&Surf"
- Improved the behaviour of the voicemail list when 6 or more entries were displayable
- An additional group call is no longer displayed in the call list when a blind transfer is returned
- Entries in the voicemail list are now displayed correctly after moving voicemail entries between folders
- Active calls to a group voicemail box can now be picked up
- Users in a fax group now generate correct call list entries
- Entries in the fax list can once again be sorted
- Improved the behaviour of redirects when only using an iFMC device
- Improved the execution of the quick dial function key in conjunction with address book entries
- Entry fields in the tabs "Server" and "Mail Server" of the administration panel are now correctly emphasized if the user attempts to save an invalid setting
- The maximum ringing time increase from 45 seconds (STARFACE 5.x) to 120 seconds (STARFACE 6.x) is now correctly applied when updating from a version lower than 6.0
- Users are now available sooner after renaming their telephones
- Call Monitoring entries are no longer listed twice
- Handling of similar number blocks for CoR Rules has been improved
- Improved the process for adding new emergency call locations
- Logging and handling of changes to the external ip address have been improved
- It is once again possible to monitor calls across the interconnection
- Call Pickup (grabbing) via the interconnection has been improved
- Updateprozess betreffend paralleler Scripverarbeitung verbessert
- The update process has been improved
- Forwarded and missed calls to groups are now correctly displayed in the call lists
- Park&Orbit has been improved for group calls
- The display of new voicemail messages on Gigaset telephones has been corrected
- Display of groups as the call recipient in the call lists has been improved
- Calling behaviour of groups over the interconnection has been improved
- The default signalling number of the fax modem has been changed (see features)
- Improved several localization inconsistencies
- Version 6.0.1.13 Released on 2015/07/10
-
Features
- Update of firmware for Sirrix USBFXS to version 0.8 and of the USBFXS driver to version 150527
Bugfixes
- Firefox 39+: The web interface could not be accessed over HTTPS
- The input 'Auth user' of provider lines did not accept the @-character
- Version 5.8.2.4 Released on 2015/07/10
-
Features
- SSL disabled and switch to TLS with strong ciphers
- Update of firmware for Sirrix USBFXS to version 0.8 and of the USBFXS driver to version 150527
Bugfixes
- Firefox 39+: The web interface could not be accessed over HTTPS
- Function keys with 5-digit IDs did not work properly
- Module Designer created too many HTTP redirects
- Version 6.0.1.12 Released on 2015/07/03
-
Bugfixes
- Some configutations can cause the webserver to restart
- Version 6.0.1.11 Released on 2015/07/01
-
Features
- Communication via the UCC Clients is now encrypted
- Improved support for IPC Telephones
- Support for Swisscom Business Connect has been added
- The HFO Siptrunk/NGN Profile has been optimized
- The 1&1 SIP Trunking Profile has been optimized
- myTweak Provider Profile has been optimized
- Call-Pickup has been implemented for the iQueue
- The display of running managed conferences has been improved
- Security issues have been fixed
- SSL has been discontinued
- TLS with strong cyphers is now used instead
- Integrated the CIFS Options-Flag for Backups on NTLMv2 SMB shares
- Corrected the formatting of user account email addresses with Active Directory
- Improved support for special characters in the Module Creator
- Tariff announcements are now audible
- Version 6.0.0.7 Released on 2015/03/25
-
Bugfixes
- Telephone signalling for group login/logout has been improved
- Fixed an issue where setting the routing priority to Line could cause IVR modules to decline a call
- Fixed an issue where the calling order of Call Hunting group members was disrupted by group login/logout actions
- Fixed an issue that prevented the forwarding of calls to speed dial keys from the call manager
- Fixed an issue where deleting lines with assigned emergency call numbers could cause problems
- Improved the integration of IPC telephones and a services restart is no longer needed to make them accessible
- Improved the response time of Call2Go (Star-Dial **)
- Fixed an issue that prevented attended transfer (*2) via an iFMC device
- The external IP Address check during the backup process has been optimized
- ISDN CallerId signalling on the internal ISDN Bus has been improved
- Star-Dials can now be set as the target of a speed dial key
- Fixed an issue that caused interconnections with overlapping number areas to improperly route calls
- A Timed Redirection module (Zeitgesteuerte Umleitung) instance is now executed before an IVR module instance
- Corrected dialling with Line Prefix for iFMC devices
- Fixed an issue which prevented the iQueue to be unreachable if an agent used *77
- Fixed an issue where the configuration area was not updating the group login status if this was set with a BLF key
- DND has been optimized so that an incoming call that arrives simultaneously with the user setting DND to active will still be connected
- iFMC signalling with "sipconnect" was optimized
- Fixed an issue where certain module functions were not producing the same result as under Bellheimer
- Fixed an issue which prevented the execution of Back-ups to USB stick
- External incoming calls to an unknown telephone number shall now be declined and will no longer be answered with a message
- Improved logging with respect to module execution
- Fixed an issue that prevented the execution of backups in the case of a changed CountryDefaultISDN value
- Improved the stability of the Fax2Mail service
- Version 6.0.0.5 Released on 2015/03/04
-
Features
- IMPORTANT: Please read the following advice BEFORE updating
- The update is being released as a soft-launch. This means that new systems will be deployed with this version pre-installed. Appliances in the field with an update contract can have the update enabled by your STARFACE Partner.
- We strongly recommend creating a backup of your current STARFACE system before updating to the new version. We recommend saving this back-up in a separate location.
- The module "Gruppe mit Warteschlange" has been replaced by the new feature "iQueue". Customers with a current Queue which uses this module will need to transfer their settings to the iQueue in the group configuration options.
- The setting "insecure=very" has been discontinued in some SIP provider profiles. Custom profiles which use this setting will need to change it to "insecure=port,invite".
- Some components in the STARFACE Module system have been changed, as has the call handling. Custom modules will therefore need to be checked after the update has been installed and, in the case of the module no longer working, the module will need to be reconfigured or rewritten.
- In the STARFACE Interconnection all connected locations must be on the same version of the STARFACE software to prevent problems.
- Features
STARFACE UCC Client for Windows
- Features of the new client
- Quick-Access-Bar allows fast access to the core functions
- The innovative panel displays allow the easy configuration of the client
- Calls can be managed completely within the Call Manager, or with Drag & Drop
- Integrated controls for call transferring and telephone conferences
- Interactive function keys
- Call lists, fax lists, voicemail and call monitoring
- Chat client and file transfers
- Integrated Softphone
- URL-Actions can be bound to calls
- Access to door cameras
- Integration of Kuando Busylights
- Pick-up and hang-up calls with Jabra headsets
- Terminal Server integration is possible with an additional licence
- New STARFACE TAPI Service Provider with extended TAPI-Capabilites
- New STARFACE Fax driver
- New STARFACE Microsoft Outlook Connector
STARFACE UCC Client for Mac OS
- Currently in Public Beta
- Features of the new UCC client
- Calls can be managed completely within the Call Manager, or with Drag & Drop
- Integrated controls for call transferring and telephone conferences
- Interactive function keys
- Call lists, fax lists, voicemail and call monitoring
- Integrated Softphone
- Integration of Kuando Busylights
- Pick-up and hang-up calls with Jabra headsets
New Call Handling
- Completely reworked call handling as a stable base for future releases
- Increased capacity for more parallel calls, which enables the support for larger operations
- Faster call placement of calls from public providers
- More comprehensive and concise call lists
- Completely new mechanism for compiling call lists
- Resolution of names in the call list for outgoing calls
- Correct display of iFMC, Call2Go, Redirect, Pick-up, Login calls
- Improved Billing (inclusion of target number, line, caller and call duration)
- Improved call signalling on the telephone display (without 15104230:xxx - no more aXXXX...)
- Unified system for Line Prefixes
- Unified number format for all dialling processes
- Call Time-out limit extended from 45 seconds to 120 seconds
User Functions
- E-Mail notification on missed call
- Group numbers can now also be assigned to individual telephones
- New Call Manager functions
- User avatars
- Unlimited Call transfers, consultation calls and call waiting
- Call2Go and Call Monitoring from inside the Call Manager
- Conference Call management in the Call Manager
- Standardization of ad-hoc, Call-In and Managed Conferences
- Live view of conferences for logged-in users and invited guests (without logging in)
- Display of who is currently talking, who can talk and who can only hear
- Every participant can request talk permission
- Additional users can be added to the conference on-the-fly
Systems changes
- Increased performance, security and the ability to implement additional SIP provider-supported features
- Integration of SIP profiles for 1&1, Deutsche Telekom, mytweak direct (Austria) and HFO Telecom NGN
- Signalling can be adapted on a provider-to-provider basis
- Improved signalling to SIP providers for emergency calls
- The Security Advisor now places SIP providers on the whitelist automatically
- Back-ups can now be exported to Dropbox and via SFTP
- Various improved security provisions for the Web Interface
New iQueue
- iQueue is our new ACD (automatic call distribution) system
- iQueue replaces the feature "Gruppe mit Warteschlange" which was available up to STARFACE version 5.8.2.0 ('Bellheimer') as a module
- The iQueue can be activated by selecting the ringing strategy "iQueue" in the group configuration
- A basic iQueue without configuration options is included for free
- Premium versions of the iQueue are available for one or more queue groups
- Configurable maximum queue length and waiting time
- Configurable options in the case of non-availability
- Upload of individual notifications and announcements
- Calls can be distributed using "parallel" and "least recent" algorithms
- Export of a queue report containing all calls as a CSV file
- Automatic optional recording of agents' calls
- A Queue Monitor pane is available in the Web Interface
- Agent intermission signalled to all users via Busy Lamp Field
Integrations
- EmergencyCall is a new call-processing entry-point for modules
- Component CallPhoneNumber extended with the parameter cancel channel, which cancel the current call, if the selected channel hangs up
- New components are available in the module designer, which provide access to UCI API Calls from within the module system
- Call.Conference - Create conference for users
- Call.getCallIds - Returns all calls of a user
- Call.getCallState - Returns detailed status of a call
- Call.getPhoneIds - Returns all telephones of a users
- Call.hangupCall - Hangs up a specific call
- CcbsCall.GetCcbsAccountState - Returns the status of a CCBS (Call Completion on Busy Status) request
- ConferenceCall.callNumberToConference - Add an additional user to a conference
- Group.GetGroupLogon - Returns if a user is logged on to a group
- Group.SetGroupLogon - Logs a user on to a group
- Group.SetAllGroupLogon - Logs a user on or off for all assigned groups
- MessageWaiting.GetMessageWaitingIndication - Returns the status of the new message indication
- Phone.GetCallWaitingIndication - Returns call waiting indication status of a user
- Phone.SetCallWaitingIndication - Sets call waiting indication status of a user
- Phone.SetPrimaryPhone - Sets the primary telephone of a user
- Redirect.SetRedirectSetting - Sets redirect settings for an account
- UserState.GetChatPresence - Returns the chat status of a user
- UserState.GetDNDSetting - Returns the Do Not Disturb status of a user
- UserState.GetRedirectAlwaysActive - Returns the Always Redirection settings for a user
- UserState.GetTelephonyState - Returns the telephony state for a user
- UserState.SetAvatarImage - Sets the avatar of a user
- UserState.SetChatMessageSetting - Sets the chat presence status of a user
- UserState.SetDND - Sets the Do Not Disturb status for a user
- New UCI 3.0 API, with a greatly increased call handling feature set
- Search Busy Lamp Fields and call grabbing
- Configure call redirects
- Transfer / consultation call / placement on hold
- Configuration of iFMC
- Call2Go, Call pick-up, DTMF, Park & Orbit
- Call Monitoring
- Comprehensive conference call controls
- iQueue management and live-reporting tools
- Einführung neuer Sicherheitsmerkmale zur Auto-Provisionierung
- Provisionierung gegen MAC-Angriffe absichern
- Firmwareaktualisierung der Sirrix USB4FXS2S0-Karte, welche die Stabilität der USB-Kommunikation verbessert
Bugfixes
- WebUI Verbesserung bei der Gruppenanmeldung
- Änderung der Funktionstasten im Administrationsbereich werden nun wieder automatisch provisioniert
- UCI: Mailbox ID in newMessageWaitingIndicationEvent wurde korrigiert
- Leitungsrouting wählt nun wieder die korrekte Leitung
- Korrekturen bei der Amtsholung mit +49
- Nummernformat "international" korrigiert auf das Verhalten in der Version < 5.8
- iQueue Verbesserungen bei der Callzustellung
- Ausgehende Rufe über internes ISDN-Endgerät korrigiert
- Modul Zeitgesteuerte Umleitung und Umleitung bei Zeitüberschreitung korrigiert
- Tarifansage nun wieder hörbar
- Routing Leitung mit ähnlichen Stammrufnummern können wieder genutzt werden
- CallerId-Korrektur am ISDN Mehrgeräteanschluß
- Leitungskonfiguration nach Update aktualisieren
- IMPORTANT: Please read the following advice BEFORE updating
- Version 5.8.2.2 Released on 2015/03/03
-
Features
- Security update for STARFACE Cloud
- Firmware update for Sirrix USB4FXS2S0 cards that improves stability of USB connection
- Version 5.8.1.0 Released on 2014/12/01
-
Features
- New provider profile "Deutsche Telekom Call & Surf IP"
- New provider profile "IP Austria SIP Connect"
- New function keys:
- Function key "Phone menu: address book"
- Function key "Phone menu: call lists"
- Function key "DTMF"
- Function key "Phone-based URL"
Bugfixes
- SIPConnect: CLIP/CLIP No Screening not possible during forwarded calls
- Call to Module Call-Hunting-Hotline leads to wrong PAI inside INVITES with provider "QSC IPfonie extended connect"
- Stability update for Sirrix USB4FXS2S0 cards
- Improved compatibility with provider "HFO Telecom NGN"
- Improved compatibility with signaling profile "sipconnect"
- Version 5.8.0.15 Released on 2014/10/14
-
Features
- NT mode for Sirrix USB4FXS2S0 cards is enabled
Bugfixes
- Stability update for Sirrix USB4FXS2S0 cards
- Firmware update for Sirrix USB4FXS cards in Compact appliances to version 0.6
- Fixes a compatibility issue with hook flash button of analog telephones
- Fixes a denial of service vulnerability in Asterisk
- Version 5.8.0.14 Released on 2014/09/30
-
Bugfixes
- Security update for bash ("ShellShock", CVE-2014-6271, CVE-2014-7169, CVE-2014-7186, CVE-2014-7187)
- Version 5.8.0.13 Released on 2014/08/28
-
Bugfixes
- Audio-optimization on FXS ports of STARFACE COMPACT
- Improvement with provider HFO
- Improvement with provider xpirio voip connect SIP(AT)
- Misconduct of the UCI corrected when diversions is set
- Version 5.8.0.12 Released on 2014/07/11
-
Features
- Supported Hardware:
- The stability of detecting and running Sirrix USB4FXS2S0 cards in Compact appliances has been improved.
- Firmware update for Sirrix USB2S0 cards in Compact appliances to version 0.9
- Firmware update for Sirrix USB4FXS cards in Compact appliances to version 0.5
Bugfixes
- The completion of external call numbers for participants without primary external numbers takes the proper effect again.
- Analog phones remain assigned correctly also after changing the call number of the FXS line in der line configuration.
- Contacts may be deleted from the built-in address book as usual again.
- The buttons for restarting services and system react reliably now.
- Supported Hardware:
- Version 5.8.0.5 Released on 2014/05/20
-
Features
- From version 5.8 on the number of available user profiles on installations without server license ("free edition") is limited to 3 (three). As well, updates will no longer be visible on systems without server license.
- Supported Hardware:
- Detection and support of the new Compact appliance
- Detection and support of Sirrix USB4FSX2S0 cards on STARFACE Compact appliances
- Detection and support of NGN ports on der STARFACE Compact appliances
- Detection and support of the second network adapter on STARFACE Enterprise appliances as NGN port
- Configuration of the OSLEC software echo-cancellation algorithm for the ISDN part of the new Sirrix USB4FSX2S0 cards.
- Sirrix driver update to version 140502
- PBX Functions:
- Configuration of NGN providers in the line setup
- Routing of all SIP and RTP packets from and to NGN providers over the dedicated NGN port
- Exclusive routing of SIP and RTP packets over the configured NGN ports.
- Addition of the NGN route in the "HFO Telecom Business NGN" provider profile for running over the NGN port
- New signaling profile "sipconnect" supplies compatibility with providers using the SipConnect 1.1 standard
- Integration of the SIP provider profile "QSC IPfonie extended connect"
- Integration of the SIP provider profile "HFO Telecom NGN"
- SIP OPTIONS packets (qualify) will now be transmitted for phone devices using NAT for improved detection of network issues.
- With enabled Active Directory Password Management, e-mails to new users will no longer be sent with STARFACE login-ID and password.
- Phone Provisioning:
- Zero-Touch Provisioning of Yealink devices T41P and T48G incl. phone search and STARFACE phonemenus
- Firmware integration of versions 36.72.150.2 and 35.72.150.2 for the Yealink phone models
- Firmware update for Yealink phones T42G and T46G to versions 29.71.150.6 and 28.71.150.18
- Firmware update for Snom 710/720/760 phones to version 8.7.3.25.5
- Logging in on Yealink T4x phones will now automatically provision the users function keys to the phone (Hot Desking BLF).
- The function key DND on Yealink T4x phones will now open the corresponding phonemenu instead of triggering the function on the phone.
- Tiptel 31xx devices will no be provided with volume settings.
Bugfixes
- Increased reliability of the update process with bad or unsteady internet connections
- Call forwarding of anonymous callers using "no screening" into the fixed telephone network will no longer get interrupted with provider HFO Telecom Business NGN.
- Substantial fax documents no longer raise an error or disconnection on STARFACE Clients (Windows/Mac).
- Inbound calls via ISDN will now be processed correctly in case of manually set incoming call number format "NATIONAL".
- The Security Advisor will no longer add "localhost" or "127.0.0.1" to the blacklist.
- The name of a groups?s voicemail box is now properly updated after renaming.
- IP addresses can no longer be on both whitelist and blacklist.
- Multiple call numbers of contacts from LDAP directories get listed in the address book again.
- Inbound and outbound calls can now be processed in spite of compromised data exchange within PBX interconnections.
- Version 5.7.0.7 Released on 2013/12/17
-
Features
- Phone Provisioning:
- The server URL used for autoprovisioning is now selectable for each device.
- Zero-touch provisioning of TipTel devices 3110, 3120 and 3130 incl. phone scan and STARFACE phone menus
- Integration of firmware version 2.0.101 for TipTel 31xx
- Zero-touch provisioning of Panasonic KX-UT133 and KX-UT136 devices
- Firmware update for Panasonic KX-UT13x series to version 01.271
- Firmware update for Gigaset N720 DECT base stations to version v78
- Firmware update for Gigaset N510 DECT base stations to version v194
- Firmware update for Gigaset DE700/DE900 devices to version v02.00.08
- Firmware update for Gigaset DE310/DE410 devices to version v02.00.05
- Firmware update for OpenStage SIP devices to version V3 R1.44.0
- Firmware update for Yealink T4x devices to version 28.71.150.16/29.71.150.5
- Provisioning of up to three Yealink EXP40 key extensions per T46G device
- The manual configuration of IPC phones offers administration of SIP interconnections with IPC systems.
- PBX Functions:
- Automatic blacklisting of suspicious IP addresses on failed login trials via SSH
- New option for installation and running on Microsofts virtualization platform Hyper-V
- The certificate management now works with 2048bit encrypted certificates.
- Integration of the SIP provider profile "HFO Telecom Business NGN"
- Expanded manual configuration of SIP provider profiles with authentification modes and cross-line call number detection
- An update of the Linux kernel improves the load balancing on appliances of the series Platinum and Enterprise.
Bugfixes
- An update of the tone schema in the Gigaset autoprovisioning removes an audible busy signal before ringing.
- Conference invitations sent by e-mail now consider time zones and daylight saving time.
- Fix for wrong labeling in STARFACE phone menus
- Adjusted ISDN ton schemata for Malta and Luxemburg
- Solves an issue which caused the line configuration to be get applied only after saving them repeatedly.
- Solves a major issue which didn't prevent assigning emergency numbers as internal numbers.
- Call pickup with *8 now works properly on internal ISDN phones, the MSN of which are also internal call numbers.
- Conferences can get started again by the OK button in the Callmanager.
- Phone Provisioning:
- Version 5.6.0.9 Released on 2013/10/08
-
Bugfixes
- The line configuration allowed to assign concurrent call numbers to two or more phone lines.
- Editing contacts in the LDAP addressbook in combination with the use of account IDs will no longer cause an error and abort.
- Module updates were not working.
- Switching off authentication in provider lines didn't get saved.
- Removing a provider line caused an unnecessary restart of the phone services.
- The line configuration listed only up to ten lines.
- Cancelling/leaving the update overview without available updates was blocked.
- The progress window for running backups did not open.
- An irrelevant warning of the autoprovisioning was logged during system start.
- Version 5.6.0.6 Released on 2013/09/10
-
Features
- Security
- Extended auto-detection of potential attacks over the internet
- Automatic blacklisting of suspicious IP addresses on
- call attempts without prior authentication,
- autoprovisioning attempts of unknown devices when the MAC address filter is enabled,
- unauthorized access to the STARFACE phone menu,
- failed login attempts in the STARFACE web interface,
- failed login attempts via XMPP or chat client,
- failed login attempts via STARFACE UCI
- Authentication for access to the STARFACE phone menus on devices by Gigaset, Yealink, Snom and Aastra
- Opportunity for administrators to confirm phones added by autoprovisioning for the first time
- The integrity of the built-in firewall is now checked after each service restart and restored if necessary.
- STARFACE user passwords must now be at least 8 characters long.
- Active Directory Password Management
- Passwords for web interface, chat and CTI can be managed in the Windows domain.
- STARFACE user can log in to the web interface, chat and CTI with their Windows username and password now.
- Configuration of the domain and Active Directory server in the administration
- Email addresses of STARFACE users must now be assigned unambiguously.
- System functions:
- The line configuration now provides creation and management of locations.
- SIP phones can be assigned individually to locations.
- Assocation of lines and emergency call numbers to locations.
- The incoming phone number format for ISDN can now be overridden individually for each line.
- Detection of DTMF input on calls from SIP devices of type "fax" will no longer be executed.
- Accelerated call handling in scenarios with status signaling on a large numbers of BLF keys
- The intercom settings now offer to set up a DTMF code without giving a camera URL.
- Supported hardware:
- Zero-touch provisioning of Yealink T46G and T42G devices including phone search and STARFACE phone menus
- Integration of the firmware for the new Yealink phones in versions 29.71.150.2 and 28.71.150.9
- Update of the DAHDI driver to version 2.7.0
- Security
- Version 5.5.0.20 Released on 2013/08/07
-
Bugfixes
- Added missing French translations for the web interface
- Prevents the WebUI from freezing in certain situations
- Fixes a bug in the inbound call number resolution causing calls to get rejected
- Solves the issue of emergency configurations not being active after backup imports until the line settings have been changed manually
- Fixes a bug which occasionally caused misconfigurations of Sirrix ISDN cards after updates and backup imports
- Solves an issue on transferring function keys with labels containing umlauts to OpenStage phones
- Version 5.5.0.14 Released on 2013/07/09
-
Bugfixes
- Introduces a short call cancellation on inbound ISDN calls through Sirrix cards in order to detect potential overlap dialing from the trunk line
- Outbound call numbers are now entirely internationalized based on the user's primary external number before a COR rule gets applied
- The resolution of inbound call numbers now also accounts for local area codes to broker calls between users in different local areas on one PBX
- The provisioned settings for Patton analog gateways have been reversed to the ones in version 5.3.0.9
- The status of function keys in the web interface gets refreshed reliably again
- E-mails will from now on be sent from the address set in the mail server administration. The user's address will only appear in the "ReplyTo" field
- Removes the cause for an Asterisk crash when processing SIP PUBLISH messages
- Removes irritating but harmless error messages in the error log
- Version 5.5.0.9 Released on 2013/06/11
-
Features
- Important Note:
This version cannot get installed by updating from STARFACE 5.3 or earlier and therefor will not be available for those systems. Systems of the model series SMALL BUSINESS APPLIANCE and PROFESSIONAL APPLIANCE - out of production since the end of 2008 - will no longer be supported from this version 5.5 on. The latest available version for these systems is STARFACE 5.3.0.9.
The update of the Linux operating system requires a completely fresh installation of the system. Before you install, please backup the system by download, e-mail or Windows share, and create an installation medium.
- Linux OS Updates:
- New Linux system 64bit based on CentOS 6.4
- Updated Linux kernel to version 2.6.32-358.el6.x86_64
- Updated DAHDI driver to version 2.6.2 mit libpri 1.4.14
- Updated Sirrix driver to version 120626
- Updated Hylafax fax system to version 5.5.2
- Updated Tomcat web server to version 6.0.24
- Updated PostgreSQL database to version 8.4.13
- Updated JavaVM to version 1.6.0_45
- Installation/Initial Configuration:
- Simplified system deployment by complete re-design of the system's initial configuration process
- Optional system update in step 1 of the initial configuration
- Backup restore in step 1 of the initial configuration for quick migration
- Considerable reduction of required configuration steps to get a running new system
- New option for installation on VMware
- Browser Interface:
- The applied HTML and Javascript have been completely restructured on basis of HTML5.
- Compatibility with current browsers: Internet Explorer 9, Safari 6, Firefox 20, Chrome 26
- Converting the voicemail player to HTML5 provides playing voicemails in all browsers.
- The auto-search for system users in the Callmanager now shows all presence states.
- The redesign configuration of the NTP service allows using multiple NTP sources.
- The settings of the internal addressbook has been extended by a field for the federal state.
- The IP addresses of Openstage devices in the phone configuration are now hyperlink via HTTPS.
- PBX Functions:
- Accelerated call initiation on inbound calls over ISDN by using number subranges in the line configuration
- Automatic installation of VMware Tools after installing on VMware ESXI
- Automatized management of the RAID system with e-mail notifications on new STARFACE Enterprise and Platinum appliances
- Improved performance of RAID systems in legacy STARFACE Enterprise and Advanced Appliances
- Several optimizations for running with SIP trunks, especially QSC and Patton
- Module System:
- Conversion of the logging mechanism from database to file system
- Module instances now produce a maximum of 30 MB of log files.
- Module instances only log events of the level set in the module configuration.
- Windows shares will no longer be mounted within a module instance.
- Phone Provisioning:
- The autoprovisioning of Gigaset DECT bases c470 IP, C475 IP and S685 IP has been disabled.
- Firmware update for Yealink devices to generation V70
- Firmware update for Atlinks devices to generation V70
- Firmware update for Gigaset N720 to version v69.1 for more dependable provisioning
- Firmware update for Grandstream ATA HT702 and HT704 to version 1.0.4.8
- Firmware update for Aastra phones to version 3.2.2.7137, resp. 3.2.2.3077
- Provisioning for Polycom conference phones with firmware 4.0.5.0
- Provisioning of maximum 20 keys per Yealink key extension
- Provisioning of an unlimited number of Yealink EXP39 key extensions
Bugfixes
- Modules using Windows shares no longer produce disproportionately large backup files.
- Backup import with alternate IP addresses now adopt the NTP settings again.
- Solved an issue which prevented editing datasets of LDAP addressbooks.
- Avatar image uploads larger than 3 MB now raise an error notification.
- Addressbook entries with call numbers containing '-' (minus) are now considered in the call number resolution.
- The list of voicemail boxes is now ordered by mailbox numbers.
- The integrated fax subsystem identifies itself to remote stations with 'STARFACE' and no longer with 'NothingSetup'.
- In order to avoid acoustic feedback, DTMF input will no longer be played on Snom Meetingpoint.
- Important Note:
This version cannot get installed by updating from STARFACE 5.3 or earlier and therefor will not be available for those systems. Systems of the model series SMALL BUSINESS APPLIANCE and PROFESSIONAL APPLIANCE - out of production since the end of 2008 - will no longer be supported from this version 5.5 on. The latest available version for these systems is STARFACE 5.3.0.9.
- Version 5.3.0.9 Released on 2013/04/30
-
Features
- Firmware update for Yealink to version V70 for compatibility with devices currently in distribution
- Firmware update for Gigaset N720 to version v69.1 for more reliable provisioning
Bugfixes
- Click2Dial with iFMC phones now works more reliably in combination with fixed-line prefix and SIP trunks
- Outbound calls with fixed-line prefix to numbers from the addressbook over BLF function keys now work more reliable
- Outbound calls with fixed-line prefix over quick dial function keysn now work reliably
- The fixed-line prefix is now automtically prepended to call numbers when they get assigned to a quick dial funtion key
- Version 5.3.0.7 Released on 2013/03/18
-
Features
- Firmware update for Gigaset N720 DECT base stations to version v68
- Firmware update for Gigaset N510 DECT base stations to version v76
- Update of JavaVM to version 1.6.0_43
Bugfixes
- Improves stability of Enterprise and Platinum appliances in combination with Digium B410P BRI interfaces
- Improves reliability of Hot Desking function keys on Openstage devices in case the device is assigned to a new user via web frontend
- Corrects a problem with wrong account information displayed on Openstage devices after autoprovisioning
- ClickToDial works now reliable on Openstage devices if the device is manually renamed after successful autoprovisioning
- The group strategy "Broadcast" works reliably in combination with Openstage devices
- Calls from the server based addressbook on Gigaset devices now take the line prefix correctly into account
- Version 5.3.0.3 Released on 2013/01/22
-
Features
- Significant quality improvements in the rendering of outbound faxes
- Faxes with different page formats within one file get rotated, scaled and transmitted properly now
- Firmware update for Gigaset N720 DECT base stations to version v67
- Firmware update for Gigaset N510 DECT base stations to version v75
- Firmware update for Siemens OpenStage devices to version V3R1.38.0
- Firmware update for Snom 7xx phones to version 8.7.3.19
Bugfixes
- E-mail notifications of voicemails now also get sent for calls processed through modules
- Improved reliability of the hardware watchdog in Enterprise v4/Platinum v4
- Fix for an issue with the processing of BMP files for avatars of function keys and Picture CLIP
- The routing now correctly takes account of state changes of the function key "Display Number"
- Increased performance and reliability on accessing large LDAP addressbooks
- The network telephone scan works more dependably in conjunction with Patton gateways
- Version 5.3.0.0 Released on 2012/12/03
-
Features
- PBX Functions:
- Provisioning of Patton analog gateways of series SN4112/JS, SN4114/JS, SN4118/JS, SN4412/JS, SN4416/JS, SN4424/JS, SN4432/JS via phone scan
- Provisioning of Grandstream analog adapters HT702 and HT704 via phone scan
- Firmware version 1.0.4.3 integration for Grandstream analog adapters HT702 and HT704
- Firmware version R6.2_2012-09-11 integration for Patton analog gateways SN44xx and SN411x
- Handsets on Gigaset N510 now also feature attended transfers by call hang-up
- Firmware update for Gigaset DE700 / DE900 devices to version v02.00.04
- Firmware update for Gigaset DE310 / DE410 devices to version v02.00.01
- When logging in on an OpenStage phone the user?s function keys will be transferred automatically to the device. (Hot Desking BLF)
Bugfixes
- The group strategy "Call-Hunting" hands the call to the next user, if the group number doesn?t ring on any of the current user?s phones
- The backup configuration on Windows Shares now supports user names containing space characters
- The backup configuration on Windows Shares now supports hidden shared folders
- Changing the password for Windows Shares in the backup configuration works reliably again
- Conference scheduling accepts manual input of call numbers with three or more zeros
- Conference scheduling now accepts input of arbitrary e-mail addresses
- The template file for user imports can now still get downloaded after several weeks of system uptime
- Greater reliability and performance of call operating with faulty configurations of the LDAP address book
- Improved voice quality and reliability of call recording and call-brokering with G722 audio on several phones
- Now, when set on hold by a remote party (ISDN over Digium B410P cards), the remote ? not the local ? MOH is played
- When two B channels of a BRI on a Digium B410P card are busy, a third caller now gets rejected with "No circuit or channel available" instead of "Incompatible destination"
- Further optimization of "Group with Waiting Queue", especially on extensive use of the agents GUI
- PBX Functions:
- Version 5.2.1.0 Released on 2012/10/16
-
Features
- PBX Functions:
- Introduction of the new standard module "STARFACE Archiving"
- Hardware Support:
- Detection and support of the new Advanced Appliance
- Detection and support of the new Enterprise Appliance
- Detection and support of the new Platinum Appliance
- Phone Integration:
- Preset SIP profile for softphone Ninja
- Considerably simplified access to the STARFACE phone menu on Aastra 6739i devices
- Firmware update for Aastra phones to version 3.2.2.6268/3.2.2.2104
- Firmware update for Gigaset N720 DECT base to version v40
- Firmware update for Gigaset N510 DECT base to version v72
- Firmware update for Alcatel Temporis phones to versions 13.60.0.89, 14.60.0.89 and 15.60.0.89
- Firmware update for Yealink phones to versions 2.61.0.146, 6.61.0.146, 7.61.0.146 and 9.61.0.146
- Firmware update for Tiptel phones to versions 2.61.13.18, 6.61.13.18, 7.61.13.18 and 9.61.13.18
- Firmware update for Panasonic phones KX-UT1xx and KX-UT248 Telefone to version v01.167
- Firmware update for Snom 8xx and 7xx phones to version 8.7.3.10/8.7.3.11
- Group with Waiting Queue:
- Increased stability and reliability on many concurrent calls
- Improved stability and performance of large waiting queues
- Great increase of performance of groups with many agents
- The log files are now stored on the file system replacing the database within the module
Bugfixes
- The microphone of Aastra phones is now immediately on when calling by ClickToDial
- Solves an issue with the time-switching to winter time on Panasonic devices
- Autoprovisioning of Gigaset devices now also works with usernames containing "&"
- Fixes a glitch in the addressbook window with multiple call numbers of LDAP entries
- Fixes the selection of voicemail announcements of users with multiple voicemail boxes
- Module Scheduled Forwarding now also processes Dutch date input
- New auto-generated user passwords are now stored reliably and will be sent by e-mail again
- The group strategy Software Fax2Mail again processes e-mails to more than five group members
- The mail server administraton now validates e-mail addresses more reliably
- Passwords of Windows Shares for the backup location now also may contain commas
- Calls can no longer be answered on iFMC devices when they have already been picked up on an other device
- When deleting user accounts the assigned iFMC numbers become available again
- Custom provider profiles now account for the setting "qualify=no", if "auth mode" is set to "IP address"
- The mailbox indicator of the telephone is displayed correctly again after assigning the device to a user via web frontend
- PBX Functions:
- Version 5.2.0.10 Released on 2012/08/07
-
Features
- PBX Functions:
- Support of door intercom systems of selected vendors with display of camera video in the Callmanager and comfortable DTMF code for opening the door
- Display of camera video from door intercom systems on Gigaset DE900 IP PRO and DE700 IP PRO
- CallerID update on call placement
- New permission for receiving system e-mail notifications
- New permission for configuration and use of function key "Module activation"
- New permission for user login and logout on phone devices by key codes *77 / *78 / *79 or via STARFACE phone menu
- New permissions for administrators, by which the sections users, groups, phones and modules can be hidden from the administration interface on per-user basis
- Outbound faxes are now stored with the file quality they were actually sent
- Detection and configuration of Digium TE407PF 4xE1 adapters of STARFACE edition
- Administration Interface:
- Administration of user avatars
- Deletion of multiple voicemail boxes at ones
- Removal of already set internal and external conference numbers
- Template variables for the e-mail invitation can now also be used in the e-mail subject
- The line configuration now takes care that SIP usernames for authentication are not assigned twice.
- Phone Provisioning:
- System call lists, call forwardings and visual voicemail on Gigaset DE700 IP PRO and DE900 IP PRO
- Firmware update for Gigaset DE700 / DE900 devices to version v02.00.03
- Firmware update for Gigaset DE310 / DE410 devices to version v02.00.00
- Firmware v38 for Gigaset N720 DECT base stations including access to system phonebook
- Firmware update for Gigaset N510 DECT base stations to version v70
- One-Touch Provisioning for Panasonic KX-UT248
- Firmware version 01.103 for Panasonic KX-UT248
- Provisioning of function keys for Panasonic Android phone KX-UT670
- Firmware update for Panasonic KX-UT670 to version 01.050
- Firmware update for Panasonic KX-UT1xx series to version 01.133
- Firmware update for Siemens OpenStage devices to version V2 R2.47.0
- Firmware update for Snom 820 / 821 / 870 to version 8.7.3.7
- Zero-Touch provisioning of the new snom 710 including phone network scan and STARFACE phone menu
- Hardware Support:
- Detection and configuration of Digium TE407PF 4xE1 adapters of STARFACE edition
- Update of JavaVM to version 1.6.0_33
Bugfixes
- The routing priority 'Line' now chooses the line for call forwardings to the fixed network by means of the signalled number of the forwarding user
- For decreased disk usage, outbound faxes will be stored with the file quality they were actually sent ? not as original files
- The fallback for loss of the SIP connection in PBX interconnections over the primary external number works reliably again on basis of the set COR rules
- iFMC devices of all group members now ring reliably on calls for the group
- The validation of e-mail addresses in the web interface has been adjusted for new top level domains
- Outbound calls over line prefix by Callmanager and by redialing out of call lists with iFMC device now work properly
- The BLF state of groups gets updated properly now when users register or log out of groups by function keys, phone menu or *32/*33
- Addressbook change from LDAP to built-in got fixed
- Problems with sending e-mails no longer affect call functions
- The group status on BLF keys is now indicated correctly after the first user has logged in by function key.
- Inbound faxes with comma in the RemoteStationID get processed reliably now.
- Saving invalid function keys now cancels with an appropriate notification.
- E-mail notifications for updates include release notes again.
- Group with Waiting Queue:
- In the browser interface calls can again get picked up which are not being connected
- The module can now play music-on-hold after intermediate announcements when calls come in over Digium cards.
- Fix for an issue causing agents to get stuck in the wrong call status
- Fixes a bug by which callers and agents could not be connected successfully
- The module detects failed connection attempts by caller hang ups more reliably.
- Increased reliability of call handling at especially high call traffic
- More precise consideration of individual agent intermissions
- Distracting messages get removed from log files
- PBX Functions:
- Version 5.1.0.13 Released on 2012/07/13
-
Bugfixes
- Group with Waiting Queue:
- In the browser interface calls can again get picked up which are not being connected
- Fix for an issue causing agents to get stuck in the wrong call status
- Fixes a bug by which callers and agents could not be connected successfully
- Increased reliability of call handling at especially high call traffic
- More precise consideration of individual agent intermissions
- Distracting messages get removed from log files
- Fix for wrong validation of e-mail addresses with more than three characters in the top-level domain
- Group with Waiting Queue:
- Version 5.1.0.10 Released on 2012/05/29
-
Features
- Existing modules cannot be run with this version.
Please check the availability of your deployed modules and upgrade them accordingly after updating the system. Then, built-in modules may get downloaded over the new integrated update mechanism.
Modules created by users will have to be opened and saved once again in the Module Designer after the system update!
- Modules:
- Automatic updates for modules in the STARFACE administration interface
- Update search for built-in / purchased Modules for each available STARFACE Version
- Module update integrated in the system update process
- Support for Modules purchased over a license document
- Easy installation of purchased Modules by input of license keys
- The function EMailGet now also can handle self-signed certificates
- PBX Functions:
- Initiation of Ad-hoc conferences with caller and all calls on hold by dialing *3 during a call
- Picture-CLIP: Display of user avatars on inbound calls on supported devices Gigaset DE700 / DE 900, Snom 720 / 760 / 820 / 821 / 870, Yealink T32 / T38
- New function key type for switching the outbound signalled call number via BLF keys
- Users with disabled call waiting indication (CWI) will now be busy from the very call placement, inbound calls will no longer be routed
- The entire web interface as well as all announcements are now available in French
- User Interface:
- Call numbers in the call list can now be marked by double click for copy and paste
- The phone selection for call placement has been removed for users with only one phone device
- Administration Interface:
- Viewing and setting group forwardings can now be controlled by a dedicated user right setting
- Passwords of provider lines (SIP passwords) will no longer be displayed as plain text
- The list of phone devices can now also be searched by assigned users
- Hardware-Echo-Cancellation for new ISDN lines is now enabled by default, if applicable
- The IP address used for a PBX interconnection can now be set on PBXs with multiple network interfaces
- The server address for phone provisioning can now be configured in the autoprovisioning settings
- The license overview has been divided for server and module licenses
- Phone Provisioning:
- One-Touch provisioning for Aastra SIP devices of the 675x and 673x series incl. phone search and STARFACE phone menus
- Zero-Touch provisioning for Alcatel devices Temporis IP200, IP600 and IP800 incl. phone search and STARFACE phone menus
- Zero-Touch provisioning for Yealink devices T20P, T22P, T26P, T28P, T32P and T38P incl. phone search and STARFACE phone menus
- Zero-Touch provisioning for Snom 720 and 780 devices incl. phone search and STARFACE phone menus
- One-Touch provisioning for Panasonic KX-UT1xx series and KX-UT670 device
- Zero-Touch provisioning for Gigaset N720 PRO Multicell-Dect solution
- Integrated firmware for Aastra phones version v3.2.2.2044 bzw. v3.2.2.6038
- Integrated firmware for Alcatel phones versions 13.60.0.77, 14.60.0.78, 15.60.0.80
- Integrated firmware for Panasonic phones versions UT11x12x-01.081_HW1, UT13x-01.081_HW1, UT670_01.023
- Integrated firmware for Yealink phones versions 2.61.0.80, 6.61.0.83, 7.61.0.80, 9.61.0.85, 32.0.150.3, 38.0.150.3
- Integrated firmware for Snom 720 / 780 version 8.7.2.9
- Integrated firmware for Gigaset N720 DECT-Bases version v35
- Firmware update for Gigaset DE700 / DE900 devices to version v01.01.14
- Firmware update for Gigaset DE310 / DE410 devices to version v01.00.08
- Firmware update for Gigaset N510 DECT-Bases to version v51
- Firmware update for Snom 300,320,360,370,820,821 and 871 to version 8.4.35
- Firmware update for Tiptel devices to versions 2.61.13.6, 6.61.13.6, 7.61.13.6, 9.61.13.6, 18.0.13.8
- Lists in STARFACE phone menus are now displayed unnumbered
- Template for printing BLF labels of Aastra phones
- Template for printing BLF labels of Panasonic phones
- Template for printing BLF labels of Siemens OpenStage 15
- Improved template for printing BLF labels of Snom phones
- Short date and time format in the call list of the STARFACE phone menu
- Update of core components:
- Update of the Linux kernel with updated network drivers
- Update of Asterisk Business Edition solves issues with receiving faxes over QSC
- Update of DAHDI driver to version 2.5.1.0
- Update of the JavaVM to Version 1.6.0_31
Bugfixes
- Avatars of function keys now get displayed properly in Internet Explorer 9
- User passwords may now include the '§' character
- The status indication for lines now also works reliably with multiple cards of the same type within one line
- The call order of group members persists throughout logging in and off via *3
- Voicemail lists again show entries for which have a call list entry no longer exists
- The country setting for call number format and ring-tones used by the autoprovisioning is now according to the country setting of the line configuration and not the user language
- The outside line prefix on inbound signalled numbers persists also with forwarded calls
- The addressbook view of contacts requested over LDAP now can also be ordered by name and forename
- The call number format with an additional '9' between country and area code for imported numbers gets processed correctly with the provider SipCall
- The display of server certificates now gets clipped if the contents is too large to fit in the window. A double-click will open them for a complete view in a pop-up window
- Groups on function keys are no longer green but gray if they?ve no users logged on
- Users on function keys are no longer green but gray as long as there?s none of their phones ringing
- Autoprovisioning of Gigaset devices now also works reliably in cases with no device provisioned in ten days
- Blocked UCI clients no longer prevent sending server events to other UCI clients
- iFMC now shows correct CLIP for users on a remote interconnection PBX if the outbound line supports CLIP No Screening
- Failed call attempts to iFMC devices get terminated properly
- The Callmanager of the user interface responds reliably to calls transferred from and answered on an iFMC device
- ISDN phones on Digium B410P now work reliably after switching the configuration from an external to an internal port
- The outside line prefix on inbound signalled numbers persists also with calls forwarded outbound, if the outgoing line supports 'CLIP no screening'
- The caller number now gets signalled correctly on iFMC devices also with an outside line prefix set, if the outgoing line supports 'CLIP no screening'
- The phone selection for call placement remains in position if its window?s height exceeds the viewport of the browser
- Outbound calls to iFMC devices get terminated properly as soon as a call redirection sets in
- Now the correct target number is shown when editing BLF function keys.
- Call numbers in the redial list of the Callmanager now include the outside line prefix where neccessary.
- The replay of voicemail announcements works again for users with more than one phone assigned.
- Users calling with an ISDN phone over a Digium ISDN card now get indicated properly on BLF.
- Existing modules cannot be run with this version.
- Version 5.0.0.14 Released on 2011/12/21
-
Features
- Downgrade of Tiptel-Firmware due to sporadic missing audio after call-waiting in later firmware version
Bugfixes
- Enables provisioning of function keys including soft-label for snom 820/821 telephones
- Display of umlaut- and special-characters on function keys of snom 820/821/870 telephones fixed
- Fixes multiple issues with fax-downloads in the web interface
- Fixes an issue in the setup of Polycom conference telephones
- Autoprovisioned phones keep their registration after renaming the telephone name in the admin interface
- Call forwarding settings of other users are now displayed correctly in the web interface with Internet Explorer 8 and 9
- Changing the assignment of Number-to-Telephone in user properties is now reliable
- Changing the setting "Ask for confirmation before deleting entries in this window" is now reliable
- Enhanced reliability of starting and calling a scheduled conference via web interface
- Fixed a display issue in the admin interface if the admin user did not have proper priviledges for user settings
- Fixed a bug in the UCI interface, resulting in mixed-up caller and callee after a connect event
- Call-Task in the web interface now closes reliably after blind-transfer of an external outgoing call
- Call-Task in the web interface now closes reliably after transfer of a call that was held before
- Fixes a problem with the module function "TextToSpeech"
- Beep on transfer is now enabled for transfer after consultation call via SIP telephone
- Redudancy-Module: The standby system does not overwrite configuration of OpenStage devices after restart anymore
- Version 5.0.0.10 Released on 2011/12/01
-
Features
- Call grabbing with *8 plus group number now also incorporates calls to individual group members if the grabbing user is a member of this group
Bugfixes
- Solves an issue by which the 'head numbers' of Austrian phone lines could not be reached
- Fixes a bug by which the addressbook in the web interface could not get opened
- The group strategy "Call Hunting" now also takes into account whether the members are actually logged in to the group
- Grabbing calls for group numbers via *8 works again
- Version 5.0.0.9 Released on 2011/11/29
-
Features
- User Interface:
- Newly designed function keys incorporate phone status, DND, call forwarding, presence and avatars in a compact layout.
- Addressbook and lists now offer multi-selection, multi-delete and column customization by drag and drop.
- Personalisation of function window characteristics: Button display in the menu bar, confirmation dialogues on deletion of list entries and update of list contents
- Fax transmission reporting as cover page and e-mail notifications
- Export of fax journals as PDF or CSV for current fax list selection
- Concise indication of system-wide DND state, if enabled
- Administration Interface:
- New section "Security" assists in avoiding potential misuse of SIP accounts by automatic whitelisting and blacklisting of IP addresses.
- Setting of minimum password strength in the section "Security" for automatically generated, autoprovisioned or manually set SIP passwords
- Extended settings in the phone administration provides protection of web interface and administrator logins of phones (Snom, Gigaset Pro, Openstage, Tiptel) by autoprovisioning with consistent usernames and PINs
- Display and setting of system-wide DND status in the user administration
- Function key configuration in the user administration
- Extended user permissions for function keys and iFMC
- Setting of the call order for call-hunting groups by drag and drop in the group administration
- Option to have groups not displayed in chat clients (XMPP) by default
- Fax journal export as PDF or CSV in the statistics section
- Optional submission of error reports to STARFACE on each manual service restart and update
- PBX Functions:
- The IAX phone plugin is no longer supported and will be disabled automatically on update.
- No automatic restart: The PBX will no longer be restarted every night (former default procedure). Thus, the module Disable Restart is obsolete.
- Unified Communication Interface (UCI) 2.2 extends the function range by group information and the new STARFACE function keys for integration in CRM/ERP systems.
- Integrated Fixed Mobile Convergence (iFMC) provides incorporation of mobile phones as devices into the PBX system with parallel call functionality.
- Quick cal handover (Call2Go) offers easy change between phone devices during a call (also with iFMC) by dialing '**' on the device key pad.
- Attended Call Transfer during calls (also via iFMC) by dialing '*2' on the device key pad.
- The group call stategy "Call Hunting" takes account of the set order of group members.
- The new gruppen strategy "Software Fax2Mail" submits received faxes to each group member by e-mail.
- Integration of a new default music-on-hold (only on new installations)
- Phone Provisioning:
- The phone autoprovisioning is now enabled by default during installation/first configuration.
- Transferring function keys to a phone now requires the device to be autoprovisioned beforehand.
- Autoprovisioned access passwords prevent modification of phones by unauthorized persons.
- Indication of general call redirections in the display and on function keys of OpenStage 20, 40, 60 and 80 devices
- Access to the PBX call lists from the STARFACE phone menu on supported snom and Tiptel models (Replaces the redial list on snom phones.)
- Indication and setting of system-wide DND from the STARFACE phone menu on supported Snom and Tiptel models (Does not replace the phone-related DND function on Snoms!)
- New idle screens for autoprovisioned devices of type Snom 360, Snom 370, Snom 820, Snom 870 and Tiptel IP 286 (no longer on Tiptel IP 284)
- Firmware update for Snom phones to version 8.4.32 by autoprovisioning
- Firmware update for OpenStage phones to version V2R1.28.0 by autoprovisioning
- Firmware update for Gigaset DE410 IP and Gigaset DE310 IP to version 01.00.06 by autoprovisioning
- Firmware update for Gigaset DE900 IP and Gigaset DE700 IP to version 01.01.10 by autoprovisioning
- Firmware update for Gigaset N510 IP to version 42.0.0.49 by autoprovisioning
- New SIP providers:
- Support of provider Silver Server
- Support of provider IP Austria
- Support of provider Sipcall Pro and Sipcall Business
- Hardware Support:
- Detection and configuration of Digium B410PF 4xS0 STARFACE model cards
- Detection and configuration of Digium TE122PF 1xE1 STARFACE model cards
- Detection and configuration of Digium TE207PF 2xE1 STARFACE model cards
- Detection and configuration of Digium TMD410PF FXS/FXO STARFACE model cards
- Only Digium cards with STARFACE Edition firmware get detected and supported!
- Cards of type Bero*fix are no longer supported.
- Changed power-off on appliances: In order to shut down the device, the power button has now to be pressed three times within 30 seconds.
- Update of Core Components:
- Update of the Linux kernel includes fixes for corrupt file systems and updated network drivers.
- Changed to Asterisk Business Edition C
- Migration from Zaptel 1.4 to Dahdi 2.5.0.2
- Update of the Sirrix driver to version 111111
- Update of Tomcat to version 5.5.34
- Update of Postgres database to version 8.3.15
- Update of JavaVM to version 1.6.0_29
- Module System:
- Now ressources can be changed retroactively in the Module Designer.
- New module function "SendFax" for sending PDF files as fax
- New module function "EMailGet" for fetching e-mails from POP3 or IMAP e-mail boxes
- New module function "GetUserForEMail" for identification of STARFACE users by e-mail address
- IMPORTANT NOTES ON MODULES:
- Please check the compatibility of your applied modules before updating STARFACE.
- Be sure to have all your modules up-to-date before updating STARFACE
- Do not update if your system depends on functions of non-compatible modules
- Find updated modules for STARFACE 5 on store.starface.de/shop/modules/compatibility.php?userversion=5.0.
- User Interface:
- Version 4.6.7.3 Released on 2011/09/27
-
Bugfixes
- Fixes an issue which occasionally made calls over certain ISDN lines impossible
- Integration of ISDN-card driver SRX-110725
- The addressbook could no longer be accessed after certain changes by an administrator
- A newly added function key of type 'Redirection all' ('busy' or 'Timeout') also set the general redirections in cases where no such key (type 'Always') existed
- Solved the issue of the line configuration not being applied after updates (related to Austria only)
- Version 4.6.7.0 Released on 2011/05/17
-
Features
- PBX Functions:
- Integration of SIP provider profile "QSC IPfonie extended"
- Integration of SIP provider profile "Xpirio VoIP Connect SIP" (Austria)
- Profile "Sipgate Team" renamed as "Sipgate trunking"
- Phone Provisioning:
- Update of Tiptel firmware V60 for improved stability and reliability
- Support for Tiptel devices IP282 und IP28xs
- The system language of Tiptel devices gets now provisioned according to the language preferences of the primary user
- Autoprovisioning of up to 6 SIP accounts on Gigaset DECT base N510 IP PRO
- Firmware update for Gigaset DE900 IP PRO and DE700 IP PRO to v01.01.01
- Module System:
- Function GroupQueue adjusted for "Gruppe mit Warteschlange" version 5xx
- Gruppe mit Warteschlange 5xx: Call placement now also takes idle times of agents into account, who work in multiple Queue Groups
- Gruppe mit Warteschlange 5xx: Concurrent placement of multiple calls to idle agents with ringing strategy 'least recent'
- Gruppe mit Warteschlange 5xx: New XML-RPC interface provides remote access to protocol data
- Please check the compatibility of your Modules with STARFACE 4.6:
https://store.starface.de/shop/modules/compatibility.php?userversion=4.6
Bugfixes
- Bulk import of large numbers of user accounts from CSV files now works perfectly again
- STARFACE phone menus on Tiptel devices run reliably again even in case of forced HTTPS
- Autoprovisioning of Gigaset devices DE900 IP PRO and DE700 IP PRO even in case of forced HTTPS
- The setting "Firmware update" is now considered with all Gigaset devices
- Provisioning of Gigaset devices now treats umlauts correctly
- Changes of contacts in the LDAP address book are now transfered correctly again
- Solves an issue by which participants of a terminated phone conference turned and remained unavailable
- Bugfix for the search input of the Callmanager showing outdated name entries
- Managed conferences can now automatically dial call numbers beginning with "+"
- Fixed a flaw in the call placement which caused occassional rejects of outgoing calls with some SIP providers
- The line configuration now gets stored properly again after realigning PCI cards
- PBX Functions:
- Version 4.6.5.1 Released on 2011/03/30
-
Features
- PBX functions:
- Configuration of function keys by drag&drop in the web interface
- Optional limitation of recording time for voicemails per voicemail box
- Optional setting per voicemail box for announcements without leaving messages
- Provisioning with 2.0 Beta4 firmware for BeroFix cards
- Support of hardware watchdog in Enterprise Appliance
- Phone provisioning:
- Firmware update V60 for Tiptel improves stability and support for KD 39 key extension
- Firmware update for Gigaset DECT to version 2227 increases interoperability with G722
- Please check the compatibility of your Modules with STARFACE 4.6: https://store.starface.de/shop/modules/compatibility.php?userversion=4.6
Bugfixes
- Fixes erroneous behavior of "Redial on busy" (CCBS) occasionally causing calls to not get connected
- Bugfix for "Redial on busy" (CCBS) not being offered as a call option when the call had been placed over the web interface
- Detection of non-responding IAX modems and their restart increases reliability of "Software Fax" and "Software Fax 2 Mail"
- Firmware provisioning for Tiptel phones will now be run over HTTP exclusively, resulting in greater stability of the devices during provisioning
- Failed call attempts via UCI and Callmanager will now be detected after maximum 30 seconds, which especially improves the interaction of ISDN phones and CTI
- Bugfix for fax transmission over UCI, where a prefix erroneously was added to the destination number
- Fix for seamingly deleted voicemails which still could get played though
- PBX functions:
- Version 4.6.1.1 Released on 2011/01/20
-
Features
- STARFACE Function Keys:
- New key type for server side DND
- New key type for redial on busy
- New key type for (de-)activation of all permanent call forwardings
- New key type for (de-)activation of all call forwardings on busy
- New key type for (de-)activation of all call forwardings on no reply
- New key type for parking and holding calls in system wide call queues
- Phone Provisioning:
- Support of STARFACE phone menus on TipTel 286 and 284 devices
- Firmware update for TipTel phones to version V60 by autoprovisioning
- Copying function keys to TipTel devices now requires enabled autoprovisioning
- Firmware update for OpenStage phones to version V2R1.21.0 by autoprovisioning
- All autoprovisioned devices now show the primary internal extension instead of the SIP name in their displays
- All autoprovisioned devices now get acknowledged of server restarts and update their configurations accordingly
- The provisioning of Gigaset DECT devices now sets a correct NTP server, if known
- The provisioning of Gigaset DECT devices now sets G722 ass preferred codec
- SIP profile "aastra DECT" provides caller ID update on the device after call answering
- Module System:
- New module function: CSVWriter for easy creation of CSV files
- Change of the module file type to .sfm to avoid automatic unpacking in some browsers
- 'Gruppe mit Warteschlange' 4xx: New version supports changed announcements
- 'Gruppe mit Warteschlange' 4xx: Support for separate reports of different module instances
- PBX Functions:
- Now system backups can be restored right on the initial system configuration
- All announcements have been thoroughly revised and partially newly recorded
- Full support for the configuration of ISDN lines in the Netherlands
- Preset SIP profiles for Dutch providers Breezz, X2Com, Infopact Allesin1 and Infopact IP-Dialtone
- Configuration of automatic error handling for the ISDN driver on ISDN communication failure
- Sirrix PCI2e1 and PCI1e1 ISDN cards now also supported for running in mixed mode
- Update of core components increases stability, reliability and security:
- Update of Linux kernel and subsystems to the latest patch levels
- Update of Sirrix driver to version 101216
- Update of Postgres data base to version 8.3.12
- Update of JavaVM to Version 1.6.0_22
Bugfixes
- Call grabbing over *8 now also works for group calls
- Improved signalisation for lines of provider dus.net with enabled "no screening"
- Fixes the issue that the search in the STARFACE phone menu didn't work with umlauts
- Solves wrong signalisation of calls transferred to fixed network when "no screening" was enabled
- Fixes a bug in the fax transmission with fax numbers prefixed with +49
- When unregistering from the primary phone with *78 the latest set device reliably becomes the primary one now
- Trying to delete an already deleted fax or voicemail via UCI will no longer throw an error
- Solves a rare problem on assigning members in the group administration
- The phone scan no longer activates the "dhcp" option of Linksys PAP2T by default
- Fixes the issue of fax transmission failures because of signaled numbers being too long
- Solves the issue by which dialout via short dial (*6X) failed if the stored number included non-digit characters
- STARFACE Function Keys:
- Version 4.5.2.0 Released on 2011/01/14
-
Features
- The head numbers of Austrian ISDN extensions can now get called without manual configuration
- Configuration with more than 1000 internal call numbers are now supported
Bugfixes
- Integration of Sirrix driver 101216
- Solves an issue which caused occasional disfunction of outgoing phone calls on some ISDN lines
- Provides configuration of automized measures for line errors
- Updated Linux kernel fixes occasional system crashing, especially in conjunction with Windows shares
- Fixes the rare scenario in which external callers could get connected unintentionally over PBX Interconnection
- Deletion of voicemails will no longer delete the corresponding call list entries
- Fix for Toplink Euroflat CH2/CH4 configuration which blocked incoming calls
- Solves an issue causing wrong voicemail entries for external callers in call lists
- Fix for faulty naming of voicemail attachments
- Solves a problem, because of which inquiry calls/transfers to users who had originally transferred the same call could not be performed
- In the module Call-Hunting-Hotline every caller was able to transfer calls
- This update will not replace customized default MOH sound files with the original MOH
- Version 4.5.1.0 Released on 2010/10/20
-
Features
- Zero-Touch autoprovisioning of TipTel 286, 284 and 280 phones
- Firmware update to version V2R1.20.0 for Siemens OpenStage phones by autoprovisoning
- CallerID update on Siemens OpenStage phones after successful call forwarding
- Firmware update to version 8.4.21 for snom phones by autoprovisoning
- Gruppe mit Warteschlange: The display widget no longer shows other modules
- More appropiate filenames for better archiving of fax and voicemail attachments
- Added module function SFtpStore for copying files by SFTP
- Added module function SendDTMF2 for playing DTMF tones
Bugfixes
- Solves an issue by which ISDN phones couldn't place calls over the browser interface or by UCI
- Sets the EHLO hostname for E-Mails over SMTP to the value given in admin interface
- Fixes a bug which caused login problems for single users after addressbook imports
- The settings for the STUN server are now stored properly again
- Solves an issue by which busy callers could not be called over the function keys
- Restores the call number display in the function keys
- Improved performance and reliability of the database on multiple concurrent accesses
- The SIP profile "Gigaset DECT" now offers click2dial function
- Please check the configuration of your music-on-hold, the factory-default might have been restored.
- Version 4.5.0.3 Released on 2010/09/08
-
Bugfixes
- Restricts the caller-ID update on phone displays to phones with the SIP profiles "snom", "tiptel" and "aastra"
- Provides enabling and disabling of TLS in the configuration for external mail servers
- Fixes an issue in the configuration of SIP profiles using "outboundproxy"
- Fixes the display of the module "Gruppe mit Warteschlange"
- Version 4.5.0.0 Released on 2010/08/24
-
Features
- Browser Interface:
- Automated e-mail notification for available updates
- Contact import into the STARFACE addressbook by CSV file
- TLS support for configuration of external mail servers
- Automatic e-mail alert on insufficient free hard disk space
- Notification in the web interface when general call redirections are changed over phone devices
- Significant performance improvements of the line configuration
- STARFACE Function Keys 2.0:
- Identical functionality in the web interface and on Snom, Openstage and TipTel phones
- Call status indication for users and groups with call pickup option
- Enabling and disabling of general call redirections via phone keys and GUI keys
- Login and logoff for groups via phone keys and GUI keys
- Activation and disactivation of module configurations via phone keys and GUI keys
- Module System 4:
- Lifecycle entrypoints allow execution of functions on loading, deleting, activation and disactivation of module instances
- Removal of Asterisk 1.2 call functions from the function library
- Completely reengineered function library for STARFACE call functions
- Many new module functions for lists, maps, I/O and STARFACE entities
- Please check your deployed modules for compatibility issues before updating from the Module Store!
- System Functions:
- Update of the call number display on the phone after call transfers
- Signalisation of the original callee and the destination number on call forwarding and inquiry calls
- Tagging calls as private by dialing *2 as prefix
- Support of HD audio codec G722 for SIP devices
- Support of Sipgate Team provider lines
- Support of Toplink Euroflat provider lines
- Update of known servers for Dusnet lines
- Phone Provisioning:
- One-touch-provisioning for Gigaset DECT C470 IP, C475 IP,S685 IP and S685 IP including support of NetDirectory addressbook
- Snom firmware update to version 8.4.18 via autoprovisioning
- Preparation of STARFACE provisioned phones for HD audio (G722) via phone detection and autoprovisioning
- Restriction for SIP devices to five simultanious calls
- Phone detection and autoprovisioning including phone menu of Snom SIP phones 820, 821, 870
- Phone detection and autoprovisioning of TipTel SIP phones with firmware version 2.5
- Auto-completion for call number input in Snom phone menus
- Hardware Support:
- Detection and setup of BeroFix 4S0 ISDN cards
- Detection and setup of Sirrix PCI1E1 ISDN cards
- Discontinued Hardware Support:
- Cards by Digium no longer supported
- Cards by Sangoma no longer detected and supported
- Xorcom Astribank no longer detected and supported
- Please check your deployed hardware for compatibility issues before the update!
- Update of Core Components:
- Linux kernel updated to version 2.6.18
- Asterisk updated to version 1.4.33.1
- Sirrix driver updated to version 100820
- Postgres database updated to version 8.3.10
- JavaVM updated to version 1.6.0_20
Bugfixes
- Solves an issue causing incomplete download of update packages
- Solves an issue causing occasional database restart hang-ups on updates
- Solves an issue causing erroneous rotation of some Asterisk and Postgres log files
- Solves an issue preventing the file user_module.conf to be loaded
- Solves an issue causing faulty allocation of ISDN phones to SRX groups
- Solves an issue because of which redirections to international call numbers with '+'-prefix could not be set
- Solves the issue of wrong voicemail count in the phone menu
- Solves an issue because of which Redial-on-Busy on lines without prefix did not work
- The listing of addressbook data in the phone menu is now identical to the listing in the web interface
- The test of the SMB settings for backups on Windows shares now works again
- Browser Interface:
- Version 4.1.0.4 Released on 2010/07/15
-
Bugfixes
- Integration of Sirrix driver 100503:
- Solving a compatibility issue with some interal ISDN devices.
- Fixing DTMF signal blocking speech transmission with calls bridged over two ISDN channels.
- Solving an issue of assigning incoming calls to wrong callee
- Specific local area numbers could only be dialed with a line prefix
- Function keys may now be copied to the phone even if auto-provisioning is disabled
- Setting internal call numbers with four ciphers is now working
- Mobile integrations (UCI 2.1) now place calls reliably when general line setting has prefix
- Auto-detection and configuration of Polycom SoundPoint BootRom 4.2.1 and higher
- Call strategy "Last Recent" now working properly with module "Gruppe mit Warteschlange"
- Please note: This update may change the order of multiple identical Sirrix cards. Please check the line settings in the configuration!
- Integration of Sirrix driver 100503:
- Version 4.1.0.0 Released on 2010/04/20
-
Features
- One-touch autoprovisioning for Openstage phones
More informationen at wiki.starface.de - Saving of preferences for cal list, fax list and voicemail list in the web interface
- Auto-detection and configuration of the new Sirrix PCI4S0ec ISDN card
- Detection of and support for the next generation of STARFACE PRO and STARFACE ADVANCED appliances
Bugfixes
- Ringing strategy Callhunting now recognizes disabled call waiting of group members
- The function keys of the web interface display the correct call number again for called contacts
- The redial list of the Callmanager is correctly updating now when reopening the window
- Mobile integrations (UCI 2.1) now can dial call numbers containing whitespaces
- Mobile integrations (UCI 2.1) now can set redirections to voicemail boxes with German umlauts in their name
- Enhanced reliability of the module "Gruppe mit Warteschlange" in combination with Windows shared folders
- Further minor bugfixes
- One-touch autoprovisioning for Openstage phones
- Version 4.0.2.12 Released on 2010/03/23
-
Features
- Mobile Client Adapter for the new STARFACE Client for BlackBerry®
More Information at wiki.starface.de - Web interface:
- Dutch localisation
- Faster perfomance of call lists
- Standardized lists for calls , faxes and voicemails
- New dialog for checking voicemails
- Phone support:
- Logging in and off for groups via phone menu
- Provisioning of TipTel 280, 284 and 286 by automatic phone search
- Copying of function keys to TipTel 280, 284 and 286
- Supporting Aastra6739i in automatic phone search
- Supporting Grandstream up to firmware 1.2.2 in automatic phone search
- Voice notification on outgoing calls, if phone is not assigned to any user
Bugfixes
- Integration of Sirrix driver 091119
- Complete call functionality (signalling/call lists/Callmanager/integrations) for Module "Gruppe mit Warteschlange"
- Removed a bug occasionally preventing XMPP service from restarting
- Improved watchdog for SIP service
- Bugfix for occasional misinterpretation of local external numbers as numbers of the PBX
- Ringing strategy Callhunting takes now into account when group members have disabled call waiting
- Correct updating of the voicemail indicator on user logout on the phone
- Now the prefix for outgoing lines is also used in interconnections
- Improved stability and performance of the UCI results in less Verbindungsabbrüche des STARFACE Client for Windows
- Fix for a bug breaking fax transmission via WinClient
- Several fixes related to call signalling in both Callmanager and function keys
- Mobile Client Adapter for the new STARFACE Client for BlackBerry®
- Version 4.0.1.14 Released on 2010/02/11
-
Bugfixes
- Autoprovisioning sets again the STARFACE Idle-Screen on Snom Phones 360 and 370
- Autoprovisioning sets the phone-language according to the STARFACE server settings
- Autoprovisioning does not change the ringer to "Ringer 1" after every reboot anymore
- A bug in the autoprovisioning causing wrong status indication of busy lamp fields on transfers got fixed
- Version 4.0.1.11 Released on 2010/01/26
-
Features
- The auto-scan for phones now detects and configures Tiptel IP 286 phones
Bugfixes
- Fix for a bug when dialing with function keys in the web frontend
- Several problems of fax list in the web frontend are solved:
- Faxes could not be deleted.
- Faxes could not be moved to different folders.
- Multiple faxes could not be displayed in succession.
- Version 4.0.1.10 Released on 2010/01/19
-
Features
- Compatibility with Estos MetaDirectory LDAP address directories
- Support for provider Solcon
Bugfixes
- Solved, serious problems:
- Fix for a critical storage problem with the XMPP server now provides more stable WinClient connections.
- Fixed a problem causing outgoing international calls to get routed only with line prefix.
- Removed a block of the PBX on calls via UCI over wrongly configured HTTP clients
- Improvement of the interconnection of systems with multiple network adapters
- Further important improvements:
- Short dial from the addressbook (*6) with active line prefix could not initiate calls.
- In some cases modules did not get executed on all group strategies.
- Phone menus always adapted the server language setting, not the user preference.
- In some cases conference members could not get added from the addressbook
- Group names did not get updated via XMPP (Chat).
- Call redirections for primary internal numbers blocked group calls for remote users in an interconnection.
- Occasional problems on connection to the interconnection after server reboot got fixed.
- Phone menus didn't work with HTTPS only.
- Interconnection sometimes didn't reconnect after network breakdown.
- Callmanager:
- Forwarding to mailbox caused an incorrect announcement.
- Display on initiating a spontanious conference after transfer was incorrect.
- Display on confirmation of a conference request after transfer was incorrect.
- When rejecting a blind transfer, the call didn't return to the initial caller.
- Modules:
- 'Gruppe mit Warteschlange': The Module indicated incorrectly for local agents.
- 'Gruppe mit Warteschlange': The Module didn't hang up for remote agents, after the caller had hung up.
- 'Ansage-vor-Melden': Module didn't respond with call-hunting groups.
- Module designer: Problems blocking copy and paste of entire module functions are now fixed.
- Module designer: Context menus didn't get displayed in very long module functions.
- Module configuration: Stack-traces were not put out in module log.
- This update contains further security relevant clean-ups and improvements, as well as many minor enhancements of the GUI
- Version 3.5.1.1 Released on 2009/12/14
-
Bugfixes
- Fax was received but not passed to the right user
- Fax list: Faxes to groups were listed only for one member
- Problems on concurrent reception of large amounts of faxes
- Module Gruppe mit Warteschlange:
- Caller got lost
- Callers remained in the call queue when forwarded between group queues
- Modules: Function VoicemailSystem now optionally enforces mailbox password
- A service restart did not restart the messaging service
- Astribank of type 113n was not detected after updates
- Web service could get started several times
- Improved performance of the watchdog
- On concurrent reception of two faxes, one fax was not delivered properly by e-mail and fax list
- Version 4.0.0.7 Released on 2009/11/18
-
Features
- STARFACE PBX Interconnection: STARFACE interconnection joins multiple locations into one unit
- Users and groups can be called over internal numbers between locations
- No difference between local system and interconnection systems on phone calls or call management
- Users and groups of remote locations can be set on BLF (Busy Lamp Fields) in both web interface and phone keys
- Users of all locations can be assigned to local groups (group call rings across the interconnection)
- Detailed configuration features for release of user and group information of single PBXs
- Routing offers breakout over different systems of the interconnection
- Fallback on Fixed Line for internal calls, if interconnection is unavailable
- STARFACE phone menus now offer classic system phone features for Snom telephones
- Login and logout on the phone including primary phone setting
- Display and check of voicemail boxes and voicemails
- Call redirections for users and groups
- Access to the STARFACE phonebook
- Call number display configuration
- Redial
- Zero Touch Deployment: Zero-Touch Autoprovisioning offers fully automatic configuration on plugging Snom phones
- Automatic detection and configuration of Snom 320, Snom 360 and Snom 370
- Automatic firmware updates (optional)
- Whitelisting for MAC Addresses (optional)
- Unified Communication Interface: The new UCI 2.1 interface extends the feature range for the integration of CRM/ERP systems
- Checking and setting call redirections
- Checking of call, fax and voicemail lists
- Deletion and moving of entries in call, fax and voicemail lists
- Voicemail replay
- Download of voicemail and fax files
- Improved features of the web interface: STARFACE 4.0 comes with useful upgrades of the web interface
- Multiple selection and search function for selection lists
- Upload of custom voicemail announcements for each user
- User search with auto-completion and status indication in the Callmanager
- Saving of redirections only effects redirections actually changed
- Improved login and logout on telephones
- The phone is set as primary phone via *77 or the system phone function
- The primary phone is reset on the former primary phone by *78, *79 or the system phone function
- Increase of physical data security: Autorepair function for STARFACE Appliances with RAID controller
- Automatic re-synchronization after swapping a hard disk in a RAID system
- Automatic e-mail notification on the RAID status after malfunction and repair
- Before you update, please check your installed Modules for compatibility with STARFACE 4 and deactivate effected Module configurations!
Bugfixes
- Fix for 4.0.0.5: Internal ISDN phones could not place outgoing calls
- STARFACE PBX Interconnection: STARFACE interconnection joins multiple locations into one unit
- Version 2.0.1.1 Released on 2006/11/23
-
Features
- Bugfix Release
Bugfixes
- LDAP-Layout fixed
- Audio file improvements
- Usage of AMT-Prefix
- Display of Callmanager fixed
- Call answering with Webphone in Internet Explorer fixed
- Text corrections in Webinterface
- Download of TAPI Service Provider in Internet Explorer fixed
- Improvements in Callmanager