1. HIGH CAPACITY PBX SYSTEM - TECHNICAL INTRODUCTION -

2. PURPOSE
Purpose of this presentation is to give a technical briefing about DS200L system.

3. TOPICS IN THIS PRESENTATION
MAIN SYSTEM PARTS
* TW200 TOWER BLOCK
* PCU200 BLOCK
* DCC BLOCK
STEPS FOR INSTALLING THE SYSTEM
PUTTING SYSTEM INTO SERVICE

4. * 2 TW200 towers exist in the figure.
SYSTEM DEFINITION
DS200L system consists of :
TW200 (Tower200) Block
PCU200 (PC Unit) Block,
DCC Block,
Network switch,
Power Inverter
External Power Block
DS200L system in a 6-rack and 19” cabinet
* 2 TW200 towers exist in the figure.

5. COMPARING WITH DS200
The differences of the DS200L system from the DS200
system are briefly as follows :
DS200L has a high capacity up to ports,
The PCU200 Block fulfills the tasks of the CPU200 card,
DS200L has the DCC Block for high capacity switching,
The units communicate over LAN with TCP/IP protocol,
It is necessary to install 4E1 cards on UTIL200 cards,

6. COMPARING WITH DS200
It is possible to utilize the CC cards in main racks, instead of the CPU200 card ,
External power block is utilized instead of the SPS200 power supply at high capacities,
DS200L utilizes Power Inverter and Network Switch.

7. PHYSICAL CONNECTIONS

8. PHYSICAL CONNECTIONS
The connections between EX200 Utility 4E1 Card and DCC block are provided via metal shielded one- to-one CAT5 STP cable
The connection between CC Card and network switch is provided via ethernet cable
The connection between maintenance computer and network switch is provided via ethernet cable

9. PHYSICAL CONNECTIONS
The connections between PCU200& redundant PCU2000 and network switch are provided via ethernet cable
The connection between DCC block and network switch is provided via ethernet cable

10. PHYSICAL CONNECTIONS
If SPS200 is not used, DCC, power inverters and SPS248 units are connected to the external power block.
Maintenance computer, CC cards in TW200 towers, external power block and PCU200 units are connected to the network switch.
PCU200 and network switch, on the other hand, are connected to the power inverters and receive the necessary voltage for their operation from the power inverters.

11. TW200 TOWER STRUCTURE
A TW200 tower consists of maximum 3 racks; one main rack and two auxiliary racks ( In fact, only a single main rack can also be named as a tower ).
The rack structure of TW200 is same as a DS200 rack.
The UTIL200 and other cards that are used in DS200 racks are also used in TW200 racks.
Since the PCU Block functions as the main processor in the DS200L system, no CPU200 card is available. The CC card is employed instead of the CPU200 card.

12. CC MODULE
NOTE: No redundant CC is used in the TW200 towers. Since the PCU200 block fulfills the tasks of CPU200 card, redundancy of the PCU200 block is available in the DS200L exchange.

13. CC MODULE CC Module has :
● 1 Ethernet port
● 32 MByte Flash Memory
● 256 MByte RAM
● Linux operating system
The main function of the CC card is : to provide
communication between the PCU200 block and the racks.

14. UTILITY 4E1 CARD

15. UTILITY 4E1 CARD

16. UTILITY 4E1 CARD
The Utility 4E1 card is mounted on to the UTIL200 card.
4 E1 ports are available on the card.
Each E1 port has 31 speech channels.

17. UTILITY 4E1 CARD
Via this card, at most 12*31 = 372 speech channels are supplied for one tower.
The connections within a tower do not require a speech channel for 4E1 card, instead directly connected by UTIL200 card.
Since there are 3 racks in a tower (TW200), at least 1, at most 12 E1 connections can be made per tower.

18. UTILITY 4E1 CARD
The E1 ports that are on the Utility 4E1 cards are connected directly to the DCC 8E1 Interface cards that are in the DCC Block.
Speech channels between the TW200 towers and the DCC block are connected through the E1 channels of the towers.

19. PCU200 BLOCK

