TelServer v1.7

Release Notes

Contents

• Latest changes
  • Enhancements
  • Bug fixes
• Summary of changes

Latest changes

The latest version is TelServer v1.7.4 (Build 20111206-1029).

TelServer v1.7.4 changes

Enhancements

• TSWidget/TSLib javascript debugging has been improved.

Bug fixes

• Before Avaya AES version 6.2, to avoid a known issue in the Avaya AES Jtapi which blocks TelServer when canceling a Forward, the use of the SetForward feature should be disabled by the configuration (removing <setForwarding/> from the pbxlink.pbx.csta.supportedServices.default setting). The fix is in Avaya AES version 6.2.

Summary of changes

TelServer v1.7.3 changes

Enhancements

• The PBX call reference is provided in TelServices call events enabling correlation with the history.
• LastRedirectionNumber and firstCalledNumber are saved in the History.
• Customer category information can be added in the directory cache to allow VIP and blacklisted calls.
• A new TelService AddPartyToCall has been added. It maps to a SingleStepConference for PBX supporting this feature.

Bug fixes

• In the SIP/CSTA gateway, dual forking with Asterisk dialplan lead to events even for the SIP trunk to the Mediation Server. A new property is created to ignore these events.

TelServer v1.7.2 changes

Enhancements

• User directory can be defined which enables synchronization with user local directories such as Microsoft Outlook.
• Changing the TelServices session phone number can be controlled by administrator userID/password check.
• WARNING: Remote management username/password settings are deprecated and have become Administrator userid/password settings. The configuration check invites you to change the settings.
• Depending on the PBX configuration and capability, a stand-by link can be defined allowing the link to the PBX to be redundant.
• The directory can search "in-line" in the LDAP or JDBC actual directory. This can be useful for huge directories that would require too much memory to be synchronized. A cache can be built for "in-line" searching.
• The web client "TelServices window" has been removed. It is replaced by the new web client "TSWidget".

Bug fixes

• With Cisco CME PBX, an error is returned if the RequestSystemStatus following a MonitorStart is responded with a SIP 404 error. This was potentially leading to "server unreachable" for valid user sessions.
• When using the CSTAp2 gateway, the MonitorStopResult is not sent to the client requesting a MonitorStop.

TelServer v1.7.1 changes

Enhancements

• Remote management can be disabled.
• In case of starting problem (which usually happens if the license is not correctly installed or is invalid), TelServer-start.log is now created in "work/logs" directory instead of "work".

Bug fixes

• The userID/password information can be used as agentId/password information provided to the PBX.
• For Asterisk, it is impossible to control a call from an unknown caller on a mutli call appearance device.
• For Asterisk, the snom phone configuration must contain the "On Disconnected" action URI.
• For Asterisk, an empty list of contexts (pbxlink.pbx.asterisk.contexts.list being unset or empty) prevents a session to be opened because the MonitorStart is rejected.

TelServer v1.7.0 changes

Enhancements

• The alerting duration of a call is saved in the history.
• Working periods can be defined for routing points. During non working hours, the call may be routed to a special non working hours route.
• Configurable timeout for fast abandoned calls by a customer allows to exclude them from the routing point and agent statistics.
• History is available through the management interface.
• TelServer can be launched as a service on a Windows 64 bits with a 64 bits JVM (using JavaService-x64.exe).

Bug fixes

• Queue slots are not released properly if the other party hangs up.

TelServer v1.6.1 changes

Enhancements

• Asterisk support has been enhanced for Asterisk 1.6 and upper versions (Asterisk 1.4 is not supported). Enhanced features (AnswerCall, HoldCall, RetrieveCall, ConferenceCall, Forward, DND) are available for SIP phones offering a http/xml interface.

Bug fixes

• A memory leak in the web browser process is caused by TSWidget when used with multiple call appearances devices.
• Log files are not rolling anymore or unexpectedly and their size is increasing unexpectedly when the embedded database is enabled.

TelServer v1.6.0 changes

Enhancements

• Routing by skills is allowed on Routing point.
• Routing points can now be closed by the management (only outbound routing points can be closed)
• Routing points configuration now contains a timeout after which the routing point is automatically closed. This is applicable for outbound routing points only so that it is removed from TelServer even if the application does not close it properly.
• TelServices sessions can be opened with no immediate monitoring of the associated PBX device. If the PBX is able to notify TelServer that an agent logs on without requiring a MonitorStart, when not all agents are working at the same time, this feature allows to get a limited number of CTI licenses on the PBX. TelServer allows to open an unlimited number of sessions which become efficient only when the agent logs on. This requires a specific TelServer license.
• Introduction of the Flash connector in TSLib and TSWidget. This feature prevents the web application to bother with document.domain. However, the default behavior is with XHR (XmlHttpRequest), so moving to Flash requires an explicit change in the config file.
• WARNING: in configuration TSWidget-config.js or TSLib-config.js, the setting WIDGET_FOLDER has been renamed TELSERVICES_FOLDER.
• WARNING: the license files are no longer searched in the 'work' directory but in the directory from where TelServer has been launched (by default 'bin'). However, it is still searched in priority relatively to the environment variable "uniGone_HOME".

Bug fixes

• RouteRequest routing points have been correctly enabled to be used before the actual pilot/group distribution of an Alcatel-Lucent Omni PCX CCS.

TelServer v1.5.1 changes

Enhancements

• The "call by name" feature is available in TSWidget. It enables entering a name as well as a phone number to place a call.

Bug fixes

TelServer v1.5.0 changes

Enhancements

• Routing points support outbound campaigns.
• TSWidget/TSlib callback functions have been enhanced and the interface has been slightly modified, see upgrading TSWidget from v1.4 to v1.5 or upgrading TSLib from v1.4 to v1.5.
• History of calls is available through TelServices protocol. It is available in TSWidget.

Bug fixes

• TSLib TELSERVICES_TELSERVER_URL accepts the '-' character (this was leading to an error and the bridge was never loaded).

TelServer v1.4.5 changes

Enhancements

• TelServices Call structure contains 'firstCalledParty' and 'lastRedirectionParty' information providing information respectively about the initially called party and the last party transferring or redirecting the call. Note that the 'firstCalledParty' was provided in the CallInfo.extraData in the previous versions, the same information is now in Call.firstCalledParty.number.

Bug fixes

• If a TransferredEvent or a ConferencedEvent is the first event received, the associated TelServices event is never reported to the client. This may happen in situations when the transferred party is the target of a consultation call while it is busy, if the PBX provides the queueEvent after the TransferredEvent.
• TelServices durations are computed wrongly for busy trunks, when an outgoing call has not been answered, cleared by the busy trunk and tried again.
• AnswerCall within TelServicesCommand does not work when there are names provided in the 'alerting' event.

TelServer v1.4.4 changes

Enhancements

• A new setting telserver.TelServicesGateway.htdocs.direct_access.enabled allows to control whether direct HTTP access to the TelServices gateway is enabled.
• TelServices protocol provides the remaining timeout for the agent state in AgentInfo.

Bug fixes

TelServer v1.4.3 changes

Enhancements

Bug fixes

• Originated events for outbound calls in Asterisk provide correct called number.
• TelServices sessions opened for a non agent user (defined through TelServer directories) can still perform agent state functions. They are then handled directly by the PBX (the user must then be defined as a PBX agent).

TelServer v1.4.2 changes

Enhancements

• Agent states are available within the TelServices widget.
• Routing points can now take fully in charge the call distribution (using 'cyclic' or 'longest_rest' distributions).

Bug fixes

• CSTAp2 conversion to CSTAp3XML was not treating the extension alternative for MakeCallResult and ConsultationCallResult.
• Diversion in CSTAp3XML was not reporting the Diverted event on the calling device if the PBX did not report this event (this is not mandatory from a protocol point of view), this could cause the communication window stay longer than required within MOC.

