dpn call redirection system user guide

DPN-100

DPN Call Redirection SystemUser Guide

241-1001-115

DPN-100


Publication: 241-1001-115Document status: StandardDocument version: 37.2S1Document 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

5

DPN-100 DPN Call Redirection System User Guide 37.2S1

List of revised pagesThe following is a list of documentation revisions for service requests (SR) orrelease 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.

6 List of revised pages

241-1001-115 37.2S1

7


Publication historyFebruary 2001

37.2S1 StandardCommercial availability

8 Publication history

241-1001-115 37.2S1

9


Contents

About this document 15Who should read this document 15What you should know 15How this document is organized 15Typographic conventions 15Related documents 16

Chapter 1Introduction to call redirection 17Why call redirection is required 17Benefits of call redirection 17When call redirection is required 17

Internal failures 18External failures 18Other failures 18

How call redirection works 18Routing identifier (RID) redirection 19DNA redirection 22Data network identification code (DNIC) redirection 27

Chapter 2Components of the call redirection system 31Introduction 31Call redirection remote server interface 31Call redirection server on an AM or RM 32

DNIC redirection 33DNA Redirection 34

Initialization of SVCs 35SVC setup on an RM 35

Interaction with other systems 37Interaction with hunt groups 37PVC back-up description 37Limitations 39

10

241-1001-115 37.2S1

Chapter 3Operations 41Introduction 41Call redirection system operator commands 42

DPN AM/RM operator commands 42DPN RM operator commands 42

Call redirection system service data 42DPN AM/RM redirection service data 43DPN RM CRD-RSI service data 44

Alarms 44Accounting 45Statistics 45

Chapter 4Provisioning the servers 47Related documents 48Provisioning Access to Call Redirection 48

Before you begin 48Service data entry fields 50Steps to follow when provisioning Access to Call Redirection 51

Provisioning Call Redirection 52Before you begin 52Service data entry fields 54Steps to follow when provisioning Call Redirection 56

Index 59

Contents 11


List of figures

Figure 1 RM RID redirection - RID failure 20Figure 2 RM RID redirection - network link failure 21Figure 3 DNA redirection - RM 24Figure 4 DNA redirection - RM 25Figure 5 Flow of DNA redirection with alternate path defined 26Figure 6 DNIC redirection 28Figure 7 DNIC redirection list - call redirection server 33Figure 8 DNA redirection list 34Figure 9 SVC initialization 36Figure 10 PVC backup 38Figure 11 Reconnecting primary slave end of a PVC 39

12 Contents

241-1001-115 37.2S1

List of tables

Table 1 Hierarchy: Access to Call Redirection components 48Table 2 ACRD service data fields 50Table 3 Hierarchy: Call Redirection server components 52Table 4 Hierarchy: Call_Redirection_Server using the

PE_Combination_Server 53Table 5 Hierarchy: Call Redirection list components 53Table 6 Call_Redirection server data fields 55Table 7 Call_Redirection list data fields 56

Contents 13


List of procedures

Procedure 1 How to add Access to Call Redirection to an RM 51Procedure 2 How to add Access to Call Redirection to an existing RMSERVER

PE 51Procedure 3 How to add the Call Redirection server 57Procedure 4 How to add the Call_Redirection_Server using the

PE_Combination_Server component 57

14 Contents

241-1001-115 37.2S1

15


About this documentThis document provides the reader with an introduction to call redirection andan outline of how the DPN Call Redirection System works. Details on how toprovision the server are also provided.

Who should read this documentThis document was written for customers interested in obtaining the CallRedirection System (CRD) for a network. The document is also intended fornetwork operators who set up and modify the CRD on a switch.

What you should knowBefore you read this document you should have a basic understanding of theDPN network. Also, you should be familiar with the DPN Architectprovisioning applications.

How this document is organizedThis document is organized into four chapters:

• Chapter 1, “Introduction to call redirection” provides an introduction tothe Call Redirection (CRD) system and describes the flow of a call throughthe system.

• Chapter 2, “Components of the call redirection system” provides adescription 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 theAccess to Call Redirection (ACRD) server and the Call Redirection (CRD)server.

Typographic conventionsThe following conventions are used in this document:

Plain text in courier font: plain text in courier font that occurs inprocedures represents system generated text or text that appears on yourscreen.

16 About this document

241-1001-115 37.2S1

Bold text: bold text in courier font that appears in a procedure representswords that you should type or that you should select on the screen.

Italics: words that appear in italics in a procedure explain the results of aparticular step and appear immediately following that step. Words that appearin italic in paragraphs represent words that are special or that need to behighlighted.

