What the vdremote.php remote login page is for

vdremote.php is a stripped-down web page in VICIdial built for Remote agent workers who need to receive calls on an external phone without sitting at a full softphone workstation. The page does two things: it gives the agent a status toggle to tell the dialer they are ready for calls, and it shows call information when a call comes in so the agent can see who is on the line and record a Disposition when the conversation ends. Nothing else is on the page. That simplicity is the point.

Why vdremote.php exists

A standard VICIdial Agent logs into the full agent interface on a desktop computer. The dialer connects calls to their browser-based softphone and the agent handles everything from that screen. That setup works well in an office, but it does not translate to someone on the road or a technician who only carries a mobile phone. Those workers need to receive calls on their actual phone, not a softphone, and they may not be able to keep a full browser session open all day.

vdremote.php solves this problem. The agent opens it on any device with a browser — a laptop, a tablet, or even a phone — sets their status to ACTIVE, and the dialer begins forwarding calls to their External Extension, which is the real phone number the dialer dials to reach them. The agent stays on their phone for the conversation and glances at the vdremote.php screen to see caller ID and other call details. When the call ends, they pick a disposition from the page. No softphone required, and no need to stay tied to an office machine.

What the page shows during a call

When the dialer connects a call to the agent's External Extension, the vdremote.php screen updates to show the caller ID and the data the system has on that lead. The Agent session stays active as long as the agent's status remains ACTIVE and the browser tab is open. The page is display-only during the call — the agent cannot transfer calls or access the full agent script panel from here. After the call ends, the disposition dropdown appears and the agent submits their outcome, which closes the call record and prepares the session for the next call.

How vdremote.php fits into the call flow

sequenceDiagram
  participant A as Agent browser
  participant V as vdremote.php
  participant D as VICIdial dialer
  participant P as External phone
  A->>V: Open page, set Status ACTIVE, click SUBMIT
  V->>D: Agent is ready to receive calls
  D->>P: Inbound call arrives - dial External Extension
  P-->>A: Phone rings, agent answers
  D->>V: Push caller ID and call info to page
  A->>V: Agent selects disposition and submits
  V->>D: Call record closed, agent ready for next call

The browser tab and the physical phone work independently but in sync. The dialer uses the status on vdremote.php to decide whether to route calls to this agent. The phone carries the audio. Together they give a field worker a fully functional call-handling setup without a desk or a VoIP headset.

Who can use it and what has to be set up first

The VICIdial user account tied to the remote agent record must be at level 4 or higher to authenticate through vdremote.php. Lower-level users are blocked from the page. Beyond the user level, the admin must create a Remote Agent record in the REMOTE AGENTS section that points at the correct User ID and lists the External Extension to dial. The Campaign the remote agent record belongs to also controls whether the agent receives inbound calls, outbound calls, or both. None of that is visible on vdremote.php itself — it all happens in the admin panel first, before the agent ever opens the page.

For a broader look at how remote agents fit into a VICIdial setup, read what a VICIdial remote agent is and the full remote agents and mobile guide. If you want a VICIdial server ready to accept remote agents without building the stack yourself, our managed VICIdial plans provision a running dialer in under 40 seconds.