IPADD

String

0.0.0.0

Specifies the IP address of the Avaya Vantage™ device. The range is from 7 to 15 ASCII characters. This is a testable parameter.

The parameter can be used in conditional statements in the 46xxsettings.txt file.

NETMASK

String

0.0.0.0

Specifies an IP subnet mask.

This parameter specifies one IP address in the dotted decimal format. The range is from 7 to 15 ASCII characters.

SUBNET

String

0.0.0.0

Specifies the subnet of the telephone. A value of SUBNET is a value of a bitwise AND operation performed on values of IPADD and NETMASK.

You can only use this parameter in conditional statements in the 46xxsettings.txt file.

Example:

IF $SUBNET SEQ 135.11.193.0 GOTO SUBNET193
GOTO OTHER_SUBNETS
# SUBNET193
##<here is where we set parameters for devices on subnet 193>
SET <para_name> <value1>

GOTO SOFTWARE_FILES
# OTHER_SUBNETS
SET <para_name> <value2>

DHCPSTD

Integer

0

Specifies the DHCP lease violation flag. Assign one of the following values:

• 1: To comply with the DHCP standard. When the DHCP lease expires, Avaya Vantage™ immediately releases an IP address.

• 0: To enter the proprietary state. When the DHCP lease expires, Avaya Vantage™ continues to use the IP address.

For provisioning, use the SET command in the 46xxsettings.txt file.

ICMPDU

Integer

1

Specifies whether Avaya Vantage™ generates Internet Control Message Protocol (ICMP) Destination Unreachable (DU) messages to inform the source host that a port is unreachable. Assign one of the following values:

• 0: DU messages are not transmitted.

• 1: For Avaya Vantage™, the behavior for the value 1 is same as 0.

• 2: DU messages are transmitted.

ICMPRED

Integer

0

Specifies whether Avaya Vantage™ processes ICMP redirect messages. Assign one of the following values:

• 0: Avaya Vantage™ does not process received redirect messages.

• 1: Avaya Vantage™ processes received redirect messages according to RFC 1122.

MTU_SIZE

Integer

1500

Specifies the Maximum Transmission Unit (MTU) size. Assign one of the following values:

• 1496

• 1500

This parameter is applicable for wired Ethernet connections only and is not used for Wi-Fi. Avaya Vantage™ uses MTU_SIZE to provide compatibility with Ethernet switches that do not support the longest maximum frame length possible with tagged frames.

IPV6STAT

Numeric

1

Specifies the mode of the IP family to be used in the current device configuration.

Assign on of the following values:

• 0: Support IPv4 only mode.

• 1: Support dual mode (IPv4 and IPv6).

• 2: Support IPv6 only mode.

In an IP Office environment, set this parameter to 0 to block IPv6 traffic because Avaya Vantage™ does not support IPv6 in an IP Office environment.

This parameter is applicable for both wired Ethernet and wireless connections.

For provisioning, use:

• The SET command in the 46xxsettings.txt file.

• The settings file received from Avaya Aura® Device Services.

DHCPSTDV6

Numeric

0

Specifies whether DHCPv6 will comply with the IETF RFC 8415 standard and immediately stop using an IPv6 address if the address valid lifetime expires, or whether it will enter an extended rebinding state.

Assign on of the following values:

• 0: If the DHCPv6 lease expires, DHCPv6 enters a proprietary extended rebinding state, in which it continues to use the IPv6 address.

• 1: If the DHCPv6 lease expires, DHCPv6 complies with the IETF RFC 8415 standard and immediately releases the IPv6 address.

For provisioning, use:

• The SET command in the 46xxsettings.txt file.

• The settings file received from Avaya Aura® Device Services.

DHCPSTAT

Numeric

3

Specifies whether DHCPv4, DHCPv6, or both are to be used to assign IP addresses to the device.

Currently, Avaya Vantage™ only supports the default value 3, which enables the use of both DHCPv4 and DHCPv6.

For provisioning, use:

• The SET command in the 46xxsettings.txt file.

• The settings file received from Avaya Aura® Device Services.

PRIVACY_SLAAC_MODE

