Howto:Softwarephone and terminal server enviroment or thin clients: Difference between revisions
No edit summary |
|||
| Line 2: | Line 2: | ||
==Applies To== | ==Applies To== | ||
This information applies to | This information applies to | ||
* innovaphone SoftwarePhone | * innovaphone SoftwarePhone | ||
* innovaphone myApps SoftphoneApp | * innovaphone myApps-SoftphoneApp | ||
<!-- Keywords: | <!-- Keywords: | ||
bria | bria | ||
rdp | rdp | ||
| Line 14: | Line 11: | ||
citrix | citrix | ||
audio | audio | ||
--> | |||
==More Information== | |||
General informations about [http://de.wikipedia.org/wiki/Thin_Client thin clients thin clients and Client/Server] | |||
===Problem Details=== | |||
Setup of a thin client environment implies to have all functionalities at the server side and just access them for use via the thin-client. | |||
Thin clients itself would not keep any locally installed applications. | |||
In case of using audio-applications and -devices such as e.g. softwarephone/myApps-SoftphoneApp and USB-headsets following problem occurs: | |||
* As the local thin-client sound card is not in use, connecting a USB Headset to the server (in the server room) and passing the USB cable to the local workplace of course is not practicable. | |||
* Thin client workers want to use their own headset connected to the thin client. | |||
For this to work, use of a local sound card for audio replay is required. | |||
As the whole user interface (e.g Windows and Applications) is running on the server, a USB sound proxy (Client Audio Mapping in Citrix Speak) must be used: | |||
Headset <--USB--> Thin Client (PC) <---- TCP/IP -------> Server (TS/Citrix Metaframe) | |||
The thin client then will send USB sound data as uncompressed audio to the Server where softwarephone/myApps-SoftphoneApp running. | |||
Audio data will be processed at the server, compressed and sent back to client via IP. | |||
This solution is wasting bandwidth and creating delay (having also an extra delay for sending data between the thin client and the server). | |||
=== Conclusion === | === Conclusion === | ||
To make audio-applications and devices work in a thin client environment with Windows operating system, recommendation is to operate a local setup at thin-client. | |||
The myApps- | * For the softwarephone, this implies to install it locally and control it from the Citrix/Terminal-Server using myPBX or myAPPs-PhoneApp. | ||
* The myApps-SoftphoneApp cannot be controlled by the PhoneApp or rccAPP, so there's no possibility to use it as a replacement for the locally installed softwarephone (which is still available in V13). | |||
As an alternative, | As an alternative, ip-deskphones can be used instead of the locally installed softwarephone. | ||
=== Additional hints === | === Additional hints === | ||
Revision as of 12:00, 21 August 2020
Having innovaphone softwarephone running on thin clients
Applies To
This information applies to
- innovaphone SoftwarePhone
- innovaphone myApps-SoftphoneApp
More Information
General informations about thin clients thin clients and Client/Server
Problem Details
Setup of a thin client environment implies to have all functionalities at the server side and just access them for use via the thin-client.
Thin clients itself would not keep any locally installed applications.
In case of using audio-applications and -devices such as e.g. softwarephone/myApps-SoftphoneApp and USB-headsets following problem occurs:
- As the local thin-client sound card is not in use, connecting a USB Headset to the server (in the server room) and passing the USB cable to the local workplace of course is not practicable.
- Thin client workers want to use their own headset connected to the thin client.
For this to work, use of a local sound card for audio replay is required. As the whole user interface (e.g Windows and Applications) is running on the server, a USB sound proxy (Client Audio Mapping in Citrix Speak) must be used:
Headset <--USB--> Thin Client (PC) <---- TCP/IP -------> Server (TS/Citrix Metaframe)
The thin client then will send USB sound data as uncompressed audio to the Server where softwarephone/myApps-SoftphoneApp running.
Audio data will be processed at the server, compressed and sent back to client via IP.
This solution is wasting bandwidth and creating delay (having also an extra delay for sending data between the thin client and the server).
Conclusion
To make audio-applications and devices work in a thin client environment with Windows operating system, recommendation is to operate a local setup at thin-client.
- For the softwarephone, this implies to install it locally and control it from the Citrix/Terminal-Server using myPBX or myAPPs-PhoneApp.
- The myApps-SoftphoneApp cannot be controlled by the PhoneApp or rccAPP, so there's no possibility to use it as a replacement for the locally installed softwarephone (which is still available in V13).
As an alternative, ip-deskphones can be used instead of the locally installed softwarephone.
Additional hints
When starting the myApps-Windows-Client in the Terminal-Server, we recommend to disable the Headset-SDKs using DISABLEHEADSETS - since the headset control will be done also locally at the softwarephone.
Also check the known issues for TerminalServer or Citrix entries.