Views

CSTA Message Dispatcher (CMD)

The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.

Revision as of 10:04, 8 November 2012 by Alexandra.allgaier (Talk | contribs)

Jump to: navigation, search


The CSTA Message Dispatcher (CMD) multiplexes the CSTA links of multiple applications on a logical link to a HiPath platform. It is used predominantly for connecting the CSTA links on the HiPath TAPI 120 service provider, when insufficient CSTA links on a HiPath platform are free.

The CMD SW-component allows a simple connection of first-party TAPI applications to HiPath platforms, if:

  • The number of CSTA interfaces on the HiPath platform are no longer sufficient to connect all TAPI 120-based applications.
  • The customer does not have a LAN with Microsoft domain structure.
  • The communication server (CTI server) may not be integrated in the customer network/domains.


Contents

Features

The CMD message dispatcher multiplexes the CSTA links of multiple applications on a logical link to a HiPath platform. The CMD still offers the following functions:

  • CTI firewall, via station number and IP address monitoring
  • License control: Each CMD user (for example, HiPath TAPI 120 users) requires a license.
  • Support for CSTA Phase III protocol
  • Connection to a HiPath platform via Ethernet LAN

Software versions

Latest Version (effective July 2011) is:

HiPath TAPI 120 V2 R1.66.0 (released 2011-07-08)

This version supports 32-bit and 64-bit Microsoft Windows operation systems.

CMD general configuration

TAPI 120 TAPI 120 with CMD

TAPI 120

TAPI 120 with CMD

In a direct connection, the CTI client PC communicates directly with HiPath TAPI 120 TSP via the HiPath platform using Ethernet LAN and CSTA protocols. The number of CTI client PCs that can be connected with TAPI 120 is equal to the number of free CSTA links available on the HiPath platform.

In a connection via CMD, the CTI client PC communicates with TAPI 120 TSP via the PC where the CMD is installed, using Ethernet LAN and CSTA protocols. The CMD multiplexes the CSTA CTI links on individual TAPI 120 TSP systems using a separate CSTA CTI link to the HiPath platform. The PC where the CMD is installed must always be reachable in the LAN for the CTI client PC.

Operation in mixed 32 and 64-bit environment

Within a customer network different Windows operating systems can be used. The released constellations of 32 and 64-bit Windows operating systems, related to HiPath TAPI 120 V2 are shown in the tables below.

TAPI 120 TSP without CMD

Scenario PC –operating system TAPI 120 variant TAPI client application Released
1 32-bit 32-bit 32-bit yes
2 64-bit 64-bit 32-bit yes
3 64-bit 64-bit 64-bit yes


Explanations: A TAPI client PC with 64-bit operating system can operate either 32-bit or 64-bit TAPI applications (e.g. scenario 2 and 3)

TAPI 120 TSP with CMD

Scenario CMD PC operating system CMD variant TAPI 120 PC operating system TAPI 120 variant TAPI Client application Released
1 32-bit 32-bit 32-bit 32-bit 32-bit yes
2 32-bit 32-bit 64-bit 64-bit 32-bit yes
3 32-bit 32-bit 64-bit 64-bit 64-bit yes
4 64-bit 64-bit 32-bit 32-bit 32-bit yes
5 64-bit 64-bit 64-bit 64-bit 32-bit yes
6 64-bit 64-bit 64-bit 64-bit 64-bit yes

Explanations: A TAPI client PC with 64-bit operating system can operate either 32-bit or 64-bit TAPI applications (e.g. scenario 5 and 6)

Prerequisites / Requirements

Platform/Phone Requirements

Supported systems

PC Requirements

PC Hardware

In general the PC hardware equipment must meet the requirements of the Windows operating system. For each TAPI line configured 200 KB of additional RAM has to be provided.

PC Software

PC operating systems:

  • Microsoft Windows 2000 Professional SP4 (32-bit)
  • Microsoft Windows XP Professional SP3 (32-bit)
  • Microsoft Windows Vista SP2 (32 & 64-bit) except Home / Home Premium Edition
  • Microsoft Windows 7 (32 & 64-bit) except Starter / Home Premium Edition
  • Microsoft Windows 2003 Server (32-bit)
  • Microsoft Windows 2008 Server (32 & 64-bit)
  • Microsoft Windows 2008 R2 Server (64-bit)

Capacities

Max 1000 CTI Links (CSTA Links)

Functional Boundary Conditions

Due to a resource conflict within the operation system simultaneous operation of CMD 64-Bit and Microsoft Office 32 Bit is not possible. In this case Microsoft Office 64 Bit has to be used or the CMD SW has to be installed on a PC without Microsoft Office 32-Bit

Documentation

Software Delivery

The CMD software is shipped on a CD labelled "HiPath TAPI 120/ 170 V2 Service Provider" which is included in serveral order positions. It is part of the HiPath TAPI 120 SW-package. Installation can done only using the HiPath TAPI 120 setup programm.


For service purposes the software can also be downloaded from the Software Supply Server of the manufacturer. software patches for dedicated problem corrections can be retrieved from the Knowledge Base within the Partner Portal (Partner Portal, login required) of the manufacturer (login required). Access to the two methods mentioned above is only granted by the manufacturer to registered partners on a contractual base.

Licensing

Use of CMD software itself is not licensed.

Backward compatibility

Connection via V.24 / S0 interfaces should only be done for existing systems, which are already connected using these interfaces. New systems may only be connected to the HiPath platforms via Ethernet LAN using TCP/IP.

  • CMD connection via S0 was only authorized with
  • Diva Server BRI-2M Version 1.0, driver 6.3 or newer
  • Diva Server BRI-2M Version 2.0, driver 7.0 or newer

with standard drivers.

This applies only for CMD 32-bit. CMD 64 bit can only be connected via Ethernet LAN.

Migration

Migration from CMD 32-bit to CMD 64-bit

CMD 64-bit is functionally backward compatible with CMD 32-bit. In case of replacement of the 32-bit CMD the deviations within the supported scenarios of CMD 64-bit in combination with TAPI 120 TSP have to be considered.

Contribution

External Links