by default the error greeting is not visible, you can expose it by using the Advanced Settings tool to do it. The Error greeting has always been in there (this is the guy that determines what we do with the call when a user enters an illegal option during a greeting for a call handler or a subscriber). Sounds like they exposed it using the Advanced Settings Tool.
Our customer experienced a very weird problem as I posed on another mail. When user call AA from internal or external and enter extension , they hear" I am sorry . I don't recognize that is a valid entry." A little chance user can access the extension from AA, We have opened case with TAC, but no luck yet.Today I saw this error greeting, I thought this error may caused by this error greeting. It seems not. What do you think?
their problem is not related to the error greeting being exposed... the error greeting is always there and always has been - it's just not visible by default on the SA. It's not responsible for deciding if an entry is valid or not, it just get's called AFTER Unity decides the entry is not valid.
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...