- Introduction
- Points to remember
- Common Issues
- 1. How to Modify the Cluster ID
- 2. How to change the Domain
- 3. How to change the Cluster ID and do not maintain the address
- 4. How to change the Cluster ID and maintain chatroom addressing via old alias
- 5. How to delete a node
- Related Links
Introduction
This document explains "How to modify chat alias in CUPS 8.x ?"
Aliases create a unique address 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. Each chat node in a system must have a unique alias.
You can assign your aliases cluster-wide, in these ways:-
- System-generated — allows the system to automatically assign a unique alias to each chat node.You do not have do to anything further to address your chat node if you enable the system-generated aliases. The system will auto-generate one alias per chat node by default using the following naming convention: conference-x-clusterid.domain, where:
- conference - is a hardcoded keyword
- x- is the unique integer value that denotes the node ID.Example: conference-3-mycup.cisco.com
- Manually — You may choose to override the default system-generated alias if the conference-x-clusterid.domain naming convention does not suit your customer deployment, for example, if you do not want to include the Cluster ID in your chat node alias. With manually-managed aliases, you have complete flexibility to name chat nodes using aliases that suit your specific requirements.
Additional Aliases
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 applies whether you assign a system-generated alias or manage your aliases manually.
Note:-
Changing chat node aliases can make the chat rooms in the database unaddressable and prevent your users from finding existing chat rooms.
Before you change the constituent parts of aliases or other node dependencies note down the following :-
- Cluster ID - This value is part of the fully qualified cluster name (FQCN). Changing the Cluster ID (select System > Cluster Topology: Settings) causes the FQCN to incorporate the new value and the system-managed alias to automatically change across the cluster. For manually-managed aliases, it is the responsibility of the Administrator to manually update the alias list if the Cluster ID changes
- Domain - This value is part of the FQCN. Changing the Domain (select System > Service Parameters > Cisco UP Proxy) causes the FQCN to incorporate the new value and the system-managed alias to automatically change across the cluster. For manually-managed aliases, it is the responsibility of the Administrator to manually update the alias list if the Domain changes.
- Connection between the chat node and external database - The chat node will not start if persistent chat is enabled and you do not maintain the correct connection with the external database.
- Deletion of a chat node - If you delete a node associated with an existing alias from the Cluster Topology, chat rooms created using the old alias may not be addressable unless you take further action.
We recommend that you do not change existing aliases without considering the wider implications of your changes, namely:
•
Make sure that you maintain the address of old chat nodes in the database so that users can locate existing chat rooms via the old alias, if required
•If there is federation with external domains, you may need to publish the aliases in DNS to inform the users in those domains that the aliases have changed and new addresses are available. This depends on whether or not you want to advertise all aliases externally.
Points to remember
- Every chat node alias must be unique. The system will prevent you from creating duplicate chat node aliases across the cluster.
- A chat node alias name cannot match the Cisco Unified Presence domain name.
- Delete old aliases only if you no longer need to maintain the address of chat rooms via the old alias.
- If you are federating with external domains, you may want to inform federated parties that the aliases have changed and new aliases are available.
- To advertise all aliases externally, configure DNS and publish the aliases as DNS records.
- Even if you configure a system-generated alias for a chat node, you can associate more than one alias with the node if required.
- If you are federating with external domains, you may want to inform federated parties that the aliases have changed and new aliases are available. To advertise all aliases externally, configure DNS and publish the aliases as DNS records.
- If users of clients applications create a chat room, they may potentially override the default number of messages that display in a chat room.
- Note that if you turn on the Archive all room messages option for persistent chat, Cisco Unified Personal Communicator actively queries Cisco Unified Presence for all instant message history regardless of the value you configure for the Number of messages in chat history displayed for
new chat participants setting.
- If you update any of the system-generated alias configuration, perform one of these actions:
- If you are running Cisco Unified Presence Release 8.0(x), restart the Cisco UP XCP Router.Select Cisco Unified Serviceability > Tools > Control Center - Network Services to restart this service.
- If you are running Cisco Unified Presence Release 8.5(x) or later, restart the Cisco UP XCP Text Conference Manager. Select Cisco Unified Serviceability > Tools > Control Center - Feature Services to restart this service.
- If you are running Cisco Unified Presence Release 8.5(x) or later, the Number of messages in chat history displayed for new chat participants setting updates dynamically; You do not need to restart the Cisco UP XCP Text Conference Manager.
- If you update any of the chat node alias configuration, perform one of these actions:
- If you are running Cisco Unified Presence Release 8.0(x), restart the Cisco UP XCP Router.
- If you are running Cisco Unified Presence Release 8.5(x), restart the Cisco UP XCP Text Conference Manager
Common Issues
1. How to Modify the Cluster ID
If you do not want to include the Cluster ID in the chat node alias and instead of the system-generated alias conference-1-mycup.cisco.com , you want to use the alias primary-conf-server.cisco.com follow the below mentioned points:-
Steps:-
1. Select Messaging > Enterprise Instant Messaging to turn off the system-generated alias. (This is on by default).
2. Edit the alias and change it to primary-conf-server.cisco.com.
When you turn off the old system-generated alias,conference-1-mycup.cisco.com reverts to a standard, editable alias listed under Group Chat Server Aliases. This maintains the old alias and the chat room addresses associated with that alias.
2. How to change the Domain
If you want to:
•change the Domain from cisco.com to abc.com and use conference-1-mycup.abc.com instead of conference-1-mycup.cisco.com.
•maintain the address of existing persistent chat rooms in the database so that users can still find old chat rooms of type xxx@conference-1-mycup.cisco.com.
Steps:-
1. Select System > Service Parameters > Cisco UP Proxy in Cisco Unified Presence Administration.
2. Edit the Domain and change it to abc.com.
When you change the domain, the fully qualified cluster name (FQCN) automatically changes from conference-1-mycup.cisco.com
to conference-1-mycup.abc.com.
The old system-generated alias conference-1-mycup.cisco.com reverts to a standard, editable alias listed under Group Chat Server Aliases. This maintains the old alias and the chat room addresses associated with that alias.
3. How to change the Cluster ID and do not maintain the address
If you :
•want to change the Cluster ID from mycup to ireland to use conference-1-ireland.cisco.com instead of conference-1-mycup.cisco.com.
•do not need to maintain the address of existing persistent chat rooms in the database.
Steps:-
1. Select Presence > Settings in Cisco Unified Presence Administration.
2. Edit the Cluster ID and change it to ireland.
3. Select Messaging > Conferencing Server Alias Mapping in Cisco Unified Presence Administration.
4. Delete the old alias conference-1-mycup.cisco.com.
When you change the Cluster ID, the fully qualified cluster name (FQCN) automatically changes from conference-1-mycup.cisco.com to conference-1-ireland.cisco.com.
The old system-generated alias conference-1-mycup.cisco.com reverts to a standard, editable alias listed under Group Chat Server Aliases. This maintains the old alias and the chat room addresses associated with that alias. Because (in this example) the Administrator has no need to maintain the old alias address, it is appropriate to delete it.
4. How to change the Cluster ID and maintain chatroom addressing via old alias
If you want to:
•change the Cluster ID from mycup to ireland to use conference-1-ireland.cisco.com instead of conference-1-mycup.cisco.com.
•only maintain chat room addressing via the old alias (does not need to associate nodes with the new system-generated alias).
Steps:-
1. Select Presence > Settings in Cisco Unified Presence Administration.
2. Edit the Cluster ID and changes it to ireland.
3. Select Messaging > Enterprise Instant Messaging and turn off the new system-generated alias,conference-1-ireland.cisco.com. (This is on by default).
4.Select Messaging > Conferencing Server Alias Mapping in Cisco Unified Presence Administration
5. Deletes the new alias conference-1-ireland.cisco.com.
When you change the Cluster ID, the fully qualified cluster name (FQCN) automatically changes from conference-1-mycup.cisco.com to conference-1-ireland.cisco.com.
When you turn off the new system-generated alias,conference-1-ireland.cisco.com reverts to a standard, editable alias listed under Group Chat Server Aliases. Because (in this example) the Administrator has no need to maintain the new alias address, it is appropriate to delete it. The old system-generated alias conference-1-mycup.cisco.com reverts to a standard, editable alias listed under Group Chat Server Aliases. This maintains the old alias and the chat room addresses associated with that alias.
5. How to delete a node
If you want to:
•delete a node associated with an existing alias from the System Topology, for example,conference-3-mycup.cisco.com.
•add a new node with a new node ID (node id: 7) to the System Topology, for example,conference-7-mycup.cisco.com.
•maintain the address of chat rooms that were created using the old alias.
Option 1
1. Select Messaging > Conferencing Server Alias Mapping in Cisco Unified Presence Administration.
2. Select Add New to add the additional alias, conference-3-mycup.cisco.com.
Option 2
1. Select Messaging > Enterprise Instant Messaging and turn off the default system-generated alias,conference-7-mycup.cisco.com. (This is on by default).
2. Edit the alias and change it to conference-3-mycup.cisco.com.
When you add the new node to the System Topology, the system automatically assigns this alias to the node:conference-7-mycup.cisco.com.
Option 1
•If you add an additional alias, the node is addressable via both aliases, conference-7-mycup.cisco.comand conference-3-mycup.cisco.com.
Option 2
•If you turn off the old system-generated alias, conference-7-mycup.cisco.com reverts to a standard, editable alias listed under Group Chat Server Aliases.