20. INFORMATION
PCU200 ( PC Unit ) is a processor that has been based on a 19” PC which controls all functions of the exchange.
The PC that functions as the PCU200 is 19” in width, 2U in height and 80 cm in depth. It is placed in a 19” cabinet.
The master software of the exchange runs under the Linux Suse on the PCU200 computer .

21. INFORMATION The minimum requirements of a DS200L PCU200 block :
Pentium IV 2.4 GHz. processor
60 GB hard disk
1 GB RAM

22. PCU200
The master software runs under LINUX in real time and performs its functions by means of a file system.
Using this file system, the entire exchange parameters, statistical data, call records, alarm information, etc. are stored in separate files on hard disk.

23. COMMUNICATION
PCU200 communicates with the other units within the exchange over the TCP/IP protocol.
PCU200 initiates intra-exchange communication.
PCU200 controls all the communications between all the exchange units .
The communication information, namely IP addresses and TPC ports of the DCC and TW200 units are entered in a table in the PCU200.

24. COMMUNICATION
Thanks to that structure, both of the blocks that carry out TDM and IP switching can be controlled by the same center.
Besides, PCU200, which provides communication through the Ethernet structure, has completely been isolated from exterior factors.
That fact is extremely essential considering that the system security is thus increased.

25. REDUNDANCY
It is possible to back up the PCU200 block upon wish, with another PC that is a one-to-one copy of it.
The redundant and functional PCU200 blocks are in connection with each-other through Ethernet ports.
In case of any malfunction that occurs in the functional PCU200 block, the redundant PCU200 directly becomes functional.

26. STRUCTURE OF PCU200
User computers that are on the same LAN provide access to PCU200. By this way, while it is possible to access all information on PCU200, raw data within the exchange is protected.
As a result of all those protection measures, the exchange security has been maximized.

27. SOFTWARE STRUCTURE
A special partition has been created on the hard disk of the PCU200 computer. There is a directory, namely karel, under that partition.
Parts of software and the files created by the exchange during run-time are placed in a subfolder which is under that directory and which is compatible with the exchange software.
For example: karel/ bin/ z_new_23.rpm

28. SOFTWARE STRUCTURE

29. SOFTWARE STRUCTURE
The directory structure given above is supposed to be created by the user on the maintenance PC that is utilized for programming purposes.
Since the same directory structure exists on the Linux PC (PCU200), that operation is also necessary to check and copy the specified files.

30. SOFTWARE STRUCTURE
► There are 3 directories under the directory karel, these are sbin, bin and home.
There are 6 files in the directory sbin.
1) dsinit: This file specifies the master software that is to run in the system.
2) check: This file allows the read-write-execute permissions of the files to be set.
3) dslog: This file allows the system logs to be displayed.

31. SOFTWARE STRUCTURE 4) stop: This file allows the system to be stopped.
5) start: This file allows the system to be started up.
6) arpsave: This file is necessary for IP and MAC
addresses matching of CC cards.

32. DIRECTORY BIN
● The master software of the exchange exists in the directory bin. ● The software runs at the level defined as “Run level 3” of the Linux operating system. ● There is a main task program at the Linux operating level, which controls the operations of the entire exchange software. This program controls the operations of other sub-tasks and in case of a malfunction, it automatically ensures that the malfunction is eliminated. That main program is the master software of the exchange. The sub-task files with the extensions "so" and "rt" exist in this master software

33. DIRECTORY HOME
There are 5 directories in the directory home. These are : log, cm, conf, data and alarm directories.
1) log: Log files for analyzing ( for maintenance) the entire
operations in the system, which are created during the
operation of the exchange are kept in this directory.
ds_gg_aa_yyyy.log is a file which saves the log information
according to date. For example, the system is operating for 2
days and the date of first started of the exchange is
, then the files named ds_2009_08_22.log and
ds_2009_08_23.log are automatically formed under the log
directory. Thanks to this, errors can be analyzed day by day.

34. DIRECTORY HOME
nks_err.log and nks.log files are the logs belonging to NetConsole Server. Besides these, there are 2 files named sip_spc_curr.log, and sip_spc_prev.log related to SIP ProxyServer under the log directory.
sip_spc_curr.log file saves the current ( active )operations of SIP Proxy Server. sip_spc_prev.log file saves the previous operations of SIP Proxy Server.
*** %40 of the karel directory can be used for logs.
NOTE : NetConsole Server is embedded and automatically
runs on the PCU200 computer.

