Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel

In this section:

Table of Contents
maxLevel3

 


The SBC Edge supports IPv6 functionality. IPv6 is supported in network services (such as interface addressing, static routing, neighbor resolution and DNS), as well as support in voice applications (such as SIP, Media Stream Control, Common Control, etc.). This document provides an overview of the IPv6 functionality and where to find configuration details.

...

In the diagram below, the SBC 1000 is displayed; the SBC 2000 supports the same functionality.

...


Typical Network

Image Modified

...

 


IPv6 Supported Deployments - Examples

...

  • IPv6-to-IPv4. The LAN uses IPv6 and the WAN uses IPv4. The SBC is responsible for interworking SIP calls between the two networks. The DNS server is provided by thr the ISP and the NTP is provided locally.

  • IPv6-to-IPv6. The LAN and the WAN use IPv6. The SBC is responsible for serving as a back-to-back user agent between the two call legs. The DNS server and NTP server are both on the WAN.

  • IPv4-to-IPv6.The LAN uses IPv4 and the WAN uses IPv6. Just as in the IPv6-to-IPv4 case, the SBC is responsible for protocol interworking between the two call legs. The DNS server and the NTP server are both on the LAN.

 

...

...


Sample Deployment Scenario

Image Modified

...

 


IPv6 Features Supported

Addressing

...

Neighbor Discovery

IPv6 uses Neightbor Neighbor Distribution Protocol (NDP) to map IPv6 addresses to link-layer addresses. In the most common scenario, this mapping occurs dynamically as and when the IPv6 address needs to be resolved to its link-layer address. Along with this dynamic IPv6 neighbor resolution, you can also create Static Neighbor Entries. These entries include: IPv6 address, MAC address, and assicated associated interface. This provides a static mapping between the provided IPv6 address and the provided MAC address.

...

  • SIP Signaling (one signaling group supports both IPv4 and IPv6). Ingress Signaling Group receives inbound request on both IPv4 and IPv6; egress Signaling Group sends SIP message to next-hop, which can be SIP Server or Outbound proxy.
  • SDN (media portion)
  • Multiple transport protocols
  • Protocol preference at multiple levels (i.e., signaling media)
  • SIP Transport (UDP, TCP, TLS)
  • SIP Registration
  • UDP, TCP, TLS

...


IPv6 Configuration Guidelines

...

The SBC supports IPv6 Registration, basic calls, call hold, and call transfer. For details on configuring the SIP Signaling Group, see Creating and Modifying SIP Signaling Groups.

Ingress SignalingEgress Signaling Media Supported
 

IPv6 Federated IP/FQDNSignaling/Media Source IP - select IPv6 interface only DSP mode, RTP-Proxy, Direct Media
 

IPv4 < > IPv6 Interworking Calls

...

Info

Things to Note:

  • If one call leg media's IP version is different than the other call leg, the Media configuration must be DSP mode; Proxy Mode or Direct Media must not be used.
  • For each call leg, bi-directional signaling must use the same IP version.
  • For each call leg, bi-directional media must use the same IP version.
  • For each leg, all media (audio and video) must use the same IP version.

 


Configuration Guidelines
Ingress Signaling/MediaEgress Signaling/MediaAudio Media SupportedVideo Media Mode Supported
IPv4IPv4DSP-Mode, RTP-proxy, Direct MediaRTP-Proxy, Direct Media
IPv6IPv6DSP-Mode, RTP-proxy, Direct MediaRTP-Proxy, Direct Media
IPv4IPv6DSP-Mode onlyVideo not allowed
IPv6IPv4DSP-Mode onlyVideo not allowed

How IPv6 is Monitored

Two diagnostic tools support IPv6 addressing: Ping and Traceroute. The IP address type selection determines which IP Protocol an FQDN will be resolved when when performing a ping or traceroute on an FQDN.pagebreak