Technical References

and a DNIS value to send with it. A scheduled target is a destination for which the ICM/IPCC
knows only the number of scheduled resources and the number of calls in progress. For each
scheduled target, the ICM/IPCC maintains Scheduled Target Real Time data.
The routing client presents the ICM/IPCC with a Dialed Number (page 156). A dialed number
can be an 800 number such as 800-555-1234, or a string such as "RTE.007." Each Dialed
Number can have a default route.
A route is associated with one or more Network Targets. The network target has one or more
associated Labels (page 226). A label is the string that is passed back to the network to indicate
the appropriate target. The Dialed Number Label (page 158) table indicates which labels are
valid for each dialed number (or you can choose to make all labels valid for a routing client
valid for all of that routing clients dialed numbers).
For each route, statistics are produced in Real Time (page 292), every Five Minutes (page 285),
and every Half-hour (page 288).
A Route Call Detail (page 278) record is produced immediately after the ICM/IPCC determines
a route. This records information about the request and the route determined by the ICM/IPCC.
A Termination Call Detail (page 407) record is produced at the end of each call. Data for this
record comes from the Peripheral Gateway . It provides information about how the call was
handled at the peripheral. The Route Call Detail and Termination Call Detail are linked by the
Day and RouterCallKey elds.
A script may direct a call to a Network VRU (page 244) associated with the routing client. The
script returns a label to the routing client. It may also specify a Network Vru Script (page 246)
to be executed by the VRU.
Schedule Tables - Database Rules
To see an illustration and a list of all tables in the Schedule category, click here (page 450).
With the optional Schedule Import feature, you can import schedules for each agent, skill group,
and service from a workforce management system.
The Schedule (page 305) table contains one entry for each schedule.
The Schedule Import (page 307) table contains the actual scheduling data for various time periods.
The Schedule Import Real Time (page 309) table contains the scheduling data that is currently
in effect.
The Schedule Source (page 314) table indicates where the data are imported from. The Schedule
Map (page 312) table gives the primary key value for the scheduling data in the source.
The ICR View (page 215) table indicates how the Schedule Import records for a schedule are to
be interpreted.
The View Column (page 433) table indicates how to interpret each eld in Schedule Import
Database Schema Handbook Cisco ICM/IPCC Enterprise & Hosted Editions 7.2(2)
508
Chapter 5: Database Rules
Schedule Tables - Database Rules