Version 6.7.0.17 Released 07/23/19

  • [h=3]Features:[/h]

    • 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.
      • 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 5223) 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

      • Die Release Notes for the UCC Client for Windows can be found here.
      • Die Release Notes für the UCC Client for Mac can be found here.



    [h=3]Bugfixes:[/h]

    • 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.




    Earlier releases...

  • Dear Forum participants,


    there have been problems with STARFACE systems on version 6.7.0.11 and 6.7.0.17 connecting to our download server. It was not possible to update system on these releases.
    We have released a module to solve this issue: https://knowledge.starface.de/x/wokDAg
    The module needs to be imported and activated, followed by a restart of the STARFACE system.


    We we release version 6.7.0.18 without the problem shortly.


    We would like to apologize for the inconvenience caused.


    Best regards,
    Your STARFACE Team

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!