Installing HMP Elements with CTI32

  1. Home
  2. CTI32 Legacy Articles
  3. Installing HMP Elements with CTI32

Installing HMP Elements with CTI32

Author’s note:  This article supports our legacy products.  At Inventive Labs, after two decades of providing telephony tools, we never stop supporting those who rely on our products to run their businesses.  We no longer recommend Dialogic. This article is for our customers who are using legacy equipment. For more information about these legacy products and where we are today, read  Ditch Dialogic & Convert to Voice Elements.

Voice Elements Platform combines Microsoft’s .NET environment with the power of the HMP Elements SIP Stack and increase the ease and productivity of development.  Legacy users of the CTI32 Toolkit can still interface with HMP Elements.  This article address how to configure the installation of CTI32 with HMP Elements.

Below are the steps necessary to have CTI32 configured to work with HMP Elements. If you have any difficulty, please email

Begin with installing Hmp Elements

Contact Support for links to the download pages at

After installation you will need to configure HMPElements. Use this page for more information on configuration:

HMP_Elements – Configuration_Settings

Install CTI32 Overlay Modules

Next you will need to update some of your CTI32 modules. Be sure to back up your existing modules. The new modules should be placed in your CTI32 folder.

A new tag must be added to the CTI32Engine.config file. Manually edit your file and within the <default> section of the XML add:


Modify your CTI32 Service Configuration File

Edit your Cti32.exe.config file. (Note: Some of these settings may already exist, so you will need to merge this into your existing .config file. Also ensure that the <configSections> has all three setting sections.)

<?xml version="1.0" encoding="utf-8" ?>
       <sectionGroup name="applicationSettings" type="System.Configuration.ApplicationSettingsGroup, System, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089" >
           <section name="HmpElements.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />
           <section name="CTI32NetLib.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />
           <setting name="HmpElementsUrl" serializeAs="String">
         <setting name="HmpDefaultDestinationHost" serializeAs="String">
         <setting name="HmpDefaultSourceDisplayName" serializeAs="String">
           <value>Inventive Labs</value>
         <setting name="HmpDefaultSourceUser" serializeAs="String">
         <setting name="HmpDefaultSourceHost" serializeAs="String">
         <setting name="HmpDefaultDestinationPort" serializeAs="String">
         <setting name="HmpDefaultSourcePort" serializeAs="String">
         <setting name="HmpDestinationHostOverrides" serializeAs="String">
       <customErrors mode="off"/>
  • The HMPElementsURL tells the CTI32NetLib where to connect to HMPElements.
  • The HmpDefaultDestinationHost tells where your sip carrier is (their IP address).
  • The HmpDefaultSourceDisplayName is the display name that is used in the FROM header.
  • The HmpDefaultSourceUser is the default oubound caller ID also in the From header.
  • The HmpDefaultSourceHost is the ip of your machine or the external ip if you are traversing a NAT.
  • The HmpDefaultDestinationPort normally is 5060
  • The HmpDefaultSourcePort also 5060
  • The HmpDestinationHostOverrides allows you to redirect traffic from the default carrier.

HmpDestinationHostOverrides is defined as:


In this way, if you dial 500, it wont go out over the default DestinationHost (IE Your SIP Carrier), instead it will go to the ip specified. This is used as a shortcut for sending traffic to a local sip phone.

Separate the number/ip pairs with a ~. You can have as many as you like.

Starting HMP Elements

HMPElements is installed as a service. You will need to issue:

NET START HmpElements

from the command line, or use the services panel.

Ensure Vap XML file exists

Was this article helpful to you? No Yes 13

How can we help?