Release notes of 5.5.2 (12513.0205)
Resolved Issues
-Minor bug fixes
-Resolved an issue for a subset of users regarding screenshots disappearing before being sent in chat.Release notes of 5.5.1 (12484.0202)
Resolved Issues
-Minor bug fixes
-Resolved an issue with the GPO/MSI flagRelease notes of 5.5.0 (12467.0131)
Changes to existing features
-Relocated and enhanced attendee view controls for webinars
-Persistent non-verbal feedback
-Enhancement to alternative host feature
General features
-Block or allow only participants from specific countries/regions
-View synced contacts in sub-folders
-Rotate camera
-Additional MSI/GPO options
Meeting/webinar features
-Share and play video files directly into meeting
-Blurred background
-Share mono or stereo sound
Meeting features
-Meeting reactions for End-to-End Encrypted meetings
-1:1 private chat for End-to-End Encrypted meetings
Phone features
-SMS for international phone numbers
-Support for SMS and MMS messages in a single message bubble
-Add contacts without specifying an email address
-Additional ringtone
-Voicemail notifications
-Group call pickup
Chat features
-Back to previous chat
-Request contact connections directly from chat channel
Resolved Issues
-Security enhancements
-Minor bug fixesRelease notes of 5.4.9 (59931.0110)
Changes to existing features
-Blocking or warning of unencrypted traffic
General features
-Additional MSI/GPO option
-Do Not Disturb when sharing - EnableDoNotDisturbInSharing
-Enforce internal meeting authentication - SetDevicePolicyToken
Meeting features
-Host can admit participants from the Waiting Room while within a Breakout Room
Resolved Issues
-Security enhancements
-Minor bug fixesRelease notes of 5.4.7 (59780.1220)
General features
-Support for Apple Silicon processors
-Enhanced cloud contact integration for chat/call features
Meeting/webinar features
-Enhanced nonverbal feedback and reactions
-Raise hand for host and co-host
-Poll reports available during live session
Meeting features
-Improved grouping of security options when scheduling
Phone features
-Support for text messaging (SMS and MMS)
-Enhancements for call queues with call monitoring
-Call end chime
-Launch an external app or a URL for incoming calls
Resolved Issues
-Minor bug fixes
-Security enhancementsRelease notes of 5.4.6 (59301.1211)
Resolved Issues
-Minor bug fixesRelease notes of 5.4.6 (59296.1207)
Changes to existing features
-Change to default behavior of desktop notifications for upcoming meetings
General features
-Partially encrypted meeting warning
-Additional MSI/GPO option
Meeting features
-Enhanced co-host privileges over Breakout Rooms
-Move participants to main session from breakout room
Phone features
-Enhanced notification for unknown emergency address
Resolved Issues
-Minor fixes related to macOS Big Sur update
-Minor bug fixesRelease notes of 5.4.4 (58903.1122)
-Fix virtual background High CPU issue in Big SurRelease notes of 5.4.3 (58887.1115)
Changes to existing features
-Non-video meeting interface will appear the same as a video meeting with video off
Meeting/webinar features
-Share multiple programs at once
Meeting features
-Enhanced in-meeting user abuse reporting
-Suspend participant activity
Chat features
-Pin chat messages
Phone features
-Enhancements to History and Voicemail tabs
Resolved Issues
-Security enhancements
-Minor bug fixesRelease notes of 5.4.2 (58740.1105)
Resolved Issues
-Minor bug fixesRelease notes of 5.4.1 (58698.1027)
Resolved Issues
-Minor bug fixesRelease notes of 5.4.0 (58631.1025)
General features
-Sync sub-folders in cloud contacts
-Enhanced login for Zoom for Government users
Meeting/webinar features
-Scheduling with custom Join Before Host time limit
Meeting features
-End-to-end (E2E) encryption for meetings
-Additional share options with Proximity Share to Zoom Rooms
-Change ringtone for meeting invites and phone calls
-Improved pre-assigned Breakout Rooms behavior
Chat features
-Search starred messages
-File size restrictions
Phone features
-Bootstrap mode for nomadic emergency services
-Call notifications for busy call queue members
-Opt out of specific call queues
Resolved Issues
-Security enhancements
-Minor bug fixesRelease notes of 5.3.2 (53291.1011)
General features
-Additional MSI/GPO options
Meeting/webinar features
-Poll reports available during live session
Webinar features
-Hyperlink support for Q&A
-Q&A indicates other panelist is responding to question
-Dismissed Q&A questions hidden from attendees
Resolved Issues
-Minor bug fixesRelease notes of 5.3.1 (52877.0927)
Resolved Issues
-Minor bug fixesRelease notes of 5.3.0 (52651.0920)
General features
-Calendar Integration sync improvement
-Enhanced Edit Country interface when scheduling
-Studio Effects
-Enhanced scheduling with default settings
-Additional MSI/GPO Options
-Spotlight Self when speaking
-Display up to 49 participants per screen in Gallery View
-Remind me () minutes before my upcoming meetings
-Uninstall desktop client via MDM
Meeting/webinar features
-Roll-up Closed Captioning
-Virtual Background not compatible explanation
Meeting features
-Self-select Breakout Room
-Share files with Microsoft SharePoint
Chat features
-Hide chat bots in IM list
-Right-click menu for links in IM chat
-Improved image preview and image viewer
-Enhanced Link Preview
-Enhanced Search
-Mark as Unread for images and files
Resolved Issues
-Resolved issue with Breakout rooms not following main session’s settings/restrictions
-Resolved issue with some webinar chats not being saved
-Resolved issue with chat messages being copyable in HIPAA compliant meetings
-Resolved issue with View More Settings option in client not routing to customer’s vanity page, if logged in via SSO
-Minor bug fixes
zoom
Re: zoom
Re: zoom
https://datacenterfrontier.com/inside-z ... and-cloud/
Most of the company's colocation infrastructure is housed at Equinix, which has been working with Zoom since 2015. As of November 2019, Zoom had deployments in nine Equinix data centers – Amsterdam, Frankfurt, Hong Kong, Melbourne, New York, Tokyo, Toronto, Silicon Valley and Sydney.May 22, 2020
https://www.computerweekly.com/news/252 ... l-with-AWS
Zoom Video Communications has signed a multi-year preferred provider deal with long-standing technology collaborator Amazon Web Services (AWS), several months after naming Oracle as a core cloud infrastructure partner.Dec. 1, 2020
https://www.oracle.com/ca-en/cloud/data-regions/
US East (Ashburn) US West (Phoenix) US West (San Jose) Canada Southeast (Toronto) Canada Southeast (Montreal) UK South (London) UK West (Newport) Germany Central (Frankfurt) Switzerland North (Zurich) Netherlands Northwest (Amsterdam) Saudi Arabia West (Jeddah) UAE East (Dubai) Brazil East (Sao Paulo) Chile Central (Santiago) Japan East (Tokyo) Japan Central (Osaka) South Korea Central (Seoul) South Korea North (Chuncheon) Australia East (Sydney) Australia Southeast (Melbourne) India West (Mumbai) India South (Hyderabad)
Re: zoom
uvic zoom now also has live transcript features https://support.zoom.us/hc/en-us/articl ... nscription
Live transcription currently only supports English and the accuracy of the feature depends on many variables, such as but not limited to:
- Background noise
- Volume and clarity of the speaker’s voice
- Speaker's proficiency with the English language
- Lexicons and dialects specific to a geography or community
Live transcription Prerequisites
- Account type: Pro, Business, Education, Enterprise
Note: Approved K-12 accounts and other accounts upon request can also have access to this feature.- Zoom desktop client for Windows, macOS: version 5.0.2 or higher
- Zoom mobile app for Android and iOS: version 5.0.2 or higher
not 100% accurate but often good enough
Re: zoom
info provided by a student
Attached are the Zoom observations from China.
Zoom datacenter
https://support.zoom.us/hc/en-us/articl ... d-webinars
https://support.zoom.us/hc/en-us/articles/360054877391/According to the first link, I found
Code: Select all
Account owners or admins can opt in for their account to use the China data center at any time. If you do not opt in by April 25, 2020, your account will not be able to connect to mainland China for data transit. Users in mainland China will connect to data centers outside of China and therefore may experience performance issues.So it seems whether or not China's data centers are selected, Zoom will not connect to them anyway now.
But I'm not sure whether HK data centers are included in the above statements, and why Zoom connect me to US data centers, not HK.Login process
If I use a free account (my personal account) to login directly from China, Zoom servers will ban my login, sends a response back like this
Code: Select all
[code]HTTP/1.1 200 Date: Sun, 09 May 2021 06:33:07 GMT Content-Type: application/x-protobuf;charset=UTF-8 Content-Length: 66 Connection: keep-alive x-zm-trackingid: WEB_c8d2f21dea41e109fba8dbc4c060a163 X-Content-Type-Options: nosniff Cache-Control: no-cache, no-store Pragma: no-cache Expires: Thu, 01 Jan 1970 00:00:00 GMT Set-Cookie: cred=7FFF4CD40CA8125916AE56DCE4509C6A; Path=/; Secure; HttpOnly Set-Cookie: _zm_ctaid=JitkpExoSB26Wbx3wa1zFA.1620541987423.2e74fcf00d357560925e5ba759c444e9; Domain=.zoom.us; Expires=Sun, 09-May-2021 08:33:07 GMT; Path=/; Secure; HttpOnly Set-Cookie: _zm_chtaid=759; Domain=.zoom.us; Expires=Sun, 09-May-2021 08:33:07 GMT; Path=/; Secure; HttpOnly Set-Cookie: _zm_ctaid=P0jQCPR8RsqzmLQDazeOEw.1620541987491.2fcd5604c6a1632b201cbb5fe94e07ac; Domain=.zoom.us; Expires=Sun, 09-May-2021 08:33:07 GMT; Path=/; Secure; HttpOnly Set-Cookie: _zm_chtaid=795; Domain=.zoom.us; Expires=Sun, 09-May-2021 08:33:07 GMT; Path=/; Secure; HttpOnly Strict-Transport-Security: max-age=31536000; includeSubDomains X-XSS-Protection: 1; mode=block Referrer-Policy: strict-origin-when-cross-origin � 5Sorry, free users are not available in your location.� �����/[/code]The login http requests mainly involes the following domains:
Code: Select all
contactservice.zoom.us us02web.zoom.us us02www3.zoom.us xmppapi.zoom.usmtr results
The first mtr result before I ticked China and HK datacenters in Zoom's profile
Code: Select all
[code] My traceroute [v0.94] local (192.168.100.196) -> 134.224.56.81 2021-05-09T14:44:44+0800 Keys: Help Display mode Restart statistics Order of fields quit Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. 192.168.100.1 0.0% 54 4.2 6.3 3.1 119.0 15.7 2. 180.171.72.1 0.0% 53 7.0 10.2 6.0 82.8 10.5 3. 61.152.54.101 0.0% 53 8.5 8.7 6.1 51.4 6.0 4. 61.152.25.202 30.2% 53 8.7 9.2 6.6 20.5 2.5 5. 202.97.57.157 28.3% 53 8.3 11.6 6.9 134.5 20.5 6. 202.97.12.210 49.1% 53 9.8 8.6 6.4 9.8 0.7 7. 202.97.51.210 0.0% 53 150.0 153.6 147.3 232.5 11.7 8. 202.97.81.182 0.0% 53 152.5 152.3 145.0 193.6 7.3 9. 218.30.53.6 3.8% 53 146.6 139.4 135.2 170.3 5.3 10. (waiting for reply) 11. (waiting for reply) 12. 54.240.242.234 50.9% 53 160.0 164.0 158.1 217.7 11.7 13. 150.222.97.15 0.0% 53 134.2 137.6 133.6 152.7 4.5 14. 150.222.97.24 0.0% 53 156.2 158.1 154.2 231.6 10.5 15. 52.93.133.80 3.8% 53 166.1 167.5 163.7 198.7 4.8 16. (waiting for reply) 17. (waiting for reply) 18. (waiting for reply) 19. (waiting for reply) 20. (waiting for reply) 21. (waiting for reply) 22. 52.93.12.46 0.0% 53 157.2 159.1 155.1 269.0 15.5 23. 52.93.12.33 0.0% 53 156.1 158.6 153.4 233.7 12.8 24. 52.93.12.68 0.0% 53 160.0 159.5 156.4 203.1 6.4 25. 52.93.12.101 0.0% 53 160.8 157.9 154.7 170.2 2.2 26. 52.93.15.223 0.0% 53 157.1 161.6 156.2 305.1 20.3 27. (waiting for reply)[/code]The second mtr result after I selected China and HK datacenters
[code] My traceroute [v0.94]
local (192.168.100.196) -> 193.122.248.141 2021-05-09T14:43:21+0800
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.100.1 0.0% 382 4.0 3.3 1.6 7.3 0.6
2. 180.171.72.1 0.0% 382 8.0 8.3 4.8 89.3 5.1
3. 61.152.53.125 64.4% 382 8.3 7.9 4.7 21.1 2.3
4. 61.152.24.142 22.8% 382 8.9 9.0 6.3 22.8 2.1
5. 202.97.83.33 90.8% 382 12.7 10.3 7.1 15.7 1.9
6. 202.97.83.38 2.6% 382 13.2 13.4 7.1 55.3 3.4
7. 202.97.52.250 0.3% 382 130.8 138.7 130.0 172.8 5.0
202.97.42.166
8. 202.97.90.118 0.3% 382 159.3 153.8 139.3 307.1 9.9
202.97.50.74
9. xe-8-3-2.edge2.sanjose3.level3.net 14.1% 382 140.4 141.7 137.5 266.8 7.9
9-1-6.ear1.losangeles1.level3.net
10. ae-1-3510.edge5.washington12.level3.net 0.3% 382 201.8 204.4 198.7 376.5 9.9
ae-2-3610.edge5.washington12.level3.net
11. 140.91.196.60 0.0% 382 220.4 220.8 217.9 334.8 6.0
12. (waiting for reply)[/code]
Re: zoom
I did another test about Zoom today, and found out that in some cases, Zoom uses p2p connection instead of routing traffic through Zoom servers.
Attached are the details of my tests. Based on the current information, only 1-1 meeting supports p2p connection, but I haven't found the pattern or under which circumstances will p2p connection be initiated because I cannot reproduce stably even under the same network setup.
Another fact is that even though Zoom has data centers in Australia and Singapore, in my tests Zoom clients still connect to US data centers. Because free personal accounts cannot change data center settings, these tests were conducted using UVic Zoom account, I'm not sure if it's related to UVic Zoom admin settings.
Re: zoom
clarkzjw wrote:I did another test about Zoom today, and found out that in some cases, Zoom uses p2p connection instead of routing traffic through Zoom servers.
Attached are the details of my tests. Based on the current information, only 1-1 meeting supports p2p connection, but I haven't found the pattern or under which circumstances will p2p connection be initiated because I cannot reproduce stably even under the same network setup.
one-on-one is always p2p if possible (so zoom can boast that one-on-one is always free and unlimited for everyone, as it has little overhead on zoom servers when p2p is not blocked by nat/firewall 
when there are more than two participants, zoom uses its servers (or multi-control unit, mcu) to aggregate and relay, so it limits 40 minutes for free accounts. ideally, users shall be associated with their nearest mcu, and mcu can interconnect with other mcu's in a more efficient way for a better performance for everyone
Another fact is that even though Zoom has data centers in Australia and Singapore, in my tests Zoom clients still connect to US data centers. Because free personal accounts cannot change data center settings, these tests were conducted using UVic Zoom account, I'm not sure if it's related to UVic Zoom admin settings.
uvic zoom is provisioned in the states, so by default it uses servers in the states. it can be configured/limited by uvic zoom account manager too
Re: zoom
thanks ansh for a tcpdump to find out the zoom server he's associated with while in india
22:33:26.749482 IP 134.224.18.47.8801 > ansh-inspiron-3576.51345: UDP, length 113
22:33:26.749610 IP 134.224.18.47.8801 > ansh-inspiron-3576.34571: UDP, length 27
22:33:26.762103 IP 134.224.18.47.8801 > ansh-inspiron-3576.51345: UDP, length 111
22:33:26.762281 IP 134.224.18.47.8801 > ansh-inspiron-3576.34571: UDP, length 277
and traceroute
> traceroute 134.224.18.47
traceroute to 134.224.18.47 (134.224.18.47), 30 hops max, 60 byte packets
1 _gateway (192.168.43.1) 8.305 ms 8.651 ms 8.706 ms
2 100.64.63.254 (100.64.63.254) 49.233 ms 56.373 ms 66.767 ms
3 192.168.34.217 (192.168.34.217) 50.313 ms 49.975 ms 50.391 ms
4 192.168.48.2 (192.168.48.2) 49.189 ms 49.030 ms 49.954 ms
5 192.168.48.33 (192.168.48.33) 49.668 ms 49.623 ms 50.939 ms
6 nsg-corporate-225.104.185.122.airtel.in (122.185.104.225) 49.374 ms 28.250 ms 29.120 ms
7 182.79.134.223 (182.79.134.223) 169.234 ms 116.119.68.60 (116.119.68.60) 182.586 ms 182.79.134.223 (182.79.134.223) 195.379 ms
8 ldn-b7-link.ip.twelve99.net (62.115.175.230) 183.093 ms 182.986 ms 183.524 ms
9 ldn-bb1-link.ip.twelve99.net (62.115.138.150) 176.930 ms 189.868 ms ldn-bb4-link.ip.twelve99.net (62.115.138.154) 176.964 ms
10 nyk-bb1-link.ip.twelve99.net (62.115.112.244) 261.713 ms nyk-bb2-link.ip.twelve99.net (62.115.113.20) 267.308 ms 267.165 ms
11 ash-bb2-link.ip.
vs what i see from victoria while in the main session
10:10:18.815459 IP paneth.64678 > 134.224.18.8.8801: UDP, length 81
10:10:18.815504 IP paneth.55795 > 134.224.18.8.8801: UDP, length 81
10:10:18.815520 IP paneth.65452 > 134.224.18.8.8801: UDP, length 81
10:10:18.894914 IP 134.224.18.8.8801 > paneth.55795: UDP, length 81
10:10:18.895338 IP 134.224.18.8.8801 > paneth.64678: UDP, length 81
10:10:18.896090 IP 134.224.18.8.8801 > paneth.65452: UDP, length 81
10:10:19.124546 IP 134.224.18.8.8801 > paneth.55795: UDP, length 81
and once i joined the breakout room
10:17:27.577900 IP 134.224.18.47.8801 > paneth.64436: UDP, length 272
10:17:27.597920 IP 134.224.18.47.8801 > paneth.64436: UDP, length 266
10:17:27.610910 IP 134.224.18.47.8801 > paneth.64436: UDP, length 64
10:17:27.618656 IP 134.224.18.47.8801 > paneth.64436: UDP, length 260
10:17:27.638720 IP 134.224.18.47.8801 > paneth.64436: UDP, length 241
10:17:27.658681 IP 134.224.18.47.8801 > paneth.64436: UDP, length 216
and if i do not join the audio
10:18:37.465004 IP paneth.49742 > 134.224.18.47.8801: UDP, length 27
10:18:37.480347 IP 134.224.18.47.8801 > paneth.49742: UDP, length 27
10:18:37.515890 IP paneth.49742 > 134.224.18.47.8801: UDP, length 27
10:18:37.531064 IP 134.224.18.47.8801 > paneth.49742: UDP, length 27
10:18:37.566834 IP paneth.49742 > 134.224.18.47.8801: UDP, length 27
10:18:37.581811 IP 134.224.18.47.8801 > paneth.49742: UDP, length 27
so it is clear that zoom allocate servers (in the same data center) for different breakout rooms, and uvic zoom (most likely due to account manager configuration) does not allow oversea users to connect to their local zoom servers
i will talk to the uvic systems admin again---hopefully our networking research people can help not only ourselves but also uvic community use networks better
Re: zoom
Release notes of 5.7.0 (446)
General features
-Support for gender pronouns
-Scheduling privilege and alternative host between linked master/sub accounts
-Authentication profile enhancement: Domain block-list
-Consistent date formatting
Meeting/webinar features
-Custom video filters
-Request Live Transcription enablement as participant
-Pairing with Zoom Rooms on Zoom desktop client
-NDI live streaming consent
-Hide full transcript panel
Meeting features
-Share screen to all Breakout Rooms
Webinar features
-Webinar File Transfer enhancement: file type and panelists restrictions
Chat features
-Improvements to chat sidebar
-Enhanced data privacy notification for chat channels with enhanced chat encryption
Phone features
-Display additional phone numbers in user contact card
-View number of callers waiting in call queue
-Enhancements to invite by phone
-Check connection to Zoom Phone server
-Enhancement to call logs
Resolved Issues
-Resolved an issue regarding a slight delay in virtual background when joining a meeting
-Resolved an issue with the video playback feature and stereo audio in a video
-Resolved an issue regarding link preview inconsistencies
-Security enhancements
-Minor Bug fixes
Re: zoom
up here, in canada
Code: Select all
$ sudo tcpdump port 8801
Password:
tcpdump: data link type PKTAP
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on pktap, link-type PKTAP (Apple DLT_PKTAP), capture size 262144 bytes
09:02:24.041883 IP paneth.60814 > 193.123.30.5.8801: UDP, length 430
09:02:24.053861 IP paneth.57004 > 193.123.30.5.8801: UDP, length 551
09:02:24.053879 IP paneth.57004 > 193.123.30.5.8801: UDP, length 946with the zoom server down there
Code: Select all
$ nslookup 193.123.30.5
Server: 1.1.1.1
Address: 1.1.1.1#53
** server can't find 5.30.123.193.in-addr.arpa: NXDOMAINby oracle
Code: Select all
$ whois 193.123.30.5
% IANA WHOIS server
% for more information on IANA, visit http://www.iana.org
% This query returned 1 object
refer: whois.ripe.net
inetnum: 193.0.0.0 - 193.255.255.255
organisation: RIPE NCC
status: ALLOCATED
whois: whois.ripe.net
changed: 1993-05
source: IANA
# whois.ripe.net
inetnum: 193.122.0.0 - 193.123.255.255
netname: NON-RIPE-NCC-MANAGED-ADDRESS-BLOCK
descr: IPv4 address block not managed by the RIPE NCC
remarks: ------------------------------------------------------
remarks:
remarks: For registration information,
remarks: you can consult the following sources:
remarks:
remarks: IANA
remarks: http://www.iana.org/assignments/ipv4-address-space
remarks: http://www.iana.org/assignments/iana-ipv4-special-registry
remarks: http://www.iana.org/assignments/ipv4-recovered-address-space
remarks:
remarks: AFRINIC (Africa)
remarks: http://www.afrinic.net/ whois.afrinic.net
remarks:
remarks: APNIC (Asia Pacific)
remarks: http://www.apnic.net/ whois.apnic.net
remarks:
remarks: ARIN (Northern America)
remarks: http://www.arin.net/ whois.arin.net
remarks:
remarks: LACNIC (Latin America and the Carribean)
remarks: http://www.lacnic.net/ whois.lacnic.net
remarks:
remarks: ------------------------------------------------------
country: EU # Country is really world wide
admin-c: IANA1-RIPE
tech-c: IANA1-RIPE
status: ALLOCATED UNSPECIFIED
mnt-by: RIPE-NCC-HM-MNT
created: 2019-01-07T10:44:05Z
last-modified: 2019-01-07T10:44:05Z
source: RIPE
role: Internet Assigned Numbers Authority
address: see http://www.iana.org.
admin-c: IANA1-RIPE
tech-c: IANA1-RIPE
nic-hdl: IANA1-RIPE
remarks: For more information on IANA services
remarks: go to IANA web site at http://www.iana.org.
mnt-by: RIPE-NCC-MNT
created: 1970-01-01T00:00:00Z
last-modified: 2001-09-22T09:31:27Z
source: RIPE # Filtered
% This query was served by the RIPE Database Query Service version 1.101 (WAGYU)
# whois.arin.net
NetRange: 193.122.0.0 - 193.123.255.255
CIDR: 193.122.0.0/15
NetName: OC-195
NetHandle: NET-193-122-0-0-1
Parent: RIPE-CBLK (NET-193-0-0-0-1)
NetType: Direct Allocation
OriginAS:
Organization: Oracle Corporation (ORACLE-4)
RegDate: 2016-09-26
Updated: 2017-11-27
Ref: https://rdap.arin.net/registry/ip/193.122.0.0
OrgName: Oracle Corporation
OrgId: ORACLE-4
Address: 500 Oracle Parkway
Address: Attn: Domain Administrator
City: Redwood Shores
StateProv: CA
PostalCode: 94065
Country: US
RegDate: 1988-04-29
Updated: 2021-01-13
Ref: https://rdap.arin.net/registry/entity/ORACLE-4
OrgTechHandle: ORACL1-ARIN
OrgTechName: ORACLE NIS
OrgTechPhone: +1-650-506-2220
OrgTechEmail: domain-contact_ww_grp@oracle.com
OrgTechRef: https://rdap.arin.net/registry/entity/ORACL1-ARIN
OrgRoutingHandle: ORACL2-ARIN
OrgRoutingName: ORACLEROUTING
OrgRoutingPhone: +1-800-392-2999
OrgRoutingEmail: network-contact_ww@oracle.com
OrgRoutingRef: https://rdap.arin.net/registry/entity/ORACL2-ARIN
OrgAbuseHandle: NISAM-ARIN
OrgAbuseName: Network Information Systems Abuse Management
OrgAbusePhone: +1-650-506-2220
OrgAbuseEmail: abuse@oracleemaildelivery.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/NISAM-ARINand how to get there from here
Code: Select all
$ sudo tcptraceroute 193.123.30.5
Selected device en0, address 192.168.1.49, port 49231 for outgoing packets
Tracing the path to 193.123.30.5 on TCP port 80 (http), 30 hops max
1 192.168.1.252 4.379 ms 4.454 ms 4.383 ms
2 70.66.224.1 21.543 ms 12.825 ms 14.620 ms
3 rd1cv-be125-1.gv.shawcable.net (64.59.161.241) 18.397 ms 17.711 ms 19.953 ms
4 rd1lp-be1.gv.shawcable.net (66.163.72.22) 20.689 ms 19.318 ms 22.180 ms
5 rc1wt-be40.wa.shawcable.net (66.163.68.18) 19.213 ms 20.056 ms 23.085 ms
6 ae22.cr4-sea2.ip4.gtt.net (209.120.141.209) 19.965 ms 19.330 ms 20.767 ms
7 ae12.cr3-phx1.ip4.gtt.net (89.149.186.54) 58.434 ms 58.484 ms 55.347 ms
8 140.91.195.5 55.354 ms 55.106 ms 56.042 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *and zoom stats for stereo audio
- Screen Shot 2021-07-01 at 8.39.25 AM.png (95.31 KiB) Viewed 6526 times
and video-optimized screen share
- Screen Shot 2021-07-01 at 8.39.35 AM.png (98.3 KiB) Viewed 6526 times
thanks jinwei
- jinwei-audio.jpg (55.2 KiB) Viewed 6526 times
- jinwei-screen.jpg (62.51 KiB) Viewed 6526 times
, fatima
- fatima-audio.png (28.06 KiB) Viewed 6526 times
- fatima-screen.png (30.35 KiB) Viewed 6526 times
and navid
- navid-audio.png (29.19 KiB) Viewed 6526 times
- navid-screen.png (33.85 KiB) Viewed 6526 times
Re: zoom
zoom removed itself from chinese market but left with a bunch of oem partners, each with a different client but with the same zoom code base too
e.g., zhumu uses udp port 8801 as well
Code: Select all
19:32:23.343431 IP 89.95.158-98.q9.net.8801 > paneth.57925: UDP, length 230
19:32:23.345786 IP 89.95.158-98.q9.net.8801 > paneth.57925: UDP, length 89
19:32:23.350651 IP 89.95.158-98.q9.net.8801 > paneth.57925: UDP, length 49
19:32:23.360527 IP 89.95.158-98.q9.net.8801 > paneth.57925: UDP, length 221
19:32:23.361861 IP 89.95.158-98.q9.net.8801 > paneth.57925: UDP, length 57
19:32:23.361864 IP 89.95.158-98.q9.net.8801 > paneth.57925: UDP, length 83
19:32:23.361974 IP paneth.63136 > 89.95.158-98.q9.net.8801: UDP, length 15ping blocked
Code: Select all
$ ping -c 5 89.95.158-98.q9.net
PING 89.95.158-98.q9.net (98.158.95.89): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
--- 89.95.158-98.q9.net ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet losstcptraceroute
Code: Select all
$ sudo tcptraceroute 89.95.158-98.q9.net
Selected device en0, address 192.168.1.49, port 60872 for outgoing packets
Tracing the path to 89.95.158-98.q9.net (98.158.95.89) on TCP port 80 (http), 30 hops max
1 192.168.1.252 4.556 ms 4.620 ms 4.539 ms
2 70.66.224.1 14.599 ms 16.579 ms 12.995 ms
3 rd1cv-be125-1.gv.shawcable.net (64.59.161.241) 16.181 ms 15.478 ms 19.204 ms
4 rd1lp-be1.gv.shawcable.net (66.163.72.22) 15.299 ms 14.756 ms 14.756 ms
5 rc1wt-be40.wa.shawcable.net (66.163.68.18) 16.695 ms 17.589 ms 16.161 ms
6 rc2wt-be18-1.wa.shawcable.net (66.163.64.82) 22.281 ms 16.091 ms 18.732 ms
7 rc3no-be100.cg.shawcable.net (66.163.75.234) 34.289 ms 33.141 ms 33.029 ms
8 rc2nr-be110-1.wp.shawcable.net (66.163.76.58) 52.266 ms 50.112 ms 53.847 ms
9 rc3fs-be25.mt.shawcable.net (66.163.76.22) 72.271 ms 74.600 ms 72.297 ms
10 66.163.66.85 73.058 ms 72.729 ms 73.148 ms
11 * ra1sh-ge4-2-14.mt.bigpipeinc.com (66.244.223.201) 77.538 ms 73.044 ms
12 rx0sh-q9-networks.mt.bigpipeinc.com (66.244.223.202) 72.220 ms 80.844 ms 71.497 ms
13 b1-2.tor1-g-b1-2.brm1.q9.net (216.220.40.165) 70.701 ms 70.715 ms 74.653 ms
14 border1-1-dist1-1.brm1.q9.net (74.200.14.210) 70.714 ms 70.723 ms 72.284 ms
15 dist1-1-access1-2-896.brm1.q9.net (74.200.10.70) 70.738 ms 70.783 ms 73.075 ms
16 67.95.158-98.q9.net (98.158.95.67) 77.544 ms 69.251 ms 71.509 ms
17 28.253.8.93 73.818 ms 71.990 ms 70.739 ms
18 28.253.8.173 80.728 ms 72.855 ms 79.968 ms
19 * * *
20 * * *whois
Code: Select all
$ whois 98.158.95.89
% IANA WHOIS server
% for more information on IANA, visit http://www.iana.org
% This query returned 1 object
refer: whois.arin.net
inetnum: 98.0.0.0 - 98.255.255.255
organisation: ARIN
status: ALLOCATED
whois: whois.arin.net
changed: 2006-10
source: IANA
# whois.arin.net
NetRange: 98.158.80.0 - 98.158.95.255
CIDR: 98.158.80.0/20
NetName: Q9-NET6
NetHandle: NET-98-158-80-0-1
Parent: NET98 (NET-98-0-0-0-0)
NetType: Direct Allocation
OriginAS: AS36031, AS36030, AS27272, AS40341, AS12188
Organization: Q9 Networks Inc. (Q9NT)
RegDate: 2009-12-18
Updated: 2012-02-24
Ref: https://rdap.arin.net/registry/ip/98.158.80.0
OrgName: Q9 Networks Inc.
OrgId: Q9NT
Address: 77 King Street West Suite 4400
City: Toronto
StateProv: ON
PostalCode: M5K-1J3
Country: CA
RegDate:
Updated: 2015-06-11
Ref: https://rdap.arin.net/registry/entity/Q9NT
ReferralServer: rwhois://rwhois.q9.net:4321
OrgAbuseHandle: ZQ8-ARIN
OrgAbuseName: IP Admin
OrgAbusePhone: +1-416-362-7000
OrgAbuseEmail: IPadmin@q9.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/ZQ8-ARIN
OrgTechHandle: ZQ8-ARIN
OrgTechName: IP Admin
OrgTechPhone: +1-416-362-7000
OrgTechEmail: IPadmin@q9.com
OrgTechRef: https://rdap.arin.net/registry/entity/ZQ8-ARIN
RTechHandle: ZQ8-ARIN
RTechName: IP Admin
RTechPhone: +1-416-362-7000
RTechEmail: IPadmin@q9.com
RTechRef: https://rdap.arin.net/registry/entity/ZQ8-ARINwhy don't they support inter-provider meeting, e.g., zoom://123456789 can talk to zhumu://1234567890 , just as xmpp for instant messaging in old days? internetwork is to connect machines and people, not to isolate them into islands or so
Re: zoom
thanks fei for providing his viewpoint on the same zhumu meeting by windump
- windump.png (93.02 KiB) Viewed 6513 times
, ping
- ping.png (30.56 KiB) Viewed 6513 times
and tracert
- tracert.png (34 KiB) Viewed 6513 times
, and from my viewpoint
Code: Select all
$ ping -c 5 103.218.218.237
PING 103.218.218.237 (103.218.218.237): 56 data bytes
64 bytes from 103.218.218.237: icmp_seq=0 ttl=48 time=210.497 ms
64 bytes from 103.218.218.237: icmp_seq=1 ttl=48 time=208.207 ms
64 bytes from 103.218.218.237: icmp_seq=2 ttl=48 time=208.107 ms
64 bytes from 103.218.218.237: icmp_seq=3 ttl=48 time=211.401 ms
64 bytes from 103.218.218.237: icmp_seq=4 ttl=48 time=208.030 ms
--- 103.218.218.237 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 208.030/209.248/211.401/1.419 msand
Code: Select all
$ sudo tcptraceroute 103.218.218.237
Password:
Selected device en0, address 192.168.1.49, port 61269 for outgoing packets
Tracing the path to 103.218.218.237 on TCP port 80 (http), 30 hops max
1 192.168.1.252 4.337 ms 4.615 ms 4.536 ms
2 70.66.224.1 15.416 ms 17.056 ms 15.373 ms
3 rd1cv-be125-1.gv.shawcable.net (64.59.161.241) 14.533 ms 17.600 ms 16.170 ms
4 rd1lp-be1.gv.shawcable.net (66.163.72.22) 15.326 ms 14.537 ms 19.221 ms
5 rc1wt-be40.wa.shawcable.net (66.163.68.18) 19.923 ms 17.656 ms 19.250 ms
6 rc3sj-be60.cl.shawcable.net (66.163.75.90) 39.946 ms 36.952 ms 37.732 ms
7 219.158.33.73 38.434 ms 38.800 ms 47.484 ms
8 219.158.98.9 181.608 ms 182.685 ms 183.725 ms
9 219.158.3.145 180.709 ms 183.538 ms 185.237 ms
10 219.158.5.145 186.924 ms 183.509 ms 186.871 ms
11 219.158.19.226 220.689 ms 218.203 ms 211.453 ms
12 221.4.0.206 214.705 ms 216.792 ms 214.170 ms
13 157.255.159.242 237.707 ms 237.272 ms 236.838 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 103.218.218.237 [closed] 204.362 ms 202.899 ms 203.003 msyes, zhumu (so zoom) does support the client-server==server-client mcu routing too
Re: zoom
Optional Reclaim Host when rejoining
When the original host of a meeting rejoins, they are now given the option to reclaim host controls or remain as a participant or co-host, in order to not disrupt the current host. This feature requires version 5.8.3 or higher and will not be immediately available, as it is dependent on a backend server update currently scheduled for November 14, 2021.
Re: zoom
pan wrote:uvic zoom now allows host to record the meeting to the cloud (finally) with watermark, and the recording will be deleted after 7 days as specified by uvic admin
also uvic zoom has been integrated with echo360 and brightspace, so record to cloud can appear in echo360 automatically for brightspace https://echo360.ca/settings/zoom-settings
Zoom Settings
Automatically transfer all your Zoom Cloud recording content to your Echo360 libraryAutomatically copy Zoom recordings to Echo360
Toggle on to automatically copy all of your Zoom recordings to your Echo360 Library.Automatically create Zoom lessons in Echo360 sections
Use the Meeting List below to map your existing Zoom meetings to Echo360 course sections. Section lessons are created after each meeting has completed. Meetings are always copied to your Echo360 library. For more information on using the Zoom mapping below, see our online help article.
https://learn.echo360.com/hc/en-us/arti ... 0052919752
Echo360 allows you to map your existing scheduled Zoom meetings into existing Echo360 sections. Once mapped, Echo360 automatically creates new classes in the selected Echo360 section and automatically publishes the completed Zoom recordings there. If mapped to a section, your recordings will reside in BOTH your Echo360 library as well as the targeted section.