If you’re switching your home phone to VoIP, one of the most common questions is:

“Do I need a VoIP adapter?”

There’s a lot of mixed information online. Some phones are described as “VoIP compatible,” some routers have phone ports built in, and marketplaces don’t always explain the difference clearly. Today we’ll dive in and help you decide if you need a VoIP adapter.

This guide explains, in plain English:

• What an ATA is
• When you need one
• When you don’t
• And how to tell the difference

What Is an ATA?

An ATA (Analogue Telephone Adapter) is a small powered device that allows a traditional landline phone to work with a VoIP service.

Your existing home phone is analogue.
VoIP calls travel over the internet as digital data.

An ATA converts:

• Your voice (analogue) → into digital data for the internet
• Incoming digital data → back into analogue sound for your handset

Think of it as a translator between your old-style phone and modern internet calling.

An ATA Is Not Just a Plug

This is important.

An ATA is not:

• A simple socket adapter
• A BT plug converter
• An ADSL microfilter
• A passive cable

It is a powered electronic device that connects to:

• Your router (via Ethernet)
• Your phone (via standard phone lead)
• A power supply

If it isn’t powered on, your phone will not work.

“VoIP Compatible” Phones on Amazon & eBay

You may see standard home phones described as “VoIP compatible.”

In most cases, this simply means:

They can be used with VoIP — if you have an ATA.

A standard phone with a BT plug or that connects to a wall phone socket is still an analogue phone. It cannot plug directly into your router and work on its own.

If a phone:

• Connects using a BT plug
• Has no Ethernet port
• Has no SIP account settings

It is not a true VoIP phone.

What Is a True VoIP Phone?

A genuine VoIP (IP) phone:

• Connects directly to your router using a network cable
• Allows you to enter SIP account details
• Does not use a BT-style phone plug

Examples include desk phones from Yealink and cordless systems from Gigaset (when used with a SIP-compatible base station).

These do not require an ATA because they already speak “internet language.”

What About My Broadband Router’s Phone Port?

Many modern routers now include a phone socket. This causes a lot of confusion.

Major UK providers such as BT, Sky and Virgin Media often supply routers with a built-in phone port for their own “Digital Voice” services.

However:

• That port is usually locked to the provider’s own voice service
• You normally cannot enter third-party SIP details
• The settings are hidden or restricted
• In some cases, the port won’t function unless their voice package is active

So even if your router has a phone socket, it does not automatically mean you can use it with any VoIP provider.

When can a router’s phone port be used?

• If you are using your broadband provider’s own digital voice service
• If you have a third-party router that allows manual SIP configuration
• In rare cases, with smaller ISPs that allow open SIP settings

With most major UK broadband brands, third-party SIP accounts are not supported on their supplied routers.

When Do You Need an ATA?

You will need an ATA if:

• You want to keep your existing analogue home phone
• Your phone connects via a BT plug
• Your cordless phone base plugs into a phone socket
• Your router does not support third-party SIP accounts

You do not need an ATA if:

• You already have a proper IP/VoIP phone
• Your device connects via Ethernet
• You can enter SIP credentials directly into the phone

Quick Decision Guide

You need an adapter if:

• Your phone connects to a wall socket
• It has a BT plug
• It has no network (Ethernet) port

You don’t need an adapter if:

• Your phone connects to your router with a network cable
• It has SIP account settings
• It is a true IP phone

Do I Need to Configure an ATA?

If you buy a generic ATA online, you would normally need to:

• Find its IP address
• Log into its web interface
• Enter your extension or user ID
• Enter your SIP domain
• Enter your password
• Configure NAT settings (such as rport and keep-alive)
• Set timezone, date, and other parameters

For non-technical users, this can be confusing and time-consuming.

If you get an adapter from us, it comes:

• Fully preconfigured
• Linked to your account
• Ready to plug in
• No SIP settings to enter
• No IP addresses to find
• No technical setup required

Simply connect it to your router and plug in your phone — it’s ready to go.

Still wondering if you need a VoIP adapter?

