n Genesys Framework, the T-server is THE component to monitoring extensions (and other DNs as well).
The generic term of T-server is CTI server which
(1) interfaces to switch's CTI-link
(2) sends command requests to switch (or PABX)
(3) receives results of sent commands asynchronously
(4) receives registered DNs change of states messages with attached data asynchronously
Genesys T-server transfers business data by mean of Key/Value pairs.
There are 3 linked lists in the event message structure
- Users: for application/user defined data; must have an active interaction
- Extensions: telephony system or special data; on active interaction
- Reasons: 'usually' for agent mode operation; not necessarily on active interaction
The framework holds up to 64KB KV pairs data in an interaction.
In additional to KV pairs data, event message structure also includes a list of telephony data fields such as CLI, DNIS, call ID (from CTI-link/switch), connection ID (generated by Genesys T-server), calling/called/other DNs, transferred number/connectionID, ....
Genesys T-server maintains KV pairs data by itself.
When an application registers an extension to T-server via Genesys SDK, event messages along with "Attached data" will be distributed to the registered application asynchronously.
Genesys offers training courses to cover above technical stuff in details.
Take them whenever possble!