35. DIRECTORY HOME
2) cm: The files cm00.bin, cm01.bin, cm15.bin,
which contains the call record information of the exchange
are kept in this directory.
Size of each file is 16 MB
call records in total are stored in the exchange memory.

36. DIRECTORY HOME 3) conf: There are 4 files in this directory ;
pbxcomm.conf, dsinit.conf, snmp.conf and sip_spc.conf .
*** Two text files pbxcomm.conf and dsinit.conf are
supposed to be created manually before installation of
the exchange starts.

37. PBXCOMM.CONF
pbxcomm.conf is the file that specifies the IP addresses, orders and TCP Port numbers of TW200 towers and DCC block.
Explanations of pbxcomm.conf are written inside the file.
In this file, there is a template which shows how to enter the
data into this file.

38. PBXCOMM.CONF
The user will make the definitions in the part which is under the template of the file.
The command that is to be used in the text file is “ connect ”. Some of the parameters, which are to be used afterwards are given in the following pages.

39. PBXCOMM.CONF

40. PBXCOMM.CONF EXAMPLE connect -t cc -a 192.168.2.1
NOTE: “vr” and “ss7” definitions in the template are used only for Public Switch Systems. These definitions are not valid for PBX systems.
EXAMPLE connect -t cc -a
connect -t cc -a
connect -t cc -a
connect -t dcc -a
3 of TW200 towers and 1 of DCC block have been
defined in the file pbxcomm.conf, which has been
stated above as an example.

41. PBXCOMM.CONF
The IP addresses and port numbers to be entered in that file completely depend on the requirements of the installation location. On the other hand, since the DS200L IP system is completely isolated from external networks, desired IP numbers can be used in the table.
Order of the defined TW200 towers is from the top to the bottom, i.e., the tower at the top with the IP address is the first tower, the tower in the second line is the second tower and so on. The line defining a new tower must precede the line in which the DCC block is defined.

42. DSINIT.CONF
The file dsinit.conf specifies the master software to run on the system .
The main exchange software existing in the dsinit.conf file can be automatically set by the command check z_xxx which is entered from the SSH Secure Shell Program. So , there is no need for the user to enter this information into the dsinit.conf file manually. But the version information needs to be checked in the dsinit.conf file.
And if redundant PCU200 is running in the system,
“buddy= x2” definition should be made into the dsinit.conf file
manually.

43. DSINIT.CONF
● buddy= X2 [ This definition is necessary for operation of X2
computer (redundant PCU200 ) ]
● VERSION = z_new_68 [ line specifies the master software to run on
the system].

44. SNMP.CONF
This file is formed for SNMP ( Simple Network Management Protocol ) applications.
Normally, there is no need to make a definition into this file. In this case SNMP connection can be provided from any IP address.
If preferred, IP definiton can be made by entering an IP address after “=” into the “TrapTargets” field. For this case, SNMP connection can be done only from the device which has this IP address.
If more than one IP address will be entered, there should be comma between the IP addresses.

45. SNMP.CONF For example; TrapTargets= 192.168.179.122 ,192.168.179.101
When this definition is entered, this means SNMP
connection can be made only from the devices which has
the IP address and

46. SNMP.CONF

47. SIP_SPC.CONF DS200L system also has an IP extension support. IP
extensions can be defined on the system. There is an
embedded SIP Proxy Server in the DS200L system’s
master software. The configuration file for this proxy is
sip_spc.conf .
At the beginning, there is no need to make a definition in
this file. In sip_spc.conf file , there is a template (explanation
part ). If needed, the definitions will be made below the
template part.

48. SIP_SPC.CONF

49. SIP_SPC.CONF
IP address definition as NAT IP address in the part under the template above is done for the internet connection.

50. SOFTWARE STRUCTURE
4) Data: The files pertaining to the entire programmed parameters in the exchange are stored in this directory.

51. SOFTWARE STRUCTURE
5) Alarm: The files alarm00.bin and alarm01.bin, which contain alarm information of the exchange are stored in this directory.

