DPN Call Redirection System User Guide

DPN-100
DPN Call Redirection System

User Guide
241-1001-115
DPN-100

User Guide
Publication: 241-1001-115
Document status: Standard
Document version: 37.2S1
Document date: February 2001
Copyright 1986 - 2001 Nortel Networks.

All Rights Reserved.
Printed in Canada
NORTEL, NORTEL NETWORKS, the globemark design, the NORTEL NETWORKS corporate logo,
DPN, and PASSPORT are trademarks of Nortel Networks
List of revised pages

The following is a list of documentation revisions for service requests (SR) or
release reports, or both:
Updates: Page 16, 18, 19, 20, 21, 23, 24, 25, 26, 27, 28, 29, 31, 32, 34, 35, 37,
39, 42, 43, 44, 45, 47, 48, 51, 52, 53, and 57.
DPN-100 DPN Call Redirection System User Guide
37.2S1
6 List of revised pages
241-1001-115 37.2S1
Publication history
February 2001
37.2S1 Standard
Commercial availability
37.2S1
8 Publication history
241-1001-115 37.2S1
Contents
About this document
15
Who should read this document 15

What you should know 15
How this document is organized 15
Typographic conventions 15
Related documents 16
Chapter 1
Introduction to call redirection
17
Why call redirection is required 17

Benefits of call redirection 17
When call redirection is required 17
Internal failures 18
External failures 18
Other failures 18
How call redirection works 18
Routing identifier (RID) redirection 19
DNA redirection 22
Data network identification code (DNIC) redirection 27
Chapter 2
Components of the call redirection system
31
Introduction 31
Call redirection remote server interface 31
Call redirection server on an AM or RM 32
DNIC redirection 33
DNA Redirection 34
Initialization of SVCs 35
SVC setup on an RM 35
Interaction with other systems 37
Interaction with hunt groups 37
PVC back-up description 37
Limitations 39
37.2S1
10
Chapter 3
Operations
41
Introduction 41
Call redirection system operator commands 42
DPN AM/RM operator commands 42
DPN RM operator commands 42
Call redirection system service data 42
DPN AM/RM redirection service data 43
DPN RM CRD-RSI service data 44
Alarms 44
Accounting 45
Statistics 45
Chapter 4
Provisioning the servers
47
Related documents 48
Provisioning Access to Call Redirection 48
Before you begin 48
Service data entry fields 50
Steps to follow when provisioning Access to Call Redirection 51
Provisioning Call Redirection 52
Before you begin 52
Service data entry fields 54
Steps to follow when provisioning Call Redirection 56
Index
241-1001-115 37.2S1
59
Contents 11
List of figures
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
Figure 9
Figure 10
Figure 11
RM RID redirection - RID failure 20

RM RID redirection - network link failure 21
DNA redirection - RM 24
DNA redirection - RM 25
Flow of DNA redirection with alternate path defined 26
DNIC redirection 28
DNIC redirection list - call redirection server 33
DNA redirection list 34
SVC initialization 36
PVC backup 38
Reconnecting primary slave end of a PVC 39
37.2S1
12 Contents
List of tables
Table 1
Table 2
Table 3
Table 4
Table 5
Table 6
Table 7
241-1001-115 37.2S1
Hierarchy: Access to Call Redirection components 48

ACRD service data fields 50
Hierarchy: Call Redirection server components 52
Hierarchy: Call_Redirection_Server using the
PE_Combination_Server 53
Hierarchy: Call Redirection list components 53
Call_Redirection server data fields 55
Call_Redirection list data fields 56
Contents 13
List of procedures
Procedure 1
Procedure 2
Procedure 3
Procedure 4
How to add Access to Call Redirection to an RM 51

How to add Access to Call Redirection to an existing RMSERVER
PE 51
How to add the Call Redirection server 57
How to add the Call_Redirection_Server using the
PE_Combination_Server component 57
37.2S1
14 Contents
241-1001-115 37.2S1
15
About this document

This document provides the reader with an introduction to call redirection and
an outline of how the DPN Call Redirection System works. Details on how to
provision the server are also provided.
Who should read this document

This document was written for customers interested in obtaining the Call
Redirection System (CRD) for a network. The document is also intended for
network operators who set up and modify the CRD on a switch.
What you should know

Before you read this document you should have a basic understanding of the
DPN network. Also, you should be familiar with the DPN Architect
provisioning applications.
How this document is organized

This document is organized into four chapters:
Chapter 1, Introduction to call redirection provides an introduction to

the Call Redirection (CRD) system and describes the flow of a call through
the system.
Chapter 2, Components of the call redirection system provides a

description of the system components.
Chapter 3, Operations provides an outline of the Operations,

Administration, and Maintenance aspects of the system.
Chapter 4, Provisioning the servers explains how to provision both the

Access to Call Redirection (ACRD) server and the Call Redirection (CRD)
server.
Typographic conventions
The following conventions are used in this document:
plain text in courier font that occurs in
procedures represents system generated text or text that appears on your
screen.
Plain text in courier font:
37.2S1
16 About this document
bold text in courier font that appears in a procedure represents

words that you should type or that you should select on the screen.
Bold text:
Italics: words that appear in italics in a procedure explain the results of a

particular step and appear immediately following that step. Words that appear
in italic in paragraphs represent words that are special or that need to be
highlighted.
[optional_parameter]: words in square brackets represent optional parameters.
The command can be entered with or without the words in the square brackets.
<general_term>: words in angle brackets represent general terms which are to
be replaced with specific numeric values.
UPPERCASE, lowercase: uppercase and lowercase letters that appear in
commands and parameters must be matched exactly. The system matches
upper and lowercase characters differently unless otherwise stated.
Related documents
The following publications are referred to in this document:
NTP 241-1001-110, DPN Routing System General Description
NTP 241-1001-153 DPN System Engineering Guidelines
NTP 241-1001-183 Addressing Plan
NTP 241-1001-303 Operator Commands and Responses
NTP 241-2001-340 Envelope Definitions
Other relevant documents are as follows:
NTP 241-1001-506 Alarm Console Indications
NTP 241-1001-509 Call Clear, Reset and Diagnostic Codes
NTP 241-1001-117 DPN AM/RM Hunt Group Server User Guide
241-1001-115 37.2S1
17
Chapter 1
Introduction to call redirection
This chapter provides an introduction to the Call Redirection system and
describes the flow of a call through the system. The information in this chapter
is ordered as follows:
Why call redirection is required
When call redirection is required
How call redirection works
Why call redirection is required

Call Redirection is required in a network to route calls to alternate destinations
if the primary destination is not available. This allows subscribers to achieve
higher reliability on data communication paths by providing one or more
redundant paths for call attempts.
Benefits of call redirection

