26Unified ICM Configuration
2.10.1.Simple Case
In the simplest case, only one CompuCALL Session is configured in the DMS PIM, in the third-party application, in CCS, and at the DMS-100 (see diagram below).In this simple case, exactly one connection will be used:
1.Between CCS and the third-party application (X.25 or TCP)
2.Between CCS and the DMS PIM (Cisco proprietary EMT interface)
3.Between CCS and the DMS-100 (X.25 or TCP).
Figure 4: CompuCALL Session: Simple Case
In this simple case, which will likely also be the typical case, the CCS setup requires the configuration of the following:
1.One ACD Link of type X.25 or TCP (from CCS to the DMS-100)
2.One application Link of type X.25 or TCP (from CCS to the third- party application)
3.One Session – which includes which ACD Links are used by the Session (from item 1 above)
4.Two applications for the Session:
•One for the third-party application -- which includes which application Links are used by the third-party application (from item 2 above)
•One for the DMS PIM
Once the CCS is configured and running, the third-party application and the DMS PIM can execute the following steps (just as they would if connected directly to the DMS-100):
1.Create a connection (either X.25 SVC or TCP for the application, EMT for the PIM)
2.Send a Session Logon message on the connection
3.DN Associate those Agents or Agent groups to be monitored
When the PIM or the third-party application logon, whichever is first, CCS will establish a connection to the DMS-100 and send the logon message to establish a CompuCALL Session with the DMS-100. This Session will be shared by both the third-party application and the DMS PIM, once both have logged on. The DMS-100 Session will be maintained as long as either the third-party application or the DMS PIM remains logged on to the CCS. (Generally, either the third-party application or the PIM can log on first; however, the third-party application and the PIM can be assigned a
