Is there a way to 'turn off' a IM chat window from automatically opening in a separate window in Webex Teams? I don't want a separate window to open and I can't find a way to turn this off. I only see a way to 'open in new window' which it does automatically.
This article provides guidance and direction on how to allow Webex meeting network traffic on your network.
Webex Meeting Traffic
Allow domains access through your Firewall, Web Proxy, or any other filtering device, List of IP addresses by region, Ports used by the Webex client for communication for both inbound and outbound traffic, Default Ports used by Video Collaboration Devices.
- Troubleshoot the Webex User Account Activation Email Not Received Issue Follow the instructions if you did not receive the email to activate your Webex account. Verify the email is not in your spam/junk folder, and your mail server does not block emails from.
- Try to find the account you are using to sign in to Teams and Office 365 apps, click on it and click Disconnect. After the action, you will have to sign in to all Office 365 applications again. Teams desktop app should also ask you to enter your credentials. Check whether the issue persists after the action.
How do I allow Webex Meetings traffic on my network?
- Network Requirements
- Network Requirements for Cisco Webex
- How do I optimize firewall and proxy settings for use with Webex services?
- What ports need to be opened to use Webex services?
- What exceptions should I add to my firewall for Webex?
- What IP range is assigned to Webex?
- What settings does Webex recommend for proxy servers?
Using TCP in a near congested network will cause retransmissions, which in turn can create a choppy video or low bandwidth error experience. UDP does not retransmit, and will provide a better video experience.
For more info on the low bandwidth error, see: WBX84420 - I Get a Low-Bandwidth Error when I Try to View Video from TelePresence Users
Audio / Video packets use the standard RTP protocol. Depending on your existing firewall rules, an adjustment may be necessary to allow the standard RTP protocol.
Solution:
Ports used by Webex Meeting Clients:
Depending on the services you are using in your particular deployment of Webex, you may connect to our services over a variety of different ports.
The chart below is provided to help you identify what ports you might need to open on your firewall. Some services like video collaboration, have on-premise components that can be configured to use non-standard port ranges. For those devices, please see the specific deployment guide for that device or technology in order to determine the exact ports to open.
If you are also leveraging Webex Teams (formerly Cisco Spark) in your environment, implement the settings from this article and the Webex Teams Network Requirements article.
Ports used by the Webex client for communication (both inbound and outbound traffic):
In order to connect to Webex, you must have a working DNS server. Most DNS queries are made over UDP; however, DNS queries may use TCP as well.
| Webex website, Webex Desktop App/Productivity Tools, Webex Meetings for Android/iOS, Webex Web App | ||||
|---|---|---|---|---|
| Protocol | Port Number(s) | Direction | Access Type | Comments |
| TCP | 80 / 443 | Outbound | Webex Client Access port | The Webex Client makes the majority of its data transfers and loading using HTTPS over port 443. In some cases, port 80 will also be used before being redirected to a secure connection. |
| TCP/UDP | 53 | Outbound | DNS | In order to connect to Webex you must have a working DNS server. Most DNS queries are made over UDP; however, DNS queries may use TCP as well. |
| UDP | 9000 | Outbound | Webex Client Media for Webex Events (Audio Streaming) | Webex utilizes port 9000 for the Webex Events Audio Broadcast feature. If unable to connect, it will use TCP 443. |
| UDP | 9000 | Outbound | Webex Client Media (VoIP and Video RTP) | The Webex client will try to connect to a Multimedia server over UDP port 9000. If unable to establish a connection over UDP 9000, it will use TCP port 443. Due to the nature of TCP and how lost delayed packets are retransmitted, it is not recommended to use TCP. We recommend allowing UDP port 9000 whenever possible. (This media is sent over standard RTP. Firewalls should not manipulate the RTP being sent or received.) |
| TCP / UDP | Operating System Specific Ephemeral Ports | Inbound | Return traffic from Webex | Webex will communicate to the destination port received when the client makes its connection. A firewall should be configured to allow these return connections through. |
| Default Ports used by Video Collaboration Devices: These ports are provided as a reference only. Please refer to the deployment guide/manufacturer recommendation for full details. | ||||
|---|---|---|---|---|
| Protocol | Port Number(s) | Direction | Access Type | Comments |
| TCP | 5060-5070 | Outbound | SIP signaling | The Webex media edge listens on 5060 - 5070. For more information, please see the configuration guide on the specific service being used: Cisco Webex Meeting Center Video Conferencing Enterprise Deployment Guide.pdf |
| TCP | 5060, 5061 and 5065 | Inbound | SIP signaling | Inbound SIP signaling traffic from the Webex cloud. |
| TCP / UDP | 1719, 1720 and port 15000-19999 | Inbound and Outbound | H.323 LS | If your endpoint requires gatekeeper communication, also open port 1719 which includes Lifesize. |
| TCP / UDP | Ephemeral Ports 36000-59999 | Inbound and Outbound | Media ports | If you're using a Cisco Expressway, the media ranges need to be set to 36000-59999. If you are using a third party endpoint or call control, they need to be configured to use this range. |
| Ports used by Webex Edge Audio: | ||||
|---|---|---|---|---|
| Protocol | Port Number(s) | Direction | Access Type | Comments |
| TCP | 5061, 5062 | Inbound | SIP Signaling | Inbound SIP signaling for Webex Edge Audio. |
| TCP | 5061, 5065 | Outbound | SIP Signaling | Outbound SIP signaling for Webex Edge Audio. |
| TCP / UDP | Ephemeral Ports 8000 - 59999 | Inbound | Media Ports | On an enterprise firewall, pinholes need to be opened for incoming media traffic with a port range from 8000 - 59999. |
List of IP address ranges used by Cisco Webex Meeting services:
- 64.68.96.0/19 (CIDR) or 64.68.96.0 - 64.68.127.255 (net range)
- 66.114.160.0/20 (CIDR) or 66.114.160.0 - 66.114.175.255 (net range)
- 66.163.32.0/19 (CIDR) or 66.163.32.0 - 66.163.63.255 (net range)
- 170.133.128.0/18 (CIDR) or 170.133.128.0 - 170.133.191.255 (net range)
- 173.39.224.0/19 (CIDR) or 173.39.224.0 - 173.39.255.255 (net range)
- 173.243.0.0/20 (CIDR) or 173.243.0.0 - 173.243.15.255 (net range)
- 207.182.160.0/19 (CIDR) or 207.182.160.0 - 207.182.191.255 (net range)
- 209.197.192.0/19 (CIDR) or 209.197.192.0 - 209.197.223.255 (net range)
- 216.151.128.0/19 (CIDR) or 216.151.128.0 - 216.151.159.255 (net range)
- 114.29.192.0/19 (CIDR) or 114.29.192.0 - 114.29.223.255 (net range)
- 210.4.192.0/20 (CIDR) or 210.4.192.0 - 210.4.207.255 (net range)
- 69.26.176.0/20 (CIDR) or 69.26.176.0 - 69.26.191.255 (net range)
- 62.109.192.0/18 (CIDR) or 62.109.192.0 - 62.109.255.255 (net range)
- 69.26.160.0/20 (CIDR) or 69.26.160.0 - 69.26.175.255 (net range)
Webex does not support or recommend filtering IP addresses for a particular region. Filtering by region can cause serious degradation to the in meeting experience up to and including the inability to join meetings entirely.
Webex leverages the Akamai content delivery network (CDN). The addresses akamaicdn.webex.com and lp.webex.com serve static content and are hosted by Akamai, which has IP ranges outside of the Webex IP ranges and these are subject to change at anytime.
Domains that need to be whitelisted
Webex recommends that content should not be cached at any time. The following domain(s) will be used by meeting clients that connect to Webex Meetings:
| Client Type | Domain(s) |
|---|---|
| Webex Desktop Clients (Mac/PC, including WebApp the browser based thin client) connecting to Webex Meetings. | *.webex.com |
| On-prem SIP/H323 devices calling into (or being called back from) a Webex Meeting. | *.webex.com (note IP dialing also available) |
| Webex Mobile Clients (iOS, Android) connecting to Webex Meetings. | *.webex.com |
| Teams Desktop Clients, Cloud Registered Devices (including Webex Boards), connecting to Webex Meetings. | See Article: Network Requirements for Webex Teams Services |
If leveraging the People Insights feature the domain *.accompany.com also needs to be whitelisted.
We also require certificate validation through a certificate revocation list. This Certificate Revocation List is hosted by Quovadis, and will require the following domain to be reachable:
- *.quovadisglobal.com
Webex Teams Not Working On Vpn
If your firewall or web filtering system does not allow wildcard filtering, you can open your firewall by IP address (this is not recommended). Due to the expanding nature of the Cisco Webex business, we maintain the right to add IP addresses at any time without notice.
All Webex hosted services are advertised under AS13445. All traffic from AS13445 should be allowed. Services hosted by other service providers are not included here. This includes TSP partner systems or our content delivery partners. If you are connecting to partner-hosted systems such as a Partner VoIP system, please contact the partner for the appropriate IP addresses and ports or refer to the peering policy .
Information for China Clusters
Additional Resource:
This information was obtained from the following source: https://help.webex.com/WBX264/How-Do-I-Allow-Webex-Meetings-Traffic-on-My-Network
Webex Teams Not Opening On Mac
Introduction
This document describes how to troubleshoot the Webex account activation email not received issue.
Background Information
This document provides steps for these queries as well:
- The Webex user account activation email has not been received.
- How to resend the Webex account activation email to a customer?
- How to troubleshoot an activation email not received issue?
Troubleshoot the Webex User Account Activation Email Not Received Issue
Follow the instructions if you did not receive the email to activate your Webex account.
Step 1. Verify the email is not in your spam/junk folder, and your mail server does not block emails from:
- webex.com
- em.webex.com
Step 2. Whitelist these IP addresses:
- 142.0.167.102
- 142.0.167.103
- 142.0.167.104
- 147.253.211.216
- 147.253.211.217
Webex User:
To have an activation email resent to you:
Step 1. Navigate your web browser to https://web.webex.com.
Step 2. Enter the email address that was used for the Webex Online account, then select Continue.
Step 3. On the Sign in to Webex page, enter your password, then select Sign In.
Step 4. On the Your account is pending activation page, click on the Resend link as shown in the image.
Webex Teams Audio Not Working
Instructions to activate your account will be sent to you.
Note: You continue to get the account is pending activation email until your account is activated.
If you still do not receive your activation email, contact technical support.