NEC Neax 2400 Ipx Fusion Network System Manual

							CHAPTER 4 NDA-24299
Page 56
Revision 1.0
INSTALLATION
Connecting Cables
Figure 4-16 shows some typical examples where 10 BASE-T cables are connected to the FCH card(s) mounted
in PIM3 of 1-IMG system, under the following conditions:
Table 4-9 Connection of 10 BASE-T Cables to FCH Card(s) in PIM3 of 1-IMG
Note 1:
Cables contained in each cable unit are as follows:
SR1201 ETIF CAU-D: UTP CTG5 ST CA-N, UTP CTG5 ST CA-J
SR1201 ETIF CAU-DD: UTP CTG5 ST CA-L, UTP CTG5 ST CA-J, UTP CTG5 CRS CA-F
Note 2:The cables cited in Figure 4-16 can be used in the 1-IMG system only.
Figure 4-16   Examples of Ethernet Cable Connection-FCH in PIM3 (1-IMG System) (1/2)Configuration
of CPUConfiguration
of LANUsed Cable Unit
(Note 1, Note 2)Number of HUB/
FCH
Pattern 1 Single Single SR1201 ETIF CAU-D × 1 HUB× 1, FCH× 1
Pattern 2 Dual SingleSR1201 ETIF CAU-D × 1
SR1201 ETIF CAU-DD × 1HUB× 2, FCH× 2
Pattern 3 Single Dual SR1201 ETIF CAU-D × 2 HUB× 2, FCH× 2
Pattern 4 Dual DualSR1201 ETIF CAU-D × 2
SR1201 ETIF CAU-DD × 2HUB× 2, FCH× 2
ATTENTIONContents
Static Sensitive
Handling
Precautions R equired
06 04 05 03 02 01 0006 04 05 03 02 01 00
CNCN
HUB
BASEU
UTP CTG5 ST CA-J
FA NU
BSCM
FCH
CN
CN
UTP CTG5 ST CA-N
PIM 1
PIM 2
PIM 3
PIM 0
LPM
TOPU
< F C H  in  P IM 3 (P a ttern 1 )>   < F C H  in  P IM 3 (P a ttern 2 )>  
06 04 05 03 02 01 00
06 04 05 03 02 01 00
CN
CN
CN
CN
UTP CTG5 ST CA-J
CNFCH
HUB
CN
CN
HUB
BASEU
PIM 1
PIM 2
PIM 3
LPM
CN
TOPU
FANU
PIM 0
BSCM
UTP CTG5 CRS CA-F
CNFCH
CN
UTP CTG5 ST CA-N
UTP CTG5 ST CA-L
FCH (PA-FCHA)HUB (PA-M96)
TP0-X TP1-X TP2-X
TP3-X TP4-X TP5-X
TP6-X
TP7-X
10 BASE-T
Connectors for 10 BASE-T
FRONT VIEWFRONT VIEW
CN= 10  BASE-T Connector
Use 10  B AS E-T connectors.  
						

							NDA-24299 CHAPTER 4
Page 57
Revision 1.0
INSTALLATION
Connecting Cables
Figure 4-16   Examples of Ethernet Cable Connection-FCH in PIM3 (1-IMG System) (2/2)
ATTENTIONContents
Static Sensitive
Handling
Precautions Required
06 04 05 03 02 01 0006 04 05 03 02 01 00
CN
CNCN
CN
HUB
CN
CNHUB
BASEU
PIM 1
PIM 2
PIM 3
UTP CTG5 ST CA-J
PIM 0
LPMFANU
BSCM BSCM
CN
FCH
CN
UTP CTG5 ST CA-J
FCH
CN
CN
UTP CTG5 ST CA-N
TOPU
06 04 05 03 02 01 00
06 04 05 03 02 01 00
CN
CN
CN
CNCN
CNUTP CTG5 ST CA-J
CN
FC H
HUB
CN
HUB
BASEU
PIM 1
PIM 2
PIM 3
LPM
CN
CN
FANU
PIM 0
CN
FCH
CN
UTP CTG5 ST CA-N
UTP CTG5 ST CA-L
UTP CTG5 ST CA-J
TOPU
   
Note:When dual LANIs are used in both Slot 00 and 03 of CPR (Pattern 3 or 4), be sure to use at least two
HUB cards: One HUB for internal LANI (in Slot 00) and the other for external LANI (in Slot 03).
However, if this is the case, and FCH is also in a dual configuration, the 10 BASE-T “cr os s”
connection between the HUBs is not required.  
						

							CHAPTER 4 NDA-24299
Page 58
Revision 1.0
This page is for your notes. 
						

							NDA-24299 CHAPTER 5
