IPv6 in Enterprise Unified Communications Networks

Transcription

1

2 IP in Enterprise Unified Communications Networks BRKCOL-2020 Tony Mulchrone - Technical Marketing Engineer Cisco Collaboration Technology Group

3 Agenda IP Addressing summary IP and UC Networks summary IP Addressing and Cisco devices DHCP and DNS for IP IP Campus and WAN Deployment Options IP UC Configuration CUCM IP Device Configuration Parameters and Media Handling Other IP Design Considerations IP UC Deployment Guidelines Summary

4 Why Deploy IP? IP deployment is primarily driven by IP address space exhaustio The number of applications, devices, services requiring IP addresses is rapidly increasing as the world becomes more and more IP centric Addresses in IP are 128 bits long versus 32 bits IP address. The larger address space avoids the potential exhaustion of IP addresses without need for Network Address Translation. By avoiding the need for complex sub-netting scheme, IP addressing space easier to understand, making administration of medium and larger networks simpler. IP hosts can be configured automatically using Stateless Address Auto- Configuration (SLACC) when connected to a routed IP network using ICMP router discovery messages. BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 4

5 IP Addressing Space IP = 32 bits IP = 128 bits IP uses 32 bits = ~ 4,200,000,000 possible addressable nodes CIDR and NAT techniques used to make the best possible use of address space IP uses 128 bits = 340,282,366,920,938,463,463,374,607,431,768,211,456 nodes = 52 Trillion Trillion addresses per person in the world = More than enough Allows for scalable, simple and easily understandable addressing schemes BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 5

6 IP Address Format An IP address is composed of 8 sets of 16 bit hexadecimal values, 128 bits in length 2001:0db8:1234:5678:9abc:def0:1234: bit hex values are separated by colons (:) Abbreviation is possible Leading zeros can be omitted Consecutive zeros in contiguous blocks can be represented by (::) 2001:0db8:0000:130F:0000:0000:087C:140B becomes 2001:0db8:0:130F::87C:140B Double colons can only appear once in the address Network prefix representation like IP CIDR --- e.g. 2001:db8:12::/64 BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 6

7 IP Address Network and Host IDs Network ID Host ID XXXX:XXXX:XXXX:XXXX:YYYY:YYYY:YYYY:YYYY 64 Bits 64 Bits IP Unicast addresses use 64 bits for the Network ID and 64 bits for the Host ID The Host ID can be auto-configured by : 1) Using a randomly generated number, or 2) By using the (Extended Unique Identifier) EUI-64 format. This format expands the 48 bit MAC address to 64 bits by inserting FFFE into the middle 16 bits. Cisco commonly uses this Host ID format. 3) The host ID can also be assigned using DHCP or manually configured FC 0F FC 0F FF FE FF FE 17 FC 0F U0 Where U= 1 = Unique ID 0 = Not Unique U = FF FE 17 FC 0F BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 7

8 IP - Addressing Model Addresses are assigned to interfaces An Interface is expected to have multiple addresses Addresses have scope Link Local Unique Local Global Global Unique Local Link Local BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 8

9 Primary Types of IP Address Unicast Address Identifies a single node/interface. Traffic destined to a Unicast address is forwarded to a single interface Multicast Address Identifies a group of nodes/interfaces. Traffic destined to a Multicast address is forwarded to all the nodes in the group No more Broadcast addresses Too resource intensive, IP uses Multicast addresses instead BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 9

10 Link-Local Unicast Addresses 128 Bits Remaining 54 Bits Interface ID FE80::/10 10 Bits Link-Local Addresses are : Mandatory addresses - used exclusively for communication between two IP devices on the same link. Automatically assigned by the device as soon as IP is enabled Only Link Specific scope not routed Remaining 54 bits of network ID are typically zero but could be set to any manually configured value Interface ID has the same meaning for all unicast addresses, 64 bits long using the EUI-64 format Example - FE80:0000:0000:0000:0987:65FF:FE01:2345 Generally represented as FE80::987:65FF:FE01:2345 BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 10

11 Unique-Local Unicast Addresses 128 Bits 1 Global ID 40 Bits Interface ID FD00::/7 7 Bits Subnet ID 16 Bits 1 Bit : L = 1 Locally assigned; L = 0 Future Use Unique-Local Addresses are : Analogous to Private IP addresses (e.g ) Not Routable on the Internet (would require IP NAT) Global IDs do not have to be aggregated Subnet IDs are defined by the administrator of the local domain Subnet IDs typically use a hierarchical addressing plan to allow for route summarization Interface ID has the same meaning for all unicast addresses, 64 bits long using the EUI-64 format Example - FD00:aaaa:bbbb:CCCC:0987:65FF:FE01:2345 BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 11

12 Global Unicast Addresses Network ID RIR ISP LAN Host 3 21 Bits 24 Bits 16 Bits 64 Bits Global Prefix TLA NLA SLA Interface ID 001 Global Unicast Addresses are : /24 /48 /64 Routable / reachable across the Internet Identified by their 3 high level bits set to 001 ( 2000::/3 ) Global Routing Prefix assigned to Regional Internet Registries by Internet Assigned Numbers Authority (IANA) Next Level Aggregator (NLA) assigned to ISP Site Level Aggregator (Subnet ID) assigned to a customer by their Service Provider Example :0DB8:BBBB:CCCC:0987:65FF:FE01: Cisco and/or its affiliates. All rights reserved. Cisco Public

13 IP Multicast Addresses 128 Bits 8-bits 4-bits 4-bits Lifetime Scope 112-bits Group-ID Lifetime Scope 0 If Permanent 1 Node 1 If Temporary 2 Link 5 Site 8 Organization E Global IP multicast addresses have a prefix FF00::/8 ( ) The second octet defines the lifetime and scope of the multicast address Used for Router Advertisements, DHCP, Multicast Applications Multicast addresses are always destination addresses BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 13

