FastDials service not working properly after upgrade to 4.1.3

Unanswered Question
Mar 18th, 2007

I had the XML FastDials service configured and running properly on a CallManager cluster running 4.1.2. I subsequently upgraded to 4.1.3 and since the upgrade there appears to be a lack of synchronization between what is entered by users in the Speed Dials page on their CCMUser pages and what appears on the phone when the FastDials service is accessed. Speed dials slots configured from the CCMUser page come up "unassigned" when accessed through the Fastdials service through the phone. The converse is also true. When a user adds a speed dial through the phone, it does not show up when they subsequently log in to their CCMUser pages. Any one else seen this behavior? Any ideas what could possibly be the cause?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)


This Discussion