Howto:Softwarephone and terminal server enviroment or thin clients: Difference between revisions
mNo edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
This information applies to | This information applies to | ||
* innovaphone | * innovaphone softwarephone or myApps softphone App | ||
<!-- Keywords: | <!-- Keywords: | ||
| Line 20: | Line 20: | ||
===Problem Details=== | ===Problem Details=== | ||
The softwarephone needs a local sound card, | The softwarephone or myApps softphone App needs a local sound card, which means it makes little sense connecting an USB Headset on the server (in the server room) and pass the USB cable till the local workplace. You want to connect the USB audio cable on the local PC you are working on - the thin client. | ||
As the whole user interface (e.g Windows and Applications) is running on the server, you will need an USB sound proxy (Client Audio Mapping in Citrix Speak), and will look like this: | As the whole user interface (e.g Windows and Applications) is running on the server, you will need an USB sound proxy (Client Audio Mapping in Citrix Speak), and will look like this: | ||
Headset <--USB--> Thin Client (PC) <---- TCP/IP -------> Server (Citrix Metaframe) | |||
In the thin client from the USB sound proxy to the USB sound data must be an uncompressed conversation to the Server , because there is the softwarephone running. There the data will be processed, compressed and sent via IP. This is not a nice solution - wasting bandwidth and delay creating (having also an extra delay for thin client to the server). | In the thin client from the USB sound proxy to the USB sound data must be an uncompressed conversation to the Server , because there is the softwarephone/myApps softphone running. There the data will be processed, compressed and sent via IP. This is not a nice solution - wasting bandwidth and delay creating (having also an extra delay for thin client to the server). | ||
=== Conclusion === | |||
A thin client with Windows operating system is the recommendation for such a setup. Here you install the softwarephone locally and control if from the Citrix/Terminal-Server using myPBX or phone-App. | |||
The myApps-Softphone App cannot be controlled by the RCC-App or phone-App, therefore you cannot use it as a replacement for the locally installed softwarephone. | |||
As an alternative, you can of course use ip-hardphones instead of the locally installed softwarephone. | |||
=== Additional hints === | |||
When starting the myApps-Windows-Client in the Terminal-Server, we [[Reference13r1:Concept_myApps#MSI_parameters | recommend to disable the Headset-SDKs using DISABLEHEADSETS]] - since the headset control will be done also locally at the softwarephone. | |||
Also check the [[Reference13r1:Concept_myApps#Known_issues myApps |known issues]] for TerminalServer or Citrix entries. | |||
<!-- == Related Articles == --> | <!-- == Related Articles == --> | ||
[[Category:Howto|{{PAGENAME}}]] | [[Category:Howto|{{PAGENAME}}]] | ||
Revision as of 15:21, 19 August 2020
Having innovaphone softwarephone running on thin clients
Applies To
This information applies to
- innovaphone softwarephone or myApps softphone App
More Information
informations about thin clients and Client/Server thin clients
Problem Details
The softwarephone or myApps softphone App needs a local sound card, which means it makes little sense connecting an USB Headset on the server (in the server room) and pass the USB cable till the local workplace. You want to connect the USB audio cable on the local PC you are working on - the thin client.
As the whole user interface (e.g Windows and Applications) is running on the server, you will need an USB sound proxy (Client Audio Mapping in Citrix Speak), and will look like this:
Headset <--USB--> Thin Client (PC) <---- TCP/IP -------> Server (Citrix Metaframe)
In the thin client from the USB sound proxy to the USB sound data must be an uncompressed conversation to the Server , because there is the softwarephone/myApps softphone running. There the data will be processed, compressed and sent via IP. This is not a nice solution - wasting bandwidth and delay creating (having also an extra delay for thin client to the server).
Conclusion
A thin client with Windows operating system is the recommendation for such a setup. Here you install the softwarephone locally and control if from the Citrix/Terminal-Server using myPBX or phone-App. The myApps-Softphone App cannot be controlled by the RCC-App or phone-App, therefore you cannot use it as a replacement for the locally installed softwarephone.
As an alternative, you can of course use ip-hardphones 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.