DECT CE Manual PDF

AMENDMENTS ................................................................................................2 PREFACE ...........................................................................................................8 1. 1.1. 1.2. 1.3. DECT SYSTEM CHARACTERISTICS .............................................................9 GENERAL DESCRIPTION .........................................................................................
9 RFP-PP COMMUNICATION .................................................................................. 10 BEACON SIGNAL ................................................................................................... 13 1.3.1. General ........................................................................................................ 13 1.3.2. Beacon Signal and PP ................................................................................... 14 CALL HANDLING PROCEDURES BETWEEN PP AND RFP ................................ 14 1.4.1. Setting up a Call ........................................................................................... 14 1.4.2. Paging and Answering a Call ........................................................................ 14 1.4.3. Encryption .................................................................................................... 15 CLUSTER ARRANGEMENT .................................................................................... 15 1.5.1. General ........................................................................................................ 15 1.5.2. RFP Behaviour in a Cluster .......................................................................... 15 1.5.3. PP Behaviour in a Cluster ............................................................................ 15 HANDOVER ............................................................................................................ 16 CALL QUALITY CONTROL ................................................................................... 17 SUBSCRIPTION AND DE-SUBSCRIPTION ........................................................... 18 SECONDARY ACCESS RIGHTS IDENTIFIER (SARI) ............................................. 19 SYSTEM ARCHITECTURE ...................................................................................... 21 1.10.1. General ........................................................................................................ 21 1.10.2. DECT Manager ............................................................................................ 25 1.10.3. BackBone Architecture ................................................................................ 25 SYSTEM CONFIGURATION ................................................................................... 29 1.11.1. General ........................................................................................................ 29 1.11.2. Configuration Rules ...................................................................................... 30 1.11.3. System Expansions ....................................................................................... 30 1.11.4. Maximum System Configuration 24-DCC (old and new) ............................ 31 1.11.5. Maximum System Configuration 32-DCC ................................................... 31 1.11.6. Mixed System Configuration 32-DCC - DCC-8 .......................................... 32 HARDWARE INSTALLATION ......................................................................33 GENERAL ................................................................................................................. 33 2.1.1. General Requirements ................................................................................. 33 2.1.2. Site Requirements ........................................................................................ 33 2.1.3. Visual Check ................................................................................................ 33 2.1.4. Installation Procedures ................................................................................ 33 RFP-DCC Cabling .................................................................................................... 34 INSTALLING THE RFPs WITH DCC-RFP CABLING ............................................. 36
1.4.
1.5.
1.6. 1.7. 1.8. 1.9. 1.10.
1.11.
2. 2.1.
Table of Contents i
2.2. 2.3.
2.4. 2.5. 2.6. 2.7. 3. 3.1. 3.2.
INSTALLING THE DCC AND BBR .........................................................................38 V.24 DECT Manager INTERFACE ...........................................................................43 DSP (DECT SYNCHRONISATION PORT) INTERFACE ........................................45 SYSTEM CLOCK SYNCHRONISATION .................................................................48 PROJECTING DECT IN ISPBX .....................................................................50 GENERAL .................................................................................................................50 PROJECTING IN SSW 300 .......................................................................................50 3.2.1. Projecting Procedures ..................................................................................50 3.2.2. Projecting Example in an iS3030 ..................................................................52 PROJECTING IN SSW 740/800/805 ........................................................................53 3.3.1. Projecting Procedures ..................................................................................53 3.3.2. Projecting Example One Shelf DECT system in a SOPHO iS3050 ..............55 3.3.3. Projecting a DECT system in a PM255 Shelf ................................................56 3.3.4. Projecting a Four Shelf DECT system in a SOPHO iS3050 .........................57 PROJECTING IN Call@Net .....................................................................................60 3.4.1. Projecting Aspects ........................................................................................60 3.4.2. Projecting Procedure ...................................................................................61 EXAMPLE OF ENTERING THE PARI .....................................................................64 IMPORTANT FIRMWARE ISSUES ...............................................................65 MIXED CONFIGURATION ........................................................................... 67 GENERAL .................................................................................................................67 SUPPORTED HARDWARE ......................................................................................67 MINIMUM SOFTWARE REQUIREMENTS ..............................................................67 HARDWARE CONFIGURATIONS ..........................................................................67 HOW TO PROJECT .................................................................................................68 IP PARAMETERS ........................................................................................... 69 SETTING THE IP PARAMETERS .............................................................................69 EXAMPLE OF SETTING PARAMETERS ..................................................................69 DISPLAYING THE IP PARAMETERS .......................................................................70 6.3.1. Displaying IP Parameters (All Firmware Versions) .......................................70 6.3.2. Displaying IP Parameters in Firmware F43240.302 or higher ......................70 EXAMPLE OF DISPLAYING PARAMETERS ............................................................70 DEFAULT IP PARAMETERS .....................................................................................71 HOSTNAME, USERNAME, PASSWORD ................................................................71 CHANGING IP ADDRESS VIA "TELNET" ...............................................................72 USEFUL FUNCTIONALITY ..........................................................................73 CALL FORWARDING ON NOT REACHABLE .......................................................73
3.3.
3.4.
3.5. 4. 5. 5.1. 5.2. 5.3. 5.4. 5.5. 6. 6.1. 6.2. 6.3.
6.4. 6.5. 6.6. 6.7. 7. Table of Contents ii 7.1.
7.2. 7.3.
7.4.
7.5.
TWINNING ............................................................................................................. 73 MESSAGING ............................................................................................................ 74 7.3.1. General ........................................................................................................ 74 7.3.2. Implementing Messaging in SSW 805 Oriented Systems ............................. 74 7.3.3. Implementing Messaging in Call@Net Oriented Systems ........................... 77 7.3.4. Messaging via a CSTA Link .......................................................................... 79 DECT MOBILITY IN iSNET MAN ........................................................................... 80 7.4.1. General ........................................................................................................ 80 7.4.2. Preconditions ............................................................................................... 81 7.4.3. Execution ..................................................................................................... 81 7.4.4. Interaction with other Facilities ................................................................... 82 7.4.5. Implementing DECT Mobility ...................................................................... 83 DECT MOBILITY IN iSNET WAN .......................................................................... 86 7.5.1. General ........................................................................................................ 86 7.5.2. Mixed DPNSS and QSIG Networks ............................................................ 87 7.5.3. Preconditions ............................................................................................... 88 7.5.4. Execution ..................................................................................................... 89 7.5.5. Interactions with other facilities ................................................................... 90 7.5.6. Implementing DECT Mobility ...................................................................... 91 MAKING THE SYSTEM OPERATIONAL .....................................................98 GENERAL ................................................................................................................. 98 STARTING UP THE DCC BOARDS ....................................................................... 98 STARTING UP THE DECT SYSTEM ....................................................................... 99 8.3.1. C-DOS/UNIX Based DECT Manager ......................................................... 99 8.3.2. Windows Based DECT Manager ............................................................... 100 SUBSCRIPTION OF PORTABLE PART ................................................................ 100 8.4.1. General ...................................................................................................... 100 8.4.2. Example of Subscription Procedure (C-DOS/UNIX DECT Man.) ............ 101 8.4.3. Example of Subscription Procedure (Windows DECT Man.) .................... 102 8.4.4. Overwrittting an Existing Subscription in a Portable Part Type C311 ...... 102 8.4.5. Problems During Subscription ................................................................... 104 TESTS ..................................................................................................................... 105 8.5.1. Initial Test Procedure ................................................................................ 105 8.5.2. Trouble Shooting During Initial Tests ........................................................ 105 8.5.3. Testing Handover and RFPs ....................................................................... 106 8.5.4. Trouble Shooting in Handover Test .......................................................... 107 8.5.5. Testing a System with BBR and Backbone Cabling .................................... 107 ALARM REPORTS .................................................................................................. 108 SUBSCRIPTION OF ALL PORTABLE TERMINALS .............................................. 108 MAINTENANCE ..........................................................................................109 Table of Contents iii
8. 8.1. 8.2. 8.3.
8.4.
8.5.
8.6. 8.7. 9.
9.1. 9.2.
9.3.
9.4. 9.5. 9.6. A. B. C. D. D.1. D.2. E. F. G. G.1. G.2. H. H.1. H.2. I.
GENERAL MAINTENANCE ..................................................................................109 THE CLEARANCE OF FAULTS .............................................................................109 9.2.1. Fault Indications ..........................................................................................109 9.2.2. Dead System ..............................................................................................110 9.2.3. User Complaints ........................................................................................110 9.2.4. Alarm Reports/Codes (SSW 300) ...............................................................111 9.2.5. Alarm Reports/Codes (SSW 740/800 and Upwards) .................................112 REPLACEMENT PROCEDURES ............................................................................117 9.3.1. The Portable Terminal ...............................................................................117 9.3.2. The Radio Fixed Part (RFP) ........................................................................118 9.3.3. DECT Cluster Controller (DCC) ...............................................................119 9.3.4. The BackBone Repeater (BBR) ..................................................................120 LED INDICATIONS ON DCC BOARD ................................................................121 RFP LED INDICATIONS ........................................................................................124 DISPLAYING CIRCUITs IN USE ............................................................................125 CABLES ........................................................................................................127 UPGRADE 24 ->32 DCC .............................................................................140 SUPPORTED 32-DCC DECT CONFIGURATIONS .................................. 141 HARDWARE CONFIGURATIONS .............................................................143 BASED ON FIRMWARE F43040.XXX AND F43140.XXX ..................................143 BASED ON FIRMWARE F43240.XXX. .................................................................146 REMOTE CONNECTION FOR SNMP ........................................................148 MORE DECT CLUSTERS IN ONE UNIT ....................................................149 CUSTOMIZING SYSTEM PARAMETERS ................................................. 151 SYSTEM PARAMETERS ..........................................................................................151 SG960X BYTES AND THEIR MEANING ..............................................................151 ENTERING DATA INTO DCC SIGNALLING GROUPS DIRECTLY .........157 SSW 805 ..................................................................................................................158 Call@Net ................................................................................................................160 DIAGRAMS ..................................................................................................164
Table of Contents iv
Business Mobility DECT - Customer Engineer Manual
Release date : 13/Mar/2007
AMENDMENTS
The items that follow are incorporated in the update of this manual from issue 9902 to 0004: CHAPTER/ SECTION All Chapters 3.5. "EXAMPLE OF ENTERING THE PARI" 7.3.1. "General" 7.3.2. "Implementing Messaging in SSW 805 Oriented Systems" DESCRIPTION Minor changes SG9600 bit 1 changed from logic "1" to logic "0" SG9600 bit 1 changed from logic "1" to logic "0" SG9600 bit 1 changed from logic "1" to logic "0"
The items that follow are incorporated in the update of this manual from issue 0004 to 0011: CHAPTER/ SECTION All Chapters 1.3.1. "General" 1.7. "CALL QUALITY CONTROL" 1.8. "SUBSCRIPTION AND DESUBSCRIPTION" 1.9. "SECONDARY ACCESS RIGHTS IDENTIFIER (SARI)" Chapter "Site Survey" 2.2. "RFP-DCC Cabling" 2.3. "INSTALLING THE RFPs WITH DCC-RFP CABLING" 2.4. "INSTALLING THE DCC AND BBR" 2.7. "SYSTEM CLOCK SYNCHRONISATION" DESCRIPTION Minor changes SARI added Completely revised. Completely revised
Section added
Removed. See SiteSurvey Manual Reference to DCC-V4 changed to DCC Minimum distance between RFPs changed
DCC with connection to BBR must be in UG0 CSN-BC clock has same accuracy as PMC clock
CHAPTER/ SECTION 3. "PROJECTING DECT IN ISPBX" 4. "IMPORTANT FIRMWARE ISSUES" 6. "IP PARAMETERS" 7. "USEFUL FUNCTIONALITY" 9. "MAINTENANCE" Appendix "Survey Example" A . "CABLES"
DESCRIPTION Adapted to F4324x.xxx Chapter added Chapter added Aapted to F4324x.xxx Adapted to F4324x.xxx Removed Adapted for Windows DECT Manager
Appendix "Calculating the Removed PARK" D . "HARDWARE CONFIGURATIONS" E . "REMOTE CONNECTION FOR SNMP" F . "MORE DECT CLUSTERS IN ONE UNIT" G . "CUSTOMIZING SYSTEM PARAMETERS" Adapted to F4324x.xxx Added
Added
Added
Added H . "ENTERING DATA INTO DCC SIGNALLING GROUPS DIRECTLY" I . "DIAGRAMS" 12 NCs for DCC-* and BBR-V2 changed
The items that follow are incorporated in the update of this manual from issue 0011 to 0012: CHAPTER/ SECTION 9.5. "RFP LED INDICATIONS" 9.6. "DISPLAYING CIRCUITs IN USE" DESCRIPTION Section added. Section added.
The items that follow are incorporated in the update of this manual from issue 0012 to 0104: CHAPTER/ SECTION All DESCRIPTION "Call@Net" introduced.
The items that follow are incorporated in the update of this manual from issue 0104 to 0108: CHAPTER/ SECTION DESCRIPTION
6.7. "CHANGING IP Section added. ADDRESS VIA "TELNET"" 7.3.2. "Implementing Messaging in SSW 805 Oriented Systems" Alternative destination dialling tree added.
The items that follow are incorporated in the update of this manual from issue 0108 to 0109: CHAPTER/ SECTION 1.10.2. "DECT Manager" 1.11.6. "Mixed System Configuration 32-DCC DCC-8" 2.4. "INSTALLING THE DCC AND BBR" 8.1. "GENERAL" DESCRIPTION Note added. Dect Manager under CDOS or UNIX cannot be used with Call@Net software Section added
Note added for reference to DCC-8 CE Manaual Adapted for starting up procedure for the DCC boards.
8.2. "STARTING UP THE Section added. DCC BOARDS"
CHAPTER/ SECTION 5. "MIXED CONFIGURATION"
DESCRIPTION Section added
G.2. "SG960X BYTES Enable/Disable display time and date (byte 14) added. AND THEIR MEANING" E . "REMOTE CONNECTION FOR SNMP" I . "DIAGRAMS" Old section contents removed. New contents added.
Diagram 300 adapted for mixed configuration, diagram 305 and 306 added.
The items that follow are incorporated in the update of this manual from issue 0109 to 0112: CHAPTER/ SECTION DESCRIPTION
7.4. "DECT MOBILITY IN New section iSNET MAN" H.1. "SSW 805" G . "CUSTOMIZING SYSTEM PARAMETERS" SARI removed In subsection "SARI", line added "Only applicable for Call@Net Software"
The items that follow are incorporated in the update of this manual from issue 0112 to 0204: CHAPTER/ SECTION 2.3. "INSTALLING THE RFPs WITH DCC-RFP CABLING" 7.4. "DECT MOBILITY IN iSNET MAN" DESCRIPTION Note added
Added since Call@Net 2.8
The items that follow are incorporated in the update of this manual from issue 0204 to 0207: CHAPTER/ SECTION 9.5. "RFP LED INDICATIONS" DESCRIPTION RFP type B6xx added.
CHAPTER/ SECTION 7.4.5. "Implementing DECT Mobility" 7.5. "DECT MOBILITY IN iSNET WAN"
DESCRIPTION Minor corrections/changes Added since Call@Net 2.9
The items that follow are incorporated in the update of this manual from issue 0207 to 0210: CHAPTER/ SECTION 7.4.1. "General" 7.5.1. "General" DESCRIPTION Software requirements added. Adapted for QSIG (Call@Net 2.10) and software requirements added.
7.5.2. "Mixed DPNSS and Section added. QSIG Networks" 7.5.3. "Preconditions" 7.5.4. "Execution" 7.5.5. "Interactions with other facilities" 7.5.6. "Implementing DECT Mobility" Adapted for QSIG (Call@Net 2.10) Adapted for QSIG (Call@Net 2.10) Adapted for QSIG (Call@Net 2.10) and Note added. Adapted for QSIG (Call@Net 2.10)
The items that follow are incorporated in the update of this manual from issue 0210 to 0211: CHAPTER/ SECTION 7.4.2. "Preconditions" 7.5.3. "Preconditions" 7.5.6. "Implementing DECT Mobility" DESCRIPTION Preconditions changed Preconditions changed Minor changes. Number analysis for DDI and Alternative destination dialling added.
The items that follow are incorporated in the update of this manual from issue 0211 to 0601: CHAPTER/ SECTION 1.9. "SECONDARY ACCESS RIGHTS IDENTIFIER (SARI)" 2.7. "SYSTEM CLOCK SYNCHRONISATION" DESCRIPTION Although the ISG can be used as digital link to/from other exchange, it does not provide a clock for synchronization. Note for ISG added.
The items that follow are incorporated in the update of this manual from issue 0601 to 0606: CHAPTER/SECTION 6.3. "DISPLAYING THE IP PARAMETERS" DESCRIPTION Two subsections added (OM command DITCPC)
PREFACE
This Customer Engineer Manual is valid for the Digital Enhanced Cordless Telecommunication (DECT) System, issue 1. PRODUCT DISPOSAL INFORMATION (EN) For countries in the European Union The symbol depicted here has been affixed to your product in order to inform you that electrical and electronic products should not be disposed of as municipal waste. Electrical and electronic products including the cables, plugs and accessories should be disposed of separately in order to allow proper treatment, recovery and recycling. These products should be brought to a designated facility where the best available treatment, recovery and recycling techniques is available. Separate disposal has significant advantages: valuable materials can be re-used and it prevents the dispersion of unwanted substances into the municipal waste stream. This contributes to the protection of human health and the environment. Please be informed that a fine may be imposed for illegal disposal of electrical and electronic products via the general municipal waste stream. In order to facilitate separate disposal and environmentally sound recycling arrangements have been made for local collection and recycling. In case your electrical and electronic products need to be disposed of please refer to your supplier or the contractual agreements that your company has made upon acquisition of these products. At www.nec-philips.com/weee you can find information about separate disposal and environmentally sound recycling. For countries outside the European Union Disposal of electrical and electronic products in countries outside the European Union should be done in line with the local regulations. If no arrangement has been made with your supplier, please contact the local authorities for further information.
1.
1.1.
DECT SYSTEM CHARACTERISTICS

GENERAL DESCRIPTION
The DECT System allows mobile users to use the switched telecommunication facilities provided by a SOPHO ISPBX. Such a mobile user can make or receive calls by using a cordless handset. All call handling facilities of the ISPBX are available on the cordless handset. As the cordless connection is a data connection, data transport will also be possible in the future. The Digital Enhanced Cordless Telecommunication (DECT ) interface has been developed by the European Telecommunication Standards Institute (ETSI). Mobile users carry a portable handset which uses a radio transceiver to communicate with the ISPBX. The radio transceivers are connected to the ISPBX. They are placed within the working area so that a portable handset/telephone is always within radio reach of at least one such transceiver. The portable telephone is called a Portable Part (PP) of the system. It also contains a transceiver. A transceiver connected to the ISPBX is called the Radio Fixed Part (RFP). The RFP is also referred to as a base station.
SOPHO ISPBX RFP pp
RFP
RFP
pp
Figure 1-1 Radio Parts The radio area covered by a single RFP is called a cell. The RFPs are located so that the cells overlap slightly and the PP can remain in contact with the ISPBX when moving from one cell to another. A group of cells belonging to one DECT system is called a cluster. Up to 4 RFPs can be connected to a DECT Cluster Controller (DCC) board. A DCC provides 30 user
channels to the switching network. A DCC is placed in the first position of a unit group (0 ... 7) and it uses all timeslots in that unit group. The ISPBX treats the channels as ISDN channels. When the ISPBX is running Call@Net, up to 510 DNRs can be assigned to the 30 user channels. The number of RFPs needed to cover a certain area (within which the mobile telephone users might roam) depends on many factors such as: The size of the area. The nature of the area; - The number and the size of buildings in the area. - The radio propagation characteristics of the building(s). - Materials used for walls, floors, elevator shafts, reinforced glass, doors etc. - Strong magnetic fields in the area (e.g. as result of welding equipment, radar, etc.). The amount of telephone users in an area, and how often they make or receive calls.
The number of PPs which can be connected simultaneous via a single DCC is limited by the number of channels provided by the DCC, i.e. 30 telephones. The number of RFPs is limited by the number of DCC boards (maximum 4 RFPs per DCC). If the 6 channel RFPs are used, the maximum number of simultaneous calls per DCC is also be limited by the RFPs (e.g. 4 RFP 6 channels = maximum of 24 simultaneous calls). This system allows other, fixed telephones to communicate with PPs without any modifications in the basic SOPHO ISPBX. The Figure 1-2 "Cordless and Fixed Telephones on The Same Exchange" depicts an iS3000 series system with line extension components together with DECT components. The speech signal will be encrypted, if the portable handset allows it, to ensure the privacy of the conversation. This encryption is done fully automatically, without the intervention of a technician.
1.2.
RFP-PP COMMUNICATION
The radio link between the RFP and a PP can carry information on any one of ten carrier frequencies and in one out of twelve pairs of time slots (12 in each direction). These carrier frequencies are between 1880 MHz and 1900 MHz and are separated by 1728 KHz. The modulated date rate is 1152 Kbs. DECT uses in the OSI physical layer the following multiplexing techniques: FDMA (Frequency Division Multiple Access);
10
TDMA (Time Division Multiple Access); TDD (Time Division Duplex).
The RFP-PP communication radio signal carries time division multiplexed frames; each frame is 10ms long. Each frame contains 12 time slots which carry data from RFP to the PPs, and 12 time slots which carry data from PP to the RFP. This means that two time slots in every time frame are needed for a full duplex connection to a PP. See Figure 1-3 "Each Timeslot can use Any of the 10 Carrier Frequencies".
SOPHO ISPBX
DCC RFP PP DCC RFP
DCC
RFP PP
DCC
RFP
ALC
DLC
ATU or DTU
Other exchange
Figure 1-2 Cordless and Fixed Telephones on The Same Exchange
11
10 ms time frame RFP to PP 0 F1 1 2 3 4 9 PP to RFP 10 11 12 13 14 15 16 21 22 23
F10
0 ms F (n) = carrier Frequency (n)
5 ms
Time
10 ms
Figure 1-3 Each Timeslot can use Any of the 10 Carrier Frequencies Figure 1-4 "DECT Time Frame and Timeslot Structure" shows a time frame and a time slot. Each time slot may carry 32 kbs Adaptive Differential Pulse Code Modulated (ADPCM) user data. Each time slot pair can contain ADPCM user data on any one of the ten carrier frequencies so that the carrier frequency often needs to be changed between time slots: Refer to Figure 1-5 "Each Time slot can use Any of the 10 Carrier Frequencies". The information within the time slot does not completely fill the time slot; time is allowed for propagation delays, ramp up and ramp down of the transmitter and for switching of the carrier synthesiser between slots.
10 ms RFP to PP 0 1 2 11 0 1 2 PP to RFP 11
416.67 s
Sync. Word 32 bits Signalling data 64 bits Speed data 320 bits Guard Space
364.67 s
52 s
Figure 1-4 DECT Time Frame and Timeslot Structure
12
10 ms time frame
F2 F7 F5 F2 F9 F3 F6 F8 F4 F6 F2 F7 F2 F7 F5 F2 F9 F3 F6 F8 F4 F6 F2 F7 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 5 ms PP to RFP
5 ms RFP to PP
Where F2 = carrier Frequency 2. Etc.
Figure 1-5 Each Time slot can use Any of the 10 Carrier Frequencies A PP might use any of the 12 time slots (in each direction) on any of the 10 frequencies for a full duplex connection. So a maximum of 120 full duplex channels are available for connections to the PPs, within a cluster of a micro-cellular DECT system. In fact, this is only possible under ideal conditions; no disturbance, no interference, no other channels used, etc. Normally the conditions are not ideal in office or factory buildings, but the number of channels available will be more than sufficient. Note that there is always a fixed relation between the downstream timeslot number (from RFP to PP) and the upstream timeslot number (from PP to RFP) in one connection: Upstream timeslot number = downstream timeslot number +12. Upstream and downstream timeslot in one connection use always the same carrier frequency.
1.3.
BEACON SIGNAL
1.3.1. General
The beacon signal is a signal which is transmitted by an RFP in case the RFP is idle (no active calls). This beacon signal contains the System Identifier of the DECT System, the so called PARI (Primary Access Rights Identifier) and the number of the RFP, the RPN (Radio Part Number). (If the SARI, Secondary Access Rights Identifier is also used, it is also included in the beacon signal.) By means of this information the PP recognises to which system a signal belongs, and whether it is subscribed to that system or not. When there is a call for a PP, it also contains paging information.
13
When the RFP is not idle (there is an active call via the RFP), the beacon signal information is also transmitted in the call connection. Therefore, the beacon signal is not necessary at an RFP which has one or more calls active. In the DECT application in the iS3000 series, there are two beacon signals transmitted per RFP when the RFP is in idle condition. If there is a call only one beacon signal remains active. When there are a number of calls via the RFP, no beacon signal is transmitted anymore.
1.3.2.
Beacon Signal and PP
When the PP is in idle condition (not involved in a conversation) it scans the environment for the signals of a nearby RFP. It locks onto the strongest signal that can be found. This signal can be a beacon or a channel which is used for a call, because such a channel contains the beacon signal information. The PP uses the signal to synchronise its timing with the central system, and then it monitors the information transmitted via that RFP for calls to itself. If the PP moves closer to another RFP, so that the signal from this other RFP becomes stronger, the PP locks onto the new, stronger signal. In this way, the PP user can move around the area from cell to cell and remain in contact with the SOPHO ISPBX via the strongest radio link.
1.4.
CALL HANDLING PROCEDURES BETWEEN PP AND RFP
1.4.1. Setting up a Call

In case the PP user wants to make a call, he goes of hook. The PP selects an unused channel at the RFP to which it is locked. This channel is in one of the timeslots (0 ... 11) from RFP to PP; the RFP will use the corresponding timeslot (12 ... 23) from PP to RFP to communicate with this PP. The connection is built up through this RFP and its connected DCC to the SOPHO ISPBX. From now on the call setup is established in the normal way, except that the interface goes via the air.
1.4.2.
Paging and Answering a Call
If a PP is locked to a system, it continuously scans the beacon signal for paging information. (This beacon signal can be part of an existing call or as stand alone beacon.) If the PP recognises its own address in the paging data it alerts the mobile user. The user presses the "off-hook" key to answer the call. Then, the PP, which has been regularly scanning the environment for signals, selects an unused channel at that RFP to answer the call. This channel is in one of the timeslots (12 ... 23) from PP to RFP; the RFP uses the corresponding timeslot (0 ... 11) from
14
RFP to PP to communicate with this PP. The connection is built up via this RFP and its connected DCC to the SOPHO ISPBX switching network where it is connected through to the caller.
1.4.3.
Encryption
Most portable sets are capable of encryption and so the user data is encrypted over the air interface. This ensures the privacy of the conversation. Encryption is a process by which the digitised speech is "scrambled" making it impossible for anyone monitoring the frequency to listen to the conversation. For this scrambling, a DCK (DECT Ciphering Key) is used. This is a key which is agreed at the first time data has been transferred between the PP and the RFP, which is at the moment that the PP "locks" to the DECT system).
1.5.
CLUSTER ARRANGEMENT
1.5.1. General
A cluster is defined as a logical group of radio cells belonging to one DECT system. Within this arrangement bearer handover is possible. Figure 1-5 "Each Time slot can use Any of the 10 Carrier Frequencies" shows an ideal cluster arrangement of radio cells in which each cell has a boundary with a number of other cells. An omnidirectional radio signal is transmitted equally in all directions so that the actual radio signal from the RFP in cell 1 overlaps slightly into cell 2, cell 3, cell 4, and so on. Similarly, the radio signal from the adjacent cells overlap into cell 1. So, cell 1 can be seen as the centre of a cluster of cells. If a certain frequency is used in a certain timeslot in cell 1, it cannot be used in any of the adjacent cells in the same timeslot because of interference at the cell boundary. But that same frequency can be used in cell 8. Thus, within a cluster a certain channel/frequency combination can be used again, simultaneously, only if the cell which uses such a combination does not interfere with another cell which uses the same combination.
1.5.2.
RFP Behaviour in a Cluster
Each RFP constantly scans the area for signals in each channel. These signals can be generated by other RFPs or other equipment. The RFP selects one or two free channels to transmit the beacon signal. (The number of beacon signals depends on the number of active calls via the RFP.)
1.5.3.
PP Behaviour in a Cluster
The PP also picks up all sorts of signals which may come from the closest RFP, the next cell or from outside equipment. It locks onto a good RFP signal, and when it must make or receive a
15
call it chooses a channel with the least interference to do this. When a call is made to a mobile telephone, that telephone must be paged. This means that all RFPs transmit a paging message. The information in each active timeslot transmitted by the RFP contains paging data, whether it is in use for a connection or being used only as a beacon. If an idle PP is locked onto a beacon it examines the control data in that signal for paging data. Thus, it always receives all paging requests, so any calls to that PP will be received and recognised. The PP alerts the PP user, who can then answer the call. The PP scans the channels regularly so that it knows which channels are available at the nearby RFP. When the PP user presses the "off hook" button, either to answer a call or to make a call, the PP selects a channel which is not being used. It uses this channel to set up the call.
RFP
Overlapping radio signals. (In practice the Overlapping area is longer)
2 7 1 6 5 10 9 4 3 8
Radio signal Interference from cell 1. Detected in surrounding cells. But not cell 8.
Figure 1-6 Cluster Arrangement of Radio Cells
1.6.
HANDOVER
Both the RFP and PP monitor the quality of the radio link. If the interference on a certain
16
carrier frequency causes problems, it might be necessary to switch to another frequency at that same base station. This is called intra-cell handover.This handover procedure requires that the connection can be supported on 2 channels simultaneously, for a while, to allow a "seamless handover" (no breaks and hiccups during the handover). First, the new channel is chosen and the connection is set up via this channel, while the old channel is still in use. Then the old channel is disconnected. If the mobile user roams from one cell to another, during the conversation, he goes probably out of range of the first RFP and into the range of the second. In that case, when the quality of the transmission requires it, the radio link switches over to the new RFP. This is called intercell handover.Once again it is a seamless handover.
Note: A handover is always initiated by the PP!
1.7.
CALL QUALITY CONTROL
Both the RFP and the PP monitor the quality of the call. If the PP decides that the quality is not acceptable, it can do one of three things: 1. Request that the RFP uses its other antenna to communicate with the PP. The signal in the cell may suffer from fading, so that at one place the signal might be poor while very close to it the signal may be acceptable. To counteract this, each RFP has two antennas mounted close together. The system tries to select the best antenna for each channel separately.This method of using two antennas is referred to as antenna diversity. 2. If the quality of the connection warrants it, the PP can request a handover to another channel. That channel may be on the same RFP (intra-cell handover) or on another RFP (inter-cell handover). During handover, the communication to the PP is built up over the new channel so that for a short time the communication is available over both the old and the new channel. Then the old channel is disconnected. The user does not notice any break in the communication due to handover. 3. Mute the output (voice connections). It blocks the stream of information from radio signal to user (ear piece, in a telephone). This stops noisy signals being passed on to the user. It is done as a temporary measure, only. Note that muting is done on both ends of the connection independently. If the RFP decides that the quality of the connection to a certain PP is not acceptable it can do one of three things:
17
1. Use the other antenna (antenna diversity). The PP does not notice the change. 2. Tell the PP that a handover is necessary. The PP always initiates the handover after selecting the best channel as seen from the PP. 3. It can temporarily block the data stream from PP to the DCC (mute the call in the direction towards the switching network). ( Note that muting is done on both ends of the connection independently.)
1.8.
SUBSCRIPTION AND DE-SUBSCRIPTION
Before a PP can be used, it must be subscribed (registered) to the system. That means that a relation must be defined between the DECT System and the PP. There are three identifiers used to define the relation between the system and the PP: IPUI (International Portable User Identity) This is the identity number of a PP. It is issued from the system to the PP during subscription. From that time onwards, the PP is recognized by the system at its IPUI. This number is a unique number in the system, there is no other PP with the same IPUI. PARI (Primary Access Rights Identity) This is a (world-wide) unique number for the DECT system. This identifier is delivered on a certificate, together with the system. It must be entered in the system manually. UAK (User Authentication Key) This is a secret key which uniquely defines the relation between the PP and the DECT system (PARI)
UAK PARI DECT System IPUI PP
Figure 1-7 UAK Relation between the IPUI and the PARI. When a PP is subscribed (made known) to a DECT system, the relation between the PARI of the DECT System and the IPUI of the PP is defined Figure 1-7 "UAK Relation between the IPUI and the PARI.". This relation is secured by the UAK, which can be seen as the glue between the IPUI and the PARI. From now on the PP knows to which system (PARI) it is subscribed.
18
For the subscription procedure the DECT Manager must be used. This is a software tool to control the DECT System. It runs under Windows NT. Older versions run under C-DOS, Unix or Windows 95. The DECT Manager PC has a TCP/IP connection to the DECT System. In the DECT Manager, an extension number must be selected which is required for the PP. Then the DECT Manager generates a code ("PIN code" or also called "Authentication Code"). This code must be entered in the PP within a certain time period. If the operation has been completed successfully, the PP is subscribed to the system and is allowed to make and receive calls. A portable can be subscribed to more than one DECT system. Therefore, it can be used in areas covered by different DECT systems or in different areas with their own DECT system. For example, this allows you to use the same PP for the DECT system which is operational in your company and also for your home DECT. Also if the company is located at different sites, it is possible to use the same PP at the different sites, if DECT systems are present on these sites. It has a different extension number for each DECT system. It cannot roam from one of these areas to the other, while busy with a conversation. The user of the portable must ensure that his set is communicating with the required DECT system, when making calls in a certain area. This may be done manually by a selection key, depending on the type of the portable. There are also PPs which selects DECT systems automatically. The DECT Manager can be used to de-subscribe (remove or disable) the PP. Such a service condition of a PP can always be displayed at the DECT Manager. A portable which has been "removed", still contains the subscription data, but cannot gain access to the system. (If a "reset" is executed at the PP, the subscription data in the portable is removed also.) The DECT Manager operator can use the "remove" command (remove subscription) in case the portable has been lost or damaged. A portable which has been "disabled" at the DECT Manager, has been put on the blacklist in the DCC. When the user of that portable goes off hook or receives a call, the DCC and the PP exchange information which results in the de-subscription of that PP. It is no longer recognised by the DECT system and it is free to be subscribed again. This is the normal way to de-subscribe a portable set. If a portable has been disabled, but is not in a state to go off hook and complete the desubscription, the remove command can be used after the disable command.
1.9.
SECONDARY ACCESS RIGHTS IDENTIFIER (SARI)
The SARI (Secondary Access Right Identifier) has the same function as the PARI, but it is used as a second check in case the PARI +UAK do not match between the DECT system and the PP.
19
The PARI is a unique number belonging to one DECT system only. The SARI can be the same identifier, used in more than one DECT system. The DECT system transmits both PARI and SARI as identification signals. If the PP detects a DECT signal in the air, it checks whether the PARI + UAK in that signal matches with its own PARI + UAK data in the subscription record. If so, the PP "locks" to that signal. If not, the PP does a second check but now on the received SARI + UAK. If that matches, the PP "locks" to that signal. The Secondary Access Rights (SARI) is used in case you want to use your PP on more than one DECT system (no handover possible between systems!), but with the same subscription record (comprising the SARI and UAK) in the handset. In that case, you must subscribe your PP to one system, and copy the subscription record to other systems, all having the same SARI. You don't need to subscribe that PP anymore to the other systems. Figure 1-8 "Using SARI in three DECT Systems." gives an example of three different DECT systems (three different PARIs) and one SARI. In this example the PP is subscribed to system with PARI X. As long as the SARI is the same as the PARI X, the subscription data (of that PP) in DECT system X can be copied to the other two DECT systems (by means of the DECT Manager). When the PP receives radio signals from system Y or system Z, it first checks the PARI of that system and if that doesn't match it will check the SARI of that system. The SARI has the same value as PARI X, so it will match and because the subscription data was copied, the UAK will also match. So. the PP can also be used on systems Y and Z.
20
DECT System X PARI = 1000900A SARI = 1000900A DNR X Subscription record for PP with SARI =1000900A RFP
Copy subscription record to:

