I am trying to establishing an WebEx-Meeting using my Windows 10 Computer.
The Problem is, that the Desktop WebEx-Client can connect to the WebEx-Server during the eBlocker, but the Audio-Connection can only established if the eBlocker is switched of.
I tried to use a manual diagnosis, but there is no error shown.
Is there something I can do?
Used config:
Probably some certificate pinning taking place here. Have you tried recording SSL errors and adding them to a trusted app? (Settings>HTTPS>Manual Recording. Select your webex device, start recording. Connect to webex & audio. Check recordings and add all errors into a Trusted App).
Unfortunately today this process is for the more tech savvy people. We'll come up with a fix in the near future that will automate today's manual process. Stay tuned 😉
Hi Karsten,
we use Webex in our Office. There in our webgateway (Clearswift) we do al lott of exceptions for Webex.
Tomorrow I can look for the List of domains and IPs to get it work.
Here are some domains 🙂
"Webex Teams"
encryption.a8.ciscospark.com
mercury-connection-partition6.a6.ciscospark.com
teams.webex.com
ec.walkme.com
atlas-a.wbx2.com
cdn.walkme.com
apheleia-a.wbx2.com
atlas-a.wbx2.com
avatar-a.wbx2.com
avatar-prod-us-east-2.webexcontent.com
calendar-a.wbx2.com
cdn.appdynamics.com
conv-a.wbx2.com
files-api-a.wbx2.com
idbroker.webex.com
identity.webex.com
janus-a.wbx2.com
locus-a.wbx2.com
mercury-connection-partition6.a6.ciscospark.com
metrics-a.wbx2.com
people.webex.com
playerserver.walkme.com
raindrop-a.wbx2.com
u2c-a.wbx2.com
u2c.wbx2.com
wdm-a.wbx2.com
wdm.a8.ciscospark.com
Good luck, more tomorrow 🤠
regards
PIO78
Hi,
thats all 🙂
*.ciscospark.com
*.walkme.com
*.wbx2.com
*.webex.com
20.10.2020 some more information
if you an firewall open the following port from internal to the internet:
TCP 5004
TCP 5061
UDP 5004
here you can test connectivity:
result attached
regards
PIO78
Excellent!
Dear all, I currently still run into this problem: Webex Audio connection fails, unless I set eblocker on pause for my macbook. I added the Webex app to trusted apps, and all domains as listed earlier in these postings are added to the trusted domains for all Webex-associated applications. Nevertheless the audio connection fails. Any idea? Thanks in advance, andreas
@andreasr Maybe/probably Webex changed their infrastructure (used domains) meanwhile. I‘d try a manual recording next time you are using Webex.
Alternatively you maybe want to try enabling the Auto Trust App (Settings > HTTPS), which might fix this automatically. It usually takes a few re-trys (of webex) until ATA records & trusts the needed domains…
Please share the solution once you got it. 👍
THX!
@random Thanks for your advice. I already did the manual recording. No other than the already mentioned domains appeared. And the Auto Trust App is on. How long does ATA take to learn. Does it run locally, or does it wait for approval by the e-blocker team?
Best, andreas
@andreasr ATA works locally only and does pretty much what you manually do. It records HTTPS connections and analyses connection errors. If the domain causing the connection error does not match a tracker signature, the domain gets added as trusted. This process is quick but it might not catch all domains instantly. That's why you might need a few retries.
Unfortunately I'm not using Webex to check myself what's going on. The only advice I can give: Try the manual recording for some longer (also using audio) and set all the recorded domains as trusted.
THX!