Howto:Softwarephone and terminal server enviroment or thin clients: Difference between revisions
| (15 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
Having innovaphone | Having innovaphone softwarephone running on thin clients | ||
==Applies To== | ==Applies To== | ||
This information applies to | This information applies to | ||
* innovaphone SoftwarePhone | |||
* innovaphone | * innovaphone myApps-SoftphoneApp | ||
<!-- Keywords: | <!-- Keywords: | ||
bria | bria | ||
rdp | rdp | ||
remote desktop | remote desktop | ||
soft phone terminal server | soft phone terminal server | ||
sotwarephone | |||
softphone | |||
myapps | |||
rcc | |||
citrix | citrix | ||
audio | audio | ||
--> | |||
==More Information== | ==More Information== | ||
informations about | General informations about [http://de.wikipedia.org/wiki/Thin_Client thin clients and Client/Server] | ||
===Problem Details=== | ===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 would not keep any locally installed applications. | |||
In the 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, the recommendation is to operate it locally at the thin-client. | |||
* For the softwarephone, this implies to install it locally and control it from the Citrix/Terminal-Server using myPBX or myAPPs-PhoneApp. | |||
* Starting with 13r3, the [[Reference13r3:Concept_App_RCC#Softphone-App_controlled_by_RCC-App|myApps-SoftphoneApp can be controlled by the rccAPP]] | |||
* 14r1 introduces the [[Reference14r1:MyApps_Plugin_for_Virtual_Desktops | MyApps Plugin for Virtual Desktops]] - the recommended solution for a thin client with Windows operating system | |||
* As an alternative, IP-deskphones can be used instead of the locally installed softwarephone or myApps-SoftphoneApp. | |||
=== Additional hints === | |||
When starting the myApps-Windows-Client in the Terminal-Server, we [[Reference13r1:Concept_myApps_platform_services#MSI_Parameters_and_install_options | recommend to disable the Headset-SDKs using DISABLEHEADSETS]] - since the headset control will be done also locally at the softwarephone. | |||
Also check the [[:Category:Problem_myApps|known issues]] for TerminalServer or Citrix entries. | |||
===Known Problems=== | |||
Be aware, that parallel operation of Softwarephone and myAPPs at the same host will not work due to conflicting audio device resource allocation. | |||
In case of a already running myAPPs, Softwarephone will not be started. | |||
Since the Windows process don't even start, there is no possibility to solve this in the softwarephone/myApps configuration. | |||
To solve this issue, just delay the autostart of myApps in the Windows configuration, so softwarephone is started before myApps. | |||
<!-- == Related Articles == --> | <!-- == Related Articles == --> | ||
[[Category:Howto|{{PAGENAME}}]] | [[Category:Howto|{{PAGENAME}}]] | ||
Latest revision as of 19:43, 6 February 2024
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 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 would not keep any locally installed applications.
In the 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, the recommendation is to operate it locally at the thin-client.
- For the softwarephone, this implies to install it locally and control it from the Citrix/Terminal-Server using myPBX or myAPPs-PhoneApp.
- Starting with 13r3, the myApps-SoftphoneApp can be controlled by the rccAPP
- 14r1 introduces the MyApps Plugin for Virtual Desktops - the recommended solution for a thin client with Windows operating system
- As an alternative, IP-deskphones can be used instead of the locally installed softwarephone or myApps-SoftphoneApp.
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.
Known Problems
Be aware, that parallel operation of Softwarephone and myAPPs at the same host will not work due to conflicting audio device resource allocation. In case of a already running myAPPs, Softwarephone will not be started.
Since the Windows process don't even start, there is no possibility to solve this in the softwarephone/myApps configuration.
To solve this issue, just delay the autostart of myApps in the Windows configuration, so softwarephone is started before myApps.