Portreferenceoplysninger for Webex Calling

A correctly configured firewall and proxy are essential for a successful Calling deployment. Webex Calling uses SIP and HTTPS for call signaling and the associated addresses and ports for media, network connection, and gateway connectivity as Webex Calling is a global service.

Not all firewall configurations require ports to be open. However, if you're running inside-to-outside rules, you must open ports for the required protocols to let out services.

Network Address Translation (NAT)

Network Address Translation (NAT) and Port Address Translation (PAT) functionality are applied at the border between two networks to translate address spaces or to prevent the collision of IP address spaces.

Organizations use gateway technologies like firewalls and proxies that provide NAT or PAT services to provide internet access to Webex App applications or Webex devices that are on a private IP address space. These gateways make traffic from internal Apps or Devices to the internet appear to be coming from one or more publicly routable IP addresses.

If deploying NAT, it’s not mandatory to open an inbound port on the firewall.
Validate the NAT pool size required for App or Devices connectivity when multiple app users and devices access Webex Calling & Webex aware services using NAT or PAT. Ensure that adequate public IP addresses are assigned to the NAT pools to prevent port exhaustion. Port exhaustion contributes to internal users and devices being unable to connect to the Webex Calling and Webex Aware services.
Define reasonable binding periods and avoid manipulating SIP on the NAT device.
Configure a minimum NAT timeout to ensure proper operation of devices. Eksempel: Cisco phones send a follow-up REGISTER refresh message every 1-2 minutes.
If your network implements NAT or SPI, then set a larger timeout (of at least 30 minutes) for the connections. This timeout allows reliable connectivity while reducing the battery consumption of the users' mobile devices.

SIP Application Layer Gateway

If a router or firewall is SIP Aware, that is the SIP Application Layer Gateway (ALG) or similar is enabled, we recommend that you turn off this functionality to maintain correct operation of service.

Check the relevant manufacturer's documentation for steps to disable SIP ALG on specific devices.

Proxy support for Webex Calling

Organizations deploy an internet firewall or internet proxy and firewall, to inspect, restrict, and control the HTTP traffic that leaves and enters their network. Thus protecting their network from various forms of cyberattacks.

Proxies perform several security functions such as:

Allow or block access to specific URLs.
Brugerbekræftelse
IP address/domain/hostname/URI reputation lookup
Traffic decryption and inspection

On configuring the proxy feature, it applies to all the applications that use the HTTP's protocol.

The Webex App and Webex device applications include the following:

Webex-tjenesteydelser
Customer device activation (CDA) procedures using Cisco Cloud provisioning platform such as GDS, EDOS device activation, provisioning & onboarding to Webex cloud.
Certificate Authentication
Firmware Upgrades
Status Reports
PRT Uploads
XSI Services

If a proxy server address is configured, then only the Signaling traffic (HTTP/HTTPS) is sent to the proxy server. Clients that use SIP to register to the Webex Calling service and the associated media aren’t sent to the proxy. Therefore, allow these clients to go through the firewall directly.

Supported Proxy Options, configuration & Authentication types

The supported proxy types are:

Explicit Proxy (inspecting or noninspecting)—Configure the clients either App or Device with explicit proxy to specify the server to use.
Transparent Proxy (noninspecting)—The Clients aren’t configured to use a specific proxy server address and don’t require any changes to work with a noninspecting proxy.
Transparent Proxy (inspecting)—The Clients aren’t configured to use a specific proxy server address. No HTTP's configuration changes are necessary; however, your clients either App or Devices need a root certificate so that they trust the proxy. The IT team uses the inspecting proxies to enforce policies on the websites to visit and the types of content that aren’t permitted.

Configure the proxy addresses manually for the Cisco devices and the Webex App using:

Platform OS
Device UI
Automatically discovered using Web Proxy mechanisms such as:
- Web Proxy Auto Discovery (WPAD) - Web Proxy Auto Discovery Protocol
- Proxy Auto Config (PAC) files - Proxy Auto-Config Files

While configuring your preferred product types, choose from the following Proxy configurations & authentication types in the table:

Produkt	Proxykonfiguration	Godkendelsestype
Webex til Mac	Manuel, WPAD, PAC	No Auth, Basic, NTLM,^†
Webex til Windows	Manuel, WPAD, PAC, GPO	No Auth, Basic, NTLM, ^†, Negotiate ^†
Webex til iOS	Manuel, WPAD, PAC	Ingen godk., grundlæggende, Digest, NTLM
Webex til Android	Manuel, PAC	Ingen godk., grundlæggende, Digest, NTLM
Webex-webapp	Supported through OS	No Auth, Basic, Digest, NTLM, Negotiate ^†
Webex-enheder	WPAD, PAC eller manuel	Ingen godk., grundlæggende, Digest
Cisco IP-telefoner	Manuel, WPAD, PAC	Ingen godk., grundlæggende, Digest
Webex Video Mesh Node	Manuel	Ingen godk., grundlæggende, Digest, NTLM

For legends in the table:

^†Mac NTLM Auth - Machine need not be logged on to the domain, user prompted for a password
^†Windows NTLM Auth - Supported only if a machine is logged onto the domain
Negotiate ^†- Kerberos with NTLM fallback auth.
To connect a Cisco Webex Board, Desk, or Room Series device to a proxy server, see Connect your Board, Desk, or Room Series device to a proxy server.
For Cisco IP phones, see Set Up a Proxy Server as an example for configuring the proxy server and settings.

For No Authentication, configure the client with a proxy address that doesn’t support authentication. When using Proxy Authentication, configure with valid credentials. Proxyer, der undersøger webtrafik, kan forstyrre WebSocket-forbindelser. If this problem occurs, bypassing the not inspecting traffic to *.Webex.com might solve the problem. If you already see other entries, add a semicolon after the last entry, and then enter the Webex exception.

Proxy settings for Windows OS

Microsoft Windows support two network libraries for HTTP traffic (WinINet and WinHTTP) that allow Proxy configuration.WinINet is a superset of WinHTTP.

WinInet is designed for single-user, desktop client applications
WinHTTP is designed primarily for multiuser, server-based applications

When selecting between the two, choose WinINet for your proxy configuration settings. For details, see wininet-vs-winhttp.

Refer to Configure a list of allowed domains to access Webex while on your corporate network for details on the following:

To ensure that people only sign in to applications using accounts from a predefined list of domains.
Brug en proxyserver til at opsnappe anmodninger og begrænse de domæner, der er tilladt.

Proxy-inspektion og certifikatfastgørelse

The Webex App and Devices validate the certificates of the servers when they establish the TLS sessions. Certificate checks that such as the certificate issuer and digital signature rely on verifying the chain of certificates up to the root certificate. To perform the validation checks, the Webex App and Devices use a set of trusted root CA certificates installed in the operating system trust store.

If you have deployed a TLS-inspecting Proxy to intercept, decrypt and inspect Webex Calling traffic. Ensure that the certificate the Proxy presents (instead of the Webex service certificate) is signed by a certificate authority, and the root certificate is installed in the trust store of your Webex App or Webex device.

For Webex App - Install the CA certificate that is used to sign the certificate by the proxy in the operating system of the device.
For Webex Room devices and Cisco multiplatform IP Phones - Open a service request with the TAC team to install the CA certificate.

This table shows the Webex App and Webex Devices that support TLS inspection by Proxy servers

Produkt	Understøtter brugerdefinerede nøglecentre til TLS-inspektion
Webex-app (Windows, Mac, iOS, Android og web)	Ja
Webex Room-enheder	Ja
Cisco IP Multiplatform (MPP) Phones	Ja

Firewall configuration

Cisco supports Webex Calling and Webex Aware services in secure Cisco and Amazon Web Services (AWS) data centers. Amazon has reserved its IP subnets for Cisco’s sole use, and secured the services located in these subnets within the AWS virtual private cloud.

Configure your firewall to allow communication from your devices, App's applications, and internet-facing services to perform their functions properly. This configuration allows access to all the supported Webex Calling and Webex Aware cloud services, domain names, IP addresses, Ports, and protocols.

Whitelist or open access to the following so that the Webex Calling and Webex Aware services function correctly.

The URLs/Domains mentioned under the section Domains and URLs for Webex Calling Services
IP subnets, Ports, and Protocols mentioned under the section IP Subnets for Webex Calling Services
If you're using the Webex Suite of cloud collaboration services within their organization, Webex Meetings, Messaging, Webex attendant console and other services then ensure you have the IP subnets, Domains/URLs mentioned in these articles are open Network Requirements for Webex Services and Network requirements for Attendant console

If you’re using only a firewall, then filtering Webex Calling traffic using IP addresses alone isn’t supported as some of the IP address pools are dynamic and may change at any time. Update your rules regularly, failing to update your firewall rules list could impact your users' experience. Cisco doesn’t endorse filtering a subset of IP addresses based on a particular geographic region or cloud service provider. Filtering by region can cause severe degradation to your calling experience.

Bemærk: Cisco doesn't maintain dynamically changing IP address pools hence it isn’t listed in this article.

If your firewall doesn’t support Domain/URL filtering, then use an Enterprise Proxy server option. This option filters/allows by URL/domain the HTTPs signaling traffic to Webex Calling and Webex Aware services in your Proxy server, before forwarding to your firewall.

You can configure traffic using port and IP subnet filtering for call media. Since the media traffic requires direct access to the internet, choose the URL filtering option for signaling traffic.

For Webex Calling, UDP is Cisco’s preferred transport protocol for media, and it recommends using only SRTP over UDP. TCP and TLS as transport protocols for media aren’t supported for Webex Calling in production environments. The connection-orientated nature of these protocols affects media quality over lossy networks. If you have queries regarding the transport protocol, raise a support ticket.

Domains and URLs for Webex Calling services

A * shown at the beginning of a URL (for example, *.webex.com) indicates that services in the top-level domain and all subdomains are accessible.

Domæne/URL-adresse	Beskrivelse	Webex-apps og -enheder, der bruger disse domæner/URL-adresser
Cisco Webex-tjenesteydelser
*.broadcloudpbx.com	Webex-godkendelsens mikrotjenester til krydsstart fra Control Hub til opkaldsadministratorportalen.	Control Hub
*.broadcloud.com.au	Webex Calling-tjenester i Australien.	Alle
*.broadcloud.eu	Webex Calling-tjenester i Europa.	Alle
*.broadcloudpbx.net	Opkaldsklientkonfiguration og administrationstjenester.	Webex-apps
.webex.com .cisco.com	Core Webex Calling & Webex Aware services Identity provisioning Identity storage Bekræftelse OAuth services Onboarding af enheder Cloud Connected UC When a phone connects to a network for the first time or after a factory reset with no DHCP options set, it contacts a device activation server for zero touch provisioning. New phones use activate.cisco.com and phones with firmware release earlier than 11.2(1), continue to use webapps.cisco.com for provisioning. Download the device firmware and locale updates from binaries.webex.com. Allow Cisco Multiplatform phones (MPPs) older than 12.0.3 version to access sudirenewal.cisco.com through port 80 to renew Manufacturer Installed Certificate (MIC) and have a Secure Unique Device Identifier (SUDI). For details, see Field notice.	Alle
*.ucmgmt.cisco.com	Webex Calling-tjenester	Control Hub
.wbx2.com og .ciscospark.com	Used for cloud awareness to reach out to Webex Calling & Webex Aware services during and after onboarding. These services are necessary for Apps and Devices management Apps Application notification mechanism service management	Alle
*.webexapis.com	Webex microservices that manage your Webex App applications and Webex devices. Profile picture service Whiteboarding service Proximity service Presence service Registration service Calendaring service Search service	Alle
*.webexcontent.com	Webex Messaging services related to general file storage including: User files Transcoded files Billeder Screenshots Whiteboard content Client & device logs Profilbilleder Branding logos Log files Bulk CSV export files & import files (Control Hub)	Webex Apps Messaging services. File storage using webexcontent.com replaced by clouddrive.com in October 2019
*.accompany.com	People insights integration	Webex-apps
Additional Webex-Related Services (Third-Party Domains)
.appdynamics.com .eum-appdynamics.com	Sporing af præstation, registrering af fejl og nedbrud, sessionsmålinger.	Control Hub
*.sipflash.com	Device management services. Firmware upgrades and secure onboarding purposes.	Webex-apps
.walkme.com .walkmeusercontent.com	Webex-brugervejledningsklient. Bruges til onboarding af og brugsanvisninger til nye brugere. Klik her for yderligere oplysninger om WalkMe.	Webex-apps
.google.com .googleapis.com	Notifications to Webex apps on mobile devices (Example: new message, when call is answered) For IP Subnets, refer to these links Google Firebase Cloud Messaging (FCM) service Apple Push Notification Service (APNS) For APNS, Apple lists the IP subnets for this service.	Webex-app

IP Subnets for Webex Calling services

IP Subnets for Webex Calling Services^*^†