The DPN Call Redirection System provides the following benefits:
high capacity
high performance
isolated change management
enhanced administration capabilities
When call redirection is required

The Call Redirection System is invoked when a destination is not available due
to a failure. There are three types of failures: internal, external, and other
failures.
To re-route a call that has been signalled on the link by the X.25 service, the
host must initiate the ITU X.25 Call Deflection feature using an X.25 facility
code.
37.2S1
18 Chapter 1
Internal failures
An internal failure occurs in switch hardware when some internal component
fails. These failures could occur in:
line cards
processors
shelves
nodes
network links
trunks
External failures
External failures occur outside the switch. These failures could occur in
customer data terminal equipment (DTE)
customer connections to the switch
Other failures
Call routing failures may not always be due to a failed component or link. One
example is when the call options specified by the calling end are not
compatible with those supported by the called end. Another example is when
the called end is busy (that is, no free channels for the incoming call).
How call redirection works

Three types of call redirection are performed:
Routing Identifier (RID) Redirection, for routing around switch or network

failures.
Data Network Address (DNA) Redirection, for routing calls to alternate

destinations within the same network.
Data Network Identification Code (DNIC) Redirection for routing to other

networks.
RID redirection will always be attempted first. If it fails, DNA redirection or

DNIC redirection will be attempted.
In order to perform these redirection functions, the following entities are
required in the network:
a Call Redirection Remote Server Interface on each RM in the network;

and
a Call Redirection Server on selected AMs or RMs in the network.
241-1001-115 37.2S1
Introduction to call redirection 19
These components are described in more detail in the section called

Components of the Call Redirection System.
Routing identifier (RID) redirection
Each node in the network is identified by an RID. A called destination may be
available through more than one RID, one of which is designated as the
primary RID and the other the back-up RID. If a call can not reach its
destination through the primary RID then the Call Redirection System will
attempt to route the call through the back-up RID.
RID redirection is intended for use for AMs connected to two distinct RIDs.
RID redirection handles two types of failure: RID failure, and network link
failure.
If the primary RID fails, calls will be routed to the destination AM through the
back-up RID. Figure 1 illustrates the flow of a call through RID redirection
caused by an RID failure.
If the network link between the primary RID and the destination AM fails, the
call will be routed to the destination AM through the back-up RID. Figure 2
illustrates the flow of a call through RID redirection caused by a network link
failure. The back-up RID, if defined, is found in the RID redirection list. This
list is derived from the RID redirection envelope and is maintained on all nodes
in the network. A single back-up RID may be defined for each RID in the
network.
RID redirection fails when one of the following occurs:
the back-up RID is not defined;
there is no route to the back-up RID; or
there is no route from the back-up RID to the called destination.
Either end of an established call that is experiencing communication problems

sends a recovery packet to the other end to reestablish the communication on
possibly a different path. This feature is described in NTP 241-1001-110, DPN
Routing System General Description under the name VC Recovery. When a
recovery packet can not reach its destination, it is sent to a Call Redirection
Remote Server Interface on an RM where the destination RID is replaced by a
back-up RID using RID Redirection.
The redirection of recovery packets is enhanced. Each end of a call is
dynamically informed of the existence of an alternate RID through which the
other end can be reached. When it sends a recovery packet, one end of a call
includes the alternate RID of the other end in the packet.
If a recovery packet must be redirected and an alternate RID is specified in it,
37.2S1
20 Chapter 1
this alternate RID is directly used as the back-up RID. This enables the backup RID to be dynamically chosen on a per call basis rather than quasi statically
specified, in service data, on a per RID basis. If no alternate RID is specified,
the back-up RID is still taken from the RID Redirection List.
Note 1: RID redirection does not modify the destination address digits of
a call.
Figure 1
RM RID redirection - RID failure
RID
REDIRECTION
LIST
CALL REDIRECTION
REMOTE SERVER
INTERFACE
1
RM2
RM1
5
3
2
RM3
AM1
(DESTINATION)
Incoming call to RM1.
Call routed to AM1 but primary RID (RM3) is not available.
Call returned to RM1 Call Redirection Remote Server Interface.
241-1001-115 37.2S1
RID redirection list is searched and an alternate RID (RM2) selected.
Call routed through RM2 to original destination.
Figure 2
RM RID redirection - network link failure
CALL REDIRECTION
REMOTE SERVER
INTERFACE
RID
REDIRECTION
LIST
4
1
RM2
RM1
AM1
(DESTINATION)
Call routed to AM1 but network link is not available.
Call returned to RM1 Call Redirection Remote Server Interface.
RID back-up list is searched and alternate RID selected.
Call routed through RM2 to original destination.

37.2S1
22 Chapter 1
DNA redirection
If RID redirection has been attempted and failed, the call redirection system
attempts DNA redirection on calls to destinations within the network. DNA
redirection tries to find another DNA in the network which has been defined as
a back-up for the called DNA.
A customer is allowed to specify a DNA to be backed up and a list of alternate
DNAs. The address to be backed up will be referred to as the primary address
and the alternate addresses will be referred to as the members of the redirection
list or secondary DNAs. A call redirection list is composed of a primary DNA
which is backed up by a number of secondary DNAs. A secondary DNA may
appear in more than one redirection list. If the call packet can not be delivered
to the primary destination, the associated list is searched sequentially from the
beginning. If one of the members of the redirection list accepts the call, it is
connected to that member. The DNA that accepted the call is returned in the
call accept packet. This allows the accounting system and the calling service
to identify to whom the call is connected. If the call can not be delivered to a
DNA, the next secondary in the list is tried. If none of the secondaries accepts
the call, the call is cleared. In this case, the clear cause will be the one supplied
by the last address tried.
The addresses in the redirection list do not have to be on the same node as each
other or that of the primary address.
An operator command may be used to add a member dynamically to the
redirection list. A member that has been added by command can also be
deleted by command.
Calls that are sent directly to a DNA that is a member of a redirection list will
not be redirected unless the member happens to be a Primary DNA of another
redirection list. Although a DNA may be a member of one redirection list and
a Primary DNA of another redirection list, a call can traverse through only one
redirection list.
When a call undergoes DNA redirection, the destination address digits are
replaced by the secondary address digits. If the originating DTE is an X.25
(1984) DTE, the call accept packet will contain the Called Line Modification
Notification (CLAMN) facility. If the back-up DTE is an X.25 (1984) DTE,
the incoming call packet sent to it by the network will contain the Call
Redirection Notification (CRN) facility.
241-1001-115 37.2S1
If a Call Redirection Server receives a failed dial-out call which has an

