Using Session Objects

Session palette steps can be useful in many situations. Some examples:

The script transfers a call contact back to a Cisco Unified IP IVR application, or redirects the call contact from one application to another application on the same Cisco Unified CCX server—This feature makes information about the original caller available to the script.
You want general information to be accessible by multiple scripts independently of contacts or customers—If you create and identify a session with a hard-coded mapping identifier, all scripts can access this session and access or alter information kept there.

Note	The created session, if not associated with a contact, is subject to deletion after the system default session timeout. However, each time the Get Session step retrieves the session, the timeout is reset.

You want to access real-time information using the real-time reporting client—This feature lets you see all sessions in the system and their associated values.

For an example that shows the use of Session palette steps, see Chapter 15, “Designing Cisco Unified CCX Scripts.” For an example that shows the use of Session palette steps, see Chapter 17, “Designing Cisco Unified CCX Scripts.”