Phone — CTI Routings

The CTI Router decides where each call goes. Every incoming call is checked against the routing table — when a rule matches, the call is sent to that rule's exit port. The first matching rule wins.

The dial plan (CTI Routings) is the set of rules that tells the Abilis phone system where to send each call. For example: "when someone dials 9 + a number, route it to the outside phone line" or "when extension 200 is called, ring the phone in the reception."

The Routing Table

CTI Routings — the main table showing three routing rules with Priority, Active, Editable, Entry Port, Called/Calling number, and Exit port columns.

Routings are checked in number order, starting from the smallest. The CTI Router reads the PR column top-down (0, then 1, then 2…) and uses the first routing that matches the call. The rest are ignored. So a more specific routing must have a smaller PR than a broader one, or it will never be reached.

The main view shows a table of all routing rules. Columns:

Column	What It Means
PR	Priority — a dropdown number. The Abilis checks rules in order from lowest PR to highest. The first matching rule wins.
Active	Checkbox — is this rule currently in use?
Editable	Checkbox — same as the User editable field shown in the rule editor below. When unticked, only administrators can modify this rule.
Description / Objective	A human-readable note explaining what this rule does.
Entry port	Where the call enters the Abilis (e.g. a SIP trunk, a CTIP port).
Called number	The number pattern to match — what was dialled. Can reference a list in single quotes (e.g. `'numsip'`) — same syntax as ACL rules.
Calling number	Who is calling — used to filter based on the caller's identity.
Exit port	Where to send the matching call.

Click New + to add a routing. Click an existing row to expand and edit it.

Editing a Routing — Three Sub-Tabs

When you create or edit a routing, you see:

Basic parameters

Active — tick to enable this routing.
User editable — tick if non-admin users should be able to modify it.
Description — free text explaining the rule's purpose.

Input values used to choose the route

New routing — Input values sub-tab showing Call Origin, Addressing, Time/Date Constraints, and Management of Alternate Routes.

Conditions that a call must match for this rule to apply:

Addressing:
— Called address input (e.g. 00 for international prefix)
— Calling address input (e.g. * for any caller)
— Advanced: Called/Calling sub-address, Redirecting calling input
Time/Date Constraints: up to 5 time intervals.
Format: <day-spec>,HH:MM-HH:MM. The day-spec can be a single day (MO), a range (MO-FR), a set (MO+WE), ALL for every day, or a specific date (24/12/26).
Examples: ALL,00:00-23:59 (24/7), MON-FRI,08:00-18:00 (business hours), SAT+SUN,10:00-16:00 (weekends only).
Management of Alternate Routes: an alternate route is a backup rule that fires only when the previous rule failed. If you're configuring one, set LAST (the "last failure reason for conditional match") to one of:
— BUSY — the previous attempt got a busy signal.
— NOANS — no answer within the timeout.
— OTHER — any other failure reason.
— ANY — catch all of the above.
For a primary (non-alternate) rule, leave LAST blank or permissive. Alternate-route rules must be consecutive in the table.

New values

What the routing rule actually does to a matching call:

Call Destination — the exit port and any per-port options. This is where the call is sent (a SIP trunk, a CTIP port, a cluster member, a DISA service, etc.).
Addressing output — how the called and calling numbers are rewritten on the way out (prepend a prefix, strip leading digits, replace entirely, etc.). Use this to translate between internal extension numbers and external dialling formats.
Alternative routing selection (NEXT) — if this rule fails, which alternate rule to try next. Pairs with the LAST parameter on the following (alternate) rule.

Advanced Parameters

Visible when the Advanced checkbox is ticked:

Bearer capability input — what kind of call this rule matches.
Common shortcuts: VOICE (Speech + 3.1 kHz, the normal voice cases), DATA (UDI + RDI, modem/data calls), TR (any).
Or pick one of the underlying values: Speech, 3.1kHz, UDI, RDI, UDI-TA, Video.
Voice compression bit rate — the bit rate the codec uses, in bits per second. Lower = less bandwidth, lower quality.
Valid values include 5300, 6300, 6400, 8000, 13200, 16000, 32000, 64000 (and several more). 6400 is a typical low-bandwidth value; 64000 is uncompressed-equivalent (G.711).
Allowed coders — which audio codecs this rule will accept. Sys (the default) means "use the coders configured on the CTISYS resource"; otherwise pick from: G.711, G.711A, G.711u, G.726, G.727, G.729A, GSM6.10, G.723.1, ILBC, SPEEX, Spirit, Transp. Click Edit Coders for the per-codec configuration dialog.

Worked examples

Two examples (adapted from the v9.0 reference manual) to show what a complete rule looks like in practice.

Example 1 — Route incoming 3-digit calls from SIP to the internal PBX

"When a call comes in on a SIP trunk and the dialled number starts with 5 followed by two more digits, route it to the internal PBX group, using the G.711 codec."

Field	Value
PR	`21`
Bearer capability	`VOICE`
Entry port	`Sip`
Called number pattern	`5??` (`?` matches one digit)
Exit port	`PBX`
Allowed coders	`G.711`

Example 2 — Route PBX calls to another Abilis via cluster

"When a call comes from the local PBX and the dialled number is in the 'ToAbilis2' list, send it to the Abilis2 cluster member."

Field	Value
PR	`2`
Bearer capability	`VOICE`
Entry port	`PBX`
Called number pattern	`'ToAbilis2'` (matches any number in the list)
Exit port	`Abilis2` (cluster member)

CTI Routings control the entire phone system. A wrong rule can prevent calls from connecting or route them to the wrong destination. Work carefully: review existing rules before adding new ones, and test each change by making a call immediately after saving.

Anteklab Technical Support Email: tem@antek.it
Tel: +39 0376 16262,27

← Statistics Phone How-To →