- Home
- /
- Articolo
Informazioni di riferimento porta per Webex Calling
Questo articolo è destinato agli amministratori di rete, in particolare i firewall e gli amministratori di sicurezza proxy che utilizzano i servizi Webex Calling all'interno della propria organizzazione. Descrive i requisiti di rete ed elenca gli indirizzi, le porte e i protocolli utilizzati per connettere i telefoni, l'app Webex e i gateway ai servizi 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. Esempio: 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.
-
Autenticazione utente
-
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:
-
Servizi Webex
-
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:
Prodotto |
Configurazione proxy |
Tipo di autenticazione |
---|---|---|
Webex per Mac |
Manuale, WPAD, PAC |
No Auth, Basic, NTLM,† |
Webex per Windows |
Manuale, WPAD, PAC, GPO |
No Auth, Basic, NTLM, †, Negotiate † |
Webex per iOS |
Manuale, WPAD, PAC |
Nessuna autenticazione, Digest, NTLM |
Webex per Android |
Manuale, PAC |
Nessuna autenticazione, Digest, NTLM |
App Webex Web |
Supported through OS |
No Auth, Basic, Digest, NTLM, Negotiate † |
Dispositivi Webex |
WPAD, PAC o Manuale |
Nessuna autenticazione, base, Digest |
Cisco IP Phone |
Manuale, WPAD, PAC |
Nessuna autenticazione, base, Digest |
Nodo mesh video Webex |
Manuale |
Nessuna autenticazione, 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. I proxy che controllano il traffico Web possono interferire con le connessioni socket Web. 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.
-
Utilizzare una server proxy per intercettare le richieste e limitare i domini consentiti.
Ispezione proxy e blocco certificati
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
Prodotto |
Supporta autorità di certificazioni attendibili personalizzate per il controllo TLS |
---|---|
App Webex (Windows, Mac, iOS, Android, Web) |
Sì |
Dispositivi Webex Room |
Sì |
Cisco IP Multiplatform (MPP) Phones |
Sì |
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.
Nota: 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.
Dominio/URL |
Descrizione |
App e dispositivi Webex che utilizzano questi domini/URL |
---|---|---|
Servizi Cisco Webex | ||
*.broadcloudpbx.com |
Microservizi di autorizzazione Webex per avvio incrociato da Control Hub al portale di amministrazione chiamate. |
Control Hub |
*.broadcloud.com.au |
Servizi Webex Calling in Australia. |
Tutti |
*.broadcloud.eu |
Servizi Webex Calling in Europa. |
Tutti |
*.broadcloudpbx.net |
Configurazione del client di chiamata e servizi di gestione chiamata. |
App Webex |
*.webex.com *.cisco.com |
Core Webex Calling & Webex Aware services
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. |
Tutte |
*.ucmgmt.cisco.com |
Servizi Webex Calling |
Control Hub |
*.wbx2.com e *.ciscospark.com |
Used for cloud awareness to reach out to Webex Calling & Webex Aware services during and after onboarding. These services are necessary for
|
Tutte |
*.webexapis.com |
Webex microservices that manage your Webex App applications and Webex devices.
|
Tutte |
*.webexcontent.com |
Webex Messaging services related to general file storage including:
|
Webex Apps Messaging services. File storage using webexcontent.com replaced by clouddrive.com in October 2019 |
*.accompany.com |
People insights integration |
App Webex |
Additional Webex-Related Services (Third-Party Domains) | ||
*.appdynamics.com *.eum-appdynamics.com |
Monitoraggio delle prestazioni, acquisizione di errori e arresto anomalo, metriche di sessione. |
Control Hub |
*.sipflash.com |
Device management services. Firmware upgrades and secure onboarding purposes. |
App Webex |
*.walkme.com *.walkmeusercontent.com |
Client di guida utente Webex. Fornisce alcune presentazioni sull'onboarding e sull'utilizzo per i nuovi utenti. Per ulteriori informazioni su WalkMe, fai clic qui. |
App Webex |
*.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. | App Webex |
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 |
Scopo connessione: | Indirizzi di origine | Porte di origine | Protocollo | Indirizzi di destinazione | Porte di destinazione | Note | |
---|---|---|---|---|---|---|---|
Segnalazione chiamata a Webex Calling (TLS SIP) | Gateway locale esterno (NIC) | 8000-65535 | TCP | Fai riferimento a Subnet IP per i servizi Webex Calling. | 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 | |
Dispositivi | 5060-5080 | 8934 | |||||
App Webex | Temporaneo (dipendente dal sistema operativo) | ||||||
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) | NIC esterna al gateway locale | 8000-48199†* | UDP | Fai riferimento a Subnet IP per i servizi Webex Calling. |
5004, 9000 (STUN Ports) Audio: 8500-8599 Video: 8600-8699 19560-65535 (SRTP over UDP) |
| |
Devices†* | 19560-19661 | ||||||
Webex App†* |
Audio: 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 | ||
Segnali di chiamata al gateway PSTN (SIP TLS) | NIC interna al gateway locale | 8000-65535 | TCP | La tua PSTN ITSP GW o Unified CM | Dipende dall'opzione PSTN (ad esempio, solitamente 5060 o 5061 per Unified CM) | ||
Call media to PSTN gateway (SRTP/SRTCP) | NIC interna al gateway locale | 8000-48199†* | UDP | La tua PSTN ITSP GW o Unified CM | Depends on the PSTN option (for example, typically 5060 or 5061 for Unified CM) | ||
Configurazione del dispositivo e gestione del firmware (dispositivi Cisco) | Webex Calling dispositivi | Temporaneo | 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:
| |
Webex App configuration | Webex App applications | Temporaneo | 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. | |
Sincronizzazione orario dispositivo (NTP) | Webex Calling dispositivi | 51494 | UDP | Fai riferimento a Subnet IP per i servizi Webex Calling. | 123 | Questi indirizzi IP sono necessari per la sincronizzazione dell'orario per i dispositivi (telefoni MPP, ATA e ATA SPA) | |
Domain Name System (DNS) resolution | Webex Calling devices, Webex App, and Webex Devices | Temporaneo | UDP e TCP | Definito dall'host | 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. | |
Protocollo NTP (Network Time Protocol) | Webex App and Webex Devices | 123 | UDP | Definito dall'host | 123 | Sincronizzazione orario | |
CScan | Web based Network readiness Pre-qualification tool for Webex Calling | Temporaneo | TCP | Fai riferimento a Subnet IP per i servizi Webex Calling. | 8934 and 443 | Web based Network readiness Prequalification tool for Webex Calling. Vai a cscan.webex.com per ulteriori informazioni. | |
UDP | 19569-19760 | ||||||
Additional Webex Calling & Webex Aware Services (Third-Party) | |||||||
Push notifications APNS and FCM services | Webex Calling Applications | Temporaneo | TCP |
Refer to IP Subnets mentioned under the links | 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 | Porte di origine | Porte di destinazione | DSCP Class and value |
---|---|---|---|---|---|
App Webex | Audio |
Refer IP subnets, Domains, and URLs for Webex Calling services | 8500-8599 | 8500-8599, 19560-65535 | Expedited Forwarding (46) |
App Webex | Video | 8600-8699 | 8600-8699, 19560-65535 | Assured Forwarding 41 (34) | |
App Webex | Segnale | Temporaneo (dipendente dal sistema operativo) | 8934 | CS0 (0) | |
Webex Devices (MPPs and Room) | Audio e video | 19560-19661 | 19560-65535 |
Expedited Forwarding (46) & Assured Forwarding 41 (34) | |
Dispositivi Webex | Segnale | 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
Riunioni e messaggi Webex - Requisiti di rete
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.
Requisiti di rete per 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: Requisiti di rete per 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
Riferimenti
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
Cronologia revisioni documenti
Data |
Sono state apportate le seguenti modifiche a questo articolo |
---|---|
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:
|
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 agosto 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 marzo 2023 |
We've overhauled the entire article to include:
|
5 marzo 2023 |
Updating the article to include the following:
|
15 novembre 2022 |
We’ve added the following IP addresses for device configuration and firmware management (Cisco devices):
We’ve removed the following IP addresses from device configuration and firmware management (Cisco devices):
|
November 14, 2022 |
Added the IP subnet 170.72.242.0/24 for the Webex Calling service. |
08 settembre 2022 |
The Cisco MPP Firmware transitions to use https://binaries.webex.com as the host URL for MPP firmware upgrades in all regions. Questa modifica migliora le prestazioni di aggiornamento del firmware. |
Il 30 agosto 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 agosto 2022 |
Nessuna modifica nella soluzione. Aggiornamento delle porte di destinazione 5062 (richiesto per il trunk basato su certificato), 8934 (richiesto per il trunk basato su registrazione) per la segnalazione di chiamata Webex Calling (SIP TLS). |
26 luglio 2022 |
È stato aggiunto l'indirizzo IP 54.68.1.225, richiesto per l'aggiornamento del firmware dei dispositivi Cisco 840/860. |
21 luglio 2022 |
Sono state aggiornate le porte di destinazione 5062, 8934 per la segnalazione di chiamata Webex Calling (SIP TLS). |
14 luglio 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 giugno 2022 |
Aggiornamento del dominio e degli URL per i Webex Calling servizi: *.broadcloudpbx.com *.broadcloud.com.au *.broadcloud.eu *.broadcloudpbx.net |
15 giugno 2022 |
Sono state aggiunte le seguenti porte e protocolli in Indirizzi IP e porte per Webex Calling servizi:
Informazioni aggiornate nella Webex Meetings /Messaggistica - Sezione Requisiti di rete |
24 maggio 2022 |
Aggiunta della subnet IP 52.26.82.54/24 a 52.26.82.54/32 per il servizio Webex Calling |
6 maggio 2022 |
Aggiunta della subnet IP 52.26.82.54/24 per il Webex Calling |
7 aprile 2022 |
Updated the Local Gateway internal and external UDP port range to 8000-48198† |
5 aprile 2022 |
Sono state aggiunte le seguenti subnet IP per Webex Calling servizio:
|
29 marzo 2022 |
Sono state aggiunte le seguenti subnet IP per Webex Calling servizio:
|
20 settembre 2021 |
Aggiunta di 4 nuove subnet IP per Webex Calling servizio:
|
2 aprile 2021 |
Added *.ciscospark.com under Domains and URLs for Webex Calling Services to support Webex Calling use cases in the Webex app. |
25 marzo 2021 |
Sono stati aggiunti 6 nuovi intervalli IP per activate.cisco.com a partire dall'8 maggio 2021.
|
4 marzo 2021 |
Sono stati sostituiti gli IP discreti e gli intervalli IP più ridotti Webex Calling con intervalli semplificati in una tabella separata per facilitare la comprensione della configurazione del firewall. |
26 febbraio 2021 |
Aggiunto 5004 come porta di destinazione per il contenuto multimediale di chiamata a Webex Calling (STUN, SRTP) per supportare il connettività interattiva Bluetooth (ICE) che sarà disponibile Webex Calling ad aprile 2021. |
22 febbraio 2021 |
Domini e URL vengono ora elencati in una tabella separata. 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):
Adding the following IP addresses for Application Configuration because Cisco Webex client points to a newer DNS SRV in Australia in March 2021.
|
21 gennaio 2021 |
We’ve added the following IP addresses to device configuration and firmware management (Cisco devices):
We’ve removed the following IP addresses from device configuration and firmware management (Cisco devices):
We’ve added the following IP addresses to the application configuration:
We’ve removed the following IP addresses from the application configuration:
We’ve removed the following port numbers from the application configuration:
We’ve added the following domains to the application configuration:
|
23 dicembre 2020 |
Sono stati aggiunti nuovi indirizzi IP di configurazione dell'applicazione alle immagini di riferimento della porta. |
22 dicembre 2020 |
È stata aggiornata la riga Configurazione applicazione nelle tabelle in modo da includere i seguenti indirizzi IP: 135.84.171.154 e 135.84.172.154. Hid the network diagrams until these IP addresses are added. |
11 dicembre 2020 |
Sono state aggiornate la configurazione del dispositivo e la gestione del firmware (dispositivi Cisco) nonché le righe di configurazione dell'applicazione per i domini canadesi supportati. |
16 ottobre 2020 |
Sono stati aggiornati i segnali di chiamata e le voci multimediali con i seguenti indirizzi IP:
|
23 settembre 2020 |
In CScan, 199.59.64.156 è stato sostituito con 199.59.64.197. |
14 agosto 2020 |
Sono stati aggiunti altri indirizzi IP per supportare l'introduzione dei centri dati in Canada: Segnale di chiamata a 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 agosto 2020 |
Sono stati aggiunti altri indirizzi IP per supportare l'introduzione dei centri dati in Canada:
|
22 luglio 2020 |
È stato aggiunto il seguente indirizzo IP per supportare l'introduzione dei centri dati in Canada: 135.84.173.146 |
9 giugno 2020 |
Sono state apportate le seguenti modifiche alla voce CScan:
|
11 marzo 2020 |
We added the following domain and IP addresses to the application configuration:
Sono stati aggiornati i seguenti domini con indirizzi IP aggiuntivi per la configurazione dei dispositivi e la gestione del firmware:
|
27 febbraio 2020 |
Sono stati aggiunti i seguenti domini e porte alla configurazione dei dispositivi e alla gestione del firmware: cloudupgrader.webex.com—443, 6970 |