This document describes the installation, testing and troubleshooting of TeamCall Server for UNIX and Windows NT platforms using a PBX with an Ethernet interface and is organized as follows:
In order to install TeamCall Server the following minimum hardware and software are required:
TeamCall Server currently supports the following PBX types with an installed CSTA interface:
Installed Ethernet interface required.
Installed Ethernet interface required.
ISDN connection: installation of the ilink TeamCall LinkISDN software is required prior to installing the TeamCall Server software. A computer running Windows with an installed ISDN interface card from Eicon Diehl with "User-to-User signaling" is also necessary.
Link via serial connection: installation of the ilink TeamCall LinkV24 software is required prior to installing the TeamCall Server software. After the ilink TeamCall LinkV24 package has been installed, install the TeamCall Server package as outlined in section 2 of this guide. Edit the configuration file "Default.conf" according to this document and "GettingStartedV24.html". Start TeamCall LinkV24 as described in "GettingStartedV24.html". Next, start TeamCall Server following the steps in this document.
The ACLC module plus Siemens CallBridge for WorkGroups software and a computer running Windows NT are required.
ISDN connection: installation of the ilink TeamCall LinkISDN software is required prior to installing the TeamCall Server software. In addition, a computer running Windows with an installed ISDN interface card from Eicon Diehl with "User-to-User signaling" is required.
To unpack and install TeamCall Server under UNIX, follow these steps:
/tmp
.# gtar -xvpzf tcserver.tgz
A directory "teamcall" will be created that contains the following two files and single directory:
- CSTAServer (The TeamCall Server binary.)
- Default.conf (The main configuration file.)
- S99CSTAServer (Script used by init.)
- tcdoc (Directory containing the TeamCall Server documentation as HTML files.)
# cd teamcall
/usr/local/bin
or /opt/bin
using the "cp" command:# cp -p CSTAServer /usr/local/bin/
/usr/local/etc/
:# cp -p Default.conf /usr/local/etc/
/usr/local/doc
using the "cp" command:# cp -pR tcdoc /usr/local/doc/
To install TeamCall Server on a computer running Windows NT, follow these steps: Before you begin, make sure you have the IP-address and the TCP/IP port number of the PBX handy.
c:\temp\teamcall
using e.g. WinZip.The following directories and files will be created in the installation path:
- CSTAServer.exe (The TeamCall Server binary.)
- Default.conf (The main configuration file.)
- doc (Directory containing the TeamCall Server documantation as HTML files.)
- logs (Directory containing the log files.)
Under UNIX, the TeamCall Server configuration file must be modified to match your local network requirements. Under Windows NT this is done during the setup process. Before editing the files, make sure you have the IP-address and the TCP/IP port number of the PBX handy.
To edit the configuraton file, follow these steps:
After you have installed and configured TeamCall Server you need to check that it works properly. To do so, you have to run TeamCall Server and perform a quick test.
If you are logged in after restarting your computer as suggested during installation, TeamCall Server should run. If you have not already restarted your computer, please do so now.
Under UNIX, you can either start the TeamCall Server binary manually when you need it, or you can configure it to start automatically while booting.
Follow these steps, to start TeamCall Server manually using the configuration file "Default.conf":
# cd /usr/local/bin
# CSTAServer -c /usr/local/etc/Default.conf
If the startup was successful, the following message should appear:
You can also install TeamCall Server to start while your OS boots.
Please note that this option is for experts only,
since we only provide an example init script that must be configured
and installed manually. It also requires knowledge of the specific boot
process of the type of UNIX you are using. This will only work
on Linux or Solaris systems. (On BSD-style systems, TeamCall
Server can be started automatically by adding a line to an rc-script like /etc/rc.local, e.g.
/usr/local/bin/CSTAServer &
)
# cd /tmp/teamcall
# cp -p S99CSTAServer /etc/rc.d/init.d
# /etc/rc.d/init.d S99CSTAServer start
# /etc/rc.d/init.d S99CSTAServer stop
Using a few simple STLI commands you can check if TeamCall Server works properly. Using STLI, you will place a call from one telephone to a second telephone, answer the call and hang up.
You will need to know the IP-address of the computer where TeamCall Server runs and the TCP/IP port number of the STLI interface. You can check the configured TCP/IP port number of the STLI interface next to the entry "stliPort" within the configuration file "Default.conf". The default TCP/IP port number is 8000. Also, you will need to have access to two telephones connected to the PBX. Windows NT users should start the "Command Prompt" application.
Use the following steps to connect to the STLI interface using the telnet command, place a call from one telephone to a second, answer the call and hang up:
# telnet 192.168.0.1 8000
The following message should appear:
MonitorStart 100
The following message should appear:
MonitorStart 101
The following message should appear:
MakeCall 100 101
The following message should appear and telephone 101 should ring.
Please note that the numbers shown in this example may differ from the messages you receive.
When using a PBX from Alcatel, please note that this step is only necessary, if the auto-answer mode is disabled for this telephone. When using a PBX from Siemens, this step can be omitted.
AnswerCall 100
The following message should appear and telephone 100 should ring:
AnswerCall 101
The following message should appear:
Now, telephone 100 and telephone 101 are connected.
ClearConnection 100
The connection should terminate and the following message should appear:
BYE
The following message should appear:
If the installation and start-up of TeamCall Server was successful, you should be able to connect to TeamCall Server's Supervisor interface, STLI interface and NetTSPI interface.
To check the availability of the above mentioned interfaces, follow these steps:
If one of the entries STLI added.
or TAPI added.
is
missing, the connection to the STLI and/or the NetTSPI interface was unsuccessful.
A networking problem may have occurred.
Check the IP-address of the
TeamCall Server and the TCP/IP port numbers of the STLI and NetTSPI interfaces
within the "Default.conf" configuration file.
You should also check your networking configuration.
TeamCall Server logs all of its activities in four different log files when activated and configured within the "Default.conf" configuration file. Only turn on the logging mechanism to debug an error and remember to turn this feature off when no longer needed.
To enable the logging mechanism, follow these steps:
On a computer running Windows, the file "Default.conf" is located in the installation path.
The log files have the following names:
Error log file: Error[<5-digit number>].log
Device log file: Devices[<5-digit number>].log
Calls log file: Calls[<5-digit number>].log
CSTA log file: CSTA[<5-digit number>].log
The Error log file contains everything to be written to stdout
.
The logging mechanism does not need to be turned on as described above
for the error logging feature.
The Error log file is created automatically when an error occurs.
The Device log file contains information about the status of the monitored telephones (devices).
The Calls log file contains information about the calls and the telephones that are connected to these calls and their status.
The CSTA log file contains the plain ASN.1 messages that are exchanged between the CSTA Server and the PBX.
The number of messages written to the log files depend on the debug level set within the "Default.conf" configuration file. To learn more about debug levels, please see the main documentation.
You will find additional and more detailed documentation within the "tcdoc" directory. To read it, simply launch the web browser of your choice and open the file "index.html".
© 2000
ilink Kommunikationssysteme GmbH
Große Hamburger Straße 32
D-10115 Berlin, Germany
Phone: +49 30 28526-0
Fax: +49 30 28526-199
info@ilink.de
www.ilink.de