Hmmmm... without looking at your system it's hard to guess, but if the recorded greeting were missing and Unity expected it to be there in a particular location that would cause that message to be played over the phone.
When you record a greeting an .STM file gets placed under the "RES\" folder on the local Unity server. If the STM file the greeting is set to point to is not there, it'll fall back on a system generated greeting which is done by pulling the voice name of the call handler (or if that's not recorded, the voice name of the message recipient for the handler and if THAT's not there, play the extension number in its place) and putting together that phrase you mention. There are other scenarios that would cause this (i.e. a call forwarding from an extension corresponding to the ID of a call handler) but that doesn’t seem real likely here.
If you can test it again (i.e. taking the new Unity server off line) and popping open the SA on the other Unity server and seeing if you can play the opening greeting from there or if the media master control for the greeting is “gray” and disabled (i.e. the media master cannot find the referenced STM file). If not, the reference has been changed to point to a different file that it’s expecting. This could happen if someone recorded the opening greeting again from the new box (not likely) or by the setup of the 2nd box overwriting it during install… which shouldn’t happen if it’s done by joining an existing location. In this scenario setup does not create any new objects in the directory, it uses existing ones. However you’re pretty sure you didn’t do that so perhaps something went haywire and setup updated those references to point locally and the greetings path references are on the other Unity box which then become invalid when that box is taken off line. Just a guess at this point (but a darn snappy theory). You can prove it quickly by doing that test.
If that’s the problem it could be as easy as copying the STM files from the 2nd Unity server over to the original one and you’re done. If I’m completely barking up the wrong tree then someone will likely need to get in your system and poke around in DOHPropTest to see what in the world is going on there.
Jeff Lindborg
Unity Product Architect/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)
