[cisco-voip] MWI Request Pending ON

[Pat Hayes]

Ok but, that's time stamped yesterday. I was asking if any events were
thrown within a minute or two of you forcing a resync on a user. In
any case, you said you have traces that show Unity dialing out the
MWI, so that rules out a lot.

That really comes down to a ccm config problem. You said you checked
CSSs, but it is probably time to go back. Specifically, you need to
verify that:

1. Unity voicemail ports have a CSS that contains the partition of the
MWI on/off code
2. The MWI on/off code has a CSS that contains the partition of
whatever phones you are trying to light.

If you have to make any changes, you'll need to restart Unity to get
the ports to re-register. If that doesn't get you anywhere, probably
time to open a TAC case.

On Tue, Apr 7, 2009 at 1:18 PM, Steven Sarte <steven.sarte at gmail.com> wrote:
> This was the error which is now fixed because of ACL's were blocking
> access to the domain controller.
>
> Event Type:     Warning
> Event Source:   CiscoUnity_DSAD
> Event Category: Warning
> Event ID:       1017
> Date:           4/6/2009
> Time:           1:17:52 PM
> User:           N/A
> Computer:       UNITY01P
> Description:
> The Cisco Unity service that monitors Active Directory (AvDSAD) is
> skipping a synchronization cycle because it failed to connect to
> domain controller XXXXXXXSDC1.york-claims.com. Ensure that the server
> is accessible and is configured as a domain controller, and that no
> DNS issues exist. The service has failed to connect to this domain
> controller for 14 consecutive synchronization cycle(s). After 15
> consecutive failed connection(s), The Cisco Unity service that
> monitors Active Directory (AvDSAD) will attempt to connect to a
> different domain controller.
>
> Diagnostic Info:
>
> Domain Controller: XXXXXXXDC1.york-claims.com
> Binding String: LDAP://XXXXXXXXDC1.XXXXXXXXX.com:389/ROOTDSE
> Error Code: ERROR_DS_UNAVAILABLE
> Description: The directory service is unavailable.
>
> I do have traces from CM and I see that Unity does contact callmanager
> to set the MWI.
>
> Thanks,
> Steven
>
> On Tue, Apr 7, 2009 at 12:05 PM, Pat Hayes <pat-cv at wcyv.com> wrote:
>> What did you find in the application event log? Hit the manual
>> refresh, wait a minute or two, and see what warnings or errors were
>> generated.
>>
>> On Tue, Apr 7, 2009 at 11:04 AM, Steven Sarte <steven.sarte at gmail.com> wrote:
>>> We did have this issue with the Unity box not able to communicate to
>>> the Active Directory because of ACL's which our security group
>>> implemented but we took care of that.
>>>
>>> I deleted a user from Unity and recreated the account still didn't work.
>>>
>>> Thanks,
>>> Steven
>>>
>>> On Tue, Apr 7, 2009 at 10:12 AM, Pat Hayes <pat-cv at wcyv.com> wrote:
>>>> Always a good idea to start in the application log and look for
>>>> warnings or errors. There are a few possible causes for this condition
>>>> and most/all of them throw a vaguely useful event.
>>>>
>>>> On Tue, Apr 7, 2009 at 9:44 AM, Steven Sarte <steven.sarte at gmail.com> wrote:
>>>>> I have an update on this, Indicator Lamps states ON in Unity but no
>>>>> light on the phone.
>>>>>
>>>>> Thanks,
>>>>> Steven Sarte
>>>>>
>>>>> On Tue, Apr 7, 2009 at 9:38 AM, Steven Sarte <steven.sarte at gmail.com> wrote:
>>>>>> I'm having this situation for a new site we just brought up the MWI
>>>>>> lights aren't working.  In Unity it just states MWI Request is pending
>>>>>> ON.  Tripled checked CSS, not the issue.
>>>>>>
>>>>>> Thanks,
>>>>>> Steven Sarte
>>>>>>
>>>>> _______________________________________________
>>>>> cisco-voip mailing list
>>>>> cisco-voip at puck.nether.net
>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>
>>>>
>>>
>>
>