Cannot delete call handler from Unity Connection 7.1
I have a call handler that was not working correctly. I create another one to do what I wanted that one to do and I went in to delete the bad one and it tells me the handler is in use and will not delete it.
Is there some way to have it not be in use when nothing is pointing to it so I can delete it?
Re: Cannot delete call handler from Unity Connection 7.1
Most likely there is something referencing it somewhere (or it could be a dependency issue bug - there have been a couple of those along the way). In Connection 8 there is a "check dependencies" button for all objects to help with this - in 7.1 this function didn't exist. The Audio Text Manager does have a dependency check report for users, call handlers and interview handlers which can help run down issues such as this (assuming there is a reference from some object to that handler causing the delete to choke):
I'll be adding call handlers to the BUlk Delete tool for Connection this dev cycle and that would get around this as well by using a forced replacement object when deleting (which tells the database to relax about references to a handler being deleted since it can replace those reference with another).
but there's no way to force an object the database _thinks_ is being referenced to be removed - Connection's database enforce strict foreign key constraints unlike Unity (i.e. it's not possible to get orphaned data or have invalid links like you can in Unity).
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...