14 Some Well-Known Multicast Addresses Address Scope Meaning FF01::1 Node-Local Same Node FF02::1 Link-Local All Nodes on a Link FF01::2 Node-Local Same Router FF02::2 Link-Local All Routers on a Link FF05::2 Site-Local All Routers on Intranet FF02::1:FFXX:XXXX Link-Local Solicited-Node More details at Solicited Node Addresses - Used for Neighbor Discovery and Duplicate Address Detection 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public

15 Agenda IP Addressing summary IP and UC Networks summary IP Addressing and Cisco devices DHCP and DNS for IP IP Campus and WAN Deployment Options IP UC Configuration CUCM IP Device Configuration Parameters and Media Handling Other IP Design Considerations IP UC Deployment Guidelines Summary

16 IP and IP Icons and Terminology IP Only Device communicates with and understands IP addresses only IP Only Device communicates with and understands IP addresses only Dual Stack (IP and IP) with ANAT This device communicates with and understands both IP and IP addresses and can also negotiate the use of either IP or IP for media IP Aware Device communicates with IP addresses, but can receive and understand IP addresses embedded in Application PDUs Typically used by applications which use IP to transport IP information BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 16

17 IP and IP Product Support UC11.X - Summary (1 of 2) Call Control CUCM 7.1(2)+ IM & P Services 10.5(1) External Connections only e.g. federation CUBE 12.4(22)T+ CUCME 8.0+ Cisco IP Phones 7906G, 7911G, 7931G, 7941G, 7941GE, 7942G, 7945G, 7961G, 7961GE, 7962G, 7965G, 7970G, 7971G-GE, 7975G 6901, 6911, 6921, 6922, 6941, 6942, 6945, 6946, 6961, , 7821, 7841, 7845, 7861, 8961, 9951, 9971 SIP based Cisco Telepresence Endpoints: C20, C40, C60, C90, MX Series, DX Series, EX Series, SX20, SX60 BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 17

18 IP and IP Product Support UC11.X - Summary (2 of 2) Gateways IOS SIP Gateways ISR G2, ASR SCCP/SIP Analogue Gateways VG Gateway platforms SCCP FXS ports on ISR G2 routers IOS software and harwdare MTPs for IP - IP RTP Media conversion CUBE IP to IP voice interworking CUCM SIP Trunks IP/IP signalling, ANAT for Dual stack media negotiation Applications Unity Connection IP, IP/IP ANAT Cisco WebEx Meeting Server IP, IP/IP ANAT for Web/Audio connections only. Cisco Prime Collaboration Suite IP, IP Aware Cisco Meeting Server - IP, IP Cisco Telepresence Server - IP, IP/IP ANAT; Cisco TP Conductor IP BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 18

19 IP Capable UC Devices Summary SIP Trunks H323 ICT Trunks IP/IP IP Only Jabber Mobile Clients SRST Soft Phones SCCP ISR Analogue Ports CUCME (SCCP Phones only) SIP TelePresence Endpoints VG Analogue Gateways CUBE / SIP Gateways Newer SIP based Phones Older SCCP based Phones Cisco Expressway C/E Newer SCCP based Phones Older SIP based Phones MGCP/ H323 Gateways BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 19

20 IP Capable UC Applications - Summary SIP Trunks H323 ICT Trunks IP/IP IP Only Cisco Meetings Server Cisco Emergency Responder Telepresence Server Directory Cisco Prime Collaboration Suite TelePresence Endpoints IM&P Cisco Webex Meeting Server Newer SIP based Phones Unified Contact Centre IOS based DHCP/ DNS Newer SCCP based Phones Unity Express Unity Connection 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public

21 Agenda IP Addressing summary IP and UC Networks summary IP Addressing and Cisco devices DHCP and DNS for IP IP Campus and WAN Deployment Options IP UC Configuration CUCM IP Device Configuration Parameters and Media Handling Other IP Design Considerations IP UC Deployment Guidelines Summary

22 IP CUCM Addressing CUCM can support: One Link Local IP Address and One Unique Local IP Address or One Global IP Address (and an IP address) BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 22

23 IP IP Phone Addressing IP Phones can support: One Link Local IP Address and Multiple Unique Local IP Addresses Multiple Global IP Addresses (and an IP address) IP Phone will use one IP address (Global or Unique Local) for CUCM signaling and media. A Link Local address will never be sent to CUCM as a signaling and media address If the phone has both Unique Local and Global addresses, the Global Addresses take precedence over Unique Local Addresses. If multiple Unique Local or multiple Global addresses exist - the first address configured will be used as the signaling and media address sent to CUCM BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 23

24 IP IOS Addressing IOS devices can support: One Link Local IP Address and Multiple Unique Local IP Addresses Multiple Global IP Addresses (and multiple IP addresses) Per Interface Routers use Link Local Addresses for Routing protocols and the Address Selection Algorithm (RFC 3484) for applications running on routers (Telnet, SSH, etc.) e.g. For responses to devices - Routers will try to use the same Network Prefix as the device initiating communications BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 24

25 Agenda IP Addressing summary IP and UC Networks summary IP Addressing and Cisco devices DHCP and DNS for IP IP Campus and WAN Deployment Options IP UC Configuration CUCM IP Device Configuration Parameters and Media Handling Other IP Design Considerations IP UC Deployment Guidelines Summary

26 IP Phones IP and IP Address Allocation Options IP Address Configuration Options Manual Configuration via Phone User Interface DHCP IP Address Configuration Options Manual Configuration via Phone User Interface Auto Configuration DHCP Note - Phones require a minimum of an IP address and TFTP server address IOS supports DHCP server with vendor option classes BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 26

27 IP Phone IP Address Allocation SLAAC StateLess Address Auto-Configuration (SLAAC) - RFC 2462 Configurable for IP enabled Phones CUCM Default - Auto Configuration = On On power up phone sends a Router Solicitation (RS) message requesting Address configuration information Router responds and periodically sends a Router Advertisement (RA) RA can contain one or more Network Prefixes Network Prefix and EUI-64 Host ID used to create interface address RA also contains O and M bits: O bit = 1 Indicates that the Phones should use the advertised Network Prefix(es) to auto-configure its address, but should also request Other information from the DHCP server e.g. TFTP server address, DNS server address M bit =1 Indicates that the Phone should use DHCP for stateful address assignment BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 27

