Office Manager Not Working After Configuring CallConnector

Unanswered Question
May 21st, 2010

I recently stared over with my UC500 demo kit and configured it from scratch with CCA v2.2.4. When I was complete, Office Manager worked just fine. I then configured both CallConnector (Server and Client) and Operator on the same laptop and Office Manager is now broke. It can't discover devices and just hangs. Is anyone else experiencing this problem?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Steven DiStefano Sat, 05/22/2010 - 07:16

Just seeking some clarification...Are you saying you installed UCC

Personal client, and UCC Server, and SCC Attendant console on the same

laptop, and got that to coreside? I didn't think that was possible.

Have you made sure CCA was not running when you started OM?

You may still be able to click Advanced toolbar menu option on OM

after it fails, and enable debug log to your PC, and attach that.

marknigh1 Mon, 05/24/2010 - 14:38

Attached is the log. I had the first Office Manager beta so uninstalled and installed the lastest with the same problem, "error reading user data".

In addition, I removed Operator so it will not conflict and will run it off my laptop for demos. CCA was not running.

Thanks.

Steven DiStefano Tue, 05/25/2010 - 12:49

One of the Engineers who works on OM took a look at the logs.  He asked the following...(snip below).  I am wondering if the user is an 'enabled' user, if we dont see the prompt?

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman","serif"; mso-fareast-font-family:"Times New Roman";}

"So we are sending the username and then the password but never get any type of prompt that we recognize. At this point the prompt has to have a '#' at the end, is it possible that the CallConnector is removing it from the prompt?"

Steven DiStefano Wed, 05/26/2010 - 12:30

Have you had a chance to look at this again, with assurance the user is level 15 enabled in CLI?

Steve

Actions

This Discussion

Related Content