NEC Neax 2400 Imx Fusion Network System Manual

							CHAPTER 3 ND-70185 (E)
Page 16
Revision 3.0
SYSTEM CONFIGURATION
System Considerations
Condition 5: Up to eight (8) routes can be assigned as alternate routes for a connection trunk.
Figure 3-10   Connection Trunk Alternate Routing
Condition 6: Connection trunks and the Fusion data link must be assigned on an “associated” basis.
Figure 3-11   Fusion Network on an Associated Basis
Condition 7: One fusion data link must be assigned on each T1 link.
Condition 8: A maximum of eight (8) data links can be used for a connection trunk for redundancy.
A maximum of eight (8) alternate routes can be assigned  for Connection Trunks.
:
:
:
:
Node
Node
Node
Node
Node Alt-C_RT1
Alt-C_RT2
Alt-C_RT3
Alt-C_RT4
Alt-C_RT8
Node A
Node B
Alt-C_RT:  Alternate Connection Route
B ch
B ch D ch D ch
network on an associated basisnetwork on a quasi-associated basis
Node ANode B
Node C
B ch
D chD ch
Node ANode B
Node C
B ch: Connection Trunk        D ch: Fusion Data Link 
						

							ND-70185 (E) CHAPTER 3
Page 17
Revision 3.0
SYSTEM CONFIGURATION
System Considerations
Condition 9: The maximum of data link speed is “1.5 Mbps.”
Condition 10: Connection Trunks (B ch) conform to the following specifications:
 Existing external trunk cannot be used as alternate routes for connection trunks.
 Billing information on connection trunks cannot be output.
 Under the following conditions, “connection trunk seizure NG” will occur:
Data Link Failure
Connection Trunk all busy
LANI (built-in) - FCH failure
 Connection test for connection trunks is not provided.
 Nailed Down connection is not provided for connection trunks.
Specifications on Release 2 or earlier software:
 PAD value for connection trunks is fixed to 0 db.
 Echo canceller (EC) / MPC control is not provided.
 Nailed Down connection is not provided for connection trunks.
Condition 11: If a “ layer 2 failure” occurs, the connections are released.
Condition 12: When fusion links and CCIS links coexist on a Fusion network, the following conditions
should be considered: 
A Fusion link may be used as a CCIS link through data programming. In this instance, if the other node
accommodates a dedicated CCIS card, CCIS will not work even if the self-node accommodates a Fusion-
Link-Card. Therefore, the same Fusion-Link-Card must be accommodated at both nodes. Figure 3-13
shows an example of CCIS-FUSION networks. 
						

							CHAPTER 3 ND-70185 (E)
Page 18
Revision 3.0
SYSTEM CONFIGURATION
System Considerations
3.2 Centralized Billing - Fusion (Polling Method)
This section explains the conditions of Centralized Billing - Fusion, focusing on when CCIS links are in-
volved. To use this feature, select Center Node(s) on the Fusion network.
 
Figure 3-12   Centralized Billing - Fusion (1/3)
FCCS
FCCS
FCCS Fusion Network - Node A (Fusion - Center Node) collects the billing information of Nodes B and C via FCCS using polling method. - Example 1
billing information
      of Node C
billing information
      of Node B
- Example 2
- Example 3
CCIS
IMXnon IMX
CCIS
IMXnon IMX CCIS - Center Node
CCIS - Center Node
CCIS
IMXIMX
IMX
CCIS
IMX CCIS - Center Node
CCIS - Center Node In either case, Centralized Billing - CCIS is used.  (The size of call base table is 144 Bytes.)
In either case, Centralized Billing - CCIS is used.  (The size of call base table is 144 Bytes.)
IMX
IMXIMX
0!KK01090010030020210
100100100202070010010
0000000004111106341997
1225223209199712252314
010112345000000000008
................. Billing Format:  CCIS
144 Bytes Call Base Table
0!KK01090010030020210
100100100202070010010
0000000004111106341997
1225223209199712252314
010112345000000000008
................. Billing Format: CCIS
144 Bytes Call Base Table
0!KK01090010030020210
100100100202070010010
0000000004111106341997
1225223209199712252314
010112345000000000008
................. Billing Format:  CCIS
144 Bytes Call Base Table
0!KA01090010030020210
100100100202070010010
0000000004111106341997
1225223209199712252314
010112345000000000008
................. Billing Format:  CCIS
144 Bytes Call Base Table
Node A
Node A
Node A
Node A
Node C
Node B
Node B
Node B
Node B
12345566
451566465
876464646
646522130
0221313131
654654654
12345566
451566465
876464646
646522130
0221313131
654654654
polling
: Fusion Call Control 
  Signal (FCCS)
