Yes, it should be possible. There are several requirements to make it working:
Both PBXes are monitored by T-Servers
Call transferred from PBX_A to PBX_B is transferred to specified numbers only
Number mentioned in previous note have to be provisioned in Genesys configuration as COF (Call Overflow) DNs - that way T-Servers can match the call and exchange UserData.
Please read section “ISCC/COF Feature” in T-Server Deployment Guide.
If steps 1 & 2 do not involve Genesys, I can’t see how you can set key-value pairs (but maybe that depends on the PBX in question). To transfer the call between the 2 PBX, you either need some tie-curcuits or need to route the call via the public network, either way what would pass the key-value pairs?
I think for this to work you would need Genesys to be involved from the beginning, and then to use ISCC as Rene suggests.
The PBX_A is not under my control, it’s from outside, so I can’t get a TServer on it (I knew this). I have chosen a brute solution to transfer the calls from PBX_A on specific numbers, so now I have calls incoming on diferent DNs (PBX_B) that I’ve maped them into groups …and now I know what to do with each type of call
So I somehow managed to pool this off, for now…
Well, that’s a good idea. Managing to pool this off will make you feel better, I guess so. By the way, can I know the advantages of PBX key call transfer without having CTI?