Commit d4d26822 authored by Stepan Kabele's avatar Stepan Kabele

1011 XCI Intended usage with diagram

parent ba924f20
*.dia binnary
...@@ -2,42 +2,80 @@ ...@@ -2,42 +2,80 @@
Intended usage Intended usage
************** **************
The XiVO Centralized Interface (XCI) is intended for specific use-case of multi-Xivo heterogeneous system. The XiVO Centralized Interface (XCI) is intended for specific use-case of centralized routing
and user management.
.. warning:: .. warning::
Using XCI for use-case different from the one described bellow is neither supported nor recommended. Using XCI for use-case different from the one described bellow is neither supported nor recommended.
Even if it works now, it may be broken in future version without warning. If XCI routing schema or centralized user management does not fit your use case, XCI is not good solution for your
telephony system. Using XCI for user management only is not recommended.
Non-standard installations may be broken by update to future version without warning.
-------
Routing
-------
Goals Routing support heterogeneous numbering plan administration:
=====
Heterogeneous numbering plan administration: * Centralized dialplan management.
* Route incoming and outgoing calls, independently of the entry point to the target telephony subsystem hosting this number.
* Simple configuration of dialplan richness (prefix, short numbers, numbers of different length, emergency calls, live destination modification).
* Protects against routing loops.
* Centralized dialplan management Routing is using concept of two layers:
* Route incoming and outgoing calls, independently of the entry point to the target telephony subsystem hosting this number
* Simple configuration of dialplan richness (prefix, short numbers, numbers of different length, emergency calls, live destination modification)
* Protect against routing loops **TODO is it already there?**
* Simplify user migration (lifetime DID for users) **TODO is it already there?**
Administration without knowledge of low-level telephony details: 1. "Logical" layer - users are routed using centralized database, with extensions correctly routed irrespective
to point of entry of call.
2. "Physical" layer - arbitrary connection (direct or indirect) via trunks is supported.
* Configure from point of view of organization administrator, not telephony technician Mapping between "Logical" and "Physical" layer is done by routing contexts. Every Xivo has routing context for every
* Present only relevant choices and options other Xivo (attached to trunk it will use). Routing context with the same name on different Xivo will be configured
* Avoid errors caused by multiple configuration points accordingly to the position of the Xivo in the network. This way you can adapt your physical layer to your network
* Users can be allowed to manage only part of the system topology. Intervals can overlap between Xivos, therefore logical structure of dialplan can be independent on
* Log all configuration changes for auditability physical location of users.
Routing .. image:: diagrams/XCI_routing.png
======= :align: center
See :ref:`xci_configuration_of_centralized_routing` for more configuration details.
Implementation of routing
=========================
When there is dial request on some Xivo and destination number is not found locally, AGI script in the dialplan requests
a route from the routing database and gets:
* A context used to process the call.
* Rules to update the destination number.
* Requests can be chained.
Fault tolerance:
* Local calls work, even when other network links and/or centralized user database are unreachable.
* Routing server can be setup in High Availability master-slave mode. When master routing server is down, routing
requests are automatically processed by slave.
Routing is using concept of two tiers: ---------------------------
Centralized user management
---------------------------
1. "Physical" tier - Routing between XiVOs based on contexts. User management allows centralized administration without knowledge of low-level telephony details:
2. "Logical" tier - Localization of users using centralized database.
**TODO image "How it works" from presentation** * Configuration is done from point of view of organization administrator, not telephony technician.
* User creation is simplified by line templates.
* Only relevant choices and options are presented.
* Extension number for new user is checked to be unique among all Xivos. Therefore you can use some extension range
for logical group, while creating its users on multiple Xivos.
* XCI accounts can be restricted to manage only part of the system.
* All configuration changes are logged for auditability.
Local calls work, even when other network links and/or centralized user database are unreachable. Compatability with configuration via Xivo WebUI:
* Users added by Xivo WebUI before adding Xivo to XCI are imported, but they not reachable by centralized routing.
* Combining user management by XCI and by Xivo WebUI is bad idea, which usually leads to misconfiguration.
* Managing users by XCI and call-center configuration (Queues, Agents) via Xivo WebUI is possible, but queue numbers
are not reachable by centralized routing.
* Configuring conference rooms via Xivo WebUI is possible, but conference room numbers are not reachable by centralized
routing.
\ No newline at end of file
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