That message indicates the client was able to contact the Unity server propertly and the dialout attempt was made... this eliminates a bunch of possible problems and narrows it down to some sort of error when we try to go "off hook" and dial the phone itself.

If the line were busy or was RNA you'd get a message to that effect so I'm assuming either one or more ports on the Unity side are out of service (i.e. one of the ports designated for TRAP dialouts is in a locked up state) or the phone system is giving us an error back when we actually dial the extension in question. Since this worked in the past I kinda doubt it's a search space issue or anything along those lines.

Check the ports on Unity (using Status Montior) and see if they're all responsive. Dialouts are attempted from the highest port number and move forward so if, for instance, the very last port were "burned" that could be causing this problem. A restart of Unity would probably clear it, but certainly report it to TAC. We've had several reports of ports going out of service and clearly we need to figure out what's going on under the covers in these cases.


Jeff Lindborg
Unity Product Architect/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)