TelServer v1.4.1 changes

Enhancements

• TelServer provides support for Cisco shared lines.
• Routing points configuration now contains no answer timeout and agent no answer timeout.

Bug fixes

• Some transfer calls (involving several call appearances) were leading the widget to provide the wrong call information.

TelServer v1.4.0 changes

Enhancements

• TelServer now supports Cisco JTAPI.
• The TelServices Javascript API has been enhanced. It also proposes a new TelServices widget (in place of the TelServices window).
• TelServices protocol have been enhanced and slightly modified :
  • several clients at a time can open a session per device number,
  • the 'conferenced' state has been replaced by the 'isConference' indicator allowing a simpler handling of that particular configuration (added parties numbers if available are fully provided),
  • the 'otherPartyNumber' and 'otherPartyName' have been replaced by a 'otherParty' structure containing more information,
  • the 'reference' in the Call structure has been replaced by the 'id' of the CallInfo (the reference of a call is still the other party number),
  • an event 'connected' with a cause 'heldByOtherParty' is received on a party that has been held by the other party,
  • an event 'connected' with a cause 'retrievedByOtherParty' is received on a party that has been retrieved by the other party,
  • 'permittedServices' have been added : this make the handling of an event easier since it sets all the permitted services that are available after that event, the application does not have to compute the permitted services itself.
• The CSTAp2 gateway have been added : it allows a CSTAp2 application to use TelServer as a proxy for non CSTA PBX, or as a proxy for demultiplexing data flows per device.
• The company directories can be used by TelServer.
• Routing points can be defined to authorize smart routing.

Bug fixes

• In the TelServices windows : using 'drop' after 'alternate' was always rejected because the TelServices window always pass the secondary number to the server.

TelServer v1.3.2 changes

Enhancements

• The configuration file can be passed through the command line.
• TelServices window : the functions TelServices_isWindowVisible and TelServices_showWindow manage the visibility of the TelServices window.
• Scripts to launch TelServer have been enhanced to handle start/stop as a service both on Windows and Unix.

Bug fixes

• TelServices window : the TelServices window can bother the user because it can stay in the middle of the page. Now, when the user scrolls so that the TelServices window is no more visible, then it will still be made visible but always be hooked in the top left angle of the page.

TelServer v1.3.1 changes

Enhancements

• TelServices interface : in the situation when E calls G who will transfer to A1, E is the initial calling device, G is the ACD which distributes the call to agent A1 with a transfer. The initial calling number E can be known before the actual transfer if the PBX link provides the information through correlator data for example. In the TelServices interface, the number is then provided in the 'otherPartyNumber' component of the Call event with a state 'alerting' or 'connected'. The addition of a new setting telserver.sessions.correlator_data_as_calling_device.enabled makes this possible.
  For example, in the CSTA phase I interface of the Alcatel OXO R6.0, for an ACD distribution, the CSTAPrivateData hold correlator data that provide the initial calling device in Delivered/Established events on the agent treating the call; the new setting makes it possible to report the initial calling device before the transfer.
• TelServices interface : the causes 'transfer/conference' have been added in the CallInfo cause component to indicate why a new event is emitted to the client.
• PBX properties : addition of PBX_ALCATEL_OMNI_PCX_ENTREPRISE (equivalent to PBX_ALCATEL_4400) and PBX_ERICSSON_AL (for the Ericsson Application Link).
• PBX properties : addition of a new setting to control the SnapshotDevice request after a MonitorStart, pbxlink.pbx.csta.snapshotDevice_at_monitorStart.enabled.

Bug fixes

