-
Notifications
You must be signed in to change notification settings - Fork 384
fix(plugin-meetings): saving subnet ip details in reachability with p… #4542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: next
Are you sure you want to change the base?
Conversation
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
|
Added extra fields in the Reachability Results like details (includes subnet's IP, latency, answered-tx, lost-tx, port) , minLatency, and other fields for each protocol in cluster. Implemented Per URL check for UDP, triggering based on the flag(reachabilityEnablePerUrlForUdp) in config.ts. Took a separate class (SubnetReachabilityChecker) and used that class for every UDP URL from CLusterReachability class. Sample Results when Sample Results when |
…/webex-js-sdk into subnet_details_2
…/webex-js-sdk into subnet_details_2
COMPLETES #SPARK-610518
This pull request addresses
Saving the subnet ip details which includes subnet IPs, latency, etc..
by making the following changes
Saved the subnet ip details in reachability results and sending to web-client, implements each UDP URL checks for Reachability.
Change Type
The following scenarios were tested
< ENUMERATE TESTS PERFORMED, WHETHER MANUAL OR AUTOMATED >
The GAI Coding Policy And Copyright Annotation Best Practices
I certified that
Make sure to have followed the contributing guidelines before submitting.