1 Report Information

This configuration report contains the configuration objects for the IM and Presence cluster.

1.1 Report Generation

This configuration report for Cisco Unified CM IM and Presence cluster has the following details:

1.2 Presenter

1.3 Client

2 System

The System section contains the following items:

• Server
• Services
• Status
• Application Listeners
• Security
• Settings
• Incoming ACL
• Outgoing ACL
• TLS Context Configuration
• TLS Peer Subjects
• Service Parameters
• Enterprise Parameters

2.1 System - Server

The following IM and Presence servers are present in this cluster:

2.2 System - Status

The IM and Presence system status shows the Sync Information and System Information. The system status displays the IP address of the publisher server and when the sync occurred.

System Information displays the following read-only fields:

• Number of end users
• Number of phone devices
• Number of licensed IM and Presence end users
• Number of licensed Cisco Unified Personal Communicator end users
• Number of assigned Microsoft Office Communicator end users
• Number of end users associated with an inter-cluster peer

2.3 System - CUCM Publisher

The following Cisco Unified Communications Manager (CUCM) Publisher is configured. Data will be synchronized from the publisher to the IM and Presence Service cluster.

2.4 System - Services

The following services are present on this server:

2.5 System - Application Listeners

You can configure application listeners for the SIP proxy server, presence engine, and profile agent. The system binds each application listener to a specific address and port combination. If you choose TLS protocol, you must also choose a TLS context.

2.6 Security

The Security section contains the following items:

• Settings
• Incoming ACL
• Outgoing ACL
• TLS Context Configuration
• TLS Peer Subjects

2.6.1 Security - Settings

This section contains settings for secure modes of XMPP traffic, the preferred transport protocol for SIP intracluster traffic, and the domain name for the XMPP server-to-server certificate.

2.6.2 Security - Incoming ACL

The Access Control List (ACL) configure patterns that control which hosts and domains can access Cisco Unified Presence.

Configure an address which will be added to the SIP Proxy list of allowed incoming addresses. Note: any address added to this list will bypass digest authentication. By default, the behavior is to deny all incoming requests.

2.6.3 Security - Outgoing ACL

The Outgoing Access Control List (ACL) configures patterns that control which outgoing hosts and domains can have access to the network from Cisco Unified Presence.

Configure an address which will be added to the SIP Proxy list of allowed outgoing addresses. Note: any address added to this list will bypass digest authentication. By default, the behavior is to deny all outgoing requests.

2.6.4 Security - TLS Context Configuration

Each transport listener can have a single associated transport layer security (TLS) context, and each TLS context can have multiple ciphers and peer subjects.

TLS context configuration enables you to map ciphers and peer subjects to a transport listener.

2.6.5 Security - TLS Peer Subjects

TLS peer subject configuration enables you to create and modify peer subjects that you can associate with a transport listener.

2.7 System - Service Parameters

The following are the service parameters for particular services, per server:

Please note that only the common clusterwide parameters are listed as not all parameters can be retrieved.

2.8 System - Enterprise Parameters

Enterprise parameters provide default settings that apply to all devices and services in the same cluster. A cluster is a set of servers that share the same database. When you install a new server, it uses the enterprise parameters to set the initial values of its device defaults.

You cannot add or delete enterprise parameters, but you can update existing enterprise parameters.

3 Presence

The Presence section contains the following items:

• Settings
• Gateways
• Inter-Clustering
• Inter-Domain Federation
• SIP Federation
• XMPP Federation
• Routing
• Settings
• Static Routes
• Method Event-Routing
• Number Expansion
• Domains

3.1 Settings

The Presence > Settings section contains the following items:

• Standard Configuration
• Advanced Configuration

3.1.1 Presence - Standard Configuration

The following settings include global availability sharing capability for all clients that connect to IM and Presence.

3.1.2 Presence - Advanced Configuration

The Advanced Presence Settings include default domain and the IM address scheme. The IM address scheme has two options:

• UserID@[Default Domain]: each user's IM address matches the format UserID@Default_Domain
• Directory URI: each user's IM address matches their Cisco Unified Communications Manager Directory URI setting.

3.2 Presence - Gateways

The purpose of a presence gateway is to enable the transfer of presence status information from the configured gateway to the Presence Engine in IM and Presence. The following gateways are supported:

• Cisco Unified Communications Manager gateway: You can configure a Cisco Unified Communications Manager server as a presence gateway. The IM and Presence server sends SIP Subscribe messages to Cisco Unified Communications Manager over a SIP trunk (configured on Cisco Unified Communications Manager), which allows the IM and Presence server to receive presence information, for example, phone on/off hook status.
• Microsoft Exchange (Calendaring) gateway: You can configure a Microsoft Exchange server (for Microsoft Outlook) as a presence gateway. This allows the IM and Presence server to collect presence information (calendar/meeting status) on a per-user basis and incorporate it into the presence status of the user.

3.3 Presence - Inter-Clustering

You can associate one or more external IM and Presence clusters (peers), which enable you to route requests to user names and phone numbers on other IM and Presence clusters. You can transmit instant messages and presence status across multiple IM and Presence clusters.

