Kolmisoft Wiki - User contributions [en]

M4 Users

2022-07-12T11:44:53Z

Bogdan:

=Where to find user details?=

Go to '''SETTINGS –> Users'''

Here you can see list of all users.
 
[[File:M4_Users_path_2.png]]
 
Select the [[image:icon_edit.png]] icon in window above and you will reach personal User settings page. In this window you will see a lot of options grouped into sections.


'''NOTE''' that admin is not shown in Users list. To see your own details go to '''PERSONAL MENU –> Details'''.
 
Select the [[image:icon_edit.png]] Bulk management icon in a window above to access bulk management options.
 
[[File:M4_Users_path_bulk_management.png]]

= Details update =

Every User can update his own details in '''PERSONAL MENU –> Details'''. 
To disallow users to change their details Admin/Reseller has to check setting "Do not allow users to change their Personal Details" in '''SETTINGS -> Setup -> Settings -> Various'''. After this User Details can only be updated by user's owner. 
'''NOTE''' that even if User is not allowed to update his own details, he still can see it in '''PERSONAL MENU –> Details''' as form with not editable options.
 
= General =

* '''Status''' - indicates User status for accounting purposes. It is just a note and does not affect functionality in any way.
* '''Username''' – username for user to login to MOR GUI.
* '''Password''' – password for user to login to MOR GUI.
* '''Suggest strong password''' - secure password will be generated and filled in the password field.
* '''2FA Enabled''' - enables two factors authentication for this User. Only visible if 2FA is enabled in system settings.
* '''[[Balance and Credit | Balance]]''' – the user's balance.
* '''Balance range''' – minimal and maximal balance which User will be able to have.
* '''[[Minimum contract billing | Minimal Charge for Calls]]''' – minimum charge user pays for voice calls.
* '''[[Minimum contract billing | Minimal Charge for Calls Date]]''' – date since when the previous option is valid.
* '''[[Hide Users | Not Hidden/Hidden]]''' – is this user hidden?
* '''[[Simultaneous call limitation | Call Limit]]''' – how many simultaneous calls the user can make?
* '''Max Call rate''' - set maximum allowed rate (price per min) when making calls (0 - unlimited).
* '''Price Protection''' - set User's Price Protection method.
** '''Off''' - Price Protection disabled (default)
** '''Minimal Rate Margin''' - if margin is lower than this value, call will fail with [[Rate margin is lower than allowed|HGC 324 - Rate margin is lower than allowed]]
** '''Minimal Rate Margin Percent''' - if margin percent is lower than this value, call will fail with [[Rate margin is lower than allowed|HGC 324 - Rate margin is lower than allowed]]
* '''Default Currency''' – User's default Currency
* '''Time Zone''' – User's native Time Zone
* '''Time Format''' – Available options - '''Default''' from general settings, '''H:M:S''', '''M:S'''. The option is taken into account when showing the user info on the GUI and creating invoices for the user.
* '''Responsible Manager''' – dropdown to choose Manager responsible for this User. (only Admin can set Responsible Manager)
* '''PBX Pool''' – PBX pool assigned to User
* '''Hide Non-Answered calls''' – with this option enabled simple user sees only answered calls in [[Last Calls]] and in Detailed Statistics page. 
* '''Ignore Global Alerts''' – check and User will be ignored on checking for [[M2_Alerts | Alerts]]
* '''Show Hangup Cause''' – allow User to see numeric hangup cause value (for example '''FAILED (41)''' instead of '''FAILED''').
* '''Round Call Price in CDR''' - Yes or No. This is not a visual setting. For E.g. Call Price will be saved in CDR rounded by these settings.
* '''Digits used for Price''' - round the call price to this many decimal places.
* '''Rounding method''' - rounding method to use for the call price.
* '''Rate Notification Template''' - [[Rate Notifications | select desired template]]'''
* '''Hide financial data in Quick Stats''' - if enabled, financial data in Quick Stats will be hidden.
* ''' Show Calls Statistics for last''' - allows to set a day amount limit on shown calls statistics.
 

= Fraud Protection =
* '''Enforce Daily Limit''' - enable or disable Fraud Protection.
* '''Daily Spend Limit''' - limit in User's currency. When Daily Spend Limit value reached, the User cannot make more calls. Daily Spend Limit value is reset at midnight in the User's time zone.
* '''Daily Spend Warning''' - the User will receive an email with a warning message once set value reached.
* '''Kill Calls In Progress''' - kill all User's calls when Daily Spend Limit reached.
* '''Show Daily Limit''' - the User will see Daily Spend Limit in his account dashboard.
* '''Allow Customer To Edit''' - the User can set his Fraud Protection Daily Spend Limit value.
* '''Kill All Calls Now''' - all User's calls will be terminated.
 

= Blocking =

Various options for [[User Blocking]].
 
= Warning Balance Email =

If you want to get and email notification or send it to a User and Accountant (or take another action) when his balance drops lower than a certain amount, check this setting and enter the desired amount.

More details: [[M2 Warning Balance | Warning Balance]]
 

= Invoices =

* '''Generate Invoice automatically''' – should we generate Invoices for this User automatically based on set Billing Period?
* '''Generate Invoice manually''' - should this user be included when we generate Invoice manually with option "All Users"?
* '''Billing Period''' – select period for which Invoice should be generated.
* '''Grace Period''' – select period for which Invoice should be paid by User. For example, if you generate Invoice for January 1-31, and you set Grace Period 15 days, then User will see Due Date February 15 (15 days after Invoice period end).
* '''Create Invoices on Manual Payments''' - generate an Invoice when a new [[M2 Payments | Payment]] (of type Payment from Client) is made. An invoice will be sent to the User's email and will be listed in the Invoice list. It is not possible to recalculate such an invoice.
 

== Static Invoice Billing Period time ==
[[File:InvoicesStaticPeriod.png]]
 

Static Billing Period time can be set to one of these values: Weekly, Bi-weekly, Monthly, Bimonthly, Quarterly, Half-yearly.

Once the Period will be selected, information will be displayed about the First Day of the Period, the Last Day of the Period, and the Invoice creation date.

==Every X days in Dynamic Periodic type==

[[File:Everyxdaysm2.png]]
 
Dynamic Periodic Type allows selecting flexible billing periods.
If '''Generation time:''' is set to 24 hours (default value), Invoice will be generated at midnight (00:00), at today + period day(s) + 2.

For example, let's say today is 2018-09-06 and we choose parameter '''From date''' 2018-09-06 and parameter '''every 4 days''' and '''Generation time:''' 24 hours (default value).
System will start to generate the invoice at 2018-09-11 00:00:00 and invoice will be generated for period 2018-09-06 and 2018-09-09.
Next invoice generation will begin at 2018-09-15 and period for this invoice will be 2018-09-10 and 2018-09-13.

If '''Generation time:''' is less than 24 hours, invoice will be generated at selected hour, at today + period day(s) + 1 day + Generation time. This is handy if we want to generate invoice for each day.
For example, let's say today is 2018-09-06 and we set parameter '''From date''' 2018-09-06 and parameter '''every 1 days''' and '''Generation time:''' 23 hours.
Invoice will be generated for 2018-09-06 00:00:00 - 23:59:59 at 2018-09-07 23:00:00. Next invoice will be generated at 2018-09-08 23:00:00 for 2018-09-07 00:00:00 - 23:59:59 and so on.
 

= Documents =
Here Admin can upload documents for simple Users. Each document can have a comment made by Admin. Admin can upload, download and delete documents for simple Users.

Simple users can see these documents under their '''Personal Details''' menu. Simple User can only download documents, it is not possible to delete or upload new Documents for him/her.
 
[[File:documents_admin.png]]

= PayPal =
[[File:M2_users_paypal.png]]

* '''Allow PayPal''' - enable or disable PayPal payments for user. If enabled, PayPal will be displayed on the user's dashboard.
* '''Need Approval''' - if enabled, the user's balance will be updated only when the admin confirms the payment.
* '''Credit Entered Amount''' - credit entered amount minus the calculated fee.
* '''Credit Net Amount''' - amount returned by PayPal minus the calculated fee.
* '''Charge Fee on Entered Amount''' - amount in percent.
* '''Charge Fee on Net Amount''' - amount in percent.
* '''Do not send confirmation email''' - if enabled, a confirmation email is not sent to the user.

 
= Details =

Self-explanatory.

If Country of Taxation is in the EU, validation of TAX Registration Number will be checked from this website: http://ec.europa.eu/taxation_customs/vies/
 
= Company Emails =

Self-explanatory:

* '''Main email'''
* '''NOC email'''
* '''Billing email'''
* '''Rates email'''
 
= Taxes =

Here tax parameters are entered for the user.

The tax system is explained [[Multi-Tax system | here]].
 
= Registration Address =

Self-explanatory.

'''NOTE:'''

From version 2.255, '''Email''' field was removed. All entered email addresses are moved to '''Main Email''' field in section '''Company Emails'''.

 

=Blacklists / Whitelists=

'''Enable static Source''' - enables static Blacklist or Whitelist 
* '''No''' - do not use any Blacklist or Whitelist
* '''Blacklist''' - choose [[Number Pool]] which will be used to block calls sent by User specific Source numbers. If User sends CallerID number which is in selected [[Number Pool]] then call will be hangup with hangupcause ''334 - Source number is in blacklist''
* '''Whitelist''' - choose [[Number Pool]] which will be used to allow User to send only specific Source numbers. If User sends number which is NOT in selected [[Number Pool]] then call will be hangup with hangupcause ''335 - Source number is not in whitelist''

'''Enable static Destination''' - enables static Blacklist or Whitelist 
* '''No''' - do not use any Blacklist or Whitelist
* '''Blacklist''' - choose [[Number Pool]] which will be used to block User from calling specific Destination numbers. If User calls number which is in selected [[Number Pool]] then call will be hangup with hangupcause ''325 - Destination is in blacklist''
* '''Whitelist''' - choose [[Number Pool]] which will be used to allow User to call only specific Destination numbers. If User calls number which is NOT in selected [[Number Pool]] then call will be hangup with hangupcause ''326 - Destination is not in whitelist''
 
'''Note:''' when using Number Pools for Blacklist/Whitelist, it is possible to upload prefixes. To do so, just import prefixes with percent sign at the end (example: 370% will act as prefix for 370xxxxxxxx number).
 
'''Important:''' Blacklists / Whitelists work for Originator only. They will not work for Terminator.

Data import

2022-07-12T09:39:56Z

Bogdan:

= User/Device/DID/CLI import =

You must import the data in the following order '''from CSV files''':

1. Users data 
2. Devices data 
3. DIDs data 

'''Import Devices from CSV''' link is disabled while Users data is not imported. '''Import DIDs from CSV''' link is disabled while Devices data is not imported.

CLIs data can be imported for already existing Devices by Device ID or for just imported Devices by Temporary Device ID (which is in '''SETTINGS -> Users -> Import''').

Functionality is available for '''Admin''' and '''Reseller'''.

== CSV file format ==
 
'''Please note that such details like tariff, LCR, IDs should be specified in csv instead names.'''

Example you have LCR called "My first LCR" this LCR ID is 2. You should specify in csv 2, but not My first LCR.

Other way if you will not specify ID system will not find it.

You can upload your data from a CSV file that has the following structure: 
1. Each record is started in a new line. 
2. Each piece of record information is separated by commas (see the example). 
3. Text is enclosed within inverted commas (for example: "name"). 
4. Numbers are written without inverted commas (for example: 4). 
5. The first line can be used for your own needs, such as for naming each field of information. '''If you use this line, do not select the "include first line?" option when asked.
'''

'''For example:''' 
We have a CSV file named '''example.csv''' with the contents:

"id", "username", "password", "e-mail" 
1, "username1", "verySecretPassword", "example@example.com" 
2, "username2", "34r34r4232", "example2@example.com" 
3, "username3", "23er29923wjwe", "example3@example.com" 

'''Explanation:''' 
The '''first line''' is used in this case for naming the fields, so '''when asked, do not select the "include first line?"''' option. (If you won't use the first line for '''naming the fields''', please do select '''"include first line?")''' 
The other three lines (starting 1, 2, 3) are for data records. Each record (the first one is: 1, "username1", "verySecretPassword", "example@example.com") represents: 

1 - user id. 
"username1" - user's username. 
"verySecretPassword" - user's password. 
"example@example.com" - user's e-mail. 

Your CSV file can have any number of lines with any number of fields ('''each line must have the same number of fields''').

P.S. The file should not have any other symbols than those mentioned above. Be careful, as some editors can add their own formatting symbols. In Windows we recommend using Notepad, and in Linux: gedit, kedit, nano.

'''Here are some examples:'''

'''Users CSV file example:''' 

38,2,0,"NULL","NULL",TRUE,"11420471-2-03","Example ZRt","Example ZRt","example example. 11","76/356-650","example@example.hu",04/06/07 01:48 PM," ","en",97,20,0,FALSE,TRUE,5,0,04/06/07,"NULL","NULL",0,FALSE,04/06/07,"Lajosmi",6050,1,0,1,1,TRUE,"NULL","NULL",3 
45,2,0,"95757bfa00bf85b17921d709b5af0234","NULL",TRUE,"12969247-2-03","Example Ákos","Example Example, Kft","Example's 38","70/235-45-89","example@example2.hu",04/06/09 11:28 AM," ","en",97,20,0,FALSE,TRUE,5,0,04/07/09,"NULL","NULL",0,FALSE,04/06/09,"Kecexample",6000,1,0,1,1,TRUE,"NULL","NULL","NULL" 
2138,2,0,"cc1b3ae8986559b10786d6ea73912bd5","NULL",TRUE,"11871633-2-03","Kos Tas","Ks Kft","Alsó ast","20/229-36-78","pli@example.hu",12/13/07 09:42 AM," ","en",97,20,0,FALSE,TRUE,5,0,12/13/07,"NULL","NULL",0,FALSE,12/13/07,"Sirly",6031,1,0,1,1,TRUE,"NULL","NULL","NULL"

In the first column is a Temporary User's ID; the other columns represent other data. As mentioned above, it does not matter in which order your data is represented in the CSV file. It only matters that each column (the data between commas) represents the same data value (id, email, password or other).

"Blocked" column accepts values "1", "y", "true", "yes", "block" or "blocked". These values will result in imported User being blocked. Any other or empty value will result in User not being Blocked.

'''Devices CSV file example:'''

38,38,76824435,"3676586421","asd dsa u.12","jamaica","7ewfw@sip.example.com",TRUE,"dynamic","sip",TRUE,"NULL","NULL","NULL","NULL","NULL","NULL","NULL","NULL","NULL","NULL","NULL","NULL","NULL","NULL" 

45,45,76846301,"3676886421","fgh hgf u.","ergerSiP","76886421@sip.example.com",TRUE,"dynamic","sip",TRUE,"NULL","NULL","NULL","NULL","NULL","NULL","NULL","NULL","NULL","NULL","NULL","NULL","NULL","NULL" 

2138,2138,76505921,"3676505921","jkl lkj u.12","treK","6654@sip.example.com",FALSE,"dynamic","sip",TRUE,"NULL",FALSE,FALSE,10,FALSE,FALSE,FALSE,FALSE,FALSE,FALSE,FALSE,FALSE,,FALSE

The first column here represents "id", the second "user_id", and the others represent other data. YOUR ORDER CAN BE DIFFERENT. The main thing is that each type of data (email, password, id...) must be in the same column. When you are asked to provide data when importing, be sure to assign the correct data from CSV for each column and MOR will know which column represents which data.

'''Dids CSV file example:'''

37067531061,38,38 
37065431061,45,22 
37062431031,2138,2138 

In this example I have used the first column for DID, the second for Temporary User ID, and the third for Temporary Device ID. Your data order can be completely different. You just need to select the correct values when asked.

== Importing data ==

Firstly, from the MOR Graphical User Interface (GUI), navigate to: '''Settings -> Users -> Import''', as in the picture:
 
[[Image:Imports_menu.png|alt import_menu]]
 
=== Temporary User ID & Temporary Device ID ===

These fields are necessary to map DIDs to Devices and Devices to Users.

Temporary IDs can be integer digits only.

Example:

You have some other system with some user_ids, device_ids, DID_ids. You export them into CSV files. The relations between them are kept by these IDs, so importing them to MOR will keep these relations.

First you need to import a User with some temporary ID, then make sure this ID is near each Device you are trying to import. Select this ID as Temporary User ID when importing Devices. That way these devices will be mapped to this User.

== Importing users ==

To import users, click on the "Import Users from CSV" link:
 
[[Image:Imports_users_selection.png|alt Imports_users_selection]]
 
Now locate the CSV file in your local system by clicking the "Browse" button. As indicated above, don't click the "Include first line?" checkbox if you have used the first line for commenting on the fields.
 
[[Image:Upload_csv_file.png|alt upload_csv_file]]
 

'''Click on the "Upload file" button.'''

In next menu, please fill in the requested data (you should select the correct field from your CSV file). '''You must select a field for each selection box marked with an asterisk (*) symbol'''. Having finished, press the "Assign columns" button.
 
[[Image:User import.png|alt select_fields]]
 
On the next page, check whether all the data was assigned correctly. If not, click the "Back" button and correct the mistakes. If all the data was assigned correctly, click the "Confirm columns" button. After the "Columns assigned" notification informs you that data successfully imported.

'''NOTE:''' When you are going to import CSV file, which includes Tariff and/or LCR, the '''IDs''' of Tariff and LCR should be specified in CSV file.

Where to find ID of Tariff or LCR? Just go to some of them and press on edit icon, where Browser navigator bar will show full link with location, last number is ID.

'''NOTE:''' In the Payment type section you have to select do you want to upload prepaid or postpaid user. In CSV file 1 stand for postpaid user, 0 for prepaid user. By default, if Payment type is not select all users will be uploaded as prepaid users.

Having completed all these steps, you should see a page similar to this:
 
[[Image:Users_imported.png|alt Users_imported]]
 

== Importing devices ==

Click on the "Import Devices from CSV" link and follow the same procedure for uploading a CSV file as in the "Importing users" section. That is, locate the CSV file in your local system by clicking the "Browse" button. As stated before, don't click the "Include first line?" checkbox if you have used the first line for commenting on the fields. Click on the "Upload file" button. Now you should see a menu similar to this:
 
[[Image:Device_selection.png|alt device_selection]]
 
In this menu, once again select a matching field from your CSV file for each selection box. '''It is very important to correctly select Temporary User ID and Temporary Device ID, because these fields are necessary to map DIDs to Devices and Devices to Users.'''

'''NOTE:''' When you are going to import CSV file, which includes Location, the '''name''' of Location should be specified in CSV file.

Having finished selecting the fields, press the "Assign columns" button.

Once the columns are assigned, check whether all the data is correct. If not, press the "Back" button and correct the mistakes. Now, if you haven't made any mistakes, you should see two tables similar to these:
 
[[Image:Users_devices_tables.png|alt users_devices]]
 

== Importing DIDs ==

Click on the "Import Devices from CSV" link and follow the same steps for uploading a CSV file as in the "Importing users" section. That is,
locate the CSV file in your local system by clicking the "Browse" button. As stated before, don't click on the "Include first line?" checkbox if you have used the first line for commenting on the fields. Click on the "Upload file" button. Now you should see a menu similar to this:
 
[[Image:Dids select.png|alt dids_selection]]
 
Select all matching fields from your CSV here. It is very IMPORTANT to select the CORRECT Temporary User ID and Temporary Device ID! Having selected everything correctly, click the "Assign columns" button. In the next page, if all imported data is assigned correctly, click the "Confirm columns" button. If you haven't made any mistakes, you should now see a "DIDs successfully imported" message.

== Importing CLIs ==



CLIs data can be imported for already existing Devices by Device ID or for just imported Devices by Temporary Device ID.

Click on the "Import CLIs from CSV" link and follow the same steps for uploading a CSV file as in the "Importing users" section. That is, locate the CSV file in your local system by clicking the "Browse" button. As stated before, don't click on the "Include first line?" checkbox if you have used the first line for commenting on the fields. Click on the "Upload file" button. Now you should see a menu similar to this:
 
[[Image:CLIs select.png|alt clis_selection]]
 
Select all matching fields from your CSV here. It is very IMPORTANT to select the CORRECT Device ID (if it is selected "Use Device ID") or Temporary Device ID(if it is selected "Use Temporary Device ID")! Having selected everything correctly, click the "Assign columns" button. In the next page, if all imported data is assigned correctly, click the "Confirm columns" button. If you haven't made any mistakes, you should now see a "CLIs successfully imported" message.

You can now check whether all your data has been imported.

To check users, go to: '''SETTINGS –> Users'''.

To check devices, go to: '''SETTINGS –> Users –> Devices'''.

To check DIDs, go to: '''SETTINGS –> Billing –> DIDs'''.

To check CLIs, go to: '''SETTINGS –> Billing –> Devices –> CLIs'''.
 
[[Image:Dids devices users.png|alt dids_devices_users]]
 

= Explanation of IDs =

Many users find it difficult to understand what User_ID or Device_ID mean in Data Import.

These are temporary IDs created only for import purposes. '''These IDs have NO relation to User ID/Device ID in the Users/Devices windows of the MOR system.'''

The workflow of Import is:

1. We have Users/Devices/DIDs.

2. We create a separate file with Users and add a unique ID to every User. The ID is NOT related to User ID in MOR DB/GUI.

3. We create a separate file with Devices and add a unique ID to every Device. The ID is NOT related to Device ID in MOR DB/GUI. Near each device we add a temporary User ID from previous file, which shows which Device belongs to which User.

4. We create a separate file with DIDs and near each DID add a User_ID/Device_ID that shows which DID belongs to which User/Device.

5. We import the User file, and MOR remembers the temporary User_ID.

6. We import the Device file, and MOR remembers the temporary Device_ID and checks the User_ID for such Devices which have a User_ID near them in the file. It assigns this Device to the appropriate User.

7. We import the DID file. MOR checks the Device_ID/User_ID in the DIDs file and assigns a DID to this Device/User.

8. We import the CLI file. If during import there is selected "Use Temporary Device ID " MOR checks the Device_ID in the CLIs file and assigns a CLI to this Device. If it is checked "Use Device ID" MOR checks the ID of Device in the CLIs file and assigns a CLI to this Device

NOTE: in all processes, only a TEMPORARY User_ID/Device_ID is used. In the database, Users' ID/Devices' ID are not used directly. They have no relation to the User_ID/Device_ID from import files.

= See also =

* [[Export Users and Devices]]

M4 Termination Points

2022-04-05T10:46:54Z

Bogdan:

=Description=

Termination Point is connection to some final entity (device/line/trunk/provider/supplier/etc) where call will be terminated.

Call comes from [[M2 Origination Points | Origination Points]] and goes to Termination Point.

Termination Points are assigned to [[M2 Dial Peers | Dial Peers]]. 

==Timeouts==

* '''Progress Timeout''' – allows to limit the maximum time we will wait before we get media (whether it's early media, ringing or answer). Leave 0 for unlimited.
* '''Ringing Timeout''' – allows to limit the ringing duration in seconds. Leave 0 for unlimited. Minimal value is 10 seconds.
* '''Call Timeout''' – allows to limit answered call duration. Leave 0 for unlimited.

==Termination Point==
[[File:TerminationPoint.png]]
* '''Act as Termination Point''' - turns on/turns of Termination Point. If selected No and saved, all settings of Termination Point will be erased. 
* '''Active''' - activates/deactivates Termination Point. 
* '''Source Transformation''' - special [[M2 Source Transformation | Source Transformation]] rules used to modify Source number. 
* '''Destination Transformation''' - special [[M2 Destination Transformation | Destination Transformation]] rules used to modify outgoing number. 
* '''Capacity''' - limits the number of concurrent calls to this termination point. 
* '''Source (CallerID) Allow''' - regular expression (regexp) for CallerIDs that are allowed to go through this termination point (use regexp '''.*''' if you want to allow all CallerIDs to go through this termination point). 
* '''Source (CallerID) Deny''' - regular expression (regexp) for CallerIDs that are NOT allowed to go through this termination point (leave empty if you do not want to disallow any CallerIDs). 
* '''Register''' - should we register the provider? This option is not available on M4 yet 
* '''From Domain''' - field is active only whent Register is enabled 
* '''[[M2 Mobile Number Portability|MNP]] Carrier Group''' - name of [[M2 MNP Carrier Groups | MNP Carrier Group]] 
* '''Authentication - Enabled/Disabled''' - When Enabled, login and username data can be entered.
* '''Login/Username''' - username if your provider asks for it. 
* '''Password''' - password used for authentication by your provider. 
* '''USA Jurisdictional Routing''' - Jurisdictional routing is telephone call routing logic based upon the locations of the calling and called number and regulatory considerations. '''Can be enabled by Kolmisoft only. Please contact support to enable.''' More information can be found here [https://transnexus.com/whitepapers/jurisdictional-routing Here]
* Intra Tariff- Tariff for Intrastate routing. Calls between two points within the same state
* Inter Tariff - Tariff for Interstate routing. Calls made from one state to another
* Indeter Tariff - Tariff for Invalid ANI, or indeterminate routing. Calls where the calling number is any value other than a valid telephone number—these are usually rated at the intrastate rate

==Termination Point Tariffs==
[[File:TerminationPoint_Tariffs.png]]
* '''Tariff''' - Tariff used for Termination Point accounting. 
* '''Use Tariffs by CLIs''' – disabled by default. 

==Codecs==

Define which Codecs will be offered when dialing Terminator (in the order they are listed).

* '''Enforce leg A Codecs to leg B''' - if this option is enabled in Terminator settings, M2 will ignore selected Terminator Codecs and will offer the same Codecs (in same order) from leg A to leg B. More information can be found [[M2 Codec Negotiation | here]].

== CallerID ==

* '''Name''' - set name part for CallerID. 
* '''Number''' - set number part for CallerID. 
* '''Random Number from Number Pool''' - set random number from Number Pool. Only number part for CallerID is set.
** '''Random''' - Send random CallerID from Number Pool.
** '''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.