Page 59
Revision 1.0
CHAPTER 5 DATA PROGRAMMING
This chapter explains how to set Fusion network data, using the following data categories:
System Data
Numbering Plan Data
Station Data
Fusion Link Data
Figure 5-1 shows the overall data programming procedure:
Figure 5-1   Data Programming Flow Chart
AFMU
ANPD ANPDL
STN
SSC
SSCA
OGC
OGCA
LCR
LCRS
UNIF
:
:
:
------------
SSC
------
OGC
OGCA
LCR
LCRS
:
:   
:
TELN           Note
ASDT
System Data
Numbering Plan Data
Station Number Data
ACRD
ACRD
ACTKMBCTAFCHAFPC
AFPC
ACANAFRT
ASYDN
ASYDL
Fusion Link Data
with FCH
w/o FCH
ALRTN
Physical Number
ALGNL
ALGSL
Telephone Number
ALGNN
ALGSN
Telephone Number
: Available command at NCN. Note: Telephone Number is
           available only in self
           node. NCN:
LN:
ASPA ASPAL
ANPDN
 -----
SSC
SSCA
OGC
OGCA
LCR
LCRS
:
:
:
:
ASPAN
   TELN 
						

							CHAPTER 5 NDA-24299
Page 60
Revision 1.0
DATA PROGRAMMING
Network Data Programming Summary
1. Network Data Programming Summary
This section provides a summary of the data programming of Fusion systems.
1.1 Brand-new Fusion Network
To install the Fusion network as a brand-new system, follow the overall data programming procedure
below.
1.1.1 System Data
Decide an NCN and LN on the network.
Assign System Data for each node. Use the ASYDN command for the NCN and the ASYDL
command for all nodes. The system data includes the size of LDM, NDM, Fusion Point Code
(FPC), etc.
Note:The data becomes effective by executing “Non-Load Initial” after setting the FPC.
Assign unit data using the AFMU command for each node that exists on the network. Note that the
AFMU command is available at NCN only.
Assign Logical Route Numbers for all routes (external trunk) on the network using the ALRTN
command. Note that the ALRTN command is available at NCN only.
1.1.2 Numbering Plan Data
ANPDN → ASPAN (for NCN only): Assign numbering plan data for telephone number.
ANPDL → ASPAL (for NCN and LN): Assign numbering plan data for Service Codes, Trunk
Access Codes, etc., other than STN (physical station) and TELN.
ANPD → ASPA (for NCN and LN): Assign numbering plan data for Physical Station Number using
STN.
Note:The Numbering Plan data for the LDM and/or NDM cannot use separate Tenant Numbers (TN), so be sure
to assign the following data on the ASYDL command.
ASYDL command, SYS1, INDEX 800
b1 = 1 (ASPAL command tenant data table development on LDM = Common)
b2 = 1 (ANPDL command tenant data table development on LDM = Common)
1.1.3 Station Numbering
Assign Telephone and/or Physical Station Numbers using the following command:
ALGNN → ALGSN: Assign telephone number on the network. (NCN only)
ASDT: Assign Physical Number for each node as required. (available for NCN and LN) 
						

							NDA-24299 CHAPTER 5
Page 61
Revision 1.0
DATA PROGRAMMING
Network Data Programming Summary
1.1.4 Fusion Link Data
Assign the Fusion link data using the following commands:
Fusion with FCH:ACRD →  ACTK →  ACAN →  MBCT →  AFCH →  AFPC →  AFRT
Fusion w/o FCH:ACRD →  ACTK →  ACAN →  MBCT →                AFPC
1.2 Upgrading a CCIS Network
To install the Fusion system to an existing CCIS network, follow the overall programming procedure
below:
1.2.1 System Data
Decide an NCN and LN on the network.
Assign System Data for each node. Use the ASYDN command for NCN and the ASYDL command
for LN. The system data includes the size of LDM, NDM, Fusion Point Code (FPC), etc. 
Note:The data becomes effective by executing “Non-Load Initial” after setting the FPC.
Assign unit data using the AFMU command for each node that exists on the network. Note the
AFMU command is available at NCN only.
Assign Logical Route Numbers of all routes (external trunk) on the network using the ALRTN
command. Note that the ALRTN command is available at NCN only.
1.2.2 Numbering Plan Data
ANPDN →  ASPAN (for NCN only): Assign numbering plan data for telephone number.
When “Operator Call” or “Priority Call (ATT)” is used on the Fusion network, replace the existing
numbering plan data for these features using the ANPDL and ASPAL commands.
Note:The Numbering Plan data for the LDM and/or NDM cannot use separate Tenant Numbers (TN), so be sure
to assign the following data on the ASYDL command.
ASYDL command, SYS1, INDEX 800
b1 = 1 (ASPAL command tenant data table development on LDM = Common)
b2 = 1 (ANPDL command tenant data table development on LDM = Common)
1.2.3 Station Numbering
Assign telephone numbers using the following commands:
ALGNN →  ALGSN: Assign telephone number at network level. (NCN only)
1.2.4 Fusion Link Data
Assign the Fusion link data using the following commands:
Fusion with FCH: ACRD →  ACTK →  ACAN →  MBCT →  AFCH →  AFPC →  AFRT
Fusion w/o FCH: ACRD →  ACTK →  ACAN →  MBCT →                AFPC 
						

							CHAPTER 5 NDA-24299
