Help Center
How Can We Help You?
Video tutorials, visual guides, and documentation for WOCOM AI, Cloud PBX, and SIP Trunk services.
🌐 Network Requirements
LAN and WAN planning guide for WOCOM Cloud Hosted PBX — cabling, switching, QoS, firewall rules, and bandwidth sizing.
📡 System Components
The key elements that make up a WOCOM Cloud Hosted PBX deployment.
📞 SIP Devices
IP phones, softphones, and ATAs on your premises. Each connects via Ethernet and optionally draws PoE power from the switch.
🔌 Ethernet Switches
Connect SIP devices to each other and the broader network. PoE-capable switches can power phones through the same cable used for data.
🔀 Network Configuration
Phones can share switches with PCs or be placed on separate VLANs for traffic isolation and easier management.
🔗 Ethernet Cabling
Cat5 or higher cabling with RJ-45 connectors links all SIP devices to the network infrastructure.
☁️ Hosted PBX Platform
The WOCOM cloud call-control platform handles call routing, voicemail, IVR, and PSTN connectivity for all your SIP devices.
🌍 Internet (WAN)
Your broadband connection links your site to the WOCOM cloud. BYOB (Bring Your Own Broadband) is supported.
WOCOM Cloud Hosted PBX — Component Overview
🔌 Cabling & Power Infrastructure
Physical layer requirements for reliable voice communications.
If your office network has been established within the past five years, you likely already have the requisite LAN cabling and power infrastructure. Verify these standards are met:
- Category 5 or higher Ethernet cabling (Cat5e or Cat6 recommended)
- RJ-45 connectors on all LAN cable runs
- Sufficient power outlets near each SIP device location
- PoE switches recommended to eliminate separate power adapters for phones
- Power outlets near switches and the access router
Cabling Standards
🔀 Ethernet Switching Guidelines
How to connect SIP devices to your network with optimal performance.
Segmentation Best Practice
Ideally, deploy separate Ethernet switches for SIP devices, keeping the existing PC network unchanged. This simplifies management and ensures voice traffic is isolated from data traffic.
If SIP devices and computers must share the same switches, implement VLANs (802.1Q) to logically segregate traffic and prevent data-heavy operations from impacting voice quality.
- Use 100Mbit or auto-sensing 100/1000Mbit Ethernet switches
- Never use hubs or 10Mbit switches for SIP devices
- If sharing switches, ensure 802.1Q VLAN support
- Implement VLANs to isolate voice from data traffic
Dedicated vs. Shared Switching
Voice 📞
Data 💻
⚡ Quality of Service (QoS)
Prioritize voice traffic over data to ensure crystal-clear phone calls.
🔝 Traffic Prioritization
Configure your router and switches to prioritize SIP and RTP packets above all other traffic types. Voice must always take precedence over data.
📊 Bandwidth Reservation
Reserve a dedicated portion of your WAN bandwidth exclusively for voice traffic. This prevents data-heavy operations from consuming voice capacity.
🏷️ DSCP Marking
SIP devices typically mark voice packets with DSCP EF (Expedited Forwarding). Ensure your network equipment honors these markings end-to-end.
📈 Monitoring
Regularly monitor jitter, latency, and packet loss. Target: latency <150ms, jitter <30ms, packet loss <1% for acceptable voice quality.
- Enable QoS on your router and switches
- Prioritize SIP (UDP/TCP 5060) and RTP (UDP 19560–24560) traffic
- Configure DSCP EF marking for voice packets
- Large bandwidth alone does not guarantee good call quality — QoS is required
🔍 DHCP & DNS Services
Network discovery and configuration services required for SIP device operation.
DHCP Requirements
Every SIP device on your network must receive a unique IP address via DHCP. The DHCP server allocates addresses along with essential network parameters.
- DHCP must provide: IP address/mask, default gateway, DNS server
- Custom DHCP options (e.g., Option 66) are not required and will be ignored
- Ensure sufficient IP address pool for all SIP devices
DNS Requirements
DNS translates domain names into IP addresses, enabling SIP devices to locate WOCOM cloud servers. DNS also supports service redundancy by mapping names to multiple IPs.
- Provide a reliable DNS server to all SIP devices
- DNS must resolve external domains (WOCOM cloud endpoints)
- Consider using a secondary DNS for redundancy
🛡️ Firewall & NAT Configuration
Essential firewall rules and NAT settings for WOCOM Cloud Hosted PBX operation.
Firewall Traffic Flow
Required Firewall Rules
| Service | Protocol / Port | Purpose |
|---|---|---|
| HTTP | TCP/80 | SIP device interaction with WOCOM cloud configuration servers |
| TLS/SSL | TCP/443 | Secure encrypted SIP communication — confidentiality and data protection |
| SIP | UDP/5060 TCP/5060 UDP/10000-20000 TCP/10000-20000 | Call signalling between SIP devices, WOCOM call-control platforms, and gateways |
| RTP | UDP/19560-24560 | Real-time voice media between SIP devices and WOCOM platform |
| NTP | UDP/123 | Clock synchronization for SIP devices |
| DNS | UDP/53 TCP/53 | Name-to-IP resolution for WOCOM service discovery |
NAT (Network Address Translation)
NAT translates multiple private LAN IP addresses to a single public WAN IP. For WOCOM to work correctly, your NAT must be SIP-aware — it needs to maintain a durable binding between each internal SIP device and its external address.
- NAT must be SIP-aware with durable bindings
- Binding lifetime: 30–60 seconds recommended
- Without proper NAT, calls may be one-way or fail to connect
- Enable SIP ALG (Application Layer Gateway) only if your device implements it correctly — otherwise disable it
📊 Bandwidth Planning
Calculate the WAN and LAN bandwidth needed for your deployment.
WAN Bandwidth Formulas
• Available Voice Bandwidth — the lower of download/upload speed, minus data traffic reservation
• 64 Kbps — bandwidth per standard phone call (including ATA devices)
• Users per Simultaneous Call — typically 4 for average office usage
Example Bandwidth Calculations
| Internet Speed | Voice Allocation | Max Calls | Max Phones (4:1) |
|---|---|---|---|
| 2 Mbps upload | 1 Mbps (1,000 Kbps) | 15 calls | 60 phones |
| 5 Mbps upload | 2.5 Mbps (2,500 Kbps) | 39 calls | 156 phones |
| 10 Mbps upload | 5 Mbps (5,000 Kbps) | 78 calls | 312 phones |
| 20 Mbps upload | 10 Mbps (10,000 Kbps) | 156 calls | 624 phones |
LAN Bandwidth
LAN bandwidth is determined by your switch and cabling throughput. Following the cabling and switching requirements in this guide (100Mbit+ switches, Cat5e+ cabling), your LAN should have sufficient capacity. Undersized LANs may experience degraded call quality during peak traffic.
🗺️ Network Topologies
Reference diagrams for common WOCOM Cloud PBX network configurations.
Topology 1 — Single Untagged VLAN (Small Office)
Best for smaller environments with approximately 10 computers and IP phones. A single untagged VLAN is used for both voice and data, simplifying setup and management.
Figure 1.0 — Flat Network (Single VLAN)
Topology 2 — Separate VLANs for Voice & Data (Recommended)
Recommended for most deployments. Separate VLANs logically isolate voice and data traffic, enabling different IP schemes, simplified troubleshooting, and stronger security.
Figure 2.0 — VLAN Separation (Voice + Data)
📱 Compatible Phones & Devices
WOCOM Hosted PBX integrates with a wide range of SIP devices from leading manufacturers.
📞 Polycom VVX Series
- VVX 101 / VVX 201
- VVX 300, 301, 310, 311
- VVX 400, 401, 410, 411
- VVX 500, 501
- VVX 600, 601
- VVX 1500
📞 Grandstream GXP Series
- GXP1600 Series
- GXP1700 Series
- GXP2100 Series
- GXP2100EXT Expansion Module
📞 Grandstream GRP Series
- GRP2612, GRP2613, GRP2614, GRP2615
- GRP2712, GRP2713, GRP2714, GRP2715
📹 Grandstream GXV Video
- GXV3240 / GXV3275
- GXV3370 / GXV3380
📞 Other Supported Brands
- Yealink
- Cisco / Linksys SPA 50x, SPA 122, SPA 30x
- Fanvil
- Htek
- Snom
- Zoiper (Softphone)
Need help planning your network? Contact your dedicated WOCOM account team for personalized guidance.
cloudsupport@wocomja.com | www.wocomja.com