Avaya SBC supports both IPv4 and IPv6 addresses to PSTN (public) SIP trunk servers and private enterprise SIP trunk servers. Avaya SBC uses dual stack nodes that run both IPv4 and IPv6.
In addition to standard IPv4 support, Avaya SBC supports the following features using IPv6:
IPv6 unique local unicast address and IPv6 global unicast address.
IPv6 communication with entities such as SIP servers, SIP endpoints, DNS servers, NTP server, syslog server, and Avaya Aura® Media Server.
Note:
If the DNS response has both IPv4 and IPv6 addresses, Avaya SBC relies on configuration policies to determine the address types to be tried.
IPv6 communication with EMS.
Avaya SBC supports:
IPv6 communication with SIP recording server.
IPv6 in Remote Worker deployments.
Avaya SBC supports the following features over IPv6:
High availability (HA)
Access to EMS web interface
Time synchronization with the configured NTP server
SIP trunking
Avaya SBC supports Alternate Network Address Types (ANAT) semantics for SDP to permit alternate network addresses for media streams. ANAT semantics are useful in environments with both IPv4 and IPv6 hosts. When Avaya SBC receives an SDP offer with ANAT semantics, Avaya SBC:
Determines whether the enterprise network uses only IPv4.
Strips media line grouping and sends only the IPv4 address in the m line if the enterprise network uses IPv4.
Picks an m line based on ANAT preference configuration and sets the port to 0 in other m lines.
Avaya SBC supports ANAT RFC for audio and video on SIP trunk and Remote Worker deployments. Avaya SBC learns from Registration messages whether remote workers are capable of supporting ANAT and dual stack media interfaces.
SIP entities that generate an SDP offer with ANAT semantics place the sdp-anat-option-tag in the Require header field. Avaya SBC supports the sdp-anat-option tag. Avaya SBC supports UDP/RTP, TCP/RTP, TLS/SRTP, and other combinations in IPv6-only, dual stack, and mixed mode networks.
If you have an environment with both IPv4 and IPv6 hosts, you must go to Domain Policies Media Rules, and select ANAT Enabled. For more information, see Administering Avaya Session Border Controller.
Avaya SBC also supports the following IPv6-related features:
Avaya SBC terminates SIP IPv6 signaling and converts all SIP signaling headers to corresponding SIP IPv4 addresses. By doing this, Avaya SBC does not expose any IPv6 SIP address anywhere within Avaya Aura® core services.
When Session Manager also supports SIP IPv6 addresses, you can set a tolerance flag on Avaya SBC to that Avaya SBC may not do a strict conversion or hiding of SIP IPv6 address and pass the IP address to Session Manager.
Avaya SBC can learn the IPv4 and IPv6 address family dynamically for media and signaling for automatic configuration.
Avaya SBC supports NAT64 interworking with PSTN providers.
Avaya SBC supports call flows from mobile PSTNs on IPv6 or IPv4 to dual stack WiFi using both media and signaling services.
Avaya SBC supports IPv6 to IPv4 conversion on HTTP and PPM messages.
Avaya SBC does not support TURN on IPv6 nor interworking of IPv6 an IPv4 on TURN media.
