Cisco Unified Contact Center Enterprise Solution Reference ...
Cisco Unified Contact Center Enterprise Solution Reference ...
Cisco Unified Contact Center Enterprise Solution Reference ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Conferences in a <strong>Unified</strong> CCE Environment<br />
Reconnect<br />
Alternate<br />
1-30<br />
<strong>Cisco</strong> <strong>Unified</strong> <strong>Contact</strong> <strong>Center</strong> <strong>Enterprise</strong> 7.x SRND<br />
Chapter 1 Architecture Overview<br />
Generally the conferencing agent will not click the Conference Complete button before the target agent<br />
answers because the probable reason they used consultative conference was that they wanted to talk with<br />
the target agent before completing the conference. However, the conferencing agent can click on the<br />
Conference Complete button at any time after it is enabled.<br />
If the agent is conferencing the call to a generic DN to find an available agent with a particular skill, but<br />
no such agent is currently available, then the <strong>Unified</strong> ICM routing script should be configured to route<br />
the call to an IVR for queuing. In this scenario, the conferencing agent would hear the <strong>Unified</strong> IP IVR<br />
queue announcements. The conferencing agent could press the Conference Complete button at any time<br />
to complete the conference. This particular scenario is known as warm transfer. The caller and the agent<br />
would then begin hearing the <strong>Unified</strong> IP IVR queuing announcements while the agent still guides the<br />
caller or continues to process the call while waiting. Upon availability of an appropriately skilled agent,<br />
the <strong>Unified</strong> IP IVR conferences the call to this target agent and pops any call data onto their screen.<br />
If the agent is conferencing the call to a number that is not in the <strong>Unified</strong> ICM Dialed Number Plan and<br />
a number that is not valid on the <strong>Cisco</strong> <strong>Unified</strong> CallManager, the conferencing agent will hear the failed<br />
consultation call and will be able to reconnect with the original caller, as explained in the section on<br />
Reconnect, page 1-30.<br />
During the consultation leg of a consultative conference, the conferencing agent can reconnect with the<br />
caller and release the consult call leg. To do so, the agent simply clicks the Reconnect button. This action<br />
causes the agent desktop to instruct the <strong>Cisco</strong> <strong>Unified</strong> CallManager PIM to instruct <strong>Cisco</strong> <strong>Unified</strong><br />
CallManager to release the consultation call leg and to reconnect the agent with the original caller.<br />
This is basically the process an agent should use when they want to make a consultation call but for<br />
foreseen or unforeseen reasons do not desire to complete the conference. After a call is successfully<br />
reconnected, the conferencing agent's desktop functionality will be exactly the same as before they<br />
requested the conference. Therefore, the conferencing agent can later request another conference, and<br />
there is no limit to the number of consultation calls an agent can make.<br />
Consultative conferences and reconnects are all done from the agent desktop and use the single<br />
<strong>Cisco</strong> <strong>Unified</strong> CallManager extension that is associated with the <strong>Unified</strong> CCE. The <strong>Unified</strong> CCE system<br />
does not support allowing the conferencing agent to place the original caller on hold and then use a<br />
second extension on their hardware phone to make a consultation call. The hardware phone offers a<br />
button to allow this kind of conference, but it is not supported in a <strong>Unified</strong> CCE environment. If an<br />
agent conferences a call in this way, any call data will be lost because the <strong>Unified</strong> ICM did not route the<br />
call.<br />
Alternate is the ability for the agent to place the consultation call leg on hold and then retrieve the<br />
original (or conference) call leg while in the midst of a consultative conference. The agent can then<br />
alternate again to place the original caller back on hold and retrieve the consultation call leg. An agent<br />
can alternate a call as many times as they would like.<br />
When the conferencing agent has alternated back to the original caller, the only call controls (buttons)<br />
that are enabled are Release and Alternate. The Conference (Complete) and Reconnect controls will be<br />
disabled. The Alternate control will alternate the conferencing agent back to talking with the consulted<br />
party. When the agent has alternated back to the consultation leg, the Release, Alternate, Conference,<br />
and Reconnect call controls will be enabled. The Alternate control will alternate the conferencing agent<br />
back to talking with the original caller. The Conference control will complete the conference, and the<br />
Reconnect button will drop the consulted party and reconnect the agent with the original caller.<br />
OL-8669-05