■ Phone 3: Phone 3 can access Phone 1, Phone 2, Phone 4, and Phone 5.
■ Phone 2: Phone 2 can access Phone 1, Phone 3, Phone 4, and Phone 5. Devices cannot access DNs in the same partition unless their CSS gives explicit permission to that partition.
Phone 1 can access DN 1 on Phone 2 and Phone 4. ■ Phone 1: Like all other phones, this phone has access to all devices that do not have a lock applied (Phone 4 in this example). Phone 5 does not have any keys, which restricts Phone 5 to call only other DNs in the null partition.Īs a result of this implementation of locks and keys, the following effective permissions The key ring of Phone 4 contains only the lobby key. The executive key is not seen in the example, but it will be used in the system for executive management.
Phone 3 has a key ring with the lobby, employee, manager, and executive keys. Phone 2 has a key ring with keys for the lobby, employee, and manager key ring. When approaching CSSs from the perspective of key rings, Phone 1 has a key ring with the lobby and employee key on it. Phone 4 is therefore in the null partition, and everyone has access to call Phone 4. Following the analogy with locks and keys, there are three different types of locks (lobby, employee, and manager). Phone 4 has not been assigned to a partition. In Figure 13-1, DN 1 of Phone 1 has been configured in the lobby partition, and DN 1 of Phone 2 is in the employee partition, while Phone 3 and Phone 5 are both in the manager partition. If each house on a block has a different lock (partition), your key ring (CSS) would have to include many keys (to unlock different doors). An easier way of understanding partitions and CSSs is to use an analogy of locks and key rings. In Figure 13-1, various partitions and CSSs have been created. Partition is commonly referred to as the null partition. Entities that do not have a CSS assigned can only access numbers that are in partition. Members of partition are always accessible by sources of a call-routing request, regardless of the CSS applied to the calling party. Calls that come into the network from a gateway or trunk inherit the CSS assigned to the gateway or trunk.īy default, all entities that can be configured with a partition are in partition (null partition), all entities that can be configured with a CSS are assigned with CSS (null CSS). Any entry of the call-routing table, including voice- mail ports, directory numbers (DN), route patterns, translation patterns, meet-me conference numbers, and so on can be assigned to a partition.ĬSSs are assigned to devices, which are the source of a call-routing request (phones, phone lines, gateways, trunks, voice-mail ports, and computer telephony integration ports). Partitions are assigned to call-routing targets. A device can call only those call-routing table entries located in partitions that are part of the CSS assigned to the device. As soon as a phone number is assigned to a different partition, the devices in the network will not be able to access that phone number without the configuration of a calling search space (CSS).Ī CSS defines which partitions are accessible to a particular device. All phone numbers are in the null partition by default, and all devices have access to the null partition. Any dialable pattern can be assigned to a partition. Rebuild UCCX and perform a DRS restore.A partition is a group of dialable patterns with similar accessibility. Take a Disaster Recovery Service (DRS) backup.ģ. %CCBU_CUIC_MODEL_OBJECTS-0-EXCEPTION_INFO: %[exception=: is not in the allowed format for valuelistĢ. %CCBU_CUIC_MODEL_OBJECTS-0-ERROR: <- CuicFilterInfoRESTProvider.java:352Exception occured while building filter info: filterParam::AgentCSQStats.csqName=CL&= (Actual Agent ID) %CCBU_CUIC_MODEL_OBJECTS-3- field validation error: %]: Field validation failed POST /cuic/rest/en_US/filters/ HTTP/1.1 500ĬUIC service logs show the following errors: If the condition persists, contact your administrator."ĬUIC localhost_access_log.txt logs show an HTTP 500 Internal server error when loading the filter for the live data reports for newly added agents since new agents are not able to be synced from the UCCX db_cra database and don't exist in the UCCX_AgentID CUIC value list: The UCCX data source on CUIC shows "Offline".įor newly added agents, Live Data reports show "Error fetching filter info.