Attendant Console showing question marks

Answered Question
Aug 29th, 2007
User Badges:
  • Purple, 4500 points or more

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.

Correct Answer by gogasca about 9 years 7 months ago

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

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


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (1 ratings)
Loading.
Correct Answer
gogasca Wed, 08/29/2007 - 17:08
User Badges:
  • Green, 3000 points or more

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

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


Anthony Holloway Wed, 08/29/2007 - 18:22
User Badges:
  • Purple, 4500 points or more

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.

tomkir Wed, 09/12/2007 - 06:44
User Badges:

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.

Chris Deren Wed, 09/12/2007 - 10:01
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,
  • Cisco Designated VIP,

    2017 IP Telephony, Contact Center, Unified Communications

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

tomkir Wed, 09/12/2007 - 10:25
User Badges:

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

Anthony Holloway Wed, 09/12/2007 - 10:09
User Badges:
  • Purple, 4500 points or more

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.

Actions

This Discussion