Switching from a traditional landline to VoIP doesn’t have to be complicated.

Most people can keep their existing phones — they just need the correct equipment.

The key points to remember:

• A standard phone with a BT plug is not a VoIP phone
• A router phone port is often locked to the broadband provider
• An ATA is a powered device that converts analogue to digital
• A true IP phone does not need an adapter

If you’re unsure, check your phone against the quick guide above or contact us and we’ll confirm what you need before you order.

We’re here to make the switch simple.

Want to avoid the hassle of selecting a VoIP phone or adapter, sign up for our residential VoIP service today and we can supply a pre-configured adapter for £50 or get in touch to find out more about phones and adapters available for business.

VoIP Adapters – Frequently Asked Questions

The post Do You Need a VoIP Adapter? Analogue Telephone Adapters Explained appeared first on Plexatalk.

Property management is a fast-moving business. Landlords, tenants, buyers, and sellers all expect quick responses. Every missed call could mean a missed rent payment, an unhappy tenant, or even a lost property sale.

For many estate agents and property managers, the question isn’t whether to invest in a phone system — it’s which one: stick with mobiles, or switch to VoIP?

In this guide, we’ll compare VoIP vs Mobile in detail, looking at costs, features, and how each option supports the unique needs of estate agencies and property management businesses.

1. The Role of Communication in Property Management

• Every interaction matters: arranging viewings, reporting maintenance, handling landlord queries.
• Calls are often urgent — delays frustrate clients.
• A reliable, professional phone system makes the difference between winning instructions and losing clients.

(Keywords: property management communication, estate agent phone systems)

2. Mobile Phones in Property Management

Pros of Using Mobiles:

• Always with you — convenient for agents on the move.
• No setup required.
• Familiar and simple.

Cons of Relying Solely on Mobiles:

• Unprofessional: sharing personal numbers doesn’t look credible.
• No call recording (compliance issue).
• Calls tied to one person — risky if they’re unavailable.
• Hard to scale for growing agencies.
• Costs can add up with business mobile contracts.

(Keywords: mobile phone systems estate agents, property managers using mobiles)

3. VoIP Phone Systems Explained

VoIP (Voice over Internet Protocol) uses the internet to make and receive calls. Instead of being tied to a mobile SIM or a landline, VoIP gives you a business phone system that works across devices — mobiles, desk phones, or even laptops.

Key Features for Property Managers:

• Professional business numbers (01, 02, 0800, 0330).
• Call routing & forwarding (never miss a client call).
• Call recording (compliance + training).
• Scalability (add lines or features as you grow).
• Integration with CRMs (sync calls with your property management system).
• Voicemail to email (stay on top of messages anywhere).

(Keywords: VoIP phone systems, VoIP for property management, estate agent VoIP features)

4. VoIP vs Mobile: Feature-by-Feature Comparison

5. Cost Analysis: VoIP vs Mobile in Real Life

Example: 5-Person Estate Agency

• Mobile contracts: £30/month each → £150/month total.
• VoIP numbers: £1/month per number + calling packages → ~£50/month total.

That’s £100+ saved every month — while gaining features mobiles simply don’t offer.

(Keywords: VoIP cost savings estate agents, affordable phone systems for property management)

6. Scalability: Growing With Your Business

• Mobile: each new agent = new phone + contract.
• VoIP: add a number or line in minutes, no new hardware needed.
• Perfect for agencies expanding portfolios or opening new offices.

7. Professionalism & Branding

• Mobile numbers feel personal and temporary.
• Clients prefer calling a local landline or freephone (0800).
• VoIP lets you present as an established, trustworthy business — even if you’re a solo agent starting out.

8. Compliance & Risk Management

• Increasingly, property management involves compliance (recording conversations, managing disputes, etc.).
• Mobiles rarely offer recording.
• VoIP makes it simple to log and store calls securely.

9. Hybrid Option: Best of Both Worlds

With modern VoIP (like PlexaTalk), you don’t have to choose.

