Your changes will require approval by an administrator before they are published.
The article has been updated successfully but requires approval before it is published.Softswitch upgrade procedures to 6.7.0.205
Standard Upgrade procedures with full shutdown of all servers:1. If you have a redundant server, restart the inactive/secondary server, if not, proceed to step 2.
After the server has been restarted, check Replication Status in Redundancy Administration dialog. The status should show “Updated” on both primary and secondary servers before proceeding to the next step.
2. From the Primary softswitch server, go to Start-> Programs->MaxCommunication Server ACC/ACM->Utilties->ACC/ACM Backup and Restore. Make sure to backup to a network drive or a USB drive.
3. Once the backup is done, detach all the gateway and HMCP servers from the softswitch one by one, making sure that each server is detached before detaching the next. The Application server does not need to be detached or disconnected.
4. If you have redundancy, turn off the "Automatically assume control when active system is not available" feature on the
secondary softswitch.
5. Shut down services on ALL servers. This includes both the Primary and Secondary servers, Gateway servers, HMCP and Application server, if applicable.
6. Then follow standard upgrade procedures. Apply 6.7.0.105 to all servers, reboot, stop services then apply 6.7.0.205.
7. Once all services have been started on all servers, you may attach all the gateways on the primary.
8. If you have redundancy, turn on the "Automatically assume control when active system is not available" feature on the
secondary softswitch.
Procedures for upgrading a redundancy softswitch while running on secondary server
(This will allow users to still be able to make minimal calls)
1. Restart the inactive/secondary server. After the server has been restarted, check Replication Status in Redundancy Administration dialog. The status should show “Updated” on both primary and secondary servers before proceeding to the next step.
2. From the Primary softswitch serve r, go to Start-> Programs->MaxCommunication Server ACC/ACM->Utilties->ACC/ACM Backup and Restore. Make sure to backup to a network drive or a USB drive.
3. Once the backup is done, turn off the "Automatically assume control when active system is not available" feature on the
secondary softswitch.
turn off the "Automatically assume control when active system is not available" feature on the
secondary softswitch.
4. On the Primary server, go to System->Redundancy and click on the "Status" button. Confirm that the Primary server is the Active system, the server is in control, switching is up and the replication status says, "Updated" Then click on the "Manual Switch Over" button. This should now change the Active system to the secondary server. Make sure the Secondary server is now in control, the switching is up and the replication status is updated. Please wait 2-3 minutes for the switch over to occur.
5. Log onto the Secondary server and confirm that the switch over is complete and make a few test calls. Start by detaching all gateways and HMCP servers from the softswitch one by one, making sure that each server is detached before detaching the next. The Application server does not need to be detached or disconnected. Leave one gateway attached, preferably the gateway with some analog trunks or PRI. Enough for users to make some calls if needed.
6. Now the Primary server is ready to be upgraded.
5. Shut down AltiGen services on ALL servers. This includes both the Primary server, Gateway servers, HMCP and Application server, if applicable.
6. Then follow standard upgrade procedures. Apply 6.7.0.105 to all servers, reboot, stop services then apply 6.7.0.205.
7. Once all services have been started on all servers, manually switch back to the Primary server from the secondary. Verify that the Primary server is now in control, the switching is up and the replication status is updated. Please wait 2-3 minutes for the switch over to occur. Then detach the remaining gateway on the primary.
8. Stop the AltiGen services on the remaining gateway and follow standard upgrading procedures. Then attach the gateway on the primary.
9. Then proceed to stop the services on the secondary and follow upgrade procedures. Once the server is back up, turn on the "Automatically assume control when active system is not available" feature on the secondary softswitch.
Attachments
No attachments were found.Related Articles
- MAXCS 7.5 Upgrade Guide
- Redundant SoftSwitch reboot procedure
- MaxCS Softswitch SaaS Datasheet
- MaxCS 7.5 All-software Solution Deployment Guide
- General Upgrade Procedures
