I have the default opening greeting set to blank and to hangup. What is happening is that when someone leaves a message for a subscriber and they press "1" to send the message. The system will state that the message has been sent, and then play a Call Handler greeting for another location. Too make matters more interesting, I can't really be in this call handler. I say this because none of the call handler caller input options work (but they do work when I am correctly in this call handler). I have looked for this call handler greeting in other call handlers and cannot find it anywhere.
Well several things could be happening here. In your post, you mention that someone leaves a message for a subscriber and the caller presses 1 to send the message. Is this the call flow from within your default greeting OR could the caller just be calling the subscriber direct and forward no answer/busy to Unity? In the latter case, you may want to check the After Message action for the individual subscriber setting and see where this goes. I would also check the After Greeting action on the Greetings page of your default opening greeting call handler as well as the Messages page for the After Message action. For troubleshooting, you can use the Call Viewer (for CallManager integrations) or also the Port Status monitor as a starting point. There is also the AudioText Manager tool available on www.ciscounitytools.com that can help "picturize" the flow of your default greeting call flow.
In addition to what Ginger wrote, turn on Micro Traces for PhraseServer to Monitor, values 10, 11, 12. Then open Port Status Monitor (from \CommServer\Utilities\PortStatusMonitor\PortStatusMonitor.exe) to see what is actually happenning. In PSM, under the Ports menu, you can also Log All Active which will then output the information you see in PSM to a csv file in \CommServer\Utilities\PortStatusMonitor\ folder
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
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...