== Advanced Settings ==

* '''Grace Time''' - Grace time in seconds.
* '''Custom SIP Header''' - adds custom header to SIP request. Format is header: value (for example x-My-Custom-Header: my value). Do not omit space after colon character.
* '''Limit up to X Calls, during Y seconds''' - allows to control Calls per Second (CPS). 
* '''Disable Q.850 Reason''' - by default M2 returns Q.850 Reason header in SIP responses to Originator. This can be disabled by setting this option to "yes".
* '''Bypass Media''' - when set, the media (RTP) from the originating endpoint is sent directly to the destination endpoint and vice versa. The signaling (SIP) for both endpoints still goes through M2, but the media is point-to-point.

== Advanced Termination Point Settings ==

* '''Interpret NO ANSWER as FAILED''' - makes NO ANSWER calls interpretation as FAILED. 
* '''Interpret BUSY as FAILED''' - makes BUSY calls interpretation as FAILED 
* '''Periodic check''' - if enabled, periodic SIP OPTIONS requests will be sent to Termination Point to check if it is reachable. If Periodic Check is enabled and Termination Point does not respond to OPTIONS request then Termination Point will be marked as unreachable and will be skipped with '''HGC 324 - Unreachable Terminator skipped (Periodic Check is enabled)''' when making calls. Once Termination Point starts to respond to OPTIONS request it will be marked as reachable and calls will be routed through this Termination Point. Termination Points are checked every 5 minutes. If Periodic check is enabled, and Termination Point IP is reachable, in [[M2_Connection_Points|Connection Points]] window IP will be in green color. If Termination Point IP is NOT reachable, its IP will be in red color, also UNCREACHABLE icon near IP will appear in Termination Point edit window. 
* '''Sticky Contact''' – if this option is enabled, M2 uses only first SIP Contact header received from Termination Point. Sometimes Terminators change Contact header in the middle of SIP dialog and in some cases this may lead to unpredicted behavior (for example Terminator changes Contact header to wrong address and calls do not terminate properly). Use this option only if you know what you are doing. This option applies only to Termination points.
* '''Disable SIP URI encoding''' - enable or disable SIP URI encoding. If enabled, then some characters in SIP URI (Invite, To) are encoded in percent-encoding. For example if you send number 123#99999, encoded SIP URI will be sent to Provider as 123%2399999 (note that # is replaced by %23). If your Provider does not accept encoded SIP URI, you may disable this feature and characters like # will not be encoded.

