Yo must download the entire software package which includes the android OS and the Avaya APPs, to upgrade you need a separate http server due to the size of files.
After that you can provide a device factory default to be sure it gets all the IP Office paramenters and then config the Apps.
Device configuration
Updated on Oct 15 2019
The following list shows the methods you can use to configure Avaya Vantage™. The methods are listed in order of precedence, from the lowest to highest priority:
LLDP. This is the lowest priority.
DHCP. This includes the following options:
Standard
Option 43
Option 242
46xxsettings.txt file.
Settings menu on the device. This is the highest priority.
Note:
The installation wizard on Avaya Vantage™ K165 and K175 devices and Device Enrollment Services have the same priority as the Settings menu.
In the BroadSoft environment, you can perform device-specific configuration on the BroadWorks server if Device Management is configured.
Most parameters are configurable through multiple methods. When Avaya Vantage™ receives a new parameter value, it checks precedence rules to determine whether the new value must be applied. Avaya Vantage™ changes the parameter value only if the precedence level of the new value source is higher than the precedence level of the current value source. If a source precedence level is not defined for a parameter, Avaya Vantage™ does not use the parameter values provided by that source.
For parameter descriptions, see “Appendix A: Supported configuration parameters”.
Configuration verification
To verify configuration and ensure that the device is ready to use, see Verifying device configuration.
Tap Settings > Debugging options > Configuration verifier.
On the Configuration verifier screen, ensure that the status of the following validations are PASS:
Network Status: Validates whether the IP address is defined and the device is connected to the network.
DNS Status: Validates whether a DNS server is configured and reachable.
Date & Time Status: Validates whether an SNTP server is configured and reachable to synchronize the device clock.
File Server Status: Validates whether the file server address is received from a configuration source and the file server is reachable.
SIP Settings Status: Validates whether the SIP domain and SIP controllers are configured.
Note:
SIP Settings Status does not validate SIP registration for the Avaya IX™ Client SDK telephony application.
Phone Application Status: Validates whether a telephony application is defined as the active application and installed successfully. You can install Avaya Vantage™ Connect as the active Avaya telephony application.
Administrator Password Status: Validates whether the administrator password is configured correctly. You can use the administrator password to access administrator options in the Settings menu on Avaya Vantage™.
FIPS Mode Status: Indicates whether the device has passed the FIPS self test for Avaya cryptography library when FIPS mode is enabled. If the device currently supports FIPS, the detailed status displays whether any non-compliant services are running on the device. The detailed status also indicates if any identity certificate was installed on the device before FIPS mode is enabled.
The Configuration verifier screen only displays this status if FIPS mode is enabled for your setup.
Camera Status: Validates whether the camera for the device is enabled.
To see the details for one of the configuration items, tap the appropriate item.
The configuration verifier displays the configuration details and status. If the status is NOTICE or FAIL, the verifier displays the possible reasons for the configuration failure. Sometimes the configuration might be correct, but verification might fail because of network connectivity issues.
If any required configuration is missing or incorrect, modify the appropriate configuration parameter definitions.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.