How to Login to Avaya IP Office Web Manager (Admin Guide)

If you administer an Avaya IP Office system, the difference between a five-minute change and a five-hour outage usually comes down to knowing exactly where a setting lives. This guide covers how to login to Avaya IP Office Web Manager and then walks through the four tasks that make up most day-to-day administration: signing in, resetting a password, changing a user's display name, and adding a new user and extension.

Every step below was checked against Avaya's own IP Office documentation for current releases. Paths are written for IP Office Web Manager specifically, not the legacy thick-client IP Office Manager now distributed as Admin Lite, because Web Manager is where most moves, adds, and changes are handled today.

Quick answer: To log in, open a supported browser, go to https://<IP_Address>:8443/WebMgmtEE/WebManagement.html, enter your service user name and password (the factory default is Administrator / Administrator), then click Login. You are prompted to change any default password on first access.

TL;DR

• Web Manager is reached at https://<IP_Address>:8443/WebMgmtEE/WebManagement.html, and the default Administrator credential must be changed on first login.
• Logging in, resetting a user login code, changing a display name, and adding a user with a matching extension all live under Call Management.
• "Password" maps to three separate fields: the user phone login code, the extension phone password, and the service-user admin password.
• Some changes apply live through a merge. Others require Offline Mode and a reboot using Immediate or Timed mode.
• On-premises IP Office puts every routine move, add, and change on your desk, often with a reboot attached. A cloud platform removes that overhead.

The rest of this guide expands each of those points with exact menu paths, then closes with the operational reality of running the box by hand.

Why Avaya Admins Are Reassessing On-Prem

A little context frames why this knowledge matters more than usual right now. Avaya filed for Chapter 11 bankruptcy protection for the second time on February 14, 2023, in the U.S. Bankruptcy Court for the Southern District of Texas, its second filing since 2017. In its filing, the company attributed the restructuring in part to a long decline in capex-based revenue from software licenses and hardware, consistent with customers shifting toward cloud-based solutions. Avaya then completed a court-confirmed prepackaged restructuring plan that eliminated more than 75 percent of its debt, cutting total debt from roughly 3.4 billion dollars to about 800 million dollars, and emerged as a private company in the spring of 2023.

That corporate context lines up with where the buying market has gone. According to Metrigy's UCaaS market forecast, the global UCaaS market reached 21.7 billion dollars in 2024, up 6.5 percent year over year, and is projected to grow to 26.5 billion dollars by 2029. Metrigy also reports cloud telephony seats worldwide grew to 114.0 million in the first half of 2025. The adjacent contact-center market is on a steeper curve still.

The single most important data point for anyone running an on-premises box is that, by Metrigy's count, a little under half of all telephony seats worldwide still sit on customer-owned platforms, which the firm frames as the remaining migration runway. None of this means your IP Office stops working tomorrow. It means the platform is increasingly an island. With that established, here are the steps.

How to Log In to Avaya IP Office Web Manager

To log in to Avaya IP Office Web Manager, open a supported browser and navigate to the Web Manager URL on port 8443. Web Manager is browser-based, so there is nothing to install on the admin workstation, but the management files must be present on the system SD card for the console to load.

Avaya supports Microsoft Edge, Mozilla Firefox, Google Chrome, and macOS Safari for IP Office web access. Older Internet Explorer builds are not reliable and should be avoided.

Login steps

1. From a client PC on the same network as the system, open your browser.
2. Enter https://<IP_Address>:8443/WebMgmtEE/WebManagement.html, replacing <IP_Address> with your system IP address. As an alternative, browse to the system IP directly and select IP Office Web Manager from the landing menu.
3. Accept the browser certificate warning. IP Office ships with a self-signed certificate, so a security prompt on first connection is expected. Proceed past it.
4. At the login menu, enter your service user name and password. The factory default account is Administrator / Administrator. On Basic Edition systems there is also a non-deletable Business Partner account used to provision other service users.
5. If the change you intend to make requires a reboot, for example line settings, enable Offline Mode before logging in. In Offline Mode a Save to IP Office link appears at the top of the window for committing the change and triggering the reboot.
6. Click Login. On a system still using a factory password, you are prompted to change it immediately. Do this. Leaving default credentials in place is the most common security finding on IP Office estates.

