Manage Chat Overview
IM and Presence Service provides you with settings you can use to manage your chat rooms and to control who has access to them. This includes the ability to:
Create new rooms, manage members and the configurations of the rooms they create.
Control access to persistent chat rooms so that only members of that room have access.
Assign Administrators to a chat room.
Invite other users to a room.
Determine the presence status of the members displayed within the room. The presence status displayed in a room confirms the attendance of the member in a room but may not reflect their overall presence status.
IM and Presence Service also lets you manage chat node aliases. Chat node aliases make it possible for your users to search for specific chat rooms on specific nodes, and to join those chat rooms.
In addition, the IM and Presence Service also stores transcripts and makes this chat room history available to room members, including members who have just joined the chat room. You can configure how much of the existing archive you want to make available to new and old members. .
Chat Node Alias Overview
Each chat node in a system must have a unique alias. Chat node aliases are unique addresses for each chat node so that users
(in any domain) can search for specific chat rooms on specific nodes, and join chat in those rooms. Chat node aliases form
a part of the unique ID for each chat room that is created on that node. For example, the alias
conference-3-mycup.cisco.com gets used to name the chat room
firstname.lastname@example.org that is created on that node.
There are two modes for assigning chat node aliases:
System-generated—The system automatically assigns a unique alias to each chat node. By default, the system auto-generates one alias per chat node by using the following naming convention:
conferenceis a hardcoded keyword
xis the unique integer value that denotes the node ID
clusteridis the configured enterprise parameter
domainis the configured domain
For example, the system might assign:
Manual—You must disable system-generated aliases to be able to assign chat node aliases manually. With manually-assigned aliases, you have complete flexibility to name chat nodes using aliases that suit your specific requirements. For example, you might do this if the
congerence-x-clusterid.domainnaming convention does not suit your deployment needs.
Assigning Multiple Aliases per Node
You can associate more than one alias with each chat node on a per-node basis. Multiple aliases per node allows users to create additional chat rooms using these aliases. This functionality applies to both system-generated aliases and aliases that are created manually.