What Create Alias Entries Does for Phone Login Load Balancing

On a single-server VICIdial install you never think about aliases. The moment you run more than one server, you need a way for one login to mean the same phone no matter which box it lands on. That is what the Create Alias Entries option on Bulk Phone Insert sets up, and it is the piece that makes phone-login load balancing actually work.

What an alias is

Setting Create Alias Entries to YES makes a phones alias entry for each Extension you insert. That alias ties together all the same-numbered extension entries across every server, so the agent interface can treat them as one logical phone instead of several unrelated ones. The result is phone-login load balancing: an Agent logs in with one id and gets routed onto whichever server has room, rather than always hitting the same box.

How the suffix builds the alias id

The Alias Suffix is the string appended to the extension to form the alias id. If the extension is cc100 and the suffix is x, the alias id is cc100x. Pick a short, consistent suffix and use it across every bulk run so your alias ids stay predictable - mixing suffixes between runs is a quick way to end up with aliases that do not line up the way you expect.

How a login resolves

flowchart TD
  A[Agent logs in with cc100x] --> B[Alias cc100x]
  B --> C{Which servers have cc100?}
  C --> D[Server A cc100]
  C --> E[Server B cc100]
  C --> F[Server C cc100]
  D --> G[Pick least-loaded server]
  E --> G
  F --> G
  G --> H[Agent connects there]

When to turn it on

• You run two or more servers and want one login to work across all of them.
• You want the agent interface to spread phone logins for balance rather than pinning each agent to one box.
• You are inserting the same extension list across every server in the same run, which is the only way the aliases can line up.

When to leave it off

On a single server there is nothing to balance across, so aliases add complexity with no payoff - leave Create Alias Entries set to NO. The same goes for a setup where you deliberately want each SIP (Session Initiation Protocol) or IAX2 phone tied to one specific box, for instance when a particular agent must always register to a particular server. In those cases an alias just gets in the way.

Get the surrounding steps right

Aliases only help if the underlying extensions exist on every server first - the alias points at the per-server phone rows, so those have to be there. Build that matrix as described in how to bulk-insert phones across multiple servers, and review the full field list in what the Bulk Phone Insert page does. Both sit inside our VICIdial admin bulk tools guide. And remember to rebuild your conf files afterward - the insert does not do it for you, aliases included.

So aliases are a small option with a big role: they are the glue that turns several independent servers into one pool an agent can log into without caring which box answers. Set the suffix once, keep it consistent, and let the agent interface handle the routing. Not sure you need a multi-server setup at all? Most teams run fine on one dedicated box, where load balancing and aliases simply do not apply. See VICIfast pricing to compare.