Page 62
Revision 1.0
DATA PROGRAMMING
Network Data Programming Summary
Note:
When the Fusion system is incorporated in an existing CCIS network, all nodes must be linked via CCIS on
the network.
If there are any nodes linked via ACIS alone, add the CCIS link before installing the Fusion link. (See
Figure 5-2.) Refer to CCIS-related manuals for more detailed information.
1.3 Fusion Link Data
Assign the Fusion link data using the following commands:
Fusion with FCH: ACRD ➔ ACTK ➔ MBCT ➔ AFCH ➔ AFRT ➔ AFPC ➔ AC A N
Fusion w/o FCH: ACRD ➔  AFPC
Note:When the Fusion system is incorporated in an existing CCIS network, all nodes must be linked via CCIS on
the network.
If there are any nodes linked via ACIS alone, add the CCIS link before installating the Fusion link. (See
Figure 5-2 below.) Refer to CCIS-related manuals for more detailed information.
Figure 5-2   Fusion-CCIS Network
  
...
...
...
...
......
...
...
...
......
...
...
...
......
...
...
...
...
Node A 
PC=10
80
Node B
PC=11
81 Node C
82CCIS ACIS
PSTN
  
... ...
...
...
......
...
...
...
......
...
...
...
......
...
...
...
...
  
...
...
...
...
......
...
...
...
......
...
...
...
......
...
...
...
...
Add CCIS link.
PC: Point Code (CCIS)
PC=12 
						

							NDA-24299 CHAPTER 5
Page 63
Revision 1.0
DATA PROGRAMMING
Network Data Programming Summary
Figure 5-3 shows how to upgrade an existing CCIS network, focusing on the Numbering Plan. The example data 
setting assumes the existing network uses this particular numbering. For more detailed information on how to assign 
telephone numbers, see Assignment of Telephone Numbers.
Figure 5-3   How to Upgrade the Numbering Plan Data of an Existing CCIS Network
 
Before Upgrading
STN: 2000
A
CB
80
82
81
STN: 2000
STN: 2000 CCIS
CCIS
PSTN
13-H 
1 .  xx xx xxxx  0010 1222 
4.  x0010 1110  10110 1FFF  
7.  E23C  CAAB12  000 0000
CCIS network
ATTCON 0
PC=10
PC=12PC=11
MAT
9
PC: Point Code
STN: 2000LSTN: 430000
8280
81
STN: 2000
STN: 2000 CCIS
CCIS FCCSFCCS
PSTN
13 - H  
1.  x xxx  xx xx  0010 1222 
4.  x 0010 1110 10110 1FF F 
7. E23C C AAB12 000 0000
CCIS-Fusion network
ATTCON 0
PC=10
PC=12 FPC=3PC=11
MAT
9
PC: Point Code FPC: Fusion Point Code
Numbering Plan Data of Node A
(before upgrading)
Numbering Plan Data of Node A
(after upgrading)
100: Priority Call 1 (ATT) 
101: Priority Call 2 (ATT) 
102: Priority Call 3 (ATT) 
2xxx: Physical STN 
8x: CCIS access code 
9: CO call 
 0: Operator Call 
 
- Numbering Data (example)
100: Priority Call 1 
101: Priority Call 2 
102: Priority Call 3 
   0: Operator Call
- Numbering Data (example) Numbering Plan (Example) before Upgrading
Numbering Plan (Example) after Upgrading
After Upgrading
Assign this  using the ANPDN 
and ASPAN commands.
Numbering Plan Data for Telephone Numbers
To assign telephone numbers 4xxxxx, set the Numbering Plan data at Network Control Node (in this instance Node A) as follows:
ANPDN ASPAN
1st DC = 4     NND = 6 1st DC = 4     SSC = 16 (Logical Number)2xxx: Physical STN 
8x: CCIS access code 
9: CO call
4xxxxx: Telephone Number
FPC=1
FPC=2
TELN: 410000
TELN: 430000TELN: 420000
Assign these codes using ANPDL 
and ASPAL commands if these features 
are provided on the Fusion network. 
						

							CHAPTER 5 NDA-24299