• Make and receive business calls through your mobile app.
• Keep your personal number private.
• Present your business caller ID on every call.

(Keywords: VoIP mobile app estate agents, hybrid phone systems property management)

10. How to Choose the Right Phone System for Your Property Management Business

When deciding, ask:

1. Do I want my agency to look professional?
2. Do I need scalability?
3. Is call recording important?
4. Do I want to save money on phone systems?
5. Will I benefit from integration with property management software?

If the answer is yes to most of these → VoIP is the better choice.

11. Real-Life Scenarios

• Solo property manager: Mobile works short-term, but VoIP with a business number creates a professional image fast.
• Growing estate agency: VoIP saves money and scales instantly.
• Multi-branch business: VoIP unifies calls across locations, something mobiles can’t do.

Why Estate Agents Are Moving to VoIP

Mobile phones are convenient, but limited. For estate agents and property managers, VoIP offers scalability, professionalism, compliance, and cost savings.

📞 Want to upgrade your property management phone system? PlexaTalk’s VoIP solutions are built specifically for estate agents — with business numbers from just £1/month, call routing, recording, and full CRM integration.
👉 Find out more here

FAQs for Property Management Companies

The post VoIP vs Mobile: Choosing the Right Phone System for Your Property Management Business appeared first on Plexatalk.

VoIP traffic is light on bandwidth — roughly 80–88 Kbps per call — but extremely sensitive to latency, jitter, and packet loss. Even a short delay can lead to echo, choppy audio, or dropped calls.
A correct draytek voip qos configuration ensures your voice packets always get top priority, even when your network is under heavy load.

This guide walks you through a draytek qos setup for VoIP on all DrayTek Vigor models, from home routers to enterprise-grade devices. We’ll cover quick methods, advanced class-based setups, firmware variations, and troubleshooting tips.

1. Understanding DrayTek QoS for VoIP

DrayTek routers manage bandwidth using Quality of Service (QoS).
For VoIP, there are two main options:

• First Priority for VoIP SIP/RTP — Quick, automatic bandwidth reservation for calls.
• Class-based QoS — Fine-grained control, allowing multiple priority levels for different traffic types.

2. Pre-Setup Checklist

Before starting your draytek qos setup, make sure you have:

• Router login details (default IP: 192.168.1.1)
• Latest firmware (older versions may have different menus or missing features)
• Accurate upload/download speeds from a wired speed test (values must be in Kbps)
• VoIP provider port details
  • SIP: UDP 5060 (sometimes 5061)
  • RTP: UDP 16384–32767 (varies per provider)

3. Logging Into Your DrayTek Router

Log into your DrayTek router at 192.168.1.1 to begin the QoS configuration process.

4. Enabling QoS on Your WAN Interface

Enable QoS for the WAN interface carrying VoIP traffic, then set accurate inbound/outbound bandwidth values.

Steps:

1. Go to Bandwidth Management > Quality of Service.
2. Tick Enable for the WAN interface used for VoIP.
3. Enter Inbound and Outbound bandwidth (Kbps).
4. Apply changes.

💡 Tip: Incorrect speeds will break QoS effectiveness.

5. Quick Method — First Priority for VoIP

Enable “First Priority for VoIP” to automatically reserve bandwidth for SIP and RTP traffic.

Steps:

1. Scroll to VoIP Prioritisation at the bottom of the QoS page.
2. Tick Enable the First Priority for VoIP SIP/RTP.
3. If your SIP server uses a different port, update SIP UDP Port.
4. Click OK.

How it works:

• Reserves 2 × 88 Kbps by default per call
• Dynamically adjusts if call quality drops or more calls occur

6. Advanced Method — Class-Based DrayTek QoS Setup

Use App QoS to assign VoIP traffic to a high-priority class for more granular control.

Step A — Set Class Priorities

• Go to Class Setup.
• Assign Class 1 as High Priority.
• Reserve ~10–20% upload bandwidth for Class 1.

Step B — Define VoIP Traffic

