09-11-2009 11:56 AM - edited 03-18-2019 11:41 PM
Hi,
We are deploying CUPC to a small group of users for proof of concept before we rollout to the entire organization but I am having problem with new users. The majority of users have their phone status as "disabled" and are unable to change it to anything else. The options for deskphone and softphone aren't even available. One of the users CUPC randomly started working this week with no changed being made. Any idea what would cause the phone control to be disabled?
All users are associated with the correct device and userID is associated to all lines for each user. Plenty of users are working on the current CUP server. new users seem to be the issue...
09-11-2009 01:18 PM
Go to CUCM > User Management > End User > look for a drop-down menu called "Primary Extension". Does the user have it configured?
If yes, you might also want to restart SyncAgent on CUPS to synchronize the data.
Michael
09-15-2009 09:08 PM
Yes, primary extensions are configured. I will restart the SyncAgent and see what happens.
09-16-2009 03:36 AM
I have exactly the same problem. Looking through your book Michael the only item I could see worth checking was the users number.
The CUPC error report indeed indates 'No Primary Extension' but this is populated, we sync this with AD, and a restart of the SyncAgent makes no difference.
Only one user has this problem and he is setup the same as all the rest - though this is only 20 users at the moment.
Anything else I can try to resolve this error? Or could something else be causing it?
09-22-2009 09:52 AM
We also sync with AD and have no success with restarting the sync agent service...once in a while the users will randomly start working with no changes being made.
10-27-2009 11:25 AM
I have been battling the same issue now for two days. Users sometimes have Deskphone access, sometimes not. Some can choose a different phone others cannot... No changes were made.
Was anyone able to solve this?
10-28-2009 02:14 AM
Hi there,
Try check the End User management config. Confirm that the user has a Primary Extension within the 'Directory Number Associations' field.
Also, check that the phone/user has 'CTI Enabled'.
Hope this helps. Worked for me.
Cheers
Bob
10-30-2009 07:38 AM
Yes, the killer for me was the Primary extension field not being populated. Once that was changed, all seems to work fine.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide