System.conf

From Kolmisoft Wiki

(Difference between revisions)
Jump to: navigation, search
(MNP)
 
Line 48: Line 48:
=== MNP ===
=== MNP ===
 +
* '''mnp_enabled''' - Default 0. If 1, then MNP will be enabled in core.
* '''mnp_update_period''' - Default 120. How often to update MNP settings (DB configs, Prefixes)
* '''mnp_update_period''' - Default 120. How often to update MNP settings (DB configs, Prefixes)
* '''mnp_down_continue_call''' - Default 1. Should we continue call if MNP fails?
* '''mnp_down_continue_call''' - Default 1. Should we continue call if MNP fails?

Latest revision as of 05:46, 20 July 2021

This file is in /etc/m2/system.conf and describes some values for the M2/M4 systems.

Contents

[edit] Basic settings

  • dbname - MySQL database name
  • dbuser - MySQL database user
  • dbhost - MySQL database host
  • dbsecret - MySQL database password
  • dbport - MySQL database port
  • global_call_timeout - maximum length of call (default 7200 seconds)
  • balance_check_period – how often to recalculate total price for user's concurrent calls. The calculated price is compared with the user's balance and if the total price is lower than the balance limit, all user's calls will be terminated. The default value is 1 (in seconds)
  • active_calls_check_period – how often to update active calls. Default value is 5 (in seconds)
  • start_timeout - timeout between call initiation and answer/hangup. The default value is 240 seconds. If the call is not answered or hangup in this period of time, M2 will drop the call with 314 HGC.
  • stop_timeout - timeout between call answer and hangup. The default value is 7200 seconds. If the call is answered but the hangup is not received in this period of time, M2 will drop the call with 315 HGC.
  • server_id - current server id (should match Maintenance -> Servers)
  • billsec_round_function - how billsec should be rounded? Allowed values are ceil, round and floor. Ceil will round to higher value (1.1 will be rounded to 2), round will round to the closest value (1.4 will be rounded to 1 and 1.6 will be rounded to 2), floor will round to the lower value (1.9 will be rounded to 1). By default, ceil is used to round billsec.
  • mysql_ping - Default 0 (disabled). If the value is greater than 0, then M2 Core will periodically ping the MySQL server to keep connections alive. Value (in seconds) defines how often to ping MySQL server.
  • prefix_handle - controls which prefix is saved to the database (statistics depend on prefixes so this variable changes how statistics are presented). Accepted values are default, originator, terminator. The default value is default which tells the core to save the longest prefix from both Originator's and Terminator's tariffs. Value originator tells core to save prefix that was used from Originator's Tariff (statistics will be presented from Originator's perspective). Value terminator tells core to save prefix that was used from Terminator's Tariff (statistics will be presented from Terminator's perspective).
  • dial_peers_by_originator_prefix - Default 0. If 1, then Dial Peers will be searched by selected prefix from originator tariff. If 0, then Dial Peers are searched by the longest matching prefix.
  • invoice_generate_wait_time - how many hours system should wait before the Invoice is generated automatically. The default value is 6 hours. Acceptable values are 0 - 23. Since CDRs are created after the call ends, we need to wait sometime before generating an Invoice. For example, if the call starts at 23:55:00 and lasts more than 5 minutes, we cannot generate an invoice at midnight because this call will not be included in the Invoice. Wait time allows postponing Invoice generate event.
  • non_blocking_balance - Default 0. If > 0, then it activates the new balance update mechanics which updates the User's balance every X seconds, where X is the value of this setting. Eg. non_blocking_balance = 10, will update balances every 10s. Setting can help with high system load when Concurrent Calls > 4000 / CPS > 150. With a lower load on the server, this setting will not be useful.
  • disable_advanced_routing - Default 0. If 1 - the core will not calculate quality statistics for Quality Routing. Disable this option if you are not using Quality Routing.
  • connp_list_ttl - Default 30 (seconds). Determines how often to refresh the internal Connection Point cache (list).
  • show_entity_names - default 0. Shows entity names in the core log if enabled. Tariffs, DPs, TPs, OPs, RGs. Good for easier/faster troubleshooting. Slightly decreases core performance.

