ND-70185 (E) ISSUE 3 STOCK # 200869 ® Fusion Network System Manual MAY, 2000 NEC America, Inc.
LIABILITY DISCLAIMER NEC America, Inc. reserves the right to change the 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 Dterm are registered trademarks of NEC Corporation.
Issue No. PAGE No. 4 5 Issue No. PAGE No.
Issue No. PAGE No. Issue No. PAGE No.
Issue No. PAGE No. 1 2 3 1 2 3 144 1 2 145 1 2 146 1 143 4 5 Issue No. PAGE No.
ND-70185 (E) ISSUE 3 MAY, 2000 NEAX2400 IMX Fusion Network System Manual TABLE OF CONTENTS Page CHAPTER 1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2. How to Follow This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TABLE OF CONTENTS (CONTINUED) Page 3. Mounting Circuit Cards in PIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 3.1 Mounting HUB (PA-M96) in a PIM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 3.2 Mounting FCH (PA-FCHA) and DTI (PA-24DTR) Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 4. Connecting Cables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TABLE OF CONTENTS (CONTINUED) Page 8. Office Data Sheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 8.1 Data Sheet for AFMUPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 8.2 Data Sheet for ALRTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 8.3 Data Sheet for ANPD/ANPDL/ANDPN . . . . . . .
TABLE OF CONTENTS (CONTINUED) Page CHAPTER 7 TROUBLESHOOTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 1. List of Fusion-related System Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 2. 3-B PM C-level Infinite Loop (Permanent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 2.1 Repair Procedure . . . . . . . . . . . . . . . . . . .
LIST OF FIGURES Figure Title Page Figure 2-1 Figure 2-2 Figure 2-3 Figure 2-4 Figure 2-5 Figure 2-6 Figure 2-7 Figure 2-8 Figure 2-9 Figure 2-10 Figure 2-11 Figure 3-1 Figure 3-2 Figure 3-3 Figure 3-4 Figure 3-5 Figure 3-6 Figure 3-7 Figure 3-8 Figure 3-9 Figure 3-10 Figure 3-11 Figure 3-12 Figure 3-13 Figure 3-14 Figure 3-15 Figure 3-16 Figure 3-17 Figure 3-18 Figure 3-19 Figure 3-20 Figure 4-1 Figure 4-2 Figure 4-3 Figure 4-4 Figure 4-5 Figure 4-6 Figure 4-7 Figure 4-8 Figure 4-9 Figure 4-10 Figure 4-1
LIST OF FIGURES (CONTINUED) Figure Title Figure 5-2 Figure 5-3 Figure 5-4 Figure 5-5 Figure 5-6 Figure 5-7 Figure 5-8 Figure 5-9 Figure 5-10 Figure 5-11 Figure 5-12 Figure 5-13 Figure 5-14 Figure 5-15 Figure 5-16 Figure 5-17 Figure 5-18 Figure 5-19 Figure 5-20 Figure 5-21 Figure 5-22 Figure 5-23 Figure 5-24 Figure 5-25 Figure 5-26 Figure 5-27 Figure 5-28 Figure 5-29 Figure 5-30 Figure 5-31 Figure 5-32 Figure 5-33 Figure 5-34 Figure 5-35 Figure 5-36 Figure 5-37 Figure 5-38 Figure 5-39 Figure 5-40 Figure 5-
LIST OF FIGURES (CONTINUED) Figure Title Page Figure 5-51 Figure 5-52 Figure 5-53 Figure 5-54 Figure 5-55 Figure 5-56 Figure 5-57 Figure 5-58 Figure 5-59 Figure 6-1 Figure 6-2 Figure 6-3 Figure 6-4 Figure 6-5 Figure 6-6 Figure 6-7 Figure 6-8 Figure 6-9 Figure 6-10 Figure 6-11 Figure 6-12 Figure 6-13 Figure 6-14 Figure 6-15 Figure 7-1 Figure 7-2 Figure 7-3 Figure 7-4 Figure 7-5 Figure 7-6 Figure 7-7 Figure 7-8 Figure 7-9 Figure 7-10 Figure 7-11 Figure 7-12 Figure 7-13 Figure 7-14 Figure 7-15 Figure 7-16 F
LIST OF FIGURES (CONTINUED) Figure Title Figure 8-1 Figure 8-2 Figure 8-3 Figure 8-4 Figure 8-5 Figure 8-6 Figure 8-7 Figure 8-8 Figure 8-9 Network Connection Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NEAX2000 IVS2 to NEAX2400 IMX Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NEAX2400 IMX to NEAX2400 IMX Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LIST OF TABLES Table Title Page Table 4-1 Table 4-2 Table 4-3 Table 4-4 Table 4-5 Table 5-1 Table 5-2 Table 5-3 Table 7-1 Table 8-1 Table 8-2 Table 8-3 Table 8-4 SENSE Switch Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 MODE Switch Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 DIP Switch (SW14) Setting . . . . . . . . . . . . . . . . . . . . . . . .
This page is for your notes. LIST OF TABLES Page x Revision 3.
CHAPTER 1 INTRODUCTION 1. General 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 how to use this manual. • CHAPTER 2 (GENERAL) Outlines the Fusion system configuration and lists available service features. • CHAPTER 3 (SYSTEM CONFIGURATION) Explains the hardware configuration of the Fusion system.
INTRODUCTION Related Manuals 3. Related Manuals To complete the installation of the Fusion system, the following manuals are required: • NEAX2400 IMX Circuit Card Manual • NEAX2400 IMX Installation Manual • NEAX2400 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 1 Page 2 Revision 3.
CHAPTER 2 GENERAL 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 eliminate the constraints normally associated with network services that are offered using Common Channel Inter-Office Signaling (CCIS). 1.2 Use of Telephone Numbers A Fusion system allows you to use Telephone Numbers in addition to the existing station numbers.
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.
GENERAL Fusion System Configuration 3. Fusion System Configuration The Fusion system can be divided into the following two types. Figure 2-4 shows a Fusion system with Fusion Call Control Handler (FCH) cards. Node A Node B DTI DTI Fusion Link DTI Node C DTI 1.5M 4.9 ft. FCH FCH Dch: 64K-1.5M FCH Dch: 64K-1.5M 4.9 ft. 4.9 ft. HUB DTI 1.5M 4.9 ft.
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 the network. This node has the Centralized-MAT to collect fault information from other nodes on the network. Multiple nodes cannot be assigned as a Network Control Node. • Local Node All nodes other than Network Control Node are called Local Node.
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.
GENERAL Fusion Network Examples When the NDM (master) is modified, the new data is automatically copied. NCN LN LN DM DM DM LDM LDM LDM NDM (master) NDM NDM Change... copy copy Fusion Link The standard size of each memory is as follows: NCN: Network Control Node DM (Data Memory): 4M Bytes LDM (Local Data Memory): 2M Bytes NDM (Network Data Memory): 2M Bytes LN: Local Node Figure 2-8 Network Data Memory Copy 6.
GENERAL Fusion Network Examples 81: CCIS for Node B 82: CCIS for Node C 8x: CCIS access for CCIS Network 4x...: Fusion access [Open Numbering] CCIS Network "8x" IS CC NCN FCCS LN Node C "82" FPC= 3 Node A "80" FPC = 1 FCCS PC =10 CCIS CCIS LN Node B "81" FPC = 2 TELN PC = 12 TELN ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... 430000 420000 PC = 11 410001 410000 ... ... ... TELN TELN ... ... ... ... ... ... ... ... ... ... ... ...
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. ACIS T CO FCCS NCN FCCS Node B LN Node A calling party ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... TELN TELN 410000 430000 ... ... ... ... ... ... ... ... ... ... ... ... ... ...
CHAPTER 3 SYSTEM CONFIGURATION Fusion systems can be divided into the following two types: • Fusion system with FCH • Fusion system without FCH Fusion Call Control Handler (FCH): PA-FCHA Note: This chapter explains the system configuration of each Fusion system. 1. Fusion System without FCH A sample Fusion system configuration 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.
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 configuration, the Fusion link is established between nodes via the T1 link. Figure 3-2 shows a Fusion system configuration with FCH. This figure shows a Fusion System Configuration with FCH.
SYSTEM CONFIGURATION Fusion System with FCH 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. LANI#0-A CPU#0 DTI FCH0 .... LANI#0-B 10 Base T HUB0 to the same route HUB1 ....
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. 10 Base T 10 Base T PCI Bus DTI FCH LANI#0 CPU#0 .... HUB CPU#1 LANI#1 10 Base T PCI Bus Figure 3-6 Non-Redundant Configuration 3. System Considerations 3.1 Fusion Network Conditions This section explains how to design a Fusion network.
SYSTEM CONFIGURATION System Considerations Condition 2: A maximum of four (4) nodes can be connected as tandem nodes. max 4 nodes FCCS Node A FCCS Node B Node C FCCS Node D 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.
SYSTEM CONFIGURATION System Considerations Condition 5: Up to eight (8) routes can be assigned as alternate routes for a connection trunk. A maximum of eight (8) alternate routes can be assigned for Connection Trunks.
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.
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 involved. To use this feature, select Center Node(s) on the Fusion network. - Example 1 - Node A (Fusion - Center Node) collects the billing information of Nodes B and C via FCCS using polling method.
SYSTEM CONFIGURATION System Considerations - Example 4 • 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.
SYSTEM CONFIGURATION System Considerations - Example 7 • 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.
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 conditions for this feature are shown below. Node B FCCS Node D FCCS Fault! Node A FCCS 13-H 1. xxxx xxxx 0010 1222 4. x0010 1110 10110 1FFF 7.
SYSTEM CONFIGURATION System Considerations The following explains service conditions for the network including both FCCS and CCIS links. Example: 1 When the network comprises FCCS and CCIS links NEC PRT Node B PC=11 FPC=2 Node C FCCS 13-H 1. xxxx xxxx 0010 1222 4. x0010 1110 10110 1FFF 7.
SYSTEM CONFIGURATION System Considerations Example: 2 When both FCCS and CCIS links are established between two nodes Node B PC=11 FPC=2 Node C FCCS 13-H 1. xxxx xxxx 0010 1222 4. x0010 1110 10110 1FFF 7. E23C CAAB12 000 0000 PC=12 FPC=3 Centralized MAT Fusion FCCS CCIS NEC CCIS PC=10 FPC=4 Node A Node D Center Node: Node C Figure 3-15 Centralized Management Report-Fusion (Example 2) Node A/B/C:Refer to Example 1 on the previous page.
SYSTEM CONFIGURATION System Considerations Example: 3 When a node is linked with LAN interface NEC PRT Node B PC=3 FPC=11 CCIS CCIS Node C FCCS FPC=10 FCCS with LAN PC=2 FPC=12 Node A Node D Center Node: Node E 13-H 1. xxxx xxxx 0010 1222 4. x0010 1110 10110 1FFF 7.
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.
SYSTEM CONFIGURATION System Considerations 3.4.2 Central Office Incoming Call (Ring Down) Each node can specify a terminating node for Ring Down calls using the system data. In this example, Node A and Node D specify Node C and Node E as the terminating node respectively. The terminating node is assigned using the ASYDL command (SYS 1, Index 640). Note that self-FPC is assigned at the terminating node.
SYSTEM CONFIGURATION System Considerations 3.4.3 Day/Night Change Day/Night information is transferred from an ATTCON/DESKCON to predetermined nodes. In this example, Node C specifies Node A and Node B as destination nodes by assigning FPCs 1 and 2 in Indexes 704-735. Node A and Node B specifies Node C as a terminating node for Ring Down calls from PSTN by assigning FPC 3 in Index 640. Node E specifies Node D as a destination.
This page is for your notes. CHAPTER 3 Page 28 Revision 3.
CHAPTER 4 INSTALLATION This chapter covers the installation of the Fusion system. The following topics are covered: • How to set switches on the following circuit cards: PA-M96 (HUB) PA-FCHA (FCH) PA-24DTR (DTI) • How to mount the circuit cards • How to run the 10 BASE-T cables 1. Anti-Static Caution This manual provides Static Caution indicators on pages where work involving static-sensitive components is described. When performing work accompanied by this mark, be sure to use the anti-static kit.
INSTALLATION Anti-Static Caution Figure 4-2 shows the anti-static kit that is provided. Use the kit as shown below when handling static-sensitive components such as circuit cards and cables. Connect the ground wire to the earth terminal of the frame. PBX Earth Terminal Ground Wire Conductive Sheet Wrist Strap Ground Cable Figure 4-2 How to Use the Anti-static Kit CHAPTER 4 Page 30 Revision 3.
INSTALLATION Anti-Static Caution 1.1 Circuit Cards Required Depending on the system type, the following circuit cards are required to install the Fusion system: • Fusion with FCH HUB (PA-M96) FCH (PA-FCHA) DTI (PA-24DTR) • Fusion without FCH DTI (PA-24DTR) HUB (PA-M96) Before starting installation, make sure that all necessary cards are at your site.
INSTALLATION Key Setting on Circuit Cards 2. Key Setting on Circuit Cards 2.1 PA-M96 (HUB) Set the SEL switch on the HUB (PA-M96) card(s), after referring to Figure 4-4 and Table 4-1. OPE ATTENTION Card -M96) UB (PA MB Contents Static Sensitive Handling Precautions Required H ST7 CR7 ~ ~ CR0 ST0 246 E0 AC 246 0E C A SENSE TP7-X TP6-X TP5-X TP4-X TP2-X C A TP3-X 6 E0 2 4 ch wit . .
INSTALLATION Key Setting on Circuit Cards 2.2 PA-FCHA (FCH) Set the switches on the FCH (PA-FCHA) card(s) as shown below. This card has DIP switches, whose key settings determine the time slots of the Fusion link. In Figure 4-5, CH3 is designated as the D/I channel in an example.
INSTALLATION Key Setting on Circuit Cards Table 4-2 MODE Switch Setting SWITCH NAME SETTING MODE 0-7 DESCRIPTION Not used × 8 4 6 A E0 2 C STANDARD SETTING Standard setting (When the DTI is connected with the card’s front cable) Fusion link test mode (When the DTI is connected with the card’s front cable) 9 A-F Not used Table 4-3 DIP Switch (SW14) Setting SWITCH NAME SW14 1 2 3 SWITCH NUMBER SETTING STANDARD SETTING ON × 1 OFF DESCRIPTION Positive logic for the D/I CONT Negative lo
INSTALLATION Key Setting on Circuit Cards 2.3 PA-24DTR (DTI) There are two types of the PA-24DTR (DTI) card as shown below. Refer to Figure 4-6 and Table 4-4 to set each switch to the proper positions.
INSTALLATION Key Setting on Circuit Cards Table 4-4 Switch Setting Patterns for the DTI Card (Continued) SWITCH NAME 1 SW4D 1 3 2 4 5 6 SWITCH NUMBER 7 8 2 OFF 3 SETTING STANDARD SETTING ON OFF Transmission Signal A Logic: Negative × ON OFF 6 × ON 1 SW25 1 2 OFF 3 4 OFF × RMT Alarm Sending: To be sent out ON × Simultaneous Seizure Supervision: Not to be controlled OFF Simultaneous Seizure Supervision: To be controlled ON Data Link Control: MOS OFF × Multiframe Selectio
INSTALLATION Key Setting on Circuit Cards Table 4-4 Switch Setting Patterns for the DTI Card (Continued) SWITCH NAME SWITCH NUMBER 1 2 SETTING STANDARD SETTING ON OFF × ON × OFF SW39 1 2 3 4 5 6 7 8 3 OFF ON 5 7 × OFF ON PAD CONTROL ON ON Both directions OFF ON Receiving only ON OFF Sending only OFF OFF ARTD is fixed SW39-3 SW39-4 DATA PAD ON ON 64K OFF ON 56K ON OFF 48K OFF OFF 64K INV.
INSTALLATION Key Setting on Circuit Cards Table 4-4 Switch Setting Patterns for the DTI Card (Continued) SWITCH NAME SW6C 1 2 3 4 5 6 7 SWITCH NUMBER SETTING STANDARD SETTING 1 ON × Fixed 2 ON × Fixed 3 ON × Fixed 4 ON × Fixed 5 ON × Fixed 6 ON × Fixed 7 ON × Fixed 8 ON × Fixed 8 OFF 1 SW58 2 1 2 3 4 5 6 7 ON Equalizer Setting OFF ON OFF ON 8 OFF 3 MEANING OFF SW 58-1 SW 58-2 SW 58-3 DISTANCE ON ON ON 0 - 131 ft (0 - 040 m) ON ON OFF 13
INSTALLATION Key Setting on Circuit Cards Table 4-4 Switch Setting Patterns for the DTI Card (Continued) SWITCH NAME SWITCH NUMBER SETTING STANDARD SETTING Digital PAD ROM selection: Special specification ON SW5D 1 1 2 3 2 3 × Digital PAD ROM selection: Standard specification ON × LAYER2 signal logic: Positive OFF LAYER2 signal logic: Negative ON Line fault is not notified to the upper CPU × OFF 4 Note: OFF 4 OFF MEANING Line fault is notified to the upper CPU ON Zero Code Suppre
INSTALLATION Mounting Circuit Cards in PIM 3. Mounting Circuit Cards in PIM 3.1 Mounting HUB (PA-M96) in a PIM Mount the HUB (PA-M96) card in an appropriate slot of a PIM as shown below. When the MAT is connected via a HUB card, be sure to use a dedicated HUB for the Fusion link. Note: HUB (PA-M96) can be mounted wherever in a PIM of any IMG stack. However, if your system is 1-IMG type, mount the HUB in PIM0. Mount a HUB card in an appropriate slot providing the anti-static kit.
INSTALLATION Mounting Circuit Cards in PIM 3.2 Mounting FCH (PA-FCHA) and DTI (PA-24DTR) Cards Mount the FCH (PA-FCHA) and the DTI (PA-24DTR) card in appropriate slots in a PIM. Mount the two cards in adjacent slots since these cards must be connected on the front connectors. Figure 4-8 shows an example with the FCH and DTI cards mounted in PIM 1. This figure shows an example where FCH and DTI cards are mounted in PIM 1.
INSTALLATION Connecting Cables 4. Connecting Cables 4.1 Connecting DTI-FCH Front Cables Connect the furnished front cable to the connectors on the DTI and FCH cards. Use DTI and CN2 connectors on the FCH and DTI cards respectively. Since an FCH card is equipped with one Handler circuit, a maximum of five FCH cards can be connected to a DTI card. (See Figure 4-10.) However, if a DCH card is also cascaded, a maximum of three FCH cards can be added to the DTI card.
INSTALLATION Connecting Cables Since a maximum of five Handler circuits can be used, five FCH cards can be cascaded. Figure 4-10 shows an example where three FCH cards are cascaded. Since a maximum of five " Handler" circuits can be used, five FCH cards can be cascaded. This figure shows an example where three FCH cards are cascaded.
INSTALLATION Connecting Cables 4.2 Connecting 10 BASE-T Cables Figure 4-11 shows sample cable connections, where HUB (PA-M96) cards are provided in a dual configuration and the FCH (PA-FCHA) card is located in PIM 1 (1-IMG system/IMG0). When HUB cards are provided in a dual configuration, the two HUB cards must be connected on each front edge connector using a 10 BASE-T cross cable.
INSTALLATION Connecting Cables 4.3 10 BASE-T Connection Procedure The pattern for 10 BASE-T cable connections may vary, depending on the system configuration (such as number of IMG stacks or the mounting location/number of the FCH/HUB cards, etc.). According to your system configuration, connect necessary Ethernet cables: 4.3.1 Procedure for 1-IMG System If your system is 1-IMG type, the 10 BASE-T connection should use either of the following cables: 1. Cable unit specified as SR1201 ETIF CAU-n 2.
INSTALLATION Connecting Cables 4.3.3 When not using the cable unit SR1201 ETIF CAU-n When your system doesn’t use the cable unit classified as SR1201 ETIF CAU-n, perform the 10 BASET connections as instructed below: 1. Depending on your system configuration, connect the 10 BASE-T straight cable(s) between the HUB (PA-M96) and LANI (PZ-PC19) cards. Use the cable UTP CTG5 ST CA-O, which must be provided by the user.
INSTALLATION Connecting Cables When dual LANIs are used in both Slot 00 and 03 of CPR#0/CPR#1, be sure to use at least two HUB cards as separate 10 BASE-T connection terminals. Use one HUB for the internal LANI (LANI-A: in Slot 00 of each CPR) and use the other for the external LANI (LANI-B in Slot 03 of each CPR). 2. When the HUB is in a dual configuration, connect the 10 BASE-T cross cable between the HUB cards. Use the following cables, which are provided by the user.
INSTALLATION Connecting Cables When dual FCH is provided for the HUB dedicated to each internal LANI card (LANI-A: in Slot 00 of each CPR), connect FCH#0 to HUB#0 and FCH#1 to HUB#1. When your system also uses the external LANI cards (LANI-B in Slot 03 of each CPR), prepare another set of FCH cards for the HUB dedicated to the external LANI cards. Then, if the FCH is in dual configuration, connect one FCH to the HUB for No. 0 system of the external LANI, and the other to the HUB for the No.
INSTALLATION Connecting Cables Figure 4-13 shows some typical examples, where 10 BASE-T cables are connected to the FCH card(s) mounted in PIM0 of 1-IMG system, under the following conditions: Configuration of CPU Configuration of LAN Single Single Pattern 1 Pattern 2 Dual Single Pattern 3 Single Dual Pattern 4 Dual Dual Used Cable Unit (Note 1, Note 2) Number of HUB/ FCH SR1201 ETIF CAU-A × 1 HUB× 1, FCH× 1 SR1201 ETIF CAU-A × 1 SR1201 ETIF CAU-DA × 1 SR1201 ETIF CAU-A × 2 HUB× 2, FCH× 2
INSTALLATION Connecting Cables ATTENTION Contents Static Sensitive Handling Precautions Required TOPU TOPU PIM 3 PIM 3 PIM 2 PIM 2 FANU FANU PIM 1 PIM 1 UTP CTG5 ST CA-J UTP CTG5 ST CA-D CN CN CN CN CN HUB FCH FCH CN HUB HUB FCH FCH HUB 00 01 02 03 04 05 06 00 01 02 03 04 05 06 CN BSCM BSCM CN LPM CN CN CN CN CN CN CN CN UTP CTG5 ST CA-D CN CN CN CN PIM 0 PIM 0 UTP CTG5 ST CA-J 00 01 02 03 04 05UTP 06 00 01
INSTALLATION Connecting Cables Figure 4-14 shows some typical examples, where 10 BASE-T cables are connected to the FCH card(s) mounted in PIM1 of 1-IMG system, under the following conditions: Configuration of CPU Configuration of LAN Single Single Pattern 1 Pattern 2 Dual Single Pattern 3 Single Dual Pattern 4 Dual Dual Used Cable Unit (Note 1, Note 2) Number of HUB/ FCH SR1201 ETIF CAU-B × 1 HUB× 1, FCH× 1 SR1201 ETIF CAU-B × 1 SR1201 ETIF CAU-DB × 1 SR1201 ETIF CAU-B × 2 HUB× 2, FCH× 2
INSTALLATION Connecting Cables Figure 4-15 shows some typical examples, where 10 BASE-T cables are connected to the FCH card(s) mounted in PIM2 of 1-IMG system, under the following conditions: Configuration of CPU Configuration of LAN Pattern 1 Single Single Pattern 2 Dual Single Pattern 3 Single Dual Pattern 4 Dual Dual Used Cable Unit (Note 1, Note 2) Number of HUB/ FCH SR1201 ETIF CAU-C × 1 HUB× 1, FCH× 1 SR1201 ETIF CAU-C × 1 SR1201 ETIF CAU-DC × 1 SR1201 ETIF CAU-C × 2 HUB× 2, FCH×
INSTALLATION Connecting Cables A T T E N T IO N C ontents Static S ens itive H andling Prec autions R equired TO PU TO PU PIM 3 PIM 3 U TP C TG 5 ST C A -K CN CN CN CN P IM 2 P IM 2 FAN U UTP C TG 5 S T C A-M PIM 1 P IM 1 U TP CTG 5 ST CA -M UTP C TG 5 S T C A-J CN CN CN CN CN CN CN CN HUB HUB HUB HUB 00 01 02 03 04 05 06 00 01 02 03 04 05 06 CN BS C M B SC M CN LPM UTP C TG 5 S T C A-J U TP C TG 5 ST C A -J 00 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: Configuration of CPU Configuration of LAN Pattern 1 Single Single Pattern 2 Dual Single Pattern 3 Single Dual Pattern 4 Dual Dual Used Cable Unit (Note 1, Note 2) Number of HUB/ FCH SR1201 ETIF CAU-D × 1 HUB× 1, FCH× 1 SR1201 ETIF CAU-D × 1 SR1201 ETIF CAU-DD × 1 SR1201 ETIF CAU-D × 2 HUB× 2, FCH×
INSTALLATION Connecting Cables ATTENTIO N C o nte nts S tatic S en sitive H a nd ling P re cau tio ns R eq uired TO PU TO PU CN CN CN CN PIM 3 PIM 3 FC H FC H FCH FC H P IM 2 P IM 2 U TP C TG5 ST C A-N U TP C TG5 ST CA-N P IM 1 U TP C TG 5 ST C A-L FANU FANU P IM 1 U TP C TG5 ST C A-J CN CN CN CN CN CN CN CN CN CN CN CN P IM 0 P IM 0 HUB HUB HUB HUB 00 01 02 03 04 05 06 00 01 02 03 04 05 06 B SCM CN B SC M
This page is for your notes. CHAPTER 4 Page 56 Revision 3.
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: System Data NCN: ASYDN LN: ASYDL Numbering Plan Data AFMU ALRTN ANPD ANPDL ASPA ANPDN ASPAL STN SSC SSCA OGC OGCA LCR LCRS UNIF : : : ------ ------ SSC ------ OGC OGCA LCR LCRS : : : TELN ASPAN Note Note: Telepho
DATA PROGRAMMING Network Data Programming Summary 1. Network Data Programming Summary This section explains 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, the overall data programming procedure is as follows. 1.1.1 Note: • 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.
DATA PROGRAMMING Network Data Programming Summary 1.2 Upgrading a CCIS Network To install the Fusion system to an existing CCIS network, the overall programming procedure is as follows: 1.2.1 Note: • 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. The data becomes effective by executing “Non-Load Initial” after setting the FPC. 1.2.
DATA PROGRAMMING Network Data Programming Summary 1.3 Fusion Link Data • Assign the Fusion Link data using the following commands: Fusion with FCH: ACRD ➔ ACTK ➔ MBCT ➔ AFCH ➔ AFRT ➔ AFPC ➔ ACAN 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 the installation of the Fusion link (See Figure 5-2 below.
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, please see Assignment of Telephone Numbers. Before Upgrading CCIS network Numbering Plan Data of Node A (before upgrading) PSTN "9" ATTCON "0" A CCIS PC=10 CCIS 13-H 1. xxxx xxxx 0010 1222 4.
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. The ASYDN command is used at NCN only. Use the ASYDL command at all nodes.
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. This figure shows an example of FPC assignment. Assign a unique FPC for each node.
DATA PROGRAMMING Assignment of System Data Index 800 For ASYDL b0 : 0/1 = ALGNL, ALGSL on a UGN (TN) basis/b1 : 0/1 = ASPAL on a TN basis/b2 : 0/1 = ANPDL on a TN basis/b4 : 0/1 = AFRSL, ASTPL, AUNEL on a TN basis/b5 : 0/1 = ASTPL on a TN basis/b7 : 0/1 = AAEDL on a TN basis/- For ASYDN b0 : 0/1 = ALGNN, ALGSN on a UGN (TN) basis/b1 : 0/1 = ASPAN on a TN basis/b2 : 0/1 = ANPDN on a TN basis/b4 : 0/1 = AFRSN, ASTPN on a TN basis/b5 : 0/1 = ASTPN on a TN basis/b6 : 0/1 = ARSCN on a TN basis/b7 : 0/1 = AAE
DATA PROGRAMMING Assignment of FPC and MG and UNIT into Network 3. Assignment of FPC and MG and UNIT into Network 3.1 AFMU Assign the module accommodation data by giving Module Group Number and Unit Number on an FPC basis. This data is necessary to allocate unique Network ID (NID) to each MG/UNIT of the whole Fusion network nodes. Note This data can be set at the NCN only. Note: A unique NID is assigned to each MG/UNIT, automatically by entering the AFMU data.
DATA PROGRAMMING Assignment of Logical RT in Network DM (NDM) 4. Assignment of Logical RT in Network DM (NDM) 4.1 ALRTN/ARTKN This command is used to assign Logical Route Numbers to all external trunks used on a Fusion network. Assign unique Telephone Numbers to the whole route for external trunks on the network (including COT, DAT, Dummy Route, etc.) using this command. The data can be set at the NCN only and should be set for every external route in every node.
DATA PROGRAMMING Assignment of Numbering Data for Telephone Numbers The ALRTN command display should look similar to the following: ALRTN (Assignment of Logical RT in Network DM (NDM)) FPC (Fusion Point Code): 1 - 253 LGRT 1 LGRT (Logical Route Number): 1 - 899 RT 4 FPC 3 RT (External Route Number): 1 - 899 (Maximum) WRT? Y Figure 5-12 ALRTN Command Display 5. Assignment of Numbering Data for Telephone Numbers STEP 1: ANPDN Make a Telephone Numbering plan on the network.
DATA PROGRAMMING Assignment of Numbering Data for Telephone Numbers STEP 2: ANPDN Assign Pre-translation Data for the Telephone Numbers planned in Step 1 using the ANPDN command at NCN.
DATA PROGRAMMING Assignment of Numbering Data for Telephone Numbers STEP 3: ASPAN Assign special access code data for the Telephone Numbers using the ASPAN command. SRV=TELN is the data for Telephone Numbers.
DATA PROGRAMMING Assignment of Telephone Numbers 6. Assignment of Telephone Numbers This section explains how to program Telephone Numbers. To program Telephone Numbers, use ALGSN command. Telephone Number can be assigned to a station using the LENs or the Physical Station Number depending on programming. Note: The Fusion Link must be operational before programming telephone numbers in the Fusion Network.
DATA PROGRAMMING Assignment of Telephone Numbers ALGSN (Assignment of Telephone Station Data In Network) TYPE UGN 1 1 Telephone Number TELN 41000 FPC LENS 1 000100 WRT? Physical LENS Y For Help, press F1 NUM ALGSN (Assignment of Telephone Station Data In Network) TYPE UGN 2 1 TELN Telephone Number 41000 FPC 1 TN 1 STN 2000 WRT? Y Physical Station Number For Help, press F1 NUM Figure 5-19 ALGSN Command Display (example) ND-70185 (E) CHAPTER 5 Page 71 Revision 3.
DATA PROGRAMMING Assignment of Telephone Numbers 6.1 Assignment of Connection Route/Trunk Data STEP 1: ACRD Using the ACRD command, assign the connection route data of Fusion link. The data must be assigned for both B-channel and D-channel. Assign appropriate data referring to the Table 5-1. This figure shows an example of route number.
DATA PROGRAMMING Assignment of Telephone Numbers Table 5-1 Route Class Data Assignment CDN Node A Node B type B-channel D-channel B-channel D-channel RT C_RT: 10 C_RT: 11 C_RT: 12 C_RT: 13 Description 1 TF 3 3 3 3 Trunk Kind 3: Bothway (fixed) 2 TCL 4 4 4 4 Trunk Class: 4 (fixed) 3 RLP 2 2 2 2 Release Method : Assign 2-First Party Release. 4 SMDR 0 0 0 0 Assign 0.
DATA PROGRAMMING Assignment of Telephone Numbers Note: CDN 1: Trunk Kind 0-2: 3: Bothway Trunk CDN 2: TCL (Trunk Class) 0-3: 4: Fusion Trunk 5-31: - CDN 3: RLP (Release Pattern) 0: Calling Party Release 1: 2: First Party Release 3: - CDN 4: SMDR (SMDR for station-to-station call) Assign 0. CDN 5: LSG (Line Signal) 12: B channel for No.7 CCIS/ISDN 13: D channel for No.
DATA PROGRAMMING Assignment of Telephone Numbers CDN 10: FPEG (Fusion Trunk Peg Count) Assign 0. CDN 11: TC (Timer Class) 0: 1: 1 sec 2: 2 sec 3: 8 sec 4: 20 sec 5-7: - CDN 12: MTC (Miscellaneous Timer Counter) CDN 13: STSEQ (Status Enquiry) 0: 1: cancel CDN 14: FGH (Fusion Gateway Handler) Assign 0.
DATA PROGRAMMING Assignment of Telephone Numbers STEP 2: ACTK Assign the connection trunk data of both B-channel and D-channel using the ACTK command. Assign the Connection Equipment Number (C_LENS) referring to Figure 5-22 through Figure 5-25. The ACTK command display should look similar to the following.
DATA PROGRAMMING Assignment of Telephone Numbers Table 5-2 Data Programming Sheet for Regular Density Slot C_RT (1-1023) C_LENS C_TK(1-4095) MG U Time Slot Allocation G LV 1 0 0 0 0 1 0 2 0 0 0 0 1 1 3 0 0 0 0 1 2 4 0 0 0 0 1 3 5 0 0 0 0 1 4 6 0 0 0 0 1 5 7 0 0 0 0 1 6 8 0 0 0 0 1 7 9 0 0 0 0 2 0 10 0 0 0 0 2 1 11 0 0 0 0 2 2 12 0 0 0 0 2 3 13 0 0 0 0 2 4 14 0 0 0 0 2 5 15 0 0 0 0 2 6 16 0 0 0
DATA PROGRAMMING Assignment of Telephone Numbers 6.1.2 When FCH is Mounted in a High Density Slot If the FCH is to be mounted in the High Density Slot, the connection trunk data should be assigned as shown in the figures below. Figure 5-24 shows an example where these cards are mounted in Slots 11 and 12. The figure below shows an example where these cards are mounted in slots 11, and 12.
DATA PROGRAMMING Assignment of Telephone Numbers When the DTI cards is mounted in a double density slot, the C_LEN data for the FCH and DTI cards are as follows.
DATA PROGRAMMING Assignment of Telephone Numbers Table 5-3 Data Programming Sheet for High Density Slot C_RT (1-1023) 10 (B-ch) 11 (D-ch) CHAPTER 5 Page 80 Revision 3.
DATA PROGRAMMING Assignment of FCH Related Data STEP 4: MBCT Unbusy the connection trunk data assigned in the previous step using MBCT (Make Busy of Connection Trunk) command. This step is required for both B-channel and D-channel trunk. The MBCT command should look similar to the following.
DATA PROGRAMMING Assignment of FCH Related Data Figure 5-29 shows a sample data assignment when FCH cards are located in the PIM 0 slot 4 and PIM 2 slot 11. As an example, data assignment when FCH cards are accommodated in the following slots is shown here. PIM 0, slot 4 and PIM 2, slot 11 NEC Use "odd number" as the Group No. and "Level 0" for the FCHN. NEAX 2400 IMS FCH card example 1 (Regular-density slot 04) example 2 (High-density slot 11) FCHN=2 LENS 011190 PIM 2 Slot 11 DTI Slot No.
DATA PROGRAMMING Assignment of FCH Related Data STEP 2: AFRT (Fusion with FCH only) Assign connection route numbers as shown below using the AFRT command. LN LN LN FCHN = 1 CNT = 1 Node A C_RT : 10 NCN Self-Node 1 FCIC=1 FCIC=2 FCIC=n FCHN=1 TRK 1 TRK 3 : : TRK 10 TRK 31 FCIC=1 TRK 32 FCIC=2 : : FCIC=n TRK 40 Node B LN 2 C_RT=10 LN LN Figure 5-29 AFRT Sample Data Sheet The AFRT command display should look similar to Figure 5-30.
DATA PROGRAMMING Assignment of FCH Related Data STEP 3: AFPC Assign FCH routing data using the AFPC command. A maximum of 8 connection routes and FCHN/ FPCN can be assigned on a node basis. FCHN is used for Fusion System with FCH. FPCN is used for Fusion System without FCH. The list box labeled FCH on the AFPC command determines the system type. Assign “0” for Fusion System without FCH and “1” for Fusion System with FCH. In this step, the explanation is given using the following network as an example.
DATA PROGRAMMING Assignment of FCH Related Data The table in Figure 5-33 shows a sample data sheet for Node A on a Fusion network with FCH. Assign the data for all nodes including the nodes which are not directly connected on the network. For example, in this figure Node C and Node D are not directly connected to the network.
DATA PROGRAMMING Assignment of FCH Related Data STEP 4: ACAN Assign the Fusion Connection Index Code (FCIC) and the LENs on an adjacent FPC basis. Figure 534 shows a sample data sheet for Node A. Note: It is not necessary to assign the same number as trunk and FCIC. However, FCIC numbers between adjacent nodes must be identical. A sample data sheet at Node A is as follows.
DATA PROGRAMMING Assignment of FCH Related Data 7.1 Assignment of Access Code for Tandem Connection via FCCS - ACIS For Release 3 or later software, tandem connection via FCCS - ACIS link can be established. Using LDM, appropriate routing data for each node can be assigned as shown in the following example. Example of Fusion Network LGRT:200 COT ACIS LGRT:100 COT LGRT:300 ACIS COT FCCS ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... FCCS ... ... ... ...
DATA PROGRAMMING Assignment of FCH Related Data STEP 1: ANPDN/ANPDL Note Assign the first digit of the OGC access code. When the access code is common to all nodes, use the ANPDN command. When the access code is assigned for each node, use the ANPDL command. 1st DC=9 CI=N (Normal) NND=1 1st DC=9 CI=H (Hooking) NND=1 STEP 2: ASPAN/ASPAL Note Assign the OGC access code. When the access code is common to all nodes, use the ASPAN command.
DATA PROGRAMMING Assignment of FCH Related Data 7.1.2 OGCA A procedure for assigning OGCA access code is explained using the following example. Node B Node C BUSY FCCS ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... COT LGRT:100 STN (C) FCCS Station C dials 9-1-303-456-7890 PSTN LGRT:200 COT Node A 1-303-456-7890 Figure 5-37 Example of OGCA STEP 1: ANPDN/ANPDL Note Assign the first digit of the OGCA access code.
DATA PROGRAMMING Assignment of FCH Related Data STEP 3: ANNDL/AMND Assign the necessary number of digits using the ANNDL or the AMND command depending on the route data. • When the ARTD command OSGS is 2 (Second Dial Tone), use the ANNDL (Necessary Digits Data) command. RT=100 OG NND=12 RT=200 OG NND=12 • When the ARTD command OSGS is 4/6/7 (Sender Immediate Start/Sender Delay Dial Start/ Sender Wink Start), use the AMND command.
DATA PROGRAMMING Assignment of FCH Related Data STEP 1: ANPDN/ANPDL Note Assign the first digit of the LCR/LCRS access code. When the access code is common to all nodes, use the ANPDN command. When the access code is assigned for each node, use the ANPDL command. TN=1 1st DC=8 CI=N (Normal) NND=1 TN=1 1st DC=8 CI=H (Hooking) NND=1 STEP 2: ASPAN/ASPAL Note Assign the LCR/LCRS access code for a dummy route number. When the access code is common to all nodes, use the ASPAN command.
DATA PROGRAMMING Assignment of FCH Related Data STEP 5: ARTD/ARTDN Using ARTD, assign the following CDN data for the dummy route number. Note 1 CDN 6 (TCL)=1 or 4 (depending on requirement) CDN 7 (L/T)=1 CDN 13 (AC)=1 The other CDNs may be left default (data 0) for the dummy route. STEP 6: AFRSL/AFRSN Note 2 Using AFRSL, assign the Number Pattern Code (NPC) and the Outgoing Route Selection Pattern Number (OPR) for the dummy route number.
DATA PROGRAMMING Assignment of FCH Related Data 7.2 Data Assignment for 52M-SDH Interface This section explains the Fusion Connection with 52M-SDH interface, which is available for Release 4 or later software. The figures below explain the connection pattern.
DATA PROGRAMMING Assignment of FCH Related Data Specifications for the SDH data setting are described below. 1. When FCCS and CCIS links are used together in the network, the different route number must be assigned to each Connection Trunk (B-ch), Connection Link (D-ch), Speech Line for CCIS and Signal Line for CCIS.
DATA PROGRAMMING Assignment of FCH Related Data • Connection Link (for Data) C_RT: 11 TCL=4 LSG=13 STEP 3: ACTK Assign the Connection Trunk data for B-ch and D-ch. Example: (When using 512kbps (8ch) TS as Connection link) • Connection trunk (B-ch) C_RT: 10 • Note: TK: 1-664 CLENS: LEN for the SDT Connection Link (D-ch) C_RT: 11 TK: 1-8 CLENS: LEN for the FCH C_RT: 11 TK: 9-16 CLENS: LEN for the SDT Set the switch on the FCH card depending on the transmission speed.
DATA PROGRAMMING Assignment of FCH Related Data STEP 8: AFPC Assign the FCCS routing data. FPC: 1 (FPC of the adjacent node)FCCH: 1 (with FCCH) CRT: 10 FCHN: 2 STEP 9: ACAN Assign the CIC number to the connection trunk. FPC: 1 FCIC: 1-664 CLENS: LEN of the connection trunk STEP 10: AFCD Assign NAILED DOWN CONNECTION for the connection link established between FCCH and SDT. CHAPTER 5 Page 96 Revision 3.
DATA PROGRAMMING Assignment of FCH Related Data 7.3 FCCS Link via Internet/Intranet The system can exchange FCCS data via the Internet/Intranet. As shown below, an FCCS Link can be established by using the following features: 7.3.1 External Router Fusion over IP External Router This feature allows the system to exchange the FCCS data via the Internet/Ethernet. For this feature, an FCCS link is connected to an external router. FCCS signaling is exchanged via the Internet/Intranet.
DATA PROGRAMMING Assignment of FCH Related Data STEP 1: ACRD Assign Route Class Data of Speech Route, FCH, FGH routes, respectively. A sample data assignment is shown below. See 6.1 Assignment of Connection Route/Trunk Data for more detailed information.
DATA PROGRAMMING Assignment of FCH Related Data STEP 2: ACTK Assign the connection trunk data of DTI, FCH, and FGH cards, using the ACTK command. When assigning FCH, FGH trunk data, eight trunks must be set. A sample data assignment of FCH, FGH card is as follows. When FCH and FGH cards are mounted in the following slots with the specified RT numbers, data setting is as follows.
DATA PROGRAMMING Assignment of FCH Related Data STEP 3: AFCH Assign FCH number on an FCH circuit card basis. In the following example, FCHN=1 is assigned for the FCH circuit card. For the FGH card, FCHN assignment is not necessary. PBX RT10 Speech DTI Fusion Network AFCH command display FCH FCHN 1 RT11 Signal FCHEN 000030 Note 1 IP address: xxx.xxx.xxx.x RT15 HUB ROUTER Note 1 : This setting is a sample. FGH IP address: aaa.aaa.aaa.
DATA PROGRAMMING Assignment of FCH Related Data STEP 5: AFPC Assign internal LAN routing data. FPC (Fusion Point Code): Assign FPC number (1-253) of the Destination Node. FCCH: Assign "1". C_RT (Connection Router): 1-1023 FCHN/FPCN (FCH/FPC Number): Assign the FCH Number, specified in STEP 3. USE_GATE: Assign "1 (=Gateway function is used)".
DATA PROGRAMMING Assignment of FCH Related Data STEP 6: AETH Assign the external router routing data. FPC (Fusion Point Code): Assign FPC number (1-253) of the Destination Node. USE_GATE: Assign "1 (=use Gateway)". FCHN (FCH Number): Assign the FCH Number, specified in STEP 3. C_RT (Connection Route): 1-1023 DST_IP (Destination IP Address): Assign FGH IP address of the Destination Node. NEXT_IP (Next IP Address): Assign FGH IP address of the Next Node (Node to be passed to).
DATA PROGRAMMING Assignment of FCH Related Data STEP 7: ACAN Assign the Fusion Connection Index Code (FCIC) for the Next Node. FPC (Fusion Point Code): Assign FPC number of the Next Node (Node to be passed to). FCIC (Fusion Connection Index Code): Assign Fusion CIC of the Next Node (Node to be passed to). C_LENS (Connection_LENS): Assign DTI LENS data (Bch data), specified in STEP 2.
DATA PROGRAMMING Assignment of FCH Related Data 7.3.2 FCCS Networking over IP This feature allows the system to exchange both speech and FCCS signaling over Internet/Intranet. To establish/release a call, Q-sig is used between the system and the router. H.323 is used as a protocol between routers. Fusion network is realized via the Internet/Intranet. PBX PBX Speech H.
DATA PROGRAMMING Assignment of FCH Related Data STEP 1: ACRD Assign Route Class Data of Speech Route, FCH, FGH routes, respectively. A sample data assignment is shown below.
DATA PROGRAMMING Assignment of FCH Related Data STEP 3: MBCT Unbusy the connection trunk data assigned in the previous step, by using the MBCT command. This is required for FCH, FGH trunks as well as speech channels. STEP 4: AFCH Assign FCH number on an FCH circuit card basis. In the following example, FCHN=1 is assigned for the FCH circuit card. For the FGH card, FCHN assignment is not necessary.
DATA PROGRAMMING Assignment of FCH Related Data STEP 5: AETH Assign the FCCS routing data, when external router is used by specifying IP address. FPC (Fusion Point Code): Assign FPC number (1 - 253) of the Destination Node. USE_GATE: Assign "0 (= not use gateway)". FCHN (FCH Number): Assign the FCH Number, specified in STEP 4. C_RT (Connection Route): 1 - 1023 DST_IP (Destination IP Address): Assign FGH IP address of the Destination Node.
DATA PROGRAMMING Assignment of FCH Related Data STEP 6: ACAN Assign the Fusion Connection Index Code (FCIC) for the Next Node. FPC (Fusion Point Code): Assign FPC number of the Self-node. FCIC (Fusion Connection Index Code): Assign Fusion CIC of the Self-node. C_LENS (Connection_LENS): Assign DTI LENS data (Bch data), specified in STEP 2.
DATA PROGRAMMING Assignment of FCH Related Data STEP 8: AGIP Assign IP addresses of FGH card and its connected router. FCHEN (FCH Equipment Number): Assign LV0 data of FGH LENs. FGH_IP (FGH IP Address): Assign IP address of the FGH card. DG_IP (Default Gateway IP Address): Assign IP address of the router. ARP (ARP Frame Type): Assign "2 (= DIX spec.)". CONTTYP (Voice Channel Control Type): Assign "1 (= Server)".
DATA PROGRAMMING Assignment of FCH Related Data STEP 9: AFIP Assign the FCCS Networking over IP data for controlling Speech Channels between PBX and router. FCHN (FCH Number): Assign FCHN specified in STEP 4. FGHEN (FGH Equipment Number): Assign LV0 data of FGH LENs. LENS (Equipment Number of Qsig-Prime B channel): Assign basic LENS of the Speech Channels. Note 2 RT-ACC (Router Access Number): Assign the Router Access Number (max. 16 digits).
DATA PROGRAMMING Assignment of FCH Related Data 7.4 Flexible Routing - FCCS A Fusion trunk call can be routed via "non-Fusion" trunk (C.O. or Tie Line), if the Fusion trunks are all busy or Data Link Failure occurs at the FCH card, etc. This feature can be used since program software Release 5. Service Conditions • This feature may be activated when the Fusion trunks are all busy or FCCS Link Failure (Layer 2 down) occurs at the FCH card.
DATA PROGRAMMING Office Data Sheets 8. Office Data Sheets 8.1 Data Sheet for AFMUPL FUSION POINT CODE (FPC) 1-253 MODULE GROUP (MG) 0/1 UNIT 0-3 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 CHAPTER 5 Page 112 Revision 3.
DATA PROGRAMMING Office Data Sheets 8.2 Data Sheet for ALRTN LOGICAL ROUTE NUMBER (LGRT) 1-899 FUSION POINT CODE (FPC) 1-253 EXTERNAL ROUTE NUMBER (RT) 1-255 ND-70185 (E) REMARKS CHAPTER 5 Page 113 Revision 3.
DATA PROGRAMMING Office Data Sheets 8.3 Data Sheet for ANPD/ANPDL/ANDPN TENANT NUMBER (TN) CHAPTER 5 Page 114 Revision 3.
DATA PROGRAMMING Office Data Sheets 8.4 Data Sheet for ASPA/ASPAL TENANT NUMBER (TN) CONNECTION ACCESS KIND OF STATUS CODE SERVICE INDEX (ACC) (SRV) (CI) 1/2 MAX.
DATA PROGRAMMING Office Data Sheets 8.5 Data Sheet for ALGNL USER GROUP NUMBER (UGN) CHAPTER 5 Page 116 Revision 3.0 LOGICAL STATION NUMBER (LSTN) MAX.
DATA PROGRAMMING Office Data Sheets 8.6 Data Sheet for ALGSL (TYPE1) TYPE UGN 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 LSTN ND-70185 (E) LENS REMARKS CHAPTER 5 Page 117 Revision 3.
DATA PROGRAMMING Office Data Sheets 8.7 Data Sheet for ALGSL (TYPE2) TYPE UGN 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 CHAPTER 5 Page 118 Revision 3.
DATA PROGRAMMING Office Data Sheets 8.8 Data Sheet for ASDT TENANT NUMBER (TN) STATION NUMBER (STN) LINE EQUIPMENT NUMBER (LENS) MG U G SERVICE ROUTE TELEPHONE EQUIPMENT RESTRICTION FEATURE CLASS REMARKS CLASS CLASS (SFC) (RSC) (TEC) LV 0-15 0-15 1-31 ND-70185 (E) CHAPTER 5 Page 119 Revision 3.
DATA PROGRAMMING Office Data Sheets 8.9 Data Sheet for ACRD CONNECTION RT No.
DATA PROGRAMMING Office Data Sheets CDN CONNECTION RT No. (C_RT) 1-1023 FUNCTION (FUNC) 10 FPEG - Fusion-PEG (Fixed “0”) 0 = Nothing of FUSION-PEG 1 = Exist of FUSION-PEG 0 0 0 0 0 0 11 TC - Timer Class (Fixed “0”) 1 = 1 sec. 2 = 2 sec. 3 = 8 sec. 4 = 30 sec.
DATA PROGRAMMING Office Data Sheets 8.10 Data Sheet for ACTK CONNECTION ROUTE NUMBER (C_RT) 1-1023 CHAPTER 5 Page 122 Revision 3.
DATA PROGRAMMING Office Data Sheets 8.11 Data Sheet for AFCH FCCH NUMBER (FCHN) 1-255 LENS OF FCCH (FCHEN) REMARKS MG U G L 1 0 2 0 3 0 4 0 5 0 6 0 7 0 8 0 9 0 10 0 11 0 12 0 13 0 14 0 15 0 16 0 17 0 18 0 19 0 20 0 21 0 22 0 23 0 24 0 25 0 26 0 27 0 28 0 29 0 30 0 31 0 32 0 33 0 ND-70185 (E) CHAPTER 5 Page 123 Revision 3.
DATA PROGRAMMING Office Data Sheets FCCH NUMBER (FCHN) 1-255 CHAPTER 5 Page 124 Revision 3.
DATA PROGRAMMING Office Data Sheets 8.
DATA PROGRAMMING Office Data Sheets FUSION POINT CODE (FPC) 1-253 FCCH USE OR NOT USE (FCCH) 0/1 1 2 CONNECTION ROUTE (C_RT) 1-1023 FCCH NUMBER/FUSION POINT CODE NUMBER (FCHN/FPCN) 1-255/1-253 CHAPTER 5 Page 126 Revision 3.
DATA PROGRAMMING Office Data Sheets 8.13 Data Sheet for ACAN FUSION POINT CODE (FPC) 1-253 FUSION CIC NUMBER (FCIC) 1-4095 CONNECTION EQUIPMENT NUMBER (C_LENS) ND-70185 (E) REMARKS CHAPTER 5 Page 127 Revision 3.
DATA PROGRAMMING Office Data Sheets 8.14 Data Sheet for AFRT FCCH NUMBER (FCHN) 1-255 CHAPTER 5 Page 128 Revision 3.
DATA PROGRAMMING Office Data Sheets 8.15 Data Sheet for AETH DESTINATION FPC (FPC) 1-253 GATEWAY USING FLAG (USE_GATE) 0/1 FCCH NUMBER (FCHN) 1-255 CONNECTION ROUTE (C_RT) 1-1023 ND-70185 (E) DESTINATION IP ADDRESS (DST_IP) NEXT IP ADDRESS (NEXT_IP) CHAPTER 5 Page 129 Revision 3.
DATA PROGRAMMING Office Data Sheets 8.16 Data Sheet for AGIP LINE EQUIPMENT NUMBER OF FCCH (FCHEN) MG U CHAPTER 5 Page 130 Revision 3.0 G LV CLIENT/ VOICE FRAME IP ADDRESS SERVER CHANNEL QSIG-PRIME TYPE OF FGH IP FOR DEFAULT CONTROL LINK NUMBER CONNECTION ARP ADDRESS (LINK_NUM) MAX.
DATA PROGRAMMING Office Data Sheets 8.17 Data Sheet for AFIP FCH NUMBER (FCHN) LINE EQUIPMENT NUMBER OF FGH (FGHEN) MG U G LV LINE EQUIPMENT NUMBER OF QSIG-PRIME Bch (LENS) MG U G ND-70185 (E) ROUTER ACCESS NUMBER (RT_ACC) Max. 16 digits LV CHAPTER 5 Page 131 Revision 3.
DATA PROGRAMMING Office Data Sheets 8.18 Data Sheet for AFRFL TN FPC (1-253) CHAPTER 5 Page 132 Revision 3.0 ACC MAX.
CHAPTER 6 POST INSTALLATION TEST This chapter covers how to perform installation tests focusing on the Fusion Call Control Signal (denoted in the remainder of this manual as FCCS) connections, after hardware installation and data assignment.
POST INSTALLATION TEST Repair Procedure When LED Indicates Abnormality 1.1 How to check LYR LED 1. Confirm the LYR LED lights green on the front edge of the FCH (PA-FCHA) circuit card. (See “LED Indication (A)” in Figure 6-2.) When the LED lights green, the fusion link is established. 2. Make sure that any alarm LED is not ON (red/yellow). (See LED Indication (B) in Figure 6-2.) When all alarm LEDs are OFF, the DTI (PA-24DTR) card is in normal operation.
POST INSTALLATION TEST Repair Procedure When LED Indicates Abnormality • FCH (PA-FCHA) switch setting Make sure that the following keys are set properly: • • Dch TS designation (0ch - 23ch: SW11, SW12, SW13) • Data Link Signal Logic (positive/negative: SW14-1) • Fusion Data Link Speed (48/56/64 kbps: SW14-2, 3) • LAPD Signal Link (user/network: SW14-4) 24DTI (PA-24DTR) switch setting Make sure that the keys are properly set on the card. See the NEAX2400 IMX Circuit Card Manual.
POST INSTALLATION TEST Repair Procedure When LED Indicates Abnormality All 24 B-channels sent from the TSW are looped back to the TSW at Interface on the card. At this time, the adjacent node detects AIS signals. (See ① in the figure below.) 2. Line Loopback All 24 B-channels sent from the line are looped back to the line at Line Interface on the card. (See ② in the figure below.) 3. Payload Loopback All 24 B-channels sent from the line are looped back to the line at Speech Path Control Block on the card.
POST INSTALLATION TEST Repair Procedure When LED Indicates Abnormality 2.3 Test Procedure STEP 1: Set the MODE switch to 9 (Fusion Link Test) from 8 (standard setting) on the FCH card and initialize the circuit card by turning the MB switch ON→OFF (1) Change the mode switch (8 9). (2) Initialize the FCH card.
POST INSTALLATION TEST FCCS Network Connection Test Make sure that the LYR LED flashes at 60-INT. FCH (PA-FCHA) card When the result of test is OK, the LYR LED flashes. MB Flash LYR MNT EST3 Send Remains ON LB when available for Ethernet Receive Polarity of EST2 pair-wire is normal EST1 Receive Mode 8 DTI EST0 Link is established LOAD Remains ON when ready to broadcast data packets Note FCH Front View Front View Note: When the FCH is a “Root Bridge”, the LOAD LED remains ON.
POST INSTALLATION TEST FCCS Network Connection Test STEP 4: The call terminates on STN B. STEP 5: Confirm the speech condition is sufficient (no noise, not one-way speech, etc.). STEP 6: Replace the handset of STN A. STEP 7: Repeat the above steps for all Fusion links. Check 3.1.2 FCCS Call Termination Test STEP 1: Using the MBCT command, make busy all trunks in the origination route except the trunk to be tested at Node B. STEP 2: Lift the handset of STN B in Node B.
POST INSTALLATION TEST FCCS Network Connection Test 3.2 ATTCON Connection Test (via FCCS) Perform the ATTCON connection test, using the following procedure. Check 3.2.1 ATTCON Call Origination Test STEP 1: Dial the operator access code (normally “0”), from STN A in Node A. STEP 2: Confirm that the ATT lamp flashes and ringer sounds at each ATTCON in Node B. STEP 3: Answer the call by pressing the ATND key. STEP 4: Confirm the speech condition is sufficient (no noise, not one-party speech, etc.).
POST INSTALLATION TEST FCCS Network Connection Test 3.3 Line (LC, ELC, DLC Card) Connection Test (via FCCS) Perform the Line (LC, ELC, DLC Card) connection test, following the procedures listed below. Check 3.3.1 Line Origination Test: Confirmation of Physical/Telephone STN Number STEP 1: Connect the line circuit card to be tested to a telephone set in Node A (self-Node). STEP 2: Lift the handset of STN A and confirm DT (Dial Tone). STEP 3: Place a call to an ATTCON or Dterm in Node B.
POST INSTALLATION TEST FCCS Network Connection Test 3.4 3-party Conference Trunk Function Test (via FCCS) Perform the 3-party conference trunk function test, following the procedures listed below. STEP 1: Using the MBTK Command, make busy all 3-party Conference Trunk (CFTs) except the trunk to be tested. Check STEP 2: Establish a station-to-station connection between STNs A and B in self node (Node A).
POST INSTALLATION TEST Fusion and Non-Fusion Connection Tests 3.5.1 Primary Route Trunk Test Check STEP 1: Using the MBCT command, make busy all trunks in the primary route except the trunk to be tested. STEP 2: Lift the handset of STN A in self-node (Node A). STEP 3: Dial the Telephone Number of STN B which belongs to other node (STN B). STEP 4: Confirm the speech condition is sufficient (no noise, not one-way speech, etc.). STEP 5: Replace the handset of STN A.
POST INSTALLATION TEST Fusion and Non-Fusion Connection Tests 4.1 When Seizing a Trunk from a Station Check STEP 1: Using the MAT command, make busy all trunks in the route except the trunk to be tested. STEP 2: Station A in self-node (Node A) dials the Physical Station Number for Station B in Node C. STEP 3: The call terminates to Station B via FCCS and non-FCCS. STEP 4: Confirm the speech condition is sufficient (no noise, not one-way speech, etc.). STEP 5: Replace the handset of STN A.
POST INSTALLATION TEST SDT Card Loopback Test 5. SDT Card Loopback Test The patterns for loopback test, which can be set by the SDT card, are as follows: 1. Local Loopback Loopback tests are performed only on the SDT card at the self-node. 2. Remote Loopback Loopback tests are performed between different nodes. The result of this test can be confirmed not at the self-node, but at the distant node.
POST INSTALLATION TEST SDT Card Loopback Test STEP 2: Make sure that the “LPB” lamp on the PA-SDTA card, or the “SYCxx” lamp on the PA-SDTB card lights steady-green. STEP 2.5: When the loopback pattern is “local loopback,” confirm that the “OPT” and “SYNC” lamps are both OFF on the PA-SDTA card. (“OPT” and “SYNC” lamps are OFF = Result of loopback test is fine) STEP 3: Return the key settings of the P-SW key (on PA-SDTA card: see Figure 6-15) to the original position. CHAPTER 6 Page 146 Revision 3.
CHAPTER 7 TROUBLESHOOTING This chapter explains the Fusion-related system messages that may be displayed, together with procedures on how to repair the indicated failure. If the message is displayed, follow the procedure described in each system message. For more information on the other system messages, see the NEAX2400 IMX System Operations and Maintenance Manual. 1. List of Fusion-related System Messages Table 7-1 List of Fusion-related System Messages No.
TROUBLESHOOTING List of Fusion-related System Messages Figure 7-1 shows a sample system configuration. The number of cards and cables may vary depending on the system. This figure shows an example of system configuration. Note that the number of cards and cables may vary depending on the system. TOPU : 10 BASE-T cable : Front Cable FCH DTI CN FCH CN System Message CN DTI CN CN PIM 1 13-H "Signaling Link Failure" 1. 0001 0000 0000 0000 2.
TROUBLESHOOTING 3-B PM C-level Infinite Loop (Permanent) 2. 3-B PM C-level Infinite Loop (Permanent) This message is displayed when a C-level program abnormal state has been detected as permanent. When the abnormal state is detected by the Port Microprocessor (PM) on an FCH card, the PM places the card into make-busy status. If the failure occurs more than 15 times an hour, the system judges the failure as permanent, issuing 3-B system message. 1. xx00 0000 0000 0000 2. 0000 0000 0000 0000.........
TROUBLESHOOTING 3-B PM C-level Infinite Loop (Permanent) [How to Replace FCH card] 1) Provide the anti-static kit. ATTENTION 2) Turn ON the MNT 3 switch. (make-busy-request) Contents Static Sensitive Handling Precautions Required 3) Make sure that system message (23-W) "FCH Alternate Routing (Start)" is displayed. 4) Turn the MB key upward. (make-busy) FCH (PA-FCHA) 5) Disconnect the front cable from the FCH card with care. MB 6) Extract the FCH card from the slot.
TROUBLESHOOTING 3-C PM C-level Infinite Loop (Temporary) 3. 3-C PM C-level Infinite Loop (Temporary) This message is displayed when the C-level program has been detected as abnormal by the Port Microprocessor (PM) mounted on the FCH (PA-FCHA) card. In this instance, the system performs an appropriate restart (B-monitor/Initial restart) according to the frequency of the failures. If the frequency exceeds 15 times an hour, it is judged as permanent. See "3-B PM C-level Infinite Loop (Permanent)". 1.
TROUBLESHOOTING 3-E PM Lockup Failure (Temporary) 4.1 Repair Procedure STEP 1: Make sure that station-to-station connections can be established in the PIM containing the indicated FCH (PA-FCHA) card. If the station-to-station connections cannot be established, the PIM is faulty. Repair the PIM. Otherwise, move to STEP 2. STEP 2: Initialize the FCH card using the MB key. See Figure 7-3 “How to Initialize FCH (PA-FCHA) Card.
TROUBLESHOOTING 13-H/I/J Signaling Link Failure (Permanent)/(Temporary)/(Recovery) 6. 13-H/I/J Signaling Link Failure (Permanent)/(Temporary)/(Recovery) This message is displayed when the Fusion link (D-ch) has a failure. If the failure occurs frequently, the system displays 13-H Signaling Link Failure (Permanent). The shaded area in the figure listed below is related to this message.
TROUBLESHOOTING 13-H/I/J Signaling Link Failure (Permanent)/(Temporary)/(Recovery) 6.1 Repair Procedure • 13-H (Permanent) STEP 1: Make sure that the front cable is securely inserted. See Figure 7-10 below. FCH Firmly insert the connector on the front edge of the indicated FCH card.
TROUBLESHOOTING 23-S FCH Failure Notification (Detection) 6.2 Repair Procedure • 13-I (Temporary) STEP 1: Make sure that the front cable is securely inserted. (See Figure 7-10.) STEP 2: If this message has been displayed once or twice, monitor the failure for a while. Otherwise, move to STEP 3. STEP 3: If 13-J (Recovery) has been displayed after this message, monitor the failure for a while. Otherwise, move to STEP 4. STEP 4: Initialize the indicated FCH (PA-FCHA) card using the MB key.
TROUBLESHOOTING 23-S FCH Failure Notification (Detection) 7.1 Repair Procedure STEP 1: Make sure that the related Ethernet cables are securely inserted into the connectors. (See the example shown below.) If not, securely insert the cable. In this instance, confirm whether System Message 23T FCH Fault Recovery Notification is displayed as the result of cable insertion. If no fault is found in this step, move to STEP 2. STEP 2: The following equipment is suspected to be faulty.
TROUBLESHOOTING 23-S FCH Failure Notification (Detection) B HUB-HUB Cable Connection Test 1) Turn ON the MNT switch of the FCH cards which are connected to the both HUB cards. 2) Make sure that system message (23-W) "FCH Alternate Routing (start)" is displayed for each FCH. ATTENTION 3) Turn ON the MB key on the both HUB cards.
TROUBLESHOOTING 23-S FCH Failure Notification (Detection) DTI (PA-24DTR) FCH(PA-FCHA) ATTENTION HUB(PA-M96) Contents Static Sensitive Handling Precautions Required MNT 3 HUB(PA-M96) MB When this MB key is set in up position (Make-busy), all 10 BASE-T interfaces connected to this card become inoperative. MB : 10 BASE-T cable [How to Replace HUB card] 1) Provide anti-static kit. 2) Turn ON the MNT3 switch of the FCH cards which are connected to the HUB card to be replaced.
TROUBLESHOOTING 23-T FCH Fault Notification (Recovery) 8. 23-T FCH Fault Notification (Recovery) This message is displayed when the FCH (PA-FCHA) card that was detected as faulty is recovered. The message is displayed in the following format. 1. xx0x xx00 0000 0000 2. 0000 0000 0000 0000......... FLTINF: Fault Information Note Circuit Number of FCH (0 - 7) FLTINF FCH Mounting Location MG: Module Group U: Unit (0-3) G: Group (00-23) FCH CKT No.
TROUBLESHOOTING 23-U FCH Status Information 9. 23-U FCH Status Information This message is displayed when the status change of FCH (PA-FCHA) card is detected, which includes “FCH Initial Setting Failure,” “ETHER Transfer Failure.” When this message is displayed, follow the procedure explained on a fault information basis. The figure below shows the general format of this message. 1. xx0x xxxx xxxx xxxx 2. xxxx xxxx xxxx xxxx.........
TROUBLESHOOTING 23-U FCH Status Information 9.1 FLTINF = 00H Initial Setting Failure This message is displayed when the Ethernet Controller Initial Setting ends in failure. The detailed information is indicated in the following format. "Initial Setting Failure" 1. xx 0x 00 xx xx xx xx xx 2. xx xx xx xx 0000 0000......... b7 b0 : : : : b7 6 Bytes b0 MAC Address of FCH b7 b0 Other Results: 00H = Normal Other Results b7 b0 ETHER Results: See below.
TROUBLESHOOTING 23-U FCH Status Information 9.2 FLTINF = 18H Spanning Tree Abnormal Answer This message is displayed when Spanning Tree Abnormal Answer is detected. The detailed information is indicated in the following format. "Spanning Tree Abnormal Answer" 1. xx 0x 18 xx xx xx xx xx 2. xx xx xx xx xx xx xx xx 3. xx xx xx xx xx xx xx xx 4. xx xx xx xx xx xx xx xx 5. xx xx xx 00 0000 0000 6.
TROUBLESHOOTING 23-U FCH Status Information 9.2.1 Repair Procedure A Fusion Point Code (FPC) is assigned using the AFPC command. If any FPC data has not been assigned properly, this message is displayed. Make sure that the indicated FPC data is properly assigned. See the sample below. Assign all nodes' FPCs including nodes which are not directly connected. 11 self-Node 10 This FPC has not been assigned.
TROUBLESHOOTING 23-U FCH Status Information 9.3 FLTINF = 1DH ETHER Transfer Failure This message is displayed when an FCH card discards an abnormal Ethernet packet (i.e. abnormal IP address destination) that was received from other node on the network. "ETHER Transfer Failure" 1. xx 0x 1D xx xx xx xx xx 2. xx xx xx xx xx xx xx xx 3. xx xx xx xx xx xx xx xx 4. xx xx xx xx xx xx xx xx 5. xx xx xx xx xx xx xx xx 6. xx xx xx xx xx xx xx xx 7. xx xx xx xx xx xx xx xx 8.
TROUBLESHOOTING 23-U FCH Status Information 9.4 FLTINF = 1EH Spanning Tree Generation End This message is displayed when Spanning Tree Generation is complete. The detailed information is indicated in the following format. "Spanning Tree Generation End" 1. xx 0x 1E xx xx xx xx xx 2. xx xx xx xx xx xx xx xx 3. xx xx xx xx xx xx xx xx 4. xx xx xx xx xx xx xx xx 5. xx xx xx 00 0000 0000 6.
TROUBLESHOOTING 23-U FCH Status Information 9.5 FLTINF = 1FH Spanning Tree Generation Start This message is displayed when Spanning Tree Generation starts. "Spanning Tree Generation Start" 1. xx 0x 1F xx 00 00 00 00 2. 00 00 00 00 00 00 00 00.........
TROUBLESHOOTING 23-W FCH Alternate Routing Start Notification 10. 23-W FCH Alternate Routing Start Notification This message is displayed when the indicated FCH card of self-Node becomes inoperative. This message is also displayed when the card is placed in make busy status by MNT 3 switch operation. In addition, when the FCH of the adjacent node becomes inoperative, this message is displayed. 1. xx0x 0000 0000 0000 2. 0000 0000 0000 0000 b7 3. 0000 .........
This page is for your notes. CHAPTER 7 Page 168 Revision 3.
CHAPTER 8 EX- FCCS 1. General This feature provides the following functions (they are activated when connecting multiple Fusion networks) or a NEAX2000 IVS2 system to a Fusion Network using the Enhanced CCIS feature. The network connected by EX-FCCS function is referred as EX-FCCS Network in this manual. The network connected via Enhanced CCIS function is referred to as Enhanced CCIS network in the manual. 1. Number Portability See Section 3.1 “Number Portability”.
EX- FCCS EX-FCCS Network Configuration 2. EX-FCCS Network Configuration 2.1 Network Configuration The summary of network configuration classified into two types are shown in Table 8-1. See Table 8-1 in conjunction with Figure 8-1 for easy understanding of network configuration. The following items and sections explain more details.
EX- FCCS EX-FCCS Network Configuration 2.2 Conditions for Network Establishment (NEAX2000 IVS2 to NEAX2400 IMX Connection) Conditions for connecting the NEAX2000 IVS2 to NEAX2400 IMX are described below. 1. All IVS2 systems must be directly connected to an IMX. See Figure 8-2. NEAX2000 IVS2 (B) cannot be added to NEAX2000 IVS2 (A) which is already connected with NEAX2400 IMX. UNAVAILABLE Enhanced CCIS IVS2 (A) IVS2 (B) IMX Figure 8-2 NEAX2000 IVS2 to NEAX2400 IMX Connection 2.
EX- FCCS EX-FCCS Network Configuration 2.3 Conditions for Network Establishment (NEAX2400 IMX to NEAX2400 IMX Connection) Conditions for establishing a FCCS network (NEAX2400 IMX to NEAX2400 IMX) are shown below. 1. Each Fusion Network can accommodate a maximum of 253 network IDs. 2. Each Fusion Network can accommodate a maximum of 899 logical routes. 3. The NCN and NDM exist individually in each Fusion Network. Network configuration of the NEAX2400 IMX to NEAX2400 IMX connection is as follows.
EX- FCCS EX-FCCS Network Configuration 2.4 Fusion Network Group (FUG) [Fusion Network Group (FUG)] When connecting multiple Fusion networks using EX-FCCS, a Fusion Network group number is required to distinguish different Fusion Network groups. A Fusion Network Group is called as “Fusion Group (FUG)”. A maximum of 4 FUGs can be connected via EX-FCCS. [Center Fusion Group (Center FUG)] Identify the Center Fusion Group (Center FUG) from the FUGs in the EX-FCCS network.
EX- FCCS EX-FCCS Network Configuration 2.5 Interactions 1. Conditions for PS Service Roaming and Hand-over feature cannot be activated between FUG-FUG in an EX-FCCS network and FUG-IVS2 in an Enhanced CCIS network. To execute roaming service, connect other Q.931a/IS11572 lines. 2. Conditions for OAI/ACD Service The OAI/ACD service in EX-FCCS Network is executed on the same condition in CCIS Network. CHAPTER 8 Page 174 Revision 3.
EX- FCCS EX-FCCS Features 3. EX-FCCS Features 3.1 Number Portability [Operating Procedure] 1. Log in to the NCN of the Center FUG from the Centralized-MAT for EX-FCCS. 2. Assign the Telephone Number data using AELGN command. The new data is automatically copied to the NDM in the self-FUG and the other FUG in an EX-FCCS network. AELGN command is also used to delete or change Telephone Number data in addition to assignment.
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. 6 IVS 2 FUG(A) IVS 2 FUG(B) 7 FPC1 NCN(A) 5 8 FPC1 NCN(B) FPC2 FPC2 3 1 FPC3 FPC4 FPC3 FPC4 2 LEGEND : FCCS : EX-FCCS 4 : Enhanced CCIS : Fusion Group (FUG) Figure 8-5 Patterns of Number Portability Table 8-2 Patterns of Number Portability NO.
EX- FCCS EX-FCCS Features 5. Up to a maximum of 120,000 Telephone Numbers may be assigned in the entire Enhanced CCIS/EXFCCS 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 IVS2 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.
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.
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 IVS2 System). See Figure 8-6.
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.
EX- FCCS EX-FCCS Features 2. Unique PCs (Point Codes) in the CCIS network connected with EX-FCCS are required. All PCs used in the network must be different. (For the system to be connected with the next system via CCIS link or the large sized network, this assignment is required.
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 Network. 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.
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.
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.
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 IVS2 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.
EX- FCCS Data Programming 4.1 Brand-new EX-FCCS Network To install EX-FCCS network as a brand-new system between two Fusion Groups (when no CCIS data has been assigned), the overall data programming procedure is as follows. [Example EX-FCCS Network] FUG2 FUG1(Center FUG) NCN2 NCN1 EX-FCCS FCCS FCCS PC1 FPC1 PC4 FPC1 FCCS PC3 FPC3 FCCS Centralized MAT PC6 FPC3 FCCS FCCS PC2 FPC2 4.1.
EX- FCCS Data Programming STEP 2: ARTD Assign the following three routes for this feature: • Speech Path Route (Traffic Route) • Signaling Route • Dummy Route (Flag Route) Assign each route data in accordance with the table shown below. Note that data assignment in this table is a typical example.
EX- FCCS Data Programming STEP 4: MBTC Assign IDLE status of trunks by designating Route Number and Trunk Number. STEP 5: ADPC Assign the destination PC (Point Code) on RT (for speech path) number basis for all the nodes in the EX-FCCS network. STEP 6: ACSC Assign the location of the CCH in CSCG (Common Channel Signaling Controller Group). Assign thue location of the CCH using the ACSC command. The following is sample data assignment. In this sample, PC 3 is equipped with three DTI cards.
EX- FCCS Data Programming STEP 7: ACIC1 Assign CSCG for Basic/Primary Route. The odd numbered CSCG for Alternate Route assignment. PC CSCG 4 130 STEP 8: ACIC2 Assign CICs (Circuit Identification Codes) corresponding to trunk number. Although trunk number and the CIC may not be identical, the same CIC must be given to one speech line between two nodes as illustrated in Figure 8-9. Be sure to assign PCs of all the nodes in the EX-FCCS network corresponding to ADPC/ACIC1 command.
EX- FCCS Data Programming STEP 1: ASYD Assign the Point Code to all the nodes in the network uniquely as described on Page 163. STEP 2: ADPCL Assign the destination PC (Point Code) on LGRT (for speech path) number basis for all the nodes in the network. STEP 3: ACSCL Assign the location of the CCH and FPC of the node which accommodates CCIS trunk in CSCG (Common Channel Signaling Controller Group) for all the nodes in the network.
EX- FCCS Data Programming STEP 3: AFUGN Assign EX-FCCS Fusion Group data. Designate Self-FUG Number, Connection FUG Number and Fusion Point Code (FPC) of the NCN within each FUG. Either of FUG is set as the Center FUG by checking the “CENTER” parameter. STEP 4: AEXFN Assign the EX-FCCS CCH Selection Data by designating all the Fusion Point Code (FPC) and the Point Code (PC) in the connected Fusion Group.
EX- FCCS Data Programming STEP 5: ARNPL Assign the access code for LCR/LCRS as assigned in ASPAN associated with the logical routes for each external trunk assigned in ARTD/ARTDN. STEP 6: AMND Assign the Maximum Necessary Digit (MND). Note 1: The MND is the total number of ACC + Telephone Number. Note 2: Refer to CHAPTER 5, Section 7.1 “Assignment of Access Code for Tandem Connection via FCCS - ACIS“ for more detail data programming related to LCR/LCRS such as AFRSN, AOPRN, ARNPL and AMND command.
EX- FCCS Data Programming 4.2 Upgrading CCIS Network to EX-FCCS Network This section explains the way to assign the data when upgrading a CCIS Network to an EX-FCCS Network. Perform the necessary data programming using the following upgrading patterns: • Upgrading CCIS between FUGs to EX-FCCS Network • Upgrading CCIS between FUG and IVS2 system to Enhanced CCIS Network • Upgrading CCIS between IMX system and IVS2 systems to Enhanced CCIS Network 4.2.
EX- FCCS Data Programming 1. To Log-in to All Nodes in EX-FCCS Network Perform the following data programming at each NCN of all the Fusion Groups. STEP 1: AFUGN Assign EX-FCCS Fusion Group data. Designate Self FUG Number, connection FUG Number and Fusion Point Code of the NCN within each FUG. Either of the FUGs assigned as the Center FUG by clicking the “CENTER” check box.
EX- FCCS Data Programming 4.2.2 Upgrading CCIS between FUG and IVS2 System to Enhanced CCIS Network FUG (Center FUG) IMX IMX IVS 2 System FCCS NCN PC1 FPC1 Enhanced CCIS PC3 FPC3 FCCS IMX PC4 FCCS PC2 FPC2 FCCS CCIS FCCS 1. FCCS To Log-in to All Nodes in EX-FCCS Network Assign the following data at the NCN of FUG with Centralized MAT for Fusion. STEP 1: AFUGN Assign EX-FCCS Fusion Group data.
EX- FCCS Data Programming 2. To Access EX-FCCS Trunk via EX-FCCS Telephone Number Assign the following data at NCN of the FUG. STEP 1: AEADN Assign the ADC (Abbreviate Digit Code) for connection Fusion Group. Enter the FUG Number assigned by AFUGN command, TN, and ADC to be assigned. STEP 2: AELGN Telephone Numbers must be assigned for all the station within the network uniquely. Use AELGN command to allocate EX-FCCS Telephone Number.
EX- FCCS Data Programming 1. To Log-in to All Nodes in EX-FCCS Network To upgrade CCIS network to EX-FCCS Network as shown in the figure on the previous page, all the IMX systems are set as NCNs respectively. To construct a EX-FCCS Network including stand-alone IMX system, the node must be assigned as a Fusion Network configured by the NCN only, and handled by the NDM data. Assign the following data at all the NCNs (that is, all the IMX systems of each node) within the EX-FCCS Network.
This page is for your notes. CHAPTER 8 Page 198 Revision 3.
