NEC Neax 2400 Imx Fusion Network System Manual

							CHAPTER 8 ND-70185 (E)
Page 176
Revision 3.0
EX- FCCS
EX-FCCS Features
3. The node that requires the data programming or data change for Number Portability depends on the
pattern. See Figure 8-5 and Table 8-2 that explain the eight patterns.
Figure 8-5   Patterns of Number Portability
Note 1:
Destination node
Note 2:Node to be connected to the FUG where the new number is added
Note 3:Node where Telephone Number is located before the Number Portability activation
4. Telephone Numbers used in the other FUG and the connected NEAX2000 IVS
2 system are managed
in the new table in NDM (the table differs from the existing table for Telephone Numbers used in self
FUG).
(a) Telephone Number data in a NEAX2000 IVS
2 is managed in the NDM of NCNs within all
FUGs and the NEAX2000 IVS2.
(b) Telephone Number data in a NEAX2400 IMX is managed in the NDM of NCN within all
FUGs. 
Table 8-2 Patterns of Number Portability
NO.PATTERN 
(Telephone Number is moved from A to B)NODE REQUIRED DATA CHANGE
Moving a number within the same FUG NCN in Center FUG
Moving a number in an FUG to another FUG NCN in Center FUG
Moving a number in a FUG to a NEAX2000 IVS
2NCN in Center FUG + NEAX2000 IVS2 Note 1
Adding a new number to an FUG NCN in Center FUG + NEAX2000 IVS
2 Note 2
Moving a number in a NEAX2000 IVS
2 to an FUG NCN in Center FUG + NEAX2000 IVS2 Note 3
Moving a number from a NEAX2000 IVS
2 to another 
NEAX2000 IVS2NCN in Center FUG + a NEAX2000 IVS2 Note 3
+  another NEAX2000 IVS2 Note 1
Moving a number within the same NEAX2000 IVS
2NEAX2000 IVS2 Note 1, Note 3
Adding a new number in an NEAX2000 IVS
2NCN in Center FUG + NEAX2000 IVS2 Note 1
LEGEND: EX-FCCS : Fusion Group (FUG) : FCCS
6
2
FUG(A)IVS2
8
5
1
FPC1 
NCN(A)FPC2
FPC4 FPC3
FUG(B)
FPC1 
NCN(B)FPC2
FPC3 FPC4
3
4
7
IVS2
: Enhanced CCIS
1
2
3
4
5
6
7
8 
						

							ND-70185 (E) CHAPTER 8
Page 177
Revision 3.0
EX- FCCS
EX-FCCS Features
5. Up to a maximum of 120,000 Telephone Numbers may be assigned in the entire Enhanced CCIS/EX-
FCCS network (including Telephone Numbers in the NEAX2000 IVS2) and a maximum of 48,000
per FUG (not to exceed 120,000 per total network). 
3.2 Centralized-MAT for EX-FCCS
[Centralized Maintenance]
(a) NEAX2000 IVS
2
1. MAT software for NEAX2400 IMX system and NEAX2000 IVS2 system are installed on a PC called
the “MAT.” Depending on the system logged into determines the MAT software used.
2. To log in the NEAX2000 IVS
2 system, Point Code of the system is designated. 
3. See the manual describing NEAX2000 IVS
2 for the method of checking the log-in user.
4. The data transmission speed between NEAX2000 IVS
2 and NEAX2400 IMX may be a maximum of
64Kbps since the CCH card is used.
(b) NEAX2400 IMX 
1. All systems in the EX-FCCS network can be maintained by one MAT.
2. To log in to the NEAX2400 IMX system, assign FUG no. to designate the desired Fusion Network
Group (FUG) and FPC to designate the desired node in the FUG. 
3. The user ID and password written in the NDM of each FUG is checked when logging into the
NEAX2400 IMX. This data is programmed using the AUIDN command.
4. When any of the conditions below are met, the MAT is logged into the node designated by the FPC,
but within the FUG where the MAT is installed regardless of entered FUG no. data. 
 No data is assigned to SELF_ FUG (Fusion Group number in the self-FUG) in AFUGN command. 
 FUG requested by the MAT is 0
 FUG requested by the MAT is the FUG number of self-FUG
5. The existing system (not NEAX2400 IMX) can not be maintained via the Centralized-MAT for EX-
FCCS. 
6. Time required for transmitting the 1Mbyte data (1 block of DM) is 2 hours at 64Kbps data speed/1
hour at 128Kbps data speed/15 minutes at 512Kbps data speed.
Note:The number of MAT to be installed may vary depending on the customer specification (one or two MAT can
be used to centralize the MAT operation or three or more MATs can be used to separate the MAT
operation). 
						

							CHAPTER 8 ND-70185 (E)
Page 178
Revision 3.0
EX- FCCS
EX-FCCS Features
[Centralized Traffic Collecting]
1. The feature to collect traffic information of NEAX2000 IVS
2 system is activated by logging in to the
NEAX2000 IVS2 node with Centralized-MAT for EX-FCCS using the traffic collecting command
dedicated for NEAX2000 IVS2 system.
2. For IMX systems, logging in to the NCN of each FUG with Centralized-MAT activates the feature to
collect traffic information.
[Centralized System Management Report]
1. This function is controlled by the Centralized-MAT for EX-FCCS only.
2. The Centralized-MAT for EX-FCCS connected to Center Office collects fault information by polling
all of the nodes (NEAX2400 IMX and NEAX2000 IVS
2 ).
3. When a fault occurrs at a NEAX2000 IVS
2 system, only basic fault information is collected by the
Center Office using the polling method. To collect more detail information, log in to the system where
the fault has occurred.
4. The buffer for fault information of the NEAX2400 IMX and NEAX2000 IVS
2 systems is separate.
There are a maximum of 64 buffers per site. Therefore, the fault that occurrs when the buffer is full
can not be stored at the center system. The center system sends a NACK signal to the system with the
fault. After a predetermined time, the system with the fault attempts to resend the information. 
5.Table 8-3 shows the controllability of the fault information indication received from the NEAX2000
IVS
2 system: (1) alarm indication LED of the TOPU, (2) “IMX MAT Menu” displayed on the MAT,
(3) DFTD command operation
Note:Available when the alarm grade is changed via ALMG command.
6. The fault information of the NEAX2000 IVS
2 received at the Center Office is cleared by the RALM/
RALMN command.
Table 8-3 NEAX2000 IVS2 Fault Information
× : Controllable   – : Not controllable
Connection 
MethodSMJ/SMN Lamp 
on TOPUMenu Display 
on MATDFTD 
command
IVS
2 to IMX Enhanced CCIS ––
Note–
IMX (A) to IMX (B) within an FUG FCCS –××
FUG (A) to FUG (B)EX-FCCS
××× 
						

							ND-70185 (E) CHAPTER 8
Page 179
Revision 3.0
EX- FCCS
EX-FCCS Features
7. When the fault information occurring at all FUGs is managed by the Centralized-MAT for EX-FCCS,
the destination for the output of the fault message must be changed to the designated Center Office
(for example, NCN) at each LN (including NEAX2000 IVS
2 System). See Figure 8-6.
Figure 8-6   Centralized Maintenance - EX-FCCS
W hen collecting the fault information of nodes (including the connected NEAX2000IVS ) at each FUG,  
 
When collecting the fault information of all FUGs and connected NEAX2000IVS  s at one MAT in FUG (A),[E xam ple D ata]
[E xam ple D ata]
LEGEND
: EX-FCCS : Fusion Group (FUG) : AIarm Occurrence : FCCS
NEXT 
1NEXT 
2NEXT 
3NEXT 
4
FUG (A)
PC=1
A larm  Info.PC=3PC=2
A larm  In fo .
Centralized-MAT-FCCS
NEXT 
8NEXT 
7NEXT 
6NEXT 
5
FUG (B)
PC=6
A larm  In fo .PC=4PC=5IV S2
Alarm Info.
C e ntra lized -M A T-FC C S
NEXT 
1NEXT 
2NEXT 
3NEXT 
4
FUG (A)
PC=1
A larm  Info.PC=3PC=2
A larm  Info.
Centralized-MAT for EX-FCCS
NEXT 
8NEXT 
7NEXT 
6NEXT 
5
FUG (B)
PC=6
A larm  In fo .PC=4PC=5
A larm  Info.
2
2
FU G  (A ) 
PC1- the node of Centralized M anagem ent Report-CCIS is PC2 
NEXT1,3,4-ASYDL,SYS1,INDEX532 (the CN of Centralized M aintenance-Fusion) is FPC of NEXT2 
NEXT2-ASYDL,SYS1,INDEX532 (the CN of Centralized Maintenance-Fusion) is 0 
FU G  (B ) 
PC6-the node of Centralized M anagem ent Report-CCIS is PC5 
NEXT5~7-ASYDL,SYS1,INDEX532 (the CN of Centralized Maintenance-Fusion) is FPC of NEXT8 
NEXT2-ASYDL,SYS1,INDEX532 (the CN of Centralized Maintenance-Fusion) is 0 
 
 
F U G  (A ) 
PC1-the node of Centralized M anagem ent Report-CCIS is PC2 
NEXT1,3,4-ASYDL,SYS1,INDEX532 (the CN of Centralized Maintenance-Fusion) is FPC of NEXT2 
NEXT2-ASYDL,SYS1,INDEX532 (the CN of Centralized Maintenance-Fusion) is 0 
F U G  (B ) 
PC6-the node of Centralized M anagem ent Report-CCIS is PC3 
NEXT6~8-ASYDL,SYS1,INDEX532 (the CN of Centralized M aintenance-Fusion) is FPC of NEXT5 
NEXT5-ASYD,SIS1,INDEX184 and 185 (the node of Centralized M anagem ent Report-CCIS) is PC3 
             ASYDL,SYS1,INDEX532 (the CN of Centralized Maintenance-Fusion) is 0 
 
  IV S
2
IV S2IV S2
: Enhanced CCIS 
						

							CHAPTER 8 ND-70185 (E)
Page 180
Revision 3.0
EX- FCCS
EX-FCCS Features
3.3 CCIS Features Activated with EX-FCCS
1. CCIS features in Table 8-4 are available in EX-FCCS network.
Table 8-4 CCIS Service in EX-FCCS Network
Note:
Telephone Numbers should be used for activating CCIS services through the network.
Note 1:This feature is available on the condition that the NEAX2000 IVS2 is the satellite office.
Note 2:This feature is available for calling number display only
FEATURE
CODEFEATURE NAMENETWORK CONFIGURATION
without 
NEAX2000 IVS
2with
NEAX2000 IVS2
A-44 ASYNCHRONOUS DATA SWITCHING - CCIS×
A-45 ATTENDANT CAMP-ON WITH TONE INDICATION - CCIS×× Note 1
B-9 BUSY VERIFICATION - CCIS×× Note 1
C-44 CALL BACK - CCIS×× Note 1
C-45 CALL FORWARDING-ALL CALLS - CCIS××
C-46 CALL FORWARDING-BUSY LINE - CCIS××
C-47 CALL FORWARDING-DON’T ANSWER - CCIS××
C-50 CALL TRANSFER-ALL CALLS - CCIS××
C-52 CALLING/CALLED NUMBER DISPLAY - CCIS×× Note 2
C-54 CALL TRANSFER-ATTENDANT - CCIS×× Note 1
C-55CENTRALIZED BILLING - CCIS 
Note:
Message Format is the same as before.×× Note 1
C-56 CENTRALIZED DAY/NIGHT MODE CHANGE - CCIS×× Note 1
C-57 CENTRALIZED SYSTEM MANAGEMENT REPORT - CCIS××
D-68 DATA PRIVACY ON DEMAND - CCIS×
D-71 DIAL ACCESS TO ATTENDANT - CCIS×× Note 1
D-72 DIGITAL DISPLAY-STATION - CCIS×
D-74 DIRECT-IN TERMIANTION - CCIS××
D-75 DISTINCTIVE RINGING - CCIS××
D-76D DO NOT DISTURB-D
term - CCIS××
E-8 EXECUTIVE RIGHT-OF-WAY - CCIS×
H-12 HOTLINE - CCIS××
M-34 MESSAGE REMINDER - CCIS×
M-34D MESSAGE REMINDER-D
term - CCIS×
M-38 MISCELLANEOUS TRUNK RESTRICTION - CCIS×
N-37 NAME DISPLAY - CCIS××
S-52 SERIAL CALL - CCIS×
S-53D SERVICE DISPLAY-D
term - CCIS×
S-57 STATION-TO-STATION-CALLING - CCIS××
S-59 STEP CALL - CCIS×
S-60 SYNCHRONOUS DATA SWITCHING - CCIS×
S-73 SUPERVISORY CALL - CCIS×
T-26 TOLL RESTRICTION-3/6DIGIT - CCIS×
V-7 VOICE CALL - CCIS×× 
						

							ND-70185 (E) CHAPTER 8
Page 181
Revision 3.0
EX- FCCS
EX-FCCS Features
2. Unique PCs (Point Codes) in the CCIS network connected with EX-FCCS are required. 
Figure 8-7   PC Assignment in EX-FCCS Network
3. The CCH to be used is selected as follows.
1) when the call is processed using the speech line (Bch), the outgoing/incoming route, Logical Route
(LRT), decides CCH.
LRT → PC → CSCG → CCH 
2) when the call is processed without speech line (Bch) - inter-office service such as CALL BACK,
MESSAGE WAITING service, MCI, etc., the called party’s number or PC of the destination decides
CCH. 
(a) the called party’s number → LRT → PC → CSCG → CCH
(b) PC → CSCG → CCH
3) when logging into NEAX2000 IVS
2 or remote FUG from the Centralized-MAT, PC of the node to
be logged in decides CCH. 
(a) NEAX2000 IVS
2 
PC → CSCG → CCH
(b) Remote FUG 
FUG+FPC → PC → CSCG → CCH
*FUG and FPC to be designated for log-in are converted automatically within the system. 
 All PCs used in the network must be different.
FUG1
 
PC1 
PC2
 
PC4  
PC3
FUG2
PC5
FPC2 
PC6
FPC3 
PC7FPC4 
PC8  
FUG3
FPC1 
PC9FPC2 
PC10
FPC4 
PC12FPC3 
PC11   PC13
PC14 (For the system to be connected with the next system via CCIS link or the large sized network, this assignment is  
required.)
FPC1 FPC2
FPC3 FPC4FPC1 IVS
2IVS2
LEGEND: EX-FCCS
: Fusion Group (FUG) : FCCS
: Enhanced CCIS 
						

							CHAPTER 8 ND-70185 (E)
Page 182
Revision 3.0
EX- FCCS
EX-FCCS Features
3.4 Centralized Message Center Interface - EX-FCCS
This section explains the conditions of Centralized Message Center Interface feature within EX-FCCS Net-
work. This feature provides an interface to the external CPU for Message Center (MC) information when
a specified UCD group in the network is called. This interface allows external control of Message Waiting
Lamp (MWL) indications on equipped PBX stations.
Note:Calls terminated to a UCD hunt group within a FUG will output MCI data to the Centralized MCI output
port for that FUG if assigned. Each FUG that requires a message center interface must have a message
center interface assigned within the FUG,
 The number of digits to be indicated for MCI message (in case 7 or 8-digit Telephone Number is used)
is determined by the following system data.
ASYD SYS1, INDEX246, b3. Maximum valid number of MCI digits is, 0/1=6 digits/8 digits.
Note:MCI equipment must be able to support 8-digit numbers.
 Centralized MCI feature is activated by assigning MCI equipment and UCD group at Centralized Of-