Alternate Path Dial-Out list defined, the Call Redirection Server sends the call
(before searching for the next call redirection member) back to the Dial-Out
Routing Server (DORS) for alternate path dialing. This is achieved by
replacing the destination address digits with the dial-out address digits found
in the Dial Command Utility in the call block. If the primary DORS is down,
the call will be sent to the backup DORS for alternate path dialing.
If no connection can be established by the Alternate Path Dial-Out members,
or if both primary and backup DORS are down, the call will be sent to the next
call redirection member in the Call Redirection list.
Figure 3 and Figure 4 illustrate the flow of a call through DNA redirection.
Figure 5 illustrates the flow of DNA redirection with the alternate path defined.
Use and handling of RID 0
The use and handling of RID 0 is covered below:
1
On-Switch
Note: The use of RID 0 for Call Redirection is restricted to networks where
all of the Call Redirection Servers are on RMs, and/or AMs connected to
RMs.
When a member with RID 0 is specified, the Call Redirection Server sends the
call packet to the Source Call Router (SCR) for routing. If a non-zero RID is
entered, the packet is sent directly to the Destination Call Router (DCR) for
routing directly to the indicated RID.
37.2S1
24 Chapter 1
Figure 3
DNA redirection - RM
CALL REDIRECTION
REMOTE SERVER
INTERFACE
RM1
CALL REDIRECTION
SERVER
AM2
AM1
DNA
REDIRECTION
LIST
2
SECONDARY
DNA
PRIMARY
DNA
Call routed to primary DNA and connection fails.
Failed call returned to RM Call Redirection Remote Service Interface.
Call routed through an SVC to the AM1 Call Redirection Server.
DNA redirection list is searched and secondary DNA selected.
Call is routed to the secondary DNA.
241-1001-115 37.2S1

Figure 4
DNA redirection - RM
CALL REDIRECTION
SERVER
CALL REDIRECTION
REMOTE SERVER
INTERFACE
1
RM1
DNA
REDIRECTION
LIST
RM2
5
6
AM1
AM2
2
SECONDARY
DNA
PRIMARY
DNA
Failed call returned to RM Call Redirection Remote Server Interface.
DNA redirection list is searched and secondary DNA selected.
Call is routed to the secondary DNA.
37.2S1
26 Chapter 1
Figure 5
Flow of DNA redirection with alternate path defined
CALL REDIRECTION
REMOTE SERVER
INTERFACE
RM1
3
7
10
ALTERNATE
PATH
DIALOUT
LISTS
AM2
AM3
5
AM1
DNA
REDIRECTION
LIST
ALTERNATE
PATH DIAL-OUT
MEMBER DNA
DIAL-OUT
DNA
DIAL-OUT
ROUTING
SERVER
CALL REDIRECTION
SERVER
PRIMARY
DNA
DNA redirection list is searched and secondary DNA selected (dial-out

address).
Call is routed to AM2 Dial-Out Routing Server and mapped to Dial-Out

port DNA and connection fails.
Failed call returned to RM.
241-1001-115 37.2S1
Call is routed through an SVC to the AM1 Call Redirection Server. This
time the Call Redirection Server determines that the call needs alternate
path dialing (based on the existence of Alternate Path Dial-Out list).
Call is routed to AM2 Dial-Out Routing Server, the Alternate Path DialOut list is searched and an Alternate Path Dial-Out member is selected.
10 Call is routed to the Alternate Path Dial-Out member.

Data network identification code (DNIC) redirection
If RID redirection has been attempted and failed, the Call Redirection System
will attempt DNIC redirection on calls to destinations outside the network.
Note that in the case of routing off-network calls, the gateway call routing
system (GCRS) supersedes the DNIC redirection system. The destination
DNA is translated into a routing ID (RID) for on-network calls or into a
network ID (NID) for off-network calls. If the address maps to a NID, which
can be either an adjacent NID (ANID) or a non-adjacent NID (NNID), the call
packet is forwarded for further handling to the GCRS system. The GCRS
system has the capability of allowing the user to specify two sets of routes
(ANIDs) per destination network in service data, via the Preside Multiservice
Data Manager system. The first set contains the primary routes (the possible
routes to which calls are normally routed). The second set contains the
secondary routes (used only as backup routes if the primary routes fail or
become unavailable). Refer to NTP 241-1001-181 DPN-100 X.75 Service
Specification and NTP 241-1001-313 DPN-100 X.75 Gateway Call Routing
System User Guide for further details on the gateway call routing system.
The call packet contains a DNIC which identifies the call as destined for
another network. Inside the DPN network the call is routed by SNRID which
identifies the gateway leading to that network. When DNIC redirection is
performed, the call redirection system tries to find another SNRID to which the
call can be routed. This may be another SNRID to the destination network or
a SNRID to a transit network which will route the call to the destination
network.
The customer can define a DNIC redirection list containing up to seven backup SNRIDs. If the DNIC redirection list contains the destination DNIC an
attempt is made to route the call to the first back-up SNRID. If the new gateway
is also not available, the next member of the same back-up list will be chosen.
This process is repeated until either the call is routed by means of the alternate
route or all members have been tried. In the latter case the call will be cleared.
37.2S1
28 Chapter 1
Unlike DNA redirection, which changes the destination address in the call
packet, DNIC redirection only changes the routing identified by the SNRID.
The destination address, composed of DNIC + DNA, is not affected, i.e.,none
of the destination digits are modified.
Figure 6 illustrates the flow of a call through DNIC redirection.
Note: The RPOA network mapping flags must be set to the following
values for the DNIC redirection to be attempted:
RPOA-Transit
Optional (default is NO)
RPOA-Forward
Disabled (default is NO)
RPOA-Priority
To-Directly-Connected-Network
(default is NO)
Figure 6
DNIC redirection
CALL REDIRECTION
REMOTE SERVER INTERFACE
ALTERNATE
GATEWAY
6
RM2
RM1
2
GATEWAY 1
AM1
DNIC
REDIRECTION
LIST
CALL REDIRECTION
SERVER
241-1001-115 37.2S1
Call routed to Gateway 1 and connection fails.
DNIC redirection list searched and alternate Gateway selected.
Call routed through RM1 to alternate Gateway on RM2.
37.2S1
30 Chapter 1
241-1001-115 37.2S1
31
Chapter 2
Components of the call redirection
system
This chapter provides a description of the system components. The
information in this chapter is ordered as follows:
Introduction
Call
Call redirection server on AM or RM
Initialization of SVCs
Interaction with other systems
Interaction with hunt groups
PVC back-up description
Limitations
redirection remote server interface
Introduction
The Call Redirection System has a unique component on each distinct piece of
hardware in a DPN network. On every RM, there is a Call Redirection Remote
Server Interface (CRD-RSI). On some AMs or RMs, or both, there are Call
Redirection Servers (CRServ). All of these components make up the Call
Redirection System (CRS).
Every RM must have CRD-RSI. However, a minimum of one CRServ is
required in the system. Usually, more CRServs are configured on a system; this
allows redundancy and maintains sufficient throughput. Nevertheless, not
every AM or RM requires a CRServ. The following sections examine these
components in greater detail.
Call redirection remote server interface