DECT System Y PARI = 10009011 SARI = 1000900A DNR Y Subscription record for PP with SARI =1000900A RFP
Subscription record for PP with SARI =1000900A This subscription record matches on three systems. If the PP is used on system X, it has DNR X, if used on system Y it has automatically DNR Y, if used on system Z it has automatically DNR Z
DECT System Z PARI = 10009035 SARI = 1000900A DNR Z Subscription record for PP with SARI =1000900A RFP
Figure 1-8 Using SARI in three DECT Systems.
1.10.
SYSTEM ARCHITECTURE
1.10.1. General
The DECT system is integrated in the SOPHO iS3000 system. In Figure 1-9 "DECT System Configuration in iS3000 series Systems" its architecture is depicted. The subsections in this section explain various functions of the hardware. The following hardware is required for the DECT System: DCC (DECT Cluster Controller). This is a PCT which can be used in the first position of Unit Group 0 ... 7. It has 30 circuits available for user channels. When the ISPBX is running Call@Net, 510 DNRs can be
21
assigned. Up to 8 DCCs can be placed in a shelf (PM255 or PM1100) and up to four shelves can be used in one DECT System. Therefore up to 32 DCCs can be configured in one DECT System. Note that the DCC can handle a maximum of one call set-up per second. BBR (BackBone Repeater) This board only derives power from the backpanel. Its main function is to interconnect the BackBone busses of up to four shelves with each other. The BBR also provides a Barrier Box function for the V.24 connection between the system and the DECT Manager PC. Although not depicted the BBR is equipped with a second barrier box function which is used for synchronisation signals, to synchronise DECT systems which are used close to each other. For more information, see also chapter 2. "HARDWARE INSTALLATION". The BBR is also equipped with an accurate clock, to synchronise the system clock of the ISPBX. The accuracy of this clock agrees with the DECT standard. This clock is only required if your system is an iS3010, iS3030 or iS3050 and the system clock is not synchronised with the public telephone network via a Digital Trunk using DTX-I or DTUPH (not ISG!)). PP (Portable Part) The Portable Part is a handset for the DECT system. Any portable part can be used as long as it complies with the GAP (General Access Profile), ETS 300 444 agreements. Full interworking with the SOPHO DECT System, however, is only guaranteed for handsets which are tested by Philips Business Communications. RFPs (Radio Fixed Part) Transceiver for the DECT radio signals. Various type are available (for more info, consult chapter 2. "HARDWARE INSTALLATION"). DECT Manager PC. The DECT Manager is a software tool running under C-DOS/UNIX or Windows. It is used for management of the DECT System.
Note: If your DCC(s) is/are equipped with firmware package F4324x.xxx, you have to use the latest version of the Windows DECT Manager (version 3). This DECT Manager version supports the SNMP protocol over TCP/IP (via V.24), which is the management communication protocol of this firmware package. So, older DECT Manager versions cannot be used with this firmware. BackBone (Bus) The BackBone bus provides the interface between the DCC boards.
The DCC boards can be configured in a cluster of up to 32 DCC boards, each DCC capable of handling 4 RFPs. The DCC boards make use of the four BackBones in each PM1100 shelf. The four BackBones in each shelf in the cluster must be connected together by means of the
22
BackBone Repeater (BBR) board. A cluster which covers more than one PM shelf (up to four) requires one BBR. The BBR can be placed in any PCT position as it only derives power from the backpanel. The connections between the shelves are established by means of cabling between one of the DCCs in each shelf and the BBR. If there is only one shelf which is used for the DECT System, the BBR is not required for the BackBone configuration. However it can still be used for the Barrier Box (BB) function which provides an isolation between the V.24 interface at the iS3000 system and the V.24 external. It can also be required for isolation of the DECT sync port interface or for the accurate time reference signal.
23
SOPHO ISPBX
Shelf 1 DCC RFP PP
Back Bone Bus
DCC
RFP
RFP DCC Backbone Connection Shelf 2 DCC Position 01 RFP Back Bone Bus DCC
RFP PP
V.24
DECT Manager Local or Remote
BBR BB
V.24
Figure 1-9 DECT System Configuration in iS3000 series Systems
24
1.10.2. DECT Manager

The management of the DECT System is done with the DECT Manager software. For subscription, each DECT System must have its own DECT Manager, with files of data for that DECT System. The DECT Manager is used for: control and configuration of the DECT System. easy control of subscriptions to the DECT System. configuring radios. licensing.
For detailed information refer to DECT Manager User Guide.
Note: If your DCC(s) is/are equipped with firmware package F4324x.xxx, you have to use the latest version of the Windows DECT Manager (version 3). This DECT Manager version supports the SNMP protocol over TCP/IP (via V.24), which is the management communication protocol of this firmware package. So, older DECT Manager versions cannot be used with this firmware. Note: Do not use the Unix or CDOS Dect Manager for Call@Net software.
1.10.3. BackBone Architecture

The Backbone architecture is required for the communication between the DCCs in the system. This communication is required for rerouting the calls in case of handover and also for the communication between the DECT Manager and the DCC boards (the DECT Manager interface is connected to only one DCC!). The following explains the function of the BackBone architecture in case of handover: If the PP user roams around the whole area covered by RFPs, his access to the ISPBX Switching Network must still be made via the same (SN-)DCC channel, no matter which DCC has the connection to the RFP and PP. The DNR of a PP is related to the channel between a certain DCC and ISPBX Switching Network in the same way as a fixed telephone is related to an ALC or a DLC. If the PP user roams around the whole area covered by RFPs, his access to the ISPBX Switching Network is still be made via the same DCC channel.
25
This means that handover actions require interactions between DCC boards, if the handover goes from an RFP on one DCC board to an RFP on another DCC board. To allow handover actions between DCC boards, without using the SN, a BackBone bus is used. The BackBone bus connects together DCCs in Unit Group 0...7 via the backpanel of the PM1100 and PM255. In the PM55 shelf it connects together DCC in Unit Groups 0...2. This bus comprises four 20 Mbit/s connections in the PM1100 shelves and one 20 Mbit/s connection in the PM55 and PM255 shelves. The DCC to which a PP is related by his DNR is called his "home" DCC. It may have a connection via an RFP on his home DCC or via an RFP on another DCC - the "visiting" DCC. In the latter case, the call is routed between PP - RFP - visiting DCC - BackBone - home DCC - SOPHO ISPBX. See Figure 1-10 "An example of the Home and Visiting DCCs Using the BackBone". If the DCCs are placed in more than one shelf, the backbone bus must be interconnected between the shelves. To do this, a BackBone Repeater (BBR) board with interconnection cabling must be installed in one of the shelves. See Figure 1-11 "Maximum DCC Configuration Using the BackBone (in Call@Net it can be 8 DCC x 510 PPs = 4080 PPs)" for configuration. The BackBone Repeater board connects together the backbone busses of up to four PM1100 shelves. Each shelf contains up to eight DCCs. This means that a maximum of 32 DCCs can be connected together via the Backbone.
26
SOPHO ISPBX
30 channels
DCC
VISITING DCC RFP
RFP
Backbone Bus Conversation connection
DCC
To the Switching Network 30 channels
RFP
RFP
DCC
30 channels
HOME DCC RFP
RFP
Conversion connection between SN and RFP - PP
Figure 1-10 An example of the Home and Visiting DCCs Using the BackBone
27
SOPHO ISPBX
Shelf 0 DCC 7 DCC 0 RFP
8x RFP RFP
8(DCC) x30 (PP) = 240 PPs
Back Bone Repeater (BBR) Barrier Box
8x RFP Shelf 1 DCC 7 DCC 0 RFP RFP

8(DCC) x30 (PP) = 240 PPs

8(DCC) x30 (PP) = 240 PPs

8(DCC) x30 (PP) = 240 PPs
V.24
DECT Manager
Figure 1-11 Maximum DCC Configuration Using the BackBone (in Call@Net it can be 8 DCC x 510 PPs = 4080 PPs)
28
1.11.
SYSTEM CONFIGURATION
1.11.1. General
In many cases the customer has chosen a combination of mobile telephones and conventional wire connected telephones. The SOPHO ISPBX allows the customer to phase in the use of mobile telephones and migrate from a fixed wired system to a mobile system in small steps. The maximum number of simultaneous connections that can be made in a DECT system depends on the following: The number of portable sets that are subscribed to that system, and their location. The number of RFPs that are included in the system. The way the RFPs are arranged and positioned.
Each DCC allows 30 channels to be used for subscription. Up to 30 simultaneous connections per DCC are possible, although up to 510 PPs can be subsribed to one DCC. Depending on the type of RFP an RFP allows 6 or 12 full duplex channels (out of 120) to be used simultaneously, within it's cell. A maximum of 4 RFPs can be connected to one DCC. In case of an 12 channels RFP, this assumes that the maximum number of channels is 48. However, the DCC limits this number to 30 channels as a result of the circuits on the DCC. It is difficult to determine the configuration of cluster. The type of construction of the building has unpredictable influence on the propagation of the radio signals. Also the effect of radio interference and of obstacles cannot be calculated. It is expected that the minimum range (radius) of an RFP is 20 metres, while the maximum range may be 80 metres, depending on the environment and the required quality. Therefore a site survey must always be made to acquire information about the propagation of the radio signals, the location of RFPs and the coverage. To make a Site Survey, you must use a special Site Survey kit. For more information consult the "Site Survey / Deployment manual" that comes with the kit. Be also aware of areas with high concentrations of PPs. With sufficient and correct site information the configuration and location of RFPs is determined. As soon as the number of RFPs is determined the number of DCCs can be calculated. Note that the number of DCCs is not only determined by the number of RFPs but also by the number of PP (extensions). Per DCC there are 30 user channels available to the Switching Network, so this means that a maximum of 30 simultaneous calls are possible per DCC.
29
1.11.2. Configuration Rules

The following general configuration rules are valid for the DCC boards: Always in the first board position of a Unit Group. The DCC occupies all the channels in that Unit Group. DCC is NOT allowed in Unit Groups 8 and 9.
Note: Don't use ATU-ST03, ATU-EL03, ATU-IL03, ATU-IL23 or ATU-PA*) boards in a PM1100 or CSM shelf in which a DCC is installed. *) This is not valid for the upgraded ATU-PA boards (12 NC: 9562 151 46200). Do not use the DTU-PH in Unit Groups 0...7 in a PM in which also DCCs are installed. This is not valid for the upgraded DTU-PH with 12 NC 9562 158 37300. Furthermore, the configuration rules depend on: Your system type (iS3010, iS3030, iS3050, iS3070, iS3090) The boards and shelves that are used for DECT in your system: - 24-DCC old (see Figure I-7 "Diagram 300"for specifications); - 24-DCC new (see Figure I-7 "Diagram 300"for specifications); - 32-DCC; - PM1100 old; - PM1100 new; - BBR (three different types)
To determine the allowed configuration together with the configuration rules, consult Figure I-7 "Diagram 300". This diagram helps you determine your DECT system type and it refers to Figure I-8 "Diagram 301", Figure I-9 "Diagram 302" and Figure I-10 "Diagram 303" for the configuration rules.
1.11.3. System Expansions

Note that for system expansions, you sometimes need to upgrade your system. For upgrading the following rules are applied: Expansion of a "24-DCC old" system can only be done with equipment which has 12 NCs that correspond with the 12 NCs mentioned in Figure I-8 "Diagram 301". If no such equipment available, then you have to upgrade to a "24-DCC new" system.However, it is always advised to upgrade the "24-DCC old" system to "24-DCC new". This means that the 24-DCC boards as well as the BBR must be upgraded in the factory
30
(see Figure I-7 "Diagram 300"). If you use PM1100 or CSM shelves for the DECT system, you may need to upgrade the PM1100 shelves depending on the 12 NC (see Figure I-7 "Diagram 300"etc.). For upgrading, see Field Change Orders. The CSM shelf is NOT upgradable. If you want to expand your "24-DCC new" system then make sure that you have the correct 12 NCs for the DECT equipment parts. See Figure I-9 "Diagram 302". If you want to expand the "24-DCC new" system and it exceeds the system limits (max. 24 DCCs, 96 RFPs) then you must upgrade the whole system to 32-DCC. This means upgrading the DCC boards. For upgrading consult the Field Change Orders.
1.11.4. Maximum System Configuration 24-DCC (old and new)

In the table below the maximum system configurations are given. In case of the maximum configuration the user channels of Unit Groups 1 ... 6 are occupied by the DCC boards.
SYSTEM TYPE
MAX. NUMBER OF DCCs 2 6 24 24 24
MAX. NUMBER OF RFPs 8 24 96 96 96
MAX. NUMBER OF PPs up to SSW 805 60 180 720 720 720 Call@Net only 1020 3060 12240 12240 12240
iS3010 iS3030 iS3050 with four PM1100 shelves iS3070 with four PM1100 shelves iS3090 with four PM1100 shelves
Table 1-1 Maximum System Configuration 24-DCC (old and new)
1.11.5. Maximum System Configuration 32-DCC

In the table below the maximum system configurations are given. In case of the maximum configuration the user channels of Unit Groups 0 ... 7 are occupied by the DCC boards.
31
SYSTEM TYPE
MAX. NUMBER OF DCCs 3 8 32 32 32
MAX. NUMBER OF RFPs 12 32 128 128 128
MAX. NUMBER OF PPs up to SSW Call@Net 805 only 90 240 960 960 960 1530 4080 16320 16320 16320
iS3010 iS3030 iS3050 with four PM1100 shelves iS3070 with four PM1100 shelves iS3090 with four PM1100 shelves
Table 1-2 Maximum System Configuration 32-DCC
1.11.6. Mixed System Configuration 32-DCC - DCC-8

The 32-DCC boards can be mixed with the new DCC-8 boards (see iSMobile DCC-8 Customer Engineer Manual) in one DECT cluster. However, the firmware and the BBR must have the correct version. If not, then you cannot make a mixed configuration!!!! For more information consult chapter 5. "MIXED CONFIGURATION" Make sure that you also check which hardware is installed and what should be upgraded before you create a mixed system. Consult the diagrams in section I . "DIAGRAMS". The 24-DCC boards can never be used in systems with 32-DCC boards or DCC-8 boards. Therefore, if you want to expand an existing 24-DCC DECT system, you must either install 24-DCC boards or upgrade your DECT system to either 32-DCC boards or directly to DCC8 boards.
32
2.
2.1.
HARDWARE INSTALLATION
GENERAL
2.1.1. General Requirements

Apart from the equipment to be installed, the technician requires an ordinary set of tools comprising such things as screwdrivers and pliers. Further, the person who does the physical installation of equipment may need a drill, screws, wall plugs, etc, for fixing an RFP to a wall or appropriate materials for fixing the RFPs in other locations.
2.1.2.
Site Requirements
The DCC will be mounted within the cabinet of the SOPHO ISPBX, therefore, the site requirements for the SOPHO ISPBX are applicable. The RFPs will be usually fixed to existing walls or mounted on separate stands in the positions determined by the site survey. Each power supply charging station for the portable sets needs a mains power point.
2.1.3.
Visual Check
The equipment must be carefully unpacked and examined for any visible sign of damage. The items must be checked against the material specifications for any discrepancies. Anything not OK should be reported back to the supplier, as soon as possible, to avoid delays during installation due to missing equipment.
2.1.4.
Installation Procedures
The installation of the DECT equipment comprises the installation of: the boards for the DECT system; - strap settings - cabling between the boards the RFPs; the interface to the DECT Manager PC; the DECT Synchronisation Port (if required).
Installation of the cabling between the DCC boards and the RFPs is not described in particular. However in the section RFP-DCC cabling the various cabling configurations and requirements are described.
33
2.2.
RFP-DCC Cabling
Each Radio Fixed Part (RFP) is connected to the DCC by a 22 wire twisted telephone cable (120 ohm); one pair for signals from DCC to RFP and the other pair for signals from RFP to DCC.
Note: The RFP-DCC cable has to be twisted pair from the beginning to the end. If one metre in the RFP-DCC cabling is not twisted pair it can result in an instable behaviour of the RFP. The cabling configuration for the RFP Type B306 and successors with DCC is depicted in the figure below.
SOPHO ISPBX Main Distribution Frame DCC RFP Connector Box RJ45 RFP
See table 2.1
Figure 2-1 RFP B306 (and Successors) Connection to DCC. Table 2-1 "Indications of Maximum allowed Cable Length for various Cable Diameters" gives an overview of the maximum cable length. These values are only indications, valid for class 5 cable. (Class 3 can only be used for distances up to 1 km).
34
TWISTED PAIR CABLE TYPE 0.4 mm 0.5 mm 0.6 mm 0.8 mm
MAX. CABLE LENGTH (RFP type B306 and successors, cable class 5) 1000 m 1500 m 1700 m 2000 m
Table 2-1 Indications of Maximum allowed Cable Length for various Cable Diameters Note: The values in the table above may differ due to environment conditions, cable quality, the number of MDFs in between, etc.! No rights can be claimed on these values! The cabling between the RFP and the DCC transports the AC signals and the DC power provision for the RFP ("phantom" power provision). The DC power is transported as follows: -58 volts via the receiving lines of the DCC and the 0 volts via the transmitting lines. On long lines: The DC voltage on the RFP side should be at least -35V to ensure correct working of the RFP. The AC line signal is 2 Mbit/s, HDB3 coded. The following general rules are applicable for the cable: The cabling between the ISPBX MDF and the wall socket must meet the requirements for at least category '3' UTP cable as defined in the EIA/TIA bulletin: TSB 36. The signal loss may not exceed 34 dB at 1,024 MHz per wire pair and measured between the DCC and the RFP. Cross talk level (between wire pairs) must be >or equal 54 dB at 1,024 MHz. The DC loop resistance of the cable may not exceed 180 ohms, measured between the DCC and the RFP. If the twisted pair from the MDF to the RJ45 socket is part of a cable with other twisted pairs, the other pairs in the cable may not be used for analogue interfaces.
The cable might already be laid from MDF to the site, as an ordinary telephone cable. In that case, the installing engineers need only to lay a cable from that telephone connection to the RFP. Ensure that the cable is twisted pair from the beginning to the end!! The cable should terminate close to the RFP in an RJ45 connector box. Note: Be sure that there is no 100 ohms terminating resistor present in the RJ45 connector box! For the connection between the RJ45 connector box and the RFP, use only the factory made
35
cables. Note: Cabling distances are only valid for the mentioned (supported) equipment.
2.3.
INSTALLING THE RFPs WITH DCC-RFP CABLING
The initial site survey should provide a plan with the positions of the RFPs. It may prove impossible to mount the RFPs in the exact position determined by the survey. In this case it should be possible to mount the RFP within a metre or two of the initial survey position without having any noticeable effect on performance. The RFP radio 'footprint' is more or less spherical.
Note: The RFP should be placed in a vertical position. A horizontal position can result in smaller range in some environments. The RFP should be placed where it is unlikely to be damaged. For example, an RFP in a warehouse should be placed where it can not be damaged by a forklift truck. The RFP should be placed high enough to be unaffected by surrounding objects. For example, an RFP in a car park needs to be placed higher than any vehicle that may be parked next to it. The minimum distance between 2 RFPs must be >5 meter. It is advised to keep the distance between two RFPs as wide as possible. The RFPs are provided with a cable which is terminated with an RJ45 connector. This connector must be plugged into a wall socket which must be wired as depicted in Figure 2-2 "RFP Jack (Socket)". Installation Procedure For installing the RFP, execute the following steps: 1. Determine the position of the RFP according to the results of the site survey. 2. Mount the mounting plate for the RFP to the wall. 3. Ensure that the cable with the RJ45 plug is installed in the RFP. If not, install the cable. Note: Only use factory made cables! Try to lead the cable away from the RFP as much as possible. 4. Install the cabling between the MDF and the RJ45 connector. Consult the sections "DCCRFP Cabling" and see Figure 2-2 "RFP Jack (Socket)"and Figure 2-3 "RFP Connections from the DCC on the MDF".
36
If you are using existing cabling for this connection, check that it agrees with the requirements as denoted in "DCC-RFP Cabling". The cable is connected to an MDF block. Each RFP needs 2 transmit signal wires (TFx and TRFx) and 2 receive signal wires (RFx and RFRx). The power supply for the RFP is injected as a "phantom" circuit onto these lines; the -58 volts is connected to the receiving part of the DCC and the 0 volts is connected to the transmitting part. Note: The DCC is protected against short circuit. But if short circuit is made on one of the RFP interfaces on a DCC, the operation of other RFPs on the DCC can be affected by that. Calls via the other RFPs may be lost.
Legend; 1 = Not connected 2 = Not connected 3 = HDB3 Out 1 4 = HDB3 In 1 5 = HDB3 In 2 6 = HDB3 Out 2 7 = Not connected 8 = Not connected
RFx TFx TRFx RFRx
876 54321 RTTR
Figure 2-2 RFP Jack (Socket)

From DCC
RF 0 RFR 0 RF 1 RFR 1 RF 2 RFR 2 RF 3 RFR 3
TRF 3 TF 3 TRF 2 TF 2 TRF 1 TF 1 TRF 0 TF 0
Figure 2-3 RFP Connections from the DCC on the MDF Installing the RFP (B412E) with External Antenna's The RFP type B412E is a 12 channel RFP equipped with connectors, to connect external antenna's. The connectors are inside the box. In the rear side of the RFP box holes are preconfigured, which can easily be opened by pushing on them. You can lead the cables from
37
the inside connectors to the external antenna's via the holes in the rear side. Note: In case of application of an external DECT antenna used outside the recommended outdoor cabinet (12NC: 9562 043 48100), a precaution should be taken: a distance of at least 6,5 cm between the antenna and the general public must be guaranteed. This is in order to comply with the Council recommendation 1999/519/EC.
2.4.
INSTALLING THE DCC AND BBR
Note: Do not use ATU-ST03, ATU-EL03, ATU-IL03, ATU-IL23 or ATU-PA*) boards in a PM1100 or CSM shelf in which a DCC is installed. *) This is not valid for the upgraded ATU-PA boards (12 NC: 9562 151 46200). Also, do not use a DTU-PH in Unit Groups 0 ... 7 if a DCC is installed in the same PM. This is not valid for the upgraded DTU-PH with 12 NC = 9562 158 37300. To install the DCC and BBR execute the following steps: 1. Consult Figure I-7 "Diagram 300", Figure I-8 "Diagram 301", Figure I-9 "Diagram 302" and Figure I-10 "Diagram 303"for configuration rules for the DCC board(s). Note: In an iS3030 Extended, it is not possible to configure more than one backbone. 2. Check the strap settings of the DCC board. The positions of the straps and connectors on the DCC board are depicted in Figure 2-4 "Layout of the DCC Board". Note: The Built-In-Self-Test (BIST) connector is used in the factory and not used for installation or maintenance at the customers site.
38
Straps on DCC (V4 and DCC V4.1): Strap X9.1 These straps are only present on V4.0 boards (12 NC: 9562 158 79xxx); they must not be installed, because the board is equipped with an ASIC. On later versions of the board the straps are not present anymore. Strap X10.1 The strap setting depends on the system type. See Figure I-7 "Diagram 300", Figure I-8 "Diagram 301", Figure I-9 "Diagram 302" and Figure I-10 "Diagram 303". Strap X10.2 In case of model iS3010/iS3030 or a PM55 and PM255 the jumper is placed on position 102-103. In all other SOPHO ISPBXs the jumper is placed on position 101-102. Note: If your system is a mixed 32-DCC and DCC-8 system, also consult the iSMobile DCC-8 Customer Engineer manual for the strap settings on the DCC-8.
39
Mark
FBB
RFP
103 102 101
X10.1 Only on V4.0 X10.2 X9.1

103 102 101 101 102 201 202
BB
V.24
FCC Connectors for Synchronisation X1.4 X1.3
Backbone Connectors X1.2 X5. BIST (Factory test connector)
X1.3 = DECT Sync. Signal FROM BBR (IN) X1.4 = DECT Sync. Signal TO BBR (OUT)
Figure 2-4 Layout of the DCC Board 3. To connect the individual backbone buses of the Peripheral Modules one BackBone Repeater (BBR) board is required. Although no special board position is required, it is advised to insert the BBR board next to the left most DCC position of the second PM1100 shelf. Each backbone connection requires one special backbone cable. Take care, when installing the backbone cables. They carry 20 Mb/s. Always install them separate from all analogue cabling! Refer to Figure 2-5 "Backbone Connections between the DCC and the BBR" which depicts the interconnections and Figure 2-6 "Layout of the BBR Board"which depicts the board layout. Note that the BackBone cable must be connected between the DCC in UG0 (of each shelf with DCCs) and the BBR.
40
PM1100 Shelf 1 DCC in UG0 X1.2 Backbone cables
BBR Connector X1.5
PM1100 Shelf 2 DCC in UG0 X1.2 X1.6
Figure 2-5 Backbone Connections between the DCC and the BBR Note: Do not install the backbone cables in the same cable duct as cables carrying analogue information. See Figure I-1 "Backbone cabling example, new cabinet with built-in MDF", Figure I-2 "Backbone cabling example, new cabinet witout MDF" and Figure I-3 "BackBone Cabling (Current Configuration)" for backbone cabling instructions.
41
Mark X1.10 X1.9

