×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Virtualised CUPC and VXC Troubleshooting

Document

Thu, 01/17/2013 - 21:55
Jan 17th, 2013
User Badges:
  • Cisco Employee,

1. CUPC Virtualised Block Diagram

   

Notes for CUPC Deployment with Virtualisation:

1. vxcc registration with CUCM

VXCC is a soft client deployed by UC add-ons and it needs to  register with callmanager for call control and media termination. For  VXCC to attempt to connect to callmanager, it required to retrieve below  information from CUPC in HVD via the virtual channel:

1. TFTP address

2. Devicename to be used for registration to callmanager

3. Certification info.

When vxcc comes up, it needs to connect to TFTP server to download  the <devicename>.cnf.xml configuration file to learn about the  callmanager server ip address it need to register itself to, and the  line number that is configured in callmanager for this device, if the  required line number is missing from the configuration file, typically  caused by CM services and TFTP services not restarted after the COP file  installation on CUCM, vxcc will not validate the configuration file and  make no attempt to register with callmanager.

Once vxcc has registered with callmnager, CUPC in HVD will receive  the devince and line in-service event, and CUPC will start the use of  CTI to control this vxcc soft phone for call call control functionality.

Troubleshooting tools:

1. Use any TFTP clients including Windows built-in tftp client to  download the <devicename>.cnf.xml configuration file from TFTP  server to examine the file has contained all the required parameter.

2. Wireshark capture to check and verify the network connectivity  between the VXC 6215 and TFTP server and tftp network transactions.

3. Grab core.log from PRT and vxcc.log from  /var/log/cisco, or VXC.txt from PRT collected by CUPC in HVD. To turn  on vxcc logging, execute below command in VXC: "vxcc -l on"

4. To check if vxcc is running on VXC 6215, execute below command: "ps -A | grep vxcc"

5. CUPC has to be launched for vxcc to register with callmanager.


2. Citrix USB device redirection and CUPC USB device recognition.

USB devices are classified with a series of IDs: VID, PID, Class,  Sub-Class, Prot and Rev. Citrix Xendesktop have USB redirection policy  to be either enabled or disabled, and USB redirection policy rule sets  to be ALLOW or DENY certain USB devices to control what kind of USB  devices need to be mapped to HVD by ICA client. These policy rules are  enforced by ICA clients at endpoints or thin clients and VDA agent in  HVD, and implemented in ICA clients configuration and registry settings  in HVD. A USB device that is allowed in the policy will be recognised by  the HVD OS device manager when they are plugged in. Refer to Citrix  article CTX129558, and CTX132716.

However, USB device redirection for USB camera and audio device is  not desired in VXC 6215 deployment. In the VXC 6215 environment  Real-time audio and video is handled by the device locally to ensure the  best possible real-time voice and video experience.

In any real-world deployment of VDI if you try to hair-pin real-time  audio and video through the HVD you will get very poor audio and video  due to packet loss and severely increased latency & network  bandwidth consumption. This is exactly what the VXC 6215 is intended to  resolve.

Therefore in general we should not use USB redirect with  headsets and cameras in a 6215 deployment. The device-manager in VXC  6215 will work with the device switcher in HVD and communicate via the  virtual channel (ICA Connection) so that the device switcher will be  able to list the camera and audio devices that are locally attached to  the VXC USB ports, and these multimedia devices will be directly  controlled by CUPC and the GIPs media engine on the VXC 6215. And  regardless wether or not any USB devices are plugged in, the default  sound device in VXC 6215 should be listed by the device switcher as "HDA  ATI SB Analog Stereo", and if this device is not listed, the device  switcher and the device manager are not working properly and required  further troubleshooting.

To troubleshooting device switcher, and device manager, grab the following logs:

On HVD:

1. Collect PRT from CUPC, or

2. Locate the logs at  "c:\Users\<userid>AppData\Local\Cisco\Unfied  Communications\Virtualisation\" deviceswitcher.txt, and  VirtualChannelLib.txt

On VXC:

1. Under root account bash shell, "/var/log/cisco/", device-managerConsole.log and device-managerError.log

3. Auto-login add-on with UC Add-on deployment.


auto-login add-on package is by default enabled  in Cisco shipped VXC 6215, and it will auto login to vxc 6215 locally  with thinuser/thinuser credential once the box is booted up. We can  choose to disable auto-login package so that we can log in to the device  with admin/admin credential to gain full access to the vxc 6215 control  centre and have the ability to configure everything locally. UC Add-on  is only tested with auto-login package tuned on and around the thinuser  context, and it has strict dependancies on thinuser environments. If the  user is not loged on as thinuser, device-manager on VXC 6215 will not  work properly and device switcher on HVD will not list any devices, and  as such, voice and video calls will not work.

Loading.

Actions

This Document