Numeric

1

Specifies the preference for privacy extensions (RFC3041) when using SLAAC to generate IPv6 addresses.

Assign on of the following values:

• 0: Disable privacy extensions. One stable address is generated using modified EUI-64 format interface identifier based on the device MAC address. The device address selection preference is based on default RFC6724 SASA rules.

• 1: Enable privacy extensions with a preference for public addresses over temporary addresses. One stable address is generated using modified EUI-64 format interface identifier based on the device MAC address and one temporary private address is generated. This parameter value overrides the default RFC6724 SASA Rule 7 to prefer a manual, DHCPv6, or stable SLAAC address over a SLAAC temporary address.

• 2: Enable privacy extensions with a preference for temporary addresses over public addresses. One stable address is generated using modified EUI-64 format interface identifier based on the device MAC address and one temporary private address is generated. The device address selection preference is based on default RFC6724 SASA rules. The default SASA rule 7 is used to prefer a SLAAC temporary address over manual, DHCPv6, or stable SLAAC addresses.

For provisioning, use:

• The SET command in the 46xxsettings.txt file.

• The settings file received from Avaya Aura® Device Services.

DUAL_IPPREF

Numeric

4

Specifies IPv4 or IPv6 preferences. The parameter controls the selection of SSON either from DHCPv4 or DHCPv6 when the device is in dual mode.

DHCP clients use DUAL_IPPREF to decide which SSON configuration attributes to apply for DHCPv4 and DHCPv6 interworking in dual mode.

Assign on of the following values:

• 4: Prefer IPv4 over IPv6.

• 6: Prefer IPv6 over IPv4.

For provisioning, use:

• The SET command in the 46xxsettings.txt file.

• The settings file received from Avaya Aura® Device Services.

SIGNALING_ADDR_MODE

Numeric

4

Specifies IPv4 or IPv6 preference for SIP registration. This parameter comes into effect only when both the device and Session Manager are in dual mode with both IPv4 and IPv6 addresses configured.

Based on the value of the parameter, the Avaya™ Client SDK application uses the preferred IP addresses of Session Manager from SIP_CONTROLLER_LIST.

Assign on of the following values:

• 4: Prefer IPv4 over IPv6.

• 6: Prefer IPv6 over IPv4.

This parameter is not supported in the non Avaya™ Client SDK application based mode.

If Avaya Vantage™ is in IPv4 or IPv6 only mode, it ignores SIGNALING_ADDR_MODE.

If Avaya Vantage™ is in IPv4 only mode, and Session Manager is either in IPv4 only or dual mode, then the SIP controller’s IPv4 addresses are selected from SIP_CONTROLLER_LIST for SIP registration. If Session Manager is in IPv6 only mode, the Avaya™ Client SDK application cannot connect with the SIP controller.

If Avaya Vantage™ is in IPv6 only mode, and Session Manager is either in IPv6 only or dual mode, then the SIP controller’s IPv6 addresses are selected from SIP_CONTROLLER_LIST for SIP registration.

For provisioning, use:

• The value stored on the PPM server.

• The SET command in the 46xxsettings.txt file.

• The settings file received from Avaya Aura® Device Services.

• A name=value pair in a DHCPACK message.

• A name=value pair in the DHCPv6 Reply VSI option 242.

MEDIA_ADDR_MODE

Numeric

4

Specifies the preference of SDP media group lines by the active Avaya™ Client SDK application on Avaya Vantage™.

If Avaya Vantage™ is in IPv4 or IPv6 only mode, it ignores MEDIA_ADDR_MODE.

This parameter is not supported in the non Avaya™ Client SDK application based mode.

Assign on of the following values:

• 4: Use IPv4.

• 6: Use IPv6.

• 46: Prefer IPv4 over IPv6.

• 64: Prefer IPv6 over IPv4.

For provisioning, use:

• The value stored on the PPM server.

• The SET command in the 46xxsettings.txt file.

• The settings file received from Avaya Aura® Device Services.

• A name=value pair in a DHCPACK message.

• A name=value pair in the DHCPv6 Reply VSI option 242.

IPV6DADXMITS

