Partitions & Search Spaces TOI

1. Partitions & Search SpacesTOI Aaron Belcher

2. Overview This feature is an attempt to create a grouping mechanism for Unity Connection that maps to CUCM's call search space and route partition features. CUCM object to corresponding CUC object: • route partition -> partition • call search space -> search space

3. Partitions: • Addressable objects are assigned to a primary partition. The primary partition contains the object and the objects primary extension. • Subscribers can also have alternate extensions in other partitions called alternate partitions. The alternate partition contains the subscriber and the subscribers alternate extension. • When an object is created it is assigned to the search space and partition of the template if one is used or the system default settings when a template wasn’t used. • Alternate extensions are always create in the primary partition of the subscriber, but the administrator can move them to a different partition. • All the extensions within a partition must be unique.

4. Search Space usage: • Search spaces limit the objects that a caller or logged in subscriber can see in the system. • The search space’s partition order is used in a numeric search to decided on a single, unique match. • These objects have search spaces: Subscribers, Directory Handlers, Call Handlers, VPIM Locations, Subscriber Templates, and System Call Handler Templates.

5. Searches using Search Spaces • When Unity Connection searches for an extension, caller id, or forwarding id it looks through the search space's partition list in order until it finds a primary or alternate extension that matches. • When Unity Connection performs other types of searches it returns all objects that are in the search space's partition list that match the search criteria.

6. Search space of the call concept: • Each call is assigned a search space by the routing rule. These search spaces are used when matching the caller/forwarding ID to a subscriber, when a caller tries to sign in, or when a caller enters an extension in a call handler. • The search space of the call is changed when the caller hits a call handler with a different search space. The search space of the call can only be changed by a routing rule or a call handler. The search space of the call is not changed when a user logs in or a directory handler with a different search space is used.

7. Subscribers and Search Spaces While a subscriber is logged into either the TUI, VUI and CPCA, all searches that a subscriber does use the subscribers search space. The subscribers search space is also used when searching for recipients while a message is delivered. If the recipient isn’t in the search space an NDR is created. During message deliver, we only check the search space membership of top level recipients. We don’t check each member of a distribution list.

8. Handlers and Search Spaces • Directory handlers can be configured to use either the call’s search space or a specific search space to scope its searches. • Call Handlers can be configured to either change the search space of the call, or inherit the calls search space. The search space of the call is used in the call handler when doing extension based searches or signing in.

9. Other objects and Search Spaces • VPIM Locations: A VPIM locations search space is used for matching incoming VPIM messages from the sending VPIM Location to extensions. • Routing Rules: When a routing rule is matched, the routing rule’s search space is set to be the search space of the call. • Templates: When an object is created using a template the object is created with the templates search space.

10. Deleting a partition To delete a partition it must be empty. If you try to delete a partition that is in use you will get an error. You can look at each object using the “Limit the Search to” “partition” option. Here is a list of objects: subscriber (Check the Display and Alternate Extensions radio button), contacts, VPIM locations, System Call Handlers, Interview Handlers, and Directory Handlers.

11. Deleting a search space: When an administrator deletes a search space the administrator is asked to select a replacement search space. All objects assigned to use the original search space, will be assigned to use the replacement search space, and the original search space will be deleted. There will be a log file called SearchspaceRemovalLog.txt describing what happened during this operation.

12. Advanced Searches using Search Spaces When Unity Connection is doing a search using the VPIM location’s “dtmf access id” plus “VPIM Remote Mailbox Number” or Vui’s “Contact’s name or VPIM Remote Mailbox Number ” at “VPIM location’s name” syntax the VPIM’s locations partition membership is checked. Then all contact’s associated with the VPIM location that match the “VPIM Remote Mailbox Number” or “Contacts name” are returned regardless of their partition membership. For example, if you have a VPIM location with the “Seattle” name and a dtmf access id of 8256, then these searches will all work if the VPIM location is in a partition in the current search space: • 82563071, “Aaron Belcher” at “Seattle” and “3071” at “Seattle”

13. Using Search Spaces to Restrict access to contacts. If the customer want’s to restrict the contacts that a subscriber can access, they should: • 1. Not add the VPIM locations partition to the subscriber’s search space. (This affectively, disabled the dtmfaccessid and “at” VUI syntax. • 2. Assign the contacts that the subscriber can access to a partition in the subscribers search space. • 3. Assign the contacts that the subscriber can’t access to a partition outside of the subscribers search space.

14. Deployment Recommendation’s for multi-site deployments. • Create one partition for globally unique numbers on each server. • Create one partition for each site homed on each server or rename the default partition. • Create one search space per site or rename the default search space. • Add the site’s partition followed by a globally unique partition’s to it’s search space. • Assign all the subscribers to corresponding partition/search space.

15. Configuring dial plan with CUCM: • Unique outdial numbers: • Create a hunt pilot per site on CUCM • Create a routing rule to match the hunt pilot and assign the search space of the call to associated site. • For transfers and outdials always use the unique number outdial number… • Per site/voicemail ports. • Create a set of voicemail ports per site on CUCM • Create a switch on Unity Connection per set of voicemail ports • Create a routing rule to match the switch and assign the search space of call to the site.

16. Trouble shooting Tips… • Reports: • Dial Plan Report • Dial Search Scope Report • Traces: • Generic trouble shooting: • Service “Connection Conversation Manager”, • Macro Trace: “Call Flow Diagnostics->Conversation Flow Diagnostics” • Micro Trace: Component CDE, 04 Search Space • Troubleshooting NDRs: • Service: “Connection Message Transfer Agent”, • Micro Trace: Component MTA, all flags

17. Common Issue 1: Can’t find remote Users • Issue: A networking node was added but users can’t find remote users. • Solution: Add the remote partitions to the local search space once replication has completed. • Diagnostics: Conversation Manager

18. Common Issue 2: User can’t login • Issue: A user can’t log in over the TUI. • Solution: Make sure the routing rule is pointing to call search space that include the subscriber • Diagnostics: Conversation Manager

19. Common Issue 3: NDR’s from VPIM • Issue: NDR’s from VPIM • Solution: Make sure that the recipient’s extension is in a partition that is in the search space of the VPIM Location. • Diagnostics: MTA