free stats
NEC NEAX 2400 IMX Manual
  1. Manuals
  2. Brands
  3. NEC Manuals
  4. Network Hardware
  5. NEAX 2400 IMX
  6. Manual
NEC NEAX 2400 IMX Manual

NEC NEAX 2400 IMX Manual

Fusion network system
Hide thumbs Also See for NEAX 2400 IMX:
Table of Contents

Advertisement

Quick Links

Download this manual
ND-70185 (E)
ISSUE 3
STOCK # 200869
®
Fusion Network System Manual
MAY, 2000
NEC America, Inc.
Get other manuals https://www.bkmanuals.com

Advertisement

Table of Contents
loading

Related Manuals for NEC NEAX 2400 IMX

Summary of Contents for NEC NEAX 2400 IMX

  • Page 1 ND-70185 (E) ISSUE 3 STOCK # 200869 ® Fusion Network System Manual MAY, 2000 NEC America, Inc. Get other manuals https://www.bkmanuals.com...
  • Page 2 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.
  • Page 3 Issue No. Issue No. PAGE No. PAGE No. viii ISSUE 1 ISSUE 2 ISSUE 3 ISSUE 4 DATE JANUARY, 1998 DATE MARCH, 1999 DATE MAY, 2000 DATE ISSUE 5 ISSUE 6 ISSUE 7 ISSUE 8 DATE DATE DATE DATE NEAX2400 IMX Fusion Network System Manual Issue Revision Sheet 1/3 ND-70185 (E) ISSUE 3...
  • Page 4 Issue No. Issue No. PAGE No. PAGE No. ISSUE 1 ISSUE 2 ISSUE 3 ISSUE 4 DATE JANUARY, 1998 DATE MARCH, 1999 DATE MAY, 2000 DATE ISSUE 5 ISSUE 6 ISSUE 7 ISSUE 8 DATE DATE DATE DATE NEAX2400 IMX Fusion Network System Manual Issue Revision Sheet 2/3 ND-70185 (E) ISSUE 3...
  • Page 5 Issue No. Issue No. PAGE No. PAGE No. ISSUE 1 ISSUE 2 ISSUE 3 ISSUE 4 DATE JANUARY, 1998 DATE MARCH, 1999 DATE MAY, 2000 DATE ISSUE 5 ISSUE 6 ISSUE 7 ISSUE 8 DATE DATE DATE DATE NEAX2400 IMX Fusion Network System Manual Issue Revision Sheet 3/3 ND-70185 (E) ISSUE 3...
  • Page 6 ND-70185 (E) ISSUE 3 MAY, 2000 NEAX2400 IMX Fusion Network System Manual TABLE OF CONTENTS Page CHAPTER 1 INTRODUCTION ............1.
  • Page 7 TABLE OF CONTENTS (CONTINUED) Page 3. Mounting Circuit Cards in PIM ............Mounting HUB (PA-M96) in a PIM.
  • Page 8 TABLE OF CONTENTS (CONTINUED) Page 8. Office Data Sheets ..............112 Data Sheet for AFMUPL .
  • Page 9 TABLE OF CONTENTS (CONTINUED) Page CHAPTER 7 TROUBLESHOOTING ............147 1.

  • Page 10: Table Of Contents

    LIST OF FIGURES Figure Title Page Figure 2-1 Telephone Number ............Figure 2-2 Free Location .
  • Page 11 LIST OF FIGURES (CONTINUED) Figure Title Page Figure 5-2 Fusion-CCIS Network ............Figure 5-3 How to Upgrade the Numbering Plan Data of an Existing CCIS Network .
  • Page 12 LIST OF FIGURES (CONTINUED) Figure Title Page Figure 5-51 Sample Data Assignment (ACRD) ..........Figure 5-52 Sample Data Assignment (ACTK) .
  • Page 13 LIST OF FIGURES (CONTINUED) Figure Title Page Figure 8-1 Network Connection Type ........... . Figure 8-2 NEAX2000 IVS to NEAX2400 IMX Connection .
  • Page 14 LIST OF TABLES Table Title Page Table 4-1 SENSE Switch Setting ............Table 4-2 MODE Switch Setting.
  • Page 15 This page is for your notes. LIST OF TABLES ND-70185 (E) Page x Revision 3.0 Get other manuals https://www.bkmanuals.com...
  • Page 16 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.
  • Page 17 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.

  • Page 18: Figure 2-1 Telephone Number

    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).

  • Page 19: Figure 2-2 Free Location

    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. Node C Telephone Number 411111...

  • Page 20: Figure 2-4 Fusion System Configuration (With Fch)

    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 Node C Fusion Link Fusion Link 1.5M 1.5M...

  • Page 21: Figure 2-6 Maximum System Configuration

    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.

  • Page 22: Figure 2-7 Network Data Memory

    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.

  • Page 23: Figure 2-8 Network Data Memory Copy

    GENERAL Fusion Network Examples When the NDM (master) is modified, the new data is automatically copied. Change... (master) copy copy Fusion Link The standard size of each memory is as follows: DM (Data Memory): 4M Bytes LDM (Local Data Memory): 2M Bytes NDM (Network Data Memory): 2M Bytes NCN: Network Control Node LN: Local Node...

  • Page 24: Figure 2-10 Open Numbering Fusion-Ccis Network

    GENERAL Fusion Network Examples 81: CCIS for Node B 82: CCIS for Node C CCIS [Open Numbering] 8x: CCIS access for Network CCIS Network "8x" 4x...: Fusion access Node A FCCS "80" FCCS FPC = 1 CCIS Node C CCIS PC =10 Node B "82"...

  • Page 25: Figure 2-11 Tandem Connections Via Fusion Link

    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 ACIS is established. FCCS FCCS Node B Node A TELN...

  • Page 26: Figure 3-1 Fusion System Configuration Without Fch

    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.

  • Page 27: Figure 3-2 Fusion System Configuration With Fch

    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 configu- ration, the Fusion link is established between nodes via the T1 link. Figure 3-2 shows a Fusion system con- figuration with FCH.

  • Page 28: Figure 3-3 Redundant Configuration (Lani, Hub, Fch, And Dti)

    SYSTEM CONFIGURATION Fusion System with FCH 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.

  • Page 29: Figure 3-6 Non-Redundant Configuration

    SYSTEM CONFIGURATION System Considerations Figure 3-6, no redundancy is shown in the Fusion link. In this case, no redundancy is taken as to Fusion link. LANI#0 CPU#0 10 Base T 10 Base T PCI Bus ..CPU#1 LANI#1 10 Base T PCI Bus Figure 3-6 Non-Redundant Configuration 3.

  • Page 30: Figure 3-9 Maximum Number Of Ports Between Nodes

    SYSTEM CONFIGURATION System Considerations Condition 2: A maximum of four (4) nodes can be connected as tandem nodes. max 4 nodes FCCS FCCS FCCS Node A Node B Node C 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.

  • Page 31: Figure 3-10 Connection Trunk Alternate Routing

    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. Node Alt-C_RT1 Node Alt-C_RT2 Node A Node B Alt-C_RT3 Node...
  • Page 32 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.

  • Page 33: Figure 3-12 Centralized Billing - Fusion (1/3)

    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. - Example 1 - Node A (Fusion - Center Node) collects the billing information of Nodes B and C via FCCS using polling method.
  • Page 34 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. •...
  • Page 35 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. •...

  • Page 36: Figure 3-13 Centralized Management Report-Fusion

    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. Node B FCCS Fault!

  • Page 37: Figure 3-14 Centralized Management Report-Fusion (Example 1)

    SYSTEM CONFIGURATION System Considerations The following explains service conditions for the network including both FCCS and CCIS links. When the network comprises FCCS and CCIS links Example: 1 Node B Node C 13-H 1. xxxx xxxx 0010 1222 FCCS 4. x0010 1110 10110 1FFF PC=11 PC=12 7.

  • Page 38: Figure 3-15 Centralized Management Report-Fusion (Example 2)

    SYSTEM CONFIGURATION System Considerations Example: 2 When both FCCS and CCIS links are established between two nodes Node B Node C 13-H 1. xxxx xxxx 0010 1222 FCCS 4. x0010 1110 10110 1FFF PC=11 PC=12 7. E23C CAAB12 000 0000 FPC=2 FPC=3 Centralized MAT...

  • Page 39: Figure 3-16

    SYSTEM CONFIGURATION System Considerations Example: 3 When a node is linked with LAN interface Node B Node C PC=3 FCCS FPC=10 FPC=11 FCCS with LAN CCIS PC=2 FPC=12 CCIS Node A Node D Center Node: Node E 13-H 1. xxxx xxxx 0010 1222 4.

  • Page 40: Figure 3-17 Operator Calls On A Fusion Network

    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.

  • Page 41: Figure 3-18 Ring Down Calls On A Fusion Network

    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).

  • Page 42: Figure 3-19 Day/Night Information Transfer By Attcon/Deskcon

    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.
  • Page 43 This page is for your notes. CHAPTER 3 ND-70185 (E) Page 28 Revision 3.0 Get other manuals https://www.bkmanuals.com...

  • Page 44: Figure 4-1 Static Caution Indicator

    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 •...

  • Page 45: Figure 4-2 How 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. Earth Terminal Ground Wire Wrist Strap Conductive Sheet...

  • Page 46: Figure 4-3 Circuit Cards For Fusion

    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.

  • Page 47: Figure 4-4 Switch Setting On Hub (Pa-M96) Card

    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 Table 4-1. ATTENTION Contents Static Sensitive Handling Precautions Required SENSE TP7-X TP6-X TP5-X TP4-X...

  • Page 48: Figure 4-5 Switch Setting On Fch (Pa-Fcha) Card

    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.

  • Page 49: Table 4-2 Mode Switch Setting

    INSTALLATION Key Setting on Circuit Cards Table 4-2 MODE Switch Setting STANDARD SWITCH NAME SETTING DESCRIPTION SETTING MODE Not used 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) Not used Table 4-3 DIP Switch (SW14) Setting SWITCH...

  • Page 50: Figure 4-6 Switch Locations On Dti (Pa-24Dtr) Card

    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 Table 4-4 to set each switch to the proper positions. DTI (PA-24DTR) Card ATTENTION Contents Static Sensitive N-OPE Handling...
  • Page 51 INSTALLATION Key Setting on Circuit Cards Table 4-4 Switch Setting Patterns for the DTI Card (Continued) SWITCH STANDARD SWITCH NAME SETTING MEANING NUMBER SETTING Transmission Signal A Logic: Negative × SW4D Transmission Signal A Logic: Positive Receiving Signal A Logic: Negative ×...
  • Page 52 INSTALLATION Key Setting on Circuit Cards Table 4-4 Switch Setting Patterns for the DTI Card (Continued) SWITCH STANDARD SWITCH NAME SETTING MEANING NUMBER SETTING × SW39-1 SW39-2 PAD CONTROL × Both directions Receiving only Sending only SW39 ARTD is fixed ×...
  • Page 53 INSTALLATION Key Setting on Circuit Cards Table 4-4 Switch Setting Patterns for the DTI Card (Continued) SWITCH STANDARD SWITCH NAME SETTING MEANING NUMBER SETTING × Fixed × Fixed SW6C × Fixed × Fixed × Fixed × Fixed × Fixed × Fixed Equalizer Setting DISTANCE...

  • Page 54: Table 4-5 Digital Pad Setting

    INSTALLATION Key Setting on Circuit Cards Table 4-4 Switch Setting Patterns for the DTI Card (Continued) SWITCH STANDARD SWITCH NAME SETTING MEANING NUMBER SETTING Digital PAD ROM selection: Special specifica- SW5D tion Digital PAD ROM selection: Standard specifica- × tion ×...

  • Page 55: Figure 4-7 Mounting Hub Card In Pim 0

    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 con- nected via a HUB card, be sure to use a dedicated HUB for the Fusion link. HUB (PA-M96) can be mounted wherever in a PIM of any IMG stack.

  • Page 56: Figure 4-8 Mounting Fch And Dti Cards

    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.

  • Page 57: Figure 4-9 Connecting Front Cables

    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 connec- tors 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.

  • Page 58: Figure 4-10 Fch Cascade Connections

    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.

  • Page 59: Figure 4-11 Overall 10 Base-T Connections

    10 BASE-T cross cable. However, when dual LANIs (LANI-A and LANI-B) are used for each CPU, the cross cable connection between HUBs for FCH#0 and #1 is not necessary. The Ethernet cables shown in the examples in this section are NOT available from NEC. These cables must Note: be provided by the customer, depending on the system configuration.
  • Page 60 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...
  • Page 61 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 BASE- T 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.
  • Page 62 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).

  • Page 63: Figure 4-12 Connecting 10 Base-T Cables (Example)

    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.

  • Page 64: Figure 4-13 Examples Of Ethernet Cable Connection-Fch In Pim0 (1-Img System) (1/2

    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 Configuration Used Cable Unit Number of HUB/ of CPU of LAN (Note 1, Note 2) SR1201 ETIF CAU-A ×...
  • Page 65 INSTALLATION Connecting Cables ATTENTION Contents Static Sensitive Handling Precautions Required <FCH in PIM0 (Pattern 3)> <FCH in PIM0 (Pattern 4)> 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 PIM 0 PIM 0...

  • Page 66: Figure 4-14 Examples Of Ethernet Cable Connection-Fch In Pim1 (1-Img System)

    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 Configuration Used Cable Unit Number of HUB/ of CPU of LAN (Note 1, Note 2) SR1201 ETIF CAU-B ×...

  • Page 67: Figure 4-15 Examples Of Ethernet Cable Connection-Fch In Pim2 (1-Img System) (1/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 Configuration Used Cable Unit Number of HUB/ of CPU of LAN (Note 1, Note 2) SR1201 ETIF CAU-C ×...
  • Page 68 INSTALLATION Connecting Cables A T T E N T IO N C ontents Static S ens itive H andling Prec autions R equired <FC H in PIM 2 (Pattern 3)> <FC H in PIM 2 (Pattern 4)> TO PU TO PU PIM 3 PIM 3 U TP C TG 5 ST C A -K...

  • Page 69: Figure 4-16 Examples Of Ethernet Cable Connection-Fch In Pim3 (1-Img System) (1/2

    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 Configuration Used Cable Unit Number of HUB/ of CPU of LAN (Note 1, Note 2) SR1201 ETIF CAU-D ×...
  • Page 70 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 <FC H in PIM 3 (Pattern 3)> <FCH in PIM 3 (Pattern 4)> TO PU TO PU PIM 3 PIM 3...
  • Page 71 This page is for your notes. CHAPTER 4 ND-70185 (E) Page 56 Revision 3.0 Get other manuals https://www.bkmanuals.com...

  • Page 72: Figure 5-1 Data Programming Flow Chart

    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 AFMU ALRTN...
  • Page 73 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 System Data •...
  • Page 74 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 System Data • Decide an NCN and LN on the network. •...

  • Page 75: Figure 5-2 Fusion-Ccis Network

    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.

  • Page 76: Figure 3-8

    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.

  • Page 77: Figure 5-4 Assignment Of Memory Block

    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.

  • Page 78: Figure 5-6 Self-Fpc Assignment

    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 ASY- DL 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.

  • Page 79: Figure 5-7 Asydn Command Display (Example)

    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...

  • Page 80: Figure 5-8 Assignment Of Module Accommodation Data

    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.

  • Page 81: Figure 5-10 Telephone Number Required

    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.

  • Page 82: Figure 5-12 Alrtn Command Display

    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 LGRT (Logical Route Number): 1 - 899 RT (External Route Number): 1 - 899 (Maximum) WRT? Figure 5-12 ALRTN Command Display...

  • Page 83: Figure 5-14 Anpdn Sample Data Sheet

    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 com- mand at NCN. In Figure 5-14, the data setting should be as follows: - ANPDN Data Sheet (example) Telephone Number - NCN (Node A)

  • Page 84: Figure 5-16 Aspan Sample Data Sheet

    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. - ASPAN Data Sheet (example) Telephone Number - NCN (Node A) SRV (Kind of Service) TELN: Telephone Number 4 x x x x x...

  • Page 85: Figure 5-18 Algsn Sample Data Sheet

    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 com- mand. Telephone Number can be assigned to a station using the LENs or the Physical Station Number depend- ing on programming.

  • Page 86: Figure 5-19 Algsn Command Display (Example)

    DATA PROGRAMMING Assignment of Telephone Numbers ALGSN (Assignment of Telephone Station Data In Network) TYPE Telephone Number TELN 41000 LENS 000100 WRT? Physical LENS For Help, press F1 ALGSN (Assignment of Telephone Station Data In Network) TYPE Telephone Number TELN 41000 2000 WRT?

  • Page 87: Figure 5-20 B-Ch And D-Ch

    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.

  • Page 88: Table 5-1 Route Class Data Assignment

    DATA PROGRAMMING Assignment of Telephone Numbers Table 5-1 Route Class Data Assignment Node A Node B type B-channel D-channel B-channel D-channel Description C_RT: 10 C_RT: 11 C_RT: 12 C_RT: 13 Trunk Kind 3: Bothway (fixed) Trunk Class: 4 (fixed) Release Method : Assign 2-First Party Release.
  • Page 89 DATA PROGRAMMING Assignment of Telephone Numbers 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)
  • Page 90 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: -...

  • Page 91: Figure 5-22 Actk Command Display (Example)

    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. As- sign 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. C_RT: Connection Route (1-1023) C_TK: Connection Trunk (1-4095) C_LENS: Connection Line Equipment Numbers...

  • Page 92: Table 5-2 Data Programming Sheet For Regular Density Slot

    DATA PROGRAMMING Assignment of Telephone Numbers Table 5-2 Data Programming Sheet for Regular Density Slot C_LENS C_RT C_TK(1-4095) Time Slot Allocation (1-1023) Example mounting slot Slot No. Group No. Dch (TK1) Bch (TK8) Bch (TK23) Bch (TK1) Bch (TK9) Extended Group 10 (B-ch) Dch (TK2) Specify Dch -TS by setting switch on FCH.

  • Page 93: Figure 5-24 Mounting Fch And Dti Cards In High-Density Slots

    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.

  • Page 94: Figure 5-25 How To Assign C_Len Data (Type 2)

    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. Universal Slots Universal Slots 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 03 05 07 09 11 05 07 02 04 06 08 10...

  • Page 95: Table 5-3 Data Programming Sheet For High Density Slot

    DATA PROGRAMMING Assignment of Telephone Numbers Table 5-3 Data Programming Sheet for High Density Slot C_LENS C_RT C_TK Time Slot Allocation (1-1023) (1-4095) mounting slot Slot No. Group No. Dch (TK1) Bch (TK23) Bch (TK17) Dch (TK2) Bch (TK16) Bch (TK9) Bch (TK8) Bch (TK1) 10 (B-ch)

  • Page 96: Figure 5-26 Mbct Command Display

    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 Connec- tion Trunk) command. This step is required for both B-channel and D-channel trunk. The MBCT command should look similar to the following.

  • Page 97: Figure 5-27 Assignment Of Fch Number

    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 Use "odd number"...

  • Page 98: Figure 5-29 Afrt Sample Data Sheet

    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. FCHN = 1 Node A CNT = 1 C_RT : 10 Node B TRK 1 TRK 31 FCIC=1 FCIC=1...

  • Page 99: Figure 5-31

    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.

  • Page 100: Figure 5-33 Afpc Sample Data Sheet

    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.

  • Page 101: Figure 5-34 Acan Sample Data Sheet

    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 5- shows a sample data sheet for Node A. It is not necessary to assign the same number as trunk and FCIC. However, FCIC numbers between adja- Note: cent nodes must be identical.

  • Page 102: Figure 5-36 Example Of Ogc

    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 LGRT:100...
  • Page 103 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...

  • Page 104: Figure 5-37 Example Of Ogca

    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 C Node B BUSY FCCS LGRT:100 STN (C) FCCS PSTN Station C dials 9-1-303-456-7890 LGRT:200 1-303-456-7890 Node A Figure 5-37 Example of OGCA STEP 1: ANPDN/ANPDL Note...

  • Page 105: Figure 5-38 Example Of Lcr/Lcrs

    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.
  • Page 106 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 com- mand.
  • Page 107 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.
  • Page 108 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. Fusion Link with FCCH F u s i o n Node-A Node-B...
  • Page 109 DATA PROGRAMMING Assignment of FCH Related Data Specifications for the SDH data setting are described below. 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.
  • Page 110 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. (When using 512kbps (8ch) TS as Connection link) Example: • Connection trunk (B-ch) C_RT: 10 TK: 1-664 CLENS: LEN for the SDT...
  • Page 111 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...

  • Page 112: Figure 5-39 External Router - Overview

    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 es- tablished by using the following features: • External Router • Fusion over IP 7.3.1 External Router...

  • Page 113: Figure 5-41 Connection Route Class Data Sample

    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. 6.1 Assignment of Connection Route/Trunk Data for more detailed information. RT10 Speech Fusion Network Sample Data Assignment Type...

  • Page 114: Figure 5-42

    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.

  • Page 115: Figure 5-43

    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. RT10 Speech Fusion Network...

  • Page 116: Figure 5-44 Sample Data Assignment (Afpc)

    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)".

  • Page 117: Figure 5-46 Sample Data Assignment (Aeth)

    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.

  • Page 118: Figure 5-48

    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.

  • Page 119: Figure 5-49 Fccs Networking Over Ip - Overview

    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 be- tween routers.

  • Page 120: Figure 5-51 Sample Data Assignment (Acrd)

    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. speech Type Speech FCCH signaling SMDR RT14 ROUTER Q-sig 0(1) TRKS TC/EC FINT FPEG RT13...

  • Page 121: Figure 5-53 Assignment Of Fchn (Example)

    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.

  • Page 122: Figure 5-54 Sample Data Assignment (Aeth)

    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.

  • Page 123: Figure 5-56 Sample Data Assignment (Acan)

    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.

  • Page 124: Figure 5-58

    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.

  • Page 125: Figure 5-59 "Basic Lens Data" Assignment Of Speech Channels (Afip)

    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.
  • Page 126 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.
  • Page 127 DATA PROGRAMMING Office Data Sheets 8. Office Data Sheets 8.1 Data Sheet for AFMUPL FUSION POINT CODE MODULE GROUP UNIT (FPC) (MG) REMARKS 1-253 CHAPTER 5 ND-70185 (E) Page 112 Revision 3.0 Get other manuals https://www.bkmanuals.com...
  • Page 128 DATA PROGRAMMING Office Data Sheets 8.2 Data Sheet for ALRTN LOGICAL ROUTE FUSION POINT EXTERNAL ROUTE NUMBER CODE NUMBER REMARKS (LGRT) (FPC) (RT) 1-899 1-253 1-255 ND-70185 (E) CHAPTER 5 Page 113 Revision 3.0 Get other manuals https://www.bkmanuals.com...
  • Page 129 DATA PROGRAMMING Office Data Sheets 8.3 Data Sheet for ANPD/ANPDL/ANDPN TENANT 1ST DIGIT CONNECTION STATUS INDEX BUSY LAMP FIELD NUMBER (1ST DC) (CI) (BLF) (TN) CHAPTER 5 ND-70185 (E) Page 114 Revision 3.0 Get other manuals https://www.bkmanuals.com...
  • Page 130 DATA PROGRAMMING Office Data Sheets 8.4 Data Sheet for ASPA/ASPAL ANNOUNCEMENT ANNOUNCEMENT ACCESS CONNECTION TENANT KIND OF TENANT EQUIPMENT CODE STATUS NUMBER SERVICE NUMBER NUMBER REMARKS (ACC) INDEX (TN) (SRV) (TN) (EQP) MAX. 6 DIGITS (CI) 1/2 1-125 122-125 Normal Hooking Normal Hooking...
  • Page 131 DATA PROGRAMMING Office Data Sheets 8.5 Data Sheet for ALGNL LOGICAL STATION NUMBER USER GROUP NUMBER (LSTN) REMARKS (UGN) MAX. 16 DIGITS CHAPTER 5 ND-70185 (E) Page 116 Revision 3.0 Get other manuals https://www.bkmanuals.com...
  • Page 132 DATA PROGRAMMING Office Data Sheets 8.6 Data Sheet for ALGSL (TYPE1) TYPE LSTN LENS REMARKS ND-70185 (E) CHAPTER 5 Page 117 Revision 3.0 Get other manuals https://www.bkmanuals.com...
  • Page 133 DATA PROGRAMMING Office Data Sheets 8.7 Data Sheet for ALGSL (TYPE2) TYPE LSTN LENS REMARKS CHAPTER 5 ND-70185 (E) Page 118 Revision 3.0 Get other manuals https://www.bkmanuals.com...
  • Page 134 DATA PROGRAMMING Office Data Sheets 8.8 Data Sheet for ASDT LINE EQUIPMENT TELEPHONE ROUTE SERVICE TENANT STATION NUMBER EQUIPMENT RESTRICTION FEATURE NUMBER NUMBER (LENS) CLASS CLASS CLASS REMARKS (TN) (STN) (TEC) (RSC) (SFC) 1-31 0-15 0-15 ND-70185 (E) CHAPTER 5 Page 119 Revision 3.0 Get other manuals https://www.bkmanuals.com...
  • Page 135 DATA PROGRAMMING Office Data Sheets 8.9 Data Sheet for ACRD CONNECTION RT No. (C_RT) 1-1023 FUNCTION (FUNC) TF - Type of Trunk 0-2 = Bothway Trunk (BWT) TCL - Trunk Class (Fixed “4”) 0-3 = - 4 = Fusion Trunk 5-31 = - RLP - Trunk Release Pattern (Fixed “2”)
  • Page 136 DATA PROGRAMMING Office Data Sheets CONNECTION RT No. (C_RT) 1-1023 FUNCTION (FUNC) FPEG - Fusion-PEG (Fixed “0”) 0 = Nothing of FUSION-PEG 1 = Exist of FUSION-PEG TC - Timer Class (Fixed “0”) 1 = 1 sec. 2 = 2 sec. 3 = 8 sec.
  • Page 137 DATA PROGRAMMING Office Data Sheets 8.10 Data Sheet for ACTK CONNECTION ROUTE CONNECTION TRUNK CONNECTION EQUIPMENT NUMBER NUMBER NUMBER REMARKS (C_RT) (C_TK) (C_LENS) 1-1023 1-4095 CHAPTER 5 ND-70185 (E) Page 122 Revision 3.0 Get other manuals https://www.bkmanuals.com...
  • Page 138 DATA PROGRAMMING Office Data Sheets 8.11 Data Sheet for AFCH FCCH NUMBER LENS OF FCCH (FCHEN) (FCHN) REMARKS 1-255 ND-70185 (E) CHAPTER 5 Page 123 Revision 3.0 Get other manuals https://www.bkmanuals.com...
  • Page 139 DATA PROGRAMMING Office Data Sheets FCCH NUMBER LENS OF FCCH (FCHEN) (FCHN) REMARKS 1-255 CHAPTER 5 ND-70185 (E) Page 124 Revision 3.0 Get other manuals https://www.bkmanuals.com...
  • Page 140 DATA PROGRAMMING Office Data Sheets 8.12 Data Sheet for AFPC FUSION POINT CODE FCCH USE OR (FPC) NOT USE (FCCH) 1-253 CONNECTION ROUTE (C_RT) 1-1023 FCCH NUMBER/FUSION POINT CODE NUMBER (FCHN/FPCN) 1-255/1-253 FUSION POINT CODE FCCH USE OR (FPC) NOT USE (FCCH) 1-253 CONNECTION ROUTE (C_RT)
  • Page 141 DATA PROGRAMMING Office Data Sheets FUSION POINT CODE FCCH USE OR (FPC) NOT USE (FCCH) 1-253 CONNECTION ROUTE (C_RT) 1-1023 FCCH NUMBER/FUSION POINT CODE NUMBER (FCHN/FPCN) 1-255/1-253 CHAPTER 5 ND-70185 (E) Page 126 Revision 3.0 Get other manuals https://www.bkmanuals.com...
  • Page 142 DATA PROGRAMMING Office Data Sheets 8.13 Data Sheet for ACAN FUSION POINT CODE FUSION CIC NUMBER CONNECTION EQUIPMENT (FPC) (FCIC) NUMBER REMARKS 1-253 1-4095 (C_LENS) ND-70185 (E) CHAPTER 5 Page 127 Revision 3.0 Get other manuals https://www.bkmanuals.com...
  • Page 143 DATA PROGRAMMING Office Data Sheets 8.14 Data Sheet for AFRT FCCH NUMBER CONNECTION ROUTE (C_RT) 1-1023 (FCHN) 1-255 CHAPTER 5 ND-70185 (E) Page 128 Revision 3.0 Get other manuals https://www.bkmanuals.com...
  • Page 144 DATA PROGRAMMING Office Data Sheets 8.15 Data Sheet for AETH DESTINATION GATEWAY FCCH CONNECTION DESTINATION NEXT IP USING FLAG NUMBER ROUTE IP ADDRESS ADDRESS (FPC) (USE_GATE) (FCHN) (C_RT) (DST_IP) (NEXT_IP) 1-253 1-255 1-1023 ND-70185 (E) CHAPTER 5 Page 129 Revision 3.0 Get other manuals https://www.bkmanuals.com...
  • Page 145 DATA PROGRAMMING Office Data Sheets 8.16 Data Sheet for AGIP VOICE CLIENT/ FRAME LINE EQUIPMENT IP ADDRESS CHANNEL QSIG-PRIME SERVER FGH IP TYPE OF NUMBER OF FCCH FOR DEFAULT LINK NUMBER CONTROL CONNECTION ADDRESS (FCHEN) GATEWAY (LINK_NUM) TYPE MAX. NUMBER (FGH_IP) (ARP) (DG_IP)
  • Page 146 DATA PROGRAMMING Office Data Sheets 8.17 Data Sheet for AFIP LINE EQUIPMENT LINE EQUIPMENT NUMBER OF ROUTER ACCESS NUMBER NUMBER OF FGH QSIG-PRIME Bch NUMBER (RT_ACC) (FGHEN) (LENS) (FCHN) Max. 16 digits ND-70185 (E) CHAPTER 5 Page 131 Revision 3.0 Get other manuals https://www.bkmanuals.com...
  • Page 147 DATA PROGRAMMING Office Data Sheets 8.18 Data Sheet for AFRFL FPC (1-253) MAX. 24 digits CHAPTER 5 ND-70185 (E) Page 132 Revision 3.0 Get other manuals https://www.bkmanuals.com...

  • Page 148: Figure 6-1 Fusion Network

    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. This chapter describes the following tests: •...

  • Page 149: Figure 6-2 Led Indications On Fusion Link Related Circuit Cards

    POST INSTALLATION TEST Repair Procedure When LED Indicates Abnormality 1.1 How to check LYR LED 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. Make sure that any alarm LED is not ON (red/yellow).

  • Page 150: Figure 6-3 Fusion Link Test Mode

    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) •...

  • Page 151: Figure 6-4 Loopback Points Of Dti Card

    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.

  • Page 152: Figure 6-5 How To Set The Fusion Link Test Mode

    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 (2) Initialize the FCH card.

  • Page 153: Figure 6-7 Fusion Link-Test Results

    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. Flash EST3 Send Remains ON Receive Polarity of Mode when available EST2 pair-wire is normal for Ethernet...

  • Page 154: Figure 6-8 Station-To-Station Connection Test (Origination) Via Fccs

    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...

  • Page 155: Figure 6-9 Attcon Connection Test (Origination) Via Fccs

    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.

  • Page 156: Figure 6-10 Line Connection Test (Origination) Via Fccs

    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).

  • Page 157: Figure 6-11 3-Party Conference Trunk Function Test Via Fccs

    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.

  • Page 158: Figure 6-12 Fusion Alternate Routing Test

    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).

  • Page 159: Figure 6-13 Ccis-Fccs Outgoing Call Test

    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.

  • Page 160: Figure 6-14 Loopback Points Of Sdt Card

    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: Local Loopback Loopback tests are performed only on the SDT card at the self-node. Remote Loopback Loopback tests are performed between different nodes.
  • Page 161 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.

  • Page 162: Table 7-1 List Of Fusion-Related System Messages

    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.

  • Page 163: Figure 7-1 Related Hardware

    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.

  • Page 164: Figure 7-2 3-B Pm C-Level Infinite Loop (Permanent)

    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.

  • Page 165: Figure 7-4 How To Replace The Fch (Pa-Fcha) Card

    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 3) Make sure that system message (23-W) "FCH Alternate Routing (Start)" Precautions Required is displayed.

  • Page 166: Figure 7-5 3-C Pm C-Level Infinite Loop (Temporary)

    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 Micropro- cessor (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.

  • Page 167: Figure 7-7 3-E Pm Lockup Failure (Temporary)

    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. Other- wise, move to STEP 2.

  • Page 168: Figure 7-8 Fusion Link (Signaling Link) Failure

    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.

  • Page 169: Figure 7-10 Fch-Dti Connection

    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. Firmly insert the connector on the front edge of the indicated FCH card. DTI (PA-24DTR) ATTENTION FCH(PA-FCHA)

  • Page 170: Figure 7-11 23-S Fch Failure Notification

    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.

  • Page 171: Figure 7-12 10 Base-T Cable Connection Check

    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 23- T FCH Fault Recovery Notification is displayed as the result of cable insertion.

  • Page 172: Figure 7-13 How To Check 10 Base-T Cables

    TROUBLESHOOTING 23-S FCH Failure Notification (Detection) 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.

  • Page 173: Figure 7-14 How To Replace Hub (Pa-M96) Card

    TROUBLESHOOTING 23-S FCH Failure Notification (Detection) DTI (PA-24DTR) FCH(PA-FCHA) ATTENTION HUB(PA-M96) Contents Static Sensitive MNT 3 Handling HUB(PA-M96) Precautions Required When this MB key is set in up position (Make-busy), all 10 BASE-T interfaces connected to this card become inoperative. : 10 BASE-T cable [How to Replace HUB card] to LANI...

  • Page 174: Figure 7-15 23-T Fcch Fault Recovery Notification

    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.

  • Page 175: Figure 7-16 23-U Fcch Status Information

    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 ex- plained on a fault information basis.

  • Page 176: Figure 7-17 23-U Fcch Status Notification - Initial Setting Failure

    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.

  • Page 177: Figure 7-18 23-U Fcch Status Notification - Spanning Tree Abnormal Answer

    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 indi- cated in the following format. "Spanning Tree Abnormal Answer" 1. xx 0x 18 xx xx xx xx xx 2.

  • Page 178: Figure 7-19 Spanning Tree Abnormal Answer

    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.

  • Page 179: Figure 7-20 23-U Ether Transfer Failure

    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.

  • Page 180: Figure 7-21 23-U Fcch Status Notification - Spanning Tree Generation End

    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.

  • Page 181: Figure 7-22 23-U Fcch Status Notification - Spanning Tree Generation

    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..Spanning Tree Generation Start: 00H = Normal FLTINF: 1FH = Spanning Tree Generation Start TRC: Trace Confirmation Bit...

  • Page 182: Figure 7-24 23-W Fcch Alternate Routing Start Notification

    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.
  • Page 183 This page is for your notes. CHAPTER 7 ND-70185 (E) Page 168 Revision 3.0 Get other manuals https://www.bkmanuals.com...
  • Page 184 CHAPTER 8 EX- FCCS 1. General This feature provides the following functions (they are activated when connecting multiple Fusion networks) or a NEAX2000 IVS 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.

  • Page 185: Figure 8-1 Network Connection Type

    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 conjunction with Figure 8-1 for easy understanding of network configuration. The following items and sec- tions explain more details.

  • Page 186: Figure 8-2 Neax2000 Ivs

    EX- FCCS EX-FCCS Network Configuration 2.2 Conditions for Network Establishment (NEAX2000 IVS to NEAX2400 IMX Connection) Conditions for connecting the NEAX2000 IVS to NEAX2400 IMX are described below. 1. All IVS systems must be directly connected to an IMX. See Figure 8-2.

  • Page 187: Figure 8-3 Neax2400 Imx To Neax2400 Imx Connection

    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.

  • Page 188: Figure 8-4 Allowable Span From The Center Fug

    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)”.
  • Page 189 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-IVS in an Enhanced CCIS network. To execute roaming service, connect other Q.931a/IS- 11572 lines. 2.
  • Page 190 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.

  • Page 191: Figure 8-5 Patterns Of Number Portability

    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 Table 8-2 that explain the eight patterns. FUG(A) FUG(B) FPC1 FPC1 FPC2 FPC2 NCN(A) NCN(B) FPC3 FPC4 FPC3...
  • Page 192 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 IVS ) 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...

  • Page 193: Table 8-3 Neax2000 Ivs 2 Fault Information

    EX- FCCS EX-FCCS Features [Centralized Traffic Collecting] 1. The feature to collect traffic information of NEAX2000 IVS system is activated by logging in to the NEAX2000 IVS node with Centralized-MAT for EX-FCCS using the traffic collecting command dedicated for NEAX2000 IVS system.

  • Page 194: Figure 8-6 Centralized Maintenance - Ex-Fccs

    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 System).

  • Page 195: Table 8-4 Ccis Service In Ex-Fccs Network

    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 NETWORK CONFIGURATION FEATURE FEATURE NAME without with CODE NEAX2000 IVS NEAX2000 IVS ×...

  • Page 196: Figure 8-7 Pc Assignment 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.) PC13 PC14...
  • Page 197 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.
  • Page 198 EX- FCCS EX-FCCS Features • Call Waiting Lamp Controll information is sent from the MCI within Center FUG to other Fusion Groups and NEAX2000 IVS system via CCIS. FUG1 (Center FUG) FUG2 Node Node Node Node Node Node Node Node EX-FCCS FCCS (Fusion Call Control Signal) Enhanced CCIS...
  • Page 199 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. •...
  • Page 200 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. When connecting a stand-alone NEAX2400 IMX, non-fusion system (via EX-FCCS) or a NEAX2000 using Enhanced CCIS feature to an existing FUG: (a) The system must be the NCN.
  • Page 201 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...

  • Page 202: Figure 8-8 Port Allocation And Related Command For Ccis Trunk

    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.
  • Page 203 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.

  • Page 204: Figure 8-9 Cic Number Assignment

    EX- FCCS Data Programming STEP 7: ACIC1 Assign CSCG for Basic/Primary Route. The odd numbered CSCG for Alternate Route assignment. CSCG 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.
  • Page 205 EX- FCCS Data Programming <Node which uses CCIS Trunk via Fusion Link (PC1 and PC2 in the example)> 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.
  • Page 206 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.
  • Page 207 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.
  • Page 208 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 •...
  • Page 209 EX- FCCS Data Programming 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.
  • Page 210 EX- FCCS Data Programming 4.2.2 Upgrading CCIS between FUG and IVS2 System to Enhanced CCIS Network FUG (Center FUG) IVS System FCCS Enhanced CCIS FPC1 FPC3 FCCS FCCS FPC2 FCCS CCIS FCCS 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.
  • Page 211 EX- FCCS Data Programming 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 as- signed 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.
  • Page 212 EX- FCCS Data Programming 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 sys- tems 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.
  • Page 213 This page is for your notes. CHAPTER 8 ND-70185 (E) Page 198 Revision 3.0 Get other manuals https://www.bkmanuals.com...

Table of Contents