Rel 7.5 Installation Summary

CPPM Co Res Call server

The following summary describes the steps to build a CoRes Call server and assumes that the system built is the Primary UCM server. Remember the following when you use this:-

• If you are building more than one server only the Primary needs the .NAI file adding to it.
• All Pre-Deployment and Deployment should be done from the Primary UCM
• You need to ensure you either have a DNS in place or edit your Hosts file on your PC to use the FQDN's of the servers.
• If you have multiple Call servers under one UCM you will need to run the REG UCM SYS command on each to ensure that the CS and Media gateways are registered to the UCM correctly.
• Some of the differences when deploying a SA or HA call server are listed at the end of this document.

Install Steps

1. Create the installation compact flash card or USB stick dependent on the cards being used (CPPM Compact Flash, CPMG/CPDC USB). Optionally add the .NAI file for software deployment to the installer device, which should be a minimum of 2Gb but preferably 4Gb.
2. Prepare the card for CoRes operation
   1. CPMG & CPDC have 250 Gb Hard Drive and 2Gb memory so only Dongle required.
   2. CPPM Card requires 2Gb Ram - 40Gb Hard Drive - Switch 5 set to 2 and a Dongle.
   3. Older CPPM cards may require the following:-
      1. Reset the CMOS on the card to Factory Defaults
      2. Using a VXWORKS installation compact Flash install BIOS upgrade to card
         1. Boot from CF
         2. Go to Tools Menu
         3. Select BIOS upgrade option and install lmdu74aa_0018
3. Insert the Linux Installer CF or USB and boot the system
   1. On CPPM cards press F when prompted. If there is an existing system on the card you will be prompted again so press F again to boot from Faceplate.
   2. On CPMG & CPDC press F to go to BOOT manager (watch bottom of initial screen). At the Boot Manager use Arrow keys to select USB and press enter.
