When Avaya Analytics™ tries to subscribe to a UCM topic that does not exist in Oceana 3.7.0.1, it does not receive events and notifications from Avaya Oceana®.
Cause
The problem occurs because of incorrect settings in the deployment spreadsheet, when you select the correct Oceana version 3.7.0.1, but incorrectly set the UCM subscription notification value.
Solution
Log in to the Cluster Control Manager (CCM) console as the customer user.
To switch to the root user, type su and press Enter.
To edit the input adapter configuration map, run the following command:
ADDITIONAL INFORMATION:
kubectl edit cm orca-ref-input-adaptor
In command mode in a vi editor, enter the following command:
ADDITIONAL INFORMATION:
%s/SEND_NOTIFICATION/FORWARD_NOTIFICATION/g
Run the following command to save the changes: wq
To run the Analytics Administration script, use the following command:
ADDITIONAL INFORMATION:
ccm release orca analytics
Select the Restart Ref Input Adaptor option by entering the corresponding number to restart the Input Adaptor pods.
ADDITIONAL INFORMATION:
The restart might take several minutes to complete.
In the Proceed with REF Inpur Adapter restart field, type y.
