Showing results for 
Search instead for 
Did you mean: 

Deleting System Call Handlers in Unity 7.x

I am trying to delete a system call handler for a conference room extension we have.  When I try and delete it I get an error message  "Operation cannot be completed because the object is in use"  How can I find out what its linked to so I can remove the link and delete the system call handler.

Cisco Employee

The same issues can happen when trying to delete a user if they are referenced in a call handler or something else.

The following bug was used to address that CSCsv34638 which is fixed in 7.1 according to notes on bug. Your situation may also be addressed by that bug fix but I'm just not sure.

Currently I have not been able to find any queries that might be able to find what references that call handler.

But most likely the Call Handler you have is referenced in another Call Handler, User or perhaps a Routing Rule.

Sorry I know that probably doesn't help that much.





Did a little more checking the issue with the call handler is more likely to be addressed in Unity Connection 8.x. So you could leave your current handler and then attempt to delete again when you upgrade to 8.x if you are unable to find where else in the system the Call Handler is referenced.

In speaking with another engineer you probably can user Audio Text Manager to attempt to find where the Call Handler is being referenced.

The tool can be found here:

There is a video that you can watch to learn how to use it.

Also note that this tool is not TAC Supported. This means you cannot call into TAC to get assistance with using the tool.

Hope that helps.



As Scott noted there are a couple of bugs related to dependency issues. The

Audio Text Manager tool that is available on can check

for references/dependencies on users, call handlers, and interview handlers.

Check this URL:

There is no way (that I know of) to force a delete when a dependency exists.

The approach is to use ATM to find the dependencies and then remove them





Please remember to rate helpful posts.

HTH -Bill (b) (t) @ucguerrilla

Please remember to rate helpful responses and identify

Cisco Employee

Bill et al,

For handlers (interview, directory, system, etc) that refuse to go  away, follow the same process as above but use this query:

run cuc dbquery unitydirdb select * from vw_handlerreference where  objectid in (select objectid from tbl_handler where  fn_tolower(displayname) = lower('myhandler'));

Replace myhandler with the actual display name of the handler.


run cuc dbquery unitydirdb select * from vw_handlerreference where  objectid in (select objectid from tbl_handler where  fn_tolower(displayname) = lower('Goodbye'));

objectid                             displayname                   referencetype referrerobjectid                     referrerobjecttype
------------------------------------ ----------------------------  ------------- ------------------------------------ ------------------
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 Opening Greeting              AfterMessage  3cbc5620-28b9-4757-8e20-138bbb5f8a27 3               
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 Operator                      AfterMessage  97ce3eab-4eb4-4627-acbf-627bb98cbd8d 3               
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 Primary                       AfterMessage  83b42c0c-38eb-47bd-8e95-a917b55b678d 3               
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 Primary                       AfterMessage  cd3764df-6ff9-4856-9910-abdc73e7125d 3               
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 RobWeimann                    AfterMessage  132b5cfe-e045-42ee-bcd0-2b7d86ce7cbf 3               
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 System Call Handler Template  AfterMessage  51f8b56a-61ac-4909-9dba-17aa18556571 3               
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 System Directory Handler      NoInput       a6dea20d-f5a9-4f76-be60-8aa8994c3037 6               
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 System Directory Handler      NoSelection   a6dea20d-f5a9-4f76-be60-8aa8994c3037 6               
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 abell                         AfterMessage  b55f1562-45e3-4b54-9e55-7a6d4ac081b2 3               
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 ebell                         AfterMessage  75c3f060-c5bf-4d24-9ffa-d056362dce47 3               
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 manoj3                        AfterMessage  8304ac82-63fa-4e80-9cc1-6b8052d73575 3               
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 miyazaki                      AfterMessage  8ce70dbd-9a6b-4ee6-8387-8a1dc4ced323 3               
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 operator                      AfterMessage  d0906380-687c-448f-a078-d8b8b7bfa3d1 3               
6b2bb401-f362-4010-8c4b-b389e4ac7eb6 undeliverablemessagesmailbox  AfterMessage  964fd52e-ed65-4992-b9fe-22cc7e39f560 3

99% of the cases I've seen are with users that have a caller  input option configured to point to the specific call handler.  In that  case, you'll see a "TTx" under the referencetype column where x=0-9.  Example, TT7 means caller input key 7 is configured to send to the call  handler you're trying to remove.

Hope that helps everyone,



This worked for me with a System Call Handler I tried to delete in Unity 10.5.  Turns out there was a Routing Rule I missed and this dbquery command found it for me.