Page 64
Revision 1.0
DATA PROGRAMMING
Assignment of System Data
2. Assignment of System Data
STEP 1: ASYDL and ASYDN
Assign the number of data memory blocks for the Network Data Memory (NDM) and the Local Data
Memory (LDM). Use the ASYDN command for the NCN. Use the ASYDL command for all nodes.
Figure 5-4 shows ASYDL Indexes 513 and 514 as an example.
Figure 5-4   Assignment of Memory Block
(1) Assign the following data to all nodes.
ASYDL, Index 513 Local Data Memory (LDM) usage
Assign 1 for bit(s) corresponding to the data memory block to be used as Local Data Memory (LDM).
Assign 01H for systems having 2M-LDM.
ASYDL, Index 514 Network Data Memory (NDM) usage
Assign 1 for bit(s) corresponding to the data memory block to be used as Network Data Memory (NDM).
Assign 01H for systems having 2M-NDM.
Allowable memory block of LDM and NDM assigned by ASYD are shown in Figure 5-5.
Figure 5-5   LDM and NDM Allocation (ASYDL)
(2) Assign the data to NCN only.
ASYDN, Index 514 Network Data Memory (NDM) usage
Assign 1 for bit(s) corresponding to the data memory block to be used as Network Data Memory (NDM).
Assign 01H for systems having 2M-DM.
NCN: Network Control Node 
LN: Local Node
ASYDN ASYDL
LN
LNLN LN
LNLN
LN LNNCN
Index 514 (NDM )=01H
ASYDLIndex 513 (LDM )=01H 
Index 514 (N DM )=01H Index 513 (LDM )=01H  
Index 514 (N DM )=01H
   
Note
Note:
ASYDL must be assigned at each node on the network.
Each bit corresponds to one block having 2M  Bytes.
    N D M  b lo ck s  
  (INDEX 514)
   LDM  blocks 
 (INDEX 513)
block #4
block #3
block #2
block #1
block #0
block #2
block #1
block #0
Relationship between Bit and Block Num ber
INDEX Bit   (Setting) M eaning
  513 
(LD M )
  514 
(NDM)0        (1 )
1        (0)  N ote 
2        (0)  N ote 
3        (0) 
4        (0 )
5        (0 )
6        (0 )
7        (0)
0        (1 )
1        (0)  N ote 
2        (0)  N ote 
3        (0)  N ote 
4        (0 )  N o te
5        (0 )
6        (0 )
7        (0)M em ory Block #0 
M em ory Block #1 
M em ory Block #2 
 
 
 
 
 
M em ory Block #0 
M em ory Block #1 
M em ory Block #2 
M em ory Block #3 
M em ory Block #4 
 
 
 Not used
Not used
Note:    These bits are normally assigned as 0 (i.e. 01H is normally set for both INDEX 513 and 514).  The flagging of the bit(s) 
             is possible but only if your system  should use the bit-corresponding M em ory Block(s) for som e reason. 
						

							NDA-24299 CHAPTER 5
Page 65
Revision 1.0
DATA PROGRAMMING
Assignment of System Data
STEP 2: ASYDL
Assign the self-Fusion Point Code (self-FPC) at each node. FPC ranges from 1 to 253. Use the
ASYDL command. (Index 512 b0-b7)
Index 512 self-Fusion Point Code
Assign a unique FPC for each node.
Figure 5-6 shows an example of FPC assignment.
Figure 5-6   Self-FPC Assignment
STEP 3: ASYDL
Assign the data of DP (Dial Pulse) relay broadcasting to Fusion Link using the ASYDL command
(Index 527, b4): 0/1=DP relay broadcasting is invalid/valid.
Note
Note:
Provided that the DP (10 or 20 pps) is set in the Signal Selecting for Outgoing C.O./Tie Line calls, assign
this data to bit4=1 (DP relay broadcasting is valid) when a call is originated at the node which doesn’t
accommodate C.O./Tie Line Trunk. The listed conditions for DTI circuit card have to be followed:
Firmware
PA-24DTR SP3010: Issue 11 or later
When PA-24DTR circuit card is used, turn the SW13/6C No.8 switch to OFF.
Figure 5-7   DP Signal Relay Broadcasting over Fusion Link (example)
NCN: Network Control Node 
LN: Local Node
LN
LNLNLN
LNLN
LN LN
NCN1
2 1011
1221
22
23 24
ASYDL Index 512 (b0-b7)
NECNE CNEC
DTIDTIDTIDTI
COT
TLT Private 
Network   P u b lic 
Network
FCCS
FCCS: Fusion Call Control Signal FCCSDP signal
DP signal Node A Node B Node C
Call Origination to  
C.O. line, Tie line
Originating NodeNode accommodating 
the C.O./Tie Line Trunk
ELC
Fusion Network