• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2828
  • Last Modified:

Citrix XENAPP 6.0 Virtual IP not working for Server 2008 R2

I am trying to use a Nortel softphone app on the new XENAPP 6.0 server. all published app and desktops work great. Except this one I need unique IP addresses for each softphone. So I followed the instruction and went into the terminal server configuration and enabled Virtual IP also selecting the only Nic Adapter and BY session. I also tried by Program. I went int the Delivery Service Console (replaced the Access Manager) and created a Policy for Virtual IP all 4 policies that are called 4 selecting default check box becasue I set them for session.
1 Solution
Interesting. I havent used virtual ip addresses yet on XA6, hopefully its not a bug. I have used and packaged avayas softphone and the cisco ip communicator. Is there no way to base nortel off of something else? Like username or extension? Because if you could do extension, then you could package the softphone and then isolate the registry key for user. Just like with the ip communicator as shown here. Works very well,.

The new audio subsystem in XenApp 5 for Windows Server 2008 can now handle applications that need to open the audio device more than once (e.g. once for ringtone and then again for the voice path), as Cisco IP Communicator does. We successfully tested Cisco IP Communicator 2.1 on XenApp PS 4.5 FP1 for Windows Server 2003 using a specially modified audio driver that allowed the app to do that (although it didn't solve the mixing issues with the previous audio subsystem). I'm trying to arrange for that testing to be repeated on XenApp 5 for Windows Server 2008 but it hasn't been scheduled yet. Don't be shy to let your Cisco contacts know that you'd like that to happen! XenApp 5 for Windows Server 2008 can be used to deliver softphones and other applications with "voice chat" functionality to on-premises users (LAN-connected to the XenApp server). Since packet loss results in retransmission which introduces delay, we do not recommend delivering softphones to remote workers in this way.

Here are the details on how we tested IP Communicator. We ran IP Communicator in an isolation environment and disabled Cisco Discovery Protocol on the server since the CDP driver was not multi-user compatible.
•      Install the Cisco IPC software on Citrix XenApp 5 using all the installation defaults.
•      Publish the following two applications on XenApp:
o      C:\Program Files\Cisco Systems\Cisco IP Communicator\AudioTuningWizard.exe
(This is the Cisco Audio Tuning Wizard)
o      C:\Program Files\Cisco Systems\Cisco IP Communicator\Communicatork9.exe
(This is the Cisco IP Communicator)
•      Create a new isolation environment to run the Cisco software using the XenApp Console.
o      Once you have created the new isolation environment, delete all the rules that are created by default.
o      Add the following four new rules to your isolation environment:
¿      Rule to IGNORE ALL Files.
¿      Rule to IGNORE ALL Registry Entries.
¿      Rule to IGNORE ALL Named Objects.
¿      Rule to ISOLATE the "HKLM\SOFTWARE\Cisco Systems, Inc.\Communicator" registry entry. The isolation must be "per user".
o      o Add the two applications that you published above to the newly created isolation environment.
•      Verify allowed audio quality for ICA in Terminal Services Configuration:
o      Launch Start->Administrative Tools->Terminal Services Configuration.
o      Launch the ICA Configuration by double clicking on "ICA-tcp" on the right pane.
o      Select the "ICA Settings" tab.
o      Set the "Client Audio Quality" to Medium. The recommended setting for this configuration is Medium because the High quality setting (uncompressed) uses significant bandwidth (roughly 1 Mbps for bidirectional audio) which may cause peripheral issues when using the Cisco IP Communicator, and the Low quality setting (intended for dial-up modem connections) results in a suboptimal user experience. For most customers, Medium quality provides the best balance between sound quality and bandwidth efficiency.
•      Launch the published "Cisco IP Communicator" application:
o      Launch the Cisco IPC published app from either PN Agent (preferred) or PN Classic or Web Interface. In either of these methods, make sure that the audio setting in use is the recommended "Medium Quality".
o      When the application is launched the first time, it will go through audio configuration and also through network configuration. When configuring the audio, both the input and outputs should work at this point. If they do not, please make sure that you have bidirectional audio enabled.
o      At this point, you will also need to know the parameters for your Cisco Call Manager IP PBX.
•      Disable Cisco CDP on the server:
o      The Cisco IPC currently uses Cisco's CDP protocol in its implementation of Enhanced 911 to associate a physical location to the calling party's number. However, the CDP driver provided by Cisco is not multi-user compatible. If it is left enabled, all users that launch the Cisco IPC application after the first user will get an error indicating the inability to use CDP. The application will work but E911 will not be available. In order to eliminate the error, add the following value to the registry under "HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\Communicator":
¿      Add REG_DWORD called "EnableCDP" with value of 0.
¿      In a 64-bit environment, this value will need to be located in "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cisco Systems, Inc.\Communicator" instead.
o      Disabling CDP does not disable 911 services. It only disables the enhanced geo-location features of 911 services.
o      If after performing this step, the Cisco IP Communicator is still displaying the warning message, it may be necessary to delete and recreate the isolation environment.

CyprexxDevAuthor Commented:
That you for the response, how ever my issue was more of a terminal serive virtual IP VS Xen APP 6.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now