28 IP Router Advertisements and DHCP Operation Stateless DHCP When a router sends an Router Advertisement (RA) with the O bit set, but does not set the M bit, the client can use Stateless Address Auto-configuration (SLAAC) to obtain its IP address, and use DHCP for obtaining additional information. (e.g. TFTP Server address, DNS server address). This mechanism is known as Stateless DHCP, because the DHCP server does not need to keep track of the client address bindings. Stateful DHCP When a router sends an RA with the M bit set, this indicates that clients should use DHCP to obtain Addresses. Note - When the M bit is set, the setting of the O bit is irrelevant, since the DHCP server will also return Other configuration information together with addresses. This mechanism is known as Stateful DHCP, because the DHCP server does keep track of the client address bindings. IP Phone DHCP Client Reply Request Advertise Solicit DHCP Server RA with O and /or M bit set BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 28

29 IP Phones IP Address Allocation - DHCP Methods: Stateless DHCP (RFC 3736) DHCP server only provides Other Information e.g. DNS Server, TFTP Server address Stateful DHCP (RFC 3315) DHCP server provides IP Network Address and optionally : Host ID - Host ID can also be generated by host using EUI-64 Other Information e.g. DNS Server address, TFTP Server Address Note Default Router address is not a required option with IP - Multicast is used instead to discover Routers on the Link DHCP Prefix Delegation (RFC 3633) Primarily used by Service Providers to automatically assign a Network Prefix to a customer s site Allows the delegation of prefixes from a delegating router to requesting routers. Devices use Multicast to find DHCP servers IOS DHCP Relay is supported BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 29

30 IP DNS CUCM can use DNS Name to Address Resolution for three purposes : If DNS names are used to define CUCM servers If SIP Route Patterns use DNS names to define destinations If SIP Trunks use DNS names to define Trunk destinations The principle for IP DNS is the same as IP but : The nomenclature is different AAAA instead of A records DNS name to address queries can return multiple IP addresses (and an IP address) Hostname to IP Address Resolution IP A record: A IP AAAA record: AAAA 2001:db8:C18:1::2 IP Address to Hostname Resolution PTR record: in-addr.arpa. PTR PTR record: c.0. 8.b.d ip6.arpa PTR BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 30

31 Agenda IP Addressing summary IP and UC Networks summary IP Addressing and Cisco devices DHCP and DNS for IP IP Campus and WAN Deployment Options IP UC Configuration CUCM IP Device Configuration Parameters and Media Handling Other IP Design Considerations IP UC Deployment Guidelines Summary

32 General IP Deployment Guidelines Almost all IP deployments will run a combination of IP and IP Both LAN and WAN environments also need to be considered when deploying IP for UC In almost all cases Dual Stack deployments offer the best approach when introducing IP into any network environment - As both IP devices and Dual Stack (IP/IP) devices can interoperate and disruption to the existing network is minimal. In the following sections we will focus on IP deployments for UC. We will touch upon the Campus and WAN environments, but mainly to reference existing design guidance for IP deployment BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 32

33 IP Campus Deployments Dual Stack Campus Model Dual Stack is the preferred and most versatile way to deploy IP in existing IP environments. Dual Stack is not the only IP deployment option in a Campus environment - other hybrid models that use tunnelling in the Campus network also exist. For more info see : Deploying IP in Campus networks Also : This week at Cisco Live Berlin BRKRST-2301 Enterprise IP Deployment - 9am Friday BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 33

34 Campus IP Deployment Options Dual-Stack IP/IP IP is transparent on L2 switches except for multicast - MLD snooping is available on most switching platforms IP uses the same types of routing protocols as IP, but with some slight modifications to account for specific requirements of IP The Catalyst platforms support Static, RIPng, EIGRP and OSPFv3 routing for IP IP First Hop Redundancy Protocols such as HSRP & GLBP are supported by IOS routing platforms. HSRP & GLBP are supported by most Catalyst platforms Use Cisco First Hop Security for IP to secure your Layer 2 environment (Cisco FHS includes RA guard, DHCP guard, IP Snooping and more IP& IP Dual Stack Hosts Dual Stack Dual-stack Server Access Layer Distribution Layer Core Layer Aggregation Layer (DC) Access Layer (DC) BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 34

35 IP WAN/Branch Deployment Headquarters Cisco routers have supported IP for a long time Dual-stack should be the focus of your implementation but, some situations still call for tunneling IP is supported for every media/wan type (Frame Relay, leased-line, broadband, MPLS, etc.) Don t assume all features for every technology are Dual Stack SP Cloud Dual Stack Dual Stack IP-enabled Dual Stack Dual Stack BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 35

36 IP Capable UC Devices Summary SIP Trunks H323 ICT Trunks IP/IP IP Only Jabber Mobile Clients SRST Soft Phones SCCP ISR Analogue Ports CUCME (SCCP Phones only) SIP TelePresence Endpoints VG Analogue Gateways CUBE / SIP Gateways Newer SIP based Phones Older SCCP based Phones Cisco Expressway C/E Newer SCCP based Phones Older SIP based Phones MGCP/ H323 Gateways BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 36

37 IP Capable UC Applications - Summary SIP Trunks H323 ICT Trunks IP/IP IP Only Cisco Meetings Server Cisco Emergency Responder Telepresence Server Directory Cisco Prime Collaboration Suite TelePresence Endpoints IM&P Cisco Webex Meeting Server Newer SIP based Phones Unified Contact Centre IOS based DHCP/ DNS Newer SCCP based Phones Unity Express Unity Connection 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public

38 Agenda IP Addressing summary IP and UC Networks summary IP Addressing and Cisco devices DHCP and DNS for IP IP Campus and WAN Deployment Options IP UC Configuration CUCM IP Device Configuration Parameters and Media Handling Other IP Design Considerations IP UC Deployment Guidelines Summary

39 IP CUCM Configuration Steps Server Platform IP Address configuration CUCM IP Address configuration CUCM IP Cluster wide configuration IP Device Specific configuration parameters Common Device configuration SIP Trunk configuration SIP ANAT and CUCM Trunk Operation BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 39

40 Server Ethernet Port - IP Address Configuration To allow IP based call processing IP must first be enabled throughout the cluster. This involves two steps: 1) Configuring IP via the OS CLI, or CUCM OS GUI on each server in the cluster (below) 2) Configuring IP via the CUCM GUI Server Configuration Server OS Admin CLI commands : To enable IP : set network ip service enable To set a static IP server address : "set network ip static_address <addr> <mask>" Using the DHCP client is not recommended. To view IP address settings : show network ip settings 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public

