I agree, the term "unidentified" does seem contradicting. Cisco Unity attempts to associate the Caller ID with a subscribers mailbox extension so that it can include the message senders name in the subject. If the Caller ID does not match a subscribers mailbox number then the callers name is "unidentified".
Customizing the subjects allows you to change the text that is included in the subjects.
I suspect you have found a bug similar to the one below.
Perhaps you could try and reproduce the problem by calling in as an external caller and leaving a message for a subscriber mailbox, after recording the message try each of the following scenarios to send the message and end the call. I suspect one of these conditions might create the situation where "unidentified caller" is missing from the subject line.
1. Record the message and when finished [Hang up] immediately (before the after recording menu) to send the message.
2. Record the message and when finished recording, press [#] to terminate the recording, then [Hang up] during the after recording menu to send the message.
3. Record the message and when finished recording, press [#] to terminate the recording, then press [#] during the after recording menu to send the message.
No NAME for subscriber message subject line for some hang up conditions
okay I figured out via CDR under which conditions this is happening and reproduced the scenario. Now I just need to understand the WHY. Here's what happens:
First msg was left when ext was CFA to voicemail.
2nd msg rang the ext, (which is a shared line), the admin with the shared line, picked it up and transferred call to vm using *7210.
This results in 2 different Final Called Party situations for the calls. The final called party number for the "unidentified" message is from the hunt pilot for voicemail (7999). In the other message the final called number is 1003 (a voice mail port).
So neither of these are subscribers so I wonder why 1 would be considered unidentified and not the other? Sorry if I am beating a dead horse, I just hate not understanding something.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.