Connector X1.9 = DECT Synchronisation signal TO DCC Connector X1.10 = DECT Synchronisation signal FROM DCC
FAB
DECT- Sync. Port (DSP)
FAD
V.24 Interface Port to/from DECT Manager
X1.5
X1.1
Backbone Connection to Backbone Section 0 Connector X1.6 or X1.1 may be used.
X1.6
X1.2
X1.7
X1.3
X1.8
X1.4
BB
FCC X2.1
V.24 Interface Port to/from DCC Precision 2.048 Mhz clock source to synchronise the system clock.
Figure 2-6 Layout of the BBR Board 4. If the DECT System is located very close to another DECT system, then the timing of each DECT system should be synchronised to the other, this will avoid problems with radio interference. To install a synchronisation link between the two systems, consult section "DSP (DECT Synchronisation Port) Interface" in this chapter. 5. Insert the DCCs in the PM shelves, in the leftmost board position of a Unit Group. 6. Install a standard F122 - MDF cable between the FBB front connector on the DCC and the MDF. 7. Install the cabling between the MDF and the RFPs and install the RFPs. Consult section "Installing the RFPs with DCC-RFP Cabling". 8. Connect the DECT Manager PC to the DCC. Consult section "V.24 DECT Manager Interface" in this chapter. Appendix A . "CABLES" gives an overview of the types of interface cables. Consult this Appendix for more information.
42
2.5.
V.24 DECT Manager INTERFACE
All DCC boards are equipped with a V.24 interface. This interface is required for the connection to the DECT Manager PC. Only one DCC in the DECT system requires a connection to the DECT Manager. Any DCC can be used for this connection. Due to currents through the earth wire in the interface, a barrier box function is mandatory in this connection. There are two configuration possibilities for the barrier box function: An external barrier box is used between the DCC and the DECT Manager PC. The barrier box function on the BBR is used.
These configurations are depicted in Figure 2-7 "DECT V.24 Cable Configuration with external Barrier Box"and Figure 2-8 "DECT V.24 Cable Configuration with BBR Barrier Box Function".
DCC
V.24 cable
FCC F122 Conn.
V.24 BARRIER BOX
V.24 cable
Figure 2-7 DECT V.24 Cable Configuration with external Barrier Box Appendix A . "CABLES" gives an overview of the required cabling for the external barrier box (e.g. Westermo type MA52).
43
DCC
BBR
FAC F122 Conn. V.24 BARRIER BOX V.24 cable
FCC F122 Conn.
FCC F122 Conn.
V.24 cable F122 - F122 One to one
Figure 2-8 DECT V.24 Cable Configuration with BBR Barrier Box Function The V.24 barrier box interface on the BBR provides an isolation function. The isolation functionality is according to the EN60950 agreements. This means that the interface withstands peak voltages of 1500 V against the voltage level of the system ground (not the DSP ground). The following cabling is distinguished: DCC - BBR V.24 Cabling The cable between the DCC and the BBR is a standard F122-F122 one-to-one cable. It can be connected from any DCC to the BBR. Refer to Figure 2-9 "V.24 DECT Manager Connections". BBR - DECT Manager PC Cabling The cabling between the BBR and the DECT Manager PC is a cable which is depicted in Appendix A . "CABLES".
44
1 0 0
FAA B C D FBA B C D FCA B C
1 0 0
1 0 0
FAA B C D FBA B C
1 0 0
V.24 to PC to Or Modem
V.24 Cable can be installed Between any DCC in the DECT system and the BBR
D FCA B C
V.24 from DCC
D C C
D C C
D C C
B B R
Precision clock output
Figure 2-9 V.24 DECT Manager Connections
Note: If your DCC(s) is/are equipped with firmware package F4324x.xxx, you have to use the latest version of the Windows DECT Manager (version 3). This DECT Manager version supports the SNMP protocol over TCP/IP (via V.24), which is the management communication protocol of this firmware package. So, older DECT Manager versions cannot be used with this firmware.
2.6.
DSP (DECT SYNCHRONISATION PORT) INTERFACE
The DSP Interface is used to synchronise two DECT systems which operate next to each other. By means of this, the transmitted timeslots of the DECT systems are synchronised. The interface for this synchronisation is agreed with other manufacturers of DECT systems. The interface cabling configuration is as depicted in the figure below.
45
DCC X1.4 X1.3
DSP cable Outgoing *
DCC X1.4 X1.3 DSP cable Incoming *
BBR X1.10 X1.9 FAB
MDF Connection To/from other DECT System
DCC X1.4 X1.3
* Between two systems, either the Incoming or the Outgoing DSP Cable is installed! Outgoing DSP cable used: this system is master, the other slave; Incoming DSP cable used: this system is slave; the other is master
Figure 2-10 DECT Synchronisation Port Cabling Structure Note: Besides this DECT synchronisation, a 2.048 MHz clock synchronisation to the public network or another ISPBX is always necessary. DCC - BBR Cabling The cable between the DCC and the BBR is a twisted pair flat cable. The synchronisation signals must be provided by (system is master) or to (system is slave) the leftmost DCC in the first DECT shelf. Note that normally only one flat cable must be installed: either the incoming or the outgoing. The flat cable is the same type as the flat cable for the backbone connection between the DCCs and the BBR. Don't mix them up! BBR Interface Isolation The interface for the DSP on the BBR provides an isolation function. The isolation functionally is according to the EN60950 agreements. This means that the interface withstands peak voltages of 1500 V against the voltage level of the system ground (not the DSP ground). BBR - MDF Cabling
46
The cabling between the BBR and the MDF is a standard F122 - MDF cable. BBR External DSP Interface The interface on the BBR is according the RS422 agreements. It is a balanced interface. The maximum voltage difference between the DSP ground and the signal wires is -7 V and +12 V. To avoid higher potentials, it is required to use shielded, twisted cabling, with the cable shield connected to the DSP ground. In the figure below the external interface connections are depicted.
Incoming DECT Sync. RJ45
1a 2a 1b 2b 3b 4b 5b 6b 7b 8b Outgoing DECT Sync signal a Outgoing DECT Sync signal b DSP Ground Incoming DECT Sync signal a Incoming DECT Sync signal b DSP Ground (not connected) 3 4
1 0 FAA 0 B C D
3a 4a 5a 6a 7a
FBA B C D FCA B C B D B R
8a
Outgoing DECT Sync. RJ45

Note: Either incoming or outgoing DECT Sync is wired. 3 4 1 6
Note: The ground wire of the DECT Syncport is isolated from the SOPHO ISPBX, but must be connected to the ground of the other system. In case of an other SOPHO ISPBX it must be connected again to the ground of the DSP port.
Figure 2-11 BBR DECT Synchronisation Port Connections For DSP cabling instructions, see Figure I-4 "DECT-sync cabling, new iS3030 cabinet.", Figure I-5 "DECT-sync cabling, old iS3030 cabinet."and Figure I-6 "DECT-sync cabling, new iS3050/ 3070 cabinet.". Configurations with DECT Synchronisation The maximum number of DECT systems, that can be connected for synchronisation, is 4. When two or more systems must be connected for synchronisation, one must be
47
connected as master. To this master a system is connected as slave. This slave is again connected as master to the following system. See the figure below.
Synchronisation To/from PSTN or other PBX
DS OUT DECT System 1 Master
Dect synchronisation cable
DS IN = DECT Sync port in DS OUT = DECT Sync port out -------- = Digital trunk line
DS IN DS OUT DECT System 2
DS IN DS OUT DECT System 3
DS IN DECT System 4
Figure 2-12 Example of a maximum configuration with DECT synchronisation The distance between the systems is limited. Important is the delay time. The maximum delay time between the first and the last system is 5 microseconds. The delay time in each system is 1 microsecond. Added to this must be the delay in the cable. This is 1 microsecond for 160 m. of cable. Refer to the Figure 2-12 "Example of a maximum configuration with DECT synchronisation" to see the maximum total (sync) cable length can be 3160 m. = 480 m. The clock of DECT system 1 must be synchronised to the Public Switched Telephone Network or other PBX. The clocks of the other systems must either be synchronised to the PSTN or through digital trunks to DECT system 1.
2.7.
SYSTEM CLOCK SYNCHRONISATION
The BBR is equipped with a precision clock circuit which generates a precision clock signal to synchronise the system clock. Don't mix this clock signal up with the DECT Synchronisation Port! (The DSP is discussed in the previous section.) The system clock in the ISPBX has a precision which agrees with the standards for ISPBXs. DECT, however, requires a more accurate system clock. If the system clock is already synchronised by means of a digital trunk connection to the Public Telephone Network, the precision clock on the BBR is not needed, because the precision of the clock signal of a public telephone network agrees with the requirements of the DECT standard. If the system clock is not synchronised with the clock signal of the public telephone network,
48
it must be synchronised with the precision clock on the BBR.
Note: iS3010/3030/3050: If no synchronisation with the public telephone network or other PBX is possible, always use the precision clock of the BBR, even if the BBR is not needed for backbone connections. iS3070 or iS3090: The system clock is accurate enough. For DECT no system clock synchronisation is required. In the table below an overview is given of the required system clock synchronisation in the various systems. SYSTEM iS3010, iS3030, iS3050 iS3070, iS3090 TRUNK WITH PSTN ANALOGUE BBR Clock to PMC CSG or SNS clock DIGITAL Clock from DTU/DTX-I to PMC Clock from DTU/DTX-I to PMC
Table 2-2 System Clock Synchronisation required for DECT Note: If your system with CSN-BC or PMC clock, has a digital connection via an ISG instead of a DTX-I/DTU-PH, no clock signal is provided via the digital connection (on the ISG). Use a BBR as clock source for system clock synchronization. To synchronise, execute the following steps: 1. Connect the coax clock output connector of the BBR to the coax clock input connector on the PMC or CSN-BC. Use a coax cable which can also be used for a clock synchronisation connection between a DTU and the PMC or CSN-BC. 2. Assign the clock entry on the PMC or CSN-BC. For SSW 300 use OM command DICLKS. For SSW 740/741, 800, 805 and onwards use OM command ASCRUE.
49
3.
3.1.
PROJECTING DECT IN ISPBX

GENERAL
The DECT system must be projected in the ISPBX and in the DECT Manager. Projecting procedures for the DECT Manager are described in the DECT Manager User Guide. The projecting procedures in the ISPBX are described in this chapter. Due to the differences in System SoftWare, the procedures are different for SSW 300.31 and SSW 740/800 and upwards.
3.2. 3.2.1.
PROJECTING IN SSW 300 Projecting Procedures
Projecting the DECT system can be done by means of a number of PE commands. The only board type that has to be projected is the DCC. The BBR only derives power from the backpanel and therefore does not have to be projected. To project the DCC boards, execute the following steps: 1. Make sure that the DCC board positions are defined according to the configuration rules. The BBR can be placed anywhere since it only derives power from the backpanel. 2. If the DCC boards are spread over more than one shelf, determine which shelf is the first DECT shelf (Back Bone section), which shelf is the second DECT shelf (Back Bone section) etc. This depends on the connection of the backbone cable from one DCC in the shelf to the backbone BBR. Each cable from the BBR is connected to a Back Bone section. There are four BackBone sections: Position BB0 BB1 BB2 BB3 BackBone section (see note) 0 1 2 3
Note: Although the PM55 and PM255 comprises two shelves, in the DECT system backbone configuration, a PM55 cabinet or PM255 cabinet is considered as one shelf. This is because the backbone in the back panel of the two shelves consists of the same physical wires and thus, one BackBone section. 3. Assign the DCC boards by means of PE command 4000. Use the following parameters:
50
PCT-Type: Circuits in HW addr.: Sig-Group:
02 (LCT) 02 ... 31 0920 for the DCCs in BackBone section 0 (see step 2) 0921 for the DCCs in BackBone section 1 (see step 2) 0922 for the DCCs in BackBone section 2 (see step 2) 0923 for the DCCs in BackBone section 3 (see step 2) 4. Enter the PARI (Primary Access Rights Identifier) of your DECT system. This is (worldwide) a unique number determined for your DECT system. Therefore you must enter it in the system in the peripheral data. This number consists of eight hexadecimal digits. However the number must be entered in decimal. Therefore convert the PARI (e.g. AA BB CC DD) into decimal values as follows: PARI HEXADECIMAL AA BB CC DD PARI DECIMAL UUU TTT SSS RRR
To enter the decimal value of the PARI, execute PE command 4400 as follows:
PROJPA:4400,092 PROJPA:4400,092 PROJPA:4400,092 PROJPA:4400,092 PROJPA:4400,092 PROJPA:4400,092 PROJPA:4400,092 PROJPA:4400,092 PROJPA:4400,092 PROJPA:4400,092 PROJPA:4400,092 PROJPA:4400,092 PROJPA:4400,092 PROJPA:4400,092 PROJPA:4400,092 PROJPA:4400,092 x,8,0; x,9,1; x,10,26; x,11,UUU; x,12,0; x,13,1; x,14,27; x,15,TTT; x,16,0; x,17,1; x,18,28; x,19,SSS; x,20,0; x,21,1; x,22,29; x,23,RRR;
Note: The PARI must be entered per PM1100 shelf, in the signalling group which is used by the DCCs in that shelf. Depending on the BackBone section, these signalling groups can be 0920, 0921, 0922 and 0923.
51
If the decimal values (UUU, SSS, TTT, RRR) of the PARI contain leading zeros, these can be omitted. 5. With the command PROJPA:4400 signalling data is stored in the PMC-MC. To download this data, perform a warmstart. 6. The address for each DCC must be determined and then entered into file EHWADCC.PDT. The EHWA - DNR relation must be defined in file EHWADNR.PDT in the DECT manager. Enter the license information in the file LICENSE.PDT. Consult the DECT Manager User Guide for more information.
3.2.2.
Projecting Example in an iS3030
In this example, two DCCs are projected in a iS3030 in the first shelf and the second shelf: First shelf : board position 01 Second shelf : board position 05
The following PE commands must be executed:

PROJPA:4000, 00102, 00131, 02, 0920; PROJPA:4000, 10502, 10531, 02, 0920;
Note that the PCT type for the DCC is:02(LCT) Now the PARI must be assigned. This number is different for each individual DECT system. In this example it is assumed that the PARI is 1000901C. The PARI must be entered in bytes in the signalling group data. This is done by executing PE command 4400 for all bytes which have to be changed:
PROJPA:4400,0920,8,0; PROJPA:4400,0920,9,1; PROJPA:4400,0920,10,26; PROJPA:4400,0920,11,16; PROJPA:4400,0920,12,0; PROJPA:4400,0920,13,1; PROJPA:4400,0920,14,27; PROJPA:4400,0920,15,0; PROJPA:4400,0920,16,0; PROJPA:4400,0920,17,1; PROJPA:4400,0920,18,28;
(16 = 10 Hex)
(0 = 00 Hex)
52
PROJPA:4400,0920,19,144; PROJPA:4400,0920,20,0; PROJPA:4400,0920,21,1; PROJPA:4400,0920,22,29; PROJPA:4400,0920,23,28;
(144 Dec. = 90 Hex)
(28 Dec. = 1C Hex)
Now perform a warmstart to activate the new signalling group data. Assign also DNRs to the circuits on the DCC boards. Check that the circuits on the DCC boards are in service.
3.3. 3.3.1.
PROJECTING IN SSW 740/800/805 Projecting Procedures
Projecting the DECT system can be done by means of a number of OM commands. The only board type that has to be projected is the DCC. The BBR only derives power from the backpanel and therefore does not have to be projected. To project the DCC boards, execute the following steps: 1. Make sure that the DCC board positions are defined according to the configuration rules. The BBR can be placed anywhere since it only derives power from the backpanel. 2. If the DCC boards are spread over more than one shelf, determine which shelf is the first DECT shelf (Back Bone section 0), which shelf is the second DECT shelf (Back Bone section 1) etc. This depends on the connection of the backbone cable from one DCC in the shelf to the backbone BBR. Each cable from the BBR is connected to a Back Bone section. There are four BackBone sections: Position BB0 BB1 BB2 BB3 BackBone section (see note) 0 1 2 3
Note: Although the PM55 and PM255 comprises two shelves, in the DECT system backbone configuration, a PM55 cabinet or PM255 cabinet is considered as one shelf. This is because the backbone in the back panel of the two shelves consists of the same physical wires and thus, one BackBone section. 3. Assign the DCC boards by means of OM command ASBRDS. Use the following parameters:
53
Board-type: Sig-Group:
HW-type:
15 0920 for the DCCs in BackBone section 0 (see step 2) 0921 for the DCCs in BackBone section 1 (see step 2) 0922 for the DCCs in BackBone section 2 (see step 2) 0923 for the DCCs in BackBone section 3 (see step 2) Can be omitted.
The DNRs/BSP-IDs which are assigned to the circuits on the DCC boards require Facility Class Mark 12 (SOPHO-SET). 4. Enter the PARI (Primary Access Rights Identifier) of your DECT system. This is (worldwide) a unique number determined for your DECT system. Therefore you must enter it in the system in the peripheral data. This number consists of eight hexadecimal digits. However the number must be entered in decimal. Therefore convert the PARI (e.g. AA BB CC DD) into decimal values as follows: PARI HEXADECIMAL AA BB CC DD PARI DECIMAL UUU TTT SSS RRR
To enter the decimal value of the PARI, execute CHPMPD on signalling group 9600 as follows:
CHPMPD:0, 9600; 1,1,UUU; 2,1,TTT; 3,1,SSS; 4,1,RRR;
; If the decimal values (UUU, SSS, TTT, RRR) of the PARI contain leading zeros, these can be omitted. Note: The signalling group 9600, which is read by the DCC signalling groups 0920, 0921, 0922 and 0923, only exists from PMC packages 405.6 (and 505.6) and up. If your system has an older PMC package, you must enter the PARI directly in the signalling groups 0920, 0921, 0922 and 0923, depending on the backbone sections used in your system. Also if you have more than one DECT cluster in your system, you must enter the PARI(s) directly in signalling groups 092x instead of 9600. Note that you must change this signalling group data in either signalling group 9600 or 092x. Do not change the signalling group data in both signalling groups.
54
5. With the command CHPMPD signalling data is stored in the PMC. To download this data, set the PMC(s) Out of Service and In Service again or perform a warm start. 6. In the CDOS/UNIX based DECT Manager, the address for each DCC must be determined and then entered into file EHWADCC.PDT. The EHWA - DNR relation must be defined in file EHWADNR.PDT in the DECT manager. Enter the license information in the file LICENSE.PDT. Consult the DECT Manager User Guide for more information. If you are using the Windows based DECT Manager, you must enter the DNRs in the "Configuration" screen. 7. Set the DCC boards in service. First SETINS the leftmost DCC(s) per shelf, after that the other DCC boards. 8. In SSW 741/800/805: Check the MSN configuration. It should be: Fixed MSN. For even EHWAs: MSN-digit 2 For odd EHWAs: MSN-digit 3 (default projecting)
3.3.2.
Projecting Example One Shelf DECT system in a SOPHO iS3050
A DECT system is to be installed in one complete PM1100 shelf of a SOPHO iS3050 with SSW 800/805. Suppose EHWA = (UUCCS) = 12011: meaning unit 12, cabinet 01, shelf 1. Add the DCC board to the configuration by using command ASBRDS. The signalling group is 0920. The PCT type is 15. The boards should be placed in the first position of unit groups 0 ... 7.
D C C
D C C
D C C
D C C
D C C
D C C
D C C
D C C
Slot positions
01 02 03 04
05 06 07 08 09 10
11 12 13 14 15 16 17
18
19 20 21 22
23
Figure 3-1 Installing a DECT system in SOPHO iS3050 The following projecting commands are required:
55
ASBRDS : 12011,01,15,0920; ASBRDS : 12011,03,15,0920; IIII ASBRDS : 12011,15,15,0920;
See DECT Manager User Guide for the required data in the EHWADCC.PDT file.
To assign the DNRs or BSP-IDs execute OM command CHDNRC for all the DNRs. An example is given:
CHDNRC : 5123,12011,01,03;
DNR 5123 is assigned to circuit 03 of the DCC board 01 in unit 12, cabinet 01, shelf 1, board position 01.
Now, the PARI must be entered in the signalling Group Data. Therefore continue with section 3.5. "EXAMPLE OF ENTERING THE PARI".
3.3.3.
Projecting a DECT system in a PM255 Shelf
A DECT system is to be installed in a PM255 shelf with SSW 800/805. Suppose EHWA = (UUCC) = 1201: meaning unit 12, cabinet 01. Add the DCC board to the configuration by using OM command ASBRDS. The signalling group is 0920 and the PCT type is 15.
56
D C C
D C C
Slot Positions
01 02 03
D C C
04 05 06 07
D C C P M C
08
C P U
09 10
Slot Positions
01 02 03 04
05 06 07 08
09
Figure 3-2 Installing a DECT system in a PM255 Shelf Projecting Commands:
ASBRDS : 12011,01,15,0920; ASBRDS : 12011,03,15,0920; ASBRDS : 12012,01,15,0920; ASBRDS : 12012,05,15,0920; To assign the DNRs or BSP-IDs execute OM command CHDNRC for all the DNRs. An example is given:
CHDNRC : 2024,12011,01,02;
DNR 2024 is assigned to circuit 02 of the DCC in board position 01 in shelf 1.
Now, the PARI must be entered in the signalling Group Data. Therefore continue with section 3.5. "EXAMPLE OF ENTERING THE PARI".
3.3.4.
Projecting a Four Shelf DECT system in a SOPHO iS3050
One DECT system containing four PM1100 shelves is to be installed in a SOPHO iS3050 with SSW 800/805. Suppose the EHWAs of the shelves are = (UUCCS) = 12011, 12012, 12013, 12014: meaning unit 12, cabinet 01, shelves 1 ... 4. The backbone sections are denoted as 0 ...
57
3. Add the DCC board to the configuration by using command ASBRDS. The signalling groups are 0920, 0921, 0922, 0923. The PCT type is 15. To connect the 4 backbones one BackBone Repeater (BBR) board is required, which only derives power supply from the backpanel. Backbone cables are available with a different length. Note that you may have only one cable of 5 meters. The other backbone cables must be shorter. In some configurations only cables of 3 meters or less are allowed, Refer to chapter 2. "HARDWARE INSTALLATION".
Shelf 12011 BB section 0
D C C D C C D C C D C C D C C D C C D C C D C C
Slot Positions Shelf 12012 BB section 1
01 02 03
D C C B B R D C C
04 05 06 07
D C C
08 09 10 11 12 13 14
15 16 17
18
19 20 21 22
23
01 02 03 04
D C C D C C
05 06 07 08 09 10 11 12 13
D C C D C C
14 15 16 17
18
19 20 21 22
23
01 02 03
D C C D C C
04 05 06 07
08 09 10 11 12 13 14
15 16 17
18
19 20 21 22
23
Slot Positions 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Figure 3-3 Installing a DECT system in SOPHO iS3050 Note: For exact backbone cabling instructions, see Chapter 2. "HARDWARE INSTALLATION"and Figure I-1 "Backbone cabling example, new cabinet with built-in
58
MDF", Figure I-2 "Backbone cabling example, new cabinet witout MDF", Figure I-3 "BackBone Cabling (Current Configuration)"and . Projecting Commands: ASBRDS : 12011,01,15, 0920,255; ASBRDS : 12011,03,15, 0920,255; IIII ASBRDS : 12011,15,15, 0920,255; ASBRDS : 12012,01,15, 0921,255; ASBRDS : 12012,03,15, 0921,255; ASBRDS : 12012,05,15, 0921,255; ASBRDS : 12013,01,15, 0922,255; ASBRDS : 12013,03,15, 0922,255; ASBRDS : 12013,05,15, 0922,255; ASBRDS : 12013,07,15, 0922,255; ASBRDS : 12014,01,15, 0923,255; ASBRDS : 12014,03,15, 0923,255; To assign the DNRs or BSP-IDs execute OM command CHDNRC for all the DNRs. An example is given:
CHDNRC : 4022,12011,03,02;
DNR 4022 is assigned to circuit 02 of the DCC board 01 in unit 12, cabinet 01, shelf 01, board position 03.
Now, the PARI must be entered in the signalling Group Data. Suppose the PARI given by Philips, uniquely belonging to your specific DECT system, is: 10009005(H). To enter the PARI execute CHPMPD as follows:
CHPMPD:0,9600; 1,1,16; 2,1,0; 3,1,144; 4,1,5; ;
16 = 10(H) 0 = 00(H) 144 = 90(H) 5 = 05(H)
59
With the command CHPMPD signalling data is stored in the PMC. To download this data, set each PMC in shelves with DCC boards, Out of Service and In Service again or perform a warm start. The PARI is broadcasted and can be readout at a number of handset types (depends on facilities in the handset). At the handset the PARI is displayed as part of the RFP-ID. The broadcasted general RFP-ID will be in this case 10009005XX(H) where XX(H) = 01, 03, 05, ... FF. XX(H) indicates one of the max. 128 (32 4) individual RFPs (see Appendix D . "HARDWARE CONFIGURATIONS") and 10009005 is the PARI.
3.4. 3.4.1.
PROJECTING IN Call@Net Projecting Aspects
To project the DECT System in a Call@Net system, you need top assign the DCC board(s), extension numbers, and you need to change settings. You will neven need to assign/project the BBR board, because it only derives power from the back panel. Projecting the DECT System can be done by means of a number of OM commands. The only board type that has to be projected is the DCC. The BBR only derives power from the backpanel and therefore does not have to be projected. Note: Projecting the DECT system in Call@Net is completely different compared to projecting DECT in SSW 805. In Call@Net the DCC(s) is projected in concentrated mode. The following overview explains the properties of this type of projecting: DCC Firmware Package. The firmware package of the DCC must be F4314x.xxx or higher or F4324x.xxx or higher. DCC Board type and Signalling Group. The DCC is projected with board type 16 and signalling groups 6204 (BB section 0) ... 6207 (BB section 3) "B-channel group" is automatically created. When you assign board type 16, a "B-channel group" is automatically created. A "B-channel group" is a group of 30 B-channels on the DCC board, that supports overflow between all channels. FCM "B-channel overflow" is not required for this type of B-channel overflow. The maximum number of "B-channel groups" (and therefore DCCs) is limited by the boundary "Max Number of DCCs". Default this boundary is set to 4! So, if you need to project more than 4 DCCs in the system, increase this boundary! Signalling Group 9600 Adaptation.
60
Assign "concentrated" mode in signalling group 9600. This means that bit 0 in byte 9 must be set to "1" by means of the OM command CHPMPD. If you are using E2 profile messaging, you need to set bit 4 in byte 9 to "1" as well. You need to enter the PARI in bytes 1 ... 4 as decimal values (see next section). Use Fixed MSN to assign more than one BSPs to a circuit. Fixed MSN is automatically assigned to the circuits. In Call@Net you can assign up to 6 fixed MSN digits to a BSP-ID by means of OM command "CHFMSN". The CPU in the ISPBX uses the MSN digits as identifier for the PP. So if the PP goes offhook , the DCC will send the MSN digits string to the CPU. In the CPU, these digits are converted to the actual DNR as extension number of the PP. Vice versa, when the CPU sets up a connection it will convert the dialled DNR into the MSN number on the DCC for setting up a connection. So, the MSN digits are the identifier for the PP which means that you must use this MSN number as the extension number of the PP in the DECT Manager. Especially when you want to use Desk-Sharing for the PP, the only fixed number for the PP will be the MSN number. If you assign a DNR to a DCC circuit by means of OM command CHDNRC, it will automatically copy the DNR digits to fixed MSN digits. Therefore you don't need to assign the MSN digits after have assigned to DNR. Used Circuits for DNRs (BSP-IDs). The circuits that can be used to assign BSP-IDs, are the following: 1 ... 15, 17 ... 31. Maximum number of extensions on one DCC. The maximum number of extensions on one DCC is determined by the maximum number of BSP-IDs per circuit. The maximum is determined by boundary 248 (Max. number of BSPs per extension circuit) which is 4 by default. This means that you can have a maximum of 4 x 30 ccts = 120 BSP-IDs per DCC. If the traffic value of the extensions is very low, you might increase this boundary and assign more BSP-IDs to the circuits. If you are using Desk Sharing, you need to set the boundary twice as high as the maximum number of BSPIDs that you want to assign to the circuits.
Note: For normal ISPBX operation, a maximum of 100 extensions per DCC is allowed. Higher numbers of extensions per DCC will result in unacceptable blocking chances.
3.4.2.
Projecting Procedure
To project the DCC boards in Call@Net, execute the following steps: 1. Make sure that the DCC board positions are defined according to the configuration rules. The BBR can be placed anywhere since it only derives power from the backpanel. 2. If the DCC boards are spread over more than one shelf, determine which shelf is the first DECT shelf (Back Bone section 0), which shelf is the second DECT shelf (Back Bone
61
section 1) etc. This depends on the connection of the backbone cable from one DCC in the shelf to the backbone BBR. Each cable from the BBR is connected to a Back Bone section. There are four BackBone sections: Position BB0 BB1 BB2 BB3 BackBone section (see note) Shelf in iS3050/3070/3090 0 DECT shelf connection to BBR connector BB0 1 DECT shelf connection to BBR connector BB1 2 DECT shelf connection to BBR connector BB2 3 DECT shelf connection to BBR connector BB3
Note: Although the PM55 and PM255 comprises two shelves, in the DECT system backbone configuration, a PM55 cabinet or PM255 cabinet is considered as one shelf. This is because the backbone in the back panel of the two shelves consists of the same physical wires and thus, one BackBone section. 3. Assign the DCC boards by means of OM command ASBRDS. Use the following parameters: Board-type: Sig-Group: 16 6204 for the DCCs in BackBone section 0 (see step 2) 6205 for the DCCs in BackBone section 1 (see step 2) 6206 for the DCCs in BackBone section 2 (see step 2) 6207 for the DCCs in BackBone section 3 (see step 2) Can be omitted.
HW-type:
If you get a message "Lack of space", check boundary 303 (Max. number of DCCs). The DNRs/BSP-IDs which are assigned to the circuits on the DCC boards require Facility Class Mark 12 (SOPHO-SET). This FCM is assigned automatically to the BSP-IDs. 4. Check the firmware package in the DCC. It should be F4314x.xxx or higher or F4324x.xxx or higher. 5. Change the setting in signalling group 9600 from un-concentrated to concentrated mode, by means of one of the following commands: For systems which do not use "Low Rate Message Service"
CHPMPD:0, 9600; 9,1,1;
; For systems using "Low Rate Message Service"

