Please enable JavaScript to view this site.

UC Module

> Module Installation

Igniting the Module Services

Scroll Prev Up Next More

Following software installation, the module requires ignition. For a Unified Communications Module v2 this is indicated by the message "Idle, card has not been ignited" and the lower LED green.

To ignite the module services:

1.From a client PC, start the browser. Enter https:// followed by the LAN1 IP address of the IP Office system and :7071. For example, enter https://192.168.42.1:7071.

2.The login menu appears:

a.Note the release number shown after the R in the menu title. If this does not match the software release of the IP Office system, stop ignition and install the appropriate Unified Communications Module release to match the system.

b.Enter the default password (Administrator).

c.Click Login. If you accept the license, select I Agree and click Next.

3.Enter the IP address and DNS settings that the module should use. Enter details that give the module an IP address on the same subnet as the LAN1 interface of the IP Office system.
c110_ignite_03

4.Select the services that you want the module to provide for the IP Office system.
c110_ignite_04

5.Click Next. Enter and confirm new passwords. These are the passwords for various Management Services service user accounts and also for the Linux accounts created on the server. Ensure that you note the passwords set.
c110_ignite_05

The passwords must be 8 to 32 characters, containing at least two types of character (lower case, upper case, numeric and special characters) and no more the 3 consecutive characters.

root/security password
This sets the password for both the Linux root user account and also the security account of the Management Services service.

Administrator password
This sets the password for Linux Administrator account and also the Administrator account of the Management Services service run on the Unified Communications Module. With Referred Authentication enabled (the default) this is also the default account used for Voicemail Pro and one-X Portal for IP Office administrator access.

System password
This sets the System password for the Management Services.

6.Click Next. Enter basic details for the module.
c110_ignite_06

Hostname
This value is used as the DNS host name of the server.

For internal use, this value must be reachable by DNS within the customer network. If also supporting external client connections, it needs to be reachable by external DNS. Consult with the customer's IT support to ensure the name is acceptable and that routing to it has been configured correctly. External access must also include a firewall and/or SBC.

Use NTP/NTP Server
Do not change the settings. The default 169.254.0.1.setting is an internal address for the module to get its time its host system.

7.Click Next. The menu prompts which security certificate the server should use.
c110_ignite_07

If you select Generate CA automatically, you must download the certificate from the next screen.

If you select Import CA, click Browse and locate the security certificate file that the server should use. Click Upload.

8.Select whether you want the server to be supported by Avaya through their EASG service. Click Next.

9.Click Next. A summary of the settings appears.
c110_ignite_08

10.If Generate New was selected for the server's security certificate, download the security certificate files from the menu and store these safely. These certificates need to be used by the browser and other applications for future access to the server.

11.Click Apply. Click OK when displayed to access the server's IP Office Web Manager menus. Note that this can take up to 10 minutes.

12.Follow the instructions for adding a certificate to your browser.

 

 

Performance figures, data and operation quoted in this document are typical and must be specifically confirmed in writing by Avaya before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments at its own discretion. The publication of information in this document does not imply freedom from patent or any other protective rights of Avaya or others. All trademarks identified by ™, ® or © are registered trademarks or trademarks respectively are the property of their respective owners.

© 2022 Avaya
Issue 16.d.-
Thursday, February 17, 2022