These variables can be used in emails (both in Email Subject line and in Email Body):

===Every email===
''These variables are available for email templates, which are not listed on this page.''
* '''<%= server_ip %>''' - server IP where your users should register their SIP/IAX2 devices.
* '''<%= device_type %>''' - shows the user's primary device type. (The device is set as the primary device after user registration).
* '''<%= device_username %>''' - shows the user's primary device username. (The device is set as the primary device after user registration).
* '''<%= device_password %>''' - shows the user's primary device password. (The device is set as the primary device after user registration).
* '''<%= login_url %>''' - GUI login url.
* '''<%= login_username %>''' - user's username to login to GUI.
* '''<%= username %>''' - same as login_username.
* '''<%= first_name %>''' - first name of the user.
* '''<%= last_name %>''' - last name of the user.
* '''<%= full_name %>''' - first name and last name of the user.
* '''<%= balance %>''' - user's balance.
* '''<%= credit %>''' - user's credit. 
* '''<%= nice_balance %>''' - formated user's balance.
* '''<%= warning_email_balance %>''' - amount below which user should be warned with email.
* '''<%= nice_warning_email_balance %>''' - formated amount below which user should be warned with email.
* '''<%= currency %>''' - default system currency's short name (USD).
* '''<%= user_email %>''' - user's email address.
* '''<%= company_email %>''' - company email address.
* '''<%= email %>''' - company email address.
* '''<%= company %>''' - company title.
* '''<%= primary_device_pin %>''' - PIN of user's default device. The fault device is created the moment the user registers, so this variable can be used universally.
* '''<%= calldate %>''' - used only from api request [[MOR API email_send| email_send]].
* '''<%= source %>''' - used only from api request [[MOR API email_send| email_send]].
* '''<%= destination %>''' - used only from api request [[MOR API email_send| email_send]].
* '''<%= billsec %>''' - used only from api request [[MOR API email_send| email_send]].
* '''<%= balance_range_min %>''' - Balance range min. value set in User settings. M2 only.
* '''<%= balance_range_max %>''' - Balance range max. value set in User settings. M2 only.
* '''<%= warning_balance_admin_value %>''' - Warning balance Admin value set in User settings. M2 only.

===After registration===
''These variables are only available to email templates which are used to send emails after user's successful registration.''

* '''<%= login_password %>''' - user's password to login to GUI.
* '''<%= user_ip %>''' - user's IP address.

