WTOS 9.1 and Cisco Webex Meetings package v40.10.11.15_4

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #61991
    Avatarbrian1020
    Participant
    • Total Post: 186
    • Jacked into The Matrix
    • ★★★★★★

    Curious if anyone has the WebEx Meeting package working and offloading audio and video?

    I don’t yet, working with Cisco engineering later this week.  We have the Zoom package working without issue.  The thin client, thankfully, takes a WebEx Unified Trace (.wbt file) when you pull the logs from the thin client.  I also took a .wbt log from the Virtual Machine. I can see from the logs the Virtual Channel is opening, then closing and there are some errors but I’m not familiar with wbt logs, I know enough to get me into trouble with guessing what is happening.

    On the thin client side, the policy is set for Zoom and WebEx v-channels ON and the other v-channels are turned off, the packages are installed, and USB redirection for webcams and audio devices is set to use HDX, not USB redirect.

    I figured I would start a topic and see if there are any suggestions, and I’ll also post root cause once I find it and hopefully a fix.  Right now without taking pcaps I’m leaning down the firewall is shutting down whatever port the v-channel is trying to establish itself on.  Our Zoom sessions are proxied but WebEx is going out the firewall.

    #81221
    AvatarWyseVet
    Participant
    • Total Post: 13
    • Regular Joe
    • ★★

    I had been doing early testing for the plugin , we are a Webex shop (seems to be the unpopular choice but i can’t change it). The plugin seemed to be working well in the Beta 9.1. 1036 with Webex 401002341.2 package but when the 9.1.1131 firmware with Webex package 40.10.11.15.4 came out its stopped working (VDI banner no longer comes up ).  and i can start a Citrix Xendesktop session to same desktop from a laptop with the plugin loaded and it works.  I have started a ticket with Dell , they first mentioned that the new 3.1.1. hotfix would address it but I don’t think that’s valid, it would have to be firmware i think.

    I did not know about the .wbt log file that may be helpful. Have you seen a good how to on setting it up anywhere? The Cisco documentation seems scattered , vs a do this and this , bullet point how to.

    Glad to see someone else working on this ,will try to update as I test!

    • This reply was modified 2 months, 2 weeks ago by AvatarWyseVet.
    #81245
    Avatarbrian1020
    Participant
    • Total Post: 186
    • Jacked into The Matrix
    • ★★★★★★

    Funny enough, I just got this working today. Prepare yourself, this was pretty involved, but I am happy its working now and got the VDI tag.

    First firewall blocks, had to add several firewall IP ranges to allowed and ports, don’t know how this copy/past will go from my spreadsheet but this is what I added for my change control on the firewall:

    https://help.webex.com/en-us/WBX000028782/Network-Requirements-for-Webex-Services

    WebEx IP Subnets for Media Services (Updated 1/21/21 by Cisco)
    IP Owner Lookup
    Location

    3.22.157.0/26
    Amazon AWS
    North America, USA, Ohio

    3.25.56.0/25
    Amazon AWS
    Oceania, Australia, Sydney

    3.101.70.0/25
    Amazon AWS
    North America, USA, California

    3.101.71.0/24
    Amazon AWS
    North America, USA, California

    3.101.77.128/28
    Amazon AWS
    North America, USA, California

    3.235.73.128/25
    Amazon AWS
    North America, USA, Virginia

    3.235.80.0/23
    Amazon AWS
    North America, USA, Virginia

    3.235.122.0/24
    Amazon AWS
    North America, USA, Virginia

    3.235.123.0/25
    Amazon AWS
    North America, USA, Virginia

    18.132.77.0/25
    Amazon AWS
    Europe, United Kingdom, London

    18.141.157.0/25
    Amazon AWS
    Asia, Singapore

    18.181.18.0/25
    Amazon AWS
    Asia, Japan, Tokyo

    18.181.178.128/25
    Amazon AWS
    Asia, Japan, Tokyo

    18.181.204.0/25
    Amazon AWS
    Asia, Japan, Tokyo

    18.230.160.0/25
    Amazon AWS
    South America, Brazil, Sao Paulo

    20.50.235.0/24*
    Microsoft Azure
    Europe, Netherlands

    20.53.87.0/24
    Microsoft Azure
    Oceania, Australia, Sydney

    40.119.234.0/24*
    Microsoft Azure
    Asia, Singapore

    44.234.52.192/26
    Amazon AWS
    North America, USA, Kansas

    52.232.210.0/24*
    Microsoft Azure
    North America, USA, Virginia

    62.109.192.0/18
    Cisco WebEx
    Europe, Netherlands

    64.68.96.0/19
    Cisco WebEx
    North America, USA, Kansas

    66.114.160.0/20
    Cisco WebEx
    North America, USA, Kansas

    66.163.32.0/19
    Cisco WebEx
    North America, USA, Kansas

    69.26.160.0/19
    Cisco WebEx
    North America, USA, Kansas

    114.29.192.0/19
    Cisco WebEx
    Asia, Singapore

    150.253.128.0/17
    Cisco WebEx
    North America, USA, Kansas

    170.72.0.0/16
    Cisco WebEx
    North America, USA, Utah

    170.133.128.0/18
    Cisco WebEx
    North America, USA, Kansas

    173.39.224.0/19
    Cisco WebEx
    North America, USA, California

    173.243.0.0/20
    Cisco WebEx
    North America, USA, Kansas

    207.182.160.0/19
    Cisco WebEx
    North America, USA, Kansas

    209.197.192.0/19
    Cisco WebEx
    North America, USA, Kansas

    210.4.192.0/20
    Cisco WebEx
    Asia, Singapore

    216.151.128.0/19
    Cisco WebEx
    North America, USA, Kansas

    Port
    Protocol
    Description
    WebEx Service
    443
    TLS
    Webex HTTPS signalling. Session establishment to Webex services is based on defined URLs, rather than IP addresses.
    All
    444
    TLS
    Video Mesh Node secure signalling to establish cascade media connections to the Webex cloud
    Video Mesh Node
    123
    UDP
    Network Time Protocol (NTP)
    All
    53
    UDP/TCP
    Domain Name System (DNS) Used for DNS lookups to discover the IP addresses of services in the Webex cloud. Most DNS queries are made over UDP; however, DNS queries may use TCP as well.
    All
    5004 and 9000*
    SRTP over UDP
    Encrypted audio, video, and content sharing on the Webex App and Webex Room devices. *The Webex App uses UDP port 9000 to connect to Webex Meetings media services
    Webex App and Video Mesh Nodes
    5004
    SRTP over TCP
    Used for encrypted content sharing on the Webex App and Webex Room devices. TCP also serves as a fallback transport protocol for encrypted audio and video if UDP cannot be used.
    Webex App, WebEx Room and Video Mesh Nodes
    33434
    SRTP over UDP/TCP
    Port 33434 is used for encrypted media if port 5004 is blocked by your firewall. Note that a TCP socket on port 33434 will be established, but only used if connections fail over TCP and UDP on port 5004 and UDP on port 33434. (2)
    Webex App
    443 (2)
    SRTP over TLS
    Used as a fallback transport protocol for encrypted audio, video and content sharing if UDP and TCP cannot be used.
    Webex App

    Media over TLS is not recommended in production environments
    Webex Room Devices

     

    After that I found out that if your VM (HVD) is running  a VGPU, WebEx doesn’t think its a HVD so it shuts down the plugin agent and runs in fallback mode.  Add these REG keys if you don’t have them… scroll down to the regedits: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/vdi/wbx-teams-vdi-deployment-guide/wbx-teams-vdi-deployment_chapter_010.html

    HKEY_LOCAL_MACHINE\Software\Cisco Spark Native\  ***Note I had to add Cisco Spark Native folder***

    [HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Spark Native] “isVDIEnv” = “true”, datatype:REG_EXPAND_SZ

    [HKEY_CURRENT_USER\Software\Cisco Systems, Inc.\CiscoVDI] “isVDIEnv” = “true”, datatype:REG_EXPAND_SZ

     

    Optional

    Step 1
    In Windows search or the Run window, type regedit and then press Enter
    Step 2
    Go to HKEY_LOCAL_MACHINE\Software\Cisco Spark Native\.
    Step 3
    Change values for the following registry keys as needed:
    Step 4
    Choose a DWORD value for VDIFallBackConf:

    0—Advanced video features are disabled. (Default)
    1—Advanced video features are enabled. Users will be in full mode, which is the same as Webex for Windows (audio, video, screen share and advanced video features).
    2—Video and screen sharing are disabled. Users are able to do audio only calls.
    3—Video is disabled. Users are able to do audio calls with sharing capability.
    4—Screen or application share only is enabled. Users cannot make audio or video calls and are in messaging only mode.
    5—A dialogue prompt shows an error message: “Due to your company policy, you are not allowed to start Webex Calling  without VDI-Optimized on Hosted Virtual desktop. Please ask your site admin for help.”
    Note
    This registry key only works when enablevdi=1 during installation and the VDI plugin is not installed. because In fallback mode, datacenter load increases, so media is not used to prevent overload.
    Step 5
    Choose a DWORD value for VDIBackgroundEnabled:

    0—Disables virtual backgrounds when Webex is in optimized VDI mode. (Default)
    1—Disables virtual backgrounds when Webex is in optimized VDI mode.
    Step 6
    Choose a DWORD value for VDIScreenShareEnabled:

    0—Disables full screen sharing when Webex is in optimized VDI mode. With this setting, users can only share the HVD window view.
    1—Enables full screen sharing when Webex is in optimized VDI mode. (Default)

     

    Hope this helps, it was quite a process getting this working over several weeks of CCIDs and trial and error.

    #81246
    Avatarbrian1020
    Participant
    • Total Post: 186
    • Jacked into The Matrix
    • ★★★★★★

    For the record, this was the one that finally got it working

    [HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Spark Native] “isVDIEnv” = “true”, datatype:REG_EXPAND_SZ

    Also, for obvious reasons, make sure your turn on the Citrix Virtual Channels for the different unified communications in WMS for the policy under Citrix Session Settings… Zoom VDI, WebEx VDI, Teams VDI etc.

     

    I now have both Zoom VDI and WebEx VDI working.

    #81761
    AvatarWyseVet
    Participant
    • Total Post: 13
    • Regular Joe
    • ★★

    Wow that is some great info thank you for posting. Can you confirm you got this working using 9.1.1131 firmware with Webex package 40.10.11.15.4? The behavior i have seemed to see is it works ok with the older 9.1.1036 (Beta) but does not in 9.1.1131. so it seemed to be our connectivity\firewall\virtual machine was ok , was just the firmware on the thin client that seemed to be at fault.

    But i will definitely comb through your post and confirm, some  great info there, and some reg keys i was not aware of. Thanks again for posting!

    #81806
    Avatarbrian1020
    Participant
    • Total Post: 186
    • Jacked into The Matrix
    • ★★★★★★

    I can confirm:

    • Cisco WebEx Meetings app v41.3.0.113
    • Cisco WebEx Meetings plugin 40.10.11.15.4 (from Dell site)
    • WTOS 9.1.1131

    WebEx VDI

    #81808
    AvatarWyseVet
    Participant
    • Total Post: 13
    • Regular Joe
    • ★★

    Great , again good info. that’s a slightly newer version of Webex meetings than we are on (we are on 40.10.12.19) so i may need to test that version out. Have you seen anything stated about version correlations from the plugin to the Webex meetings app and also the Webex site version? do they have to match in a certain range, doenst matter etc? Have not seen clear info on that . Have a great day and thanks for the tips!

     

     

    #90715
    AvatarWyseVet
    Participant
    • Total Post: 13
    • Regular Joe
    • ★★

    Good afternoon brian1020, wanted to ask if you have updated to WMS hotfix 3.1.1 as part of getting Webex package working (or what version you are running?). So far i have had no luck with the 9.1.1131 software ,and working with Dell Tech support they have asked for logs etc but have no fix  yet. Our shop is still at 40.10.12.19 version Webex site and software .. so maybe thats it?  But it still seems strange that i can connect to the same Xendesktop using Windows laptop with the Webex VDI plugin , works fine .  Thanks for the info you have already provided..

    • This reply was modified 2 months ago by AvatarWyseVet.
    #90739
    Avatarbrian1020
    Participant
    • Total Post: 186
    • Jacked into The Matrix
    • ★★★★★★

    We use WMS Public Cloud so it was updated last week I believe. Things are still working without issue.

    Is there a reason you can’t move forward with a newer version of WebEx just for testing?

    You have the “VDI” turned on in the WebEx admin console and the registry edits on the desktop install?

    #93274
    AvatarWyseVet
    Participant
    • Total Post: 13
    • Regular Joe
    • ★★

    Wanted to come back and report in, got Webex VDI working finally i had missed some settings inside WMS itself. . It turned out to be a setting in WMS for the virtual channel. I had to import new config UI package into WMS itself, to then have new WMS policy settings available  about virtual channels . The Webex Meeting channel i guess is off by default. Found the fix from very helpful post  on their community. I think some of the info Brian had posted , we must have already had setup by our Webex team, i just needed this last setting to engage. See info here:

     

    https://www.dell.com/community/Wyse-ThinOS/Webex-Meetings-VDI-with-ThinOS-9-1-not-working/m-p/7826320/emcs_t/S2h8ZW1haWx8cmVhc29uX2JveF9zdWJzY3JpcHRpb258S00yOEo0T0U4TkVQOEx8NzgyNjMyMHxPVEhFUlN8aEs#M3387 

    • This reply was modified 1 month, 3 weeks ago by AvatarWyseVet.
    #93277
    Avatarbrian1020
    Participant
    • Total Post: 186
    • Jacked into The Matrix
    • ★★★★★★

    Glad you got it working. To be fair I did mention that in my February 22 post

    For the record, this was the one that finally got it working

    [HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Spark Native] “isVDIEnv” = “true”, datatype:REG_EXPAND_SZ

    Also, for obvious reasons, make sure your turn on the Citrix Virtual Channels for the different unified communications in WMS for the policy under Citrix Session Settings… Zoom VDI, WebEx VDI, Teams VDI etc.

     

    I now have both Zoom VDI and WebEx VDI working.”

Viewing 11 posts - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.