IP Office can supported J100 and Avaya Workplace Client extensions that use IPv6 using one of the following methods:

• Remote IPv6 extensions using a dual-stack ASBCE

  This method of connection uses an ASBCE R10.1.2 or higher configured for dual-stack (IPv4/IPv6) and IP Office R11.1.3.1 or higher. It only supports IPv6 for remote J100 and Avaya Workplace Client extensions. See Deploying Remote IP Office SIP Phones with an ASBCE.

• Remote and local J100 IPv6 extensions

  This method uses a Linux-based IP Office server (R12.1 and higher) configured with IPv6 addresses. That allows connection of both remote and local IPv6 J100 and Avaya Workplace Client extensions. Note: Avaya still only supports remote extensions when connected through a firewall and/or session border controller.

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

  • Within the IP Office configuration, you must use FQDNs where supported by the configuration fields.

  • For J100 phones using IPv6, for resilience you must also configure the failover IP Office to use IPv6.

  • The IP Office does not support Direct Media for extension connections that use ANAT. However, it will apply RTP relay to reduce the IP Office resource requirements.

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

You cannot combine the two methods. For example, you cannot use a dual-stack ASBCE and an IP Office with an IPv6 address.