DID Extension Context explained

When you edit a DID (direct inward dialing), one of its routing choices sends the call straight to a raw dialplan extension. Two fields control that path: Extension and Extension Context. They look simple, but getting the context wrong is a common reason calls vanish or voicemail refuses to play.

Where these fields come in

A DID has a DID Route that decides where its calls go. The options include EXTEN to send a call to a dialplan extension, AGENT to send it to a logged-in agent, PHONE for a configured phone, IN_GROUP for an inbound group, VOICEMAIL for a mailbox, and CALLMENU for an IVR menu. The default route is EXTEN.

The Extension and Extension Context fields only matter when the route is EXTEN. The Extension is the dialplan extension the call is sent to; its default is 9998811112, which is the built-in no-service announcement. The Extension Context is the dialplan context that extension lives in, and its default is simply default.

What a context actually is

Think of a context as a named bucket of dialplan rules in the Dialplan. The same extension number can mean different things in different contexts, so the system needs both the number and the context to know exactly which rule to run. This is why an EXTEN route is really a pair: an extension plus the context it should be looked up in.

Because DIDs can point at extensions in any context, including Asterisk-based IVRs, this is also how you hand a call off to custom dialplan logic that lives outside the standard VICIdial screens.

How the route reads these fields

flowchart TD
  A[Call hits DID] --> B{DID Route}
  B -->|EXTEN| C[Read Extension and Context]
  C --> D[Look up Extension in that Context]
  D --> E[Run dialplan rule]
  B -->|VOICEMAIL| F[Context must be default]
  F --> G[Mailbox plays]

If you are not building custom dialplan rules, you usually will not touch the context at all. Most real inbound setups skip EXTEN entirely and route the DID into an inbound group so calls reach agents in a managed queue. When you do that, the Extension and Context fields are ignored and the in-group settings take over.

When EXTEN does make sense is when you have hand-built dialplan logic the standard screens do not cover: a custom announcement, an after-hours branch, or an Asterisk IVR that someone wrote for you. In those cases the extension and its context are how the call crosses from VICIdial's routing into that code. If you find yourself guessing at a context name, that is usually a sign the call belongs in an inbound group or a call menu instead, where the routing is point and click and there is no context to get wrong.

Worth noting: once a DID is created you cannot rename its extension. To change it you delete the DID and re-create it. So pick the extension and route carefully the first time. If you have not built a group for these calls to land in yet, follow how to add an inbound group first, then come back and set the route. The wider walkthrough lives in the inbound call handling guide.

Editing contexts by hand assumes you have a healthy box and access to the dialplan. If you would rather have a working, ready-to-route system stood up for you in under a minute, see our managed VICIdial plans.