Port 2860: Dialpad Voice 1 — A Registered Port That Feels Unassigned

What Port 2860 Is

Port 2860 is a registered port in the IANA Service Name and Transport Protocol Port Number Registry, listed under the service name dialpad-voice1 — Dialpad Voice 1.¹

Dialpad is a cloud-based business communications platform: VoIP calls, messaging, video meetings. Port 2860 (TCP and UDP) and its companion port 2861 (dialpad-voice2) were registered for carrying voice traffic in the Dialpad system.²

In practice, most port reference databases flag this port as unassigned or unknown. The registration exists; it just doesn't carry much weight in the broader ecosystem. If you're running a Dialpad-connected system, you might see traffic here. If you're not, you almost certainly won't.

The Registered Port Range

Ports 1024–49151 are called registered ports (sometimes "user ports"). The idea: companies and projects can apply to IANA to stake a claim on a port number for a specific service. This prevents two applications from accidentally colliding on the same number — at least in theory.

In practice, the registry is crowded with registrations that are:

• Commercial products with niche user bases
• Services that changed how they work and no longer use their registered port
• Projects that died years ago but kept their IANA entry

Port 2860 falls somewhere in this category: legitimately registered, largely invisible in the wild.

If You See Traffic on Port 2860

There are three likely explanations:

1. Dialpad client software — If anyone on your network uses Dialpad for business calls, their client may use this port for voice media.
2. Something unrelated — Applications routinely pick ports without checking IANA registrations. A game, a custom service, or a misconfigured daemon could be using 2860 for entirely different reasons.
3. A port scan hit — Automated scanners probe every port. An inbound connection attempt here doesn't mean there's a Dialpad server expected.

How to Check What's Using Port 2860

On Linux or macOS:

# Show what process is listening on port 2860
ss -tlnp | grep 2860
# or
lsof -i :2860

On Windows:

netstat -ano | findstr :2860

The output will show the process ID. Cross-reference with Task Manager (Windows) or ps aux | grep <PID> (Linux/macOS) to identify the process.

Why This Matters

The registered port system works because of shared convention. When everyone agrees port 443 is HTTPS, routers, firewalls, and monitoring tools can make intelligent decisions about traffic. Registered-but-invisible ports like 2860 sit in a gray zone: technically claimed, practically unclaimed.

For security teams, this matters: an unrecognized service on a registered-but-obscure port deserves the same scrutiny as one on a completely unassigned port. The registration doesn't confer trust — it just means someone filed paperwork.

Related Ports