The Call Redirection Remote Server Interface (CRD-RSI) resides in the
ROUT386 image, runs on a processor element (PE). It must have service data
to do RID redirection and it must have service data for the long-term SVCs that
37.2S1
32 Chapter 2
link with the CRServs on one or more AMs and/or RMs. Every RM is required
to have a CRD-RSI. For redundancy and loadsharing, CRD-RSIs may be
defined on multiple Processor Elements in an RM. There may be an SVC
defined from one CRD-RSI to up to eight CRServs. Each CRD-RSI in an RM
will call the same group of CRServs.
Note: The AM CRServs and RM CRServs may have either an E.164 or
X.121 address if called from an RSI.
Call redirection server on an AM or RM

The CRServ resides on at least one AM or RM in the network. It has its own
software image and runs on an dedicated PE. This software has four
responsibilities:
accept SVC calls from CRD-RSI in network
perform DNIC redirection on X.75 gateway calls
perform DNA redirection on national calls
clear calls for which DNIC or DNA redirection cannot be performed
The server contains code which will accept SVC calls and set up the
appropriate virtual circuit processes to handle the communication. Currently,
each CRServ can maintain 127 connections between itself and the CRD-RSIs
in the network.
The server receives failed calls from the network through its SVCs in the form
of data packets. The data packets are converted back into call packets and the
appropriate redirection is performed from the AM or RM CRServ. The node
performing the call routing must have sufficient capacity to handle the routing
of redirected calls as well as its normal load.
241-1001-115 37.2S1
Components of the call redirection system 33
Similarly, for CRServs residing on RMs, and/or AMs connected to RMs, both
trunks/network links connecting the node/module performing call redirection,
must have sufficient capacity to handle the call redirection load as well as the
normal load of data traffic. The requirement for sufficient capacity can also
affect the call throughput of subscribers whose lines are connected on the same
AM or RM that contains the CRServ or to an AM homed to an RM which
contains the CRSserv.
DNIC redirection
The CRServ is also responsible for DNIC redirection. Service data must be
defined for a DNIC redirection list which associates a 4 digit DNIC with up to
7 alternate SNRIDs which support a connection to either the destination
network or a transit network which ultimately connects to the destination
network. A model of this table follows.
Figure 7
DNIC redirection list - call redirection server
Primary DNIC
Alternate SNRID #1
Alternate SNRID #2
Alternate SNRID #3
Direction
of
search
Alternate SNRID #4
Alternate SNRID #5
Alternate SNRID #6
Alternate SNRID #7
The search algorithm is a simple linear selection through this list with software
maintaining a count of how many times the call has been through DNIC
redirection. If the count reaches seven, or the redirection list has been
exhausted, then the call is cleared by CRServ. The clear cause given is that
which is specified by the attempt to connect with the last alternate destination
in the list.
37.2S1
34 Chapter 2
DNA Redirection
DNA redirection also requires a list of service data associating a primary DNA
with up to seven secondaries. Again, the search algorithm is a simple linear
selection through the list. However, DNA redirection has an additional feature.
Through an operator command, an operator may specify one additional
alternate DNA for each primary DNA. This additional member becomes the
first member selected when doing DNA redirection. A model of a DNA
redirection list is shown below (they are all X.121 members).
Note 1: The members may be either E.164, X.121, or a mixture of both.
Note 2: Call redirection list primary addresses and secondary addresses
may be of address types X.121 or E.164, except for X.32 (dialout)
addresses. In the case of X.32 addresses they are allowed as call redirection
list members but not as primary addresses.
Figure 8
DNA redirection list
Primary DNIC+DNA
Dynamic Alternate DNIC+DNA
Dynamic RID
Secondary #1 DNIC+DNA
Sec. #1 RID
Sec. #2 RID
Sec. #3 RID
Sec. #4 RID
Sec. #5 RID
Sec. #6 RID
Sec. #7 RID
In searching through this redirection list, DNA redirection replaces the

destination DNA with the secondary DNA in the call packet. While this is
done, any subaddress digits from the original call are preserved (for X.121
addresses only). The primary and secondary addresses should be of the same
length if they are both X.121 addresses.
It is important to note that the dynamic specification shown in the first line of
the DNA redirection list only applies to the specific CRServ in which the
command is applied. In order for the dynamic DNA to appear in the selection
process of each CRServ, the operator must enter the command on all CRServs
in the network. This is required because CRServs have no knowledge of each
other. Therefore, consistency of redirection lists is an operators responsibility.
241-1001-115 37.2S1
Initialization of SVCs
When the CRD-RSI initializes it must check service data in order to determine
where the CRServs reside. The required envelope is the CRDACC DNA/LIST
envelope.This envelope contains the DNAs of the CRServs on AMs or RMs,
or both, that are to be called in order to establish the system. Refer to Figure 9.
For each of the DNAs in the envelope, the following is initiated by each Call
Redirection Remote Server Interface:
1
Prepare the call attempt to that DNA; send to routing.
Wait for the call accept.
If the call is accepted, add to available SVC table.

OR
If the call is cleared, generate an alarm indicating why the call was
rejected. This is provided only if the cause is different from the previous
clear cause.
This process repeats every 30 seconds until the call is accepted. This may
continue indefinitely if the call is continually cleared.
SVC setup on an RM
Each CRD-RSI in an RM loadshares among all of its available SVCs. There is
no concept of hot standby on an RM. Refer to Figure 9.
37.2S1
36 Chapter 2
Figure 9
SVC initialization
CR2
CR3
AM
AM
CR1
AM
CR4
RM
RM
DNA OF CR1
DNA OF CR4
DNA OF CR3
DNA OF CR2
CRD ACC
DNA/LIST
ENVELOPE
241-1001-115 37.2S1
Interaction with other systems

Some of the redirection systems interact with each other; for instance, a DNA
redirected call may end up being RID redirected to get to a secondary member.
Similarly, RID and DNIC redirection may interact. The DNIC and DNA backup will never interact on the same network; however, it could happen that a call
is DNIC redirected on network A and then DNA redirected on network B. Call
redirection does not work over X.75.
Interaction with hunt groups

Whenever a non-hunted call fails, it is sent to the nearest CRD-RSI, at which
point RID redirection is tried. If this fails, or has already been attempted, the
call usually goes to a CRServ through an SVC.
Hunted calls are different in three ways:
If a hunted call fails at a hunt group member, the call will be returned back
to the hunt group.
Hunt group DNAs may be backed up. DNA redirection will only be
invoked when all hunt group members have been attempted with no
success.
Individual member DNAs of a hunt group may be DNA redirected only if

