Hi Vinoth,
Maybe this would work
Subscriber Message Activity Report
Use the Subscriber Message Activity report to diagnose voice message problems reported by a subscriber (for example, voice messages are not being sent or received, or the message waiting indicator is not being turned on or off properly). You generate this report for an individual subscriber only.
The Subscriber Message Activity report includes the following information:
Date and Time The date and time that the subscriber took action on the message.
Source Either the computer or the phone that generated the message activity.
Action Taken in Response to Message The activity that took place in regards to voice messages (for example, New Message, Message Read, Save, Delete, Mark New, Login, and Logoff).
The actions MWI On Requested and MWI On Completed indicate, respectively, that Cisco Unity sent a request to the phone system to turn on the MWI and received a request-completed confirmation. In cases where the phone system does not provide a confirmation, Cisco Unity assumes the request was successful.
Number of New Messages The number of new voice messages in the subscriber mailbox.
Sender's Name and DTMF The name and extension of the message sender, if known.
Date and Time Message Arrived The date and time that the message arrived in the mailbox.
Dial Out Number The number to which a message notification was sent.
Dial Out Result The result of the outgoing call for the message notification. Possible results include:
Busy The dialed number was busy.
Connected The called party answered the phone.
Failure The call failed.
Port Disabled All ports for outgoing calls were disabled.
Port Unavailable No ports were available for the outgoing call.
RNA (Ring No Answer) The dialed number did not answer.
Release The result is unknown. This typically happens for notifications sent to pagers.
Unknown The result is unknown.
Cheers!
Rob