52. DIGITAL CROSS CONNECT A DCC block consists of the units below:
DCC Chassis
DCC Backplane
DCC Utility Card
DCC 8E1 Interface
Card
DCC Power In Card

53. DCC BLOCK
The DCC Block is the switching matrix that fulfills the main switching function for the exchange.
DCC Block has a structure that includes the main switching controller card ( DCC Utility), 14 8E1 Interface card slots and a power regulation card (DCC Power In).
Due to its standard 19” structure, it is placed in the same 19” cabinet with the main processor PCU200.

54. DCC CHASSIS
The DCC chassis is a 19”, 6U-high box, which has been formed of an aluminum cage structure and which mechanically places the entire cards in contact.
It has slots for 17 cards inside, which is composed of plastic rails that are at the top and bottom of the slot.

55. DCC BACKPLANE
Communication of the entire electronic units in the DCC block is made over the DCC backplane.
The DCC backplane transfers all signals used by DCC cards to pertinent card slots and it distributes the power coming from the DCC Power In card to all card slots.

56. DCC BACKPLANE
The DCC backplane is the card that forms the electronic skeleton of the DCC Block.
There are 2 special slots for the DCC Utility card and one special slot for the DCC Power In card on the backplane, as well as 14 slots for DCC 8E1 Interface cards.

57. DCC POWER IN CARD
The DCC Power In card regulates the -48 VDC feed voltage it receives from the power block of the DS200L system and transfers it to the backplane.
The Power Control Card controls the -48 VDC voltage fed to the DCC unit and minimizes surges in voltage with fuses and regulators on it.

58. DCC POWER IN CARD
The card also generates the reference signal for the backplane, which is 1.5 VDC.
Each DCC unit has minimum one Power In card. The card definitely must not be removed from its slot while the system is ON.

59. DCC POWER IN CARD
The DCC Power In card is plugged in the rightmost slot. If redundant of this card is available, redundant card should be installed into the leftside ( slot number 0 ) of the DCC Power In card. Normally, this slot is used for DCC 8E1 Interface cards.
When redundant DCC Power In card is installed, number of DCC 8E1 Interface cards to be installed is decreased by 1 and is equal to 13.
When redundant DCC Power In card is installed into the system, system will go on operating without any problem in case any problem occurs at master DCC Power In Card.

60. DCC POWER IN CARD ● The LEDs signifying +3V3 and
+1V5 statuses are supposed to
be continuously ON state during
the normal operation of the
system, whereas all the other
LEDs are supposed to be OFF. ● In case the LED statuses are
different from what have been
specified here, the system should
be checked.

61. DCC UTIL CARD
The DCC Utility card is the main unit, which controls the entire DCC functions and which includes the switching matrix.
The DCC Utility card consists of the Utility motherboard and the PPC CPU card, which has been attached to the motherboard with two connectors that are on the motherboard.
The main processor of the DCC Utility card is the Power PC CPU card.

62. DCC UTIL CARD
A single UTIL card suffices for DCC operation. However, a redundant one may be made available when needed, i.e., two UTIL cards can be installed in the DCC block.
Both cards are identical in hardware. In case of a malfunction in the functional DCC Utility card, the DCC automatically shifts to the redundant UTIL card. During that transition, no system pause or data loss occurs.

63. DCC UTIL CARD
The DCC Utility card and the redundant DCC Utility card, if available, are supposed to be installed in the slots in the middle, which are labeled CP1 and CP2 on the DCC backplane. Master DCC Utility card is installed into the CP1 slot and redundant DCC Utility card is installed into the CP2 slot.
An RS232 input, a 100 Mbit Ethernet input, a 10 MB Ethernet input and some LEDs are available on the DCC Utility card. Functions of those LEDs will be explained later in the document.

64. DCC UTIL CARD

65. DCC UTIL CARD
The LEDs on the DCC Utility card and their functions have
been explained below:
POWER: This LED is supposed to be continuously ON. If
it flashes, then the DCC block must be turned OFF and
then back ON after seconds.
DSP-A, DSP-B, DSP-C, DSP-D: These LEDs signify that
the DSP unit is operational. They are supposed to be
blinking.

