- الرئيسية
- /
- المقال
هذه المقالة مخصصة لمسؤولي الشبكات، وخاصةً مسؤولي جدران الحماية وأمان الوكيل الذين يستخدمون خدمات Webex Calling داخل مؤسساتهم. إنه يصف متطلبات الشبكة ويسرد العناوين والمنافذ والبروتوكولات المستخدمة لتوصيل هواتفك وتطبيق Webex والبوابات إلى خدمات 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. مثال: 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.
-
مصادقة المستخدم
-
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
-
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:
المنتج |
تكوين الوكيل |
نوع المصادقة |
---|---|---|
Webex لنظام التشغيل Mac |
يدوي، WPAD، PAC |
No Auth, Basic, NTLM,† |
Webex لنظام التشغيل Windows |
يدوي، WPAD، PAC، GPO |
No Auth, Basic, NTLM, †, Negotiate † |
Webex لنظام التشغيل iOS |
يدوي، WPAD، PAC |
لا توجد مصادقة، أساسية، ملخص، NTLM |
Webex لنظام التشغيل Android |
يدوي، PAC |
لا توجد مصادقة، أساسية، ملخص، NTLM |
تطبيق Webex على الويب |
Supported through OS |
No Auth, Basic, Digest, NTLM, Negotiate † |
أجهزة Webex |
WPAD أو PAC أو يدوي |
لا توجد مصادقة، أساسية، ملخص |
هواتف Cisco IP |
يدوي، WPAD، PAC |
لا توجد مصادقة، أساسية، ملخص |
عقدة شبكة فيديو Webex |
يدوي |
لا توجد مصادقة، أساسية، ملخص، 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 |
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.
-
استخدم خادما وكيلا لاعتراض الطلبات والحد من المجالات المسموح بها.
فحص الوكيل وتثبيت الشهادة
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
المنتج |
يدعم جهات CA المخصصة الموثوق بها لفحص TLS |
---|---|
تطبيق Webex (أنظمة التشغيل Windows وMac وiOS وAndroid وعلى الويب) |
نعم |
أجهزة Webex Room |
نعم |
Cisco IP Multiplatform (MPP) Phones |
نعم |
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.
ملاحظة: 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.
المجال/ عنوان URL |
الوصف |
تطبيقات Webex والأجهزة التي تستخدم هذه المجالات / عناوين URL | ||
---|---|---|---|---|
خدمات Cisco Webex | ||||
*.broadcloudpbx.com |
Webex authorization microservices for cross-launch from Control Hub to Calling Admin Portal. |
Control Hub | ||
*.broadcloud.com.au |
خدمات Webex Calling في أستراليا. |
الكل | ||
*.broadcloud.eu |
خدمات Webex Calling في أوروبا. |
الكل | ||
*.broadcloudpbx.net |
الاتصال بخدمات تكوين وإدارة العميل. |
تطبيقات 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. |
الكل | ||
*.ucmgmt.cisco.com |
خدمات Webex Calling |
Control Hub | ||
*.wbx2.com and *.ciscospark.com |
Used for cloud awareness to reach out to Webex Calling & Webex Aware services during and after onboarding. These services are necessary for
|
الكل | ||
*.webexapis.com |
Webex microservices that manage your Webex App applications and Webex devices.
|
الكل | ||
*.webexcontent.com |
Webex Messaging services related to general file storage including:
|
Webex Apps Messaging services.
| ||
*.accompany.com |
People insights integration |
تطبيقات Webex | ||
Additional Webex-Related Services (Third-Party Domains) | ||||
*.appdynamics.com *.eum-appdynamics.com |
تتبع الأداء وتسجيل الأخطاء والأعطال وقياسات الجلسات. |
Control Hub | ||
*.sipflash.com |
Device management services. Firmware upgrades and secure onboarding purposes. |
تطبيقات Webex | ||
*.walkme.com *.walkmeusercontent.com |
عميل توجيه مستخدم Webex. يوفر جولات توضح خطوات الضم والاستخدام من أجل المستخدمين الجدد. لمعرفة مزيد من المعلومات عن WalkMe، انقر هنا. |
تطبيقات 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)
| تطبيق 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 |
الغرض من الاتصال | عناوين المصدر | Source Ports | البروتوكول | عناوين الوجهة | منافذ الوجهة | ملاحظات | |||
---|---|---|---|---|---|---|---|---|---|
إرسال شارات المكالمات إلى Webex Calling (SIP TLS) | البوابة المحلية الخارجية (NIC) | 8000-65535 | TCP | ارجع إلى شبكات IP الفرعية لخدمات 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 | |||
الأجهزة | 5060-5080 | 8934 | |||||||
تطبيق Webex | قصير الأجل (يعتمد على نظام التشغيل) | ||||||||
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 | 8000-48199†* | UDP | ارجع إلى شبكات IP الفرعية لخدمات Webex Calling. |
5004, 9000 (STUN Ports) الصوت 8500-8599 الفيديو: 8600-8699 19560-65535 (SRTP over UDP) |
| |||
Devices†* | 19560-19661 | ||||||||
Webex App†* |
الصوت 8500-8599 الفيديو: 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 | ||||
إرسال شارات المكالمات إلى بوابة PSTN (SIP TLS) | البوابة المحلية الداخلية NIC | 8000-65535 | TCP | ITSP PSTN GW أو Unified CM الخاص بك | يتوقف على خيار PSTN (على سبيل المثال، عادةً ما يكون 5060 أو 5061 لنظام Unified CM) | ||||
Call media to PSTN gateway (SRTP/SRTCP) | البوابة المحلية الداخلية NIC | 8000-48199†* | UDP | ITSP PSTN GW أو Unified CM الخاص بك | Depends on the PSTN option (for example, typically 5060 or 5061 for Unified CM) | ||||
تكوين الجهاز وإدارة البرامج الثابتة (أجهزة Cisco) | أجهزة Webex Calling | قصير الأجل | 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 | قصير الأجل | 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.
| |||
مزامنة وقت الجهاز (NTP) | أجهزة Webex Calling | 51494 | UDP | ارجع إلى شبكات IP الفرعية لخدمات Webex Calling. | 123 | عناوين IP المذكورة مطلوبة من أجل المزامنة الزمنية للأجهزة (هواتف MPP وأجهزة ATA وأجهزة SPA ATA) | |||
Domain Name System (DNS) resolution | Webex Calling devices, Webex App, and Webex Devices | قصير الأجل | UDP وTCP | محدد من قِبل المضيف | 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. | |||
بروتوكول وقت الشبكة (NTP) | Webex App and Webex Devices | 123 | UDP | محدد من قِبل المضيف | 123 | Time Synchronization | |||
CScan | Web based Network readiness Pre-qualification tool for Webex Calling | قصير الأجل | TCP | ارجع إلى شبكات IP الفرعية لخدمات Webex Calling. | 8934 and 443 | Web based Network readiness Prequalification tool for Webex Calling. انتقل إلى cscan.webex.com لمعرفة مزيد من المعلومات. | |||
UDP | 19569-19760 | ||||||||
Additional Webex Calling & Webex Aware Services (Third-Party) | |||||||||
Push notifications APNS and FCM services | Webex Calling Applications | قصير الأجل | 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) |
|
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 | منافذ المصدر | منافذ الوجهة | DSCP Class and value |
---|---|---|---|---|---|
تطبيق Webex | الصوت |
Refer IP subnets, Domains, and URLs for Webex Calling services | 8500-8599 | 8500-8599, 19560-65535 | Expedited Forwarding (46) |
تطبيق Webex | الفيديو | 8600-8699 | 8600-8699, 19560-65535 | Assured Forwarding 41 (34) | |
تطبيق Webex | اشارات | قصير الأجل (يعتمد على نظام التشغيل) | 8934 | CS0 (0) | |
Webex Devices (MPPs and Room) | الصوت والفيديو | 19560-19661 | 19560-65535 |
Expedited Forwarding (46) & Assured Forwarding 41 (34) | |
أجهزة Webex | اشارات | 5060-5080 | 8934 | Class Selector 3 (24) |
|
Webex Meetings/المراسلة - متطلبات الشبكة
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.
متطلبات شبكة 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: متطلبات الشبكة لحلول 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
المراجع
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
محفوظات مراجعة المستندات
التاريخ |
لقد أجرينا التغييرات التالية على هذه المقالة | ||
---|---|---|---|
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 أغسطس 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.
| ||
July 5, 2023 |
Added the link https://binaries.webex.com to install the Cisco MPP Firmware. | ||
7 مارس 2023 |
We've overhauled the entire article to include:
| ||
5 مارس 2023 |
Updating the article to include the following:
| ||
15 نوفمبر 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. | ||
September 08, 2022 |
The Cisco MPP Firmware transitions to use https://binaries.webex.com as the host URL for MPP firmware upgrades in all regions. This change improves firmware upgrade performance. | ||
August 30, 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 أغسطس 2022 |
No change in the solution. Updated the destination ports 5062 (required for Certificate-based trunk), 8934 (required for Registration-based trunk) for Call signaling to Webex Calling (SIP TLS). | ||
July 26, 2022 |
Added the 54.68.1.225 IP Address, which is required for firmware upgrade of Cisco 840/860 devices. | ||
July 21, 2022 |
Updated the destination ports 5062, 8934 for Call signaling to Webex Calling (SIP TLS). | ||
July 14, 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 يونيو 2022 |
Updated the Domain and URLs for Webex Calling services: *.broadcloudpbx.com *.broadcloud.com.au *.broadcloud.eu *.broadcloudpbx.net | ||
June 15, 2022 |
Added the following ports and protocols under IP Addresses and Ports for Webex Calling Services:
Updated information in Webex Meetings/Messaging - Network Requirements section | ||
24 مايو 2022 |
Added the IP subnet 52.26.82.54/24 to 52.26.82.54/32 for Webex Calling service | ||
6 مايو 2022 |
Added the IP subnet 52.26.82.54/24 for Webex Calling service | ||
7 أبريل عام 2022 |
Updated the Local Gateway internal and external UDP port range to 8000-48198† | ||
5 أبريل عام 2022 |
تم إضافة شبكات IP الفرعية التالية لخدمة Webex Calling:
| ||
29 مارس عام 2022 |
تم إضافة شبكات IP الفرعية التالية لخدمة Webex Calling:
| ||
13 سبتمبر عام 2020 |
تم إضافة 4 شبكات IP فرعية جديدة لخدمة Webex Calling:
| ||
2 أبريل عام 2021 |
Added *.ciscospark.com under Domains and URLs for Webex Calling Services to support Webex Calling use cases in the Webex app. | ||
25 مارس عام 2021 |
تم إضافة 6 نطاقات IP جديدة من أجل activate.cisco.com، والتي ستدخل حيز التنفيذ اعتبارًا من 8 مايو عام 2021.
| ||
4 مارس عام 2021 |
تم استبدال عناوين IP المنفصلة الخاصة بتطبيق Webex Calling ونطاقات IP الأصغر بنطاقات مبسطة في جدول منفصل لسهولة فهم عملية تكوين جدار الحماية. | ||
26 فبراير عام 2021 |
Added 5004 as destination port for Call media to Webex Calling (STUN, SRTP) to support Interactive Connectivity Establishment (ICE) that will be available in Webex Calling in April 2021. | ||
22 فبراير عام 2021 |
تم الآن إدراج المجالات وعناوين URL ضمن جدول منفصل. 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 يناير عام 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 ديسمبر عام 2020 |
تم إضافة عناوين IP الجديدة لتكوين التطبيق إلى الصور المرجعية للمنفذ. | ||
22 ديسمبر عام 2020 |
تم تحديث صف "تكوين التطبيق" في الجداول لتضمين عناوين IP التالية: 135.84.171.154 و135.84.172.154. Hid the network diagrams until these IP addresses are added. | ||
11 ديسمبر عام 2020 |
تم تحديث تكوين الجهاز وإدارة البرامج الثابتة (أجهزة Cisco) وصفوف تكوين التطبيق للمجالات الكندية المدعومة. | ||
16 أكتوبر عام 2020 |
تحديث إرسال إشارات المكالمات وإدخالات الوسائط باستخدام عناوين IP التالية:
| ||
23 سبتمبر عام 2020 |
ضمن CScan، تم استبدال 199.59.64.156 بالمجال 199.59.64.197. | ||
14 أغسطس عام 2020 |
تم إضافة المزيد من عناوين IP لدعم تقديم مراكز البيانات في كندا: إرسال شارات المكالمات إلى 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 أغسطس عام 2020 |
تم إضافة المزيد من عناوين IP لدعم تقديم مراكز البيانات في كندا:
| ||
21 يوليو عام 2020 |
تم إضافة عناوين IP التالية لدعم تقديم مراكز البيانات في كندا: 135.84.173.146 | ||
9 يونيو عام 2020 |
لقد أجرينا التغييرات التالية على إدخال CScan:
| ||
11 مارس عام 2020 |
We added the following domain and IP addresses to the application configuration:
قمنا بتحديث المجالات التالية باستخدام عناوين IP إضافية لتكوين الجهاز وإدارة البرامج الثابتة:
| ||
27 فبراير عام 2020 |
أضفنا المجال والمنافذ التالية إلى تكوين الجهاز وإدارة البرامج الثابتة: cloudupgrader.webex.com—443, 6970 |