Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

CUPC Error - Failed to start conversation Start conversation capability is not available

We are running CUCM 7.1.5.32900-2 and Presence 8.5.2.10000-49.

When some of the users highlight numbers and call them using click to call (The click to call that comes as a part of CUPC), they are getting the following error box...

Error

Failed to start conversation

Start conversation capability is not available

Our users typically have 7941 phones that are associated with their user. They are not using softphone.

Has anyone else come across this error, and what was the culprit?

Thanks,

David

2 REPLIES

CUPC Error - Failed to start conversation Start conversation cap

Hi David,

http://www.cisco.com/en/US/docs/voice_ip_comm/cups/8_0/english/install_upgrade/deployment/guide/deploy.html

Cannot Place or Receive Calls After a Secure Profile is Enabled

Problem   After a secure profile is enabled for a user, the user cannot place or receive calls. The user might see the following error message multiple times:

Failed to start conversation

The user can use the instant messaging features.

This problem occurs if a secure profile is enabled for the user in Cisco Unified Communications Manager while either of the following is true:

•The user is signed in to Cisco Unified Personal Communicator.

•The cucsf.exe process is running on the computer of the user, that is, Cisco Unified Personal Communicator is running, but the user has not signed in.

Ask the user to sign out of Cisco Unified Personal Communicator, then sign in again.

Hope it helps,

Anand

New Member

CUPC Error - Failed to start conversation Start conversation cap

Hi Anand,

One of my customers has the same issue. And indeed, signing out and back in again solved the problem but the user also has to close the cucsf.exe process first.

I guess this is not normal behaviour? Can this be prevented?

Thanks,

Kurt

2709
Views
0
Helpful
2
Replies
CreatePlease login to create content