• In App QoS, tick your VoIP apps or create custom rules for SIP and RTP ports.
• Apply them to Class 1.

7. Model-Specific DrayTek VoIP QoS Setup Notes

Vigor 2760 / 2830 Series

• Menu Path: Bandwidth Management > QoS
• Setup Tip: These older DrayTek models don’t have App QoS. You’ll need to use the Filter Setup menu to create rules for SIP and RTP ports manually.
• Ideal for small networks where simple prioritisation is enough.

Vigor 2860–2862 Series

• Menu Path: Bandwidth Management > QoS / Class Setup
• Setup Tip: Supports DSCP tagging, allowing the router to prioritise traffic based on packet markings from VoIP phones or PBX systems.
• Useful in business environments with managed switches and VLANs.

Vigor 2765 / 2865 / 2927 Series

• Menu Path: QoS Control + App QoS
• Setup Tip: Newer firmware can auto-detect VoIP traffic for faster setup. You can still create manual rules for specific SIP/RTP ports if needed. Get the latest firmware from DrayTek.
• Recommended for users who want both quick setup and the flexibility to fine-tune.

Vigor 3910 and Higher

• Menu Path: Advanced QoS per VLAN
• Setup Tip: Perfect for larger deployments. You can dedicate a VLAN to VoIP and apply QoS rules at the VLAN level for maximum reliability.
• Best suited for high-density offices, call centres, and enterprise environments.

8. Advanced QoS Tuning

CLI Commands (Telnet/SSH):

qos setup -I [value]  # Min download bandwidth for non-VoIP traffic
qos setup -O [value]  # Min upload bandwidth for non-VoIP traffic
qos setup -v 1        # Apply limits immediately when VoIP detected

DSCP Tagging:
If your phones mark packets with DSCP EF (46), enable DSCP-based QoS to automatically prioritise them.

VLAN Segregation:
Place VoIP devices on their own VLAN and apply per-VLAN QoS rules.

9. Testing Your Setup

• Start a heavy download.
• Make a VoIP call.
• Audio should remain clear and uninterrupted.
• Check QoS Status or Syslog for “VoIP calls detected.”

10. Troubleshooting

If calls are still choppy:

• Check that bandwidth values match real speeds.
• Reduce lower-priority traffic limits.
• Disable SIP ALG if causing issues.

If rules don’t match traffic:

• Ensure they’re applied to the correct WAN.
• Confirm SIP/RTP ports are correct.

Whether you choose the quick First Priority option or a custom class-based draytek qos setup, these steps will ensure your draytek voip qos configuration delivers crystal clear calls under any network load.

DrayTek VoIP QoS – Frequently Asked Questions

Enabling QoS because of call issues?

If you’re having call issues it may also be NAT issues such as SIP ALG issues or because you haven’t enabled rport.

The post How to Configure DrayTek VoIP QoS (All Models Guide) appeared first on Plexatalk.

If you’ve ever experienced choppy VoIP calls, conversations where the other person can’t hear you, or the dreaded “dead silence” when you answer the phone, there’s a good chance you’ve run into one of the most common yet least obvious culprits: SIP ALG. This router feature, often buried deep in the settings, can cause symptoms like calls cutting off mid-sentence, no inbound calls ringing through, or frustrating one-way audio issues.

The problem? Many routers ship with SIP ALG enabled by default. While it was designed to help with VoIP call setup and NAT traversal, in practice it often rewrites data in a way that breaks more than it fixes. Most VoIP providers recommend disabling SIP ALG for a smoother, more reliable calling experience.

Think of it as a “helpful” friend who keeps rewriting your letters before they get sent—sometimes they improve the message, but more often they just make it unreadable.

What is SIP ALG? (Plain English & Technical)

Plain English:
SIP ALG stands for Session Initiation Protocol Application Layer Gateway. It’s a router feature designed to help VoIP calls work behind firewalls and NAT (Network Address Translation) by inspecting and altering SIP packets as they pass through. In theory, it’s supposed to make sure your phone system can connect smoothly to the internet by “fixing” the addressing inside those packets.