66. DCC UTIL CARD 10 RX, 10 TX/ 100RX, 100TX: These are supposed to be
flashing during data transmission or reception over local
area network (LAN).
CPU: It is supposed to blink periodically.
M/S (Master/Slave): This LED is supposed to be continuously
ON, if the master DCC Utility card is functional in the DCC
Block.

67. DCC UTIL CARD LOCK: This LED is supposed to be blinking periodically,
if DCC is using external clock. If it does not blink
periodically, then that signifies there is a problem with the
external clock signal.
HOLD: This LED is supposed to be continuously ON, if
DCC is using its own clock signal.
10 BASE-T / 100 BASE-T: If the upper green LED is ON
after an ethernet cable has been inserted, then that
signifies the connection has been established. On the other
hand, the red LED signifies a problem with the cable or the
connection.

68. DCC 8E1 CARD

69. DCC 8E1 CARD
The DCC 8E1 Interface card has 8 E1 ports as its name already indicates and it can be installed in the 14 general purpose slots within DCC.
8E1 cards have been numbered starting with the rightmost slot in the DCC Block. The rightmost slot ( leftside slot of the DCC Power In Card ) has been reserved for the 8E1 card number 0, and the leftmost one for the 8E1 card number 13 in the DCC block.

70. DCC 8E1 CARD
The DCC 8E1 Interface card receives the 48 VDC feed voltage from the backplane and generates the 3.3 VDC signal it needs. By this way, the power signals within the DCC block have been isolated from each other, so that defective units are prevented from adversely affecting other units.

71. DCC 8E1 CARD
The DCC 8E1 Interface card has embedded self-test feature.
The DCC 8E1 Interface card is capable of applying BERT to the E1 channels within DCC. By this way, any problem that might occur in the future is easily detected in advance and necessary precautions are taken before system performance deteriorates.

72. DCC 8E1 CARD
The DCC E1 lines constitute the main frame for voice transmission system of the exchange. Those lines can be used to provide transmission paths for speech channels between DCC and TW200 towers.
The E1 lines extending to TW200 towers are connected to the Utility 4E1 cards that are in the towers.

73. DCC 8E1 CARD
Each E1 line provides 31 speech channels to a tower. It is sufficient to increase number of E1 connections to towers in order to increase number of speech channels.
In case several E1 channels are connected to the TW200 4E1 card, distribution of speech channels to those E1 lines is arranged by the system automatically.

74. SWITCHING ON DCC
Intra-rack and inter-rack switching in the DS200L system is conducted over the UTIL200 card, whereas inter-tower switching ( switching between towers ) are conducted over DCC.
The DCC block has a 4096 x 4096 switching matrix. By this way, 8192 channels in the DS200L exchange can be simultaneously used for conversations.
The switching matrix on the DCC block is distributed to the TW200 towers over E1 lines in DCC. Thanks to the isolated E1 structure, trouble-free connections can be established even with the distant TW200 towers.

75. SWITCHING ON DCC
Due to its structure, DCC is continuously in communication with both the TW200 towers and the PCU block. It communicates with the towers over E1 connection, whereas it communicates with the PCU Block over TCP/IP.
Number of 8E1 cards to be installed depends on the capacity of the exchange to be used.
At most 14 DCC 8E1 Interface cards can be installed in the DCC block. By this way, the capacity may vary between 8 and 112 E1 lines.

76. SWITCHING ON DCC
If the capacity provided by only a single DCC is not enough, then it may be expanded by including a second DCC in the system, so that both the switching capacity is increased from 4096 x 4096 to 8192 x 8192, and number of E1 lines is increased up to 224.
1 to 12 E1 lines can be connected to each tower, depending on capacity requirements (Each E1 has 31 channels).
*** By this way, it is possible to provide 31 to 372 speech
channels for 672 extensions.

77. NETWORK SWITCH
NOTE: IP addresses of the devices specified below must be so adjusted that they are in the same local area network.

78. NETWORK SWITCH
Function of the network switch is to provide the TCP/IP switching of the system blocks and to coordinate the IP communication.
Communication and information exchange in the DS200L systems are carried over the IP network.
The network switch is located in the 19” cabinet.
Using a programmable network switch (which has port mirroring feature) will be useful for managing the network.

