KKO help system includes following chapters:
This document is an introduction and includes following items:
Basic definitions
KKO- conference card, dedicated for MD-110 Consono exchange
manufactured by Ericsson, and makes it possible to carry out two simultaneous voice
conferences for up to 60 subscribers.
kClient- Windows98/Me/2000/XP/NT application, designated for managing
of the KKO resources (conferences, announcements, settings etc.)
kServer- Windows98/Me/2000/XP/NT application, which makes link between
the KKO card (via RS232) and kClient's workstations (via LAN).
User- kClient software user logged on the KKO card via RS232 or LAN works
in on-line mode.
General remarks for KKO card
- The KKO is adapted to directly puting on in MD-110 exchange magazine
- The KKO gets only power supply from the exchange(+5V and -5V)
- The KKO is connected to the exchange by using TLU76 PCM30 interface
card; CAS signalling scheme is used.
- Phisycally the KKO is connected to the exchange by using a 120 ohm twisted pair cable.
- For cable details, see "User's manual"
- The KKO has JP1 jumper, which makes possible "cold" reset
KKO card install procedure in exchange magazine
- Find a free slot in MD-110 magazine, which has +5V and -5V power supply.
- If we want to get a cold reset (factory settings), put on the JP1 jumper.
- Place the KKO card in the founded slot.
- Press the reset button (near to red led) on the front panel.
- Wait several seconds for the autotest (all leds blinking).
- If we don't want a cold reset next time, remove the JP1 jumper and press reset again.
(the best way for it is to take off the KKO card, remove the jumper and put it on again).
You need to remember to press the reset key again!
- Wait until the red led stops to blink fast.
- Connect PCM route (routes) to TLU76 (one or two depending on conference's capacity).
Respectively yellow leds should be shining. This means full synchronization (correct status).
- Connect RS232 cable to your computer.
- Run kClient (or kServer for work via LAN) software and authorize as Administrator
or Supervisor and select kind of connection.
- Click the "Alarms" button and read alarms again. All alarms should have
"old" (green) state.
- Click the "Events" button and read all new events.
- Click the "Settings" button and check all options. If necessary correct them
and send new settings to the KKO card.
General remarks for MD110 exchange settings
On TLU76 card you must set the following parameters:
rocap:rou=1;
ROUTE CATEGORY DATA
ROU SEL TRM SERV NODG DIST DISL TRAF SIG BCAP
1 011000000000 3 0010030000 0 30 128 00151515 111100000000001100
END
rodap:rou=1;
ROUTE DATA
ROU TYPE VARC VARI VARO FILTER
1 TL30 H'00000000 H'00000009 H'00000055 NO - for tone dialing
1 TL30 H'00000000 H'00000009 H'00000054 NO - for pulse dialing
END
However, if you are going to use the password security option or you expect
conference groups to call by phone etc. you need extend timeout between entering of consecutive
digits to 90 seconds. It is important for system phones and phones with pulse dialling.
The MD-110 exchange does not transmit pulses and tones from system phones into route
after exceed of this timeout. This problem does not concern analog phones with tone
dialling - tones are always sent.
Basic informations for kClient software
- After running the kClient you need to select an access level:
"Supervisor", "Administrator" or
"Dispatcher" and enter the password; after the installation all
passwords are empty. All passwords are stored in the kClient.pw file in the [data] subdirectory.
- Now, you need to select a communication mode (RS232/LAN), the number of conferences
(for dispatcher only) and login on KKO. Selected options will be stored in the kClient.cf file
in the [data] subdirectory and will be set in the next software running.
- "Dispatcher" level is convenient for conferencing. On this level
you have to make sure that you have reserved conference(s) for yourself only.
Note, that if you take both conferences, other dispatchers will not be able to
carry out any conferences. Conferencing by phone and scheduling will be inaccessible.
- If you work as Administrator or Supervisor you have an access to both conferences always.
You may view both conferences' state but be careful - you may break a conference which is
being carried out by an other dispatcher. Higher level users get as special privileged.
- Most options are accessible for the dispatcher in the read-only mode,
higher levels make it possible to have a full access for editing and loading parameters into the KKO.
- Only one "Administrator" or "Supervisor" may be logged on the KKO simultaneously
and up to 9 "Dispatchers" (via LAN only)
- Logging on the "Supervisor" level gets nearly the same possibility as "Administrator".
The difference is that e.g. "Supervisor" can switch the "Full archive" option
(for additional error diagnostics on the manufacturer level) and directly watch sending
and receiving data frames on the console. Generally for nearly all cases the "Administrator" level
is enough.
- Each user logging opens a new session and a new log file. In the [log] subdirectory a new
log file is created with name: rrmmmdd_hhmmss_0.log, where:
rr - the 2 last digits for year,
mmm - the 3-chars contraction for name of a month,
dd - month day,
hh - login hour,
mm - login minute,
ss - login second.
This file saves all information about inserting subscribers for conferences, for alarms,
for events, all user's actions, messages etc. If you switch on the
Settings/Other/Set full log file additional in this file will contain all details.
If the log file size will be larger them 64000 bytes, a new file will be created with the same name
plus "_1.log" ending at the end of the name. Is the way for saving very long sessions in
several subfiles.
NOTE:
For cleaning your PC, check number of the log files and the size of the [log] subdirectory.
Remove all unnecessary and old files, please. If you ignore this advice, your hard disk
may be overflowing.
kClient HTML Help: INTRODUCTION
Return to beginning of this page