41 CUCM Service - IP Address Configuration ICCS TFTP TFTP For the CUCM service Configure an IP address or name If a name is used, DNS is required This name / IP address is used by the TFTP server in the configuration files that are sent to devices. The address is used by these devices for CUCM registration Cisco and/or its affiliates. All rights reserved. Cisco Public

42 CUCM Enterprise Parameters for IP Enable IP Cluster-wide via CUCM GUI Configure Cluster-wide: IP Addressing Mode Preference for Media IP Addressing Mode Preference for Signalling IP for Phones Signalling Preference and Phone Configuration settings are also configurable at the device level Device setting takes precedence BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 42

43 IP CUCM Common Device Configuration SIP Trunks The Common Device Configuration is a configuration template that can be applied to Phones and Trunks. For IP capable devices the following values can be configured : IP Addressing Mode: IP Only - Device uses one IP address only IP Only - Device uses one IP address only IP and IP - Device uses one IP address & one IP address IP Addressing Mode Preference for Signalling: IP only IP only System Default IP Configuration For Phones : On/ Off/ Default 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public

44 Agenda IP Addressing summary IP and UC Networks summary IP Addressing and Cisco devices DHCP and DNS for IP IP Campus and WAN Deployment Options IP UC Configuration CUCM IP Device Configuration Parameters and Media Handling Other IP Design Considerations IP UC Deployment Guidelines Summary

45 IP and IP Icons and Terminology IP Only Device communicates with and understands IP addresses only IP Only Device communicates with and understands IP addresses only Dual Stack (IP and IP) with ANAT This device communicates with and understands both IP and IP addresses and can also negotiate the use of either IP or IP for media IP Aware Device communicates with IP addresses, but can receive and understand IP addresses embedded in Application PDUs Typically used by applications which use IP to transport IP information BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 45

46 IP and IP Product Support UC11.X - Summary (1 of 2) Call Control CUCM 7.1(2)+ IM & P Services 10.5(1) External Connections only e.g. federation CUBE 12.4(22)T+ CUCME 8.0+ Cisco IP Phones 7906G, 7911G, 7931G, 7941G, 7941GE, 7942G, 7945G, 7961G, 7961GE, 7962G, 7965G, 7970G, 7971G-GE, 7975G 6901, 6911, 6921, 6922, 6941, 6942, 6945, 6946, 6961, , 7821, 7841, 7845, 7861, 8961, 9951, 9971 SIP based Cisco Telepresence Endpoints: C20, C40, C60, C90, MX Series, DX Series, EX Series, SX20, SX60 BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 46

47 IP and IP Product Support UC11.X - Summary (2 of 2) Gateways IOS SIP Gateways ISR G2, ASR SCCP/SIP Analogue Gateways VG Gateway platforms SCCP FXS ports on ISR G2 routers IOS software and harwdare MTPs for IP - IP RTP Media conversion CUBE IP to IP voice interworking CUCM SIP Trunks IP/IP signalling, ANAT for Dual stack media negotiation Applications Unity Connection IP, IP/IP ANAT Cisco WebEx Meeting Server IP, IP/IP ANAT for Web/Audio connections only. Cisco Prime Collaboration Suite IP, IP Aware Cisco Meeting Server - IP, IP Cisco Telepresence Server - IP, IP/IP ANAT; Cisco TP Conductor IP BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 47

48 IP CUCM Phone Signaling and Addressing Options IP Signalling IP Signalling SCCP Phones 7906G, 7911G, 7931G 7941G, 7941GE, 7942G, 7945G, 7961G, 7961GE, 7962G, 7965G, 7970G, 7971G-GE, 7975G 6901, 6911, , 6945, 6961 IP IP Media Media SIP Phones 9951, 9971, 8961, 7821, 7841, 7845, 7861, 6922, 6942, 6946, 6962, 3905 Telepresence Endpoints: C20, C40, C60, C90, MX Series, DX Series, EX Series, SX20, SX60 IP Addressing Mode: (For Media and Signalling) Phone uses one IP address only Phone uses one IP address only Phone uses one IP address and one IP address IP Addressing Mode Preference for Signalling IP only/ IP only/ System Default IP for Phones - On/ Off/ Default 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public

49 IP CUCM Phone Signaling and Media Options IP Signalling IP is supported by the following Cisco Phones : IP IP IP Signalling Media Media SCCP Phones 7906G, 7911G, 7931G 7941G, 7941GE, 7942G, 7945G, 7961G, 7961GE, 7962G, 7965G, 7970G, 7971G-GE, 7975G 6901, 6911, , 6945, 6961 MTP For IP Addressing Mode mis-matches between Phones - CUCM inserts an MTP for IP IP conversion SIP Phones 9951, 9971, 8961, 7821, 7841, 7845, 7861, 6922, 6942, 6946, 6962, 3905 Telepresence Endpoints: C20, C40, C60, C90, MX Series, DX Series, EX Series, SX20, SX60 MTP Dual Stack Phones use the Cluster-wide IP Addressing mode for Media Preference to select addressing mode (IP or IP) for media between phones. BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 49