[edit] Radius Log

  • show_debug = default 0. If 0, then DEBUG messages will not be written in /var/log/radius/radiusd.log
  • show_notice = default 1. If 0, then NOTICEmessages will not be written in /var/log/radius/radiusd.log
  • show_warning = default 1. If 0, then WARNING messages will not be written in /var/log/radius/radiusd.log
  • show_error = default 1. If 0, then ERROR messages will not be written in /var/log/radius/radiusd.log
  • show_sql = default 0. If 1, then full SQLs will be written in /var/log/radius/radiusd.log (used in debug)
  • show_slow_sql = default 1. If 0, then slow SQLs will not be written in /var/log/radius/radiusd.log
  • no_uniqueid_in_log - Default 0. If 1, then no uniqueid will be written into radius.log. Used in development to save screen space.

[edit] CDR

  • cdr_batch_size – after call end, cdr is stored in a buffer and when that buffer is full, all CDRs are flushed to the database. This variable defines how many CDRs are buffered before flushing to the database. The default value is 30 (after 30 calls all CDRs will be flushed to the database). Max value is 100.
  • cdr_flush_time – cdr buffer is periodically flushed to database. This variable defines how often to flush cdr buffer to the database (value is in seconds). The default value is 60 seconds (after 60 seconds, all CDRs will be flushed to the database, no matter how many calls are buffered)
  • do_not_log_cached_cdrs - Default 1. If 1, then M2 will not log CDRs refused by the cache. This is the recommended setting because there is no need to write all the failed CDRs to DB when one is enough to identify the cause of call failure.
  • do_not_log_system_cdrs - Default 0. If 1, then M2 will not write FAILED CDRs with HGC >= 300. Use this option if you don't need such CDRs, it will slightly improve system performance.
  • do_not_log_failed_cdrs - Default 0. If 1, then M2 will not write FAILED CDRs to the database. Use this option if you don't need FAILED CDRs, it will slightly improve system performance.
  • log_only_last_cdr - Default 0. If 1, then M2 logs only the last CDR for the Call. M2 will not log failed attempts to terminators until the call goes over the last one. Only one CDR is logged for the call. It can be used to improve system performance.

[edit] HGC

  • enforced_global_hgc – set specific hangupcause for all failed, busy, and no answer calls. Only answered calls will return default 16 hangupcause. For example enforced_global_hgc = 34 will return 503 Service Unavailable to originator for all non answered calls.
  • reroute_stop_hgc - List of hangup cause codes (ISDN codes for M2, SIP codes for M4) that should stop rerouting through other terminators. If the terminator returns a code that is specified in the reroute_stop_hgc setting, the core will skip other terminators in the routing list. Multiple causes can be specified by separating them with comma separator, for example, reroute_stop_hgc = 1,2,3 (for M2) or reroute_stop_hgc = 408,500,603 (for M4)
  • change_failed_16_to - allows to change FAILED(16) hangupcause to another hangupcause, for example FAILED(34). Accepted values are between 1 and 127 (ISDN codes).

[edit] MNP

  • mnp_enabled - Default 0. If 1, then MNP will be enabled in core.
  • mnp_update_period - Default 120. How often to update MNP settings (DB configs, Prefixes)
  • mnp_down_continue_call - Default 1. Should we continue call if MNP fails?
  • mnp_timeout_count_before_hold - Default 3. How many timeouts should we receive before pausing MNP check
  • mnp_hold_time - Default 30. For how long should we stop MNP check after N timeouts
  • db_mnp_connections - How many MySQL connections will be created for MNP database. Default number of connections is the number of CPU core count
  • db_mnp_connections_timeout - Timeout for MNP database connections. Default 1 sec.


Make sure that format is:

variable = value

Note that there are spaces around = symbol


When settings are changed, core needs to be reloaded using the following command:

m2 reload
Personal tools

Try MOR

Try M2