Specifications

ManualsBrandsSiemens ManualsConsumer electronicsHiPath 3000 V3.0 or later Gigaset M1 Professional

171

172

173

174

175

176

177

178

179

180

3000sb3.fm

P31003-H3560-X100-1-7618, 09/05

HiPath 3000/5000 V6.0, System Description

3-5

For internal use only

HiPath 5000 System Overview

Software Structure

The following table shows the most important features of the Feature Server.

Presence Manager

This is a Feature Server service for signaling the call processing station states “free”, “busy”

and “call” using the LEDs on the optiset E and optiPoint telephones in a HiPath 3000/HiPath

5000 network. You can pick up a call by pressing the appropriate button.

Call processing states can only be signaled for a station if the Presence Manager can set a

CSTA monitor point on the relevant station. The status of a MULAP call number cannot be sig-

naled, for example, because a CSTA monitor point cannot be set on a call number of this type.

The dssserver.exe service for the Presence Manager is installed with the HiPath 5000 software.

This is a user-configured service that receives its information from vaplx.dll. The TAPI Ser-

vice Provider is required for the Presence Manager to work.

Table 3-1 Feature Server Components

Component Function

vsrv.exe Basic Feature Server component. As an MS Windows service, it starts all

other components.

vaplx.dll Logical interface for applications. Provides read-only and read/write access

to CDB data.

cars.exe The Call Address Resolution Server provides the HG 1500 boards with the

call numbers of all HiPath 3000 systems (nodes) that belong to the net-

work.

Note: Event 1027 confirms that the corresponding HG 1500 board was

successfully downloaded with the call numbers of all HiPath 3000 systems

associated with the network.

regserv-

er.exe

Following startup, the HG 1500 boards automatically log on to the Feature

Server over the Registration Server.

vsync.exe All “node-specific” CDB changes (for example, by key programming, Assis-

tant T) are reported by the node to the Feature server’s VSYNC process.

This ensures the automatic synchronization of the Feature Server with the

new CDB data.

FCT.dll Interface to the systems for direct CDB data access.