===Invoices===
''These variables are only available to [[Emails|invoices template]] which is used to [[Invoices#Send_invoices_by_email_.28manual.29|send Invoices]]''

* '''<%= invoice_price %>''' - price of Invoice.
* '''<%= invoice_price_with_tax %>''' - price of Invoice with Tax.
* '''<%= invoice_currency %>''' - Invoice currency.
* '''<%= invoice_period_start %>''' - Invoice period start.
* '''<%= invoice_period_end %>''' - Invoice period end.

===Cyberplat payment report===

* '''<%= currency %>''' - payment currency.
* '''<%= amount %>''' - payment amount.
* '''<%= date %>''' - payment date.
* '''<%= auth_code %>''' - authorization code.
* '''<%= transaction_id %>''' - payment transaction ID provided by Cyberplat.
* '''<%= customer_name %>''' - payment customer name provided by Cyberplat.
* '''<%= description %>''' - payment details provided by Cyberplat.

===Calling Card purchase ===

* '''<%= cc_purchase_details %>''' - cards list (Number, Pin, Price).

===Recordings===

Templates ''recording_new'' and ''recording_delete'' accept '''only''' these variables: 

* '''<%= calldate %>''' - Call date and time (when Call started).
* '''<%= source %>''' - Source number (number only, CallerID ''name'' included).
* '''<%= destination %>''' - Destination number.
* '''<%= billsec %>''' - Call duration.
* '''<%= full_name %>''' - first name and last name of the user.

===CDR Export===

Templates ''cdr_export_success'' and ''cdr_export_error'' accept '''only''' these variables: 

* '''<%= current_date %>''' - current date (when CDR Export was executed).
* '''<%= date_from %>''' - Date 'From', specified in Last Calls filter.
* '''<%= date_till %>''' - Date 'Till', specified in Last Calls filter.
* '''<%= archive_size %>''' - size of CDR archive (tgz).
* '''<%= search_user_username %>''' - username to login of the user who was selected in search filter.
* '''<%= search_user_fullname %>''' - first name and last name of the user who was selected in search filter.
* '''<%= search_reseller_username %>''' - username to login of the reseller who was selected in search filter.
* '''<%= search_reseller_fullname %>''' - first name and last name of the reseller who was selected in search filter.
* '''<%= search_device_description %>''' - description of the device which was selected in search filter.
* '''<%= search_device_username %>''' - username of the device which was selected in search filter.

===Provider Deviation Observers===
* '''<%= lcr_name %>''' - Observed LCR name.
* '''<%= lcr_id %>''' - Observed LCR id.
* '''<%= provider_name %>''' - Main Provider.
* '''<%= asr_deviation %>''' - tolerated ASR deviation.
* '''<%= acd_deviation %>''' - tolerated ACD deviation.
* '''<%= changed_providers %>''' - comma separated list of changed Privders in a Deviation Observer.

===Payment===
* '''<%= payment_id %>''' - Payment ID
* '''<%= payment_tax''' - Payment Tax
* '''<%= payment_gross %>''' - Payment Gross
* '''<%= payment_user %>''' - Payment User
* '''<%= payment_user_balance_before %>''' - User's balance before making payment
* '''<%= payment_user_balance_after %>''' - User's balance after making payment

===Statement of Account===
* '''<%= full_name %>''' - User Full Name
* '''<%= date %>''' - Email sending date

===Auto Aggregate Report===
* '''<%= auto_aggregate_export_from %>''' - Export from date
* '''<%= auto_aggregate_export_till %>''' - Export till date
* '''<%= auto_aggregate_export_template %>''' - Export template

===Automatic tariff import===
Please see [[Automatic_Tariff_Import#Notifications|here]].

===Two Factors authentication===
* '''<%= two_fa_code %>''' - two factors authentication code
* '''<%= user_edit_url %>''' - URL to users settings page
* '''<%= current_time %>''' - current date and time
* '''<%= two_fa_code_attempt %>''' - number of attempt
* '''<%= two_fa_login_status %>''' - login status
* '''<%= two_fa_login_ip %>''' - IP which tries to login

===Fax2email===
''Fax2email supports only these variables.''
* '''<%= first_name %>''' - first name of the user.
* '''<%= last_name %>''' - last name of the user.
* '''<%= full_name %>''' - first name and last name of the user.
* '''<%= source %>'''

 
 

=== Example ===
This template:
<pre>
Hello, <%=full_name%>
 
Your balance in MOR has fallen below <%= nice_warning_email_balance %> <%= currency %> and now is <%= nice_balance %> <%= currency %>.
 
Please login to <%= login_url %> and replenish it.
 
Yours sincerely,
 
KOLMISOFT
</pre>

will result in an email similar to this:

<pre>
Hello, John Smith

Your balance in MOR has fallen below 10.00 USD and now is 5.67 USD.
Please login to http://your_site/billing and replenish it.

Yours sincerely,
KOLMISOFT
</pre>

 

= Illegal usage =

You will get an error when you try to use non-existent variables.

Also, you cannot use something like this: <%= "www.kolmisoft.com" %>

 
= See also =
* [[Configuration from GUI#Emails | Email Configuration]]
* [[Emails|Mass Emails]]

Email variables

2026-04-08T07:33:47Z

Dmitrij: /* Fax2email */

Email variables

2026-04-08T07:32:41Z

Dmitrij:

These variables can be used in emails (both in Email Subject line and in Email Body):

===Every email===
* '''<%= server_ip %>''' - server IP where your users should register their SIP/IAX2 devices.
* '''<%= device_type %>''' - shows the user's primary device type. (The device is set as the primary device after user registration).
* '''<%= device_username %>''' - shows the user's primary device username. (The device is set as the primary device after user registration).
* '''<%= device_password %>''' - shows the user's primary device password. (The device is set as the primary device after user registration).
* '''<%= login_url %>''' - GUI login url.
* '''<%= login_username %>''' - user's username to login to GUI.
* '''<%= username %>''' - same as login_username.
* '''<%= first_name %>''' - first name of the user.
* '''<%= last_name %>''' - last name of the user.
* '''<%= full_name %>''' - first name and last name of the user.
* '''<%= balance %>''' - user's balance.
* '''<%= credit %>''' - user's credit. 
* '''<%= nice_balance %>''' - formated user's balance.
* '''<%= warning_email_balance %>''' - amount below which user should be warned with email.
* '''<%= nice_warning_email_balance %>''' - formated amount below which user should be warned with email.
* '''<%= currency %>''' - default system currency's short name (USD).
* '''<%= user_email %>''' - user's email address.
* '''<%= company_email %>''' - company email address.
* '''<%= email %>''' - company email address.
* '''<%= company %>''' - company title.
* '''<%= primary_device_pin %>''' - PIN of user's default device. The fault device is created the moment the user registers, so this variable can be used universally.
* '''<%= calldate %>''' - used only from api request [[MOR API email_send| email_send]].
* '''<%= source %>''' - used only from api request [[MOR API email_send| email_send]].
* '''<%= destination %>''' - used only from api request [[MOR API email_send| email_send]].
* '''<%= billsec %>''' - used only from api request [[MOR API email_send| email_send]].
* '''<%= balance_range_min %>''' - Balance range min. value set in User settings. M2 only.
* '''<%= balance_range_max %>''' - Balance range max. value set in User settings. M2 only.
* '''<%= warning_balance_admin_value %>''' - Warning balance Admin value set in User settings. M2 only.

===After registration===
''These variables are only available to email templates which are used to send emails after user's successful registration.''

* '''<%= login_password %>''' - user's password to login to GUI.
* '''<%= user_ip %>''' - user's IP address.

===Invoices===
''These variables are only available to [[Emails|invoices template]] which is used to [[Invoices#Send_invoices_by_email_.28manual.29|send Invoices]]''

* '''<%= invoice_price %>''' - price of Invoice.
* '''<%= invoice_price_with_tax %>''' - price of Invoice with Tax.
* '''<%= invoice_currency %>''' - Invoice currency.
* '''<%= invoice_period_start %>''' - Invoice period start.
* '''<%= invoice_period_end %>''' - Invoice period end.

===Cyberplat payment report===

* '''<%= currency %>''' - payment currency.
* '''<%= amount %>''' - payment amount.
* '''<%= date %>''' - payment date.
* '''<%= auth_code %>''' - authorization code.
* '''<%= transaction_id %>''' - payment transaction ID provided by Cyberplat.
* '''<%= customer_name %>''' - payment customer name provided by Cyberplat.
* '''<%= description %>''' - payment details provided by Cyberplat.

===Calling Card purchase ===

* '''<%= cc_purchase_details %>''' - cards list (Number, Pin, Price).

===Recordings===

Templates ''recording_new'' and ''recording_delete'' accept '''only''' these variables: 

* '''<%= calldate %>''' - Call date and time (when Call started).
* '''<%= source %>''' - Source number (number only, CallerID ''name'' included).
* '''<%= destination %>''' - Destination number.
* '''<%= billsec %>''' - Call duration.
* '''<%= full_name %>''' - first name and last name of the user.

===CDR Export===

Templates ''cdr_export_success'' and ''cdr_export_error'' accept '''only''' these variables: 

* '''<%= current_date %>''' - current date (when CDR Export was executed).
* '''<%= date_from %>''' - Date 'From', specified in Last Calls filter.
* '''<%= date_till %>''' - Date 'Till', specified in Last Calls filter.
* '''<%= archive_size %>''' - size of CDR archive (tgz).
* '''<%= search_user_username %>''' - username to login of the user who was selected in search filter.
* '''<%= search_user_fullname %>''' - first name and last name of the user who was selected in search filter.
* '''<%= search_reseller_username %>''' - username to login of the reseller who was selected in search filter.
* '''<%= search_reseller_fullname %>''' - first name and last name of the reseller who was selected in search filter.
* '''<%= search_device_description %>''' - description of the device which was selected in search filter.
* '''<%= search_device_username %>''' - username of the device which was selected in search filter.

===Provider Deviation Observers===
* '''<%= lcr_name %>''' - Observed LCR name.
* '''<%= lcr_id %>''' - Observed LCR id.
* '''<%= provider_name %>''' - Main Provider.
* '''<%= asr_deviation %>''' - tolerated ASR deviation.
* '''<%= acd_deviation %>''' - tolerated ACD deviation.
* '''<%= changed_providers %>''' - comma separated list of changed Privders in a Deviation Observer.

===Payment===
* '''<%= payment_id %>''' - Payment ID
* '''<%= payment_tax''' - Payment Tax
* '''<%= payment_gross %>''' - Payment Gross
* '''<%= payment_user %>''' - Payment User
* '''<%= payment_user_balance_before %>''' - User's balance before making payment
* '''<%= payment_user_balance_after %>''' - User's balance after making payment

===Statement of Account===
* '''<%= full_name %>''' - User Full Name
* '''<%= date %>''' - Email sending date

===Auto Aggregate Report===
* '''<%= auto_aggregate_export_from %>''' - Export from date
* '''<%= auto_aggregate_export_till %>''' - Export till date
* '''<%= auto_aggregate_export_template %>''' - Export template

===Automatic tariff import===
Please see [[Automatic_Tariff_Import#Notifications|here]].

===Two Factors authentication===
* '''<%= two_fa_code %>''' - two factors authentication code
* '''<%= user_edit_url %>''' - URL to users settings page
* '''<%= current_time %>''' - current date and time
* '''<%= two_fa_code_attempt %>''' - number of attempt
* '''<%= two_fa_login_status %>''' - login status
* '''<%= two_fa_login_ip %>''' - IP which tries to login

===Fax2email===
''These variables are only available for the fax2email template.''
* '''<%= first_name %>''' - first name of the user.
* '''<%= last_name %>''' - last name of the user.
* '''<%= full_name %>''' - first name and last name of the user.
* '''<%= source %>'''

 
 

=== Example ===
This template:
<pre>
Hello, <%=full_name%>
 
Your balance in MOR has fallen below <%= nice_warning_email_balance %> <%= currency %> and now is <%= nice_balance %> <%= currency %>.
 
Please login to <%= login_url %> and replenish it.
 
Yours sincerely,
 
KOLMISOFT
</pre>

will result in an email similar to this:

<pre>
Hello, John Smith

Your balance in MOR has fallen below 10.00 USD and now is 5.67 USD.
Please login to http://your_site/billing and replenish it.

Yours sincerely,
KOLMISOFT
</pre>

 

= Illegal usage =

You will get an error when you try to use non-existent variables.

Also, you cannot use something like this: <%= "www.kolmisoft.com" %>

 
= See also =
* [[Configuration from GUI#Emails | Email Configuration]]
* [[Emails|Mass Emails]]

Recommended hardware

2026-02-11T09:34:39Z

Dmitrij: /* Specifications */

== Specifications ==

Ensure the server is clean, with no unnecessary packages installed. For a single-server setup, we recommend:

{| border="1" cellpadding="5" cellspacing="0"
| '''Component''' || '''Minimum requirement (for testing)''' || '''Recommended (for production)''' || '''Comment'''
|-
| CPU || 4c/8t (four core, eight thread) Xeon || any higher CPU, at least 8 cores ||
|-
| RAM || 16 GB || 32 GB || 32/64 GB ||
|-
| HDD || 100 Gb SSD (Solid State Drives) all space must be assigned to / partition; 500+ GB for M4 || 500+ Gb, SSD (Solid State Drives)/NVM Express (NVMe), [http://en.wikipedia.org/wiki/RAID#RAID_1 RAID Type 1] all space must be assigned to / partition; || separated /boot partition is fine since it is small; do not create separated partitions for /home, /var and similar ||
|-
| OS || Rocky 9 minimal || Rocky 9 minimal || OS timezone must be set to UTC; language/locale should be default one (en_US)
|-
| NIC|| Any || '''M4''': Intel I210, I350, X550T (if you need over 700 concurrent calls) || Realtek RTL8111/8168/8411, Intel 82574L are weak NICs, not recommended
|-
| Brand|| Any || Intel, DELL, HP, Fujitsu ||
|}

 

== Requirements for specific elements in a multi-server deployment MOR ==

'''Asterisk/Core server:''' same requirements as above, except SSD would not increase performance so it is not needed and 4 GB of RAM is sufficient. CPU is most important component here. If Proxy solution is in use, Asterisks cannot be under NAT, it must have Public IP for SIP and RTP traffic. Must be located as close as possible to Database server to avoid problems caused by latency.

'''Database server:''' same requirements as above and SSD is highly recommended here. SSD is must if system has more than one Asterisk server. There should be 100GB or more space as database grows fast on high traffic. Fast data storage device and CPU are most important here. If more than one Database server is in use, UPS (Uninterruptible Power Supply) devices must be used for these servers, otherwise power outage would cause broken replication. 8Gb RAM minimum. Must be located as close as possible to Asterisk server to avoid problems caused by latency.

'''GUI server:''' same requirements as above.

'''Proxy server:''' same requirements as above, except 4 GB of RAM and 40 GB on HDD will be enough here. SSD would not increase performance. Proxy server cannot be under NAT, it must have Public IP for SIP traffic.
 

== Requirements for specific elements in a multi-server deployment M4 ==

'''DB/Core server:''' same requirements as above and SSD is a must. There should be 100GB or more space as the database grows fast on high traffic. It is recommended to start with at least 400GB on M4 systems. Fast data storage device and CPU are most important here. 16GB RAM minimum, 32GB for production.

'''GUI server:''' same requirements as above.

'''Proxy / B2BUA server:''' same requirements as above. Can have a smaller SSD. CPU is most important here.

'''Media server:''' same requirements as above. Can have a smaller SSD. CPU is most important here.
 
== Requirements for redundant deployment ==
Requirements for network to which servers are connected:
* Both servers should be within same subnet.
* Both servers should be able to ''broadcast'' packets to UDP 694 port.
* Both servers should be able to receive packets broadcasted by other server.
* There should be Virtual IP reserved in Subnet.
* Both servers should be able to work with that Virtual IP (only one server at same time).

If any of requirements above are not met, in some cases it is possible to adapt different network configurations or services (like "IP Failover").

In this case, you need to develop and manage special scripts or third-party software to achieve this (Kolmisoft does not provide this service).

 

== Virtualization ==

Our system was tested and working on the following Virtualization technologies:
* Proxmox
* VMware
* VirtualBox
* XEN
* AWS
* Azure

In general, we do not recommend using Virtual machines for multi-server solutions when those Virtual machines are running on the same host.

Best multi-server system performance is achieved when running on Dedicated servers or on Virtual machines running on dedicated servers.

 

== FAQ ==

* '''Do you have the provision of STUN and TURN servers on your end?'''

No, we do not provide STUN servers. MOR should receive Public IPs on SIP headers. NAT traversal should be done on the customer's side.

* '''Can I have redundancy between two data centers?'''

There's always a risk that the data center in which you keep your servers can be down for various reasons.

To reduce such risk, you can consider redundancy between two data centers located in different countries or continents.

Such implementation can work only if both data centers meet the requirements described [[Recommended_hardware#Requirements_for_redundant_deployment | here]].

However, we do not recommend this because of the following reasons:

1. Different data centers cannot ensure the same subnet for servers, so you must use VPN which is difficult to manage or DNS.

2. MySQL replication requires a stable connection. If replication fails, you will have a "split-brain" scenario and it will not be possible to fix this without losing calls and billing information.

 

= See also =

* [[How fast MOR can perform]]
* [[Check server compatibility]]

Pilot Project

2026-02-10T09:27:28Z

Dmitrij: /* STEP 2 – Preparing Your Server & Getting Login Credentials */

A Pilot Project is an advanced way to test the fully functional Kolmisoft system for one month in a live environment. It includes:
* On-premise or hosted installation
* Fully functional system
* Technical support
* Private training session via Zoom
 
== STEP 1 – Defining Your Goals ==

To get started, please answer the following questions:

* Do you want to use our server or your own?
* What are your main goals for the Pilot Project? Please be as specific as possible so we can align with your expectations.
* If we successfully meet your goals, what will be your next step after the Pilot Project?
* Which default currency would you like to set in the system?

 

== STEP 2 – Preparing Your Server & Getting Login Credentials ==

If you choose to use:
* Kolmisoft's server – No action is needed.
* Your own server – Please prepare it according to our [[Installation|installation instructions]].

Installation is typically completed within 8 hours (during working time) after the server is received.

Once the system is ready, you will receive an email from noreply@kolmisoft.com with the login details.

 

== STEP 3 – Configuration & Support ==

=== Getting Started ===
Follow one of these guides to begin:
* '''MOR''' [[How_to_make_first_call|How to make a first call]]
* '''MOR''' [[Usual_configuration_sequence|Usual configuration sequence]]
* '''M4''' [[M4_How_to_make_first_call|How to make a first call]]
 
=== Documentation ===

To set up the system according to your predefined goals, refer to our documentation:
* [[MOR_Manual|MOR manual]]
* [[M4_Switch_Manual|M4 manual]]

For specific questions, use the '''search function''' in the left menu bar of https://wiki.kolmisoft.com/.

 

=== Private Training ===

All Pilot Project users can receive a private training session via Zoom.

 
=== Technical Support ===

Whenever you encounter difficulties or have questions, please create a ticket in the Support System and our team will assist you.

* '''Working Hours''': Monday to Friday, 8 AM - 6 PM EET (Eastern European Time) UTC/GMT +2 hours.
* '''Emergency Support (BLOCKER priority tickets)''': Available 24/7 via the [https://support.kolmisoft.com/ Kolmisoft Support System].
 
More information about Kolmisoft Support System:
* [[Support_System_explanation|Support System Overview]]
* [[Create_new_Ticket_in_Ticket_System|How to Create a New Ticket]]
* [[Write_comment_to_the_Ticket|How to Write a Comment]]
* [[Support|Support Plans & Working Hours]]
 
Why use Kolmisoft Support System?
* Keeps issues organized
* Ensures faster and more efficient assistance
* Enables tracking and monitoring of response times

 

== STEP 4 – Evaluating Results ==

Before the end of the Pilot Project, we will review the results to determine its success.
* '''If successful''', we will propose next steps to continue working together.
* '''If unsuccessful''', we will analyze the core challenges and look for ways to improve our service.

 

== STEP 5 – Moving Forward After a Successful Pilot Project ==

If the Pilot Project meets your expectations and you wish to continue working with Kolmisoft, you can become our client. You will have the option to either:
* Retain the same server used during the Pilot Project.
* Migrate to a new server for continued operations.
 
If you have any questions, feel free to reach out via email or Kolmisoft Support System. We look forward to working with you!

Pilot Project

2026-02-10T09:26:45Z

Dmitrij: /* STEP 2 – Preparing Your Server & Getting Login Credentials */

A Pilot Project is an advanced way to test the fully functional Kolmisoft system for one month in a live environment. It includes:
* On-premise or hosted installation
* Fully functional system
* Technical support
* Private training session via Zoom
 
== STEP 1 – Defining Your Goals ==

To get started, please answer the following questions:

* Do you want to use our server or your own?
* What are your main goals for the Pilot Project? Please be as specific as possible so we can align with your expectations.
* If we successfully meet your goals, what will be your next step after the Pilot Project?
* Which default currency would you like to set in the system?

 

== STEP 2 – Preparing Your Server & Getting Login Credentials ==

If you choose to use:
* Kolmisoft's server – No action is needed.
* Your own server – Please prepare it according to our [[Installation|installation instructions]].

Installation is typically completed within 8 hours (during working time) after the server is received.

Once the system is ready, you will receive an email from noreply@kolmisoft.com with the text: '''COMMENT HIDDEN IN EMAIL'''.

Login details are sent via email.

 

== STEP 3 – Configuration & Support ==

=== Getting Started ===
Follow one of these guides to begin:
* '''MOR''' [[How_to_make_first_call|How to make a first call]]
* '''MOR''' [[Usual_configuration_sequence|Usual configuration sequence]]
* '''M4''' [[M4_How_to_make_first_call|How to make a first call]]
 
=== Documentation ===

To set up the system according to your predefined goals, refer to our documentation:
* [[MOR_Manual|MOR manual]]
* [[M4_Switch_Manual|M4 manual]]

For specific questions, use the '''search function''' in the left menu bar of https://wiki.kolmisoft.com/.

 

=== Private Training ===

All Pilot Project users can receive a private training session via Zoom.

 
=== Technical Support ===

Whenever you encounter difficulties or have questions, please create a ticket in the Support System and our team will assist you.

* '''Working Hours''': Monday to Friday, 8 AM - 6 PM EET (Eastern European Time) UTC/GMT +2 hours.
* '''Emergency Support (BLOCKER priority tickets)''': Available 24/7 via the [https://support.kolmisoft.com/ Kolmisoft Support System].
 
More information about Kolmisoft Support System:
* [[Support_System_explanation|Support System Overview]]
* [[Create_new_Ticket_in_Ticket_System|How to Create a New Ticket]]
* [[Write_comment_to_the_Ticket|How to Write a Comment]]
* [[Support|Support Plans & Working Hours]]
 
Why use Kolmisoft Support System?
* Keeps issues organized
* Ensures faster and more efficient assistance
* Enables tracking and monitoring of response times

 

== STEP 4 – Evaluating Results ==

Before the end of the Pilot Project, we will review the results to determine its success.
* '''If successful''', we will propose next steps to continue working together.
* '''If unsuccessful''', we will analyze the core challenges and look for ways to improve our service.

 

== STEP 5 – Moving Forward After a Successful Pilot Project ==

If the Pilot Project meets your expectations and you wish to continue working with Kolmisoft, you can become our client. You will have the option to either:
* Retain the same server used during the Pilot Project.
* Migrate to a new server for continued operations.
 
If you have any questions, feel free to reach out via email or Kolmisoft Support System. We look forward to working with you!

Responsible Accountant

2026-02-05T07:59:23Z

Dmitrij: /* Monitoring */

=Description=

Responsible Accountant is an [[Users#User_types |Accountant]] who can be assigned either to specific User(s) and/or Provider(s).
 
==User's Responsible Accountant==

A Responsible Accountant can be assigned for the User in the [[User Details|User Settings]] page, General block. After the Accountant is assigned to the User as the Responsible Accountant, he can:

* Get [[Warning balance]] email which informs about the Users' critical Balance.
 

When the "Show only assigned Users:" setting is checked in the Accountant edit form, that Accountant will be able to see just those Users whom he is assigned as the Responsible Accountant. That means that Users who are assigned to other Accountants or not assigned at all, will not be shown in the Accountants' GUI. Pages that will be affected are:
* [[Active Calls]]
* [[Provider Active Calls]]
* [[Action log]]
* [[Archived calls | Archived Calls]]
* [[Aggregate]]
* [[Invoices]]
* [[Last Calls]]
* [[Payments]]
* [[User Details]]
* [[Users Calls]]
* [[Country Stats]]
* [[Loss Making Calls]]
* [[Calls per Day]]
* [[Calls per Hour]]
* System Stats
* Hangup Cause
* [[Profit Stats]]
* [[Graphs]]
* Faxes
 
'''NOTE''' Responsible Accountant can be assigned only for Admin users - Reseller, Partner and simple User.
 


==Provider's Responsible Accountant==
Responsible Accountant can be assigned for Provider in [[Providers#General|Provider Settings]] page, General block. When the "Show only assigned Providers:" setting is checked in the Accountant edit form, that Accountant will be able to see just those Providers to which he is assigned as the Responsible Accountant. That means that Providers that are assigned to other Accountants or not assigned at all, will not be shown in the Accountants' GUI. Pages which will be affected are:

* [[Providers]]
* [[Provider Active Calls]]
* [[Quick Providers changes]]
* [[Providers Statistics]]
* [[Active Calls]]
* [[Aggregate]]
* [[Archived calls]]
* [[Calls per Day]]
* [[Calls per Hour]]
* [[DID Management|DIDs]]
* [[DIDs Stats]]
* DIDs Summary
* Hangup Cause Stats
* [[LCR]] - Providers will be shown but without real names.
* [[Last Calls]]
* [[Local Calls]]
* [[Simultaneous Calls stats|Load Stats]]
 

==Accountant Settings==
 
[[File:Accountant settings.png]]
 
===General===

*'''Username''' - username for the Accountant to log in to MOR GUI.
*'''Password''' - password for the Accountant to log in to MOR GUI. Password must contain at least one numeric value, a capital, and a lowercase symbol. Note: To use simple passwords, turn off the setting in the Security section called Use strong passwords for users.
*'''User Type''' - User Type is Accountant. Here it is possible to choose Permission group for the accountant.
*'''Default Currency''' - currency which will be used to show balance, rates, and prices in Users' GUI and exported files. Notice that balance (also other values) will be saved in default system currency in DB and converted on the fly using current exchange rate - e.g. balance can change when exchange rate changes. So your user can be surprised when he does not make calls but balance fluctuates.
*'''Time Zone''' - time zone which will be used to show dates and time in Users' GUI and exported files.
*'''Show only assigned Users''' - setting allows to show calls and other data only of assigned users.
*'''Show only assigned Providers''' - setting allows to show calls and other data only of assigned providers.
*''' Show Price in Last Calls''' - allow to show prices in the Last Calls.

===Blocking===

Various options for [[User Blocking]].

===Monitoring===
*'''ChanSpy Device'''- Allows listening calls.

More information here: [https://wiki.kolmisoft.com/index.php/Spy_real-time_calls Spy real-time calls]

===Warning Balance===

*'''Warning Balance Email''' - email that should receive warning balance notifications.

More details: [[Warning balance]]

===Details===

Self-explanatory.

===Comment===

Here you are able to write private comment about user.

=See Also=

* [[Accountant permissions]]

Responsible Accountant

2026-02-05T07:56:38Z

Dmitrij:

=Description=

Responsible Accountant is an [[Users#User_types |Accountant]] who can be assigned either to specific User(s) and/or Provider(s).
 
==User's Responsible Accountant==

A Responsible Accountant can be assigned for the User in the [[User Details|User Settings]] page, General block. After the Accountant is assigned to the User as the Responsible Accountant, he can:

* Get [[Warning balance]] email which informs about the Users' critical Balance.
 

When the "Show only assigned Users:" setting is checked in the Accountant edit form, that Accountant will be able to see just those Users whom he is assigned as the Responsible Accountant. That means that Users who are assigned to other Accountants or not assigned at all, will not be shown in the Accountants' GUI. Pages that will be affected are:
* [[Active Calls]]
* [[Provider Active Calls]]
* [[Action log]]
* [[Archived calls | Archived Calls]]
* [[Aggregate]]
* [[Invoices]]
* [[Last Calls]]
* [[Payments]]
* [[User Details]]
* [[Users Calls]]
* [[Country Stats]]
* [[Loss Making Calls]]
* [[Calls per Day]]
* [[Calls per Hour]]
* System Stats
* Hangup Cause
* [[Profit Stats]]
* [[Graphs]]
* Faxes
 
'''NOTE''' Responsible Accountant can be assigned only for Admin users - Reseller, Partner and simple User.
 


==Provider's Responsible Accountant==
Responsible Accountant can be assigned for Provider in [[Providers#General|Provider Settings]] page, General block. When the "Show only assigned Providers:" setting is checked in the Accountant edit form, that Accountant will be able to see just those Providers to which he is assigned as the Responsible Accountant. That means that Providers that are assigned to other Accountants or not assigned at all, will not be shown in the Accountants' GUI. Pages which will be affected are:

* [[Providers]]
* [[Provider Active Calls]]
* [[Quick Providers changes]]
* [[Providers Statistics]]
* [[Active Calls]]
* [[Aggregate]]
* [[Archived calls]]
* [[Calls per Day]]
* [[Calls per Hour]]
* [[DID Management|DIDs]]
* [[DIDs Stats]]
* DIDs Summary
* Hangup Cause Stats
* [[LCR]] - Providers will be shown but without real names.
* [[Last Calls]]
* [[Local Calls]]
* [[Simultaneous Calls stats|Load Stats]]
 

==Accountant Settings==
 
[[File:Accountant settings.png]]
 
===General===

*'''Username''' - username for the Accountant to log in to MOR GUI.
*'''Password''' - password for the Accountant to log in to MOR GUI. Password must contain at least one numeric value, a capital, and a lowercase symbol. Note: To use simple passwords, turn off the setting in the Security section called Use strong passwords for users.
*'''User Type''' - User Type is Accountant. Here it is possible to choose Permission group for the accountant.
*'''Default Currency''' - currency which will be used to show balance, rates, and prices in Users' GUI and exported files. Notice that balance (also other values) will be saved in default system currency in DB and converted on the fly using current exchange rate - e.g. balance can change when exchange rate changes. So your user can be surprised when he does not make calls but balance fluctuates.
*'''Time Zone''' - time zone which will be used to show dates and time in Users' GUI and exported files.
*'''Show only assigned Users''' - setting allows to show calls and other data only of assigned users.
*'''Show only assigned Providers''' - setting allows to show calls and other data only of assigned providers.
*''' Show Price in Last Calls''' - allow to show prices in the Last Calls.

===Blocking===

Various options for [[User Blocking]].

===Monitoring===
*'''ChanSpy Device'''- Allows listening calls.

More information here: [Spy_real-time_calls]

===Warning Balance===

*'''Warning Balance Email''' - email that should receive warning balance notifications.

More details: [[Warning balance]]

===Details===

Self-explanatory.

===Comment===

Here you are able to write private comment about user.

=See Also=

* [[Accountant permissions]]

2025-06-11T12:13:11Z

Dmitrij: /* Where to find PayPal? */

= WARNING =
[[Image:warning.png|right|250px]]

<center><big><big>

VERY IMPORTANT WARNING! PAYPAL is DANGEROUS to use!

</big></big></center>
 
<big>

You can lose money using PayPal because of the way PayPal works.

# The user can pay you.
# He can make calls.
# '''He can then REFUND his money back from your account'''.

'''IMPORTANT!''' PayPal will not cover your loss, because they classify it as: "Seller Protection - Ineligible".

Only allow PayPal payments for users you trust.
</big>

 
=About=
[https://www.paypal.com/lt PayPal] is a popular payment gateway which allows you to collect money from your clients. Clients are not required to have a PayPal account to pay you. They can pay with their credit/debit card (Visa, MasterCard, American Express, and Discover) — all without having a PayPal account (you need a PayPal PRO account and MOR [[Payment_Gateway_Addon|Payment Gateway Addon]] to enable your users to pay without a PayPal account). More information is available [https://www.paypal.com/cgi-bin/webscr?cmd=xpt/Marketing_CommandDriven/merchant/wpstandard/WPStandardFAQsBFTwo-outside here].

 
==Where to find PayPal?==

1. Navigate to '''ADDONS -> Payment gateways -> Payments''':
 
[[File:payments_path.png]]
 
2. Select the PayPal tab:
 
[[File:paypal11.png]]
 
* '''Enabled''' - enable or disable PayPal payments on your system.
* '''Test''' - enable or disable test mode.
* '''Paypal Client ID''' - Paypal client ID (provided by Paypal).
* '''Secret PayPal Key''' - key to verify transactions (provided by PayPal).
* '''Currency''' - default currency for payments via PayPal.
* '''Default amount''' - default amount.
* '''Minimal amount''' - minimal amount of money the user is allowed to transfer you.
* '''Maximum amount''' - maximum amount of money the user is allowed to transfer you.
* '''Disable PayPal for resellers''' - enable or disable PayPal for resellers.
* '''User pays transfer fee''' - if selected, transfer fee will be deducted from initial payment made by User before charging MOR fees.
* '''Payment confirmation by you''' - allows you to confirm received payments. If payment is not confirmed - it is not added to user balance.
* '''Notify by email''' - enable/disable notifications about new payments.

'''NOTE:''' There is related option '''Hide payment options for postpaid users''' in SETTINGS > Setup > Settings > Visual. It hides payment options for postpaid users. Set it to suit your needs.

'''NOTE:''' Make sure you also set your company name correctly since it will be used in PayPal's invoices (see: [[Global_Settings|Global Settings]])
 

== Detailed warning example ==

# A User is prepaid, and his balance is 0.
# User makes payment #1 for 100USD. His balance becomes 100USD.
# User makes payment #2 for 200USD. His balance becomes 300USD (100 + 200).
# User makes calls for 300USD. His balance decreases to 0 USD. The system does not allow him to make any more calls.
# User goes to PayPal and issues refund for payment #1. PayPal refunds his money back to him, and alerts MOR about this transaction. MOR subtracts 100USD from the user's balance. User balance becomes -100 USD ( 0 - 100).
# User goes to PayPal and issues refund for payment #2. PayPal refunds his money back to him, and alerts MOR about this transaction. MOR subtracts 200USD from the user's balance. User balance becomes -300 USD ( -100 - 200).
# In the end, you suffer a loss totalling -300 USD. The user in the system stays prepaid and his balance = -300 USD.

 

----
 

= Details =

A user can pay for services or increase his balance using PayPal. MOR is fully integrated into PayPal and does not need any manual intervention from an
administrator.

All PayPal options can be set in the Configuration menu of the PayPal section.

The PayPal payment option can be reached by clicking on the PayPal picture in the main entry window:

[[Image:paypal_logo.gif]]

When the user clicks on this image, he will be able to enter the amount he wishes to pay:

[[Image:paypal1.png]]

Note the minimum value which can be set in Configuration menu. If the user enters a lower value, he will not be able to proceed.

After clicking on '''Confirm''', he gets another window which shows him how much he will pay:

[[Image:paypal2.png]]

After pressing on Pay, he goes to the PayPal webpage, where he enters his account details and confirm the transfer.

After PayPal completes the transfer, the user gets back to the MOR interface. Now, under his payments he will see a PayPal payment with a Status regarding his payment.

There are many reasons why a PayPal payment may not be completed. To make these reasons clear, all this information is presented on the Payments page.

Some possible reasons for a PayPal payment not being completed:

* '''echeck''': The payment is pending because it was made by an eCheck that has not yet cleared.
* '''intl''': The payment is pending because the seller holds a non-U.S. account and does not have a withdrawal mechanism. Seller must manually accept or deny this payment.
* '''multi-currency''': Seller does not have a balance in the currency sent. Seller must manually accept or deny this payment.
* '''unilateral''': The payment is pending because it was made to an email address that is not yet registered or confirmed.
* '''upgrade''': The payment is pending because it was made via a credit card and seller must upgrade his account to Business or Premier status in order to receive the funds.
* '''verify''': The payment is pending because seller is not yet verified. Seller must verify his account before he can accept this payment.
* '''other''': The payment is pending for a reason other than those listed above. For more information, contact PayPal Customer Service.
* '''Denied''': Seller refused to accept this payment.

When payment is completed, the user's balance will increase by the value (without TAX) he paid by PayPal.

This integration makes possible a fully autonomous system in which a user can register online, pay using PayPal, configure his device and dial instantly WITHOUT any intervention from the system administrator.

ATTENTION – for PayPal to work, your server should have a real IP and should be reachable from the internet.

=== Resellers ===

Each Reseller can enter his own PayPal settings.

If you change PayPal as System Administrator, the new Reseller will have same the PayPal address upon creation. He is able to change this address later.

----

Question:

What kind of PayPal account is needed to interwork with MOR?
Paypal offers two account types: a Business Account and a Web Account.

Answer:

Both types appear to work with MOR. I can verify that a business account works 100%.
You can create a Web account and try it with MOR. If it doesn't work, it can be upgraded free to a Business account.

----

= Notes =

* When an account is blocked, the user can't use PayPal.

 

= How a payment is processed =

* User enters AMOUNT he wants to pay.
* System calculates AMOUNT+TAX.
* System sends AMOUNT+TAX to payment gateway.
* Payment gateway calculates FEE from AMOUNT+TAX.
* In payment gateway, AMOUNT+TAX is deducted from the user account.
* In payment gateway, AMOUNT+TAX-FEE is added to system owner account.
* After returning to the MOR, MOR adds AMOUNT to User balance.
* Payment is created which shows that AMOUNT was added to User's balance.
* If it is marked that User should pay FEE, then FEE is deducted from User's balance.
* Payment is created, which shows that FEE was deducted from User's balance.

 

= Testing mode =

If you get a message such as this when trying to use PayPal:

Please login to use the PayPal Sandbox features.

... it means you are using PayPal in Testing mode. Uncheck '''Test''' option in '''ADDONS -> Payment gateways -> Payments -> PayPal tab''':

 
[[File:paypal11.png]]
 
= See also =
* [[Payments]]
* [[Payment_Gateway_Addon | Payment Gateway Addon]]
* [[Payment_Fee|Payment fee]]
* [[PayPal Custom Buttons]]
* [[Payment_gateways_(PayPal_and_others)|Questions/Answers for payment gateways]]
* [[PayPal_payments_do_not_work|PayPal payments do not work]]

File:Paypal11.png

2025-06-11T12:08:48Z

Dmitrij: Dmitrij uploaded a new version of File:Paypal11.png

Warning balance

2025-06-10T08:05:08Z

Dmitrij:

= Description=

This function allows a number of actions to be taken when a user's balance drops lower than the set value.

You can edit '''Warning Balance''' in [[User Details]].

== From Admin Account ==

[[Image:Warning balance user edit.png]]
 

Check '''Active''' to activate this function.

Upon activation, the User, Admin and Responsible Accountant will receive an email when User balance drops lower than the balance set in the fields after: '''Send email when balance drops lower than'''.

Select when to send such an email and for who:

* '''Only once when balance drops lower than''' – email will be sent only one time when balance drops lower than written.
* '''Every day at''' – email will be sent every day at selected time, by users time zone, while balance is lower than written.

Additionally, you can play an audio message whenever the user makes a call if balance drops below setup Warning Balance.

Check '''Play before every call''' and select the audio file to play.

'''Play when balance drops lower than''' lets to set balance limit for above option.

Use this with caution - not many users will like this!

* '''Warning Balance Email''' – This Email is used as a primary email where to send Warning Balance email. If this email is empty '''Email''' in Registration Address section is used.

== From Reseller Account ==

[[Image:Warning_balance_user_edit_from_reseller.png]]
 

Check '''Active''' to activate this function.

Upon activation, the User and Reseller will receive an email when User balance drops lower than the balance set in the fields after: '''Send email when balance drops lower than'''.

Select when to send such an email and for who:

* '''Only once when balance drops lower than''' – email will be sent only one time when balance drops lower than written.
* '''Every day at''' – email will be sent every day at selected time, by users time zone, while balance is lower than written.

Additionally, you can play an audio message whenever the user makes a call if balance drops below setup Warning Balance.

Check '''Play before every call''' and select the audio file to play.

Use this with caution - not many users will like this!

* '''Warning Balance Email''' – This Email is used as a primary email where to send Warning Balance email. If this email is empty '''Email''' in Registration Address section is used.

=Other notes=

*Emails are sent hourly that means that it might take some time for you to receive an email after the balance drops.
*Function is available from MORx5
 

= See also =

* [[User Details]]

Warning balance

2025-06-02T10:43:24Z

Dmitrij: /* From Admin Account */

= Description=

This function allows a number of actions to be taken when a user's balance drops lower than the set value.

You can edit '''Warning Balance''' in [[User Details]].

== From Admin Account ==

[[Image:Warning balance user edit.png]]
 

Check '''Active''' to activate this function.

Upon activation, the User, Admin and Responsible Accountant will receive an email when User balance drops lower than the balance set in the fields after: '''Send email when balance drops lower than'''.

Select when to send such an email and for who:

* '''Only once when balance drops lower than''' – email will be sent only one time when balance drops lower than written.
* '''Every day at''' – email will be sent every day at selected time, by users time zone, while balance is lower than written.

Additionally, you can play an audio message whenever the user makes a call if balance drops below setup Warning Balance.

Check '''Play before every call''' and select the audio file to play.

'''Play when balance drops lower than''' lets to set balance limit for above option.

Use this with caution - not many users will like this!

* '''Warning Balance Email''' – This Email is used as a primary email where to send Warning Balance email. If this email is empty '''Email''' in Registration Address section is used.

== From Reseller Account ==

[[Image:Warning_balance_user_edit_from_reseller.png]]
 

Check '''Active''' to activate this function.

Upon activation, the User and Reseller will receive an email when User balance drops lower than the balance set in the fields after: '''Send email when balance drops lower than'''.

Select when to send such an email and for who:

* '''Only once when balance drops lower than''' – email will be sent only one time when balance drops lower than written.
* '''Every day at''' – email will be sent every day at selected time, by users time zone, while balance is lower than written.

Additionally, you can play an audio message whenever the user makes a call if balance drops below setup Warning Balance.

Check '''Play before every call''' and select the audio file to play.

Use this with caution - not many users will like this!

* '''Warning Balance Email''' – This Email is used as a primary email where to send Warning Balance email. If this email is empty '''Email''' in Registration Address section is used.

* '''Send SMS in addition to Emails''' - if this option is active (available from X15), MOR will send SMS in addition to Email. MOR will send SMS to number set in "Mobile Phone:" field in Registration Address section.

=Other notes=

*Emails are sent hourly that means that it might take some time for you to receive an email after the balance drops.
*Function is available from MORx5
 

= See also =

* [[User Details]]

Warning balance

2025-06-02T10:43:16Z

Dmitrij: /* From Admin Account */

= Description=

This function allows a number of actions to be taken when a user's balance drops lower than the set value.

You can edit '''Warning Balance''' in [[User Details]].

== From Admin Account ==

[[Image:Warning balance user edit.png]]
 

Check '''Active''' to activate this function.

Upon activation, the User, Admin and Responsible Accountant will receive an email when User balance drops lower than the balance set in the fields after: '''Send email when balance drops lower than'''.

Select when to send such an email and for who:

* '''Only once when balance drops lower than''' – email will be sent only one time when balance drops lower than written.
* '''Every day at''' – email will be sent every day at selected time, by users time zone, while balance is lower than written.

Additionally, you can play an audio message whenever the user makes a call if balance drops below setup Warning Balance.

Check '''Play before every call''' and select the audio file to play.

'''Play when balance drops lower than''' lets to set balance limit for above option.

Use this with caution - not many users will like this!

* '''Warning Balance Email''' – This Email is used as a primary email where to send Warning Balance email. If this email is empty '''Email''' in Registration Address section is used.

== From Reseller Account ==

[[Image:Warning_balance_user_edit_from_reseller.png]]
 

Check '''Active''' to activate this function.

Upon activation, the User and Reseller will receive an email when User balance drops lower than the balance set in the fields after: '''Send email when balance drops lower than'''.

Select when to send such an email and for who:

* '''Only once when balance drops lower than''' – email will be sent only one time when balance drops lower than written.
* '''Every day at''' – email will be sent every day at selected time, by users time zone, while balance is lower than written.

Additionally, you can play an audio message whenever the user makes a call if balance drops below setup Warning Balance.

Check '''Play before every call''' and select the audio file to play.

Use this with caution - not many users will like this!

* '''Warning Balance Email''' – This Email is used as a primary email where to send Warning Balance email. If this email is empty '''Email''' in Registration Address section is used.

* '''Send SMS in addition to Emails''' - if this option is active (available from X15), MOR will send SMS in addition to Email. MOR will send SMS to number set in "Mobile Phone:" field in Registration Address section.

=Other notes=

*Emails are sent hourly that means that it might take some time for you to receive an email after the balance drops.
*Function is available from MORx5
 

= See also =

* [[User Details]]

M4 Warning Balance

2025-06-02T10:42:53Z

Dmitrij: /* Usage */

=Description=

This function allows a number of actions to be taken when a User's balance drops lower or increases more than the set value.

You can edit Warning Balance in [[M4 Users | User Details]].
 
=Usage=

* Check '''Active''' to activate this function.
* Upon activation, the User, Admin, and Responsible Accountant will receive an email when the balance
** drops lower than the balance set in the fields.
** increases more than the balance set in the fields.
* '''Only once when the balance drops lower than''' – the email will be sent only one time when the balance drops lower than written.
* '''Every day at''' – the email will be sent every day at the selected time, by the user's time zone, while the balance is lower than written.
* Check '''Play before every call''' and select the audio file to play an audio message whenever the user makes a call if the balance drops below the setup Warning Balance.

[edit]

== For Terminators ==

Take note that the balance for Terminators increases when calls are made using them. So set values accordingly:

Send an email when the balance
x INCREASES more than:

And in the money input box enter a negative value.

Example:

[[File:m2_term_warning_balance_example.png]]

'''Use this with caution - not many users will like this!'''
 

=Destination of Email=

The email goes to one of the preset email addresses:

* Usually email is sent to '''Billing email''' address.
* If '''Billing email''' address is not set, email is sent to '''Main email''' address.
* If '''Main email''' address is not set, email is sent to '''Rates email''' address.
* If '''Rates email''' address is not set, email is sent to '''NOC email''' address.
* If none of the Billing, Main, Rates, or NOC emails is set, no warning balance email will be sent.

Admin and Accountant Warning Email gets into the email address which is written in the Registration Address block of Personal details.

File:Warning balance user edit.png

2025-06-02T10:38:44Z

Dmitrij: Dmitrij uploaded a new version of File:Warning balance user edit.png

File:Warning balance user edit from reseller.png

2025-06-02T10:37:08Z

Dmitrij: Dmitrij reverted File:Warning balance user edit from reseller.png to an old version

MOR API did details update

2025-05-29T11:24:48Z

Dmitrij: /* Parametres */

=Description=

[[MOR API]] DID details update

Please note that only admin, accountant(with device management) with permission and reseller can use this API.
 
=Usage=

* Call: /api/did_details_update
* Methods: POST, GET(if allowed, not recomended)
 
===Parametres===

Parameter which is '''included''' into hash:

* '''did_id''' – this is the id of DID which has to be updated. '''Required'''.

'''Note that parameters are shown in the same order as they have to be when generating the hash. Last parameter in a row is API_Secret_Key'''
 
Parameters which are '''not included''' into hash:

* [[MOR API hash construction | hash]] - SHA1 hash constructed using '''did_id''' and API_Secret_Key ([[MOR API hash construction | More described in Constructing hash]]). '''Required'''.
* '''u''' – username to login. '''Required'''.
* '''call_limit''' – call limit of did which will be updated. '''Optional'''
* '''did_user_id''' – User ID from database whom DID should be assigned. '''Just free DID can be assigned to User.''' DID can be assigned to Reseller or simple User. Set -1 to make DID free. '''Optional'''
* '''active_from''' - Active from date in Unix timestamp format. '''Optional'''.
* '''active_till''' - Active till date in Unix timestamp format. '''Optional'''.
* '''grace_time''' - same as [[DID_Management#Details|Grace Time GUI option]]: If call duration is less than Grace Time, it will not be accounted, for example: Grace Time = 3s, call duration <= 3s, then price for the call = 0. '''Optional'''
* '''language''' - allows setting two letters (i.e. en, it, es, ...) language code. '''Optional'''
* '''did_provider_id''' - this is the id of the Provider. Reseller Pro can use this as well.
* '''custom_sip_header''' - adds a custom SIP header. An empty value of the parameter (custom_sip_header=) removes the existing value.
 

===Request===

We have API Secret Key = secret, did_id = 6511 
We send:

HTML POST: http://<server_ip>/billing/api/did_details_update?u=admin&did_id=6511&call_limit=999&hash=f7de355c9b4421ce6c705b4b32c89dbcaca51e46

'''* Note that username is not included in hash'''
 

===Returns===

'''Success'''

<page>
<status>
<success>DID details successfully updated</success>
</status>
</page>

'''After successfully updating DID action log record is added.'''
 
----
'''Errors'''
* <error>Access Denied</error> – Specified username (u) does not exist or u is not admin, reseller or accountant with permission.
* <error>Incorrect hash</error> – Hash was not correct. Check API_Secret_Key and order or params while concatenating hash_string.
* <error>Call limit is incorrect format</error> – Specified call limit has to be 0 or positive number.
* <error>DID is already assigned</error> – DID is already assign to other User, Reseller or Dial Plan.
* <error>DID was not found</error> – Specified did does not exist or it belongs to different username(u).
* <error>Active till must be greater than Active from</error>
* <error>Active till must be a valid timestamp</error>
* <error>Active from must be a valid timestamp</error>

 

=See also=

* [[MOR API]]

MOR API did create

2025-05-29T11:19:16Z

Dmitrij: /* Parametres (in this order only) */

=Description=

[[MOR API]] Create DID
 
=Usage=

* Call: /api/did_create
* Methods: POST, GET(if allowed, not recomended)
 
===Parametres (in this order only) ===

* u - username for authentication. '''Required'''.
* provider_id - Provider ID in MOR database, for which DID should be created '''Required'''.
* did - DID number to be created '''Required'''.
* custom_sip_header - adds a custom SIP header.

Note that when creating DID from '''Reseller'''`s account, provider_id parameter is '''not required''', but also can be used. In this case default provider id will be used.
* [[MOR API hash construction | hash]] - SHA1 hash constructed using '''params''' and '''API_Secret_Key''' ([[MOR API hash construction | More described in Constructing hash]]). '''Required'''.
'''provider_id and did are included in hash. username is not included in hash.'''
 

===Request===

We have provider_id = 1, API Secret Key = secret. We want to create DID with number 123456789.

We send:

HTML POST: http://<SERVER_IP>/billing/api/did_create?u=username&did=123456789&provider_id=1&hash=bc2f114099d16656d37e45fd9e8744cb9386d462

Now we can find these DIDs in GUI DID list.

 

===Returns===

'''Success'''
<?xml version="1.0" encoding="UTF-8"?>
<page>
<status>
<success>DID created</success>
</status>
<did_details>
<id>3</id>
</did_details>
</page>
 
----

'''Errors'''

<?xml version="1.0" encoding="UTF-8"?>
<page>
<status>
<error>Error message</error>
</status>
</page>

Error messages:

* Incorrect hash – Hash was not correct. Check API_Secret_Key and order or params while concatenating hash_string.
* Access Denied – Only Admin, Accountant or Reseller may use API.
* Provider was not found – Enter existing Provider ID.
* Your are not authorized to use this Provider – Specified Provider is not available to this user.
* You are not authorized to manage DIDs – If Accountant or Reseller is using API, they should have all permissions to perform specified actions.
* DID already exists – Enter unique DID number.
* Invalid DID specified – Enter a valid (numeric) DID number.
* DID creation failed – unknown error
 

=See also=

* [[MOR API]]

MOR API did create

2025-05-29T11:18:39Z

Dmitrij: /* Parametres (in this order only) */

=Description=

[[MOR API]] Create DID
 
=Usage=

* Call: /api/did_create
* Methods: POST, GET(if allowed, not recomended)
 
===Parametres (in this order only) ===

* u - username for authentication. '''Required'''.
* provider_id - Provider ID in MOR database, for which DID should be created '''Required'''.
* did - DID number to be created '''Required'''.

Note that when creating DID from '''Reseller'''`s account, provider_id parameter is '''not required''', but also can be used. In this case default provider id will be used.
* [[MOR API hash construction | hash]] - SHA1 hash constructed using '''params''' and '''API_Secret_Key''' ([[MOR API hash construction | More described in Constructing hash]]). '''Required'''.
'''provider_id and did are included in hash. username is not included in hash.'''
'''custom_sip_header''' - adds a custom SIP header.
 

===Request===

We have provider_id = 1, API Secret Key = secret. We want to create DID with number 123456789.

We send:

HTML POST: http://<SERVER_IP>/billing/api/did_create?u=username&did=123456789&provider_id=1&hash=bc2f114099d16656d37e45fd9e8744cb9386d462

Now we can find these DIDs in GUI DID list.

 

===Returns===

'''Success'''
<?xml version="1.0" encoding="UTF-8"?>
<page>
<status>
<success>DID created</success>
</status>
<did_details>
<id>3</id>
</did_details>
</page>
 
----

'''Errors'''

<?xml version="1.0" encoding="UTF-8"?>
<page>
<status>
<error>Error message</error>
</status>
</page>

Error messages:

* Incorrect hash – Hash was not correct. Check API_Secret_Key and order or params while concatenating hash_string.
* Access Denied – Only Admin, Accountant or Reseller may use API.
* Provider was not found – Enter existing Provider ID.
* Your are not authorized to use this Provider – Specified Provider is not available to this user.
* You are not authorized to manage DIDs – If Accountant or Reseller is using API, they should have all permissions to perform specified actions.
* DID already exists – Enter unique DID number.
* Invalid DID specified – Enter a valid (numeric) DID number.
* DID creation failed – unknown error
 

=See also=

* [[MOR API]]

M4 CDR Management

2025-05-13T10:57:50Z

Dmitrij: /* Configuration */

=Description=

When there are many old calls that are no longer useful, they can be archived and moved to another place.

Such housekeeping increases system stability, reliability, and speed.
 
=Usage=

==Configuration==

Archiving options can be set in '''MAINTENANCE -> Settings''' in '''Archived Calls''' section:

* '''Archive to''' - choose where to store Archived Calls. By default Archived Calls are stored in another MySQL table ''mor.calls_old''. You can also choose to store Archived Calls in compressed CSV files by selecting ''File (TGZ)'' option. 
** It is also possible to choose to store Archived Calls to FTP (TGZ). In this case, Archived Calls will be stored on an FTP server. Please enter [http://wiki.kolmisoft.com/index.php/M4_settings#FTP FTP]server details if you would like to use this option. 
* '''Archive Calls older than''' – this is the number of days. When a Call is older than the number you set, it will be archived and moved to Archived Calls. 
* '''Archive only ANSWERED calls''' – check to archive only answered Calls. Failed, Busy and No Answer Calls will be deleted. 
* '''Archive Calls every day at''' – when archiving process should be started? Call archiving requires a lot of system resources therefore it is advisable to start archiving when call traffic is low. 
* '''Stop Archiving Calls at''' – when archiving process should be stopped? It is advisable to stop archiving before call traffic is increased. If time is not specified, Call archiving will be stopped when all Calls are archived. 
* '''Delete Calls instead of Archiving''' - if you don't need Calls older than X days, you can delete them instead of archiving them. 
* '''Delete Archived Calls older than''' - this is the number of days. When '''archived''' Call is older than the number you set, it will be deleted. 
* '''SQL Max Execution Time''' - max time in seconds for SQL query. The default time is 300 seconds (5 minutes). Used in Statistics pages (Calls List export and similar).

'''NOTE''': you can check the completion of the call archiving process and other information in Background Tasks.
 

==Archived Calls==

If calls are stored in another MySQL table ''mor.calls_old'' it can be found at '''Reports –> Call list –> Archived Calls'''. 
Here you can see a similar table to Last Calls, so you can check call information at any time you want. You can find more information about each field in [[Last Calls]] 

'''NOTE''' Simple Users cannot see the Archived Calls page.
 
==Archived Calls in Files==

If ''Archive to File (TGZ)'' option is enabled, Calls will be archived to CSV files (max 50000 lines per file), then compressed to TGZ and stored in your Backup storage directory (http://wiki.kolmisoft.com/index.php/Backup_system#Configuration). 
'''Calls archiving into file allows avoiding growing database and lets to use archived calls data more flexible.'''

Files with calls can be found at '''REPORTS –> Call list –> Archived Calls -> Files'''
 
[[File:m4_old_calls_in_file.png]]
 
'''NOTE''' Files can be reached and managed by '''admin''' only.
 
===Bulk management===

Files can be deleted one by one with click on '''DELETE''' in the files list or a few at a time by selecting the period in '''Bulk management'''

 
= See also =
* [[M4 Automatic CDR Export | Automatic CDR Export]]

Why call was not routed through other provider/trunk?

2025-03-20T11:49:28Z

Dmitrij:

If you see that a call was not routed through the second (third/fourth/...) Provider/Trunk, take the following steps:

1. Check '''[[Call Tracing]]''' – it is possible that other Providers can't handle the call (no rates, not configured properly, not assigned to LCR, etc).

2. Call hangup cause is not FAILED. (Next provider is used ONLY when call hangup cause is FAILED). Check '''STATISTICS –> Calls –> Last Calls''' – check '''Hangup Cause''' for your failed call. If the Hangup Cause is NO ANSWER or BUSY, then MOR does not route the call to the next provider. More details [[NO ANSWER/BUSY interpretation for providers | here]].
 

==User case==
As shown in the picture, the Provider is not responding. Provider did not fail yet and because of that the next provider is not used. The user did not wait for provider timeout/failure and canceled the call. 
[[File:Provider not responding.png]] 
To solve the issue, the Qualify option was enabled at provider settings to skip this provider and use next provider in the Call.

 
= See also =
* [[I have a problem with Calls]]
* [[I HAVE A PROBLEM]]

File:Provider not responding.png

2025-03-20T11:44:01Z

Dmitrij:

Device settings

2025-03-07T09:25:11Z

Dmitrij: /* Advanced */

<mkmeta>MOR Device Settings Explained</mkmeta>
=General=

* '''Accountcode''' – the unique ID of the device in the system.
* '''Description''' – for informational purposes.
* '''PIN''' – device PIN for authentication/authorization.
* '''Device group''' – to which group the device belongs (not used most of the time).
* '''Type''' – what type of device it is. Device type '''cannot''' be changed once it is created.
* '''Extension''' – a short number by which this device can be reached; must be unique in the system.
* '''DTMF Mode''' – in which protocol phone button presses are sent over network. The available options are: inband, info, RFC2833, and auto. Choose which one your provider uses (RFC2833 is used most often). This setting applies to SIP, H.323 and IAX2 protocols. For ZAP devices edit the configuration files in /etc/asterisk.
* '''Location''' – the default is Global. Choose the appropriate location based on [[Localization]] needs.
* '''Ringing Timeout''' – allows to limit the ringing duration in seconds. Minimal value is 10 seconds. Option is designed for incoming calls.
* '''Call Timeout''' – allows to limit answered call billsec. Leave 0 for unlimited.
* '''[[Trunks | Trunk]]''' – No/ Yes/ Yes with ANI/ 3CX – Is this device Trunk with/without ANI, 3CX? The "3CX" option adds rinstance parameter to R-URI which is used on 3CX authentication. More details: https://www.3cx.com/docs/sip-trunk-registration-authentication/
* '''[[Multi_Server_support | Server]]''' – allows to choose server in multiple servers system. Choose '''''All''''' to assign all servers. Option '''All''' can be used and is shown only for IP Authenticated devices. (While Carrier Class Addon is active, all Virtual and Fax devices are auto-assigned to all present Asterisk servers and cannot be re-assigned. Disabling Carrier Class Addon all Virtual and Fax devices will be assigned to default Asterisk server chosen from Addons > Carrier Class > Settings dropdown).
* '''Balance''' – a balance of the device. Disabled by default. Balance is decreasing when the User makes calls. Payments does not affect device balance.
 

=Authentication=

===For dahdi devices:===

* '''Channel''' – which channel (or channel group) to use on PRI/BRI/PSTN card. Channels and groups should be configured in ''zapata.conf''.
 
===For SIP, H323 and IAX2 Devices:===

'''IP Authentication:'''
* '''Hostname''' – Device hostname. Use "IP Address" instead if you have problems with inbound calls.
* '''IP Address''' – Device IP address in one of the following formats:
** '''IP''' – understands simple IPv4 address, IPv4 address with it's Subnet Mask and IPv4 address with it's Range. For example ''192.168.0.1'', ''192.168.0.1/24'' and ''192.168.0.0-255''. Or IPv6 address without a Subnet Mask or Range.
* '''Accept calls from any port''' – this option lets you receive calls from different Ports. This option is just on SIP (when [[SIP balancer]] in use) and H323.
* '''Port''' – Device Port.

'''Dynamic:'''

* '''Username''' – username you enter in your Device.
* '''Password''' – password you enter in your Device.
* '''IP Address''' – shows Device IP address.
* '''Port''' – shows Device Port.
* '''Registration Status''' - available only for SIP devices. If device is assigned to server A but registers to server B - status will not be shown (devices must register to the server they are assigned to). If no status is displayed - device has not tried to register or no one called to that device. Qualify must enabled if you want to monitor device status.
* '''UNREGISTER''' - last registration information will be deleted (ipaddr, port, fullcontact).
 

=CallerID=
 
[[File:device_callerid.png]]
 
A CallerID consists of two parts: Name and Number. The "Number" part is transferred by default by all technologies (GSM, PSTN, SIP etc), but the "Name" part is transferred only by some. The number you see on your mobile phone when someone is calling you is the "Number" part.

* '''Name''' – the "Name" part of the CallerID.
* '''Number''' – the "Number" part of the CallerID. Only numerical values can be entered in this field.

NOTE: if you leave these fields empty, the user can set the CallerID name by himself. Usually it is not advisable to allow the user do it on his own. If CallerID number field is empty, system will take device username as CallerID number (if device is username/password authenticated).

* '''Number from DID''' - use the DID as the CallerID (only available when the device has DIDs), this option just sets CallerID Number to be equal to DID. Next time you will edit Device's settings, first option - Number will be checked

* '''Control by DIDs (CID from DIDs)''' – only available when the device has DIDs and "Number" field is empty.

This setting lets you control what a CID user can enter in his devices. CID numbers should be from the set of the device's DIDs. They are mainly used when the user's PBX is connected over Trunk and many DIDs are routed to this Trunk. Calls coming out from this PBX must have a CallerID Number from the set of DIDs assigned to this Trunk (PBX). If "CID from DIDs" is checked, the system checks whether the device's CID number is from DIDs assigned to this device. If no DIDs are assigned, this value is ignored. In order for this setting to be active, CID Name/Number fields must be empty to allow the user to enter any CID number he wants. If "CID from DIDs" is checked and user enters any CID (not from his DIDs), the system will change his CID to one of the DIDs assigned to this Device. Original (non Localized) CallerID is used for DID matching.

* '''Control by CIDs''' – system checks incoming CallerID (Device's CallerID which is set on the Device). If CallerID matches one of the Device's CIDs - then such CallerID will be allowed. If it does not match - it will be changed to the selected CID.

* '''Control by Destination''' – This is advanced option which works by such algorithm:

# system checks Destination and checks DIDs assigned to calling Device. Then it finds 'nearest' DID to the Destination by subtracting DID from Destination in numerical form (Example, DID: 11111, Destination: 11112, |DID-Destination|=|1111-11112|=1) If Device has several DIDs - the lowest value is selected and this DID is set as CallerID.
#If Device has no DIDs - then User DIDs are used.
#If Device does not have DIDs and User has no DIDs, then CallerID set in Number field will be used.
#If nothing is set here - CallerID coming from Device will be used.
Note: behavior can be [http://wiki.kolmisoft.com/index.php/Mor.conf changed] to search for '''best matching''' DID instead of '''nearest''' DID
* '''Random Number from Number Pool''' – This functionality gives you an ability to send different caller number on each Call. Available from MOR X4. More information: [http://wiki.kolmisoft.com/index.php/Number_Pool Number Pool].
#Random - Send random CallerID.
#Pseudorandom with Deviation. Range can vary from 0 to 9999999. If 0 is chosen, then all numbers will be chosen same amount of times. If 9999999 is set, then numbers will be completely random.

* '''Unknown''' - This option lets you set CallerID number to ''unknown'' and pass a custom CallerID in either RPID or PAI header: 
[[File:Unknown_cid_rpid_pai.png]]

* '''Copy Leg A Name to Leg B Number''' – Leg A name will be used as Leg B number.
 

=Network Related=

===For H323:===

* '''Fast start''' – option for faster H.245.
* '''h245 Tunneling''' – use H.245 without opening a second TCP/IP channel.
More info you can find [http://toncar.cz/Tutorials/VoIP/VoIP_Protocols_H323_Call_Signalling_Optimizations.html here].
 
===For SIP and IAX2===

* '''Media control''' – can reinvite. Do you want your server to stay in media path between your clients and your provider? Please note that this option will work only if it is supported from both, device and provider, sides and it allows to handle SIP packets only. Moreover, no codec mismatch between device and provider is available. Default value is ''No''. '''WARNING''': This option can cause [[Call was billed incorrectly|incorrect billing]].
** canreinvite = yes "allow RTP media direct"
** canreinvite = no "deny re-invites"
** canreinvite = nonat "allow reinvite when local, deny reinvite when NAT"
** canreinvite = update "use UPDATE instead of INVITE"
** canreinvite = update,nonat "use UPDATE when local, deny when NAT"
* '''NAT''' – the available options are: yes, no, never, force_rport, comedia. For a detailed explanation of these settings, refer to [http://www.voip-info.org/wiki/view/Asterisk+sip+nat here].
* '''Qualify''' – how long to wait for a response to Qualify request. If you have lot of Devices in your system, set it to 9000ms or more. More details [http://www.voip-info.org/wiki/view/Asterisk+sip+qualify here] for SIP devices and [http://www.voip-info.org/wiki/view/Asterisk+iax+qualify here] for IAX2 devices.
* '''IAX2 Trunking Mode''' – enable/disable trunking mode, which allows multiple voice streams to share a single "trunk" to another server, reducing overhead created by IP packets. Only on IAX2.
 

=Groups=

* [[What are callgroups and pickupgroups | Call Group]] – to which Call Group this device belongs.
* [[What are callgroups and pickupgroups | Pickup Group]] – which Call Groups this device can pick up.
 
=Voicemail=

* '''Email''' – where to send received Voicemail.
* '''Password''' – the digital password the user enters when he calls the Voicemail number to hear his messages.
Voicemail login details are required when the user access Voicemail from outside over DID.
* '''Enable MWI''' - In telephony, a Message Waiting Indicator (MWI) is a telephone calling feature that illuminates a LED on selected telephones to notify a user of waiting for voicemail messages. It works on most telephone networks and PBXs.
* '''Subscribe MWI''' - If set to 'no', then Asterisk will send notifications to the phone about new voicemails. If set to 'yes', then the Phone should subscribe to Asterisk to get messages. If MWI does not work on your phone, try to switch this setting on/off.
* '''Delete VoiceMail after sending it''' – If it is set to 'yes', the VoiceMail will be deleted after it is sent to email.
 
* Language – (in Advanced settings) sets Voicemail language (and IVR language)

 

=Codecs=

[[Which codecs should I choose for devices | Choose the codecs]] your provider uses.

NOTES:
* When no fields are checked, all codecs are available – for example, settings in sip.conf or iax.conf are effective.
* If the Provider and the Device do not have similar codecs, no call can be established.
 

=Allowed Addresses=

Described [[Allowed Addresses | here]]

 

=Limits=

Here is possible to set various limits for a device.
 
[[File:Mor_device_call_limits.png]]
 

*'''Separate concurrent Call Limits'''
**'''Outbound concurrent Call Limit''' - how many outbound simultaneous calls a Device can make?
**'''Inbound concurrent Call Limit''' - how many inbound simultaneous calls a Device can get?
*'''One concurrent Call Limit (Outbound + Inbound)''' - how many outbound simultaneous and inbound simultaneous together calls a Device can make?
*'''Time limit per day''' - Total time available for device per day. When the limit is reached call fails with HGC "239 - Device used its daily call time limit" (total time is calculated after rounding rules and minimal time adjustment, so if the user's tariff has increment higher than 1 or minimal time set, then the total device time may be different than actual call time).
*'''Time limit per month''' - Total time available for device per month. You can also set the day of the limit reset (the default is 1st day of a month). When the limit is reached, the call fails with HGC "286 - Device used its monthly call time limit" (total time is calculated after rounding rules and minimal time adjustment, so if the user's tariff has increment higher than 1 or minimal time set, then total device time may be different than actual call time).
*'''(CPS) Limit up to''' - allows setting calls per second limit in some period.
*'''Hangup Call if PDD is more than'''- set maximum PDD time (in seconds) before call hangup. Note that failover providers will not be used in this case. The call will be hung up completely and will not be passed to other providers in LCR.

=Advanced=

* '''Fromuser/Fromdomain''' – used when calling TO this peer FROM Asterisk. If you're using _register=>_ with another SIP proxy, this setting can come in handy since some SIP networks only allow users in the right domain with the correct user name.
* '''Trustrpid''' – defines whether or not Remote-Party-ID is trusted. It's defined in http://tools.ietf.org/id/draft-ietf-sip-privacy-04.txt.
* '''Sendrpid''' – defines whether a Remote-Party-ID SIP header should be sent. The default setting is "no". This field is often used by wholesale VoIP providers to provide calling party identity regardless of the privacy settings (the From SIP header).
* [http://www.voip-info.org/wiki/index.php?page=Asterisk+sip+insecure Insecure]
** port: ignore the port number where the request came from. '''WARNING:''' do NOT enable it on username/password authenticated devices.
** invite: don't require authentication of incoming INVITEs. '''WARNING:''' do NOT enable it on username/password authenticated devices.
** port, invite: don't require initial INVITE to authenticate and ignore the port where the request came from. '''WARNING:''' do NOT enable it on username/password authenticated devices.

Both of these settings are enabled by default for [[Authentication | IP Authenticated]] devices, but they can be changed, unless you are using Carrier Class Addon, which forces the device to ignore the port number and the authentication from an incoming request.

Insecure Invite means that MOR will not challenge for a password, it means that anyone who knows extension can call without password, this is the reason why it is very insecure to use for username/password authenticated devices.

Insecure Port means that MOR will allow INVITES from a different port than the one REGISTER packets come from. This could be used with username/password authenticated devices too.

* '''Disable global pass_privacy''' - if set to yes, this option disables global [[mor.conf|pass_privacy_header]] variable for this device. If global pass_privacy_header variable is not set to yes, this option has no effect.
* '''Usereqphone''' - Yes or No. The default setting is "No". Option adds ;user=phone in From, To, INVITE and PAI headers. Only active for incoming calls. If the device is originator, please set '''Usereqphone''' in Provider settings.
* '''Custom SIP Header''' - adds custom header to SIP request. Format is '''header: value''' (for example '''x-My-Custom-Header: my value''')
* '''[http://www.voip-info.org/wiki/index.php?page=Asterisk+sip+progressinband Progressinband]''':
** yes – when the "RING" event is requested, always send 180 Ringing (if it hasn't been sent yet) followed by 183 Session Progress and in-band audio.
** no – send 180 Ringing if 183 has not yet been sent, establishing an audio path. If the audio path is established already (with 183), then send in-band ringing (this is the way Asterisk historically behaved because of buggy phones like Polycom's).
** never – whenever ringing occurs, send "180 ringing" as long as "200 OK" has not yet been sent. This is the default behavior of Asterisk.
NOTE: if Progressinband does not work, add "prematuremedia=no" to sip.conf and reload Asterisk.
* '''Video support''' – does your provider support Video over IP? More info [http://www.voip-info.org/wiki/view/Asterisk+video here].
* '''[[Duplicate call prevention | Allow duplicate calls]]''' – the default setting is "no".
* '''Language''' – sets IVR language
* '''Use ANI (if available) for CallerID:''' – When the call comes the information about who is calling is found in CallerID field. This field is used to determine who is calling. When the call comes through PRI/SS7 channels - then additional information is available who is calling in ANI field (in call's data channel) so sometimes CallerID might be empty or anonymous, but the caller can be found in ANI field. This option allows to use ANI field as CallerID to determine and recognize who is calling.
* '''Incoming Call CallerID Presentation''' – sets CallerID Presentation. Please note that this setting applies only for incoming calls. More information can be found [http://www.voip-info.org/wiki/view/Asterisk+cmd+SetCallerPres here] and [http://www.voip-info.org/wiki/view/Asterisk+cmd+CallingPres here]
* '''Change Failed Code To''' – if call fails change Hangup Cause Code to this value. This works only for outgoing calls from device. '''Not for Incoming'''
* '''Forward DID''' – it allows to forward call to DID which is assigned to Authorization by PIN or Calling Cards dial plan. After user enters PIN of any device or card, call gets connected with destination.
* '''Anti-resale (Auto-answer)''' – when option is set to YES, MOR answers the call before sending it to provider in order to generate FAS. This does not affect billing in MOR (User is not billed for extra time).
* '''Anti-resale (Auto-answer) Sound file''' - this setting is visible when the Anti-resale (Auto-answer) is set to '''Yes''' only.
* '''Transport''' – lets you choose protocol(s) for data transfer. Appears only if device is SIP and when Asterisk 1.8 is enabled. Default value: ''udp''. If TCP is used, it has to be [[How_to_enable_TCP_for_Asterisk |enabled in Asterisk]].
* '''T.38 Support''' – should T.38 pass-through be supported
* '''SRTP Encryption''' – should SRTP protocol be used for calls
* '''Block callerid if (number) simultaneous calls come from it''' – blocks CallerID if the entered number of simultaneous calls come from it

* '''Outbound Proxy''' – send outbound signaling to this proxy, not directly to the peer (Internal Asterisk option).
* '''SIP Session Timers''' - SIP Session Timers provide an end-to-end keep-alive mechanism for active SIP sessions. Possible values are "accept", "originate", "refuse":
** '''originate''' - request and run session-timers always.
** '''accept''' - run session-timers only when requested by other UA.
** '''refuse''' - do not run session timers in any case.
* '''SIP Session Refresher''' - The session refresher (uac|uas). Defaults to 'uas'.
** '''uac''' - default to the caller initially refreshing when possible.
** '''uas''' - default to the callee initially refreshing when possible.
* '''SIP Session Expires''' - maximum session refresh interval in seconds. Defaults to 1800 secs.
* '''SIP Min Session''' - minimum session refresh interval in seconds. Defaults to 90 secs.
* '''Localize PAI''' - if set to 'yes' then MOR will localize originator's number from PAI (P-Asserted-Identity) by [[Localization | CallerID Localization Rules]]. Works only if '''pass_pai''' is set in [[Mor.conf|mor.conf]].
* '''Pass PAI''' - available options are 'Global', 'Yes', 'No'. Global (default value) means use value from pass_pai in [[mor.conf]] file. More information available in table [[P-Asserted-Identity#How_P-Asserted-Identity_.28PAI.29_is_handled_in_MOR_X11_and_later_versions|here]].
* '''PAI Transformation''' - PAI Transformation. More info [https://wiki.kolmisoft.com/index.php/MOR_SIP_Header_Transformations here].
* '''Use random Number when CallerID is invalid''' - if set to ''Yes'' then when CallerID is NOT found in a Number Pool set in '''Number Pool with valid CallerIDs''' then CalleID in FROM is changed to "anonymous" and random CallerID taken from '''Random Number from a Number Pool''' is set in PAI/RPID headers.
* '''Emergency CallerID''' - number from this field will be used as CallerID if Destination number matches any number from '''Emergency CallerID Number Pool''' (see below). Localization rules will be applied before checking Destination number in Number Pool. P-Asserted and/or Remote-party-ID will be overwritten with the same as CallerID. If Destination number (after localization applied) does not match any number in '''Emergency CallerID Number Pool''', then CallerID is handled as usual.
* '''Emergency CallerID Number Pool''' - Number Pool with numbers used for '''Emergency CallerID''' feature.
* '''Music On Hold to Device''' - what to play when this Device is made On Hold by other party. Feature named "mohinterpret" on Asterisk.
* '''Music On Hold from Device''' - what to play to other party, when this Device sets it On Hold. Feature named "mohsuggest" on Asterisk.
* '''Announcement to the Called Party''' - plays specified announcement to callee in the beginning of conversation, right after call is answered. For example you can play message like "This conversation will be recorded" before every call from this Device.
* ''' Allow forward from Resellers''' - If option is enabled, Reseller can forward call to this device from Reseller's User's Device Call-flow window. Username of the Device owner and Device extension will be visible from the Reseller account. Setting is active only when enabled at [https://wiki.kolmisoft.com/index.php/Configuration_from_GUI#Various Settings]
 

=Tell Options=

* '''Tell rate before call''' - should MOR tell announce minute price (rounded to cents) before every call. Default value is "no".
* '''Tell balance before call''' – should MOR tell the user his balance every time he tries to dial? The default setting is "no".
* '''Tell time''' - should MOR tell the user his remaining time every time he tries to dial? The default setting is "no".
** Time is told in MINUTES only. Currently it is not possible to tell both in minutes and seconds.
* '''Tell remaining time when left''' – when some time is left, MOR will tell the remaining time to talk (in seconds).
* '''Repeat remaining time when left''' – repeats the remaining time when some time is left (in seconds).
 
=Debug=

* [[SIP debug info|'''Process SIPCHANINFO''']] - shows SIP channel info in [[Asterisk CLI]] and saves this information on database.
NOTE: debug should be enabled only if you are experiencing any problems. It should be disable in any other cases, because it stores lot of information on database.
 

=Recordings=

This section is available when [[Recordings Addon]] is installed in the system.
 
=Comment=

Devices can have Comments, which gives information about the Device.
 
=See also=

* [[Devices]]
* [[Grace_time | Grace time]]
* [[PAP_device_configuration | PAP device configuration]]
* [[H323 Device settings]]
* [[Hide Device username for Users]]
* [[What is PIN]]

M4 Calls per Hour

2025-03-07T08:09:32Z

Dmitrij: /* Usage */

= Description =

This page shows statistics of calls grouped first by days, then users, then hours and then by prefixes.

== Who can access the page? ==

Admin and Manager.

= Usage =

Go to '''Reports –> Calls Per Hour''' 
 
[[File:Cph menu.png]]
 
You can Refine the search results by providing an intended time period, an Originator, an Origination point, a Terminator and a Termination point, Prefix 
 
[[File:Cph search.png]]
 
Besides Calls date, number of Attempted Calls, Answered Calls, Duration of calls made during the specific day/user/hour/prefix, Average Retries, you can also check and [http://wiki.kolmisoft.com/index.php/ASR/ACD ASR/ACD] information.
 
[[File:Cph table.png]]
 
You will not see days here that have no calls.

File:Cph search.png

2025-03-07T08:07:52Z

Dmitrij: Dmitrij uploaded a new version of File:Cph search.png

Device settings

2025-03-07T07:17:48Z

Dmitrij: /* Advanced */

<mkmeta>MOR Device Settings Explained</mkmeta>
=General=

* '''Accountcode''' – the unique ID of the device in the system.
* '''Description''' – for informational purposes.
* '''PIN''' – device PIN for authentication/authorization.
* '''Device group''' – to which group the device belongs (not used most of the time).
* '''Type''' – what type of device it is. Device type '''cannot''' be changed once it is created.
* '''Extension''' – a short number by which this device can be reached; must be unique in the system.
* '''DTMF Mode''' – in which protocol phone button presses are sent over network. The available options are: inband, info, RFC2833, and auto. Choose which one your provider uses (RFC2833 is used most often). This setting applies to SIP, H.323 and IAX2 protocols. For ZAP devices edit the configuration files in /etc/asterisk.
* '''Location''' – the default is Global. Choose the appropriate location based on [[Localization]] needs.
* '''Ringing Timeout''' – allows to limit the ringing duration in seconds. Minimal value is 10 seconds. Option is designed for incoming calls.
* '''Call Timeout''' – allows to limit answered call billsec. Leave 0 for unlimited.
* '''[[Trunks | Trunk]]''' – No/ Yes/ Yes with ANI/ 3CX – Is this device Trunk with/without ANI, 3CX? The "3CX" option adds rinstance parameter to R-URI which is used on 3CX authentication. More details: https://www.3cx.com/docs/sip-trunk-registration-authentication/
* '''[[Multi_Server_support | Server]]''' – allows to choose server in multiple servers system. Choose '''''All''''' to assign all servers. Option '''All''' can be used and is shown only for IP Authenticated devices. (While Carrier Class Addon is active, all Virtual and Fax devices are auto-assigned to all present Asterisk servers and cannot be re-assigned. Disabling Carrier Class Addon all Virtual and Fax devices will be assigned to default Asterisk server chosen from Addons > Carrier Class > Settings dropdown).
* '''Balance''' – a balance of the device. Disabled by default. Balance is decreasing when the User makes calls. Payments does not affect device balance.
 

=Authentication=

===For dahdi devices:===

* '''Channel''' – which channel (or channel group) to use on PRI/BRI/PSTN card. Channels and groups should be configured in ''zapata.conf''.
 
===For SIP, H323 and IAX2 Devices:===

'''IP Authentication:'''
* '''Hostname''' – Device hostname. Use "IP Address" instead if you have problems with inbound calls.
* '''IP Address''' – Device IP address in one of the following formats:
** '''IP''' – understands simple IPv4 address, IPv4 address with it's Subnet Mask and IPv4 address with it's Range. For example ''192.168.0.1'', ''192.168.0.1/24'' and ''192.168.0.0-255''. Or IPv6 address without a Subnet Mask or Range.
* '''Accept calls from any port''' – this option lets you receive calls from different Ports. This option is just on SIP (when [[SIP balancer]] in use) and H323.
* '''Port''' – Device Port.

'''Dynamic:'''

* '''Username''' – username you enter in your Device.
* '''Password''' – password you enter in your Device.
* '''IP Address''' – shows Device IP address.
* '''Port''' – shows Device Port.
* '''Registration Status''' - available only for SIP devices. If device is assigned to server A but registers to server B - status will not be shown (devices must register to the server they are assigned to). If no status is displayed - device has not tried to register or no one called to that device. Qualify must enabled if you want to monitor device status.
* '''UNREGISTER''' - last registration information will be deleted (ipaddr, port, fullcontact).
 

=CallerID=
 
[[File:device_callerid.png]]
 
A CallerID consists of two parts: Name and Number. The "Number" part is transferred by default by all technologies (GSM, PSTN, SIP etc), but the "Name" part is transferred only by some. The number you see on your mobile phone when someone is calling you is the "Number" part.

* '''Name''' – the "Name" part of the CallerID.
* '''Number''' – the "Number" part of the CallerID. Only numerical values can be entered in this field.

NOTE: if you leave these fields empty, the user can set the CallerID name by himself. Usually it is not advisable to allow the user do it on his own. If CallerID number field is empty, system will take device username as CallerID number (if device is username/password authenticated).

* '''Number from DID''' - use the DID as the CallerID (only available when the device has DIDs), this option just sets CallerID Number to be equal to DID. Next time you will edit Device's settings, first option - Number will be checked

* '''Control by DIDs (CID from DIDs)''' – only available when the device has DIDs and "Number" field is empty.

This setting lets you control what a CID user can enter in his devices. CID numbers should be from the set of the device's DIDs. They are mainly used when the user's PBX is connected over Trunk and many DIDs are routed to this Trunk. Calls coming out from this PBX must have a CallerID Number from the set of DIDs assigned to this Trunk (PBX). If "CID from DIDs" is checked, the system checks whether the device's CID number is from DIDs assigned to this device. If no DIDs are assigned, this value is ignored. In order for this setting to be active, CID Name/Number fields must be empty to allow the user to enter any CID number he wants. If "CID from DIDs" is checked and user enters any CID (not from his DIDs), the system will change his CID to one of the DIDs assigned to this Device. Original (non Localized) CallerID is used for DID matching.

* '''Control by CIDs''' – system checks incoming CallerID (Device's CallerID which is set on the Device). If CallerID matches one of the Device's CIDs - then such CallerID will be allowed. If it does not match - it will be changed to the selected CID.

* '''Control by Destination''' – This is advanced option which works by such algorithm:

# system checks Destination and checks DIDs assigned to calling Device. Then it finds 'nearest' DID to the Destination by subtracting DID from Destination in numerical form (Example, DID: 11111, Destination: 11112, |DID-Destination|=|1111-11112|=1) If Device has several DIDs - the lowest value is selected and this DID is set as CallerID.
#If Device has no DIDs - then User DIDs are used.
#If Device does not have DIDs and User has no DIDs, then CallerID set in Number field will be used.
#If nothing is set here - CallerID coming from Device will be used.
Note: behavior can be [http://wiki.kolmisoft.com/index.php/Mor.conf changed] to search for '''best matching''' DID instead of '''nearest''' DID
* '''Random Number from Number Pool''' – This functionality gives you an ability to send different caller number on each Call. Available from MOR X4. More information: [http://wiki.kolmisoft.com/index.php/Number_Pool Number Pool].
#Random - Send random CallerID.
#Pseudorandom with Deviation. Range can vary from 0 to 9999999. If 0 is chosen, then all numbers will be chosen same amount of times. If 9999999 is set, then numbers will be completely random.

* '''Unknown''' - This option lets you set CallerID number to ''unknown'' and pass a custom CallerID in either RPID or PAI header: 
[[File:Unknown_cid_rpid_pai.png]]

* '''Copy Leg A Name to Leg B Number''' – Leg A name will be used as Leg B number.
 

=Network Related=

===For H323:===

* '''Fast start''' – option for faster H.245.
* '''h245 Tunneling''' – use H.245 without opening a second TCP/IP channel.
More info you can find [http://toncar.cz/Tutorials/VoIP/VoIP_Protocols_H323_Call_Signalling_Optimizations.html here].
 
===For SIP and IAX2===

* '''Media control''' – can reinvite. Do you want your server to stay in media path between your clients and your provider? Please note that this option will work only if it is supported from both, device and provider, sides and it allows to handle SIP packets only. Moreover, no codec mismatch between device and provider is available. Default value is ''No''. '''WARNING''': This option can cause [[Call was billed incorrectly|incorrect billing]].
** canreinvite = yes "allow RTP media direct"
** canreinvite = no "deny re-invites"
** canreinvite = nonat "allow reinvite when local, deny reinvite when NAT"
** canreinvite = update "use UPDATE instead of INVITE"
** canreinvite = update,nonat "use UPDATE when local, deny when NAT"
* '''NAT''' – the available options are: yes, no, never, force_rport, comedia. For a detailed explanation of these settings, refer to [http://www.voip-info.org/wiki/view/Asterisk+sip+nat here].
* '''Qualify''' – how long to wait for a response to Qualify request. If you have lot of Devices in your system, set it to 9000ms or more. More details [http://www.voip-info.org/wiki/view/Asterisk+sip+qualify here] for SIP devices and [http://www.voip-info.org/wiki/view/Asterisk+iax+qualify here] for IAX2 devices.
* '''IAX2 Trunking Mode''' – enable/disable trunking mode, which allows multiple voice streams to share a single "trunk" to another server, reducing overhead created by IP packets. Only on IAX2.
 

=Groups=

* [[What are callgroups and pickupgroups | Call Group]] – to which Call Group this device belongs.
* [[What are callgroups and pickupgroups | Pickup Group]] – which Call Groups this device can pick up.
 
=Voicemail=

* '''Email''' – where to send received Voicemail.
* '''Password''' – the digital password the user enters when he calls the Voicemail number to hear his messages.
Voicemail login details are required when the user access Voicemail from outside over DID.
* '''Enable MWI''' - In telephony, a Message Waiting Indicator (MWI) is a telephone calling feature that illuminates a LED on selected telephones to notify a user of waiting for voicemail messages. It works on most telephone networks and PBXs.
* '''Subscribe MWI''' - If set to 'no', then Asterisk will send notifications to the phone about new voicemails. If set to 'yes', then the Phone should subscribe to Asterisk to get messages. If MWI does not work on your phone, try to switch this setting on/off.
* '''Delete VoiceMail after sending it''' – If it is set to 'yes', the VoiceMail will be deleted after it is sent to email.
 
* Language – (in Advanced settings) sets Voicemail language (and IVR language)

 

=Codecs=

[[Which codecs should I choose for devices | Choose the codecs]] your provider uses.

NOTES:
* When no fields are checked, all codecs are available – for example, settings in sip.conf or iax.conf are effective.
* If the Provider and the Device do not have similar codecs, no call can be established.
 

=Allowed Addresses=

Described [[Allowed Addresses | here]]

 

=Limits=

Here is possible to set various limits for a device.
 
[[File:Mor_device_call_limits.png]]
 

*'''Separate concurrent Call Limits'''
**'''Outbound concurrent Call Limit''' - how many outbound simultaneous calls a Device can make?
**'''Inbound concurrent Call Limit''' - how many inbound simultaneous calls a Device can get?
*'''One concurrent Call Limit (Outbound + Inbound)''' - how many outbound simultaneous and inbound simultaneous together calls a Device can make?
*'''Time limit per day''' - Total time available for device per day. When the limit is reached call fails with HGC "239 - Device used its daily call time limit" (total time is calculated after rounding rules and minimal time adjustment, so if the user's tariff has increment higher than 1 or minimal time set, then the total device time may be different than actual call time).
*'''Time limit per month''' - Total time available for device per month. You can also set the day of the limit reset (the default is 1st day of a month). When the limit is reached, the call fails with HGC "286 - Device used its monthly call time limit" (total time is calculated after rounding rules and minimal time adjustment, so if the user's tariff has increment higher than 1 or minimal time set, then total device time may be different than actual call time).
*'''(CPS) Limit up to''' - allows setting calls per second limit in some period.
*'''Hangup Call if PDD is more than'''- set maximum PDD time (in seconds) before call hangup. Note that failover providers will not be used in this case. The call will be hung up completely and will not be passed to other providers in LCR.

=Advanced=

* '''Fromuser/Fromdomain''' – used when calling TO this peer FROM Asterisk. If you're using _register=>_ with another SIP proxy, this setting can come in handy since some SIP networks only allow users in the right domain with the correct user name.
* '''Trustrpid''' – defines whether or not Remote-Party-ID is trusted. It's defined in http://tools.ietf.org/id/draft-ietf-sip-privacy-04.txt.
* '''Sendrpid''' – defines whether a Remote-Party-ID SIP header should be sent. The default setting is "no". This field is often used by wholesale VoIP providers to provide calling party identity regardless of the privacy settings (the From SIP header).
* [http://www.voip-info.org/wiki/index.php?page=Asterisk+sip+insecure Insecure]
** port: ignore the port number where the request came from. '''WARNING:''' do NOT enable it on username/password authenticated devices.
** invite: don't require authentication of incoming INVITEs. '''WARNING:''' do NOT enable it on username/password authenticated devices.
** port, invite: don't require initial INVITE to authenticate and ignore the port where the request came from. '''WARNING:''' do NOT enable it on username/password authenticated devices.

Both of these settings are enabled by default for [[Authentication | IP Authenticated]] devices, but they can be changed, unless you are using Carrier Class Addon, which forces the device to ignore the port number and the authentication from an incoming request.

Insecure Invite means that MOR will not challenge for a password, it means that anyone who knows extension can call without password, this is the reason why it is very insecure to use for username/password authenticated devices.

Insecure Port means that MOR will allow INVITES from a different port than the one REGISTER packets come from. This could be used with username/password authenticated devices too.

* '''Disable global pass_privacy''' - if set to yes, this option disables global [[mor.conf|pass_privacy_header]] variable for this device. If global pass_privacy_header variable is not set to yes, this option has no effect.
* '''Usereqphone''' - Yes or No. The default setting is "No". Option adds ;user=phone in From, To, INVITE and PAI headers. Only active for incoming calls. If the device is originator, please set '''Usereqphone''' in Provider settings.
* '''Custom SIP Header''' - adds custom header to SIP request. Format is '''header: value''' (for example '''x-My-Custom-Header: my value''')
* '''[http://www.voip-info.org/wiki/index.php?page=Asterisk+sip+progressinband Progressinband]''':
** yes – when the "RING" event is requested, always send 180 Ringing (if it hasn't been sent yet) followed by 183 Session Progress and in-band audio.
** no – send 180 Ringing if 183 has not yet been sent, establishing an audio path. If the audio path is established already (with 183), then send in-band ringing (this is the way Asterisk historically behaved because of buggy phones like Polycom's).
** never – whenever ringing occurs, send "180 ringing" as long as "200 OK" has not yet been sent. This is the default behavior of Asterisk.
NOTE: if Progressinband does not work, add "prematuremedia=no" to sip.conf and reload Asterisk.
* '''Video support''' – does your provider support Video over IP? More info [http://www.voip-info.org/wiki/view/Asterisk+video here].
* '''[[Duplicate call prevention | Allow duplicate calls]]''' – the default setting is "no".
* '''Language''' – sets IVR language
* '''Use ANI (if available) for CallerID:''' – When the call comes the information about who is calling is found in CallerID field. This field is used to determine who is calling. When the call comes through PRI/SS7 channels - then additional information is available who is calling in ANI field (in call's data channel) so sometimes CallerID might be empty or anonymous, but the caller can be found in ANI field. This option allows to use ANI field as CallerID to determine and recognize who is calling.
* '''Incoming Call CallerID Presentation''' – sets CallerID Presentation. Please note that this setting applies only for incoming calls. More information can be found [http://www.voip-info.org/wiki/view/Asterisk+cmd+SetCallerPres here] and [http://www.voip-info.org/wiki/view/Asterisk+cmd+CallingPres here]
* '''Change Failed Code To''' – if call fails change Hangup Cause Code to this value. This works only for outgoing calls from device. '''Not for Incoming'''
* '''Forward DID''' – it allows to forward call to DID which is assigned to Authorization by PIN or Calling Cards dial plan. After user enters PIN of any device or card, call gets connected with destination.
* '''Anti-resale (Auto-answer)''' – when option is set to YES, MOR answers the call before sending it to provider in order to generate FAS. This does not affect billing in MOR (User is not billed for extra time).
* '''Anti-resale (Auto-answer) Sound file''' - this setting is visible when the Anti-resale (Auto-answer) is set to '''Yes''' only.
* '''Transport''' – lets you choose protocol(s) for data transfer. Appears only if device is SIP and when Asterisk 1.8 is enabled. Default value: ''udp''. If TCP is used, it has to be [[How_to_enable_TCP_for_Asterisk |enabled in Asterisk]].
* '''T.38 Support''' – should T.38 pass-through be supported
* '''SRTP Encryption''' – should SRTP protocol be used for calls
* '''Block callerid if (number) simultaneous calls come from it''' – blocks CallerID if the entered number of simultaneous calls come from it

* '''Outbound Proxy''' – send outbound signaling to this proxy, not directly to the peer (Internal Asterisk option).
* '''SIP Session Timers''' - SIP Session Timers provide an end-to-end keep-alive mechanism for active SIP sessions. Possible values are "accept", "originate", "refuse":
** '''originate''' - request and run session-timers always.
** '''accept''' - run session-timers only when requested by other UA.
** '''refuse''' - do not run session timers in any case.
* '''SIP Session Refresher''' - The session refresher (uac|uas). Defaults to 'uas'.
** '''uac''' - default to the caller initially refreshing when possible.
** '''uas''' - default to the callee initially refreshing when possible.
* '''SIP Session Expires''' - maximum session refresh interval in seconds. Defaults to 1800 secs.
* '''SIP Min Session''' - minimum session refresh interval in seconds. Defaults to 90 secs.
* '''Localize PAI''' - if set to 'yes' then MOR will localize originator's number from PAI (P-Asserted-Identity) by [[Localization | CallerID Localization Rules]]. Works only if '''pass_pai''' is set in [[Mor.conf|mor.conf]].
* '''Pass PAI''' - available options are 'Global', 'Yes', 'No'. Global (default value) means use value from pass_pai in [[mor.conf]] file. More information available in table [[P-Asserted-Identity#How_P-Asserted-Identity_.28PAI.29_is_handled_in_MOR_X11_and_later_versions|here]].
* '''PAI Transformation''' - PAI Transformation. More info [https://wiki.kolmisoft.com/index.php/MOR_SIP_Header_Transformations here].
* '''Use random Number when CallerID is invalid''' - if set to ''Yes'' then when CallerID is NOT found in a Number Pool set in '''Number Pool with valid CallerIDs''' then CalleID in FROM is changed to "anonymous" and random CallerID taken from '''Random Number from a Number Pool''' is set in PAI/RPID headers.
* '''Emergency CallerID''' - number from this field will be used as CallerID if Destination number matches any number from '''Emergency CallerID Number Pool''' (see below). Localization rules will be applied before checking Destination number in Number Pool. P-Asserted and/or Remote-party-ID will be overwritten with the same as CallerID. If Destination number (after localization applied) does not match any number in '''Emergency CallerID Number Pool''', then CallerID is handled as usual.
* '''Emergency CallerID Number Pool''' - Number Pool with numbers used for '''Emergency CallerID''' feature.
* '''Music On Hold to Device''' - what to play when this Device is made On Hold by other party. Feature named "mohinterpret" on Asterisk.
* '''Music On Hold from Device''' - what to play to other party, when this Device sets it On Hold. Feature named "mohsuggest" on Asterisk.
* '''Announcement to the Called Party''' - plays specified announcement to callee in the beginning of conversation, right after call is answered. For example you can play message like "This conversation will be recorded" before every call from this Device.
* ''' Allow forward from Resellers''' - If option is enabled, Reseller can forward call to this device from Reseller's User's Device Call-flow window. Username of the Device owner and Device extension will be visible from the Reseller account
 

=Tell Options=

* '''Tell rate before call''' - should MOR tell announce minute price (rounded to cents) before every call. Default value is "no".
* '''Tell balance before call''' – should MOR tell the user his balance every time he tries to dial? The default setting is "no".
* '''Tell time''' - should MOR tell the user his remaining time every time he tries to dial? The default setting is "no".
** Time is told in MINUTES only. Currently it is not possible to tell both in minutes and seconds.
* '''Tell remaining time when left''' – when some time is left, MOR will tell the remaining time to talk (in seconds).
* '''Repeat remaining time when left''' – repeats the remaining time when some time is left (in seconds).
 
=Debug=

* [[SIP debug info|'''Process SIPCHANINFO''']] - shows SIP channel info in [[Asterisk CLI]] and saves this information on database.
NOTE: debug should be enabled only if you are experiencing any problems. It should be disable in any other cases, because it stores lot of information on database.
 

=Recordings=

This section is available when [[Recordings Addon]] is installed in the system.
 
=Comment=

Devices can have Comments, which gives information about the Device.
 
=See also=

* [[Devices]]
* [[Grace_time | Grace time]]
* [[PAP_device_configuration | PAP device configuration]]
* [[H323 Device settings]]
* [[Hide Device username for Users]]
* [[What is PIN]]

Configuration from GUI

2025-03-07T07:16:37Z

Dmitrij: /* Various */

=Where I can find this settings menu?=

You can find this menu in '''SETTINGS –> Setup –> Settings'''

[[File:Settings_path.png]]
 
== Global ==

'''SETTINGS –> Setup –> Settings –> [[Global_Settings | Global]]'''

* '''Company''' – name of the company.
* '''Company email''' – email address of the company.
* '''Version''' – version number.
* '''Copyright Title''' – copyright title supports html text format.
* '''Browser Title''' – browser title for MOR GUI.
* '''Front Page Text''' – some text to place on front page.
* '''Login Page Text''' – some text to place on login page
 

== Registration ==

'''SETTINGS –> Setup –> Settings –> Registration'''

* '''Enabled?''' – do we want to let users [[Online registration | register online]] automatically?
* '''Hide registration link in Login page?''' – tick this option if you do not want users to be able to register online.
* '''Default country'''
* '''Asterisk server IP''' – what IP should user connect his softphone/server to?
* '''Send Email to User after registration''' – just yes or no.
* '''Send Email to Admin after registration''' – just yes or no.
* '''Send Email To User after User was created''' – just yes or no.
* '''Send Email To Admin after User was created''' – just yes or no.
* '''[[ReCAPTCHA]] configuration'''
* '''[[User_Agreement|Terms and conditions]]'''
* '''Allow to create user and device with matching username and password''' – just yes or no. If this setting is not enabled - username and password from MOR GUI will have to be different than device's username and password.
* '''Enable VAT checking for EU companies''' – you can choose whether to check '''TAX Registration Number:''' during the [[Online registration]] or not. Done over [http://ec.europa.eu/taxation_customs/vies/?locale=lt EU page].
* '''Allow blank VAT for EU companies''' – allows to leave blank '''TAX Registration Number:''' field during the [[Online registration]]
 
===See also===

* [[Default user]]
 

== Invoices ==

'''SETTINGS –> Setup –> Settings –> Invoices'''

Invoice configuration is divided into '''Prepaid''' and '''Postpaid'''.
 
=== Settings ===

* '''Number start''' – how the invoice number should start.
* '''Number length''' – the length in digits AFTER Number Start – e.g. Number Start is not counted into this length. This value is active only for first number type.
* '''Number type''' – select more appropriate number format.
* '''Invoice period start''' – when invoices are issued, default is first day of the month.
* '''Show calls in detailed invoice''' – yes or no.
* '''[[Outstanding balance(Debt) | Show balance line]]''' – shows balance line in Invoice PDF files when Invoice is generated from first day of month till last one.
* '''Round finals to 2 decimals''' – round or not total in Invoices to 2 decimals.
* '''Use short file name'''
* '''Group Subscriptions''' - User's subscriptions will be grouped by service (only applies to PDF and XLSX invoice).
* '''Show Quantity''' - Show quantity of each service (only applies to PDF invoice).
* '''Invoice Page Limit:''' – invoice will be generated till this page limit. Additional page is added with an explanation that page limit was reached.
* ''' Rename 'DID owner cost' label in detailed PDF invoice:''' – text which will be used instead of '''DID owner cost''' in detailed PDF invoice.
* ''' Hide 'DID owner cost' line in detailed PDF invoice:''' – checkbox, which control whether or not DID owner cost should be shown in detailed PDF invoice.
* ''' Show Destination with Prefix in Detailed Invoice:''' - checkbox, if enabled, destination will be shown as '''Destination Name (prefix)'''.
* ''' Rename red 'INVOICE' label in Simplified PDF Invoice:'''
* ''' Rename red 'INVOICE' label in Detailed PDF Invoice:'''
* ''' Rename red 'INVOICE' label in PDF Invoice by CallerID:'''
 

=== Details ===

* '''Address format''' – changes field positioning in the invoice for the address. You must select it in order to show address in the invoice.
* '''Address line 1-4''' – address info.
* '''Bank details line 1-5''' – bank details info.
* '''Invoice balance line''' – line for balance (e.g. "Your current balance is")
* '''Invoice to pay Line'''
* '''End title''' – a title for the end of your invoice.

* '''Add Average rate in detailed invoice''' – adds average rate in detailed invoice.
* '''Show Time in Minute''' – shows time in mm:ss instead of hh:mm:ss, for example, not 02:13:42 but 133:42.
 

=== Additional ===

* '''Show additional details on separate page''' – enables additional custom page at the end of the invoice.
* '''Additional details''' – the information to be displayed in a custom page at the end of the invoice.
 
=== Functionality ===

* '''Invoice allow recalculate after send''' – allows recalculating invoices after being sent. This setting also allows to delete sent invoices.
* '''Do not generate Invoices for blocked Users''' - if enabled Invoices will not be generated for blocked Users.
* '''Rename "Calls" label''' - changes 'Calls' name for Simplified Invoices and new Invoice XLSX. If you want to apply new 'Calls' name for old XLSX, you should go to Settings > Invoices > XLSX and mark 'New XLSX template apply for old Invoices'
* '''Start value for Invoice numbers''' - defines number from which Invoices numeration should start.
* '''Duration Format:''' - time format in invoice. This setting applies for XLSX type invoices (and PDF invoices generated from XLSX invoice) and Invoice Details page. Available options - 'H:M:S', 'H:M', 'M'. When option 'M' is used, sub option Decimal places appear, where you can select precision.
* '''Invoice Group By: Prefix / Destination'''
* '''Show Rates:No / Yes'''
* '''Show Calls in CID Invoice (CSV)''' - if enabled, then CSV Invoice by CallerID will show a list of calls.

 

=== XLSX ===
* '''XLSX Template''' - choose XLSX Template for Invoices.
* '''Send XLSX Invoices converted to PDF''' – If enabled XLSX invoices will be converted to PDF before sending over [[Invoices#Send_invoices_by_email_.28manual.29|Email]] or [[Cron_actions#Generate_Invoices_and_send_by_Email|using cron action]]
* '''Group regular Calls by Destination''' - Groups regular Calls be destination
 

===See also===

* [[Invoices]]
* [[Invoice configuration]]
 

== Emails ==

'''SETTINGS –> Setup –> Settings –> Emails'''

* ''' Sending globally enabled''' – if this is checked, you will be able to use Mass Mailing and the system will send emails upon user registration.
* ''' Add recipient first name and last name''' – if this is checked, it will show the user's first name and last name if they are entered in the User Settings.
* '''SMTP server''' – hostname of the server.
* '''Port''' – port of SMTP server.
* '''Login''' – username to your SMTP server.
* '''Password''' – password to your SMTP server.
* '''Batch size''' – value for Mass Mailing, or how many emails to send at once.
* '''From''' – email address to put into From: field in email. Acceptable formats are: '''example@email.com''' or '''John Smith <example@email.com>'''.
* '''Test email sending''' – save settings and press this to test email sending. Do not forget to save settings first!
* '''TLS''' – '''Auto''', '''Yes''' or '''No'''. Default '''Auto'''.

'''P.S. Remember to set admin's e-mail in admin's personal settings. Without this test email sending will not work!'''

 
===See also===

* [[Emails|Mass Emails]]
* [[Email variables]]
 

== Various ==

'''SETTINGS –> Setup –> Settings –> Various'''

* '''Days for DID to close''' – how long to keep DID closed before making it free.
* '''Agreement number length''' – number length in digits.
* '''Change dahdi''' – Sometimes this is used to change "Zap" to something else in GUI, e.g. to "PSTN", mainly because not everybody knows what Zap stands for. PSTN is more common.
* '''Device PIN length''' – length for automatically generated PIN codes for devices.
* '''Device range MIN''' – from which extension automatic extension assigning starts.
* '''Device range MAX''' – till which extension automatic extension assigning goes.
** For example, from this interval: [Device range MIN, Device range MAX] MOR will select extensions for newly created Devices.
* '''Random Device Extension''' – when creating device, random number from '''Device Range''' will be taken.
* '''Enable "Allowed addresses" option for Devices:''' – allows [[Device_settings#Allowed_Addresses | Allowed Addresses]] functionality in Devices settings.
* '''Enable "Allowed addresses" option for Providers:''' – allows Allowed Addresses functionality in Providers settings.
* '''User wholesale tariff enabled''' – enables user wholesale tariffs.
* '''Play IVR for unauthenticated call'''
* '''Banned CLIs default IVR''' – default IVR to route banned numbers.
* '''Do not allow duplicate device user names'''
* '''Do not allow users to change their email addresses'''
* '''Logout link''' – a user will be redirected to this link after pressing "Logout"
* '''Change ANSWER to FAILED if HGC not equal to 16 for Users''' – changes the Hangupcause for users in call reports from Answered to Failed if Hangupcause is not 16.
* '''Inform when Devices are created or updated''' – check to get an email about every newly created or updated Device.
* '''Show Usernames on PDF/CSV Export Files in Last Calls''' – if checked, when a particular User in the Last Calls page search is selected, the Last Calls PDF/CSV file name will be composed also of the Name of selected User. If you are looking for All Users, no User Name will be used. (Name of the User will be shown in Name of the CSV/PDF file).
* '''Do not allow PREPAID User balance drop below zero (block them instead)'''
* '''Do not block POSTPAID User when balance goes bellow zero on subscription count'''
* '''Allow identical email addresses to different Users''' – allows creating Users or registering users with identical email addresses. After checking this setting you will be not able to check
* '''Show forgot password''', because this functionality requires a unique email in the system. The setting can be unchecked if all emails are unique in the system.
* '''Allow same IP and Port combinations in multiple Devices''' – allows creating Devices with the same IP and Port combination.
* '''Low Disk Space Alert''' – indicator when system should inform admin about low [[Multi_Server_support|Server]] space. By default 20%. Notice will appear in [[Integrity Check]] and every hour will send an email "Low Disk Space Alert". Which template can be found and edited on [[Emails]] page. Information about the Server and the remaining free space will be provided.
* '''Limit PDF size in Last Calls''' - limits how many pages can be exported from Last Calls to PDF. It takes a lot of system resources to generate PDF files therefore this limit should be low enough to prevent high load on system.
* '''Google Maps API key''' - the setting is necessary for using the Google Maps functionality. For more on how to configure this key please check [[Get Google Maps key]].
* '''Allow login by email''' - allow users to log in by email instead of a username.
* '''Call Forwarding CallerID''' - allows to manage CallerID when [http://wiki.kolmisoft.com/index.php/Call_Flow#Change_Forward_action_by_Call forwarding is set by call].
** '''From Device''' - puts CallerID for the Device that is forwarding the call. If Device CallerID is empty, then the originator's CallerID will be used.
** '''Same as comes - unchanged''' - leaves the CallerID as it comes from the originator.
** '''Same as comes - with Diversion''' - leaves the CallerID as it comes from the original caller and additionally adds SIP header Diversion with CallerID from the Device that is forwarding the call (header will not be added if Device does not have CallerID set).
* '''DID for Unassigned DID''' - this feature is used for calls coming from providers to system DIDs. Allows redirecting call to specific DID if client dials nonexistent DID. If empty, then this feature is disabled and a call will be terminated with [http://wiki.kolmisoft.com/index.php/207_Not_clear_who_should_receive_call 207 Not clear who should receive call] hangup code.
* '''Default Music On Hold''' - allows to select Default Music On Hold.
* '''Use Extension in CallerID for Local Calls''' - overwrites original CallerID with Device Extension when making local calls. Outside calls are not affected by this setting.
*'''Send Recordings space warning Email''' - sends Email to Admin once a day if recordings exceed space limit.
*'''Hide Provider Payments from User Payment List''' - default off.
*'''Delete Tariff Jobs older than''' - deletes tariff jobs older than set days.
*'''Delete Automatic Tariff Import Inbox Messages older than''' - deletes automatic tariff import inbox messages older than set days.
*'''Allow forward from Resellers''' - enables advanced device option: Allow forward from Resellers. More information about option in [https://wiki.kolmisoft.com/index.php/Device_settings#Advanced device settings].

== Tax ==

'''SETTINGS –> Setup –> Settings –> Tax'''

Settings are explained here: [[Multi-Tax system]]
 
== Backups ==

'''SETTINGS –> Setup –> Settings –> Backups'''

Configuration is explained here: [[Backup system]]
 
== API ==

'''SETTINGS –> Setup –> Settings –> API'''

* '''Allow API''' – enable/disable API.
* '''Allow GET API''' – enable/disable GET in API - use only for testing!
* '''API Secret Key''' – secret key for API. This will be used as a password for signing queries to MOR API, check [[MOR_API | MOR API documentation]] for more information
* '''XML API Extension''' – .NET does not follow standards (surprise!); enable this setting if you are using it to get XML starting with HTTP tags.
* '''Allow API Login Redirect''' – enable/disable
* '''API allow registration''' – enable/disable registration through API
* '''API allow Payments''' – enable/disable payments through API
* '''API Payment confirmation''' – enable/disable payments confirmation through API
* '''[[Balance_in_phone|Allow devices to check balance over HTTP]]''' – enable/disable device balance checking
* '''[[MOR_API_rate_get|Allow devices to check rate over HTTP]]''' – enable/disable device rate checking
* '''Disable hash checking''' – lets you skip hash parameter using API
* '''Uniquehash''' – shows your uniquehash
* '''Send Email To Admin after API/Manual Payment''' - sends Email to Admin after API/Manual payment. Email Template name: manual_payment_email
* '''Send Email to User after API/Manual Payment''' - sends Email to User after API/Manual payment. Email Template name: manual_payment_email_for_user
* '''Send Email To Admin after API/Balance Update''' - sends Email to Admin after API/Balance Update. Email Template name: balance_update_email
 
===See also===

[[MOR API]]
 

== Functionality ==

'''SETTINGS –> Setup –> Settings –> Functionality'''
 
===FAX===

* '''Fax device enabled''' – enable/disable Fax device in MOR. When admin enables FAX, Functionality tab appears in Reseller's GUI configuration. He can then enable or disabled fax for his own users himself.
* '''Fax2Email From Sender''' – there is a field "From:" in an email form. When MOR sends Fax to Email, "Fax2Email From Sender" value is displayed in "From:" field.
* '''Allow Users to change FAX email''' - allow simple Users to add/remove/edit FAX emails in FAX Devices.
* '''Fax2Email Email Template''' - [[Emails|email template]] to be used for Fax2Email emails. "None" means the default Asterisk template.
 

===CSV===

* '''CSV Column Separator''' – how columns are separated in imported/exported CSV files.
* '''CSV Decimal Separator''' – how decimal parts in numbers are separated in imported/exported CSV files.
* ''' Archive CSV file when size reaches''' – if CSV file reaches a certain size, the system will archive it to save time to download it (0 means to archive always)
 
===Active Calls===

* '''How many maximum [[Active_Calls|Active Calls]] to show in GUI''' – how many [[Active_Calls| Active Calls]] to show in GUI
* '''[[Active_Calls| Active Calls]] refresh interval''' – [[Active_Calls|Active Calls]] refresh interval in seconds
* '''Show [[Active_Calls|Active Calls]] for Users''' – tick if you want to allow users to see [[Active_Calls|Active Calls]]
* '''Show Servers in [[Active_Calls|Active Calls]]'''
* '''Show DIDs in [[Active_Calls|Active Calls]]'''
* '''Show localized Source in [[Active_Calls|Active Calls]]''' - if set, [[Active_Calls|Active Calls]] will show callerid number after localisations (if any) have been applied.
 

===Tariffs/Rates===

* '''Show rates for users''' – allows users to see rates
* '''Show rates without Tax''' – shows rates without TAX
* '''Show [[Advanced_Rates|Advanced Rates]] for users''' – allows users to see [[Advanced_Rates|Advanced Rates]]
* '''Show zero rates in LCR tariff export:''' – shows zero rates in LCR tariff exported file.
* '''Show Ghost percent column in Tariffs:''' – if enabled, the Ghost percent column will be shown in the tariff. Default disabled.
NOTE: if [[Custom Rates]] and/or Tariff Rates are set for the user, only the custom rates will be shown in the details of destination rates.
 

===Statement of Account===
* ''' PDF Settings ''' - allows to put Address lines of PDF file for Statement of Account.
*Address line 1: Street Address
*Address line 2: City, Country
*Address line 3: Phone, fax
*Address line 4: Web, email
*Bank details line 1
*Bank details line 2
*Bank details line 3
*Bank details line 4
*Bank details line 5
*Bank details line 6
*Bank details line 7
*Bank details line 8
 

==Privacy==

'''SETTINGS –> Setup –> Settings –> Privacy'''

* '''[[Privacy_to_hide_Destination_ends|Privacy to hide Destination ends]]'''
* '''[[GDPR]] Activated''' – hides User data with notification "Data hidden due GDPR. Press to show data (action will be logged)". Valid for Admin, Accountant, Reseller and Partner.

== Visual ==

'''SETTINGS –> Setup –> Settings –> Visual'''

* '''Items per page''' – the number of items to display per one page
* '''[[Global_date_format| Default date format]]''' – System default date format
* '''Default Time Format''' – System default time format
* '''Default Hour Format''' - System default hour format
* '''Number digits''' – how many digits to display after a comma
* '''Hide Quick Stats in Start page''' – hide Quick stats from start page
* '''Hide device passwords for users''' – do not display device passwords for users
* '''Hide "Information about this page" link''' – hide HELP banner in GUI
* '''Hide "I want to" help links'''
* '''[[Remove_Manual_link_from_admin_GUI|Hide "Manual" link]]''' – hides "Manual" link
* '''Show logo on first page''' - untick to hide logo on the start page
* '''Show Full Source (CallerID Name and Number)'''
* '''Use <> brackets in CDR export''' - changes brackets in CDR export
* '''Hide payment options for postpaid users''' - will hide the payment option for all postpaid users (including Resellers if they are postpaid).
* '''Hide non-completed payments for user''' – hides non-completed payments (the ones which are started in MOR, but are not completed in a payment gateway website)
* '''Show only main page''' – this is a very advanced feature for those who want to hide default MOR menu tree on the left so that they could build their own menu using advanced techniques without modifying MOR GUI sources.
* '''Show forgot password''' – turns on '''[[MOR_forgot_user_password | Forgot password]]''' functionality.
* '''Hide Recordings for all users''' – hides recordings for all system users from menu and device settings.
* '''Show recordings with zero billsec''' – shows recordings with zero billsec
* '''Default Number Decimal''' – with this option you can set default number decimal for all GUI
* '''Show user_billsec for Users instead of billsec''' – shows user_billsec instead of billsec in Users invoices and last calls. Notice that Billsec shows real Call duration, user_billsec shows Call duration after minimal time or increment applied. For example, if user tariff has 60 sec minimal time and user made a Call for 20 sec, then billsec will show 20 sec and user_billsec will show 60 sec (minimal time is applied).

* '''Show Calls statistics to User for last''' – number of Calls statistics to show in days. For example, if you enter 5 days, users will only see 5 days old calls, they will not be able to check older calls.
* '''Show Device and it's CallerID in Last Calls''' – shows additional column in [[Last Calls]] page with Device and its CallerID information. Click to reach that Device settings page..
* '''Allow User to assign DID to Device''' – lets User to assign DID to Device.
* '''Allow User to assign DID to Trunk''' – lets User to Assign DID to Trunk.
* '''Show DID User instead of Device User in Last Calls''' - if enabled, always shows DID User name in Last Calls.
* '''New Menu Active''' - if enabled, changes main menu to the new structure.
* '''Show Replication Broken warning only for Admin''' - if enabled, shows Replication Broken warning message only for Admin account.
* '''Dropdown field in User's subscriptions''' - enables old style Service selection in Subscription form.
* '''Show detailed Quick Stats''' - shows modified quick stats of first page.
* '''Show Terminated by in Last Calls''' - show Terminated By column in [[Last Calls]], calls CSV/PDF export, and adds the possibility to select this column in [[CDR Export Templates]].
* '''Show entered Destination only for Users''' - show the Destination numbers for Users that were entered by them and not Destination numbers after Localization.
* '''Show Company Name column in Users page''' - show "Company Name" column in Users list page.
 

== Server load ==

'''SETTINGS –> Setup –> Settings –> Server load'''
 
Settings for GUI Server and Database Server

* '''HDD utilisation higher than''' – Percentage of CPU time during which I/O requests were issued to the device (bandwidth utilization for the device).
* '''CPU General Load higher than''' – CPU General load higher than – Percentage of the CPU for user processes.
* '''CPU Load Stats 1 higher than''' – average load per one minute on the system
* '''CPU MySQL process higher than''' – Percentage of the CPU for MySQL process
* '''CPU Ruby process higher than''' – Percentage of the CPU for Ruby process
* '''CPU Asterisk process (if present) higher than''' – Percentage of the CPU for Asterisk process
* '''Delete Server Load Stats older than''' – deletes internal servers load statistics older than defined number of days.
 

== Calls ==

'''SETTINGS –> Setup –> Settings –> Calls'''
* '''Retrieve PCAP files from the Proxy Server''' – default off. Works only when CCL module is activated.

* '''SQL Max Execution Time''' - max execution time in seconds for SQL query. The default time is 300 seconds (5 minutes). Used in Statistics pages (Calls List export and similar).
 
[[Archived calls]]
 

== FTP ==
Please fill up FTP server details if you want to store Archived calls or/and Backups to FTP server.

* '''IP''' - Enter FTP server IP.
* '''Port''' - Enter FTP server Port.
* '''Username''' - Enter FTP server Username.
* '''Password''' - Enter FTP server Password.
* '''Path for Archived Calls''' - Enter Path for Archived Calls.
* '''Path for Backups''' - Enter path for Backups.
* '''Path for CDR Export''' - Enter path where to export CDRs.
 

== SFTP ==
Please fill up SFTP server details if you want to use SFTP for [[Automatic CDR Export]].

* '''IP''' - IP of the SFTP server.
* '''Port''' - Port of the SFTP server.
* '''Username''' - Username to connect to SFTP server.
* '''Password''' - Password to connect to SFTP server.
* '''Use SSH key''' - Use SSH key configured as described [[Configure SSH connection between servers|here]].
* '''Path for CDR Export''' - Path in SFTP server where to export CDRs.
 

== Security ==
* '''Allow short passwords in devices'''
* '''Use strong passwords for users'''
* '''Admin login with approved IP only''' - security measure which allows to approve IP's that try to [[MOR_Login_with_approved_IP%27s|login with Admin Account]].
* '''Enable IP report warning on login failure''' - show [[MOR_Login_Failure_Report|warning]] on unsuccessful login attempts.
* '''Logout after password change''' - terminates all sessions of the User whose password is changed.
* '''Logout after closing browser window''' - terminates all sessions of the User after closing browser window.
* '''Do not logout on session IP change''' - do not logout from MOR GUI if IP is changed.
* '''2FA Enabled''' - Enables two factors authentication. Two factors authentication requires to enter emailed code during login to user account. '''2FA Enabled must be also enable on individual [[User_Details|User settings]] to make it work for that User.'''
** '''Email Template''' - [[Emails|email template]] used to send the code.
** '''Code length (digits)''' - code length.
** '''Code Enter Attempts Allowed''' - number of attempts to enter the code correctly. Code expires after this number of failed attempts.
** '''Code Enter Time Allowed''' - code is valid for this amount of time.
** '''Send Notification Email to Admin on Login''' - allows admin to get email notification on login.
*** '''Email Template''' - [[Emails|email template]] used to notify admin.
*** '''On Admin Login''' - get notification on login to Admin's account.
*** '''On User Login''' - get notification on login to User's accounts.
** '''Send Notification Email on Login''' - allows this mailbox to get email notification on login.
*** '''Email Template''' - [[Emails|email template]] used to notify.
*** '''On Admin Login''' - get notification on login to Admin's account.
*** '''On User Login''' - get notification on login to User's accounts.
 

=See also=

* [[Server is overloaded]]