called directly without going through the hunt group.
PVC back-up description

Each PVC has a primary slave end which is called by the master end to
establish the PVC. If the slave end cannot accept the PVC connection, the PVC
call is redirected to the DPN Call Redirection System. If the slave end of the
PVC is a primary DNA of a DNA redirection list, the call is redirected to the
secondary DNAs. Refer to Figure 10. Each member of the redirection list must
have a PVC envelope identical to the one defined for the primary slave end,
except for the slave end DNA. The local LCN for the primary for the primary
slave and the secondary slaves must be identical. For a description of the
addressing scheme used during call redirection, refer to DNA Redirection
on page 34.
There are two methods to re-establish the PVC to the primary slave end of the
PVC once the PVC has been set up with a secondary slave end.
The first method provides an automatic reconnection when the primary slave
becomes available. This method is selected by means of the service data
setting the Slave Send Call Packet to TRUE. Note that only the primary slave
end of a PVC can have this option set.
37.2S1
38 Chapter 2
When the primary slave end of a PVC that subscribes to this option comes up,
a call packet is sent to the master end of the PVC. The master then disconnects
the current PVC if one is established and reconnects with the primary slave end
of the PVC. Refer to Figure 11.
The second method of re-establishing the PVC to the primary slave end of the
PVC is by disabling the currently established PVC to the secondary slave end
of the PVC. The X.25 service supports an operator command that stops the
PVC currently established to the secondary slave end of the PVC and reestablishes the PVC to the primary slave end of the PVC. This command is
issued on the master end or the slave end.
Figure 10
PVC backup
Call fails between master (M) and primary (P) ends of PVC
Call is DNA redirected to secondary (S) slave end of PVC
PVC connected between master and secondary slave ends of PVC
241-1001-115 37.2S1

Figure 11
Reconnecting primary slave end of a PVC
1
P
2
M
1. Primary slave end (P) becomes available

2. Call packet sent to notify master end (M)
3. Master end disconnects PVC from secondary end (S)

4. Master end reconnects PVC with primary end
Limitations
The following is a list of limitations in the system:
Maximum of 127 SVCs from CRD-RSIs per CRServ.
Maximum of eight SVCs to CRServs per RM defined in service data.
Maximum seven static members per DNA/DNIC redirection list.
RID redirection can have only one alternate RID.
Each CRServ requires a PE.
CRServs cannot exist on a cascaded AM.
37.2S1
40 Chapter 2
Dynamic Redirection DNAs must be entered on each CRServ to maintain

network consistency.
Maximum of one Call Redirection Server per AM or RM.
Primary addresses can be of address type X.121 or E.164 except for E.164
dialout (X.32) addresses.
Call redirection list numbers can be of address type X.121 or E.164

including dialout (X.32) addresses.
241-1001-115 37.2S1
41
Chapter 3
Operations
This chapter provides an outline of the Operations, Administration, and
Maintenance aspects of the system. The information in this chapter is ordered
as follows:
Introduction
Call redirection system operator commands
Call redirection system service data
Alarms
Accounting
Statistics
Call redirection system reports
Introduction
The Call Redirection Operation, Administration and Maintenance (OAM)
System provides an integrated set of facilities managing the Call Redirection
System. The Call Redirection OAM System provides three management
capabilities:
Operation for status monitoring and control.
Administration for service assignment, configuration and data collection.
Maintenance for fault diagnosis, isolation and service restoration.
The OAM system is supported by the following:
operator commands
service data
system reports
alarms
37.2S1
42 Chapter 3
accounting
statistical data
Call redirection system operator commands

Operator commands are provided for use on the Access Module (AM) and
Resource Module (RM).
DPN AM/RM operator commands
There are a number of operator commands that are specific to the DPN AM/
RM Call Redirection Server. These commands can be issued from a DPN NCS
terminal or the AM/RM Local Operator. The following types of operator
commands can be issued:
querying of envelopes
displaying contents of DNA redirection file
displaying of dynamic DNA redirection information
displaying call information
displaying statistics
setting statistic flags
allowing or disallowing dynamic redirection assignment
initializing the Call Redirection Server
DPN RM operator commands

There are a number of operator commands that are specific to the DPN RM
Call Redirection Remote Server Interface. The operator commands can be
issued for the following:
querying of envelopes
displaying lists of Remote Server Interfaces
displaying statistics
setting statistic flags
displaying call information
A complete list of the supported commands and their capabilities is provided

in NTP 241-1001-303 Operator Commands and Responses.
Call redirection system service data

The service data required by the Call Redirection System is explained in
further detail, below.
241-1001-115 37.2S1
Operations 43
DPN AM/RM redirection service data

The processing of service data at the Call Redirection Server is consistent with
that on the DPN AM/RM system. That is, the redirection envelopes are
received from the provisioning system and are stored on the DPN AM/RM
disk.
Only a single view of Redirection Server service data is provided within each
Master Configuration File (MCF).
Note that DNA or DNIC can be changed dynamically by activating a new
MCF. This procedure does not take the server out of service. However, if the
server DNA/CUG envelope is changed, then the server is taken out of service
while it reinitializes with the new service data.
DPN AM/RM CRserv service data envelopes
Three types of service data envelopes are required by the DPN AM/RM
Redirection Server.
1
Process-type Envelope: This envelope defines the global number of the

redirection server process to be created.
DNA/CUG Envelope: This envelope defines the parameters necessary for

receiving calls at the Redirection Server from the DPN-RM CRD-RSI. It
is consistent with the general description of the envelope in the DPN AM/
RM system. See NTP 241-2001-340 Envelope Definitions.
DNIC Redirection List Envelope: This envelope defines all the DNIC
redirection information. It defines each primary DNIC with all its
secondary SNRID members. See NTP 241-2001-340 Envelope
Definitions.
Copies of the three envelopes are delivered separately to each Call Redirection
Server. With the exception of the DNA in the DNA/CUG envelope, all copies
of the envelopes normally contain the same information.
DNA redirection list file
This is a file which defines all the fixed DNA redirection lists given as primary
DNA with all its secondary members. See NTP 241-2001-340 Envelope
Definitions.
Each DNA is stored in full international format. The provisioning system also
provides a Call Redirection Manager (REDMAN) SDA envelope specifying
whether the name of the DNA is in the Redirection List File. See NTP
241-2001-340 Envelope Definitions.
37.2S1
44 Chapter 3
Criticality of service data