50 IP and CUCM Video Calls With UC it is recommended that all Voice, Video and Telepresence endpoints are registered to CUCM. CUCM supports Video over IP with UC 10.0 Video Calls can generate multiple media streams e.g. audio, main video, desktop sharing, far end camera control If an MTP is inserted into the call path up to 16 media channels can be supported for a single call (IOS release 15.3(2)T +) SIP Trunk Audio Main Video Slide Video Binary Floor Control Far End Camera Control BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 50

51 IP IP Phones - Other Signaling Options Phones use IP to interact with other CUCM services and network based services: Phone IP addresses are sent to access switches in CDP/ LLDP Phones use IP to contact their TFTP server Phones use HTTP for Phones Services, Extension Mobility, Directory Look Ups etc TFTP PUB For IP only CUCM and Phone deployments IP is used in CDP/LLDP and for TFTP and HTTP services TFTP HTTP CDP/LLDP BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 51

52 IP IP Phones - Other Signaling Options Phones use IP to interact with other CUCM services and network based services: Phone IP addresses are sent to access switches in CDP/ LLDP Phones use IP to contact their TFTP server Phones use HTTP for Phones Services, Extension Mobility, Directory Look Ups etc TFTP PUB For Dual Stack CUCM and Phone deployments IP and IP addresses are transported in CDP/LLDP TFTP can use IP and/or IP HTTP services use IP only TFTP HTTP CDP/LLDP BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 52

53 IP CUCM Phones - Other Signaling Options Phones use IP to interact with other CUCM services and network based services: Phone IP addresses are sent to access switches in CDP/ LLDP Phones use IP to contact their TFTP server Phones use HTTP for Phones Services, Extension Mobility, Directory Look Ups etc TFTP PUB For IP only CUCM and Phone deployments IP addresses are transported in CDP/LLDP (Layer 2) TFTP can use IP No HTTP services are supported in IP TFTP CDP/LLDP IP only HTTP and CDP/LLDP services will be introduced in a later Phase of IP development BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 53

54 IP VG Analogue Gateways and IOS FXS Analogue Ports VG Gateway Analog Phones IP IP IP IP Signalling Signalling Media Media VG224 IOS Gateway Analog Phones VG Analogue Gateways and IOS FXS ports can use MGCP or SCCP to register analog FXS ports (as Phones) with CUCM If Analogue Gateways use SIP Phones connect to CUCM via a SIP Trunk and support fewer features BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 54

55 IP CUCM SIP Gateways and SIP Trunks Signaling and Addressing Options SIP Signalling IP IP IP IP Signalling Signalling Media Media SIP based CUCM Trunks support IP SIP based IOS Gateways support IP IP Addressing Mode: (For Media and Signalling) Phone uses one IP address only Phone uses one IP address only Phone uses one IP address and one IP address - Recommended IP Addressing Mode Preference for Signalling (outbound) IP only/ IP only/ System Default Allow Auto-Configuration for Phones etc N/A 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public

56 IP CUCM SIP Gateways and Trunks Signaling and Media Options IP Signalling IP Signalling IP Media SCCP Signalling IP Media SIP Signalling MTP MTP For Media addressing mis-matches CUCM inserts an MTP for IP IP conversion PSTN Dual Stack SIP Gateways and Phones use the Cluster-wide IP Addressing mode for Media Preference to select addressing mode (IP or IP) for media between phones Cisco and/or its affiliates. All rights reserved. Cisco Public

57 Negotiating Media for dual stack devices Alternative Network Address Types (ANAT)

58 What is ANAT? Alternative Network Address Type Media lines in the Session Description Protocol (SDP) body are grouped using ANAT semantics to provide alternative types of network addresses to establish a particular media stream The entity creating an SDP body with an ANAT group MUST be ready to receive (or send) media over any of the grouped 'm' lines The identifiers of the media streams MUST be listed in order of preference in the group line UC Manager supports Dual-Stack SIP devices using ANAT semantics BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 58

59 ANAT Attributes in Session Description Protocol (SDP) Mid (Media Stream Identification) Uniquely identifies each media stream m line within the SDP body. Particularly useful when multiple media streams are present. Group Used for grouping together different media streams. In ANAT context, used to group together identical media streams that use different address types. Specifies the address preference between the two alternate address types. All the "m" lines of a session description must be associated with a MID value to be considered for grouping. BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 59

60 IP SIP Gateways and Trunks Alternative Network Address Types (ANAT) RFC 4091 & 4092 SIP INVITE w/o SDP (Delayed Offer) Supported : sdp-anat 200 (OK) with SDP (OFFER) a=group:anat 2 1 m=audio RTP/AVP 0 c=in IP ACK with SDP (ANSWER) a=mid:1 a=group:anat 2 m=audio RTP/AVP 0 m=audio 0 RTP/AVP 0 c=in IP6 2001:0db8 bbbb::0123:45ff:fe32:191d c=in IP a=mid:2 a=mid:1 m=audio RTP/AVP 0 c=in IP6 2001:0db8:aaaa::0987:65ff:fe01:234b a=mid:2 ANAT allows both IP and IP addresses to be exchanged in the SIP Offer and SIP Answer Depending on which SIP header sdp-anat value is sent indicates whether ANAT is Required or Supported The SDP body of the SIP Offer can contain both an IP and IP address preference is indicated in the a=group:anat field (using the a=mid: values associated with each address) The SDP body of the SIP Answer can contain both an IP and IP address the selected address is indicated in the a=group:anat field (using the a=mid: values associated with each address). The UDP port number of the nonpreferred IP address is set to 0 BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 60