Technical:
SIP ALG operates at the application layer, intercepting SIP signalling traffic, rewriting packet headers, and modifying the SDP (Session Description Protocol) payload. The intention is to solve NAT traversal problems by ensuring that private IP addresses inside SIP messages are replaced with the public IP of the router. Unfortunately, in many implementations, this process is buggy or overly aggressive, leading to broken call setup, missing audio streams, and dropped connections.

It’s worth noting that there are alternative, cleaner ways to handle NAT traversal without rewriting SIP headers at all. For example, rport ensures NAT reply routing is maintained while leaving the original SIP message intact—avoiding many of the problems caused by SIP ALG.

Why SIP ALG Exists (and When It Helps)

SIP ALG wasn’t invented to make life harder for VoIP users—it was originally designed to solve very real networking challenges. In certain environments, especially those with symmetrical NAT or with SIP servers that lack built-in NAT traversal mechanisms, VoIP traffic can fail outright without some form of packet modification.

By intercepting SIP signalling and rewriting the addresses inside, SIP ALG can, in theory, help phones and PBXs register successfully, even when they’re sitting behind tight corporate firewalls or in networks where the router is the only device aware of the public IP. In some rare edge cases—such as legacy SIP servers that aren’t NAT-aware—it can be the difference between a working call and no call at all.

These scenarios are increasingly uncommon thanks to modern SIP servers and features like STUN, ICE, and rport, but they do still exist. Knowing when SIP ALG helps—and when it hurts—separates network troubleshooting guesswork from informed, precise fixes.

How SIP ALG Breaks VoIP

While SIP ALG is meant to help, in practice it often causes more problems than it solves. Here are the most common ways it disrupts calls:

1. Header Mangling
   SIP ALG may alter critical SIP headers such as Contact or Via. These changes can prevent a VoIP endpoint from properly registering with the server or cause inbound calls to fail completely.
2. Incorrect SDP Rewriting
   By inserting the wrong IP addresses or ports into the Session Description Protocol (SDP), SIP ALG can send media streams to the wrong place. This is one of the leading causes of SIP ALG one-way audio—where you can hear the other party, but they can’t hear you (or vice versa).
3. Port Mapping Confusion
   SIP ALG can create mismatched NAT bindings, causing signalling packets and RTP streams to arrive on ports the phone or PBX isn’t expecting. This often leads to dropped calls or failed media negotiation.
4. Blocking Server-Side NAT Solutions
   Many modern VoIP providers implement their own NAT traversal techniques. SIP ALG can override or corrupt this process, interfering with solutions like rport or STUN, and breaking otherwise healthy call flows.

SIP ALG vs Other NAT Traversal Tools

SIP ALG is just one approach to solving NAT traversal issues—but it’s also the most invasive, since it rewrites packet data in-flight. Modern VoIP environments typically use less disruptive, standards-based methods. Here’s how they compare:

• rport – Safe, signalling-only method that ensures NAT reply routing without altering SIP headers.
• STUN – Lets devices discover their public IP address and port mapping so they can advertise correct details in SIP/SDP.
• Keep-alives – Periodically send small packets to maintain an active NAT binding.
• TURN – Relays media through an external server when direct peer-to-peer streams aren’t possible.
• Outbound proxy – Centralises NAT traversal logic by routing all SIP signalling through a single, provider-controlled server.

Why These Alternatives Work Better
Where SIP ALG modifies SIP messages on the fly—risking broken headers and mangled media paths—tools like rport, STUN, and TURN operate within established SIP and RTP standards. They focus on ensuring packets reach their destination without altering the original signalling content.

For example, rport is specifically designed to fix reply routing issues by letting the server send responses to the correct external port, all without rewriting your SIP headers. STUN and keep-alives help devices maintain accurate connection details, while TURN and outbound proxies handle more restrictive environments by providing controlled relay points.

Together, these techniques provide reliable NAT traversal without the unpredictable side effects that make SIP ALG infamous in VoIP troubleshooting.

