> ## Documentation Index
> Fetch the complete documentation index at: https://docs.talview.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Network Requirements
What your organization's network must allow for the Proview SDK to work inside an enterprise environment. Written for client-side IT and network administrators configuring firewalls, proxies and whitelists — refer to it during initial onboarding and at periodic IT security audits.
For the specification of the test-taker's machine itself, see [System Requirements](/sdk/system-requirements).
## Network & Bandwidth Requirements
| Use Case | Minimum Requirement | Recommended Requirement |
| --------------------------------------------------------------- | ------------------------------------ | ----------------------------- |
| **Proctoring** | Upload & Download: 512 Kbps | Upload & Download: 5 Mbps |
| **Proctoring - Secondary Camera** *(mobile device, if enabled)* | Upload & Download: 512 Kbps | Upload & Download: 5 Mbps |
| **Latency** | \< 150ms | \< 80ms |
| **Jitter** | \< 30ms | \< 20ms |
| **Packet Loss** | \< 1% | 0% |
| **Connection Type** | Wi-Fi acceptable, Ethernet preferred | Ethernet strongly recommended |
* If a secondary camera is enabled, it streams a parallel video feed for the full test duration — budget bandwidth for both streams.
* For proctoring, wired (Ethernet) connections are preferred for the primary device to minimize video transmission issues.
* SB sessions are sensitive to latency, jitter, and bandwidth dips — encourage test-takers to use a wired connection wherever possible.
## Firewall and Proxy Configuration
> The Proview SDK communicates with Talview's application and media services to enable real-time proctoring, secure content delivery, analytics, and user authentication. To ensure full platform functionality, the following domains and ports must be whitelisted at your organization's firewall and proxy gateways.
SB and the SDK both require uninterrupted access to Talview's domains. Blocking these may prevent SB or the SDK from launching sessions, or from streaming video/audio correctly.
### Domain Whitelisting
Ensure the following domains and ports are accessible over HTTPS (443) and HTTP (80) from all candidate machines:
| Host | Ports | Purpose/Service |
| ------------------------------------ | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| `*.talview.com` | 443, 80 | Talview assessment service, booking service, proctoring services (backend: `supergraph.talview.com/v1/graphql`), live video/audio infrastructure |
| `*.talview.app` | 443, 80 | Proctoring secondary device |
| `*.tlv.cx` | 443, 80 | Content delivery & secure access |
| `turn-vr.talview.com` | 443 (TCP), 3478 (UDP) | TURN relay fallback for restrictive firewalls — required when direct/STUN connections are blocked |
| `*.firebasedatabase.app` | 443, 80 | Backend data access |
| `*.freshdesk.com`, `*.freshchat.com` | 443, 80 | Help center access |
### IP Whitelisting
**Talview Infra IPs – Active Clusters**
> The following IPs power Talview's backend services, including proctoring infrastructure, media handling, and secure test access. These should be unblocked for both egress (outbound) and ingress (inbound) communication as specified.
| IP | Description |
| ----------------- | ----------------------------------------- |
| `51.136.86.154` | Core \[tv-prod-16] — Ingress |
| `20.16.66.17` | Core \[tv-prod-16] — Ingress |
| `20.101.160.199` | Core \[tv-prod-16] — Egress |
| `51.105.132.215` | Platform \[tv-prod-platform-01] — Ingress |
| `50.85.186.100` | Platform \[tv-prod-platform-01] — Egress |
| `135.236.56.144` | VR server/egress — Ingress |
| `108.143.41.13` | VR server/egress — Egress |
| `172.201.191.250` | VR server/egress — Egress |
| `20.234.211.87` | VR server/egress — Egress |
### Video Service
Proctoring's media transport routes audio/video/screen-share through a **dynamic global edge network** rather than fixed per-region IP ranges. Because edge nodes and their IPs can change without notice, **whitelist by domain and port, not by static IP** — do not attempt to pin specific IP ranges for media traffic.
**Minimum requirement:** allow **TCP** on port **443** (signaling, ICE-TCP fallback, and TURN relay over TLS) and **UDP** on port **3478** and the **10000–20000** range for `vr.talview.com` and `turn-vr.talview.com`.
| Port | Protocol | Purpose |
| ----------- | -------- | ------------------------------------------------------ |
| 443 | TCP | Signaling (WSS), ICE-TCP fallback, TURN relay over TLS |
| 10000–20000 | UDP | Media, direct (primary) |
| 3478 | UDP | STUN + TURN/UDP |
If a test-taker is connecting from a mobile network (e.g., for Secondary Camera use), ensure mobile data providers or local firewalls do not restrict these ports. For enterprise environments, opening TCP 443 and UDP 3478 plus the 10000–20000 UDP media range is required for signaling/STUN/TURN/media traffic to succeed when direct peer connections are blocked.
### Proctoring - Secondary Camera (if enabled)
If clients enable Secondary Camera (mobile), the second device must also have open internet access to the same domains listed above — no separate domains or IPs are required for mobile, it connects to the same infrastructure over HTTPS/WebRTC.
## Support
For support, contact Talview at [support@talview.com](mailto:support@talview.com) or via [https://talview.freshdesk.com/en/support/tickets/new](https://talview.freshdesk.com/en/support/tickets/new).
**For IT teams:** for bulk deployments or managed environments, request SB installers in advance and test on representative machines with firewall exceptions configured.