There are so many reason why a call can get "stuck." If this is a chronic, business impacting problem, I suggest opening a TAC case to have your logs reviewed.
Otherwise, search the forums for other threads relating to this topic.
Do you know if the call was active? What I mean is, was there a caller on the line for 45 minutes? I doubt it, as most people will not wait 45 minutes.
There has been a long standing issue with phantom calls in UCCX, and in 7x Cisco provided a way to clear these calls without the need for bouncing the whole CRS engine. So it's just something you learn to live with.
I would encourage you, if you don't already, limit the length of time a caller can queue, before you send them somewhere else. Or, put some sort of notification in place (email, place call, etc) so you can address the issue, before it becomes a 45 minute call, followed by a disconnect.
Please use the star ratings to help drive great content to the top of searches.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.