23.89.0.0/16	85.119.56.0/23	128.177.14.0/24
128.177.36.0/24	135.84.168.0/21	139.177.64.0/21
139.177.72.0/23	144.196.0.0/16	150.253.128.0/17
163.129.0.0/17	170.72.0.0/16	170.133.128.0/18
185.115.196.0/22	199.19.196.0/23	199.19.199.0/24
199.59.64.0/21

Tilslutningsformål	Kildeadresser	Kildeporte	Protocol	Destinationsadresser	Destinationsporte	Bemærkninger
Opkalds signal til Webex-opkald (SIP TLS)	Ekstern lokal gateway (NIC)	8000-65535	TCP	Se IP-undernet for Webex Calling-tjenester.	5062, 8934	These IPs/ports are needed for outbound SIP-TLS call signaling from Local Gateways, Devices, and Webex App Applications (Source) to Webex Calling Cloud (Destination). Port 5062 (required for Certificate-based trunk). And port 8934 (required for Registration-based trunk
	Enheder	5060-5080			8934
	Webex-app	Kortvarig (OS-afhængig)			8934
Call signaling from Webex Calling (SIP TLS) to Local Gateway	Webex Calling address range. Refer to IP Subnets for Webex Calling Services	8934	TCP	IP or IP range chosen by customer for their Local Gateway	Port or port range chosen by customer for their Local Gateway	Applies to certificate-based local gateways. It is required to establish a connection from Webex Calling to a Local Gateway. A Registration-based local gateway works on reusing a connection created from the local gateway. Destination port is customer chosen Configure trunks
Call media to Webex Calling (STUN, SRTP/SRTCP, T38)	Ekstern lokal gateway (NIC)	8000-48199^†^*	UDP	Se IP-undernet for Webex Calling-tjenester.	5004, 9000 (STUN Ports) Lyd: 8500-8599 Video: 8600-8699 19560-65535 (SRTP over UDP)	These IPs/ports are used for outbound SRTP call media from Local Gateways, Devices, and Webex App Applications (Source) to Webex Calling Cloud (Destination). For Calls within the organization where STUN, ICE negotiation is successful, the media relay in the cloud is removed as the communication path. In such cases the media flow is directly between the user's Apps/devices. For eksempel: If media optimization is successful, Webex App sends media directly between one another on port ranges 8500–8699 and devices send media directly to one another on ports ranges 19560–19661. For certain network topologies where firewalls are used within a customer premise, allow access for the mentioned source and destination port ranges inside your network for the media to flow through. Eksempel: For webex App, allow the source and destination port range Audio:8500-8599 Video:8600-8699
	Devices^†^*	19560-19661
	Webex App^†^*	Lyd: 8500-8599 Video: 8600-8699
Call media from Webex Calling (SRTP/SRTCP, T38)	Webex Calling address range. Refer to IP Subnets for Webex Calling Services	19560-65535 (SRTP over UDP)	UDP	IP or IP range chosen by customer for their Local Gateway	Media port range chosen by customer for their Local Gateway
Opkaldssignal til PSTN-gateway (SIP TLS)	Intern lokal gateway (NIC)	8000-65535	TCP	Din ITSP PSTN GW eller Unified CM	Afhænger af PSTN-muligheden (f.eks. typisk 5060 eller 5061 for Unified CM)
Call media to PSTN gateway (SRTP/SRTCP)	Intern lokal gateway (NIC)	8000-48199^†^*	UDP	Din ITSP PSTN GW eller Unified CM	Depends on the PSTN option (for example, typically 5060 or 5061 for Unified CM)
Enhedskonfiguration og firmwareadministration (Cisco-enheder)	Webex-opkald enheder	Kortvarig	TCP	3.20.185.219 3.130.87.169 3.134.166.179 52.26.82.54 72.163.10.96/27 72.163.15.64/26 72.163.15.128/26 72.163.24.0/23 72.163.10.128/25 173.37.146.128/25 173.36.127.0/26 173.36.127.128/26 173.37.26.0/23 173.37.149.96/27 192.133.220.0/26 192.133.220.64/26	443, 6970, 80	Required for the following reasons: Migrating from Enterprise phones (Cisco Unified CM) to Webex Calling. See upgrade.cisco.com for more information. The cloudupgrader.webex.com uses ports: 6970,443 for the firmware migration process. Firmware upgrades and secure onboarding of devices (MPP and Room or Desk phones) using the 16-digit activation code (GDS) For CDA / EDOS - MAC address-based provisioning. Bruges af enheder (MPP-telefoner, ATA'er og SPA ATA'er) med nyere firmware. For Cisco ATAs ensure that the devices are on the minimum firmware of 11.1.0MSR3-9. When a phone connects to a network for the first time or after a factory reset, without the DHCP options set, it contacts a device activation server for zero touch provisioning. New phones are use activate.cisco.com instead of webapps.cisco.com for provisioning. Phones with firmware released earlier than 11.2(1) continue to use webapps.cisco.com. It’s recommended to allow all these IP subnets. Allow Cisco Multiplatform phones (MPPs) older than 12.0.3 version to access sudirenewal.cisco.com through port 80 for renewing the Manufacturer Installed Certificate (MIC) and having a Secure Unique Device Identifier (SUDI). For details, see Field Notice
Webex App configuration	Webex App applications	Kortvarig	TCP	62.109.192.0/18 64.68.96.0/19 150.253.128.0/17 207.182.160.0/19	443, 8443	Used for Id broker Authentication, Webex App configuration services for clients, Browser based web access for self-care AND Administrative interface access. The TCP port 8443 is used by Webex App on Cisco Unified CM setup for downloading configuration. Only customers who use the setup to connect to Webex Calling must open the port.
Synkronisering af enhedstid (NTP)	Webex-opkald enheder	51494	UDP	Se IP-undernet for Webex Calling-tjenester.	123	Disse IP-adresser er nødvendige for synkronisering af klokkeslæt for enheder (MPP-telefoner, ATA'er og SPA ATA'er)
Domain Name System (DNS) resolution	Webex Calling devices, Webex App, and Webex Devices	Kortvarig	UDP og TCP	Værtsdefineret	53	Used for DNS lookups to discover the IP addresses of Webex Calling services in the cloud. Even though typical DNS lookups are done over UDP, some may require TCP, if the query responses can’t fit it in UDP packets.
Netværkstidsprotokol (NTP)	Webex App and Webex Devices	123	UDP	Værtsdefineret	123	Tidssynkronisering
CScan	Web based Network readiness Pre-qualification tool for Webex Calling	Kortvarig	TCP	Se IP-undernet for Webex Calling-tjenester.	8934 and 443	Web based Network readiness Prequalification tool for Webex Calling. Få flere oplysninger på cscan.webex.com.
CScan		Kortvarig	UDP	Se IP-undernet for Webex Calling-tjenester.	19569-19760
Additional Webex Calling & Webex Aware Services (Third-Party)
Push notifications APNS and FCM services	Webex Calling Applications	Kortvarig	TCP	Refer to IP Subnets mentioned under the links Apple Push Notification Service(APNS) Google-Firebase Cloud Messaging (FCM)	443, 2197, 5228, 5229, 5230, 5223	Notifications to Webex Apps on mobile devices (Example: When you receive a new message or when a call is answered)

^†^*CUBE media port range is configurable with rtp-port range.
^†^*Media ports for devices and applications that are dynamically assigned in the SRTP port rages. SRTP ports are even numbered ports, and the corresponding SRTCP port is allocated with the consecutive odd numbered port.
If a proxy server address is configured for your Apps and Devices, the signaling traffic is sent to the proxy. Media transported SRTP over UDP flows directly to your firewall instead of the proxy server.
If you’re using NTP and DNS services within your enterprise network, then open the ports 53 and 123 through your firewall.

Quality of Service (QoS)

Allows you to enable tagging of packets from the local device or client to the Webex Calling cloud platform. QoS enables you to prioritize real-time traffic over other data traffic. Enabling this setting modifies the QoS markings for Apps and devices that use SIP signaling and media.

Source Addresses	Traffic type	Destination Addresses	Kildeporte	Destinationsporte	DSCP Class and value
Webex-app	Lyd	Refer IP subnets, Domains, and URLs for Webex Calling services	8500-8599	8500-8599, 19560-65535	Expedited Forwarding (46)
Webex-app	Video		8600-8699	8600-8699, 19560-65535	Assured Forwarding 41 (34)
Webex-app	Signal		Kortvarig (OS-afhængig)	8934	CS0 (0)
Webex Devices (MPPs and Room)	Lyd og video		19560-19661	19560-65535	Expedited Forwarding (46) & Assured Forwarding 41 (34)
Webex-enheder	Signal		5060-5080	8934	Class Selector 3 (24)

Create a separate QoS profile for Audio and Video/Share since they have different source port range to mark traffic differently.
For Windows Clients: To enable UDP Source Port Differentiation for your organization, contact your local account team. Without enabling, you cannot differentiate between the Audio and Video/Share using the Windows QoS Policies (GPO) because the source ports are the same for audio/video/share. For details, see Enable media source port ranges for Webex App
For Webex Devices, configure the QoS setting changes from the Control Hub device settings. For details, see Configure & modify device settings in Webex-Calling

Webex Meetings/-meddelelser – netværkskrav

For customers who’re using Webex Suite of cloud collaboration services, Webex cloud registered products, onboard the MPP devices to the Webex Cloud for services like Call History, Directory Search, Meetings, and Messaging. Ensure that the Domains/URLs/IP Addresses/Ports mentioned in this article are open Network Requirements for Webex Services.

Netværkskrav til Webex for Government (FedRAMP)

For customers who require the list of Domains, URLs, IP address ranges and ports for Webex for Government services (FedRAMP), information can be found here: Netværkskrav til Webex for Government

Network Requirements for Webex Attendant Console

For customers who are using attendant console - receptionists, attendants, and operators feature, ensure Domains/URLs/IP Addresses/Ports/Protocols are open Network requirements for attendant console

Getting started with Webex Calling Local Gateway

For customers using the Local Gateway solution with Webex Calling for premises-based PSTN and third-party SBCs interoperability, read through the article Get Started with Local Gateway

Referencer

To know What's new in Webex Calling, see What's new in Webex Calling

For Security requirements for Webex Calling, see Article

Webex Calling Media Optimization with Interactive Connectivity Establishment (ICE) Article

Dokumentets revisionshistorik

Dato	Vi har foretaget følgende ændringer i denne artikel
July 25, 2024	Added back the 52.26.82.54 IP subnet as it’s required for the Cisco ATA device configuration and firmware management.
July 18, 2024	Updated with the following details: QoS (TOS/DSCP) values supported for Webex Calling (Apps, Devices) Updated the Network diagram Including the link for network requirements related to Webex Attendant Console.
June 28, 2024	Updated the usage of both SRTP/ SRTCP port ranges for the Webex Calling Media specification.
June 11, 2024	Removed the "huton-dev.com" domain as it’s not used.
May 06, 2024	Updated the usage of both SRTP/ SRTCP port ranges for the Webex Calling Media specification.
April 03, 2024	Updated the IP Subnets for Webex Calling services with 163.129.0.0/17 to accommodate Webex Calling market expansion for the India region.
December 18, 2023	Included the sudirenewal.cisco.com URL and port 80 requirement for device configuration and firmware management of the Cisco MPP phone's MIC renewal.
December 11, 2023	Updated the IP Subnets for Webex Calling services to include a larger set of IP addresses. 150.253.209.128/25 – changed to 150.253.128.0/17
November 29, 2023	Updated the IP Subnets for Webex Calling services to include a larger set of IP addresses to accommodate Webex Calling region expansion for future growth. 144.196.33.0/25 – changed to 144.196.0.0/16 The IP Subnets for Webex Calling services sections under Webex Calling (SIP TLS) and Call media to Webex Calling (STUN, SRTP) is updated for clarity on certificate-based trunking and the firewall requirements for Local Gateway.
14. august 2023	We’ve added the following IP addresses 144.196.33.0/25 and 150.253.156.128/25 to support increased capacity requirements for Edge and Webex Calling Services. This IP range is supported only in the U.S. region.
July 5, 2023	Added the link https://binaries.webex.com to install the Cisco MPP Firmware.
7. marts 2023	We've overhauled the entire article to include: Included options for Proxy support. Modified Calling flow diagram Simplified Domains/URLs/IP subnet portions for Webex Calling and Webex Aware services Added 170.72.0.0/16 IP subnet range for Webex Calling & Webex Aware services. Removed the following ranges 170.72.231.0, 170.72.231.10, 170.72.231.161 and 170.72.242.0/24
5. marts 2023	Updating the article to include the following: Added the UDP-SRTP port range (8500-8700) used by applications. Added the ports for the Push notifications APNS and FCM services. Split the CScan port range for UDP & TCP. Added the references section.
15. november 2022	We’ve added the following IP addresses for device configuration and firmware management (Cisco devices): 170.72.231.0 170.72.231.10 170.72.231.161 We’ve removed the following IP addresses from device configuration and firmware management (Cisco devices): 3.20.118.133 3.20.228.133 3.23.144.213 3.130.125.44 3.132.162.62 3.140.117.199 18.232.241.58 35.168.211.203 50.16.236.139 52.45.157.48 54.145.130.71 54.156.13.25 52.26.82.54 54.68.1.225
November 14, 2022	Added the IP subnet 170.72.242.0/24 for the Webex Calling service.
08. september 2022	The Cisco MPP Firmware transitions to use https://binaries.webex.com as the host URL for MPP firmware upgrades in all regions. Denne ændring forbedrer firmwareopgraderingsydeevnen.
30. august 2022	Removed reference to Port 80 from Device configuration and firmware management (Cisco devices), Application configuration and CScan rows in the Port table as there’s no dependency.
18. august 2022	Ingen ændring i løsningen. Opdaterede destinationsporte 5062 (påkrævet for certifikatbaseret trunk), 8934 (påkrævet for registreringsbaseret trunk) for opkaldssignal til Webex-opkald (SIP TLS).
26. juli 2022	Tilføjede IP-adressen 54.68.1.225, som er påkrævet for firmwareopgradering af Cisco 840/860-enheder.
21. juli 2022	Opdaterede destinationsporte 5062 og 8934 for opkaldssignalering til Webex-opkald (SIP TLS).
14. juli 2022	Added the URLs that support a complete function of Webex Aware services. Added the IP subnet 23.89.154.0/25 for the Webex Calling service.
27. juni 2022	Opdaterede domænet og URL-adresserne for Webex-opkald tjenester: .broadcloudpbx.com .broadcloud.com.au .broadcloud.eu .broadcloudpbx.net
15. juni 2022	Tilføjede følgende porte og protokoller under IP-adresser og porte til Webex-opkald tjenester: Tilslutningsformål: Webex-funktioner Kildeadresser: Webex Calling-enheder Kildeporte: Kortvarig Protokol: TCP Destinationsadresser: Refer to IP Subnets and Domains defined in Webex Meetings/Messaging - Network Requirements. Destinationsporte: 443 Noter: The Webex Calling Devices use these IP addresses and domains to interface with Webex Cloud Services such as Directory, Call History and Meetings. Opdaterede oplysninger i afsnittet Webex Meetings/meddelelser – netværkskrav
24. maj 2022	Tilføjede IP-undernet 52.26.82.54/24 til 52.26.82.54/32 for Webex-opkald tjeneste
6. maj 2022	Tilføjede IP-undernet 52.26.82.54/24 for Webex-opkald tjeneste
7. april 2022	Updated the Local Gateway internal and external UDP port range to 8000-48198^†
5. april 2022	Tilføjede følgende IP-undernet for Webex-opkald tjeneste: 23.89.40.0/25 23.89.1.128/25
29. marts 2022	Tilføjede følgende IP-undernet for Webex-opkald tjeneste: 23.89.33.0/24 150.253.209.128/25
20. september 2021	Tilføjede 4 nye IP-undernet for Webex-opkald tjeneste: 23.89.76.128/25 170.72.29.0/24 170.72.17.128/25 170.72.0.128/25
2. april 2021	Added .ciscospark.com under Domains and URLs for Webex Calling Services* to support Webex Calling use cases in the Webex app.
25. marts 2021	Tilføjede 6 nye IP-intervaller til activate.cisco.com, som vil blive gennemført fra den 8. maj 2021. 72.163.15.64/26 72.163.15.128/26 173.36.127.0/26 173.36.127.128/26 192.133.220.0/26 192.133.220.64/26
4. marts 2021	Udskiftede Webex Calling diskrete IP-adresser og mindre IP-intervaller med forenklede intervaller i en separat tabel for at gøre det nemmere at forstå firewall-konfiguration.
26. februar 2021	Vi tilføjede 5004 som destinationsport for Call-medie til Webex-opkald (STUN, SRTP) for at understøtte INTERACTIVE Connectivity Animation (ICE), som vil være tilgængelige i Webex-opkald i april 2021.
22. februar 2021	Domæner og URL-adresser er nu angivet i en separat tabel. IP Addresses and Ports table are adjusted to group IP addresses for the same services. Adding the Notes column to the IP Addresses and Ports table that aids in understanding the requirements. Moving the following IP addresses to simplified ranges for device configuration and firmware management (Cisco devices): activate.cisco.com 72.163.10.125 -> 72.163.10.96/27 173.37.149.125 -> 173.37.149.96/27 webapps.cisco.com 173.37.146.134 -> 173.37.146.128/25 72.163.10.134 -> 72.163.10.128/25 Adding the following IP addresses for Application Configuration because Cisco Webex client points to a newer DNS SRV in Australia in March 2021. 199.59.64.237 199.59.67.237
21. januar 2021	We’ve added the following IP addresses to device configuration and firmware management (Cisco devices): 3.134.166.179 50.16.236.139 54.145.130.71 72.163.10.125 72.163.24.0/23 173.37.26.0/23 173.37.146.134 We’ve removed the following IP addresses from device configuration and firmware management (Cisco devices): 35.172.26.181 52.86.172.220 52.203.31.41 We’ve added the following IP addresses to the application configuration: 62.109.192.0/19 64.68.96.0/19 207.182.160.0/19 150.253.128.0/17 We’ve removed the following IP addresses from the application configuration: 64.68.99.6 64.68.100.6 We’ve removed the following port numbers from the application configuration: 1081, 2208, 5222, 5280-5281, 52644-52645 We’ve added the following domains to the application configuration: idbroker-b-us.webex.com idbroker-eu.webex.com ty6-wxt-jp.bcld.webex.com os1-wxt-jp.bcld.webex.com
23. december 2020	Tilføjede nye IP-adresser til applikationskonfiguration til portreferencebillederne.
22. december 2020	Opdaterede rækken Applikationskonfiguration i tabellerne til at inkludere følgende IP-adresser: 135.84.171.154 og 135.84.172.154. Hid the network diagrams until these IP addresses are added.
11. december 2020	Opdaterede enhedskonfiguration og firmwareadministration (Cisco-enheder) og rækkerne for applikationskonfiguration for de understøttede canadiske domæner.
16. oktober 2020	Opdaterede opkaldssignalering og medieoptegnelser med følgende IP-adresser: 139.177.64.0/24 139.177.65.0/24 139.177.66.0/24 139.177.67.0/24 139.177.68.0/24 139.177.69.0/24 139.177.70.0/24 139.177.71.0/24 139.177.72.0/24 139.177.73.0/24
23. september 2020	Under CScan, erstattede 199.59.64.156 med 199.59.64.197.
14. august 2020	Tilføjede flere IP-adresser for at understøtte introduktionen af datacentre i Canada: Opkaldssignal til Webex Calling (SIP TLS) – 135.84.173.0/25,135.84.174.0/25, 199.19.197.0/24, 199.19.199.0/24
12. august 2020	Tilføjede flere IP-adresser for at understøtte introduktionen af datacentre i Canada: Opkaldsmedie til Webex Calling (SRTP) – 135.84.173.0/25,135.84.174.0/25, 199.19.197.0/24, 199.19.199.0/24 Call signaling to publicly addressed endpoints (SIP TLS)—135.84.173.0/25,135.84.174.0/25, 199.19.197.0/24, 199.19.199.0/24. Enhedskonfiguration og firmwareadministration (Cisco-enheder) – 135.84.173.155,135.84.174.155 Synkronisering af enhedstid – 135.84.173.152, 135.84.174.152 Applikationskonfiguration – 135.84.173.154, 135.84.174.154
22. juli 2020	Tilføjede følgende IP-adresse for at understøtte introduktionen af datacentre i Canada: 135.84.173.146
9. juni 2020	Vi har foretaget følgende ændringer i CScan-indtastningen: Rettet en af IP-adresserne —ændrede 199.59.67.156 til 199.59.64.156. New features require new ports and UDP—19560-19760.
11. marts 2020	We added the following domain and IP addresses to the application configuration: jp.bcld.webex.com—135.84.169.150 client-jp.bcld.webex.com idbroker.webex.com—64.68.99.6, 64.68.100.6 Vi opdaterede følgende domæner med yderligere IP-adresser til enhedskonfiguration og firmwareadministration: cisco.webexcalling.eu—85.119.56.198, 85.119.57.198 webapps.cisco.com—72.163.10.134 activation.webex.com—35.172.26.181, 52.86.172.220 cloudupgrader.webex.com—3.130.87.169, 3.20.185.219
27. februar 2020	Vi har føjet følgende domæne og porte til enhedskonfiguration og firmwareadministration: cloudupgrader.webex.com—443, 6970