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
    • You can find the release notes for the UCC Client for Windows here.

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: Events were not being triggered by the fax list
    • 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



Earlier releases...