Unity 4.0(4)UM Directory Handler Looping

[johutchins]

I'm reinitiating this in the Unity group... any one have a fix... I ran dbWalker. No love there.

On Unity 4.0(4) the directory handler (dial by name) gets in a loop as follows:

- caller hits AA, presses # (in our case, instead of 4) to get to the directory handler

- Unity says "Spell the last and first name, then press #

- Caller spells last name, presses pound.

- Unity says "For <subscribers recorded name> at extension 1234 press #"

- Caller presses #

- Unity says "Spell the last and first name, then press #

This is odd, because Unity does indeed find the subscriber, the subscriber has completed enrollment, but just doesn't transfer the call.

If the caller chooses not to enter the directory handler, they can dial the subscriber's extension directly (ie. 1234) and the call is transferred successfully.

Thanks,

--Jon

[lindborg]

When you do this does anything show up in the application event log?

Also, can you pop open the Port Status Monitor (which you'll find in the tools depot on your Unity desktop) and see what's happening there when you do this? It may spit out some conversation path that would reveal what's happening there.