We're having problems transferring to ICD from the Opening Greeting by pressing 0. 0 is set to attempt transfer to a subscriber whose extension is the CTI route point for ICD. We basically want to have 0 send callers to an operator queue in ICD. However, when a caller presses 0, instead of transferring into ICD and hearing the ICD prompts, there are 4 rings followed by a busy signal. We receive the same result be dialing the extension directly from the Opening Greeting. Picking up the phone and dialing the CTI route point takes you right into ICD. Transfers to regular extensions seem to working fine. Does anybody know why Unity can't transfer to ICD?<br><br>Unity 3.13c<br>TSP 6.01<br>CM 3.1<br>ICD 2.2x (I think)<br>Windows 2000<br><br>
You've got real close to manually simulating what Unity is trying to do, but not exactly. Can to take IP phoneA, call IP phoneB, and from IP phoneB transfer IP phoneA to the CTI route point that takes calls to the ICD?
This problem was just resolved by upgrading to the most recent version of ICD 2.2x that supports CM 3.1. This upgrade coupled with the addition of a 2 second delay before the call is accepted by ICD fixed the transfer problem. Evidently, Unity holds onto the call briefly when doing a release to switch transfer and this causes issues with ICD.
I'm trying to do this right now with CM 3.2(2a), ICD 2.2(3b), and Unity 3.1(4). Transfers to regular extensions work, but when trying to transfer to the CTI route point for the ICD queue, it simply hangs up. When I initially set it up, it worked for about 3-5 times, but then just stopped.
How/where do you add a delay before call is accepted by ICD?
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.