4. When the installer displays a list of BOOT options (COM1/COM1-NFS etc) press return at the BOOT: prompt to configure the installation via the COM port. Be patient.
5. The install programme will then guide you through adding the IP addresses, Hostname, Domain, time zone etc. CHECK THE TIME IS CORRECT ON THE SYSTEM.
6. You will also be prompted for the passwords for the accounts 'root' and 'admin2' which need to be complex (suggestion CS1000+r6).
7. The Final questions will ask if the server is to be a DEPLOYMENT server, answer yes if this is the case and yes to the following question to confirm the server will be the primary UCM. The install will then proceed - be patient.
8. When the system completes installation and reboots, login at the Linux prompt to check both accounts are working correctly.
9. Browse in internet Explorer to the TLAN address of the system e.g. HTTP://10.5.10.12 , or the FQDN if you have a DNS. This should bring up a login page for the UCM, ignore any certificate errors at this point and continue.
10. Login using the 'admin2' account where you will be offered the options of Security Configuration or Local Administration. If you need to add other Hosts (for name resolution if you don't have a DNS) or check/set the time select Local administration. If you use the Local Administration option you will need to log out and log back in again before continuing.
11. Select Security Configuration, check the FQDN is correct and click next. Select which Security server type you require (One Primary, one Backup, multiple Members. Primary for a standalone system).You are then prompted for the UCM 'admin' account password (suggestion Avaya_123), this is the built-in Network Administrator account. Click Next
12. You are now prompted to add the Certificate information for the system. Complete the form leaving the Common Name as it is,(Don't use odd characters such as '&+-' as they can cause problem on the Certificate) and submit. When the completed screen is displayed click the Restart button and wait 10 minutes before trying to login again.
13. If you are not using a DNS entry for the system edit the 'Hosts' file on your PC (windows/system32/drivers/etc ) to contain an entry to link the FQDN to TLAN address e.g. 10.5.10.32 sys3.gktrain.com. On Windows 7 and Vista you will need to open NOTEPAD as an Administrator (Use a Right hand Mouse click) before editing the file or you won't be able to save it back in the right folder.
14. Next click on the CERTIFICATES menu option under SECURITY. In the CERTIFICATE ENDPOINTS tab use the radio button to select the endpoint and then click on WEB SSL in the Endpoints Detail area. This will offer you a dialogue with several certificate options. Choose ASSIGN AN EXISTING CERTIFICATE and assign the certificate offered. This is the one created when you did the Security Configuration.
15. Now click on the PRIVATE CERTIFICATE AUTHORITY tab and use the DOWNLOAD button to save the certificate to your PC. Leaving your web browser locate the downloaded certificate and double click it to install it on your PC. Make sure you save the certificate into the TRUSTED ROOT CERTIFICATION AUTHORITIES store. This will stop any further certificate errors being flagged up. Remember to avoid the Certificate error messages always connect using the FQDN not the IP address.
16. Access the Patch manager on the UCM or Base manager and apply any Linux Service Updates e.g. LINUXBASE/BASEWEB/PATCHWEB.
17. Return to the UCM browser window and now select SOFTWARE DEPLOYMENT under CS 1000 SERVICES. If this is the first access the system will request the account to be used for Deployment. Enter the 'admin' username and password.
18. You should now have the Deployment Targets window. However we need to add a software load before we can deploy applications to the server so select the SOFTWARE LOADS menu option.
19. Select the Location (Client or Deployment server) for the '.NAI' file and use the BROWSE button to select the file from your Client PC or the Install Media on the Deployment server. Use the ADD LOAD button to add it to copy the file to the server. Be patient. When the load has been added return to the DEPLOYMENT TARGETS screen.
20. To deploy the call server select CS1000 SYSTEMS from the VIEW menu on the right hand side of the screen.
21. From the left hand menu select CS1000 from the drop down list and click the ADD button.
22. You will now be asked for the name for the call server and a description and to select the Linux server that the Call Server will be deployed on and the system TAPE ID (Dongle).
23. As you are deploying a Call Server you will be prompted for a Keycode which can be selected from either the DEPLOYMENT SERVER or the CLIENT PC. Once selected click the VALIDATE button to check it. Next select the Languages and select which database to use then click next.
24. On the following screen select the Linux server to be used as the primary Element Manager and if available the alternative Element Manager. On the lower part of the screen you must select the Linux server(s) to use as the Signalling Server from the Drop down menu and click the ADD button to enter them into the list. When complete click the FINISH button.
25. Switch the VIEW to NETWORK SERVICES and select from the drop down list on the left the option to add e.g. NRS or Subscriber Manager and click the ADD button to define the service. Subsequent screens will request the name and Linux server to be used to host the service. (NOTE:- When adding the NRS you will be asked for both the Primary and Alternate servers).
26. When all services have been added, return to the SERVERS list using the VIEWS menu, check the configurations created and then use the COMMIT button (Bottom right) to complete the Pre-Deployment.
27. Finally select the server to deploy using the radio button alongside it and then select the DEPLOY option from the DEPLOYMENT ACTIONS drop down menu to initiate the process.
28. When the deployment completes the system is ready to login to.
29. Access the Patch manager on the UCM or Base manager and apply any Service Updates or Service Packs.
30. Once the Service packs are applied and activated you can configure the system as normal. You may need extra PTY's on a CoRes system. To access the Call server on a CoRes system use 'csconsole' on the Linux command line (<CTRL>ad to return to Linux).
31. When you have created the Media Gateways you need to add them into the Security Domain, otherwise they will not register correctly to the Call Server. To do this, use REG UCM SYSTEM/DEVICE in LD 117.
32. If REG UCM fails then you may need to login directly to each Media Gateway using <CTRL> oam (Remember to use the 'admin2/0000' login as the MGC/MGS is still outside the UCM domain. From the command line issue the command 'joinSecDomain' and follow the prompts to register the device to the UCM.
33. Once you have run REG UCM SYSTEM and all the devices have been added to the Security Domain you will only be able to login using the admin account or another UCM based account. admin1 & admin2 will no longer work unless the call server is removed from the Security Domain.
34. In Element Manager you will need to 'Save & Transfer' the IP Node (you may also need to create it or change the server used as the Signalling Server depending on the upgrade).This is now known as SYNCHRONIZE. When you open the Node it will have a STATUS in the far right column probably SYNCHRONIZED (Even though it isn't at this point). Click on this link.
35. This will open the SYNCRONIZE page. Select the Node (Check box) and click the START SYNC button.
36. When the Node is SYNCRONIZED, as this is the first time the Sig Server has received the configuration you will need to RESTART APPLICATIONS. Select the Node and click the RESTART APPLICATIONS button.
37. Remember to EDD the Call Server. Where the database has been converted (Small system to Large) you will need to do an EDD CLR on the first backup.

Differences when building an SA or HA system

1. The VxWorks Call Servers are installed or upgraded before the Deployment is carried out.
2. In the Deployment Manager you must first ADD a VxWORKS server to the configuration and define if it is HA or not and add the ELAN IP address(es) of the Call Server (i.e. Active and Inactive IP).
3. In the Pre-Deployment phase the select the VxWORKS server as the Call server when configuring the CS1000 System.
4. Ensure you have run the REG UCM SYS command before attempting to synchronise the IP telephony node as the security will need to be in place before the Node information will copy correctly from the Call Server to the Signalling servers.

---