Phone_integration_connectors_8.0
Phone_integration_connectors_8.0
Version 8.0
This documentation is provided under restrictions on use and are protected by intellectual property laws. Except as
expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate,
broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any
means. Reverse engineering, disassembly, or decompilation of this documentation, unless required by law for
interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you
find any errors, please report them to us in writing.
Table of Contents
Can I dial an external phone number with an extension external number, bypassing the secretary/answering machine?
How can I add a custom process to the CTI panel? 2928
Feature comparison for supported phone systems 30
Notes 31
Note. If you purchase Webitel Call Manager cloud, all setup will be performed by Webitel support. If you
purchase Webitel Call Manager on-site, you can order setup service from Webitel or study the
requirements and perform the setup according to the Webitel setup guide.
A green indicator at the top right corner of the application indicates that phone integration runs correctly in
Creatio (Fig. 1).
To work with the service, populate the “Webitel users” lookup. You have to register your company's employees in
Creatio to enable them to make internal calls directly from the application.
Note. See more details on how to register Creatio users in the “Add a new user in Creatio” article.
When adding a Creatio user, the system will automatically assign a Webitel extension number. It will be displayed
on the Communication options detail of the contact page. By default, the phone number assignment starts
from 100. Upon the next user registration, the following ordinal numbers will be assigned, for example, 101, 102,
103, etc.
Note. The telephone number is generated automatically based on the specified template. You can change
the auto-numbering using the "Webitel user number mask" system setting.
a. [ Disable Contact Center integration ] – select to disable a built-in Webitel integration. The call button will not
be displayed on the communication panel of the application.
b. [ Enable debugging ] – this checkbox allows you to display troubleshooting information within the browser
console. This troubleshooting information can be used when the phone integration runs into problems and
the customer addresses the service team.
c. [ Use Web phone ] – this checkbox enables you to use a webphone. Clear the checkbox if you need to use
the down-line phone.
d. [ Use video ] – this checkbox enables making video calls on internal numbers.
1. Click [ Save ].
In Creatio, the Asterisk integration functionality requires a separate license. You need to generate a license
request, send it to our support team, upload the received license file into the system, and distribute the licenses
among users. Learn more in separate articles: Creatio licensing and Manage user licenses.
The integration is only possible if complete preliminary Asterisk setup was performed by the phone integration
administrator.
Attention. If you set up the telephony for a Creatio production environment, deploy Creatio Messaging
Service on a separate node rather than on the Creatio application server. To ensure the fault tolerance of
your phone integration, we recommend setting up at least two nodes with Creatio Messaging Service as
well as a balancer that redirects users in case connection with one of the nodes is lost.
[creatio]
secret = creatio
deny=0.0.0.0/0.0.0.0
permit=0.0.0.0/0.0.0.0
read = call,agent,originate
write = call,agent,originate
Replace the deny and permit values with the corresponding addresses.
Attention. Software phones or agent phones can place calls on hold. Communication panel handles the
call status change. The panel indicates that calls are placed on hold and resumed, but it cannot place calls
on hold.
a .NET Framework package version 4.7.2 or later on the server where you are going to install Creatio
Messaging Service
at least 2 Gb of RAM and 20 Gb of free drive space
2. Contact Creatio support to receive the messaging service installation files or download the files via the URL:
Download the archive. Unpack the archive to a folder to ensure a smooth installation. If you run the installation
directly from the archive, the archiver application might interfere with the install wizard.
Attention. Deploy CMS on the server connected to both the Creatio application server and the PBX.
Learn more in a separate article: Telephony integration basics.
3. Run the Creatio Messaging Service Install.msi file on the machine intended as the message exchange
server and proceed with the installation.
4. Make sure that the TerrasoftMessagingService service is running in the Windows Services application. If
the TerrasoftMessagingService service is not running, start it manually.
5. Open the folder that contains the service files: ~\Terrasoft Messaging Service. Specify the following
parameters for Asterisk connector in the Terrasoft.Messaging.Service.exe.config configuration file:
<asterisk filePath="" url="Asterisk server name or URL" port="Asterisk server port" userName="Asteris
filePath Use the parameter for system diagnostics. It lets you repeat a set
of events from the pre-configured scenario file. The default value
must be empty.
originateContext Initiates a call to a phone number from Creatio. Contains the name
of the context from which to call the user phone number. The
default value for FreePBX is from-internal .
queueExtensionFormat The format that determines the call channel while receiving calls
from the queue. The default value for LocalChannel in FreePBX is
Local/{0}@from-queue .
sendRingStartedOnRingingState Ensures the call retrieval from the queue is handled correctly. If
you select the checkbox, Creatio displays the call for the user after
receiving the NewState AMI event that has the Ringing parameter.
By default, “On.”
traceQueuesState Diagnoses the agent status in the queue. Use the parameter to
debug the queue if the agent receives a second call from the
queue while handling the first call in Creatio. Agent status data is
written to the connector log file. By default, “Off.”
protocol The protocol type: SIP or PJSIP. Contact your PBX administrator to
find out the needed protocol type.
6. Restart the CMS and test the phone integration. The connection to Asterisk is established on CMS startup but
packet handling begins after an agent goes online.
Note. Follow this instruction if you need to update Creatio Messaging Service.
Attention. You can set up Messaging Host (Creatio Messaging Service) on .NET Core in Creatio version
7.16.3 – 8.0.8. Support for .NET Core 3.1 will be retired in Creatio version 8.0.9. We recommend moving to
.NET 6 when updating Creatio to version 8.0.8. You can set up Messaging Host (Creatio Messaging Service)
on .NET 6 in Creatio version 8.0.8 and later.
1. Install Docker. To install Docker on Linux, follow the guide in the Docker documentation. To check the installed
Docker version, run the following command at the Linux terminal:
docker --version
2. Install Docker Compose. To install Docker Compose on Linux, follow the guide in the Docker documentation.
To check the installed Docker Compose version, run the following command at the Linux terminal:
docker-compose --version
3. Install and set up the Docker Compose components. Deploy the container of the messaging service via the
Docker Compose utility. Download the archive via the following link: Download the archive. Unpack the archive
that contains the configuration files and scripts to any directory, for example, /opt/messaging.host.
Note. The configuration files contain all necessary default settings for a Linux-based server.
The structure of the archive that contains the configuration files and scripts:
/etc/
4. Use Linux terminal to go to the /docker-compose directory of the unpacked archive, for example,
/opt/messaging.host/docker-compose.
5. Run the sudo docker-compose pull command at the terminal. Wait until the required service component
images are downloaded from the Docker Hub completely.
Attention. If the server Internet access is restricted, download the needed images manually to a
machine that has free access (see the docker-compose.yml configuration file) and transfer the images
as files to the target machine using the sudo docker export and sudo docker import commands.
6. Specify the following parameters for Asterisk connector in the etc/appsettings.json configuration file:
{
"url": "Asterisk server name or URL",
"port": "Asterisk server port",
"userName": "Asterisk login",
"secret": "Asterisk password",
"originateContext": "Outbound context",
"autoPauseOnCommutationStart": "true",
"queueExtensionFormat": "Local/{0}@from-queue/n",
"asyncOriginate": "true",
"sendRingStartedOnRingingState": "true",
"traceQueuesState": "false",
"protocol": "The protocol type used: SIP/ or PJSIP/",
"packetInfoConfig": "Additional packet parameters to handle within the configuration",
"filePath": ""
}
{
"url": "10.0.15.185",
"port": "5038",
"userName": "creatio",
"secret": "creatio",
"originateContext": "from-internal",
"autoPauseOnCommutationStart": "true",
"queueExtensionFormat": "Local/{0}@from-queue/n",
"asyncOriginate": "true",
"sendRingStartedOnRingingState": "true",
"traceQueuesState": "false",
"protocol": "PJSIP/",
"packetInfoConfig": "",
"filePath": ""
}
7. Run the sudo docker-compose up -d command to launch the service. A logs directory will be created in the
current catalog.
See the list of Asterisk connector parameters in the following table:
originateContext Initiates a call to a phone number from Creatio. Contains the name
of the context from which to call the user phone number. The
default value for FreePBX is from-internal .
queueExtensionFormat The call channel format while receiving the call from the queue. The
default value for LocalChannel in FreePBX is Local/{0}@from-queue .
sendRingStartedOnRingingState Ensures the call retrieval from the queue is handled correctly. If
you select the checkbox, Creatio displays the call for the user after
receiving the NewState AMI event that has the Ringing parameter.
By default, “On.”
traceQueuesState Diagnoses the agent status in the queue. Use the parameter to
debug the queue if the agent receives a second call from the
queue while handling the first call in Creatio. Agent status data is
written to the connector log file. The default value is “Off”.
protocol The protocol type: SIP or PJSIP. Contact your PBX administrator to
find out the needed protocol type.
filePath Use the parameter for system diagnostics. It lets you repeat a set
of events from the pre-configured scenario file. The default value
must be empty.
8. Restart the CMS and test the phone integration. The connection to Asterisk is established on CMS startup but
packet handling begins after an agent goes online.
1. Open the System Designer, for example, by clicking in the top right corner of the application.
3. Open the “Default messages exchange library” (“SysMsgLib” code) system setting and set its default value to
“Asterisk 13/16/18 (AMI) telephony integration library.”
4. Open the “Message exchange server” (“SysMsgServerNode” code) system setting and specify the connection
parameters of the system messages service. Specify the network address of the message exchange server in
the [ Default value ] field. Use the following format: “ws://[ server ]:2013” for sites served over HTTP or
“wss://[ server ]:2013” for sites served over HTTPS, where:
[ server ] is the domain name of the server that hosts the message exchange service. We do not
recommend using IP addresses or “localhost.”
2013 is the default port to connect to the messaging service. You can change the port number in the
Terrasoft.Messaging.Service.exe.config file. We do not recommend using “localhost” as it might
cause errors when connecting to the phone integration server. When using a wss connection, make sure
that server address matches the address in the SSL certificate.
Note. If your website is served over HTTPS and secure (WSS) connection is used for WebSockets,
install a security certificate on the message exchange server and specify the certificate in the
configuration files of the message service. For more information about the setup process, contact
Creatio support.
ATTENTION. You can set up Messaging Host on .NET Core in Creatio version 7.16.3 – 8.0.8. Support for
.NET Core 3.1 will be retired in Creatio version 8.0.9. We recommend moving to .NET 6 when updating
Creatio to version 8.0.8. You can set up Messaging Host on .NET 6 in Creatio version 8.0.8 and later.
1. Open the System Designer, for example, by clicking in the top right corner of the application.
[ server ] is the domain name of the server that hosts the message exchange service. We do not
recommend using IP addresses or “localhost.”
2013 or 2014 is the default port to connect to the messaging service. You can change the port number in
the docker-compose.yml configuration file. We do not recommend using “localhost” as it might cause
errors when connecting to the phone integration server. When using an HTTPS connection, make sure that
server address matches the address in the SSL certificate.
Note. If your website is served over HTTPS and secure connection is used for WebSockets, install a
security certificate on the message exchange server and specify the certificate in the docker-
compose configuration. For more information about the setup process, contact Creatio support.
1. Open the user profile page by clicking the [ Profile ] image button on the main page of the application.
2. Click the [ Call Center parameters setup ] button. This opens a page.
3. Fill out the following fields:
a. Select the [ Disable Call Center integration ] checkbox to disable Creatio integration with the phone service.
This hides the call button from the Creatio communication panel.
b. Specify the Asterisk user line number in the [ Number ] field. The line number matches the phone number
by default. For example, to track the SIP/305 user line, specify 305 , and to track the SIP/office line, specify
the office .
Attention. Each user uses an individual line. We do not recommend specifying the same line for
multiple users as it can cause errors.
c. Specify the context of the outgoing call in the [ Outgoing call context ] field if the context for the user must
differ from the system context specified in the Terrasoft.Messaging.Service.exe.config file.
d. Select the [ Enable debugging ] checkbox to display troubleshooting information in the browser console.
You can use the information if you encounter phone integration and customer contact issues.
4. Click [ Save ].
5. Refresh the browser page to apply the changes.
In Creatio, the Avaya integration functionality requires a separate license. You need to generate a license request,
send it to our service team, upload the received license file into the system, and distribute the licenses among the
users. Read more: Creatio licensing and Manage user licenses.
The integration is only possible if complete preliminary Avaya setup was performed by the phone integration
administrator.
Attention. If you set up the telephony for a Creatio production environment, deploy Creatio Messaging
Service on a separate node rather than on the Creatio application server. To ensure the fault tolerance of
your phone integration, we recommend setting up at least two nodes with Creatio Messaging Service, as
well as a balancer that would redirect users in case of lost connection with one of the nodes.
Attention. Install Creatio Messaging Service on a .NET Framework Windows server to integrate Avaya
PBX.
DMCC .NET API integration protocol requires licenses. The number of licenses should correspond to the number
of Creatio users who simultaneously use Avaya phone integration. See Avaya documentation for more
information.
Note. Your PBX must include Avaya Application Enablement Services (AES) component for Avaya phone
integration. The integration is available for AES server version 5.2 and later.
1. Before installing Creatio Messaging Service (CMS), make sure that your computer runtime environment has:
A .NET Framework package version 4.7.2 or later on the server where you are going to install Creatio
Messaging Service.
At least 2 Gb of RAM and 20 Gb of free drive space.
2. Contact Creatio support to receive the messaging service installation files or download the files via the URL:
Download Creatio Messaging Service. Unpack the archive to a folder to ensure a smooth installation. If you
run the installation directly from the archive, the archiver application may interfere with the install wizard.
Attention. Deploy CMS on the server connected to both the Creatio application server and the PBX.
Read more: Telephony integration basics.
3. Run the Creatio Messaging Service Install.msi file on the machine intended as the message exchange server
and proceed with the installation.
4. Make sure that the “TerrasoftMessagingService” service is running in the Windows Services application. If the
“TerrasoftMessagingService” service is not running, start it manually.
5. Open the folder with the service files: ~\BPMonline Messaging Service. Specify the following parameters for
Avaya connector in the “Terrasoft.Messaging.Service.exe.config” configuration file:
port Connection port to AES server. Default value: “4721” for the unsecured
connection or “4722” for the secured connection.
useSecureSockets The checkbox for the encrypted connection usage requires adding a certificate.
By default, “False.”
protocolVersion The protocol used to connect to AES server. the default value:
“http://www.ecma-international.org/standards/ecma-323/csta/ed3/priv6.”
Note. Follow this instruction if you need to update the Creatio Messaging Service.
1. Open the system designer by clicking in the top right corner of the application window.
“0.0.0.0” – IP address that your Creatio users use to access your message exchange server.
“2013” – the port used by default for connecting to the messaging service. You can change the port
number in the “Terrasoft.Messaging.Service.exe.config” file.
Note. If your website is served over HTTPS and secure (WSS) connection is used for WebSockets, you
will need to install a security certificate on the message exchange server and specify it in the
configuration files of the message service. For more information about the setup process, contact
Creatio technical support.
5. Click [ Save ].
1. Open the user profile page by clicking the [ Profile ] image button on the main page of the application.
2. Click the [ Call Center parameters setup ] button.
3. On the opened page, fill out the required values:
a. [ Disable Call Center integration ] – this checkbox allows you to disable Creatio integration with the phone
integration. The call button will not be displayed on the communication panel of the application.
4. Click [ Save ].
5. Refresh the browser page to apply the changes.
This article describes integration with Cisco Finesse version 11.5 and later. We recommend using new
phone service versions to ensure secure and reliable operation. If you need to set up integration with Cisco
Finesse version 11.0 and earlier for testing purposes or to look for errors, follow the instructions for
Creatio version 7.16.
In Creatio, the Cisco Finesse integration functionality requires a separate license. To license the phone service,
generate a license request, send it to our support team, upload the received license file to Creatio, and distribute
the licenses among users. Learn more in separate articles: Creatio licensing, Manage user licenses.
Before you set up the integration, make sure that the phone service administrator has already configured Cisco
Finesse.
Attention. To ensure the integration operates as intended, enable the CORS technology support in Cisco
Finesse settings. You can do this using the following commands
utils finesse cors enable_all
4. Click [ Save ].
5. Specify the WSS protocol address of your Cisco Finesse server in the “Finesse 11.5+ websocket address”
(“FinesseWebsocketAddress” code) system setting. Use the following format: wss://:8445. For example,
wss://hq-uccx.abc.inc:8445.
6. Click [ Save ].
1. Open the user profile page, e. g., by clicking [ Your profile ] on the Creatio homepage.
a. Select the [ Disable Contact Centre integration ] checkbox to disable Creatio integration with the phone
service. This hides the call button from the Creatio communication panel.
b. Specify the Cisco Finesse user parameters in the [ Agent Id ], [ Extension ], [ Password ] fields.
c. Select [ Enable debugging ] checkbox to display troubleshooting information within the browser console.
For example, you can use the information if you encounter phone service and customer contact issues.
4. Click [ Save ].
5. Refresh the browser page to apply the changes.
In Creatio, the TAPI integration functionality requires a separate license. You need to generate a license request,
send it to our service team, upload the received license file into the system, and distribute the licenses among the
users. Read more: Creatio licensing and Manage user licenses.
The integration is only possible if complete preliminary TAPI driver setup was performed by the phone integration
administrator.
Attention. If you set up the telephony for a Creatio production environment, deploy Creatio Messaging
Service on a separate node rather than on the Creatio application server. To ensure the fault tolerance of
your phone integration, we recommend setting up at least two nodes with Creatio Messaging Service, as
well as a balancer that would redirect users in case of lost connection with one of the nodes.
Attention. Install Creatio Messaging Service on a .NET Framework Windows server to integrate TAPI PBX.
1. Before installing Creatio Messaging Service (CMS), make sure that your computer runtime environment has:
A .NET Framework package version 4.7.2 or later on the server where you are going to install Creatio
Messaging Service.
At least 2 Gb of RAM and 20 Gb of free drive space.
2. Contact Creatio support to receive the messaging service installation files or download the files via the URL:
Download Creatio Messaging Service. Unpack the archive to a folder to ensure a smooth installation. If you
run the installation directly from the archive, the archiver application may interfere with the install wizard.
Attention. Deploy CMS on the server connected to both the Creatio application server and the PBX.
Read more: Telephony integration basics.
3. Run the Creatio Messaging Service Install.msi file on the machine intended as the message exchange server
and proceed with the installation. The TAPI driver must be installed and configured on the same computer by
the phone integration administrator. To ensure that the TAPI driver runs correctly, use the “Conference.exe”
utility you can receive from the support team.
4. Test the phone integration.
Note. Follow this instruction if you need to update the Creatio Messaging Service.
1. Open the system designer by clicking in the top right corner of the application window.
“0.0.0.0” – IP address that your Creatio users use to access your message exchange server.
“2013” – the port used by default for connecting to the messaging service. You can change the port
number in the “Terrasoft.Messaging.Service.exe.config” file.
Note. If your website is served via HTTPS and secure (WSS) connection is used for WebSockets,
you will need to install a security certificate on the message exchange server and specify it in the
configuration files of the message service. For more information about the setup process, contact
Creatio technical support at [email protected].
5. Click [ Save ].
1. Open the user profile page by clicking the [ Profile ] image button on the main page of the application.
a. [ Disable Call Center integration ] – this checkbox allows you to disable Creatio integration with the phone
integration. The call button will not be displayed on the communication panel of the application.
b. [ Line ] – user line number in TAPI.
Attention. A separate line is used for each user. It is not recommended to specify the same line for
several users, as it may cause errors.
c. [ Enable debugging ] – this checkbox allows you to display troubleshooting information within the browser
console. This troubleshooting information can be used when the phone integration runs into problems and
the customer addresses the service team.
4. Click [ Save ].
5. Refresh the browser page to apply the changes.
In Creatio, the CallWay integration functionality requires a separate license. You need to generate a license
request, send it to our service team, upload the received license file into the system, and distribute the licenses
among the users. Read more: Creatio licensing and Manage user licenses.
The integration is only possible if complete preliminary CallWay setup was performed by the phone integration
administrator.
Attention. If you set up the telephony for a Creatio production environment, deploy Creatio Messaging
Service on a separate node rather than on the Creatio application server. To ensure the fault tolerance of
your phone integration, we recommend setting up at least two nodes with Creatio Messaging Service, as
well as a balancer that would redirect users in case of lost connection with one of the nodes.
1. Before installing Creatio Messaging Service (CMS), make sure that your computer runtime environment has:
A .NET Framework package version 4.7.2 or later on the server where you are going to install Creatio
Messaging Service.
2. Contact Creatio support to receive the messaging service installation files or download the files via the URL:
Download Creatio Messaging Service. Unpack the archive to a folder to ensure a smooth installation. If you
run the installation directly from the archive, the archiver application may interfere with the install wizard.
Attention. Deploy CMS on the server connected to both the Creatio application server and the PBX.
Read more: Telephony integration basics.
3. Run the Creatio Messaging Service Install.msi file on the machine intended as the message exchange server
and proceed with the installation.
4. Make sure that the “TerrasoftMessagingService” service is running in the Windows Services application. If the
“TerrasoftMessagingService” service is not running, start it manually.
5. Open the folder with the service files: ~\BPMonline Messaging Service. Specify the CallWay server address in
the “Terrasoft.Messaging.Service.exe.config” file:
login
Integration protocol login and password.
password
restoreConnectionInterval The time interval to reconnect the integration messaging service to the
CallWay phone integration server if a failure occurs. The value is
specified in milliseconds and is “2000” - by default.
Note. Follow this instruction if you need to update the Creatio Messaging Service.
1. Open the system designer by clicking in the top right corner of the application window.
“0.0.0.0” – IP address that your Creatio users use to access your message exchange server.
“2013” – the port used by default for connecting to the messaging service. You can change the port
number in the “Terrasoft.Messaging.Service.exe.config” file.
Note. If your website is served over HTTPS and secure (WSS) connection is used for WebSockets,
you will need to install a security certificate on the message exchange server and specify it in the
configuration files of the message service. For more information about the setup process, contact
Creatio technical support at [email protected].
5. Click [ Save ].
1. Open the user profile page by clicking the [ Profile ] image button on the main page of the application.
2. Click the [ Call Center parameters setup ] button.
3. On the opened page, fill out the required values:
a. [ Disable Call Center integration ] – this checkbox allows you to disable Creatio integration with the phone
service. The call button will not be displayed on the communication panel of the application.
b. [ Agent internal number ] – CallWay user phone number.
c. [ Routing rule ] – specify the routing rule if it is required for the CallWay configured server.
d. [ Use CallWay client ] – select the checkbox if an employee uses CallWay internal client. While using the
CallWay internal client, the answer button in the application becomes available.
e. [ Enable debugging ] – this checkbox allows you to display troubleshooting information within the browser
console. This troubleshooting information can be used when the phone integration runs into problems and
4. Click [ Save ].
5. Refresh the browser page to apply the changes.
In Creatio, the Infinity integration functionality requires a separate license. You need to generate a license request,
send it to our service team, upload the received license file into the system, and distribute the licenses among the
users. Learn more in separate articles: Creatio licensing, Manage user licenses.
The integration is only possible if complete preliminary Infinity setup was performed by the phone integration
administrator.
Attention. If you set up the telephony for a Creatio production environment, deploy Creatio Messaging
Service on a separate node rather than on the Creatio application server. To ensure the fault tolerance of
your phone integration, we recommend setting up at least two nodes with Creatio Messaging Service, as
well as a balancer that would redirect users in case of lost connection with one of the nodes.
1. Prepare Infinity X
Create an account in Infinity X with the role “Third-Party integration connection”. This account will be used on the
integration service level. It is not recommended to use this user account for other purposes, or log in under this
user account, as this may cause integration errors.
Attention. Install Creatio Messaging Service on a .NET Framework Windows server to integrate Infinity X
PBX.
1. Make sure that your computer runtime environment has the following before installing Creatio Messaging
Service (CMS):
a .NET Framework package version 4.7.2 or later on the server where you are going to install Creatio
Messaging Service
at least 2 Gb of RAM and 20 Gb of free drive space
2. Send the following files from the “Client” folder created during the Infinity X setup to Creatio support:
Cx.Integration.BaseConnector.dll
Cx.Integration.AgatInfinityConnectorInterfaces.dll
Cx.Integration.AgatInfinityConnectorFactory.dll
3. Creatio support will send you an archive with CMS files to upload and install on the server. Unpack the archive
to a folder to ensure a smooth CMS installation. If you run the installation directly from the archive, the install
wizard might not operate as intended.
Attention. Deploy CMS on the server connected to both the Creatio application server and the PBX.
Learn more in a separate article: Telephony integration basics.
4. Run the Creatio Messaging Service Install.msi file on the machine intended as the message exchange server
and proceed with the installation.
5. Make sure that the “TerrasoftMessagingService” service is running in the Windows Services application. If the
“TerrasoftMessagingService” service is not running, start it manually.
6. Copy the “Client” folder (created during the Infinity X setup) to a separate folder, e.g., the folder with the CMS
service.
7. Open the folder with the service files: ~\BPMonline Messaging Service.
8. Specify the following parameters in the Infinity block of the Terrasoft.Messaging.Service.exe.config file:
a. infinityXClientPath. The path to the “Client” folder. If the “Client” folder is located in the CMS service folder,
the parameter value will be as follows: infinityXClientPath="\Client"
b. thirdPartyIntegrationLogin. The login of the user with the “Third-Party integration connection” role.
c. thirdPartyIntegrationLogin. The password of the user with the “Third-Party integration connection” role.
1. Open the system designer by clicking in the top right corner of the application window.
3. Set the default value of the “Default messages exchange library” (“SysMsgLib” code) system setting to
“Telephony integration library based on Infinity protocol”.
4. Specify the message service connection parameters. To do this, open the “Message exchange server”
(“SysMsgServerNode” code) system setting. In the [ Default value ] field, specify the network address of the
message exchange server in the following format: “ws://0.0.0.0:2013” if your website is served over HTTP or
“0.0.0.0” is the IP address that your Creatio users use to access your message exchange server.
“2013” is the port used by default for connecting to the messaging service. You can change the port
number in the “Terrasoft.Messaging.Service.exe.config” file.
Note. If your website is available by HTTPS and secure (WWS) connection is used for WebSockets,
you will need to install a security certificate on the message exchange server and specify it in the
configuration files of the message service. For more information about the setup process, contact
Creatio technical support at [email protected].
5. Click [ Save ].
1. Open the user profile page by clicking the [ Profile ] image button on the main page of the application.
2. Click the [ Call Center parameters setup ] button. This opens a page.
3. Fill out the required values on the page that opens:
a. Select the [ Disable Contact Centre integration ] checkbox to disable Creatio integration with the telephony.
The call button will not be displayed on the communication panel of the application.
b. Specify application IP address and port in the [ Infinity server address ] field. Learn more about the ports
required for implementing the full functionality of Infinity X in Creatio Community.
c. Specify the telephone number of the line which will be used for the call in the [ Line ] field.
Attention. A separate line is used for each user. It is not recommended to specify the same line for
several users, as it may cause errors.
d. Select [ Enable debugging ] checkbox to display troubleshooting information within the browser console.
This troubleshooting information can be used when the phone integration runs into problems and the
customer addresses the service team.
4. Click [ Save ].
5. Refresh the browser page to apply the changes.
You can configure a WSS phone service connection. This procedure is relevant for Asterisk, Avaya, TAPI,
CallWay, and Infinity phone service users.
Note. Configure the WebSockets technology to ensure the correct operation of the phone service in
Creatio.
Modify the Terrasoft.Messaging.Service.exe.config configuration file on the phone server to configure the
secure connection with the phone service:
1. Delete or comment out the following configuration block in the <servers> section:
<server name="ClientWebSocketService"
idleSessionTimeOut="10000" maxCommandLength="4096"
maxConnectionNumber="10000">
</server>
2. Contact an official certification center to receive a PFX certificate. A system administrator must obtain the
certificate.
3. Remove the comment from the following block in the <servers> section:
<server name="ClientWebSocketService"
</server>
4. Specify the PFX digital certificate you received from the certification center, as well as the access password in
the <certificate> section. Place the certificate in the folder with the Creatio Messaging Service binary files.
Attention. It is not recommended to use self-signed certificates, because this may violate security
conditions.
5. After modifying the configuration file, change the address of the connection to the phone server in the
“Message exchange server” (“SysMsgServerNode” code) system setting from ws:// to wss://.
6. Install the new version of Creatio Messaging Service. Unpack the archive to a folder to ensure a smooth
installation. If you run the installation directly from the archive, the archiver application may interfere with the
install wizard.
7. Compare the settings in the new and the old version. Transfer the settings to the new version if needed.
8. Make sure that the “TerrasoftMessagingService” service is running in the Windows Services application. If the
“TerrasoftMessagingService” service is not running, start it manually.
This depends on the settings in the PBX API. Most APIs do not have this function. If the PBX API has this
function, you will need to perform additional settings on the phone integration server.
To add a business process to the CTI panel, you need to add the process to the [ CTI panel actions ] lookup. As a
result, the process will become available in the [ Processes ] area of the CTI panel for the Contact Center agents.
Note. In Creatio, “contact center agents” are users who are members of the organizational role specified
in the “Folder – Contact Center agents” (ContactCenterOperatorsFolder) system setting. By default, the
role is “CC agents.”
Add the following process parameters to bind the process to other Creatio records:
“CallId” of the “Unique identifier” data type. This parameter is automatically populated with the unique
identifier of the corresponding [ Calls ] section record.
“ContactId” of the “Lookup” data type. Populate this parameter with the unique ID of the caller/call
recipient’s contact.
“AccountId” of the “Lookup” data type. Populate this parameter with the unique ID of the caller/call
recipient’s account.
“PhoneNumber” of the “Text (250 characters)” data type. Populate this parameter with the telephone
You can use this data to automatically populate the fields of the new record created during the process
execution.
The telephony features in Creatio vary depending on the connected phone system. By default, Creatio is
integrated with Webitel telephone service. If necessary, you can connect a different system.
Below is a feature comparison table for different phone systems:
Note 1 + + + + + +
+ + + + + Note 2 Note 3
+ + + + + - Note 4
+ + + + + + +
+ + + + + + +
Note 5 + + + + - +
+ + + + + + +
+ + + + + + +
- - - + - - -
- - - + - - -
Notes
1
Due to TAPI limitations, caller identification is unavailable for calls routed through UCCX while using CUCM.
2
The user might have to respond to an incoming system call to initiate an outgoing call from Creatio. The call flow
depends on the software/hardware phone version/model.
3
CallWay software phones are fully supported. If the agent uses a different IP or software phone, they have to
respond to an incoming “system” call to initiate an outgoing call from Creatio.
4
Only CallWay software phones are fully supported.
5
The following 2 statuses are available: “Ready” and “Do not disturb” (DND). Cisco is currently not supported.