Release 3.26

JTELDEV-6460

It was possible to read web server files outside the data directory with a very complicated GET request. This security leak was fixed.

Running an update on any system would break the creating import / export schemes function. This problem has been fixed.

Introdueced login with security token.

A new object "Wait" has been added to the IVR. This performs a simple sleep operation. This can, for example, be used to allow a ring tone to be heard for a certain number of seconds before proceeding in the application.

The IVR did not record statistics correctly for calls which were refused before any event (ringing or connect) had been sent. This problem has been fixed. Note: this requires an update of the telephony server to version 5.23.18 or later.

A new IVR Object "Ringing" has been added. This allows you to explicitly send 180 RINGING (alerting) to the far end from the IVR. Note: ringing and offhook are still sent implicitly by certain functions such as the ACD (when entered - ringing) and when announcements are played (offhook).

The following parameters can be added to an ACD Group which causes the server to send http GET requests (REST calls) to a configured URL when events occur in the call flow to agents.

CallTransfer.Client.<UseCase>.<Event>

The parameter UseCase may be one of:

INBOUND.ACD.DIRECT
INBOUND.ACD.BLENDED
OUTBOUND.CLICKTOCALL
OUTBOUND.DIALLER
TRANSFER.AGENT
TRANSFER.GROUP
TRANSFER.SYNONYM
TRANSFER.NUMBER
TRANSFER.NUMBER_ANNOUNCEMENT

The parameter Event may be one of:

RINGING <-- sent when the call is in the ringing state
CONNECTED <-- sent when the call is connected
CONNRES.1 <-- sent when the call was successful and is ended
CONNRES.2 <-- sent when the call was not answered
CONNRES.3 <-- sent on outbound calls only when the destination is busy
CONNRES.4 <-- sent when the caller hangs up during the call to an agent (inbound calls only)
CONNRES.6 <-- sent when the called agent refused the call or hungup during a whisper transfer announcement

Note, the use cases CONNRES.3 (Busy on an inbound call) and CONNRES.5 (SIP Reason) and CONNRES.7 (Error) are not necessary, since a RINGING event must always be received before any REST calls are made.

The value of the parameter is specified as a multi-line value instructing the server what to do. The following lines are allowed:

URL=<url> <- Specifies a URL to be called
METHOD=GET/POST <- Specifies the http method to use
TIMEOUT=<ms> <- Specifies a timeout in ms before the function is aborted.
HEADER=<http_header> <- Specifies an http header to be used. May be specified multiple times.
QUERYPARAM=<param=value> <- Specifies a query parameter which will be added to the URL in URL encoded format
DATA=<value> <- Specifies POST data which will be sent with the request

The following variables may be used in the parameter value:

$date_time <- the current date and time
$service_number <- the ServiceNumbers.Name field
$service_name <- the ServiceNumbers.Name2 field
$caller <- the caller ID
$agent_name <- The surname of the agent
$agent_firstname <- The firstname of the agent
$agent_number <- The number of the agent
$agent_id <- The ID of the agent
$agent_tel <- The telephone number of the agent
$agent_uid <- The UID of the agent
$agent_nickname <- The NickName of the agent
$group_name <- The name of the ACD group
$group_number <- The number of the ACD group
$diallercampaign_name <- The name of the dialler campaign
$diallercontact_name <- The surname of the dialler contact
$diallercontact_firstname <- The firstname of the dialler contact
$diallercontact_externalsystemlink <- The external system link for the dialler contact
$diallercontact_userdata <- The UserData field for the dialler contact

Examples:

This will send a GET request when a direct inbound ACD call is ringing:

Parameter:
CallTransfer.Client.INBOUND.ACD.DIRECT.RINGING
Value:
URL=http://myrestserver:9999/inbound_acd/ringing
METHOD=GET
TIMEOUT=3000
HEADER=X-JTEL-ACD: True
QUERYPARAM=agentNickname=$agent_nickname
QUERYPARAM=caller=$caller
QUERYPARAM=service_number=$service_number
QUERYPARAM=call_id=$statisticsparta_id
QUERYPARAM=direction=inbound
QUERYPARAM=service_name=$service_name
QUERYPARAM=group_name=$group_name

This will send a POST request when a direct inbound ACD call is not answered:

Parameter:
CallTransfer.Client.INBOUND.ACD.DIRECT.CONNRES.2

Value:
URL=http://myrestserver:9999/inbound_acd/noanswer
METHOD=POST
HEADER=X-JTEL-ACD: True
DATA=agentNickname=$agent_nickname

ACD-S-002 - the records in columns "Answered in Service Calls", "Answered not in Service Calls", "Lost Calls", "Quote Lost Calls" and "Service Level" were not correct depending on the time interval and the granularity chosen. This problem has been fixed.

In Salesforce, the lightning support module now pops up the softphone in addition to any Salesforce record found or screen popped, when a call notification is received.

The full client now supports the same functionality as the mini client - it is possible to call agents, groups, PBX users and numbers directly from the agent home screen. This functionality has been available for several releases in the mini client.

A new object “CRM+ Query” has been added to the IVR for querying the Brainformatik CRM+ system. See https://wiki.jtel.de/x/LoRhAg for details on how this object works.

When generating the reports "ACD Groups Report 5" and "ACD Groups Report 7 "without any selection, an error occurred. This problem has been now fixed.

When trying to generate the report "Transaction Codes Overview" without any selected agents, an error occurred. This problem has now been fixed.

The service installation scripts for the platform UDP listener have been updated to start the UDP listener using java 12.

The login screen now accepts huge passwords with practically no limit.

Extensions with a ' in the name caused problems in the NFON presence connector. This problem has been fixed.

Previously the message “Email sent“ was not translated. This has been corrected.

The JREST server now supports the function {clientsID}/info which returns the time zone information from the server.

Incoming date / time formats now support the following format if configured in the REST server:

yyyy-MM-dd'T'HH:mm:ss.SSSZ

Using an apostrophe or comma in the name of an IVR object would cause problems. These characters are now converted to similar unicode characters which do not cause problems.

The reporting terminology has been changed from ISDN cause to SIP reason in all relevant reports.