Documente Academic
Documente Profesional
Documente Cultură
241-1001-115
DPN-100
Publication: 241-1001-115
Document status: Standard
Document version: 37.2S1
Document date: February 2001
37.2S1
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
Chapter 1
Introduction to call redirection
17
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
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
Contents 13
List of procedures
Procedure 1
Procedure 2
Procedure 3
Procedure 4
37.2S1
14 Contents
241-1001-115 37.2S1
15
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
Related documents
The following publications are referred to in this document:
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:
high capacity
high performance
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
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).
241-1001-115 37.2S1
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)
241-1001-115 37.2S1
Figure 2
RM RID redirection - network link failure
CALL REDIRECTION
REMOTE SERVER
INTERFACE
RID
REDIRECTION
LIST
4
1
RM2
RM1
AM1
(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
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
241-1001-115 37.2S1
CALL REDIRECTION
SERVER
CALL REDIRECTION
REMOTE SERVER
INTERFACE
1
RM1
DNA
REDIRECTION
LIST
RM2
5
6
AM1
AM2
2
SECONDARY
DNA
PRIMARY
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
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.
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
RPOA-Forward
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
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
Initialization of SVCs
Limitations
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.
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.
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
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 RID
Secondary #1 DNIC+DNA
Secondary #2 DNIC+DNA
Secondary #3 DNIC+DNA
Secondary #4 DNIC+DNA
Secondary #5 DNIC+DNA
Secondary #6 DNIC+DNA
Secondary #7 DNIC+DNA
Sec. #1 RID
Sec. #2 RID
Sec. #3 RID
Sec. #4 RID
Sec. #5 RID
Sec. #6 RID
Sec. #7 RID
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
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
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.
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
241-1001-115 37.2S1
1
P
2
M
Limitations
The following is a list of limitations in the system:
37.2S1
40 Chapter 2
Primary addresses can be of address type X.121 or E.164 except for E.164
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
Alarms
Accounting
Statistics
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:
operator commands
service data
system reports
alarms
37.2S1
42 Chapter 3
accounting
statistical data
querying of envelopes
displaying statistics
querying of envelopes
displaying statistics
241-1001-115 37.2S1
Operations 43
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
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:
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-1001-119 DPN Closed User Group Description and User Guide
service data hierarchy: how the service data should be configured; and
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
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)
37.2S1
50 Chapter 4
Field
Default
available
Envelope
RID_Redirection
RIDn
Yes
DNA_CUG
Outgoing call
Yes
DNA/CUG
CUG ID
No
DNA/CUG
Yes
DNA/CUG
In CUG Calls
Yes
DNA/CUG
Privileged
Yes
DNA/CUG
Statspool
Yes
DNA/List
Yes
DNA/List
Server DNA n
No
DNA/List
Notes
default priority
NCUGs
NCUG_Index/n
Direct_Call_List
241-1001-115 37.2S1
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.
Complete the RID Redirection table. You may want to fill in this table later using
the GDM tool.
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.
37.2S1
52 Chapter 4
service data hierarchy: how the service data should be configured; and
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.
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
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)
241-1001-115 37.2S1
Component
Field
PE_Mnemonic
service mnemonic No
Envelope
Notes
See your Network
Administrator for an
appropriate service mnemonic.
Call_Redirection_Serv
er
DNA_CUG
On_line
Yes
DNA/CUG
Statspool
Yes
CUG ID
No
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
No
Loader
Percent heap
Yes
Processor type
No
MUX DNA
Yes
NCUG_Index/n
37.2S1
56 Chapter 4
Table 7
Call_Redirection list data fields
Component
Field
Default
Available
Member DNA/n
No
Envelope
Notes
DNARED
file
Primary_Dnas
Primary/X302112
241-1001-115 37.2S1
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 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.
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.
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
Components of the call redirection system 31
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
H
How call redirection works 18
I
Initialization of SVCs 35
Interaction with hunt groups 37
Interactions with other systems 37
Introduction 41
Introduction to call redirection 17
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