Skip to main content

SIP Trunking Primer

Session Initiation Protocol (SIP) trunking is a popular method for businesses to connect their telephone systems directly to the Public Switched Telephone Network (PSTN) over the internet. It replaces traditional phone lines with a more flexible, cost-effective solution, allowing voice calls to travel over IP networks. However, SIP trunking also requires careful setup and management to avoid common pitfalls.

This article explains what SIP trunking is, details the critical information needed to implement it successfully, highlights potential caveats, and discusses two common methods of SIP trunking: Back-to-Back SIP trunking (gateway-to-gateway) and Registration-based SIP trunking.

What is SIP Trunking?​

SIP trunking is a VoIP solution that uses the SIP protocol to provide voice connectivity between an organization's internal telephone system (often an IP-PBX) and the external PSTN or VoIP provider. Instead of physical phone lines, SIP trunks transmit voice data digitally over an internet connection.

Think of SIP trunks as virtual phone lines that travel over the internet rather than traditional copper wiring.

Required Information for SIP Trunking to Work​

To establish a functioning SIP trunk, your provider and your internal IP-based telephone system will require certain details:

Essential SIP Trunking Information:​

  • Provider SIP Gateway/Proxy Information:

  • SIP Server address (IP or domain)

  • SIP signaling port (typically 5060 or 5061 for secure SIP using TLS)

  • Authentication Details:

  • SIP username and password (for registration-based trunks)

  • SIP authentication methods (Digest authentication is most common)

  • Codec Negotiation Information:

  • Supported codecs (e.g., G.711, G.729, Opus)

  • Codec priorities (preferred codec lists)

  • Dial Plan and Number Formatting:

  • DID (Direct Inward Dialing) numbers assigned to your trunk

  • E.164 or international dialing rules

  • Network Information:

  • Your external (public) IP addresses for firewall configuration

  • Internal IP addressing (for NAT configuration)

  • RTP port range (commonly 10,000 to 20,000 UDP)

Common SIP Trunking Caveats and Troubleshooting​

While SIP trunking is efficient and flexible, there are common pitfalls to avoid during implementation and maintenance:

1. Firewall and Security Issues​

  • SIP signaling (port 5060 or 5061) and RTP ports must be correctly allowed through firewalls.
  • Improper firewall rules can lead to:
  • Calls not connecting.
  • One-way audio issues (when one party can’t hear the other).
  • Consider using SIP-aware firewalls or Session Border Controllers (SBCs) to secure SIP traffic.

2. NAT (Network Address Translation) Problems​

  • NAT translates your internal network addresses to a single external public IP. SIP signaling and RTP traffic can fail if not configured properly.
  • Common issues include:
  • Call failures or dropped calls.
  • Audio distortions or one-way audio.
  • Solutions include using NAT-aware SIP proxies or SBCs, which handle NAT traversal efficiently.

3. RTP Handling​

  • RTP (Real-time Transport Protocol) delivers your voice packets, separate from SIP signaling.
  • Incorrect RTP port range configuration can result in:
  • Poor audio quality or jitter (delays between voice packets).
  • Failed or silent calls.
  • Configure RTP port ranges correctly and ensure adequate bandwidth for quality calls.

Types of SIP Trunking Implementation​

Two main implementations of SIP trunking are commonly used:

1. Back-to-Back SIP Trunking (Gateway-to-Gateway)​

In Back-to-Back SIP Trunking, two gateways (often session border controllers or VoIP gateways) directly communicate with each other without registration. Both gateways must explicitly trust each other's IP addresses.

Use Cases:

  • Large enterprises connecting their internal VoIP infrastructure directly to carriers.
  • Providers offering wholesale voice services.

Key Points:

  • No user/password authentication; relies solely on IP-based trust.
  • Simplifies signaling but requires secure IP configuration.

Typical Configuration:

Enterprise IP-PBX <-> Enterprise SBC <--> Provider SBC <-> PSTN

2. Registration-based SIP Trunking​

In Registration-based SIP Trunking, your internal phone system registers (authenticates) with the provider's SIP proxy server using a username and password. It functions similarly to how a smartphone registers with your mobile provider.

Use Cases:

  • Small to medium-sized businesses.
  • Remote offices or home offices that frequently change IP addresses.

Key Points:

  • Requires username/password authentication.
  • Provides flexibility in dynamic or changing network environments.

Typical Configuration:

Internal IP-PBX or VoIP phone -> Firewall/NAT device -> Internet -> SIP provider

Practical Example: Common Setup Scenario​

Consider a small business connecting to a SIP trunk provider:

  • IP-PBX: Asterisk IP-PBX system
  • Firewall: Cisco ASA or similar firewall
  • SIP provider details:
  • SIP Proxy: sip.provider-example.com
  • SIP Port: 5060 UDP
  • RTP Ports: 10000–20000 UDP
  • Authentication: Username/password provided by SIP provider

Typical Configuration Steps:​

  • Configure firewall rules allowing inbound/outbound UDP ports for SIP (5060) and RTP (10,000–20,000).
  • Configure NAT traversal methods (nat=yes in Asterisk, or equivalent SIP proxy settings).
  • Set codec priorities (G.711 commonly used).
  • Configure SIP registration credentials provided by your SIP trunk provider in your IP-PBX settings.

Conclusion and Best Practices​

SIP trunking offers significant benefits, including reduced communication costs, flexibility, and scalability. However, proper planning and configuration are crucial to a smooth and reliable deployment.

Best Practices to Ensure Success:​

  • Clearly document all required SIP trunking information before deployment.
  • Use Session Border Controllers (SBCs) for enhanced security and NAT handling.
  • Regularly audit firewall rules and network configurations to ensure RTP and SIP signaling remain uninterrupted.
  • Understand clearly whether your scenario calls for Back-to-Back SIP Trunking or Registration-based SIP Trunking.

By proactively addressing common pitfalls—firewall and NAT handling, RTP configurations, and authentication mechanisms—you can reliably implement SIP trunking and enjoy the benefits of modern IP-based telecommunications.