3.4 Inter-Domain Federation

The Inter-Domain Federation section contains the following items:

• SIP Federation
• XMPP Federation

3.4.1 Inter-Domain Federation - SIP Federation

IM and Presence permits integration with a Microsoft OCS foreign domain for interdomain federation. This allows IM and Presence users in an enterprise domain to interact with users of Microsoft Office Communicator in a foreign domain.

3.4.2 XMPP Federation

The Extensible Messaging and Presence Protocol (XMPP) is the core protocol on Cisco Unified Presence. This interface provides instant messaging, availability and roster management services. The following objects are defined:

• Settings
• Default Policy
• Exception Policy

3.4.2.1 XMPP Federation - Settings

IM and Presence can be configured for inter-domain federation, that is to dynamically federate with IM and Presence, WebEx, IBM and any XMPP standards-compliant server.

3.4.2.2 XMPP Federation - Default Policy

IM and Presence Service allows you to specify a default policy to either allow or deny all federated traffic from/to all configured federated enterprises. However, you can provision exceptions to this default policy.

3.4.2.3 XMPP Federation - Exception Policy

These are the exceptions to the default XMPP Federation Policy

3.4.3 Email Federated Domains

Email domains associated with users in the IM and Presence Service deployment. If the IM and Presence Service is configured to use the email address when federating, then all local users are identified by their email address to federated contacts, rather than their IM address. However, if the Enable use of Email Address for Inter-domain Federation parameter is disabled (default setting), then users are identified by their IM address instead, and the email domains listed on this window are not used.

By default, email domains are managed by the system. The system-managed email domains list contains the email domains of all users configured on the system. You can use this window to add email domains in addition to those already managed by the system.

In addition to providing the list of email domains, this window also specifies whether each administrator-managed email domain was configured on the local cluster, peer cluster, or both. Likewise, it also specifies whether each system-managed email domain is in use on the local cluster, peer cluster, or both.

System-managed email domains, by their nature, cannot be edited because they are in use. However, a system-managed email domain automatically becomes an administrator-managed email domain if there are no longer users on the system with that email domain (for example, due to user deletion). You can edit or delete administrator-managed domains.

3.5 Routing

The Routing section contains the following items:

• Settings
• Static Routes
• Method Event-Routing
• Number Expansion

3.5.1 Routing - Settings

This section contains the proxy server settings for the IM and Presence server.

The Method/Event Routing Status parameter specifies whether the method/event routing module is enabled or disabled in the SIP proxy server.

The Preferred Proxy Listener parameter specifies which SIP proxy listener is considered the preferred listener. The list contains SIP proxy server listeners that you defined in the Transport Listeners window.

3.5.2 Routing - Static Routes

This section defines static routes that the SIP proxy server uses. A dynamic route represents a path through the network that automatically get calculated according to routing protocols and routing update messages. A static route represents a fixed path through the network that you explicitly configure. Static routes take precedence over dynamic routes.

3.5.3 Routing - Method Event-Routing

Method-based or event-based routing configure the SIP proxy server to route SIP messages on the basis of their content.

3.5.4 Routing - Number Expansion

Number expansion configuration allows you to provision patterns that expand an extension number to its full E.164 telephone number. You can also use number expansion to strip numbers. You may want to manipulate the telephone number to match global dialing patterns and to route SIP requests accordingly.

Number expansion requires no precedence so ordering is not required. Instead the SIP Proxy processes the rules from the most specific to the least specific.

3.6 Presence - Domains

By default, domains are managed by the system. The system-managed domains list contains the domains of all users configured on the system. It also specifies whether each system-managed presence domain is in use on the local cluster, peer cluster, or both.

The following domains are managed by the IM and Presence Service:

4 Messaging

The Messaging section contains the following items:

• Settings
• External Server Setup
• External Database
• Third-Party Compliance Server
• External File Servers
• File Transfer
• Compliance
• Group Chat and Persistent Chat
• Group Chat Alias Mapping
• Group Chat System Administrators

4.1 Messaging - Settings

The following settings apply to the global instant messaging (IM) sharing capability for all clients that connect to IM and Presence.

4.2 External Server Setup

The External Server Setup section contains the following items:

• External Database
• Third-Party Compliance Server

4.2.1 Messaging - External Databases

External databases are required for:

• To use persistent chat rooms, you must configure a unique external database instance per node.
• If you use an external database for persistent chat logging, consider the size of your database. Archiving all the messages in a chat room is optional, and will increase traffic on the node and consume space on the external database disk. In large deployments, disk space could be quickly consumed. Ensure that your database is large enough to handle the volume of information.

The following external databases are configured:

4.2.2 Messaging - Third Party Compliance Servers

To use the third-party compliance solution you must configure a third-party compliance server for each node in the cluster. IM and Presence passes all messages that are sent to or from any users associated with a node to the designated third-party compliance server for that node. The third-party compliance server applies any relevant policy or filtering to the message, and then passes the message back to IM and Presence. IM and Presence delivers the message to the recipient.

