Hi @shrwnaik ,
Might be worth checking if the VM is using a Proxy, judging by the code you are using the python websockets library which says that the client (being your python code) can't use a proxy to connect via websockets to the internet websocket server, I have been shying away from using the quite sensible approach of deploying a client on prem and having it connect via websockets to my cloud websockets server for webex bots because of this, unless the client signs in blood that they will exempt the local VM-local Kubernetes-OpenShift platform from having to connect to the internet via websockets.
If you can use a browser on that VM try the website below to see if you are behind a proxy, I would expect you would get some sort of error when running the code in your VM, but that is not clear to me based on your original description, if you are not behind a proxy then what I am saying here is not your issue and it is what @dtibbe said (firewall/something else killing the connection).
https://whatismyipaddress.com/proxy-check
https://websockets.readthedocs.io/en/stable/reference/features.html#known-limitations
In that same limitation documentation of websockets, it mentions that there is another websocket implementation that does support proxies and it has been succesful in other websockets general cases (nothing to do with webex), I haven't put the cycles to try it because it has been easier to work with customers to no use proxy on the hosts where the software runs, eventually I will run into someone who will force me to put the time, just trying to leave you with an alternative if you actually are behind a proxy:
https://github.com/racinette/websockets_proxy