: Common Chanel 
   Inter-Office Signaling (CCIS)
SMDR equipment
polling
Fusion - Center Node
: Fusion Call Control
Signal (FCCS)
: Common Channel
Inter-Office Signaling (CCIS) 
						

							ND-70185 (E) CHAPTER 3
Page 19
Revision 3.0
SYSTEM CONFIGURATION
System Considerations
Figure 3-12   Centralized Billing - Fusion (2/3)
FCCS
FCCS
Fusion Network - Example 4
- Example 5
CCIS
IMX
IMXIMX
Node B
Node C
Fusion - Center Node
CCIS - Center Node
FCCS
Fusion Network
Fusion Network
CCISCCIS
CCIS
IMX
non IMX
non IMXIMX
IMX IMX
IMX
Fusion - Center Node
FCCS
FCCS
FCCS
Fusion - Center Node
DPC0: 
Node D
DPC0: 
Node C
DPC0: 
Node A
CCIS - Center Node
 Node A collects the billing information of Node B and Node C via FCCS using polling method.
 Node A sends the billing information of Node A, Node B, and Node C to Node D.

CCIS - Center Node
Node A
Node B
Node C
Node A
Node ANode B
Node C
Node DSMDR equipmentSMDR equipment SMDR equipment SMDR equipment
SMDR equipment
ignores
12345566
451566465
876464646
646522130
0221313131
654654654
12345566
451566465
876464646
646522130
0221313131
654654654
Billing Information
       of Node B
12345566
451566465
876464646
646522130
0221313131
654654654
Billing Information
       of Node B
Billing Information
       of Node Cpolling
12345566
451566465
876464646
646522130
0221313131
654654654
12345566
451566465
876464646
646522130
0221313131
65465465412345566
451566465
876464646
646522130
0221313131
65465465412345566
451566465
876464646
646522130
0221313131
654654654
Billing Information
       of Node B
12345566
451566465
876464646
646522130
0221313131
654654654Billing Information
       of Node C
polling
polling
polling
ignores
polling
 Node A tries to collect the billing information of Node B, and Node C via FCCS using polling method.
 (Node A cannot collect the billing information of Node C via FCCS.)
 Node C sends the billing information via CCIS, ignoring polling from Node A.
 Node C deletes the self-Point Code (CCIS) when requiring to send billing information for polling from Node A.
 Node A tries to collect the billing information of Node B via FCCS using polling method.
 (Node A cannot collect the billing information of Node B via FCCS.)
 Node B sends the billing information to Node C via CCIS, ignoring polling from Node A.
 Node B deletes the self-Point Code (CCIS) when requiring to send billing information for polling from Node A.
- Example 6
Billing Information
  of Nodes A, B, C 
						

							CHAPTER 3 ND-70185 (E)
Page 20
Revision 3.0
SYSTEM CONFIGURATION
System Considerations
Figure 3-12   Centralized Billing - Fusion (3/3)
FCCS
FCCS
FCCS
Fusion Network - Example 7
- Example 8
CCIS
IMX
IMXnon IMX IMX
DPC0: 
Node D
CCIS - Center Node
SMDR equipment
SMDR equipment Fusion - Center Node
FCCS
FCCS
FCCS
Fusion Network
CCIS
IMX
IMXnon IMX IMX
DPC0: 
Node B
CCIS - Center Node
SMDR equipment
SMDR equipment Fusion - Center Node
 Node A collects billing information of Node B and Node C via FCCS by polling method.
  (Billing information of Node B cannot be collected.)
 Node B sends billing information to Node D via CCIS, ignoring polling from Node A.
 Node B deletes the self-Node Point Code (CCIS) when Node B wants to send billing information.
 Node A collects the billing information of Node B, Node C, and Node D which are stored in Node B and Node C by polling method.
 Node D sends billing information to Node B.
