Adtran 1560 Reset & Connector Checklist: Handling Routers, Connectors, and Locked Phones

When to use this checklist

I'm a field service engineer at a telecom integration company. I've handled 400+ emergency network repairs in nine years, including same-day turnarounds for enterprise and service provider clients. This checklist is for the situation where an Adtran 1560 gateway stops forwarding traffic, a connector is suspect, or a phone on the network is locked.

Five steps. I wrote them in the order I actually run them on-site—not the order in the manual, because field conditions rarely cooperate. A quick caveat before we start: Adtran firmware changes behavior between releases. This was accurate as of Q1 2025. Verify against the release notes for your specific 1560 revision before doing a full reset.

Step 1: Confirm the symptom actually needs a reset

Before you touch the reset button, separate "device is broken" from "device is working but upstream is broken." I've watched techs factory-reset an Adtran 1560 that was perfectly healthy—the actual fault was a dirty connector one rack over.

Do this check first:

• Read the LEDs. On the 1560, a solid power LED with an off internet LED usually points to the WAN side, not a router that needs wiping.
• Ping the gateway from a laptop on the LAN side. If it responds, the router is alive.
• Inspect the upstream fiber or copper run for visible damage before blaming the device.

If the LAN side responds and the WAN side doesn't, you have a connector or upstream problem—skip to Step 3. A reset won't fix a dirty connector, and it will wipe the customer's provisioning.

Step 2: Reset the Adtran 1560 (only if Step 1 says so)

The 1560 has a recessed reset button. If I remember correctly, it's behind the front bezel on the right side—though I might be misremembering the exact position on the newer hardware revisions. Use a paperclip, not a screwdriver. The screwdriver is how people crack the bezel.

Two reset modes matter:

• Short press (under 10 seconds): soft reboot. Keeps configuration. Use this to clear a hung process without touching provisioning.
• Long press (15–20 seconds): factory reset. Wipes the config. Use only when you have the provisioning file ready to restore.

Adtran's documentation for the 1560 series specifies that long hold window for a factory reset, but verify it against your hardware revision—the exact timing has shifted between releases. After a long press, the device takes roughly 90 seconds to reboot. I want to say the last one I timed was back up in under two minutes, but don't quote me on that. Watch the LED sequence anyway—don't walk away. If the power LED never goes solid, the reset didn't take, and you shouldn't assume the unit is dead until you've confirmed the LED pattern.

The upside of a factory reset is a clean slate. The risk is wiping the customer's provisioned configuration in the middle of a workday. I kept asking myself: is saving 20 minutes worth a two-hour re-provisioning call? Most of the time, the answer is no.

Step 3: Check the connector (the step most techs skip)

This is the one most techs skip, and it causes more unnecessary Adtran "resets" than any other single factor.

On the 1560, you're typically dealing with an SC/APC fiber connector on the uplink and RJ45 on the LAN side. Both fail in the same quiet way: link negotiates, traffic drops, no obvious error log.

What I actually do in the field:

• Fiber: inspect the end face with a scope. Dust is the silent killer. Clean both sides of the mating sleeve, not just the patch cord. If the connector feels loose, re-seat it fully—a half-seated SC connector can look fine on the LED and still drop packets under load.
• RJ45: re-seat the connector, then check the cable for strain near the boot. Bent pins inside a molded connector are more common than people think, and they show up as intermittent link.
• Port mapping: verify you're plugged into the correct WAN port on the 1560. On some revisions the WAN and LAN ports sit close together and are easy to swap.

Some of this is basic. The fiber end-face check is the one I'd underline. A dirty connector will make a healthy Adtran 1560 look like a failing router, and no amount of resetting fixes it.

Step 4: Reset a locked phone on the Adtran network

If the device in question is a VoIP or SIP handset on an Adtran voice deployment, "locked" usually means one of three things: an admin lock, a provisioning lock, or a SIP registration lock. The reset method depends on which one you have, so diagnose before you act.

1. Admin lock: the handset's web UI is locked. Without admin credentials, do a factory reset on the handset itself (check your handset vendor's manual—it's usually a key combination held during boot). This wipes the handset config, so re-provision from the Adtran voice platform afterward.
2. Provisioning lock: the handset is bound to a stale configuration server. Delete the phone's entry in the Adtran provisioning service and re-add it. The handset won't re-register until the stale binding is cleared.
3. SIP registration lock: the extension is locked to an old MAC or IP. Clear the registration in the Adtran voice server, then re-bind.

One thing tripping people up: a factory reset on the handset does not clear the server-side binding. You have to clear both sides. Otherwise the phone comes back up, re-registers, and locks again within minutes. If you're resetting a locked phone and it keeps locking, this is almost always the reason.

If "locked phone" here means a carrier-locked handset, that's outside the Adtran network scope—that's a carrier unlock request, not something an Adtran reset resolves. I've had to explain that difference more than once on a support call.

Step 5: Verify recovery before you leave

Don't close the ticket on "the LEDs look good." Verify the things the customer actually cares about:

• WAN-side connectivity: ping both a public endpoint and a customer endpoint.
• Voice: place a test call through the SIP trunk—not just a handset-to-handset call inside the LAN.
• Throughput: run a quick speed test, especially after a fiber re-seat. A marginal connector shows up as low throughput under load.
• Config: confirm provisioning restored correctly. If you did a factory reset, spot-check at least one customer-specific setting before you pack up.

Had 45 minutes before a customer's service window closed on a recent job. Normally I'd run every connector through a full inspection, but there was no time. I went with a visual check and a scoped inspection on the main uplink only, then flagged the secondary run for a follow-up. In hindsight, I should have flagged the secondary run before I started—but with the window closing, I made the call with what I had.

Notes and common mistakes

A few things I've paid for in time, so you don't have to:

• Don't factory-reset before checking the connector. This is the mistake that costs the most, because it turns a 10-minute fix into a two-hour re-provisioning job.
• Don't assume "reboot" and "reset" are the same thing. On the 1560, a short press and a long press do very different things. Know which one you're holding before you commit.
• Don't skip the fiber end-face inspection. It's the single most-missed step in field service, and it's responsible for a lot of phantom "bad Adtran unit" tickets.
• Don't reset a locked phone without clearing the server-side binding. Both sides, or it locks again.

Firmware behavior and reset timing here were accurate as of Q1 2025. Adtran changes release behavior between versions, so verify against the current Adtran 1560 documentation before you commit to a factory reset on a production unit. That last part isn't just legal hedging—release notes are where Adtran documents the specific reset behavior changes between revisions, and they're worth two minutes of your time before you hold down a button.