== Termination Point Signaling Settings ==
* '''Remote-Party-ID to TP''' - same options as for ''' P-Asserted-Identity to TP''' below. These options are identical both for Remote-Party-ID and for P-Asserted-Identity and so only P-Asserted-Identity will be described below
* ''' P-Asserted-Identity to TP''' - allow manipulation P-Asserted-Identity headers before sending them to TP. Available options are: [[File:Pai_to_tp.png]] 
** '''Drop''' - drop (do not send) header to TP.
** '''Forward''' - Forward header from OP to TP.
*** '''PAI from OP Transformation:''' - Optional regex to transform header before forwarding. [[M4 Transformations | More info]].
** '''Generate if missing''' - Generate header if it is missing.
*** '''PAI from OP Transformation:''' - Optional regex to transform header before forwarding if header is '''not''' missing. [[M4 Transformations | More info]].
*** '''PAI Generation:''' - PAI header value to genrate if header '''is''' missing. [[M4 PAI And RPID Header Generation| More info]].
** '''Overwrite''' - Overwrite header value with a new one.
*** '''PAI Generation:''' - PAI header value to generate which will overwrite existing PAI. [[M4 PAI And RPID Header Generation| More info]].
* '''Send PAI Number as CallerID (From:) to TP:''' - available options are: Never, Always, If FROM is Anonymous, If FROM is not Anonymous, By OP (uses Origination Point setting).

