Hosted Customer Technical Requirements

Here’s what you need to bring to the table to ensure your system works as expected:

 

From your internet  provider (wide area network or WAN)

  • Public internet access with sub-200ms latency ICMP pings back to the Fonality network.

  • Bandwidth from that delivers reliable and consistent throughput.

  • A minimum of 100 kbps of bandwidth per maximum number of simultaneous phones at any location with a WAN connection, both up and down speed, for voice traffic. Ensure you have enough bandwidth for other data needs, too. Typical small offices may want to provide 1 mbps per employee to be safe.

  • An Internet handoff that provides access to configure LAN routing and firewall rules. Often, this means placing cable modems and other provider-supplied devices into “bridge mode” and using LAN equipment such as a router at the edge of your network.

 

 

At your place (local area network or LAN)

Some firewalls block outbound traffic by default unless specifically allowed. Make sure traffic from  desk phones, smartphones, computers, HUD Mobile, and Wi-Fi users gets through by allowing outbound and responses to Fonality on the following ports:

  • TCP 80 (web admin)

  • UDP 123 (time)

  • TCP 443 (HUD authentication over https)

  • UDP 4000-4031 (HUD Mobile on Wi-Fi)

  • TCP and UDP 5060  (SIP)

  • TCP 5222  (HUD status and control)

  • TCP 5269  (HUD Chat)

  • UDP 10000  through 20000  (RTP)

 

 

Top 5 frequently missed configurations

  1. Allow incoming and outgoing TCP and UDP 5060 and10000-20000 to and from  phone handsets, including any softphones or HUD Mobile users  that might be on Wi-Fi.

  2. Don’t modify SIP packets. No SIP ALG, transformations, fixup SIP, etc.  Just  let it flow.

  3. If there is bandwidth contention, prioritize traffic from and to Fonality using whatever methods are available to do so.

  4. No double NATs (don’t NAT a NAT). It can cause audio quality problems.

  5. Don’t let anything in the network slow down your  audio packets. Be wary of deep packet inspection, latent WAN links, and resource-constrained equipment that cannot keep up with the volume of traffic expected.

Return to Documentation Home I Return to Sangoma Support