This documentation relates to iSymphony 3.5. You can view older documentation on the Older Documentation page

Skip to end of metadata
Go to start of metadata

The following is a complete list of changes made between iSymphony 3.1.4 and iSymphony 3.2.0. If you are upgrading from iSymphony 3.0.x, please see the change log for iSymphony 3.1.4 as well.

Features

  • Added Support Asterisk 12 and 13
    • Added support for the new channel bridging mechanism used by Asterisk 12 and 13.
    • Added support for the new DialEnd and DialBegin AMI events.
    • Added support for the new ConfBridgeMute AMI event.
    • Added support for the new MusicOnHoldStart and MusicOnHoldStop AMI events.
    • Added support for the new QueueCallerJoin, QueueCallerLeave, and QueueMemberPause AMI events.
    • Added support for new properties in various other AMI actions and events.
  • Added support for the PJSIP channel driver
    • Users can now see the registration status of PJSIP endpoints.
    • Users can now see and control calls based on PJSIP channels.
    • Users can now toggle DND for a PJSIP endpoint.
  • A new open option (Always) has been added to the CRM Widget. When the CRM Widget is set to use this option, it will keep the specified URL open at all times.
  • A new Live API has been added to the REST interface, that provides realtime information concerning the state of the server, along with facilities to execute actions.
    • The server now accepts HTTP REST requests on the URL http://<ip or hostname of the server>:58080/communication_manager/rest/live.
    • The server now accepts HTTP REST requests on the URL https://<ip or hostname of the server>:55050/communication_manager/rest/live.
    • Resources for the following objects have been added to the REST interface:
      • Core Servers
      • Users
      • User Logins
      • User Status
      • Extensions
      • Queues
      • Agents
      • Calls
      • Statistics
    • Resources for the following actions have been added to the REST interface:
      • Setting the status of a user
      • Setting the DND state of an extension
      • Originating calls
      • Transferring calls
      • Logging agents in and out of queues
      • Pausing and Unpausing Agents
      • Setting the penalty of an agent
  • A new WebSocket Event API has been added, that provides realtime events concerning changes to the state of the server:
    • The server now accepts WebSocket connections on the URL path ws://<ip or hostname of the server>:58080/communication_manager/ws/event.
    • The server now accepts WebSocket connections on the URL path wss://<ip or hostname of the server>:55050/communication_manager/ws/event.
    • The ability to provide filters, specifying which events the WebSocket connection wants to receive, has been added.
    • The following events are now fired by the WebSocketEvent API:
      • Agent Login Event
      • Agent Logout Event
      • Agent Pause Event
      • Agent Unpause Event
      • Agent Statistic Event
      • Dial Begin Event
      • Dial End Event
      • DND Disable Event
      • DND Enable Event
      • Hangup Event
      • Link Begin Event
      • Link End Event
      • Queue Call Enter Event
      • Queue Call Leave Event
      • Queue Statistic Event
      • User Login Event
      • User Logout Event
      • User Status Event
  • Users can now check the version of the current iSymphony server installation by running the following command:

    service iSymphonyServerV3 version

Resolved Bugs

  • Resolved an issue where only one device state id would be processed when handling an ExtensionStatus event.
  • Resolved an issue where updates to an agent's last call time, and number of calls taken, would be delayed.
  • Resolved an issue where the max property of the queue would report the number of total calls seen by the queue, instead of the maximum number of calls allowed by the queue. 
  • Resolved an issue where some recording metadata would not appear in the Recording Widget, for extensions that are part of a FreePBX Find Me Follow Me configuration.
  • Resolved an issue that would cause the server.xml configuration file to get wiped out in some rare instances, preventing startup of the server.
  • Resolved an issue where the CDR database connection would cease to function after some time of inactivity, preventing recording metadata from populating properly.
  • Resolved an issue where call history items, with blank caller ID would be created, when listening to voicemail or recordings over the phone, or calling a queue, conference room, or parking lot directly.
  • Resolved an issue where the voicemail playback bar would not hide properly, when multiple voicemails were selected.
  • Resolved an issue that prevented some exception stack traces from being written to the log.
  • Resolved an issue where multiple CRM popups would open when a space was present in the URL.
  • Resolved an issue where the extension login button, above the Agent List in the Queue Widget, would still be visible if the user did not have permission to log agents into the currently selected queue.
  • Resolved an issue where an upgrade performed via the iSymphony Administration Interface or the install.sh script would fail, when the current JAVA_HOME path was not set to /usr/java/latest.
  • Resolved an issue that would cause client sessions to leak memory, eventually leading to OutOfMemoryErrors and server instability.
  • Resolved an issue that would sporadically prevent call state from appearing in the queue agent list.
  • Resolved an issue that could cause a deadlock situation in the communication event system, preventing the server from starting.

Improvements

  • The UNIQUEID variable is now available via the CRM widget, when using newer versions of Asterisk that do not report the UNIQUEID value as a channel variable over the AMI.
  • The startup scripts now verify the Java version before attempting to launch the server process. If the current installed version of Java  is not supported by the current iSymphony server installation, an error message will be displayed and the server startup will abort.
  • The client and administrator login forms now trim any whitespace surrounding the entered username and password.
  • The following URL variables have been added for use in the CRM Widget:
    • ${USER_ID}: Specifies the id of the current logged in user.
    • ${USER_LOGIN_ID}: Specifies the id of the user's current login session.
  • The following CRM Widget open options have been renamed:
    • Never -> On Demand
    • Ring -> On Ring
    • Answer -> On Answer

Performance Improvements

  • Performance of loading state from the Asterisk server, on startup or reload, has been slightly improved.

Regressions

  • Due to the new method of setting SIP headers for PJSIP endpoints, iSymphony will no longer auto answer any calls that are stolen from another extension, or transferred from a parking lot, if the destination of the call is a PJSIP endpoint. Auto answer, in these situations, will still fiction as before, if the endpoint is managed by the chan SIP driver. Auto answer, on origination from a PJSIP endpoint, will function correctly.
  • No labels