[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 tobe replaced with specific numeric values.

UPPERCASE, lowercase: uppercase and lowercase letters that appear incommands and parameters must be matched exactly. The system matchesupper and lowercase characters differently unless otherwise stated.

Related documentsThe following publications are referred to in this document:

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

• NTP 241-1001-153DPN System Engineering Guidelines

• NTP 241-1001-183Addressing Plan

• NTP 241-1001-303Operator Commands and Responses

• NTP 241-2001-340Envelope Definitions

Other relevant documents are as follows:

• NTP 241-1001-506Alarm Console Indications

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

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

17


Chapter 1Introduction to call redirection

This chapter provides an introduction to the Call Redirection system anddescribes the flow of a call through the system. The information in this chapteris ordered as follows:

• Why call redirection is required

• When call redirection is required

• How call redirection works

Why call redirection is requiredCall Redirection is required in a network to route calls to alternate destinationsif the primary destination is not available. This allows subscribers to achievehigher reliability on data communication paths by providing one or moreredundant paths for call attempts.

Benefits of call redirectionThe DPN Call Redirection System provides the following benefits:

• high capacity

• high performance

• isolated change management

• enhanced administration capabilities

When call redirection is requiredThe Call Redirection System is invoked when a destination is not available dueto a failure. There are three types of failures: internal, external, and otherfailures.

To re-route a call that has been signalled on the link by the X.25 service, thehost must initiate the ITU X.25 Call Deflection feature using an X.25 facilitycode.

18 Chapter 1

241-1001-115 37.2S1

Internal failuresAn internal failure occurs in switch hardware when some internal componentfails. These failures could occur in:

• line cards

• processors

• shelves

• nodes

• network links

• trunks

External failuresExternal failures occur outside the switch. These failures could occur in

• customer data terminal equipment (DTE)

• customer connections to the switch

Other failuresCall routing failures may not always be due to a failed component or link. Oneexample is when the call options specified by the calling end are notcompatible with those supported by the called end. Another example is whenthe called end is busy (that is, no free channels for the incoming call).

How call redirection worksThree types of call redirection are performed:

• Routing Identifier (RID) Redirection, for routing around switch or networkfailures.

• Data Network Address (DNA) Redirection, for routing calls to alternatedestinations within the same network.

• Data Network Identification Code (DNIC) Redirection for routing to othernetworks.

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

In order to perform these redirection functions, the following entities arerequired 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.

Introduction to call redirection 19


These components are described in more detail in the section calledComponents of the Call Redirection System.

Routing identifier (RID) redirectionEach node in the network is identified by an RID. A called destination may beavailable through more than one RID, one of which is designated as theprimary RID and the other the back-up RID. If a call can not reach itsdestination through the primary RID then the Call Redirection System willattempt 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 linkfailure.

If the primary RID fails, calls will be routed to the destination AM through theback-up RID. Figure 1 illustrates the flow of a call through RID redirectioncaused by an RID failure.

If the network link between the primary RID and the destination AM fails, thecall will be routed to the destination AM through the back-up RID. Figure 2illustrates the flow of a call through RID redirection caused by a network linkfailure. The back-up RID, if defined, is found in the RID redirection list. Thislist is derived from the RID redirection envelope and is maintained on all nodesin the network. A single back-up RID may be defined for each RID in thenetwork.

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 problemssends a recovery packet to the other end to reestablish the communication onpossibly a different path. This feature is described in NTP 241-1001-110,DPNRouting System General Description under the name VC Recovery. When arecovery packet can not reach its destination, it is sent to a Call RedirectionRemote Server Interface on an RM where the destination RID is replaced by aback-up RID using RID Redirection.

The redirection of recovery packets is enhanced. Each end of a call isdynamically informed of the existence of an alternate RID through which theother end can be reached. When it sends a recovery packet, one end of a callincludes 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,

20 Chapter 1

241-1001-115 37.2S1

this alternate RID is directly used as the back-up RID. This enables the back-up RID to be dynamically chosen on a per call basis rather than quasi staticallyspecified, 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 ofa call.

Figure 1RM RID redirection - RID failure

1 Incoming call to RM1.

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

3 Call returned to RM1 Call Redirection Remote Server Interface.

RM2

RM3

RM1

1

2

3

4

5

AM1(DESTINATION)

RIDREDIRECTIONLIST

CALL REDIRECTIONREMOTE SERVER

INTERFACE



4 RID redirection list is searched and an alternate RID (RM2) selected.

5 Call routed through RM2 to original destination.

Figure 2RM RID redirection - network link failure


2 Call routed to AM1 but network link is not available.

3 Call returned to RM1 Call Redirection Remote Server Interface.

4 RID back-up list is searched and alternate RID selected.

5 Call routed through RM2 to original destination.

RM2RM1

1

2

35

4

RIDREDIRECTIONLIST


INTERFACE

AM1(DESTINATION)

22 Chapter 1

241-1001-115 37.2S1

DNA redirectionIf RID redirection has been attempted and failed, the call redirection systemattempts DNA redirection on calls to destinations within the network. DNAredirection tries to find another DNA in the network which has been defined asa back-up for the called DNA.

A customer is allowed to specify a DNA to be backed up and a list of alternateDNAs. The address to be backed up will be referred to as the primary addressand the alternate addresses will be referred to as the members of the redirectionlist or secondary DNAs. A call redirection list is composed of a primary DNAwhich is backed up by a number of secondary DNAs. A secondary DNA mayappear in more than one redirection list. If the call packet can not be deliveredto the primary destination, the associated list is searched sequentially from thebeginning. If one of the members of the redirection list accepts the call, it isconnected to that member. The DNA that accepted the call is returned in thecall accept packet. This allows the accounting system and the calling serviceto identify to whom the call is connected. If the call can not be delivered to aDNA, the next secondary in the list is tried. If none of the secondaries acceptsthe call, the call is cleared. In this case, the clear cause will be the one suppliedby the last address tried.

The addresses in the redirection list do not have to be on the same node as eachother or that of the primary address.

An operator command may be used to add a member dynamically to theredirection list. A member that has been added by command can also bedeleted by command.

Calls that are sent directly to a DNA that is a member of a redirection list willnot be redirected unless the member happens to be a Primary DNA of anotherredirection list. Although a DNA may be a member of one redirection list anda Primary DNA of another redirection list, a call can traverse through only oneredirection list.

When a call undergoes DNA redirection, the destination address digits arereplaced by the secondary address digits. If the originating DTE is an X.25(1984) DTE, the call accept packet will contain the Called Line ModificationNotification (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 CallRedirection Notification (CRN) facility.



If a Call Redirection Server receives a failed dial-out call which has anAlternate Path Dial-Out list defined, the Call Redirection Server sends the call(before searching for the next call redirection member) back to the Dial-OutRouting Server (DORS) for alternate path dialing. This is achieved byreplacing the destination address digits with the dial-out address digits foundin 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 nextcall 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 0The 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 whereall of the Call Redirection Servers are on RMs, and/or AMs connected toRMs.

When a member with RID 0 is specified, the Call Redirection Server sends thecall packet to the Source Call Router (SCR) for routing. If a non-zero RID isentered, the packet is sent directly to the Destination Call Router (DCR) forrouting directly to the indicated RID.

24 Chapter 1

241-1001-115 37.2S1

Figure 3DNA redirection - RM


2 Call routed to primary DNA and connection fails.

3 Failed call returned to RM Call Redirection Remote Service Interface.

4 Call routed through an SVC to the AM1 Call Redirection Server.

5 DNA redirection list is searched and secondary DNA selected.

6 Call is routed to the secondary DNA.

AM2 AM1

RM11

2

3 4

5

6

DNAREDIRECTIONLIST

CALL REDIRECTIONSERVER


INTERFACE

SECONDARYDNA

PRIMARYDNA



Figure 4DNA redirection - RM



3 Failed call returned to RM Call Redirection Remote Server Interface.


5 DNA redirection list is searched and secondary DNA selected.

6 Call is routed to the secondary DNA.

RM1 RM2

1

2

3

4

5

6

AM1AM2

DNAREDIRECTIONLIST

CALL REDIRECTIONSERVER CALL REDIRECTION

REMOTE SERVERINTERFACE

SECONDARYDNA

PRIMARYDNA

26 Chapter 1

241-1001-115 37.2S1

Figure 5Flow of DNA redirection with alternate path defined





5 DNA redirection list is searched and secondary DNA selected (dial-outaddress).

6 Call is routed to AM2 Dial-Out Routing Server and mapped to Dial-Outport DNA and connection fails.

7 Failed call returned to RM.

AM1AM2

AM3

1

2

34

5

6

97

108

CALL REDIRECTIONREMOTE SERVERINTERFACE

DNAREDIRECTIONLIST

PRIMARYDNA


DIAL-OUT

SERVERROUTINGDIAL-OUT

DNA

ALTERNATE

MEMBER DNAPATH DIAL-OUT

RM1

NATE

LISTS

PATH

OUT

ALTER-

DIAL-



8 Call is routed through an SVC to the AM1 Call Redirection Server. Thistime the Call Redirection Server determines that the call needs alternatepath dialing (based on the existence of Alternate Path Dial-Out list).

9 Call is routed to AM2 Dial-Out Routing Server, the Alternate Path Dial-Out 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) redirectionIf RID redirection has been attempted and failed, the Call Redirection Systemwill attempt DNIC redirection on calls to destinations outside the network.

Note that in the case of routing off-network calls, the gateway call routingsystem (GCRS) supersedes the DNIC redirection system. The destinationDNA is translated into a routing ID (RID) for on-network calls or into anetwork ID (NID) for off-network calls. If the address maps to a NID, whichcan be either an adjacent NID (ANID) or a non-adjacent NID (NNID), the callpacket is forwarded for further handling to the GCRS system. The GCRSsystem has the capability of allowing the user to specify two sets of routes(ANIDs) per destination network in service data, via the Preside MultiserviceData Manager system. The first set contains the primary routes (the possibleroutes to which calls are normally routed). The second set contains thesecondary routes (used only as backup routes if the primary routes fail orbecome unavailable). Refer to NTP 241-1001-181DPN-100 X.75 ServiceSpecification and NTP 241-1001-313DPN-100 X.75 Gateway Call RoutingSystem User Guide for further details on the gateway call routing system.

The call packet contains a DNIC which identifies the call as destined foranother network. Inside the DPN network the call is routed by SNRID whichidentifies the gateway leading to that network. When DNIC redirection isperformed, the call redirection system tries to find another SNRID to which thecall can be routed. This may be another SNRID to the destination network ora SNRID to a transit network which will route the call to the destinationnetwork.

The customer can define a DNIC redirection list containing up to seven back-up SNRIDs. If the DNIC redirection list contains the destination DNIC anattempt is made to route the call to the first back-up SNRID. If the new gatewayis 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 alternateroute or all members have been tried. In the latter case the call will be cleared.

28 Chapter 1

241-1001-115 37.2S1

Unlike DNA redirection, which changes the destination address in the callpacket, DNIC redirection only changes the routing identified by the SNRID.The destination address, composed of DNIC + DNA, is not affected, i.e.,noneof 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 followingvalues for the DNIC redirection to be attempted:

Figure 6DNIC redirection


RPOA-Transit = Optional (default is NO)

RPOA-Forward = Disabled (default is NO)

RPOA-Priority = To-Directly-Connected-Network(default is NO)

RM1 RM2

GATEWAY 1

1

2

34

5

6

CALL REDIRECTIONREMOTE SERVER INTERFACE


DNICREDIRECTIONLIST

ALTERNATEGATEWAY

AM1



2 Call routed to Gateway 1 and connection fails.



5 DNIC redirection list searched and alternate Gateway selected.

6 Call routed through RM1 to alternate Gateway on RM2.

30 Chapter 1

241-1001-115 37.2S1

31


Chapter 2Components of the call redirectionsystem

This chapter provides a description of the system components. Theinformation in this chapter is ordered as follows:

• Introduction

• Call redirection remote server interface

• Call redirection server on AM or RM

• Initialization of SVCs

• Interaction with other systems

• Interaction with hunt groups

• PVC back-up description

• Limitations

IntroductionThe Call Redirection System has a unique component on each distinct piece ofhardware in a DPN network. On every RM, there is a Call Redirection RemoteServer Interface (CRD-RSI). On some AMs or RMs, or both, there are CallRedirection Servers (CRServ). All of these components make up the CallRedirection System (CRS).

Every RM must have CRD-RSI. However, a minimum of one CRServ isrequired in the system. Usually, more CRServs are configured on a system; thisallows redundancy and maintains sufficient throughput. Nevertheless, notevery AM or RM requires a CRServ. The following sections examine thesecomponents in greater detail.

Call redirection remote server interfaceThe Call Redirection Remote Server Interface (CRD-RSI) resides in theROUT386 image, runs on a processor element (PE). It must have service datato do RID redirection and it must have service data for the long-term SVCs that

32 Chapter 2

241-1001-115 37.2S1

link with the CRServs on one or more AMs and/or RMs. Every RM is requiredto have a CRD-RSI. For redundancy and loadsharing, CRD-RSIs may bedefined on multiple Processor Elements in an RM. There may be an SVCdefined from one CRD-RSI to up to eight CRServs. Each CRD-RSI in an RMwill call the same group of CRServs.

Note:The AM CRServs and RM CRServs may have either an E.164 orX.121 address if called from an RSI.

Call redirection server on an AM or RMThe CRServ resides on at least one AM or RM in the network. It has its ownsoftware image and runs on an dedicated PE. This software has fourresponsibilities:

• 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 theappropriate virtual circuit processes to handle the communication. Currently,each CRServ can maintain 127 connections between itself and the CRD-RSIsin the network.

The server receives failed calls from the network through its SVCs in the formof data packets. The data packets are converted back into call packets and theappropriate redirection is performed from the AM or RM CRServ. The nodeperforming the call routing must have sufficient capacity to handle the routingof redirected calls as well as its normal load.

Components of the call redirection system 33


Similarly, for CRServs residing on RMs, and/or AMs connected to RMs, bothtrunks/network links connecting the node/module performing call redirection,must have sufficient capacity to handle the call redirection load as well as thenormal load of data traffic. The requirement for sufficient capacity can alsoaffect the call throughput of subscribers whose lines are connected on the sameAM or RM that contains the CRServ or to an AM homed to an RM whichcontains the CRSserv.

DNIC redirectionThe CRServ is also responsible for DNIC redirection. Service data must bedefined for a DNIC redirection list which associates a 4 digit DNIC with up to7 alternate SNRIDs which support a connection to either the destinationnetwork or a transit network which ultimately connects to the destinationnetwork. A model of this table follows.

Figure 7DNIC redirection list - call redirection server

The search algorithm is a simple linear selection through this list with softwaremaintaining a count of how many times the call has been through DNICredirection. If the count reaches seven, or the redirection list has beenexhausted, then the call is cleared by CRServ. The clear cause given is thatwhich is specified by the attempt to connect with the last alternate destinationin the list.

Primary DNIC

Directionofsearch

Alternate SNRID #1

Alternate SNRID #2

Alternate SNRID #3

Alternate SNRID #4

Alternate SNRID #5

Alternate SNRID #6

Alternate SNRID #7

34 Chapter 2

241-1001-115 37.2S1

DNA RedirectionDNA redirection also requires a list of service data associating a primary DNAwith up to seven secondaries. Again, the search algorithm is a simple linearselection through the list. However, DNA redirection has an additional feature.Through an operator command, an operator may specify one additionalalternate DNA for each primary DNA. This additional member becomes thefirst member selected when doing DNA redirection. A model of a DNAredirection 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 addressesmay be of address types X.121 or E.164, except for X.32 (dial–out)addresses. In the case of X.32 addresses they are allowed as call redirectionlist members but not as primary addresses.

Figure 8DNA redirection list

In searching through this redirection list, DNA redirection replaces thedestination DNA with the secondary DNA in the call packet. While this isdone, any sub–address digits from the original call are preserved (for X.121addresses only). The primary and secondary addresses should be of the samelength if they are both X.121 addresses.

It is important to note that the dynamic specification shown in the first line ofthe DNA redirection list only applies to the specific CRServ in which thecommand is applied. In order for the dynamic DNA to appear in the selectionprocess of each CRServ, the operator must enter the command on all CRServsin the network. This is required because CRServs have no knowledge of eachother. Therefore, consistency of redirection lists is an operator’s responsibility.

Primary DNIC+DNA Dynamic Alternate DNIC+DNA Dynamic RID

Secondary #1 DNIC+DNASecondary #2 DNIC+DNASecondary #3 DNIC+DNASecondary #4 DNIC+DNASecondary #5 DNIC+DNASecondary #6 DNIC+DNASecondary #7 DNIC+DNA

Sec. #1 RIDSec. #2 RIDSec. #3 RIDSec. #4 RIDSec. #5 RIDSec. #6 RIDSec. #7 RID



Initialization of SVCsWhen the CRD-RSI initializes it must check service data in order to determinewhere the CRServs reside. The required envelope is the CRDACC DNA/LISTenvelope.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 CallRedirection Remote Server Interface:

1 Prepare the call attempt to that DNA; send to routing.

2 Wait for the call accept.

3 If the call is accepted, add to available SVC table.

OR

4 If the call is cleared, generate an alarm indicating why the call wasrejected. This is provided only if the cause is different from the previousclear cause.

This process repeats every 30 seconds until the call is accepted. This maycontinue indefinitely if the call is continually cleared.

SVC setup on an RMEach CRD-RSI in an RM loadshares among all of its available SVCs. There isno concept of hot standby on an RM. Refer to Figure 9.

36 Chapter 2

241-1001-115 37.2S1

Figure 9SVC initialization

CR1

CR2 CR3

AM

AM AM

CR4

RM

RM

DNA OF CR1

DNA OF CR4

DNA OF CR3

DNA OF CR2

CRD ACCDNA/LIST

ENVELOPE



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

Interaction with hunt groupsWhenever a non-hunted call fails, it is sent to the nearest CRD-RSI, at whichpoint RID redirection is tried. If this fails, or has already been attempted, thecall 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 backto the hunt group.

• Hunt group DNAs may be backed up. DNA redirection will only beinvoked when all hunt group members have been attempted with nosuccess.

• Individual member DNAs of a hunt group may be DNA redirected only ifcalled directly without going through the hunt group.

PVC back-up descriptionEach PVC has a primary slave end which is called by the master end toestablish the PVC. If the slave end cannot accept the PVC connection, the PVCcall is redirected to the DPN Call Redirection System. If the slave end of thePVC is a primary DNA of a DNA redirection list, the call is redirected to thesecondary DNAs. Refer to Figure 10. Each member of the redirection list musthave 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 primaryslave and the secondary slaves must be identical. For a description of theaddressing 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 thePVC once the PVC has been set up with a secondary slave end.

The first method provides an automatic reconnection when the primary slavebecomes available. This method is selected by means of the service datasetting the Slave Send Call Packet to “TRUE”. Note that only the primary slaveend of a PVC can have this option set.

38 Chapter 2

241-1001-115 37.2S1

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 disconnectsthe current PVC if one is established and reconnects with the primary slave endof the PVC. Refer to Figure 11.

The second method of re-establishing the PVC to the primary slave end of thePVC is by disabling the currently established PVC to the secondary slave endof the PVC. The X.25 service supports an operator command that stops thePVC currently established to the secondary slave end of the PVC and re-establishes the PVC to the primary slave end of the PVC. This command isissued on the master end or the slave end.

Figure 10PVC backup

1 Call fails between master (M) and primary (P) ends of PVC

2 Call is DNA redirected to secondary (S) slave end of PVC

3 PVC connected between master and secondary slave ends of PVC

M

P

S3

1

2



Figure 11Reconnecting primary slave end of a PVC

LimitationsThe 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.

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

M

M

P

P

S

S

4

2

1

3

40 Chapter 2

241-1001-115 37.2S1

• Dynamic Redirection DNAs must be entered on each CRServ to maintainnetwork 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.164dial–out (X.32) addresses.

• Call redirection list numbers can be of address type X.121 or E.164including dial–out (X.32) addresses.

41


Chapter 3Operations

This chapter provides an outline of the Operations, Administration, andMaintenance aspects of the system. The information in this chapter is orderedas follows:

• Introduction

• Call redirection system operator commands

• Call redirection system service data

• Alarms

• Accounting

• Statistics

• Call redirection system reports

IntroductionThe Call Redirection Operation, Administration and Maintenance (OAM)System provides an integrated set of facilities managing the Call RedirectionSystem. The Call Redirection OAM System provides three managementcapabilities:

• 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

42 Chapter 3

241-1001-115 37.2S1

• accounting

• statistical data

Call redirection system operator commandsOperator commands are provided for use on the Access Module (AM) andResource Module (RM).

DPN AM/RM operator commandsThere 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 NCSterminal or the AM/RM Local Operator. The following types of operatorcommands 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 commandsThere are a number of operator commands that are specific to the DPN RMCall Redirection Remote Server Interface. The operator commands can beissued 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 providedin NTP 241-1001-303Operator Commands and Responses.

Call redirection system service dataThe service data required by the Call Redirection System is explained infurther detail, below.

Operations 43


DPN AM/RM redirection service dataThe processing of service data at the Call Redirection Server is consistent withthat on the DPN AM/RM system. That is, the redirection envelopes arereceived from the provisioning system and are stored on the DPN AM/RMdisk.

Only a single view of Redirection Server service data is provided within eachMaster Configuration File (MCF).

Note that DNA or DNIC can be changed dynamically by activating a newMCF. This procedure does not take the server out of service. However, if theserver DNA/CUG envelope is changed, then the server is taken out of servicewhile it re–initializes with the new service data.

DPN AM/RM CRserv service data envelopesThree types of service data envelopes are required by the DPN AM/RMRedirection Server.

1 Process-type Envelope: This envelope defines the global number of theredirection server process to be created.

2 DNA/CUG Envelope: This envelope defines the parameters necessary forreceiving calls at the Redirection Server from the DPN-RM CRD-RSI. Itis consistent with the general description of the envelope in the DPN AM/RM system. See NTP 241-2001-340Envelope Definitions.

3 DNIC Redirection List Envelope: This envelope defines all the DNICredirection information. It defines each primary DNIC with all itssecondary SNRID members. See NTP 241-2001-340EnvelopeDefinitions.

Copies of the three envelopes are delivered separately to each Call RedirectionServer. With the exception of the DNA in the DNA/CUG envelope, all copiesof the envelopes normally contain the same information.

DNA redirection list fileThis is a file which defines all the fixed DNA redirection lists given as primaryDNA with all its secondary members. See NTP 241-2001-340EnvelopeDefinitions.

Each DNA is stored in full international format. The provisioning system alsoprovides a Call Redirection Manager (REDMAN) SDA envelope specifyingwhether the name of the DNA is in the Redirection List File. See NTP241-2001-340Envelope Definitions.

44 Chapter 3

241-1001-115 37.2S1

Criticality of service dataIt is possible to change some Call Redirection service data without adverselyaffecting Call Redirection service. A new MCF must be activated on the AMor RM that contains the Call Redirection Server. This new MCF will differfrom the currently active MCF in only the DNIC Redirection Envelope, theDNA Redirection List File, or both.

If this is the case, the Call Redirection Server will take the new data andprocess it into its database. The old data will be replaced by the new withoutinterrupting the Call Redirection Service.

Activation of a modified DNA/CUG envelope will cause all SVCs to becleared and reconnected, causing a brief outage.

DPN RM CRD-RSI service dataThe processing of service data for the RM Call Redirection Remote ServerInterface (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 CallRedirection Servers elsewhere in the network.

See NTP 241-2001-340Envelope Definitions for a description of theseenvelopes.

The Office level service data resides in separate files so that it is not necessaryto load it into the PEs other than the Office PE and Server PE. The data is keptat 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 ServerInterfaces (RSI) for the Call Redirection System.

AlarmsThere are a number of alarms generated by the AM/RM Redirection Server,RM Call Redirection Server Interface. See NTP 241-1001-506Alarm ConsoleIndications for a detailed description of the specific alarms.

Operations 45


AccountingThe internal SVCs for the Call Redirection System do not generate anyaccounting information.

StatisticsThe AM/RM CRServ collects statistical information about its currentoperational condition. A statistic record is forwarded to the DPN-NCS dataspooling site if the STATSPOOL flag is enabled by the operator. The defaultsetting of the flag is specified in the AM/RM DNA/CUG envelope. On everystatistics probe received by the AM/RM CRServ, a statistics record isgenerated. The PE utilization value of the server PE is also required.

46 Chapter 3

241-1001-115 37.2S1

47


Chapter 4Provisioning the servers

This chapter discusses the provisioning requirements for two servers:Accessto Call Redirection (ACRD) andCall Redirection (CRS). Step-by-stepprocedures are provided which explain how to provision the servers using theDPN Architect provisioning applications. The information in this chapter isordered 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

— Service data entry fields

— Steps to follow when provisioning CRS

48 Chapter 4

241-1001-115 37.2S1

Related documentsThis section lists other documents that you may refer to for more informationon provisioning.

The provisioning of theCall Redirectionserver (CRS) and theAccess to CallRedirection server (ACRD) is performed using the DPN Architectapplications. For more details, please refer to the following documents:

• NTP 241-6001-012Preside MDM Architect for DPN User Guide

• NTP 241-6001-304Preside MDM Architect Administrator Guide

• NTP 241-2001-340Envelope Definitions

• NTP 241-1001-119DPN Closed User Group Description and User Guide

• NTP 241-1001-109AM and RM Provisioning User Guide

Provisioning Access to Call RedirectionThis section describes the steps involved in provisioning Access to CallRedirection.

Before you beginReview 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.

PrerequisitesThere must be a PE under this resource module (RM) that has a Simple_Servercomponent 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 hierarchyThis section shows the hierarchy of components for theAccess to CallRedirection server (ACRD). See Table 1,Hierarchy: Access to CallRedirection components.

Table 1Hierarchy: Access to Call Redirection components

Component KeyMandatory/Optional

Access_To_Call_Redirection None M (Max 1) *

Rid_Redirection None M (Max 1)

(Sheet 1 of 2)

Provisioning the servers 49


Impacts of changes to envelopesThis section discusses how service data updates affect envelopes in theAccessto Call Redirection server (ACRD).

The termcritical change, when used below, refers to restart upon activation.

CRDACC RID Backup envelope An update to the DNA is considered acritical change. Other changes to this envelope take effect upon new calls.

CRDACC DNA/List envelope All updates to this envelope are consideredcritical changes.

CRDACC DNA/CUG envelope Changes to this envelope are considerednon-critical.

DNA_CUG DNA M (Max 1)

NCUGs

NCUG_Index/1 Cug Index = 1 M (Max 1)

Direct_Call_List None M (Max 1)

* = mandatory forRM modulesonly, not allowedon AM modules.

Table 1 (continued)Hierarchy: Access to Call Redirection components


(Sheet 2 of 2)

50 Chapter 4

241-1001-115 37.2S1

Service data entry fieldsThe tables in this section list the components that must be provisioned alongwith their associated data entry fields for theAccess to Call Redirectionserver(ACRD). Refer to the previous section called “Service data hierarchy”, for acompletelist of components that must exist for each service. If a default existsfor a field, “Yes” will appear under the heading “Default available”. Thedefault value is supplied as a suggested starting point for defining the servicedata. It may be used, unless there are engineering or other reasons for using adifferent value. For more details, please refer to NTP241-2001-340EnvelopeDefinitionsand NTP 241-1001-119DPN Closed User Group Description andUser Guide.

Table 2ACRD service data fields

Component FieldDefaultavailable Envelope Notes

RID_Redirection RIDn Yes RID Backup n = 1 to 126.

DNA_CUG Outgoing call Yes DNA/CUG

default priority

NCUGs

NCUG_Index/n CUG ID No DNA/CUG See your NetworkAdministrator for anappropriate CUG ID. Note: nmust be 1.

Out CUG Calls Yes DNA/CUG

In CUG Calls Yes DNA/CUG

Privileged Yes DNA/CUG

Direct_Call_List Statspool Yes DNA/List

DNA list type Yes DNA/List

Server DNA n No DNA/List See your NetworkAdministrator for appropriateServer DNAs; (n = 1 to 16).Note: Up to 16 server DNAfields may be used.



Steps to follow when provisioning Access to Call RedirectionThe following procedure explains how to add theAccess to Call Redirectionserver (ACRD) on RMs using the DPN Architect provisioning application.Please refer to NTP 241-6001-012Preside MDM Architect for DPN UserGuide and NTP 241-6001-304Preside MDM Architect Administrator Guidefor details on how to use the Architect application.

The term packet module (PM) is used synonymously with the terms accessmodule (AM) and resource module (RM); both of which are also referred to asDPN-100 modules.

Note:Ensure that the PM (RM) is BOTH owned before performing thefollowing procedure.

Procedure 1How 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_Loadercomponent is presented and must be completed. Ensure that the PE_Loader hasa load filename of ROUT386.<level> for HPPE or PE386 type PEs. APE_Servers component is added automatically.

2 Under the PE_Servers component, add a Simple_Server component. Selectthe Access to call redirection server option.

3 Optionally, under the PE, add a PE_Mnemonic with service mnemonicRMSERVER.

4 Under the PM, add the Access_to_Call_Redirection component. Enter theDNA of the ACRD as the <key value> .

5 Complete the RID Redirection table. You may want to fill in this table later usingthe GDM tool.

6 Complete the fields for the DNA_CUG component.

7 Complete the fields for the Direct_Call_List component.

8 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 2How to add Access to Call Redirection to an existing RMSERVER PE

1 Edit the Simple_Server component under the RMSERVER PE. Select the Accessto Call Redirection server option in addition to the other options selected.

2 Continue from step 4 in Procedure 1.

52 Chapter 4

241-1001-115 37.2S1

Provisioning Call RedirectionThis section describes the steps involved in provisioning Call Redirection.

Before you beginReview 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.

PrerequisitesIf the CRS is defined on an AM, the office image must support servers.

Service data hierarchyThis section shows the hierarchy of components for theCall Redirectionserver (CRS). There are two methods for provisioning this component.

• Using the Call_Redirection_Server component: In this method, one PE isused to run the Call_Redirection_Server. See Table 3,Hierarchy: Call Redirection Server components.

• Using the PE_Combination_Server component: Using this method, youcan combine other servers on the same PE. The following servers can becombined: 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-117DPN AM/RM Hunt Group Server User Guideand NTP 241-1001-112Off-Network NUI Validation System User Guidefor details on how to provision the Hunt_Group_List_Server and theNDI_Server components.

Table 3Hierarchy: Call Redirection server components


PE/n PE number

PE_Loader M (Max 1)

PE_Mnemonic O

PE_Servers M

Call_Redirection_Server M

DNA_CUG DNA M

(Sheet 1 of 2)



NCUGs M

NCUG_Index/1 CUG index = 1 M (Max 1)

DNIC_Redirection O

DNICs M

DNIC/n DNIC O (Max 100)

Table 4Hierarchy: Call_Redirection_Server using the PE_Combination_Server


PE_Combination_Server/n PE number O

PE_Loader M

PE_Mnemonic O

PE_Servers M

Call_Redirection_Server O

DNA_CUG DNA M

NCUGs M

NCUG_Index/1 CUG index = 1 M (Max =1)

DNIC_Redirection O

DNICs M

DNIC/n DNIC O (Max =100)

Table 5Hierarchy: Call Redirection list components


Call_Redirection_List None O (SDA external)

Call_Redirection_DNAs

(Sheet 1 of 2)

Table 3 (continued)Hierarchy: Call Redirection server components


(Sheet 2 of 2)

54 Chapter 4

241-1001-115 37.2S1

Impacts of changes to envelopesThis section discusses how service data updates affect envelopes in theCallRedirection server (CRS).

The termcritical change, when used below, refers to restart upon activation.

DPN-AM Call Redirection server DNA/CUG envelope Updates to thisenvelope are considered critical changes.

DPN-AM DNA Redirection list file An update to the DNA is considered acritical change. Other changes to this envelope take effect upon new calls.

DPN-AM DNIC Redirection envelope The changes to this envelope areconsidered critical.

Service data entry fieldsThe tables in this section list the components that must be provisioned alongwith their associated data entry fields for theCall Redirection server (CRS).Refer to the previous section called “Service data hierarchy”, for acompletelist 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 issupplied as a suggested starting point for defining the service data. It may beused, unless there are engineering or other reasons for using a different value.For more details, please refer to NTP 241-2001-340Envelope DefinitionsandNTP 241-1001-119DPN Closed User Group Description and User Guide.

Primary_Dnas (maximum 1000)

Primary/X302112345 DNA O

Primary/X302154321 DNA O

Table 5 (continued)Hierarchy: Call Redirection list components


(Sheet 2 of 2)



Table 6Call_Redirection server data fields

Component FieldDefaultavailable Envelope Notes

PE_Mnemonic service mnemonic No See your NetworkAdministrator for anappropriate service mnemonic.

Call_Redirection_Server

DNA_CUG On_line Yes DNA/CUG

Statspool Yes ”

NCUG_Index/n CUG ID No ” See your NetworkAdministrator for anappropriate CUG ID. NOTE: nmust be 1.

Out CUG Calls Yes ”

In CUG Calls Yes ”

Privileged Yes ”

DNIC/n SNRID/n No DNICRedirection

See your NetworkAdministrator for appropriateSNRIDs. NOTE: Up to 7 fieldscan be used.

PE_Loader Percent heap Yes PE_Loader

Processor type Yes ” See System Administrator forappropriate processor type.

MUX DMA Yes ”

Load file name No Loader See System Administrator forappropriate file name.

Percent heap Yes

Processor type No

MUX DNA Yes

56 Chapter 4

241-1001-115 37.2S1

Steps to follow when provisioning Call RedirectionThe following procedure explains how to add the Call Redirection server(CRS) using DPN Architect. Please refer to NTP 241-6001-012Preside MDMArchitect for DPN User Guide and NTP 241-6001-304Preside MDMArchitect Administrator Guide for details on how to use the Architectapplication.

The term packet module (PM) is used synonymously with the terms accessmodule (AM) and resource module (RM); both of which are also referred to asDPN-100 modules.

Table 7Call_Redirection list data fields

Component FieldDefaultAvailable Envelope Notes

Primary_Dnas

Primary/X302112 Member DNA/n No DNAREDfile

See your NetworkAdministrator for anappropriate Member DNAnumber.



Procedure 3How to add the Call Redirection server

1 Add a PE on the PM (AM or RM) that is to contain the CRS server. ThePE_Loader component is presented and must be completed. Ensure that thePE_Loader has a load filename of CSERV386.<level> for HPPE or PE386.

2 Under the PE, add PE_Mnemonic with service mnemonic REDSERV.

3 Under the PE_Servers component, add a Call_Redirection_Servercomponent. Enter the DNA of the CRS as the <key value> .

4 Complete the fields for the DNA_CUG component.

5 Under the NCUGs component, add a CUG with an NCUG index of 1 as the <keyvalue> . The CUG ID must match the CUG ID of the ACRD server.

6 Optionally, under the Call_Redirection_Server, add a DNIC_Redirectioncomponent.

7 Enter the first DNIC as the <key value> . Complete the fields for the DNICcomponent.

8 Optionally, add more DNIC components under the DNICs component. Enter theDNIC as the <key value> , and complete the fields.

9 Under the PM (AM or RM), add a Call_Redirection_list component andenter the first primary DNA as the <key value> . Complete the fields for thePrimary component.

10 Optionally, add more Primary components under the Primary_DNAs component.

Procedure 4How to add the Call_Redirection_Server using the PE_Combination_Servercomponent

Note: Ensure that another PE does not exist with the same PE number as thePE_Combination_Server . This PE can also be used to provision theHunt_Group_Server and/or the NDI_Server components.

1 Add a PE_Combination_Server under the PM (AM or RM) that is to containthe Call_Redirection_Server . Enter the PE number as the <key value> .The PE_Loader component is presented and must be completed. Ensure thatthe PE_Loader has the Processor type set to HPPE or PE386, and theLoad file name is CSERV386.<level> .

2 Optionally, under PE_Combination_Server , add PE_Mnemonic with servicemnemonic CSERV.

3 Complete the fields for the PE_Mnemonic component.

4 Under the PE_Combination_Server , add a PE_Servers component.

5 The remaining components are provisioned as described in Procedure 3, How toadd the Call Redirection server. Refer to steps 3 through 10.

58 Chapter 4

241-1001-115 37.2S1

59


AAccess to Call Redirection

impacts of changes to envelopes 49prerequisites 48provisioning 48service data entry fields 50service data hierarchy 48

Accounting 45

BBenefits of call redirection 17

CCall Redirection 52

prerequisites 52service data entry fields 54service data hierarchy 52

Call redirection remote server interface 31Call redirection server on an AM or RM 32Call redirection system operator

commands 42Call redirection system service data 42Components of the call redirection system 31Criticality of service data 44

DData network identification code (DNIC)

redirection 27DNA redirection 22, 34DNA redirection list file 43DNIC redirection 33DPN AM/RM operator commands 42DPN AM/RM redirection service data 43

DPN RM CRD-RSI service data 44DPN-AM CRserv service data envelopes 43

HHow call redirection works 18

IInitialization of SVCs 35Interaction with hunt groups 37Interactions with other systems 37Introduction 41Introduction to call redirection 17

LLimitations 39

OOperations 41

PProvisioning

Access to Call Redirection 48Call Redirection 52impacts of changes to envelopes 49, 54prerequisites 48, 52service data entry fields 50, 54service data hierarchy 48, 52

PVC back-up description 37

RRouting identifier (RID) redirection 19

Index

241-1001-115 37.2S1

60 Index

SStatistics 45SVC setup on an RM 35

UUse and handling of RID 0 23

WWhen call redirection is required 17Why call redirection is required 17

DPN-100


Copyright © 1986 - 2001 Nortel NetworksAll Rights Reserved.

NORTEL, NORTEL NETWORKS, the globemark design, the NORTELNETWORKS corporate logo, DPN, and PASSPORT are trademarks of NortelNetworks.

Publication: 241-1001-115Document status: StandardDocument version: 37.2S1Document date: February 2001Printed in Canada

dpn call redirection system user guide

Documents

redirection components

dna redirection rm

dna redirection list

dnic redirection list

flow of dna redirection

redirection server components

redirection system user

dpn rm operator commands