cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
1655
Views
0
Helpful
6
Replies
Highlighted
VIP Mentor

Attendant Console showing question marks

I am having a hard time identifying the underlying cause for the AC application showing a question mark for the line status. This is happening off and on, on several users desktops.

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Advocate

Re: Attendant Console showing question marks

Any NAT or Firewall between the stations and the TCD server (CCM)?

Try restarting TCD service or AC service (CCM 5.x and higher)

View solution in original post

6 REPLIES 6
Highlighted
Advocate

Re: Attendant Console showing question marks

Any NAT or Firewall between the stations and the TCD server (CCM)?

Try restarting TCD service or AC service (CCM 5.x and higher)

View solution in original post

Highlighted
VIP Mentor

Re: Attendant Console showing question marks

Yes NAT and Firewall, the ACs are at several remote locations while the cluster is in a central site.

but there was never a problem before, and all of the sudden this is happening OFF and ON.

I rebooted the PCs, but that didn't help. Tonight I will reboot the CCM Pub/Sub cluster and report back.

Just wondering what would cause this.

Highlighted
Beginner

Re: Attendant Console showing question marks

Did the reboot of the CCMs work? I am also having a similar problem with the unknown status for the speed dials and user lists.

I upgraded to new servers running CCM 4.3 and while Attendant worked properly on 4.1 even the Cisco techs are unable to resolve at this point.

Highlighted
Hall of Fame Master

Re: Attendant Console showing question marks

Did you reinstall the AC application with the version that is bundled with CM 4.3?

At least check if the versions are the same.

Chris

Highlighted
Beginner

Re: Attendant Console showing question marks

All versions are current. Even unloaded the old versions as an attempt

Highlighted
VIP Mentor

Re: Attendant Console showing question marks

actually yes, the reboot has solved the problem.

Also, I had another cluster with the same issue, and I just bounced the TCD service and that fixed it.