The following third-party compliance servers are configured:

4.2.3 Messaging - External File Servers

Settings for an External File Server on the IM and Presence Service, including the user credentials and the connection information for the External File Server

4.3 Compliance

A compliance server can be used to log and archive all instant messaging traffic. The IM and Presence Service administrator can select which IM, presence, or group chat events are passed to the compliance server(s), and which events are blocked. The events must be selected based on policy.

The IM and Presence IM compliance chapter includes:

• Compliance Settings
• Compliance Profiles
• Compliance Profiles Routing Priority

4.3.1 Compliance - Settings

The following options are available for Instant Message (IM) compliance:

• Not Configured: no compliance solution is used.
• Message Archiver: use built-in Message Archiver component on IM and Presence as the compliance solution and assign a preconfigured external database to one or more nodes.
• Third-Party Compliance Server: use a third-party server as the compliance option.

4.3.2 Compliance - Profiles

A compliance profile contains a set of Jabber Session Manager (JSM) and\or Text Conferencing (TC) events that you can use to monitor for compliance. You can create a compliance profile that consists of only JSM events, only TC events, or a combination of both JSM and TC events.

Within a compliance profile, JSM and TC events are configured which are logged to the compliance server. These events also decide what type of handling is performed by the compliance server, how IM and Presence Service handles error responses from the compliance server, and whether the IM and Presence Service node waits for a response from the compliance server before processing the event further.

4.3.3 Compliance - Routing Priority

Events that are configured in multiple profiles will be routed in the order as specified here.

Compliance Profiles listed by routing priority (top is highest priority):

4.4 Messaging - File Transfer

File Transfer and Managed File Transfer configurations. Assign an External Database and an External File Server on all nodes where Managed File Transfer is to be active. Install the Node Public Key onto each associated External File Server.

The Node Public Key will be invalidated if the node''s assignment is removed. A new Node Public Key will be generated if the node is reassigned.

The Cisco XCP File Transfer Manager service must be active on each node where Managed File Transfer is required.

4.5 Messaging - Group Chat and Persistent Chat

This section defines settings to manage the primary chat server alias associated with each node, and configure permanent chat rooms as opposed to temporary (ad-hoc) chat rooms.

4.6 Messaging - Group Chat Server Aliases

The following additional aliases to a chat server are configured:

4.7 Messaging - Group Chat System Administrators

Group chat system administrators can do the following:

• Configure a room
• Join a password-protected room without supplying the password
• Change a room's subject
• Join any room (including members-only rooms)
• Moderate a room
• Join a room when the maximum occupancy is reached
• Destroy a room
• Browse a room for the list of participants
• Query a room and its items
• Remain in a room if the room changes to be members-only, or if their affiliation changes to "none" in a members-only room
• Change the affiliation of other users in a room
• Invite other users to a members-only room (even when members invite is not allowed)

The following Group chat system administrators are configured:

5 Application

The Application section contains the following items:

• Legacy Client Settings
• Settings
• CCMCIP Profile
• Microsoft RCC
• Settings
• User Assignment
• Third-Party Clients
• Third-Party LDAP Servers
• Third-Party LDAP Search Settings
• Client Types

5.1 Application - Settings

The following lists then Cisco Unified Personal Communicator settings that apply to all Cisco Unified Personal Communicator users:

5.2 Application - CCMCIP Profile

The folllowing Cisco CallManager Cisco IP Phone (CCMCIP) profiles for Cisco Unified Personal Communicator are configured:

5.3 Microsoft RCC

The Microsoft RCC section contains the following items:

• Settings
• User Assignment

5.3.1 Microsoft RCC - Settings

This section lists the Computer Telephony Interface (CTI) gateway settings that apply to the CTI gateway. These settings enable call control via TAPI (TSP) to Cisco Unified Communications Manager (CUCM).

5.3.2 Microsoft RCC - User Assignment

IM and Presence can use the Desk Phone Control service. This is not a licensed service, rather, the assignment is needed to limit the users for performance reasons.

5.4 Third-Party Clients

The Third-Party Clients section contains the following items:

• Third-Party LDAP Servers
• Third-Party LDAP Search Settings

5.4.1 Third-Party Clients - LDAP Servers

Third-Party XMPP clients may wish to provide LDAP based contact search. You can provision LDAP servers on IM and Presence to support LDAP based contact search by third party XMPP clients.

The following LDAP servers to support LDAP based contact search are configured:

5.4.2 Third-Party Clients - LDAP Settings

You must specify the LDAP search settings that will allow IM and Presence to successfully perform contact search for third party XMPP clients.

This references an LDAP server for third-party XMPP client search.

5.5 Application - Client Type

The IM and Presence service includes a default set of Cisco Unified Communications and third-party client types supported by the client configuration SOAP interface. You should only add a new client type if instructed to do so by a client application. Otherwise, new client types are unsupported and will be removed when you next upgrade IM and Presence.

Enable 'Version Check Required' to verify that users have the minimum version of the software clients installed. If users do not have the minimum version indicated, they will not be able to sign on

The following lists configured Client types: