I’ve earlier explained how to unlock GoToMeeting (GTM) to support Audio capability using VoIP in a Citrix XenApp session, you can refer to the article here: Application Behaviour Analysis – Citrix GoToMeeting for Application Virtualization environments like XenApp
In this article, we’ll see the use case and limitations of GTM using VoIP in a Citrix XenApp ICA Session. Essentially, this explains why was Citrix locking down VoIP by default in XenApp ICA session.
Evaluating GoToMeeting in XenApp VoIP:
Scenario Environment:
- Single XenApp 6.5 server with FP4
- GoToMeeting 6.3.0.1468 installed under Program Files (x86) for all users. No other versions of GTM are existing run by users on the app server.
Test Cases:
- You connect to multiple XenApp ICA sessions and Launch GTM from all of them. That means multiple instance of GTM running on a single server simultaneously.
- One of the user hosts the Meeting and rest of the users join to attend the same meeting on the same server via different XenApp sessions.
Results:
- As you would expect that all of the users be able to join the meeting with Audio.
- However, while continuing the Meeting, you keep on loosing audio of one or more or all users in the call
- If you trim down the participants to two one-on-one then the audio works usually normal and no issues noticed
- You hear lot of echo’s, if the participants are on Speakers.
- While you invoke more GTM instances, you start seeing increased CPU usage
- On a 8 Core vCPUs servers
- it touches 17-20% for two participants
- for three users it reaches 24-28% of CPU