Reading the 3-way press-1 special extension (49907, dial prefix, phone code, number)

When an agent starts a 3-way press-1 call to an outside agent, the call goes out on a single long string that looks like nonsense at first: 49907917275551212. It is not nonsense. It is four fields glued together, and once you can read it you can build the dialplan entry and debug a failed launch in seconds.

Breaking the string apart

Take the example 49907917275551212 and read it left to right:

1. 49907 is the special extension. This is the fixed prefix that tells the Dialplan to route the call into the press-1 launch script rather than dial it straight out.
2. 9 is the dial prefix. This is the digit your carrier wants in front of an outbound number, the same way a desk phone often needs a 9 to reach an outside line.
3. 1 is the phone code, the country code for the outside-agent number.
4. 7275551212 is the outside-agent number that actually gets dialed.

So 49907 + 9 + 1 + 7275551212 is just route-me-to-press-1, then dial 9, then 1, then the number. Every press-1 launch string follows that same order. If a launch fails, line the string up against these four fields and the wrong piece usually jumps out.

How the dialplan matches it

Your server matches this with a pattern like _49907. where the trailing dot means any digits can follow. That extension answers the channel, plays a moment of silence, and hands off to the launch script. Because the match is a pattern, the same single entry handles every outside-agent number; only the digits after 49907 change from call to call.

flowchart TD
  A[Agent starts press-1 call] --> B[String 49907 9 1 7275551212]
  B --> C{Dialplan matches _49907 dot}
  C --> D[Strip 49907 special extension]
  D --> E[Read 9 as dial prefix]
  E --> F[Read 1 as phone code]
  F --> G[Dial 7275551212 outside agent]
  G --> H[Hand off to press-1 scripts]

Common mistakes

The two fields that trip people up most are the dial prefix and the phone code. If your carrier does not want a 9, leaving it in turns a good number into garbage and the call dies at the Carrier. The phone code matters too: a US number wants a 1, an international one wants its own code, and mixing them up sends the call to the wrong place or nowhere. When this kind of call breaks, it is almost always one of those two single digits, not the ten-digit number on the end.

It also helps to remember what the string is for. It launches a Three-way call where the outside agent must press 1 before the customer is connected, so even a perfectly formed string is only the start. The press-1 prompt and the accept-or-decline logic come from a pair of helper scripts that run after this extension matches. If the number dials fine but the outside agent never gets prompted, the problem is downstream of the string you are reading here.

For the script that actually launches the call once this extension matches, see our writeup of agi-3way_press_agent.agi, and for the overview of when press-1 makes sense, read about 3-way press-1 calls. The whole feature sits inside the larger transfers and closers guide.

If hand-assembling dial strings and dialplan patterns is not your idea of a good time, a managed dialer hides all of it behind the agent screen. See our pricing for what that looks like.