fice for the specific FUG. (MCI message cannot be transferred to the Centralized Office via EX-FCCS.)
(a) Message data is transferred to the offered MCI (connected to Node B) in FUG1, given that a call from 
a station in IVS
2 node terminates to a UCD station (in Node A shown in the figure) within FUG1 via 
EX-FCCS.
(b) Message data is transferred to the offered MCI (connected to Node B) in FUG1, given that a call from 
any station within FUG2 terminates to a UCD station within FUG1 via EX-FCCS.
(c) If a call from Node F terminates to a UCD station in Node E, the message cannot be transferred to the 
MCI connected to the Centralized Office. In this case, the message is sent to the MCI connected to 
Node H within FUG2.
(d) Message data is transferred to the shared MCI (connected to Node H) in FUG2 when a call from any 
station terminates to a UCD station in the same Fusion Group.
Node
ANode
CNode
DNode
E
MCIMCI FUG1 (Center FUG)
FUG2
IVS
(a)UCD
B NodeNode
H
EX-FCCS
FCCS (Fusion Call Control Signal)Direction of a call Direction of MCI message
Node
GNode
F
UCD
UCD
(b)(c)
(d)
2IVS2
Enhanced CCIS 
						

							ND-70185 (E) CHAPTER 8
Page 183
Revision 3.0
EX- FCCS
EX-FCCS Features
 Call Waiting Lamp Controll information is sent from the MCI within Center FUG to other Fusion
Groups and NEAX2000 IVS2 system via CCIS.
 When the Centralized Office adopts the ICS MCI format method, the receiving message field is output
as it is. When in the IMX MCI format method, the originating information field is also output to Tele-
phone Number field.
FUG1 (Center FUG)
Node
ANode
CNode
DNode
E
MCIMCI FUG2
IVS
UCDUCD
UCD
Node
H
EX-FCCS
FCCS (Fusion Call Control Signal)
Direction of a call Direction of MCI message
Node
GNode
F
Call Waiting Lamp ControllingIVSB Node22
Enhanced CCIS 
						

							CHAPTER 8 ND-70185 (E)
Page 184
Revision 3.0
EX- FCCS
EX-FCCS Features
3.5 Centralized Billing - EX-FCCS (Polling Method)
This section explains the conditions of Centralized Billing feature within EX-FCCS Network.
 Two methods of administering Centralized Billing information are available: either the CCIS billing
method or the FCCS billing method.
 When a 7-digit or 8-digit EX-FCCS Telephone Number is used in the network, for the NEAX2000
IVS
2 system, the EX-FCCS Telephone Number is output to Station Number field and the Office Code
field of the originating party.
As Telephone Number is not used in ICS text format, when 7 or 8 digits Telephone Number is used in
the network, the number is converted to Office Code and Station Number, then the Station Number is
output to Station Number field of originating party, and the Office Code is output to Office Code field
of originating party.
 When the Centralized Billing Office adopts the CCIS billing method, receiving message field is output
as it is.
 When the Centralized Billing Office adopts the Fusion billing method, the information field of origi-
nating call is also output to Telephone Number field.
ICS Format
1 2 3 4 5 8 12 14 19 98 0
S
T
XStation Number of
Originating Party  
last 6 digits of
Telephone Number
Office Code
of Origina-  
ting Party   
first 2 digits
of Telephone
Number
S

AU

AKAR T T K TNE
T
X

 
						

							ND-70185 (E) CHAPTER 8
Page 185
Revision 3.0
EX- FCCS
Data Programming
4. Data Programming
This section explains how to assign a brand-new EX-FCCS network data.
There are some conditions for data programming to be required for EX-FCCS.
1. When connecting a stand-alone NEAX2400 IMX, non-fusion system (via EX-FCCS) or a NEAX2000
IVS
2 using  Enhanced CCIS feature to an existing FUG:
(a) The system must be the NCN.
(b) The system is programmed as the Fusion Network configured by one NCN only.
(c) Use the NDM of the system to program the network data.
2. When connecting the NEAX2400 IMX system and the NEAX2000 IVS
2 system, CIC (Circuit Identifica-
tion Code) =1 should always be assigned using ACIC2 command.
3. ACSCL command data (CCH location per CSCG) must be programmed against the PC of the connected
NEAX2400 IMX or NEAX2000 IVS
2 system using ACIC1 command.