Numeric

1

Specifies whether Duplicate Address Detection (DAD) is performed on tentative addresses, as specified in RFC 4862. A non-zero value specifies the maximum number of transmitted Neighbor Solicitation (NS) messages to determine whether an IPv6 address is already in use.

The value can be in the range from 0 to 5.

Assign on of the following values:

• 0: Disable DAD.

• 1 to 5: Enable DAD. The value indicates the maximum number of transmitted NS messages.

For provisioning, use:

• The SET command in the 46xxsettings.txt file.

• The settings file received from Avaya Aura® Device Services.

BLUETOOTHSTAT

Numeric

1

Specifies whether Bluetooth is allowed for user configuration. Assign one of the following values:

• 0: Bluetooth and the Bluetooth menu are disabled in the Settings menu on the device. The user cannot enable Bluetooth.

• 1: Bluetooth and the Bleutooth menu are enabled in the Settings menu on the device. The user can enable or disable Bluetooth.

For provisioning, use the SET command in the 46xxsettings.txt file.

BLUETOOTH_FEATURES_SHARED_VIA_STAT

Numeric

0

Specifies whether users have access to Shared via Bluetooth options in the Setting menu on the device.

• 0: Users cannot use Shared via Bluetooth.

• 1: Users can use Shared via Bluetooth.

For provisioning, use the SET command in the 46xxsettings.txt file.

NFCSTAT

Numeric

1

Specifies whether users have access to Near Field Communication (NFC).

• 0: NFC is disabled. The user does not get an option to enable NFC.

• 1: By default, NFC is disabled. The user can enable or disable NFC through the Settings menu on the device.

For provisioning, use the SET command in the 46xxsettings.txt file.

TRUST_AGENTS_STAT

Numeric

1

Specifies whether users can configure trust agents.

• 0: Users cannot access Trust agents in the Settings menu. All trust agents are disabled.

• 1: Users can access Trust agents in the Settings menu. Users can enable or disable the available trust agents

For provisioning, use the SET command in the 46xxsettings.txt file.

TRUST_AGENTS_AVAYA_SMARTLOCK_STAT

Numeric

1

Specifies whether users can configure the Avaya Smart Lock feature.

• 0: Users cannot access Avaya Smart Lock in the Settings menu. The Avaya Smart Lock feature is disabled.

• 1: Users can access Avaya Smart Lock in the Settings menu. Users can enable or disable the Avaya Smart Lock feature.

For provisioning, use the SET command in the 46xxsettings.txt file.

WIFISTAT

Numeric

1

Specifies whether users can configure Wi-Fi.

• 0: Wi-Fi is disabled. Users cannot enable Wi-Fi.

• 1: Wi-Fi is enabled. Users can enable or disable WiFi and configure Wi-Fi settings through the Settings menu on the device.

For provisioning, use the SET command in the 46xxsettings.txt file.

WIFIAPSTAT

Numeric

0

Specifies whether users can configure the Wi-Fi access point.

• 0: Wi-Fi access point is disabled. Users cannot enable the access point.

• 1: Users can enable and configure the access point.

For provisioning, use the SET command in the 46xxsettings.txt file.

WIFI_CON_STATUS_ON_LOGOUT

Numeric

1

Specifies whether Avaya Vantage™ keeps information about wireless connections after logout.

• 0: Avaya Vantage™ deletes information about Wi-Fi connections, such as Wi-Fi passwords.

• 1: Avaya Vantage™ keeps information about Wi-Fi connections and the active wireless connection, such as Wi-Fi passwords.

This parameter is not supported in the non Avaya™ Client SDK application based mode.

For provisioning, use the SET command in the 46xxsettings.txt file.

GRATARP

Numeric

0

Specifies whether an existing Address Resolution Protocol (ARP) cache entry is updated with a MAC address received in a gratuitous ARP message. Assign one of the following values:

• 0: Avaya Vantage™ ignores gratuitous ARP messages.

• 1: Avaya Vantage™ uses gratuitous ARP messages to update the existing ARP cache entry.

For provisioning, use the SET command in the 46xxsettings.txt file.