From v12.20 on you have to enter the address and port of the authentication service for connections via RemoteConnector in the SwyxIt! configuration.
Important: For reliable compatibility with SwyxWare 12.10 the firmware on Yealink phones must be updated: • SwyxWare 12.10 customers who do not use a local copy of the Yealink firmware in their LAN (Standard use case), must get the new firmware version 66.84.133.8 via Swyx Control Center manually. • SwyxWare 12.10 customers who use a local copy of the Yealink firmware instead, must place both firmware versions, 66.84.133.1 and 66.84.133.8, in the same local folder so that Yealink phones can be updated to the new firmware. The corresponding URL to the locally stored firmware 66.84.133.8 must be entered into Swyx Control Center. • SwyxON customers do not need to perform any of the above steps! If the above steps have been performed, the Yealink firmware will be automatically updated to the current version as soon as the devices are connected.
If no user is logged in to a certified SIP phone, no calls (including emergency calls!) can be initiated from this phone.
Information for existing customers with Yealink phones: The method of logging in to the device has changed: From now on the "User PIN on Desk Phone" must be used to log in. With the same PIN the user can also log in to a SwyxPhone.
The extended DCF 2.0 functionality is not yet available with SwyxWare 12.10 for the following devices: Yealink CP-920, CP-960.
It is not recommended to change the selection in the configuration wizard from Swyx Messenger to SwyxIt! Messenger again at a later time, otherwise all Swyx Messenger chats of all users will be deleted!
The option "Show calendar" in the context menu of the SwyxIt! speed dials does not work if the Swyx Notes Integration is used.
Phone number resolution does not work if SwyxIt! is opened before the Notes client.
SwyxWare 12 is supported on the following Windows operating system versions:
SwyxWare 12 supports the following database versions:
Please refer to the Release Notes for a list of supported hardware devices.
For detailed server hardware recommendations see:
https://www.swyx.com/products/support/knowledge-base/article-details/swyxknowledge/kb4621
SwyxWare 12 can update SwyxWare 2015 R40.3 or a previous 11.xx.xx version. Updates from older versions are not supported. Updates of SwyxWare Compact are not supported. Please contact your reseller for migrating options.
The recommended update procedure is to update SwyxServer first, then SwyxWare Administration. Client should be updated last.
It is recommended to update SwyxWare directly instead of removing the old version first.
You need a "SwyxServer 12 Update" license to be able to run SwyxWare 12 after an update from any SwyxWare 11 or older version. SwyxWare setup asks you for an update license key.
Note that the aforementioned license has nothing to do with the "Software Update Licenses Service" key. See also: https://www.swyx.com/products/support/knowledge-base/article-details/swyxknowledge/kb2928
For detailed installation instructions see the SwyxWare Administrator Documentation. You can find user manuals online at https://help.swyx.com
Online Licensing of SwyxWare 11.50 and higher is not supported in Master - Standby scenarios.
Ensure that the latest Windows operating system Service Packs and SQLServer Service Packs are installed as well. We recommend to have Windows Update enabled to automatically get important Microsoft security updates for your operating system.
The server components of SwyxWare should be updated first, then the SwyxIt! clients. Older SwyxIt! versions are not fully supported and need to be updated to v11.
It is not recommended to remove the older SwyxWare version first.
If you are updating your SwyxStandby systems please refer to the following Knowledge Base article for detailed installation instructions: https://www.swyx.com/products/support/knowledge-base/article-details/swyxknowledge/kb3171
Make sure that the Windows account used for running the SwyxWare 12 setup has got administrative rights on the system where SwyxWare is installed.
Please note that the user account used for running the SwyxWare services must not have administrative rights. If you have created the service account for yourself, make sure that the account is not a member of the local administrators or domain administrators group. This ensures that SwyxWare services do not run with higher privileges than necessary.
It is highly recommended to use the same Windows domain account for installation or update of the Master and the Standby SwyxServer. This account needs local administrative rights on both systems.
When using SQLExpress on the standby server you have to install the 'Replication' feature of SQLExpress before installing SwyxWare.
A Windows server can have multiple IP addresses permanently or temporarily, for example, when using multiple network cards or remote access software. Under such circumstances, SwyxWare services might use a wrong IP address. Therefore the preferred IP address can be configured within the Windows registry. Please add to the registry key HKEY_LOCAL_MACHINE\Software\Swyx\General\CurrentVersion\Options a string value named "LocalIpAddress" and set the value to the IP address the SwyxWare services ought to use. Please add to the registry key HKEY_LOCAL_MACHINE\Software\Swyx\General\CurrentVersion\Options a string value named "LocalIpAddress" and set the value to the IP address the SwyxWare services ought to use.
Using STUN for SIP Trunks please keep in mind that the STUN server must be always available. Otherwise telephoning is sometimes not possible via these Trunks.
The delivered Compatibility List "ProviderProfiles.config" configures STUN.SWYX.COM for some providers instead of their own STUN server. This Swyx STUN Server is only meant as a placeholder. It isn't always available. Please replace this STUN server on the tab "SIP" in the Trunk Group properties using a STUN server which is supported by the provider.
SwyxWare Administration 12 requires Microsoft .Net Framework 4.7.2, which is either part of the Windows operating system or can be installed via Windows Update.
To record or play back WAV files for music on hold or voicemail, SwyxIt! 12 must be installed on the same system.
To configure SwyxPhone firmware update, SwyxWare Administration is able to retrieve the firmware information from the FTP server you configure. You do this by opening server properties, select tab page "SwyxPhone Firmware Update”. Enter the FTP server information and click "Get". On Windows 7 or Windows Server 2012 R2 or newer the built-in firewall is enabled by default and blocks FTP traffic. If you click on "Get" without configuring the firewall, SwyxWare Administration will freeze.
To configure the firewall for FTP access, open a command prompt and enter these two commands:
netsh advfirewall firewall add rule id="FTP (no SSL)" action=allow protocol=TCP dir=in localport=21
netsh advfirewall set global statefulftp enable
This applies to the firmware information retrieval via SwyxWare administration only. For the actual firmware update, SwyxPhones need FTP access to the server you have configured.
SwyxWare Administration 12 package contains the "Active Directory Integration" component. This component integrates into the Microsoft "Active Directory Users and Computers". MMC snap-in allowing basic SwyxWare Administration tasks directly from this snap-in.
On a 64bit platform, the Active Directory Extension is available only for the 64bit version of the "Active Directory Users and Computers" MMC snap-in.
Windows 7 x64 Edition: These editions do not have any Active Directory tools installed by default. You must install a 64bit version of "Windows Server 2008 Remote Server Administration Tools for Windows Vista" and run the 64bit version of the "Active Directory Users and Computers" MMC snap-in to use Active Directory Extension.
Via "Remote Admin Connector" the Partner Level Administrators SwyxON can get access to the SwyxWare Administration of their customers to directly configure the corresponding UC Tenants. The "Remote Admin Connector" is included into the SwyxWare installation package, though it can only be installed by applying the corresponding command line parameter as described below.
msiexec /i Admin64.msi RemoteAdminConnector=1
SwyxWare Setup window appears.
Swyx Control Center is a web-based configuration tool providing for customers a possibility to perform basic configuration of SwyxWare (server and user properties).
This version is a bugfix release
Swyx Control Center requires the IIS (Internet Information Service) running on the hosting computer. If this Windows feature has not been turned on yet, it will be automatically activated during the installation process. IIS must not be stopped during installation and operation of Swyx Control Center.
Swyx Control Center requires Swyx Management Service to be installed on the target system. Please select this option during the SwyxWare installation process.
Swyx Control Center requires Microsoft .Net Framework 4.7.2, which is either part of the Windows operating system or can be installed via Windows Update.
To install Swyx Control Center click on the corresponding link on the DVD. Swyx Control Center can also be installed via the respectively named .msi file.
You can also start the installation of Swyx Control Center by opening it via the command line. Start the installation with the command "msiexec /i". You can control the scope and the progress of the installation with certain parameters, e. g.:
msiexec /i "SwyxControlCenter.msi" /passive /l*v MyLogFile.txt WEBSITEFOLDER= "C:\Program Files (x86)\Swyx" INSTALLPORT=9443 INSTALLSHORTCUT=1 SHOULDUNINSTALLIIS=0
You can use the following parameters:
| Parameter | Explanation |
|---|---|
| msiexec /i | Start of installation |
| SwyxControlCenter.msi | Name of installation file. Please check that the name of the MSI installation file is correct |
| /passive | Use this parameter to display the installation progress bar. No prompts or error messages are displayed. The installation cannot be aborted |
| /l*v <FileName>.txt | Use this parameter to record the installation process in a log file |
| WEBSITEFOLDER | This option allows you to set the directory in which the IIS-Website is to be installed. Standard value: /swyxcontrolcenter |
| INSTALLPORT | This option allows you to set the port for the IIS web site, (from 1 to 65535) default value: 9443 |
| INSTALLSHORTCUT | You can use this option to specify whether a desktop shortcut is to be stored for the call (=0:no, Default value: =1:yes) |
| SHOULDUNINSTALLIIS | With this option you can define if IIS should be deactivated during SwyxWare uninstallation (=1:yes, default value: =0:no) |
After a successful installation you can open Swyx Control Center via the windows start menu, or call it up via the URL in a web browser. The standard URL will be https://127.0.0.1:9443/swyxcontrolcenter/, if you keep the default installation parameters.
A SwyxIt! installed on the same machine as a SwyxWare Administration (MMC) version 12.10 must also be updated to version 12.10. Otherwise SwyxIt! with a lower version than 12.10 will crash in this case.
From v12.20 on you have to enter the address and port of the authentication service for connections via RemoteConnector in the SwyxIt! configuration.
If several users on a terminal server start a SwyxIt! with RemoteConnector Tunnel, the first SwyxIt! builds the tunnel, and all further SwyxIt! clients use it. If the first SwyxIt! is terminated, the shared tunnel is also terminated and all other SwyxIt! clients lose their connection to the SwyxServer. Only restarting at least one SwyxIt! will solve the problem.
Due to the simple and automatic Remote Connector Tunnel configuration via URL in the welcome email (see above) this scenario will occur more often in the future if the users did NOT configure a Remote Connector connection in the past. I.e. in future there is always a tunnel connection available as fallback if the administrator has configured this in the MMC.
Remarks:
Swyx Messenger is not supported with remote desktop services / in terminal server environments. In these scenarios SwyxIt! Messenger should be used.
Additional port that must be open for Swyx Messenger to reach the required Instant Messaging server(s): TCP 443.
Swyx Messenger only works reliably between users on different SwyxWare instances if the instances are registered in Operator under the same "Customer". In addition, the SwyxWare instances must be connected via SwyxLink in order to display user names, user pictures and status information reliably.
If an administrator in Swyx Control Center does not allow the use of Swyx Messenger for a user in the available functions, Swyx Messenger is not automatically started with SwyxIt! for this user. However, this setting has no effect on a Swyx Messenger already installed on the user's computer.
Windows notifications about incoming instant messages via Swyx Messenger may not work reliably on Windows 7.
Swyx Messenger does not work as a stand-alone application, i.e. without SwyxIt!
The following items are required for the installation and operation of SwyxIt!:
Audio input/output equipment:
Device specific functions like hook switch are supported only for certain devices (e.g. P280, JabraDevices connected via Jabra Direct functionality)
Run the SwyxIt! setup .msi file and follow the installation instructions. For further information, including instruction for unattended installation, please refer to the SwyxIt! user manual.
On a Windows Terminal Server the Swyx TSP can provide an arbitrary number of lines. During the setup of SwyxIt! with enabled feature "TSP" on server, the properties dialogue of the TSP appears.
On a server the dialogue allows to change the number of available lines. If the number is changed later on, the telephony service must be restarted.
For each user an individual TSP line must be configured:
Within a terminal window only assigned lines will be visible. Only administrators will see all lines.
Assign exactly one TSP line to one user. This is required for a proper association between TSP lines and terminal client sessions.
To enable or disable a Telephony Server:
TapiMgmt.mscIf the 'Enable telephony server' check box is unavailable, you need to start the Telephony service first:
After you enable the server, specify a logon account in the Account Information area.
The logon account you specify must be a member of the Administrators group on the server. It must also be in the same domain as the server or in a domain that has a two-way trust relationship with the domain containing the server.
How to Assign a Telephony User to a Line or Phone:
These steps define whether clients can use the telephony devices accessible to the server. Changes take effect the next time the computer attempts to start the TAPI service. To manage the Telephony service, you must be a telephony administrator on the server or logged on as an administrator. If the user assignment menu entries are disabled, please try to log on as local administrator.
Updating SwyxIt! versions 2015 R40.3 or newer is supported by the installation program. Run the SwyxIt! setup .msi file and follow the installation instructions. For further information, please refer to the SwyxIt! User Documentation.
Microsoft Web Service Enhancement 3 (WSE 3.0) is no longer required for SwyxIt!. If you update from an earlier version, it is safe to remove WSE 3.0 either after or before updating SwyxIt!
The new Swyx VisualContacts feature will not be installed when updating from an older SwyxIt! version. Run the setup again after the update, select the custom installation option ("Modify") and select "VisualContacts AddIn" to install it.
The new DATEV integration will be installed automatically when DATEV has been detected on the system. If you install DATEV after SwyxIt!, run the SwyxIt! setup again. Select the custom installation option and then the DATEV AddIn to install it.
Collaboration with TeamViewer is supported with TeamViewer 8 or higher. It is highly recommended to use TeamViewer 9 or newer. If your network environment requires a https proxy and the proxy configuration is automatically detected by Internet Explorer, please make sure to use the latest TeamViewer version.
Swyx Meeting is an additional collaboration tool for up to 10 participants. The use of Swyx Meeting for 2 participants is free for every SwyxIt! user and possible without additional registration. To start a session with Swyx Meeting for 10 participants, the moderator needs an account which has been registered by the corresponding Swyx Partner. Other participants can join a Swyx Meeting without registration. If you install SwyxIt! 11.38 (or higher) for the first time, Swyx Meeting is configured as the default collaboration tool. Use one of the following browsers for Swyx Meeting: Google Chrome (desktop or mobile version) or Edge Chromium from version 72, Mozilla Firefox from version 65, Apple Safari or iOS from version 13.
When using the Headset H390, the SwyxIt! volume slider does not work correctly. The device maintains its own volume control and does not respond to the master volume of the corresponding Windows mixer. For changing the volume of that headset please use the volume buttons on the device.
Per default the SwyxIt! audio devices H370 and H371 cannot be configured as ringing device. The H370 and H371 will always signal incoming calls with device specific ringtones. Nevertheless, it is possible to enable the configuration as ringing device via a registry value:
On 32 bit systems:
HKEY_LOCAL_MACHINE\SOFTWARE\Swyx\Client␣Line␣Manager\CurrentVersion\Options\AudioDevicePlugIns\IpPbx.Client.Devices.Audio.Plugins.JabraAudioDeviceCollection
On 64 bit systems:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Swyx\Client␣Line␣Manager\CurrentVersion\Options\AudioDevicePlugIns\IpPbx.Client.Devices.Audio.Plugins.JabraAudioDeviceCollection
The only purpose of this setting is to render the notification tone for calls being on hold at the H370 or H371. For example, if a transferred call is not accepted by the transferee, this call will be put on hold after a timeout and the notification tone will be rendered at the ringing device.
In some rare cases SwyxIt! audio could be disturbed when a SwyxIt! audio device is also used as Windows default sound device. If you observe such problems, try using a different audio device as Windows default sound device and do not use your headset or handset for Windows sound output. You should not use your headset or handset for Windows sound output.
In Microsoft Office 2010 a Rich Presence state of contacts sometimes is shown with delay or not until hovering over with the cursor.
In Microsoft Office 2013 a Rich Presence state of the member of a group is lost after hovering over with the cursor until the Office application has been restarted.
From the contact card or the context menu of an Office contact only audio calls can be initialised via SwyxWare.
After installation of the Office Communication AddIn, only presence information of SwyxIt! is shown within Office applications. To show the presence information from other IM clients, this AddIn must be uninstalled first. Detailed instructions are available in the SwyxWare Knowledge base (kb-Article 4552).
After installation of the Office Communication AddIn and first start of SwyxIt!, Office applications must be restarted once to enable status signalling.
Swyx Connector for Skype for Business will only work, if the "Office Communication AddIn" is disabled during installation of SwyxIt!. You can also disable this feature via the Control Panel: “Apps and Features | SwyxIt! | Change | Modify".
This version is a bugfix release which is available on the Swyx website.
This version is a bugfix release which is available on the Swyx website.
This version is a maintenance release in which the following error has been fixed:
The Swyx VisualGroups extension provides intelligent queuing capabilities for your SwyxWare. Swyx VisualGroups is useful for all teams who want to handle more incoming calls more effectively.
Swyx VisualGroups is licensed as a floating license on a user basis. There are two licenses available: a standard version and an enhanced version with reports and statistics.
It is recommended to license Swyx VisualGroups in SwyxWare prior to installation and configuration. If you use SwyxWare with the included evaluation license, you can install VisualGroups to benefit from five free VisualGroups Enhanced licenses during the evaluation phase.
The Push Notification component is required for SwyxMobile for iOS/Android.
Push notifications are available in the Swyx Mobile clients from version 2.x onwards.
Swyx Mobile clients 1.x with no integrated support for push notifications, will still work with a SwyxServer version 11 and onwards, but will not profit from the benefits mentioned above and will not be developed any further in the future.
After updating to version 12.10, all mobile clients must re-register. It is sufficient if all users open the Swyx Mobile App and bring it into the foreground. The user registration will be updated and the users can be reached by phone again. This is only necessary this one time, not for future updates.
To guarantee the data transfer between the Push Notification Service and the corresponding Apple/Google push notification gateways, make sure, that the required ports on the Internet firewall are open:
Outbound TCP connections to port 443 on api.push.apple.com
Outbound TCP connections to port 443 on fcm.googleapis.com
Push notification gateways may use different IP addresses with the above mentioned DNS names. Allow connections to the DNS names, not specific IP addresses.