How to Block Agents From Dialing Out With the agent-nodial Phone Context

If you run a call center, you usually do not want agents picking up their handset and dialing whatever number they like. Unrestricted outbound dialing is a compliance risk, a cost risk, and a security risk all at once. VICIdial lets you lock that down with a single field on the Bulk Phone Insert page: Phone Context. This post explains what that field does and how the value agent-nodial stops outbound dialing cold - without you writing any custom dialplan code.

What Phone Context actually controls

Phone Context is the Dialplan context that a phone uses when it tries to dial out. Asterisk reads the context to decide which set of dial rules applies to that Extension. The default value is the literal word default, which is wired up to place normal calls. If you change the context to a name that does not exist in the dialplan, Asterisk has no rules to match - so any call attempt from that phone simply fails.

That is the whole trick. You do not need to write a single line of restrictive dialplan code, build an outbound deny list, or maintain a custom context. You just point the phone at a context that is empty by design, and the dial attempt dead-ends. It is the kind of fix that is hard to break, because there is nothing there to break - the absence of rules is doing the work.

Why agent-nodial is the conventional value

agent-nodial is just a well-known, deliberately undefined context name. There is nothing magic about the string itself - any non-existent context would work. The convention matters because the next person who reads the phone config understands the intent immediately: this phone is not allowed to dial out on its own. Pick a random misspelled context and a teammate might assume it is a typo and try to fix it; agent-nodial reads as a decision.

Crucially, this does not break the agent's actual work. Calls still flow normally inside the VICIdial application, because the dialer hands those calls to the Agent through its own channels, not through the phone's outbound context. The agent answers customers, transfers calls, and joins conferences exactly as before. The only thing you have removed is the ability to start a freelance call from the device itself.

How the decision plays out

flowchart TD
  A[Agent phone tries to dial] --> B{Phone Context value}
  B -->|default| C[Dialplan matches]
  C --> D[Outbound call placed]
  B -->|agent-nodial| E[No matching context]
  E --> F[Dial attempt fails]
  G[VICIdial app call] --> H[Routed by dialer]
  H --> I[Agent connected normally]

Inbound campaign calls and dialer-pushed calls are unaffected. Only operator-initiated outbound dialing from the device is blocked. That distinction is the whole point: agents stay productive on the calls you assign them, but they cannot route personal or unauthorized calls through your trunks and your caller ID.

Setting it during bulk insert

When you create phones in batches, set the value once and it applies to every phone in that run. The fields you care about here are:

• Phone Context - type agent-nodial instead of default.
• Phones - one extension per line, the set you are locking down.
• Client Protocol - the phone protocol, for example SIP (Session Initiation Protocol), which writes the matching Conf file entries.

There is no UNDO on the bulk insert utility, so test with two or three phones before running a large batch. Confirm those test phones behave the way you expect - they should register and take dialer calls, but a manual dial-out attempt should fail - and only then run the full set. For the wider walkthrough of every field on that page, see the Bulk Phone Insert explainer.

One gotcha: rebuild the conf files

Submitting the bulk insert form does not rebuild Asterisk config on its own. You have to trigger a manual rebuild before the new context takes effect on the phones. See why bulk phone insert needs a manual conf rebuild for the exact steps.

This field is part of the larger set of batch admin utilities. For the full map of what each tool does, read our VICIdial admin bulk tools guide.

Want a managed VICIdial box where the phone provisioning and dialplan are set up for you? Check VICIfast pricing and get a branded dialer in under 40 seconds.