61 Voice and Video Call - Offer SDP with ANAT group a=group:anat 1 2 Audio streams a=group:anat 3 4 Video Streams m=audio RTP/AVP 8 c=in IP6 2001:db8:123:1:ee44:76ff:fe1f:7f5c a=rtpmap:9 PCMA/8000 a=mid:1 Audio stream with IP Preference m=audio RTP/AVP 8 c=in IP a=rtpmap:8 PCMA/8000 a=mid:2 Audio stream with IP Preference m=video RTP/AVP 98 c=in IP6 2001:db8:123:1:ee44:76ff:fe1f:7f5c b=tias: a=rtpmap:126 H264/90000 a=mid:3 Video stream with IP Preference m=video RTP/AVP 98 c=in IP b=tias: a=rtpmap:97 H264/90000 a=mid:4 Video stream with IP Preference BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 61

62 Voice and Video Call - Answer SDP with ANAT group a=group:anat 1 Audio Stream with IP address a=group:anat 3 Video Stream with IP address m=audio RTP/AVP 8 c=in IP6 2001:db8:123:1:128c:cfff:fe75:8208 a=rtpmap:9 PCMA/8000 a=mid:1 m=audio 0 RTP/AVP 8 c=in IP a=rtpmap:8 PCMA/8000 a=mid:2 m=video RTP/AVP 98 c=in IP6 2001:db8:123:1:128c:cfff:fe75:8208 b=tias: a=rtpmap:126 H264/90000 a=mid:3 m=video 0 RTP/AVP 98 c=in IP a=rtpmap:97 H264/90000 a=mid:4 BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 62

63 IP SIP Gateways and Trunks Alternative Network Address Types (ANAT) Media Mismatch SIP INVITE w/o SDP (Delayed Offer) Supported : sdp-anat ACK with SDP (ANSWER) m=audio RTP/AVP 0 c=in IP (OK) with SDP (OFFER) m=audio RTP/AVP 0 c=in IP MTP If Early Offer is configured : If Delayed Offer is configured : sdp-anat is sent in the Require : SIP Header sdp-anat is sent in the Supported : SIP Header If sdp-anat sent in : Require header Supported header far end must send both IP and IP addresses (MTPs are likely to be required) far end should send both IP and IP addresses (MTPs may be required) For Delayed Offer - If a media mismatch occurs CUCM will insert an MTP to convert from IP IP BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 63

64 IP SIP Trunks Configuring IP and ANAT SIP INVITE w/o SDP (Delayed Offer) Supported : sdp-anat 200 (OK) with SDP m=audio RTP/AVP 0 c=in IP m=audio RTP/AVP 0 c=in IP db8:aaaa::0987:65ff:fe01:234b ACK with SDP m=audio RTP/AVP 0 c=in IP Cisco and/or its affiliates. All rights reserved. Cisco Public

65 IP CUCM SIP Trunk Configuration Common Device Configuration Applies Addressing Mode and Signalling preference settings Recommended Addressing Mode : IP and IP Recommended Trunk Configuration SIP Delayed Offer with ANAT for Voice & Video SIP Trunk with ANAT IP or IP Destination Addresses If IP Destination Address is an SRV Cluster wide DNS address must be configured SIP Profile Applies ANAT setting 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public

66 CUCM SIP Trunks - Voice & Video IP Recommendations IP Only SIP Trunk Standard Configuration IP Only SIP Trunk Addressing Mode - IP Only Signalling Mode Preference IP No ANAT IP Trunk destination address or server name (for signalling) SIP Delayed Offer only for Voice and Video calls Dual Stack SIP Trunk with ANAT Addressing Mode - IP and IP Signalling Mode Preference IP or IP ANAT Enabled IP or IP Trunk destination address or server name SIP Delayed Offer only for Voice and Video calls In all cases - Determine the far end Trunk device s capabilities : e.g. IOS Gateways : Always send SIP Early Offer - Can accept SIP Early and Delayed Offer calls. (Once the IOS SIP stack is configured as Dual Stack - ANAT is automatically enabled) IOS IP VOIP implementation Guide at BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 67

67 IP CUCM Dual Stack SIP Trunks Delayed and Early Offer support Voice and Video Deployment Scenarios and Operation For CUCM SIP Trunks You must use Delayed Offer on SIP Trunks for Voice and Video calls SIP EO for voice and video - Mandatory (insert MTP if needed) does not support IP SIP EO for voice and video - Best Effort (No MTP inserted) does not support IP If MTP Required is used for Early Offer Only Voice calls are supported SIP Trunk Configuration Options Dual Stack SIP Trunk - Delayed Offer Dual Stack SIP Trunk - Early Offer MTP Required Voice and Video Voice Only If Early Offer is configured : sdp-anat is sent in the Require : SIP Header If Delayed Offer is configured : sdp-anat is sent in the Supported : SIP Header If sdp-anat sent in : Require Header far end must send both IP and IP addresses (MTPs may be required) Supported Hedaer far end should send both IP and IP addresses (MTPs not required) BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 68

68 Agenda IP Addressing summary IP and UC Networks summary IP Addressing and Cisco devices DHCP and DNS for IP IP Campus and WAN Deployment Options IP UC Configuration CUCM IP Device Configuration Parameters and Media Handling Other IP Design Considerations IP UC Deployment Guidelines Summary

69 IP Media Termination Points (MTPs) For Media IP Address Translation IP IP MTP Supported MTPs for IP Address Translation IOS H/W MTPs (NM-HDV2 with PVDM2, PVDM DSPs) and IOS S/W MTPs support SRTP MTP SRTP IP IP Media Translation for devices with mis-matched media address settings MTPs use the pass-through codec - Encrypted media also supported MTP With IOS release 15.3(2)T Media Termination Points support up to 16 media channels per call SIP Trunk Audio Main Video Slide Video Binary Floor Control Far End Camera Control 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public

70 Effect of IP Enterprise Parameter Settings on MTP Selection Cluster-wide Addressing Mode Preference for Media value = IP MTP Cluster-wide Addressing Mode Preference for Media value = IP MTP Cluster-wide Addressing Mode Preference for Media value = IP BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 71