Best Practice – SIP ALG Off, These On

For most modern VoIP setups, the safest and most reliable configuration is to turn off SIP ALG and enable standards-based NAT traversal tools instead. Here’s the checklist we recommend:

• Disable SIP ALG on your router to prevent packet rewriting.
• Enable rport on your phones, PBX, or ATA to ensure correct NAT reply routing.
• Use STUN or your provider’s outbound proxy so devices know their public IP and signalling path.
• Keep-alives enabled to maintain stable NAT bindings and prevent call drops.

If you use Plexatalk preconfigured phones or adapters, SIP ALG is already off and NAT-friendly settings like rport, STUN, and keep-alives are enabled by default—no manual tweaks needed. That means you can skip the guesswork and get straight to clear, reliable calls. This being said… your router may have SIP ALG turned on.

How to Disable SIP ALG (Router Brand Guide)

Disabling SIP ALG varies by router brand. Use the links below to jump directly to your model’s instructions:

Netgear | TP-Link | Asus | DrayTek | Mikrotik | BT Hub | Virgin Hub | Others

What If I Can’t Disable SIP ALG?

Some routers don’t expose a toggle for SIP ALG, or their “off” setting still interferes with VoIP. If you can’t disable it, try these proven workarounds:

Workarounds

• Use TLS to mask SIP signalling from ALG
  • Switch your phones/PBX to SIP over TLS (for signalling) so the router can’t read/modify headers.
  • Pair TLS with SRTP for encrypted media when supported.
  • Tip: Ensure server certificates and ports are correctly configured (often TCP 5061 for TLS).
• Change the router to one without ALG (or with a better implementation *recommended*)
  • Use a VoIP-friendly router that lets you fully disable SIP ALG and supports rport, STUN, keep-alives, and outbound proxy.
  • If your ISP router allows it, enable modem/bridge mode and place your own router behind it.
• Place the VoIP device in the router’s DMZ
  • DMZ can bypass ALG manipulation by sending unsolicited inbound replies straight to the device.
  • Security note: Only use DMZ for a dedicated VoIP device (not a PC), keep firmware updated, and restrict services to SIP/RTP.
  • Still use strong passwords and allowlists where possible.

Good to know: Plexatalk supplies VoIP-friendly routers and adapters preconfigured — SIP ALG is off and NAT-safe settings (rport, STUN/keep-alives, outbound proxy) are enabled, so you don’t need to tweak anything.

SIP ALG and Security Implications

Although SIP ALG was never designed as a security feature, its packet inspection and modification can have knock-on effects for network security — both positive and negative.

Potential Benefits

• By rewriting SIP headers, SIP ALG can, in theory, hide internal IP addresses from the public internet.
• Some implementations will drop malformed SIP packets, acting as a very basic filter against certain malformed traffic.

Security Risks

• Firewall Pinholes: In poorly implemented ALGs, the automatic opening of RTP ports can create unnecessary exposure, allowing malicious traffic in.
• Reduced Transparency: Because ALG modifies packets, it can make troubleshooting and monitoring more difficult — potentially letting suspicious traffic patterns go unnoticed.
• Bypassing Intended Policies: Some enterprise firewalls rely on predictable packet structures for policy enforcement; ALG’s rewriting can unintentionally bypass or break these rules.

The takeaway? SIP ALG is not a replacement for VoIP security best practices. Proper security comes from TLS/SRTP encryption, strong authentication, and well-configured firewalls. If anything, disabling SIP ALG and relying on standards-compliant NAT traversal tools gives you a more predictable, auditable security posture.

Real-World Cases: When SIP ALG Helps (and When It Hurts)

Case 1 – The Legacy PBX in a Corporate LAN
A manufacturing company still ran an early-2000s SIP-based PBX that had no NAT awareness. With symmetrical NAT in place, calls simply failed without ALG rewriting headers. In this scenario, enabling SIP ALG restored basic call functionality — though long-term, replacing the PBX was the real fix.

