Nortel Modular Ics 6.1 Installer Guide

							Dialing plans / 111
P0603534  02Modular ICS 6.1 Installer Guide
Call-by-Call Services Example
This example highlights the use of PRI Call-by-Call Services.
Call-by-Call routing
It shows two offices of a company. One office is in New York, 
the other is in Toronto. Each office is equipped with a Norstar 
system and a PRI line. Each office has to handle incoming and 
outgoing calls to the public network. In addition, employees at 
each office often have to call colleagues in the other office. To 
reduce long-distance costs, and to allow for a coordinated 
dialing plan between the offices, private (tie) lines are used to 
handle inter-office traffic.
Network calls are external calls, even though they are dialed 
as if they were internal calls. Only the features and 
capabilities available to external calls can be used.
When programming a button to dial a Network number 
automatically (autodial), network calls must be treated as 
external numbers, even though they resemble internal 
telephone numbers (DNs).
Toronto Office
New York  Office
Network #: 2221
    Recd #: 2221
 Internal #: 2221
DID #: 763-2221Network #: 6221
    Recd #: 6221
 Internal #: 6221
DID #:562-6221
Central
OfficeCentral
Office PRIPRI
Public NetworkTie Connection
Toronto officeNew York office
Network #: 2221
Rec’d #: 2221
Internal #: 2221
DID #: 763-2221Network #: 6221
Rec’d #: 6221
Internal #: 6221
DID #: 763-6221
PRI
Tie connection
PRI
Central 
OfficeCentral 
Office
Public network 
						

							112 / Dialing plans
Modular ICS 6.1 Installer GuideP0603534  02
If call-by-call services were not used, each Norstar system 
might have to be equipped with the following trunks:
• 12 DID lines needed to handle peak incoming call traffic.
• eight Tie (E&M) lines needed to handle inter-office calls.
• eight lines needed to handle outgoing public calls
The total required is 28 lines. If the Norstar systems were using 
T1 trunks, then two T1 spans would be required at each office. 
Note that the total of 28 lines represents the worst case value 
for line usage. In reality, the total number of lines in use at any 
one time will generally be less than 28. For example, during 
periods of peak incoming call traffic, the demand for outgoing 
lines will be low.
With PRI call-by-call services, it is not necessary to configure 
a fixed allocation of trunks. Each of the 23 lines on the PRI can 
be used for DID, Tie, or outgoing public calls. This 
consolidation means that it may be possible for each office to 
use a single PRI span, rather than two T1 spans. 
With PRI call-by-call services, the only limitation is that there 
are no more than 23 calls in progress at any one time.
The dialing plan at each Norstar site is configured to determine 
the call type based on the digits dialed by the user. If a user in 
Toronto wishes to dial a colleague in New York, they dial the 
four-digit private DN (such as 6221). The dialing plan 
recognizes this as a private network DN, and routes the call 
using Tie service with a private numbering plan.
Incoming Tie calls are routed to telephones based on the digits 
received by the network, which in this case will be the four-
digit private DN.
If a user in either location wishes to dial an external number, 
they dial 9, followed by the number (such as 9-555-1212). The  
						

							Dialing plans / 113
P0603534  02Modular ICS 6.1 Installer Guide
dialing plan recognizes this as a public DN, and routes the call 
using Public service.
Incoming DID calls will be routed to telephones based on the 
trailing portion of the digits received by the network. For 
example, if a public network user dials an employee in the 
Toronto office, the network will deliver digits 4167632221. 
Norstar will route the call using the last four digits, 2221.
Norstar Configuration
Toronto:
HardwareCard 1PRI
ProtocolNI-2
Trk/Line DataLine 245Target line
Rec’d #2221
Line AccessDN 2221L245:Ring only
Line pool accessLine pool PRI-A
To New York:
Routing ServiceRoute001
DIalOutNo numbr
UsePool PRI-A
SrvcTypeTie
ServiceID1
DN typePrivate
DestCode6
Normal rte001
Absorb0 
						

							114 / Dialing plans
Modular ICS 6.1 Installer GuideP0603534  02
To Public Network:
Routing ServiceRoute002
DialOutNo numbr
UsePool PRI-A
DN typePublic
DestCode9
Normal rte002
AbsorbALL
New York:
HardwareCard 1PRI
ProtocolNI-2
Trk/Line DataLine 245Target line
Rec’d #6221
Line AccessDN 6221L245:Ring only
Line pool accessLine pool PRI-A
To Toronto:
Routing ServiceRoute001
DialOutNo numbr
UsePool PRI-A
SrvcTypeTie
ServiceID1
DN typePrivate
DestCode2
Normal rte001
Absorb0 
						

							Dialing plans / 115
P0603534  02Modular ICS 6.1 Installer Guide
PRI dialing plan example for two-way DID
The following list shows the steps involved in configuring a 
dialing plan for two-way DID which uses a Public service. In 
this example the user dials the prefix 8 to place a call over a 
PRI line. 
Note:  Call-by-call is not needed to have two-way DID.
•in Hardware programming, configure the DTI card (PRI) 
to use a Public protocol
• for incoming calls you need to program target lines to 
match the DID digit that is being received on the PRI 
interface
•set Dial Out to None
• select PRI-A as the line pool
•set SrvcType to Public
•in Services programming access Routing Service to 
enter a Destination Code (8 in this example)
• set the Absorb Length to All
• the telephone that you are dialing out from must have 
access to the PRI Pool (programmed in Terminals/Sets)
To Public Network:
Routing ServiceRoute002
DialOutNo numbr
UsePool PRI-A
DN typePublic
DestCode9
Normal rte002
AbsorbALL 
						

							116 / Dialing plans
