I wanted to ask a question to see if anyone has seen this problem before.I have an offic in Ohio and when you call you get the auto attendant which answers the call and guides you to where you want to be. But some times when uses call they get the generic Cisco Unity VM prompt to leave a message. I called and thested it myself and they are right, the first time i called I got the generic VM prompt. I hung up and called right back and got the pre configured auto attendant. It's like hit and miss and I don't know what's causing this with the auto attendant so if anyone can point me in the right direction I would be greatly appreicate it and thanks in advance.
I believe that Rob has the right idea for this question. The key is to figure out what is different in the two call flows or to see if the call info is different from one call to the next. The reason why one call would take you to the auto attendant and one would not is all about the call info. If Unity Connection recognizes the called extenstion it will route it to the correct prompt. If it doesn't recognize the number we play opening greeting and the system will require more information before we get them to the correct prompt.
The good news is that you have a working and a nonworking example. You just need to compare them and this will tell you what is happening. Port Status Remote Monitor will show that call info so try that out and let us know what you get.
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...