Case 2 – The Modern Hosted VoIP Deployment
A marketing agency moved to a cloud VoIP service with rport, STUN, and keep-alives already enabled by the provider. SIP ALG was left on in their Netgear router, resulting in intermittent one-way audio and dropped calls. Disabling ALG fixed the issue immediately — no other changes needed.

Case 3 – The ISP-Locked Router
A small business using an ISP-supplied hub found SIP ALG could not be disabled. Outbound calls worked, but inbound calls often went straight to voicemail. Switching the hub to modem mode and adding a VoIP-friendly router with ALG disabled resolved the problem and improved call quality.

These examples underline the rule of thumb: ALG can help in very specific, usually outdated setups, but it’s far more likely to interfere in modern VoIP environments.

SIP-ALG FAQ’s

SIP ALG was created to solve older networking problems, but in today’s VoIP environments it’s more often a source of dropped calls, one-way audio, and frustrating troubleshooting sessions. While it can help in rare edge cases, most modern systems work best when SIP ALG is disabled and standards-based NAT traversal tools take its place.

With Plexatalk, you can skip the headaches. We supply preconfigured, tested hardware with SIP ALG disabled and NAT-safe settings enabled, including rport, STUN, keep-alives, and outbound proxy support. That means your VoIP setup works reliably right out of the box — even on tricky networks.

Contact us if you want a VoIP solution that works from day one, without the trial-and-error.

The post What is SIP ALG and Why You Should Usually Disable It for VoIP appeared first on Plexatalk.

NAT (Network Address Translation) is what most home and office routers use to let multiple devices share one public IPv4 address. It’s great for security and address conservation, but it changes packet headers in ways that can confuse SIP — the protocol VoIP uses to set up calls.

When SIP gets confused, call signalling packets can vanish, incoming calls fail to arrive, and audio streams may get lost.

That’s where the rport parameter comes in. Defined in RFC 3581, it’s a small change in SIP behaviour that can make the difference between unreliable and rock-solid VoIP.

At Plexatalk, most customers never need to think about rport. We preconfigure the phones and VoIP adapters we supply so they’re ready for NAT handling from the moment you plug them in. But if you’re bringing your own device, using a third-party softphone, or troubleshooting another provider’s service, understanding rport can save you hours of frustration.

Quick Answer — What is rport in VoIP?

In plain English:

rport tells a SIP server to send responses back to the IP address and port that your request actually came from — not the ones written in your SIP headers.

This matters because behind NAT, your device’s internal IP and port (e.g., 192.168.1.50:5060) are not reachable from the internet. Your provider needs to send packets to your router’s public IP and the actual source port NAT assigned (e.g., 81.2.3.4:32415).

Without rport, the server may try to send packets to your private address — and those packets never make it back.

RFC 3581 definition (simplified):

The rport parameter requests that the server send the response back to the source IP address and port from which the request originated.

Example of rport in a SIP Via header:

Without rport:

Via: SIP/2.0/UDP 192.168.1.50:5060;branch=z9hG4bK-123456

With rport:

Via: SIP/2.0/UDP 192.168.1.50:5060;branch=z9hG4bK-123456;rport

SIP, NAT, and the Problem rport Solves

SIP without NAT

When you’re on a public IP:

1. Your phone sends a SIP request (REGISTER, INVITE, etc.).
2. It includes its own IP and port in the Via: header.
3. The SIP server sends its reply to that IP and port.

Everything works fine because the address in the header is valid.

What NAT changes

Behind NAT:

• Your phone thinks it’s sending from 192.168.1.50:5060.
• Your router rewrites this to your public IP (e.g., 81.2.3.4:32415).
• The SIP server sees the request coming from 81.2.3.4:32415 but still reads 192.168.1.50:5060 in the Via: header.

If the server replies to 192.168.1.50:5060, the packet never arrives — NAT doesn’t know where to send it.

How rport fixes it

With rport:

1. Your device adds ;rport (empty) to its Via: header.
2. The SIP server fills it with the actual source port it sees (e.g., 32415).
3. The server replies to your public IP and the correct mapped port.

