Missing ANS button in Webex Calling Receptionist Client

If you are using the Webex Calling Receptionist Client, then receive an incoming call, but you do not see the ANS answer button, please ensure that the phone you are using is the Primary Device for the user account you are signed in as. If you navigate to Users, click on the user being used for the receptionist client, then click on Devices and the phone being used to receive the calls, you should see "Primary Device". If you don't see this, you will not see the ANS button an will be unable to use the receptionist client to answer the calls. There is currently a method to set a device as primary, so you might need to delete the device, then re-add the device for this user. An example of how this can happen is when you setup a user account for the receptionist client, then add a device, then add another device, then delete the first device. The 2nd device will not automatically become the primary device in this case. So, you need to delete and re-add it.

UCCX error - Authorization failed. Contact your system administrator.

I ran into an issue today where I was unable to log into Finesse on UCCX 11.6 and got the error - "Authorization failed. Contact your system administrator." I think it was because I had CUIC opened but then tried to login to Finesse on that same tab and got this error. Closing all Chrome tabs and opening it back up then let me get to Finesse.

Installing CUCM 10 in VMware Workstation

OK, CUCM 10 is out.  You can't get the ISO on CCO yet, so you will need to get it either through a new order, or through the Product Upgrade Tool (PUT) to get the bootable ISO.  Once an SU comes out, you can download the upgrade ISO and modify the boot info file to make it bootable.

In this example, I used VMware Workstation 9 and Bootable_UCSInstall_UCOS_10.0.1.10000-24.sgn.iso file.  Sorry, I don't provide that.  You're on your own.  OK, let's get started.

• In VMWare Workstation, click File > New Virtual Machine to launch the New Virtual Machine Wizard window.
• Select Custom (advanced), then click Next.

• Set the Hardware compatibility dropdown selection to Workstation 9.0 and click Next.

• On the Guest Operating System Installation page, select I will install the operating system later.  Click Next.

• On the Select A Guest Operating System page, select the Linux radio button and select Red Hat Enterprise Linux 6 64-bit in the Version dropdown box.  Click Next.

• Give your virtual machine a name, such as CUCM10 in my example.
• Set the location somewhere on your system.  In my example, I have it located in the D:\VMs\CUCM10 folder.  

• On the Processor Configuration page, leave the Number of processors at 1 and Number of cores per processor at 1.  Click Next.

• Set the Memory for this virtual machine value to be 4096 MB.  Click Next.

• For the Network Type, I always select Use bridged networking.  That way, I can give the virtual machine an IP address in the same network as my host machine running VMware Workstation.
• If you want, you can select Use network address translation (NAT), but be sure to check your network settings for NAT in VMware Workstation by going into Edit > Virtual Network Editor to check the NAT address range.
• Click Next.

• For the I/O Controller Type, select LSI Logic (Recommended) and click Next. 

• For Disk, select Create a new virtual disk and click Next. 

• For the Disk Type, select SCSI (Recommended) and click Next.

• For Disk Capacity, type 160 in the Maximum disk size (GB) box.
• I do not select Allocate all disk space now to save space.
• I select Split virtual disk into multiple files.
• Click Next.

• For the Disk File, just keep the default name, which is CUCM10.vmdk in this example.  Click Next. 

• If you want, you can click Customize Hardware and remove things like floppy disk, USB, etc.
• Otherwise, just leave it the way it is and click Finish.

• Now, you are at the final screen after creating the virtual machine. Click the Edit virtual machine settings link.

• Highlight the CD/DVD (IDE) device on the left pane.
• On the right side of the screen, select Use ISO image file and browse to the bootable CUCM 10 ISO file.
• Click OK.

• The virtual machine will boot and show you the media test screen.  I always choose Skip in non-production environments.

• You’ll see it mount block device /dev/sr0, then go through the VMware hardware detection.
• Eventually, you will see that we can select Cisco Unified Communications Manager. Select OK.

• (If we wanted, we could have beefed up the resources, more HD and RAM, which would allow us to install Unity Connection.  We’ll do that in another post.)
• This is a fresh install, so there isn’t a version on the disk yet, so choose Yes. 

• Select Proceed.

• This is the FCS build of CUCM 10, so we don’t have a patch yet.  Select No.

• Not too many choices here.  Let’s go with, ummmm…., Continue.

• Select the Timezone you are in, or want to take a vacation in.

• Select Continue for the Auto Negotiation Configuration screen.

• We won’t change MTU, so choose No.

• Have you ever used DHCP on a CUCM install?  Me neither.  Choose No.

• Enter the hostname, IP, Mask, and gateway information and select OK.

• We aren’t going to mess with DNS yet, so choose No.

• Enter the Platform administration username.  This is your OS-level user account you will use when logging in via a VMware console or when you SSH into the virtual machine.  I always use administrator.  Type your favorite or not-so-favorite password.  Select OK.

• Enter the certificate information.  This server is in the Organization organization, the Unit unit, and is located in Location, ST in the good ol’ US.

• This is the first node, so select Yes.

• Enter a valid NTP server.  If it can’t reach it, you will have problems.  You can use a public one such as us.pool.ntp.org or even a local router or server running NTP.  Select OK.

• Enter your favorite or not-so-favorite password to be used for the Security Password for intraserver communications and for DRS backups.

• We’ll worry about SMTP notifications later, so choose No for the SMTP Host Configuration.

• We’ll setup Call Home later.  I have a terrible memory, so I selected Remind me later.  Select OK.

• Enter a username for the Application User.  This is what you will use to log in to CUCM's infamous ccmadmin administration URL.  Again, enter your favorite or not-so-favorite password.  Select OK.

• That’s it.  All info is entered.  Select OK.

• Then, it will create and format the partitions, go through Package Installation progress bars.

• If you are watching, you will see it installing the platform components.

• Don’t touch anything.  You will see text scrolling by.  Its all automated.  Just watch it.

• Again, don’t touch anything.  Just let it do its thing.

• OK, more progress bars.  Yep, we need a database.

• Ah, unified communications manager component. Makes sense I guess – we are installing CUCM.

• Platform component – well, it does need a platform to run on.

• ELM – what would CUCM be without licensing.

• Success!  Congratulations – you’ve installed CUCM 10.  Now what?

• Open your browser.
• Go to https://192.168.1.80/ccmadmin (or whatever IP address you used)
• I’m using Internet Explorer 11 and will show you something you need to do if using IE 11.
• Notice that you don’t have the down arrow icons next to each menu?  We need to add this site to the Compatilibity View list.
• (Weird – I just noticed it shows 64 vCPUs.  Wow.)

• If you are using IE 11, we need to add this IP address to the Compatibility View.  Click the Settings (gear) icon and select Compatibility View settings.

• In the Add this website box, make sure your CUCM IP address is in the box, click Add, and it will move down to the box containing Websites you’ve added to Compatibility View.  Click Close.

• You may need to refresh or go to https://192.168.1.80/ccmadmin again.
• Look ma! The menus work! Now, start playing around with CUCM 10!