In this post, we continue our look into IPv6 and its implementation in a Cisco UC environment.
Will customers begin using IPv6 in their internal networks? Time will tell. However, it does us all a lot of good to understand the implications and caveats of using this new IP version.
IPv6 Best Practices: Single-Site Model
IPv6-enabled Phones:
- Configuration: IPv4 and IPv6 (dual stack)
- Use IPv6 for signaling to CUCM
- Prefer IPv6 over IPv4 for media
PSTN Gateways:
- Standard: CUCM SIP trunk to IOS SIP gateway
- Configuration: IPv4 and IPv6 (dual stack)
- ANAT enabled
- Use IPv6 for signaling to CUCM
- Prefer IPv6 over IPv4 for media
Note 1: Regarding the usage of MTPs in a dual stack environment, CUCM SIP trunks and SIP gateways can be configured to use either of the following:
- SIP Early Offer (MTP required checked and used for every call.)
- SIP Delayed Offer (MTP Required unchecked, although MTPs may be inserted dynamically for some calls for conversions between IPv4 and IPv6 addresses.)
Note 2: Regarding workarounds to decrease MTP usage:
If a single dual-stack gateway is used and the cluster-wide preference for media is set to IPv6, an MTP will be used for all calls to IPv4-only devices to convert from IPv4 to IPv6.
If the widespread use of MTPs is not acceptable in the single-site deployment, configure two PSTN gateways instead of just one. Configure one as a dual-stack SIP gateway using SIP Delayed Offer as described above, and the other as a standard IPv4-only gateway.
Calling search spaces and partitions can then be used to direct PSTN calls from IPv4-only and dual-stack devices to their respective gateways.
Campus LAN:
If the campus LAN is Layer 2 only, enable Multicast Listener Discovery (MLD) to reduce unwanted multicast traffic in the LAN.
If the campus LAN is Layer 3 enabled, configure switches to support dual-stack (IPv4 and IPv6) routing.
Continue Reading…