diff --git a/en/general.rst b/en/general.rst index 614149d..3cffa21 100644 --- a/en/general.rst +++ b/en/general.rst @@ -76,7 +76,7 @@ Routing - Capacity control for gateways, destinations, companies, accounts - Source and Destination number based Blacklisting and per number translation rules - Possibility to rewrite/modify caller-id, DNIS at the any routing stage -- Time-based routing +- :ref:`Time-based routing ` - Statistic and quality control for the each destination - Gateways grouping and load-balancing for cases when supplier provides several gateways for the termination - Possibility to silently reject unauthorized SIP INVITEs diff --git a/en/web-interface/equipment/gateways.rst b/en/web-interface/equipment/gateways.rst index 94d12ee..c1983cb 100644 --- a/en/web-interface/equipment/gateways.rst +++ b/en/web-interface/equipment/gateways.rst @@ -314,6 +314,22 @@ Dump Level Transport protocol Transport protocol that is used + + +SIP Schema + Specifies the URI schema used in the **Request-URI**, **From**, and **To** headers. + + **Possible values:** + + - **sip** — URI is built as ``sip:number@domain`` + - **sips** — URI is built as ``sips:number@domain`` + - **sip with user=phone** — URI is built as ``sip:number@domain;user=phone`` + + + .. seealso:: `RFC3966 `_, `RFC4967 `_ + + .. warning:: In Yeti, using the **sips** schema does **not** automatically enable any encryption mechanisms. It only affects the URI generation logic. + Host IP address or DNS name of remote gateway to send SIP signaling (only for termination). diff --git a/en/web-interface/system.rst b/en/web-interface/system.rst index 95bbf87..c14b819 100644 --- a/en/web-interface/system.rst +++ b/en/web-interface/system.rst @@ -26,5 +26,6 @@ YETI WEB interface - System menu description. This section describes general con system/networks_prefixes system/sensors system/smtp_connections + system/schedulers diff --git a/en/web-interface/system/jobs.rst b/en/web-interface/system/jobs.rst index 9c705b3..a8173fb 100644 --- a/en/web-interface/system/jobs.rst +++ b/en/web-interface/system/jobs.rst @@ -14,7 +14,7 @@ You could press "Run" link for execute some procedure or "Unlock" in case of som - **PartitionRemoving** - procedure of removing partitions of tables :ref:`CDR History `, :ref:`Auth logs `, :ref:`RTP Statistics ` and :ref:`API Logs `. Storage period for each table defined at regulated by configurations parameter **partition_remove_delay** at /opt/yeti-web/config/yeti_web.yml - - **CallsMonitoring** - procedure that is used for periodical (once per minute) calculation of cost for all active calls for each :ref:`Account ` and comparison their cost with current :ref:`Account Balance `. If account balance is less than cost of all active calls for the :ref:`Account ` all calls will be dropped by Yeti. This procedure also is used for calculating statistics for :ref:`Dushboard ` and :ref:`Active calls `; + - **CallsMonitoring** - procedure that is used for periodical (once per minute) calculation of cost for all active calls for each :ref:`Account ` and comparison their cost with current :ref:`Account Balance `. If account balance is less than cost of all active calls for the :ref:`Account ` all calls will be dropped by Yeti. This procedure also is used for calculating statistics for :ref:`Dashboard ` and :ref:`Active calls `; - **StatsClean** - procedure of removing statistics that are used for calculation of quality parameters (ACD, ASR and Short Calls) for :ref:`Gateways ` and :ref:`Dialpeers `; diff --git a/en/web-interface/system/scheduler.png b/en/web-interface/system/scheduler.png new file mode 100644 index 0000000..7baa63b Binary files /dev/null and b/en/web-interface/system/scheduler.png differ diff --git a/en/web-interface/system/schedulers.rst b/en/web-interface/system/schedulers.rst new file mode 100644 index 0000000..7d20b75 --- /dev/null +++ b/en/web-interface/system/schedulers.rst @@ -0,0 +1,57 @@ +.. _schedulers: + +========== +Schedulers +========== + +Schedulers provide an automatic mechanism to enable, disable, and toggle the **Reject Calls** flag in **Customer Auth**, **Destination**, **Dialpeer**, and **Gateway** objects. + + +Scheduler Fields +================ + +Id + Unique scheduler identifier. + +Name + User-friendly scheduler name. + +Enabled + Only enabled schedulers are processed by the system. + +Use Reject Calls + When enabled, the scheduler applies the **reject_calls** flag to **Customer Auth** and **Destination** objects to block traffic. + +Current State + The current operational state of the scheduler. The system automatically recalculates this state every 2 minutes. + +Timezone + The timezone that determines when the scheduler operates. + + +Ranges Configuration +==================== + +By default, a scheduler allows all traffic. To define when traffic should be blocked, create one or more **ranges**. Range Attributes: + +Months + Months during which blocking will be applied. An empty value means *any month*. + +Days + Days of the month when blocking will be applied. An empty value means *any day of the month*. + +Weekdays + Days of the week when blocking will be applied. An empty value means *any day of the week*. + +From Time + Start time of the blocking period. An empty value means *start of the day*. + +Till Time + End time of the blocking period. An empty value means *end of the day*. + + +.. figure:: scheduler.png + :alt: Example of a scheduler configuration + :align: center + + Example of Scheduler configuration.