Node ANode B
Node C
Node D
Node ANode B
Node C
Node D
12345566
451566465
876464646
646522130
0221313131
654654654
12345566
451566465
876464646
646522130
0221313131
65465465412345566
451566465
876464646
646522130
0221313131
654654654
Billing Information
       of Node B
Billing Information
       of Node BBilling Information
       of Node D
12345566
451566465
876464646
646522130
0221313131
654654654Billing Information
       of Node C
12345566
451566465
876464646
646522130
0221313131
654654654Billing Information
       of Node C
polling
polling
ignores
: Fusion Call Control 
  Signal (FCCS)
: Common Chanel 
   Inter-Office Signaling (CCIS)DPC           :  Destination Point Code
: Destination Point Code
: Fusion Call Control
Signal (FCCS)
: Common Channel
Inter-Office Signaling (CCIS) 
						

							ND-70185 (E) CHAPTER 3
Page 21
Revision 3.0
SYSTEM CONFIGURATION
System Considerations
3.3 Centralized Management Report-Fusion
To collect fault information in a Fusion network, the Centralized Management Report-Fusion is used. This
feature provides automatic reporting of fault occurrence from Local Nodes to Center Node. Service condi-
tions for this feature are shown below.
Figure 3-13   Centralized Management Report-Fusion
 Center Node for Centralized Management Report-Fusion is specified in the following system data:
ASYDL, SYS1, Index 532 (FPC of Center Node for Centralized Management Report-Fusion).
 At Center Node, system messages received from the other nodes are stored in the buffer memory for
Centralized Management Report-Fusion.
 The MAT connected to Center Node polls only the self-node.
 Office Name (ASYD, Index 96 through 115) is used for identification of each node.
 When a system message printer is connected to a node other than Center Node, system messages sent
to Center Node are also output to the system message printer.
 When a system message has been sent to Center Node, the message is regarded as an old message.
 When the system fails transmission of a system message to Center Node, retry operation is executed.
When the retry operation also fails, transmission is aborted and the message is to be sent together with
the next system message.
FCCSFCCS
FCCSFCCS
Centralized MATNode ANode B
Node C Node D
Fusion
13-H
1. xxxx xxxx 0010 1222
4. x0010 1110 10110 1FFF
7. E23C CAAB12 000 0000
NEC
Fault! 
						

							CHAPTER 3 ND-70185 (E)
Page 22
Revision 3.0
SYSTEM CONFIGURATION
System Considerations
The following explains service conditions for the network including both FCCS and CCIS links.
Example: 1When the network comprises FCCS and CCIS links
Figure 3-14   Centralized Management Report-Fusion (Example 1)
Node A: To send system messages to Node C via Office B, assign Point Code of Node C (12) to ASYD, SYS
1, Indexes 184 and 185.
Node  B: To send system messages to Node C, assign Fusion Point Code of Node C (3) to ASYDL, SYS1, Index
532. When this system data is assigned, system messages received from Node A are also transferred
to Node C. However, when data is not assigned (0), system messages received from Node A are ig-
nored and not transferred to Node C.
System messages received from Node A are not output to the system message printer connected to
Node B.
Node  C: Received system messages are stored in the memory area for Centralized Management Report-Fusion.
Node  D: To send system messages to Node C, assign Fusion Point Code of Node C (3) to ASYDL, SYS1, Index
532.
Centralized MAT
Center Node: Node CFusion
NEC
13-H
1. xxxx xxxx 0010 1222
4. x0010 1110 10110 1FFF
7. E23C CAAB12 000 0000
NEC
PRT
PC=10FPC=4
PC=11
FPC=2PC=12
FPC=3
Node B Node C
Node A Node DFCCS FCCS
CCIS 
						

							ND-70185 (E) CHAPTER 3
