Contacts Separation. 1 Introduction. 1.1 Article Purpose. 2 Environment Configuration. 2.1 Imagicle ApplicationSuite configuration

Transcription

1 Contacts Separation 1 Introduction 1.1 Article Purpose Speedy Enterprise is the solution that centralizes and synchronizes company directories, providing fast searches, click to call and caller ID on phone, web, mobile and Cisco Jabber. Speedy supports four different directory types: 1. Local Directories (internal contacts only); 2. Public Directories (external contacts, not to be used in a Multi-Tenant/Company environment); 3. Department Directories (internal or external contacts); 4. Personal Directories (external contacts only). Speedy can be used in the following scenarios: 1. In a single Tenant/Company environment, making available one Local Directory shared-accessible by all users; 2. In a single Tenant-Company environment with different departments, where users belonging to each Department can be granted access to only their own department contacts (Contacts Separation); 3. In a Multi-Tenant/Company environment, where users belonging to each Tenant/Companies can be granted access only to their own Company contacts (Contacts Separation). In case Contacts separation is not required, please refer to standard Speedy configuration documentation ( which covers both the cases for local-vpn and in mobility (MRA) connectivity. In case Contacts Separation is required, please continue reading this guide. In scenarios 2 and 3, it is a common requirement to ensure a separated access to contacts and directories to the different departments-tenants included into the same shared instance; this is typically required for Corporate Directory access from IP Phones and for Jabber clients, both from the office or VPN and when in MRA. In such situations, Imagicle Speedy can: Replace existing Cisco UDS server and act as an alternate UDS server to provide each customer with the proper list of own Department-Tenant Internal Contacts on their Jabber Clients and other devices supporting UDS; Replace existing Cisco Global Directory XML service to provide each customer with the proper list of own Department-Tenant Internal and External Contacts on their IP Phones; The following chapters explain how to configure the environment for proper contacts separation with all supported devices and scenarios. 2 Environment Configuration This chapter details how to configure contacts separation in the different supported scenarios. Paragraph 2.1 contains configuration common across all scenarios while the following paragraphs describe additional scenario-specific configuration. 2.1 Imagicle ApplicationSuite configuration In order to enable Imagicle Application Suite to deliver contacts separation through Speedy Directory service, it is required to access Speedy and to set in "Manage service" menu option, a specific flag, as per picture below. Contacts Separation 1/9 Contacts Separation

2 It is required to click on "Save" at the bottom of the page to apply change(s). This is a general setting that should be configured in all the three cases, described in detail in the following chapters: 1. UDS-based Internal Contacts Separation configuration for Jabber and supported devices; 2. Speedy Gadget for Jabber Internal and External Contacts Separation configuration; 3. XML-based Internal and External Contacts separation configuration for IP Phones. 2.2 UDS-based Internal Contacts Separation configuration for Jabber and supported devices This configuration applies to all devices which use Cisco Unified Communications Manager User Data Service (UDS) protocol (Jabber clients, DX, MX, SX, Telepresence Codecs. Etc.) that are registered to a Cisco Unified Call Manager. To enable contacts separation, Imagicle Speedy has to act as an alternate UDS Server to all the supported devices; to do so, it is required to: In case of Jabber clients, apply a specific configuration to the Jabber configuration file(s) in order to enable Imagicle Speedy Directory service to take care of Contacts related actions (contact searches and relevant pictures). The configuration is different in case a customized Jabber configuration file is already in place (chapter 2.2.2) or not (chapter 2.2.3); In case of all the other supported endpoints, to specify UDS as alternate phone book server type (picture below, with Imagicle Server FQDN) in the CuCM, in their relevant device configuration page. Please note that it is required to create one general system-wide Jabber config file and one jabber config file per each Customer-Tenant Customer-Tenant based Contacts separation DNS configuration Before proceeding with jabber configuration, it is required to make sure that each customer-tenant in Shared Architecture infrastructure has an associated DNS entry pointing to Imagicle server's IP address. (i.e. *.imagicle.mydomain.com). This is done creating a new Sub-Domain entry into the Company Domain Manager, as in figure below. Contacts Separation 2/ Customer-Tenant based Contacts separation DNS configuration

3 Each Imagicle Application Suite Server must have an associated Host A entry inside the above created Sub Domain. If High Availability is in place it is necessary to create two HA entries, one pointing to primary and one to secondary node. Host A entry name should be created using "*", in order to match any FQDN in the Sub Domain resolving it with Imagicle Server IP address (in figure above ) Contacts Separation 3/ Customer-Tenant based Contacts separation DNS configuration

4 2.2.2 Already existing customized Cisco Jabber gadget xml configuration file General system-wide Jabber config file must be configured to prevent contacts search into any Customer Tenants. This jabber config will be used in case of any type of misconfiguration at device level or xml file level. Name must be "jabber-config.xml" <UdsServer>empty-uds.imagicle.mydomain.com</UdsServer> In case a customized Cisco configuration file is already in place, it is recommended to modify this file adding the XML code lines highlighted in the example jabber config file below; these lines should be contained in-between the "Directory" XML statement <Client> <jabber-plugin-config> <browser-plugin> <page refresh="false" preload="false"> <tooltip>speedy</tooltip> <icon> <url> </page> </browser-plugin> </jabber-plugin-config> </Client> <Policies> <DirectoryURI>mail</DirectoryURI> <EnableCallPickup>true</EnableCallPickup> <EnableGroupCallPickup>true</EnableGroupCallPickup> <EnableSIPURIDialling>true</EnableSIPURIDialling> <UserDefinedRemoteDestinations>true</UserDefinedRemoteDestinations> <Voic _Enabled>false</Voic _Enabled> </Policies> <UdsServer>customer1.imagicle.mydomain.com</UdsServer> See for file upload. Contacts Separation 4/ Customer-Tenant based Contacts separation DNS configuration

5 2.2.3 Not existing customized Cisco Jabber gadget xml configuration file General system-wide Jabber config file must be configured to prevent contacts search into any Customer Tenants. This jabber config will be used in case of any type of misconfiguration at device level or xml file level. Name must be "jabber-config.xml" <UdsServer>empty-uds.imagicle.mydomain.com</UdsServer> In case no Jabber config file is in place, it is possible to create one containing the following lines. <UdsServer>customer1.imagicle.mydomain.com</UdsServer> See for file upload Configuration file upload It is required to upload all the created Jabber configuration files into "CUCM TFTP File Management" and to restart CUCM TFTP service. Finally, it is needed to fill "Cisco Support Field" into CuCM Jabber Desktop/Mobile phone devices, for all Tenant-Customer's Users. See sample below In both the above cases, performing this configuration enables contacts separation directly in Jabber search tab (see picture below) Contacts Separation 5/ Not existing customized Cisco Jabber gadget xml configuration file

6 2.3 Speedy Gadget for Jabber Internal and External Contacts Separation configuration This configuration applies to Jabber, where it is also possible to configure a dedicated Speedy Gadget as a Custom Tab to enable advanced Directory search features, including access to Internal and External Contacts. It is required to apply a specific configuration to the Jabber configuration file(s) in order to enable Imagicle Speedy gadget and related advanced Directory services. The configuration is different in case a customized Cisco configuration file is already in place or not Existing customized Cisco Jabber gadget xml configuration file In case a customized Cisco configuration file is already in place, it is recommended to modify this file adding the XML code lines highlighted in the example jabber config file below; these lines should be contained in-between "client" statements. <client> <jabber-plugin-config> <browser-plugin> <page preload="false" refresh="false"> <tooltip>speedy</tooltip> <icon> <url> </page> </browser-plugin> </jabber-plugin-config> </client> Adding "&HideLocalContacts=0" enables also Internal Contacts search within Speedy Jabber Gadget Contacts Separation 6/ Not existing customized Cisco Jabber gadget xml configuration file

7 Finally, it is required to upload the created Jabber configuration file into "CUCM TFTP File Management" and to restart CUCM TFTP service. Finally, it is needed to fill "Cisco Support Field" into CuCM Jabber Desktop/Mobile phone devices, for all Tenant-Customer's Users. See sample below Not existing customized Cisco Jabber gadget xml configuration file In case no Jabber config file is in place, it is possible to create one containing the following lines. <client> <jabber-plugin-config> <browser-plugin> <page preload="false" refresh="false"> <tooltip>speedy</tooltip> <icon> <url> </page> </browser-plugin> </jabber-plugin-config> </client> Adding "&HideLocalContacts=0" enables also Internal Contacts search within Speedy Jabber Gadget Finally, it is required to upload the created Jabber configuration file into "CUCM TFTP File Management" and to restart CUCM TFTP service. Finally, it is needed to fill "Cisco Support Field" into CuCM Jabber Desktop/Mobile phone devices, for all Tenant-Customer's Users. See sample below. In both the above cases, performing this configuration enables Speedy Jabber gadget button (see picture below). Contacts Separation 7/ Not existing customized Cisco Jabber gadget xml configuration file

8 The following is an example with Speedy gadget and UDS configured <Client> <spell_check_enabled>true</spell_check_enabled> <jabber-plugin-config> <browser-plugin> <page refresh="false" preload="false"> <tooltip>speedy</tooltip> <icon> <url> </page> </browser-plugin> </jabber-plugin-config> </Client> <Options> <AllowUserCustomTabs>true</AllowUserCustomTabs> </Options> <BDIUseSIPURIToResolveContacts>true</BDIUseSIPURIToResolveContacts> <PhotoUriSubstitutionToken>sAMAccountName</PhotoUriSubstitutionToken> <UdsPhotoUriWithToken> <BDIUriPrefix>sip:</BDIUriPrefix> 2.4 XML-based Internal and External Contacts Separation configuration for IP Phones This configuration applies to devices which use XML protocol (i.e. IP phones), where it is possible to configure a dedicated Speedy Directory to enable advanced Directory search features, including access to external department and personal directories. It is required to create a new CuCM directory XML Phone Service or modify the existing one called "Corporate Directory". To do so, please follow the instructions at the following link: It is recommended to perform an Enterprise Subscription in order to enable directory access to all IP Phones. You also need to enable the Internal Contacts access via XML service following link: Contacts Separation 8/ Not existing customized Cisco Jabber gadget xml configuration file

9 2.5 MRA specific configuration In case of MRA scenario, besides the Expressway configurations described at the following link: it is required to apply below configuration to enable UDS access (port 8443). Create one editable inbound rule with the following parameters (Url must be set as configured in Jabber configuration files, system-wide jabber-config.xml and all the different jabber-config-customerx.xml) Contacts Separation 9/ Not existing customized Cisco Jabber gadget xml configuration file