Frequently asked questions about TeamCall CSTAServer
Last modified $Date: 2000/03/29 13:28:38 $
The TeamCall CSTAServer is a middleware for Computer Telephony Integration (CTI).
There are two socket/stream-based APIs:
It is inspired by ECMA's CSTA standard.
It is compliant to Microsoft's (R) TAPI (Version <=2.x)
Check www.ilink.de
Each message is terminated with a CR
LF
(``\r\n'') at the end.
When an external incoming call (i.e. a call outside the PBX) is signaled,
the dialing number of the calling party starts with a ``+'' (unless you
specified a prefixPlan
in your configuration file) for the following events:
In these events, the CSTA protocol (Phase I and II) identifies the calling party as exactly one of these types:
In order to identify external and internal devices within the events signaled via STLI/TAPI, we prepended a ``+'' to the calling device number if it's tyoe is either implicitPublic or explicitPublic.
Which type is used for signalisation depends on the PBX/Switch. Usually, external devices are of the type implicitPublic.
Please refer to ECMA-218 for more information.
The connection list, which is transmitted via the transfer, does not
contain any information about the origin of the included devices. They are
simply transmitted as DeviceID
without further specification. There is no distinction of types as for
example in the Delivered event (see also Why are external calls sometimes signaled with a leading "+" ?).
It may be configurable within your PBX if the dialing numbers are generally signalled with the whole information, i.e. country code, area code and phone number.
If the external incoming call would have been delivered (or queued) to an internal and monitored device, the Server could have had the knowledge about the calling device if it is internal or external. But if the external call is transferred from a non-monitored (or even external) device or first delivered to a non-monitored device, this knowledge does not exist. Thus we decided not to gather these informations as there are too much cases where the information would not have been transmitted.
This section treats questions concerning specific Switches,PBXs
This PBX needs either the LinkISDN or the LinkV24.
Contact your Siemens dealer and ask him to check your H150. The signalling of the trunkIds (usually 7801,7802, etc.) has to be activated in the H150-Configuration.
Check your Configuration file. Usually, both LinkISDN/V24 and CSTAServer use the same file. If not, compare the entries
cstaLinkAddress cstaLinkPort
Check the Configuration entries for the LinkISDN/V24 (LinkISDN, LinkV24).
This PBX needs the ISDNRouter.
ISDN D-channel Router for Siemens A6,Telekom Octopus.
This version is only for Win32-plattforms.
ISDN B-channel Router for Hicom 150.
This version is only for Win32-plattforms.
Check your PBX-Configuration if the ISDN-Link is enabled. If not, contact your PBX-Dealer.
Check if your ISDN board supports User-to-User ISDN protocol.
Check if you entered the correct directory number for the CSTA Connection
in your Configuration file (cstaLinkNumber
). For Hicom150, this is usually 891.
Check if you entered the correct serial device for the CSTA Connection in
your Configuration file (serialDevice
).
Check if the serial device for the CSTA Connection in your Configuration
file (serialDevice
) is available for reading/writing, i.e. if no other process blocks it.
Check if the baudRate
in your Configuration file corresponds to the settings in the PBX. For
Hicom150, the default setting usually is 9600.
The main purpose is debugging and tracing. If you have a problem with your server, turn on the debugging (please refer to your manual) and send us the log files.
The format may change from version to version without notice. As the logfiles are for internal use only, the format won't be described further. If you are really interested, please contact us, we can arrange a training for you.
Feel free to use it but read What is the format of the logfiles ? before.