• The TelServicesWindow is not updated with existing calls if any after an openSession. This happened because the mapping of the SnapshotDeviceResult in CSTAp1 to CSTAp2 when no extension is present was leading to an Asn1ValidationException. This bug happened on CSTA phase I PBX (e.g.Alcatel OXO - R6.0).
• When the TelServices HoldCall invites the user to enter a number (through a CSTA ServiceInitiated), it was not reflected in the TelServicesWindow. It is now possible to enter a number through TelServicesWindow, only the MakeSecCall and DropCall buttons being offered. This bug happened on Alcatel OXO - R6.0.
• Some external calls for which the dialing number is not provided and that are transfered are not shown on the TelServicesWindow of the party to which the call is transfered. The cause is that if a CSTAp1 TransferredEvent contains a connection with no static endpoint in the ConnectionList, an Asn1ValidationException is thrown for the mapped CSTAp2 event and the event is not fired to the upper layers. This bug happened on CSTA phase I PBX (e.g.Alcatel OXO - R6.0).
• Some messages/events are not reported to the client of TelServer. One cause is because the Asn1ValidationException is considered as a true Exception and not reported to the upper layer. Another cause is when an Asn1ValidationException occurs on a ROSE return to an invoke, the link does not provide an immediate error but actually returns after the timeout.
• Following a transfer, the incomingCall callback was not invoked within the transferred agent page.

TelServer v1.3.0 changes

Enhancements

• The TelServices Asn1API (built from the ASN.1 schema for the TelServices protocol) for Java and C# is included in the distribution. This can help developing a TelServices client application for TelServer. Examples are provided.
• A javascript library handling the TelServices protocol is available. It can be used to control the desktop phone from any HTML application (it is a pure Ajax library requiring no client installation except the browser).
• TelServices call events report the duration of the call (from start of call).
• TelServices 'snapshot' service allows to be answered upon change only. This permits an Ajax client to leave an open connection waiting for the next incoming call for instance (without being forced to poll the server). A timeout can be given to get an answer even if no change has occured.
• Some PBX settings have been renamed, it is recommended to modify them in your configuration file :
  • pbxlink.pbx.acse.enabled => pbxlink.pbx.csta.acse.enabled
  • pbxlink.pbx.cstaVersion => pbxlink.pbx.csta.version
  • pbxlink.pbx.csta_supported_services.default => pbxlink.pbx.csta.supportedServices.default
  • pbxlink.pbx.csta_supported_events.default => pbxlink.pbx.csta.supportedEvents.default

Bug fixes

• Many other issues have been addressed in this version.

TelServer v1.2.3 changes

Enhancements

• TelServices gateway also makes use of numbering rules if defined by the configuration. This allows the user client to provide numbers to the server without caring if they are PBX analyzable numbers.
• TelServices gateway accepts the 'POST' HTML method. It is preferrable to use POST rather than GET to make the browser not register the URL in its temporary cache.

Bug fixes

TelServer v1.2.2 changes

Enhancements

• Documentation has been improved with the addition the SIP/CSTAGateway guide (with examples for the Microsoft LiveCommunications Server) and TelServices guide.
• The new 'snapshot' service of the TelServices protocol allows the client to get a snapshot of the context within TelServer (calls, forward, doNotDisturb, msgWaiting and optionally agentState).

Bug fixes

TelServer v1.2.1 changes

Enhancements

• Mainly a refactoring version.

Bug fixes

TelServer v1.2.0 changes

Enhancements

• TelServer can link to a LDAP server so that TelServices can provide the name as well as the dialing numbers of involved parties.
• TelServices protocol includes "extraData" fields that can be provided in the CSTA CorrelatorData in MakeCall, ConsultationCall. Events report the CSTA correlatorData in the "extraData" field.

Bug fixes

TelServer v1.1.0 changes

Enhancements

• TelServer now supports a SIP+CSTAp3XML client such as Microsoft Live Communication Server. It is compliant with ECMA TR87.
• TelServices have been enhanced with addition of consultation, conference, divert, transfer services.

Bug fixes

TelServer v1.0.0 changes

• First version.