[cisco-voip] Unity Connection - Query to find references to mailbox?

[James Avalos]

I think I know what you're asking, but could be wrong.
Do you know whether the voicemail messages being left for this mailbox are direct calls or forwarded calls?
You may want to check your call manager to see if any of your extensions are configured to route to that mailbox for any reason.
An all details export should give you everything but takes a while to complete.
Calls may also be hitting this mailbox from system call handlers from within Unity Connection. Perhaps this mailbox has an alternate DN configured against it, and is accepting messages.  If you run a quick CDR for the DN in question using the time the messages were left, you might be able to find their origin.
If in fact, they're coming from CM.   Or, they could be routing there via CxN.
Can you give an example or additional details?



From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Matthew Loraditch
Sent: Friday, May 16, 2014 5:36 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Unity Connection - Query to find references to mailbox?

I know Unity Connection doesn't have dependency records, but is there a query or a utility I don't know of, that can show what is referencing a mailbox? I've got an account getting voicemails that it shouldn't but all the places that I've looked aren't pointing to it... but something must be!

I'm going to start messing around in CUDLI, but would appreciate any assistance.
Thanks!

Matthew G. Loraditch - CCNP-Voice, CCNA-R&S, CCDA
1965 Greenspring Drive
Timonium, MD 21093

direct voice. 443.541.1518
fax.  410.252.9284

Twitter<http://twitter.com/heliontech>  |  Facebook<http://www.facebook.com/#!/pages/Helion/252157915296>  | Website<http://www.heliontechnologies.com/>  |  Email Support<mailto:support at heliontechnologies.com?subject=Technical%20Support%20Request>
Support Phone. 410.252.8830


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140516/631c5b21/attachment.html>