IPv6 support

For IP Office R12.1, IP Office systems can support IPv6 features in addition to the existing IPv4 features.

• IP Office supports IPv6 on Linux-based IP Office systems only.

• Use of IPv6 does not require any additional license or subscription.

• IPv4 remains always enabled. The IP Office does not support an IPv6 only mode.

The IPv6 features are:

• IP Addressing

  Avaya supports IPv6 on IP Office LAN1. Avaya also supports IPv6 on LAN2 but only when IPv6 is enabled on LAN1 also.

• DHCPv6 Support

  You can configure the IP Office to support DHCPv6. It can function as a DHCPv6 server or client on each IP Office LAN.

• Stateless Address Auto Configuration (SLAAC)

  You can configure the IP Office to use SLAAC to assign its IPv6 address on LAN1 and/or LAN2. You can also configure the IP Office to respond as an IPv6 router for other devices that are using SLAAC.

• IPv6 Routing Support

  You can configure the IP Office with static routes for IPv6 traffic.

• Avaya Workplace IPv6 Support

  You can use IPv6 for Avaya Workplace Client extension connection. That includes connection as local and remote extensions.

  • Avaya Workplace Client support for IPv6 with IP Office R12.1 requires Avaya Workplace Client R3.37 and higher.

  • The IP Office licensing and configuration requirements for remote extensions are the same for IPv6 as for IPv4. The IP Office treats any extension using an IPv6 global unicast address not issued by IP Office DHCP as a remote extension.

    • The IP Office must have an FQDN that resolves to both the IPv4 and IPv6 addresses of the IP Office.

    • You must configure the one-X Portal host domain settings (Configuration > Host Domain Name) with the FQDN of the IP Office server running the one-X Portal service.

  • Avaya Cloud Services do not support IPv6. Therefore, any Avaya Workplace Client using IPv6 cannot use features provided by Avaya Cloud Services. For example:

    • No client registration using email or SSO login.

    • No instant messaging if the IP Office uses Avaya Cloud Services as its messaging server.

• J100 Phone IPv6 Support

  You can use IPv6 for J100 Series phone extension connection (except J129). That includes connection as local and remote extensions.

  • IP Office support for IPv6 with J100 phones requires the phones to use J100 R4.1.6.0 or higher firmware.

  • For IPv6, IP Office supports the J100 Series phones (except J129) in dual-stack mode with the signaling address set to IPv6 and the media IP preference set to IPv6 over IPv4 (64). That is the default configuration set in the auto-generated 46xxsettings.txt file. For Avaya does not support the use of any other combination of signaling and media address mode as that can cause unexpected call failures.

  • The IP Office licensing and configuration requirements for remote extensions are the same for IPv6 as for IPv4. The IP Office treats any extension using an IPv6 global unicast address not issued by IP Office DHCP as a remote extension.

  • The IP Office must have an FQDN that resolves to both the IPv4 and IPv6 addresses of the IP Office.

• Certificates

  The IP Office will include its IPv6 addresses when regenerating IP Office signed certificates.

  • If using the IP Office self-signed certificates, you must regenerate the self-signed IP Office certificates after enabling IPv6 support.

All other IP Office connections and features use IPv4 as in previous IP Office releases.

Support for KVM virtual servers

For IP Office R12.1, Avaya supports the deployment of IP Office virtual machines on the Avaya Solutions Platform 130 Appliance R6 platforms (ASP 130 R6). Avaya supplies the ASP 130 R6 with Red Hat Enterprise Linux 8.10 pre-installed and configured to support KVM based virtual machines.

J100 USB Headset support

The J100 R4.1.6 firmware installed by default with IP Office R12.1 includes support for USB HID headsets on J100 Series phones that have USB ports (J159 and J189).