NEC Neax 2400 Imx Fusion Network System Manual
Here you can view all the pages of manual NEC Neax 2400 Imx Fusion Network System Manual. The NEC manuals for Communications System are available online for free. You can easily download all the documents as PDF.
Page 31
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...
Page 32
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) -...
Page 33
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...
Page 34
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...
Page 35
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...
Page 36
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...
Page 37
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)...
Page 38
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...
Page 39
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...
Page 40
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...