You can find information on the hardware requirements in our knowledge database: https://service.swyx.net/hc/en-gb/articles/13772878531996
You can find information on the hardware requirements in our knowledge database: https://service.swyx.net/hc/en-gb/articles/13916515322908
You need a "SwyxServer 14 Update" license to run Swyx 14 after an update from a SwyxWare 13 or older version. You must enter an update license key during installation.
Please note that the above license is not linked to the "Software Update Licenses Service Key". See also: service.swyx.net/hc/en/articles/360000012780-Swyx-Update-Service
Swyx 14 can be used to update SwyxWare 12.41 or higher. Updates of older versions and updates of SwyxWare Compact are not supported. For information on SwyxWare migrations, please contact your reseller
When updating, you should first update SwyxServer, Swyx Control Center and then SwyxWare Administration. Client should be updated last.
It is recommended to update SwyxWare directly instead of removing the old version first.
Information on updating the software can be found on our online help pages: https://help.enreach.com/cpe/14.00/Administration/Swyx/en-US/index.html#page/help/chap_installation.08.01.html
We recommend stopping all SwyxWare services before updating. This can be done by executing the command 'ippbxconfig.exe /stop /y' in the SwyxWare program folder.
Microsoft service packs and updates
Ensure that the latest Windows operating system service packs and SQL Server service packs are installed. We recommend to have Windows Update enabled to automatically get important Microsoft security updates for your operating system.
Make sure that the Windows user you use for the Swyx 14 setup must have administrator rights on the system on which the 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 the Swyx services do not receive any higher authorizations than necessary.
Master / Standby
Please note that a master / standby installation, as well as the updating of such an installation, is not supported. Master/Standby must be switched off before updating.
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. To do this, please add a character string with the name "LocalIpAddress" to the registry under the key HKLM\SOFTWARE\Swyx\General\CurrentVersion\Options. Enter as value the IP address that the SwyxWare services should use.
"ProviderProfiles.config"
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.
SwyxIt! is the desktop telephony client for Windows systems
Swyx Connector for Microsoft Teams v5 or higher only supports the new Microsoft Teams Client
Installation via .MSI installation package requires administrator rights
By running the installation, both clients (SwyxIt! and SwyxIt! Classic) are installed:
Start the SwyxIt! Setup.msi file and follow the installation instructions. Further information, also on unattended installation, can be found in the SwyxIt! User Documentation.
If you start SwyxIt! unattended (without displaying the user interface), e.g. with the command line parameter "/qn" in the MSI, the update may hang. This happens if you have installed the Outlook Add-In and outlook.exe or another Office application is running. For a smooth unattended update experience, make sure that no SwyxIt! related processes or Microsoft Office applications are running. Technically, there is a third-party component in the installer that displays a message box that cannot be seen and confirmed by the user in certain deployment scenarios, e.g. deployment via Microsoft InTune. We plan to improve the unattended update experience in a future update.
As a first workaround, add 'PERUSERADDINREGISTRATION=1' to the MSI command line when using a deployment tool such as Microsoft InTune. This changes the Outlook AddIn registration to a mechanism per user instead of per computer. This workaround becomes effective in the update step after you have set the property to 1.
On a Windows Terminal Server the Swyx TSP can provide an arbitrary number of lines. When installing SwyxIt! with the "TSP" feature activated on a server, the TSP properties dialog 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.
If you use a Jabra device with SwyxIt!, please note the following information:
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.
SwyxIt! 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. 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. Audio output is disturbed when the SwyxIt! Audio device additional as default Windows audio 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.
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.
After installation of the Office Communication AddIn and first start of SwyxIt!, Office applications must be restarted once to enable status signalling.
Information on setting up integration with Microsoft services can be found in our knowledge base
You can find information on the hardware requirements in our knowledge database: https://service.swyx.net/hc/en-gb/articles/13772878531996
You can find information on the hardware requirements in our knowledge database: https://service.swyx.net/hc/en-gb/articles/13916515322908
Swyx Control Center requires the IIS (Internet Information Service) running on the hosting computer. If this Windows function is not yet active, it will be activated automatically during installation. (The installation process may take considerably longer as a result). IIS must not be stopped during installation and operation of Swyx Control Center.
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\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 |
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.
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.
Detailed information on VisualGroups 1.14.4119.0 can be found in the release notes at https://service.swyx.net/hc/en-gb/articles/13988039884060-Swyx-VisualGroups-1-14
To enable communication between the push notification service and the responsible push notification gateways at Apple/Google, the necessary ports must be opened in the Internet firewall:
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.