I know the version is really old, but since this product has gone end of support it's a little tricky getting help with the product. I have a client who is running CCM 4.1 and they are experiencing a challenge with getting one user to appear in the corporate directory. We have tried removing/recreating the user, but there are other new users we can add in.... I found this: Some Users are not Listed in the Corporate Directory With Cisco Callmanager 4.1(3), some users are not listed in the Corporate Directory on the Cisco IP Phone. These users have user profiles and device profiles configured in Callmanager. Complete these steps in order to resolve the issue: 1. In the CCM Administration Page, choose Application > Cisco CallManager Serviceability. 2. In the Serviceability page, choose Tools > Control Center. 3. Click the server, choose the Cisco Telephony Call Dispatcher service, and click Restart. Note: If you have multiple server clusters, repeat step 3 for all the servers in the cluster, starting from subscribers and ending with the publisher. There will be no impact to services, but I would prefer after our last test you do this after hours as I mentioned.                 Followed it, but it has done nothing either. Does anyone else have any suggestions outside of a cluster reboot? Thanks Ron ... View more

Hi Guys, I need to know if it’s possible to warn a caller prior to leaving a message that the mailbox they ware calling into is full.  The default behavior seems to be to tell the caller after they finish leaving the message that the mailbox is full and the voicemail box will not be taking any new messages. I believe the setting I am looking at is Full Mailbox Check for Outside Caller Messages, but as per the definition: Indicates whether Cisco Unity Connection first determines if a user mailbox is full before allowing an outside caller to leave a message for the user. (The maximum size of a mailbox is determined by quota settings either on the Message Storage > Mailbox Quotas page or, if the quota is overridden for an individual user, on the Mailbox page for that user.) When this check box is checked, if the user mailbox is full, the outside caller is not allowed to leave a message. When this check box is not checked, Connection does not determine whether the mailbox is full; the outside caller is allowed to leave the message even if mailbox is full. Note that this setting is applicable only to outside callers. If a Connection user signs in and sends a message to another user, Connection always checks whether the user mailbox is full regardless of whether this setting is enabled. Default setting: Check box not checked. But nowhere in the definition does it mention where it will alert the user, and the user after enabling this is indicating that they are hearing the message that a voicemail cannot be sent is after the caller leaves the voicemail, not prior. Anyone deal with a similar issue, or know where to modify the setting? Thanks! -Ron ... View more

Good Afternoon, I have a client that regularly practices changing Subscriber properties from time to time as employees change, a name might change or a setting changes.  For the most part this has not been a problem, but we have started to notice that Subscriberse are appearing in the system, such that when you attempt to make any change to their settings you get: Invalid service capability. Calendar capability is not enabled for the service. Now I have gone through the Internet/NetPro etc... and can't actual match on this exact error.  This comes from the Subscriber configuration page at the top after you change any setting and hit Save. Now this doesn't effect all users, and in fact we have only been noticing it on a case by case basis, but it's beginning to seem as a concern because my only workaround at this point is to delete the Subscriber and then recreate it.  Problem is alot of these Subscribers are referenced as Caller-Inputs and have many dependencies, so deleting would cause problems with those as well as a loss of messages. Has anyone noticed this problem in the past, or have any idea of what may be causing this? The exact version of Unity Connection is 8.5.1ES45.12021-45 -Ron ... View more