Commit ae5a1869 authored by Vojtech Sodoma's avatar Vojtech Sodoma

Merge branch 'Callisto.13' into 2019.05

parents 6edeb260 fae06be2
......@@ -76,89 +76,17 @@ automatically available in :ref:`CCmanager <ccmanager>` and new real time counte
| | |
+---------------------------------+---------------------------------+
.. _screen_popup:
Screen Popup
============
It is possible to display customer information in an external web application using Xivo :ref:`sheet <custom-call-form>` mecanism.
* :menuselection:`Services > CTI Server > Sheets > Models`:
* Tab *General Settings*: Give a name
* Tab *Sheet*: You must define a sheet with at least ``folderNumber`` and ``popupUrl`` fields set:
* ``folderNumber`` (MANDATORY)
* field type = ``text``
* It has to be defined. Can be calculated or use a default value not equal to "-"
* Note: You could leave "empty" using a whitespace (in hexadecimal: %20)
* ``popupUrl`` (MANDATORY)
* field type = ``text``
* The url to open when call arrives : i.e. http://mycrm.com/customerInfo?folder= the folder number will be automatically
appended at the end of the URL
* Additionally to the existing xivo variables, you can also use here the following variables(only available in Web Agent and Desktop Agent):
* ``{xuc-token}``: will be replaced by a token used for xuc websocket and rest api, for example ``http://mycrm.com/customerInfo?token={xuc-token}&folder=``
* ``{xuc-username}``: will be replaced by the username of the logged on user, for example ``http://mycrm.com/customerInfo?username={xuc-username}&folder=``
* ``multiTab`` (OPTIONAL)
* field type = ``text``
* set to the text ``true`` to open each popup in a new window.
* :menuselection:`Services > CTI Server > Sheets > Events`: Choose the right events for opening the URL (if you choose two events, url will opened twice etc.)
Example : Using the caller number to open a customer info web page
* Define ``folderNumber`` with any default value i.e. 123456
* Define ``popupUrl`` with a display value of http://mycrm.com/customerInfo?nb={xivo-calleridnum}&fn= when call arrives web page http://mycrm.com/customerInfo?nb=1050&fn=123456 will be displayed
.. figure:: example_xivo_sheet.png
:scale: 90%
.. _run_executable_sheet:
This section has been moved to :ref:`configuration section <screen_popup>`.
Run executable
==============
It is also possible to run an executable using Xivo :ref:`sheet <custom-call-form>` mecanism. This is only available in the desktop agent and desktop assistant.
* :menuselection:`Services > CTI Server > Sheets > Models`:
* Tab *General Settings*: Give a name
* Tab *Sheet*: You must define a sheet with at least ``runAsExecutable`` and ``popupUrl`` fields set:
* ``popupUrl`` (MANDATORY)
* field type = ``text``
* It should contain an executable name accessible by the client user (where the desktop application is) or a full executable path.
* ``runAsExecutable`` (MANDATORY)
* field type = ``text``
* Display value ``true``
* ``executableArgs`` (OPTIONAL)
* field type = ``text``
* set the argument for the executable.
* :menuselection:`Services > CTI Server > Sheets > Events`: Choose the right events for starting the application.
Example : Run the ``notify-send`` command on linux:
* Define ``popupUrl`` with a display value of ``notify-send``
* Define ``runAsExecutable`` with a display value of ``true``
* Define ``executableArgs`` with a display value of ``caller:{xivo-calleridnum}`` where the variable ``xivo-calleridnum`` will be replaced by the caller phone number.
.. figure:: example_xivo_sheet_exe.png
:scale: 90%
This section has been moved to :ref:`configuration section <run_executable_sheet>`.
.. _login_pause_funckeys:
......
......@@ -10,3 +10,137 @@ Disabling WebRTC
================
WebRTC can be disabled globally by setting the ``DISABLE_WEBRTC`` environment varibale to ``true`` in :file:`/etc/docker/compose/custom.env` file.
.. _screen_popup:
Screen Popup
============
It is possible to display customer information in an external web application using Xivo :ref:`sheet <custom-call-form>` mecanism.
* :menuselection:`Services > CTI Server > Sheets > Models`:
* Tab *General Settings*: Give a name
* Tab *Sheet*: You must define a sheet with at least ``folderNumber`` and ``popupUrl`` fields set:
* ``folderNumber`` (MANDATORY)
* field type = ``text``
* It has to be defined. Can be calculated or use a default value not equal to "-"
* Note: You could leave "empty" using a whitespace (in hexadecimal: %20)
* ``popupUrl`` (MANDATORY)
* field type = ``text``
* The url to open when call arrives : i.e. http://mycrm.com/customerInfo?folder= the folder number will be automatically
appended at the end of the URL
* Additionally to the existing xivo variables, you can also use here the following variables(only available in Web Agent and Desktop Agent):
* ``{xuc-token}``: will be replaced by a token used for xuc websocket and rest api, for example ``http://mycrm.com/customerInfo?token={xuc-token}&folder=``
* ``{xuc-username}``: will be replaced by the username of the logged on user, for example ``http://mycrm.com/customerInfo?username={xuc-username}&folder=``
* ``multiTab`` (OPTIONAL)
* field type = ``text``
* set to the text ``true`` to open each popup in a new window.
* :menuselection:`Services > CTI Server > Sheets > Events`: Choose the right events for opening the URL (if you choose two events, url will opened twice etc.)
Example : Using the caller number to open a customer info web page
* Define ``folderNumber`` with any default value i.e. 123456
* Define ``popupUrl`` with a display value of http://mycrm.com/customerInfo?nb={xivo-calleridnum}&fn= when call arrives web page http://mycrm.com/customerInfo?nb=1050&fn=123456 will be displayed
.. figure:: example_xivo_sheet.png
:scale: 90%
.. note::
* The default behaviour for the client sheet is to automatically open on CCagent and to not open on the UCassistant.
You can manage it to obtain behaviours that are different from the default ones.
To manage the client sheet on the CCagent and UCassistant, you can configure a variable in the webi and then add it on users or queues via a subroutine.
* :menuselection:`Services > IPBX > IPBX Configuration > configuration files > xivo-extrafeatures.conf`: In the file content box, add a variable::
[add-variable]
exten = s,1,NoOp(******************* Add variable *******************)
same = n,UserEvent(dialplan2cti,UNIQUEID: ${UNIQUEID},CHANNEL: ${CHANNEL},VARIABLE: popupagent,VALUE: "false")
same = n,UserEvent(dialplan2cti,UNIQUEID: ${UNIQUEID},CHANNEL: ${CHANNEL}, VARIABLE: popupassistant,VALUE: "true")
same = n,DumpChan()
same = n(return),Return()
* :menuselection:`Services > CTI Server > Sheets > Models`:
* Tab *Sheet*: You can add the following fields :
* ``popupAgentActivated`` (OPTIONAL)
* field type = ``text``
* display value = ``{dp-popupagent}``
* ``popupUCActivated`` (OPTIONAL)
* field type = ``text``
* display value = ``{dp-popupassistant}``
* Add the variable on a user or a queue via a subroutine : in the subroutine field type "add-variable" which is the name of the variable we set in the configuration.
.. warning:: The variable can be added in a subroutine on users or/and on queues, it cannot be added in a subroutine on agents.
Example :
I want my user U1 to have access to the client sheet when a customer calls on the UCassistant.
* :menuselection:`Services > IPBX > User > Edit user`: In the General tab, write "add-variable" in the subroutine field.
The popupUCActivated field is set to "true" in the configuration, so user U1 will receive the client sheet.
.. _run_executable_sheet:
Run executable
==============
It is also possible to run an executable using Xivo :ref:`sheet <custom-call-form>` mecanism. This is only available in the desktop agent and desktop assistant.
.. warning:: The executable will be run by default on the desktop Agent but not on the desktop Assistant.
To run an executable on the desktop Assistant, you need to set the popupassistant variable to true and add it in a subroutine on a user.
For more details about the configuration, see :ref:`configuration section <screen_popup>`
* :menuselection:`Services > CTI Server > Sheets > Models`:
* Tab *General Settings*: Give a name
* Tab *Sheet*: You must define a sheet with at least ``runAsExecutable`` and ``popupUrl`` fields set:
* ``popupUrl`` (MANDATORY)
* field type = ``text``
* It should contain an executable name accessible by the client user (where the desktop application is) or a full executable path.
* ``runAsExecutable`` (MANDATORY)
* field type = ``text``
* Display value ``true``
* ``executableArgs`` (OPTIONAL)
* field type = ``text``
* set the argument for the executable.
* :menuselection:`Services > CTI Server > Sheets > Events`: Choose the right events for starting the application.
Example : Run the ``notify-send`` command on linux:
* Define ``popupUrl`` with a display value of ``notify-send``
* Define ``runAsExecutable`` with a display value of ``true``
* Define ``executableArgs`` with a display value of ``caller:{xivo-calleridnum}`` where the variable ``xivo-calleridnum`` will be replaced by the caller phone number.
.. figure:: example_xivo_sheet_exe.png
:scale: 90%
......@@ -78,7 +78,7 @@ it executable::
And run it::
./xivo_install.sh -a 2018.16-latest
./xivo_install.sh -a 2019.05-latest
At the end of the installation, you can continue by running the :ref:`configuration
wizard. <configuration_wizard>`
......
......@@ -153,7 +153,7 @@ Recording purging is based on the statistic data, so the statistic data must not
Launch installation::
./xivocc_install.sh
./xivocc_install.sh -a 2019.05-latest
.. _after_install_xivocc:
......
......@@ -127,11 +127,11 @@ Table listing the current version of the components.
+======================+================+
| **XiVO** |
+----------------------+----------------+
| XiVO PBX | 2019.05.08 |
| XiVO PBX | 2019.05.13 |
+----------------------+----------------+
| config_mgt | 2019.05.08 |
+----------------------+----------------+
| db | 2019.05.09 |
| db | 2019.05.13 |
+----------------------+----------------+
| outcall | 2019.05.10 |
+----------------------+----------------+
......@@ -157,11 +157,62 @@ Table listing the current version of the components.
+----------------------+----------------+
| xivo-full-stats | 2019.05.00 |
+----------------------+----------------+
| xuc | 2019.05.12 |
| xuc | 2019.05.13 |
+----------------------+----------------+
| xucmgt | 2019.05.12 |
| xucmgt | 2019.05.13 |
+----------------------+----------------+
Callisto.13
-----------
Consult the `Callisto.13 Roadmap <https://projects.xivo.solutions/versions/166>`_.
Components updated: **xivo-confgend**, **xivo-config**, **xivo-dao**, **xivo-db**, **xivo-monitoring**,
**xivo-web-interface**, **xivocc-recording**, **xucmgt**, **xucserver**
**Desktop Assistant**
* `#2932 <https://projects.xivo.solutions/issues/2932>`_ - config.ini file is not kept when updating desktop app
.. important:: **Behavior change** Instead of being directly next to the executable file, the ini config file is now in a config directory, one folder higher.
Config file will be kept only when upgrading by automatic upgrade.
We now have a log file called log.log for electron related logs.
Doc : https://www.npmjs.com/package/electron-log
**Recording**
* `#2952 <https://projects.xivo.solutions/issues/2952>`_ - Recording of number not to be recorded is still recorded
**Web Assistant**
* `#2886 <https://projects.xivo.solutions/issues/2886>`_ - "Play audio" signal from keyboard or headset plays the xivo ringing sound
**XUC Server**
* `#2366 <https://projects.xivo.solutions/issues/2366>`_ - [C] - No error is displayed on login page when agent is already logged on another phone
* `#2912 <https://projects.xivo.solutions/issues/2912>`_ - [C] - Transfer completion may fail (all is hangup) if transfer completion is done while destination is ringing
* `#2921 <https://projects.xivo.solutions/issues/2921>`_ - Sheet event is taken into account on UC clients
.. important:: **Behavior change** The executable run by the sheet event will be run by default on the desktop Agent but not on the desktop Assistant.
To run an executable on the desktop Assistant, you need to set the popupassistant variable to true and add it in a subroutine on a user.
For more details consult the configuration section.
* `#2945 <https://projects.xivo.solutions/issues/2945>`_ - Phone status of other users is wrong in UC Assistant
* `#2956 <https://projects.xivo.solutions/issues/2956>`_ - MDS users don't see participants of a conference in UC Assistant
**XiVO PBX**
* `#2513 <https://projects.xivo.solutions/issues/2513>`_ - Source number is wrong when you call with UC Assistant from a MDS
* `#2737 <https://projects.xivo.solutions/issues/2737>`_ - Database: set synchronous_commit to off by default to enhance performance
* `#2874 <https://projects.xivo.solutions/issues/2874>`_ - Asterisk munin plugins don't work
* `#2883 <https://projects.xivo.solutions/issues/2883>`_ - [XiVO Phonebook] Phonebook numbers like +XX (E.164 format) should be allowed
* `#2936 <https://projects.xivo.solutions/issues/2936>`_ - Disabled incoming calls (DID) are still generated in the dialplan
Callisto.12
-----------
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment