HiPath Parameters

HiPath connectors connect to Siemens HiPaths and monitors listed devices as well as sending call control commands to the HiPaths.

Supported PBX’s using HiPath connector

The HiPath connector can be used connecting to HiPath 3000 series, OpenScape Office single node and OpenScape Business single/multi node.

OpenScape Office/Business connection

When connecting to OSO/OSB the port is 8800 as default. When using OSB the password must match the password set in OSB administration.

When using OSB multi node there is only need for a single CSTA connection to the master node. The master node then handles the communication with the slave nodes.

Before you start

Additional to the HiPath parameters below, the external trunks and IP trunks for each connected HiPath are to be listed under Devices.

IP address, Port
Address and port of the HiPath PBX
PBX Trunk Code
The digit to dial when creating an external call from the PBX. Usually this is 0
Incoming Trunk Code
Depending on the PBX setup, external incoming A-numbers may or may not have a preceding digit (usually 0). If this is the case, this digit should be defined here so that the incoming numbers can be interpreted correctly
Username and Password
CSTA user name and password. If empty the default is AMHOST and 77777.
International prefix
Usually 00. For example 0045xxxx Denmark and 00298xxxx Faroe Islands.
International code
Country code. For example 45 for Denmark and 298 for Faroe Islands
Area trunk code
In countries that are using open calling number and where an arenas trunk code is used (usually 0), the digit should be defined here so that incoming number can be interpreted correctly

Examples of such countries are Sweden and England

Local start/end
Fill in the first and last local number of all the connected HiPaths. All numbers that are not in the interval are treated as external numbers
Max externally called deviceid
The following two parameters are added to solve a problem with the presentation of the called deviceid. In some situations when external incoming calls travel between nodes, the calledDeviceid is changed from the internal representation to the external representation. When this occurs Totalview is not able to map the calledDeviceid with the correct user. N.B. This check is only needed in special cases and when multiple nodes are connected. Do only use if problem appears.
Enable max local digits
Enable the test of the max length of the calledDeviceid as explained above.
Max length
Set the max length of externally called calledDeviceid’s. E.g. if an external incoming call is calling deviceid 4095, but a travel through nodes changes this to 344095, then a max length of 4 assures us that Totalview interprets this as 4095.
Max national digits
In some cases the CSTA callingDevice and calledDevice do not contain the international prefix (typically 00). Totalview uses the 00 to differentiate between international and national calls.

Setting the max national digits helps solve this problem when it occurs. E.g. national digits are 22334455 (8 digits) and international call is 4622334455 (10). Using this parameter Totalview can differentiate between the calls. N.B. This check is only needed in special cases and when multiple nodes are connected. Do only use if problem appears.

Wait for delivered
When blind transferring calls to external devices, the HiPath connector by default does not wait for a delivered event before transferring the call.

In some situations this might cause problems for third party monitoring software.

When “Wait for Delivered” is enabled, the HiPaths wait for the delivered event before transferring the call.

N.B. Waiting for the delivered event before transferring the call might slow down transfers to external devices – especially if the external device is a mobile device.

Always add trunk code
When “Always add trunk code” is enabled the Totalview server will add the outgoing trunk code to external numbers. E.g. if the user enters 05000, then the HiPath will dial 005000
Generate call statistics
Enable to generate call statistics data from the HiPath connector. The “Call statistics enabled” settings under “Server settings” must also be enabled to generate call statistics data. Default value is true.
Use ClearConnection
When enabled, ClearConnection is used in Consult/Transfer calls instead of the default TransferCall. Using TransferCall sometimes result in undesired behavior on HiPath installations. If experiencing problems with BlindTransfer or Consult/Transfer then enabled “Use ClearConnection”.

N.B. TransferCall is required when using OpenScape Business.

Master OSB node When using OpenScape Business in nodes and using one TotalviewHiPath connector per node, the DeviceIDs will first be initialized on non-master nodes.
If a DeviceID is not found on non-master nodes then is initialized against the master node.
This solves the problem with DeviceIDs being initialized both on slave and master.
Only one TotalviewHiPath connector should be set as master.

Internal representation of external numbers

The Totalview server uses the values defined in Incoming Trunk Code, International prefix, International code and Area trunk code to convert external numbers to fully qualified numbers.

Fully qualified numbers means that numbers are defined with the international code, e.g. +4532003200 or +4670320032.

For closed number plans, like Denmark, the A-number 32003200 is changed to +4532003200.

For open number plans, like Sweden, the A-number 016320032 is changed to +4616320032.

When Totalview is looking in the phonebook for owners of incoming A-numbers the fully qualified number is used. Registered numbers in the phonebook must therefore also be fully qualified.


Monitoring external numbers

External numbers can be monitored when the HiPaths external trunks. The external numbers must be registered as fully qualified in Users for the monitoring to function properly.

Examples for fully qualified numbers are:

Faroe Islands

Normally used settings

International prefix International code Area code trunk
00 45
00 47
00 46 0
00 358 0
Faroe Islands
00 298

MULAP monitoring

In CSTA V8 changes are made to the HiPath software that enables monitor on MULAP groups. Totalview implements MULAP monitoring.

When using MULAP monitoring the CallControl and Events changes. MULAP monitoring is enabled using the HiPath using Manager E. The setting is found under System parameters.Plus product flags. MULAP monitoring is always enabled when using OpenScape Business

MULAP group numbers must be registered as the users default local device and not as a MULAP number.
Registering MULAP member devices is optional.

When using MULAP monitoring the following applies:

  • SetDoNotDisturb is not implemented for MULAP number. Totalview contains a work around for this problem.
  • If changing MULAP monitoring in HiPath Plus Product Flags, the connector must be restarted for the changes to be reflected in Totalview.
  • If deactivating MULAP monitoring in HiPath Plus Product Flags, the HiPath must be restarted for the changes to take effect.

In OSB the “MULAP monitoring” behavior have changed compared to HiPath v9.

The MULAP device is seen as the users single contact point and it is not possible to monitor member devices. This results in the following:

  • No events are generated for calls directly to the member devices. Events are only generated for calls to the MULAP device.

It is there for not possible for Totalview to show direct calls to MULAP member devices.

  • No events are generated for DND on MULAP device or members.

Totalview is not notified if DND is set on the MULAP or MULAP member devices.

This might result in Totalview showing the wrong DND state if DND is set using service codes and not the Totalview client.

IP monitoring

The following applies if using HiPath. This is not required if using OpenScape Business.

If using the Plus product function “Networked-CTI domain”, available in CSTA v8 MR5, the following Totalview setup must be true.

  • The Behaviour Configuration “Wait for Delivered” must be enabled in Admin.Connectors.Hipath connector. If not, transfers to another node over IP will fail.
  • Only external trunks must be listed in Admin.Devices.Trunk Devices. If IP trunks are listed, retrieving calls transferred to antother node over IP will fail.
Last edited on September 14th, 2018