I'm not sure what happened but I have one other site that reported the same type of thing after an upgrade. Can you call TAC and get a ticket open? We'd definitely like to poke around and see if we can find the original STM file (the greeting storage file) that was being pointed at and see if it's there and/or damaged or if it was removed or the reference is invalid or what...
was this after an upgrade? What version are you on?
I'm on version Unity 2.4 Build 18.104.22.168. We didn't do an upgrade. We rebooted because our wave driver lost communication with CallManager.
After looking through Unity Admin to see if changes were made, but not making changes, the recorded opening greeting we created came back. The only thing I did was click on the already selected radio button selecting the recorded greeting, and clicked save. I didn't change the selection.
So the radio button got changed to "system" you you set it back to "recording"? That would make sense... the greeting doesn't go away in that case, we just switch over to generating a greeting based on the recorded name and/or ID of the box such as " is not available now" or "the person at extension 3189 is not available now".
I'm not real sure why it would have just switched over to system on you, however...
No. The opening greeting was set to the recording we created not system. However, it was playing the system greeting. I re-selected the already selected recorded opening greeting which allowed me to hit save. No one touched the Unity setting prior to me doing this. I'm not sure that what I did could or would make a difference. It's probably just a coincidence that the greeting came back.
I know this is getting confusing, so let me recap and refrase; We rebooted, we made no changes, Our opening greeting disappeared and the system greeting took it's place, we looked for a change that may have been made, but didn't modify anything, then the greeting just came back. Nutty.
If you see it lose a greeting again, can you leave the system in that state and get on the horn to TAC? It'd be handy to call in and poke around in DOHPropTest to see which stream path it's trying to use and why it's not valid. The only thing I can think of is the old UNC path would be left there and the SA forced it to the "offset" path it should be using, but that should only be an issue for upgrades which doesn't sound like your problem.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...