Once authenticated, the dashboard and the Call Management menu are your home base for the next three tasks.

Reset or Change a User Password on Avaya IP Office

Resetting a password on IP Office starts with knowing which password you mean, because the system uses three distinct credentials that admins routinely confuse. Getting this wrong is the difference between fixing a handset login and locking yourself out of the console.

Reset a user handset login code

The user login code is the most common reset request, and it lives under the user Telephony settings. In Web Manager, go to Call Management > Users, select the user, open the Telephony tab, then Supervisor Settings, and edit the Login Code field. Save the change. This is the code the user enters at the handset to log in.

Reset the Administrator (admin) password

The service-user password that gets you into Web Manager is managed separately under Security Settings in the Security Manager, in the Service Users list, not under Call Management. If you are locked out entirely because the default was changed and lost, recovery requires defaulting security settings at the system level, which is a deliberately heavier process.

Change a User Name and Display Name

Changing a user name on IP Office means editing one of two fields on the User record, and the distinction matters because they control different things. The Name field is the system identity, or account name. The Full Name field is what appears on phone displays for caller ID between internal users.

Steps to change a display name

1. Go to Call Management > Users and select the user you want to edit.
2. On the User tab, locate the Name and Full Name fields.
3. Edit Full Name to change the display name shown on handsets. This is almost always the field a name-change request is actually about, for example after a marriage or a legal name change.
4. Edit Name only if you intend to change the underlying account identity. Changing this can affect downstream references, so change it deliberately.
5. Click Update or OK, then commit the change to the system as described in the saving section below.

Changing a user Extension number does not simply rename them. On IP Office it effectively creates a new user and is not a clean merge operation. If your real goal is to move a person to a different physical phone, swap the handsets or re-associate the extension rather than editing the extension number on the user record. Edit names freely, and treat extension-number changes as a rebuild.

Add a New User and Extension in IP Office Web Manager

Adding a new user and extension in IP Office Web Manager is a single workflow that starts with the user record and lets the system generate the matching extension. The order matters. Create the user first, then let IP Office build the extension to match.

Steps to add a user and extension

1. Go to Call Management > Users.
2. Click Actions and choose Add User. In some releases this is a +Add control.
3. Enter the Name for account identity, the Full Name for the display name on phones, and the Extension number you want to assign.
4. Open the Telephony tab, then Supervisor Settings, and set a Login Code so the user can log in at their handset.
5. Save the user. When prompted to automatically create a matching extension entry, allow it, and select the correct extension type, for example a SIP extension for a VoIP phone.
6. Commit the configuration to the system.

To add many users at once without repeating every field, use templates. In Web Manager, go to Call Management > Users > Actions > Template Management to define a user template, and Call Management > Extensions > Actions > Template Management for an extension template. New users then inherit a standard configuration, which is how you keep a growing estate consistent and avoid one-off misconfigurations. The same discipline applies to endpoints, and our device setup and provisioning guides follow the same template-first approach.

Saving Changes and Reboot Modes

Saving changes on IP Office is not always instant, and knowing the difference between a live change and a reboot-required change prevents accidental outages. IP Office distinguishes between mergeable changes that apply to a running system and non-mergeable changes that need a restart.

• Mergeable changes, which include many user adds and edits, apply to the live system without dropping calls.
• Non-mergeable changes, such as line settings and certain structural changes, require Offline Mode, then Save to IP Office, then a reboot.
• Immediate reboot mode restarts the system at once and disconnects any active calls. Use it only when you can afford downtime.
• Timed reboot mode waits and applies the change during a defined window, which is the safer option for changes made during business hours.