That means the NAT device can forward the packet back to your phone.

RFC 3581 Mechanics — In Plain Language

RFC 3581 introduced Symmetric Response Routing for SIP over UDP.

Basic flow

1. Client sends SIP request with rport present but empty.
2. Receiving proxy takes the source IP and source port from the UDP header.
3. Proxy fills in the rport parameter with the observed port.
4. All replies are sent to that observed IP/port instead of the ones in the SIP header body.

Multi-proxy environments

In a chain of SIP proxies:

• Each proxy appends its own received= parameter (observed IP) to the Via: header.
• If rport is present, it also appends the observed port.
• This ensures signalling can route back correctly even through multiple NAT layers and firewalls.

Example: Via header before and after

Before processing:

Via: SIP/2.0/UDP 192.168.1.50:5060;branch=z9hG4bK-111111;rport

After proxy sees packet from 81.2.3.4:32415:

Via: SIP/2.0/UDP 192.168.1.50:5060;branch=z9hG4bK-111111;received=81.2.3.4;rport=32415

What rport Does Not Do

rport is not a cure-all. It:

Does not replace the need for an outbound proxy in some complex topologies.

Does not solve RTP (media) traversal — you still need STUN, TURN, ICE, or symmetric RTP.

Does not keep NAT bindings open — use SIP keep-alives or periodic REGISTERs for that.

When your VoIP provider Might Ask You to Enable rport

If you’re using Plexatalk-supplied hardware (ATAs, IP phones), rport is already set.
If you bring your own device or app, your VoIP provider or even us depending on config – might recommend enabling rport if you:

• Use Starlink, 4G/5G, or satellite broadband
• Have double NAT (ISP router + your router)
• Use Zoiper or another softphone that moves between networks
• Experience incoming call failures or dropped registrations

How to Enable rport — Device Walkthroughs

Plexatalk tip: If we’ve supplied your device, these settings are already correct. If you’ve brought your own, we can confirm the right configuration for your SIP account.

rport vs Other NAT Traversal Tools

• rport – Fixes where SIP signalling replies are sent. It tells the server to use your actual public IP and the port NAT assigned, not the private address in your SIP header.
• STUN – Lets your VoIP device discover its public IP and port mapping, which can then be used in SIP and SDP. Often used alongside rport.
• Keep-alives – Sends small packets periodically to keep NAT bindings open. Useful so that incoming calls still work after periods of inactivity.
• TURN – Relays SIP and/or RTP traffic through a third-party server, bypassing NAT issues entirely. More bandwidth-intensive.
• Outbound Proxy – All signalling and media are sent to one central proxy, which handles NAT traversal for you.

Pitfalls & Misunderstandings

• Disabling rport “just to test” often creates more problems.
• SIP ALG in many routers can override or strip rport info — best to disable SIP ALG.
• rport only affects SIP signalling — your RTP/media path still needs to be correct.

Example Call Flows

Without rport:

1. Phone sends REGISTER with Via: 192.168.1.50:5060.
2. NAT changes source to 81.2.3.4:32415.
3. Server replies to 192.168.1.50:5060 — lost.

With rport:

1. Phone sends REGISTER with Via: 192.168.1.50:5060;rport.
2. NAT changes to 81.2.3.4:32415.
3. Server fills rport=32415, replies to 81.2.3.4:32415 — delivered.

Why Preconfigured Hardware Saves Time

Plexatalk ships VoIP devices pre-tuned for UK ISPs and NAT environments. That includes:

• rport enabled where needed
• Correct SIP timers
• Keep-alives configured
• SIP ALG workarounds in place

You plug in, it works.
If you bring your own hardware, we’ll guide you — but preconfigured gear removes guesswork.

References & Further Reading

• RFC 3581 — Symmetric Response Routing in SIP
• Wikipedia — Session Initiation Protocol

Frequently Asked Questions – rport in VoIP

The post What is rport and Why Your VoIP Supplier Might Need You to Enable It appeared first on Plexatalk.