Directory Handler Failures

Unanswered Question
Mar 1st, 2008

We can not use a Directory Handler to access subscribers on other Unity servers in the same dialing domain. A subscriber can be found but when selected the caller is not connected and the Directory Handler loops back to the begining. Errors from the Event Log attached. This work fines for subscribers on the same system.

The subscribers on the other Unity systems can be reached doing a compose message.

The other Unity systems can reach the suspect Unity system using Directory Handlers.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Rob Huffman Sun, 03/02/2008 - 10:25

Hi Steven,

This is likely a problem with the CSS/Partition assigned to these Unity ports. Here are two examples;

The "Reorder tone detected" indicates you might have something configured on CCM or the gateway that blocks transfers to that number. Keep in mind that transfering to a number is very different than direct dialing the number.

To "verify that transfers are working" you should put an IP phone in the same CSS and Partition as Unity. Then call into that phone and use it to attept a transfer to 2625244162.

Transfers out of Cisco Unity fail.

This is usually caused when Cisco CallManager issues a reorder tone to Cisco Unity when a user tries to transfer out. In most cases, MIU errors appear in the application event log and complains about failed blind transfers, as shown in these examples:

Event Type: Error

Event Source: AvMiu_MC

Event Category: Error

Event ID: 525

Date: 1/9/2002

Time: 2:02:21 PM

User: N/A

Computer: PONY



Component Miu: Thread 0x00000C64 had a Failure on Port 3 in

Method CAvMiuLine::Transfer(eMIU_XFER_RELEASE)

Event Type: Warning

Event Source: AvCiscoTsp_MC

Event Category: None

Event ID: 111

Date: 1/9/2002

Time: 2:15:52 PM

User: N/A

Computer: PONY


AvCiscoTsp device 7: Failed blind transfer to extension 13800.

Reorder tone detected

For this issue, you need to start to verify these questions in order to troubleshoot with Cisco CallManager:

Does the extension the call is forwarded to actually exist?

Is the extension in a partition that is in the Calling Search Space of the voice mail ports? For example, can Cisco Unity call that extension?

What happens in the Cisco CallManager traces?

Hope this helps!


s.casper_2 Tue, 03/04/2008 - 04:37

Thanks for the response Rob. We are set up to go directly to a subscibers mailbox not ring an extension so I think that the Call Transfer function back to Call Manager should not be invoked. Shouldn't this be using Unity Digital Networking?

Rob Huffman Tue, 03/04/2008 - 05:47

Hi Steve,

In your error log it shows this;

Cisco Unity-CM TSP device 68 (Cisco Unity port 65): Failed blind transfer to extension 6396337. Reorder tone detected.

Which leads me to beleive an actual Transfer is being tried.

Let us know,


ranpierce Tue, 03/04/2008 - 09:47

there might be other configuration issues so let us know if what you decide is working for you.


s.casper_2 Sat, 03/08/2008 - 12:11

Ended up opening a TAC case. So far they have no fix yet. Will post solution.

Tray Stoutmeyer Sun, 03/09/2008 - 07:09

I have to agree with Rob here. If you get a re-order during a transfer (yes the transfer is being tried), this is going to come from Callmanager as Unity doesn't play re-order tone. Also re-order probably means there is a CSS/Partition issue as it can't reach the CSS/Partition that the extension is in. Good luck with the TAC case.


s.casper_2 Sun, 03/09/2008 - 13:21

I think the problem is that it IS trying to transfer via Call Manager. It should not - it should stay within Unity and use Digital Networking. Our mailbox numbers do not match our Call Manager Directory numbers so if the transfer function was being utilized then this should not work on my other Unity systems either.


This Discussion