Vertex EEE — Troubleshooting Guide

Vertex VoIP - EEE Troubleshooting Guide

Print This Guide

EEE Troubleshooting Guide

Energy Efficient Ethernet Conflicts with Vertex VoIP Devices

Common Installation Issue

Energy Efficient Ethernet (EEE / IEEE 802.3az) can prevent the Vertex from detecting call traffic. This guide explains how to identify and resolve EEE conflicts.

1. What is EEE (Energy Efficient Ethernet)?

Energy Efficient Ethernet (IEEE 802.3az) is a power-saving technology built into many modern network devices. When enabled, it reduces power consumption during low traffic periods by putting the network interface into a low-power idle state.

The Problem with Vertex Devices

The Vertex VoIP Caller ID device sits inline between network devices to capture VoIP call signaling. When EEE is active on connected devices (ISP router, Cradle Point, phone switches), the network interface enters power-saving modes that can:

Cause packet loss or delay during the "wake up" period

Prevent the Vertex from seeing traffic on the monitored ports

Result in intermittent or missing call data

Create timing issues with VoIP signaling capture

2. Symptoms of EEE Conflicts

Symptom Description Likelihood

No calls detected Vertex shows connected but never receives call data High

Intermittent call capture Some calls captured, others missed randomly High

First call missing First call after idle period not captured, subsequent calls work High

Port LEDs not blinking ISP or Phone port shows link but no activity Medium

Partial call data Call start captured but no call end, or vice versa Medium

3. The Solution: Insert an Unmanaged Switch

Breaking the EEE Signaling Chain

The most reliable solution is to insert a simple unmanaged network switch between the Vertex and the device causing the EEE conflict. This "breaks" the EEE negotiation and forces standard Ethernet operation.

3.1 Typical Problem Configuration

PROBLEM: Direct Connection with EEE

ISP Router (EEE Enabled) ───── VERTEX ISP Port ───── VERTEX Phone Port ───── Phone Switch (EEE Enabled)

EEE signaling passes through Vertex, causing traffic detection issues

3.2 Corrected Configuration

SOLUTION: Insert Unmanaged Switch

ISP Router (EEE Enabled) ─── VERTEX ISP Port ─── VERTEX Phone Port ─── Unmanaged Switch ─── Phone Switch (EEE Enabled)

Unmanaged switch breaks EEE chain - Vertex sees all traffic

3.3 Step-by-Step Installation

1 Identify the Connection Causing Issues

Check the Vertex LED status. If the Phone port shows link but no activity during calls, the phone switch side is likely the problem. If the ISP port shows link but no activity, the ISP/Cradle Point side is the problem.

2 Obtain an Unmanaged Switch

Use a simple 5-port or 8-port unmanaged Gigabit switch. Recommended models:

NETGEAR GS305 (5-port)

TP-Link TL-SG105 (5-port)

D-Link DGS-105 (5-port)

Important: Must be UNMANAGED. Managed switches may also have EEE enabled.

3 Insert Switch Between Vertex and Phone System

Disconnect the cable from the Vertex Phone Port that goes to the phone switch. Connect that cable to the unmanaged switch. Run a new cable from the unmanaged switch to the Vertex Phone Port.

4 Verify Operation

Check the Vertex diagnostics panel. You should now see activity on the Phone port when calls are made. Test with several calls to confirm reliable capture.

4. Alternative Solutions

4.1 Disable EEE on Source Device (If Possible)

Managed Switch Option: If you have access to the phone switch configuration, you may be able to disable EEE on the specific port connected to the Vertex. This is device-specific and may require administrator access.

Device Type How to Disable EEE Difficulty

Cisco Switches no power efficient-ethernet auto on interface Medium

HP/Aruba Switches Web UI: Port Settings > Green Ethernet > Disable Medium

ISP Routers Usually not accessible - use switch solution Not Possible

Cradle Point Check admin panel for "Green Ethernet" or "EEE" settings Medium

4.2 Use Line Duplicator Differently

In some configurations, adjusting how the Line Duplicator is positioned in the network can help isolate the EEE-enabled device from the Vertex monitoring path.

5. Diagnostic Checklist

EEE Troubleshooting Checklist

Vertex shows "Connected" status but no calls are captured

ISP/Phone port shows green link LED but no amber activity LED

Phone system is modern (purchased within last 5 years)

ISP equipment is a Cradle Point or enterprise-grade router

First call after idle period is missed, subsequent calls work

Packet capture shows gaps or missing SIP packets

If 3 or more items are checked, EEE conflict is likely. Insert unmanaged switch as described above.

6. When to Escalate

Contact CallerID.com Support if: Inserting unmanaged switch does not resolve the issue

Problem persists with multiple switch types

LEDs show activity but calls still not captured

Firmware update is needed to address compatibility

Support: (404) 555-1234 | Info@CallerID.com

CallerID.com | 5680 Oakbrook Parkway, Ste 150, Norcross, GA 30093

EEE Troubleshooting Guide v1.0 | Back to Documentation Index