/mcpKeys and NULL Option Data Type Description Name NULL DBINT Number of calls skipped due to Consider If in step 2. SkipStep2 NULL DBINT Number of calls skipped due to Consider If in step 3. SkipStep3 NULL DBINT Number of calls skipped due to Consider If in step 4. SkipStep4 NULL DBINT Number of calls skipped due to Consider If in step 5. SkipStep5 NULL DBINT Number of calls skipped due to Consider If in step 6. SkipStep6 NULL DBINT Number of calls skipped due to Consider If in step 7. SkipStep7 NULL DBINT Number of calls skipped due to Consider If in step 8. SkipStep8 NULL DBINT Number of calls skipped due to Consider If in step 9. SkipStep9 NULL DBINT Number of calls skipped due to Consider If in step 10. SkipStep10 NOTNULL DBINT The Central Controller’s time zone for the date and time. The value is the offset in minutes from UTC (formerly GMT).The value is negative for time zones to the east of UTC and positive for time zones to the west of UTC. TimeZone Routing_Client This is in the Device category (see Device, on page 618). For database rules, see Device Tables, on page 698. Each row corresponds to a routing client; that is, an entity that can submit routing requests to the system software. A routing client can be either a Network Interface Controller (NIC) or a Peripheral Gateway (PG). Use the NIC Explorer tool to add, update, and delete Routing_Client records. Related Tables Default_Call_Type, on page 209 (via RoutingClientID) Dialed_Number, on page 215 (via RoutingClientID) Label, on page 283 (via RoutingClientID) Logical_Interface_Controller, on page 288(via LogicalControllerID) Peripheral, on page 326 (via PeripheralID) Route_Call_Detail, on page 380 (via RoutingClientID) Routing_Client_Five_Minute, on page 420 (via RoutingClientID) Translation_Route_Half_Hour, on page 588 (via RoutingClientID) Database Schema Handbook for Cisco Unified Contact Center Enterprise, Release 15.0(1) 416 All Tables Routing_Client