79. NETWORK SWITCH
The Ethernet cables that are supposed to be connected to
the switch are as follows:
The Ethernet cables coming from the CC cards in TW200 towers ,
The Ethernet cables coming from the PCU200 Block and the redundant PCU200 Block ,
The Ethernet cable of the maintenance computer,
The Ethernet cable coming from the DCC Block ,
The Ethernet cable coming from the Power Supply ( if exists )

80. EXTERNAL POWER BLOCK
In case of large capacity DS200L systems require high capacity battery groups, External power supplies can be used instead of SPS200 power supplies.
For proper power regime, in addition to external power supplies the capacities of the batteries must be selected appropriately for the system capacity.
External Power Block feeds DCC block, power inverter and the SPS248 power supplies which are at the TW200 towers by -48V. Cabling is to be made from External power supply to each tower and to other units.

81. Power Inverter and redundant one for DS200L system

82. POWER INVERTER
For small capacity systems, in case system is fed by SPS200 power supplies, PCU Block and network switch can get the required 220V AC voltage from the electricity network. In this case, there will be no need for power inverter.
For large capacity systems, system gets -48V voltage from the External power supply , -48V coming from External power block is converted to 220V AC and transmitted to PCU200 block, redundant PCU200 block and network switch.

83. POWER INVERTER
Power Inverters are located in the 19” cabinet. Optionally, redundant power inverter can be installed to the system.
At the systems which has redundant power inverter, in case any problem with any of the power inverter occurs, the redundant power inverter is put into operation. Thus, PCU200 blocks and network switch get the 220V AC input from the redundant one and keep operating without any problem.

84. When installing the DS200L system, after the physical
INSTALLATION
When installing the DS200L system, after the physical
connections have been made, the instructions below should be followed in the specified order.

85. INSTALLATION Power ON all the system. And turn ON the PCU200 and
maintenance computer.
2) Check the IP addresses of the CC cards , DCC Utility
Card, PCU200 and maintenance computer.
3) Run WinSCP program at maintenance computer. Check
the “karel” directory and the directories in it. If there is a data
missing, copy it from the maintenance computer.

86. INSTALLATION
4) At WinSCP program, write the IP addresses of the towers and
DCC block into the “pbxcomm.conf” file . And also master
software version is checked from the “dsinit.conf” file. And if
redundant PCU200 block is available in the system, write the
“buddy=x2” definition into this file.
5) At SSH Secure Shell program at the karel/bin command
prompt, enter “rpm –ivh –force zr_xxx.rpm” command. By this
command zipped zr_xxx.rpm software is extracted. After this,
enter the “check z_xxx” command. By this command, read-write
execute (r-w-x) authorities of all the files under karel directory
are set. Furthermore by this command, master software version
of the system is automatically written into the “dsinit.conf” file.

87. STARTING THE SYSTEM
Follow the instructions below to commission the system
after installation has been completed:
Power ON all the system. And turn ON PCU200 and
maintenance computer.
2. Check whether the towers and the DCC block are
reachable from the PCU200 block, by entering the
command “ping” in the program SSH Secure Shell.
Example:
Type “ping ” in the MSDOS command line and press
the ENTER key. If a reply comes from the IP address ,
then that indicates the address is reachable.

88. STARTING THE SYSTEM
3. Start the system by the command “start” through the program SSH
Secure Shell. Extensions begin receiving the dial tone after that
command.
4. Select “NetConsole Server” as the connection type in the program
IDEA and write the IP address of the PCU200 block, so that connection
is established with the system. After connecting to the system, check the
configuration.
NOTE: The NetConsole Server program runs automatically when the
DS200L system starts.

89. STARTING THE SYSTEM
5. Select “ DCC Connection ” as the connection type in the
program IDEA and write the IP address of the DCC block
( DCC Utility card ), so that connection is established
with the DCC. At IDEA program, check statuses of cards in
the DCC block through the configuration window.
6. After the system has been put into service, check through
the LEDs synchronization statuses of system units.

90. STARTING THE SYSTEM
7. Check whether it is possible to make intra-rack, inter- rack and inter-tower calls.
8. Check whether other computer interface programs such as IDEA, Net Console and Net CM can run or not.

91. THANK YOU VERY MUCH...