Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
We are in the process of piloting Webex (formerly Teams) as a replacement for Webex Meetings. Our issue is that is people click a "Join" URL from an Outlook invite or similar, it cross launches to the Webex Meetings app, rather than the new Webex Ap...
We have a new deployment of CMS 3.0 and TMS 15.12, with TMS scheduling "Automatic Connect" conferences to VCS X12.6.2 registered endpoints (CE9.14.3, TC7.3..). We have had multiple reports of CE9.x endpoint users muting themselves, then being unable ...
I've got a weird issue with a VCS-C cluster. I have two nodes running X12.6.2. Node 1 is a "cluster of 1" with itself defined as peer 1 (using IP address, everything set to permissive).When I add peer 2, they cluster OK and peer 2 grabs all its con...
I posted this in the Webex forum but didn't get much traction, thought I'd try my luck here. I've got several on-prem VC deployment customers who use the "Join Webex" button to join scheduled Webex meetings via the meeting number. This button of cou...
As most people are aware, Webex invites generally include a SIP URI and meeting number on the invite, e.g.:123 456 789sip:john.doe@company.webex.comHowever, you've also always been able to dial both <meeting-number>@webex.com and <meeting-number>@com...
The assistant can sign up for a "free" Webex account, or can be assigned one in Control Hub, without requiring a paid license.The manager can then log onto your Webex site and set the assistant as a scheduling delegate.
Thanks for the response - the peer IP addresses and certificates remain intact so it doesn't look like it's being removed from the cluster. In addition, yes we do reboot after maintenance mode.
Hi Amit, the cluster configuration is the same on both nodes. After I reboot the second node and lose clustering, I see cluster errors on both nodes. It was the second node where I saw the error in the logs, although I didn't actually check the log...
