This knowledge article discusses information provided by the Orum Engineering Team regarding recommended networking configurations to best sync with the product. Please create a ticket for our Customer Support Team if further assistance or explanation is required.

IMPORTANT: All whitelisting recommendations should be applied to any networks, firewalls, security applications, or other networking applications installed in office locations or on company hardware.

Orum Dialer:

Orum uses WebRTC to transport audio to our telephony server. Because we're establishing an audio connection with your local machine, we have to perform NAT traversal. To do so, your computer will connect to public STUN and TURN servers to get its external IP address and port. This IP and port is communicated to our SIP server, and then audio data is sent via RTP (which operates over UDP) between our SIP server and your local machine. If you have a symmetric NAT, or a firewall dropping UDP packets, it can cause issues here. In the case that your machine is not directly reachable, your traffic may be routed through the TURN server instead to help with routability.

In order for the STUN and TURN protocols to work, please allow outbound UDP and TCP ports to Cloudflare's public servers as listed here: https://developers.cloudflare.com/realtime/turn/

Orum SalesFloor:

Orum uses a 3rd party service provider (Vonage) to drive several of the SalesFloor functionalities. We recommend reviewing their Video API whitelisting recommendations to ensure all data passes as expected.

Embedded Support Application:

Additionally, we use DevRev.ai as our support service application provider. Since this app is embedded directly within Orum, it may be necessary to have ".ai" domains allowed. Please contact the Orum support team if you have any questions.