1304 - Add documentation for new call transfer

source/administrator/xivocc/install_and_config/phone_integration/index.rst

@@ -95,21 +95,24 @@ Known limitations
 
 Phone integration with Agent and Web / Desktop Assistant has these limitations:
 
-Transfer with Snom
-------------------
-
-- Transfer button in Agent / Assistant must be pressed twice to complete the transfer
-- If the second call was initiated from Agent / Assistant and the called user rejected the call, the first call will stay
-  hold until it is manually resumed
-
-Transfer with Yealink / Polycom
--------------------------------
+Transfer
+--------
 
+- If the second call was initiated from Agent / Assistant and the called user rejected the call, the first call will stay hold until it is manually resumed
 - If the second call was initiated from the phone, the transfer must be also completed from the phone. It can't be completed from Agent / Assistant.
-- If the second call was initiated from Agent / Assistant, the transfer should be completed from there. It is also possible
-  to complete it by hanging up the phone but not by using the transfer key.
+- You cannot complete a transfer initiated from the Agent / Assistant by hanging up.
+- WebRTC transfer is currently not working with this version.
+ 
+
 
 Conference with Yealink / Polycom
 ---------------------------------
 
 - Conference can't be created from Agent or Web / Desktop Assistant
+
+.. _disabling_ami_transfer:
+
+Disabling AMI transfer
+======================
+
+Since Polaris version, transfers are no longer done through the device capabilities or using DTMF but using AMI command to manage the device calls. If you want to revert to the old behavior you just need to set the ENABLE_AMI_TRANSFER to false in the docker custom.env file. Please check previous versions documentation for limitations.

source/releasenotes/polaris_iv.rst

@@ -102,7 +102,18 @@ Consult the `2017.11 Roadmap <https://projects.xivo.solutions/versions/53>`_ for
 **Xuc Server**
 
 * `#1393 <https://projects.xivo.solutions/issues/1393>`_ - Remove call stuck in CCManager after attended transfer
+* `#1363 <https://projects.xivo.solutions/issues/1363>`_ - Complete transfer using AMI
+* `#1304 <https://projects.xivo.solutions/issues/1363>`_ - Initiate second call for transfer using AMI
 
+  .. note::
+     
+    **Behavior change** :
+       * The attended transfer is no longer done through the device capabilities or using DTMF but using AMI command to manage the device calls.
+       * Snom devices required previously the user to complete the transfer twice to actually perform the transfer, this is no longer the case.
+       * WebRTC transfer is currently not working with this version.
+       * You cannot complete a transfer initiated from the Agent / Assistant by hanging up.
+
+    The old behavior can be enabled if needed, see :ref:`disabling_ami_transfer`
 
 2017.10
 =======