Home

NEC NEAX2400 Network Cables User Manual

1. AKAN 176 2000 IVS Fault Information cer eR n 178 CCIS Service in EX FCCS 180 ND 70185 E LIST OF TABLES Page ix Revision 3 0 This page is for your notes LIST OF TABLES ND 70185 E Page x Revision 3 0 1 INTRODUCTION 1 General This manual covers the installation of the Fusion system 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 CHAPTER 4 INSTALLATION Consists of the following topics e Static Cautions e Switch Settings PA M96 PA FCHA PA 24DTR CHAPTER 5 DATA PROGRAMMING Provides basic data assignment procedures using the following examples e Installing a new Fusion network e Upgrading a CCIS network CHAPTER 6 POST INSTALLATION TEST Explains how to perform installation tests focusing on the Fusion link connection test CHAPTER 7 TROUBLESHOOTING Explains Fusion related system messages and the repair procedures CHAPTER 8 EX FCCS Consists of the following EX FCCS topics e Network Configuration e Feature Descriptions Data Programming ND 70
2. Note 72 Numbers should be used for activating CCIS services through the network Note 1 This feature is available on the condition that the NEAX2000 IVS is the satellite office Note 2 This feature is available for calling number display only CHAPTER 8 ND 70185 E Page 180 Revision 3 0 5 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 14 LEGEND 5 EX FCCS 11111 Enhanced CCIS Fusion Group FUG Figure 8 7 PC Assignment in EX FCCS Network 3 The CCH to be used is selected as follows 1 when the call is processed using the speech line Bch the outgoing incoming route Logical Route LRT decides CCH LRT gt PC gt CSCG gt CCH 2 when the call is processed without speech line Bch inter office service such as CALL BACK MESSAGE WAITING service MCI etc the called party s number or PC of the destination decides CCH a the called party s number gt LRT PC gt CSCG gt CCH b PC CSCG CCH 3 when logging into NEAX2000 IVS or remote FUG from the Centralized MAT PC of the node to be logged in decides CCH a NEAX2000 IVS PC gt CSCG gt CCH b Remote FUG FUG FPC P
3. 41 14 Figure 3 7 Fusion Nenvork 1 22 sace x aos que cay d obe CR OR Cadets 14 Figure 3 8 Leading Tandem GoanDBOIONS VAGA EY RO X ORO CRY RS UR d 15 Figure 3 9 Maximum Number of Ports between Nodes 15 Figure 3 10 Connection Trunk Alternate Routing 16 Figure 3 11 Fusion Network on an Associated Basis 16 Figure 3 12 Cenivalized Billig Fusion 1 3 au eua RO ERR WES UR d 18 Figure 3 13 Centralized Management 21 Figure 3 14 Centralized Management Report Fusion Example 1 22 Figure 3 15 Centralized Management Report Fusion Example 2 23 Figure 3 16 Centralized Management Report Fusion Example 3 24 Figure 3 17 Operator Cals on a Fusion uaa ee wee ted SO RUE tees 25 Figure 3 18 Ring Down Calls on a Fusion 26 Figure 3 19 Day Night Information Transfer by ATTCON DESKCON 27 Figure 3 20 Day Night Information Transtar uso veda du ere XX Ru P E XAR RU 27 Figure 4 1 esc t uen Tel seca Que bis RP ERA REV ED Pee wd eerta E aq E IE 29 Figu
4. DTI PA 24DTR CONSE TT ni EE Beans Required MB 5 MB E E FE E 10AL 10 FLT CA gt B i 10AL 10 FLT cal al 27 1 OAL 1 O FLT CA E Anti static Kit FRONT VIEW FRONT VIEW MA Figure 4 9 Connecting Front Cables CHAPTER 4 ND 70185 E Page 42 Revision 3 0 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 ATTENTION Contents Static Sensitive Handling Precauli DTI A 24DTR L 10 FLT CA 10AL 10 i CN2 OVERVIEW FRONT VIEW Figure 4 10 FCH Cascade Connections ND 70185 E CHAPTER 4 Page 43 Revision 3 0 INSTALLATION Connecting Cables 4 2 Connecting 10 BASE T Cables Figure 4 11 shows sample cable connections where HUB 96 cards are provided in a dual configu ration and the PA FCHA card is located in 1 1 IMG When HUB cards are pro vided in a dual configuration the two HUB cards must be connected on each front edge connector using a 10 BASE T cross cable However when dual LANIs LANI A and
5. 149 Figure 7 3 How to Initialize the FCH PA FCHA 149 Figure 7 4 How to Replace the FCH PA FCHA 150 Figure 7 5 3 C PM C level Infinite Loop 151 Figure 7 6 D PM Lockup Failure Pemanen 2 Rees ees RERO Yap 151 Figure 7 7 PM Lockup Failure Temporaly 225555428 948 945 OR REG CRGA 152 Figure 7 8 Fusion Link Signaling Link 153 Figure 7 9 13 H 13 1 13 J Signaling Link Failure System Message 153 Figure 7 10 PORE GODBEBBIT dw aed dub eae y aer dd 154 Figure 7 11 22 9 FOH NoBIGSEOIT usua eo ck brbRIOr I RR bd AG Rae RA YEA 155 Figure 7 12 10 BASE T Cable Connection Check RR 156 Figure 7 13 Haw te Check 10 BASE T Cables sae RR eek ar wh 157 Figure 7 14 How to Replace HUB PAM96 Card Bec Rue Rue ud be dde 158 Figure 7 15 23 Fault Recovery Notifications 159 Figure 7 16 284 FOCH Status Oe RR SERED 160 Figure 7 17 23 0 FCCH Status Notification Initial Setting
6. Set the SENSE Switch arrow to the proper direction referring to Table 4 1 Note and 4 to F of the SENSE Switch are not available in this version Figure 4 4 Switch Setting on HUB PA M96 Card Table 4 1 SENSE Switch Setting STANDARD SWITCH NAME SETTING SETTING DESCRIPTION SENSE Polarity indication on the STn lamps for TPn Xports Not used TPn X ports operate as a repeater HUB Standard setting Data Packet Collision indication on the STn lamps for TPn X ports Not used CHAPTER 4 ND 70185 E Page 32 Revision 3 0 INSTALLATION Key Setting on Circuit Cards 2 2 PA FCHA FCH Set the switches on the FCH 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 ES D I channel CH3 example Jo Yt Cuba Contents Static Sensitive Handling OFF Precautions Required 16 17 18 19 20 21 22 23 p FCH PA FCHA Card Pee ctp n 8 9 10 11 12 13 14 15 Make busy request lf 2 J S T4 12334567 CH Note Multiple choices are OFF SW14 3 Not Used available Refer to Table 4 3 P MNT MNT 10 I
7. CNT 5 CR Connection Route E il ES AFRT Assignment of FCCH Controlled Connection Route Data for Local a Figure 5 30 AFRT Command Display ND 70185 E CHAPTER 5 Page 83 Revision 3 0 DATA PROGRAMMING Assignment of FCH Related Data STEP3 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 Figure 5 31 shows a sample Fusion network Each number in the circle represents the Fusion Point Code FPC LN Network Control Node LN Local Node Figure 5 31 Fusion Network example The AFPC command display Fusion with FCH should look similar to the following AFPC Assignment of FCCH Routing Data for Local Assign Destination FPC far end FPC FPC FCCH 0 Fusion without FCH 1 Fusion with FCH 22 1 22 EE FCH number 1 255 CNT C RT FOHNIFPON CNT C RT FCHN FPCN For Help press F
8. E Make Busy Information 0 Make Idle 1 Make Busy Outgoing Figure 5 26 MBCT Command Display 7 Assignment of FCH Related Data STEP 1 For Fusion with FCH only e Assign Number on an PA FCHA circuit card basis e The FCH Number must conform to the following conditions FCH Number range must be between 1 and 255 At the network level the same FCH Numbers can be assigned However they must be unique at the node level Use sequential numbers starting from 1 as FCH Numbers ND 70185 E CHAPTER 5 Page 81 Revision 3 0 DATA PROGRAMMING Assignment of FCH Related Data Figure 5 29 shows a sample data assignment when FCH cards are located in the 0 slot 4 and 2 slot 11 Use odd number as the Group No and Level 0 for the FCHN FCH card example 1 example 2 Regular density slot 04 High density slot 11 LENS 011190 FCHN 2 PIM 2 Slot 11 DTI DTI SlotNo 04 05 SlotNo 11 12 Group No Group No B Dch TK1 Bch TK8 Doh TK1 Bch TK23 Ow LENS 000270 FCHN 1 E Pph TK23 8 0 Slot 04 i AP Bch TK17 Bch TK1 FOR 02 Bch TK16 PBX FR OIN FCH 9 5 8 Bch TK9 i 9 fi Sr Bech TK9 Bch TK8 9 d o H FCHEN 8 i XX x 190 94 Bch TK1 Data Assignment m
9. 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 LGRT 300 ACIS CIS Node A m Node C 5 5 91202 A in 91303 area B e Logical route to be seized Access code STN A STN B STN C 1st LGRT 200 2nd LGRT 100 3rd LGRT 300 Ist LGRT 200 LGRT 200 2nd LGRT 100 1st LGRT 100 Ist LGRT 100 LGRT 100 2nd LGRT 200 3rd LGRT 300 2nd LGRT 200 Note When the related data is assigned to DM outgoing connection is available only for external routes in self node i e FCCS ACIS link cannot be established To initiate seizure of an external trunk one of four methods OGC OGCA LCR LCRS can be used See the following sections 7 1 1 A procedure for assigning the OGC access code is explained using the following example Node B Node A COT PSTN STN B 1 202 345 6789 Station B dials 9 1 202 345 6789 Figure 5 36 Example of OGC ND 70185 E CHAPTER 5 Page 87 Revision 3 0 DATA PROG RAMMING Assignment of FCH Related Data STEP 1 STEP 2 STEP 3 STEP 4 ANPDN ANP
10. ND 70185 E CHAPTER 5 Page 131 Revision 3 0 DATA PROGRAMMING Office Data Sheets 8 18 Data Sheet for AFRFL ACC FPC 1 253 MAX 24 digits CHAPTER 5 ND 70185 E Page 132 Revision 3 0 CHAPTER6 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 e How to Check Fusion Link by LEDs Card Repair Procedure When LED Indicates Abnormality e 5 Network Connection Test e FCCS Alternate Routing Test Fusion and Non Fusion Connection Test At the end of this chapter the Fusion Link Test Sheet is attached Make photo copies of the sheet to record the test results In this chapter explanations are given using the following network numbering as an example Node B other Node Node A self Node STN 2000 FUSION Network TELN 410000 STN 2000 FCCS Fusion Call Control Signal STN Physical Station Number Telephone Number Figure 6 1 Fusion Network Note The Individual Trunk Access feature is not available for Fusion Trunks To seize a specific Fus
11. 161 Figure 7 18 23 U FCCH Status Notification Spanning Tree Abnormal Answer 162 Figure 7 19 Spanning Tree Abnormal Answer 163 Figure 7 20 Z8 ETHER Fone ong cece deed ceed tx dona RR EORR Re RR 164 Figure 7 21 23 0 FCCH Status Notification Spanning Tree Generation 165 Figure 7 22 23 0 FCCH Status Notification Spanning Tree 166 Figure 7 23 23 0 FCCH Status Notification Checksum Verification 166 Figure 7 24 23 W FCCH Alternate Routing Start Notification 167 Figure 7 25 23 FCCH Alternate Routing End 167 ND 70185 E LIST OF FIGURES Page vii Revision 3 0 LIST FIGURES CONTINUED Figure Title Page Figure 8 1 Network Connection TYDE 5996 se PR d EAE 170 Figure 8 2 NEAX2000 IVS to NEAX2400 IMX 171 Figure 8 3 NEAX2400 IMX to NEAX2400 IMX 172 Figure 8 4 Allowable SPAN from the Center 173 Figure 8 5 of Number Portabllibi 2242 2 Yid ded 176 Figure 8 6 Cantralized Maintenanos EX
12. 2 2 ERONT VIEW PIM 1 PIM 1 UTP CTG5 ST PIMO 00 010203040510 5 UTP ST DECR 00 01020304051 fr UTP 05 ST CA Ik ee BASEU Figure 4 16 Examples of Ethernet Cable Connection FCH PIM3 1 IMG System 1 2 CHAPTER 4 ND 70185 E Page 54 Revision 3 0 INSTALLATION Connecting Cables Note lt FCH in PIM3 Pattern 3 FCH in Pattern 4 TOPU TOPU CTG5 ST CA L ATTENTION fecaulfons Required PIM 3 PIM 3 PIM 2 PIM 2 FANU PIM 1 UTP CTG5 ST CA N UTP CTG5 ST CA N UTP CTG5 ST CA J PIM 0 01 02 UTP CTG5 ST UTP CTG5 ST CA J LPM LI 0102031040577 LPM UTP CTG5 ST CA J BASEU J BASEU When dual are used in both Slot 00 and 03 of CPR Pattern 3 or 4 be sure to use HUB cards One HUB for internal LANI in Slot 00 and the other for ex
13. ACRD gt AFPC Available command at NCN Figure 5 1 Data Programming Flow Chart ND 70185 E CHAPTER 5 Page 57 Revision 3 0 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 1 1 1 Note To install the Fusion network as a brand new system the overall data programming procedure is as follows System Data Decide an NCN and LN on the network e Assign System Data for each node Use the ASYDN command for the NCN and the ASYDL com mand for all nodes 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 e Assign unit data using the AFMU command for each node which exists on the network Note that the AFMU command is available at NCN only e Assign Logical Route Numbers for all routes external trunk on the network using ALRTN command Note that the ALRTN command is available at NCN only 1 1 2 Numbering Plan Data Note e ANPDN ASPAN for NCN only Assign numbering plan data for Telephone Number e ANPDL ASPAL for NCN and LN Assign numbering plan data for Service Codes Trunk Ac cess Codes etc other than STN physical station and TELN e ASPA for NCN and LN Assign numbering plan data for Physical Station
14. oj x 10 B ch N AR tA oOo Oo oO OF CO CO oo N NIN DI c o o o o o 11 D ch CHAPTER 5 Page 80 Revision 3 0 Ol Oo oO CO Oo CO oO oO OT Oy Oo OY OF Oy am N N N N N N N N N N N N N N NI N N N NI NI NIN Wl BW WI NI NI F2 F2 N NI N ej ej ej ej ej ej Rete NI OINI MY amp NTR OLN HY RI NJI ej ND 70185 E mounting slot pri Slot No Group No Dch TK2 11 12 Deh TK1 Bch TK23 Bch TK17 Bch TK16 Bch TK9 Bch TK8 Ow Bch TK1 STEP 4 DATA Assignment of FCH Related Data 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 MBCT Make Busy of Connection Trunk Data MBCT Make Busy of Connection Trunk for Local C RT C RT 1023 5 TK 1 4095 WRT
15. sre gr ducem 140 3 2 1 ATTCON Call Origination 140 3 2 2 Call Termination 140 2 3 Line LC ELC DLC Card Connection Test via 141 3 3 1 Line Origination Test Confirmation of Physical Telephone STN Number 141 3 3 2 Line Termination Test Confirmation of Telephone STN Number 141 3 3 3 Line Connection Test Case of Hot Line House Phone 141 3 4 3 party Conference Trunk Function Test via 142 25 FOCS Alters iaces qe award dide don NUR d alan 142 Paiman Route TOS esos dicem x dope edo C RAO ow dob s e os 143 2 5 2 Altemate Route Trunk Test dane eee dde RODEO X 143 4 Fusion and Non Fusion Connection 143 4 1 When Seizing a Tunk from a Stallion 144 4 2 When Seizing a Trunk from an 144 m SEI Gard Loopback edd dece 145 ND 70185 E TABLE OF CONTENTS Page iii Revision 3 0 TABLE CONTENTS CONTINUED Page GHAPTERT TROUBLESHOOTING 4 12 duro sy PRO ERE
16. ND 70185 E ISSUE 3 STOCK 200869 NEAX 2400 IMX 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 DM are registered trademarks of NEC Corporation All other brand or product names are or may be trademarks or registered trademarks of and are used to identify products or services of their respective owners MS DOS and Microsoft are registered trademarks of Microsoft Corporation Microsoft Windows 95 and Windows NT are trademarks of Microsoft Corporation Copyright 1998 1999 2000 NEC America Inc Printed in the U S A PACE NG Issue No PAGE No Issue No 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 i 1 2 29 1 2 3 ii 1 2 3 30 1 2 3 iii 1 2 3 31 1 2 3 iv 1 2 3 32 1 ome 1 2 33 1 2 3 vi 1 34 1 2 1 2 NS 35 1 viii 1 2 3 36 1 2 1 2 37 1 2 1 38 1 2 3 1 1
17. When FCH and FGH cards are mounted in the following slots with the specified RT numbers data setting is as follows C TK FCH RT14 FGH RT15 U ATS eroe as ur wo n E EOE 1114 0 0 0 0 DUE 1116 0 0 0 0 3 5 Loans arfor ofofo eto o o o 3 7 puss foots tis tLlY H d SLLH HOJd Wr er ee iH ayo 510105 510121 zs Figure 5 42 Sample Data Assignment ACTK ND 70185 E CHAPTER 5 Page 99 Revision 3 0 DATA PROGRAMMING Assignment of FCH Related Data STEP3 AFCH Assign number on an 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 AFCH command display FCHN FCHEN IP address 000030 Note 1 zm ROUTER Note 1 7his setting is a sample IP address aaa aaa aaa a External LAN RT14 FCHN 1 Note 2 FCHEN 000030 Internal LAN CPU Note 2 This card cannot be used as a CCIS 7 signaling channel Figure 5 43 Assignment of FCHN Example STEP 4 AGIP Assign IP addresses of card and its connected router FCHEN FCH Equipment Number Assign LV
18. OOOOOOOOOOO0O0O0OO0O0000000000 PBA FPC 1 FPC 13 MG 0 UNIT 0 MG 1 uo u 1 RE UNIT 1 UNIT 2 22 UNIT 3 Node D uo u 1 MG 1 UNIT 0 13 UNIT 1 Figure 5 8 Assignment of Module Accommodation Data The AFMU command display should look similar to the following AFMU Assignment of FPC and MG and UNIT for Network Data Memory Fusion Point Code 1 253 UNIT 1 fo MG Module Group Number 0 7 um U Unit Number 0 3 Note For more information on each parameter please see the Office Data Specification manual Figure 5 9 AFMU Command Display ND 70185 E CHAPTER 5 Page 65 Revision 3 0 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 The Logical Route Numbers should be alloted to the whole external trunks such as the Non Fusion trunks including COT TLT DAT and LCR as well as DTI s B ch and D ch used for Fusion Assign the necessary data by using the ALRTN command Internal Trunk Fusion Relat
19. Anti static Kit MBR key operation 2 Turn ON the MNT 3 switch make busy request 3 Make sure that system message 23 W FCH Alternate Routing Start 5 Disconnect the front cable from the FCH card with care 8 Turn ON the MNT 3 switch on the new FCH card make busy request 9 Turn the MB key upward on the new FCH card 11 Connect the disconnected front cable again with care 14 Make sure that system message 23 X FCH Alternate Routing Stop FCH DTI Coni Handlin ATTENTION tents Static Sensitive Precautions Required M OPE 7 MNT LH d mm MB key operation FCH PA FCHA FCH DTI OPE MB uis HHHH 55151558 BEE 3 Front Cable Cable Disconnection MB MNT CHAPTER 7 Page 150 Revision 3 0 Figure 7 4 How to Replace the FCH Card ND 70185 E TROUBLESHOOTING 3 PM C level Infinite Loop Temporary 3 3 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 appr
20. 0 CHAPTER 4 ND 70185 E Page 40 Revision 3 0 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 ATTENTION ntents DTI PA 24DTR FCH PA FCHA BN 4 EY 2a DD S Anti static Kit RS i n 6 HUB X Nd X X S Figure 4 8 Mounting FCH and DTI Cards ND 70185 E CHAPTER 4 Page 41 Revision 3 0 INSTALLATION Connecting Cables 4 Connecting Cables 4 4 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 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 DCH is equipped with two Handler circuits per card A jq Connect 10AL 10 FLT CA to the connectors 1 1
21. ETT cM 29 1 1 TEES 31 E Fey BN On DP dedicar dca do od dio 32 2 1 HUE ee eed deed Cees dee ae eee Eq dV ate d Ep 32 2 2 uos p ORO FOE RECTO 39 2 3 Pe BaD TAD PCT r 35 2 4 itat PADS SEE eens Ace Su iod UR de cen ede 39 ND 70185 E TABLE OF CONTENTS Page i Revision 3 0 TABLE CONTENTS CONTINUED Page 3 Croot cards M PIN Ea S QR E d XA RP OSEE AE SR 40 3 1 Mounting HUB LEAS GFW 55356255 RT ques er uer qe det EE E 40 32 Mounting FCH PA FCHA and DTI PA 24DTR 41 S SII o caudae dax sspe SAC d RGB hare d Rd eau qd dad deest 42 4 1 Gannecang Front Cables iussi osque RR PERRA OA R 42 4 2 Connecting TO BASE T Eee pape dd 44 4 3 10 BASE T Connection 45 43 1 Procedure ior 1 IMG ka RE 3E ARE XX RR ERR RA RR 45 4 3 2 When using cable unit SR1201 ETIF 45 4 3 3 When not using the cable unit SR1201 46 4 3 4 Procedure for 4 IMG
22. Figure 6 6 Loopback Point Designation STEP 3 When the LYR LED flashes at 60 INT the loopback in the block specified in Step 2 is OK ND 70185 E CHAPTER 6 Page 137 Revision 3 0 POST INSTALLATION TEST FCCS Network Connection Test When the result of test is OK the LYR LED flashes Make sure that the L YR LED flashes at 60 INT ae b PA FCHA card EST3 Send LYR Flash N B RES MNT wh av Receive Polarity of TS 3 n avai abe ESS EST2 pair wire is normal Mode thernet e EST Receive Vr esto Linkis Ta established AR reac No Da ro data pac Sexe Front View s Front View Note When the FCH is a Root Bridge the LOAD LED remains Figure 6 7 Fusion Link Test Results STEP 4 Return Mode to 8 standard setting when the test is complete STEP 5 Initialize the PA FCHA card using the MB switch Note Besure to initialize the FCH PA FCHA card after changing the setting of the Mode Switch 3 FCCS Network Connection Test This section explains how to perform the following connection tests within the Fusion network e Station to Station Connection Test via FCCS ATTCON Connection Test via FCCS Line LC ELC DLC card Connection Test via FCCS e 3 party Conference Trunk Function Test via FCCS 3 1 Station to Stati
23. Remane oN XX Receive Polarity of Payload Z LED Indication B for Ethernet pairwire is normal Line Receive A Internal If any LED is ON refer to the Circuit SAL ON Card Manual ESTO Link is a established 0 when loss occurs LOAD c 0 FRM when Frame Loss occurs Remains ON 8 0 BER when Bit Error occurs when ready to broadcast 0 On when Remote Alarm is received data packets Note a AIS On when AIS signal is detected 0 o M DTI 0 0 Front Cable 9 FCH FRONT Note When the FCH is a Root Bridge the LOAD LED remains ON When the is Backup Bridge the LOAD LED flashes 60INT Figure 6 2 LED Indications on Fusion Link Related Circuit Cards 2 Repair Procedure When LED Indicates Abnormality If the LED indication appears abnormal check the following items again 2 1 Front Cable Make sure that front cable 1OAL 10 FLT is securely inserted into the connectors CHAPTER 6 ND 70185 E Page 134 Revision 3 0 POST INSTALLATION TEST Repair Procedure When LED Indicates Abnormality e PA FCHA switch setting Make sure that the following keys are set properly e Dch TS designation Och 23ch SW11 SW12 SW13 e Data Link Signal Logic positive negative SW14 1 e Fusion Data Link Speed 48 56 64 kbps SW14 2 3 LAPD Signal Link user netwo
24. ed ames qe EE 57 ND 70185 E LIST OF FIGURES Page v Revision 3 0 0101 Figure 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 41 Figure 5 42 Figure 5 43 Figure 5 44 Figure 5 45 Figure 5 46 Figure 5 47 Figure 5 48 Figure 5 49 Figure 5 50 LIST OF FIGURES Page vi Revision 3 0 LIST OF FIGURES CONTINUED Title Page Fusia GI NND 2 E tov SUE XE P QU VERE ew PR PE 60 How to Upgrade the Numbering Plan Data of an Existing CCIS Network 61 Assignment of Memory 62 and Allocation ASYDL has Xx E RARE EAE T ERR 62 Sell FPC ASSIQBEUL 225555255993 XP CU ere RESCUE Ed E AX Cd eor sea 63 ASYDN Command Display example ideae ra kh RR RR RR RR 64 Assignment of Module Accommodation Data 65 Command Display cR
25. 161 92 FLTINF 18H Spanning Tree Abnormal Answer 162 BE PEOCEOU E usata x dX EAE REE Reed ee 163 9 3 FETINI TEM ETHER Fallurg 432222 REG See dR ous XS x 164 9 4 1EH Spanning Tree Generation RR RR RR Rn 165 9 5 FLTINF Spanning Tree Generation 166 9 6 FLTINF 85H Checksum Verification Failure 166 10 23 W FCH Alternate Routing Start 167 11 23 X FCH Alternate Routing End Notification vues 167 GHAPTER O EX FOCO same oc dq 169 Ac saas quad Ea 169 2 EAC Network e mob E pe Ed Rap dud de 170 2 1 Network Configuration ax s REREuT ERG OO REA ARR Rx EORR OA EROR ARA 170 2 2 Conditions for Network Establishment NEAX2000 IVS to NEAX2400 Connection 171 2 3 Conditions for Network Establishment NEAX2400 IMX to NEAX2400 IMX Connection 172 2 4 Fusion Nehari Group FUG deed accade beer x quei 173 25 T aad hh Bel
26. FCH Mounting Location Note 1 FLTINF Fault Information consists of the following OOH Initial Setting Failure Notification ISH Spanning Tree Abnormal Answer Notification IDH ETHER Transfer Failure Notification 1 Spanning Tree Generation End Notification IFH Spanning Tree Generation Start Notification 65H Check Sum Verify Failure Notification Note 2 When 1 the subsequent data indicates Date Information Primitive Contents The detailed fault information is explained on the following pages Figure 7 16 23 0 FCCH Status Information CHAPTER 7 ND 70185 E Page 160 Revision 3 0 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 Ox Z00 xx XX XX 2 0000 0000 LILI for 6 Bytes MAC Address of FCH b7 L Other Results b7 50 h ETHER Results See below L ETHER Results b7 bo __ HDLC Results Normal HDLC Results 2 E REM FLTINF 00H Initial Setting Failure b7 TRC Trace Confirmation Bit E T 0 1 Status Notification Primitive Trace RS Receive Send Primitive Trace not effective FCH CKT No
27. dua HARES HAR EE AES 65 Telephone Number gt 255 455555 995 998 66 Assignment or Logical Route NUMDO ss2cdos aces Chas REOR e3 weg REC RES RES 66 ALRIN Command DISplay RR Reb RR E Rd E 67 Telephone Number Allocation 2 2 4 67 ANPDN Sample Data Short aic 232 A RR teks Poet teneawsakds 68 ANFEN Commend suo ae we ded pa e duct dade eade dd 68 ASPAN Sample Data 69 Command Display RARE 69 ALGSN Sample Data Sheh 6 1825 deeds 70 ALGSN Command Display example ees uer aso RYE RR ans 71 EOD und ioa d agone I OR RO Reo opui DRE RAR OGRA RR 72 ACRD Command Display 72 ACTK Command Display example 76 Mounting FCH and DTI Cards in Regular Density Slots 76 Mounting FCH and DTI Cards in High Density 78 How to Assign LEM Data 2 cc ccccasc duce a ra RA RR CERE XAR 79 Command 55552255 Oho RO RUEDA E Qc Pope ord BR RA
28. 01090010030020210 100100100202070010010 fo gT 0000000004111106341997 CCIS Cen 1225223209199712252314 Doni ces 010112345000000000008 IMX Billing Format CCIS 144 Bytes Call Base Table 01 01090010030020210 N 100100100202070010010 00000000041 11106341997 1225223209199712252314 010112345000000000008 CCIS Fusion Call Control Signal FCCS i Channel i i Inter Office Signaling CCIS Figure 3 12 Centralized Billing Fusion 1 3 CHAPTER 3 ND 70185 E Page 18 Revision 3 0 SYSTEM CONFIGURATION System Considerations Example 4 Node A tries to collect the billing information of Node B and Node C 5 using polling method Node A cannot collect the billing information of Node C via 5 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 i Fusion Center Node Fusion Network i CCIS Center Node Billing Information of Node B Billing Information of Node C Example 5 Node A tries to collect the billing information of Node B via FCCS using polling method Node A cannot collect the billing information of Node B via FCCS Node B sends the billing information to Node C via CCIS ignoring polling from Node A Node B deletes t
29. 1 All IVS systems must be directly connected to an IMX See Figure 8 2 NEAX2000 IVS B cannot be added to NEAX2000 52 which is already connected with NEAX2400 IMX UNAVAILABLE Enhanced CCIS IMX Figure 8 2 NEAX2000 IVS to NEAX2400 IMX Connection 2 number of logical routes available 899 in the FCCS network is reduced by one for every route provide in the NEAX2000 IVS when connected via Enhanced CCIS Note above is a condition of data assignment in the NEAX2400 IMX system The NEAX2000 IVS system accommodates up to 255 nodes including NEAX2400 IMX and NEAX2000 I Vs systems The number of point codes assignable in the NEAX2000 IVS system is amaximum of 255 including Enhanced CCIS net works 3 When directly connecting a NEAX2000 IVS to a NEAX2400 IMX one signal channel may support multiple voice routes However when the Enhanced CCIS function is provided with EVENT BASED CCIS a signal route must be provided per voice route ND 70185 E CHAPTER 8 Page 171 Revision 3 0 5 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 and NDM exist individually in each Fus
30. Circuit No of FCH TRC RS FCH CKT No b7 50 Je u LEE MG Module Group 0 Unit 0 3 FCH Mounting Location G Group 0 23 Figure 7 17 23 FCCH Status Notification Initial Setting Failure ETHER Results 00H Normal 01H ETHER Controller Reset Impossible 03H ETHER Controller Initial NG 02H Configuration Error 04H ETHER Controller Initial NG ND 70185 E CHAPTER 7 Page 161 Revision 3 0 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 Ox XX XX XX 2 XX XX XX XX XX XX 3 XX XX XX XX XX XX XX XX 4 XX XX XX XX XX 5 XX XX XX 00 0000 0000 6 0000 0000 0000 0000 b7 50 15 14 13 12 11 10 9 8 23 22 21 20 19 18 17 16 239 238 237 236 235 234 233 232 247 246 245 244 243 242 241 240 255 254 253 252 251 250 249 248 57 50 XQ aa eee Each bit represents abnormal FPC Fusion Point Code When 1 is set the FPC has not been assigned Use the AFPC command 32 Bytes b7 bo T Abnormal Information b7
31. Make idle all the trunks which were placed in make busy state in STEP 1 and STEP 2 Primary Route Node A Self Node Alternate Route STNB TELN 420000 STN 2000 Figure 6 12 Fusion Alternate Routing Test Fusion and Non Fusion Connection Tests Use the following procedures to perform the connection test between the FCCS and non Fusion Common Chan nel Interoffice Signaling CCIS or Associated Channel Interoffice Signaling ACIS ND 70185 E CHAPTER 6 Page 143 Revision 3 0 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 STEP2 Station A in self node Node A dials the Physical Station Number for Station B in Node C STEP3 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 STEP 6 Repeat the above steps for all Fusion links Check 4 2 When Seizing a Trunk from an ATTCON STEP 1 The operator at the ATTCON in Self Node Node A dials Physical Station Number for Station B in Node C STEP 2 call terminates to Station B via and non FCCS STEP3 Confirm the speech condition is sufficient no noise not one way speech etc STEP 4 The operator at the ATTCON releases the call by p
32. Network Control Node LN Local Node STN Physical Station Number Note The ALGSN command is used for assigning Telephone Numbers See 5 6 Assignment of Telephone Numbers for more detail Figure 2 2 Free Location 2 1 Centralized Maintenance Administration Terminal MAT A Fusion network has one Network Control Node NCN and Local Nodes LNs The NCN has the Cen tralized MAT which runs on Windows 95 NT The MAT can collect fault information from all nodes on the network The NCN has Network Data Memory which stores the data related to network level The Tele phone Numbers for example can be changed using the Centralized MAT at the NCN The MAT also al lows the user to manage network level office data Fault Information Node B December 12 1997 AM 3 12 13 Fusion Link Node B Failure MG 00 U 02 11 Fault Information Note Network Control Node Local Node Note Actual system message is indicated in a different format Figure 2 3 Centralized MAT on Fusion Network CHAPTER 2 ND 70185 E 4 Revision 3 0 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 Dch 64K 1 5 4 9 ft 1OBASE T 10 5 10 5 Digital Trunk Interface Fu
33. 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 Example data assignment is shown in Figure 5 54 and Figure 5 55 FPC USE GATE FPC USE GATE FCHN FCH Number NEXT IP bbb bbb bbb b FCH Number DST IP bbb bbb bbb b bbb bbb bbb b A maximum of 8 routings are available Figure 5 54 Sample Data Assignment AETH destination information embedded in the packet Internet Intranet CCC CCC CCC C DST bbb bbb bbb b I i shioutos ROUTER aaa aaa aaa a Router bbb bbb bbb b Wes C_RT 1 speech placing a via FCCS Destination Node does not change Address of node to be passed to DST_IP NEXT_IP _ Destination IP Next IP Figure 5 55 How to Assign Destination IP and Next IP ND 70185 E CHAPTER 5 Page 107 Revision 3 0 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
34. Destination Poin Fusion Call Control Signal FCCS Common Channel Inter Office Signaling CCIS Figure 3 12 Centralized Billing Fusion 3 3 CHAPTER 3 ND 70185 E Page 20 Revision 3 0 SYSTEM CONFIGURATION System Considerations 3 3 Centralized Management Report Fusion To collect fault information in a Fusion network the Centralized Management Report Fusion is used This feature provides automatic reporting of fault occurrence from Local Nodes to Center Node Service condi tions for this feature are shown below Node B Node D FCCS Centralized MAT Fusion Figure 3 13 Centralized Management Report Fusion e Center Node for Centralized Management Report Fusion is specified in the following system data ASYDL SYSI Index 532 FPC of Center Node for Centralized Management Report Fusion At Center Node system messages received from the other nodes are stored the buffer memory for Centralized Management Report Fusion e MAT connected to Center Node polls only the self node e Office Name ASYD Index 96 through 115 is used for identification of each node When a system message printer is connected to a node other than Center Node system messages sent to Center Node are also output to the system message printer e When system message has been sent to Center Node the message is regarded as an old message When the system fails transmission
35. EY 2 0 000010 i D D Figure 5 22 Command Display example The mounting location of the FCH DTI cards can be classified into the following two types Regular Density Slot 16 port slot See Figure 5 23 High Density Slot 32 port slot See Figure 5 24 and Figure 5 25 6 1 1 When is mounted in a Extended Density Slot If the FCH is to be mounted in the Extended Density Slot the connection trunk should be assigned as shown in the figures below If the card s mounting location is in any of the Slot Nos 04 06 08 or 15 17 19 the following extended Group should be used for the Dch trunk G27 29 or 31 Figure 5 23 shows an example where the cards are mounted in density Slots 04 or 05 0 02 04 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 example I 15 19 23 15 19 23 05 07 09111 _ 4 01 03 05 07 09 11 o g 7 14 Bree ss 14 18 22 hl 13 17 21 5 5 13 17121 i 04 06 08 10 00 02 04 06 08 10 12 16 20 12 16 20 L 16 Port 32 Port 16 Port 32 Port FRONT VIEW Figure 5 23 Mounting FCH and
36. 1 1023 FCHN 1 255 3 4 5 6 CHAPTER 5 ND 70185 E Page 128 Revision 3 0 8 15 Data Sheet for AETH DESTINATION FPC FPC 1 253 GATEWAY USING FLAG USE GATE 0 1 CONNECTION ROUTE C RT 1 1023 DATA PROGRAMMING Office Data Sheets DESTINATION IP ADDRESS DST IP NEXT IP ADDRESS NEXT IP ND 70185 E CHAPTER 5 Page 129 Revision 3 0 DATA PROGRAMMING Office Data Sheets 8 16 Data Sheet for AGIP LINE EQUIPMENT NUMBER OF FCCH FCHEN U G FGH IP ADDRESS FGH IP IP ADDRESS FOR DEFAULT GATEWAY DG IP VOICE CHANNEL CONTROL TYPE CONTTYP 0 1 QSIG PRIME LINK NUMBER LINK NUM 0 32 CLIENT SERVER CONNECTION MAX NUMBER CSLINK NUM 0 15 CHAPTER 5 Page 130 Revision 3 0 ND 70185 E DATA PROGRAMMING Office Data Sheets 8 17 Data Sheet for AFIP LINE EQUIPMENT LINE EQUIPMENT NUMBER OF NUMBER OF FGH ROUTER ACCESS NUMBER FGHEN QSIG PRIME Bch RT ACC LENS Max 16 digits U G MG U G LV
37. 46 4 3 5 Procedure for IMX U 47 GHAPTER OS DATA PROGRAMMING ui pde ade Rede dau br eR Eq qe P EIC Iq S7 1 Network Data Programming Summary 58 1 41 Brand new Fusion Network usas 4 Re RARO AEG ORA AREA RARO REOR 58 4 Vas crete 58 Fiat OON e dos dade up e 58 13 9 Staton 2 eg REX 58 LA POSING OMe 224235545426 d d dre 4 eens 58 he Up reding a OCIS PRESE ede desea se Vala 59 el vue de RSS Teque bee id dame 59 Lez dMunenag Plan Deli oos secedere pde X RO CRY Ro GR RC red 59 Lee Staten NUMBING Good RUE GRECIA ERR E RR 59 Jensen Links Dales uses ts x RA Sees SOURCE SAX te eS 59 1 3 odore a au ees V p qd ade qu RE Rad e MUR Ede 60 2 Assignment of System Data 22 are hu RR ERRARE RRRMARERX ERE 62 3 Assignment of FPC and MG and UNIT into 65 21 eee EET 65 4 Assignment of Logical RT in Network DM iius e RR X Xx ERR RR
38. 8 3 Data Sheet for ANPD ANPDL ANDPN TENANT NUMBER TN 1ST DIGIT 1ST DC CONNECTION STATUS INDEX BUSY LAMP FIELD BLF CHAPTER 5 Page 114 Revision 3 0 ND 70185 E 8 4 Data Sheet for ASPA ASPAL DATA PROGRAMMING Office Data Sheets ANNOUNCEMENT ANNOUNCEMENT TENANT CODE UST KIND OF TENANT EQUIPMENT NUMBER SERVICE NUMBER NUMBER REMARKS 1 125 122 125 N Normal 10 H Hooking N Normal 10 H Hooking N Normal 10 H Hooking N Normal 10 H Hooking N Normal 10 H Hooking N Normal 10 H Hooking N Normal 10 H Hooking N Normal 10 H Hooking N Normal 10 H Hooking N Normal 10 H Hooking N Normal 10 H Hooking N Normal 10 2 Hooking N Normal 10 H Hooking N Normal 10 H Hooking N Normal 10 H Hooking N Normal 10 H Hooking N Normal 10 H Hooking N Normal 10 H Hooking N Normal 10 H Hooking ND 70185 E CHAPTER 5 Page 115 Revision 3 0 DATA PROGRAMMING Office Data Sheets 8 5 Data Sheet for ALGNL USER GROUP NUMBER UGN LOGICAL STATION NUMBER LSTN MAX 16 DIGITS REMARKS CHAPTER 5 Page 116 Revision 3 0 ND 70
39. Bao RD se 147 1 List of Fusion related System 147 2 3 B PM C level Infinite Loop 149 2 1 on I RUE d RE Rap EROR Rp d Ro quee Bots 149 3 3 C PM C level Infinite Loop Temporary 151 3 1 Heed i od ope i Ide t CNRC Rede padece qp eehidqey pneu ud 151 4 8 D PM Lockup Failure Permanent ee E ERR Y eR 151 4 1 s ssa aae Tees dade 152 5 Lockup Failure Tempolaly E ven KERN 152 5 1 por PII Qe qe Gut weal nee beds queda 152 6 13 H I J Signaling Link Failure 153 6 1 Hopair se d aeque Sup CUTS Faq d qud auque dq 154 6 2 p 155 7 23 9 Failure Notification Detection Rae du RR ERA RE AH 155 2 1 Repar FICE rrr 156 8 23 7 FCH Fault Notification RECOVEry 159 POM Status NNO wad datu Ver P SERS E R WERFEN 160 9 1 FLTINE Initial Setting Fale 1 2 es d idine
40. FCH Mounting Location i E Gas 0028 Figure 7 9 13 H 13 1 13 J Signaling Link Failure System Message ND 70185 E CHAPTER 7 Page 153 Revision 3 0 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 DTI Firmly insert the connector on the front edge of the indicated FCH card DTI PA 24DTR FCH PA FCHA zu sd Y k EON l 10AL 10 FLT n 10AL 10 FLT CA DTI E DTI H FCH E i FCH nicae FCH card Figure 7 10 FCH DTI Connection STEP 2 Initialize the indicated card using the MB key MB key Down Up gt Down See Figure 7 3 When the LED on the FCH card lights green and the related system messages are not displayed anymore monitor the system for a while Otherwise move to STEP 3 STEP3 Replace the FCH card following the procedure listed in Figure 7 4 If the failure exists after card re placement move to STEP 4 STEP 4 Replace the front cable labeled 10AL 10 FLT CA since the cable is suspected as faulty CHAPTER 7 ND
41. Revision 3 0 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 DTI 10 Base T LANI 0 A LANHIO A to the same route FCH1 pn L CPU 1 zi BANER 10 Base Redundancy Figure 3 3 Redundant Configuration LANI HUB FCH and DTI In Figure 3 4 HUB FCH and DTI are shown in a redundant configuration CPU amp S0 1 LANI 0 mer FCH DTI gt PCI Bus 10 Base 10 Base HUB 10 Base T to the same route HUB LANI p PCI Bus 10 Base T 10 Base T i Redundancy Figure 3 4 Redundant Configuration FCH and DTI In Figure 3 5 FCH and DTI are shown in a redundant configuration FCH m gt 10 Base 34 LANI 0 PCI Bus 10 Base T 10 Base T to the same route FcH 1 4 10 Base PCI Bus Redundancy Figure 3
42. command 100 NND 12 RT 200 OG NND 12 e When the ARTD command OSGS is 4 6 7 Sender Immediate Start Sender Delay Dial Start Sender Wink Start use the AMND command DC 9 MND 12 STEP 4 ARSCN Assign the Route Restriction Class RSC that allows RRIs for the external trunk route The same route restriction data must be assigned for each node 7 1 3 LCR LCRS A procedure for assigning LCR LCRS access code is explained using the following example Destination Node C Node B BUSY Node Station C dials 8110 3500 LGRT 200 1 202 567 8901 Node A Figure 5 38 Example of LCR LCRS CHAPTER 5 ND 70185 E Page 90 Revision 3 0 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 TN 1 Ist DC 8 CI N Normal NND 1 TN 1 Ist 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 When the access code is assigned for each node use the ASPAL command ACC 8 Normal SRV LCR LCRS LGRT Dummy route number ACC 8 Hooking SRV LCR LCRS LGRT Dummy route number STEP 3 AMND Using AMND assign the Maximum Necessary Digits to be received by Register ORT
43. oc oc DATA PROGRAMMING Office Data Sheets 8 12 Data Sheet for AFPC FUSION POINT CODE FCCH USE OR FPC NOT USE FCCH 1 253 0 1 CONNECTION ROUTE 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 0 1 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 0 1 CONNECTION ROUTE RT 1 1023 FCCH NUMBER FUSION POINT CODE NUMBER FCHN FPCN 1 255 1 253 ND 70185 E CHAPTER 5 Page 125 Revision 3 0 DATA PROGRAMMING Office Data Sheets FUSION POINT CODE FCCH USE OR FPC NOT USE FCCH 1 253 0 1 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 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 DATA PROGRAMMING Office Data Sheets 8 14 Data Sheet for AFRT FCCH NUMBER CONNECTION ROUTE C RT
44. 1 Time Slot Sequence Integrity TSSI must be guaranteed at the network side Note 3 The following is an example key setting when n 2 5011 1 ON SWI1 2 ON ON 234567 8 OM as u S 8 4 ee eee T Ai EY ELLE 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 5 11 SW12 SW13 CHAPTER 4 ND 70185 E Page 34 Revision 3 0 2 3 PA 24DTR DTI INSTALLATION Key Setting on Circuit Cards There are two types of the PA 24DTR DTT card as shown below Refer to Figure 4 6 and Table 4 4 to set each switch to the proper positions DTI PA 24DTR Card J SW4D 5450 00000000 000 swec sws9 00000000 n SW58 f 00000000 91 25 0000 MB E sws E BL23 BLOO CN2 ATTENTION Contents Static Sensitive Handling Precautions Required Note Dots printed in DIP switches represent the standard settings Figure 4 6 Switch Locations on DTI PA 24DTR Table 4 4 Switch Setting Patterns for the DTI Card SWITCH STANDARD SWITCH NAME NUMBER SETTING SETTING MEANING MB UP Circuit card make busy DOWN x Circuit card make busy cancel 0 ON Internal Loopback Set OFF x Internal Loopback Cancel SW13B 1 ON External Loopback Set a OFF x External Loopback C
45. 2 3 39 1 2 2 1 2 3 40 1 1 2 41 1 2 4 1 42 1 2 3 5 1 2 NS 43 1 2 6 1 2 3 44 1 2 8 7 1 45 1 2 3 8 1 2 46 1 2 3 9 1 2 3 47 1 2S 10 1 2 3 48 1 2 11 1 2 8 49 1 2 3 12 1 2 50 1 2 3 13 1 2 3 51 1 14 1 NS 52 1 15 1 2 53 1 2 3 16 1 2 54 1 2 3 17 1 2 3 55 1 2 18 1 2 3 56 1 2 3 19 1 57 1 2 3 20 1 2 58 1 2 3 21 1 2 3 59 1 2 3 22 1 2 3 60 1 2 23 1 2 61 1 3 24 1 2 62 1 3 25 1 2 3 63 1 26 1 2 3 64 1 44175 27 1 65 1 2 3 28 1 2 66 1 2 3 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 Issue SAGE Ne Issue No 1 2 3 4 5 6 7 8 1 2 4 5 6 7 8 67 1 2 3 105 1 2 3 68 1 2 3 106 1 2 3 69 1 2 3 107 1 2 3 70 1 2 3 108 1 2 3 71 1 2 3 109 1 2 3 72 1 2 3 110 1 2 3 73 1 2 3 111 1 2 3 74 1 2 3 112 1 2 3 75 1 2 3 113 1 2 3 76 1 2 3 114 1 2 3 77 1 2 3 115 1 2 3 78 1 2 3 116 1 2 3 79 1 2 3 117 1 2 80 1 2 3 118 1 2 3 81 1 2 3 119 1 2 3 82 1 2 3 120 1 2 3 83 1 2 3
46. 70185 E Page 154 Revision 3 0 TROUBLESHOOTING 23 S FCH Failure Notification Detection 6 2 Repair Procedure STEP 1 STEP 2 STEP 3 STEP 4 STEP 5 STEP 6 13 I Temporary Make sure that the front cable is securely inserted See Figure 7 10 If this message has been displayed once or twice monitor the failure for a while Otherwise move to STEP 3 If 13 J Recovery has been displayed after this message monitor the failure for a while Otherwise move to STEP 4 Initialize the indicated PA FCHA card using the MB key MB key Down gt Up gt Down See Figure 7 3 When the LED on the FCH card lights green and the related system messages are not displayed any more monitor the system for a while Otherwise move to STEP 5 Replace the FCH card following the procedure listed in Figure 7 4 If the failure exists after card re placement move to STEP 6 Replace the front cable labeled 10 10 FLT CA since the cable is suspected as faulty 23 S FCH Failure Notification Detection This message is displayed when the FCH PA FCHA card is faulty due to the problems such as an Ethernet controller initial failure The message is displayed in the following format If this message is displayed check the related Ethernet cables following the procedure listed on the next page 1 0 00 0000 0000 2 0000 0000 0000 0000 Note FLTINF 01H ETHER Controller Initial
47. 81 Assignmemt or FOH NOISE 82 AFCH Command Display 82 AFRIT Sample Data ARS 83 BERT Command DEN 2222559 o A e Y qu P Qo SE EN E 83 Fusion ero REC db RE I eu dep qb wd dee pe ed 84 AFPC Command Display example 84 AFPC Sample Data Sheet 2 2 2 555 QR RARE T RRA 85 Sample Dala SS 86 Command Display example issues dne aes 86 Example or OGO lon X 87 e buenas 89 dde beu dab que Va d duod 90 External Rouler io cosas RC des pru WEE bcp quedar qe 97 Hardware Connections for External 97 Connection Route Class Data Sample 98 sample Data Assignment AGIA cu 0s 0 a5 Re RET 99 Assignment or FOHM Example ear R3 100 Sample Data Assignment 101 Internal LAN Routing Data Assi
48. BASE T connection should use either of the following cables 1 Cable unit specified as SR1201 CAU n 2 Cables other than those of SR1201 ETIF that are provided by the user Based on the cable type perform the following 4 3 2 When using cable unit SR1201 CAU n 1 Referring to any of Figure 4 13 through Figure 4 15 connect the 10 BASE T straight cables be tween the LANI PZ PC19 and HUB PA M96 cards and between the HUB and FCH PA FCHA cards If the HUB is in a dual configuration also connect the 10 BASE T cross cable be tween HUB 0 and HUB 1 When dual LANIS are used in both Slot 00 and 03 of CPR 0 CPR 1 be sure to use at least two cards Use one HUB for the internal LANI in Slot 00 and use the other for external LANI in Slot 03 available for Series 7300 Release 3 software or later If FCH is also in a dual configuration the 10 BASE T cross connection between the two HUBs is not required 2 If your system needs more PA FCHA and or 96 cards provide the required Ethernet connection s for the added card s using the following cables e When adding card in PIMO UTP CTG5 ST CA D When adding HUB card in PIMO UTP CTG5 CRS CA D e When adding FCH card in PIM1 UTP CTG5 ST When adding HUB card in UTP CTG5 CRS e When adding FCH card PIM2 UTP CTG5 ST e When adding HUB card in 2 UTP CTG5 CRS CA M e When addin
49. CCIS Service in EX FCCS Network NETWORK CONFIGURATION FEATURE NAME without with NEAX2000 IVS NEAX2000 IVS ASYNCHRONOUS DATA SWITCHING CCIS ATTENDANT CAMP ON WITH TONE INDICATION CCIS BUSY VERIFICATION CCIS CALL BACK CCIS CALL FORWARDING ALL CALLS CCIS CALL FORWARDING BUS Y LINE CCIS CALL FORWARDING DON T ANSWER CCIS CALL TRANSFER ALL CALLS CCIS CALLING CALLED NUMBER DISPLAY CCIS CALL TRANSFER ATTENDANT CCIS CENTRALIZED BILLING CCIS Note Message Format is the same as before CENTRALIZED DAY NIGHT MODE CHANGE CCIS CENTRALIZED SYSTEM MANAGEMENT REPORT CCIS DATA PRIVACY ON DEMAND CCIS DIAL ACCESS TO ATTENDANT CCIS DIGITAL DISPLAY STATION CCIS DIRECT IN TERMIANTION CCIS DISTINCTIVE RINGING CCIS DO NOT DISTURB D CCIS EXECUTIVE RIGHT OF WAY CCIS HOTLINE CCIS MESSAGE REMINDER CCIS MESSAGE REMINDER D CCIS MISCELLANEOUS TRUNK RESTRICTION CCIS NAME DISPLAY CCIS SERIAL CALL CCIS SERVICE DISPLAY D CCIS STATION TO STATION CALLING CCIS STEP CALL CCIS SYNCHRONOUS DATA SWITCHING CCIS SUPERVISORY CALL CCIS TOLL RESTRICTION 3 6DIGIT CCIS VOICE CALL CCIS x Note 1 x Note 1 x Note 1 x Note 2 x Note 1 x Note 1 x Note 1 x x Note 1
50. CCIS for Node B 82 CCIS for Node C CCIS Open Numbering 8x CCIS access for Network CCIS Network 8x 4x Fusion access TELN 420000 TELN 1410001 0001 SEE STN 2000 STN 2000 STN 2000 STN Physical Station Number TELN Telephone Number FPC Fusion Point Code Point Code CCIS Figure 2 10 Open Numbering Fusion CCIS Network conditions for Telephone Number Digits When incorporating the Fusion system with the CCIS network consider the following conditions as to the available Telephone Number digits Display Telephone Number Inter Office Composition ATTCON Service DESKCON 4 digits or less Note 4 8digits Note 9 digits or more Note x Available Not available Note When the network is Open Numbering the digits in the table above must be the number of Office Code digits Telephone Number digits ND 70185 E CHAPTER 2 Page 9 Revision 3 0 GENERAL Tandem Connections via Fusion Link 7T 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 gt c CO ACIS ACIS is established TELN calling party TE E 410000 Es E STN A eS Figure 2 11 Tandem Connections via Fusion Link CHAPTER 2 ND 70185 E Page 10 Revision 3 0 CHAPTER3 SYSTEM CO
51. CTG5 ST CA D PIM UTP CTG5 ST 00011021031040506 5 5 UTP 5 ST CPM 00 01 02030405 06 5 ST UTP 5 ST M Note When dual LANIs are used in both slot 00 and 03 of CPR Pattern 3 or 4 be sure to use at least two HUB cards One HUB for internal LANI in slot 00 and the other for external LANI in slot 03 available for Release 3 or later software However if this is the case and FCH is also in a dual configuration the 10 BASE T cross connection between the HUBs is not required Figure 4 13 Examples of Ethernet Cable Connection FCH in PIMO 1 IMG System 2 2 CHAPTER 4 ND 70185 E Page 50 Revision 3 0 INSTALLATION Connecting Cables Figure 4 14 shows some typical examples where 10 BASE T cables are connected to the FCH card s mounted in PIMI of 1 IMG system under the following conditions Configuration Configuration Used Cable Unit Number of HUB of CPU of LAN Note 1 Note 2 FCH Pattern 1 SR1201 ETIF CAU B x 1 HUBx 1 FCHx 1 SR1201 ETIF CAU B x 1 SR1201 ETIF CAU DB x 1 Pattern 3 SR1201 ETIF CAU B x 2 HUBx 2 FCHx 2 SR1201 ETIF CAU B x 2 SR1201 ETIF CAU DB x 2 Pattern 2 HUBx 2 FCHx 2 Pattern 4 HUBx 2 FCHx 2 Note 1 Cabl
52. DTI Cards in Regular Density Slots CHAPTER 5 ND 70185 E Page 76 Revision 3 0 DATA PROGRAMMING Assignment of Telephone Numbers Table 5 2 Data Programming Sheet for Regular Density Slot C LENS C TK 1 4095 Time Slot Allocation z Example mounting slot FCH DTI Slot No Group No Bch TK8 Dch TK1 Bch TK23 Bch TK1 CO u DW BB WY TK9 Nj Extended Group N 10 B ch Dch TK2 LU Specify Dch TS by setting switch on FCH AR EN N N N N 11 D ch o oy c oc ocolo o oc c oc oc coc oc oc o oc ococ o ococ o OF OF co oO Oo CO oO Co Wl W W 9 WI NH N N NI ND 70185 E CHAPTER 5 Page 77 Revision 3 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
53. IVS system are installed on a PC called the Depending on the system logged into determines the MAT software used 2 Tologin the NEAX2000 IVs system Point Code of the system is designated 3 See the manual describing NEAX2000 IVS for the method of checking the log in user 4 The data transmission speed between NEA 2000 IVS and NEAX2400 IMX may be a maximum of 64Kbps since the CCH card is used b 2400 IMX 1 systems in the EX FCCS network can be maintained by one 2 To log in to the NEAX2400 IMX system assign FUG no to designate the desired Fusion Network Group FUG and FPC to designate the desired node in the FUG 3 The user ID and password written in the NDM of each FUG is checked when logging into the NEAX2400 IMX This data is programmed using the AUIDN command 4 When any of the conditions below are met the MAT is logged into the node designated by the FPC but within the FUG where the MAT is installed regardless of entered FUG no data e No data is assigned to SELF FUG Fusion Group number in the self FUG in AFUGN command e FUG requested by the MAT is 0 e FUG requested by the MAT is the FUG number of self FUG 5 The existing system not NEAX2400 IMX can not be maintained via the Centralized MAT for EX FCCS 6 Time required for transmitting the 1Mbyte data 1 block of DM is 2 hours at 64Kbps data speed 1 hour at 128Kbps data speed 15 minutes at 512Kbps data speed The numbe
54. NG If this is indicated replace FCH card FLTINF 02H ETHER Link Failure FLTINF Fault Information Note FLTINF Circuit Number of FCH 0 7 TT FCH Mounting Location FCH CKT No MG Module Group U Unit 0 3 T T T i G Group 00 23 FCH Mounting Location Figure 7 11 23 5 FCH Failure Notification ND 70185 E CHAPTER 7 Page 155 Revision 3 0 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 If no fault is found in this step move to STEP 2 STEP 2 The following equipment is suspected to be faulty Check for each item e Ethernet cables 10 BASE T cables See Figure 7 13 How to Check 10 BASE T cables e HUB PA M96 lt See Figure 7 14 How to Replace HUB 96 card PA FCHA lt See Figure 7 4 How to Replace card PIM 1 PIM 0 10 BASE T cable FCH PA FCHA card indicated by system message ATTENTION Contents Static Sensitive dling Precautions Required wa d CEL sunm
55. Number using STN The Numbering Plan data for the LDM and or NDM cannot use separate Tenant Numbers TN Therefore be sure to assign the following data on the ASYDL command e ASYDL command SYSI INDEX 800 bl 1 ASPAL command tenant data table development on LDM Common b2 I ANPDL command tenant data table development on LDM Common 1 1 3 Station Numbering 1 1 4 e Assign Telephone and or Physical Station Numbers using the following command ALGNN gt ALGSN Assign Telephone Number on the network NCN only ASDT Assign Physical Number for each node as required available for NCN and LN Fusion Link Data e Assign the Fusion Link data using the following commands Fusion with FCH ACRD gt ACTK gt MBCT AFCH AFRT Fusion w o FCH ACRD gt MBCT gt AFPC CHAPTER 5 ND 70185 E Page 58 Revision 3 0 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 e Decide an NCN and LN on the network e 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 etc Note The data becomes effective by executing Non Load Initial after setting the FPC e Assign unit data using the AFMU command for each no
56. OFF ON Note When setting this key refer to Digital PAD Setting Table Table 4 5 Alarm Sending when this circuit card is in N OPE state CHAPTER 4 ND 70185 E Page 38 Revision 3 0 SWITCH INSTALLATION Key Setting on Circuit Cards Table 4 4 Switch Setting Patterns for the DTI Card Continued SWITCH NUMBER SETTING STANDARD SETTING MEANING Note 2 4 SWSD p ON Digital PAD ROM selection Special specifica tion Digital PAD ROM selection Standard specifica tion LAYER2 signal logic Positive LAYER signal logic Negative Line fault is not notified to the upper CPU Line fault is notified to the upper CPU Zero Code Suppression is not provided This switch setting is applicable for a system which adopts Associated Channel Interoffice Signalling ACIS Digital PAD Setting The PA 24DTR card is equipped with a mask ROM in which the following typical PAD patterns have been already written PAD value is determined by selecting a desired PAD pattern which can be done by key setting of the SW 58 elements 4 5 6 on the card and programming of the PAD data by the ARTD com mand CDN 30 PAD The PAD patterns and ARTD data correspond as follows Table 4 5 Digital Pad Setting PAD Pattern dB Selected by key setting PAD Pattern 1 PAD Pattern 2 Ay Loss Bothwa
57. POCS agre RR RC Cn 179 Figure 8 7 PC Assignment in EX FCCS 181 Figure 8 8 Port Allocation and Related Command for CCIS 187 Figure 8 9 CIG Number ASSIgTn 53452342 sade tek ane 189 LIST OF FIGURES ND 70185 E Page viii Revision 3 0 Table 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 LIST OF TABLES Title Page GENE WET o aa Qe d 4 a2 MODE Switch SEI xata Eee SR E eese 4 dE S Rhe d Subs duis x 34 Suo EV HD BUDE ui b cR Lcd aora aed 34 Switch Setting Patterns tor the RR dh ee wees de 35 Pad 2532 dU 39 Route Class Data 2 2 4 4 4 4 lt 73 Data Programming Sheet for Regular Density 77 Data Programming Sheet for High Density 0 80 List of Fusion related System 147 EX FCCS Network Type Classification 170 Patterns of Number
58. SRV SSC SID 2 operator call FPC 3 Node C Cal O Node having ATTCON DESKCON FPC 5 Node E Node w o ATTCON DESKCON Data Programming Node B Figure 3 17 Operator Calls on a Fusion Network ND 70185 E CHAPTER 3 Page 25 Revision 3 0 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 Note 1 When assigning the data regarding the call termination to ATT be sure to develop the unified data at each node Note 2 Terminating node cannot be assigned differently at each tenant TN Note 3 When the connection routes C RT are all busy any attempted call via C O Line is not connected to the ATT As a result the calling party is provided with the Ring Back Tone RBT and even when a C RT later becomes idle the RBT connection is still maintained and the C O call does not terminate to the ATT ASYDL Node A PSTN Index 640 FPC 3 Node C ASYDL Node D Index 640 FPC 5 Node E Fusion Network Node providing ATTCON DESKCON Node providing ATTCON DESKCON Data Programming Node A Data Progra
59. STEP 2 FCIC1 002010 1 2 002011 FCIC3 002012 FPC 10 29 i FCIC10 002022 d NN ccs A ACAN command parameters 01 V dd FPC EPG i lt Self node 5 10 FGH E 1 FCIC 14 1 ROUTER i 1 o 5 2 C LENS cay j 002010 RT13 Note to CPU Note This setting is a sample Figure 5 56 Sample Data Assignment ACAN STEP 7 AFRT Set Connection Route Numbers of the Speech Channels for the FCHN which was assigned in STEP 4 FCHN FCH Number Assign FCHN specified in STEP 4 C RT Connection Route Assign Connection Route of the Speech Channels specified in STEP 2 PBX _ Speech RTI sei AFRT command parameters i i FCHN assigned 22 inSTEP4 z m E CNT CRT Jo i i e RT14 ROUTER 5 9 FCHN 1 2 Qu Y s a Note 1 RT13 Note 2 to CPU Note 1 This setting is a sample Note 2 A maximum of 8 RT can be programmed Figure 5 57 Sample Data Assignment AFRT CHAPTER 5 ND 70185 E Page 108 Revision 3 0 DATA Assignment of FCH Related Data STEP 8 AGIP Assign IP addresses of FGH card and its connected router FCHEN FCH Equipment Number Assign LVO 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 CONTTYP Voic
60. VA Veith VV py C Note 0 BASE T cable connections may differ depending on system configuration CHAPTER 7 Page 156 Revision 3 0 Figure 7 12 10 BASE T Cable Connection Check ND 70185 E TROUBLESHOOTING 23 S FCH Failure Notification Detection HUB 96 N 1 HUB 96 MB modular to LANI PZ PC19 SEERE 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 Contents Static Sensitive 4 Unplug and plug the modular connector a few times at each conne Handling s Required ctor since the connection may be a poor contact 5 If the above procedure does not result in normal operation perform DTI PA 24DTR the conductive test of the 10 BASE T cable 9 1 Turn ON the MNT 3 switch on the FCH card make busy request HUB FCH Cable Connection Test Alternate Routing start is displayed Turn ON the MB key on the FCH card make busy Turn ON the MB key on the HUB card make busy Unplug and plug the modular connector a few times at each connector since the connection may be a poor c
61. XX XX XX XX XX XX XX XX 3 XX XX XX XX XX XX XX XX L 11 L i 4 XX XX XX XX XX XX XX XX 5 XX XX xx 00 0000 0000 6 0000 0000 0000 0000 239 238 237 247 246 245 255 254 253 T T 2 Each bit represents FPC Fusion Point Code When 1 is set the FPC has joined the spanning tree configuration 32 Bytes 50 T Spanning Tree Configuration Results b7 a FLTINF 1EH Spanning Tree Generation End Notification 57 50 r Trace Confirmation Bit olo 0 1 Status Notification Primitive Trace RS Receive Send Primitive Trace not effective TRC RS FCH CKT No L FCH CKT No Circuit No of FCH b7 50 wc MG Module Group U Unit 0 3 FCH Mounting Location G Group 0 23 Figure 7 21 23 0 FCCH Status Notification Spanning Tree Generation End ND 70185 E CHAPTER 7 Page 165 Revision 3 0 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 Ox Fixx 0000 0000 2 0000 0000 0000 0000 LI b7 Spanning Tree Generation Start 00H Normal L b7 FLTINF 1FH Spanning Tree Generation Start 57 50 r Trace Confirmation Bit C 0 1 Status Notification Primitive Trace IL RS Receive Send Primitive Tr
62. YAU MODE 00 Refer to Table 4 2 ON T203 Timer Variable OFF T203 Timer 10 secs Standard Setting sees Not Used Figure 4 5 Switch Setting on FCH PA FCHA Card ND 70185 E CHAPTER 4 Page 33 Revision 3 0 INSTALLATION Key Setting on Circuit Cards Table 4 2 MODE Switch Setting STANDARD SWITCH NAME SETTING SETTING DESCRIPTION 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 STANDARD SWITCH NAME NUMBER SETTING SETTING DESCRIPTION SW14 ON x Positive logic for the D I CONT Negative logic for the D I CONT 22227 The fusion data link speed inserted onto the interface Note 3 SPEED Note 2 64Kbps x n 1 24 48Kbps x n 1 24 56Kbps x n 1 24 Not used LAPD signal link performs as network LAPD signal link performs as user Note 1 64Kbps is used for or interface 56Kbps is used for interface with bit stealing 46Kbps is used for interface with both bit stealing and Zero Code Suppression or Bit 7 Stuffing Note 2 When n is bigger than
63. and the FCH card mounted in PIM 1 of the 1 IMG system Connect HUB and FCH using a 10 BASE T straight cable Refer to figures listed on the following pages S DENE Connect two HUB cards using a 10 BASE T cross cable When HUB is in dual configuration Note 22 8 LL LET 6 v A e Connect the LANI and the HUB card using a 10 BASE T straight cable Eight 10 BASE T connectors TPO X TP7 X are furnished on the front edge of the HUB card Use one of the connectors Note This step can be skipped when dual LANIs LANI A and LANI B are used for each CPU and is provided in a dual configuration Figure 4 12 Connecting 10 BASE T Cables example CHAPTER 4 ND 70185 E Page 48 Revision 3 0 INSTALLATION Connecting Cables Figure 4 13 shows some typical examples where 10 BASE T cables are connected to the FCH card s mounted in PIMO of 1 IMG system under the following conditions Configuration Configuration Used Cable Unit Number of HUB of CPU of LAN Note 1 Note 2 FCH Pattern 1 SR1201 ETIF CAU A x 1 HUBx 1 FCHx 1 SR1201 ETIF CAU A x 1 HUBx 2 FCHx 2 Pattern 2 SR1201 CAU DA x 1 Pattern 3 SR1201 ETIF CAU A x 2 HUBx 2 FCHx 2 SR1201 ETIF CAU A x 2 HUBx 2 FCHx 2 SR1201 ETIF CAU DA x 2 Pattern 4 Note 1 Cables Contained in each cable unit
64. are as follows SR1201 ETIF CAU A UTP CTG5 ST CA D CTG5 ST CA J SR1201 ETIF CAU DA UTP CTG5 ST CA D UTP CTG5 ST CA J UTP CTG5 CRS CA F Note 2 The cables cited in Figure 4 13 be used in the 1 system only Refer to Page 45 through Page 48 for more details 96 FCH Ji FL 10 BASE T Connector Use 10 BASE T connectors i TOPU TOPU TP7 X FCH in PIMO Pattern 1 gt FCH in PIMO Pattern 2 ur WEE IOBASET 2 1 a TP5 X f i 1 36 8 40 siojoauu09g FRONT VIEW FIM2 FIM FANU FANU PIM 1 PIM 1 UTP CTG5 CRS CA F UTP CTG5 ST CA D 10010102103 0410570 UTP 05 ST 10010102103 040570 BASEU BASEU Figure 4 13 Examples of Ethernet Cable Connection FCH in PIMO 1 IMG System 1 2 ND 70185 E CHAPTER 4 Page 49 Revision 3 0 INSTALLATION Connecting Cables FCH in PIMO Pattern 3 FCH PIMO Pattern 4 TOPU PIM 3 PIM 2 PIM2 FANU PIM 1 PIM 1 UTP 5 ST CA J UTP
65. bo Ls 18 FLTINF 18H Spanning Tree Abnormal Answer Notification b7 50 TRC Trace Confirmation Bit olo 0 1 Status Notification Primitive Trace RS Receive Send Primitive Trace not effective TRC RS FCH CKT No FCH CKT No Circuit No of FCH b7 bo MG A G 0 MG Module Group U Unit 0 3 FCH Mounting Location G Group 0 23 Figure 7 18 23 0 FCCH Status Notification Spanning Tree Abnormal Answer CHAPTER 7 ND 70185 E Page 162 Revision 3 0 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 ette 00 Node H Q Node G This FPC has not E been assigned Spanning Tree Abnormal 2l p Node Node F Node E Figure 7 19 Spanning Tree Abnormal Answer ND 70185 E CHAPTER 7 Page 163 Revision 3 0 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 Ox H D X
66. but only in case that your system should use the bit corresponding Memory Block s for some reasons Figure 5 5 LDM and NDM Allocation ASYDL 2 Assign the data to NCN only e ASYDN Index 514 Network Data Memory usage Assign 1 for bit s corresponding to the data memory block to be used as Network Data Memory NDM Assign 01H for systems having 2M DM CHAPTER 5 ND 70185 E Page 62 Revision 3 0 DATA Assignment of System Data STEP2 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 7 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 Network Control Node LN Local Node ASYDL Index 512 b0 b7 Figure 5 6 Self FPC Assignment STEP3 ASYDL and ASYDN Assign other system data using the ASYDL ASYDN command When Timing Start is used assign the following data Index 161 b6 0 1 Timing Start using 4 code b7 0 1 Timing Start using code Index 170 b4 0 1 Timing Start out of Service Timing Start in Service Note 1 Index 640 Fusion Point Code FPC of node providing ATTCON Note 2 Index 704 735 ASYDL FPC of the node to which ATTCON transfers the Day Night changeover information Note 3 Assign FPC of a terminating node for House Phone Off
67. doe 129 S16 Dabei 225334562 Sohn d Kod NOU do do 130 Bur Dole duet equ d A E aided gud dq 181 8 18 Data Sheet tor lt 5 5 gt 4 lt 55 ORAE ARR PRE PARA 132 CHAPTERS POSTINSIALLAIION TEST 4 52960 REA ARE APEX Sd Eds 133 t How to Check Fusion Link by LEDs an POH Card ER RR E Rx us 133 1 1 Flow io cheek 202 22 5 5 99 boo X OD ORE Yee rd 134 2 Repair Procedure When LED Indicates 134 Fist HEB GRO OR ues 134 2 2 How 15 Parm the Fusion Link 546926356 redes bud 135 2 2 4 Fusion Link Test Mode 0 135 2 2 2 Loopback Point Designation 4 cdccc sande Phe aq issit 148 2 3 Sek HR OW KU PK QUERN Se dos fn 137 s FODSNaon Connechon Tesi e 138 ay Station to Station Connection Test via 5 138 21 FOCS Call Origination Test 56 xassunk ka ORE RA 138 ie FOCS Call Termination 139 3 2 BITGON ConrigetlonTest uia POS
68. has a Fusion Link via the 96 cards this section gives details related only to the connection between the and FCH PA FCHA cards 1 Refer to the NEAX2400 Installation Manual IMX U to make sure that the necessary 10 BASE T both straight and cross connections between the ISW and each LN Local Node are all securely provided Connect the 10 BASE T straight cable s between the HUB PA M96 and FCH PA FCHA cards Use the following cable which must be provided by the user UTP CTGS ST CA F When the HUB and are in the same PIM UTP CTG5 ST CA O When the HUB and are in different PIMs but in the same IMG UTP CTG5 ST CA X When the HUB and are in different IMG stacks but in the same LN UTP CTG5 ST CA A0 When HUB and are in different LNs ND 70185 E CHAPTER 4 Page 47 Revision 3 0 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 1 system of the external LANI Figure 4 12 shows an example of a HUB in a dual configuration
69. mounted MG number Note SDT can be mounted in the odd MG only STEP2 ACRD Assign the Connection Route Class data e Connection trunk for Voice C RT 10 3 TCL 4 RLP 2 LSG 12 CHAPTER 5 ND 70185 E Page 94 Revision 3 0 DATA PROGRAMMING Assignment of FCH Related Data e 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 e Connection trunk B ch C RT 10 TK 1 664 CLENS LEN for the SDT e 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 Note Set the switch on the FCH card depending on the transmission speed See CHAPTER 4 INSTALLATION for more information on switch settings STEP4 AFCH Assign the FCCH number for each FCCH FCHN 2 FCCH number FCHEN LEN of FCCH STEP 5 AFPC Assign the FCCS routing data FPC 1 FPC of the adjacent node FCCH 1 with FCCH CRT 10 FCHN 2 STEP 6 ACAN Assign the CIC number to the connection trunk FPC 1 FCIC 1 664 CLENS LEN of the connection trunk STEP 7 AFRT Assign the FCCH Controlled Connection Route data FCHN 2 CRT 10 ND 70185 E CHAPTER 5 Page 95 Revision 3 0 DATA PROGRAMMING Assignment of FCH Related Data STEP 8 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 F
70. of a system message to Center Node retry operation is executed When the retry operation also fails transmission is aborted and the message is to be sent together with the next system message ND 70185 E CHAPTER 3 Page 21 Revision 3 0 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 Node B Node C Centralized Fusion Center Node Node C Node A Node D Figure 3 14 Centralized Management Report Fusion Example 1 Node A To send system messages to Node C via Office B assign Point Code of Node C 12 to ASYD SYS Node B Node C Node D CHAPTER 3 Page 22 Revision 3 0 1 Indexes 184 and 185 To send system messages to Node C assign Fusion Point Code of Node C 3 to ASYDL SYS1 Index 532 When this system data is assigned system messages received from Node A are also transferred to Node C However when data is not assigned 0 system messages received from Node A are ig nored and not transferred to Node C System messages received from Node A are not output to the system message printer connected to Node B Received system messages are stored in the memory area for Centralized Management Report Fusion To send system messages to Node C assign Fusion Point Code of Node C 3 to ASYDL SYS1 Index 532 ND 70185 E SYSTEM CO
71. order to monitor the PM If the CPU cannot receive the return data within a predetermined time period the system displays this data When the failure is detected more than 15 times per hour the failure is judged as per manent Otherwise 3 E PM Lockup Failure Temporary is displayed 1 00 0000 0000 0000 2 0000 0000 0000 0000 FCH Mounting Location i MG Module Group T T T d U Unit 0 3 e U G iG Group 00 23 Figure 7 6 3 D PM Lockup Failure Permanent ND 70185 E CHAPTER 7 Page 151 Revision 3 0 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 STEP 2 Initialize the FCH card using the MB key See Figure 7 3 How to Initialize FCH PA FCHA Card When the LED lights green and no system message related to this failure displays again monitor the system for a while Otherwise move to STEP 3 STEP 3 Replace the card Refer to Figure 7 4 How to Replace PA FCHA Card 5 3 E PM Lockup Failure Temporary The CPU sends diagnosis data at periodic intervals to the Port Microprocessor PM on the FCH PA FCHA cards in order to monitor the PM If the CPU cannot receive the return data
72. remaining HUB cards except the HUB card used for the MAT connection Connect the 10 BASE T straight cable s between the HUB and FCH PA FCHA cards Use the following cables which must be provided by the user CTGS5 ST CA F When the HUB and are in the same PIMO UTP CTGS5 ST CA O When the HUB are in different PIMs When is in a dual configuration connect FCH 0 to the side and FCH 1 to the HUB 1 side 4 3 A Procedure for 4 IMG System When your system is 4 IMG type the procedure for 10 BASE T connection is as follows Because the 96 can be mounted anywhere in a of any IMG the Ethernet cables must be arranged by the user depending on the system configuration l CHAPTER 4 Page 46 Revision 3 0 Depending on your system configuration connect the 10 BASE T straight cable s between the 96 and LANI PZ PC19 cards Use the following cable prepared by the user CTG5 ST CA O When the HUB and LANI are in the same IMG IMGO UTP 5 ST CA X When the HUB and LANI are in different IMGs When a single LANI is used for each CPR Slot 00 only and the HUB is in a dual configuration connect HUB 0 to LANI using two 10 BASE T cables ND 70185 E 4 3 5 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 conn
73. 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 PBX RT10 CPU LANI 1 MDF uoeeds __ FCIC1 002010 FCIC2 002011 002012 FCIC10 002022 Speech FCHN is not required for FGH External LAN FCHN 1 FCHEN 000030 Internal LAN ACAN command parameters FPC FPC 11 Next Node FCIC EE C LENS 00201 0 Note Note This setting is a sample STEP8 MBCT Figure 5 48 Sample Data Assignment ACAN Unbusy the connection trunk data assigned in the previous steps by using the MBCT command This is required for FCH FGH trunks as well as speech channels ND 70185 E CHAPTER 5 Page 103 Revision 3 0 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 Fusion network is realized via the Internet Intranet PBX PBX Internet Intranet Rou
74. the information field of origi nating call is also output to Telephone Number field ND 70185 E 5 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 non fusion system via EX FCCS or NEAX2000 IVS using Enhanced CCIS feature to an existing FUG a The system must be the b The system is programmed as the Fusion Network configured by one NCN only c Use of the system to program the network data 2 When connecting the NEAX2400 IMX system and the NEAX2000 IVs system CIC Circuit Identifica tion Code 1 should always be assigned using ACIC2 command 3 ACSCL command data CCH location must be programmed against the PC of the connected NEAX2400 IMX or NEAX2000 IVS system using command ND 70185 E CHAPTER 8 Page 185 Revision 3 0 5 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 FUG1 Center FUG FUG2 4 1 1 To Log in to All Nodes EX FCCS Network Assign the following system data for all the nodes in the network According to the condi
75. the installation of the Fusion link See Figure 5 2 Please refer to CCIS related manuals for more detailed information ND 70185 E CHAPTER 5 Page 59 Revision 3 0 DATA PROGRAMMING Network Data Programming Summary 1 3 Fusion Link Data e Assign the Fusion Link data using the following commands Fusion with gt ACTK gt MBCT gt AFCH gt AFRT gt AFPC gt Fusion w o ACRD gt 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 Please refer to CCIS related manuals for more detailed information PSTN Add CCIS link X PC Point Code CCIS Figure 5 2 Fusion CCIS Network CHAPTER 5 ND 70185 E Page 60 Revision 3 0 DATA PROGRAMMING Network Data Programming Summary Figure 5 3 shows how to upgrade an existing CCIS network focusing on the Numbering Plan The example data setting assumes the existing network uses this particular numbering For more detailed information on how to assign Telephone Numbers please see Assignment of Telephone Numbers Before Upgrading Numbering Plan Data of Node before upgrading D x 100 Priority Call 1 ATT 101 Priority Call 2 ATT 102 Priority Call 3 ATT 2xxx Physical STN 8x CCIS ac
76. within a predetermined time period the system displays this data When the failure is detected more than 15 times per hour the failure is judged as permanent Otherwise 3 E Lockup Failure Temporary is displayed 1 xxOx 0000 0000 0000 2 0000 0000 0000 0000 LJ PM Restart Type Note T GN CQ EC RC UCM gt 0 1 B monitor Initial Restart p a PM Restart Type FCH Mounting Location MG Module Group SCS E U Unit 0 3 i G Group 00 23 FCH Mounting Location i Figure 7 7 3 E PM Lockup Failure Temporary Note B monitor Restart Ports whose link have already been established remain connected while ports process ing a call origination may be released Initial Restart All ports on the circuit card are force released to be placed in idle state 5 1 Repair Procedure STEP 1 Ifthis system message has been displayed only once or twice monitor the failure for a while Other wise move to STEP 2 STEP2 Initialize the FCH PA FCHA card using the MB key See Figure 7 3 How to Initialize FCH Card If this message is not displayed any more monitor the FCH card for a while Otherwise move to STEP 3 STEP3 Replace the FCH card referring to Figure 7 4 How to Replace FCH PA FCHA Card CHAPTER 7 ND 70185 E Page 152 Revision 3 0 6 TROUBLESHOOTING 13 H I J Si
77. 1 Figure 5 32 AFPC Command Display example WARNING The AFPC command affects communications between nodes Change the data with extreme care CHAPTER 5 ND 70185 E Page 84 Revision 3 0 DATA 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 AFPC at Node A Fusion with FCH Node B FPC 2 to Node B FCCH 1 with FCH To Node B CNT CRT FCHN 1 10 1 Node A D C_RT 10 FCHN 1 Node C To Node C FPC 21 to Node FCCH 1 with CNT C_RT FCHN 1 10 1 Assign all nodes data in the same manner O O00000000000000000000000000000 This table shows a sample data sheet for Node A on the fusion network without FCH Assign the data for all nodes including the nodes which are not directly connected on the network i e Node C Node D AFPC at Node A Fusion without FCH Node B FPC 2 to Node B FCCH O without FCH CR To Node B CNT C RT PM ps Node A i Node Assign adjacent Node s Assign destination far Node s FPC To Node C Node C 1 10 Assign
78. 121 1 2 3 84 1 2 3 122 1 2 3 85 1 2 3 123 1 2 3 86 1 2 3 124 1 2 3 87 1 2 3 125 1 2 3 88 1 2 3 126 1 2 3 89 1 2 3 127 1 2 3 90 1 2 3 128 1 2 3 91 1 2 3 129 1 2 3 92 1 2 3 130 1 2 3 93 1 2 3 131 1 2 3 94 1 2 3 132 1 2 3 95 1 2 3 133 1 2 3 96 1 2 3 134 1 2 97 1 2 3 135 1 2 9 98 1 2 3 136 1 2 3 99 1 2 3 137 1 2 3 100 1 2 3 138 1 2 3 101 1 2 3 139 1 2 3 102 1 2 3 140 1 2 3 103 1 2 3 141 1 2 3 104 1 2 3 142 1 2 3 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 Issue FAGENES Issue No 1 2 3 4 5 6 7 1 2 9 4 5 6 7 8 143 1 2 3 181 3 144 1 2 3 182 3 145 1 2 3 183 3 146 1 2 3 184 3 147 2 3 185 3 148 2 3 186 3 149 2 3 187 3 150 2 3 188 3 151 2 3 189 3 152 2 3 190 3 153 2 3 191 3 154 2 3 192 3 155 2 3 193 3 156 2 3 194 3 157 2 3 195 3 158 2 3 196 3 159 2 3 197 3 160 2 3 198 3 161 3 162 3 163 3 164 3 165 3 166 3 167 3 168 3 169 3 170 3 171 3 172 3 173 3 174 3 175 3 176 3 177 3 178 3 179 3 180 3 ISSUE 1 ISSUE 2 ISSUE 3 ISSUE 4 DATE JANUARY
79. 185 E DATA PROGRAMMING Office Data Sheets 8 6 Data Sheet for ALGSL TYPE1 REMARKS 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 ND 70185 E CHAPTER 5 Page 117 Revision 3 0 DATA PROGRAMMING Office Data Sheets 8 7 Data Sheet for ALGSL TYPE2 REMARKS 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 me met et a Rt et RY ey Rt 5 5 ND 70185 E Page 118 Revision 3 0 8 8 Data Sheet for ASDT TENANT NUMBER TN STATION NUMBER STN LINE EQUIPMENT NUMBER LENS U G TELEPHONE EQUIPMENT CLASS TEC 1 31 ROUTE RESTRICTION CLASS RSC 0 15 DATA PROGRAMMING Office Data Sheets SERVICE FEATURE CLASS SFC 0 15 ND 70185 E CHAPTER 5 Page 119 Revision 3 0 DATA PROGRAMMING Office Data Sheets 8 9 Data Sheet for ACRD CONNECTI
80. 185 E CHAPTER 1 Page 1 Revision 3 0 INTRODUCTION Related Manuals 3 Related Manuals To complete the installation of the Fusion system the following manuals are required e 2400 IMX Circuit Card Manual e 2400 IMX Installation Manual e 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 ND 70185 E Page 2 Revision 3 0 CHAPTER2 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 In the remainder of this manual the existing station numbers are referred to as Physical Station Numbers Fusion service features are activated when a Telephone Number is dialed The Telephone Number which can be assigned on a station basis is a unique number on a Fusion network If required numbering plan data which is identical to that of an existing station number can be used to maintain consistency of the number ing plan When this plan is adopted you can use th
81. 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 ND 70185 E ISSUE 3 MAY 2000 NEAX2400 IMX Fusion Network System Manual TABLE OF CONTENTS Page CHAPTER UNTRODUGTIGN 2 ecu dion e Ea Qe d a CRDI s dd do ci a ones 1 REESE 1 GE oie Pole TMe MaMa 1 3 Related Manuale iesu cce rc RE REX EFE X ee REX Eque d RR ER ee 2 GHAPTIER GENERAL cance RE REA Robe Rea p e CR ERES marks 3 1 Whatis Fusion and its AGVantageS cd caw toes oie uc iE ds ordo d Cae ARR 3 14 Improved Inter Office Service 3 1 2 Use of Telephone Numbers e sace acuti d Gel ce Gio RR ae E Qe rot ed 3 2 Free emheh e Rep xm Rx mr ERR eae x neu x p d doe 4 Za Centralized Maintenance Administration Terminal MAT 4 3 Fusion System COMNGUISUON issues eee x eee hee PRR beh ES Eee Rea 5 alr hc cee th cee are adeeb aoe 6 5 Data Memory Configuration 2 uua cur mmm beens me
82. 2 OGCA A procedure for assigning OGCA access code is explained using the following example Node C NodeB BUSY 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 Assign the first digit of the OGCA 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 Ist DC 9 CI N Normal NND 1 Ist DC 9 CI H Hooking NND 1 STEP 2 ASPAN ASPAL Note Assign the OGCA access code When the access code is common to all nodes use the ASPAN com mand When the access code is assigned for each node use the ASPAL command 9 CI N Normal SRV OGCA COUNT 2 IstLGRT 100 2nd LGRT 200 9 CI H Hooking SRV OGCA COUNT 2 IstLGRT 100 2nd LGRT 200 Note When entering the data in STEP I and STEP 2 do not mix the commands for LDM and NDM Write the data on the same data memory as shown below When writing the data on the LDM ANPDL STEP 1 gt ASPAL STEP 2 When writing the on the ANPDN STEP 1 ASPAN STEP 2 ND 70185 E CHAPTER 5 Page 89 Revision 3 0 DATA PROGRAMMING Assignment of FCH Related Data STEP3 ANNDL AMND Assign the necessary number of digits using the ANNDL or the AMND command depending on the route data e When the ARTD command OSGS is 2 Second Dial Tone use the ANNDL Necessary Digits Data
83. 4 Page 51 Revision 3 0 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 Pattern 1 Configuration of CPU Configuration of LAN Used Cable Unit Note 1 Note 2 SR1201 ETIF CAU C x 1 Number of HUB FCH HUBx 1 FCHx 1 SR1201 ETIF CAU C x 1 SR1201 ETIF CAU DC x 1 SR1201 ETIF CAU C x 2 SR1201 ETIF CAU C x 2 SR1201 CAU DC 2 Pattern 2 HUBx 2 FCHx 2 Pattern 3 HUBx 2 FCHx 2 Pattern 4 HUBx 2 FCHx 2 Note 1 Cables contained in each cable unit are as follows SRI201 CAU C UTP CTG5 ST CA M UTP CTG5 ST CA J SRI201 CAU DC UTP CTG5 ST UTP CTG5 ST CA J UTP CTG5 CRS CA F Note 2 The cables cited in Figure 4 15 can be used in the 1 system only Refer to Page 45 through Page 48 for more details HUB PA M96 FCH PA FCHA 10 lt FCH in PIM2 Pattern 1 FCH in 2 Pattern 2 gt 1 Use 10 BASE T connectors 48 E TOPU T
84. 5 Redundant Configuration FCH and DTI ND 70185 E CHAPTER 3 Page 13 Revision 3 0 SYSTEM CONFIGURATION System Considerations In Figure 3 6 no redundancy is shown in the Fusion link CPU4SQ 31 LANI 0 DI PCI Bus 10 Base 10 Base T HUB CPUs LANI 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 In the following diagram a Fusion Link is printed in a thick line while a CCIS link is printed in a dotted line Condition 1 maximum number of nodes on a Fusion network is sixteen 16 nodes example 2 example 1 Routing from Node Routing from Node D gt Node C 2 NEC d E Node D Node Node B gt Node C Node D Node B Node C Node Node B Node Node A 4 I FCCS FCCS example 3 Figure 3 7 Fusion Network Topologies CHAPTER 3 ND 70185 E Page 14 Revision 3 0 SYSTEM CONFIGURATION System Considerations Condition 2 maximum of four 4 nodes can be connected as tandem nodes max 4 nodes FCCS Tandem Connection over FCCS links Figure 3 8 Fusion Tandem Connections C
85. 66 4 1 khen tor epe dort Red eo PARC De Adeo bd 66 5 Assignment of Numbering Data for Telephone 67 6 Assignment of Telephone 70 6 1 Assignment of Connection Route Trunk 72 6 1 1 When is mounted in a Extended Density 76 6 1 2 When is Mounted in a High Density 0 78 7 Assignment af FCH Related Data os oc sas or EY dered SEER desea e ped pda 81 7 1 Assignment of Access Code for Tandem Connection via FCCS ACIS 87 POE 87 ERE ded 89 Pia B Rd d ee a Sor Ete dedo a 90 72 Data Assignment for 52M SDH Interface 93 251 Data roD esce dedo exa ke dodo CR ORPHEO dr RC OU de hoes 94 7 3 FCCS Link via 97 71 Eum BOUE 245359554959 shee destin eka SEE a 97 fag Networking over lP Ere Wd 104 7 4 Flexible Routing FOCOS Rn RET 111 TAB
86. 8 1 See Table 8 1 in conjunction with Figure 8 1 for easy understanding of network configuration The following items and sec tions explain more details Table 8 1 EX FCCS Network Type Classification x Available CONNECTION A MAXIMUM SERVICE CENTRALIZED FUNCTION TYPE TYPE NUMBER OF IMX to IVS2 to TELEPHONE NUM to Ivs2 to MAINTE BILENG Enhanced 120 000 poe x x x CCIS service service EX Enhanced CCIS CCIS FCCS CCIS 0000 service P i Note Hardware Configuration For IMX to IMX connection type both FCH and CCH cards are available For IVS to IMX connection type FCH card is not available Use CCH card PA SCIG6 CCH card is not available for the EX FCCS network establishment There are two connection types 1 NEAX2000 IVS to NEAX2400 IMX connection Enhanced CCIS 2 NEAX2400 IMX to NEAX2400 IMX connection EX FCCS FCCS NETWORK 1 1 NEAX2000 IVS to NEAX2400 IMX FCCS NETWORK 2 IMX a IMX 2 NEAX2400 IMX to Legend NEAX2400 EX FCCS i 5 5 Enhanced CCIS Figure 8 1 Network Connection Type CHAPTER 8 ND 70185 E Page 170 Revision 3 0 5 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
87. ALLATION Key Setting on Circuit Cards Table 4 4 Switch Setting Patterns for the DTI Card Continued SWITCH STANDARD SWITCH NAME NUMBER SETTING SETTING MEANING ON PAD CONTROL ON Both directions Receiving only Sending only ARTD is fixed 22222222 DATA PAD 64K 56K 48K 64K INV T SIG CONTROL ABCD ABAB Bit steal is in hibited AAAA R SIG CONTROL ABCD ABAB Bit steal is in hibited AAAA ND 70185 E CHAPTER 4 Page 37 Revision 3 0 INSTALLATION Key Setting on Circuit Cards Table 4 4 Switch Setting Patterns for the DTI Card Continued SWITCH NAME SMITH SETTING STANDARD NUMBER SETTING MEANINS 62222222 x Equalizer Setting DISTANCE 0 131 ft fp 25 7202 0 040 m DENEN 131 262 ft 22222222 40 080 m 262 393 ft 80 120 m 393 524 ft 120 160 m 524 656 ft 160 200 m Other Combinations Not Allowed ON PAD Pattern Selection SW SW SW 58 4 58 5 58 6 ON PAD Pattern 1 ON PAD Pattern 2 A Loss Bothway ON OFF Loss Receive pA Loss Bothway OFF OFF OFF Loss Receive Other Combinations Not Allowed PAD PATTERN ON OFF OFF
88. AN NS 2 SDT SDH SONET Digital Trunk FCH Fusion Call Control Handler ND 70185 E CHAPTER 5 Page 93 Revision 3 0 DATA PROGRAMMING Assignment of FCH Related Data Specifications for the SDH data setting are described below 1 When FCCS 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 Example Available Not Available Houte Network cone Network Number Connection Trunk Connection Trunk Connection Link Connection Link Speech Line Speech Line Signal Line Signal Line The same route number can not be used for the different route 2 System data SYS1 INDEX 531 must be assigned prior to the trunk data assignment for the SDT 3 When the SDT card is used to replace with the DTI card and the trunk data has already been assigned for the DTI perform the circuit card initialization after setting system data 4 When assigning Connection Links to the SDT card a maximum of 512kbps 8ch TS Time slot be used as Connection Link data link Assignment order of TSs used for Connection Link between SDT and FCH must be identical Any TS can be used for Connection link 7 2 4 Data Programming STEP 1 ASYDL Designate the MG of accommodating the SDT circuit card b0 b7 Assign 1 to the bit number corresponding to the
89. C gt CSCG gt CCH FUG and FPC to be designated for log in are converted automatically within the system ND 70185 E CHAPTER 8 Page 181 Revision 3 0 EX FCCS EX FCCS Features 3 4 Centralized Message Center Interface EX FCCS This section explains the conditions of Centralized Message Center Interface feature within EX FCCS Net work This feature provides an interface to the external CPU for Message Center MC information when a specified UCD group in the network is called This interface allows external control of Message Waiting Lamp MWL indications on equipped PBX stations Note Calls terminated to a UCD hunt group within a FUG will output MCI data to the Centralized MCI output port for that FUG if assigned Each FUG that requires a message center interface must have a message center interface assigned within the FUG e The number of digits to be indicated for MCI message in case 7 or 8 digit Telephone Number is used is determined by the following system data ASYD SYS1 INDEX246 b3 Maximum valid number of MCI digits is 0 1 6 digits 8 digits Note MCI equipment must be able to support 8 digit numbers e Centralized MCI feature is activated by assigning MCI equipment and UCD group at Centralized Of fice for the specific FUG MCI message cannot be transferred to the Centralized Office via EX FCCS FUG1 Center FUG Node __ Node __ Node LA D gi N I I
90. CCS ATTCON TELN 410000 STN 2000 TELN Telephone Number STN Physical Station Number Figure 6 9 Connection Test origination via 5 CHAPTER 6 ND 70185 E Page 140 Revision 3 0 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 in Node STEP 4 Answer the call and confirm the speech condition and Physical Telephone station number of the calling station STEP 5 Release the call Check 3 3 2 Line Termination Test Confirmation of Telephone STN Number STEP 1 Place a call from ATTCON D in Node B using the Telephone Number of STN A STEP2 Answer the call STEP3 Confirm the number dialed and that the Telephone Number of STN A are the same on the display of the ATTCON D STEP 4 Release the call Check 3 3 3 Line Connection Test Case of Hot Line House Phone Involved STEP 1 The Station to be tested goes off hook and confirms Ring Back Tone RBT STEP 2 Check whether the call is routed to the prede
91. CICI command Relationship between CICG and CIC Figure 8 9 CIC Number Assignment ND 70185 E CHAPTER 8 Page 189 Revision 3 0 5 Data Programming Node which uses CCIS Trunk via Fusion Link PC1 and PC2 in the example STEP 1 STEP 2 STEP 3 ASYD Assign the Point Code to all the nodes in the network uniquely as described on Page 163 ADPCL Assign the destination PC Point Code on LGRT for speech path number basis for all the nodes in the network 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 e Assign the 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 Note that if the system employs one CCIS link enter the same data in CSCG130 and CSCG131 130 Basic Primary Route c c CCH 0 131 CCH 2 Alternate CCH I Route Note 1 Jn the case of actual data entry enter corresponding LEN numbers instead of letters such as Note 2 Refer to Figure 8 8 Port Allocation and Related Command for CCIS Trunk STEP 4 ACICI Assign CSCG for Basic Primary Rou
92. CN in Center FUG 4 NEAX2000 IVS Note 3 Moving a number from a NEAX2000 IVS to another NCN in Center FUG a NEAX2000 IVS Note 3 NEAX2000 IVS another NEAX2000 IVS Note 1 Moving a number within the same NEAX2000 IVS 2000 IVS Note 1 Note 3 Adding a new number in an NEAX2000 IVS in Center FUG NEAX2000 IVS Note 1 NODE REQUIRED DATA CHANGE Note 1 Destination node Note 2 Node to be connected to the FUG where the new number is added Note 3 Node where Telephone Number is located before the Number Portability activation 4 Telephone Numbers used in the other FUG and the connected NEAX2000 IVS system are managed in the new table in NDM the table differs from the existing table for Telephone Numbers used in self a Telephone Number data NEAX2000 IVS is managed in of NCNs within all FUGs and NEAX2000 IVS b Telephone Number data in a NEAX2400 IMX is managed in the NDM of NCN within all FUGs CHAPTER 8 ND 70185 E Page 176 Revision 3 0 5 EX FCCS Features 5 Upto 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 5 Note Centralized Maintenance NEAX2000 IVS 1 MAT software for NEAX2400 IMX system and NEAX2000
93. Centralized Maintenance Fusion is 0 FUG B PC6 the node of Centralized Management Report CCIS is PC5 NEXT5 7 ASYDL SYS1 INDEX532 the CN of Centralized Maintenance Fusion is FPC of NEXT8 NEXT2 ASYDL SYS1 INDEX532 the CN of Centralized Maintenance Fusion is 0 FUG A FUG B IVS IVS PC 1 E PC 6 Alarm Info Alarm Info Centralized MAT FCCS Centralized MAT FCCS When collecting the fault information of all FUGs and connected NEAX20001VS s at MAT in FUG Example Data e FUG 1 node of Centralized Management Report CCIS is PC2 NEXT1 3 4 ASYDL SYS1 INDEX532 the CN of Centralized Maintenance Fusion is FPC of NEXT2 NEXT2 ASYDL SYS1 INDEX532 the CN of Centralized Maintenance Fusion is 0 FUG B PC6 the node of Centralized Management Report CCIS is PC3 NEXT6 8 ASYDL SYS1 INDEX532 the CN of Centralized Maintenance Fusion is FPC of NEXT5 NEXT5 ASYD SIS1 INDEX184 and 185 the node of Centralized Management Report CCIS is ASYDL SYS1 INDEX532 the CN of Centralized Maintenance Fusion is 0 1 Alarm Info Alarm Info Centralized MAT for EX FCCS LEGEND FCCS EX FCCS Enhanced lt Fusion Group FUG x Alarm Occurrence Figure 8 6 Centralized Maintenance EX FCCS ND 70185 E CHAPTER 8 Page 179 Revision 3 0 EX FCCS EX FCCS Features 3 3 CCIS Features Activated with EX FCCS CCIS features in Table 8 4 are available in EX FCCS network Table 8 4
94. DL 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 Ist DC 9 CI N Normal NND 1 Ist DC 9 CI H Hooking NND 1 ASPAN ASPAL Note Assign the OGC access code When the access code is common to all nodes use the ASPAN com mand When the access code is assigned for each node use the ASPAL command ACC 9 CI N Normal SRV OGC LGRT 200 ACC 9 CI H Hooking SRV OGC LGRT 200 ANNDL AMND Assign the necessary number of digits using the ANNDL or the AMND command depending on the route data e When the ARTD command OSGS is 2 Second Dial Tone use the ANNDL Necessary Digits Data command RT 200 OG NND 12 e When the ARTD command OSGS is 4 6 7 Sender Immediate Start Sender Delay Dial Start Sender Wink Start use the AMND command DC 9 MND 12 ARSCN Assign the Route Restriction Class RSC that allows RRIs for the external trunk route The same route restriction data must be assigned for each node Note When entering the data in STEP I and STEP 2 do not mix the commands for LDM and NDM Write the data on the same data memory as shown below CHAPTER 5 Page 88 Revision 3 0 When writing the data on the LDM ANPDL STEP 1 gt ASPAL STEP 2 When writing the data on the ANPDN STEP 1 ASPAN STEP 2 ND 70185 E DATA PROGRAMMING Assignment of FCH Related Data 71
95. F 01H ETHER Controller Initial NG FLTINF 02H ETHER Link Failure FLTINF Fault Information Note Circuit Number of FCH 0 7 FCH Mounting Location MG Module Group 0 Unit 0 3 G Group 00 23 Figure 7 15 23 T FCCH Fault Recovery Notification ND 70185 E CHAPTER 7 Page 159 Revision 3 0 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 The figure below shows the general format of this message 1 0 2 LILI Lot gt a EE NET i DATA Circuit Number of FCH 0 7 b7 bo i FCH Mounting Location E AE E i Module Group i The contents vary depending FLTINF i U Unit 0 3 i G Group 00 23 s b7 50 FLTINF b7 bo 0 TRC RS Nite 5 FCH CKT No b7 U G
96. Fault Notification Recovery _ Status Information FCH Alternate Routing Start Notification N FCH Alternate Routing End Notification ND 70185 E CHAPTER 7 Page 147 Revision 3 0 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 TOPU 10 BASE T cable 1 d P ERES NR 4 Front Cable FCH DTI PIM 1 System Message 13 H Signaling Link Failure 1 0001 0000 0000 0000 2 0000 0000 0000 0000 PIM BSCM LPM L BASEU FRONT VIEW Figure 7 1 Related Hardware CHAPTER 7 ND 70185 E Page 148 Revision 3 0 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 00 0000 0000 0000 2 0000 0000 0000 0000 T T T MG Module Group Un
97. G U Gr ty 9 AFCH Assignment of FCH Number for 9 dt Mon m Dch TK2 9 0 1 FCHEN 000 27 0 FGH 8 9 FCHN 2FCHEN 010 19 0 Use this LENS 0 BE 9 27 0 MG 0 Gr Lv Figure 5 27 Assignment of FCH Number The AFCH command display should look similar to the following 1 255 wa Untitled _FCHEN File View Help f MG 0 7 AFCH Assignment of FCCH Number for U 0 3 Group 00 31 FCHN Lv 0 7 FCHNEN WRT Note Before assigning FCHN the trunk data must have been assigned using the ACTK command Figure 5 28 AFCH Command Display example CHAPTER 5 ND 70185 E Page 82 Revision 3 0 STEP 2 AFRT Fusion with FCH only DATA PROGRAMMING Assignment of FCH Related Data Assign connection route numbers as shown below using the AFRT command FCHN 1 CNT 1 C 10 31 2 3 32 C RT 10 TRK 10 TRK 40 LN The AFRT command display should look similar to Figure 5 30 Figure 5 29 AFRT Sample Data Sheet Untitled EclipseCmd File View Help FCHN Assign FCHN CNT C RT 1 2 For Help press F1
98. Hook Alarm and Ring Down IC calls from PSTN Day Night information is transferred from the terminating node Note 1 When Timing Start is in service Called Sub Address for ISDN Network cannot be dialed Note 2 This data is necessary at each node Assign the self FPC at the terminating node Note 3 This data is necessary at the node providing ATTCON ND 70185 E CHAPTER 5 Page 63 Revision 3 0 DATA PROGRAMMING Assignment of System Data Index 800 For ASYDL b0 0 1 ALGNL ALGSL UGN TN basis b1 0 1 2 ASPAL on a TN basis b2 0 1 ANPDL on TN basis b4 0 1 AFRSL ASTPL AUNEL on TN basis b5 0 1 ASTPL on a TN basis b7 0 1 AAEDL on a TN basis For ASYDN 0 1 ALGNN ALGSN UGN TN basis b1 0 1 ASPAN on a TN basis 2 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 AAEDN on a TN basis When different numbering development on a TN basis is not required set the above bits This figure shows the display of the ASYDN command Index 514 as an example A ASTON Lleyda Figure 5 7 ASYDN Command Display example Note 4 Be sure to execute Non Load Initial after setting the FPC data The assigned FPC becomes effective by this operation CHAPTER 5 ND 70185 E Page 64 Revision 3 0 DATA PROGRAMMING Assignment of FPC and MG and UNIT into Netw
99. LANI B are used for each CPU the cross cable connection between HUBs for 1 is not necessary Note The Ethernet cables shown in the examples in this section are NOT available from NEC These cables must be provided by the customer depending on the system configuration See Chapter 6 Connecting 10 BASE T Cables Note When connecting the MAT using HUB card be sure to use a dedicated HUB for the MAT DTI PA 24DTR ATTENTION Contents Static Sensitive Precautions Required z Ww 060 yn 10 BASE T cable straight 52 VM OA 0090 2000 09 9 2 X mU gt Pr ac 9 D Guo a AM PZ PC19 ct N 55590 Om San 10 BASE T cable straight 10 BASE T cable for Fusion Link 10 BASE T cable for MAT Figure 4 11 Overall 10 BASE T Connections CHAPTER 4 ND 70185 E Page 44 Revision 3 0 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
100. LE 5 ND 70185 E Page ii Revision 3 0 TABLE CONTENTS CONTINUED Page ilies Pala sets 5 E 112 8 1 Data Shee Or AF as aqu a dp em pe du 112 8 2 Data Sheet of ALAIN ded d eid Keats 118 8 3 Data Sheet for 114 8 4 Data Sheet for y XR SE RE Seed E DRE RUPES 115 8 5 Datasheet tr ALONE eod dd eu PIE QE 116 8 6 Data Sheet tor 2 5 2 lt 55955 5666 58 ERROR ERE 117 B 7 Data Sheet for ALGSL TYPE2 EES SR RS 118 8 8 Dati base TO poses ER RAE ERES eq rd e 119 8 9 Data shes OT BORD asses qued aped 120 810 Data Shes lo ADIK 22654 cakes ER RYE AR Rr eR ER RUE RR OR RAE CORA 122 8 11 Data Sheel for AFGH qa dad 123 SIE Daa 27 Laon Ead UP Oed dd EO RC odo ede doped 125 Bio Dass br ACAN 127 8 14 5 24 5 gt 455 555 128 815 Date Shieettor ACTA
101. LED Indicates Abnormality 2 3 Test Procedure STEP 1 Setthe 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 FCH card J 1 mi Q 2 FCH gn Mode Switch E 8 standard setting ATTENTION 12 9 Fusion Link Test Mode Bandi Required ode i UP 829 B i DOWN screw driver X m S E Anti static Kit Front View Front View Note Be sure to initialize the card after changing the setting of the Mode Switch Figure 6 5 How to Set the Fusion Link Test Mode STEP 2 Select an appropriate loopback point by setting the switch SWO1 SW13B Select a loopback point by setting the switch To set Internal Loopback DTI PA 24DTR 3 swoog BER RM Aj d Contents BL23 SW01 SW13B MB WU E Anti static Kit Line External LJ Setting a Loopback point Payload Internal
102. NFIGURATION Fusion systems can be divided into the following two types e Fusion system with e Fusion system without Note Fusion Call Control Handler FCH PA FCHA 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 con figuration the Fusion link is established between nodes using Ethernet The DTI card carries B channels only in this example Figure 3 1 shows a Fusion System Configuration without FCH This figure shows a Fusion System Configuration without FCH Node A Node B TSW INT TSW INT MUX MUX DTI DTI B channel Max 328 ft Max 328 ft Max 100 m Max 100 m gt D channel e Fusion Link Note HUB 10 Base T 10 Base T CPU H LANI LANI PCI Bus PCI Bus TSW Time Division Switch PH SW 10 MUX PH PC36 LANI LAN Interface PZ PC19 DTI Digital Trunk Interface PA 24DTR Note maximum of 4 HUBs be cascaded per route Figure 3 1 Fusion System Configuration without FCH ND 70185 E CHAPTER 3 Page 11 Revision 3 0 SYSTEM CONFIGURATION Fusion System with FCH 2 Fusion System with FCH 2 4 System Configuration A sample Fusion system configuration that uses a DTI to
103. NFIGURATION System Considerations Example 2 When both FCCS and CCIS links are established between two nodes Node B Node C Centralized Fusion Center Node Node C Node A Node D Figure 3 15 Centralized Management Report Fusion Example 2 Node A B C Refer to Example 1 on the previous page Node D When Point Code of Node C 12 is assigned to ASYD SYS 1 Indexes 184 and 185 System mes sages are sent to Node C using CCIS When this system data is not assigned 0 and Fusion Point Code of Node C 3 is assigned to ASYDL SYS 1 Index 532 system messages are sent to Node C using FCCS ND 70185 E CHAPTER 3 Page 23 Revision 3 0 SYSTEM CONFIGURATION System Considerations Example 3 When a node is linked with LAN interface Node PRT FCCS with LAN CCIS Node D el Centralized MAT Fusion Node E Figure 3 16 Centralized Management Report Fusion Example 3 Node A send system messages to Node E assign Point Code of Node C 1 to ASYD SYS 1 Indexes 184 and 185 Node B send system messages to Node E assign Point Code of Node C 1 to ASYD SYSI Indexes 184 and 185 When this system data is assigned system messages received from Nodes C and D are also transferred to Node E However when this data is not assigned 0 system messages re ceived from Nodes C and D are ignored and not transferred to No
104. O data of FGH LENs 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 Assign 2 DIX spec CONTTYP Voice Channel Control Type Assign 1 Server LINK NUM Qsig Prime Link Number Assign the number 1 32 of interfaces for speech total DTI card number CSLINK NUM Client Server Connection Max Number Assign 0 CHAPTER 5 ND 70185 E Page 100 Revision 3 0 DATA PROGRAMMING Assignment of FCH Related Data STEP 5 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 2Gateway function is used P ROUTE Priority Route 0 1 FCH FGH Example data assignment is shown in Figure 5 44 and Figure 5 45 FPC FCCH FCH NUMBER USE GATE P ROUTE ROUTE E A total of 8 routings CNT 1 8 must be assigned When alternative routing is not required assign the same routing data for each CNT Figure 5 44 Sample Data Assignment AFPC Internet Intranet Router Router 5 w w ES ROUTER J aaa aaa aaa a bbb bbb bbb b CCC CCC CCC C FCHN 1 self Node b Speech Figure 5 45 Internal LAN Routing Data Assign
105. ON RT No C RT 1 1023 FUNCTION FUNC TF Type of Trunk 0 2 3 Bothway Trunk BWT TCL Trunk Class Fixed 47 0 3 4 Fusion Trunk 5 31 RLP Trunk Release Pattern Fixed 2 0 1 2 First party Release dum SMDR Detailed Billing Information Fixed 4 0 0 0 0 0 0 0 0 SMDR is out of service 12 SMDR is in service LSG Line Signal 0 11 5 12 B channel 13 D channel 14 15 PAD PAD control Fixed 7 0 0 Default Send 8bD Receive 0dB Send 4dB Receive 4dB Send 8dB Receive 12dB Send 8dB Receive 8dB 5 OdB TRKS Trunk Selection Sequence 7 0 LIFO 0 0 0 0 0 0 1 FIFO TC EC Fixed 0 02 No MPC EC 8 1 0 0 0 0 0 0 2 2 3 Not used FINT Fusion Interface Specification 9 0 Fusion standard 0 0 0 0 0 0 1 15 CHAPTER 5 ND 70185 E Page 120 Revision 3 0 1 1023 FUNCTION FUNC FPEG Fusion PEG Fixed 0 0 Nothing of FUSION PEG Exist of FUSION PEG DATA PROGRAMMING Office Data Sheets TC Timer Class Fixed 0 1 1 2 2 3 8 sec 4 30 sec Miscellaneous Timer Counter Fixed 0 Timer value TC x MTC STSEQ Status ENQ Fixed 0 Fusion link status check 0 Available 1 Unavailable Fusion Gateway Han
106. OPU 5 3 Tex MjioBasET 8 5 S o PIM3 PIM3 rx al Wrox 0 UTP CTG5 ST CA K ROVEN PIM 2 PIM2 m EV A FANU PIM 1 PIM 1 UTP CTG5 ST PiMO pimo T 5 E 1001010203040506 i 1 BSCM BSCM UTP CTG5 ST CA J i 00 01 02 03 04105 LPM LPM UTP CTG5 ST BASEU BASEU Figure 4 15 Examples of Ethernet Cable Connection FCH in 2 1 IMG System 1 2 CHAPTER 4 Page 52 Revision 3 0 ND 70185 E INSTALLATION Connecting Cables Note ATTENTION lt FCH in PIM2 Pattern 3 gt lt FCH in PIM2 Pattern 4 gt TOPU TOPU PIM 3 PIM 3 y 0705 ST CAK PIM 2 2 PIM 1 UTP CTG5 ST CA CTG5 ST UTP CTG5 ST CA J z a PIM 0 00 0 1 02 03 04 05 06 1 5 5 I CTG5 ST CA J LPM UTP CTG5 ST CA J mj 00 01 02 03 04 05 06 01 02 03 04 05 LPM UTP CTG5 ST CA J J L BASEU When dual LANIs are used in both Slot 00 and 03 of CPR Pattern 3 or 4 be sure to use at least two HUB cards One HUB for internal LANI in Slot 00 and the other for external LANI in Slot 03 However if this is the case and FCH is also
107. PC 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 LENS A LEN of SDT EAD A 07 pad off LENS B LEN of FCCH EAD B 07 pad off CHAPTER 5 ND 70185 E Page 96 Revision 3 0 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 7 31 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 Node A Node B Speech Data for Fusion Fusion Network MT Internet NT uif R LEM oner Intranet Router Signaling data for Fusion FCCS link Figure 5 39 External Router Overview Speech Fusion Network c ROUTER ACRD 4 j 10BASE T i nterne ACIE BM i Intranet AETH i i i MU EE signaling PBX 10101 ipu pm 55 ACRD D lt Procedure gt 1 AERE pm 3 1 Using two DTI cards make a loop connec
108. Page 70 Revision 3 0 DATA Assignment of Telephone Numbers Figure 5 19 ALGSN Command Display example ND 70185 E CHAPTER 5 Page 71 Revision 3 0 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 m Route 1 FPC Fusion Network D ch Route 11 13 B ch Bearer Channel Data Channel FPC Fusion Point Code Figure 5 20 B ch and D ch The ACRD command should look similar to the following This figure shows an example of data setting for a B ch route ACRD Assignment of Connection Route Class Data C_RT 1 1023 CDN FUNC DT CDN FUNC DT FUNC DT 3 7 o 13 o e 4 8 TC EC o 14 FGH 2 9 FNT o 15 o o 10 FPEG o 16 LKIND o tse 12 10 o o PAD 7 12 MTC 55 1 mm a Figure 5 21 ACRD Command Display example CHAPTER 5 ND 70185 E Pa
109. 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 Fusion Network i Fusion Center IMX 5 2 C polling p gt F FCCS SMDR equipment billing information Node B Node A FCCS of Node B polling x MX FCCS billing information of Node C Node C Example 2 ey In either case Centralized Billing CCIS is used The size of call base table is 144 Bytes i CCIS Center IMX non IMX CCIS SEX Billing Format CCIS Node B 144 Bytes Call Base Table 01 01090010030020210 100100100202070010010 25223209199 314 iai A 010112345000000000008 non iMX 44 Bytes Cali Table 01KA01090010030020210 5 100100100202070010010 0000000004111106341997 1225223209199712252314 010112345000000000008 Example 3 In either case Centralized Billing CCIS is used The size of call base table is 144 Bytes i CCIS Center Node IMX CCIS Node A Billing Format CCIS 144 Bytes Cali Base Table 01
110. Telephone Numbers STEP 1 ANPDN Make a Telephone Numbering plan on the network The explanation is given here on the assumption that the network adopts the numbering plan shown below Therefore make modifications to the data assignment explained here when you assign the data on your network White numerals on black background are Telephone Numbers 12 11 430000 STN 2000 TELN 420000 STN 2000 ANPDN ASPAN y STN Physical Station Number STN 2000 TELN Telephone Number Figure 5 13 Telephone Number Allocation ND 70185 E CHAPTER 5 Page 67 Revision 3 0 DATA PROGRAMMING Assignment of Numbering Data for Telephone Numbers STEP2 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 O NCN Node A Telephone Number 4 O TN 1 1stDC 4 CI N Normal NND 6 BLF 0 Eg TN 1 1stDC 4 0 NND 6 BLF 0 6 digits O O O O Figure 5 14 ANPDN Sample Data Sheet The ANPDN command display should look similar to the following 1stDC 1st Digit Code ASCII 0 9 ANPDN Assignment of Numbering Plan for Network Data Memory CI Connection Index N Normal TN 1stDC CI H Hooking B Busy NND Necessary Digit 1 16 digits BLF Busy La
111. X 1 Make Busy B ch idle i Ba Call Origination 5 2 9 Note Using the MBCT command make busy all B channels in the route except the trunk to be tested Figure 6 8 Station to Station Connection Test origination via FCCS ND 70185 E CHAPTER 6 Page 139 Revision 3 0 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 11 ATTCON Call Origination Test STEP 1 Dial the operator access code normally 0 from STN A in Node 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 STEP 5 Release the call by pressing the CANCEL key STEP 6 Replace the handset of STN A in Node A Check 3 2 2 ATTCON Call Termination Test STEP 1 Press a LOOP key on an ATTCON in Node B STEP 2 Dial the Telephone Number of STN A STEP3 Confirm the ringer sounds properly at STN A STEP 4 Answer the call and confirm the speech condition is sufficient no noise not one way speech etc STEP 5 The operator at the ATTCON releases the call by pressing the CANCEL key STEP 6 Replace the handset of STN A in Node A Node A Self Node Node B Code 0 RINGING S 1 F
112. a 8 I Direction of MCI message FCCS Fusion Call Control Signal Direction of a call Enhanced CCIS a Message data is transferred to the offered MCI connected to Node B in FUGI given that a call from a station in IVS node terminates to a UCD station in Node A shown in the figure within FUGI via EX FCCS b Message data is transferred to the offered MCI connected to Node B in FUGI given that a call from any station within FUG2 terminates to a UCD station within FUGI via EX FCCS c Ifa call from Node F terminates to UCD station in Node E the message cannot be transferred to the MCI connected to the Centralized Office In this case the message is sent to the MCI connected to Node H within FUG2 d Message data is transferred to the shared MCI connected to Node H in FUG2 when a call from any station terminates to a UCD station in the same Fusion Group CHAPTER 8 ND 70185 E Page 182 Revision 3 0 5 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 EX FCCS FCCS Fusion Call Control Signal Enhanced CCIS Direction of MCI message Direction of a call Call Waiting Lamp Controlling When the Centralized Office adopts the ICS MCI f
113. ace not effective TRC RS FCH CKT No FCH CKT No Circuit No of FCH b7 MG u U Unit 0 3 FCH Mounting Location L G Group 0 23 Figure 7 22 23 U FCCH Status Notification Spanning Tree Generation 9 6 FLTINF 85H Checksum Verification Failure This message is displayed when Checksum verification has resulted in failure between the PBX and the firm ware Checksum Verification Failure 1 xx 85 xx 00 0000 2 0000 0000 0000 00 00 LILI b7 50 Checksum of Firmware L b7 50 L b7 50 85 Checksum Verification Failure b7 50 TRC Trace Confirmation Bit 010 0 1 Status Notification Primitive Trace L IL RS Receive Send Primitive Trace not effective TRC RS FCH CKT No FCH CKT No Circuit No of FCH b7 50 TD F MG G MG Module Group 0 Unit 0 3 FCH Mounting Location G Group 0 23 Figure 7 23 23 0 FCCH Status Notification Checksum Verification Failure CHAPTER 7 ND 70185 E Page 166 Revision 3 0 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 op
114. adjacent Node s FPC O OOOOOOO0O000000000000000000000000 Assign all nodes data in the same manner Figure 5 33 AFPC Sample Data Sheet ND 70185 E CHAPTER 5 Page 85 Revision 3 0 DATA PROGRAMMING Assignment of FCH Related Data STEP 4 Assign the Fusion Connection Index Code FCIC and the LENs on an adjacent FPC basis Figure 5 34 shows a sample data sheet for Node A Note not necessary to assign the same number as trunk and FCIC However FCIC numbers between adja cent nodes must be identical LCN LCN V TRK 1 TRK 31 rreiczr Node B LCN 2 FCIC 4 LENS 000013 i LCN TRK 3 TRK 32 9 2 1 LENS 000010 2 9 2 FCIC 2 C LENS 000011 FOIC n 7 TRK 10 40 LECIG n 8 FPC 2 FCIC 3 C LENS 000012 _4 9 Self Node C 10 Adjacent Node 9 LCN FCIC number must be identical Figure 5 34 ACAN Sample Data Sheet The ACAN command display should look similar to the following ACAN Assignment of CIC Number between Adjacent Node for Network Assign Adjacent FPC FPC FCIC Fusion Circuit Identification Code 2 C_LENS WRT C LENS For Help press F1 mm 74 Figure 5 35 ACAN Command Display example CHAPTER 5 ND 70185 E Page 86 Revision 3 0 DATA
115. ail data programming related to LCR LCRS such as AFRSN AOPRN ARNPL and AMND com mand STEP 7 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 Note Check whether the trunk originating call via CCIS be executed by dialing ACC Telephone Number here Reexamine the assigned numbering plan data if the call cannot be connected There may be some er ror in data setting so far 4 1 3 To Access EX FCCS Trunk via EX FCCS Telephone Number NCN of the Center Fusion Group AELGN Telephone Numbers must be assigned for all the station within the network uniquely Use AELGN command to allocate EX FCCS Telephone Number FUG data must be assigned previously by AFUGN command to activate this command Only readout function can be used by this command in case both the Self FUG Number and the Con nection FUG Number are assigned if the Self FUG is not the Center FUG Note Check whether the trunk originating call via CCIS can be executed by dialing EX FCCS Telephone Num ber Reexamine the assigned numbering plan data if the call cannot be connected There may be some error in data setting CHAPTER 8 ND 70185 E Page 192 Revision 3 0 5 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
116. amine the assigned numbering plan data if the call cannot be connected There may be some er ror in the data setting so far ND 70185 E CHAPTER 8 Page 197 Revision 3 0 This page is for your notes CHAPTER 8 ND 70185 E Page 198 Revision 3 0
117. ancel Payload Loopback Set OFF x Payload Loopback Cancel 3 ON Channel Make Busy Set Note OFF x All Channel Make Busy Cancel ND 70185 E CHAPTER 4 Page 35 Revision 3 0 INSTALLATION Key Setting on Circuit Cards Table 4 4 Switch Setting Patterns for the DTI Card Continued SWITCH STANDARD SWITCH NAME NUMBER SETTING SETTING MEANING ON Transmission Signal A Logic Negative SW4D Transmission Signal A Logic Positive ON Receiving Signal A Logic Negative 622222227 Receiving Signal A Logic Positive ON RMT Alarm Sending Not to be sent out RMT Alarm Sending To be sent out Simultaneous Seizure Supervision Not to be controlled Simultaneous Seizure Supervision To be con trolled Data Link Control MOS Data Link Control BOS Multiframe Selection 12 Multiframe Multiframe Selection 24 Multiframe Signal Selection AMI Alternate Mark Inver sion Signal Selection B8ZS Bipolar with 8 Zeros Substitution Fixed Impedance setting 100 Impedance setting 110 Transformer at Middle Point Transmission Ground Transformer at Middle Point Transmission Open Transformer at Middle Point Receive Ground Transformer at Middle Point Receive Open Idle Code To be sent out Idle Code Not to be sent out CHAPTER 4 ND 70185 E Page 36 Revision 3 0 INST
118. and the Point Code PC in the connected Fusion Group Note Confirm the Centralized can log in to each node here Reexamine the assigned data if log in can not be executed There may be some error in data setting so far 2 Access to EX FCCS Trunk via EX FCCS Telephone Number Assign the following data to activate originating calls via EX FCCS trunk EX FCCS Abbreviated Digit Code ADC must be assigned by using AEADN command at all the IMX nodes in the network Only at the NCN of the Center Fusion Group allocate EX FCCS Telephone Numbers for all the stations in the network uniquely lt the nodes consist of IMX system 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 NCN of the Center FUG AELGN Telephone Numbers must be assigned for all the station within the network uniquely Use AELGN command to allocate EX FCCS Telephone Number FUG data must be assigned previously by AFUGN command to activate this command Only readout function can be used by this command in case both the Self FUG Number and the Con nection FUG Number are assigned if the Self FUG is not the Center FUG Note 1 Refer to the service feature manual for NEAX2000 I vs system as to the data programming on NEAX2000 IVS side Note 2 Check whether the trunk originating call via CCIS can be executed by dialing EX F CCS Telephone Number here Reex
119. are mounted in the following slots with the specified RT numbers data setteing is as follows FCH RT13 FGH RT14 LIH HOd v1 LH HOd EN ERUIT slot05 slot21 Figure 5 52 Sample Data Assignment ND 70185 E CHAPTER 5 Page 105 Revision 3 0 DATA PROGRAMMING Assignment of FCH Related Data STEP3 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 PBX speech RT1 oe DT Ti AFCH command display a FGH signaling x RTI4 A ROUTER 5 Q sig FCHEN 000030 Note gt zi FCHN 1 S e 9 Note This setting is sample 5 ci m _ FCHEN 000030 2 RT13 to CPU Figure 5 53 Assignment of FCHN Example CHAPTER 5 ND 70185 E Page 106 Revision 3 0 DATA PROGRAMMING Assignment of FCH Related Data STEP5 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 not use gateway FCHN FCH Number Assign the FCH Number specified in STEP 4 C RT Connection Route 1 1023
120. 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 Note that if the system employs one CCIS link enter the same data in CSCG130 and CSCG131 0 130 Primary Route CCH2 CCH 1 www w w w gt Note 1 Jn the case of actual data entry enter corresponding LEN numbers instead of letters such as Note 2 Refer to Figure 8 8 Port Allocation and Related Command for CCIS Trunk CHAPTER 8 ND 70185 E Page 188 Revision 3 0 STEP 7 STEP 8 EX FCCS Data Programming ACICI Assign CSCG for Basic Primary Route The odd numbered CSCG for Alternate Route assignment 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 corre sponding to ADPC A
121. cards are mounted in Slots 11 and 12 00 2 04 05 06 07 08 0910 13 14 22 93 5 7 19 23 01 03 05 07109 11 um 14 18 22 2 13 13 17 21 00 102 04 06 08 1 i 00 02 04 06 08 10 12 5 12 16120 HHI Figure 5 24 Mounting FCH and DTI Cards in High Density Slots CHAPTER 5 ND 70185 E Page 78 Revision 3 0 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 19 20 21 22 23 ald 14 18 22 gt i 13 17 21 x X 00 02104 06 08 10 12 16 20 d d 4 DTI Figure 5 25 How to Assign LEN Data 2 D 79189 E CHAPTER 5 Page 79 Revision 3 0 DATA Assignment of Telephone Numbers Table 5 3 Data Programming Sheet for High Density Slot C TK 1 4095 ci o Time Slot Allocation DE ms Bl
122. 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 Node A Node B D channel example TSW INT cho E ch 23 TSW INT MUX MUX Fusion Link DTI DTI DA B channel D channel DA FCH T 10 Base T 10 Base T pues pe HUB T 10BaseT 10 BaseT CPU LANI CPU PCI Bus PCI Bus TSW Time Division Switch PH SW 10 HUB PA M96 MUX PH PC36 LANI LAN Interface PZ PC19 FCH Fusion Call Control Handler PA FCHA DTI Digital Trunk Interface PA 24DTR Figure 3 2 Fusion System Configuration with FCH 2 2 Redundancy of Fusion Link The FCH PA FCHA card handles a Fusion link occupying one time slot of a frame by D I function located on the DTI card In terms of redundancy the Fusion system with FCH can have one of the following config urations Redundant Configuration LANI FCH and DTI e Redundant Configuration HUB and DTI e Redundant Configuration and DTI e Non Redundant Configuration CHAPTER 3 ND 70185 E Page 12
123. cations on Fusion Link Related Circuit Cards 134 Figure 6 3 Fusion Link Fest ccc idee nee eee he ERS WHEE DERE S ERR wee 135 Figure 6 4 Loopback Pans br DTI sa dcc bo CERO dee ae XN eas 136 Figure 6 5 How ta Set the Fusion Link Test RR i de UR b ds 137 Figure 6 6 Loopback Paint Designation CR RERO SLO RAT R OR dd 137 Figure 6 7 Fusion Link Test dace ed e ARR E ERE dane 138 Figure 6 8 Station to Station Connection Test origination via FOCS 139 Figure 6 9 ATTCON Connection Test origination via 140 Figure 6 10 Line Connection Test origination via 141 Figure 6 11 3 party Conference Trunk Function Test via 142 Figure 6 12 Fusion 4s Qua LES 143 Figure 6 13 CGIS FGCS Outgoing Call Tesh use dada pack o x a CHO RC GC RR RR E 144 Figure 6 14 Loopback Palris Br SDT OBI o CR CIR EY CR ARCA 145 Figure 6 15 Loopback Setting by P SW key PA SDTA 145 Figure 7 1 2246 ERA dep Seer 148 Figure 7 2 3 B PM C level Infinite Loop
124. cess code 9 CO call 0 Operator Call CCIS network ATTCON 0 STN 2000 STN 2000 PC Point Code Numbering Data example Numbering Plan Example before Upgrading After Upgrading Numbering Plan Data of Node A after upgrading Ds N 100 Priority Call 1 101 Priority Call 2 Assign these codes using ANPDL 102 Priority Call 3 ASPAL commands if these features 0 Operator Call are provided on the Fusion network CCIS Fusion network 2xxx Physical STN 8x CCIS access code 9 CO call 4xxxxx Telephone Number Assign this using the ANPDN and ASPAN commands STN 2000 TELN 410000 Numbering Data example go STN 2000 STN 2000 TELN 420000 TELN 430000 PC Point Code FPC Fusion Point Code Numbering Plan Example after Upgrading Numbering Plan Data for Telephone Numbers To assign Telephone Numbers 4xxxxx set the Numbering Plan data at Network Control Node in this instance Node A as follows 1 1 I I IstDC 4 gt NND 6 1st DC 4 SSC 16 Logical Number l 1 I 1 Figure 5 3 How to Upgrade the Numbering Plan Data of an Existing CCIS Network ND 70185 E CHAPTER 5 Page 61 Revision 3 0 DATA PROGRAMMING Assignment of System Data 2 Assignment of System Data STEP 1 ASYDL and ASYDN Assign the number of da
125. circuit DC 8110 8 STEP 4 ARNPL Using ARNPL assign the access code for each external trunk route but not for a dummy route RT 10 ACC 8 RT 200 ACC 9 Note When entering the data STEP 1 2 6 7 and 8 do not mix the commands for LDM and NDM Write the data on the same data memory as shown below When writing the data on the LDM ANPDL ASPAL AFRSL gt AOPRL gt AADCL STEP 1 STEP 2 STEP 6 STEP 7 STEPS When writing the data on the NDM ANPDN ASPAN gt AFRSN gt AOPRN gt AADCN STEP 1 STEP 2 STEP 6 STEP 7 STEPS ND 70185 E CHAPTER 5 Page 91 Revision 3 0 DATA PROGRAMMING Assignment of FCH Related Data STEP 5 STEP 6 STEP 7 STEP 8 STEP 9 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 1 The other CDNs may be left default data 0 for the dummy route 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 LGRT Dummy route number NPC 8110 OPR 1 AOPRL AOPRN Note 2 Using AOPRL assign the external route number to OPR assigned in the AFRSL command TDPTN 0 OPR 1 RA 0 E 1 LGRT 10 5 4 PNL 0 OVFT 0 PRSC 0 TDPTN 0 OPR 1 RA 1 E 0 LGRT 200 SKIP 8 PNL 128 0 PRSC 0 AADCL AADCN Note 2 Using AADCL assign the additional Digit Code
126. cy CHAPTER 3 ND 70185 E Page 16 Revision 3 0 SYSTEM CONFIGURATION System Considerations Condition 9 The maximum of data link speed is 1 5 Mbps Condition 10 Connection Trunks B ch conform to the following specifications Existing external trunk cannot be used as alternate routes for connection trunks Billing information on connection trunks cannot be output e Under the following conditions connection trunk seizure NG will occur Data Link Failure Connection Trunk all busy LANI built in FCH failure e Connection test for connection trunks is not provided e Nailed Down connection is not provided for connection trunks Specifications on Release 2 or earlier software e value for connection trunks is fixed to 0 db e Echo canceller EC MPC control is not provided e Nailed Down connection is not provided for connection trunks Condition 11 Ifa layer 2 failure occurs the connections are released Condition 12 When fusion links and CCIS links coexist on a Fusion network the following conditions should be considered A Fusion link may be used as a CCIS link through data programming In this instance if the other node accommodates a dedicated CCIS card CCIS will not work even if the self node accommodates Fusion Link Card Therefore the same Fusion Link Card must be accommodated at both nodes Figure 3 13 shows an example of CCIS FUSION networks ND 70185 E CHAPTER 3 Page 17 Revision 3 0
127. data programming using the following upgrading patterns e Upgrading CCIS between FUGs to EX FCCS Network e Upgrading CCIS between FUG and IVs system to Enhanced CCIS Network e Upgrading CCIS between IMX system and IVs systems to Enhanced CCIS Network 4 2 4 Upgrading CCIS between FUGs to EX FCCS Network FUG1 Center FUG FUG2 FCCS ccs entralized MAT ND 70185 E CHAPTER 8 Page 193 Revision 3 0 5 Data Programming 1 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 STEP2 Assign the CCH Selection Data by designating all the Fusion Point Code FPC and the Point Code PC in the connected Fusion Group Note Confirm whether the Centralized can log in to each node here Reexamine the assigned data so far if log in can t be executed There may be some error in data setting 2 To Access EX FCCS Trunk via EX FCCS Telephone Number Assign the data at the NCN of each Fusion Group Abbreviate Digit C
128. de E System messages received from Nodes C and D are not output to the system message printer con nected to Node B Node C D To send system messages to Node E via Node B and Node A assign Fusion Point Code of Node B 11 to ASYDL SYS 1 Index 532 Node E Received system messages are stored the memory area for Centralized Management Report Fu sion CHAPTER 3 ND 70185 E Page 24 Revision 3 0 3 4 3 4 1 1 SYSTEM CONFIGURATION System Considerations Fusion Attendant Desk Console 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 00 Or 01 7 As regards the following data Waiting Call Display data be sure to develop the unified data at each node ASYD SYS2 INDEX 8 ASYD SYS2 INDEX 9 Note 2 When the connection routes RT are all busy the operator call becomes in Night mode ASPAL Node A ACC 90 SRV SSC SID 2 operator call FPC 3 Node C Fusion Network ASPAL Node D ACC 91 SRV SSC SID 2 operator call FPC 5 Node E Data Programming Node D Data Programming Node A z E 90 4 91 Operator Call Operator Call ASPAL Node B ACC 90
129. de which exists on the network Note the AFMU command is available at NCN only e Assign Logical Route Numbers of all routes external trunk on the network using the ALRTN com mand Note that the ALRTN command is available at NCN only 1 2 2 Numbering Plan Data e ANPDN ASPAN for NCN only Assign numbering plan data for Telephone Number When Operator Call or Priority Call ATT is used on the Fusion network replace the existing numbering plan data for these features using the ANPDL and ASPAL commands Note Numbering Plan data for the LDM and or NDM cannot use separate Tenant Numbers TN Therefore be sure to assign the following data on the ASYDL command e ASYDL command 8 81 INDEX 800 I ASPAL command tenant data table development on LDM Common b2 1 ANPDL command tenant data table development on LDM Common 1 2 3 Station Numbering e Assign Telephone Numbers using the following commands ALGNN gt ALGSN Assign Telephone Number at network level NCN only 1 2 44 Fusion Link Data e Assign the Fusion Link data using the following commands Fusion with ACRD gt ACAN gt MBCT gt AFCH gt AFPC gt AFRT Fusion w o ACRD gt gt gt MBCT gt 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
130. dler Fixed 0 MMN Kind of Multiple Equipment 0 TDM 1 MM Node 2 3 ND 70185 E CHAPTER 5 Page 121 Revision 3 0 DATA PROGRAMMING Office Data Sheets 8 10 Data Sheet for ACTK CONNECTION ROUTE CONNECTION TRUNK NUMBER NUMBER C RT TK 1 1023 1 4095 CONNECTION EQUIPMENT NUMBER REMARKS C LENS CHAPTER 5 ND 70185 E Page 122 Revision 3 0 8 11 Data Sheet for AFCH DATA PROGRAMMING Office Data Sheets FCCH NUMBER LENS OF FCCH FCHEN FCHN 1 255 MG U G REMARKS BY 9 N AR on oo N N N N N N N N N N oo N o N 99 cO o o ND 70185 E CHAPTER 5 Page 123 Revision 3 0 DATA PROGRAMMING Office Data Sheets FCCH NUMBER LENS OF FCCH FCHEN FCHN 1 255 MG U G REMARKS 34 CHAPTER 5 ND 70185 E Page 124 Revision 3 0
131. e Channel Control Type Assign 1 Server LINK_NUM Qsig Prime Link Number Assign the number 1 32 of interfaces for speech total DTI card number CSLINK_NUM Client Server Connection Max Number Assign 0 DG_IP FPC 10 Speech 2 T1 LVO data of FGH LENS amp E 2 ROUTER i 5 2 S ES RT13 to CPU Note This setting is a sample Figure 5 58 Sample Data Assignment AGIP ND 70185 E CHAPTER 5 Page 109 Revision 3 0 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 LVO 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 Note 1 Assign LENS and RT ACC corresponding to the router port Note 2 Assign the Basic LENS data of the Speech Channels 1st LEN of the HW block where the DTI card is mounted The following shows basic LENS data for assigning Q sig Prime B channel data Assign the 1st LEN of the HW block where the DTI card is mounted PIM 2 2 4
132. e Ses 174 us EX FOCOS PBASE MAREE A RED idest 175 3 1 Number Porabllib VES dep P dr o 175 3 2 Genralized MAT for EX FOCS i tpe ud d ep dq qd e 127 CCIS Features Activated with 180 3 4 Centralized Message Center Interface 182 3 5 Centralized Billing EX FCCS Polling 184 B Dnro I rie I us ande EES 185 4 1 Brand new 5 186 4 1 4 To Log in to All Nodes EX FCCS 186 4 1 2 To Access EX FCCS Trunk via ACC Telephone Number 191 4 1 3 To Access EX FCCS Trunk via EX FCCS Telephone 192 4 2 Upgrading CCIS Network to EX FCCS 193 4 2 4 Upgrading CCIS between FUGs to EX FCCS Network 193 4 2 2 Upgrading CCIS between FUG and IVS System to Enhanced CCIS Network 195 4 2 3 Upgrading CCIS Network including IVS System to EX FCCS Network 196 TABLE OF CONTENTS ND 70185 E Page iv Revision 3 0 LIST FIGURES Figure Title Page Figure 2 1 dob ve Lee a d
133. e same numbering plan data after introducing the Fusion system Note maximum of 16 digits can be used as aTelephone Number Telephone Number can be assigned to a station using the LENs or by the Physical Station Number depending on the programming as shown below When using LENs CO 2000 LA STN 2000 ES LENS 000010 EZ aV LENS 000010 LENS 000010 410000 LENS gt Telephone Number 410000 When using Physical Station Number c 2000 STN 2000 TENS 000010 LENS 000010 522 222 STN 2000 410000 Physical Staion Number Telephone Number 410000 Note For more information see Assignment of Telephone Numbers in this manual Fusion features are activated when a Telephone Number is dialed STN 2000 Telephone Number 410000 Telephone Number 410001 Fusion Network Fusion features 74 are activated A STN 2500 STN Physical Station Number Figure 2 1 Telephone Number ND 70185 E CHAPTER 2 Page 3 Revision 3 0 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 Telephone Number 411111 Telephone 411111 Node A STN 2000 xe Telephone 411111 Node B STN 2000 Fusion Network
134. ection 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 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 UTP 5 CRS CA F When the HUB and are in the same PIM UTP 5 CRS CA O When the HUB and HUB in different PIMs but in the same IMG UTP 5 CRS CA X When the HUB and HUB are in different IMG stacks When using more than two HUB cards also connect the cross cable s for the remaining HUB card s except the HUB for the MAT connection This step is not necessary when your system uses dual LANIs for CPU 0 CPU 1 and FCH is also in a dual configuration Connect the 10 BASE T straight cable s between the HUB and FCH PA FCHA cards Use the following cable which must be provided by the user UTP CTGS5 ST CA F When the HUB are in the same PIM UTP CTGS5 ST CA O When the HUB and are in different PIMs but in the same IMG UTP CTGS5 ST CA X When the HUB and in different IMG stacks When is in a dual configuration connect FCH 0 to the HUB 0 side and FCH 1 to HUB 1 side Procedure for IMX U System When your system is the IMX U type configured to a maximum of 4 Local Nodes 1ISW the pro cedure for the 10 BASE T connection is as follows Because this system already
135. ed DTI _ D ch External d Logical Route Number Non Fusion DAT wipes 2 LCR Figure 5 10 Telephone Number Required This figure shows an example data assignment of this Logical Route data Data Assignment at NCN Node A LGRT 100 FPC 1 RT 2 COT LGRT 101 FPC 1 RT 27 DAT COT RT3 DAT RT 23 Node B LGRT 200 FPC 11 RT 25 COT LGRT 201 FPC 11 RT 15 TLT LGRT 202 11 7 DAT TLT 15 COT RT 25 FPC 12 Node C LGRT 300 FPC 12 RT 3 LGRT 301 FPC 12 RT 23 DAT DAT RT 7 Node D LGRT 400 FPC 13 RT 255 LCR LGRT 401 13 1 DAT DAT RT 1 LCR 255 COT RT2 FPC 13 Figure 5 11 Assignment of Logical Route Number CHAPTER 5 ND 70185 E Page 66 Revision 3 0 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 FPC RT LGRT Logical Route Number 1 899 WRT RT External Route Number 1 899 Maximum Y Figure 5 12 ALRTN Command Display 5 Assignment of Numbering Data for
136. eee HW Highway Block HWO HW1 HW2HW3 HW5 HW6 HW7 HW8 HW9 HW11 HW4 HW10 indicates basic LENS data Figure 5 59 Basic LENS Data Assignment of Speech Channels AFIP STEP 10 ASYD Assign the data for nailed down connection between FCH and FGH cards SYS 1 Index 60 b4 1 Nailed down connection In service STEP 11 AFCD Assign the detailed nailed down connection data LENS A Assign the LENS data of FCH card EAD A Assign 0 LENS B Assign the LENS data of FGH card EAD B Assign 0 Note Assign all the data for FCH FGH LENS LVO LV7 CHAPTER 5 ND 70185 E Page 110 Revision 3 0 DATA 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 e This feature may be activated when the Fusion trunks are all busy or FCCS Link Failure Layer 2 down occurs at the FCH card e This feature is available when the called party is an analog station D or ISDN terminal When the called party is wireless terminal or DAT Paging Trunk the feature is not activated e Use LCR LCRS for this feature The access code of this feature ACC max 24 digits is assigned by the AFRFL command When the selected non Fusion trunks LCR LCRS a
137. eferred 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 The Telephone Number data in a Fusion Network can be moved to another different Fusion Network by a simple command operation from the sole Centralized MAT in multiple Fusion Networks connected through EX FCCS link or Enhanced CCIS link See Centralized Maintenance Centralized MAT for FCCS for explanation of the Centralized MAT Centralized Maintenance Centralized MAT for EX FCCS See Section 3 2 Centralized MAT for EX FCCS nodes NEAX2400 IMX system in the multiple Fusion Networks and NEAX2000 IVS systems con nected through Enhanced CCIS link can be maintained from one MAT The MAT used for Centralized Maintenance is called as Centralized MAT for EX FCCS Inter network service equivalent to CCIS features For details of CCIS features activated through EX FCCS networks and Enhanced CCIS networks see 3 3 CCIS Features Activated with EX FCCS For the basic operation or the data programming for NEAX2000 IVS see other manuals specified the 2000 IVS system ND 70185 E CHAPTER 8 Page 169 Revision 3 0 5 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
138. en a station activates this feature CFT in Self Node is used In this case CFT in Node A is used 3 5 FCCS Alternate Routing Test This section explains how to perform the test for Fusion link alternate routing Following the procedures below make sure that the connection and alternate routing to all FCCS lines are normal and correctly es tablished CHAPTER 6 ND 70185 E Page 142 Revision 3 0 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 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 STEP 6 Make idle all the trunks which were placed in make busy state in STEP 1 3 5 2 Alternate Route Trunk Test STEP 1 Using the MBCT command make busy all trunks in the primary route STEP 2 Using the MBCT command make busy all trunks in the alternate route except the trunk to be tested STEP3 Liftthe handset of STN A STEP 4 Dial the Telephone Number of STN B STEP 5 Confirm the speech condition is sufficient no noise not one way speech etc STEP 6 Replace the handset of STN STEP 7 STNA TELN 410000 STN 2000
139. eration In addition when the FCH of the adjacent node becomes inoperative this message is displayed 1 XxOx 0000 0000 0000 2 0000 0000 0000 0000 3 0000 b7 50 FE Circuit Number of FCH 0 7 p ie nee CKT No FCH Mounting Location Pel ea U G MG Module Group U Unit 0 3 FCH Mounting Location i G Group 00 23 Figure 7 24 23 W FCCH Alternate Routing Start Notification 11 23 X FCH Alternate Routing End Notification This message is displayed when an inoperative FCH card of self Node resumes its operation Therefore when the card is placed in make idle status by MNT 3 switch operation this message is also displayed 1 xxOx 0000 0000 0000 2 0000 0000 0000 0000 3 0000 57 50 Circuit Number of FCH 0 7 bo FCH Mounting Location MG Module Group 20 Unit 0 3 FCH Mounting Location Group 00 23 Figure 7 25 23 FCCH Alternate Routing End Notification ND 70185 E CHAPTER 7 Page 167 Revision 3 0 This page is for your notes CHAPTER 7 ND 70185 E Page 168 Revision 3 0 CHAPTER8 5 1 This feature provides the following functions they are activated when connecting multiple Fusion networks a NEAX2000 IVS system to a Fusion Network using the Enhanced CCIS feature The network connected by EX FCCS function is r
140. es contained in each cable unit are as follows SR1201 ETIF CAU B UTP CTG5 ST CA K UTP CTG5 ST CA J SR1201 ETIF CAU DB UTP CTG5 ST CA I UTP CTG5 ST CA J UTP CTG5 CRS CA F Note 2 The cables cited in Figure 4 14 can be used in the 1 system only Refer to Page 45 through Page 48 for more details HUB PA M96 FCH PA FCHA Bg BU OA lt FCH in PIM1 Pattern 1 gt lt FCH Pattern 2 gt Use 10 BASE T connectors o B S 7 8 Wio 5 Bre B T 3 3 x 1 EL ERONT VIEW RMS FANU UTP CTG5 ST PIM 1 PIM 1 5 ST PMO PIMO 1 CTG5 CRS 010203040506 i i 1 BSCM BSCM ST UTP CTGS ST CA J 0110210304081 y UTP CTG5 ST CA J i BASEU BASEU Figure 4 14 Examples of Ethernet Cable Connection FCH in PIM1 1 IMG System ND 70185 E CHAPTER
141. es from the card Extract the HUB card from the slot Set key settings on the new HUB card Turn ON the MB key on the new HUB card Mount the new HUB card in the slot 0 Turn OFF the MB key on the card JL 1L JE IL E i Qa DTI PA 24DTR HUB PA M96 Sate Senstive Handling HUB PA M96 Precautions Required N When this MB key is set in up position Make busy all 10 BASE T interfaces connected to this card become inoperative to LANI PZ PC19 HUB HUB MB 4 p 1 B OPE Anti static Kit 10 BASE T MB key operation 10 BASE T Cable Disconnection WARNING CHAPTER 7 Page 158 Revision 3 0 Figure 7 14 How to Replace HUB PA M96 Card When a HUB card is placed in make busy all BASE T interfaces connected to the HUB card become inoperative ND 70185 E 8 23 T FCH Fault Notification Recovery TROUBLESHOOTING 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 MG 1 xx0x 00 0000 0000 2 0000 0000 0000 0000 T FLTINF FCH CKT No vee U G FCH Mounting Location Note FLTIN
142. et ae Parade 7 D Fusion Network sirara SER 8 7 Tandem Connections via Fusion LINK si Eur RR Exe RE C ERR eee 10 GHAPTERS SYSTEM CONFIGURATION s xoa donem tome xm exem un 11 NET Ee iae TE 11 2 busonoystem WH POR 52285 ees Ned eR M XE d 12 2 1 e dn us od oes ap o ed Guo dicar aca boc deca laud ea BOR 12 2 2 Redundancy or Fusion LINK uus sas 12 3 NOI SII DOS cuu db 14 3 1 Fusion Network Comming causae Eee wee X Weed I EN Ress 14 3 2 Centralized Billing Fusion Polling 18 3 3 Centralized Management 21 3 4 Fusion Attendant Desk Console 2 ioca edo CR RC od 25 241 Operar Callin Ene Goede Ree ew MP e 25 3 42 Central Office Incoming Call Ring Down 26 wae IpEBIIDS PPP URP 27 INSTALLATION x pedubpEWPLese4e d Pedo bm ee LESEN RE 29 AN MMC TII MP ea
143. for node accommodating an external key box by External Key Box External Key Box Fusion System without ATTCON DESKCON O Day mode Night mode Figure 3 20 Day Night Information Transfer ND 70185 E CHAPTER 3 Page 27 Revision 3 0 This page is for your notes CHAPTER 3 ND 70185 E Page 28 Revision 3 0 CHAPTER 4 INSTALLATION This chapter covers the installation of the Fusion system The following topics are covered e How to set switches on the following circuit cards PA M96 HUB PA FCHA FCH PA 24DTR DTI e How to mount the circuit cards e How torun 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 Figure 4 1 shows the Static Caution indicator ATTENTION Contents Static Sensitive andling Precautions Required Figure 4 1 Static Caution Indicator ND 70185 E CHAPTER 4 Page 29 Revision 3 0 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 NN Conductive Sheet Wrist Strap N Cable Figure 4 2 How to Use the Anti static Ki
144. g FCH card in PIM3 UTP 5 ST CA N e When adding HUB card in PIM3 UTP CTG5 CRS CA N Note The cables cited above and used in Figure 4 13 through Figure 4 15 are for the 1 IMG system only not available the 4 IMG IMX U system ND 70185 E CHAPTER 4 Page 45 Revision 3 0 INSTALLATION Connecting Cab les 4 3 3 When not using the cable unit SR1201 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 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 When a single LANI is used for each CPR Slot 00 only and the HUB is in a dual configuration connect HUB 0 to LANI 0 HUB 1 to LANI 1 using two 10 BASE T cables When dual LANIs are used in both Slot 00 and 03 of CPR 0 CPR 1 use at least two HUB cards as separate 10 BASE T connection terminals One HUB for the internal LANI LANI A in Slot 00 Of each CPR and the other for the external LANI LANI B in Slot 03 of each CPR The external LANI is available for Series 7300 Release 3 software or later When HUB is in a dual configuration connect the 10 BASE T cross cable between the HUB cards Use the cable UTP CTG5 CRS which must be provided by the user When using more than two HUB cards connect the cross cable s for the
145. ge 72 Revision 3 0 Table 5 1 Route Class Data Assignment Node A Node B B channel D channel B channel D channel C RT 10 C RT 11 C RT 12 C RT 13 DATA PROGRAMMING Assignment of Telephone Numbers Description Trunk Kind 3 Bothway fixed Trunk Class 4 fixed Release Method Assign 2 First Party Release 3 3 3 3 4 4 4 4 2 2 2 2 Assign 0 B ch 12 D ch 13 0 0 0 0 12 12 0 FIFO 1 LIFO Fusion Interface Kind Assign 0 Fusion Trunk Peg Count Assign 0 Timer Class Timer Counter Status Enquiry 0 0 1 cancel Assign 0 CHAPTER 5 Page 73 Revision 3 0 ND 70185 E DATA Assignment of Telephone Numbers CDN 1 CDN 2 CDN 3 CDN 4 CDN 5 CDN 6 Trunk Kind 0 2 3 Bothway Trunk TCL Trunk Class 0 3 4 Fusion Trunk 5 31 RLP Release Pattern 0 Calling Party Release 1 2 First Party Release 3 SMDR SMDR for station to station call Assign 0 LSG Line Signal 12 B channel for No 7 CCIS ISDN 13 D channel for No 7 CCIS ISDN PAD Note 0 Depending Key Setting of Circuit Card 1 Send 8 dB Receive 0 dB 2 Send 4 dB Receive 4 dB 3 Send 8 dB Receive 12 dB 4 Send 8 dB Receive 8 dB 5 6 7 0 dB Note When PAD data is assigned by AFPD command AFPD data takes precedence over this data For more in formation o
146. gnaling Link Failure Permanent Temporary Recovery 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 self Node other Node D channel example TSW INT cho E ch 23 TSW INT MUX B MUX B A A 3A Fusonlink y B channel D channel D I 10BaseT x 10 Base T i HUB HUB PciBus 10 10 t LANI i M MEE i SEE PCI Bus LANI 13 H TSW Time Division Switch PH SW 10 HUB PA M96 MUX PH PC36 LANI LAN Interface PZ PC19 FCH Fusion Call Control Handler PA FCHA DTI Digital Trunk Interface PA 24DTR Signaling Link Failure 1 0001 0000 0000 0000 2 0000 0000 0000 0000 Figure 7 8 Fusion Link Signaling Link Failure 1 xx0x 0000 0000 0000 2 0000 0000 0000 0000 Circuit Number of FCH 0 7 zt FCH CKT No FCH Mounting Location MG Module Group i
147. gnment Image 101 sample Data Assignment 102 How to Assign Destination IP Next IP issuance mre EGER RERO RARE RT 3E 102 Sample Data Assignment 103 FCCS Networking over Overview 1 104 Hardware Connections for FCCS Networking 104 ND 70185 E LIST FIGURES CONTINUED Figure Title Page Figure 5 51 Sample Data Assignment 105 Figure 5 52 Sample Data Assignment ACMA re usua ae ka RO Re ee 105 Figure 5 53 Assignment of FCHN Example 106 Figure 5 54 Sample Data Assignment 107 Figure 5 55 How to Assign Destination and Next IP isis earr dass 107 Figure 5 56 Sample Data Assignment eruere RR XA 108 Figure 5 57 Sample Data Assignment 108 Figure 5 58 Sample Data Assignment 109 Figure 5 59 Basic LENS Data Assignment of Speech Channels AFIP 110 Figure 6 1 Fusion REP rer 133 Figure 6 2 LED Indi
148. he NEAX2000 I vs system several commands are required for assignment For details see related NEAX2000 IVS manuals Note 2 When logging in to the node other than the NCN of the Center FUG LN in Center FUG or LN NCN in other FUGs only reading out the AELGN command data is available Note 3 Jf the center FUG group is not 0 FUG is assigned to another group AELGN command data assignment is available for the node to be logged in only Service Conditions 1 Aclosed numbering network is recommended for numbering plan of the EX FCCS network 2 Only Telephone Number max 8 digits is allowed for the extension number used in an EX FCCS network ND 70185 E CHAPTER 8 Page 175 Revision 3 0 EX FCCS EX FCCS Features 3 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 EX FCCS 2 2 2 Enhanced Fusion Group FUG Figure 8 5 Patterns of Number Portability Table 8 2 Patterns of Number Portability PATTERN Telephone Number is moved from A to B Moving a number within the same FUG NCN in Center FUG Moving a number in an FUG to another FUG NCN in Center FUG Moving a number in a FUG to a NEAX2000 IVS NCN in Center FUG NEAX2000 IVS Note 1 Adding a new number to an FUG NCN in Center FUG NEAX2000 IVS Note 2 Moving a number in NEAX2000 IVS to an FUG N
149. he self Point Code CCIS when requiring to send billing information for polling from Node A Fusion Center Node i Fusion Network polling ignores SMDR equipment Example 6 Node A collects the billing information of Node B and Node C via FCCS using polling method Node A sends the billing information of Node A Node B and Node C to Node D i Fusion Center Node CCIS Center Node Fusion Network FCCS polling Billing Information of Nodes A B C Billing Informatig Figure 3 12 Centralized Billing Fusion 2 3 ND 70185 E CHAPTER 3 Page 19 Revision 3 0 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 Fusion Network polling sss i Billing Information of Node CCIS Example 8 Node collects the billing information of Node B Node C and Node D which are stored in Node B and Node C by polling method Node D sends billing information to Node B non IMX Billing Information Billing Information i DPCO of Node B of Node D i Node B CCIS am Node D DPC
150. ialing EX FCCS Telephone Number here Reexamine the assigned data if the call cannot be connected There may be some error in data setting so far Note 2 Refer to the service feature manual for NEAX2000 I vs system as to the data programming on NEAX2000 IVS side 42 3 Upgrading CCIS Network including IVS System to EX FCCS Network IVS System gt 2 Enhanced CCIS UG1 IVS System CHAPTER 8 ND 70185 E Page 196 Revision 3 0 5 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 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 Assign the following data at all the NCNs that is all the IMX systems of each node within the EX FCCS Network STEP 1 AFUGN Assign EX FCCS Fusion Group data such as Self FUG Number and connection FUG Number des ignating Fusion Point Code of the NCN within FUG Assign one of the IMX systems as the Center Fusion Group by clicking the check box in the CENTER parameter 5 2 Assign the CCH Selection Data by designating all the Fusion Point Code
151. in dual configuration the 10 BASE T cross connection between the HUBs is not required Figure 4 15 Examples of Ethernet Cable Connection FCH in PIM2 1 IMG System 2 2 ND 70185 E CHAPTER 4 Page 53 Revision 3 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 PIMG of 1 IMG system under the following conditions Configuration Configuration Used Cable Unit Number of HUB of CPU of LAN Note 1 Note 2 FCH Pattern 1 SR1201 ETIF CAU D x 1 HUBx 1 FCHx 1 SR1201 ETIF CAU D x 1 SR1201 ETIF CAU DD x 1 Pattern 3 SR1201 ETIF CAU D x 2 HUBx 2 FCHx 2 Pattern 4 Dual Dual SR1201 CAU D x 2 SR1201 CAU DD x 2 Pattern 2 HUBx 2 FCHx 2 HUBx 2 FCHx 2 Note 1 Cables contained in each cable unit are as follows SRI201 CAU D CTG5 ST CA N UTP CTG5 ST CA J SRI201 ETIF CAU DD UTP CTG5 ST CA L UTP CTG5 ST CA J UTP CTG5 CRS CA F Note 2 The cables cited in Figure 4 16 can be used in the 1 system only Refer to Page 45 through Page 48 for more details HUB PA M96 FCH PA FCHA EJ 10 BASE T Connector Use 10 BASE T connectors FCH in PIMS Pattern 1 gt lt FCH in PIMS Pattern 2 gt TOPU HOBASET UTP CTG5 ST CA L PIM 3 PIM 3 1 3SY8 01 20 10 0
152. ion Network Network configuration of the NEAX2400 IMX to NEAX2400 IMX connection is as follows In this Fusion Network NDM a is used VETUS A LGRT899 Fusion Network B LGRT200 FPC1 FPC2 NCN FPC3 4 LGRT4 GRT3 LGRT1 2 LGRT3A Fusion Network C Sw In this Fusion Network 2 b is used FPC1 LGRT100 FPC2 NCN FCCS FPC3 4 LGRT899 EX FCCS In this Fusion Network gt NDM is used Fusion Group FUG Figure 8 3 2400 IMX to NEAX2400 IMX Connection CHAPTER 8 ND 70185 E Page 172 Revision 3 0 5 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 This is the sole node allowed to assign or delete Telephone Numbers within the self FUG and the other FUG l An EX FCCS network may consist of FUGs connected via EX FCCS and NEAX2000 IVS Sys tems connected via Enhanced CCIS All FUGs must be connected to the Center FUG within a range of 1 or 2 EX FCCs links or 1 or 2 Enhanced CCIS links from
153. ion Trunk use the MBCT command to make busy trunks which are not being tested This command leaves the Fusion trunk to be tested in an idle state 1 How to Check Fusion Link by LEDs on FCH Card Before performing the Fusion link test be sure to check the Fusion Link LEDs Refer to Figure 6 2 When the Fusion link is established the LYR lamp lights green on the FCH PA FCHA circuit card However if it re mains off the layer 2 Link Layer is not established If this is the case follow the repair procedure listed here ND 70185 E CHAPTER 6 Page 133 Revision 3 0 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 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 If any abnormal state is detected please see the NEAX2400 IMX Circuit Card Manual _____ FCH PA 24DTR LED Indication A Remains ON LYR when Fusion Link is established EST3 Send pes k N
154. it 0 3 G Group 00 23 FCH Mounting Location Figure 7 2 3 B PM C level Infinite Loop Permanent 2 1 Repair Procedure STEP 1 Initialize the indicated card using the MB key MB key Down Up gt Down When the LED on the FCH card lights green and the related system messages are not displayed mon itor the system for a while Otherwise move to STEP 2 Flip the MB key as follows to initialize the FCH card EN mw LAN FCH PA FCHA LED is OFF GREEN zw Per ons Required MB MB Anti static Kit FRONT VIEW Figure 7 3 How to Initialize the FCH PA FCHA Card STEP 2 Replace the card following the procedure listed in Figure 7 4 How to Replace the FCH PA FCHA card ND 70185 E CHAPTER 7 Page 149 Revision 3 0 TROUBLESHOOTING 3 B PM C level Infinite Loop Permanent is displayed MNT 3 922 is displayed DTI How to Replace FCH card 1 Provide the anti static kit 4 Turn the MB key upward make busy 6 Extract the FCH card from the slot 7 Set key settings on the new FCH card 10 Mount the new FCH card in the same slot 12 Turn the MB key downward 13 Turn OFF the MNT 3 switch make idle 5
155. k points l Internal Loopback ND 70185 E CHAPTER 6 Page 135 Revision 3 0 POST INSTALLATION TEST Repair Procedure When LED Indicates Abnormality AII 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 D in the figure below 2 Line Loopback 24 B channels sent from the line are looped back to the line at Line Interface on the card See Q in the figure below 3 Payload Loopback 24 B channels sent from the line are looped back to the line at Speech Path Control Block on the card See in the figure below Self Node External loopback 3 Payload Other Node Loopback Line Loopback loopback DTI pkg 2 i 00 o vl mE PI FUSION LEH HEL HE 3 slla BME Network ah shes ere front cable Analysis Method RISE ES ASSENS 1 FCH card i Result of gt Self Node has errors Sending Test i Result of gt NG Line has errors Datairattern Result of gt OK 2 OK 9 NG Other Node has errors Figure 6 4 Loopback Points of DTI Card CHAPTER 6 ND 70185 E Page 136 Revision 3 0 POST INSTALLATION TEST Repair Procedure When
156. ment Image Example ND 70185 E CH APTER 5 Page 101 Revision 3 0 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 zuse 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 Example data assignment is shown in Figure 5 46 and Figure 5 47 USE GATE FPC USE GATE 0001004 FCH Number pem wore 7 A maximum of 8 routings are available FCHN 1 FCH Number NEXT IP bbb bbb bbb b Figure 5 46 Sample Data Assignment AETH destintaion information embedded in the packet Internet OM Intranet CCC CCC CCC C NEXT IP DST IP bbb bbb bbb b DST Routen Router outer FGH FGH bbb bbb bbb b Destination Node does not change Address of Node to be passed to DST IP NEXT IP ud Destination IP Next IP Figure 5 47 How to Assign Destination IP and Next IP CHAPTER 5 ND 70185 E Page 102 Revision 3 0 STEP 7 DATA PROGRAMMING Assignment of FCH Related Data Assign
157. mming Node D Ring Down Call Ring Down ASYDL Node Index 640 FPC 3 Node C 4 QD Node having self node FPC Node w o ATTCON Data Programming Node C Figure 3 18 Ring Down Calls on a Fusion Network CHAPTER 3 ND 70185 E Page 26 Revision 3 0 SYSTEM CONFIGURATION System Considerations 3 4 8 Day Night Change Day Night information is transferred from an ATTCON DESKCON to predetermined nodes In this example Node C specifies Node 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 Note 1 When assigning ATTCON DESKCON on the Fusion network be sure to develop the unified System Data at each node Note 2 Terminating node cannot be assigned differently at each tenant TN by ATTCON DESKCON Data Programming Node C ASYDL Node E Fusion System with ATTCON DESKCON ASYDL Node C DEDITUS quu Index 704 735 Index 704 735 D N information are D N information are transferred FPC 4 transferred FPC 1 2 5 Data Programming Node E Q Day mode e Night mode Figure 3 19 Day Night Information Transfer by ATTCON DESKCON When an ATTCON DESKCON is not provided on the Fusion network Day Night information is effective
158. mp Field 0 Out of Service 1 In Service e HE Figure 5 15 ANPDN Command Display Note Perform the Numbering Plan data setting by using ANPD command in the same way as assigned by ANPDN command CHAPTER 5 ND 70185 E Page 68 Revision 3 0 DATA PROGRAMMING Assignment of Numbering Data for Telephone Numbers STEP3 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 NCN Node A SRV Kind of Service Telephone Number TELN Telephone Number AXXXXX 1 4 SRV TELN NND 6 6 digits TN 1 ACC 4 Cl H Hooking SRV TELN NND 6 Figure 5 16 ASPAN Sample Data Sheet ACC Access Code max 6 digits CI Connection Index N Normal ASPAN Assignment of Special Access Code Data for Network Data Memory TN 1st DC CI H Hooking ER B Busy SRV Kind of Service Note a TELN Teleph Numb Telephone Number 6 NND Maximum Number of Digits 1 16 digits Note Available SRV is Telephone Number only For more information see the Office Data Specification Figure 5 17 ASPAN Command Display Note Numbering Plan data for the LDM and or NDM cannot use separate Tenant Numbers TN Therefore be sure to assig
159. n AFPD command see the Office Data Specification CDN 7 CDN 8 CDN 9 CHAPTER 5 Page 74 Revision 3 0 TRKS Trunk Select 0 FIFO 1 LIFO TC EC 0 No MPC EC 1 2 MPC 3 FINT Fusion Interface Kind 0 Fusion 1 15 Not used ND 70185 E CDN 10 CDN 11 CDN 12 CDN 13 CDN 14 CDN 15 CDN 16 CDN 17 DATA PROGRAMMING Assignment of Telephone Numbers FPEG Fusion Trunk Peg Count Assign 0 TC Timer Class 0 1 1 sec 2 2 3 8 sec 4 20 sec 5 7 Miscellaneous Timer Counter STSEQ Status Enquiry 0 1 cancel FGH Fusion Gateway Handler Assign 0 MMN Kind of Multiple Equipment 0 TDM 1 MM Node 2 3 Fusion Link 0 via DTI 1 via ISW 2 Fusion over IP Router 3 15 Not used IPLYR Voice over IP 0 DTI interface 1 5 Mbps 1 DTI interface 2 0 Mbps ND 70185 E CHAPTER 5 Page 75 Revision 3 0 DATA PROGRAMMING Assignment of Telephone Numbers STEP2 ACTK Assign the connection trunk data of both B channel and D channel using the ACTK command As sign the Connection Equipment Number LENS referring to Figure 5 22 through Figure 5 25 The ACTK command display should look similar to the following RT Connection Route 1 1023 TK Connection Trunk 1 4095 LENS Connection Line Equipment Numbers ACTK Assignment of Connection Trunk Data for Local Data Memory C RT C TK
160. n the Fusion system is configured for the first time or the system is once initialized at the NCN Figure 2 7 Network Data Memory ND 70185 E CHAPTER 2 Page 7 Revision 3 0 GENERAL Fusion Network Examples When the NDM master is modified the new data is automatically copied NCN LN LN 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 NON Network Control Node LN Local Node Figure 2 8 Network Data Memory Copy 6 Fusion Network Examples Figure 2 9 and Figure 2 10 show examples of Fusion networks When incorporating the Fusion system with the existing CCIS network all nodes must be connected via CCIS links Note To connect a CCIS network and Fusion network use STNs and TELNs respectively 3xxx CCIS for Node C 2xxx CCIS for Node B Closed Numbering 2 CCIS 4xxxxx FUSION access bio 5xxx CCIS access for CCIS Network o NCN Node A FPC 1 LN Peale Node B FPC 2 TELN a TELN TELN 11 220000 5 zT 410000 410001 ES 88821 88851 ESAN STN 2000 STN 1000 STN 1001 STN Physical Station Number Telephone Number FPC Fusion Point Code Point Code CCIS Figure 2 9 Closed Numbering Fusion CCIS Network CHAPTER 2 ND 70185 E Page 8 Revision 3 0 GENERAL Fusion Network Examples 81
161. n the following data on the ASYDL command e ASYDL command SYSI INDEX 800 I ASPAL command tenant data table development on LDM Common b2 I ANPDL command tenant data table development on LDM Common ND 70185 E CHAPTER 5 Page 69 Revision 3 0 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 Note Fusion Link must be operational before programming telephone numbers in the Fusion Network COMMAND ALGSN ATSTN Assign Telephone Numbers to Physical Station Number Type 2 or to physical LENS Type 1 using the ALGSN ATSTN command An example data sheet Type 2 follows ALGSN Data Sheet example Telephone Number Physical Station Number NCN Node A T Type 2 UGN 1 TELN 410000 FPC 1 TN 1 STN 200 7 Node A Type 2 UGN 1 TELN 410001 1 1 1 STN 2000 Type 2 UGN 1 TELN 420000 FPC 11 TN 1 STN 2000 Node B Type 2 UGN 1 TELN 430000 FPC 12 TN 1 STN 2000 Node C Type 2 UGN 1 TELN 440000 13 TN 1 STN 2000 Node D O O O O O O O O O O O O Note This data is a sample when the Telephone Number is assigned by the ALGSN command Figure 5 18 ALGSN Sample Data Sheet CHAPTER 5 ND 70185 E
162. ode ADC data must be set by AEADN command at each NCN of all the FUGs Assign the EX FCCS Telephone Number data by using AELGN com mand at the NCN of the Center FUG only NCN of each FUG AEADN Assign the Abbreviate Digit Code ADC for connection Fusion Group Enter the FUG Number as signed by AFUGN command TN and ADC to be assigned NCN of the Center FUG AELGN Telephone Numbers must be assigned for all the station within the network uniquely Use AELGN command to allocate EX FCCS Telephone Number FUG data must be assigned previously by AFUGN command to activate this command Only readout function can be used by this command in case both the Self FUG Number and the Con nection FUG Number are assigned if the Self FUG is not the Center FUG Note Check whether the trunk originating call via CCIS can be executed by dialing EX FCCS Telephone Number here Reexamine the assigned data if the call cannot be connected There may be some error in data setting up to now CHAPTER 8 ND 70185 E Page 194 Revision 3 0 5 Data Programming 4 22 Upgrading CCIS between FUG and IVS2 System to Enhanced CCIS Network FUG Center FUG IVS System FCCS Enhanced CCIS PC3 FPC3 PC4 5 5 CCIS E pecs 1 To Log in to All Nodes in EX FCCS Network Assign the f
163. ollowing data at the NCN of FUG with Centralized MAT for Fusion STEP 1 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 Assign the FplUG as the Center by clicking the check box in the CENTER parameter 5 2 Assign the CCH Selection Data by designating all the Fusion Point Code and the Point Code PC in the connected Fusion Group Note Confirm the Centralized MAT can log in to each node here Reexamine the assigned data if log in can not be executed There may be some error in data setting so far ND 70185 E CHAPTER 8 Page 195 Revision 3 0 5 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 as signed by AFUGN command TN and ADC to be assigned STEP2 AELGN Telephone Numbers must be assigned for all the station within the network uniquely Use AELGN command to allocate EX FCCS Telephone Number FUG data must be assigned previously by AFUGN command to activate this command Only readout function can be used by this command in case both the Self FUG Number and the Con nection FUG Number are assigned if the Self FUG is not the Center FUG Note 1 Check whether the trunk originating call via CCIS can be executed by d
164. on Connection Test via FCCS Perform the station to station connection test following the procedure listed below Check 3 1 1 FCCS Call Origination Test STEP 1 Using the MBCT command make busy all trunks in the route except the trunk to be tested STEP 2 Lift the handset of STN A in Node STEP 3 Dial a Telephone Number STN B which belongs to another node CHAPTER 6 ND 70185 E Page 138 Revision 3 0 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 STEP 3 Dial a Telephone Number STN A which belongs to the self node STEP 4 The call terminates on STN A STEP 5 Confirm the speech condition is sufficient no noise not one way speech etc STEP 6 Replace the handset of STN B STEP 7 Repeat the above steps for all Fusion links Node A Self Node Node B 420000 RINGING O 5 STN B TELN 410000 TELN 420000 STN 2000 STN 2000 MBCT Command Busy Information ox 0 Make idle i B ch busy NEZ
165. on PA SDTA Card ND 70185 E CHAPTER 6 Page 145 Revision 3 0 POST INSTALLATION TEST SDT Card LoopbackTest STEP 2 Make sure that the LPB lamp on the PA SDTA card or SYCxx lamp on the PA SDTB card lights steady green STEP 2 5 When the loopback pattern is local loopback confirm that the and SYNC lamps are both OFF on the PA SDTA card and SYNC lamps are OFF Result of loopback test is fine STEP3 Return the key settings of the P SW key on PA SDTA card see Figure 6 15 to the original position CHAPTER 6 ND 70185 E Page 146 Revision 3 0 CHAPTER7 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 z e System Message Remarks PM C level Infinite Loop Permanent PM C level Infinite Loop Temporary PM Lockup Failure Permanent PM Lockup Failure Temporary Signaling Link Failure Permanent Signaling Link Failure Temporary Signaling Link Failure Recovery FCH Failure Notification Detection 1 2 3 4 5 6 7 8 9 FCH
166. ondition 3 available connection route number ranges from 1 to 1023 Condition 4 available connection trunk number of each route ranges from 1 to 4095 maximum of 4095 ports can be assigned on a t connection route basis between nodes D Zn D ch Data Link KOR d Bch Connection Trunk Max 4095 trunks per connection route Figure 3 9 Maximum Number of Ports between Nodes ND 70185 E CHAPTER 3 Page 15 Revision 3 0 SYSTEM CONFIGURATION System Considerations Condition 5 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 A Alt C RT3 Alt C_RT4 Node B Alt C_RT1 Alt C_RT2 Alt C_RT8 Alt C_RT Alternate Connection Route Figure 3 10 Connection Trunk Alternate Routing Condition 6 Connection trunks and the Fusion data link must be assigned on an associated basis B ch Connection Trunk D ch Fusion Data Link network on an associated basis network on a quasi associated basis Figure 3 11 Fusion Network on an Associated Basis Condition 7 fusion data link must be assigned on each link Condition 8 maximum of eight 8 data links be used for a connection trunk for redundan
167. ontact 6 If the above procedure does not result in normal operation perform the conductive test of the 10 BASE T cable HUB LANI Cable Connection Test 1 Turn ON the MNTS switch of the 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 3 Turn ON the MB key on the HUB card 4 Unplug and plug the modular connector a few times at each connector since the connection may be a poor contact 5 If the above procedure does not result in normal operation perform the conductive test of the 10 BASE T cable OPE MB modular connector Unplug plug the modular connector Figure 7 13 to Check 10 BASE T Cables WARNING When a HUB card is placed in make busy all BASE T interfaces connected to the HUB card become inoperative ND 70185 E CHAPTER 7 Page 157 Revision 3 0 TROUBLESHOOTING 23 S FCH Failure Notification Detection A 1 Provide anti static kit 2 Turn ON the MNTS switch of the FCH cards which are connected to the HUB card to be replaced 3 Make sure that system message 23 W FCH Alternate Routing start is displayed for the FCH cards Turn ON the MB key on the HUB card make busy Disconnect the 10 BASE T cabl
168. opriate 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 PM C level Infinite Loop Permanent 1 0 0000 0000 0000 2 0000 0000 0000 0000 PM Restart Type 0 1 B monitor Initial Restart Note kd Type E 0 EU Unit 0 3 G Group 00 23 FCH Mounting Location Figure 7 5 3 C PM C level Infinite Loop Temporary Note B monitor Restart Ports whose link has already been established remain connected while ports processing a call origination may be released Initial Restart All ports on the circuit card are force released to be placed in idle state 3 1 Repair Procedure STEP 1 Ifthe 3 C message has been displayed only once or twice monitor the failure for a while Otherwise move to STEP 2 STEP2 Initialize the indicated FCH card using the MB key See Figure 7 3 How to Initialize the FCH PA FCHA card When the LED on the FCH card lights green and the related system messages are not displayed mon itor the system for a while Otherwise move to STEP 3 STEP 3 Replace the FCH card following the procedure listed in Figure 7 4 How to Replace FCH PA FCHA card 4 3 D PM Lockup Failure Permanent The CPU sends diagnosis data at periodic intervals to the Port Microprocessor PM on FCH PA FCHA cards in
169. ork 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 unique NID is assigned to each MG UNIT automatically by entering the AFMU data When the Fusion network is configured for the first time Enter the AFMU command data for all the Fusion network nodes FPCs Then a unique NID is assigned automatically to each MG UNIT in the assigned order When the Fusion network is already configured and a module unit is to be expanded Enter the AFMU command data related to the expanded module unit Then a unique NID number just next to the last existing NID number is automatically assigned to the expanded module unit This figure shows an example data assignment for this particular network PBX Data Assignment at PBX 02 03 1 MG 0 UNIT 0 1 1021031 uo u ij UNIT 1 M FPC 12 ma MG 0 MG 1 UNIT 0 Uo UNIT 1 1 EPC 11 MG 0 UNIT 0 UNIT 1 MAT UNIT 2 UNIT 3 MG 1 UNIT 0 Node B UNIT 1 UNIT 2 UNIT 3 FPC 12 MG 0 UNIT 0 UNIT 1 UNIT 22 UNIT 2 3 Node C
170. ormat method the receiving message field is output as itis When in the IMX MCI format method the originating information field is also outputto Tele phone Number field ND 70185 E CHAPTER 8 Page 183 Revision 3 0 5 EX FCCS Features 3 5 Centralized Billing EX FCCS Polling Method This section explains the conditions of Centralized Billing feature within EX FCCS Network Two methods of administering Centralized Billing information are available either the CCIS billing method or the FCCS billing method When a 7 digit or 8 digit EX FCCS Telephone Number is used in the network for the NEAX2000 IVS system the EX FCCS Telephone Number is output to Station Number field and the Office Code field of the originating party As Telephone Number is not used in ICS text format when 7 or 8 digits Telephone Number is used in the network the number is converted to Office Code and Station Number then the Station Number 15 output to Station Number field of originating party and the Office Code is output to Office Code field of originating party ICS Format Station Number of MONA Originating Party ting Party last 6 digits of first 2 digits Telephone Number of Telephone Number CHAPTER 8 Page 184 Revision 3 0 When the Centralized Billing Office adopts the CCIS billing method receiving message field is output as it is When the Centralized Billing Office adopts the Fusion billing method
171. ote SA actes d Figure 2 2 gi LOCO PTTTTT Figure 2 3 Centralized on Fusion lt 4 2 4 Figure 2 4 Fusion System Configuration with ciis sue eR RR E ERE RS x Figure 2 5 Fusion System Configuration without FOH Figure 2 6 Maximum System ComiQuralion euauceser er Rx EO RR Red Rie Figure 2 7 open Dala MEMO dd Ra WE Tite oe a ppl bees Figure 2 8 Network Data Memory CODY RR mx RR ceded Figure 2 9 Closed Numbering Fusion CCIS Figure 2 10 Open Numbering Fusion CCIS Figure 2 11 Tandem Connections Fusion cus DA Ru CR RE EUR 10 Figure 3 1 Fusion System Configuration without FOH usas saecu RR RR HE 11 Figure 3 2 Fusion System Configuration with 1 12 Figure 3 3 Redundant Configuration LANI FCH and 13 Figure 3 4 Redundant Configuration FCH and 13 Figure 3 5 Redundant Configuration FOH and REG e RR 13 Figure 3 6 Non Redundant
172. r each NCN perform the data setting from STEP 1 through STEP 7 For other Local Nodes the assignment of STEP 5 and STEP 6 is required Just for the NCN of the Center Fusion Group assign EX FCCS Telephone Number data using AELGN com mand NCN LN STEP 1 STEP 2 STEP 3 STEP 4 ANPDN Assign Numbering Plan Data referring to the following example using ANPDN command TN 1 IstDC 8 CEN HH NND 3 BLF 0 ASPAN Assign Special Access Code using the ASPAN command referring to the following example Note that LCR must be selected in the ASPAN command to activate EX FCCS features TN 1 ACC 820 CI NH SRV LCR RT 31 2nd DT 0 AH 0 SUB 0 Note n this example RT31 is dummy route AFRSN Assign NPC Number Pattern Code and OPR Outgoing Route Selection Number for dummy route number AOPRN Assign the routes and in what order these routes will be selected corresponding to the data assigned by AFRSN command ND 70185 E CHAPTER 8 Page 191 Revision 3 0 5 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 det
173. r of MAT to be installed may vary depending on the customer specification one or two MAT can be used to centralize the MAT operation or three or more MATs can be used to separate the MAT operation ND 70185 E CHAPTER 8 Page 177 Revision 3 0 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 2 ForIMX systems logging in to the NCN of each FUG with Centralized MAT activates the feature to collect traffic information Centralized System Management Report 1 This function is controlled by the Centralized MAT for EX FCCS only 2 Centralized MAT for EX FCCS connected to Center Office collects fault information by polling all of the nodes NEAX2400 IMX and NEA X2000 IVS 3 When a fault occurrs at a NEAX2000 IVS system only basic fault information is collected by the Center Office using the polling method To collect more detail information log in to the system where the fault has occurred 4 The buffer for fault information of the NEAX2400 IMX and NEAX2000 IVS systems is separate There are a maximum of 64 buffers per site Therefore the fault that occurrs when the buffer is full can not be stored at the center system The center system sends NACK signal to the system with the faul
174. re 4 2 Haw ta Use the AntestaliG Kib iua cau ORAL SE DA d ac Ren 30 Figure 4 3 CIrpuir Garde for aio cioe ca SE UICE RO RUNG RERO COHEN OR ROGER Pag 31 Figure 4 4 switch Setting on HUB PA M96 Card ua Rara y FREE RE DRE 32 Figure 4 5 Switch Seating on 33 Figure 4 6 Switch Locations on DTI PA 24DTR 35 Figure 4 7 Mounting HUB Card in usu daa qoe RH RR 40 Figure 4 8 Mounino POM Gnd BEDS EP SE xd 41 Figure 4 9 Cormeeting Fron ii ede ree eee a 42 Figure 4 10 FOH Cascade COnebsielisi iius ord cede debet Aereo OR Ar d DER 43 Figure 4 11 Overall 10 BASE T Connections 44 Figure 4 12 Connecting 10 BASE T Cables 48 Figure 4 13 Examples of Ethernet Cable Connection FCH in PIMO 1 IMG System 1 2 49 Figure 4 14 Examples of Ethernet Cable Connection FCH in PIM1 1 IMG 51 Figure 4 15 Examples of Ethernet Cable Connection FCH in PIM2 1 IMG System 1 2 D2 Figure 4 16 Examples of Ethernet Cable Connection FCH PIM3 1 IMG System 1 2 54 Figure 5 1 Bala Programming Flow
175. re also busy route selection is performed according to the LCR LCRS table The same is performed when the selection encounters a Fusion trunk busy again STEP 1 Basic Data Make sure that the following data has been already assigned for the Fusion network Flexible Route Numbering Plan Data LCR LCRS data Station to Station connection data STEP2 AFRFL Assign Flexible Route data tenant number destination node FPC and feature access code by the AFRFL command TN Tenant Number of the Calling Party FPC Fusion Point Code of the destination node ACC Access Code for Flexible Routing to or Tie Line the same number assigned by ASPA command for LCR LCRS ND 70185 E CHAPTER 5 Page 111 Revision 3 0 DATA PROGRAMMING Office Data Sheets 8 Office Data Sheets 8 1 Data Sheet for AFMUPL FUSION POINT CODE MODULE GROUP FPC MG 1 253 0 1 REMARKS CHAPTER 5 ND 70185 E Page 112 Revision 3 0 8 2 Data Sheet for ALRTN LOGICAL ROUTE NUMBER LGRT 1 899 FUSION POINT CODE FPC 1 253 EXTERNAL ROUTE NUMBER RT 1 255 DATA PROGRAMMING Office Data Sheets REMARKS ND 70185 E CHAPTER 5 Page 113 Revision 3 0 DATA Office Data Sheets
176. ressing the CANCEL key Node A Self Node Node B Node C FCCS Non FCCS STNA STNB TELN 410000 TELN 420000 STN 2000 STN 2000 ATTCON Figure 6 13 CCIS FCCS Outgoing Call Test CHAPTER 6 ND 70185 E Page 144 Revision 3 0 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 Self Node 400 4 Local 2 Remote eer Loopback Loopback o SDT PKG Distant Node Ef 518400 SDT PKG 3 5 5 f Diagnosis SUUS Test Result 1 Error detection at self node Test Result 1 OK 2 NG Error detection on optical fiber line or distant node side Figure 6 14 Loopback Points of SDT Card e Test Procedure STEP 1 Designate the loopback test pattern by setting the P SW key on the SDT PA SDTA card see Figure 6 15 Operate switch 1 or 2 of the P SW key to designate the loopback pattern SDT PA SDTA 2 EN N Loopback SW11 SW12 ON Loca Loopback Rig 4 L4 Figure 6 15 Loopback Setting by P SW key
177. rk SW14 4 e 24DTI PA 24DTR switch setting Make sure that the keys are properly set on the card See the NEAX2400 IMX Circuit Card Manual If the Fusion link is not established using this repair procedure perform the Fusion Link Test 2 2 How to Perform the Fusion Link Test 2 2 4 Fusion Link Test Mode Setting To set the FCH card in Fusion Link Test Mode set the Mode Switch to 9 Initialize the FCH card using the MB key When the Mode is 9 the Fusion Link Controller on the FCH card sends a test data pattern When the same pattern is received again the PM activates the LYR LED flashing the LED at 60 INT which means the test result is OK To perform a Fusion link test set the Mode switch to 9 Fusion Link Controller sends test data pattern Note FCH Loopback front cable to DTI card LYR DTI Interface Send Test Receive Test Data Pattern Data Pattern Fusion Link Controller gt LYR LED flashes FCH card 9 Fusion Link Test Mode Testis 8 Standard Setting 9 FRONT VIEW Flow of Test Note Loopback points are set by a DTI card Figure 6 3 Fusion Link Test Mode Note Be sure to initialize the FCH PA FCHA card after changing the setting of the Mode Switch 2 2 2 Loopback Point Designation The DTI card can be set at one of the following loopbac
178. sion Control Handler LANI LAN Interface Figure 2 4 Fusion System Configuration with FCH Figure 2 5 shows a Fusion system without Fusion Call Control Handler FCH cards 10BASE T 10BASE T DTI Digital Trunk Interface LAN Interface Figure 2 5 Fusion System Configuration without FCH ND 70185 E CHAPTER 2 Page 5 Revision 3 0 GENERAL Node 4 Node A Fusion network consists of the following types of nodes Note 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 nodes other than Network Control Node are called Local Node Fault information generated at a Local Node is sent to the Network Control Node via a Fusion Link allowing the Network Control Node to collect the fault information A Fusion network can have a maximum of 16 nodes on the network See Figure 2 6 The actual number of nodes varies with system configurations Center Node for Centralized Billing Fusion This node collects the billing information from other nodes as well as the self node For this reason the node is called Center Node for Centralized Billing Fusion Multiple Center Nodes can be assigned on the network by specifying the polling destinations
179. t CHAPTER 4 ND 70185 E Page 30 Revision 3 0 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 e Fusion with HUB PA M96 FCH PA FCHA DTI PA 24DTR e Fusion without DTI PA 24DTR HUB PA M96 Before starting installation make sure that all necessary cards are at your site DTI PA 24DTR HUB PA M96 E 4 sws 000 sw11 0000200 sw10 00000000 os m SW15 SW14 900 000 pm DTI Digital Trunk Interface FCH Fusion Call Control Handler Figure 4 3 Circuit Cards for Fusion ND 70185 E CHAPTER 4 Page 31 Revision 3 0 INSTALLATION Key Setting on Circuit Cards 2 Key Setting on Circuit Cards 2 1 PA M96 HUB Set the SEL switch on the 96 card s after referring to Figure 4 4 and Table 4 1 6 Contents ANO Static Sensitive HUB Handling ne Required SENSE qe TP7 X TP6 X TP5 X TP4 X 2n TP3 X TP2 X TP1 X TPO X
180. t After a predetermined time the system with the fault attempts to resend the information 5 Table 8 3 shows the controllability of the fault information indication received from the NEAX2000 IVS system 1 alarm indication LED of the TOPU 2 IMX MAT Menu displayed on the MAT 3 DFTD command operation Table 8 3 2000 IVS Fault Information x Controllable Not controllable Connection SMJ SMN Lamp Menu Display DFTD Method on TOPU on MAT command IVS to IMX Enhanced CCIS IMX A to IMX B within an FUG FCCS FUG A to FUG B EX FCCS Note Available when the alarm grade is changed via ALMG command 6 The fault information of the NEAX2000 IVS received at the Center Office is cleared by the RALM RALMN command CHAPTER 8 ND 70185 E Page 178 Revision 3 0 5 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 See Figure 8 6 When collecting the fault information of nodes including the connected 20001 52 at each FUG Example Data FUG A PC1 the node of Centralized Management Report CCIS is 2 NEXT1 3 4 ASYDL SYS1 INDEX532 the CN of Centralized Maintenance Fusion is FPC of NEXT2 NEXT2 ASYDL SYS1 INDEX532 the CN of
181. t data assignment in this table is a typical example Speech Signaling Dummy The other data than above should be set 0 default data STEP3 ATRK Assign the LENs data of the trunks See Figure 8 8 r Reference 1 Reference 2 24CCT is mounted in slot 10 24DTI is mounted in slot 10 Last TS CH is used for CCIS signal CH 2CCH is mounted in slot 9 Last TS CH is used for CCIS signal CH RTx Speech CH RTy Signal CH 24DTI RTx Speech CH RTy Signal CH 2CCH x ATRK 24CCT 911 G15 mmi Signal CH RIyTK Signal CH gt 8 5 a E 9 5 9 614 5 9 9 ATRK o 8 RTx Speech CHs 9 RTx Speech CHs Note 8 9 9 Q G1 G13 G13 9 Q CCH Location 9 9 9 MG U G ME 9 XX X 10 9 912 CCH Location ARKI 5 MG U G 3 ad e RIy TK2 CCH 12 9 e e Rly TK2 CCH sot 9 10 Note Only one CCH CCH 0 CCH 1 can be assigned This example is applicable when 0 is used Slot Figure 8 8 Port Allocation and Related Command for CCIS Trunk ND 70185 E CHAPTER 8 Page 187 Revision 3 0 5 Data Programming STEP 4 Assign IDLE status of trunks
182. ta 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 Network Control Node LN Local Node L coca eens ASYDL Index 513 LDM 01H Index 514 01 ASYDN Index 514 NDM 01H ASYDL Index 513 LDM 01H Index 514 NDM 01H Note ASYDL must be assigned at each node on the network Figure 5 4 Assignment of Memory Block 1 Assign the following data to all nodes e ASYDL Index 513 Local Data Memory LDM usage Assign 1 for bit s corresponding to the data memory block to be used as Local Data Memory LDM Assign 01H for systems having 2M LDM e ASYDL Index 514 Network Data Memory usage Assign 1 for bit s corresponding to the data memory block to be used as Network Data Memory NDM Assign 01H for systems having 2M NDM Allowable memory block of LDM and NDM assigned by ASYD are shown in Figure 5 5 Each bit corresponds to one block having 2M Bytes Relationship between Bit and Block Number block 0 blocks block 0 INDEX 514 blocks INDEX 513 Note These bits are normally assigned as 0 i e 01H is normally set for both INDEX 513 and 514 The flagging of bit s is possible
183. te The odd numbered CSCG for alternate Route assignment 5566 Network Control Node in the example STEP 1 STEP 2 CHAPTER 8 Page 190 Revision 3 0 ALRTN Assign the Logical Route Numbers to all external trunks used in the EX FCCS network Assign unique Logical Route Numbers to the whole routes for external trunks on the network including COT DAT Dummy route etc using this command The data must be set at the NCN in each Fusion Group and is to be set for every external route in all the nodes ARSCN Assign route restriction information according to the Route Restriction Class RSC of the Logical Route Number in the network ND 70185 E STEP 3 STEP 4 EX FCCS Data Programming 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 Assign the EX FCCS CCH Selection Data by designating all the Fusion Point Code and the Point Code PC in the connected Fusion Group Note Confirm whether the data assignment is correctly performed by logging in to each node with Centralized MAT Reexamine the assigned system data if log in can t be activated There may be some error in data setting so far 4 1 2 To Access EX FCCS Trunk via ACC Telephone Number Assign the data at all the nodes in the EX FCCS network Fo
184. ter Node A Node B Figure 5 49 5 Networking over IP Overview The following circuit cards are required for this feature PBX Speech DI T1 H 323 Protocol Internet signaling Intranet 2 L ROUTER E E Q sig 3 11 Q ECH 10 BASE T gs DTI Digital Trunk Interface i Fusion Control Handler Fusion Gateway Handler LANE LAN Interface PZ PC19 I LANI CPU Slot 00 03 Figure 5 50 Hardware Connections for FCCS Networking over IP CHAPTER 5 ND 70185 E Page 104 Revision 3 0 DATA Assignment of Related Data STEP 1 ACRD Assign Route Class Data of Speech Route FCH FGH routes respectively A sample data assignment is shown below PBX speech amp FGH poe i NV ROUTER Q sig 5 1 FCH 3 hol ea o o 0 am e o o o fo o srssa o o to CPU ren o o hsf www fis no 2 o o Note This data setting is an example Figure 5 51 Sample Data Assignment ACRD STEP2 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 sample data assignment of FCH FGH card 15 as follows When FCH and FGH cards
185. termined station ATTCON STEP3 Answer the calls and confirm the speech condition STEP 4 Release the call Node A Self Node Node B ATTCON L 569 L_ Line to be tested 00000 Figure 6 10 Line Connection Test origination via FCCS ND 70185 E CHAPTER 6 Page 141 Revision 3 0 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 STEP3 STN A goes to Switch Hook Flash 5 and after hearing SPDT dials the Telephone Number of STN C in other node Node B STEP 4 STN C answers the call STEP 5 STN after a brief talk with STN C makes a SHF and confirms that a three way connection has been set up STEP 6 Release the call STEP 7 Repeat the above steps for all CFTs STEP 8 Using the MBTK command cancel the make busy status of the trunk SHF TELN 420000 Node A Self Node Node B M M E SINC TELN 420000 STN 2000 RG TELN 410000 STN 2000 TELN 410001 STN 2001 TSW MUX Card Figure 6 11 3 party Conference Trunk Function Test via FCCS Note Wh
186. ternal LANI in Slot 03 However if this is the case and is also in a dual configuration the 10 BASE T cross connection between the HUBs is not required at least two Figure 4 16 Examples of Ethernet Cable Connection FCH in PIM3 1 IMG System 2 2 ND 70185 E CHAPTER 4 Page 55 Revision 3 0 This page is for your notes CHAPTER 4 ND 70185 E Page 56 Revision 3 0 CHAPTER5 DATA PROGRAMMING This chapter explains how to set Fusion Network data using the following data categories e System Data e Numbering Plan Data e Station Data e Fusion Link Data Figure 5 1 shows the overall data programming procedure System Data 2 ASYDL Numbering Plan Data ANPD ANPDL ANPDN ASPA T ASPAN DD 4 7 SSC SSC 55 SSCA SSCA OGC OGC OGC OGCA OGCA OGCA LCR LCR LCR LCRS LCRS LCRS UNIF Note Telephone Number is TELN Note available only in self TENE node TELN Station Number Data Telephone Number Telephone Number Physical Number Y Y l ALGNN ASDT ALGSL ALGSN Fusion Link Data with FCH ACRD gt ACTK MBCT AFCH AFRT gt AFPC
187. the Center FUG In order for an end to end connection to be established no more than 4 EX FCCS or Enhanced CCIS links may be used See Figure 8 4 An example of EX FCCS Network configuration is shown in this figure In this example FUG2 is the Center FUG LEGEND FCCS EX FCCS Enhanced CCIS Fusion Group FUG Figure 8 4 Allowable SPAN from the Center FUG ND 70185 E CHAPTER 8 Page 173 Revision 3 0 5 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 Conditions for OAI ACD Service The OAI ACD service in EX FCCS Network is executed on the same condition in CCIS Network CHAPTER 8 ND 70185 E Page 174 Revision 3 0 5 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 Note 1 AELGN command is used to operate Number Portability forTelephone Numbers used in NEAX2400 IMX systems For t
188. tion ACAN 2 Mount FCH FGH cards Then connect the DTI and ES q cards respectively by using the front cable 3 Connect two LANI cards and HUB cards respectively a DTI Digital Trunk Interface i Fusion Control Handler LANI slot 00 03 FGH Fusion Gateway Handler PA FCHA LANI LAN Interface PZ PC19 Figure 5 40 Hardware Connections for External Router ND 70185 E CHAPTER 5 Page 97 Revision 3 0 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 PBX DTI Sample Data Assignment DID D ERES 13 3 RT14 Internal LAN CPU LANI ote This data setting is an example Figure 5 41 Connection Route Class Data Sample CHAPTER 5 ND 70185 E Page 98 Revision 3 0 DATA PROGRAMMING Assignment of FCH Related Data STEP2 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 sample data assignment of FCH FGH card is as follows
189. tion of each node perform necessary data programming as follows lt Node which accommodates CCIS Trunk PC3 in the example gt STEP 1 ASYD Assign the Point Code for all the Nodes in the network uniquely Since Point Code is used to identify each office in the EX FCCS network any identical PCs are not allowed in the same network Originating Point Code OPC assigned by Indexes 180 and 181 The OPC is a self office code which should be assigned without exception 14 bits can be used for specifying OPC Note that available PC ranges from 1 to 16367 PCs 16368 16383 are used for Loop Back Test FPC3 in FUGI whose OPC is 3 for example should be assigned as follows b5 b4 b2 bi bo b5 b4 b2 bi 0 0 0 01 01 0 1 Index 181 Index 180 Miscellaneous Data Index 186 b6 must be assigned as 1 CCIS is in service The remaining data should be determined depending on custom er s requirements b7 06 b5 b4 b3 b2 bi bo 0 1 0 1 01011 1 4 Example Index 186 CHAPTER 8 ND 70185 E Page 186 Revision 3 0 5 Data Programming STEP2 ARTD Assign the following three routes for this feature e Speech Path Route Traffic Route e Signaling Route Dummy Route Flag Route Assign each route data in accordance with the table shown below Note tha
190. to PNL assigned in the AOPRL command PNL 128 DC 12025678901 ARSCN Using ARSCN assign the Route Restriction Class RSC that allows RRIs for the external trunk route The same route restriction data must be assigned for each node Note 1 The dummy route must be assigned to all nodes including a node which does not have external routes Note 2 When entering the data STEP 1 2 6 7 and 8 do not mix the commands for LDM and NDM Write the data on the same data memory as shown below CHAPTER 5 Page 92 Revision 3 0 When writing the data on the LDM ANPDL ASPAL AFRSL gt AOPRL AADCL STEP 1 STEP 2 STEP 6 STEP 7 STEPS When writing the data on the NDM ANPDN gt ASPAN 5 AFRSN gt AOPRN gt AADCN STEP 1 STEP 2 STEP 6 STEP 7 STEPS ND 70185 E 7 2 Data Assignment for 52M SDH Interface DATA PROGRAMMING Assignment of FCH Related Data 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 7 Fusion EN Node A Node B Optical Fiber Cable FCH Connection Link Data Link Connection Trunk Speech Path eee Optical Fiber Cable For Dual Configuration Internal LAN B Internal L
191. which can be set by the ASYDL command SYS 1 Indexes 608 through 639 At the Center Node the user can select polling destinations by setting 1 to the FPC of the corresponding nodes For more information see the NEAX2400 IMX Office Data Specification A Fusion network can have a maximum of 16 nodes Fusion network N Node Figure 2 6 Maximum System Configuration CHAPTER 2 ND 70185 E Page 6 Revision 3 0 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 e Local Data Memory LDM e Network Data Memory Programmable only by the 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 When Telephone Numbers are changed the change at the will affect all nodes on the network In this figure data change at Node A is automatically transferred to each node Note E 410000 410001 updating NDM at each node NDM master Telephone Number Change 410000 410001 for self Node 420000 420001 for Node B 430000 430001 for Node C 440000 440001 for Node D 09000009900 Note data must be manually transferred using the CBCN command whe
192. x Xx XX XX XX 2 XX XX XX XX XX 3 XX XX XX XX XX XX XX XX 4 XX XX XX XX XX b XX XX XXXX XXXX XXXX XXXX XXXX XX XX T XX XX XX XX XX 8 xx 00 0000 0000 0000 239 0000 0000 0000 0000 50 E ae 53 Bytes IP Header Part 42 Bytes 57 50 IP User Part 11 Bytes l Discarded IP Packet Information b7 50 BEGUN GENE l Transfer Failure Status b7 50 1D FLTINF 1D ETHER Transfer Failure Notification b7 50 r TRC Trace Confirmation Bit 0 1 Status Notification Primitive Trace RS Receive Send Primitive Trace not effective TRC RS L FCHCKT No Circuit No of FCH b7 50 MG 0 Dd G S MG Module Group U Unit 0 3 FCH Mounting Location L G Group 0 23 Figure 7 20 23 U ETHER Transfer Failure CHAPTER 7 ND 70185 E Page 164 Revision 3 0 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 Ox 4 Ex Xx XX Xx 2
193. y Ay Loss Receive uA Loss Bothway uA Loss Receive SEND RECEIVE SEND RECEIVE SEND RECEIVE SEND RECEIVE SEND RECEIVE SEND RECEIVE 2 3 Note 0 0 0 0 0 0 0 4 3 3 4 4 0 4 4 4 0 6 6 6 0 6 6 12 3 9 8 8 0 8 8 8 Key setting of SW 39 3 4 correspond to PAD values Regardless of PAD patterns Note 0 0 Stands for 3 dB GAIN Through Through Through ND 70185 E Through Through Through Through CHAPTER 4 Page 39 Revision 3 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 96 card in an appropriate slot of as shown below When the MAT is con nected via a HUB card be sure to use a dedicated HUB for the Fusion link Note HUB PA M96 be mounted wherever a PIM of any IMG stack However if your system is 1 IMG type mount the HUB in PIMO Mount a HUB card in an appropriate slot providing the anti static kit ATTENTION Contents Static Sensitive Handling Precautions Required ze FK IA Cu 90 cy mU Q SS X x _ a V y val TA VES ac vi al Anti static Kit i um Figure 4 7 Mounting Card in

NEC NEAX2400 Network Cables User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents