NEC America, Inc. reserves t he right to change th e specifications, functions, or
features, at any time, without notice.
NEC America, Inc. has prepared this document for use by its employees and
customers. The information contained herein is the property of NEC America,
Inc. and shall not be reproduced without prior written approval from NEC
America, Inc.
This manual covers the installation of the Fusion system.
2. How to Follow This Manual
This manual consists of the following chapters:
• CHAPTER 1 (INTRODUCTION)
Explains ho w to use this manual.
• CHAPTER 2 (GENERAL)
Outlines the Fusion system configuration and lists available service features.
• CHAPTER 3 (SYSTEM CONFIGURATION)
Explains the hardwa re configurati on of the Fusi on syst em.
• CHAPTER 4 (INSTALLATION)
Consists of the foll owing topics:
•Static Cautions
• Switch Settings (PA-M96, PA-FCHA, PA-24DTR)
• CHAPTER 5 (DATA PROGRAMMING)
Provides basic data assignment procedures using the following examples:
•Installing a new Fusion network
•Upgrading a CCIS network
• CHAPTER 6 (POST INSTALLATION TEST)
Explains how to perform installation tests, focusing on the Fusion link connection test.
• CHAPTER 7 (TROUBLESHOOTING)
Explains Fusion-related system messages and the repair procedures.
NDA-24299CHAPTER 1
Page 1
Revision 1.0
INTRODUCTION
Related Manuals
3. Related Manuals
For install ation of the Fusion syste m , the followin g manuals are required:
•NEAX2400 IPX Circuit Card Manual
•NEAX2400 IPX Installation Manual
•NEAX2400 IPX Office Data Specification
To use this manual, the reader should have sufficient knowledge of the installation of both the CCIS No. 7 and
the ACIS systems. For more information on these systems, refer to the related manuals.
CHAPTER 1NDA-24299
Page 2
Revision 1.0
CHAPTER 2GENERAL
1. What is Fusion and its Advantages
The main advantages of the Fusion network are as follows:
1.1 Improved Inter-Office Service Features
The Fusion system can eli minate th e constr aints no rmally as sociate d with net wor k servic es that are of f ered
using Common Channel Inter-Office Signaling (CCIS).
1.2 Use of Telephone Numbers
A Fusion system allows you to use telephone numbers in addition to the existing station numbers. (In the
remainder of this manual, the existing station numbers are referred to as Physical Station Numbers.) Fusion
service features are activated when a telephone number is dialed. The telephone number, which can be
assigned on a station basis, is a unique number on a Fusion network. If required, numbering plan data,
which is identical to that of an existing station number, can be used to maintain consistency of the
numbering plan. When this plan is adopted, you can use the same numbering plan data after introducing
the Fusion system. Figure 2-1 illustrate s the use of teleph one number s in the Fusion netw ork.
Note:
A maximum of 16 digits can be used as a telephone number.
Telephone Number can be assigned to a station by using the LENs or by the Physical Station Number depending on the program ming
as shown below.
¥ When using LENs
STN: 2000
LENS: 000010
LENS
¥ When using Physical Station Number
STN: 2000
LENS: 000010
Physical Staio n N u m b er
Fusion features are activated when a Telephone Number is dialed.
Telephone Num ber
410001
dialing a Telephone Number.....
LENS: 000010 410000
S TN : 20 00 410 000
Fusion features
are activated.
Fusion Netw ork
Telephone Num ber: 410000
Telephone N um ber: 410000
STN: 2000
LENS: 000010
STN : 2000
LENS: 000010
STN a
STN : 2000
Telephone Num ber: 410000
STN b
STN : Physical Station Numb er
STN: 2500
Telephone N umber: 410001
Figure 2-1 Telephone Number
NDA-24299CHAPTER 2
Page 3
Revision 1.0
GENERAL
Free Numbering
2. Free Numbering
A telephone number can be assigned to a desired station on the Fusion network with the simple command
operation shown in Figure 2-2.
In this figure, the user is changing the location of Telephone Number "411111" to N ode B.
C
h
MAT
Telephone #: 411111
STN: 2000
Node A
Logical N um ber
411111
Node A
a
n
g
e
l
o
c
a
t
i
o
n
Node C
Note:
Telephone #: 411111
STN: 2000
Node B
Note
user
The AlGSN command is used for assigning Telephone Numbers. See 5.6 “Assignment of Telephone
A Fusion network has one Network Control Node (NCN) and Local Nodes (LNs). The NCN has the
Centralized-MAT, which runs on Windows 95/NT. The MAT can collect fault information from all nodes
on the network. The NCN has Network Data Memory, which stores the data related to the network level.
The telephone numbers, for exampl e, can be change d with the Central ized-MAT at the NCN. The MAT als o
allows th e user to ma nage network-level office data. Refer to Figure 2-3
Fault inform ation can be collected at NCN via Fusion Link.
Node C
Fault Infor mation
Node A
Node B
December 12 1997
AM 3:12:13
Node B FCH Failure
M G: 00
U : 02
PRT
13-H
1. xxxx xxxx 0010 1222
4. x0010 1110 10110 1FFF
7. E23C CAAB 12 00 0 0000
NEC
MAT
13-H
1. xxxx xxxx 0010 1222
4. x0010 1110 10110 1FFF
7. E23C CAAB12 000 0000
G : 11
Note
: : :
Note:
Actual system message is indicated in a different format.
Figure 2-3 Centralized MAT on Fusion Network
CHAPTER 2NDA-24299
Page 4
Revision 1.0
Fusion Network
NCN
Fa ult In for m a tio n
NCN : Network Control N ode LN: Local N ode
Fusion Link
Node B
FC H fa ult....
LN
LN
GENERAL
Fusion System Configuration
3. Fusion System Configuration
The Fusion system can be conf igured i n the foll owing two wa ys. Figure 2-4 shows a Fusion system with Fusion
Call Control Handler (FCH) cards.
Node BNode ANode C
4.9 ft
DTI
FCH
HUB
FCH
HUB
CPU
LAN I
DTI
CPU
LANI
DTI: Digital Trunk Interface FCH: Fusion Call Control Handler LANI: LAN Interface
DTI
Fusion Link
1.5M
4.9 ft
FCH
Dch: 64K-1.5M
HUB
10BASE-T10BASE-T10BASE-T
Fusion Link
1.5M
4.9 ft
Dch: 64K-1.5M
DTI
FCH
4.9 ft
HUB
Figure 2-4 Fusion System Configuration (with FCH)
Figure 2-5 shows a Fusion system without Fusion Call Control Handler (FCH) cards.
his figure shows a Fusion system w ithout Fusion Call Control Handler ( FCH) cards.
DTIDTIDTI
DTI
T1 LinkT1 Link
Node BNode ANode C
DTI
DTIDTI
CPU
LANI
DTI
CPU
LANI
Fusion LinkFusion Link
10BASE-T10BASE-T
T I: D ig ita l T ru n k In te rfac e L A NI: LA N Inter fa c e
Figure 2-5 Fusion System Configuration (without FCH)
CPU
LANI
HUB
CPU
LANI
NDA-24299CHAPTER 2
Page 5
Revision 1.0
GENERAL
Node
4. Node
A Fusion network consists of the following types of nodes:
•Network Control Node
The Network Control Node, which must be assigned on a Fusion network, manages other nodes on the
network. This no de has the Ce ntral ized- MAT to coll ect fa ult i nformat ion f rom other nodes on the netw or k.
Multiple nodes cannot be assigned as a Network Control Node.
•Local Node
All nodes other than the Network Control Node are called Local Nodes. Fault information generated at a
Local Node is sent to the Network Control Node via a Fusion link, allowing the Network Control Node to
collect the fault information. A Fusion network can have a maximum of 16 nodes on the network.
Figure 2-6.
See
Note:
The actual number of nodes varies with system configurations.
•Center Node (for Centralized Billing - Fusion)
This node collects the billing information from other nodes as well as the self-node. For this reason, the
node is called Center Node for Cent rali zed Bil ling - Fusion. Mul tiple Cent er Nodes can be as signed on th e
network by spe cifying the poll ing dest inations , which ca n be set by the ASYDL command - S YS 1 Ind ex es
608 through 639. At the Center Node, the user can select “polling destinations” by setting 1 to the FPC of
the corresponding nodes. For more information, see the NEAX2400 IPX Office Data Specification.
A Fusion network can have a maximum of 16 nodes.
N13
N14
N12
N15
N11
N16
N10
N1
N2
N9
N3
N4
N5
N6
N7
N8
N: Node
Figure 2-6 Maximum System Configuration
CHAPTER 2NDA-24299
Page 6
Revision 1.0
Fusion netw ork
GENERAL
Data Memory Configuration
5. Data Memory Configuration
Each node on a Fusion network has the following three kinds of Data Memory:
•Data Memory (DM)
•Local Data Memory (LDM)
•Network Data Memory (NDM) - Programmable only by the NCN.
When the contents of the NDM are changed at NCN, the new data is automatically copied to the NDM of each
node. The NDM of the NCN functions as primary memory. Figure 2-7 shows how a telephone number change
is performed in a Fusion network.
When telephone numbers are changed, the change at the NCN will affect all nodes on the network. In this
figure, data change at Node A is automatically transferred to each node.
410000
Centralized
MAT
Data Change...
Telephone Number Change
410000 410001 (for self-Node)
420000 420001 (for Node B)
430000 430001 (for Node C)
440000 440001 (for Node D)
Note:
The data must be manually transferred with the CBCN command when the Fusion system is
410001
TCP/IP
configured for the first time or the system is once initialized at the NCN.
NCN
Node A
updating NDM
at each node
NDM (master)
Node B
LN
Node C
LN
Node D
LN
copy
copy
copy
420000
NDM
NDM
440000
NDM
430000
420001
430001
440001
Figure 2-7 Network Data Memory
NDA-24299CHAPTER 2
Page 7
Revision 1.0
GENERAL
Fusion Network Examples
When the NDM (primary) is modified, the new data is automatically copied. See Figure 2-8
Change...
Fusion Link
NCN
DM
LDM
NDM
(m a ste r)
copy
The standard size of each mem ory is as follows:
LNLN
DMDM
LDM
NDM
LDM
NDM
copy
DM (Data Memory): 4M Bytes
LDM (Local Data Memory): 2M Bytes
NDM (N e tw o rk D a ta M e mo ry) : 2M B y tes
NCN: Network Control Node LN: Local Node
Figure 2-8 Network Data Memory Copy
6. Fusion Network Examples
Figure 2-9 and Figure 2-10 show ex amples of Fusi on networks. When i ncorporating the Fusion sys tem with the
existing CCIS network, connect all nodes via CCIS links.
Note:
To co nnect a CCIS network and Fusion network, use STNs and TEL Ns re spectively.
3x x x : CCIS for Nod e C
[Closed N um bering]
2x x x : CCIS for Nod e B
1xxx: self-Node
4xxxxx: FU SIO N acc ess
5x x x : CCIS a c c e s s f o r
C C IS Ne two rk
NCN
Node A
FPC = 1
PC =10
LN
Node C
FPC= 3
FCC S
CCIS
PC = 12
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
TELN
410000
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
STN: 3000
TELN
430000
STN: 1000
STN: Physical Station Number TELN: Telephone Number FPC: FUSION Point Code PC: Po in t Code (CCIS)
Figure 2-9 Closed Numbering Fusion-CCIS Network
CHAPTER 2NDA-24299
Page 8
Revision 1.0
S
I
C
C
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
STN: 1001
FCC S
CCIS
TELN
410001
C CIS
Network
"5xxx"
LN
Node B
FPC = 2
PC = 11
TELN
420000
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
STN: 2000
[Open Numbering]
LN
Node C
"82"
FPC= 3
PC = 12
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
STN: 2000
TELN
430000
81: CCIS for Node B
82: CCIS for Node C
8x: CCIS access for
CCIS Network
4x...: Fusion access
FCCS
CCIS
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
STN: 2000
NCN
Node A
"80"
FPC = 1
PC =10
TELN
410000
S
I
C
C
410001
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
STN: 2001
GENERAL
Fusion Network Exampl es
CCIS
Network
"8x"
FCCS
LN
CCIS
TELN
Node B
"81"
FPC = 2
PC = 11
STN: 2000
TELN
420000
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
Figure 2-10 Open Numbering Fusion-CCIS Network
[conditions for telephone number digits]
When incorporating the Fusion system with the CCIS netwo rk, consider the conditions in Table 2-1 as to the
available telephone number digits.
Telephone Number
Composition
4 digits or less Note
4~8digitsNote
9 digits or moreNote
Display
D
term
ATTCON/
DESKCON
Inter-Office
Service
MCI
××× ×××
×-×-××
--- --×
Table 2-1 Available Tele phone Nu mber Dig its
SMDR
CCISFusion
×:Availab le-:Not available
Note:
When the network is Open Numbering, the “digits” in the table abo ve must be the number of “office code
digits + telephone number digits”.
NDA-24299CHAPTER 2
Page 9
Revision 1.0
GENERAL
Tandem Connections via Fusion Link
7. Tandem Connections via Fusion Link
Tandem connections via FCCS-ACIS can be established. In Figure 2-11, STN (A) can place a tandem call via
FCCS-ACIS.
Tandem connection FCCS
ACIS is established.
LN
Node A
calling party
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
STN (A)
Figure 2-11 Tandem Connections via Fusion Link
FCCS
TELN
430000
FCCS
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
STN (B)
NCN
Node B
TELN
410000
ACIS
O
C
CO
T
CHAPTER 2NDA-24299
Page 10
Revision 1.0
CHAPTER 3SYSTEM CONFIGURATION
Fusion systems can be divided into the following two types:
•Fusion system with FCH
•Fusion system without FCH
Note:
FCH (Fusion Call Control Handler) : PA-FCHA
This chapter explains the system configuration of each Fusion system.
1. FUSION System without FCH
An example system configuration of Fusion system which does not use a DTI to carry D-channel is shown
below. In this configuration, Fusion link is established between nodes via Ethernet. The DTI card carries Bchannels only in this example. See Figure 3-1 below.
This figure shows a Fusion System Configura tion without FCH.
Node A
TS W/IN TTS W/IN T
MUX
DTIDTI
B-channel
Node B
MUX
10 Base T
CPU
PCI Bus
TSW (Time Division Sw itch): P H-SW 10
MUX: PH-PC36
LA NI (L AN In te rfa c e ): P Z-P C19
DTI (Digital Trunk Interface): P A-24DT R
Note:
A maximum of 4 HUBs can be cascaded between the originating node and the incoming node.
LANI
(Restriction by operating condition of Ethernet.)
Figure 3-1 FUSION System Configuration without FCH
Max. 100m
Note
Max. 100m
10 Base T
LANI
CPU
PCI Bus
D-channel
Fusion Link
HUB
NDA-24299CHAPTER 3
Page 11
Revision 1.0
SYSTEM CONFIGURATION
Fusion System with FCH
2. Fusion System with FCH
2.1 System Configuration
A sample system configuration of Fusion system which uses a DTI to carry D-channel is shown below. In
this configurat ion, Fusion link is established bet w een nodes via the T1 link. See Figure 3-2 below.
This figure shows a Fusion S ystem Configuration with FCH .
Node A
TSW /INTTSW /INT
MUX
DTIDTI
FCH
10 Base T
......
HUB
CPU
PCI Bus
TSW (Time Division Switch): PH-SW 10
HUB: PA-M96
MUX: PH-PC36
LANI (LAN Interface): PZ-PC19
FCH (Fusion Call Control Handler): PA-FCH A
DTI (Digital Trunk Interface): P A-24DTR
LANI
ch 0
D/ID/I
FCHFCH
10 Base T
D-channel (example)
Fusion Link
B-channel / D -channel
ch 23
FCH
10 Base T
......
HUB
10 Base T
LAN I
PCI Bus
Node B
MUX
CPU
Figure 3-2 Fusion System Configuration with FCH
CHAPTER 3NDA-24299
Page 12
Revision 1.0
SYSTEM CONFIGURATION
Fusion System with F CH
Note:
When a direct connection is added to the existing Fusion system with FCH card between the two nodes, it
is required to execute Make Busy operation (MB Key ON/OFF) on the FCH cards to prevent from packet
loop.
Node BNode A
DTI
CPU
LANI
10BASE-T
DTIDTI
FCH
Fusion Link
1.5M
MB key ON/OFF
HUB
Connect the HUBs with a cross cable
DTI
FCH
HUB
CPU
LANI
DTI : Digital Trunk InterfaceFCH : Fusion Call Control Handler LANI : LAN Interface
Figure 3-3 Add a Direct Connection to Fusion System with FCH
On other occasions for adding direct connection (connect cross cable between the HUBs) to the Fusion
network consists of mu ltiple n odes, also perform th e MB key ON/OFF oper ation on j ust a sin gle FCH card
to prevent from packet loop. See Figure 3-3
When the system applies dual configura tion, MB Key ON/OFF opera tion is to be exe cuted to an FCH car d
on each #A/#B side.
2.2 Redundancy of FUSION Link
FCH (PA-FCHA) card handles a Fusion link, occupying one time slot of a frame by D/I function equipped on
the DTI card. In terms of redundancy, Fusion system (with FCH) can have one of the following configuratio ns.
•Redundant Configuration (LANI, HUB, FCH, and DTI)
•Redundant Conf igu rat ion (HUB, FCH, and DTI)
•Redundant Configuration (FCH and DTI)
•Non Redundant Conf iguration
NDA-24299CHAPTER 3
Page 13
Revision 1.0
SYSTEM CONFIGURATION
Fusion System with FCH
Figure 3-4 shows LANI, HUB, FCH, and DTI in a fully redundant configuration.
CPU#0
CPU#1
LANI#0-A
LANI#0-B
LANI#1-A
LANI#1-B
....
HUB0
HUB1
....
Redundancy
10 Base T
10 Base T
Figure 3-4 Redundant Configuration (LANI, HUB, FCH, and DTI)
Figure 3-5 shows HUB, FCH, and DTI in a redundant configuration.
PCI Bus
PCI Bus
LANI#0CPU#0
10 Base T
LANI#1CPU#1
10 Base T
....
HUB
HUB
....
10 Base T
10 Base T
10 Base T
FCH0
FCH1
FCH
FCH
DTI
to the same route
DTI
DTI
to the same route
DTI
Figure 3-5 Redundant Configuration (HUB, FCH, and DTI)
Figure 3-6 shows FCH and DTI in a redundant configura ti on.
LANI#0CPU#0
PCI Bus
LANI#1CPU#1
PCI Bus
CHAPTER 3NDA-24299
Page 14
Revision 1.0
10 Base T
....
HUB
10 Base T
Figure 3-6 Redundant Configuration (FCH and DTI)
10 Base T
10 Base T
Redundancy
FCH
FCH
DTI
to the same route
DTI
Redundancy
In this case, no redundancy is taken as to Fusion link.
SYSTEM CONFIGURATION
Fusion System with F CH
CPU#0
PCI Bus
PCI Bus
LANI#0
10 Base T
LANI#1CPU#1
10 Base T
Figure 3-7 Non-Redundant Configuration
Note:
Be sure that the system configurations shown below are not available. The Node composed of dual-HUB
system cannot apply to the opposite side agai nst a Node with single-HUB configuration.