12.1 Certified SIP phones
Via Swyx Control Center you can create Swyx certified SIP devices to make them available to the users in your local network. Proceed in the following order:
After creation the devices are detected by SwyxServer.
4. Connecting Desk Phones,
|
If you connect the device to the network before the desk phone object has been created in Swyx Control Center, the logon prompt may not during the inital operation. The desk phone object is not detected by SwyxServer. After you have created the desk phone object, you can trigger the restart of the device as well as the logon prompt via "Reboot" or by briefly disconnecting the device from the power supply.
|
After putting the device into operation, the current firmware and user configuration data are transferred from the server.
|
Certified SIP devices are not supported in the standby scenario (SwyxStandby). Certified SIP devices cannot log on to the standby server. If Desk Phones are processed on the standby system, this may result in disturbances on the master system.
|
|
For the provisioning of the Desk Phones it is necessary that the IP address of SwyxServer can be resolved in the local network. If there is no name resolution (DNS) in your network, enter the current IP address of SwyxServer in the Windows Registry on the computer where SwyxServer is installed. (HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node \Swyx\General\CurrentVersion\Options\LocalIPAddress)
|
|
If the provisioning of phones cannot be performed via multicast due to the network infrastructure, you can also distribute the provisioning URL (e. g. http://172.20.1.1:9200/ippbx/client/v1.0/device/provision/) via DHCP Option 66.
|
|
The setting options on menu pages and in configuration wizards depend on your administration profile and your SwyxWare solution.
|