10-22-2020 09:37 AM - edited 10-27-2020 11:59 AM
To participate in this event, please use the button below to ask your questions
Ask questions from Thursday, October 22 to Friday, October 30 2020
For more information, visit the Contact Center community.
10-22-2020 11:44 AM
Hi German and Konstantin
Thank you for providing such a great event!
Please help us to answer these remaining questions from the live session:
10-27-2020 02:04 AM
Hi everyone,
1. The "Network transfer preferred" usually used in the CVP comprehensive callflow.
Unified CVP provides capabilities to transfer calls to another destination after they an agent answers them. These capabilities are referred to as Network Transfer. The Network Transfer feature does not require any special installation on the part of Unified CVP.
ICM will send the label to initial VRU (original) Route Request during the Transfer Scenario Agent has initiated CUCM as the Routing client.
Call flow
[Call Flow -> Ingress -> CVP->ICM->CVP -> LABEL->CUCM -> CUCM (Agent 1) initiate the transfer ->DN/CTIROUTE Point -> ICM -> Network Transfer Enabled ->VRU LABEL-- > CVP Routing Client ]
There are two flags in to control the Network Transfer:
• NetworkTransferEnabled — This is a flag in the Unified ICME script. If enabled, it instructs the Unified ICM to save the information about the initial routing client (the routing client that sent the NewCall route request).
• NetworkTransferPreferred — This flag is checked on the Unified CVP PG configuration. If it is checked, then any route request from this routing client (where Unified ICME knows about the initial routing client) will send the route response to the initial routing client instead of the routing client that sent the route request.
The following recommendations apply when using Network Transfer:
•Network Transfer using the two flags listed above can be used to perform a blind transfer only from agent 1 to agent 2 via Unified CVP. In this case, Unified CVP will get instruction from Unified ICME to pull the call back from agent 1 and route it either to a VoiceXML gateway (for IVR treatment) or to another destination (to agent 2, for example).
•Network Transfer cannot be used to perform a warm transfer or conference with Unified CVP because the call leg to agent 1 must be active while agent 1 performs a consultation or conference. Unified CVP cannot pull the call back from agent 1 during the warm transfer and/or conference.
2. There are no any restrictions for transferring calls to any PBX.
The PBX must be reachable by the network, so the CUCM or CVP will be able send SIP request to it.
CVP Configuration guide contains information about supported transfer methods and design considerations.
10-22-2020 02:55 PM
That’s cool guys! I am looking forward to using it!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide