Ideally you'd need to pull traces from CUC to best figure out which user account may be configured to place the notification device calls. What's likely happening is CUC dials out to the configured notification device (which doesn't pick up) and it sends the call back to voicemail. While CUC is streaming that notification device announcement, the call lands on the user's greeting and CUC begins recording itself, it's basically a looped call Then that gets left as a voice message and confuses the user The key will be to figure out which user's notification device has the configured # on their mailbox since they likely have voicemail and aren't checking them.
As an alternative to traces, you could try the following:
1. To get a list of all users with notification devices configured on the system for you to search through to find the configured notification # that's being dialed out to:
run cuc dbquery unitydirdb select objectid,phonenumber from tbl_notificationdeviceconversation
Copy the 'objectid' value that matches the notification # and plug it into the next query:
2. run cuc dbquery unitydirdb select * from tbl_notificationdevice where objectid = 'OBJECTID'
This shows you the object and the type of notification device it is, which has that extension configured on it.
Copy the subscriberobjectid value and use it in the next command to find the user it belongs to:
run cuc dbquery unitydirdb select dtmfaccessid,displayname,alias from vw_user where objectid = 'OBJECTID'
Hopefully it's that simple, otherwise traces need to be set and capture the outbound notification device calls happening so we can track which device it is.
Macro Traces:
Call Flow
Call Control
Conversation Traces
Gather from RTMT:
Connection Conversation Manager
Then search through them for the # being dialed and you should see the outbound call being placed either in the SIP or SCCP signaling, depending on your phone system integration type.
