Configuring the CSTA Connector
Pre-Requisites
- If you are using Management Framework 8.1.x, add an application of type CSTA Connector.
- If you are using Management Framework 8.0.x, or earlier, add an application of type HA Proxy.
T-Server Specific Connection Configuration
T-Server for CSTA Connector initiates a session with a CSTA Connector as follows:
- If there is at least one application of type CSTA Connector in the list of Connections, T-Server reads the CSTA Connector's connectivity options (including the secure port information) and CSTA Connector is handled as a server with normal connectivity options.
- T-Server looks for applications of type CSTA Connector or type HA Proxy (If you are using Management Framework 8.0.x, or earlier, you must use an application of type HA Proxy).
Note: At the moment, T-Server can only have one CSTA Connector in its list of connections.
- If a CSTA Connector Application object does not exist in the list of Connections, T-Server uses the normal link section configuration.
Device Configuration in the Configuration Layer
The following table displays the device configurations in the Configuration Layer:
Switch Device Type | DN Type | Switch-Specific Type | Association |
---|---|---|---|
End Point |
Extension |
Not applicable |
Not applicable |
Call Center |
ACD Queue |
Not applicable |
Not applicable |
Route Point |
|
|
|
Switch Terminology
The following table compares the relevant switch terminology with the Genesys terminology:
Genesys Term | Switch Term |
---|---|
ACD Queue |
Call Center |
Agent ID |
User |
Extension |
End Point |
Routing Point |
Route Point |
Logon |
Sign In |
Logoff |
Sign Out |
Ready |
Available |
NotReady |
Unavailable |
AfterCallWork |
ACD Wrap-up Timer |
Account Code |
Call Disposition Code |
Reason Code |
Agent Unavailable Code |
This page was last edited on August 1, 2013, at 13:39.
Comments or questions about this documentation? Contact us for support!