Transfer Attempt Warning Event ID 1155

Unanswered Question
Feb 25th, 2009
User Badges:

Does anyone have any idea why I keep getting warnings such as the one below? I have checked all of the restriction tables but everything looks good. Any ideas?

Event Type: Warning

Event Source: CiscoUnity_ConvSub

Event Category: (14)

Event ID: 1155

Date: 2/25/2009

Time: 1:42:31 PM

User: N/A

Computer: UNITY


Transfer attempt for Call Handler: SA(extension: 2803) failed on port 5. Possible reason could be the dial plan on the phone system does not allow this dial string: 2803. The dial string used was taken from the Call Handler's Contact Rule: 'Standard'.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Bradford Magnani Wed, 02/25/2009 - 22:18
User Badges:
  • Cisco Employee,


This error indicates a failed transfer to the phone system. Just throwing some ideas out... It's possible that Unity heard re-order, or no response when trying to transfer off your call handler. Or perhaps, the voice mail ports are in a partition that does not have access to transfer to a particular DN. Just some ideas...

If it's reproducible, you'll probably want to set Macro diagnostics on Unity: Call Flow, Call Control, Conversation State, Skinny TSP and also enable detailed CUCM traces if you're integrated with CUCM.

Hope that helps,


mikegemza Thu, 02/26/2009 - 05:59
User Badges:

That's the problem. It's not reproducible.

I actually set up the event monitoring service to email me every time I get one of those errors so I can call right in to try to replicate it. I can hit the same port and it will work.

I am getting tons of these every day. Most of the transfers are to ACD queues that are managed by the NEC phone switch so it is virtually impossible for it to hit busy.

If it helps Unity is integrated to an IMX 2400 via a 24 port dialogic Timg unit. I am not using any IP phones yet.

culittle Thu, 02/26/2009 - 08:51
User Badges:
  • Cisco Employee,

What choice or default call flow on your call handler is dialing 2803? Finding that should allow you to reproduce the problem.

You would then need to set the TIMG trace to record the failed call. You could then listen to the audio of the failed call to see if you are getting any error tones.

mikegemza Thu, 02/26/2009 - 09:27
User Badges:

Thats the problem. I can retrace the exact path right after I get the error and it works perfectly. It seems to be intermittent.

mikegemza Fri, 02/27/2009 - 07:44
User Badges:

I actually just created one of these warnings but my call went through as expected. I am wondering if it is actually going through as expected on all of them....

Christopher McAlpin Wed, 03/04/2009 - 16:07
User Badges:
  • Cisco Employee,

Does this seem to happen only for calls that are transfered to an ACD group?

If you can narrow it down to a specific call handler or notice that it is happening very frequently for a specific call handler, try adding a comma or two to the dial string to see if this reduces or eliminates the problem.

This is definitely shooting at the hip type troubleshooting, but many integration issues like this are timing related. There is a post-dial delay setting in UTIM but this would affect every call for that telephone integration. So adding a call to a particular call handlers dial string is less intrusive at this point in the game.

mikegemza Wed, 03/04/2009 - 18:59
User Badges:

Yep most of them are happening with ACD transfers. I will try adding a comma or two before the transfer extension and report back. Thanks for the idea!

Gear Misner Thu, 08/26/2010 - 12:29
User Badges:


Did you get anywhere with this problem?  I am running into the same issure with CUCM 7.1.5 and Unity 7.0.2.  We have the two integrated using a sip trunk.  Any help would be great.  Thanks.

dugward Tue, 09/11/2012 - 15:27
User Badges:

I believe a number of things can cause this error, one I've found is the user forwarded their phone to another extension, than forwarded that phone BACK to their main extension. Obviously it's a loop and gives you a fast busy but I've replicated this error with that situation. 

However I've received it in other instances as well and that's why I'm trying to figure the others out.


This Discussion