Chat Deployments
You can set up chat for different deployment scenarios. Sample deployment scenarios are available.
Chat Deployment Scenario 1
Deployment Scenario: |
You do not want to include the Cluster ID in the chat node alias. Instead of the system-generated alias conference-1-mycup.cisco.com, you want to use the alias primary-conf-server.cisco.com. |
Configuration Steps: |
|
Notes: |
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. |
Chat Deployment Scenario 2
Deployment Scenario: |
You want to:
|
Configuration Steps: |
|
Notes: |
When you change the domain, the fully qualified cluster name (FQDN) automatically changes from conference-1-mycup.cisco.com to conference-1-mycup.linksys.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. |
Chat Deployment Scenario 3
Deployment Scenario: |
You:
|
Configuration Steps: |
|
Notes: |
When you change the Cluster ID, the fully qualified cluster name (FQDN) 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. |
Chat Deployment Scenario 4
Deployment Scenario: |
You want to:
|
Configuration Steps: |
Option 1
Option 2
|
Notes: |
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
Option 2
|