Passing CLID and AgentID for CVP Call Transfer

Question

Hi, all.
Currently we are using CVP 7.0(2) integrated with ICM 7.5(9), Just want to check if the following is feasible:
1. Caller calls the hotline being routed to a queue.
2. An agent picks up the call.
3. Agent does a consult transfer to another ICM routing script configured with another Dialed Number. It is a post call survey.
4. The post call survey takes over the call when the agent complete the call transfer
5. The caller's no (CLID) and AgentID are passed over to the ICM Routing script of this post call survey.
Can we achieve the above mentioned scenario particularly on item 5? Would appreciate any help and advice.
Thanks & Regards,
Eric

Answer 1

Hi, Geoff.
Thanks for your reply. I have copied and pasted here a list of steps which you have posted previously about the CVP Warm Transfer.
1. PG Explorer - CUCM PIM Routing Client - Network Transfer Preferred not checked
2. PG Explorer - CVP PIM Routing Client - Network Transfer Preferred not checked
3. PG Explorer - CUCM PIM Advanced - Network VRU - NONE
4. PG Explorer - CVP PIM Advanced - Network VRU - Type 10
5. NVRU Explorer - Type 10 Network VRU, label for the CUCM routing client associated with the customer instance. Let's say this is 8222222222.
6. NVRU Explorer - Type 10 Network VRU, label for the CVP routing client associated with the customer instance. Let's say this is 8111111111.
7. Dialed Number List - dialed number for the incoming call associated with the customer instance. This dialed number is on the CVP PIM Routing Client. This DN is associated with a call type which is then mapped to the initial script.
8. Dialed Number List - transfer dialed number associated with the customer instance. This dialed number is on the CUCM PIM Routing Client. The transfer dialed number 3151 is associated with a call type which is mapped to the transfer script.
9. DNP. The number transferred to from CAD is 3141 which is a pattern in the DNP that maps to the Dialed Number 3151 with a post route to CUCM PIM Routing Client. The DNP Type is "PBX" - and PBX is set up in the Agent Desk Settings
10. Agent Desk Settings - All but "Operator" are checked
11. When the second call is placed for the warm transfer, the label defined on the CUCM RC plus the correlation ID will be sent back via EAPIM/JGW to CUCM (for example, if the label is 8222222222, with a correlation ID it could be 822222222212345) since the call originated from the CUCM RC and since the NetworkTransferPreferred check box is not checked.
12. A route pattern 8222222222! in CUCM sends the call down a SIP trunk to CUPS.
13. CUPS has a static route on 8222222222* to send the call to the CVP Call Server.
14. CUPS has a static route on 8111111111* to get the IP call to the gateway. Note that in a branch office deployment, TDM calls into the gateway use "Send to Originator" pattern in the Call Server to force the transfer label back to the voice gateway; so this pattern in CUPS is ONLY used by VoIP calls.
15. In all preliminary scripts that get the customer to the agent, set the variable Call.NetworkTransferEnabled to the value 1. This is set before the transfer is called.
18. For the device targets, you need a label on the CVP RC, but you do not need one on the CUCM RC, so do not add  one.
I did try the above mentioned steps in my system, the transfer works alright. The only difference is that I did not set the variable Call.NetworkTransferEnabled to the value 1. To the ICM, is is considered as Internal Out Transfer or External Out? Another thing I have noticed is that when the call transfer takes place, the IP phone would display the Route Pattern of the CM Label + correlation ID configured, e.g. 822222222212345. this is rather confusing for the agents when they see this long string of number as it does not make sense to them. Is there any way to display some other meaningful line display or number (E.g. Transfer to mainline or 2900) while maintaining the CM label pattern 8222222222!?
Thanks in advanced.
Regards,
Eric