Modular ICS 6.1 Installer GuideP0603534  02
•define rec’d digits for target lines
• define limits for incoming and outgoing public calls. Refer 
to Programming Call by Call Limits on page 461
Static DID and two-way DID
When configuring static DID with two-way service, the 
channels programmed as DID at the CO must be the lowest 
B-channels on the PRI. On your Norstar system, the BchanSeq 
mode must be set to descending. In this configuration, all 
calls on the PRI must be Public service.
For example, channels 1 to 4 are configured as DID at the CO. 
The CO uses ascending mode for B-channel selection, and the 
ICS uses descending mode. 
						

							Private networking using PRI SL-1 / 117
P0603534  02Modular ICS 6.1 Installer Guide
Private networking using PRI SL-1
You can use PRI SL-1 lines to tandem a number of Norstar 
units into a private network. This creates a Private Network 
Tandem Calling (PNTC) configuration. Refer to Private 
Network Tandem calling on page 119.
You can also use PRI SL-1 lines to link one or more Norstar 
systems to a Meridian 1 system, or to create a network that 
includes one or more Business Communications Manager 
systems. This creates an Advanced Private Network (APN) 
where the MCDN protocol can be used to provide network 
control features that allow network calls to be delivered and 
transferred with optimum efficiency. If you also use a central 
voice mail system or central Auto Attendant system off the 
Meridian, MCDN provides system-wide Auto Attendant 
features and line redirection. Refer to Advanced Private 
Networking on page 128.
SL-1 networking features
• common dialing plan using a Uniform Dialing Plan 
(UDP), or a Coordinated Dialing Plan (CDP)
Note: If Norstar voice mail or Auto Attendant is used as 
the centralized voice mail system, CDP must be used.
• PRI networks can be used for voice, data, and video calls
• no usage costs when placing remote calls over private 
networks
Tip - For Modular ICS 6.1 you require both a PRI software 
key (profile 1, 3, and 4 only) and an MCDN software key to 
perform SL-1 networking.
All Norstar systems in the network also must be running 
MICS 6.1 or MICS-XC 6.1 or greater software. 
						

							118 / Private networking using PRI SL-1
Modular ICS 6.1 Installer GuideP0603534  02
• caller information appears on both the caller telephone and 
the called telephone, regardless of the number of 
redirections
• PSTN lines connected to one of the nodes in a network can 
provide local public service, at local rates, to all nodes in 
the network, regardless of location
Features specific to Advanced Private Network
• centralized voice mail provides call waiting indications on 
the receiving telephone
• centralized voice mail provides common messages, call-
forwarding and transfer options to all networks. If you are 
using the Meridian attendant system, the attendant console 
on the Meridian system can use system-wide call parking 
(camp-on) and break-in features.
• if you have trunk route optimization (TRO) turned on, the 
system optimizes call routing of redirected calls over the 
private network
• the Meridian PBX can handle both UDP and CDP, thus 
providing more flexibility and less reprogramming when 
networking existing systems. The Norstar Voice mail 
system requires a CDP dialing plan when it is being used 
for central call handling.
• Trunk Anti-tromboning (TAT) provides network rerouting 
that provides more efficient routing of calls to prevent 
unnecessary tandeming and tromboning of trunks.
• ISDN Call Connection Limitation (ICCL) piggybacks on 
the call initiation request and acts as a check at transit PBX 
points to prevent misconfigured routes or calls with errors 
from blocking channels. 
						

							Private networking using PRI SL-1 / 119
P0603534  02Modular ICS 6.1 Installer Guide
• NCRI count allows a call to be forwarded in the network 
up to five times before the system releases the call as 
undelivered. However if TAT or TRO occur, the counter 
gets reset, as well. This counter is hard-coded.
Private Network Tandem calling
Tandem networking is a chained network established between 
two or more MICS systems. All the systems are connected via 
PRI SL-1 lines. 
In the network example shown below, nodes A, B, and E are 
in one location, Nodes C, D, and F are in a second location. 
The two systems are tied together between nodes A and C. 
Nodes A and C are also connected to the local public network.
Tandem network
This configuration allows both local network users and remote 
users on the public network to access the remote PSTNs 
through the private lines, thus avoiding public call charges.
Lines to public 
networkPublic
Networkprivate trunkprivate trunk
Norstar
Norstar
Public
Networkprivate trunk
Norstarprivate trunk
NorstarLines to public 
network
Norstar
private trunk
Calgar y
Norstar
Ottawa
A B
E
C
D
F
Calgary network 
routes only area 
codes 403 and 
604 Public: 403-765-XXXX
Private ID: 395
Ottawa network 
routes all area 
codes except 
403 and 604 Public: 403-762-XXXX
Private ID: 392Public: 403-761-XXXX
Private ID: 391
Public: 613-766-XXXX
Private ID: 396Public: 613-764-XXXX
Private ID: 394Public: 613-763-XXXX
Private ID: 393 
						

							120 / Private networking using PRI SL-1
Modular ICS 6.1 Installer GuideP0603534  02
All nodes have unique three-digit private identification codes 
as well as public network codes. Routes and destination tables 
are configured on all systems to correctly route dialed numbers 
to other nodes. DNs do not necessarily have to be unique, but 
they must be the same length on all systems.
Calls originating from the public network
Received Destination Description
Node A Node A User in Calgary dials 761-xxxx number
Incoming interface: Public
DN type: Public
Node A receives the call and identifies it as 
terminating locally. Uses target line to route call.
Destination: Local (target line)
Node A Node B User in Calgary dials a 762-xxxx number
DN type: Public
Node A receives it and identifies it as being for 
node B. Uses private trunk to route it to B.
Incoming interface: Public
Destination: Remote Node
Outgoing interface: Private
Node B receives the call and identifies it as 
terminating locally. Uses target line to route call.
Incoming interface: Private
Destination: Local (target line)