Guest

Preview Tool

Cisco Bug: CSCuj39803 - IPPA Server cores due to missing files in SU4 ES installer

Last Modified

Sep 27, 2013

Products (1)

  • Cisco Unified Contact Center Express

Known Affected Releases

8.5(1)SU4.1

Description (partial)

Symptom:
When a BIPPA stopRecording request is sent, IPPA will core.

Conditions:
One of the changes after the first ES1 build (but before the final SU4 build), CSCue35456, had a fix which modified a FCVoIPMonClient header file.
Because it was a header file change, it required that all dependent libraries be rebuilt and repackaged with ES1. The dependent libraries in question which weren't included with the ES installer would be libFCRasClient.so and libBIPPALibrary.so.

Because these files weren't included in the patch installer for ES1 (or any subsequent SU4 ES)... the "impossible situation" happens.

This is what the core file shows:

#2 0x0070ae81 in AgentMonitor::StartRecording () from /opt/cisco/uccx/desktop/lib/libFCVoIPMonClientRec.so
#3 0x03f46941 in FCRasClientRecordingsController::terminateRecordings_matchingTerminationCriteria () from /opt/cisco/uccx/desktop/lib/libFCRasClient.so

Translation: we go from terminateRecordings -> StartRecording.
That code flow has never been in the code, ever. The only way this can happen is if there is some sort of library file issue going on. Because a header file of libFCVoIPMonClientRec.so (where AgentMonitor resides) changed, all the function offsets that the dependent libraries use to determine where to start executing code at became invalidated. Those dependent libraries (RASCAL Client and BIPPA Library) need to be rebuilt and repackaged with the new offsets for everything to work nicely again.

Since CSCue35456 introduced a relatively small change, it appeared that even with the invalidated offsets, they were still pretty close for the most part. This is why the core would only happen on the stop recording method. It is also why only BIPPA was affected (the client-side RASCAL client is updated as a part of the ES. Only the server side isn't).
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.