Page 23
Revision 3.0
SYSTEM CONFIGURATION
System Considerations
Example: 2
When both FCCS and CCIS links are established between two nodes
Figure 3-15   Centralized Management Report-Fusion (Example 2)
Node A/B/C:Refer to Example 1 on the previous page.
Node D: When Point Code of Node C (12) is assigned to ASYD, SYS 1, Indexes 184 and 185, System mes-
sages are sent to Node C using CCIS. When this system data is not assigned (0) and Fusion Point
Code of Node C (3) is assigned to ASYDL, SYS 1, Index 532, system messages are sent to Node C
using FCCS.
Centralized MAT
Center Node: Node CFusion
13-H
1. xxxx xxxx 0010 1222
4. x0010 1110 10110 1FFF
7. E23C CAAB12 000 0000
NEC
PC=10FPC=4
PC=11
FPC=2PC=12
FPC=3
Node B Node C
Node A Node DCCIS FCCS FCCS
CCIS 
						

							CHAPTER 3 ND-70185 (E)
Page 24
Revision 3.0
SYSTEM CONFIGURATION
System Considerations
Example: 3
When a node is linked with LAN interface
Figure 3-16   Centralized Management Report-Fusion (Example 3)
Node A: To send system messages to Node E, assign Point Code of Node C (1) to ASYD, SYS 1, Indexes
184 and 185.
Node B: To send system messages to Node E, assign Point Code of Node C (1) to ASYD, SYS1, Indexes
184 and 185. When this system data is assigned, system messages received from Nodes C and D
are also transferred to Node E. However, when this data is not assigned (0), system messages re-
ceived from Nodes C and D are ignored and not transferred to Node E.
System messages received from Nodes C and D are not output to the system message printer con-
nected to Node B.
Node C/D: To send system messages to Node E via Node B and Node A, assign Fusion Point Code of Node B
(11) to ASYDL, SYS 1, Index 532.
Node E: Received system messages are stored in the memory area for Centralized Management Report-Fu-
sion.
Centralized MATCenter Node: Node E
Fusion
NEC
13-H
1. xxxx xxxx 0010 1222
4. x0010 1110 10110 1FFF
7. E23C CAAB12 000 0000
NEC
PRT
PC=2FPC=12
PC=3
FPC=11FPC=10
Node B Node C
Node A
PC=1
Node ENode DFCCS
FCCS with LAN
CCIS
CCIS 
						

							ND-70185 (E) CHAPTER 3
Page 25
Revision 3.0
SYSTEM CONFIGURATION
System Considerations
3.4 Fusion  Attendant/Desk Console
3.4.1 Operator Call
An operator call can be placed from each node by assigning the access code using the ASPAL/ASPAN
command, which allows the user to specify an appropriate node on the Fusion network by entering the
FPC.  In this example, a station user at Node B can call up an operator at Node C or Node E by dialing
“90” or “91.”
Note 1:As regards the following data (Waiting Call Display data), be sure to develop the unified data at each node:
ASYD, SYS2, INDEX 8
ASYD, SYS2, INDEX 9
Note 2:When the connection routes (C_RT) are all busy, the operator call becomes in Night ATT mode.
Figure 3-17   Operator Calls on a Fusion Network
Node A
Node B
Node CNode D
Node E
90
90 91
 91
90
91
:   Node having ATTCON/DESKCON
:   Node w/o ATTCON/DESKCON
ASPAL - Node A

ACC: 90   SRV: SSC   
SID: 2 (operator call)
FPC = 3 (Node C) 
      
Fusion Network
Data Programming (Node A)Data Programming (Node D)
Data Programming (Node B) Operator Call
Operator CallOperator CallOperator Call
ASPAL  - Node D

ACC: 91   SRV: SSC   
SID: 2  (operator call)
FPC = 5 (Node E) 
      
ASPAL - Node B

ACC: 90   SRV: SSC   
SID: 2  (operator call)
FPC = 3 (Node C) 

ACC: 91   SRV: SSC
SID: 2  (operator call)
FPC = 5 (Node E)