Commit 170819e6 authored by Etienne Allovon's avatar Etienne Allovon

Add jmx page to a toc tree and fix heading order in troubleshooting section

parent 017a2567
#################
*****************
NGINX - proxy web
#################
*****************
Basic check
===========
......
*********
Reporting
=========
*********
xivo_replic does not replicate call data
----------------------------------------
========================================
After experiencing a 'no space left on device' and restarting containers, it can sometimes happen that the data from XiVO is not replicated anymore. Container *xivocc_replic_1* logs show the following error::
......
**********
PostgreSQL
==========
**********
Container keeps on restarting after upgrade
-------------------------------------------
===========================================
After upgrading Docker it can sometimes happen that the container *xivocc_pgxivocc_1* gets stuck in restarting mode. Logs show the following error
......
.. _troubleshooting:
***************
Troubleshooting
===============
***************
Transfers using DTMF
--------------------
====================
When transfering a call using DTMF (\*1) you get an *invalid extension* error when dialing the
extension.
......@@ -29,7 +30,7 @@ to be able to transfer the called person to another extension.
.. _fax-detection:
Fax detection
-------------
=============
XiVO **does not currently support Fax detection**. The following describe a workaround to use this
feature. The behavior is to answer all incoming (external) call, wait for a number of seconds (4 in
......@@ -77,7 +78,7 @@ this example) : if a fax is detected, receive it otherwise route the call normal
.. _berofos-integration-with-pbx:
Berofos Integration with PBX
----------------------------
============================
You can use a Berofos failover switch to secure the ISDN provider lines
when installing a XiVO in front of an existing PBX.
......@@ -161,7 +162,7 @@ The following describes how to configure your XiVO and your Berofos.
Upgrading from XiVO 1.2.3
--------------------------
==========================
#. There is an issue with ``xivo-libsccp`` and ``pf-xivo-base-config`` during an upgrade from 1.2.3::
......@@ -191,7 +192,7 @@ Upgrading from XiVO 1.2.3
.. _cti-ami-proxy:
CTI server is unexpectedly terminating
--------------------------------------
======================================
If you observes that your CTI server is sometimes unexpectedly terminating with the following
message in :file:`/var/log/xivo-ctid.log`::
......@@ -236,7 +237,7 @@ To disable the ami-proxy::
Agents receiving two ACD calls
------------------------------
==============================
.. warning:: Procedure was removed since bug was fixed in asterisk version shipped in 2017.LTS1 (2017.03)
......@@ -244,7 +245,7 @@ Agents receiving two ACD calls
.. _postgresql_localization_errors:
PostgreSQL localization errors
------------------------------
==============================
The database and the underlying `database cluster`_ used by XiVO is sensitive to the system locale
configuration. The locale used by the database and the database cluster is set when XiVO is
......@@ -269,7 +270,7 @@ When working with locale and PostgreSQL, there's a few useful commands and thing
Database cluster is not starting
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
--------------------------------
If the database cluster doesn't start and you have the following errors in your log file::
......@@ -292,7 +293,7 @@ Once this is done, restart your database cluster.
Can't connect to the database
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-----------------------------
If the database cluster is up but you get the following error when trying to connect to the
``asterisk`` database::
......@@ -310,13 +311,13 @@ two choices to fix this issue:
Error during the upgrade
^^^^^^^^^^^^^^^^^^^^^^^^
------------------------
Then you are mostly in one of the cases described above. Check your log file.
Error while restoring a database backup
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
---------------------------------------
If during a database restore, you get the following error::
......@@ -339,7 +340,7 @@ your system. You have two choices to fix this issue:
Error during master-slave replication
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-------------------------------------
Then the slave database is most likely not using an UTF-8 encoding. You'll need to
:ref:`recreate the database using a different locale <postgres-change-locale>`
......@@ -348,7 +349,7 @@ Then the slave database is most likely not using an UTF-8 encoding. You'll need
.. _postgres-change-locale:
Changing the locale (LC_COLLATE and LC_CTYPE) of the database
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-------------------------------------------------------------
If you have decided to change the locale of your database, you must:
......@@ -380,7 +381,7 @@ For more information, consult the `official documentation on PostgreSQL localiza
Originate a call from the Asterisk console
------------------------------------------
==========================================
It is sometimes useful to ring a phone from the asterisk console. For example, if you want
to call the ``1234`` extension in context ``default``::
......@@ -388,7 +389,7 @@ to call the ``1234`` extension in context ``default``::
channel originate Local/1234@default extension 42@xivo-callme
WebRTC
------
======
* `http.conf` - asterisk's webserver must accept connection from outside, the listen address must be updated, for the sake of
simplicity let's use 0.0.0.0, you can also pick an address of one of the network interfaces:
......
###################################
***********************************
Xuc & Xucmgt (CC & UC applications)
###################################
Basic checks
============
***********************************
XUC overview page
-----------------
=================
XUC overview page available at @XUC_IP:PORT, usually @SERVER_IP:8090. You have to check if the "Internal configuration cache database"
contains agents, queues etc.
XUC sample page
---------------
===============
XUC sample page available at @XUC_IP:PORT/sample, usually @SERVER_IP:8090/sample. You can use this page to check user login and other
API functions. CCManager, agent and assistant web use functions available on the sample page.
XUC Internal Metrics
--------------------
====================
Internal metrics are also available - see :ref:`xuc_jmx_metrics` page.
.. toctree::
:maxdepth: 2
:hidden:
Internal metrics are also available, see :ref:`xuc_jmx_metrics`
jmx
Agent states after XUC restart
------------------------------
==============================
Please see the note in :ref:`restarting <agent_states_after_xuc_restart>` XUC server with active calls.
.. _xuc_jmx_metrics:
####################
********************
XUC Internal Metrics
####################
********************
.. contents::
......
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