71 IP Media Stream Services, Transcoding and IOS based Audio Conferencing MOH CUCM IP Voice Media Streaming Service (IPVMS) Supports IP and IP Unicast MOH IP Multicast MOH is not supported ANN CUCM IPVMS Supports IP and IP Annunciator MTP CONF Audio Conferencing resources IOS conf supports IP media streams only MTP inserted to convert from IP to IP CUCM conf supports IP and IP XCODE IOS based Audio Transcoding resources Supports IP & IP media streams BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 72

72 IP UC Encrypted Signaling and Media TLS TLS SRTP MTP SRTP CUCM supports Encrypted calls between IP Phones, Gateways and over CUCM Trunks. SRTP SRTP IP capable IP Phones, SIP Trunks SIP/SCCP Gateways and use TLS and SRTP SRTP MTPs can be dynamically inserted for IP <-> IP conversion of encrypted voice media. MTPs use the pass-through codec to transparently pass SRTP streams. BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 73

73 IP CUCM Dual Stack Deployments - Devices SIP Trunks H323 ICT Trunks IP/IP IP Only Jabber Mobile Clients SRST Soft Phones ISR Analogue Ports CUCME (SCCP Phones Only) SIP TelePresence Endpoints VG Analogue Gateways CUBE / SIP Gateways Newer SIP based Phones Older SCCP based Phones Cisco Expressway C/E Newer SCCP based Phones Older SIP based Phones MGCP / H Cisco and/or Gateways its affiliates. All rights reserved. Cisco Public

74 IP CUCM Dual Stack Deployments - Devices SIP Trunks H323 ICT Trunks IP/IP IP Only Jabber Mobile Clients Soft Phones For Dual Stack deployments MTPs are not required as CUCM will select the common addressing type for media i.e. IP SRST CUCME (SCCP Phones Only) SIP TelePresence Endpoints CUBE / SIP Gateways Newer SIP based Phones Cisco Expressway C/E Newer SCCP based Phones MGCP / H323 Gateways 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public

75 IP Dual Stack Deployments - Applications SIP Trunks H323 ICT Trunks IP/IP IP Only Cisco Meetings Server Cisco Emergency Responder Telepresence Server Directory Cisco Prime Collaboration Suite TelePresence Endpoints IM&P Cisco Webex Meeting Server Newer SIP based Phones Newer SCCP based Phones Unified Contact Centre Unity Express IOS based DHCP/ DNS Unity Connection 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public

76 IP Dual Stack Deployments - Applications SIP Trunks H323 ICT Trunks IP/IP IP Only Cisco Meetings Server Telepresence Server For Dual Stack deployments MTPs are not required as CUCM will select the common addressing type for media i.e. IP Cisco Emergency Responder Cisco Prime Collaboration Suite TelePresence Endpoints Cisco Webex Meeting Server Newer SIP based Phones IOS based DHCP/ DNS Newer SCCP based Phones Unity Connection 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public

77 IP CUCM Deployment Models and Call Admission Control SIP Trunk IP & IP WAN Supported Dual Stack Deployment Models Single Site Call Processing Multiple Site Distributed Call Processing Multiple Site Centralized Call Processing SRST Supports IP only today Dual Stack Phones fail-over to IP for SRST Call Admission Control (CAC) Use CUCM Locations based CAC CUCM Locations based CAC accounts for IP bandwidth overhead (20 additional bytes per packet ) No Support for RSVP CAC today BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 78

78 Agenda IP Addressing summary IP and UC Networks summary IP Addressing and Cisco devices DHCP and DNS for IP IP Campus and WAN Deployment Options IP UC Configuration CUCM IP Device Configuration Parameters and Media Handling Other IP Design Considerations IP UC Deployment Guidelines Summary

79 IP Deployment Options Separate Dual Stack Cluster IP WAN PSTN Single Site Deployment Model for dual stack deployment Separate Dual Stack CUCM cluster connected to production IP only cluster IP WAN between clusters IP Trunk between clusters In the Dual Stack cluster - IP or Dual Stack for Phones and Gateways Dual Stack IP Phones Addressing Mode set to IP and IP Signaling Preference IP Cluster-wide Media preference (IP) BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 80

80 IP Deployment Options Centralized Call Processing IP & IP WAN PSTN SRST Multiple Site Centralized Call Processing Single Dual Stack CUCM cluster with multiple dual stack remote sites Dual Stack WAN IP or Dual Stack Phones and Gateways Dual Stack IP Phones Addressing Mode set to IP and IP Signaling Preference IP, Cluster-wide Media preference (IP) Locations based Call Admission Control IP voice and video support Note SRST supports IP only Dual stack Phones revert IP in SRST mode BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 81

81 IP Deployment Options Multiple Dual Stack Clusters IP & IP WAN PSTN Multi Site Distributed Call Processing Deployment Model Multiple Dual Stack CUCM clusters connected via a Dual Stack WAN IP or Dual Stack Phones and Gateways IP and IP WAN between clusters Dual Stack IP Phones Addressing Mode set to IP and IP Inter Cluster SIP trunks Dual stack, Delayed Offer, ANAT Enabled Signaling Preference IP, Cluster-wide Media preference set to IP Locations based Call Admission Control IP voice and video supported BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 82

82 Agenda IP Addressing summary IP and UC Networks summary IP Addressing and Cisco devices DHCP and DNS for IP IP Campus and WAN Deployment Options IP UC Configuration CUCM IP Device Configuration Parameters and Media Handling Other IP Design Considerations IP UC Deployment Guidelines Summary

83 Summary Demand for IP only UC networks is increasing Today Dual Stack is your best approach for Cisco Collaboration CTG are planning to deliver broader IP only support across our collaboration products this year

84 Recommended Reading Collaboration SRND IP for UC Whitepaper Cisco Press Books Deploying IP Networks Cisco Self Study Implementing Cisco IP Networks IP Security - Scott Hogg, Eric Vyncke BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 85

