Skip to main content

I'm in the U.S. and opened case #10564658 about this topic.


I received an email from RingCentral on Monday 4/6 saying that by Sunday 4/12 I need to have my network admin whitelist the IP address 34.196.189.103/32.


After contacting support to clarify, it sounds like they are saying anyone I invite to a RingCentral Meeting (internal or external) will also have to whitelist this IP address in their firewall or they may not be able to join the meeting, but I'm worried their may be some miscommunication here.


I can't imagine setting up a meeting with a new recruit and sending them a link to a RingCentral meeting along with instructions on how to whitelist an IP address. Is this real?


Weaver - this would apply to companies who only allow access to specific IP addresses or address ranges on the Internet, and block everything else. In that scenario meetings could fail because the new address needs to be added to the permit list. Many (and possibly most) companies allow all traffic going out their firewall except for what they have specifically blocked, in which case the new IP address will just work with no action required.  The other reason customers need to know about the new IP is if you have implemented Quality of Service (QoS) configuration on your network equipment to "mark" and give priority to RingCentral voice and meeting traffic then you will need to add that new IP to your configurations so that it also gets prioritized (we are in that scenario).

Short story - most of the public will not need to take any action, but larger companies and those with tight network security may need to.

Reply


Terms & ConditionsCookie settings