Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1254
Views
0
Helpful
3
Replies

Context Service for CVP Deregister/Register/Connection

SEAN NILSEN
Enthusiast
Enthusiast

‎01-03-2019 10:37 AM - edited ‎03-14-2019 06:42 PM

I'm wondering if anyone has been through the Context Service Deregistration process in OAMP for CVP [v11.6(1) for CVP and Ops]?

 

The reason I ask is that the docs indicate that going through the Deregister button in OAMP should bring up the "Enable Collaboration Cloud Extensions" page.

 

Instead, the button brings me to a page prompting for "Remove Hybrid Services Cluster" which is clearly not the right page as I don't want to remove the entire config.

 

Any idea if that is a badly worded page in the WebEx Admin side or if clicking continue there will really remove the Hybrid Services Cluster?

 

My real issue driving all of this is that my Finesse Context is Operational and working AOK but the CVP Context is in an "impaired" state. The available logs are very insufficient to troubleshoot what the actual underlying issues might be.

 

The relevant exception using the BuiltIn Customer Lookup element in VXML Server is: "Context service object initialization failed."

 

Any suggestions on next steps on how to troubleshoot Context Service as it relates to CVP/VXML?

 

==== Edit 1 ===

As I continue troubleshooting, the system has now reached a state where the VXML Server is throwing:

 

Caused by: ApiError with errorType: connector.notRegistered errorData: cs_context errorMessage: connector is not registered

 

But OpsConsole still believes it's registered.

 

Anyone know if there's a manual way to kick Ops back into an unregistered state and manually clear out the nodes in WebEx Admin?

Labels:
0 Helpful
3 Replies 3

SEAN NILSEN
Enthusiast
Enthusiast

‎01-03-2019 10:59 AM

The answer is - the wording on the WebEx Admin/Deregister page is very misleading.

 

I'm pretty adventurous so I clicked the "Confirm" button anyway and that reset Ops status and removed only the CVP context.

 

After re-registering, WebEx Admin shows both Finesse and CVP Context In-Service.

 

After re-deploying the context config, and rebooting the CVP/VXML server, I am still left with the issue of:

 

01/03/2019 12:54:35.660, The error was: A built-in element encountered an exception of type com.cisco.thunderhead.errors.ConnectorIsNotRegisteredException. The root cause was: com.cisco.thunderhead.errors.ConnectorIsNotRegisteredException
com.audium.server.AudiumException: A built-in element encountered an exception of type 

<snip>
Caused by: ApiError with errorType: connector.notRegistered errorData: cs_context errorMessage: connector is not registered

 

Any suggestions?

0 Helpful