85 Complete Your Online Session Evaluation Please complete your Online Session Evaluations after each session Complete 4 Session Evaluations & the Overall Conference Evaluation (available from Thursday) to receive your Cisco Live T-shirt All surveys can be completed via the Cisco Live Mobile App or the Communication Stations Don t forget: Cisco Live sessions will be available for viewing on-demand after the event at CiscoLive.com/Online BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 86

86 Call to Action: Learning more about IP LTRSEC-3004 Advanced IOS IPSec VPN with FlexVPN hands-on Lab Tue 09:00:00 BRKIP Addressing Networking challenges with latest Innovations in IP Tue 11:15:00 BRKRST-2337 OSPF Deployment in Modern Networks Tue 11:15:00 BRKEWN-2010 Design and Deployment of Enterprise WLANs Tue 14:15:00 BRKSEC-2501 Deploying AnyConnect SSL VPN with ASA5500 Tue 14:15:00 LTRRST-2005 Introductory - LISP Cloud extension, VPN and DC Mobility Tue 14:15:00 BRKRST-2116 Intermediate - IP from Intro to Intermediate Tue 14:15:00 BRKRST-2022 IP Routing Protocols Update Tue 16:45:00 BRKSPG-2061 IP Deployment Best Practices for the Cable Access Network Wed 09:00:00 BRKRST-3045 LISP - A Next Generation Networking Architecture Wed 09:00:00 LABSPG-7122 Advanced IP Routing and services lab Wed 09:00:00 BRKSEC-3200 Advanced IP Security Threats and Mitigation Wed 11:30:00 BRKIPM-2239 Multicast and Segment Routing Wed 14:30:00 BRKIP IP for the World of IoT Wed 16:30:00 LABIPM-2007 Intermediate - IP Hands on Lab Thu 09:00:00 BRKSEC-3003 Advanced IP Security in the LAN Thu 11:30:00 BRKRST-2336 EIGRP Deployment in Modern Networks Thu 11:30:00 LABSPG-7122 Advanced IP Routing and services lab Thu 14:00:00 BRKRST-2045 BGP operational security best practices Thu 14:30:00 BRKCOL-2020 IP in Enterprise Unified Communications Networks Thu 14:30:00 LABIPM-2007 Intermediate - IP Hands on Lab Fri 09:00:00 BRKRST-2301 Intermediate - Enterprise IP Deployment Fri 09:00:00 BRKSPG-2602 IP Exhaustion: NAT and Transition to IP for Service Providers Fri 11:30:00 Lunch and Learn: IP in the Enterprise: Tue 13:00 All Things IP: Wed 13:00 Experiment with IP-only WiFi: SSID: CL-NAT64 WPA passphrase: cl-nat64 SLAAC + stateless DHCP NAT64 included to access legacy Ask all World of Solutions exhibitors for their IP support DevNet Zone: IP Content Networking + ask other demos BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 87

87 Continue Your Education Demos in the Cisco campus Walk-in Self-Paced Labs Lunch & Learn Meet the Engineer 1:1 meetings Related sessions BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 88

88 Q & A

89 Thank You

90

91 Appendix

92 Jabber IP Only CSR 11.5 DNS64, NAT64 and MRA Operation

93 Drivers for Jabber IP Only development Announcment by Apple of IP Only support Supporting IP in ios 9 August 28, 2015 At WWDC 2015 we announced that ios 9 will support IP-only network services. All apps submitted to the App Store must support IP starting in early To make sure your app is compatible, use the networking frameworks (e.g., NSURLSession ), avoid use of IP-specific APIs, and avoid hard-coded IP addresses. Before submitting your app, test for compatibility. Jabber platforms supporting IP Only : Desktop : Windows, Mac Mobile : ios, Android, Windows BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 94

94 IP Jabber - Expressway behaviour Initial connection ACME.COM DNS Record Type Entry Resolves To SRV Record _collab-edge._tls.acme.com Expressway E.acme.com A Record Expressway E.acme.com SRV Query _collab-edge._tls.acme.com Expressway E.acme.com Src Dst Src Dst DNS A Query Expressway E.acme.com CUCM Expressway C Expressway E Establish TLS connection Src Dst BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 95

95 IP Jabber - Expressway behaviour DNS64 ACME.COM DNS Record Type Entry Resolves To SRV Record _collab-edge._tls.acme.com Expressway E.acme.com AAAA Record Expressway E.acme.com NULL A Record Expressway E.acme.com CUCM Src Dst Expressway C Src Dst Expressway E DNS AAAA Expressway E.acme.com NULL A Expressway E.acme.com DNS64 IANA Well Known Prefix 64:FF9B::/96 AAAA Query Expressway E.acme.com Synthesize IP Address 64:FF9B:: :0ABC::0A:0B:0C:01 DNS64 uses the IANA assigned Well Know Prefix 64:FF9B::/96 to synthesize an IP address from an IP address. The last 32 bits of the IP address use the IP address values to create the IP Host ID in Hex (Hex values not shown for simplicity) BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 96

96 IP Jabber - Expressway behaviour NAT64 ACME.COM CUCM Src Dst Expressway C Src Dst Expressway E X Src 2001:0ABC::0A:0B:0C:01 Dst 64:FF9B:: :0ABC::0A:0B:0C:01 BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 97

97 IP Jabber - Expressway behaviour NAT64 ACME.COM Src Dst Src Dst Src Dst Src 2001:0ABC::0A:0B:0C:01 Dst 64:FF9B:: CUCM Expressway C Expressway E NAT :0ABC::0A:0B:0C:01 IP Address Advertise Well Known Prefix 64:FF9B::/96 NAT64 router advertises Well Known Prefix 64:FF9B::/96 Uses Stateful NAT64 (Similar to PAT) NAT64 does not translate embedded/ literal IP addresses e.g. In SIP headers, SDP etc (NAT64 is not an ALG and in any case cannot decrypt TLS signalling) BRKCOL Cisco and/or its affiliates. All rights reserved. Cisco Public 98