It is possible to change some Call Redirection service data without adversely
affecting Call Redirection service. A new MCF must be activated on the AM
or RM that contains the Call Redirection Server. This new MCF will differ
from the currently active MCF in only the DNIC Redirection Envelope, the
DNA Redirection List File, or both.
If this is the case, the Call Redirection Server will take the new data and
process it into its database. The old data will be replaced by the new without
interrupting the Call Redirection Service.
Activation of a modified DNA/CUG envelope will cause all SVCs to be
cleared and reconnected, causing a brief outage.
DPN RM CRD-RSI service data
The processing of service data for the RM Call Redirection Remote Server
Interface (CRD-RSI).
At the Office level, service data is required to define
the RID redirection list for the CRD-RSI
the DNA/CUGs for the CRD-RSI
the DNA/LIST information used by the CRD-RSI to call the Call

Redirection Servers elsewhere in the network.
See NTP 241-2001-340 Envelope Definitions for a description of these

envelopes.
The Office level service data resides in separate files so that it is not necessary
to load it into the PEs other than the Office PE and Server PE. The data is kept
at the Office level so that all RSIs are guaranteed to receive the same data.
At the PE level, service data is required to cause the creation of Remote Server
Interfaces (RSI) for the Call Redirection System.
Alarms
There are a number of alarms generated by the AM/RM Redirection Server,
RM Call Redirection Server Interface. See NTP 241-1001-506 Alarm Console
Indications for a detailed description of the specific alarms.
241-1001-115 37.2S1
Operations 45
Accounting
The internal SVCs for the Call Redirection System do not generate any
accounting information.
Statistics
The AM/RM CRServ collects statistical information about its current
operational condition. A statistic record is forwarded to the DPN-NCS data
spooling site if the STATSPOOL flag is enabled by the operator. The default
setting of the flag is specified in the AM/RM DNA/CUG envelope. On every
statistics probe received by the AM/RM CRServ, a statistics record is
generated. The PE utilization value of the server PE is also required.
37.2S1
46 Chapter 3
241-1001-115 37.2S1
47
Chapter 4
Provisioning the servers
This chapter discusses the provisioning requirements for two servers: Access
to Call Redirection (ACRD) and Call Redirection (CRS). Step-by-step
procedures are provided which explain how to provision the servers using the
DPN Architect provisioning applications. The information in this chapter is
ordered as follows:
Related documents for DPN Architect provisioning
Provisioning Access to Call Redirection

Before you begin
Service data entry fields
Steps to follow when provisioning ACRD
Provisioning Call Redirection

Before you begin
Steps to follow when provisioning CRS
37.2S1
48 Chapter 4
Related documents
This section lists other documents that you may refer to for more information
on provisioning.
The provisioning of the Call Redirection server (CRS) and the Access to Call
Redirection server (ACRD) is performed using the DPN Architect
applications. For more details, please refer to the following documents:
NTP 241-6001-012 Preside MDM Architect for DPN User Guide
NTP 241-6001-304 Preside MDM Architect Administrator Guide
NTP 241-2001-340 Envelope Definitions
NTP 241-1001-119 DPN Closed User Group Description and User Guide
NTP 241-1001-109 AM and RM Provisioning User Guide
Provisioning Access to Call Redirection

This section describes the steps involved in provisioning Access to Call
Redirection.
Before you begin
Review this section before you perform the actual provisioning for the server.
Specifically, this section discusses the following:
prerequisites: what has to be done before you begin provisioning;
service data hierarchy: how the service data should be configured; and
impacts of changes to envelopes.
Prerequisites
There must be a PE under this resource module (RM) that has a Simple_Server
component defined with the Access to call redirection server option checked.
It is recommended that there be at least two PEs with this option on each RM.
Service data hierarchy
This section shows the hierarchy of components for the Access to Call
Redirection server (ACRD). See Table 1, Hierarchy: Access to Call
Redirection components.
Table 1
Hierarchy: Access to Call Redirection components
Component
Key
Mandatory/
Optional
Access_To_Call_Redirection
None
M (Max 1) *
Rid_Redirection
None
M (Max 1)
(Sheet 1 of 2)
241-1001-115 37.2S1
Provisioning the servers 49

Table 1 (continued)
Hierarchy: Access to Call Redirection components
Component
Key
Mandatory/
Optional
DNA_CUG
DNA
M (Max 1)
NCUG_Index/1
Cug Index = 1
M (Max 1)
Direct_Call_List
None
M (Max 1)
NCUGs
* = mandatory for
RM modules
only, not allowed
on AM modules.
(Sheet 2 of 2)
Impacts of changes to envelopes

This section discusses how service data updates affect envelopes in the Access
to Call Redirection server (ACRD).
The term critical change, when used below, refers to restart upon activation.
CRDACC RID Backup envelope An update to the DNA is considered a
critical change. Other changes to this envelope take effect upon new calls.
CRDACC DNA/List envelope All updates to this envelope are considered
critical changes.
CRDACC DNA/CUG envelope Changes to this envelope are considered
non-critical.
37.2S1
50 Chapter 4

The tables in this section list the components that must be provisioned along
with their associated data entry fields for the Access to Call Redirection server
(ACRD). Refer to the previous section called Service data hierarchy, for a
complete list of components that must exist for each service. If a default exists
for a field, Yes will appear under the heading Default available. The
default value is supplied as a suggested starting point for defining the service
data. It may be used, unless there are engineering or other reasons for using a
different value. For more details, please refer to NTP 241-2001-340 Envelope
Definitions and NTP 241-1001-119 DPN Closed User Group Description and
User Guide.
Table 2
ACRD service data fields
Component
Field
Default
available
Envelope
RID_Redirection
RIDn
Yes
RID Backup n = 1 to 126.
DNA_CUG
Outgoing call
Yes
DNA/CUG
CUG ID
No
DNA/CUG
Out CUG Calls
Yes
DNA/CUG
In CUG Calls
Yes
DNA/CUG
Privileged
Yes
DNA/CUG
Statspool
Yes
DNA/List
DNA list type
Yes
DNA/List
Server DNA n
No
DNA/List
Notes
default priority
NCUGs
NCUG_Index/n
Direct_Call_List
241-1001-115 37.2S1
See your Network

Administrator for an
appropriate CUG ID. Note: n
must be 1.
See your Network

Administrator for appropriate
Server DNAs; (n = 1 to 16).
Note: Up to 16 server DNA
fields may be used.
Steps to follow when provisioning Access to Call Redirection

The following procedure explains how to add the Access to Call Redirection
server (ACRD) on RMs using the DPN Architect provisioning application.
Please refer to NTP 241-6001-012 Preside MDM Architect for DPN User
Guide and NTP 241-6001-304 Preside MDM Architect Administrator Guide
for details on how to use the Architect application.
The term packet module (PM) is used synonymously with the terms access
module (AM) and resource module (RM); both of which are also referred to as
DPN-100 modules.
Note: Ensure that the PM (RM) is BOTH owned before performing the
following procedure.
Procedure 1
How to add Access to Call Redirection to an RM
1
Add a PE on the PM (RM) that is to contain the ACRD server. The PE_Loader
component is presented and must be completed. Ensure that the PE_Loader has
a load filename of ROUT386.<level> for HPPE or PE386 type PEs. A
PE_Servers component is added automatically.
Under the PE_Servers component, add a Simple_Server component. Select

