Pages

Tuesday, July 16, 2019

Cisco CUACA Attendant Console Advanced Notes

Replication Issue:

Installing CUACA version 12.0.4.20-14 on Windows 2012 R2, SQL 2016 and using the CUACA High Availability (Resilient Installations) option.

I was presented with "Licensing information on publisher and subscriber servers is not in sync. Please validate replication configuration." after applying the correct Server, Sessions and Resilient Server licenses on the publisher.  Attempting to install replication via the CUACA GUI Replication drop down was a miserable failure.  A good visual of the steps required can be found here regardless: https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-attendant-console-advanced/200513-Installation-of-Replication-for-CUAC-Adv.html 

Hostnames and FQDNS resolved, SQL servers were installed correctly, firewall exceptions were in order, sa passwords checked, administrator rights to servers were good, prerequisites were verified a dozen times, CUACA uninstalled and reinstalled with new DBs, etc. etc.

TAC finally found and supplied a DLL that needed to be replaced.  See CSCvp67232.  The DLL is DBComponent.dll, the modified date on the fixed version is Thursday, ‎May ‎23, ‎2019, ‏‎5:12:26 AM and it belongs in C:\Program Files (x86)\Cisco\Utilities\DB Component and C:\Program Files (x86)\Cisco\Attendant Admin\Web\Application\Bin.

Cool.  Replication still doesn't work. 

TAC insisted it was a firewall issue after they were unable to telnet to a port the servers were not listening on. That's not how that works, but you should probably double check yours anyway.

Ultimately I found a MS Application Error on the 2012 subscriber server in the cascading mess of errors indicating the local MS DTC detected that the MS DTC on has the same unique identity as the local subscriber server.  The error text indicates the servers were likely cloned in an unsupported method. This is not unlikely in this particular environment.

There is a brief reference to this in the latest troubleshooting guide but the link to Microsoft's website is broken and you do not need to reinstall CUAC.

The fix is running 'msdtc -uninstall' and 'msdtc -install' from a command line running as administrator on the subscriber server, reboot everything, uninstall and reinstall CUACA Replication and enjoy your day.

MS DTC error message

CUCM Synchronization Issue:

When defining a device to use as a template for CUAC Queue Devices, the Owner User ID on the CUCM template device appears to need a value.  If the Owner is left Anonymous in CUCM you will find an error code 9100 Function Parameter error in the CUCM Sync Report when the process is complete.  If you lucky enough to be synching lots of devices and impatient when running the report you might catch a better description of the culprit before it finishes.

Not a helpful description

Now this... this is a helpful description.


Transfer to voicemail:

In CUACA User Configuration | General Properties the Maximum internal device digit length needs to be long enough to include the DN length plus the voicemail prefix defined in the client under Options | Dialing.  For example, if are using +E.164 DNs and a prefix of 12345, you internal device digit length needs to be 18.



1 comment:

  1. Hello, just wanted to tell you, I loved this blog post. It was practical. Keep on posting!

    ReplyDelete