If a change you made does not appear to take effect, the cause is almost always that it was a non-mergeable change saved without the required reboot.

Troubleshooting Avaya IP Office Web Manager

Most Web Manager problems fall into a short list of causes. This matrix maps the symptom to the likely cause and the fix.

On-Premises IP Office vs a Cloud Platform

Set the manual work of IP Office administration next to how the same tasks run on a cloud platform and the operational gap is easy to see. The table below contrasts on-premises IP Office with a cloud-delivered model for the tasks this guide covers.

The On-Premises Admin Tax

Here is the framing worth sitting with. Every task in this guide is something a modern cloud platform should not require an administrator to do by hand, and several of them carry a reboot. Call it the on-premises admin tax, the recurring cost in admin hours, scheduled downtime windows, and SD-card-and-certificate fragility that comes with owning the box rather than consuming the service.

A name change should not involve a tab hierarchy and a save-to-system step. Adding a user should not risk a NoUser state or a config reboot. On-premises IP Office makes each of these a manual procedure with failure modes attached. That tax compounds across every move, add, and change, and it is precisely the friction that pushed the market toward cloud delivery in the first place. For teams weighing that move, our guide to replacing legacy phone hardware covers the migration decision in detail.

This is where the contrast with a modern platform gets concrete. Viirtue runs a carrier-grade voice network delivered as a service, so routine administration happens in a single web interface without reboot windows or on-site hardware to maintain. For providers who resell communications rather than just run their own phones, the white-label reseller program packages that platform as a white label VoIP platform partners can put their own brand on, with quoting and billing automation handled by ViiBE. Provisioning a new customer or moving a user is a console action, not a maintenance event.

The differentiation goes beyond avoiding reboots. SIP-only providers hand you dial tone and leave billing, provisioning, and any intelligence layer for you to assemble. Standalone AI calling tools require stitching multiple systems together. Mainstream UCaaS platforms treat resellers as a channel afterthought. Viirtue's AI Voice Agents are native to the platform rather than bolted on, which means the same console that adds a user can stand up an AI agent. If you are evaluating where the IP Office estate goes next, the best white-label VoIP providers for 2026 is a useful starting comparison.

For context on scale, Viirtue supports 500 or more reseller partners on this model today, which is the practical evidence that channel-first, full-stack delivery is a working alternative to owning on-premises hardware.

Key Takeaways

• IP Office Web Manager is reached at https://<IP_Address>:8443/WebMgmtEE/WebManagement.html, and the default Administrator credential must be changed on first login.
• All four high-frequency admin tasks live under the Call Management menu, which makes it the one screen worth memorizing.
• The word "password" maps to three separate fields: user login code, extension phone password, and service-user password. Identify which one before you touch anything.
• Full Name controls the on-screen display name, and changing a user extension number rebuilds the user rather than renaming them.
• Mergeable changes apply live, while line and structural changes require Offline Mode and a reboot using Immediate or Timed mode.
• Every routine change that carries manual effort or a reboot is the on-premises admin tax that cloud delivery is designed to eliminate.

Keep the credential distinctions straight, respect the merge-versus-reboot rule, and most day-to-day administration stays routine.

Logging In to Avaya IP Office Web Manager and the Partner Opportunity

Knowing how to login to Avaya IP Office Web Manager and where each setting lives makes the console a capable tool, and the four tasks above cover the large majority of what an administrator does in a given week. The harder question is not how to run the box, but how long you should keep running it by hand. When the recurring admin tax starts wearing on your team, the calculus shifts from maintenance to migration.

If you resell communications and want a platform you can brand as your own, a cloud-delivered hosted VoIP model changes the math. There are no reboot windows, no SD cards, and no self-signed certificates to manage, and the same console that provisions a user can stand up an AI agent or generate a branded invoice. To see how the reseller economics work, become a Viirtue partner and walk through provisioning without the maintenance overhead. The Viirtue partner program is built for MSPs, IT providers, and telecom resellers who want margin ownership instead of referral fees.