Hey Barry -
There could be a couple pieces to this. I would first enable the Track Routing Exceptions feature in Interaction Tracker. I know we've discussed this before. It will tell you the CallId that was transferred, define the type of transfer (blind, consult, park), and determine the transfer target (queue, user, both, etc.) in the database (specifically the EE_TransferEvents_viw view).
For the other portion, actually defining the 2nd CallId, you could certainly do it via a custom handler. And I haven't tested, but I also believe you could utilize the CustomAttributes table for this. In looking at the
Attributes Reference Guide, it appears this could be custom logged via the Mappings tab of the Report Log ID 20 (Interaction Custom Attributes Log). Specifically, if you have a look at the following attribute definitions, you'll be able to get to the information you're looking for (or at least get super close if i'm misunderstanding):
Eic_ConsultCallId
Eic_ConsultingCallId
Eic_ConsultTransferCallId
Thanks