It could be trying the extension but having it pop back at us on another port (it's hard to tell what's going on from over the phone). Try popping open StatusMonitor.exe (found under the \commserver directory), monitor all ports and then watch what happens when you call in and hit 0 again. I'm guessing you'll see the call on one port, the transfer attempt will go through and then the call will slam back at us on another port.
also, is it a release or a supervised transfer that's setup for the operator box? You can try switching back and forth to see if it behaves differently as well.
it'd be helpful to see what the status monitor puts up here. It may be necessary to add a pause to the dial string (seen that before) or there may be a CM configuration issue tripping us up or something similiar.
Jeff Lindborg
Unity Product Architect/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)