This setting depends on the same setting from the OP. The logic is described below:

[[File:Send pai table.png]]

* '''Ignore SIP 183 without SDP''' - by default disabled. Select '''Yes''' to enable the option.
* '''Ignore SIP 180 after 183''' - by default disabled. Select '''Yes''' to enable the option.
* '''Disconnect Codes Group:''' - Disconnect Codes Group to use. More information available [[M4 Disconnect Codes|here]].

== Subnetting ==

It is possible to set [http://en.wikipedia.org/wiki/Subnetwork subnetwork] for Termination Point. Instead of IP address, you can set subnet in '''IP Address''' input field. Subnet should be written in [http://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing CIDR notation] (for example 192.168.0.1/28). When call is routed through Termination Point which uses subnet, '''random''' IP address from that subnet will be chosen for outgoing call.

M2 subnet value range is 4-30.
 
You can use online subnet [http://www.aboutmyip.com/AboutMyXApp/SubnetCalculator.jsp? calculator] to check first and last usable IP address from given subnet.

== IP range ==

If you need to set multiple IP addresses for single Termination Point and Subnetting does not meet your needs, then you can set IP ranges. Ranges are written in the following format:

xxx.xxx.xxx.xxx-yyy

Note that you can set range only for last octet in IP address. 

When call is routed through Termination Point which uses IP range, '''random''' IP address from that range will be chosen for outgoing call. For example, if we have IP range 192.168.0.100-150, then random IP address from range 192.168.0.100 - 192.168.0.150 will be generated. 

=See also=

* [[M2 Disconnect Code Changes|Disconnect Code Changes]]
* [[NO_ANSWER/BUSY_interpretation_for_providers]]

Centos 6 repositories does not work anymore

2021-11-11T08:42:17Z

Bogdan:

In file /etc/yum.repos.d/CentOS-Base.repo, comment out "mirrorlist" lines and add new "baseurl" lines.
File should look like:

# CentOS-Base.repo
#
# The mirror system uses the connecting IP address of the client and the
# update status of each mirror to pick mirrors that are updated to and
# geographically close to the client. You should use this for CentOS updates
# unless you are manually picking other mirrors.
#
# If the mirrorlist= does not work for you, as a fall back you can try the
# remarked out baseurl= line instead.
#
#

[base]
name=CentOS-$releasever - Base
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
baseurl=https://vault.centos.org/6.10/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

#released updates
[updates]
name=CentOS-$releasever - Updates
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/updates/$basearch/
baseurl=https://vault.centos.org/6.10/updates/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

#additional packages that may be useful
[extras]
name=CentOS-$releasever - Extras
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/
baseurl=https://vault.centos.org/6.10/extras/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

#additional packages that extend functionality of existing packages
[centosplus]
name=CentOS-$releasever - Plus
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=centosplus&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/centosplus/$basearch/
baseurl=https://vault.centos.org/6.10/centosplus/$basearch/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

#contrib - packages by Centos Users
[contrib]
name=CentOS-$releasever - Contrib
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=contrib&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/contrib/$basearch/
baseurl=https://vault.centos.org/6.10/contrib/$basearch/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

If repositories does not work after changes, run these commands:
yum clean all
yum makecache

If this does not help run:

yum update ca-certificates

If it gives such error:

[Errno 14] Peer cert cannot be verified or peer cert invalid. Trying other mirror…

In /etc/yum.conf in the [main] section add:

sslverify=false

And check that in the /etc/yum.repos.d/CentOS-Base.repo there are paths with https (if not, change from http to https) and retry yum update ca-certificates

If all ok - change https->http back (if you changed http->https before). And remove sslverify=false from /etc/yum.conf

Centos 6 repositories does not work anymore

2021-01-21T09:46:17Z

Bogdan:

External Recordings Server

2020-04-28T10:33:02Z

Bogdan:

=Configuration=

External Recordings Server allows to convert and store Recordings in external server thus increasing storage space on switch server (Asterisk). It will also reduce load on switch server because wav to mp3 convertion is executed in external server.

 
<big><big>'''NOTE: Configuration applies ONLY for fresh CentOS 6 server.'''</big></big>

 
==Configuration in GUI==

External Recordings Server can be configured in '''ADDONS -> Recordings -> Settings'''

[[File:Recordings external server.png]]

Check 'User external Server' checkbox, enter external server IP, SSH port and login username. 

'''NOTE: make sure that servers are configured with SSH keys! Login by password will not work for External Recordings Server.''' 
External recordings server must be accessible using both root (/root/.ssh/id_rsa) and special GUI /var/www/.ssh/id_rsa) SSH keys.
Just execute script below and it will check SSH keys and connectivity and will print exact command you need to enter for correct configuration. Make sure that External Recordins Server details: (IP, Port, Login) are already entered as shown in sreenshot above before executing these commands:
svn update /usr/src/mor
On Centos 6:
/usr/src/mor/x15/maintenance/test_fix_scripts/gui/check_gui_recordings_server_access.sh
On Centos 7:
/usr/src/mor/x15/maintenance/test_fix_scripts_c7/gui/check_gui_recordings_server_access.sh
 
In '''SETTINGS -> Billing -> Servers''' add new server, where

"Hostname for SIP" and "Server IP for SIP" are External Recordings Server IP,

"Type" is "Other",

"GUI" and "DB" are disables (red cross).
 

==Configuration in Database server==

In Database Server create MySQL user for External Recordings Server:

CREATE USER 'mor'@''''IP_OF_RECORDINGS_SERVER'''' IDENTIFIED BY 'mor';
GRANT ALL PRIVILEGES ON `mor`.* TO 'mor'@''''IP_OF_RECORDINGS_SERVER'''' WITH GRANT OPTION ;

 

==Configuration in External Recordings server==

1. Install required packages and dowload sources:

yum -y install subversion gcc wget perl-IO-Socket-SSL
svn co http://svn.kolmisoft.com/mor/install_script/trunk/ /usr/src/mor

2. Install Apache (change MOR version accordingly in the script):

/usr/src/mor/x15/gui/apache_install.sh
/usr/src/mor/x15/gui/apache_uid_fix.sh
iptables -F
/etc/init.d/iptables save

3. Install MySQL (change MOR version accordingly in the script):

/usr/src/mor/x15/mysql/mysql_install.sh

4. Create needed directories and permissions:

mkdir -p /var/log/mor
chmod 777 -R /var/log/mor
mkdir -p /etc/mor/
mkdir -p /var/lib/asterisk/agi-bin/
mkdir -p /usr/local/mor/recordings/
chmod 777 -R /usr/local/mor/

5. Install scripts (change MOR version accordingly in the script):

cd /usr/src/mor/x15/scripts/

gcc -Wall -Wunused -g -I/usr/include/mysql mor_record_remote.c -o mor_record_remote -lmysqlclient -lnsl -lm -lz -L/usr/lib/mysql -L/usr/lib64/mysql
cp -fr mor_record_remote /usr/local/mor

gcc -Wall -g -I/usr/include/mysql mor_record_control.c -o mor_record_control -lmysqlclient -lnsl -lm -lz -L/usr/lib/mysql -L/usr/lib64/mysql
cp -fr mor_record_control /usr/local/mor

gcc -g -Wall -o mor_delete_old_recordings mor_delete_old_recordings.c -L/usr/lib/mysql -L/usr/lib64/mysql -lmysqlclient -lm
cp -fr mor_delete_old_recordings /usr/local/mor/

gcc -Wall -g -o mor_server_loadstats mor_server_loadstats.c -L/usr/lib/mysql -L/usr/lib64/mysql -lmysqlclient -lpthread
cp -fr mor_server_loadstats /usr/local/mor/mor_server_loadstats
cp -fr mor_server_loadstats_service /etc/init.d/mor_server_loadstats
chmod +x /etc/init.d/mor_server_loadstats
chkconfig --add mor_server_loadstats
chkconfig --level 2345 mor_server_loadstats on

cp -fr cronjobs/mor_delete_old_recordings /etc/cron.d/
service crond restart

cp -fr sendEmail /usr/local/mor/

6. Install Lame (change MOR version accordingly in the script):

/usr/src/mor/x15/helpers/lame_install.sh

7. Symlink directories:

ln -s /usr/local/mor/recordings /var/www/html/recordings

8. Create configuration files:

Create file:

vi /etc/mor/system.conf

Enter:

# database connection settings
dbhost = '''Database_server_IP'''
dbname = mor
dbuser = mor
dbsecret = mor
dbport = 3306

server_id = '''unique server ID; same as on GUI'''

Save file.

Create file:

vi /var/lib/asterisk/agi-bin/mor.conf

Enter:

host = '''Database_server_IP'''
db = mor
user = mor
secret = mor
port = 3306

Save file.

9. Edit ''/etc/httpd/conf/httpd.conf''

Change from:

<Directory />
Options FollowSymLinks
AllowOverride '''None'''
</Directory>

To:

<Directory />
Options FollowSymLinks
AllowOverride '''All'''
</Directory>

And change from:

# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
AllowOverride '''None'''

To:

AllowOverride '''All'''

10. Run:

chcon -R -h -t httpd_sys_content_t /var/www/html/recordings/
service httpd restart

11. Edit ''/etc/selinux/config''

Change from:

SELINUX=enforcing

To:

SELINUX=disabled

12. Reboot server:

reboot

 

=Troubleshooting=

If Recordings are not displayed in GUI check the following log files in both servers: 
/var/log/mor/mor_record_file.log 
/var/log/mor/record_file.log

MOR Prelocalization

2018-06-22T13:26:54Z

Bogdan:

Prelocalization allows to do [http://wiki.kolmisoft.com/index.php/Localization Localization] before any other action in MOR.

=How to enable it=

'''Latest MOR X12 (or higher) version is required for this feature to work''' 

Modify '''/etc/asterisk/extensions_mor.conf''' to include MOR prelocalization AGI script (at around 40th line, just above '''exten => _X.,n,mor(${EXTEN})''')

exten => _X.,1,NoOp(MOR starts)
exten => _X.,n,GotoIf($["${MOR_DIAL_LOCAL_IVR}" != ""]?mor_dial_local_ivr,s,1)
exten => _X.,n,Gosub(diversion_settings,${EXTEN},1)
exten => _X.,n,Gosub(proxy_settings,${EXTEN},1)
exten => _X.,n,Set(__MOR_SIP_TO=${SIP_HEADER(To)})
exten => _X.,n,Set(TIMEOUT(response)=20)
exten => _X.,n,AGI(mor_prelocalization) <--------------------------------------- ADD THIS LINE HERE ----------- !!!!
exten => _X.,n,mor(${EXTEN})
exten => _X.,n,GotoIf($["${MOR_CARD_USED}" != ""]?mor_callingcard,s,1)
exten => _X.,n,GotoIf($["${MOR_ANIPIN_USED}" != ""]?mor_anipin,s,1)
exten => _X.,n,GotoIf($["${DIALSTATUS}" = "BUSY"]?BUSY,1:HANGUP,1)

Asterisk dialplan should be reloaded each time this file is changed:

asterisk -rx "dialplan reload"

=Configuration=

Configuration file '''/etc/mor/system.conf'''

'''prelocalization_location''' - which Location to use for prelocalization? Value should be Location ID. 
'''prelocalization_global_rules''' - should we include global rules? Value is either 1 or 0 (default 0). 

For example:

prelocalization_location = 17
prelocalization_global_rules = 1

Note: reload is not required when this file is changed.

=Location rules=

Prelocalization supports only '''Destination''' and '''Source''' rules. '''Combined''' rules are not supported. 

Only '''Cut''', '''Add''', '''Min Len''' and '''Max Len''' are applied when doing prelocalization.

=Script output=

Prelocalization output is written to Asterisk verbose log at the beginning of the call:

mor_prelocalization: MOR prelocalization AGI script started
mor_prelocalization: Original destination number: 00370123456
mor_prelocalization: Original source number: +390000000
mor_prelocalization: Original source name: test
mor_prelocalization: Localized dst number: 370123456 (cut: 00, add: )
mor_prelocalization: Localized src number: 390000000 (cut: +, add: )
mor_prelocalization: MOR prelocalization AGI script stopped

File:Localization copy function.png

2017-05-16T21:04:08Z

Bogdan: uploaded a new version of "File:Localization copy function.png"

File:Localization3.png

2017-05-16T21:01:15Z

Bogdan: uploaded a new version of "File:Localization3.png"

File:Localization2.png

2017-05-16T21:01:07Z

Bogdan: uploaded a new version of "File:Localization2.png"

File:Localization1.png

2017-05-16T21:00:53Z

Bogdan: uploaded a new version of "File:Localization1.png"

File:Mor accountant permissions.png

2017-05-16T20:53:29Z

Bogdan: uploaded a new version of "File:Mor accountant permissions.png"

CDR Import

2017-02-27T12:46:15Z

Bogdan: /* Setp 1 */

= Description =

Sometimes MOR can be used as separate billing software (that is, other than for real-time billing). In case if MOR is used as separate billing software, CDRs Import is most important functionality, because it allows to import CDRs from other switches (they need not be Asterisk) and bill these CDRs.
 
= Configuration =

In [[Configuration_from_GUI#Various | Configuration]], make sure you select the correct options for these values:

* '''CSV Column Separator'''.
* '''CSV Decimal Separator'''.

If the settings do not match your CSV file, you will not be able to import CDRs.
 
=Import=

==Step 1==
CDR Import can be found in '''SETTINGS –> Billing –> CDR –> Import'''.

The first step is to select a CSV file to import:
 
[[Image:cdrimport1.png]]
 

Click on '''Upload file'''.

== Step 2==

Sometimes MOR system is able to detect wrong CSV separator settings. If CSV separator settings are wrong MOR will suggest you to change them:
 
[[File:Cdr_import_wrong_separators.png]]
 
Next you will have to assign columns to CDR values. In step 2, you can see the necessary fields to select. They are marked by a star (*). Without selecting at least one field marked by *, you will not be able to continue the import process. Select the appropriate settings and click '''Assign Columns''':
 
[[Image:cdrimport2_2.png]]
 
==Step 3 ==

Here you will be presented with a parsed file. If something is not right, click the '''Back''' button. If it's okay, click '''Confirm columns''':
 
[[Image:cdrimport3.png]]
 
==Step 4 ==
Here you can choose method which should be used to assign calls to device:
 
[[Image:cdrimport4_2.png]]
 
* '''Select provider''' - allows to assign calls to certain provider. You will not see this option if you selected provider ID in step 2.
* '''Import by user''' - allows to assign calls to one user.
* '''Select user''' - user and device should be chosen here, when '''Import by user''' is selected.
* '''Import by CallerID''' - allows to automatically assign calls to users by CallerID. It checks [[CLIs_(Incoming_CallerIDs)|CLIs]] on Device settings. If CLI matches with CallerID call is assigned to this Device.
Admin are able to assign Calls to CLI of Device which belongs to User of Simple Reseller. Admin cannot import calls for Reseller PRO Users, but Reseller PRO able to import such Calls by himself.
* '''Create CallerID''' - creates list of all CallerIDs on CDR file and allows to assign CallerIDs to Devices. It creates new CLIs.
 
====Choosing provider ID during the import====

There is an option in step 2 where you can choose provider ID. System automatically selects tariff according to the ID from the file which is the same as Provider ID in MOR.

If there is provider ID in a file that doesn't exist in a system, file is not imported and you are informed about bad CDRs in step 5. If you chose to leave Provider ID not selected in step 2, everything is fine and you won't see the line "Bad CDRs".
 
[[Image:cdrimport5_2.png]]
 
When you choose to import provider ID in step 2, you can select Provider in step 6, but this is optional. This column will not be visible if you are not importing provider's ID.
 
[[Image:cdrimport6_4.png]]
 
=Imported Calls Billing=

Imported Calls are billed using [[CDR Rerating]] functionality logic. This means that imported Calls will be re-rated using Tariffs' Rates of MOR Resellers, Users and Providers who will be assigned for Calls during Calls Import.

 
=How to use file exported form [[Last Calls]]=

You can export CDR in either the PDF or the CSV format. This can be done in the Call Stats page ('''STATISTICS –> Calls''') and other places where you see:

* [[Image:pdf.png]] Export to PDF
* [[Image:excel.png]] Export to CSV

Just cick on one of these links and you will get CDR in the selected period.
 
Make sure that before exporting Last Calls, setting '''Show Full Source (CallerID Name and Number)''' in Settings Visual tab is '''unchecked''', otherwise CallerId will be exported not correctly and CDR import will be unsuccessful.
 
Check your localization rules before the import. Exported calls are localized calls (localization rules were applied to these calls). Localization rules are applied for the imported calls as well. This is how it is suppose to be, since:
 
1) If you import numbers which are not in E.164 format (not from MOR), localization rules will be applied and the calls will be billed correctly.
 
2) If you import numbers in E.164 format, they will not be changed, since there should be no localization rules for good numbers in E.164 format.
 
However, you can encounter a problem if you have incorrect Localization rules in a MOR systems.
====Example of a wrong configuration====

*There is a Global rule for international calls: '''Cut''': 00, '''Add''': , '''Min''': 1, '''Max''': 100.
*There is also a rule for Spain local calls: '''Cut''': 9, '''Add''': 349, '''Min''': 1, '''Max''': 100.
If you had a call too destination: 00972xxxxxxxxx, it will be changed to 972xxxxxxxxx (Israel number). You export the CDR of this call and re-import it (or import it to another MOR system), then localization rules will be applied again and you will have destination number 34972xxxxxxxxx (Spain number). To avoid this, use correct [[Number_Manipulation_Examples#Example_4_-_Spain | localization rules]].
 

= Other Notes=
== Calls to DIDs ==

Calls to DIDs are billed as for calls to normal numbers. 
Calls to DIDs which belong to the caller are not billed at all (Price = 0).
 
= See also =

* [[How to create a csv file]]
* [[CDR Rerating]]
* [[Automatic CDR Export]]