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.
NEAX and D
term
are registered trademarks of NEC Corporation.
All other brand or product names are or may be trademarks or registered
trademarks of, and are used to i dentify pr oducts or ser vices of, t heir respec tive
owners.
MS-DOS and Microsoft are registered trademarks of Microsoft Corporation.
Microsoft Windows 95 and Windows NT are trademarks of Microsoft
Corporation.
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, P A - 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.
•CHAPTER 8 (EX-FCCS)
Consists of the following EX-FCCS topics:
•Network Configuration
•Feature Descriptions
•Data Programming
ND-70185 (E)CHAPTER 1
Page 1
Revision 3.0
INTRODUCTION
Related Manuals
3. Related Manuals
To complete the installat io n of the Fusio n system, the following manuals are requ ired:
•NEAX2400 IMX Circuit Card Manual
•NEAX2400 IMX Installation Manual
•NEAX2 400 IMX Office Data Specification
This manual assumes that the reader has 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 1ND-70185 (E)
Page 2
Revision 3.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 Tele phone Numbers in addition to the existing stat i on 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 e xisti ng station numbe r , ca n be used to maintain con sistenc y of the numb ering plan. When this plan is ado pted, you can use th e same numbering plan data after in troducing the Fusion
system.
Note:
A maximum of 16 digits can be used as a Telephon e Number.
Telephone Number can be assigned to a station using the LENs or by the Physical Station Number depending on the programming
as shown below.
• When using LENs
STN: 2000
LENS: 000010
LENS
• When using Physical Station Number
Physical Staion Number
Note: For more information, see "Assignment of Telephone Numbers" in this manual.
Fusion features are activated when a Telephone Number is dialed.
Telephone Number
410001
dialing a Telephone Number.....
STN: Physical Station Number
STN: 2000
LENS: 000010
LENS: 000010 410000
STN: 2000 410000
Fusion features
are activated.
Fusion Network
STN: 2000
LENS: 000010
Telephone Number: 410000
STN: 2000
LENS: 000010
Telephone Number: 410000
Telephone Number: 410000
Telephone Number: 410001
STN a
STN: 2000
STN b
STN: 2500
Figure 2-1 Telephone Number
ND-70185 (E)CHAPTER 2
Page 3
Revision 3.0
GENERAL
Free Numbering
2. Free Numbering
A Telephone Number can be assigned to a desired station on the Fusion network using the simple command
operation shown below.
In this figure, the user is changing the location of Telephone Number "411111" to Node B.
C
h
MAT
Telephone #: 411111
STN: 2000
Node A
Node A
a
Telephone Number
411111
Node A
n
g
e
l
o
c
a
t
i
o
n
Node C
Telephone #: 411111
STN: 2000
Node B
Node B
user
Note
STN 2000
NCN
Fusion Network
NCN: Network Control Node
STN: Physical Station Number
Node B
LN
STN 2000
LN
STN 2000
LN: Local Node
Note: The ALGSN command is used for assigning Telephone Numbers. See 5.6 "Assignment of Telephone Numbers" for more
detail.
Figure 2-2 Free Location
2.1 Centralized Maintenance Ad min i st ration Terminal (MAT)
A Fusion network has one Network Control Node (NCN) and Local Nodes (LNs). The NCN has the Cen tralized-MAT, which runs on Windows 95/NT. The MAT can collect fault information from all nodes on
the network. The NCN has Net work Data Memory, which stores the data related t o network le vel. The Telephone Numbers, for example, can be changed using the Centralized-MAT at the NCN. The MAT also allows the user to manage network-level office data.
Fault information can be collected at NCN via Fusion Link.
Node C
Fault Information
Node B
December 12 1997
AM 3:12:13
Node A
Node B FCH Failure
MG: 00
U : 02
G : 11
Note
: :
PRT
13-H
1. xxxx xxxx 0010 1222
4. x0010 1110 10110 1FFF
7. E23C CAAB12 000 0000
NEC
MAT
13-H
1. xxxx xxxx 0010 1222
4. x0010 1110 10110 1FFF
7. E23C CAAB12 000 0000
NCN
Fault Information
:
Note:
Actual system message is in dicat ed in a diff erent format.
Figure 2-3 Centralized MAT on Fusion Network
CHAPTER 2ND-70185 (E)
Page 4
Revision 3.0
Fusion Link
Node B
LN
Fusion Network
FCH fault....
LN
NCN: Network Control Node LN: Local Node
GENERAL
Fusion System Configuration
3. Fusion System Configuration
The Fusion system can be divided in to the following two types. Figure 2-4 shows a Fusi on sys tem with Fusi on
Call Control Handler (FCH) cards.
Node BNode ANode C
DTI
CPU
LANI
TI: 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
4.9 ft.
DTI
FCH
HUB
FCH
CPU
LANI
Dch: 64K-1.5M
HUB
Fusion Link
1.5M
4.9 ft.
4.9 ft.
DTI
FCH
HUB
Figure 2-4 Fusion System Configuration (with FCH)
Figure 2-5 shows a Fusion system without Fusion Call Control Handler (FCH) cards.
Node A
DTIDTIDTI
DTI
T1 LinkT1 Link
Node B
DTI
DTIDTI
CPU
LANI
Node C
DTI
CPU
LANI
Fusion LinkFusion Link
10BASE-T10BASE-T
DTI: Digital Trunk Interface LANI: LAN Interface
Figure 2-5 Fusion System Configuration (without FCH)
CPU
LANI
HUB
CPU
LANI
ND-70185 (E)CHAPTER 2
Page 5
Revision 3.0
GENERAL
Node
4. Node
A Fusion network consists of the following types of nodes:
•Network Control Node
Network Control Node , which must be assigned on a Fusion network, manages other nodes on t he networ k.
This node has the Central ized- MAT to collec t f ault i nformat ion fr om other nodes on t he net work. Multipl e
nodes cannot be assigned as a Network Control Node.
•Local Node
All nodes other than Network Control Node are called Lo cal Node. Fault information generated at a Local
Node is sent to the Netw ork Control Node via a Fusion Link , allo wing the Netw ork Control Node to collect
the fault inform ation. A Fusion netwo rk can hav e a maximum of 16 nodes on the netw ork.
(See Figure 2-6.)
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 IMX Office Data Specification.
A Fusion network can have a maximum of 16 nodes.
N14
N13
N12
N15
N11
N16
N10
N1
N2
N9
N3
N4
N5
N6
N7
N8
N: Node
Figure 2-6 Maximum System Configuration
CHAPTER 2ND-70185 (E)
Page 6
Revision 3.0
Fusion network
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 master 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.
Note
Centralized
MAT
410001
TCP/IP
410000
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 using the CBCN command when the Fusion system is
configured for the first time or the system is once in itialized at the NCN.
NCN
Node A
updating NDM
at each node
NDM (master)
430000
440000
420001
430001
440001
Node B
LN
Node C
LN
Node D
LN
420000
copy
NDM
copy
NDM
copy
NDM
Figure 2-7 Network Data Memory
ND-70185 (E)CHAPTER 2
Page 7
Revision 3.0
GENERAL
Fusion Network Examples
When the NDM (master) is modified, the new data is automatically copied.
Change...
Fusion Link
NCN
DM
LDM
NDM
(master)
copy
The standard size of each memory is as follows:
LNLN
DM
LDM
NDM
DM
LDM
NDM
copy
DM (Data Memory): 4M Bytes
LDM (Local Data Memory): 2M Bytes
NDM (Network Data Memory): 2M Bytes
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, all nodes must be connected via CCIS links.
Note:
To co nnect a CCIS network an d Fusion network, use ST Ns and TELN s respectively.
3xxx: CCIS for Node C
[Closed Numbering]
2xxx: CCIS for Node B
1xxx: self-Node
4xxxxx: FUSION access
5xxx: CCIS access for
CCIS Network
CCIS
NCN
Node A
FPC = 1
PC =10
FCCS
CCIS
LN
Node C
FPC= 3
FCCS
CCIS
PC = 12
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
TELN
410001
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
TELN
430000
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
TELN
410000
STN: 3000
STN: 1000
STN: 1001
STN: Physical Station Number TELN: Telephone Number FPC: Fusion Point Code PC: Point Code (CCIS)
Figure 2-9 Closed Numbering Fusion-CCIS Network
CCIS
Network
"5xxx"
Node B
FPC = 2
PC = 11
LN
TELN
420000
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
STN: 2000
CHAPTER 2ND-70185 (E)
Page 8
Revision 3.0
GENERAL
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Fusion Network Exampl es
[Open Numbering]
81: CCIS for Node B
82: CCIS for Node C
8x: CCIS access for
CCIS Network
4x...: Fusion access
CCIS
Network
"8x"
CCIS
NCN
FCCS
LN
Node C
"82"
FPC= 3
CCIS
PC = 12
TELN
...
... ...
... ...
...
... ...
... ...
...
... ...
... ...
...
... ...
... ...
430000
STN: 2000
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
STN: 2000
STN: Physical Station Number TELN: Telephone Number FPC: Fusion Point Code PC: Point Code (CCIS)
Node A
"80"
FPC = 1
PC =10
TELN
410000
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
STN: 2001
FCCS
CCIS
TELN
410001
Node B
"81"
FPC = 2
PC = 11
LN
TELN
420000
...
... ... ...
...
...
... ... ...
...
...
... ... ...
...
...
... ... ...
...
STN: 2000
Figure 2-10 Open Numbering Fusion-CCIS Network
[conditions for Telephone Number Digits]
When incorporatin g the Fus ion syst em with t he CCIS ne twork, consider the fo llo wing conditi ons as t o the a vailable
Telephone Number digits:
Display
Telephone Number
Composition
4 digits or less Note
4~8digitsNote
9 digits or moreNote
term
D
××× ×××
×-×-××
--- --×
ATTCON/
DESKCON
×:Available-:Not available
Note:
When the network is Open Number ing , th e “digi ts” i n the t able a bov e mus t be the n umber of “Of fice Code
digits + Telephone Number digits”.
Inter-Office
Service
SMDR
MCI
CCISFusion
ND-70185 (E)CHAPTER 2
Page 9
Revision 3.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
TELN
430000
FCCS
FCCS
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
STN (B)
NCN
Node B
TELN
410000
ACIS
COT
CO
CHAPTER 2ND-70185 (E)
Page 10
Revision 3.0
CHAPTER 3SYSTEM CONFIGURATION
Fusion systems can be divided into the following two types:
•Fusion system with FCH
•Fusion system without FCH
Note:
Fusion Call Control Handler (FCH): PA-FCHA
This chapter explains the system configuration of each Fusion system.
1. Fusion System without FCH
A sample Fusion system configuratio n that does not use a DTI to carry D-channel is shown below. In this configuration, the Fusion link is established between nodes using Ethernet. The DTI card carries B-channels only
in this example. Figure 3-1 shows a Fusion System Configuration without FCH.
This figure shows a Fusion System Configuration without FCH.
Node A
TSW/INTTSW/INT
MUX
CPU
PCI Bus
DTIDTI
Max. 328 ft.
Max. 100 m
Max. 100m
10 Base T
LANI
B-channel
D-channel
Fusion Link
HUB
Note
Max. 328 ft
Max. 100 m
Max. 100m
10 Base T
LANI
PCI Bus
Node B
MUX
CPU
TSW (Time Division Switch): PH-SW 10
MUX: PH-PC36
LANI (LAN Interface): PZ-PC19
DTI (Digital Trunk Interface): PA-24DTR
Note:
A maximum of 4 HUBs can be cascaded per route.
Figure 3-1 Fusion System Configuration without FCH
ND-70185 (E)CHAPTER 3
Page 11
Revision 3.0
SYSTEM CONFIGURATION
Fusion System with FCH
2. Fusion System with FCH
2.1 System Configuration
A sample Fusion system configuration that uses a DTI to carry D- channel is shown below. In this configu ration, the Fusion li nk is est ablished between node s via the T1 link. Figure 3-2 sho ws a Fu sion sy stem configuration with FCH.
This figure shows a Fusion System Configuration with FCH.
The FCH (PA-FCHA) card handles a Fusion link, occupying one time slot of a frame by D/I function located
on the DTI card. In terms of redundancy, the Fusion system (with FCH) can have one of the following configurations.
•Redundant Configuration (LANI, HUB, FCH, and DTI)
•Redundant Configurat ion (HUB, FCH, and DTI)
•Redundant Configuration (FCH and DTI)
•Non-Redundant Configuration
CHAPTER 3ND-70185 (E)
Page 12
Revision 3.0
SYSTEM CONFIGURATION
I
Fusion System with F CH
In Figure 3-3 LANI, HUB, FCH, and DTI are shown in a fully redundant configuration. This configuration is
available for Release 3 or later software.
n this case, LANI, HUB, FCH, and DTI are composed in a fully redundant configuration. Note that this configuration is available for
elease 3 or later software.
CPU#0
CPU#1
LANI#0-A
LANI#0-B
LANI#1-A
LANI#1-B
....
HUB0
HUB1
....
Redundancy
FCH0
10 Base T
FCH1
10 Base T
DTI
to the same route
DTI
Figure 3-3 Redundant Configuration (LANI, HUB, FCH, and DTI)
In Figure 3-4 HUB, FCH, and DTI are shown in a redundant configuration.
n this case, HUB , FCH, and DTI are composed in a redundant configuration.
DTI
to the same route
DTI
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
FCH
FCH
Redundancy
Figure 3-4 Redundant Configuration (HUB, FCH, and DTI)
In Figure 3-5 FCH and DTI are shown in a redundant configuration.
In this case, FCH and DTI are composed in a redundant configuration.
LANI#0CPU#0
PCI Bus
LANI#1CPU#1
PCI Bus
10 Base T
....
HUB
10 Base T
Figure 3-5 Redundant Configuration (FCH and DTI)
10 Base T
10 Base T
FCH
FCH
Redundancy
ND-70185 (E)CHAPTER 3
DTI
to the same route
DTI
Page 13
Revision 3.0
SYSTEM CONFIGURATION
System Considerations
In Figure 3-6, no redundancy is shown in the Fusion link.
In this case, no redundancy is taken as to Fusion link.
CPU#0
PCI Bus
PCI Bus
3. System Considerations
3.1 Fusion Network Conditions
This section explains how to design a Fusion network. In the following diagram, a Fusion Link is printed
in a thick line w hile a CCIS link is printed in a dotted line.
Condition 1:The maximum number of nodes on a Fusion network is sixteen (16) nodes.
example 1
Node A
FCCS
4
FCCS
3
FCCS
FCCS
LANI#0
10 Base T
....
HUB
LANI#1CPU#1
10 Base T
10 Base T
Figure 3-6 Non-Redundant Configuration
example 2
Node B
Node A
1
FCCS
FCCS
1
FCCS
FCCS
2
FCH
Node B
DTI
Node C
Node C
Routing from Node A Node C
Node A Node B Node D Node C
1
Node A Node D Node C
2
Node A Node B Node C
3
Node A Node C
4
example 3
Node A
FCCS
FCCS
Node B
FCCS
Node C
FCCS
Node E
FCCS
Node D
Node D
Figure 3-7 Fusion Network Topologies
CHAPTER 3ND-70185 (E)
Page 14
Revision 3.0
2
Node D
Node A
Routing from Node D Node C
Node D Node A Node B Node C
1
Node D Node B Node C
2
example 4
FCCS
Node B
FCCS
Node C
FCCS
Node D
SYSTEM CONFIGURATION
Condition 2:A maximum of four (4) nodes can be connected as tandem nodes.
max 4 nodes
System Considerations
Node A
FCCS
Node B
FCCS
Node CNode D
FCCS
Tandem Connection over FCCS links
Figure 3-8 Fusion Tandem Connections
Condition 3:The available connection-route number ranges from 1 to 1023.
Condition 4:The available connection-trunk number of each route ranges from 1 to 4095.
DTI
card
:
:
:
:
DTI
card
IMX
B ch
DTI
card
:
:
:
:
DTI
card
max 4095 ch
T1
T1
DTI
card
DTI
card
:
:
:
:
A maximum of 4095 ports can be assigned on a
connection-route basis between nodes.
IMX
DTI
card
DTI
DTI
card
card
:
:
:
:
T1
T1
C_RT
D ch
IMX
D ch
D ch: Data Link
B ch: Connection Trunk
Max 4095 trunks per connection-route
Figure 3-9 Maximum Number of Ports between Nodes
ND-70185 (E)CHAPTER 3
Page 15
Revision 3.0
Loading...
+ 183 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.