more topics![]() |
Incoming Calls
Incoming calls are routed by line appearance or can apply routing by dial plan, a routing system for incoming calls programmed by the Dial Plan Routing Table (see Sample PRI Dial Plan Routing Table).
![]() |
Where the Switch Type setting is LEGEND-Ntwk or LEGEND-PBX for a PRI trunk, incoming calls are automatically set to Route Directly to UDP. PRI routing by dial plan and line appearance are not used. This cannot be changed unless the Switch Type setting is modified. |
PRI Call Processing (Non-Tandem Only)
Where: |
|
|
ARS = Automatic Route Selection |
DPR = Dial Plan Routing Table |
NS = Network Selection Table |
CBC = Call-by-Call Services Table |
DPT = Direct Pool Termination |
SA = System Access |
PL = Personal Line |
|
SSS = Special Services Selection Table |
Routing by Dial Plan (Hybrid/PBX Only). Routing by dial plan is similar in concept to Direct Inward Dial (DID). It provides the ability to direct a call automatically to the proper destination for improved call distribution and call handling. Unlike a DID line, a PRI line (or T1 line) programmed for routing by dial plan can accommodate outgoing calls as well as incoming calls. As with DID operation, this feature is available only in Hybrid/PBX mode.
PRI Routing by Dial Plan. Routing by dial plan also allows multiple calls to a directory number. Concurrent incoming calls with the same Called Party Number can be delivered to a destination simultaneously.
The Dialed Number Identification Service (DNIS) is a service attribute of the Megacom 800 service. Based upon customer-selected parameters, such as area code, state, or time of call, it provides distinct Called Party Numbers for incoming 800 and 900 calls.
For each B-channel group, the system can be programmed for either routing by line appearance or routing by dial plan. With routing by dial plan, the Dial Plan Routing Table must be programmed to contain a series of patterns--the number of digits in the CdPN, network services on which to match, and a number of digits to add or delete for each match--in order to route the call to the proper destination.
If a B-channel group is programmed for routing by dial plan, all incoming calls to that B-channel group are routed in a DID-like manner and terminate on an SA button, on a single-line telephone, into a Calling Group queue, or at a Queued Call Console (QCC). When an incoming call arrives, its network service type and CdPN are compared to entries in the Dial Plan Routing Table. If no match is found, the call is routed to the programmed backup position for unassigned DID calls (normally the primary system operator). If a match is found, the CdPN is manipulated according to the Dial Plan Routing Table before matching it against the inside dial plan to identify a destination to which the call is delivered. If the manipulated CdPN does not match an inside extension, it is treated as an unassigned DID call.
If a fast busy tone is programmed as the routing destination for unassigned Direct Inward Dial calls, the call is rejected. This typically causes the network to return an intercept tone instead of a fast busy tone. If the number matches a destination that DID calls are not permitted to reach (for example, pool access codes, group page codes, line access codes, or the ARS access code), the call is routed to the programmed destination for unassigned DID calls (unless the backup is a fast busy tone).
The table below is a sample Dial Plan Routing Table. Note that
in the sample table all incoming calls through the Megacom 800 service are delivered
to an extension whose dial plan number is 1234. Entry 15 would be skipped because
No Service is specified.
Sample PRI Dial Plan Routing Table
Entry |
0 |
1 |
2 |
3... |
15 |
Service |
SDN |
SDN |
MEG800 |
|
No Service |
# of digits in CdPN |
7 |
10 |
10 |
|
[not specified] |
Example # |
555-1234 |
908-555-1234 |
|
|
|
Pattern |
555 |
[none] |
[none] |
|
[none] |
Digit deletion |
3 |
6 |
10 |
|
14 |
Digit addition |
[none] |
[none] |
1234 |
|
0 |
When routing by dial plan is used for an incoming call, if the programmed service, number of digits in the Called Party Number (CdPN) and patterns match those associated with the incoming call, the appropriate digit deletion and addition are performed. The process is as follows:
![]() |
When a call arrives on a dial plan routed PRI facility and its digits match an extension on the non-local dial plan, the call is routed to the appropriate non-local extension. |
Characteristics and valid entries for the Dial Plan Routing table are as follows:
Hyphens are inserted between the digits on incoming calls (for example, 555-1234 for a 7-digit display and 123-555-1234 for a 10-digit display). Any other number of digits appears without hyphens.
A brief description of the display support for incoming calls provided follows (see Display for additional details).
![]() |
PRI display support applies to 4400-Series, MLX, TransTalk 9031/9040, Business Cordless 905, ETR, and MLS display telephones. |
Display preferences for incoming private-network calls are set up by using the Extensions menu. This setup affects calls arriving on tandem PRI trunks. You can set up 4400-Series, MLX, TransTalk 9040 (when connected to a TDL port), and ETR display telephones to display the extension number of the caller on the remote system, the programmed label, or both the label and the extension number. If ANI/ICLID information is provided for an outside call, it appears instead of the extension number and/or label. See Display for additional details.