Freguently Asked Questions
List of questions:
Using new KKO4 ISDN card
Question: Can I use new KKO4 ISDN card in older exchanges e.g. MD110?
Answer: Yes, basicly new KKO4 ISDN card is destinated to cooperation with Aastra MX-ONE in both versions : Telephony Server and Telephony Switch. But of course it is possible to connect it with another exchanges too(the exchange must service ISDN protocol) so, in MD110 of course too.
Business Phone configuration
Question: How do I configure my Business Phone exchange for cooperation with the KKO with CAS signalling?
Answer: In document: Business Phone settings you are able to find out all details for BP configuration for connections with CAS signalling. Pay your attention that the KKO BP ISDN is prepared at the moment and it will be available for Business Phone Exchange too soon.
MD110 configuration
Question: How do I configure TLU76 to work with the KKO?
Answer: We recommend following settings for new KKOv4 ISDN card:
rocap:rou=1;
ROUTE CATEGORY DATA
ROU SEL TRM SERV NODG DIST DISL TRAF SIG BCAP
1 4110000100000010 5 2111000011 0 30 128 01151515 311110000031 111111
rodap:rou=1;
ROUTE DATA
ROU TYPE VARC VARI VARO FILTER
1 SL60 H'00000300 H'10000000 H'04010000 NO
For former KKOv2 and KKOv3 we recommend following settings:
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
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
Notice: Our friendly customer from Prague found a problem with periodic ACKSZ alarm (about one alarm per month). He solved it by modification route settings:
rocap:rou=1;
ROUTE CATEGORY DATA
ROU SEL TRM SERV NODG DIST DISL TRAF SIG BCAP
1 013000000000 3 0010030000 0 30 128 00151515 111100000000001100
As you see, parameter SEL was changed.
Thanks!
Cooperation KKO with TLU20 card
Question: The KKO co-operates correctly with TLU76 but not with TLU20 not. What shall I do?
Answer: The TLU20 has the CRC-4 disabled. Since 2.05 firmware version CRC-4 alarms are disabled. Upgrade X.14 firmware+software from our download page. In this version it is possible to change CRC-4 option too.
Cooperation KKO with TRU3 dtmf receivers card
Question: I have MD-110 DTMF receivers: TRU3 R2A and R3A. The TRU3 R3A works correctly but TRU3 R2A not. What is wrong with it?
Answer: 2.05 firmware version has raised an outgoing level of tone signals. It should be help you.
Calling simoulatously and distorsions (it concerns older KKOv2 and KKOv3 only)
Question: Sometimes not all the subscribers are called to the conference but their icons appear in the conference view window. Why?
Answer: Both MD-110 and especially Business Phone exchanges have limited number of simultaneous calls. The kClient Settings window, PCM route tab consists of the following options: Call simultaneously and Disconnect simultaneously. Try decreasing these values.
Sounds and background image in kClient software
Question: The sounds generated by the kClient bore me. Can I turn them off?
Answer: Yes. Delete or change the names of sound files (*.wav) in the sound subdirectory. You can overwrite these files, maybe then you will calm down :)
Note: Since 2.08 version you can select or disable sounds and backgroud image.
Question: Sometimes I can enter to the conference myself well whilst sometimes I hear "no resources" announcement. Tell me why?
Answer: You can enter into existed conference only! You can enter by code "1" DTMF to the existing conference or by code "4" DTMF to the conference reserved by phone.
Question: I use "quick entering into conference". Sometimes I am able to enter at once whilst sometimes I am asked for number of conference. How can I solve this problem?
Answer: Dispatcher have to select only "one conference" in login procedure. If he has two, you have to select number of conference you will work.
Administrator and Dispatcher access level
Question: What is the diference between "Administrator" and "Dispatcher" access level and what level I should choice?
Answer: Dispatcher is a owner of the conference. To tell the truth Administrator and Supervisor are able to interfere to conference too but they should not do it (they see warning window when given conference is reserved). Next, higher access level means higher possibilities. E.g. all settings, announcements recording, events reading, time setting etc. Genarally speaking if you login in order to run a conference - choice dispatcher level. If you login in order to configure the card - choice administrator level.
Phone access and passwords (it concerns older KKOv2 and KKOv3 only)
Question: Can I establish a password for each user for phone access individually?
Answer: There are only 3 passwords for all users in the KKO system at the moment. If you switch on "password requirement" option, a subscriber has to enter one of them. If the password is correct, he will enter into conference or voice menu. Probably it will be possible to set different passwords for each subscriber in the future. But in current version (X.14) it is not possible.
Permanent reservation for phone (it concerns older KKOv2 and KKOv3 only)
Question: It is required to reserve conference for phone (called by phone) by dtmf '7' code always?
Answer: If you are used to run with conference called by phone, you are able to switch on "permanent reservation for phone" option. In such case you can reserve one (only one) conference for phone all the time. It makes possible to programm hot key on the phone for example.
Conference calling and releasing by scheduler (it concerns older KKOv2 and KKOv3 only)
Question: Is it possible to call a conference by scheduler and end it after given time?
Answer: In current version (X.14) it is possible to call a conference by scheduler. It lasts as long as one subscriber is active in conference. We plan expand this service in order to be possible both call and disconnect the conference on time by scheduler running. It will make possible to lease the conference for another customers by internal timetable.
Insertion mode in predefined groups
Question: Can I call a party in "auto" mode for one group and in "simplex" mode with another group?
Answer: Beginning from X.14 version, it is possible to insert one subscriber into database twice with different modes. So, it is possible to call him with differenf mode with different groups. Note, a description in database for such subscribers have to be the same.
Completion: Beginning from X.15 version, schedule system was extended and functionally expanded. There are records for both 'mere' and leased conferences.
Announcement's broadcasting
Question: Is it possible in the KKO to make broadcasting for subscriber group with an announcement?
Answer: Yes, it is enought to record an announcement, insert it into selected group predefined or local. The rest of parties you can insert in passive mode. If it is done in predefined group, such service can be called from phone and from kClient software. If it is done in local group, you have to call it by kClient software only.
KKO ver 3 and kServer software
Question: If I have KKO card in hardware 3 version need I kServer software?
Answer: Not, kServer software is required if you work with the KKOv2 hardware version. In case of KKOv3 you are able plug in it into your ethernet (switch or hub) device in order to make it available for all users in your subnet.
Autodetection of IP address
Question: Autodetection of IP address works wrongly. What can I do?
Answer: Generally speaking we suggest switch off your firewall on autodetection procedure. After detecting, you can establish constant IP address in your subnet range and switch on a firewall. It it is not possible, you have to make available port 30718 for UDP frames and make available to send UDP broadcasting frames. Also remember, to switch on only one KKO card in detection moment.
Port number for the Xport
Question: Which port is used for KKO-kClient communication via XPORT device?
Answer: Until software version X.15 port number 1962 is used by default. Both in kClient and kServer or Xport device. Beginning on X.16 version port number is editable parameter. In main window of kClient software, there is edit window in order to write required number. Also, in autodetection IP address procedure (Settings->Communication->Autodetection) from X.16 there is run detection of Xport's port number automatically. So, yau are able to check what number is set in the Xport. Additionally, if you work with the KKOv2 and network via kServer software, beginning from kServer 2.16 version, new possibility was added. You are able to select via which port both sofwares: kClient and kServer will work.
Factory defaults for the Xport
Question: The communication between KKOv3 and PC doesn't work. Can I reset Xport device? How?
Answer: From X.16 firmware version new possibility was added. It is cold reset (factory defaults) for the Xport. It is executed by closing both jumpers: JP1 and JP2 on KKO and resetting the card. All details for this procedure you can find in document (User's manual for KKO) and in context help in kClient software (bookmark: The KKOv3 with Ethernet - first start, troubleshooting).
We are waiting for next questions...