| Key: |
XCF-1068
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Walter Gillett
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
sipXconfig
Created: 2006-06-06 22:58
Updated: 2008-10-09 13:25
|
|
| Component/s: |
HA
|
| Affects Version/s: |
None
|
| Fix Version/s: |
3.11.7
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Issue Links:
|
Related
|
|
|
|
This issue related to:
|
|
XCF-2133
Cluster Management: Allow sipXconfig ...
|
|
|
|
|
|
|
The "primary server" is the one running sipXconfig. A "secondary server" is any other server in the cluster. Adding a secondary server involves altering topology.xml on the primary server to list the new server as well as updating config files on the new server.
See the HA setup guide for HA-specific work. The HA-specific part is configuring HA synchronization between all registrar instances.
|
|
Description
|
The "primary server" is the one running sipXconfig. A "secondary server" is any other server in the cluster. Adding a secondary server involves altering topology.xml on the primary server to list the new server as well as updating config files on the new server.
See the HA setup guide for HA-specific work. The HA-specific part is configuring HA synchronization between all registrar instances. |
Show » |
|
Add secondary server to cluster