CHPMPD:0, 9600;
62
; 6. Enter the PARI (Primary Access Rights Identifier) of your DECT system. This is (worldwide) a unique number determined for your DECT system. Therefore you must enter it in the system in the peripheral data. This number consists of eight hexadecimal digits. However the number must be entered in decimal. Therefore convert the PARI (e.g. AA BB CC DD) into decimal values as follows: PARI HEXADECIMAL AA BB CC DD PARI DECIMAL UUU TTT SSS RRR
9,1,17;
To enter the decimal value of the PARI, execute CHPMPD on signalling group 9600 as follows:
CHPMPD:0, 9600; 1,1,UUU; 2,1,TTT; 3,1,SSS; 4,1,RRR;
; If the decimal values (UUU, SSS, TTT, RRR) of the PARI contain leading zeros, these can be omitted. For an example, see section 3.5. "EXAMPLE OF ENTERING THE PARI". 7. With the command CHPMPD signalling data is stored in the PMC. To download this data, set the PMC(s) Out of Service and In Service again or perform a warm start. 8. Check that the circuits on the DCC have MSN type: "MSN with fixed digits" assigned. Use OM command DIMSNP to display or CHMSNP to change the MSN type. "MSN with fixed digits" must have been assigned automatically, however, if the circuits have been projected before for another type of board, it might be the case that the MSN type is not correct. 9. Assign the BSP-IDs to the circuits 1 ... 15 and 17 ... 31 on the DCC by means of OM command CHDNRC. Be aware that you cannot use circuit 16! Also be aware that you can assign more than one BSP-IDs to one circuit but the number is limited by boundary 248 (Max. number of BSPs per extension circuit). Note: Do not cluster the BSP-IDs on a few circuits only, but spread them over the circuits as much as possible. Note: If you are using "DESK Sharing" functionality on the DECT PP, make sure that the boundary 248 is set to a higher value than the number of BSP-IDs that you have assigned to the
63
circuits. E.g. if you have 3 BSP-IDs assigned to each circuit, set boundary 248 to 10 BSPs per extension circuit! 10. The MSN digits will be copied automatically and used as MSN digits. So, under normal circumstances, you don't need to assign the fixed MSN digits as a separate action and you can skip this step in the procedure. However, if you need to change the MSN idigits, you must use OM command CHFMSN. Note, that the MSN digits must be used as extension number in the DECT Manager, because that is the identifier of the PP. Especially when you use Desk-Sharing, the MSN digits are fixed, while the actual DNR may change. 11. Set the DCC boards in service. First SETINS the leftmost DCC(s) per shelf, after that the other DCC boards. 12. Set the circuits on the DCC boards in service. 13. Assign the extension numbers in the DECT Manager via the "Configuration" tab.
3.5.
EXAMPLE OF ENTERING THE PARI
Suppose the PARI given by Philips, uniquely belonging to your specific DECT system, is: 10009005(H). To enter the PARI execute CHPMPD as follows:
CHPMPD:0,9600; 1,1,16; 2,1,0; 3,1,144; 4,1,5; ;
16 = 10(H) 0 = 00(H) 144 = 90(H) 5 = 05(H)
With the command CHPMPD signalling data is stored in the PMC. To download this data, set each PMC in shelves with DCC boards, Out of Service and In Service again or perform a warm start. The PARI is broadcasted and can be readout at a number of handset types (depends on facilities in the handset). At the handset the PARI is displayed as part of the RFP-ID. The broadcasted general RFP-ID will be in this case 10009005XX(H) where XX(H) = 01, 03, 05, ... FF. XX(H) indicates one of the max. 128 (32 4) individual RFPs (see Appendix D . "HARDWARE CONFIGURATIONS") and 10009005 is the PARI.
64
4.
-
IMPORTANT FIRMWARE ISSUES

F43040.XXX F43140.XXX F43240.XXX
Three main groups of firmware packages for the DCC are distinguished:
The differences and functionality of the various packages is given in table Table 4-1 "Properties of Firmware Packages and Relations to other Software.". also, this table gives you information whether you can used the firmware packages with the various SSW versions and DECT Manager versions Item: SSW 805 Call@Net DECT Manager interface Protocol V.24 Bit Rate Messaging E2 F43 040.XXX Yes Not supported V-modem / DCMIP 9600 bit/s Not supported F43 140.XXX Yes Yes V-modem / DCMIP 9600 bit/s Yes F43 240.XXX Yes Yes TCP/IP / SNMP Auto-detect Yes
Table 4-1 Properties of Firmware Packages and Relations to other Software.
65
Firmware Package
DECT Manager C-DOS/UNIX Yes Yes Not supported Under Windows Version 1.1.0 Version 2.X Yes Yes Not supported Version 3.X Yes Yes Supported via SNMP / TCP/IP protocol Yes Not supported Not supported
F43 040.xxx F43 140.xxx F43 24x.xxx
Table 4-2 Firmware Packages in relation to DECT Manager Versions. Note: Firmware package F4324x.xxx uses the SNMP protocol on the V.24 connection to the DECT Manager. Only the latest version of the Windows DECT Manager (version 3) supports this protocol. So, older DECT Manager versions cannot be used with this firmware. Note: You can never downgrade from version F43140.XXX to F43040.XXX nor from version F43240.XXX to version F43040.XXX. Downgrading may result in data corruption in the on-board FEPROM.
66
5.
5.1.
MIXED CONFIGURATION
GENERAL
Although this manual is valid for the 24-DCC and 32-DCC configurations only, it is possible to make a 32-DCC configuration that is a mix of 32-DCC and DCC-8 boards. However, you need respect the configuration rules as described in this chapter . You must also use the appropriate firmware and software packages. Besides this, it is wise to consult the DCC-8 manual first, to get familiar with the DCC-8, DCX and BBR-V2 boards.
5.2.
SUPPORTED HARDWARE
The following hardware supports mixed configuration: DCC-8 32-DCC (The 24-DCC is NOT supported!!!) BBR-V2 (See also the "note" below.) Peripheral Modules: PM55 (iS3010), PM255 (iS3030), PM1100 version 9562155 2220x only(!), CSM version 9562 155 5820x only.
Note: It is still possible to use the BBR instead of the BBR-V2. However, it is stongly recommended to use the BBR-V2 instead of the BBR, because the BBR-V2 supports RJ45 - RJ45 connections to the DCC-8. This manual assumes that you have a BBR-V2.
5.3.
MINIMUM SOFTWARE REQUIREMENTS
The following software/firmware supports mixed configuration: SSW805.32 or higher, or Call@Net (all versions) F46000.204 or higher for DCC-8 F43240.203 or higher for the 32-DCC DECT Manager version 3.0.5. which is available under: SMPC Version 4.3 or higher SSM410 Version 4.5.1 or higher
5.4.
HARDWARE CONFIGURATIONS
The configuration rules for the mixed configuration are depicted in diagram Figure I-12 "". Keep the rules in this diagram!!
67
It does not matter whether you install a DCC-8 or a 32-DCC in one of the allowed board positions. However, in case of an PM1100 or CSM shelf, it is strongly advised to install a DCC8 in the first position of the shelf instead of a 32-DCC. A DCC-8 in this position has the advantage of having a better backbone connection (RJ45 connector and on-board driver IC) to the BBR-V2.
Note: Make sure that you set the jumpers on the DCC boards according to the rules in diagram Figure I-13 ""!!!!!If you make a mistake in the jumper setting, the system operates fine on low traffic, but behaves unstable or unpredictable when it gets busy!!! The BBR-V2 can be placed in any available board position because it only derives power from the backpanel.
5.5.
HOW TO PROJECT
Projecting a mixed configuration is done in the same way as a homogeneous configuration (either 32-DCC or DCC-8). The only difference is the board type that you assign in the OM command ASBRDS. The following table gives an overview of the Board Types that should be used:
CPU Software SSW805 Call@Net
Board Type for 32-DCC 15 16
Board Type for DCC-8 13 13
Table 5-1 Board Types used in OM Command ASBRDS.
68
6.
IP PARAMETERS
Note: This chapter is only applicable for firmware F43240.XXX, because this firmware package supports IP over PPP. The IP address, subnet mask and default gateway address must be set correct before using the DECT Manager V.24 connection. Setting or displaying the IP configuration is done by means of the OM command: CHPERD (and DIPERD to display the parameters). Note: The IP parameters are stored in the EEPROM of the DCC. If you get a DCC from the store or factory, there is already an IP configuration on the board, which is presumably wrong for your network connection or DECT Manager. So, if you want to connect your DECT Manager to a DCC which comes from store or factory, you must always start with setting the IP parameters by means of an OM command.
6.1.
SETTING THE IP PARAMETERS
The parameters: IP address, subnet mask and default gateway can be set or changed by means of the OM command CHPERD. Note: The DCC board will reset after the command is entered!!! All existing voice connections via this DCC will be lost!!
CHPERD:2,<Shelf>,<Brd>; 8800; Set IP configuration Command identifier <IP Address>; The IP address must be entered here as eight hexadecimal characters. [<Subnet Optional! The subnet mask must be entered here as eight hexadecimal characters. Mask>; [<Default Optional! The default gateway address must be entered as eight Gateway>]]; hexadecimal characters. ; Enter password Enter the password for degradation level 1. The password is displayed as .... characters and not as stars. Error 40: Not This message should be interpreted as: "command executed". So it is not an error! yet implemented
6.2.
EXAMPLE OF SETTING PARAMETERS
The following gives an example of setting the IP address to the value 192.168.1.20 and the
69
subnet mask to the value 255.255.255.0. Note: The DCC board will reset after the command is entered!!! All existing voice connections via this DCC will be lost!!
CHPERD:2,<Shelf>,<Brd>; 8800; Set IP configuration Command identifier C0A80114; Hexadecimal presentation of the IP address. FFFFFF00; Hexadecimal presentation of the subnet mask ; Enter password system; .... Error 40: Not This message should be interpreted as: "command executed". So it is not yet implemented an error!
6.3. 6.3.1.
DISPLAYING THE IP PARAMETERS Displaying IP Parameters (All Firmware Versions)
Use the OM command DIPERD for displaying the IP parameters.

DIPERD:2,<Shelf>,<Brd>; 8700; Dispaly IP configuration Command identifier
The result of this command will be a string ending with 24 hexadecimal characters, which represents the IP address, the subnet mask and the default gateway.
<IP address><subnet mask><default gateway>
6.3.2.
Displaying IP Parameters in Firmware F43240.302 or higher
Firmware F43240.302 or higher allows you to read out the IP settings using OM command: .
DITCPC:<Shelf>,<Brd>;
However, you can still use DIPERD as explained in the previous subsection.
6.4.
EXAMPLE OF DISPLAYING PARAMETERS
The following gives an example of displaying the IP parameters of a DCC.
70
DIPERD:2,<Shelf>,<Brd>; 8700; Display IP configuration Command identifier
The result of this command will be a string ending with 24 hexadecimal characters, which represents the IP address, the subnet mask and the default gateway.
C0A80114FFFFFF00C0A801FE
You must divide this string into the following three parts:
C0A80114which is the IP address: 192.168.1.20 (decimal). FFFFFF00which is the subnet mask: 255.255.255.0 (decimal). C0A801FEwhich is the default gateway: 192.168.1.254 (decimal).
6.5.
DEFAULT IP PARAMETERS
The default IP parameters are active after first time installation of the firmware package on the DCC. When the firmware package is deleted and re-installed, the IP parameters are NOT reset to default values (so, they remain uneffected). The default IP parameters are as follows: Item IP Address Subnet Mask Default Gateway Hexadecimal
C0A80101 FFFFFF00 FFFFFFFF
Decimal
192.168.1.1 255.255.255.0 255.255.255.255
The IP address is a "Class C" address in the "Private Address" range. Accordingly, the subnet mask is also "Class C".
6.6.
HOSTNAME, USERNAME, PASSWORD
In the DECT Manager PC, you need to configure the IP connection to the DCC with firmware package F43 2 4x.xxx. During this configuration process, the Connection Manager Configurator (in DECT Manager PC) asks the hostname, the username and the password of the DCC. You need to enter the following in the Connection Manager Configurator:
71
Item Host name User Name
What to enter?
Example
Password
Enter IP address of the DCC board. 192.168.1.20 dasuser Enter the user name which is fixed in the DCC firmware. The fixed user name is "dasuser". Note, this is case sensitive!!! Enter any character as password. No check at all is x done.
6.7.
CHANGING IP ADDRESS VIA "TELNET"
Via a "Telnet" session you can easily change the IP address of the relay DCC. The advantage of changing the IP address via "Telnet" is that you can enter the address in decimal. Execute the following procedure to change the IP address: 1. Make sure you have dialled the DCC via the dialup adapter in Windows. 2. Start a "Telnet" session and open the connection to the IP address of the relay DCC. Use terminal type "VT100". 3. You should see:
login:
Login with the name:dasuser Now you are asked to enter a password. Enter:dasuser Note that the username and the password are case sensitive. 4. Now the connection is open. You will see the following prompt: 5. You can change the IP address by means of the command "ipconfig"
local>ipconfig <IP Address><Subnet_mask>[<Default_Gateway>]<cr> local>
Where: <IP Address> <Subnet_mask> [<Default_Gateway>] IP address in decimal (e.g. 192.168.1.20) Subnet Mask in decimal (e.g. 255.255.255.0) Optional! Gateway in decimal (e.g. 192.168.1.254)
Example: IP address 192.168.1.20 in Class C subnet and no gateway address:

local>ipconfig 192.168.1.20 255.255.255.0<cr>
6. The board will restart!!!!!! This means that the connection will be lost. You need to establish (dial) the connection again, to get access to the DCC.
72
7.
7.1.
USEFUL FUNCTIONALITY
CALL FORWARDING ON NOT REACHABLE
From ISPBX release SSW 805.24 the facility "Call Forwarding on not reachable" is available. This facility can be very convenient for DECT extensions. If the DECT extension is out of range or switched off, calls to this extensions can be forwarded automatically to another extension or external number.
CHCALF: <CF-TYPE>[, [<ORIG-BSP-ID>s/r ][,[<DEST-NUMBER>] [,<UNIT>]]]; <CF-TYPE>must be 8 for this facility.
The call will be forwarded after a timeout. By default after approximately 9 seconds. The timer is defined in byte 12 of the signalling group 9600. Default value is 33 (Hex) = 51 (Dec). The first digits represents the so-called Page Timer, default 3 seconds. The second digit represents the Page Retry Counter, default 3 times. This means that a call to a portable, which is switched off or out of range will be retired after 3 seconds. In total 3 retries will be done. To change this timer and counter, the signalling data must be changed. This must be done by means of OM command: CHPMPD. If you want to change the Page Timer to 1 second and the Page Retry Counter to 1 time, for example, you must change byte 12 to 11(Hex) = 17(Dec):
CHPMPD:0, 9600; 12,1,17; ;
After that, SETOUT and SETINS the related PMCs will perform a warmstart.
7.2.
TWINNING
From ISPBX release SSW 805.28 the facility "Twinning" is available. This facility can be very convenient for DECT extensions if implemented as follows: If somebody wants to be reachable on a hardwired extension as well as on a DECT extension, then a DECT extension twinned with a hard wired extension. If one of the DNRs is dialled, both extensions starts ringing. The call can be answered on one of the extensions.
73
If there are two different DECT systems on different locations, then one DECT extension can be subscribed to both systems. In this case the DECT extension has two diffrent DNRs. To make sure that the DECT extension will respond to both DNRs, you can twin the two different DNRs.
7.3. 7.3.1.
MESSAGING General
From ISPBX release SSW 805.29 on the facility "Messaging" is available. This facility allows you to send messages between PPs and between a CTI (CSTA) and PPs.
Note: For PP to PP messaging CSTA is not required. Therefore, if you want to implement PP to PP messaging only, you can skip the CSTA part in this section. To allow messaging, the system requirements must be as follows: The PP must support the "E2" "Low Rate Message Service" profile. (For the C922, it means that the PP must be equipped with firmware package >or equal11 as SW package together with package >or equal20.00 as EEPROM package. In the DCC, firmware package F43 1 40.101 or higher F43 2 4x.xxx or higher must have been installed. In the PMC, firmware package F14051.000 or higher must have been installed. In Signalling Group 9600 byte 9, bit 4 must be "1". In an un-concentrated DECT configuration, the other bits of this byte are all zeros. In a concentrated DECT configuration the other bits are "0" except for bit 0.
Besides the right software/firmware, you must have the following licenses in the Unit where the CSTA link is connected to: License 17 = "S0 bus link CSTA", and/or License 21 = "Ethernet Link CSTA" License 23 = "CSTA I/O Services (yes) License 24 = "Maximum number of simultaneous I/O registrations per Unit"
7.3.2.
Implementing Messaging in SSW 805 Oriented Systems
When implementing messaging, there are two options: Messaging with delivery only when extension is free. Messaging with guaranteed delivery, even if extension is in conversation.
74
PROCEDURE: Execute the following procedure to implement messaging in SSW 805 (from version .29 onwards):
Actions 1. Change byte 9 in signalling group 9600 as follows:
CHPMPD:0, 9600; 9,1,16; ;
2. SETOUT and SETINS the related PMCs will perform a warmstart of the shelf. 3. Assign a second DNR (this can be the same DNR as the existing voice DNR) with BSPT = 0 (64 kb/s unrestricted) to the DECT extensions (PPs) with messaging. 4. If you want to make sure that a message is also received if the DECT extension (PP) is in voice conversation, you must assign facility class mark 50 (B-channel overflow) to both BSP-IDs. In that case the message is sent to the extension via the odd (second) B channel in the circuit pair. If you want to make sure that the message will always be sent to the extension, then you must not use the odd circuit for another extension; do not assign a DNR to that circuit. This means that one circuit pair is required for one extension (PP).
75
DNR BSPT Voice Data 1500 - 95 1500 - 0
DCC
EVEN CCT ODD CCT Handset 1500
Message can be delivered, only if it is free DCC Voice Data 1500 - 95 1500 - 0
Overflow
If handset (1500) is in conversation mode, a message can still be received via overflow (FCM 50) via the odd B-channel. This channel must be idle. If not idle, a message cannot be received. DCC Voice Data 1500 - 95 1500 - 0
Overflow
If handset is in conversation mode, a message can still be received via the odd B-channel. This odd B-channel is not used for another extension, so a message can always be received.
Figure 7-1 B-Channel Overflow for Messaging 5. Messaging from PP to PP, uses the Alternative Destination Dial Type. So, make sure that the DNRs of the extensions (PPs) are assigned as internal numbers in the Alternative
76
Destination Dialling tree. 6. Now messaging from PP to PP will work. However if you want to use messaging via CSTA, go to section 7.3.4. "Messaging via a CSTA Link"
PROCEDURE: Example of implementing messaging on an existing extension (DNR = 1500) with overflow for quaranteed delivery:
CHPMPD:0, 9600; 9,1,16; ;
2. Activate the projected data by means of SETOUT and SETINS the related PMCs.
SETOUT:<Shelf>,<Brd>; SETINS:<Shelf>,<Brd>;
3. Assign a second DNR (this can be the same DNR as the existing voice DNR) with BSPT = 0 (64 kb/s unrestricted) to the DECT extensions (PPs) with messaging.
CHDNRC:1500-00,<Shelf>,<Brd>,<Even-Circuit>;
4. If you want to make sure that a message is also received if the DECT extension (PP) is in voice conversation, you must assign facility class mark 50 (B-channel overflow) to both BSP-IDs.
ASFACM:50,1500-00; ASFACM:50,1500-95;
In that case the message is sent to the PP via the odd (second) B channel in the circuit pair. If you want to make sure that the message will always be received by the extension, then you must not use the odd circuit for another extension; do not assign a DNR to that circuit. This means that one circuit pair (even and odd circuit) is required for one PP. 5. Messaging from PP to PP, uses the Alternative Destination Dial Type. So, make sure that the DNRs of the PPs are assigned as internal numbers in the Alternative Destination Dialling tree.
ASBLOCK:<Alt.Dest.Dialling_Tree>,1,<TRFC>,4,10;
6. Now messaging from PP to PP will work. However if you want to use messaging via CSTA, go to section 7.3.4. "Messaging via a CSTA Link"
7.3.3.
Implementing Messaging in Call@Net Oriented Systems
Messaging is enabled by means of setting bit 4 in byte 9 of signalling group 9600 to "1". For the PP that are used for messaging you must also assign a second BSP-ID with BSPT = 64 kb/s unrestricted.
77
The second BSP-ID can be assigned to the same circuit on the DCC as where the voice BSPID of that PP was assigned. This does not mean that that circuit is actually used for the messaging or voice, because the DCC regards its circuits as a pool of B-channels from which a circuit/channel is chosen. Therefore, if a message needs to be send to the PP while in conversation, the DCC/CPU selects a free circuit on the DCC to send the message. As long as there is a free circuit available on the DCC, the message will be delivered. The second BSP-ID must also be assinged to the same MSN digits as for the voice BSP-ID, because the MSN digits are the real identifier (in the ISPBX) for the PP. In the following figure the structure for messaging is depicted.
Linked Via CHFMSN
DCC (concentrated)
DNR BSPT Voice Data 1500 - 95 1500 - 0 MSN 1500 Handset 1500
B-channel Pool
PROCEDURE: Execute the following procedure to implement messaging in Call@Net:

CHPMPD:0, 9600; 9,1,17; ;
2. SETOUT and SETINS the related PMCs will perform a warmstart of the shelf. 3. To assign a new PP with voice and messaging capabilities, you must assign a BSP-ID twice to this extension: one with BSPT voice (95) and one with BSPT = 64 kb/s unrestricted (0). It is advised to keep the DNRs in the two BSP-IDs the same.
78
Example of assigning a PP with voice and messaging: Assumptions: DNR = 1500 on EHWA = 1011,1,1 To assign the voice BSP-ID, execute the following commands:
CHDNRC:1500-95,1011,1,1; CHFMSN:1500-95,1500;
To assign the data BSP-ID, execute the following command:

CHDNRC:1500-0,1011,1,1; CHFMSN:1500-0,1500;
Because the DCC is operating in concentrated mode, you could assign a second BSP-ID pair to the same circuit. 4. Messaging from PP to PP, uses the Alternative Destination Dial Type. So, make sure that the DNRs of the PPs are assigned as internal numbers in the Alternative Destination Dialling tree. 5. If you want to make sure that a message is also received if the DECT extension (PP) is in voice conversation, you must make sure that there is always one circuit free/available on the DCC. Messaging with guaranteed delivery Messaging with guaranteed delivery is only possible as long as you are sure that there is always at least one circuit (B-channel) on the DCC free/available for sending a message. Because the DCC uses its circuits as a pool of circuits/B-channels, it can select any circuit for sending the message to a particular PP. If you accept a delivery service of 99,5% successful, you can use the Erlang / Blocking probability tables as for normal trunk traffic with a blocking probability of 0,5 %. In that case you must know the Erlang values of the PPs and make the calculation as for 30 lines (circuits/B-channels).
ASBLOCK:<Alt.Dest.Dialling_Tree>,1,<TRFC>,4,10;
7.3.4.
Messaging via a CSTA Link
The procedures for implementing messaging, enables the DECT System to handle "E2 low data profile messages". These messages can be sent between PPs but also between a Message Server and the PP. The Message Server will be connected to the ISPBX via a CSTA link. To use messaging via CSTA, the you must check that the following boundaries and timer are set to a appropriate values and if necessary reproject the boundaries and timer: Boundary 276 = Max. number of CSTA links per per unit Boundary 326 = Max. number of local CSTA data paths Boundary 327 = Max. number of global CSTA data paths Boundary 328 = Max. number of local CSTA IO registrations Boundary 329 = Max. number of global CSTA IO registrations Timer 207 = CSTA command guarding timer
79
7.4. 7.4.1.
DECT MOBILITY IN iSNET MAN General
System Requirements: Call@Net 2.8 PMC firmware packages F14100.801 or F15100.801 DCC firmware packages: F43140.206 or higher and F43240.xxx.
DECT Mobility allows the DECT user to roam from one DECT cluster to another other, using the same extension number (DNR). The DECT clusters must be in the same ISPBX unit or in the same iSNet MAN. An iSNet MAN is a fully integrated network, consisting of iS3070/3090 units only. For DECT Mobility all units within the iSNet MAN must run Call@Net 2.8 or higher. Note that it does not support automatic handover! The feature is enabled by FCM 70 (iSNet MAN DECT Mobility entitled). When multiple DECT cluster sites are being used, the calls will automatically be routed to the DECT cluster where the portable is reachable at that moment. When a DECT user moves from one DECT cluster to another, the ISPBX will be updated when the DECT portable comes in reach of an RFP of the other DECT cluster. The DECT cluster can be within the same ISPBX, a different ISPBX-Unit or in a remote PM of one of the ISPBX-Units of a Multi-Unit iSNet MAN network. All calls to a BSP-ID (DNR) with FCM 70 will automatically be routed through the DECT cluster to the RFP where the portable is reachable. Figure 7-2 "Example of DECT Mobility." illustrates the move of a portable from one DECT cluster to a another one. For example: considering that the portable with DNR 1000 has moved from DECT cluster 1 to DECT cluster 2, the radio in DECT cluster 2 will inform the ISPBX that the portable with DNR 1000 is "in reach" of DECT cluster 2 and the ISPBX will route all the calls to DNR 1000 on DECT cluster 2. This type of DECT mobility is called: INTRA UNIT MOVE of a DECT portable.
80
DECT Cluster 1
Unit 1 IMP
Unit 2
DECT Cluster 3 1001
1000
Intra Unit Move DECT Cluster 2 1001 1000 Inter Unit Move
Figure 7-2 Example of DECT Mobility. Similarly, when a DECT portable with DNR 1001 moves from DECT cluster 2 to DECT cluster 3 in the above figure, the radio of DECT cluster 3 will inform the ISPBX that DNR 1001 is "in reach" of DECT cluster 3 and the ISPBX will route all calls to this DNR on DECT cluster 3. Though DECT cluster 3 belongs to a different unit, calls to DNR 1001 will be routed through the IMP-network between the Units. This type of DECT mobility is known as INTER UNIT MOVE of a DECT portable.
7.4.2.

Preconditions
DECT Mobility requires a desksharing license. For each DNR having FCM 70, a desksharing license is required in each Unit where the DNR can be moved to. BMLOCK may not have been set. If set, the intra/inter unit move does not work. If a lock is required, set an OMLOCK instead.
7.4.3.
Execution
When a DECT portable is switched "ON" or when a DECT portable enters the area of the DECT-cluster, then the DCC sends a trigger to the CPU notifying that the DECT terminal is within reach. This trigger is used to determine whether the DECT portable requires a DNRmove. A DNR move means: moving the DNR from a DCC in a DECT cluster to another DCC in another DECT cluster. (The handset must have been subscribed to both DCCs with the same extension number.) The DNR with its data is automatically moved to the new DCC. Also the message waiting is
81
updated. When the DNR is already located at the DCC of the current DECT cluster, then no DNR-move is attempted. In the case of a failure when moving between two Units in a MAN, the portable uses the Basic DNR (if projected). When the user then tries to make a call, "diversion active" tone instead of internal dial tone is given. The recovery must be done by the user. Switching the portable off and on, will trigger a new attempt for a DNR-move.
7.4.4.
Interaction with other Facilities
Interactions with other facilities A number of features (CFDA-relations, FCMs and message waiting indication) are moved with the DNR in case of DECT Mobility, based on OM command CHDNRC. The following features have a different behaviour together with FCM 70: Activated Desksharing DNR at a DECT Mobility handset. Activation of a Desksharing DNR at a DECT Mobility handset is not supported. DNR with both FCM 70 (iSNet MAN DECT mobility entitled) and FCM 57 (Desksharing Entitled). Example: a handset with DNR 1000 has FCMs 70 (iSNet MAN DECT mobility entitled) and FCM 57 (Desksharing entitled). When the handset is outside a cluster (not reachable), desksharing could be activated on a fixed extension (e.g. DNR 2000) by dialling from that fixed extension *911000. From now on, calls for DNR 1000 are routed to the fixed terminal. When the handset becomes in reach of a DECT cluster, DNR 1000 will be moved from the fixed extension to the handset and the fixed terminal will get its original DNR 2000. If the DNR is moved to another DECT cluster, all ARBs (automatic ring back) to and from the DNR are cancelled. When another DECT cluster is entered by a busy handset, the DNR is not moved (a call to the handset now is handled as not reachable). When the user terminates the call and goes off-hook again to make another call, the basic DNR (if present) is used and the user gets diversion tone. After switching off and on the handset, an attempt will be made to move the user's DNR to the new DECT cluster. COB (Camp on Busy) and Call Waiting When a DECT handset is in conversation and becomes out-of-reach of its current DECTcluster then the current call will be cleared. Calls waiting in the COB and call-waiting queue will be handled as calls to a non-reachable DECT extension. As long as there is a call in the COB queue or call waiting COB place, the extension is busy and the DNR cannot be moved. Executive/Secretary
82
The DNR of a Executive/Secretary can not be moved to another unit. Groups The DNR of a group-member can not be moved to another unit. Special extensions (MCNE/SCNE/INE/PLE/OVE) A DNR having FCM 70 (iSNet MAN DECT mobility entitled) can not be made a special extension and vice versa. IABD/LENR IABD/LENR data is moved over the unit boundary with the DNR provided that there is sufficient space in the target unit. If there is insufficient space the IABD/LENR data is lost. DND (Don't disturb) If a DNR is moved to another unit, temporary DND is reset.
7.4.5.
Implementing DECT Mobility
PROCEDURE: Implementing DECT Mobility in Call@Net Systems Without Using SARI

Actions 1. Make sure that you have two DECT clusters in one ISPBX, either in the same unit or in a unit and in a Remote PM or in an iSNet MAN (Multi Unit) system. (The procedure is the same.) The two DECT clusters must have different PARIs! One DECT cluster is called DECT cluster A, the other is called DECT cluster B. 2. In the ISPBX where you have your DECT cluster A, you must assign the DNR by means of OM command CHDNRC. Assign the DNR of the handset to one of the circuits of the DCCs to which the handset must be subscribed. e.g. CHDNRC:1500,1011,1,1; If the handset is also used for E2 messaging, also assign the same DNR for the second time to the DCCs to which the handset is subscribed, but now with BSPT = 00. e.g. CHDNRC:1500-00,1011,1,1; 3. Check the Fixed MSN digits of the BSP-ID. These digits have to be the same as the DNR and have to be the same as the extension number that you are using in the DECT Manager (for both DECT clusters the same). e.g. DIFMSN:1500-95; and DIFMSN:1500-00; The Fixed MSN digits of must be 1500 in this example. 4. Assign FCM 70 (iSNet MAN DECT Mobility entitled), FCM 57 (Desksharing Entitled) and FCM 66 (Desk Sharing Protected) to the DNR. Note that when you use two BSP-IDs (voice and data for messging) with the same DNR, you must assign these FCMs to BSP-ID 99. e.g. ASFACM:57&66&70,1500-99;
83
5. Set Call Forwarding when not Reachable for the DNR of the handset to a wired extension. This avoids that a call remains in the COB queue of the extension when it is not within reach. (If a call remains in the COB queue, it the DNR cannot be automatically moved to a DCC.) e.g. CHCALF:8,1500-95,1000; 6. Check that the BMLOCK has not been set. This command must result in "BMLOCK not set". If the BMLOCK was set, enter the name and remove the BMLOCK. If BMLOCK is set, the ISPBX cannot automatically move the DNR to the other Unit. 7. Start up the DECT Manager for DECT cluster A. 8. Enter the extension number (e.g. 1500) of the handset in the "Configuration" tab in the DECT Manager for DECT cluster A. Subscribe the handset. 9. Check if you can make a call via this handset. It should be possible now. 10. Close the DECT Manager for DECT cluster A and go to DECT cluster B. 11. Enter thesameextension number (e.g. 1500) of the handset in the "Configuration" tab in the DECT Manager for the second DECT cluster. Subscribe the handset to the DECT cluster B. (This is possible, even when you do not have the DNR assigned in the ISPBX.) Now you have two subscription records in the handset. Switch the handset to automatic subscription selection (if the handset supports it). 12. Switch the handset "OFF" to make sure that it is not "within reach" of one of the RFPs in DECT cluster A. Make sure that it is within reach of DECT cluster B. 13. Switch the handset "ON" and check that you can receive calls on the extension using DECT cluster B. The DNR is automatically moved from the DCC in DECT cluster A to the DCC in DECT cluster B.
BMLOCK:0;
PROCEDURE: Implementing DECT Mobility in Call@Net Systems Using SARI

Make sure that you have two or more DECT clusters in an iSNet MAN (Multi Unit) system. The DECT clusters (systems) must have different PARIs. However the PARI of one DECT cluster (referred to as DECT System A) must be used as SARI in the other DECT System(s). In this procedure we assume that you have only one second DECT cluster, system B. However, if you have more than two DECT clusters in your mobility configuration, you must use the procedure for cluster B also for the other DECT clusters. Actions 1. In the ISPBX where you have your DECT cluster A, you must assign the DNR by means of OM command CHDNRC. Assign the DNR of the handset to one of the circuits of the DCCs to which the handset must be subscribed.
84
2.
3.
4.
5.
e.g. CHDNRC:1500,1011,1,1; If the handset is also used for E2 messaging, also assign the same DNR for the second time to the DCCs to which the handset is subscribed, but now with BSPT = 00. e.g. CHDNRC:1500-00,1011,1,1; Check the Fixed MSN digits of the DNR. These digits have to be the same as the DNR and have to be the same as the extension number that you aregoing to use in the DECT Manager (for both DECT clusters the same). e.g. DIFMSN:1500-95; and DIFMSN:1500-00; The Fixed MSN digits of must be 1500 in this example. Assign FCM 70 (iSNet MAN DECT Mobility entitled), FCM 57 (Desksharing Entitled) and FCM 66 (Desk Sharing Protected) to the DNR. Note that when you use two BSP-ID (voice and data for messging) with the same DNR, you must assign these FCMs to BSP-ID 99. e.g. ASFACM:57&66&70,1500-99; Set Call Forwarding when not Reachable for the DNR of the handset to a wired extension. This avoids that a call remains in the COB queue of the extension when it is not within reach. If a call remains in the COB queue, the ISPBX cannot automatically move the DNR to the other Unit. e.g. CHCALF:8,1500-95,1000; Check that the BMLOCK has not been set.
BMLOCK:0;
This command must result in "BMLOCK not set". If the BMLOCK was set, enter the name and remove the BMLOCK. If BMLOCK is set, the ISPBX cannot automatically move the DNR to the other Unit. 6. Startup the DECT Manager (Version 3.0.5 or higher) for DECT cluster A. Go to the "Boards" menu and execute a" Backup". Now the SARI of you system is copied to the DECT Manager's database. 7. Subscribe the handset with extension number 1500. Make sure that you subscribe this handset to the same DCC to which you have assigned the DNR by means of the OM command CHDNRC. 8. Go to the "File" menu in the DECT Manager (Version 3) and select "Copy and Move Subscription" 9. Select the option "Move Subscription outside the system". 10. Move the subscription record of the handset that you have subscribed to a floppy. Just follow the steps on the screen. 11. Again go to the menu "Copy and Move Subscription" in the "file" menu. and select "Import". Import the subscription record again into your DECT cluster A. Again, just follow the steps on the screen. Note: You need this floppy with the subscription file also in DECT cluster B. 12. Switch the handset "off" and "on" again.
85
13. Try to setup a call to and from the handset. It should work! 14. Close the DECT Manager for DECT cluster A. Go to DECT Cluster B. 15. If not yet done, enter the PARI of DECT cluster A, into the DECT cluster B but now as SARI. Use the OM command:CHPMPD:0,9600,,,<UNIT>;to do this. Enter the SARI into byte 17 ... 20. See section G . "CUSTOMIZING SYSTEM PARAMETERS". e.g. for SARI 1000900A
CHPMPD:0,9600,,,<UNIT>; <ITEM-NR>,<BIT/BYTE>,<DATA>:17,1,16; <ITEM-NR>,<BIT/BYTE>,<DATA>:18,1,0; <ITEM-NR>,<BIT/BYTE>,<DATA>:19,1,144; <ITEM-NR>,<BIT/BYTE>,<DATA>:20,1,10;
16. Execute a warm start in the Unit(s) where you have entered the SARI. 17. Make sure that you have DECT Manager Version 3.0.5. or higher. Start the DECT Manager for DECT cluster B. 18. Go to the boards "Tab" and click the button "Backup". Now the SARI is copied into the database of the DECT Manager. 19. Go to the "File" menu in the DECT Manager and select "Copy and Move Subscription". Select "Import". Make sure that you have the floppy with the subscription data file of DECT cluster A. Import the subscription record again into your DECT cluster B. Just follow the steps on the screen. 20. Switch the handset "OFF" and "ON" again. 21. Try to setup a call to and from the handset. It should work now on DECT cluster B. The DNR is automatically moved from the DCC in DECT cluster A to the DCC in DECT cluster B. 22. Close the DECT Manager for DECT cluster B.
7.5. 7.5.1.
DECT MOBILITY IN iSNET WAN General
DECT Mobility in iSNet WAN can be done over a DPNSS link or over a QSIG link. The implementation is nearly the same, however, there are some small difference. This chapter is valid for both: DPNSS and QSIG. The differences are denoted clearly. System Requirements for DECT Mobility WAN over DPNSS: - Call@Net 2.9 - PMC firmware packages F14100.901 or F15100.901 - DCC firmware packages: F43140.206 or F43240.xxx.
86
System Requirements for DECT Mobility WAN over QSIG: - Call@Net 2.10 - PMC firmware packages F14101.001, or F15101.001 - DCC firmware packages: F43140.206 or F43240.xxx.
DECT Mobility for iSNet WAN (Wide Area Network) allows the DECT user to move from a DECT cluster on one node to another cluster on another node, using the same extension number. The nodes are part of a WAN. The feature is enabled by FCM 71 (iSNet WAN DECT Mobility). Note that it does not support automatic handover! The figure below gives an example of a DECT WAN move. A DECT portable with DNR 1001 moves from DECT cluster 2 in node 1 to DECT cluster 3 in node 2 (see 'A' in the figure). The DNR in node 2 is the same. Let us assume that the portable with DNR 1001 moves back from node 2 to node 1, not to DECT cluster 2 but to DECT cluster 1 (see 'B' in the figure). In this case, the DECT WAN move comprises also a DECT MAN move (see 'C' in the figure).
B
DECT Cluster 1 Node 1 DPNSS or QSIG 1001 1001 Node 2 DECT Cluster 3 1001
C
DECT Cluster 2 1001 1001
Figure 7-3 DECT WAN move comprising a DECT MAN move
7.5.2.
Mixed DPNSS and QSIG Networks
It is possible to apply DECT Mobility in a network with mixed connections: DPNSS and QSIG. You must make sure that the DPNSS nodes operate with Call@Net 2.9 or higher and that the QSIG nodes operate on Call@Net 2.10 or higher. The following figure shows the configuration of a connection with a transit node (branching node).
87
Node X QSIG NAC=260 Originator for WAN update QSIG
Node Y QSIG NAC=262 Transit Node DPNSS
Node Z DPNSS NAC=28 Destination for WAN update
Figure 7-4 DECT WAN move in a mixed DPNSS - QSIG Network with transit. In the example of the above figure, there are three nodes: Node X, which is a QSIG Node. In this example the node from where the WAN update is originated. Node Y, which is the transit node. The WAN update goes via this node to Node Z. Note that the WAN update request comes in via a QSIG link and goes out via a DPNSS link. This is called a "Branching" or "Gateway" node. Node Z, which is the destination node for the WAN update. This is a DPNSS node.
DECT Mobility WAN makes use of the free numbering in DPNSS or QSIG. If a DECT WAN move takes place the free numbering table must be updated automatically. In the figure above, an update request is sent from Node X to Node Z. The originating Node X, sends an update request to node Y over a QSIG link. In Node Y this request is translated into an update request over DPNSS and send to Node Y.
7.5.3.
Preconditions
All DECT extensions which are subject to DECT WAN Mobility must have a subscription on each DECT cluster where they can be moved to: in each subscription, the same extension number should be used. In general the same set of FCMs, traffic classes and other extension data should be defined in each node, but it can be different in another node. Free numbering license in each Node. 'A Free Numbering license must be present in each unit of each node': not only in the nodes which have a DECT cluster. Each of the nodes having a DECT-cluster must have a list of node identities which need to be updated in case a DECT WAN move takes place. NESYSOP 40 must be set to 'true' in each node : a closed numbering scheme is required. NESYSOP 86 must be set to 'true' in each node : 'Unique ClusterId is required. LOSYSOP 106 must be set to 'true' in each node : 'Free Numbering'. NEBOUND 307 (maximum number of free numbering entries) should be at least equal to the maximum number of DECT extensions with FCM 71. The number of nodes in the WAN network must be equal or less than specified by NEBOUND 382 (maximum number of nodes in a WAN network).
88
The number of OM datablocks (LOBOUND 353) should be configured such that in the idle system there are at least 45 free datablocks free. In case DECT MAN moves are involved as well, desksharing licenses are necessary for the extensions. BMLOCK may not have been set. If set, the WAN move does not work. If a lock is required, set an OMLOCK instead. QSIG only. NEBOUND 348: maximum percentage of ISDN Virtual Calls. This boundary defines the maximum percentage to which ISDN / QSIG calls can take up flow resources in a unit as well as to or from a PM. Default value is 20%. QSIG only. NEBOUND 359: QSIG transit PINX counter. This boundary defines the maximum number transit nodes that a QSIG call may pass through. This is used a a protection mechanism, to avoid that an incorrectly routed call is going round in a loop. License for QSIG: All QSIG nodes that participate in the DECT WAN mobility must have a license for iSNet QSIG.
Note: DPNSS/QSIG does not support E2 messaging. Therefore E2 messaging does not work for DECT WAN!!!
7.5.4.
Execution
When a DECT portable is switched OFF and ON or when a DECT extension user enters the area of a different DECT Cluster belonging to a different node, a trigger is sent to the CPU via the DCC board notifying that the DECT extension has become 'in-reach'. In this case a WAN move is performed. This WAN move consists of autonomous execution of OM command CHFDNR in each node of the network. The free number table will be updated with the new location of the DECT portable. When the user goes Off-hook while the DECT WAN move update is going on, Basic DNR tone is given. It can also happen that a MAN move is part of a WAN move. The DECT extension moves from one node to another node and also enters a DECT cluster area different from the DECT cluster at which its DNR is located. In this case the DECT extension requires a MAN move along with a WAN move. After the move is complete, and all updates are successful, calls can be made. For a WAN move comprising of a MAN move, a Desksharing licence needs to be present along with the Free-numbering license on all the concerned nodes. An update notification is sent to all the nodes in the network implying that the new owner of the Free DNR is the node that is sending the notification. The number of such simultaneous notifications sent to the nodes depends on the value of LOBOUND 383 (Number of
89
simultaneous virtual notification calls for free DNR location update per WAN mobility) for DPNSS and also NEBOUND 348 for QSIG (maximum percentage of ISDN virtual calls). When no parallel set-up for the notifications is needed, LOBOUND 383 is set to 1. This results in sequential set-up of the notifications. In case the notifications are delayed e.g. due to congestion, after certain time (NETIMER 223 'DECT mobility update retry timer') the notification is sent again. When, in the failure situation, the DECT portable goes off hook, Basic DNR tone is given. The portable may also be switched OFF and ON. It is then checked if there were any failures for that DNR and if so, the network is updated (again).
7.5.5.
Interactions with other facilities
The following features have a different behaviour together with FCM 71: When the user moves to another PBX, ARB relations are not moved along, but also not cancelled. They will expire, depending on the timer values of NETIMER 9, 182, 183 and 184. When the user moves to another PBX, the message waiting indication is not moved along. The message waiting indication shown is the last message waiting status registered at the PBX to which the user moved to. However a new message waiting status entered through dialling of the 'message waiting LED on' prefix (type 0, 1 or 2) is routed to the location of the free number. A new message waiting status entered at a SysManager is registered with the DNR at the connected local PBX When the user's DNR is a group member and the user has moved to another ISPBX, then this DNR is still selected for a group call. Since the DECT portable is not reachable, the call is offered to the group again. Note that with a fixed or longest idle hunting scheme the call to the group will eventually fail after a number of attempts limited by the NEBOUND364 (max number of call forwarding not reachable). When the secretary has a DECT portable with Free DNR and FCM 71, and the free number has been moved to another ISPBX, then short code dialling from executive to this secretary DNR end up in local DNR : the call is handled as a call to a not reachable DECT extension. Permanent assigned features (e.g. CFDA-relations, FCMs) and dynamically assigned features (such as FM preparations/activations, DND activations) are not moved with the DNR to the other node. That means that the features for a DNR must be configured on all nodes the DNR may be moved to. For example DNR 1001 could have configured a Follow Me to DNR 1212 in node 1 and a FM to 3131 in node 2. The activation of a Desksharing DNR at a DECT Mobility handset is not supported; If the user is moved to another node, a special extension call is handled as a call to a not reachable extension.
90
If in an Executive/Secretary configuration, the portable of the secretary is moved to another node, diversions from executive to the secretary will end up in a "not reachable" condition.
Note: If a WAN move takes place, e.g. a handset moves from Node A to Node B, while the DPNSS or QSIG link is down, the free numbering table in Node A is not updated. After the link is up again, NO automatic update takes place, resulting in inconsistancy in free numbering tables in the Nodes. If you call the handset in Node B (where the handset is after the move), there is no problem. However, if you make a call to the handset from Node A (where the handset came from), the call will fail, because the handset is still in the free numbering table in Node A, but the handset is not there anymore. To solve this inconsistency, first make sure that the link is up again, then switch the DECT handset OFF and ON in Node B. Free Numbering Table is updated and made consistent. Alternatively, move the DECT handset back to Node A (where it came from) and switch it OFF and ON again. Now the tables are updated and consistent again.
7.5.6.
Implementing DECT Mobility
Implementing DECT Mobility can be done in two ways: Subscribing a handset in all clusters involved. You subscribe the handset to the PARIs of the clusters. This means that you do not use a SARI Using a SARI and the copy subscription functionality in the DECT Manager
Both options are descibed in the following procedures. Choose the procedure that is applicable for your system.
PROCEDURE: Implementing DECT Mobility in Call@Net Systems Without Using SARI

Preconditions The following assumptions are made: The precondions listed in 7.5.1. "General"and 7.5.3. "Preconditions"are met. Two DPNSS or QSIG Nodes are involved. Node 1 has cluster ID 5, Node 2 has cluster ID 6. If your system comprises more than two Nodes, repeat the actions for Node 2 also in the other Nodes! The numbering scheme comprises number ranges 1xxx for Node 1 and 2xxx for Node 2. In each Node, one DECT cluster is present. In Node 1 there is DECT cluster A, in Node 2 there is DECT cluster B.
91
The extension number for the DECT handset is a "free number" in the DPNSS or QSIG network, which means that it may not be in the number range of Node 1 or Node 2. The first digit may not be a Network Access Code in the DPNSS or QSIG network. In this example we have chosen number 3000 for the DECT extension that is going to be used for WAN mobility. Actions 1. Make sure that your DPNSS or QSIG network has a "closed" numbering scheme! 2. Make sure that you have an up and running DECT cluster in the DPNSS or QSIG nodes that you want to include in your DECT WAN configuration. The DECT clusters must have different PARIs. 3. Assign the DNR (3000) to a circuit on a DCC in Node 1. (Later in this procedure, you must subscribe the handset to this specific DCC.) Also assign the same DNR (3000) to a circuit on a DCC in Node 2. (Later in this procedure, you must subscribe the handset to this specific DCC in Node 2.) e.g. CHDNRC:3000,1011,1,1; 4. Check the Fixed MSN digits of the BSP-ID. These digits have to be the same as the DNR and have to be the same as the extension number that you are using in the DECT Manager (for both DECT clusters the same). e.g. DIFMSN:3000; The Fixed MSN digits of the DNR must be 3000 in this example. Execute this command in Node 1 and Node 2. 5. Assign FCM 71 (iSNet WAN DECT Mobility) to the DNR of the DECT extension in the Nodes involved. e.g. ASFACM:71,3000; Execute this in Node 1 and in Node 2 6. Check that the BMLOCK has not been set in the Nodes.
BMLOCK:0;
This command must result in "BMLOCK not set". If the BMLOCK was set, enter the name and remove the BMLOCK. If BMLOCK is set, the WAN DECT Mobility does not work! Execute this command in Node 1 and Node 2. 7. Assign the Node IDs using OM command ASNOIT. By means of this, the Nodes know which other Nodes in the network are involved in WAN DECT Mobility. In each Node that is involved in WAN Mobility, you must execute this command. The own Node ID is allowed to be present in the Node ID list, but this is not required. This allows each Node to have the same list of Node IDs. In Node 1 you must enter the Node ID (cluster ID) of Node 2. In this example it is "6". e.g. ASNOIT:6; In Node 2 you must enter the Node ID (cluster ID) of Node 1. In this example it is "5". e.g. ASNOIT:5; You can check the Node ID list by means of OM command DINOIT or delete a Node ID
92
from the list, using OM command ERNOIT. The OM procedure is ended now and you should continue with subscribing the handset. 8. Start up the DECT Manager for DECT cluster A in Node 1. 9. Enter the extension number (3000) of the handset in the "Configuration" tab in the DECT Manager for DECT cluster A. Subscribe the handset. 10. Check if you can make a call via this handset. It should be possible now. 11. Close the DECT Manager for DECT cluster A and go to DECT cluster B in Node 2. 12. Enter the same extension number (3000) of the handset in the "Configuration" tab in the DECT Manager for the second DECT cluster. Subscribe the handset to the DECT cluster B. Now you have two subscription records in the handset. Switch the handset to automatic subscription selection (if the handset supports it). 13. Switch the handset "OFF" to make sure that it is not "within reach" of one of the RFPs in DECT cluster A in Node 1. Make sure that it is within reach of DECT cluster B in Node 2. 14. Switch the handset "ON" and check that you can receive calls on the extension using DECT cluster B in Node 2. The DNR is automatically de-activated in Node 1 and activated in Node 2. 15. In ISPBX with cluster ID=5 (Node 1) execute the following OM commands to make the cluster IDs known in the DDI tree with a "dummy" destination 99:
ASINTN:30,5,0,91,99;
Now an analysis tree must be assigned to the dummy destination. You can create a new analysis tree for this containing DECT number blocks, however, it is easier to refer to the existing DDI tree for DPNSS/QSIG, because the required number blocks should already be present in that tree. (In this example tree 30)
CHDSTC:99,30,00,99;
16. Now, in the same ISPBX (with cluster ID=5) execute the following OM commands to assign the cluster IDs to the Alternative Destination dialling tree:
ASINTN:5,5,0,91,99; ASINTN:5,6,0,91,6;
17. Go to the other ISPBX with cluster ID=6 and execute the following OM commands to make the cluster IDs known in the DDI tree with a "dummy" destination 99:
ASINTN:30,6,0,91,99;
CHDSTC:99,30,00,99;
ASINTN:5,5,0,91,5; ASINTN:5,6,0,91,99;
93
PROCEDURE: Implementing DECT Mobility in Call@Net Systems Using SARI

Make sure that you have a DECT cluster in the Nodes that you want to use in the WAN DECT Mobility configuration. The two DECT clusters must have different PARIs. However the PARI of one DECT cluster (referred to as DECT System A) must be used as SARI in the other DECT System(s). In this procedure we assume that you have only one second DECT cluster, system B. However, if you have more than two DECT clusters in your mobility configuration, you must use the the procedure for cluster B also for the other DECT clusters. Preconditions The following assumptions are made: The precondions listed in 7.5.3. "Preconditions"are met. Two DPNSS and/or QSIG Nodes are involved. Node 1 has cluster ID 5, Node 2 has cluster ID 6. If your system comprises more than two Nodes, repeat the actions for Node 2 also in the other Nodes! The numbering scheme comprises number ranges 1xxx for Node 1 and 2xxx for Node 2. In each Node, one DECT cluster is present. In Node 1 there is DECT cluster A, in Node 2 there is DECT cluster B. The extension number for the DECT handset is a "free number" in the DPNSS or QSIG network, which means that it may not be in the number range of Node 1 or Node 2. The first digit may not be a Network Access Code in the DPNSS network. In this example we have chosen number 3000 for the DECT extension that is going to be used for WAN mobility. Actions 1. Make sure that your DPNSS or QSIG network has a "closed" numbering scheme! 2. Make sure that you have an up and running DECT cluster in the DPNSS or QSIG nodes that you want to include in your DECT WAN configuration. The DECT clusters must have different PARIs. 3. Assign the DNR (3000) to a circuit on a DCC in Node 1. (Later in this procedure, you must subscribe the handset to this specific DCC.) Also assign the same DNR (3000) to a circuit on a DCC in Node 2. (Later in this procedure, you must subscribe the handset to this specific DCC in Node 2.) e.g. CHDNRC:3000,1011,1,1; 4. Check the Fixed MSN digits of the BSP-ID. These digits have to be the same as the DNR and have to be the same as the extension number that you are using in the DECT Manager (for both DECT clusters the same). e.g. DIFMSN:3000;
94
The Fixed MSN digits of the DNR must be 3000 in this example. Execute this command in Node 1 and Node 2. 5. Assign FCM 71 (iSNet WAN DECT Mobility) to the DNR of the DECT extension in the Nodes involved. e.g. ASFACM:71,3000; Execute this in Node 1 and in Node 2 6. Check that the BMLOCK has not been set in the Nodes.
BMLOCK:0;
This command must result in "BMLOCK not set". If the BMLOCK was set, enter the name and remove the BMLOCK. If BMLOCK is set, the WAN DECT Mobility does not work! Execute this command in Node 1 and Node 2. 7. Assign the Node IDs using OM command ASNOIT. By means of this, the Nodes know which other Nodes in the network are involved in WAN DECT Mobility. In each Node that is involved in WAN Mobility, you must execute this command. The own Node ID is allowed to be present in the Node ID list, but this is not required. This allows each Node to have the same list of Node IDs. In Node 1 you must enter the Node ID (cluster ID) of Node 2. In this example it is "6". e.g. ASNOIT:6; In Node 2 you must enter the Node ID (cluster ID) of Node 1. In this example it is "5". e.g. ASNOIT:5; You can check the Node ID list by means of OM command DINOIT or delete a Node ID from the list, using OM command ERNOIT. The OM procedure is ended now and you should continue with subscribing the handset. 8. Startup the DECT Manager (Version 3.0.5 or higher) for DECT cluster A. Go to the "Boards" menu and execute a" Backup". Now the SARI of your system is copied to the DECT Manager's database. 9. Subscribe the handset with extension number 3000. Make sure that you subscribe this handset to the same DCC to which you have assigned the DNR by means of the OM command CHDNRC. 10. Go to the "File" menu in the DECT Manager (Version 3) and select "Copy and Move Subscription" 11. Select the option "Move Subscription outside the system". 12. Move the subscription record of the handset that you have subscribed to a floppy. Just follow the steps on the screen. 13. Again go to the menu "Copy and Move Subscription" in the "file" menu. and select "Import". Import the subscription record again into your DECT cluster A. Again, just follow the steps on the screen. You need this floppy with the subscription file also in DECT cluster B. Close the DECT Manager for DECT cluster A. 14. Switch the handset "off" and "on" again. 15. Try to setup a call to and from the handset. It should work!
95
16. In ISPBX with cluster ID=5 (Node 1) execute the following OM commands to make the cluster IDs known in the DDI tree with a "dummy" destination 99:
ASINTN:30,5,0,91,99;
CHDSTC:99,30,00,99;
ASINTN:5,5,0,91,99; ASINTN:5,6,0,91,6;
18. Go to the other ISPBX with cluster ID=6 and execute the following OM commands to make the cluster IDs known in the DDI tree with a "dummy" destination 99:
ASINTN:30,6,0,91,99;
Now an analysis tree must be assigned to the dummy destination. You can create a new analysis tree for this containing DECT number blocks, however, it is easier to refer to the existing DDI tree for DPNSS/QSIG, because the required number blocks should already be present in that tree. (In this example tree 30) 19. Now, in the same ISPBX (with cluster ID=72) execute the following OM commands to assign the cluster IDs to the Alternative Destination dialling tree:
ASINTN:5,5,0,91,5; ASINTN:5,6,0,91,99; CHDSTC:99,30,00,99;
20. Go to DECT Cluster B. 21. If not yet done, enter the PARI of DECT cluster A, into the DECT cluster B in Node 2, but now as SARI. Use the OM command:CHPMPD:0,9600,,,<UNIT>;to do this. Enter the SARI into byte 17 ... 20. See section G . "CUSTOMIZING SYSTEM PARAMETERS". For example SARI 1000900A:
CHPMPD:0,9600,,,<UNIT>; <ITEM-NR>,<BIT/BYTE>,<DATA>:17,1,16; <ITEM-NR>,<BIT/BYTE>,<DATA>:18,1,0; <ITEM-NR>,<BIT/BYTE>,<DATA>:19,1,144; <ITEM-NR>,<BIT/BYTE>,<DATA>:20,1,10;
22. Execute a warm start in Node B (and other Nodes) where you have entered the SARI, or execute OM commands SETOUT / SETINS of the PM containing the DCC board(s). 23. Make sure that you have DECT Manager Version 3.0.5. or higher. Start the DECT Manager for DECT cluster B. 24. Go to the boards "Tab" and click the button "Backup". Now the SARI is copied into the database of the DECT Manager.
96
25. Go to the "File" menu in the DECT Manager and select "Copy and Move Subscription". Select "Import". Make sure that you have the floppy with the subscription data file of DECT cluster A. Import the subscription record again into your DECT cluster B. Just follow the steps on the screen. 26. Switch the handset "OFF" and "ON" again. 27. Try to setup a call to and from the handset. It should work now on DECT cluster B. The DNR is automatically de-activated in Node 1 (DECT cluster A) and activated in Node 2 (DECT cluster B). 28. Close the DECT Manager for DECT cluster B.
97
8.
8.1.
MAKING THE SYSTEM OPERATIONAL

GENERAL
After all installation procedures are finished, the system can be made operational. First you must startup the DCC boards. Then the DECT Manager must be started and a PPs must be subscribed (allocated) to the DECT system.
8.2.
STARTING UP THE DCC BOARDS
When your system consists of more than four DCC boards or more than one backbone section (more than one shelf with DECT), you must execute the correct procedure for setting the DCCs in service. This is necessary, because when the DCCs become operational at the same time, they are going to execute a location registration for all handsets at the same time. This might result in hanging DCCs boards, or in handsets that needs to be switched off and on again before becoming operational. Note that each time you start the DECT system or the ISPBX, you should startup the DCC boards in the way that is described in this section. (Of course, you do NOT need to subscribe the PPs again. That is done only once.)
PROCEDURE: Setting the DCCs in service

Actions 1. Make sure that the DCCs are out of service. 2. Set the DCC in board position 01 in the first backbone section (first shelf with DCCs) in service. Wait two minutes and make sure that the red LED is off. If there is a second backbone section (second shelf with DCCs), repeat this action for the first DCC (board position 01) of this second backbone section. Repeat this action also for the first DCC in the third backbone section (if present) and first DCC in the fourth backbone section (if present). 3. Set the DCCs in the first backbone section (first shelf with DCCs) sequentially (from the left most to the right most) in service. 4. If present, set the DCCs in the second DECT backbone section sequentially (from the left most to the right most) in service. 5. If present, set the DCCs in the third backbone section sequentially (from the left most to the right most) in service. 6. If present, set the DCCs in the fourth backbone section sequentially (from the left most to the right most) in service. 7. Now all DCCs should be in service
98
8.3.
STARTING UP THE DECT SYSTEM
Note: If your DCC(s) is/are equipped with firmware package F4324x.xxx, you have to use the latest version of the Windows DECT Manager (version 3). This DECT Manager version supports the SNMP protocol over TCP/IP (via V.24), which is the management communication protocol of this firmware package. So, older DECT Manager versions cannot be used with this firmware. For further information on which DECT Manager version matches with which firmware package, consult 4. "IMPORTANT FIRMWARE ISSUES".
8.3.1.
C-DOS/UNIX Based DECT Manager
To startup the DECT system, execute the following steps: 1. Make sure that all hardware is correctly installed and that the projecting procedures are correctly executed. Also make sure that the V.24 connection between the DCC (with BBR or barrier box) and the DECT Manager PC is present. 2. Ensure that the DECT Manager is correctly installed. Make sure that the configuration files EHWADCC.PDT and EHWADNR.PDT are filled with correct data corresponding with the actual hardware configuration in the ISPBX. Make sure that your correct license string is correctly entered in the file LICENSE.PDT. The data structure in the files is described in the DECT Manager User Guide. If not yet converted, convert these files to .TXT files by means of the tool "convert" (see also DECT Manager User Guide). 3. Check that in the protocol setting of the PC, XON/XOFF is set to "off". If not, the DECT Manager communication starts correctly, but hangs itself during communication. (All other protocol settings are generally correct after installation.) 4. Start the DECT Manager according to the procedure in the DECT Manager User Guide. 5. Select "Configuration Management" in the DECT Manager and remove all existing subscriptions on the newly installed DCC board(s). After that, configure the RFPs for each DCC. If the DCCs still contain (invalid) subscriptions or if RFPs are not correctly configured, alarms are generated in the ISPBX. 6. Subscribe enough portable telephones to make calls and test the system. For subscription procedures consult the appropriate sections in this chapter. 7. Make calls to and from the portable telephones. Try each cell. Try inter-cell handover (should be seamless), and out-of-range effect (dropped call). 8. Check alarms in the ISPBX. Deal with any problems and clear alarms. 9. Subscribe all of the PPs which must be used immediately by the customer. Give each terminal a simple test (Calls to/from the PP; handover and out-of-range tests.)
99
Check that each PP has the correct traffic class and facilities.
8.3.2.
Windows Based DECT Manager
To startup the DECT system, execute the following steps: 1. Make sure that all hardware is correctly installed and that the projecting procedures are correctly executed. Also make sure that the V.24 connection between the DCC (with BBR or barrier box) and the DECT Manager PC is present. 2. If the DCC is equipped with firmware package F43240.XXX, it uses an IP address via the V.24 interface. Make sure the IP address is set correctly (consult 6. "IP PARAMETERS". 3. Ensure that the DECT Manager is correctly installed and that you have the correct Licences in the Licence Manager to use the DECT Manager. (Consult the DECT Manager Manual and the SysManager 410 documentation.) 4. Configure the Connection Manager or the NCC for the connection to your DECT System. Note: If you setup an SNMP connection via the NCC (part of the DECT Manager software) to a DCC with firmware package F43240.XXX, you need to enter a "host name" and a "user name". The "host name" is the IP address of the DCC , the "user name" is: dasuser. 1. Start the DECT Manager according to the procedure in the DECT Manager Manual. 2. Select the "Configuration" tab in the DECT Manager and enter all the extension numbers that are assigned to the DCC boards in the DECT System. Make sure that you assign them to the appropriate boards in the "Configuration" tab. 3. Subscribe enough portable telephones to make calls and test the system. For subscription procedures consult the appropriate sections in this chapter. 4. Make calls to and from the portable telephones. Try each cell. Try inter-cell handover (should be seamless), and out-of-range effect (dropped call). 5. Check alarms in the ISPBX. Deal with any problems and clear alarms. 6. Subscribe all of the PPs which must be used immediately by the customer. Give each terminal a simple test (Calls to/from the PP; handover and out-of-range tests.) Check that each PP has the correct traffic class and facilities.
8.4. 8.4.1.
SUBSCRIPTION OF PORTABLE PART General
During normal operation, both the DCC and the PP hold information which describes the subscription of that particular portable terminal to the DECT System. The PP must be given access rights to the system by a subscription process in which information is exchanged between the fixed part and the portable part of the DECT System.
100
The subscription procedure requires action at the DECT Manager side and at the PP side. The actions at the PP side differs per type of PP. Therefore consult the User Guide that is appropriate for your DECT PP. There are PP types that request for the PARK (Portable Access Rights Key) during the subscription procedure. You need to enter this PARK, only if there are other DECT systems in the environment which are operational and in Subscription mode! The PARK is displayed in the right-bottom corner in the Windows based DECT Manager. In the C-DOS and UNIX based DECT Manager, the PARK is displayed in the "Display Subscription" screen. CAUTION: DO NOT SET THE DCC OUT OF SERVICE OR DO NOT EXECUTE A WARM START, AS LONG AS THE RED LED ON THE DCC IS WINKING. ELSE THIS MIGHT CORRUPT THE SUBSCRIPTION DATA FOR THAT PP.
Note: If one or more subscriptions are in status "enabled", and the DCC board is set out of service, this/these subscriptions are reset! The subscription status "enabled" occurs when a subscription is requested and confirmed at the DECT Manager but not yet acknowledged from the PP side.
8.4.2.
Example of Subscription Procedure (C-DOS/UNIX DECT Man.)
1. Ensure that the battery of the portable part has been fully charged and that it is within range of an RFP, before attempting its subscription. At the DECT Managers side: 2. Select "Registration Management". 3. Select "Enable Subscription". 4. Enter the DNR and press <CR>. Note that the EHWA is displayed. Press <CR>to confirm. If you press "confirm" (<INS>) without entering a DNR or EHWA, the DECT Manager selects a free DNR/EHWA combination. 5. Now a PIN code is displayed on the screen. Keep this PIN code in mind and press "confirm" (within one minute) to enable this subscription. 6. If possible, check that the Red LED on the DCC board is winking. It waits for a subscription of the handset. You have only 16 minutes to confirm the subscription from the handset. At the handset side: 7. Consult the User Guide of the PP type that you want to subscribe.
101
8. Execute the procedure in the manual for a new subscription. Note: You must excute the subscription procedure at the handset within 16 minutes after the subscription procedures has been started at the DECT Manager.
8.4.3.
Example of Subscription Procedure (Windows DECT Man.)
1. Ensure that the battery of the portable part has been fully charged and that it is within range of an RFP, before attempting its subscription. At the DECT Managers side: 2. Start up the DECT Manager for the appropriate DECT System. 3. Make sure that nobody else has made changes/subscriptions via another DECT Manager. If somebody else has made changes/subscriptions via another DECT Manager, you must do a backup first (in the "Boards" tab) for all the boards in the system (one at the time). 4. In the "Subscriptions" tab, select the extension number(s) that you want to subscribe. If the extension number(s) is/are not visible in the "Subscriptions" tab screen, check the "Show ......" check boxes in the left-bottom corner of the "Subscriptions" tab. If all "Show ...." options are enabled, and still the extension number(s) is/are not displayed, you must enter the extension numbers in the "Configuration" tab/screen in the DECT Manager. In that case you must also assign the extension number(s) in the ISPBX. 5. Click on the "Enable" button in the bottom of the screen. Now, for all selected extension numbers, a PIN code is displayed on the screen. 6. If possible, check that the Red LED on the DCC board is winking. It waits for a subscription of the handset. You have only 16 minutes to confirm the subscription from the handset. At the handset side: 7. Consult the User Guide of the PP type that you want to subscribe. 8. Execute the procedure in the manual for a new subscription. Note: You must excute the subscription procedure at the handset within 16 minutes after the subscription procedures has been started at the DECT Manager.
8.4.4.
Overwrittting an Existing Subscription in a Portable Part Type C311
It is not possible to remove subscription data from the Portable Part type C311 manually at the PP side. So, if there is still subscription data left in the C311 and it is not possible to remove the subscription data by means of the "Disable" option in the DECT Manager, the subscription data cannot be removed from the C311 anymore. However, if you want to subscribe the C311 to the same DECT system (same PARI) again you need to "overwrite" the existing subscription data in the PP. To do this, execute the following procedure: 1. Ensure that the battery of the portable part has been fully charged and that it is within
102
range of an RFP, before attempting its subscription. 2. Switch the C311 off. Do this by keeping the Power button depressed for at least 5 seconds. 3. Execute the Subscription procedure at the DECT Manager side, as described in the previous sections. Note: The following three steps (steps 4 ... 6) must be executed within 4 seconds. 4. Press "R/->" twice. 5. Press the scroll up button twice. 6. Press "OK". Now the C311 tries to find a DECT system which is in subscription mode. If found, then the name of the previous subscription on that system is displayed (or the PARI). If it found more than one system in subscription mode than you can scroll though the names and/or PARIs of these systems and select the required one. If it cannot find a DECT system in subscription mode, it displays:NO BASE 7. Press "OK". Now the C311 requests for the PIN code. Enter the PIN code which was given by the DECT Manager. 8. Press "OK". A default subscription name is displayed. If you do not change this name then it will appear on the idle display. Delete the existing name by pressing "scroll down". Enter a new name or number (e.g. 1234 ABC) by means of alpha numeric characters under the numeric keys. This name or number then appears on the idle display for that subscription. 9. Press "OK". You will hear a confirmation tone. 10. Press "R/->" to return to idle mode.
Note: The C311 can be subscribed to up to four DECT systems, by executing the subscription procedure for each subscription. Be careful: It is only possible to delete a subscription from the C311 by means of executing the "disable" option in the DECT Manager on an existing and active subscription. There is no menu option in the C311 to delete a subscription from it. If there are already four subscriptions in the C311, the oldest subscription will be overwritten.
103
8.4.5.
Problems During Subscription
While executing the subscription procedure, problems may arise. The following overview denotes two major problems with possible causes: No free EHWA/DNR is available (C-DOS/UNIX Based DECT Manager) - All EHWA/DNR combinations have been allocated. A warning message is given. - The information has not yet been entered into the DECT Manager files or into the SOPHO ISPBX. Check the file EHWADNR.PDT. Check also whether the file has been converted to .TXT. - The EHWA-DNR combination was already been used for a subscription, but the subscription became invalid and was not removed. Go to "Display Subscription Data" (in the Registration menu) and display the subscription data of the DNR that you want to subscribe. Now you can choose to remove the subscription data or to go back to the Subscription menu to subscribe another DNR. - You reached the extension limit, as specified in the license string. See the file LICENSE.PDT. No free DNR available (Windows Based DECT Manager) - Check the "Show ...." check boxes in the left bottom corner of the "Subscriptions" tab screen. Turn them all on to make sure that all DNRs are visible. Check the status of the DNRs. If DNRs are Back Listed, follow the procedures in the DECT Manager Manual to make them available again. - Although all the check boxes in the left-bottom screen are enabled, still no DNRs are available. Enter new DNRs via the "Configuration" tab. In this case you must also assign these DNRs in the ISPBX (if not yet present). - You reached the extension limit, as specified in the license string. See the following menu: "View", "Options" and them the tab "General". In this screen you see a box indicating the" Maximum number of users". If you reached this limit, you need to have a licence for a higher number of users, which is possible as long as the system maximum is not yet reached. The portable telephone does not become subscribed, although a free DNR is available. - Time out after enabling the subscription. You waited too long with entering the PIN after the subscription was enabled. The subscription must be enabled, again, at the DECT Manager. - The wrong PIN has been entered. - Bad connection between RFP and PP. Try the subscription while well within range of an RFP (say within 20 metres). Check the signals for interference (DECT Manager, Performance Measurement function, RSSI Map).
104
Bad connection between RFP and DCC. The cable might be too long, or subjected to interference. There may be a physical fault in the connection. PP power supply not properly charged. The RFP/DCC is not functioning correctly. Check the status of this equipment at the DECT Manager. Check the straps on the DCC, and the cables to RFP and DECT Manager. The PP is not functioning correctly. Try another PP which is known to be in good working order. Check the configuration and also the data entered into the DECT Manager files. The portable tries to subscribe to another DECT system. (another PARI has been found by the portable.) On C211: Press P8*# and wait until the correct PARI appears on the display. On C311: Press the Scroll Down key and wait until the correct PARI appears on the display. On C911/922: Use the "System Id." ("PARK" in the DECT Manager). For other types of PPs, consult the User Guide that is supplied with the handset.
Examine the Alarm reports at the SOPHO ISPBX regularly for anything that might affect the operation of the DECT System.
8.5. 8.5.1.
TESTS Initial Test Procedure
After successful subscription of a portable telephone it should be possible to make calls to that telephone from another portable or a fixed wired telephone. Each PP must be tested on proper functioning. Test this as follows: 1. Initially, position the PP well within range of the RFP. This eliminates possible problems due to bad connection. 2. Try to make a call from the PP to a fixed wired extension. Another PP can be used instead of a fixed wired extension, but than you must ensure first that this extension operates well. 3. Try to make a call to the PP from a hard wired extension or a proper functioning PP. 4. If calls are successful in both directions, then a basic, correctly working configuration exists. If not consult section 8.5.2. "Trouble Shooting During Initial Tests".
8.5.2.
Trouble Shooting During Initial Tests
During initial tests problems may appear. Two main categories are distinguished: Problems with calls to the portable telephone (It is assumed that the basic SOPHO ISPBX works correctly, the PP has been subscribed,
105
and the PP power supply is adequately charged.) - Incorrect DNR dialled. - Wrong subscription (DECT system) selected at the PP. - Calls to the PP are blocked in the SOPHO ISPBX for any reason (internal restrictions, type of IBSC, callers traffic class, service condition of the EHWA, or any other reason) - Appearance of a fault in the DCC/RFP (Check at the PP that it is within range of a radio signal and read out alarms in the ISPBX.) - A fault has occurred in the PP. If this is suspected, use the "Disable" command to desubscribe that PP, and then subscribe another one, using the same DNR. - MSN incorrect. See section 3.3. "PROJECTING IN SSW 740/800/805". Problems with calls from the portable telephone (It is assumed that the basic SOPHO ISPBX works correctly, the PP has been subscribed, the PP power supply is adequately charged.) - Is dialtone received? If not, it might be possible to check the display of the portable terminal for symbols indicating the problem (Out of range of radio signal; PP not switched to work with this DECT System.). Also check that the portable terminal really has been subscribed (DECT Manager, Registration Management, display subscription data). - Appearance of a fault in the DCC/RFP (Check at the PP that it is within range of a radio signal and read out alarms in the ISPBX.) - If dialtone is received, the call might progress further, without being successful. Are calls from the portable telephone blocked in the SOPHO ISPBX for any reason (internal restrictions, type of IBSC, callers traffic class, Service condition of the EHWA, or any other reason)? - A fault has occurred in the PP. If this is suspected, use the "Disable" command to desubscribe that PP, and then subscribe another one, using the same DNR.
8.5.3.
Testing Handover and RFPs
After the initial test has been executed on all PPs, the RFPs must be tested. During this procedure, also the handover functionality is tested. 1. Get a map of the building with the positions of the RFPs and the cells. 2. Set up a call from a PP to another extension. Provide this other extension with a tone source or ensure a continue conversation. 3. Walk around from RFP to RFP and check the speech quality. During walking from one cell to another, the conversation must remain good quality. This also means that there should not be an unacceptable number of clicks and hiccups at any point, nor should the handover from one RFP to the other disturb the connection.
106
Check if there is a gap between the cells. Check also that all RFPs are working well. Do this by walking from cell to cell for all cells. If problems arise, consult section 8.5.4. "Trouble Shooting in Handover Test". 4. Now, check the handover function of each PP. Set up connection from a PP and walk from one RFP to another RFP, crossing a cell boundary. If the PP executes a seamless handover at crossing the cell boundary, the handover function works well. Check this for each PP. If problems arise and there were no problems in step 3 check this again with another PP. If both PPs show the same problem, there is a gap between the two cells. If one PP shows problems, the PP is faulty and must be replaced.
8.5.4.
Trouble Shooting in Handover Test
A number of main problems are distinguished during the handover and RFP test: Gap between the cells There is an unacceptable dip in the quality of the connection when you cross the cell boundary. Do the following: - Check whether the dip was caused by a permanently present obstacle to radio waves, such as a reinforced concrete wall or metal object. - Check whether the distance between two cells is too big. - Make a geographical map showing the areas where the connection is not good. Do this while walking around with the PP. - Reposition one or more RFPs if necessary.
Note: Repositioning RFPs should not be necessary if the initial tests for RFP position was done thoroughly. Individual Cells work properly; handover causes connection to be broken Check that there is no gap between the two cells. If there is a gap, continue with the subsection "Gap between the cells" in this section. If there is no gap and the RFPs are correctly functioning, there are probably problems in the backbone hardware. Do the following: - Check the strap settings on the DCC boards. - Check the cabling between the DCCs and the BBR (if BBR is present).
8.5.5.
Testing a System with BBR and Backbone Cabling
If the DECT system is installed in an iS3050, 3070 or 3090, and more than one shelf is used to install the DCCs in (multiple backbone sections), test the configuration as follows: Install in each shelf only the first DCC. Install the BBR and backbone cabling.
107
Check whether the DECT Manager communication can be established on every DCC V.24 port. Subscribe a portable on every DCC Connect only one RFP on one DCC. Check whether all portables are operational. Move the RFP to another DCC. Check all portables again. Repeat this step until all DCCs (maximum 4) are tested. If no problems occur (anymore), install the rest of the system.
8.6.
ALARM REPORTS
The alarm reports at the SOPHO ISPBX should be regularly examined, during the initial testing of the system so that unexpected faults can quickly be dealt with. At the end of the (initial) tests, the installing engineer should be reasonably confident that all parts of the DECT System are functioning correctly. The engineer should watch for alarms over the next few days, to assess the performance of the equipment. After a final examination of all alarm reports, they should be cleared, ready to collect any new problems which may appear as alarm reports.
Note: If an RFP fails (or its connection) alarms are generated. Therefore, if you have to do maintenance on cabling to an RFP or you have to disconnect the RFP, always set the RFP in "not installed" in the DECT Manager menu "Registration Management". As soon as the RFP is operational again set the RFP in "installed" in the DECT Manager. Section 9.2. "THE CLEARANCE OF FAULTS", subsection "Alarm Reports/Codes" summarises the alarm codes with their meaning. The Maintenance manual gives also information on the alarm codes.
8.7.
SUBSCRIPTION OF ALL PORTABLE TERMINALS
All portable terminals which are to be used by the customer should be subscribed and made ready for use. This does not generate alarms. Each portable terminal should be given a simple test for calls to and from the terminal, as well as inter-cell handover and range tests (consult also section 8.5. "TESTS"). The battery of each portable terminal should be charged before it is subscribed. Further, in the SOPHO ISPBX, each portable terminal should be given the required traffic class and facility class marks.
108
9.
9.1.
MAINTENANCE
GENERAL MAINTENANCE
Maintenance of the DECT System and equipment can be divided into: updating of operating information (Operational Maintenance), the loading of new, modified programs into the DCC or the DECT Manager and the corrective maintenance needed when a fault is detected.
The operational maintenance needed in the SOPHO ISPBX to add or remove DCC equipment is described in the documentation for that SOPHO ISPBX. The DECT Manager commands needed for day-to-day running of the DECT System are described in detail in the User Guide for the DECT Manager. The procedure for loading a new software package into the DCC is the same as that for other types of boards such as a DTX-I or DLC-U. It is described in the appropriate maintenance manual for that ISPBX, in the chapter dealing with the loading and retrieving of software. When loading new software into the DCC, the current DCC subscription data is NOT deleted. Note: If you have a DCC with firmware package F43040.xxx, never remove the DCC or set it out of service, when the red lamp is flashing with a 1 second rhythm. If you have a DCC with firmware package F43140.xxx or F4324x.xxx, never remove the DCC or set it out of service, when the red lamp is flashing with a 2 second rhythm. The loading of DECT Manager software is described in the DECT Manager User Guide. Corrective maintenance is described in section 9.2. "THE CLEARANCE OF FAULTS"below.
9.2. 9.2.1.
THE CLEARANCE OF FAULTS Fault Indications
A problem can appear and be reported in different ways: Nobody can use the DECT System. It is virtually dead. Fault tracing actions are discussed in section 9.2.2. "Dead System". A telephone user complains. Fault tracing actions are discussed in section 9.2.3. "User Complaints". An alarm report is generated by the SOPHO ISPBX.
109
SOPHO ISPBX generated alarms (with regard to the DECT System) depend on the type of SOPHO ISPBX. As to what action must be taken, see section 9.2.4. "Alarm Reports/ Codes (SSW 300)" or section 9.2.5. "Alarm Reports/Codes (SSW 740/800 and Upwards)". Any other report. In that case consult Appendix H . "ENTERING DATA INTO DCC SIGNALLING GROUPS DIRECTLY", which contains a flow diagram for fault tracing.
9.2.2.
Dead System
The DECT System does not work at all. Nobody can make or receive calls. A correctly working PP (properly charged) should receive and detect a radio signal when close to an RFP. If that is not so, most portable terminals will display an "Out of Range of Radio Signal" symbol on the display. - If it indicates that no signal is being received by any portable terminal, the problem is expected to be in the fixed part of the DECT System, or in the ISPBX. How far does the call attempt from a portable set progress? Do the users of portable telephones receive dial tone, when trying to make a call? - If so, it would indicate that there is very little wrong with the system and the problem might be due to an incorrect procedure during system maintenance. - If the portable set is within radio range but no dialtone is received after going off-hook, start checking another portable. After that the fixed part of the DECT System and the ISPBX. Is it possible to make or receive calls at standard fixed wired telephones on that ISPBX (assuming that they are present)? - If not, the problem is probably in the SOPHO ISPBX and the fault clearing procedures for that PBX should be followed. - If calls are possible, the problem is confined to the connections to the DECT System, or within the DECT System itself. Check the alarm reports at the SOPHO ISPBX for anything related to the DECT System (DCC board alarm or DCC channel alarms). If such an alarm report is present, follow the actions suggested in the SOPHO ISPBX fault clearing procedure. On each DCC, check the LEDs For the meaning of the LED indications, see section 9.4. "LED INDICATIONS ON DCC BOARD". Check the status of the DCCs and RFPs in the DECT Manager "Configuration Management".
9.2.3.
User Complaints
The user complains because: the quality of the connection is bad
110
If this portable set is the only one with this problem it is probably the portable set which gives the problem. It should be replaced. - If more than one set has the problem, but always within a certain area, check the RFP(s) in that area. Check whether there are RFP alarms generated in the ISPBX. If so, deal with them as given in the alarm instructions. In this case the following actions are suggested: - Check the interface cabling. If damaged, repair the cabling. - If the RFP is locally fed, check the power provision. - If the RFP is faulty, replace it. - Check for disturbance by some outside interference such as an electric welding machine. Read out the RSSI map for those base stations. the PP does not work correctly If the PP does not work correctly, you must discover as much as possible about the problem. It may be just incorrect use of that PP. In that case, the solution to the problem is a little training. The answer to the following questions can be helpful: - How far does a call progress: To that portable set? Is the portable set within range of a radio signal? From that portable set? Is dialtone heard, on attempted outgoing calls? Decide whether some equipment might be faulty or whether it is worth looking at the attributes of that set in the SOPHO ISPBX (analysis group; IBSC; etc) - Is it the only PP with the problem? if yes, suspect the set. if no, suspect the fixed equipment. Where does the problem occur? - Only at one RFP? (suspect that RFP or its interface with the DCC). - At a number of RFPs? (Suspect the DCC, if the fault appears at more than one set. Suspect the portable set, if only one set has the problem, otherwise see section 9.2.2. "Dead System"). De-subscribe that set and then subscribe another (good) portable set with that same EHWA/DNR. If it shows the same problems, look in the attributes such as traffic class and facility class marks, in the SOPHO ISPBX.
9.2.4.
Alarm Reports/Codes (SSW 300)
If alarm conditions occur, these are reported in the ISPBX. The following alarm codes refer specifically to alarms in DECT. Alarm Code 1043:
111
Error type 10 = Error type 20 = Error type 30 =
Error type 40 = Error type 50 = Error type 60 =
RFP Error Check RFP connections, check RFP or replace RFP. Burst Mode Controller Error Replace the DCC. Backbone communication is lost Check strap settings on the DCC board. Try to reboot the DCC board. If all else fails, replace the DCC board. General hardware error. General software error. The PARI downloaded from the PM to the DCC is missing or incorrect. Project correct PARI parameters in the PM data.
Alarm Code 1044: The RFP configuration does not match with the actual situation. In the DECT Manager, adapt the RFP configuration to the actual situation. Clear the alarms.
Error type 10 =
In the PE Commands Manual chapter "Alarm Level Definitions" table "Event Causing the Alarm", the rows of table Table 9-1 "Alarm Level Definitions"below must be added due to the DECT System alarms: Other alarms which can be generated in general for PCT boards can occur also. Consult the Maintenance manual for these alarms.
AL-CODE 1043 1044
EVENT CAUSING THE ALARM DCC board alarm DCC board configuration alarm
DEFAULTS MA 99 MI 99
Table 9-1 Alarm Level Definitions
9.2.5.
Alarm Reports/Codes (SSW 740/800 and Upwards)
If alarm conditions occur, these are reported in the ISPBX. The following alarm codes refer specifically to alarms in DECT. Alarm Code: Qualifier 061:065 CODE : INFORMATORY EVENT
112
QLF : The RFP configuration does not match the actual situation. TYPE : Board ADD. : Line part number (RFP number). INFO. : -. Description This alarm is generated if the following conditions are fulfilled: The DCC board is in service. The stored administrative status of the indicated RFP is 'Not Installed'. A correctly functioning RFP is connected to the DCC.
The administrative state of the RFPs should always reflect the actual situation of RFPs which are connected to the DCC. Maintenance Actions Using the DECT Manager, adapt the RFP configuration to the actual situation. Then clear the alarms.
Alarm Code: Qualifier 065:040 CODE QLF TYPE ADD. INFO. : : : : : SPECIAL HARDWARE NOTICE Radio Fixed part on DCC is malfunctioning. Board Line part number (RFP number) 1...4 or 1 ... 8. Error code 1 = Local receive signal missing (RFP disconnected). 2 = Local loss of receive slot synchronisation 3 = Local loss of receive frame synchronisation 4 = Local bit error rate bad 5 = Remote receive signal missing 6 = Remote loss of receive slot synchronisation 7 = Remote loss of receive frame synchronisation 8 = Remote bit error rate bad 9 = Synthesizer out of synchronisation
113
10 = Power amplifier out of order 11 = Round trip delay time changed 12 = RFP synthesizer type changed 13 = LFC out of synchronisation with BMC 14 = Error due to synchronisation port mutation Description This alarm is generated in the following circumstances: - The DCC board is in service - The indicated RFP is installed. - The indicated RFP is malfunctioning. Maintenance Actions Consult the error code in parameter 2. The error codes require the following actions: INFO: 13 : Set the DCC out of service and subsequently into service 14 : The alarm is automatically cleared within 200 seconds. rest : Disconnect the RFP for 10 seconds. If this does not solve the problem, then either the RFP or DCC has an hardware error.
Alarm Code: Qualifier 065:041 CODE : SPECIAL HARDWARE NOTICE QLF : Burst mode controller on 24-DCC or 32-DCC is malfunctioning or LMC error on DCC-8. TYPE : Board ADD. : Line part number (BMC number on 24-DCC and 32-DCC or LMC number on DCC-8). INFO. : Description This is a DCC hardware error : it is generated in the following circumstances: the DCC board is in service. the indicated BMC chip (24-DCC and 32-DCC) or LMC chip set (DCC-8) is malfunctioning. Maintenance Actions Reboot the DCC a couple of times (SETOUT / SETINS). If the problem persists, replace the
114
DCC by the correct one.
Alarm Code: Qualifier 065:042 CODE QLF TYPE ADD. INFO. : : : : : SPECIAL HARDWARE NOTICE Backbone communication of DCC is lost. Board Error code 1 = BBC ASIC version used in the first unit group of the shelf 2 = BBC ASIC version 1 used in the last unit group of the shelf 3 = BBC version incompatible with version of master 4 = Synchronisation lost 5 = No Synchronisation found 6 = Multiframe counter difference BBCs 7 = Multiframe counter difference BBC-BMCs 8 = Input of BBC locked 9 = I/O transmit overflow Description This alarm code indicates either a hardware or a software problem: it is generated in the following circumstances: - the DCC board is in service. - the Backbone communication is lost. Maintenance Actions 1. Check the strap settings of the DCC. 2. Try to reboot the DCC a few times. 3. If all else fails, replace the DCC board.
Alarm Code: Qualifier 065:044 CODE : SPECIAL HARDWARE NOTICE QLF : General software error on resource of PCT board. TYPE : Board
115
ADD. : INFO. : 1 = Subscription database corrupt 2 = DCC address incorrect: the DCC is placed on the wrong position or contains "old" data. 3 = Duplicate DNR in the system: a DNR has been moved to another EHWA in the DECT Manager, but the previous subscription is still present on the DCC. The alarm should be present for two boards. Note that the following codes (4, 5 and 6) are not valid for a DCC: 4 = Board is in service 5 = Board time changed 6 = Package distribution result Description This alarm indicates that the board is in service and a firmware (software) error is detected. Maintenance Actions Subscription database corrupt: use the DECT Manager to make a backup of the board. Then select "cleanup" to delete all corrupt or inconsistent subscriptions. DCC address incorrect: place the board on the right position or use the DECT Manager to remove all subscriptions. Duplicate DNR in the system: use the DECT Manager to perform a cleanup on both boards.
Alarm Code: Qualifier 065:045 CODE : SPECIAL HARDWARE NOTICE QLF : The RFP-ID (PARI) of the DCC is missing or incorrect. TYPE : Board ADD. : INFO. : Description This alarm indicates that the DCC board came in service, but the RFP-ID that was downloaded from the PM was missing or incorrect. The DCC cannot function in this case. Maintenance Actions Project the correct RFP-ID (PARI) parameters in the PM data.
116
Other alarms which can be generated in general for PCT boards can occur also. Consult the Maintenance manual for these alarms.
9.3. 9.3.1.
REPLACEMENT PROCEDURES The Portable Terminal
The portable terminal may be taken out of service for maintenance or redistribution. It might also be replaced after it has become lost, stolen or unusable. De-subscribing a PP A normally usable terminal can be de-subscribed by putting it on the blacklist, then going off-hook at the terminal. To blacklist the terminal consult the appropriate DECT Manager Manual. The terminal is now blacklisted. When the Terminal user goes off-hook or receives a call, the subscription data is deleted, both in the DCC and in the portable terminal. The terminal is free to be subscribed, again. The DNR is also free to be used again. The PP is either lost, stolen or unusable If the terminal is either lost, stolen or unusable, it cannot be used to complete a desubscription procedure. Therefore, the "Remove" command should be used. For the CDOS/UNIX DECT Manager, use the following procedure: - Ensure that this terminal must really be de-subscribed (responsibility of the DECT Manager operator). - Go to the DECT Manager main menu. - Select Registration Management. - Select Display Subscription Data. - Enter the DNR or EHWA of the terminal. - Select "Remove" (F5). To "remove" a PP by means of the Windows based DECT Manager, use the following procedure: - Ensure that this terminal must really be de-subscribed (responsibility of the DECT Manager operator). - Go to the "Subscriptions" tab and select the DNR that you want to "Remove". - Go to "Boards" menu and select "Remove". The terminal subscription data is deleted in the DCC, only. The EHWA/DNR combination is free to be used again. The terminal, however, still contains the subscription data. If an illegal user tries to make a call with this terminal, it is no longer recognised by the DECT System, which has also deleted the authentication codes for that terminal. When the DNR is used gain, they are issued with new authentication codes to another terminal. Those codes are unique to that terminal.
Note that if a portable terminal has been blacklisted by the Disable command, it might not be
117
able to go off-hook to complete the de-subscription. In that case, the Remove command can be given, to de-subscribe the blacklisted terminal. The DNR is now free to be used, again. To subscribe a new portable terminal consult section 8.4. "SUBSCRIPTION OF PORTABLE PART".
9.3.2.
The Radio Fixed Part (RFP)
The Radio Fixed Part is normally fixed to a wall or to a wall mounting plate (type B3xx and higher). It gets its power from the DCC, along the 2Mb cable connection or it is locally fed. The replacement procedure depends on the practical situation of the RFP. However, roughly the following procedure must be followed: 1. Set the RFP in condition "not installed" in the DECT Manager. Use the following procedure for the C-DOS/UNIX based DECT Manager: - Select Configuration Management. - Select DCC to which the RFP is connected. - Select <F8>. - Press <F4>and set the RFP to "Not Installed" by means of the cursor keys. - Press "Confirm" (<INS>). Use the following procedure for the Windows based DECT Manager: - Select the "Radios" tab. - Enable the two "Show ......" boxes in the left-bottom corner of the screen. - Select the RFP that you want to set to "Not Installed". - Click the button "Set Not-Installed". 2. Disconnect the power cable in case RFP is locally fed. Disconnect the RFP by means of the plug at the wall socket RJ45. This ensures that there is no longer 48 V or 59 V on the interface cable while doing the job. 3. Disconnect the interface cable at the RFP itself and wait until the RFP is 'not-operational' in the DECT Manager. 4. Install the new RFP temporarily for preliminary tests. Connecting the cables must be done in the following order: - Connect the RJ45 plug of the interface cable at the RFP side. - Connect the other side of the interface cable to the wall socket. - Connect the local power provision if required for the RFP. 5. Set the RFP in condition "Installed" by using the DECT Manager. Check that it becomes operational. Try to make calls within the cell of this RFP. This preliminary test ensures that the new RFP works. 6. Repeat steps 1 ... 3 for the temporarily installed RFP. 7. Remove the old RFP. Note that the RFPs type B3xx/l are removed by just taking them of the mounting plate. In case of other RFPs the removing procedure can be different per
118
location. Be creative! 8. Install the new RFP definitively into position. Note that the RFPs type B3xx/l are installed by just hanging them on the mounting plate. In case of other RFPs the installation procedure can be different per location. Again, be creative! 9. Connect the cabling of the RFP in the order as given in step 4. Note that the time between disconnecting and connecting must be at least 2 minutes. After having disconnected the RFP for more than two minutes, the DCC starts a line and RFP check in order to get line and RFP characteristics. 10. Set the RFP in condition "Installed" by using the DECT Manager. Check that it becomes operational. 11. Test the new RFP by making/receiving calls at all parts of the cell. Test it for inter-cell handover by roaming over the cell boundaries while maintaining a connection.
9.3.3.
DECT Cluster Controller (DCC)
To replace the DCC execute the following steps: 1. Check if the V.24 interface cable (for the DECT Manager) is connected to the DCC which you want to replace. If so, make sure that the DECT Manager is not active. Disconnect the cable from the DCC board to be replaced and connect it to any other DCC board. 2. Check whether you have a valid backup file of the subscription contents of the DCC board. If not generate one according to the following procedure: - Start up the DECT Manager. - In the DECT manager select "Configuration Management" for the C-DOS/UNIX DECT Manager or go to the "Boards" tab in the Windows DECT Manager.. - Select the DCC board. - Press <F5>in the C-DOS/UNIX DECT Manager or the "Backup" button in the Windows based DECT Manager. A backup is now generated of the DCC board. Continue when the backup action is finished. (The subscription data in a DCC will NOT be lost if the board is removed or set out of service. Only when new subscription data is restored to the DCC board, the subscription data of the (total) board is changed.) CAUTION: CONTINUING THIS PROCEDURE MAY CAUSE DROP OF EXISTING CALLS. PREFERABLY EXECUTE THIS PROCEDURE OUTSIDE WORKING HOURS. IF THE DCC IS CONNECTED TO THE BBR, AND THERE ARE MORE THAN ONE DCC BOARDS IN THE SHELF IN WHICH THE DCC IS TO BE REPLACED, THE DCC IN THIS SHELF ARE ISOLATED FROM THE DCCS IN OTHER SHELVES. THIS MEANS THAT, IF HANDOVERS OCCUR BETWEEN A SHELF AND THE SHELF IN WHICH THE DCC HAS TO BE REPLACED, THESE CONNECTIONS
119
WITH HANDOVER WILL BE LOST. ALSO DURING REPLACEMENT OF THE DCC BOARD HANDOVERS BETWEEN THIS SHELF AND OTHER SHELVES ARE NOT POSSIBLE. 3. Set the RFPs which are connected to the DCC board in "Not Installed" by means of the DECT Manager. 4. Set the DCC out of service by means of OM command SETOUT. Note: In case of a DCC with firmware package F43040.xxx, never remove the DCC or set it out of service, when the red LED is flashing with a 1 second rhythm. In case of a DCC with firmware package F43140.xxx, never remove the DCC or set it out of service, when the red LED is flashing with a 2 second rhythm. If the red LED is flashing with such a rhythm, the DCC is about to store subscription data in the Flash EPROM. After about 1 minute the red LED stops flashing and the DCC can be set out of service. 5. Remove the RFP cable from the DCC board. 6. Pull the board out of its position. If present, disconnect the cable to the BBR and/or the DSP cable. Keep in mind the connector positions of the cable connectors on the board. 7. Set the straps on the new DCC board in the same position as on the old DCC. If applicable, connect the BBR cable and/or the DSP to the connectors on the new DCC board. 8. Insert the new DCC into the board position. 9. Set the DCC in service by means of OM command SETINS. 10. Restore the subscription data to the DCC board by means of the DECT Manager. Make sure that this is the same DECT Manager as in step 2. (If not make sure that you have the correct backup file which is to be restored.) - In the DECT manager select "Configuration Management" in the C-DOS/UNIX DECT Manager or select "Boards" tab in the Windows DECT Manager. - Select the DCC board. - Press <Sft><F5>for the C-DOS/UNIX DECT Manager, or click the "Restore" button in the Windows DECT Manager. The subscription data for the selected DCC board is now restored. Continue when the restore action is finished. 11. Set the RFPs which are connected to the DCC board to "Installed" by means of the DECT Manager. - Check that the status of the RFPs is (or becomes within 90 seconds) "operational". 12. Try to make a call by means of a PP that is subscribed to the DCC board. Further the system should be tested by making calls to and from each cell, and by roaming between cells while maintaining a connection.
9.3.4.
The BackBone Repeater (BBR)
Replacing the BBR disturbs the following functions as far as they are used in the DECT System:
120
Communication between the various backbone sections; Barrier box function of the V.24 connection to the DECT Manager. Barrier box function of the DSP (DECT Synchronisation Port). Precision system clock.
Therefore it is strongly advised to replace the BBR out of worktime when the DECT System is practically not used. To replace the BBR execute the following procedure: 1. If the DECT Manager is connected via the V.24 barrier box function on the BBR and the DECT Manager program is still running, exit the DECT Manager program. CAUTION: CONTINUING THIS PROCEDURE MAY CAUSE DROP OF EXISTING CALLS. PREFERABLY EXECUTE THIS PROCEDURE OUTSIDE WORKING HOURS. If applicable, disconnect the V.24 cables from the DCC board and the V.24 cable to the DECT Manager PC. If applicable: - Disconnect the DSP cable (F122 connector) at the front side of the BBR. - Disconnect the precision clock interface cable (coax connector) from the front side of the BBR. This causes an alarm in the ISPBX. Take the BBR out of the shelf and move the backbone cables from the old BBR to the new BBR one by one. If applicable, move the DSP cable from the old BBR to the new one. Visiting calls and home calls with visiting boards on the backbone sections are lost now. Insert the new BBR into the shelf. Connect the cables (which you had disconnected in step 2 and 3) to the front connectors on the new BBR. If a clock alarm was generated, clear this alarm by means of OM commands. Now the DECT System must be operational again. Try to make a call via a home DCC in one shelf (backbone section) and a visiting DCC in another shelf (backbone section).
2. 3.
4.
5. 6. 7.
9.4.
LED INDICATIONS ON DCC BOARD
Note that there are two versions of firmware packages distinguished, which gives different LED indications. The table below gives an overview of the meaning of the LED indications on the DCC board with firmware package F43 0 40.xxx.
121
MEANING Power supply not present Internal test active Establishing synchronisation with backbone bus (just wait) or subscription database integrity error (See DECT Manager User Guide to "cleanup" or "remove" subscriptions).
LEDS GREEN Off Off Winking RED Off On On Off
Waiting for a command from a higher system part On
Subscription procedure active or backup/restore On of subscription data active Firmware downloading active Board is operational On On
Winking Flashing with short "on" period Off
Table 9-2 Meaning of LEDs of DCC with Firmware Packages F43040.xxx The table below gives an overview of the meaning of the LED indications on the DCC board with firmware apckage F43 1 40.xxx.
122
MEANING Power supply not present Internal test active Software download/remove in progress (by the boot program)
LEDS GREEN Off Off On RED Off On On Blinking: 1 sec. on / 1 sec. off Blinking: 2 sec. on / 2 sec. off
Waiting for a command from a higher system part On
Subscription or configuration data to be saved in On FEPROM or Backup/Restore of subscription data active Error condition: contents of subscription database is corrupt (See DECT Manager User Guide to "cleanup" or "remove" subscriptions). Board is synchronising to the BackBone.
Blinking: 2 sec. on / Off 2 sec. off Blinking: 1 sec. on / Off 1 sec. off
Simultaneous occurrence of: board synchronising Blinking: 1 sec. on / Blinking: 2 sec. on / 1 sec. off 2 sec. off to the BackBone and Subscription and Configuration Data to be saved to FEPROM. Board is operational On Off
Table 9-3 Meaning of LEDs of DCC with Firmware Packages F43140.xxx The table below gives an overview of the meaning of the LED indications on the DCC board with firmware apckage F43 2 40.xxx.
123
MEANING Power Supply not present Internal Test Active Waiting for command from higher system part Software download/remove in progress Subscription or configuration data to be saved in FEPROM or Backup/Restore of Subscription data active Board is synchronising to the BackBone Subscription database error (alarm 065:044 in the ISPBX) Simultaneous occurence of : board synchronising to the BackBone and Subscription and configuration Data to be saved to FEPROM Board is operational
GREEN LED Off Off On On On
RED LED Off On On Blinking: 1 sec. on / 1 sec. off Blinking 2 sec. on / 2 sec. off Off Off Blinking 2 sec. on / 2 sec. off
Blinking 1 sec. on / 1 sec. off Blinking 2 sec. on / 2 sec. off Blinking 1 sec. on / 1 sec. off
On
Off
Table 9-4 Meaning of LEDs of DCC with Firmware Packages F43240.xxx
9.5.
RFP LED INDICATIONS
The tables below give an overview of the meaning of the LED indications on the RFPs connected to the 24-DCC or 32-DCC board. Note that there is a difference between types of RFPs. B3xx, B4xx, B5xx The table below gives an overview of the meaning of the LED indications on the RFPs connected to the DCC board. The table is valid for RFP types: .
124
MEANING
LED
No power OR DCC-8 board no yet in service OR DCC-8 board not Off yet synchronised with the BackBone Power present but RFP not yet operational, or not yet synchronised Blinking with the DCC.Note, if there is a subscription data base error on the DCC this condition will occur even when the DCC is in service! RFP operational Table 9-5 RFP types B3xx, B4xx, B5xx LED Statusses. B6xx The table below gives an overview of the meaning of the LED indications on the RFPs connected to the DCC board. LED On
MEANING
No power OR DCC-8 board no yet in service OR DCC-8 board not Off yet synchronised with the BackBone Power present but RFP not yet operational, or not yet synchronised Blinking: 50% on / with the DCC.Note, if there is a subscription data base error on the 50% off DCC this condition will occur even when the DCC is in service! Power present, RFP synchronised with DCC, but no RF transmission (yet). RFP operational Table 9-6 RFP type B6xx LED Statusses. Blinking 90% on/ 10% off On
9.6.
DISPLAYING CIRCUITs IN USE
This section is valid for Call@Net and firmware package F43240.102 or higher. In Call@Net, there is no relation between the circuits that are used for a call and the extension number. This can be awkward in case there are problems with a specific circuit. By means of the second line maintenance command DIPERD, it is possible to display the circuit that is used for a call. DIPERD:2,<Shelf>,<Brd>;
125
8200; 00002130;
Display terminal data Extension number, preceded by leading zero's to fill up the string to 8 digits. In this case you want to display the status of DNR 2130.
The result of this command is a string of hexadecimal digits. The last two hexadecimal digits represents the circuit number in use. If it displays "FF" the circuit is not in use. If it displays "00" there has never been a call for this DNR.
126
A.
CABLES
The figure below shows the cables used to connect the DECT Manager to a DCC. These cables are summarised in Table A-1 "DECT Manager Cables"and shown individually in figures B.2 ... B.11. Note that the cables used for a C-DOS PC are the same as the cables used for a Windows PC. Note: If your DCC(s) is/are equipped with firmware package F4324x.xxx, you have to use the latest version of the Windows DECT Manager (version 3). This DECT Manager version supports the SNMP protocol over TCP/IP (via V.24), which is the management communication protocol of this firmware package. So, older DECT Manager versions cannot be used with this firmware. For further information on which DECT Manager version matches with which firmware package, consult 4. "IMPORTANT FIRMWARE ISSUES".
127
DECT Man. C-DOS / Win
8 or 9
ISOLATOR BOX
RELAY DCC
DECT Man. UNIX
ISOLATOR BOX
RELAY DCC
ISOLATOR 10 RELAY DCC BOX on BBR
DECT Man. UNIX
DECT Man. 5 or 6 C-DOS / Win
MODEM
MODEM
ISOLATOR BOX
RELAY DCC
DECT Man. UNIX
MODEM
MODEM
ISOLATOR BOX
RELAY DCC
5 or 6
MODEM
MODEM
DECT Man. UNIX
MODEM
MODEM
SPB
5 or 6
MODEM
MODEM
ISOLATOR BOX
RELAY DCC
SPB
DECT Man. UNIX 7 MODEM MODEM ISOLATOR BOX
4
RELAY DCC
Figure A-1 DECT Manager - PC Cabling Configurations.
128
CABLE No. FROM EQUIPMENT 1 DCC CONN. F122
TO EQUIPMENT DECT Manager C-DOS or Windows (via Isolator box) DECT Manager C-DOS or Windows SSM UNIX (Isolator box) SSM UNIX CONN. 25 Pin D-type female
BBR
F122
25 or 9 Pin Dtype female 25 Pin D-type male 25 Pin D-type male
2 2 3 4 5
DCC BBR DCC DCC MODEM
F122 F122 F122 F122 25 Pin D-type male 25 Pin D-type male 25 Pin D-type male 25 Pin D-type female 9 Pin D-type female F122
MODEM (Isolator 25 Pin D-type box) male SPB (Isolator box) 9 Pin D-type male DECT Manager C-DOS or Windows DECT Manager C-DOS or Windows SSM UNIX VARIOUS VARIOUS BBR 25 Pin D-type female 9 Pin D-type female 25 Pin D-type female 25 Pin D-type male 25 Pin D-type male F122
MODEM
7 8 9 10
MODEM VARIOUS VARIOUS DCC
Table A-1 DECT Manager Cables Note that cables 1, 2 and 3 are connected via an isolator box. This means that the cables are always required in combination with a one to one cable. Also note that cable 4 is used to connect the SPB. The SPB is internally provided with an
129
isolator box.
DECT Manager C-DOS
1
DCC or BBR
301 - GY / BK 302 - GY 103 - BL / BK 303 - WT / BK 105 - YW / BK 305 - PK /BK 107 - GN / BK 307 - BR / BK
BL / BK GY / BK
-2 -3
14
BR / BK
-5
Seen from wiring side
GN / BK - 6 GY - 7 PK / BK - 20 YW / BK - 8 WT / BK - 8
F122connector female
25
13
25-pole D-connector female F122connector pin number

Circuit 302 103 301 307 105 303 107 305 102 104 103 109 106 105 107 - GND - RXD - TXD - DCD - CTS - RTS - DSR Circuit 102 104 103 109 106 105 107 125 - GND - RXD - TXD - DCD - CTS - RTS - DSR - RI 7 3 2 8 5 4 20 6 22
25-pole D-connector pin number
108/2 - DTR
108/2 - DTR
Figure A-2 DCC - Isolator box on DECT Manager C-DOS / Windows Cable or BBR - DECT Manager C-DOS / Windows (25 p. COM port) Cable
130
DECT Manager C-DOS BBR

301 - GY / BK 302 GY 103 - BL / BK 303 - WT / BK 105 - YW / BK 305 - PK /BK 107 - GN / BK 307 - BR / BK YW / BK - 1 WT/ BK GN / BK GY / BK BR / BK BL / BK 1 6 2 7 3 1
PK / BK GY
- 4 - 5 5
9-pole D-connector female
F122connector pin number

Circuit 302 103 301 307 105 303 107 305 102 104 103 109 106 105 107 - GND - RXD - TXD - DCD - CTS - RTS - DSR Circuit 102 104 103 109 106 105 107 125 - GND - RXD - TXD - DCD - CTS - RTS - DSR - RI

5 2 3 1 7 8 4 6 9
108/2 - DTR
108/2 - DTR
Figure A-3 BBR - DECT Manager C-DOS / Windows Cable (9 p. COM port)
131
DECT Manager UNIX

1
14
DCC or BBR
301 - GY / BK 302 GY 103 - BL / BK
GY / BK BL / BK BR / BK
- 2 - 3 - 4
YW / BK - 5

105 - YW / BK 305 - PK /BK 107 - GN / BK 307 - BR / BK
PK / BK
- 6
GY - 7 GN / BK - 20 BR / BK - 8
13
25
25-pole D-connector male F122connect pin number

Circuit 302 103 301 307 105 107 305 102 104 103 109 106 - GND - RXD - TXD - DCD - CTS Circuit 102 104 103 109 106 105 108/2 - DTR 107 - DSR 107 - GND - RXD - TXD - DCD - CTS - RTS - DSR 7 3 2 8 5 4 20 6
108/2 - DTR
Figure A-4 DCC - Isolator Box (SSM UNIX) Cable. or BBR - SSM UNIX Cable
132
MODEM
1
14
DCC or BBR
301 - GY / BK 302 - GY 103 - BL / BK 303 - WT / BK 105 - YW / BK 305 - PK /BK 107 - GN / BK 307 - BR / BK
GY / BK BL / BK WT / BK
-2 -3 -4
YW / BK - 5
PK / BK
-6
GY -7 GN / BK - 20 BR / BK - 8
13
25
25-pole D-connector male F122connector pin number

Circuit 302 103 301 307 105 303 107 305 102 104 103 109 106 105 107 - GND - RXD - TXD - DCD - CTS - RTS - DSR Circuit 102 104 103 109 106 105 107 - GND - RXD - TXD - DCD - CTS - RTS - DSR 7 3 2 8 5 4 20 6
108/2 - DTR
108/2 - DTR
Figure A-5 DCC/BBR - MODEM Cable
133
SPB DCC
301 - GY / BK 102 RD 302 GY 103 - BL / BK 303 - WT / BK 105 - YW / BK 305 - PK / BK 107 - GN / BK 307 - BR / BK GN / BK GY / BK BR / BK BL / BK PK / BK RD YW / BK WT / BK 1 6 2 7 3 8 4 9 5 5 1
9-pole D-connector male
F122connector female F122connector pin number

Circuit 302 103 301 307 105 303 107 305 102 104 103 109 106 105 107 - GND - RXD - TXD - DCD - CTS - RTS - DSR Circuit 102 104 103 109 106 105 107 - GND - RXD - TXD - DCD - CTS - RTS - DSR 5 2 3 1 8 7 4 6
108/2 - DTR
108/2 - DTR
Figure A-6 DCC (or BBR) - SPB Cable
134
MODEM
1
DECT Manager C-DOS

1
14 23456720 WT YW GN PK RD YW GN PK RD
14 - 2 - 3 - 4 - 5 - 6

WT
- 7 - 20 - 8
13
25
25
13
25-pole D-connector male 25-Pole D-connector pin number

Circuit 7 3 2 4 5 20 6 102 104 103 106 105 107 - GND - RXD - TXD - CTS - RTS - DSR Circuit 102 104 103 109 106 105 107 - GND - RXD - TXD - DCD - CTS - RTS - DSR
25-pole D-connector female 25-pole D-connector pin number

7 3 2 8 5 4 20 6
108/2 - DTR
108/2 - DTR
Figure A-7 MODEM - DECT Manager C-DOS / Windows (25 Pin D-type Connector) Cable
135
MODEM
1
14 23456720 WT YW GN PK RD
DECT Manager C-DOS

1 6 2 7 3 8 4 1
GN RD YW PK WT
- 5

13 25

Circuit 7 3 2 4 5 20 6 102 104 103 106 105 107 - GND - RXD - TXD - CTS - RTS - DSR Circuit 102 104 103 109 106 105 107 - GND - RXD - TXD - DCD - CTS - RTS - DSR 5 2 3 1 8 7 4 6
108/2 - DTR
108/2 - DTR
Figure A-8 MODEM - DECT Manager C-DOS / Windows (9 Pin D-type Connector) Cable
136
MODEM
1
DECT Manager UNIX

1 23456720 WT BR YW GN PK RD GN YW PK - 2 - 3 - 4 - 5
14
14
BR WT
- 6 - 7 - 8
13
25
13
25

Circuit 7 3 2 4 20 102 104 103 106 - GND - RXD - TXD - CTS Circuit 102 104 103 109 106 105 108/2 - DTR 107 - DSR - GND - RXD - TXD - DCD - CTS - RTS
25-pole D-connector male 25-pole D-connector pin number

7 3 2 8 5 4 6
Figure A-9 MODEM - DECT Manager UNIX Cable
137
VARIOUS
1
VARIOUS
1
14 23456720 822 -
14 YW GN PK RD BL WT BR GY BK YW GN PK RD - 2 - 3 - 4 - 5 - 6 - 7 - 20 - 8 - 22
BL WT BR GY BK
13
25
25
13

Circuit 7 3 2 8 4 5 20 6 22 102 104 103 109 106 105 107 125 - GND - RXD - TXD - DCD - CTS - RTS - DSR - RI Circuit 102 104 103 109 106 105 107 125 - GND - RXD - TXD - DCD - CTS - RTS - DSR - RI
25-pole D-connector female 25-pole D-connector pin number

7 3 2 8 5 4 20 6 22
108/2 - DTR
108/2 - DTR
Figure A-10 One to One (25 to 25 Pin) Cable
138
VARIOUS
1
14 23456720 822 YW GN PK RD BL WT BR GY BK GY BL GN RD YW PK BR BK WT 1 6 2 7 3 8 4 9 5
VARIOUS
1
13
25

Circuit 7 3 2 8 4 5 20 6 22 102 104 103 109 106 105 107 125 - GND - RXD - TXD - DCD - CTS - RTS - DSR - RI Circuit 102 104 103 109 106 105 107 125 - GND - RXD - TXD - DCD - CTS - RTS - DSR - RI 5 2 3 1 8 7 4 6 9
108/2 - DTR
108/2 - DTR
Figure A-11 One to One (25 to 9 Pin) Cable
139
B.
-
UPGRADE 24 ->32 DCC
It is possible to upgrade a 24-DCC system to a 32-DCC system. To do this, you need: DCC Boards V.4 (9562 158 792xx) Upgrade kit 9562 158 95000 for each board.
Note: If you perform an upgrade, perform it on all DCC boards in the system! Note: You can NOT upgrade the "old" version of 24-DCC boards (9562 158 790xx or 9562 158 791xx). These boards have to be sent to the factory for upgrading. Necessary actions per DCC, repeat these actions for all DCC boards: 1. Make a backup of the subscription data in the DCC by means of the DECT Manager. Making a backup is for safety reasons; during upgrade, the subscription data in the board will not be overwritten, but if something goes wrong then it is handy to have a backup file which can be restored into the DCC. 2. Set the DCC board out of service; 3. Take out the DCC board and remember the board position where it came from (you must place it back into that same position after upgrading). Take the necessary anti-static precautions! 4. Remove the small BPIB (Backbone Plug-In Board) from the DCC. This board contains one IC that controls the backbone (i.c. for the 24-DCC version) 5. Insert the new BPIB that is part of the upgrade kit; 6. Remove the bootprom from the DCC board; 7. Insert the new bootprom that is part of the upgrade kit; 8. put the sticker with the new 12 NC number on the board: 9562 158 960xx; 9. Insert the DCC. Keep in mind that configuration rules are different for the 32-DCC version: You can use the same board positions, but you can now also make use of Unit Groups 0 and 7. See chapter 2. "HARDWARE INSTALLATION"and Figure I-7 "Diagram 300", Figure I-8 "Diagram 301", Figure I-9 "Diagram 302"and Figure I-10 "Diagram 303". 10. Load the new DCC firmware package; 11. If you made configuration changes in Step 8, do not forget to make these changes in the DECT Manager as well. 12. Put the DCC boards back into their original position in the shelf/shelves. If the subscription data is not valid anymore, or the DCC boards have been swapped between the various positions, restore the subscription data by means of the DECT Manager.
140
C.
SUPPORTED 32-DCC DECT CONFIGURATIONS
001 002 003 004 D C C D C C
005 P S U S / M L 105
001 002 003 004 005 006 007 008 009 010 D C C D C C D C C D C C D C C
011 P S U M L
101 102 103 104 D C C P M C M C C P U M E
101 102 103 104 105 106 107 108 109 D C C D C C D C C P M C M C C P U M E
110
Transformer and Rectifier Compartment
Transformer and Rectifier Compartment
X01 X02 X03 X04 X05 X06 X07 X08 X09 X10 X11 X12 X13 X14 X15 X16 X17 X18 X19 X20 X21 X22 X23 D C C D C C D C C D C C D C C D C C D C C D C C P M C M C P C T C I P C T C I
P S U X X
Figure C-1 Single Backbone Configurations (32-DCC)
141
001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 016 017 018 019 020 021 022 023 D C C D C C D C C D C C D C C D C C D C C D C C P M C * * P S U X X
101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 D C C B B R D C C D C C D C C D C C D C C D C C D C C P M C * * P S U X X
201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 D C C D C C D C C D C C D C C D C C D C C D C C P M C * * P S U X X
301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 D C C D C C D C C D C C D C C D C C D C C D C C P M C * * P S U X
Figure C-2 Maximum Backbone Configuration in an iS3050/iS3070 System (32-DCC)
142
D.
HARDWARE CONFIGURATIONS
In the following figures, the hardware configurations are depicted. Together with the hardware configurations the addressing is depicted.
D.1.
BASED ON FIRMWARE F43040.XXX AND F43140.XXX
143
- Possible DCC positions - Signalling Groups (S.G.) For DCCs - DCC Addresses (for reference in DECT Manager) - RFP ids (as can be displayed on handset)
iS3010
Shelf 1
01 03 S.G. 0920 05 (SSW805) 07 or S.G. 6204 (SSW810)
09 0B 0D 0F
P S U
01 02 03 04 00 01 RFP ids 00 11 13 S.G. 0920 15 (SSW805) 17 or S.G. 6204 (SSW810) 01 02 03 04 02 02 01
Position Unit Group DCC Addr.
Shelf 2
P S U
IS3030
Shelf 1
01 S.G. 03 0920 05 (SSW805) 07 or S.G. 6204 (SSW810)
09 0B 0D 0F
11 13 15 17
19 1B 1D 1F
21 23 25 27
P S U
01 02 03 04 05 06 07 08 09 10 00 01 02 03 04 00 29 S.G. 2B 0920 2D (SSW805) 2F or S.G. 6204 (SSW810) 01 31 33 35 37 02 39 3B 3D 3F 03 04
Shelf 2
01 02 03 04 05 06 07 08 09 Position Unit Group 05 06 07 05 06 07 DCC Addr.
144
IS3050 / iS3070 / iS3090
01 S.G. 03 0920 (SSW805) 05 or 07 BACKBONE S.G. SECTION 6204 0 (SSW810)
09 0B 0D 0F
11 13 15 17
19 1B 1D 1F
21 23 25 27
29 2B 2D 2F
31 33 35 37
39 3B 3D 3F RFP ids
P S U
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 00 00 41 S.G. 43 0921 (SSW805) 45 or 47 BACKBONE S.G. SECTION 6205 1 (SSW810) 01 01 49 4B 4D 4F 51 53 55 57 02 02 03 03 59 5B 5D 5F 04 04 61 63 65 67 05 05 69 6B 6D 6F 06 06 71 73 75 77 07 07 79 7B 7D 7F
P S U
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 00 01 02 03 04 05 06 07 16 81 S.G. 83 0922 (SSW805) 85 or 87 BACKBONE S.G. SECTION 6206 2 (SSW810) 17 89 8B 8D 8F 18 91 93 95 97 19 99 9B 9D 9F 20 A1 A3 A5 A7 21 A9 AB AD AF 22 B1 B3 B5 B7 23 B9 BB BD BF
P S U
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 00 32 C1 S.G. C3 0923 (SSW805) C5 or C7 BACKBONE S.G. SECTION 6207 3 (SSW810) 01 33 C9 CB CD CF 02 34 D1 D3 D5 D7 03 35 D9 DB DD DF 04 36 E1 E3 E5 E7 05 37 E9 EB ED EF 06 38 F1 F3 F5 F7 07 39 F9 FB FD FF
P S U
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 00 48 01 49 02 50 03 51 04 52 05 53 06 54 07 55
145
D.2.
BASED ON FIRMWARE F43240.XXX.

01 09 0B 0D 0F
- Possible DCC positions - Signalling Groups (S.G.) For DCCs - DCC Addresses (for reference in DECT Manager) - RFP ids (as can be displayed on handset)
iS3010
Shelf 1
S.G. 0920 (SSW805) or S.G. 6204 (SSW810)
03 05 07
P S U
01 02 03 04 00 RFP ids S.G. 0920 (SSW805) or S.G. 6204 (SSW810) 1 11 13 15 17 2 01
Shelf 2
P S U
01 02 03 04 02 3 01 S.G. 03 0920 05 (SSW805) 07 or S.G. 6204 (SSW810) 09 0B 0D 0F 11 13 15 17 19 1B 1D 1F 21 23 25 27
IS3030
Shelf 1
P S U
01 02 03 04 05 06 07 08 09 10 00 1 S.G. 0920 2D (SSW805) 2F or S.G. 6204 (SSW810) 29 2B 2 31 33 35 37 01 3 39 3B 3D 3F 02 4 03 5 04
Shelf 2
01 02 03 04 05 06 07 08 09 Position Unit Group 05 06 07 6 7 8 DCC Addr.
146
IS3050 / iS3070 / iS3090
01 S.G. 03 0920 (SSW805) 05 or 07 BACKBONE S.G. SECTION 6204 0 (SSW810)
09 0B 0D 0F
11 13 15 17
19 1B 1D 1F
21 23 25 27
29 2B 2D 2F
31 33 35 37
39 3B 3D 3F RFP ids
P S U
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 00 1 41 S.G. 43 0921 (SSW805) 45 or 47 BACKBONE S.G. SECTION 6205 1 (SSW810) 2 49 4B 4D 4F 01 3 51 53 55 57 02 4 59 5B 5D 5F 03 5 61 63 65 67 04 6 69 6B 6D 6F 05 7 71 73 75 77 06 8 79 7B 7D 7F 07
P S U
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 00 01 02 03 04 05 06 07 9 81 S.G. 83 0922 (SSW805) 85 or 87 BACKBONE S.G. SECTION 6206 2 (SSW810) 10 89 8B 8D 8F 11 91 93 95 97 12 99 9B 9D 9F 13 A1 A3 A5 A7 14 A9 AB AD AF 15 B1 B3 B5 B7 16 B9 BB BD BF
P S U
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 00 17 C1 S.G. C3 0923 (SSW805) C5 or C7 BACKBONE S.G. SECTION 6207 3 (SSW810) 01 18 C9 CB CD CF 02 19 D1 D3 D5 D7 03 20 D9 DB DD DF 04 21 E1 E3 E5 E7 05 22 E9 EB ED EF 06 23 F1 F3 F5 F7 07 24 F9 FB FD FF
P S U
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 00 25 01 26 02 27 03 28 04 29 05 30 06 31 07 32
147
E.
REMOTE CONNECTION FOR SNMP
Note: Information in this appendix is applicable for 24-DCC or 32-DCC firmware F43240.203 or higher. Lower firmware versions might give problems!!! For a remote DECT Manager connection you need a modem at both sides of the connection. Modem at DCC Side Make sure that firmware F43240. 203 or higher is installed in the DCC. The modem must be a 56 kb/s type, because the DCC communication speed is 38,4 kb/s. When you use a US Robotics modem, the modem works fine with the default factory settings. If you are not sure that the modem works with the default factory settings, initialize the modem as given in the following table. When you use a Dynalink modem, you must initiate the modem with the AT commands as given in the following table: Dynalink Modem initialization commands for modem connection to DCC AT&F AT&K0 AT&W0 AT&W1 ATY0 Meaning of command:
US Robotics initialization commands for setting to factory defaults (required for DCC connection) AT&F AT&W0 AT&W1 ATY0
Set to factory default Flow control disabled Write setting into nonvolatile memory 0 Write setting into nonvolatile memory 1 At power up, start modem with settings in non-volatile memory 0
Table E-1 Modem Settings for modem at DCC side. The cable between the DCC and the Modem is depicted in A . "CABLES" Modem at PC Side The modem at the PC side must use the default factory settings. This is automatically achieved when you install the appropriate modem drivers in your Windows environment.
148
F.
MORE DECT CLUSTERS IN ONE UNIT
Note: Information in this appendix is applicable for Call@Net or higher and PMC package F410.05.01 / F510.05.01 or higher One DECT cluster comprises DCC cards and optionally a BBR connected to one BackBone configuration with seamless handover. The BackBone configuration can consist of up to four BackBone sections. It is possible to create up to four DECT clusters in the same ISPBX. This can be necessary in case of one or more RPMs or in case the ISPBX is shared by more than one company. Note: There is NO (seamless) handover between the DECT clusters!!!!!! Each DECT cluster has it's own PARI. The PARI must be entered in a signalling group. This means that you must enter different PARIs in different signalling groups. Beside this, you must carefully assign the signalling groups, having a certain PARI, to the DCC in that specific cluster. Table F-1 "Signalling Groups for up to Four DECT Clusters."gives an overview of the available signalling groups.
149
DECT Cluster
Umbrella Signalling Group SG 9600
BackBone Section
DCC Signalling Groups Call@Net SG 6204 SG 6205 SG 6206 SG 6207 SG 6208 SG 6209 SG 620A SG620B SG 620C SG 620D SG 620E SG 620F SG 6210 SG 6211 SG 6212 SG 6213
0 1 2 3
SG 9601
0 1 2 3
SG 9602
0 1 2 3
SG 9603
0 1 2 3
Table F-1 Signalling Groups for up to Four DECT Clusters. Enter each PARI in a different umbrella signalling group (SG 9600, SG9601, SG 9602, SG 9603) per cluster. If necessary change/adapt parameters in the umbrella signalling group that belongs to the cluster. Under each umbrella signalling group, there are DCC signalling groups for each backbone section in the cluster. You must assign these signalling groups to the DCCs belonging to that specific cluster.
150
G.
CUSTOMIZING SYSTEM PARAMETERS
Note: Information in this appendix is applicable for PMC package F410.05.01 / F510.05.01 or higher.
G.1.
SYSTEM PARAMETERS
The signalling group(s) 960X contains parameters for the DECT System. Note that in a single DECT cluster system, only SG 9600 is used. In a multi DECT cluster system, SG 9600 up to SG9603 are used. In a multi cluster DECT system, each SG 960X group contains cluster specific parameters like the PARI and, if applicable, SARI. Normally you only need to fill in the PARI in bytes 1 ... 4 and you need to fill in byte 9 for messaging and/or Call@Net concentrated mode. However, SG 960X contains a few bit settings that can be useful for special applications. CAUTION: THE POSSIBILITY TO CHANGE DEFAULT SG960X SETTINGS IS A SERVICE AND NOT A SUPPORTED FEATURE OF THE DECT SYSTEM. ENTERING INCORRECT VALUES WILL CAUSE THE DECT SYSTEM TO MALFUNCTION!! BY CHANGING A BIT/BYTE, THE USER ACCEPTS FULL RESPONSIBILITY FOR THE CONSEQUENCES OF THIS CHANGE.
G.2.
SG960X BYTES AND THEIR MEANING
Table G-1 "SG9600 Bytes and their Function." gives you information about the Signalling Group bytes and their purpose:
151
FUNCTION BYTE PARI 1 ... 4
WORD LENGTH 4
DEFAULT VALUE 0
RANGE (HEX.) 00 ... FF for each byte. Byte 1 = Most significant byte of the PARI, byte 4 is the least sign. 0 .. 3 00 ... FF 00... 03 + 00 ... FF 11 ... FF
Security level 8 System Type 9 Used carriers 10 + 11 Page Timer / 12 Retry value
1 1 2
0 0 03 + FF
33 Lowest nibble = retries Highest nibble = time in seconds
Display time and date on PP. SARI
14
00
00=Display time and data on PP is enabled. 08=Display time and date on PP is disabled.
17 ... 20
FF
00 ... FF for each byte. Byte 17 = Most significant byte of the SARI, byte 20 is the least sign. (see also H . "ENTERING DATA INTO DCC SIGNALLING GROUPS DIRECTLY"
Table G-1 SG9600 Bytes and their Function. Note: The values mentioned in this Appendix are in hexadecimal. However, convert these values to decimal when entering them in the system by means of CHPMPD. The following overview describes the functions: PARI
152
The PARI consists of 4 bytes. Byte 1 represents the most significant byte of the PARI and byte 4 represents least significant byte. Note that the contents of these bytes must be decimal, while the PARI is hexadecimal.
PARI HEXADECIMAL AA BB CC DD Convert to DECIMAL Fill-in in SG9600 in Byte:
RRR SSS TTT UUU
4 3 2 1
Figure G-1 Entering the PARI. Security Level This byte defines the level of security used in DECT communication, according to the following overview: Ciphering Portable ON ON OFF OFF Authentication ON OFF ON OFF
Value 00 01 02 03
The security_level is predefined to 00 (highest level). System Type This byte defines system properties. Be careful with changing bits in this byte. It might cause your system to malfunction. Table G-2 "Meaning of Bits in Byte 9 (System Type)."following bits have useful functions.
153
Bit 0 (LSB) 1
Function 0 =.Unconcentrated system, max 30 subscriptions (SSW 805 or lower) 1 = Concentrated system, max 510 subscriptions (Call@Net) 0 = Cordless Terminal Adapters (CTA) not supported 1 = Cordless Terminal Adapters (CTA) supported
0 = The system is an iS3000 based system 1 = The system is a non-iS3000 based system
3 4
0 = BMC slot 11/23 is enabled. Default setting, do not change! 0 = E2 low data rate profile (messaging) disabled 1 = E2 low data rate profile (messaging) enabled
0 = Synchronisation window default setting (7 bits), bit 6 must also be "0". 1 = Synchronisation window narrowed (4 bits), bit 6 must also be "1".
0 = Synchronisation threshold default setting, bit 5 must also be "0". 1 = Synchronisation threshold high, bit 5 must also be "1".
7 (MSB)
0 = Normal operation 1 = Development setting
Table G-2 Meaning of Bits in Byte 9 (System Type). The synchronisation bits (bit 5 and 6) must always be changed in pairs. If bit 5 is "1" bit 6 must be "1" as well. It changes capturing the synchronisation bit string from the received data. If the bits 5 and 6 are "1" the synchronisation already takes place when 4 bits for synchronisation are received correctly instead of 7 bits. Also the threshold level of the received bits is set higher. This is can be useful in an environment with a lot of reflections.
Note: Change bits 5 and 6 only if strictly necessary because of a lot of reflections in the environment. In all other cases leave these bits "0". Page Timer/Retry Value The default value is 33 (hex). The first digit represents the so-called page timer, which is default 3 seconds. The second digit represents the Page Retry Counter, which is default 3 times. This means that a call to a portable, which is switched off or out of range, will be
154
retried after 3 seconds. In total 3 retries will be done. Used carriers Byte 10 represents the most significant bits and byte 11 the least significant bits. There are ten carriers, represented in the bits in these bytes. If a bit is a "1" it means that the carrier is enabled, a "0" means that the carrier is disabled. The bits are classified as follows: Bit 0 1 2 3 4 5 6 7 0 1 Carrier 9 8 7 6 5 4 3 2 1 0 Frequency (MHz) 1881,792 1883,520 1885,248 1886,976 1888,704 1890,432 1892,160 1893,888 1895,616 1897,344
Byte 11 11 11 11 11 11 11 11 10 10
Table G-3 Bits and Frequency Relations See ETSI specification for more info. Disable displaying Time and Date on PP Several types of PPs support displaying time and date. This time and date comes from the ISPBX. By means of changing the contents of byte 14 to decimal/hexadecimal "8", the displaying of time and date is disabled. SARI (Only applicable for Call@Net Software) The SARI consists of 4 bytes. Byte 17 represents the most significant byte of the PARI and byte 20 represents least significant byte. Note that the contents of these bytes must be decimal, while the SARI is hexadecimal. The SARI is an optional item.
155
SARI HEXADECIMAL AA BB CC DD
Convert to DECIMAL
Fill-in in SG960x in Byte:
FFF GGG HHH JJJ
20 19 18 17
Figure G-2 Entering the SARI.
156
H.
ENTERING DATA INTO DCC SIGNALLING GROUPS DIRECTLY
Note: Information in this appendix is applicable for PMC packages F410.05.01 / F510.05.01 or higher Normally, the PARI is entered in the umbrella signalling group 9600 (or in Call@Net with more than one iSMobilie cluster, other PARIs must be entered in SG 9601, SG9602, SG9603). The contents of this (these) umbrella signalling group(s) is automatically copied into the underlying DCC signalling groups. However, it is possible to enter the PARI (and other parameters) directly into the underlying signalling group(s). If something is entered directly into these underlying signalling groups, it has preference over the values in the umbrella signalling groups. Generally, you never have to enter something directly into these underlying signalling groups. However, if you want to split up one DECT cluster into two (or up to four) smaller clusters, you can enter different PARIs into these signalling groups. Note: Never connect the BackBones of different clusters together!!! (So, you can never have more than one cluster in a shelf!) Note: If you enter the PARI in the underlying signalling groups, then you must enter the other parameters, like messaging bit "on", in the underlying signalling groups as well. You cannot use the umbrella group anymore. Besides the PARI, it is also possible to enter a SARI (Secondary Access Right Identifier). The PARI (and/or SARI) consists of eight hexadecimal digits. However the number must be entered in decimal. Therefore convert the PARI (and/or SARI) into decimal values as follows:
157
PARI HEXADECIMAL AA BB CC DD
DECIMAL
RRR SSS TTT UUU
SARI HEXADECIMAL AA BB CC DD
DECIMAL
FFF GGG HHH JJJ
There is a difference in entering data between SSW 805 and Call@Net. Follow the instructions in the section that is applicable for your SSW type.
H.1.
SSW 805
For SSW 805 the underlaying signalling groups are as follows:
BackBone section 0 BackBone section 1 BackBone section 2 BackBone section 3
SG 9600 SG 0920 SG 0921 SG 0922 SG 0923
Data must be entered by means of the OM command CHPMPD. The following overview shows you how to enter the PARI and other relevant parameters.
158
CHPMPD: 0,092X;
Equals the following byte in SG 960x
Adapt the SG for DCC, enter PARI; 8,1,0; 9,1,1; 10,1,26; 11,1,UUU; PARI Byte 1 12,1,0; 13,1,1; 14,1,27; 15,1,TTT; PARI Byte 2 16,1,0; 17,1,1; 18,1,28; 19,1,SSS; PARI Byte 3 20,1,0; 21,1,1; 22,1,29; 23,1,RRR; PARI Byte 4 Security level 24,1,0; 25,1,1; 26,1,33; 27,1,AAA;
Byte 1 (1,1,UUU)
Byte 2 (2,1,TTT)
Byte 3 (3,1,SSS)
Byte 4 (4,1,RRR)
Byte 8 (8,1,AAA) Security level (see Appendix G . "CUSTOMIZING SYSTEM PARAMETERS")
System Type 28,1,0; 29,1,1; 30,1,34; 31,1,BBB;
Sytem Type (see Appendix Byte 9 (9,1,BBB) G . "CUSTOMIZING SYSTEM PARAMETERS")
159
Used carriers 32,1,0; 33,1,1; 34,1,35; 35,1,CCC;
Byte 10 (10,1,CCC) Used Carriers (see Appendix G . "CUSTOMIZING SYSTEM PARAMETERS"
36,1,0; 37,1,1; 38,1,36; 39,1,DDD;
Byte 11 (11,1,DDD) Used Carriers (see Appendix G . "CUSTOMIZING SYSTEM PARAMETERS"
Page Timer / Retry value 40,1,0; 41,1,1; 42,1,37; 43,1,EEE;
Page Timer / Retry value Byte 12 (12,1,EEE) (see Appendix G . "CUSTOMIZING SYSTEM PARAMETERS"
In-Service Delay 60,1,0; 61,1,1; 62,1,46; 63,1,KKK;
Delays the coming inservice with KKK msec.
Byte 16 (16,1,KKK)
If the decimal values which needs to be entered, contain leading zeros, these can be omitted. With the command CHPMPD signalling data is stored in the PMC. To download this data, set the PMC(s) Out of Service and In Service again or perform a warmstart.
H.2.
Call@Net
For Call@Net the underlaying signalling groups are as follows:
160
BackBone section 0 BackBone section 1 BackBone section 2 BackBone section 3
SG 9600 SG 6204 SG 6205 SG 6206 SG 6207
SG 9601 SG 6208 SG 6209 SG 620A SG 620B
SG 9602 SG 620C SG 620D SG 620E SG 620F
SG 9603 SG 6210 SG 6211 SG 6212 SG 6213
Data must be entered by means of the OM command CHPMPD. The following overview shows you how to enter the PARI and other relevant parameters.
CHPMPD: 0,62XX;
Equals the following byte in SG 960x
Adapt the SG for DCC, enter PARI; 4,1,0; 5,1,1; 6,1,26; 7,1,UUU; PARI Byte 1 8,1,0; 9,1,1; 10,1,27; 11,1,TTT; PARI Byte 2 12,1,0; 13,1,1; 14,1,28; 15,1,SSS; PARI Byte 3 16,1,0; 17,1,1; 18,1,29; 19,1,RRR; PARI Byte 4 Security level 20,1,0; 21,1,1;
Byte 1 (1,1,UUU)
Byte 2 (2,1,TTT)
Byte 3 (3,1,SSS)
Byte 4 (4,1,RRR)
161
22,1,33; 23,1,AAA;
Byte 8 (8,1,AAA) Security level (see Appendix G . "CUSTOMIZING SYSTEM PARAMETERS")
System Type 24,1,0; 25,1,1; 26,1,34; 27,1,BBB;
Sytem Type (see Appendix Byte 9 (9,1,BBB) G . "CUSTOMIZING SYSTEM PARAMETERS")
Used carriers 28,1,0; 29,1,1; 30,1,35; 31,1,CCC;
Byte 10 (10,1,CCC) Used Carriers (see Appendix G . "CUSTOMIZING SYSTEM PARAMETERS"
32,1,0; 33,1,1; 34,1,36; 35,1,DDD;
Byte 11 (11,1,DDD) Used Carriers (see Appendix G . "CUSTOMIZING SYSTEM PARAMETERS"
Page Timer / Retry value 36,1,0; 37,1,1; 38,1,37; 39,1,EEE;
Page Timer / Retry value Byte 12 (12,1,EEE) (see Appendix G . "CUSTOMIZING SYSTEM PARAMETERS"
SARI
162
44,1,0; 45,1,1; 46,1,47; 47,1,FFF; 48,1,0; 49,1,1; 50,1,48; 51,1,GGG; 52,1,0; 53,1,1; 54,1,49; 55,1,HHH; 56,1,0; 57,1,1; 58,1,50; 59,1,JJJ; In-Service Delay 60,1,0; 61,1,1; 62,1,46; 63,1,KKK;
SARI Byte 1
Byte 17 (17,1,JJJ)
SARI Byte 2
Byte 18 (18,1,HHH)
SARI Byte 3
Byte 19 (19,1,GGG)
SARI Byte 4
Byte 20 (20,1,FFF)
Delays the coming inservice with KKK msec.
Byte 16 (16,1,KKK)
If the decimal values that needs to be entered, contain leading zeros, these can be omitted. With the command CHPMPD signalling data is stored in the PMC. To download this data, set the PMC(s) Out of Service and In Service again or perform a warmstart.
163
I.
DIAGRAMS
To shelf 4 in other cabinet
To shelf 1 9562-161-65000 To shelf 2 9562-161-63000 To shelf 3 9562-161-65000 To shelf 4 in other cabinet 9562-161-66000
Dirty (analog) Cabling side
Figure I-1 Backbone cabling example, new cabinet with built-in MDF
164
To shelf 1 9562-161-65000 To shelf 2 9562-161-63000 To shelf 3 9562-161-65000 To shelf 4 9562-161-66000
Dirty (analog) Cabling side
Figure I-2 Backbone cabling example, new cabinet witout MDF
165
001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 016 017 018 019 020 021 022 023 D C C D C C D C C D C C D C C D C C D C C D C C P M C P S U X X
101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 D C C B B R D C C D C C D C C D C C D C C D C C D C C P M C P S U X X
201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 D C C D C C D C C D C C D C C D C C D C C D C C P M C P S U X X
Figure I-3 BackBone Cabling (Current Configuration) Backbone cabling example, old cabinet iS3050/3070. Separate analogue/digital cabling sides, analogue right, digital left.
166
Dect-sync. port cable(s) 9562-161-63000
Figure I-4 DECT-sync cabling, new iS3030 cabinet.
167
Figure I-5 DECT-sync cabling, old iS3030 cabinet.
168
Figure I-6 DECT-sync cabling, new iS3050/3070 cabinet.
169
CONFIGURATION SELECTION GUIDE

START HERE !! Select your DECT System Type 24-DCC (old) Properties: - Delivery dates: <01-06-1997 - DCC types: 9562 158 790xx 9562 158 791xx - BBR type: 9562 158 621xx 9562 158 622xx
See diagram 301
For system expansions, Upgrade to 24-DCC (new) (Requires upgrade for DCCs, BBRs and PM1100/CSM (if applicable) 24-DCC (new) Properties: - Delivery dates: >01-06-1997 - DCC types: 9562 158 792xx - BBR type: 9562 158 623xx
Note: Only PM1100 is field upgradeable; DCC and BBR must be sent to factory for upgrade; CSM is not upgradeable
See diagram 302
Only in case the maximum system configuration has been reached with 24-DCC and the system requires expansion, then upgrade to 32-dcc version. (requires upgrade for DCCs: field upgrade) 32-DCC (new) Properties: - Delivery dates: >01-06-1997 - DCC types: 9562 158 960xx - BBR type: 9562 158 623xx DCC - 8 Properties: - Delivery dates: > 01-12-2000 - DCC types: 9600 021 2700x - BBR type: 9600 021 2500x MIXED CONFIGURATION 32-DCC + DCC - 8
See diagram 303
See diagram 304
See diagram 305 + 306
D300
Figure I-7 Diagram 300
170
CONFIGURATION RULES AND STRAP SETTINGS FOR 24-DCC VERSION 9562 158 790xx and 9562 158 791xx
Configuration rules Strap settings X10.1** Pos. 101-102 Pos. 101-102
CAUTION
24-DCC (old)
Check that the board 12-nc of all boards is: 9562 158 790xx or 9562 158 791xx
iS3010
1st DCC in board pos. 103 2nd DCC in board pos. 201
This configuration is based on the following equipment:
DCC: 9562 158 790xx 9562 158 791xx
BBR: 9652 155 62xxx
iS3030
If not, then go back to diagram 300
1st DCC in board pos. 103 2nd DCC in board pos. 203 Other DCCs in board Pos.105....201
Pos. 101-102 Pos. 101-102 Pos.102...103
PM1100: 9562 155 2220x
Backbone cables < 3 m
iS3030 iS3070 iS3090
DCC firmware: F43040.1xx
12-nc of ALL PM1100* Yes shelves used for DCC is 9562 155 2210x
board pos 102....113 allowed
Pos. 102-103
No
12-nc of ALL PM1100* shelves used for DCC is Yes a mix of 9562 155 2210x and 9562 155 2220x Upgrade PM1100 shelves to 9562 155 2220x
No
12 nc of ALL PM1100* shelves used for DCC is 9562 155 2220x
* If CSM shelf then: - PM1100 9562 155 2210x equals CSM 9562 155 5810x - PM1100 9562 155 2220x equals CSM 9562 155 5820x -CSM 9562 155 5810x is NOT (field) upgradeable to CSM 9562 155 5820x
More than one PM with No 1st DCC in board pos. 103 other DCCs in 105....113 DECT?
Pos. 101-102 Pos. 102-103
Yes
**Other straps and strap positions on the DCC are depicted in section 2.4.
1st DCC in board pos. 103 other DCCs in 105....113
Pos. 101-102 Pos. 102-103
D301
171
CONFIGURATION RULES AND STRAP SETTINGS FOR 24-DCC VERSION 9562 158 792xx
Configuration rules Strap settings X10.1** 1st DCC in board pos. 103 2nd DCC in board pos. 201 Pos. 101-102 Pos. 101-102
CAUTION
24-DCC (new)
Check that the board 12 nc of all boards is: 9562 158 792xx
iS3010
DCC: 9562 158 792xx
BBR: 9652 155 623xx
iS3030
If not then go back to diagram 300
Pos. 101-102 Pos. 101-102 Pos.102...103
PM1100: 9562 155 2220x
IS3050 iS3070 iS3090
No
More than one PM with No 1st DCC in board pos. 103 other DCCs in 105....113 DECT? Upgrade PM1100 Shelves to 9562 155 2220x Pos. 101-102 Pos. 102-103
Yes
Pos. 102-103 Pos. 102-103
* If CSM shelf then: - PM1100 9562 155 2210x equals CSM 9562 155 5810x - PM1100 9562 155 2220x equals CSM 9562 155 5820x -CSM 9562 155 5810x is NOT (field) upgradeable to CSM 9562 155 5820x **Other straps and strap positions on the DCC are depicted in section 2.4
D302
172
CONFIGURATION RULES AND STRAP SETTINGS FOR 32-DCC VERSION 9562 158 9600x
Configuration rules Strap settings X10.1** Pos. 101-102 Pos. 101-102 Pos .102-103
CAUTION
32-DCC
Check that the board 12 nc of all boards is: 9562 158 9600x
iS3010
1st DCC in board pos. 101 2nd DCC in board pos. 201 3nd DCC in board pos.103
DCC: 9562 158 960xx
BBR: 9652 155 623xx
iS3030
If not then go back To diagram 300
Pos. 101-102 Pos. 101-102 Pos.102...103
PM1100: 9562 155 2220x
IS3050 iS3070 iS3090
No
More than one PM with No 1st DCC in board pos. 101 other DCCs in 103....115 DECT? Upgrade PM1100 shelves to 9562 155 2220x Pos. 101-102 Pos. 102-103
Yes
Pos. 102-103 Pos. 102-103
* If CSM shelf then: - PM1100 9562 155 2210x equals CSM 9562 155 5810x - PM1100 9562 155 2220x equals CSM 9562 155 5820x -CSM 9562 155 5810x is NOT (field) upgradeable to CSM 9562 155 5820x **Other straps and strap positions on the DCC are depicted in section 2.4
D303
173
CONFIGURATION RULES AND STRAP SETTINGS FOR DCC-8 VERSION

DCC - 8 Check that the board 12nc of all boards is: 9562 212 2000 If not, then go back T o diagram 300 iS3010
st
Configuration rules 1 DCC in board position 101 2nd DCC in board position 201 nd 3 DCC in board position 103 1 DCC in board position 101 2nd DCC in board position 205 Other DCC in board position 103....203
st
Strap settings X6.1** position 101-102 position 101-102 position 102-103 position 101-102 position 101-102 position 102-103
iS3030
iS3050 iS3070 iS3090
12-nc of ALL PM1100* Yes shelves used for DCC is 9562 155 2220x No Upgrade PM1100* shelves to 9562 155 2220x
1 DCC in board position 101 Other DCC in board position 103....115
st
position 101-102 position 102-103
CAUTION This configutation is based on the Following equipment: DCC-8: BBR-V2: 9600 021 2700x 9600 021 2500x
PM1100: 9562 155 2220x Backbone cables < 5 meter DCC firmware : F460xy.yzz
* If CSM shelf then: - PM1100 9562 155 2210x equals CSM 9562 155 5810x - PM1100 9562 155 2220x equals CSM 9562 155 5820x - CSM 9562 155 5810x is NOT (field) upgradeable to CSM 9562 155 5820x ** Other straps and strap positions are depicted in section 2.4.
D304
174
CONFIGURATION RULES FOR MIXED CONFIGURATION : 32-DCC + DCC-8

DCC - 8 Check that the board 12nc of all DCC-8 boards is: 9600 021 2700x And that the board 12nc of the 32-DCC 9562 158 960xx If not, then go back T o diagram 300 and if necessary upgrade your system to 32DCC first or replace all 24-DCC or 32DCC boards by DCC-8 boards. . Configuration rules for 32-DCC and DCC-8 1st DCC in board position 101 2nd DCC in board position 201 nd 3 DCC in board position 103 1st DCC in board position 101 nd 2 DCC in board position 205 Other DCC s in board position103....203
iS3010
iS3030
iS3050 iS3070 iS3090
12 nc of ALL PM1100* Yes Shelves used for DCC is 9562 155 2220x No Upgrade PM1100* Shelves to 9562 155 2220x
1 DCC in board position 101 Other DCC in board position 103....115
st
CAUTION This configutation is based on the Following equipment: 32-DCC DCC-8: 9562 158 960xx 9600 021 2700x
BBR-V2: 9600 021 2500x (See also section 5.2) PM1100: 9562 155 2220x * If CSM shelf then: - PM1100 9562 155 2210x equals CSM 9562 155 5810x - PM1100 9562 155 2220x equals CSM 9562 155 5820x - CSM 9562 155 5810x is NOT (field) upgradeable To CSM 9562 155 5820x Strap positions on the DCC are given in diagram 306 and in chapter 2 Backbone cables < 5 meter DCC-8 firmware : F46000.204 32-DCC firmware : F43240.203
Diagram 305
Figure I-12
175
STRAP SETTINGS FOR MIXED CONFIGURATION 32-DCC and DCC-8

DCC in position
32-DCC strap X10.1** 101-102 101-102 102-103
DCC-8 Strap X6.1** 101-102 101-102 102-103
CAUTION
32-DCC
Check that the board 12 nc of all boards is: 9562 158 9600x And that the 12 nc of all DCC-8 boards is 9562 212 20000
IS3010
B oard pos. 101
Board pos. 201 Board pos. 103
32-DCC: 9562 158 960xx
DCC -8 9600 021 2700x
iS3030 Board pos. 101 IS3050 iS3070 iS3090 Board pos. 205 Other positions 101-102 101-102 102-103 101-102 101-102 102-103
BBR-V2: 9600 021 2500x See also section 5.2
PM1100: 9562 155 2220x
If not then go back To diagram 300 or upgrade the 24-DCC to 32-DCC or replace all 24-DCC boards by DCC-8 boards. 12-nc of ALL PM1100* Yes shelves used for DCC is 9562 155 2220x
Firmware 32-DCC F43240.203 or higher
Firmware DCC-8 F46000.204 or higher.
No
More than one PM with No DECT? Upgrade PM1100 shelves to 9562 155 2220x
Board pos. 101 Yes Other positions
101-102 102-103
101-102 102-103
32-DCC firmware: F43240.203 or higher
Board pos. 101 Other positions
102-103 102-103
101-102 102-103
* If CSM shelf then: - PM1100 9562 155 2210x equals CSM 9562 155 5810x - PM1100 9562 155 2220x equals CSM 9562 155 5820x -CSM 9562 155 5810x is NOT (field) upgradeable to CSM 9562 155 5820x
**Other straps and strap positions on the DCC are depicted in section 2.4
Diagram 306
Figure I-13
176

DECT CE Manual PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DECT CE Manual PDF

Uploaded by

Copyright:

Available Formats

1.6. 1.7. 1.8. 1.9. 1.10.

2.4. 2.5. 2.6. 2.7. 3. 3.1. 3.2.

3.5. 4. 5. 5.1. 5.2. 5.3. 5.4. 5.5. 6. 6.1. 6.2. 6.3.

6.4. 6.5. 6.6. 6.7. 7. Table of Contents ii 7.1.

8. 8.1. 8.2. 8.3.

9.4. 9.5. 9.6. A. B. C. D. D.1. D.2. E. F. G. G.1. G.2. H. H.1. H.2. I.

Business Mobility DECT - Customer Engineer Manual

Release date : 13/Mar/2007

8.2. "STARTING UP THE Section added. DCC BOARDS"

CHAPTER/ SECTION 5. "MIXED CONFIGURATION"

DESCRIPTION Section added

Added since Call@Net 2.8

DESCRIPTION Minor corrections/changes Added since Call@Net 2.9

DECT SYSTEM CHARACTERISTICS

TDMA (Time Division Multiple Access); TDD (Time Division Duplex).

Figure 1-2 Cordless and Fixed Telephones on The Same Exchange

10 ms time frame RFP to PP 0 F1 1 2 3 4 9 PP to RFP 10 11 12 13 14 15 16 21 22 23

0 ms F (n) = carrier Frequency (n)

Figure 1-4 DECT Time Frame and Timeslot Structure

Where F2 = carrier Frequency 2. Etc.

Beacon Signal and PP

CALL HANDLING PROCEDURES BETWEEN PP AND RFP

1.4.1. Setting up a Call

Paging and Answering a Call

RFP Behaviour in a Cluster

Overlapping radio signals. (In practice the Overlapping area is longer)

Figure 1-6 Cluster Arrangement of Radio Cells

Note: A handover is always initiated by the PP!

CALL QUALITY CONTROL

SUBSCRIPTION AND DE-SUBSCRIPTION

UAK PARI DECT System IPUI PP

SECONDARY ACCESS RIGHTS IDENTIFIER (SARI)

Copy subscription record to:

Figure 1-8 Using SARI in three DECT Systems.

Back Bone Bus

DECT Manager Local or Remote

Figure 1-9 DECT System Configuration in iS3000 series Systems

1.10.2. DECT Manager

For detailed information refer to DECT Manager User Guide.

1.10.3. BackBone Architecture

VISITING DCC RFP

HOME DCC RFP

Conversion connection between SN and RFP - PP

8(DCC) x30 (PP) = 240 PPs

Back Bone Repeater (BBR) Barrier Box

8x RFP Shelf 1 DCC 7 DCC 0 RFP RFP

8x RFP Shelf 2 DCC 7 DCC 0 RFP RFP

8x RFP Shelf 3 DCC 7 DCC 0 RFP RFP

1.11.2. Configuration Rules

1.11.3. System Expansions

1.11.4. Maximum System Configuration 24-DCC (old and new)

MAX. NUMBER OF DCCs 2 6 24 24 24

MAX. NUMBER OF RFPs 8 24 96 96 96

Table 1-1 Maximum System Configuration 24-DCC (old and new)

1.11.5. Maximum System Configuration 32-DCC

MAX. NUMBER OF DCCs 3 8 32 32 32

MAX. NUMBER OF RFPs 12 32 128 128 128

Table 1-2 Maximum System Configuration 32-DCC

1.11.6. Mixed System Configuration 32-DCC - DCC-8

2.1.1. General Requirements

See table 2.1

TWISTED PAIR CABLE TYPE 0.4 mm 0.5 mm 0.6 mm 0.8 mm

INSTALLING THE RFPs WITH DCC-RFP CABLING