the Access to call redirection server option.
Optionally, under the PE, add a PE_Mnemonic with service mnemonic

RMSERVER.
Under the PM, add the Access_to_Call_Redirection component. Enter the

DNA of the ACRD as the <key value>.
Complete the RID Redirection table. You may want to fill in this table later using
the GDM tool.
Complete the fields for the DNA_CUG component.
Complete the fields for the Direct_Call_List component.
Under the NCUGs component, add a CUG with an NCUG index of 1 as the
<key value>. Complete the fields for the NCUG_Index/1 component.
Procedure 2
How to add Access to Call Redirection to an existing RMSERVER PE
1
Edit the Simple_Server component under the RMSERVER PE. Select the Access
to Call Redirection server option in addition to the other options selected.
Continue from step 4 in Procedure 1.
37.2S1
52 Chapter 4
Provisioning Call Redirection

This section describes the steps involved in provisioning Call Redirection.
Before you begin
Review this section before you perform the actual provisioning for the server.
Specifically, this section discusses the following:
prerequisites: what has to be done before you begin provisioning;
service data hierarchy: how the service data should be configured; and
impacts of changes to envelopes.
Prerequisites
If the CRS is defined on an AM, the office image must support servers.
Service data hierarchy
This section shows the hierarchy of components for the Call Redirection
server (CRS). There are two methods for provisioning this component.
Using the Call_Redirection_Server component: In this method, one PE is

used to run the Call_Redirection_Server. See Table 3,
Hierarchy: Call Redirection Server components.
Using the PE_Combination_Server component: Using this method, you

can combine other servers on the same PE. The following servers can be
combined: NDI_Server, Hunt_Group_List_Server,
Dial_Out_Routing_Server, and Call_Redirection_Server. See Table 4,
Hierarchy: Call_Redirection_Server using the PE_Combination_Server.
Refer to NTP 241-1001-117 DPN AM/RM Hunt Group Server User Guide
and NTP 241-1001-112 Off-Network NUI Validation System User Guide
for details on how to provision the Hunt_Group_List_Server and the
NDI_Server components.
Table 3
Hierarchy: Call Redirection server components
Component
Key
PE/n
PE number
Mandatory/
Optional
PE_Loader
M (Max 1)
PE_Mnemonic
PE_Servers
Call_Redirection_Server
DNA_CUG
(Sheet 1 of 2)
241-1001-115 37.2S1
DNA

Table 3 (continued)
Hierarchy: Call Redirection server components
Component
Key
NCUGs
Mandatory/
Optional
M
NCUG_Index/1
CUG index = 1
M (Max 1)
DNIC_Redirection
DNICs
DNIC/n
DNIC
O (Max 100)
(Sheet 2 of 2)
Table 4
Hierarchy: Call_Redirection_Server using the PE_Combination_Server
Component
Key
Mandatory/
Optional
PE_Combination_Server/n
PE number
PE_Loader
PE_Mnemonic
PE_Servers
Call_Redirection_Server
DNA_CUG
DNA
NCUGs
M
M
NCUG_Index/1
CUG index = 1
M (Max =1)
DNIC_Redirection
DNICs
DNIC/n
DNIC
O (Max =100)
Component
Key
Mandatory/
Optional
Call_Redirection_List
None
O (SDA external)
Table 5
Hierarchy: Call Redirection list components
Call_Redirection_DNAs
(Sheet 1 of 2)
37.2S1
54 Chapter 4
Table 5 (continued)
Hierarchy: Call Redirection list components
Component
Key
Primary_Dnas
Mandatory/
Optional
(maximum 1000)
Primary/X302112345
DNA
Primary/X302154321
DNA
(Sheet 2 of 2)
Impacts of changes to envelopes

This section discusses how service data updates affect envelopes in the Call
Redirection server (CRS).
The term critical change, when used below, refers to restart upon activation.
DPN-AM Call Redirection server DNA/CUG envelope Updates to this
envelope are considered critical changes.
DPN-AM DNA Redirection list file An update to the DNA is considered a
critical change. Other changes to this envelope take effect upon new calls.
DPN-AM DNIC Redirection envelope The changes to this envelope are
considered critical.
The tables in this section list the components that must be provisioned along
with their associated data entry fields for the Call Redirection server (CRS).
Refer to the previous section called Service data hierarchy, for a complete
list of components that must exist for each service. If a default exists for a field,
Yes will appear under the heading Default available. The default value is
supplied as a suggested starting point for defining the service data. It may be
used, unless there are engineering or other reasons for using a different value.
For more details, please refer to NTP 241-2001-340 Envelope Definitions and
NTP 241-1001-119 DPN Closed User Group Description and User Guide.
241-1001-115 37.2S1

Table 6
Call_Redirection server data fields
Default
available
Component
Field
PE_Mnemonic
service mnemonic No
Envelope
Notes
See your Network
appropriate service mnemonic.
Call_Redirection_Serv
er
DNA_CUG
On_line
Yes
DNA/CUG
Statspool
Yes
CUG ID
No
Out CUG Calls
Yes
In CUG Calls
Yes
Privileged
Yes
DNIC/n
SNRID/n
No
DNIC
Redirection
PE_Loader
Percent heap
Yes
PE_Loader
Processor type
Yes
MUX DMA
Yes
Load file name
No
Loader
Percent heap
Yes
Processor type
No
MUX DNA
Yes
NCUG_Index/n
See your Network

appropriate CUG ID. NOTE: n
must be 1.
See your Network

Administrator for appropriate
SNRIDs. NOTE: Up to 7 fields
can be used.
See System Administrator for

appropriate processor type.
See System Administrator for

appropriate file name.
37.2S1
56 Chapter 4
Table 7
Call_Redirection list data fields
Component
Field
Default
Available
Member DNA/n
No
Envelope
Notes
DNARED
file
See your Network

appropriate Member DNA
number.
Primary_Dnas
Primary/X302112
Steps to follow when provisioning Call Redirection

The following procedure explains how to add the Call Redirection server
(CRS) using DPN Architect. Please refer to NTP 241-6001-012 Preside MDM
Architect for DPN User Guide and NTP 241-6001-304 Preside MDM
Architect Administrator Guide for details on how to use the Architect
application.
The term packet module (PM) is used synonymously with the terms access
module (AM) and resource module (RM); both of which are also referred to as
DPN-100 modules.
241-1001-115 37.2S1

Procedure 3
How to add the Call Redirection server
1
Add a PE on the PM (AM or RM) that is to contain the CRS server. The
PE_Loader component is presented and must be completed. Ensure that the
PE_Loader has a load filename of CSERV386.<level> for HPPE or PE386.
Under the PE, add PE_Mnemonic with service mnemonic REDSERV.
Under the PE_Servers component, add a Call_Redirection_Server

component. Enter the DNA of the CRS as the <key value>.
Complete the fields for the DNA_CUG component.
Under the NCUGs component, add a CUG with an NCUG index of 1 as the <key
value>. The CUG ID must match the CUG ID of the ACRD server.
Optionally, under the Call_Redirection_Server, add a DNIC_Redirection

component.
Enter the first DNIC as the <key value>. Complete the fields for the DNIC
component.
Optionally, add more DNIC components under the DNICs component. Enter the
DNIC as the <key value>, and complete the fields.
Under the PM (AM or RM), add a Call_Redirection_list component and

enter the first primary DNA as the <key value>. Complete the fields for the
Primary component.
10 Optionally, add more Primary components under the Primary_DNAs component.

Procedure 4
How to add the Call_Redirection_Server using the PE_Combination_Server
component
Note: Ensure that another PE does not exist with the same PE number as the
PE_Combination_Server. This PE can also be used to provision the
Hunt_Group_Server and/or the NDI_Server components.
1
Add a PE_Combination_Server under the PM (AM or RM) that is to contain

the Call_Redirection_Server. Enter the PE number as the <key value>.
The PE_Loader component is presented and must be completed. Ensure that
the PE_Loader has the Processor type set to HPPE or PE386, and the
Load file name is CSERV386.<level>.
Optionally, under PE_Combination_Server, add PE_Mnemonic with service

mnemonic CSERV.
Complete the fields for the PE_Mnemonic component.
Under the PE_Combination_Server, add a PE_Servers component.
The remaining components are provisioned as described in Procedure 3, How to

add the Call Redirection server. Refer to steps 3 through 10.
37.2S1
58 Chapter 4
241-1001-115 37.2S1
59
Index
A
Access to Call Redirection
impacts of changes to envelopes 49
prerequisites 48
provisioning 48
service data entry fields 50
service data hierarchy 48
Accounting 45
B
Benefits of call redirection 17
C
Call Redirection 52
prerequisites 52
service data entry fields 54
service data hierarchy 52
Call redirection remote server interface 31
Call redirection server on an AM or RM 32
Call redirection system operator
commands 42
Call redirection system service data 42
Criticality of service data 44
D
Data network identification code (DNIC)
redirection 27
DNA redirection 22, 34
DNA redirection list file 43
DNIC redirection 33
DPN AM/RM operator commands 42
DPN AM/RM redirection service data 43
DPN RM CRD-RSI service data 44

DPN-AM CRserv service data envelopes 43
H
How call redirection works 18
I
Initialization of SVCs 35
Interaction with hunt groups 37
Interactions with other systems 37
Introduction 41
L
Limitations 39
O
Operations 41
P
Provisioning
Access to Call Redirection 48
Call Redirection 52
impacts of changes to envelopes 49, 54
prerequisites 48, 52
service data entry fields 50, 54
service data hierarchy 48, 52
PVC back-up description 37
R
Routing identifier (RID) redirection 19
37.2S1
60 Index
S
Statistics 45
SVC setup on an RM 35
U
Use and handling of RID 0 23
W
When call redirection is required 17
Why call redirection is required 17
241-1001-115 37.2S1
DPN-100

User Guide
Copyright 1986 - 2001 Nortel Networks
All Rights Reserved.
NORTEL, NORTEL NETWORKS, the globemark design, the NORTEL
NETWORKS corporate logo, DPN, and PASSPORT are trademarks of Nortel
Networks.
Publication: 241-1001-115
Document status: Standard
Document version: 37.2S1
Document date: February 2001
Printed in Canada

DPN Call Redirection System User Guide

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

DPN Call Redirection System User Guide

Transféré par

Droits d'auteur :

Formats disponibles

DPN-100

DPN Call Redirection System

DPN Call Redirection System

Copyright 1986 - 2001 Nortel Networks.

List of revised pages

DPN-100 DPN Call Redirection System User Guide

6 List of revised pages

DPN-100 DPN Call Redirection System User Guide

Who should read this document 15

Why call redirection is required 17

DPN-100 DPN Call Redirection System User Guide

RM RID redirection - RID failure 20

DPN-100 DPN Call Redirection System User Guide

Hierarchy: Access to Call Redirection components 48

How to add Access to Call Redirection to an RM 51

DPN-100 DPN Call Redirection System User Guide

About this document

Who should read this document

What you should know

How this document is organized

Chapter 1, Introduction to call redirection provides an introduction to

Chapter 2, Components of the call redirection system provides a

Chapter 3, Operations provides an outline of the Operations,

Chapter 4, Provisioning the servers explains how to provision both the

DPN-100 DPN Call Redirection System User Guide

16 About this document

bold text in courier font that appears in a procedure represents

Italics: words that appear in italics in a procedure explain the results of a

NTP 241-1001-110, DPN Routing System General Description

NTP 241-1001-153 DPN System Engineering Guidelines

NTP 241-1001-183 Addressing Plan

NTP 241-1001-303 Operator Commands and Responses

NTP 241-2001-340 Envelope Definitions

Other relevant documents are as follows:

NTP 241-1001-506 Alarm Console Indications

NTP 241-1001-509 Call Clear, Reset and Diagnostic Codes

NTP 241-1001-117 DPN AM/RM Hunt Group Server User Guide

Why call redirection is required

When call redirection is required

How call redirection works

Why call redirection is required

Benefits of call redirection

isolated change management

enhanced administration capabilities

When call redirection is required

DPN-100 DPN Call Redirection System User Guide

customer data terminal equipment (DTE)

customer connections to the switch

How call redirection works

Routing Identifier (RID) Redirection, for routing around switch or network

Data Network Address (DNA) Redirection, for routing calls to alternate

Data Network Identification Code (DNIC) Redirection for routing to other

RID redirection will always be attempted first. If it fails, DNA redirection or

a Call Redirection Remote Server Interface on each RM in the network;

a Call Redirection Server on selected AMs or RMs in the network.

Introduction to call redirection 19

These components are described in more detail in the section called

the back-up RID is not defined;

there is no route to the back-up RID; or

there is no route from the back-up RID to the called destination.

Either end of an established call that is experiencing communication problems

Incoming call to RM1.

Call routed to AM1 but primary RID (RM3) is not available.

Call returned to RM1 Call Redirection Remote Server Interface.