Kolmisoft Wiki - User contributions [en]

MOR API

2026-04-15T05:48:04Z

Admin: /* Rates */

[[File:warning.png|100px|alt="warning"|link=]]<big><big><big>IMPORTANT!!! API methods described here are for newest MOR version. For previous versions please check appropriate [http://wiki.kolmisoft.com/index.php/MOR_Manual#Old_Manuals manual].</big></big></big>
[[File:api.png|right|alt="api"|link=]]
<mkmeta>Application Program Interface for MOR Class 5 Softswitch</mkmeta>

 
=About=
MOR API lets other software interact with MOR without knowing the internal structure of the database (DB) and other logic.

MOR accepts requests by HTML POST and returns results in XML.

 
=MOR users that are allowed to use MOR API=
* Admin
* Reseller
* Accountant - only by using Admin Hash and Secret key
* Simple User

 

=Functions=

== API Related ==
* [[API Configuration]] – configuration options for API.
* [[MOR API hash construction|Hash construction]] – how to construct hash to authenticate data over API.

 

==Aggregate==
* [[MOR API aggregate get | aggregate_get]] - for getting MOR aggregate statistics.

 

==Autodialer==
* [[MOR API autodialer upload numbers | autodialer_upload_numbers]] - upload numbers from CSV file to existing Autodialer Campaign.
* [[MOR API autodialer get campaign statistics | autodialer_get_campaign_statistics]] - gets Autodialer campaign statistics for selected period.
* [[MOR API autodialer redial all failed calls | autodialer_redial_all_failed_calls]] - initiate Redial all failed calls action for specific campaign.
* [[MOR API autodialer get campaign ivr poll results | autodialer_get_campaign_ivr_poll_results]] - gets Autodialer camoaign ivr poll results.
* [[MOR API autodialer change campaign status | autodialer_change_campaign_status]] - changes Autodialer campaign status.

 

==Balance==
* [[MOR API user balance update | user_balance_update]] (change_user_balance) – changes User's Balance
Various methods to retrieve User balance
* [[MOR API user_balance_get|user_balance_get]] (balance) – retrieves a User Balance.
* [[Balance in phone | user_simple_balance_get]] (simple_balance) – gets User's Balance
* [[MOR API user balance get by psw | user_balance_get_by_psw]] – gets User's Balance by his owned Device's Password
* [[MOR API User Balance get by Username | user_balance_get_by_username]] – gets User's Balance by his owned Device's Username

 

==Callback==
NOTE: A Callback addon is needed. Does not work on a limited version.
* [[MOR API callback init|callback_init]] (callback) – initiates callback.

 

==Calling Cards==
* [[MOR API card_by_cli_update| card_by_cli_update]] (cc_by_cli) – creates and updates calling cards, including adding and transferring funds, by being identified according the Caller_ID.
* [[MOR API card_from_group_sell| card_from_group_sell]] (buy_card_from_callingroup) – sells cards from calling card group.
* [[MOR API card_group_get| card_group_get]] (show_calling_card_group) – show calling group info.
* [[MOR API card_balance_get| card_balance_get]] (card_balance_get) – show card's balance.
* [[MOR API card_payment_add| card_payment_add]] – add payment to the calling card.
* [[MOR_API_Calling_Cards_create| calling_cards_create]] – create Calling Cards.
* [[MOR_API_Calling_Card_update| calling_card_update]] – update Calling Card.
* [[MOR_API_Calling_Cards_get| calling_cards_get]] - get Calling Cards.
* [[MOR_API_Card_Group_create| cc_group_create]] – create Card Group.
* [[MOR_API_Card_Group_update| cc_group_update]] – update Card Group.
* [[MOR API Card Groups get| cc_groups_get]] – show Calling Cards Group info.
 

==Calls==
* [[MOR API user calls get|user_calls_get]] (user_calls) – retrieves a list of calls in a selected time period for a user/device.
* [[MOR API local calls get|local_calls_get]] - retrieves a list of local calls in a selected time period for a user.
* [[MOR_API_active_calls_get|active_calls_get]] - Retrieves list of active calls for specified User.
 

==Conflines==
* [[MOR API conflines update|conflines_update]] – changes settings for API, Default User or Default Device.

 
==Credit notes==
* [[MOR API credit_notes_get| credit_notes_get]] (credit_notes) – credit notes list.
* [[MOR API credit_note_update| credit_note_update]] – credit note update.
* [[MOR API credit_notes_create| credit_note_create]] – credit note create.
* [[MOR API credit_notes_delete| credit_note_delete]] – credit note delete.

 
==Currencies==
* [[MOR_API_Exchange_rate_update|exchange_rate_update]] - Currency Exchange rate update.

 
==Device==

* [[MOR API device create| device_create]] – create device
* [[MOR_API_device_update | device_update]] – update device settings.
* [[MOR API device delete| device_delete]] (delete_device) – delete device
* [[MOR API devices get | devices_get]] (device_list) – users device list
* [[MOR API device details get | device_details_get]] – shows all information about specified device.
 
* [[MOR API device callflow get| device_callflow_get]] - returns information about specified device callflow state.
* [[MOR API device callflow update | device_callflow_update]] – updates information of specified device callflow state.
 
* [[MOR API CLI info get | cli_info_get]] (cli_get_info) – shows id of device where CLI belongs.
* [[MOR API CLI delete | cli_delete]] – deletes specified CLI.
* [[MOR API CLI add | cli_add]] – creates CLI and assigns it to the specified device.
* [[MOR API device clis get | device_clis_get]] – CLIs list by User and/or Device
 
* [[MOR API device rules get | device_rules_get]] – show Device Rules.
* [[MOR API device rule delete | device_rule_delete]] – delete Device Rule.
* [[MOR API device rule create | device_rule_create]] – create Device Rule.
 

==DID==

* [[MOR API dids get| dids_get]] – get list of particular DIDs
* [[MOR API did_create| did_create]] – DID create
* [[MOR_API_did_device_assign| did_device_assign]] (did_assign_device) – Assign Device to DID
* [[MOR_API_did_trunk_device_assign| did_trunk_device_assign]] (did_trunk_device_assign) – Assign Trunk Device to DID
* [[MOR_API_did_device_unassign| did_device_unassign]] (did_unassign_device) – Unassign Device from DID
* [[MOR_API_did_details_update| did_details_update]] (did_details_update) – Update DID details
* [[MOR API did subscription stop|did_subscription_stop]] – STOP DID subscription
* [[MOR API did terminate|did_terminate]] – DID terminate
* [[MOR API did make free|did_make_free]] – DID make free
* [[MOR API did rates update|did_rates_update]] – Update DID rates
* [[MOR API did rates get|did_rates_get]] – Get DID rates
* [[MOR API did close|did_close]] – close the DID
* [[MOR API did delete|did_delete]] – delete the DID
* [[MOR API did rates details get|did_rates_details_get]] – Get DID rates details
* [[MOR API did rates details update|did_rates_details_update]] – Update DID rates details

 

==Email==
* [[MOR API email send| email_send]] (send_email) – send Email.

 
==Financial statements==
* [[MOR API financial_statements_get| financial_statements_get]] (financial_statements) – financial statements list.
 

==Invoices==
* [[MOR API invoices_get|invoices_get]] (invoices) – retrieves a list of invoices in a selected time period.
* [[MOR_API_invoice_update|invoice_update]] - update Invoice

 
==IVR==
* [[MOR_API_ivr_dial_plan_update|ivr_dial_plan_update]] (invoices) – Updates IVR dial plan.
* [[MOR_API_ivr_time_period_update|ivr_time_period_update]] (invoices) – Updates IVR time period.

 
==LCR==
* [[MOR API lcrs_get|lcrs_get]] - retrieves list of LCRs.
* [[MOR API lcr_create|lcr_create]] - creates LCR
* [[MOR API lcr_update|lcr_update]] - updates LCR
* [[MOR API lcr_delete|lcr_delete]] - updates LCR
* [[MOR API lcr_add_provider|lcr_add_provider]] - adds provider to LCR
* [[MOR API lcr_delete_provider|lcr_delete_provider]] - deletes provider from LCR

 

==Location Rules==
* [[MOR API location_rule_create|location_rule_create]] – creates location rule.
* [[MOR API location_rule_update|location_rule_update]] – updates location rule.
* [[MOR API location_rules_get|location_rules_get]] – retrieves location rules.
* [[MOR API location_rule_get|location_rule_get]] – retrieves location rule information.
* [[MOR API location_rule_copy|location_rule_copy]] – copies rule from one location to other one.
* [[MOR API location_rule_delete|location_rule_delete]] – delete location rule.

 

==Login==
* [[MOR API user_login|user_login]] (login) – logs user in to MOR.
* [[MOR API user_logout|user_logout]] (logout) – logs user out from MOR.

 
==Monitorings==
* [[MOR API ma_activate_api| ma_activate]] – turn on monitorings addon

 
==Number Pools==
* [[MOR API number_pools_get| number_pools_get]] – get Number Pools list
* [[MOR API number_pool_create| number_pool_create]] – create Number Pools
* [[MOR API number pool update| number_pool_update]] – update Number Pool
* [[MOR API number pool delete| number_pool_delete]] – delete Number Pool
* [[MOR API number pool numbers create| number_pool_numbers_create]] – create numbers for Number Pool
* [[MOR API number pool numbers delete| number_pool_numbers_delete]] – delete numbers from Number Pool
 

==Payments==
* [[MOR API payment_create| payment_create]] (create_payment) – create payment.
* [[MOR API payments_get| payments_get]] (payments_list) – payments list.

 
==PBX Pool==
* [[MOR API pbx_pool_create| pbx_pool_create]] – PBX Pool create.

 
==Phonebooks==
* [[MOR API phonebooks_get| phonebooks_get]] (phonebooks_api ) – phonebooks list.
* [[MOR API phonebook_edit| phonebook_edit]] (phonebook_edit_api) – edit phonebook.
* [[MOR API phonebook_record_create| phonebook_record_create]] – create phonebook.
* [[MOR API phonebook record delete | phonebook record delete]]

 

==Providers==
* [[MOR API providers get| providers_get]] – getting list of providers.
* [[MOR API provider create| provider_create]] – create provider.
* [[MOR API provider update| provider_update]] – update provider.
* [[MOR API provider delete| provider_delete]] – delete provider.
 
=== Provider Rules===
* [[MOR_API_provider_rules_get| provider_rules_get]] - shows provider rules
* [[MOR_API_provider_rule_delete| provider_rules_delete]] - deletes provider rules
* [[MOR_API_provider_rule_create| provider_rules_create]] - creates provider rules

 

==Queue==
* [[MOR API queue log get| queue_log_get]] – getting MOR queue log.

 
==Quickforwards==
* [[MOR API Quickforwards get| quickforwards_dids_get]] (quickforwards_dids_get) – get Quickforwards.
* [[MOR API Quickforwards update| quickforwards_did_update]] (quickforwards_did_update) – update Quickforwards.
* [[MOR API Quickforwards delete| quickforwards_did_delete]] (quickforwards_did_delete) – delete Quickforwards.

 
==Tariffs/Rates==
* [[MOR API rate get|rate_get]] (rate) – check user rate by prefix
* [[MOR API tariff rates get| tariff_rates_get]] (get_tariff) – get all tariff's rates
* [[MOR API tariff_retail_import | tariff_retail_import ]] (import_retail_tariff) – import xml retail tariff
* [[MOR API tariff_wholesale_update | tariff_wholesale_update ]] (wholesale_tariff) – update or create wholesale tariff
* [[MOR API tariffs_get|tariffs_get]] - retrieve list of tariffs

 

==Recordings==
* [[MOR API recordings get| recordings_get]] – get MOR recordings.
* [[MOR API recording update| recording_update]] - update comment for a specific recording.
* [[MOR API recordings delete | recordings_delete]] - delete recordings based on search parameters.

 
== Resellers ==
* [[MOR API reseller group create|reseller_group_create]] - create new Reseller Group
* [[MOR API reseller_groups_get|reseller_groups_get]] - retrieve Reseller Groups

 
==Services==
* [[MOR API Service create| service_create]] – create Service.
* [[MOR API Service delete| service_delete]] – delete Service.
* [[MOR API Services get| services_get]] – get Services.
* [[MOR API Service update| service_update]] – update Service.

 

==Spy==
* [[MOR API spy_call | spy_call]] – Initiates a spy call.

 

==Statistics==
* [[MOR API quickstats_get | quickstats_get]] – gets today's [[Quick Stats]] and [[Active Calls]] count

 

 
==Subscriptions==
* [[MOR API subscription delete|subscription_delete]] - Subscription delete.
* [[MOR API Subscriptions get|subscriptions_get]] - Subscriptions get.
* [[MOR API subscription create|subscription_create]] - Subscription create.
* [[MOR API subscription create bulk|subscription_create_bulk]] - Bulk Subscription create.
* [[MOR API subscription update|subscription_update]] - Subscription update.
* [[MOR API Subscription Flat Rate Number Status Get| subscription_flat_rate_number_status_get]] - check prefix covering flat-rate subscriptions
 

==User==

* [[MOR API user_register| user_register]] – create new user from params.
* [[MOR API user_details_get | user_details_get]] (user_details) – gets user details.
* [[MOR API user_details_raw_get | user_details_raw_get]] (user_raw_details) – gets user raw details from database.
* [[MOR_API_user_details_update| user_details_update]] (user_update_api) – update user from params.
* [[MOR API users_get| users_get]] - get user list
* [[MOR API user_delete| user_delete]] - deletes user
 

==Version==
* [[MOR API system version get| system_version_get]] (get_version) – get MOR version number.

 

==Vouchers==
* [[MOR API voucher use| voucher_use]] – use selected voucher.

 
= Examples =
* [[MOR API PHP Examples]]

 
=HTML POST=
All requests are in a similar format:

HTML POST: http://<SERVER_IP>/billing/api/<function>?u=username

* username - the user name and password of the user who is asking for the data.

If the user has 'admin' rights, he will get more results and can perform more actions compared to a user who does not have such rights.
 
=Useful to know=

* All API methods return data straight from the database. It means that MOR GUI settings do not affect data, it will be returned as it is saved in the database. For example:
** Value of money will be returned in Default System [[Currencies|Currency]].
** Date will not be affected by [[Configuration_from_GUI#Visual| Default date format]] setting.
** Value of money will not be affected by [[Configuration_from_GUI#Visual|Number digits]] setting.

 
=See also =
* [[API Configuration]]
* [[MOR integration]]
* [[How to block access to some API functions]]
* [[MOR API v2]]

MOR API

2026-04-15T05:47:31Z

Admin: /* Rates */

[[File:warning.png|100px|alt="warning"|link=]]<big><big><big>IMPORTANT!!! API methods described here are for newest MOR version. For previous versions please check appropriate [http://wiki.kolmisoft.com/index.php/MOR_Manual#Old_Manuals manual].</big></big></big>
[[File:api.png|right|alt="api"|link=]]
<mkmeta>Application Program Interface for MOR Class 5 Softswitch</mkmeta>

 
=About=
MOR API lets other software interact with MOR without knowing the internal structure of the database (DB) and other logic.

MOR accepts requests by HTML POST and returns results in XML.

 
=MOR users that are allowed to use MOR API=
* Admin
* Reseller
* Accountant - only by using Admin Hash and Secret key
* Simple User

 

=Functions=

== API Related ==
* [[API Configuration]] – configuration options for API.
* [[MOR API hash construction|Hash construction]] – how to construct hash to authenticate data over API.

 

==Aggregate==
* [[MOR API aggregate get | aggregate_get]] - for getting MOR aggregate statistics.

 

==Autodialer==
* [[MOR API autodialer upload numbers | autodialer_upload_numbers]] - upload numbers from CSV file to existing Autodialer Campaign.
* [[MOR API autodialer get campaign statistics | autodialer_get_campaign_statistics]] - gets Autodialer campaign statistics for selected period.
* [[MOR API autodialer redial all failed calls | autodialer_redial_all_failed_calls]] - initiate Redial all failed calls action for specific campaign.
* [[MOR API autodialer get campaign ivr poll results | autodialer_get_campaign_ivr_poll_results]] - gets Autodialer camoaign ivr poll results.
* [[MOR API autodialer change campaign status | autodialer_change_campaign_status]] - changes Autodialer campaign status.

 

==Balance==
* [[MOR API user balance update | user_balance_update]] (change_user_balance) – changes User's Balance
Various methods to retrieve User balance
* [[MOR API user_balance_get|user_balance_get]] (balance) – retrieves a User Balance.
* [[Balance in phone | user_simple_balance_get]] (simple_balance) – gets User's Balance
* [[MOR API user balance get by psw | user_balance_get_by_psw]] – gets User's Balance by his owned Device's Password
* [[MOR API User Balance get by Username | user_balance_get_by_username]] – gets User's Balance by his owned Device's Username

 

==Callback==
NOTE: A Callback addon is needed. Does not work on a limited version.
* [[MOR API callback init|callback_init]] (callback) – initiates callback.

 

==Calling Cards==
* [[MOR API card_by_cli_update| card_by_cli_update]] (cc_by_cli) – creates and updates calling cards, including adding and transferring funds, by being identified according the Caller_ID.
* [[MOR API card_from_group_sell| card_from_group_sell]] (buy_card_from_callingroup) – sells cards from calling card group.
* [[MOR API card_group_get| card_group_get]] (show_calling_card_group) – show calling group info.
* [[MOR API card_balance_get| card_balance_get]] (card_balance_get) – show card's balance.
* [[MOR API card_payment_add| card_payment_add]] – add payment to the calling card.
* [[MOR_API_Calling_Cards_create| calling_cards_create]] – create Calling Cards.
* [[MOR_API_Calling_Card_update| calling_card_update]] – update Calling Card.
* [[MOR_API_Calling_Cards_get| calling_cards_get]] - get Calling Cards.
* [[MOR_API_Card_Group_create| cc_group_create]] – create Card Group.
* [[MOR_API_Card_Group_update| cc_group_update]] – update Card Group.
* [[MOR API Card Groups get| cc_groups_get]] – show Calling Cards Group info.
 

==Calls==
* [[MOR API user calls get|user_calls_get]] (user_calls) – retrieves a list of calls in a selected time period for a user/device.
* [[MOR API local calls get|local_calls_get]] - retrieves a list of local calls in a selected time period for a user.
* [[MOR_API_active_calls_get|active_calls_get]] - Retrieves list of active calls for specified User.
 

==Conflines==
* [[MOR API conflines update|conflines_update]] – changes settings for API, Default User or Default Device.

 
==Credit notes==
* [[MOR API credit_notes_get| credit_notes_get]] (credit_notes) – credit notes list.
* [[MOR API credit_note_update| credit_note_update]] – credit note update.
* [[MOR API credit_notes_create| credit_note_create]] – credit note create.
* [[MOR API credit_notes_delete| credit_note_delete]] – credit note delete.

 
==Currencies==
* [[MOR_API_Exchange_rate_update|exchange_rate_update]] - Currency Exchange rate update.

 
==Device==

* [[MOR API device create| device_create]] – create device
* [[MOR_API_device_update | device_update]] – update device settings.
* [[MOR API device delete| device_delete]] (delete_device) – delete device
* [[MOR API devices get | devices_get]] (device_list) – users device list
* [[MOR API device details get | device_details_get]] – shows all information about specified device.
 
* [[MOR API device callflow get| device_callflow_get]] - returns information about specified device callflow state.
* [[MOR API device callflow update | device_callflow_update]] – updates information of specified device callflow state.
 
* [[MOR API CLI info get | cli_info_get]] (cli_get_info) – shows id of device where CLI belongs.
* [[MOR API CLI delete | cli_delete]] – deletes specified CLI.
* [[MOR API CLI add | cli_add]] – creates CLI and assigns it to the specified device.
* [[MOR API device clis get | device_clis_get]] – CLIs list by User and/or Device
 
* [[MOR API device rules get | device_rules_get]] – show Device Rules.
* [[MOR API device rule delete | device_rule_delete]] – delete Device Rule.
* [[MOR API device rule create | device_rule_create]] – create Device Rule.
 

==DID==

* [[MOR API dids get| dids_get]] – get list of particular DIDs
* [[MOR API did_create| did_create]] – DID create
* [[MOR_API_did_device_assign| did_device_assign]] (did_assign_device) – Assign Device to DID
* [[MOR_API_did_trunk_device_assign| did_trunk_device_assign]] (did_trunk_device_assign) – Assign Trunk Device to DID
* [[MOR_API_did_device_unassign| did_device_unassign]] (did_unassign_device) – Unassign Device from DID
* [[MOR_API_did_details_update| did_details_update]] (did_details_update) – Update DID details
* [[MOR API did subscription stop|did_subscription_stop]] – STOP DID subscription
* [[MOR API did terminate|did_terminate]] – DID terminate
* [[MOR API did make free|did_make_free]] – DID make free
* [[MOR API did rates update|did_rates_update]] – Update DID rates
* [[MOR API did rates get|did_rates_get]] – Get DID rates
* [[MOR API did close|did_close]] – close the DID
* [[MOR API did delete|did_delete]] – delete the DID
* [[MOR API did rates details get|did_rates_details_get]] – Get DID rates details
* [[MOR API did rates details update|did_rates_details_update]] – Update DID rates details

 

==Email==
* [[MOR API email send| email_send]] (send_email) – send Email.

 
==Financial statements==
* [[MOR API financial_statements_get| financial_statements_get]] (financial_statements) – financial statements list.
 

==Invoices==
* [[MOR API invoices_get|invoices_get]] (invoices) – retrieves a list of invoices in a selected time period.
* [[MOR_API_invoice_update|invoice_update]] - update Invoice

 
==IVR==
* [[MOR_API_ivr_dial_plan_update|ivr_dial_plan_update]] (invoices) – Updates IVR dial plan.
* [[MOR_API_ivr_time_period_update|ivr_time_period_update]] (invoices) – Updates IVR time period.

 
==LCR==
* [[MOR API lcrs_get|lcrs_get]] - retrieves list of LCRs.
* [[MOR API lcr_create|lcr_create]] - creates LCR
* [[MOR API lcr_update|lcr_update]] - updates LCR
* [[MOR API lcr_delete|lcr_delete]] - updates LCR
* [[MOR API lcr_add_provider|lcr_add_provider]] - adds provider to LCR
* [[MOR API lcr_delete_provider|lcr_delete_provider]] - deletes provider from LCR

 

==Location Rules==
* [[MOR API location_rule_create|location_rule_create]] – creates location rule.
* [[MOR API location_rule_update|location_rule_update]] – updates location rule.
* [[MOR API location_rules_get|location_rules_get]] – retrieves location rules.
* [[MOR API location_rule_get|location_rule_get]] – retrieves location rule information.
* [[MOR API location_rule_copy|location_rule_copy]] – copies rule from one location to other one.
* [[MOR API location_rule_delete|location_rule_delete]] – delete location rule.

 

==Login==
* [[MOR API user_login|user_login]] (login) – logs user in to MOR.
* [[MOR API user_logout|user_logout]] (logout) – logs user out from MOR.

 
==Monitorings==
* [[MOR API ma_activate_api| ma_activate]] – turn on monitorings addon

 
==Number Pools==
* [[MOR API number_pools_get| number_pools_get]] – get Number Pools list
* [[MOR API number_pool_create| number_pool_create]] – create Number Pools
* [[MOR API number pool update| number_pool_update]] – update Number Pool
* [[MOR API number pool delete| number_pool_delete]] – delete Number Pool
* [[MOR API number pool numbers create| number_pool_numbers_create]] – create numbers for Number Pool
* [[MOR API number pool numbers delete| number_pool_numbers_delete]] – delete numbers from Number Pool
 

==Payments==
* [[MOR API payment_create| payment_create]] (create_payment) – create payment.
* [[MOR API payments_get| payments_get]] (payments_list) – payments list.

 
==PBX Pool==
* [[MOR API pbx_pool_create| pbx_pool_create]] – PBX Pool create.

 
==Phonebooks==
* [[MOR API phonebooks_get| phonebooks_get]] (phonebooks_api ) – phonebooks list.
* [[MOR API phonebook_edit| phonebook_edit]] (phonebook_edit_api) – edit phonebook.
* [[MOR API phonebook_record_create| phonebook_record_create]] – create phonebook.
* [[MOR API phonebook record delete | phonebook record delete]]

 

==Providers==
* [[MOR API providers get| providers_get]] – getting list of providers.
* [[MOR API provider create| provider_create]] – create provider.
* [[MOR API provider update| provider_update]] – update provider.
* [[MOR API provider delete| provider_delete]] – delete provider.
 
=== Provider Rules===
* [[MOR_API_provider_rules_get| provider_rules_get]] - shows provider rules
* [[MOR_API_provider_rule_delete| provider_rules_delete]] - deletes provider rules
* [[MOR_API_provider_rule_create| provider_rules_create]] - creates provider rules

 

==Queue==
* [[MOR API queue log get| queue_log_get]] – getting MOR queue log.

 
==Quickforwards==
* [[MOR API Quickforwards get| quickforwards_dids_get]] (quickforwards_dids_get) – get Quickforwards.
* [[MOR API Quickforwards update| quickforwards_did_update]] (quickforwards_did_update) – update Quickforwards.
* [[MOR API Quickforwards delete| quickforwards_did_delete]] (quickforwards_did_delete) – delete Quickforwards.

 
==Rates==
* [[MOR API rate get|rate_get]] (rate) – check user rate by prefix
* [[MOR API tariff rates get| tariff_rates_get]] (get_tariff) – get all tariff's rates
* [[MOR API tariff_retail_import | tariff_retail_import ]] (import_retail_tariff) – import xml retail tariff
* [[MOR API tariff_wholesale_update | tariff_wholesale_update ]] (wholesale_tariff) – update or create wholesale tariff
* [[MOR API tariffs_get|tariffs_get]] - retrieve list of tariffs

 

==Recordings==
* [[MOR API recordings get| recordings_get]] – get MOR recordings.
* [[MOR API recording update| recording_update]] - update comment for a specific recording.
* [[MOR API recordings delete | recordings_delete]] - delete recordings based on search parameters.

 
== Resellers ==
* [[MOR API reseller group create|reseller_group_create]] - create new Reseller Group
* [[MOR API reseller_groups_get|reseller_groups_get]] - retrieve Reseller Groups

 
==Services==
* [[MOR API Service create| service_create]] – create Service.
* [[MOR API Service delete| service_delete]] – delete Service.
* [[MOR API Services get| services_get]] – get Services.
* [[MOR API Service update| service_update]] – update Service.

 

==Spy==
* [[MOR API spy_call | spy_call]] – Initiates a spy call.

 

==Statistics==
* [[MOR API quickstats_get | quickstats_get]] – gets today's [[Quick Stats]] and [[Active Calls]] count

 

 
==Subscriptions==
* [[MOR API subscription delete|subscription_delete]] - Subscription delete.
* [[MOR API Subscriptions get|subscriptions_get]] - Subscriptions get.
* [[MOR API subscription create|subscription_create]] - Subscription create.
* [[MOR API subscription create bulk|subscription_create_bulk]] - Bulk Subscription create.
* [[MOR API subscription update|subscription_update]] - Subscription update.
* [[MOR API Subscription Flat Rate Number Status Get| subscription_flat_rate_number_status_get]] - check prefix covering flat-rate subscriptions
 

==User==

* [[MOR API user_register| user_register]] – create new user from params.
* [[MOR API user_details_get | user_details_get]] (user_details) – gets user details.
* [[MOR API user_details_raw_get | user_details_raw_get]] (user_raw_details) – gets user raw details from database.
* [[MOR_API_user_details_update| user_details_update]] (user_update_api) – update user from params.
* [[MOR API users_get| users_get]] - get user list
* [[MOR API user_delete| user_delete]] - deletes user
 

==Version==
* [[MOR API system version get| system_version_get]] (get_version) – get MOR version number.

 

==Vouchers==
* [[MOR API voucher use| voucher_use]] – use selected voucher.

 
= Examples =
* [[MOR API PHP Examples]]

 
=HTML POST=
All requests are in a similar format:

HTML POST: http://<SERVER_IP>/billing/api/<function>?u=username

* username - the user name and password of the user who is asking for the data.

If the user has 'admin' rights, he will get more results and can perform more actions compared to a user who does not have such rights.
 
=Useful to know=

* All API methods return data straight from the database. It means that MOR GUI settings do not affect data, it will be returned as it is saved in the database. For example:
** Value of money will be returned in Default System [[Currencies|Currency]].
** Date will not be affected by [[Configuration_from_GUI#Visual| Default date format]] setting.
** Value of money will not be affected by [[Configuration_from_GUI#Visual|Number digits]] setting.

 
=See also =
* [[API Configuration]]
* [[MOR integration]]
* [[How to block access to some API functions]]
* [[MOR API v2]]

Main Page

2026-04-08T12:03:00Z

Admin:

<mkmeta>Page dedicated mainly for MOR Class 5 Softswitch and M4 Class 4 Softswitch</mkmeta>
__NOTOC__
<table border="0" cellpadding="2" cellspacing="0" >

<tr>
<td>[[Image:mor11_manual_book.png|80px|alt="Manual"|link=]]</td>
<td>
<h1>[[MOR Manual|MOR Class 5 Softswitch Manual]]</h1>
This section covers the main functionality of MOR Softswitch with Billing and Routing 
</td>
</tr>

<tr>
<td>[[Image:mor11_manual_book.png|80px|alt="Manual"|link=]]</td>
<td>
<h1>[[M4 Switch Manual|M4 Class 4 Softswitch Manual]]</h1>
This section covers the main functionality of M4 Softswitch with Billing and Routing 
</td>
</tr>

<tr>
<td></td>
<td>
<h1>[[MOR/M4 Related Guides| MOR/M4 Related Guides]]</h1>
Here you will find all topics related to the MOR/M4 but not included into Manual 
</td>
</tr>

<tr>
<td></td>
<td>
<h1>[[VOIP Business - Guides and Resources]]</h1>
All guides which are related to the VoIP business: where to look for providers, what licenses are needed, how to increase your profit, etc. 
</td>
</tr>

<tr>
<td></td>
<td>
<h1>[[Various Guides]]</h1>
All guides which are not related to the MOR 
</td>
</tr>

<tr>
<td></td>
<td>
<h1>[[Problems/Troubleshooting]]</h1>
Guides and suggestions on how to solve various problems you can come across 
</td>
</tr>

<table>

 

'''IMPORTANT!'''   [https://www.kolmisoft.com?utm_source=wiki Kolmisoft] does not take any responsibility if you use the information found in this wiki and you cause any damage to your data, software, or servers. '''USE IT AT YOUR OWN RISK!'''

Main Page

2026-04-08T11:18:41Z

Admin:

<mkmeta>Page dedicated mainly for MOR Class 5 Softswitch and M4 Class 4 Softswitch</mkmeta>
__NOTOC__
<table border="0" cellpadding="2" cellspacing="0" >

<tr>
<td>[[Image:mor11_manual_book.png|80px|alt="Manual"|link=]]</td>
<td>
<h1>[[MOR Manual|MOR Class 5 Softswitch Manual]]</h1>
This section covers the main functionality of MOR Softswitch with Billing and Routing 
</td>
</tr>

<tr>
<td>[[Image:mor11_manual_book.png|80px|alt="Manual"|link=]]</td>
<td>
<h1>[[M4 Switch Manual|M4 Class 4 Softswitch Manual]]</h1>
This section covers the main functionality of M4 Softswitch with Billing and Routing 
</td>
</tr>

<tr>
<td></td>
<td>
<h1>[[MOR/M4 Related Guides| MOR/M4 Related Guides]]</h1>
Here you will find all topics related to the MOR/M4 but not included into Manual 
</td>
</tr>

<tr>
<td></td>
<td>
<h1>[[VOIP Business - Guides and Resources]]</h1>
All guides which are related to the VoIP business: where to look for providers, what licenses are needed, how to increase your profit, etc. 
</td>
</tr>

<tr>
<td></td>
<td>
<h1>[[Various Guides]]</h1>
All guides which are not related to the MOR 
</td>
</tr>

<tr>
<td></td>
<td>
<h1>[[Problems/Troubleshooting]]</h1>
Guides and suggestions on how to solve various problems you can come across 
</td>
</tr>

<table>

 

'''IMPORTANT!'''   [https://www.kolmisoft.com Kolmisoft] does not take any responsibility if you use the information found in this wiki and you cause any damage to your data, software, or servers. '''USE IT AT YOUR OWN RISK!'''

Alerts

2026-04-01T07:31:47Z

Admin: /* Block user if it spends more than 50EUR in 24h */

=Description=

Alerts functionality is dedicated to taking actions about your system issues which may cause a problem. You may block User, disable Provider, change LCR for User or simply send a notification to specified [[Alert Groups|Group]] of [[Alert Contacts|Contacts]].

You are able to follow these parameters:

* [[ASR/ACD|ASR]] – Answer-Seizure Ratio (percent)
* [[ASR/ACD|ACD]] – Average Call Duration (in seconds)
* PDD – Average Post Dial Delay. The time between punching in the last digit of a telephone number and receiving a ring or busy signal (in seconds)
* TTC (Time to Connect)(DURATION-BILLSEC) – Average time between receiving a ring signal and answer to the call (in seconds)
* BILLSEC – Sum of calls bilsec (in seconds)
* TOTAL CALLS – Sum of all calls.
* TOTAL OUTGOING CALLS – Sum of outgoing calls.
* ANSWERED CALLS – Sum of answered calls.
* NOT ANSWERED CALLS – Sum of not answered calls (FAILED, BUSY, NO ANSWER).
* SIMULTANEOUS CALLS – Number of simultaneous calls (only applies to users and providers).
* PRICE SUM – Sum of calls price (only applies to users and providers).
* HGC (absolute) – Sum of calls, which ended with a specific [[Hangupcause_Codes | Hangupcause code]]. The HGC has to be set in the ''HGC'' field (it appears once ''Parameter: HGC'' is chosen).
* HGC (percent) – Percent of calls, which ended with a specific [[Hangupcause_Codes | Hangupcause code]]. The HGC has to be set in the ''HGC'' field (it appears once ''Parameter: HGC'' is chosen).
* REGISTRATION - Device registration status (either registered or not).
And it is possible to make actions for these types of MOR Objects or send notification about it:

* [[Users]]
** All
** Postpaid
** Prepaid
** One User
* [[Providers]]
* [[Devices]]
* [[Directions and Destinations | Destinations]]
** One Destination by prefix.
** Few Destinations by prefix and % sign. Eg. 93%, 3706% and so on.
* [[Destinations Groups]]
* System
** Any call made will be assigned to System object (even unauthenticated calls). Useful for general System monitoring.
 

=Usage=

Go to '''ADDONS –> Monitorings –> Alerts'''
 
[[File:alerts_path.png]]
 
Here you can see list of all created Alerts and their main information like is Alert active? When it was Raised/Cleared last time? What value was at Alert/Clear...
 
[[File:alerts_list.png]]
 
Click on [[Image:icon_add.png]]'''Add new Alert''' link to create an Alert or click on [[image:icon_edit.png]] icon to change settings of existing Alert.
 
[[File:Mor_alerts_edit_4.png|right]]
 
'''General'''

* '''Name''' – Alert name.
* '''Object Type''' – select which Object you want to follow.
* '''Object Name''' – pecify name/prefix of Object.
* '''Parameter''' – choose which parameter should be followed.
* '''Alert Type''' – ABS means that absolute data values will be taken from specified time period.
'''NOTE''': Object Type, Object Name, Parameter, Alert Type cannot be changed once Alert is created.
* '''Ignore if Calls''' <= – indicate calls sum when system should ignore Alert if calls sum is less than written (if 0, Alert will not be ignored).
* '''Ignore if Calls''' >= – indicate calls sum when system should ignore Alert if calls sum is more than written (if 0, Alert will not be ignored).
* '''Group to Notify''' – select [[Alert Groups|Group]] of [[Alert Contacts|Contacts]] who should be informed about Alert/clear.
* '''Notify to User''' – it is available only when Alert object type is User or Device. Check if you want to notify User on Alert. 
'''Alert'''

* '''Alert if <=''' – indicate Parameter value when system should raise Alert if value is less than written.
* '''Alert if >=''' – indicate Parameter value when system should raise Alert if value is more than written.
* '''Disable Object''' – check if you want to disable selected Object on Alert.
* '''Disable Provider in LCR''' – indicate LCR where Provider should be disabled.
* '''LCR on Alert''' – select LCR which one should be used after Alert
* '''Notify On Alert via Email''' – check if you want that specified [[Alert Groups|Group]] will receive an email notifications about Alerts.
* '''Notify On Alert via Webhook''' – when set, the alert will send a webhook to all Contacts in Alert Group that have non-empty Webhook URL. More info [https://wiki.kolmisoft.com/index.php/Alerts#Webhook_notifications here].
 
'''Clear'''

* '''Disable Clear''' – when alert is raised, it will never be cleared.
* '''Clear on Condition'''
** '''Clear if <=''' – indicate Parameter value when system should Clear Alert if value is less than written.
** '''Clear if >=''' – indicate Parameter value when system should Clear Alert if value is more than written.
* '''Clear on time basis'''
** '''Clear after''' – indicate time value after which system should Clear Alert
** '''Clear on Date''' – indicate specific date and time when system should Clear Alert (After clear, selection will be reset)
* '''Enable Object''' – check if you want to enable selected(in Alert configuration) Object on Clear.
* '''Enable Provider in LCR''' – check if you want to enable selected(in Alert configuration) Provider on Clear.
* '''LCR on Clear''' – select LCR which one should be used after Clear.
* '''Notify On Clear via Email''' – check if you want that specified [[Alert Groups|Group]] will receive an email notifications about Clear.
* '''Notify On Alert via Webhook''' – when set, the alert will send a webhook to all Contacts in Alert Group that have non-empty Webhook URL. More info [https://wiki.kolmisoft.com/index.php/Alerts#Webhook_notifications here].

'''NOTE''' one of '''Clear on Condition''' options and both '''Clear on time basis''' options can be selected at one time. System will clear alert if at least one of conditions will be true, it means that alert will be cleared on condition which first will appear.
 
'''Period'''

You can select different time periods for each alert. This period defines time period which activity have to be checked.

Note: period has no effect when parameter SIMULTANEOUS CALLS is chosen.
 
'''Comment''' – additional notes.
 

= Webhook notifications =

When an alert is raised or cleared and options '''Notify On Alert via Webhook''' or '''Notify On Clear via Webhook''' in the Alert are enabled, a HTTP request will be sent to each Contact in the Alert Group that has '''Webhook''' URL set. The request uses HTTP POST with JSON payload (Content-Type: application/json).

JSON Payload:

* '''type''' - Alert trigger type, either "ALERT" or "CLEAR".
* '''group_id''' - Alert Group ID.
* '''alert_id''' - Alert ID.
* '''alert_name''' - Alert name.
* '''object_id''' - ID of checked Object.
* '''object_name''' - human-readable Object name.
* '''cause''' - Alert type.
* '''value''' - current value.
* '''count''' - data count.
* '''timestamp''' - timestamp when Alert/Clear triggered.

Example payload:

{
"type": "ALERT",
"group_id": 12,
"alert_id": 42,
"alert_name": "Test",
"object_id": 123,
"object_name": "Example OP",
"cause": "CALLS TOTAL",
"value": 150.0,
"count": 150,
"timestamp": "2026-02-26 12:34:56"
}

= Alert vs Clear =

Example with CPU Load just to demonstrate what is Alert and what is Clear and proper usage of them.

[[File:alert_graph.png]]

 

=Examples=

===Send notification and change LCR on Alert===

Parameter: TOTAL CALLS 
Object Type: User 
Object Name: Prepaid 
Alert if >=: 300 
Clear if <=: 200 
LCR on alert: secondary LCR 
LCR on clear: Restore Original 
Group to Notify: support group 
Notify on Alert via Email: checked 
Period: 1h 
 
This Alert monitors all Calls done by Prepaid Users. If a Prepaid User makes more than 300 Calls during one hour period, his LCR will be changed to secondary LCR and Email notification will be sent to every contact on support group.
 
If User's Call count drops below 200 calls during one hour period, his LCR will be restored to original LCR
 

===Block user when simultaneous calls are detected===

Parameter: SIMULTANEOUS CALLS 
Object Type: User 
Object Name: All 
Alert if >=: 2 
Group to Notify: administration 
Notify on Alert via Email: checked 
Disable Object: checked 
Disable Clear: checked 
 
This Alert monitors simultaneous calls done by all Users. If a User makes more than (or equal to) 2 simultaneous Calls to the same destination, his account will be suspended and Email notification will be sent to every contact on administration group.
 
This alert will no be cleared automatically and user will stay suspended even if no more simultaneous calls are present.
 

===Block user if it spends more than 50 EUR in 24h===

Parameter: PRICE SUM 
Object Type: User 
Object Name: All 
Alerf if >= 50 
Group to Notify: administration 
Notify on Alert via Email: checked 
Disable Object: checked 
Disable Clear: checked 
Check last: 24 h 
 

===Alerts triggered by other Alerts===

Administrators are able to create alerts that depend on other alerts. What that means is, that you are able to create an alert that is triggered by a set or a subset of other alerts.

'''Example:'''
* Alert 1 is triggered when a specific user's ACD drops below ten seconds.
* Alert 2 is triggered when a the same user's Device's ASR drops below 50%.
* Alert 3 is triggered when both Alert 1 and Alert 2 is triggered, so that the technicians are notified.

In order to set up such a chain of events, you should first create Alert 1 and Alert 2.

Then, you should set up Alert 3.
 
[[File:Alert_group_parameter.png‎]]
 
* Configure your alert as usual, but instead of a specific parameter choose GROUP.
* Then, add the alert dependencies using the shown interface.

 
[[File:Alert_group_alert.png‎]]
 
* Set a number of alerts, that, when reached will trigger the alert.

 
[[File:Alert_group_clear.png‎]]
 
* Finally set up a number of alerts that will clear your alert.

These alerts can also be nested, without worrying about circular-dependencies, '''MOR''' simply will not let you make them.

 
=See also=

* [[Alert Schedules]]
* [[Alert Groups]]
* [[Alert Contacts]]
* [[ASR/ACD]]
* [[How to resolve long PDD]]

M4 Rate Notifications

2026-03-14T15:12:48Z

Admin: /* Template columns (Destination Group through Status) */

= Introduction =

Whenever there are Rate updates or changes in the Tariff some sort of communication must be made with Users that are using those Rates. Rate Notifications functionality eases manual tasks by allowing users to quickly and automatically create Jobs that inform Users about upcoming (depending on 'effective from' the value in the future) Rate prices and also await their confirmation whether they agree or disagree with them.

 
= Workflow schema =

The workflow can be visualized using the following schema:
 
[[File:RateNotification1.png]]
 

 
= Rate Notifications Templates =

[[File:RateNotificationTemplate1.png]]
 
The data is generated into an XLSX file. The system contains a Default template, which is assigned to all users.
 
[[File:RateNotificationTemplate2.png]]
 
It is possible to create a custom template file and use it for customers by clicking ADD NEW TEMPLATE and filling cells according to your needs, or uploading an XLSX Template file.
*Note: If a row has a value, the column near it cannot be blank.

 
=== Template columns (Destination Group through Status) ===
 
Each row in the template form maps a data type to an Excel column and an optional header name. '''Column''' is a dropdown (letter A, B, C, … or blank); 
'''Header Name''' is a text field (max 50 characters). If a column is left blank, that data is not written to the XLSX. The following rows appear in order:

* '''Destination Group''' — Column, Header Name. Exports: destination group name.
* '''Destination''' — Column, Header Name. Exports: destination name.
* '''Dial Code/Prefix''' — Column, Header Name. Exports: prefix.
* '''Rate''' — Column, Header Name. Exports: rate (decimal, 8 decimal places).
* '''Effective From''' — Column, Header Name. Exports: effective from date/time (in the user's time zone).
* '''Rate Difference''' — Column, Header Name. Exports: raw rate difference value.
* '''Rate Difference %''' — Column, Header Name. Exports: rate difference percentage.
* '''Connection Fee''' — Column, Header Name. Exports: connection fee.
* '''Increment''' — Column, Header Name. Exports: increment (seconds).
* '''Minimal Time''' — Column, Header Name. Exports: minimal time (seconds).
* '''Min. Time / Increment''' — Column, Header Name (default: "Min.Time/Increment"). Exports: minimal_time/increment (e.g. 60/1, 30/6). Leave column blank to omit.
* '''Billing Terms''' — Column, Header Name. Exports as: minimal_time/increment/0 (e.g. 60/1/0).
* '''Status''' — Column, Header Name. Exports: rate status (e.g., Active, Blocked, Deleted; comma-separated if multiple apply).

Custom Column 1–5 (below Status) each have Column, Header Name, and an optional '''Value''' field; the same fixed Value is written in every rate row for that column.

 
[[File:RateNotificationTemplate3.png]]
 
It is also possible to assign a Rate Notification Template for a User in their settings.
 
[[File:RateNotificationTemplate4.png]]
 

 

= Rate Notifications =

Rate Notifications is the primary page of the functionality, it displays unique Tariff - User associations to whom Notification can be sent. 
This page can be found in Menu -> BILLING -> Tariffs -> Rate Notifications
 
[[File:RateNotification2.png]]
 

Associated Tariff - User objects are shown only when the following conditions are met:
* Tariff is Sell type;
* User's Connection Point is assigned Sell Tariff in Origination Point settings;
* Tariff was modified and does not have any Rate Notification Job created for specific Tariff - User;
* Tariff was modified and a specific Tariff - User Rate Notification was created prior to Tariff modifications.

 
= Creating Rate Notification =

In order to create new Rate Notification Jobs, check wanted Tariff - User associations and press Set. 
All required Notifications can be selected by clicking the header checkbox.
 
[[File:RateNotification3.png]]
 
After selection, another page will be loaded with options for these specific Notifications. 
"Selected Tariffs - Users" displays marked associations to whom Notifications will be sent.
"Options" has several settings:
* Template - Rate Notification Template.
* Email Template: which Template will be used for email? The default "tariff_rate_notification" template is already present in the system and can be modified to fit specific needs.
** Additional possible variables:
*** rate_notification_tariff_name - Rate Notification's Tariff name
*** rate_notification_url_agree - Rate Notification's Agreement link
*** rate_notification_url_disagree - Rate Notifications' Disagreement link
*** rate_notification_decreases_effective_from - Rate Notifications' Decreases Effective From date
*** rate_notification_increases_effective_from - Rate Notifications' Increases Effective From date
* Rate Notification Type:
** Delta Only: future Rates only.
** Full: all future and currently active Rates.
* Agreement Timeout in days: timeout after which Notification will be automatically marked as disagreed (ignored) if the User did not respond. A Timeout adds a specified day's value to the Notification created time.
* If Client ignores Rate Notification - possible actions are: Block increased destinations after the timeout, allow increased destinations after the timeout.
* Decreases Effective From - select date and time.
* Increases Effective From - select date and time.
* Filename - Name of the notification file.
* Send Email:
** Every day: send an email every day until either the Agreement link is pressed or Agreement Timeout is reached
** Once: send email only one time.
 
[[File:RateNotification4.png]]
 
After pressing the Create button, Jobs will be created and the Rate Notification Jobs page will be loaded.
 
[[File:RateNotification5.png]]
 

 

= Rate Notification Jobs =

Rate Notification Jobs is the page where the system will automatically gather required Rates data, send emails, and awaits Users' response. 
This page can be found in Menu -> BILLING -> Tariffs -> Rate Notifications -> Jobs

Jobs have the following states: 
'''Assigned''' 
After Rate Notification is created a new Job appears as assigned.
 
[[File:RateNotification6.png]]
 

'''Date Generated''' 
The system checks for all newly assigned Jobs and generates required data in XLSX format, which can be downloaded from the list. The same exact file will be attached to the email. 
Rates will be converted using the default currency. To prevent conversion, setting - "Use Tariff currency in the CSV export" must be enabled. 
This setting can be found in Maintenance -> Settings -> Various -> Use Tariff currency in CSV export. 
 
[[File:RateNotification7.png]]
 

'''Email Sent''' 
All Jobs that have successfully generated data will send emails to Users with unique agree and disagree links which can be clicked on only once and within the specified timeout. 
'''Email will not be sent if there were no changes in rates!'''
 
[[File:RateNotification8.png]]
 

'''Completed''' 
Depending on the User's actions, the Job can be either agreed upon, disagreed with, or ignored. The list will display specific responses and the time it was responded to. Also, an additional email will be sent to Admin informing Rate Notification Job response status. 
 
[[File:RateNotification9.png]]
 

 
= Examples =

== Type: Full, Rate Notification Agreed ==

The user have tariff with some rates:
 
[[File:RateNotification10.png]]
 
Admin uploads new rates with some changes on prices and Effective from date in the future:
 
[[File:RateNotification11.png]]
 
In Billing > Tariffs > Rate Notifications, Admin now can see a new entries. Admin selects new entry and clicks “SET”:
 
[[File:RateNotification12.png]]
 
Then Admin selects “Full” to display old rates and new rates and click “Create”:
 
[[File:RateNotification13.png]]
 
New Rate Notification is created:
 
[[File:RateNotification14.png]]
 
The user gets email with two links:
 
[[File:RateNotification15.png]]
 
and file with rates comparison:
 
[[File:RateNotification16.png]]
 
After checking new rates, the User clicks on the first link in the email to agree with the new rates:
 
[[File:RateNotification17.png]]
 
Now, Admin gets an email about new rates being confirmed:
 
[[File:RateNotification18.png]]
 
And also sees the update status in the Rate Notifications Jobs list:
 
[[File:RateNotification19.png]]
 

== Type: Delta Only, Rate Notification Disagreed ==

The user has tariff with some rates
 
[[File:RateNotification20.png]]
 
Admin uploads new rates with some changes on prices and the Effective from date in the future.
 
In Billing > Tariffs > Rate Notifications, Admin can now see new entries. Admin selects new entry and clicks “SET”:
 
[[File:RateNotification21.png]]
 
Then Admin selects “Delta” to display only new rates and presses “Create”:
 
[[File:RateNotification22.png]]
 
Tariff Rate Notification Job(s) successfully created.
 
[[File:RateNotification23.png]]
 

After this, the user gets an email with two links with rates to compare:

Dear Partner, 
Please review the attached Tariff Rate changes. 
To confirm upcoming rate changes, please click the link below: 
http://123.123.123.123/billing/tariff_rate_notification_jobs/agree?id=1128bccbac519a04a4866c785f84f873eec6d5fd 
If You do not agree with the changes, please click the link below: 
http://123.123.123.123/billing/tariff_rate_notification_jobs/disagree?id=bcc02d82cf9d919af38bb4e4677685eeb0b382a8 
Thank you for your cooperation. 
 
[[File:RateNotification24.png]]
 
For example, the User disagrees and presses the second link. He can see the notification that Tariff Rate changes successfully disagreed.

After that Admin will receive an email that the client disagreed and will see the same status in Tariff Job.

Tariff Rate Notification ID: 2 was disagreed with by the client.
 
[[File:RateNotification25.png]]

When the User disagrees with the provided rates or ignores them, the system creates a Custom Tariff from the tariff assigned to Origination Point.

Custom Tariff includes increased rates, but these rates are blocked and calls will not pass over these destinations.

This Custom Tariff is assigned to Origination Point.

'''Note''':

1. If Origination Point already has Custom Tariff assigned, Custom Tariff from Rate Notification will be applied.

2. If Origination Point has assigned a Conditional Tariff and the User disagrees with the provided rates or ignores them, Custom Tariff is created, but is not assigned to Origination Point.

M4 Rate Notifications

2026-03-14T15:12:06Z

Admin: /* Rate Notifications Templates */

= Introduction =

Whenever there are Rate updates or changes in the Tariff some sort of communication must be made with Users that are using those Rates. Rate Notifications functionality eases manual tasks by allowing users to quickly and automatically create Jobs that inform Users about upcoming (depending on 'effective from' the value in the future) Rate prices and also await their confirmation whether they agree or disagree with them.

 
= Workflow schema =

The workflow can be visualized using the following schema:
 
[[File:RateNotification1.png]]
 

 
= Rate Notifications Templates =

[[File:RateNotificationTemplate1.png]]
 
The data is generated into an XLSX file. The system contains a Default template, which is assigned to all users.
 
[[File:RateNotificationTemplate2.png]]
 
It is possible to create a custom template file and use it for customers by clicking ADD NEW TEMPLATE and filling cells according to your needs, or uploading an XLSX Template file.
*Note: If a row has a value, the column near it cannot be blank.

 
=== Template columns (Destination Group through Status) ===

Each row in the template form maps a data type to an Excel column and an optional header name. '''Column''' is a dropdown (letter A, B, C, … or blank); '''Header Name''' is a text field (max 50 characters). If a column is left blank, that data is not written to the XLSX. The following rows appear in order:

* '''Destination Group''' — Column, Header Name. Exports: destination group name.
* '''Destination''' — Column, Header Name. Exports: destination name.
* '''Dial Code/Prefix''' — Column, Header Name. Exports: prefix.
* '''Rate''' — Column, Header Name. Exports: rate (decimal, 8 decimal places).
* '''Effective From''' — Column, Header Name. Exports: effective from date/time (in the user's time zone).
* '''Rate Difference''' — Column, Header Name. Exports: raw rate difference value.
* '''Rate Difference %''' — Column, Header Name. Exports: rate difference percentage.
* '''Connection Fee''' — Column, Header Name. Exports: connection fee.
* '''Increment''' — Column, Header Name. Exports: increment (seconds).
* '''Minimal Time''' — Column, Header Name. Exports: minimal time (seconds).
* '''Min. Time / Increment''' — Column, Header Name (default: "Min.Time/Increment"). Exports: minimal_time/increment (e.g. 60/1, 30/6). Leave column blank to omit.
* '''Billing Terms''' — Column, Header Name. Exports as: minimal_time/increment/0 (e.g. 60/1/0).
* '''Status''' — Column, Header Name. Exports: rate status (e.g., Active, Blocked, Deleted; comma-separated if multiple apply).

Custom Column 1–5 (below Status) each have Column, Header Name, and an optional '''Value''' field; the same fixed Value is written in every rate row for that column.

 
[[File:RateNotificationTemplate3.png]]
 
It is also possible to assign a Rate Notification Template for a User in their settings.
 
[[File:RateNotificationTemplate4.png]]
 

 

= Rate Notifications =

Rate Notifications is the primary page of the functionality, it displays unique Tariff - User associations to whom Notification can be sent. 
This page can be found in Menu -> BILLING -> Tariffs -> Rate Notifications
 
[[File:RateNotification2.png]]
 

Associated Tariff - User objects are shown only when the following conditions are met:
* Tariff is Sell type;
* User's Connection Point is assigned Sell Tariff in Origination Point settings;
* Tariff was modified and does not have any Rate Notification Job created for specific Tariff - User;
* Tariff was modified and a specific Tariff - User Rate Notification was created prior to Tariff modifications.

 
= Creating Rate Notification =

In order to create new Rate Notification Jobs, check wanted Tariff - User associations and press Set. 
All required Notifications can be selected by clicking the header checkbox.
 
[[File:RateNotification3.png]]
 
After selection, another page will be loaded with options for these specific Notifications. 
"Selected Tariffs - Users" displays marked associations to whom Notifications will be sent.
"Options" has several settings:
* Template - Rate Notification Template.
* Email Template: which Template will be used for email? The default "tariff_rate_notification" template is already present in the system and can be modified to fit specific needs.
** Additional possible variables:
*** rate_notification_tariff_name - Rate Notification's Tariff name
*** rate_notification_url_agree - Rate Notification's Agreement link
*** rate_notification_url_disagree - Rate Notifications' Disagreement link
*** rate_notification_decreases_effective_from - Rate Notifications' Decreases Effective From date
*** rate_notification_increases_effective_from - Rate Notifications' Increases Effective From date
* Rate Notification Type:
** Delta Only: future Rates only.
** Full: all future and currently active Rates.
* Agreement Timeout in days: timeout after which Notification will be automatically marked as disagreed (ignored) if the User did not respond. A Timeout adds a specified day's value to the Notification created time.
* If Client ignores Rate Notification - possible actions are: Block increased destinations after the timeout, allow increased destinations after the timeout.
* Decreases Effective From - select date and time.
* Increases Effective From - select date and time.
* Filename - Name of the notification file.
* Send Email:
** Every day: send an email every day until either the Agreement link is pressed or Agreement Timeout is reached
** Once: send email only one time.
 
[[File:RateNotification4.png]]
 
After pressing the Create button, Jobs will be created and the Rate Notification Jobs page will be loaded.
 
[[File:RateNotification5.png]]
 

 

= Rate Notification Jobs =

Rate Notification Jobs is the page where the system will automatically gather required Rates data, send emails, and awaits Users' response. 
This page can be found in Menu -> BILLING -> Tariffs -> Rate Notifications -> Jobs

Jobs have the following states: 
'''Assigned''' 
After Rate Notification is created a new Job appears as assigned.
 
[[File:RateNotification6.png]]
 

'''Date Generated''' 
The system checks for all newly assigned Jobs and generates required data in XLSX format, which can be downloaded from the list. The same exact file will be attached to the email. 
Rates will be converted using the default currency. To prevent conversion, setting - "Use Tariff currency in the CSV export" must be enabled. 
This setting can be found in Maintenance -> Settings -> Various -> Use Tariff currency in CSV export. 
 
[[File:RateNotification7.png]]
 

'''Email Sent''' 
All Jobs that have successfully generated data will send emails to Users with unique agree and disagree links which can be clicked on only once and within the specified timeout. 
'''Email will not be sent if there were no changes in rates!'''
 
[[File:RateNotification8.png]]
 

'''Completed''' 
Depending on the User's actions, the Job can be either agreed upon, disagreed with, or ignored. The list will display specific responses and the time it was responded to. Also, an additional email will be sent to Admin informing Rate Notification Job response status. 
 
[[File:RateNotification9.png]]
 

 
= Examples =

== Type: Full, Rate Notification Agreed ==

The user have tariff with some rates:
 
[[File:RateNotification10.png]]
 
Admin uploads new rates with some changes on prices and Effective from date in the future:
 
[[File:RateNotification11.png]]
 
In Billing > Tariffs > Rate Notifications, Admin now can see a new entries. Admin selects new entry and clicks “SET”:
 
[[File:RateNotification12.png]]
 
Then Admin selects “Full” to display old rates and new rates and click “Create”:
 
[[File:RateNotification13.png]]
 
New Rate Notification is created:
 
[[File:RateNotification14.png]]
 
The user gets email with two links:
 
[[File:RateNotification15.png]]
 
and file with rates comparison:
 
[[File:RateNotification16.png]]
 
After checking new rates, the User clicks on the first link in the email to agree with the new rates:
 
[[File:RateNotification17.png]]
 
Now, Admin gets an email about new rates being confirmed:
 
[[File:RateNotification18.png]]
 
And also sees the update status in the Rate Notifications Jobs list:
 
[[File:RateNotification19.png]]
 

== Type: Delta Only, Rate Notification Disagreed ==

The user has tariff with some rates
 
[[File:RateNotification20.png]]
 
Admin uploads new rates with some changes on prices and the Effective from date in the future.
 
In Billing > Tariffs > Rate Notifications, Admin can now see new entries. Admin selects new entry and clicks “SET”:
 
[[File:RateNotification21.png]]
 
Then Admin selects “Delta” to display only new rates and presses “Create”:
 
[[File:RateNotification22.png]]
 
Tariff Rate Notification Job(s) successfully created.
 
[[File:RateNotification23.png]]
 

After this, the user gets an email with two links with rates to compare:

Dear Partner, 
Please review the attached Tariff Rate changes. 
To confirm upcoming rate changes, please click the link below: 
http://123.123.123.123/billing/tariff_rate_notification_jobs/agree?id=1128bccbac519a04a4866c785f84f873eec6d5fd 
If You do not agree with the changes, please click the link below: 
http://123.123.123.123/billing/tariff_rate_notification_jobs/disagree?id=bcc02d82cf9d919af38bb4e4677685eeb0b382a8 
Thank you for your cooperation. 
 
[[File:RateNotification24.png]]
 
For example, the User disagrees and presses the second link. He can see the notification that Tariff Rate changes successfully disagreed.

After that Admin will receive an email that the client disagreed and will see the same status in Tariff Job.

Tariff Rate Notification ID: 2 was disagreed with by the client.
 
[[File:RateNotification25.png]]

When the User disagrees with the provided rates or ignores them, the system creates a Custom Tariff from the tariff assigned to Origination Point.

Custom Tariff includes increased rates, but these rates are blocked and calls will not pass over these destinations.

This Custom Tariff is assigned to Origination Point.

'''Note''':

1. If Origination Point already has Custom Tariff assigned, Custom Tariff from Rate Notification will be applied.

2. If Origination Point has assigned a Conditional Tariff and the User disagrees with the provided rates or ignores them, Custom Tariff is created, but is not assigned to Origination Point.

MOR API did details update

2026-03-12T16:01:11Z

Admin:

=Description=

[[MOR API]] DID details update

Please note that only the admin, the accountant (with device management), those with permission, and the 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 a Reseller or a 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, 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 parameter value (custom_sip_header=) removes the existing value.
* '''comment''' - main DID comment. An empty value of the parameter (comment=) clears the existing value. '''Optional'''
* '''reseller_comment''' - reseller-specific DID comment. An empty value of the parameter (reseller_comment=) clears the existing value. '''Optional'''
 

===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, the DID action log record is added.'''
 
----
'''Errors'''
* <error>Access Denied</error> – Specified username (u) does not exist, or u is not an 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 a positive number.
* <error>DID is already assigned</error> – DID is already assigned to another 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 details update

2026-03-12T16:00:34Z

Admin: /* 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 a Reseller or a 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, 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 parameter value (custom_sip_header=) removes the existing value.
* '''comment''' - main DID comment. An empty value of the parameter (comment=) clears the existing value. '''Optional'''
* '''reseller_comment''' - reseller-specific DID comment. An empty value of the parameter (reseller_comment=) clears the existing value. '''Optional'''
 

===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]]

Re-INVITE UDP fragmentation

2026-03-05T16:15:16Z

Admin:

'''Problem''' 
The client sends SIP re-INVITEs over UDP that exceed the standard MTU (e.g. 1529 bytes > 1500 bytes). The re-INVITE is fragmented at the IP layer. On your side, re-INVITEs do not appear in traces; the client receives no response, and the call ends. Initial INVITE is within MTU and works; only the larger re-INVITE is affected.

 
'''Root cause''' 
Fragmented UDP packets are dropped by your NAT/firewall (or possibly by the server interface). Only the first fragment or no fragments are delivered, so the proxy (M4) never sees the full re-INVITE and does not respond.

 
== Solution ==

 
'''1. Review network equipment''' 
Check NAT and firewall settings for handling of fragmented UDP packets. Allow or correctly reassemble fragmented UDP so that re-INVITEs reach the M4 server. If you cannot change how fragmented UDP is handled, use the TCP option below.

 
'''2. Use TCP for SIP (workaround)''' 
If fragmented UDP cannot be fixed on the network side, use TCP for SIP instead of UDP. TCP may be handled differently by your NAT/firewall.

* On M4: enable TCP for SIP in the Operator Panel (OP): '''Advanced''' (or advanced section) → enable TCP for SIP. Verify the exact menu label in the application.
* On the client: configure the SIP stack to send signaling over TCP to M4 (same destination IP/port, TCP instead of UDP).

 
'''3. Verify with tests''' 
To confirm that oversized UDP is fragmented and that fragments are dropped on your side, use the following from a client machine and capture on the server.

* From the client (replace <code>xx.xx.xx.xx</code> with the M4/server IP, use a port that nothing listens on, e.g. 1234): 
** Non-fragmented (payload 1472 + 28 = 1500 bytes, within MTU): <code>hping3 -p 1234 -c 3 --udp -d 1472 xx.xx.xx.xx</code> 
** Fragmented (payload 1473 + 28 = 1501 bytes, over MTU): <code>hping3 -p 1234 -c 3 --udp -d 1473 xx.xx.xx.xx</code>
* Interpretation: if UDP is delivered, the host will respond with ICMP “port unreachable,” and you will see 0% packet loss. If only the 1472-byte test shows 0% loss and the 1473-byte test shows loss, fragmented UDP is being dropped.
* On the server, to see what actually arrives (replace <code>yy.yy.yy.yy</code> with the client IP): <code>tcpdump -i any -nn 'host yy.yy.yy.yy and not tcp'</code>. The <code>not tcp</code> filter prevents your SSH session from being captured. Compare what you see when sending 1472 vs 1473 bytes from the client.

 
Example where red is oversized packets and green are good UDP packets:

[[File:2603051804.png]]

 
'''Related''' 
If the initial INVITE is also too large (e.g., many codecs in SDP), reducing the SDP size (e.g., only needed codecs) can keep packets under MTU; see [[MOR_does_not_send_Contact_header | MOR does not send Contact header]]. For NAT and port forwarding in general, see [[M4_under_NAT | M4 under NAT]].

 
== See also ==
* [[MOR does not send Contact header]]

MOR does not send Contact header

2026-03-05T16:15:08Z

Admin:

= Problem Description=
MOR does not include a Contact header in 180/183/200 OK SIP messages sent back to the originating device.
The device drops the call immediately after the call is answered.

 
== Possible reasons ==
This can happen if the ACK message from the client for MOR 401 Unauthorized reaches MOR '''after second''' Invite.

[[File:Ack_after_invite.png]] 

As can be seen in the image, packets arrived in MOR out of order; the second Invite reached MOR before the ACK.
This can happen if the INVITE packet is too big and is fragmented by the IP stack.

 
== Possible solutions ==

As mentioned, the INVITE packet can be fragmented by the IP stack if it is too big.
An INVITE packet is usually too large when there are many codecs in the SDP, so one way to avoid fragmentation is to ask the client to send only the codecs that are actually needed.
For example, if in MOR Device settings only G729 and G711 codecs are enabled, the client should send only these codecs, as MOR will not use any others.

With only the necessary codecs in INVITE, packets will be smaller and not fragmented, which should prevent the IP stack from reordering them.

[[File:Ack_before_invite.png]] 

 
== Note about Wireshark and GUI pcaps ==

If packets are fragmented, PCAPS in the GUI will not show such packets at all.
To see such packets, raw pcap must be downloaded and Wireshark option '''Reassemble fragmented IPv4 datagrams''' must be '''disabled''' (not checked) in Edit->Preferences->Protocols->IPv4 before doing any filtering on a raw pcap.

[[File:Wireshark_reassemble.png]] 

 
== See also ==
* [[Re-INVITE UDP fragmentation]]

MOR does not send Contact header

2026-03-05T16:14:38Z

Admin:

= Problem Description=
MOR does not include a Contact header in 180/183/200 OK SIP messages sent back to the originating device.
The device drops the call immediately after the call was answered.

 
== Possible reasons ==
This can happen if the ACK message from the client for MOR 401 Unauthorized reaches MOR '''after second''' Invite.

[[File:Ack_after_invite.png]] 

As can be seen in the image, packets arrived in MOR out of order; the second Invite reached MOR before the ACK.
This can happen if the INVITE packet is too big and is fragmented by the IP stack.

 
== Possible solutions ==

As mentioned, the INVITE packet can be fragmented by the IP stack if it is too big.
An INVITE packet is usually too large when there are many codecs in the SDP, so one way to avoid fragmentation is to ask the client to send only the codecs that are actually needed.
For example, if in MOR Device settings only G729 and G711 codecs are enabled, the client should send only these codecs, as MOR will not use any others.

With only the necessary codecs in INVITE, packets will be smaller and not fragmented, which should prevent the IP stack from reordering them.

[[File:Ack_before_invite.png]] 

 
== Note about Wireshark and GUI pcaps ==

If packets are fragmented, PCAPS in the GUI will not show such packets at all.
To see such packets, raw pcap must be downloaded and Wireshark option '''Reassemble fragmented IPv4 datagrams''' must be '''disabled''' (not checked) in Edit->Preferences->Protocls->IPv4 before doing any filtering on a raw pcap.

[[File:Wireshark_reassemble.png]] 

 
=== See also ===
* [[Re-INVITE UDP fragmentation]]

Re-INVITE UDP fragmentation

2026-03-05T16:14:04Z

Admin:

'''Problem''' 
The client sends SIP re-INVITEs over UDP that exceed the standard MTU (e.g. 1529 bytes > 1500 bytes). The re-INVITE is fragmented at the IP layer. On your side, re-INVITEs do not appear in traces; the client receives no response, and the call ends. Initial INVITE is within MTU and works; only the larger re-INVITE is affected.

 
'''Root cause''' 
Fragmented UDP packets are dropped by your NAT/firewall (or possibly by the server interface). Only the first fragment or no fragments are delivered, so the proxy (M4) never sees the full re-INVITE and does not respond.

 
== Solution ==

 
'''1. Review network equipment''' 
Check NAT and firewall settings for handling of fragmented UDP packets. Allow or correctly reassemble fragmented UDP so that re-INVITEs reach the M4 server. If you cannot change how fragmented UDP is handled, use the TCP option below.

 
'''2. Use TCP for SIP (workaround)''' 
If fragmented UDP cannot be fixed on the network side, use TCP for SIP instead of UDP. TCP may be handled differently by your NAT/firewall.

* On M4: enable TCP for SIP in the Operator Panel (OP): '''Advanced''' (or advanced section) → enable TCP for SIP. Verify the exact menu label in the application.
* On the client: configure the SIP stack to send signaling over TCP to M4 (same destination IP/port, TCP instead of UDP).

 
'''3. Verify with tests''' 
To confirm that oversized UDP is fragmented and that fragments are dropped on your side, use the following from a client machine and capture on the server.

* From the client (replace <code>xx.xx.xx.xx</code> with the M4/server IP, use a port that nothing listens on, e.g. 1234): 
** Non-fragmented (payload 1472 + 28 = 1500 bytes, within MTU): <code>hping3 -p 1234 -c 3 --udp -d 1472 xx.xx.xx.xx</code> 
** Fragmented (payload 1473 + 28 = 1501 bytes, over MTU): <code>hping3 -p 1234 -c 3 --udp -d 1473 xx.xx.xx.xx</code>
* Interpretation: if UDP is delivered, the host will respond with ICMP “port unreachable,” and you will see 0% packet loss. If only the 1472-byte test shows 0% loss and the 1473-byte test shows loss, fragmented UDP is being dropped.
* On the server, to see what actually arrives (replace <code>yy.yy.yy.yy</code> with the client IP): <code>tcpdump -i any -nn 'host yy.yy.yy.yy and not tcp'</code>. The <code>not tcp</code> filter prevents your SSH session from being captured. Compare what you see when sending 1472 vs 1473 bytes from the client.

 
Example where red is oversized packets and green are good UDP packets:

[[File:2603051804.png]]

 
'''Related''' 
If the initial INVITE is also too large (e.g., many codecs in SDP), reducing the SDP size (e.g., only needed codecs) can keep packets under MTU; see [[MOR_does_not_send_Contact_header | MOR does not send Contact header]]. For NAT and port forwarding in general, see [[M4_under_NAT | M4 under NAT]].

 
=== See also ===
* [[MOR does not send Contact header]]

MOR does not send Contact header

2026-03-05T16:13:38Z

Admin: /* Possible solutions */

= Problem Description=
MOR does not include a Contact header in 180/183/200 OK SIP messages sent back to the originating device.
The device drops the call immediately after the call was answered.

 
== Possible reasons ==
This can happen if the ACK message from the client for MOR 401 Unauthorized reaches MOR '''after second''' Invite.

[[File:Ack_after_invite.png]] 

As can be seen in the image, packets arrived in MOR out of order; the second Invite reached MOR before the ACK.
This can happen if the INVITE packet is too big and is fragmented by the IP stack.

 
== Possible solutions ==

As mentioned, the INVITE packet can be fragmented by the IP stack if it is too big.
An INVITE packet is usually too large when there are many codecs in the SDP, so one way to avoid fragmentation is to ask the client to send only the codecs that are actually needed.
For example, if in MOR Device settings only G729 and G711 codecs are enabled, the client should send only these codecs, as MOR will not use any others.

With only the necessary codecs in INVITE, packets will be smaller and not fragmented, which should prevent the IP stack from reordering them.

[[File:Ack_before_invite.png]] 

 
=== See also ===
* [[Re-INVITE UDP fragmentation]]

== Note about Wireshark and GUI pcaps ==

If packets are fragmented, PCAPS in the GUI will not show such packets at all.
To see such packets, raw pcap must be downloaded and Wireshark option '''Reassemble fragmented IPv4 datagrams''' must be '''disabled''' (not checked) in Edit->Preferences->Protocls->IPv4 before doing any filtering on a raw pcap.

[[File:Wireshark_reassemble.png]]

MOR does not send Contact header

2026-03-05T16:12:35Z

Admin: /* Possible reasons */

= Problem Description=
MOR does not include a Contact header in 180/183/200 OK SIP messages sent back to the originating device.
The device drops the call immediately after the call was answered.

 
== Possible reasons ==
This can happen if the ACK message from the client for MOR 401 Unauthorized reaches MOR '''after second''' Invite.

[[File:Ack_after_invite.png]] 

As can be seen in the image, packets arrived in MOR out of order; the second Invite reached MOR before the ACK.
This can happen if the INVITE packet is too big and is fragmented by the IP stack.

== Possible solutions ==

As mentioned, the INVITE packet can be fragmented by the IP stack if it is too big.
INVITE packet is usually too big when there are a lot of codecs in SDP, so one solution to make sure that packet is not fragmented is to ask the client to send only codes which are actually needed.
For example, if in MOR Device settings, only G729 and G711 codecs are enabled, the client should send only these codecs, as all others will not be used by MOR in any case.

With only needed codecs in INVITE, packets will be smaller and not fragmented, and this should prevent the IP stack from reordering them.

[[File:Ack_before_invite.png]] 

 
== Note about Wireshark and GUI pcaps ==

If packets are fragmented, PCAPS in the GUI will not show such packets at all.
To see such packets, raw pcap must be downloaded and Wireshark option '''Reassemble fragmented IPv4 datagrams''' must be '''disabled''' (not checked) in Edit->Preferences->Protocls->IPv4 before doing any filtering on a raw pcap.

[[File:Wireshark_reassemble.png]]

MOR does not send Contact header

2026-03-05T16:12:22Z

Admin: /* Note about Wireshark and GUI pcaps */

= Problem Description=
MOR does not include a Contact header in 180/183/200 OK SIP messages sent back to the originating device.
The device drops the call immediately after the call was answered.

== Possible reasons ==
This can happen if the ACK message from the client for MOR 401 Unauthorized reaches MOR '''after second''' Invite.

[[File:Ack_after_invite.png]] 

As can be seen in the image, packets arrived in MOR out of the order, the second Invite reached MOR before the ACK.
This can happen if the INVITE packet is too big and is fragmented by the IP stack.

== Possible solutions ==

As mentioned, the INVITE packet can be fragmented by the IP stack if it is too big.
INVITE packet is usually too big when there are a lot of codecs in SDP, so one solution to make sure that packet is not fragmented is to ask the client to send only codes which are actually needed.
For example, if in MOR Device settings, only G729 and G711 codecs are enabled, the client should send only these codecs, as all others will not be used by MOR in any case.

With only needed codecs in INVITE, packets will be smaller and not fragmented, and this should prevent the IP stack from reordering them.

[[File:Ack_before_invite.png]] 

 
== Note about Wireshark and GUI pcaps ==

If packets are fragmented, PCAPS in the GUI will not show such packets at all.
To see such packets, raw pcap must be downloaded and Wireshark option '''Reassemble fragmented IPv4 datagrams''' must be '''disabled''' (not checked) in Edit->Preferences->Protocls->IPv4 before doing any filtering on a raw pcap.

[[File:Wireshark_reassemble.png]]

Re-INVITE UDP fragmentation

2026-03-05T16:11:52Z

Admin:

Call hangs after 15 minutes

2026-03-05T16:10:27Z

Admin: /* POSSIBLE SOLUTIONS */

The switch may not be responding to the SIP re-INVITE.

Some providers perform a SIP re-INVITE every 15 minutes for any active calls. It's a way of checking if the call is indeed still active. If an appropriate 200 OK is not received back, they disconnect the call.

 
= POSSIBLE CAUSES/SOLUTIONS =

 
=== Change Provider ===

Change the Provider and check if the issue is gone to confirm the origin of the problem.

 
=== Canreinvite setting ===

Set '''canreinvite''' to '''yes''' in the Device's Edit window.

 
=== UDP fragmentation ===

Oversized UDP packets (>1500) may be dropped at some point. That prevents the oversized Re-Invite packets from reaching the system, halting the call.

More details and how to test here: [[Re-INVITE UDP fragmentation]]

 
=== Solve NAT issues ===
* Make sure the network is configured properly, and all packets reach the Softswitch.
* Do pcap capture and analyze the logs.
** check the domain in the request URI
** check if Public IP addresses are placed in SIP headers
 

=== Adjust session timers ===

In the Device or Provider settings page, you can change these parameters:

session-timers

session-expires

session-minse

session-refresher

Check which settings the User or Provider requires and set them accordingly.

 

=== Disable session timers (not recommended) ===

In the general section in /etc/asterisk/sip.conf: session-timers=refuse

It can be done per Device on the Device Settings page.


IMPORTANT: The Drawback is that a call can appear to run forever if the BYE message is lost due to network issues.

 

=== MicroSIP example ===

Example lines from MicroSIP invite:

Supported: replaces, 100rel, timer, norefersub
Session-Expires: 1800
Min-SE: 90
User-Agent: MicroSIP/3.21.6

By default, this means that MOR should send a re-INVITE after half the Session-Expires value (1800/2 = 900 seconds = 15 minutes) to ensure the SIP session remains active.

If we can see from the SIP trace that microSIP does not respond to MOR ReINVITES (and then MOR drops the call), you can try the following in the device settings that represent the SIP device:

a) Set SIP Session Refresher: to UAC (default is UAS). This means that microSIP will send re-INVITES to MOR; maybe this will work better. (Under MicroSIP's Devices settings)

b) Another approach is to set the SIP Session Timers to refuse

 

= See also =
* [https://tools.ietf.org/html/rfc4028 Session Timers in the Session Initiation Protocol (SIP) RFC 4028]
* https://andrewjprokop.wordpress.com/2015/02/10/understanding-sip-re-invite

Call hangs after 15 minutes

2026-03-05T16:10:03Z

Admin: /* POSSIBLE SOLUTIONS */

The switch may not be responding to the SIP re-INVITE.

Some providers perform a SIP re-INVITE every 15 minutes for any active calls. It's a way of checking if the call is indeed still active. If an appropriate 200 OK is not received back, they disconnect the call.

 
= POSSIBLE SOLUTIONS =

 
=== Change Provider ===

Change the Provider and check if the issue is gone to confirm the origin of the problem.

 
=== Canreinvite setting ===

Set '''canreinvite''' to '''yes''' in the Device's Edit window.

 
=== UDP fragmentation ===

Oversized UDP packets (>1500) may be dropped at some point. That prevents the oversized Re-Invite packets from reaching the system, halting the call.

More details and how to test here: [[Re-INVITE UDP fragmentation]]

 
=== Solve NAT issues ===
* Make sure the network is configured properly, and all packets reach the Softswitch.
* Do pcap capture and analyze the logs.
** check the domain in the request URI
** check if Public IP addresses are placed in SIP headers
 

=== Adjust session timers ===

In the Device or Provider settings page, you can change these parameters:

session-timers

session-expires

session-minse

session-refresher

Check which settings the User or Provider requires and set them accordingly.

 

=== Disable session timers (not recommended) ===

In the general section in /etc/asterisk/sip.conf: session-timers=refuse

It can be done per Device on the Device Settings page.


IMPORTANT: The Drawback is that a call can appear to run forever if the BYE message is lost due to network issues.

 

=== MicroSIP example ===

Example lines from MicroSIP invite:

Supported: replaces, 100rel, timer, norefersub
Session-Expires: 1800
Min-SE: 90
User-Agent: MicroSIP/3.21.6

By default, this means that MOR should send a re-INVITE after half the Session-Expires value (1800/2 = 900 seconds = 15 minutes) to ensure the SIP session remains active.

If we can see from the SIP trace that microSIP does not respond to MOR ReINVITES (and then MOR drops the call), you can try the following in the device settings that represent the SIP device:

a) Set SIP Session Refresher: to UAC (default is UAS). This means that microSIP will send re-INVITES to MOR; maybe this will work better. (Under MicroSIP's Devices settings)

b) Another approach is to set the SIP Session Timers to refuse

 

= See also =
* [https://tools.ietf.org/html/rfc4028 Session Timers in the Session Initiation Protocol (SIP) RFC 4028]
* https://andrewjprokop.wordpress.com/2015/02/10/understanding-sip-re-invite

Re-INVITE UDP fragmentation

2026-03-05T16:05:26Z

Admin:

'''Problem''' 
The client sends SIP re-INVITEs over UDP that exceed the standard MTU (e.g. 1529 bytes > 1500 bytes). The re-INVITE is fragmented at the IP layer. On your side, re-INVITEs do not appear in traces; the client receives no response, and the call ends. Initial INVITE is within MTU and works; only the larger re-INVITE is affected.

 
'''Root cause''' 
Fragmented UDP packets are dropped by your NAT/firewall (or possibly by the server interface). Only the first fragment or no fragments are delivered, so the proxy (M4) never sees the full re-INVITE and does not respond.

 
== Solution ==

 
'''1. Review network equipment''' 
Check NAT and firewall settings for handling of fragmented UDP packets. Allow or correctly reassemble fragmented UDP so that re-INVITEs reach the M4 server. If you cannot change how fragmented UDP is handled, use the TCP option below.

 
'''2. Use TCP for SIP (workaround)''' 
If fragmented UDP cannot be fixed on the network side, use TCP for SIP instead of UDP. TCP may be handled differently by your NAT/firewall.

* On M4: enable TCP for SIP in the Operator Panel (OP): '''Advanced''' (or advanced section) → enable TCP for SIP. Verify the exact menu label in the application.
* On the client: configure the SIP stack to send signaling over TCP to M4 (same destination IP/port, TCP instead of UDP).

 
'''3. Verify with tests''' 
To confirm that oversized UDP is fragmented and that fragments are dropped on your side, use the following from a client machine and capture on the server.

* From the client (replace <code>xx.xx.xx.xx</code> with the M4/server IP, use a port that nothing listens on, e.g. 1234): 
** Non-fragmented (payload 1472 + 28 = 1500 bytes, within MTU): <code>hping3 -p 1234 -c 3 --udp -d 1472 xx.xx.xx.xx</code> 
** Fragmented (payload 1473 + 28 = 1501 bytes, over MTU): <code>hping3 -p 1234 -c 3 --udp -d 1473 xx.xx.xx.xx</code>
* Interpretation: if UDP is delivered, the host will respond with ICMP “port unreachable,” and you will see 0% packet loss. If only the 1472-byte test shows 0% loss and the 1473-byte test shows loss, fragmented UDP is being dropped.
* On the server, to see what actually arrives (replace <code>yy.yy.yy.yy</code> with the client IP): <code>tcpdump -i any -nn 'host yy.yy.yy.yy and not tcp'</code>. The <code>not tcp</code> filter prevents your SSH session from being captured. Compare what you see when sending 1472 vs 1473 bytes from the client.

 
Example where red is oversized packets and green are good UDP packets:

[[File:2603051804.png]]

 
'''Related''' 
If the initial INVITE is also too large (e.g., many codecs in SDP), reducing the SDP size (e.g., only needed codecs) can keep packets under MTU; see [[MOR_does_not_send_Contact_header]]. For NAT and port forwarding in general, see [[M4_under_NAT]].

Re-INVITE UDP fragmentation

2026-03-05T16:05:06Z

Admin:

'''Problem''' 
The client sends SIP re-INVITEs over UDP that exceed the standard MTU (e.g. 1529 bytes > 1500 bytes). The re-INVITE is fragmented at the IP layer. On your side, re-INVITEs do not appear in traces; the client receives no response, and the call ends. Initial INVITE is within MTU and works; only the larger re-INVITE is affected.

 
'''Root cause''' 
Fragmented UDP packets are dropped by your NAT/firewall (or possibly by the server interface). Only the first fragment or no fragments are delivered, so the proxy (M4) never sees the full re-INVITE and does not respond.

 
== Solution ==

 
'''1. Review network equipment''' 
Check NAT and firewall settings for handling of fragmented UDP packets. Allow or correctly reassemble fragmented UDP so that re-INVITEs reach the M4 server. If you cannot change how fragmented UDP is handled, use the TCP option below.

 
'''2. Use TCP for SIP (workaround)''' 
If fragmented UDP cannot be fixed on the network side, use TCP for SIP instead of UDP. TCP may be handled differently by your NAT/firewall.

* On M4: enable TCP for SIP in the Operator Panel (OP): '''Advanced''' (or advanced section) → enable TCP for SIP. Verify the exact menu label in the application.
* On the client: configure the SIP stack to send signaling over TCP to M4 (same destination IP/port, TCP instead of UDP).

 
'''3. Verify with tests''' 
To confirm that oversized UDP is fragmented and that fragments are dropped on your side, use the following from a client machine and capture on the server.

* From the client (replace <code>xx.xx.xx.xx</code> with the M4/server IP, use a port that nothing listens on, e.g. 1234): 
** Non-fragmented (payload 1472 + 28 = 1500 bytes, within MTU): <code>hping3 -p 1234 -c 3 --udp -d 1472 xx.xx.xx.xx</code> 
** Fragmented (payload 1473 + 28 = 1501 bytes, over MTU): <code>hping3 -p 1234 -c 3 --udp -d 1473 xx.xx.xx.xx</code>
* Interpretation: if UDP is delivered, the host will respond with ICMP “port unreachable,” and you will see 0% packet loss. If only the 1472-byte test shows 0% loss and the 1473-byte test shows loss, fragmented UDP is being dropped.
* On the server, to see what actually arrives (replace <code>yy.yy.yy.yy</code> with the client IP): <code>tcpdump -i any -nn 'host yy.yy.yy.yy and not tcp'</code>. The <code>not tcp</code> filter prevents your SSH session from being captured. Compare what you see when sending 1472 vs 1473 bytes from the client.

Example where red is oversized packets and green are good UDP packets:

[[File:2603051804.png]]

 
'''Related''' 
If the initial INVITE is also too large (e.g., many codecs in SDP), reducing the SDP size (e.g., only needed codecs) can keep packets under MTU; see [[MOR_does_not_send_Contact_header]]. For NAT and port forwarding in general, see [[M4_under_NAT]].

File:2603051804.png

2026-03-05T16:04:49Z

Admin:

Re-INVITE UDP fragmentation

2026-03-05T15:56:24Z

Admin: Created page with "'''Problem''' The client sends SIP re-INVITEs over UDP that exceed the standard MTU (e.g. 1529 bytes > 1500 bytes). The re-INVITE is fragmented at the IP layer. On your side, re-INVITEs do not appear in traces; the client receives no response, and the call ends. Initial INVITE is within MTU and works; only the larger re-INVITE is affected. '''Root cause''' Fragmented UDP packets are dropped by your NAT/firewall (or possibly by the server interface). Only..."

'''Problem''' 
The client sends SIP re-INVITEs over UDP that exceed the standard MTU (e.g. 1529 bytes > 1500 bytes). The re-INVITE is fragmented at the IP layer. On your side, re-INVITEs do not appear in traces; the client receives no response, and the call ends. Initial INVITE is within MTU and works; only the larger re-INVITE is affected.

 
'''Root cause''' 
Fragmented UDP packets are dropped by your NAT/firewall (or possibly by the server interface). Only the first fragment or no fragments are delivered, so the proxy (M4) never sees the full re-INVITE and does not respond.

 
== Solution ==

 
'''1. Review network equipment''' 
Check NAT and firewall settings for handling of fragmented UDP packets. Allow or correctly reassemble fragmented UDP so that re-INVITEs reach the M4 server. If you cannot change how fragmented UDP is handled, use the TCP option below.

 
'''2. Use TCP for SIP (workaround)''' 
If fragmented UDP cannot be fixed on the network side, use TCP for SIP instead of UDP. TCP may be handled differently by your NAT/firewall.

* On M4: enable TCP for SIP in the Operator Panel (OP): '''Advanced''' (or advanced section) → enable TCP for SIP. Verify the exact menu label in the application.
* On the client: configure the SIP stack to send signaling over TCP to M4 (same destination IP/port, TCP instead of UDP).

 
'''3. Verify with tests''' 
To confirm that oversized UDP is fragmented and that fragments are dropped on your side, use the following from a client machine and capture on the server.

* From the client (replace <code>xx.xx.xx.xx</code> with the M4/server IP, use a port that nothing listens on, e.g. 1234): 
** Non-fragmented (payload 1472 + 28 = 1500 bytes, within MTU): <code>hping3 -p 1234 -c 3 --udp -d 1472 xx.xx.xx.xx</code> 
** Fragmented (payload 1473 + 28 = 1501 bytes, over MTU): <code>hping3 -p 1234 -c 3 --udp -d 1473 xx.xx.xx.xx</code>
* Interpretation: if UDP is delivered, the host will respond with ICMP “port unreachable,” and you will see 0% packet loss. If only the 1472-byte test shows 0% loss and the 1473-byte test shows loss, fragmented UDP is being dropped.
* On the server, to see what actually arrives (replace <code>yy.yy.yy.yy</code> with the client IP): <code>tcpdump -i any -nn 'host yy.yy.yy.yy and not tcp'</code>. The <code>not tcp</code> filter prevents your SSH session from being captured. Compare what you see when sending 1472 vs 1473 bytes from the client.

 
'''Related''' 
If the initial INVITE is also too large (e.g., many codecs in SDP), reducing the SDP size (e.g., only needed codecs) can keep packets under MTU; see [[MOR_does_not_send_Contact_header]]. For NAT and port forwarding in general, see [[M4_under_NAT]].

Problems/Troubleshooting

2026-03-05T15:53:05Z

Admin: /* Asterisk */

==Problems/Troubleshooting==

[[Image:warning.png|50px]]<big><big><big>'''[[I HAVE A PROBLEM]]!!!'''</big></big></big>[[Image:warning.png|50px]]

 
===Asterisk===

* [[Cannot Connect From Certain IP]]
* [[Re-INVITE UDP fragmentation]]
* [[How to get crash info from core file with GDB]]
* [[How to resolve long PDD]]
* [[Scheduling destruction of SIP dialog]]
* [[Correct auth, but based on stale nonce received from]]
* [[IAX2 Call rejected, CallToken Support required]]
* [[sip show peers does not show devices]]
* [[DTMF problems]]
* [[Call hangs after 30 seconds]]
* [[Call hangs after 30 minutes]]
* [[Troubleshooting RINGING]]
* [[chan_sip.c:1786 __sip_xmit: sip_xmit of 0x81cbc78]]
* [[Wrong time in voice mail messages]]
* [[Failed to write frame]]
* [[Call failed]]
* [[rtcp halted Invalid argument]]
* [[no samples for g729tolin]]
* [[Asterisk can't connect to MySQL database]]
* [[Out of idle IAX2 threads]]
* [[Asterisk displays wrong time]]
* [[SIP Error Codes]]
* [[Call rejected by IP: No authority found]]
* [[Unable to forward voice frame]]
* [[CallerID not passed]]
* [[DID is not working]]
* [[Calls are not recorded]]
* [[Fax is not received]]
* [[200 MOR can't determine who is calling | MOR can't determine who is calling]]
* [[Retrieved 0 adv.rates, max adv.rate: 0.000000, total event price: 0.000000]]
* [[No reply to our critical packet]]
* [[One-way audio or not audio at all]]
** [[One way audio problems]]
* [[Voicemail]]
** [[No sound on Voicemail or Playback]]
** [[Voicemail does not work]]
* [[Dropping extra frame of G.729 since we already have a VAD frame at the end]]
* [[Comfort noise support incomplete in Asterisk (RFC 3389)]]
* [[mysql_reconnect: mor: Unknown connection error: (2006) MySQL server has gone away]]
* [[MOR Call dropped upon connection]]
* [[Starting asterisk: Cannot find your TTY]]
* [[False ANSWER| False Answer - False Ring]]
* [[Unable to allocate RTCP socket: Too many open files in system]]
* [[Echo]]
* [[Asterisk stops working with Internet loss]]
* [[Asterisk ended with exit status 1 Asterisk died with code 1]]
* [[Unknown signalling method 'pri_cpe']]
* [[ERROR: Could not open H.323 listener port on 1720]]
* [[sip_poke_noanswer: Peer 'XXX' is now UNREACHABLE!]]
* [[Unknown RTP codec 127 received]]
* [[determine_firstline_parts: Bad request protocol Packet]]
* [[Maximum retries exceeded on transmission]]
* [[RTCP Read too short]]
* [[Peer is not dynamic]]
* [[AMI Connection]]
* [[H323 problems]]
* '''Devices'''
** [[I cannot register Device]]
*** [[Registration from 'SOME DEVICE' failed for 'IP' - Not a local domain]]
*** [[Unable to find key 'XXX' in family 'SIP/Registry']]
*** [[Registration from 'sip:XXX@23.45.67.89' failed for '34.56.67.89' - No matching peer found]]
*** [[Peer is trying to register, but not configured as host=dynamic]]
** [[Device can't dial out]]
*** [[No path to translate from XXX to YYY]]
*** [[Call rejected by IP: No such context/extension]]
*** [[mor_authorize: Too low balance for more simultaneus calls!!!]]
** [[Device can't be reached]]
*** [[Unable to create channel of type 'XXX' (cause 3 - No route to destination)]]
** [[Device is not receiving video]]
** [[Device in Callshop can dial when not LOGGED IN]]
** [[Device ring non standard]]
* '''Zaptel'''
** [[Zaptel YELLOW alarm]]
** [[Unable to open master device '/dev/zap/ctl']]
* [[Cant dial to *9901]]
* [[Remote host can't match request NOTIFY]]

 

=== System ===
* [[Balance troubleshooting]]
* [[System sends email every hour on 1st day of the month]]
* [[How to forward port using Putty]]

 

===GUI===
* [[How correctly extract tar.gz file?]]
* [[How to remove calling cards (ccshop) shop from GUI]]
* [[System uses too much memory]]
* [[Can't open MOR GUI]]
* [[Graphs does not appear]]
* [[Can't open phpMyAdmin]]
* [[Can't send email]]
* [[Can't initiate web callback]]
* [[Can't setup callback]]
* [[Vouchers are not accepted]]
* [[Why_MOR_does_not_allow_to_delete_users | Cannot delete device/user]]
* [[lib/transaction/simple.rb:46: warning: already initialized constant Messages]]
* [[We're sorry, but something went wrong]]
* [[GUI Error - Errno::ENETUNREACH]]
* [[GUI Error - SystemExit]]
* [[GUI Error - Sender address rejected]]
* [[GUI Error - Email Username and Password not accepted]]
* [[GUI Error - Email SMTP server timeout]]
* [[GUI Error - Message refused]]
* [[GUI Error - Email SMTP]]
* [[GUI Error - Ruby Gems]]
 

===MySQL===

* [[How to repair MySQL table]]
* [[Incorrect key file for table '/tmp/#sql_xxxx.MYI'; try to repair it ]]
* [[Data truncated for column]]
* [[DB Tips]]

 

===Installation===

* [[rails: command not found]]
* [[yaml.rb:133: BUG Segmentation fault]]

 
== Other ==
* [[OpenVPN]]

Problems/Troubleshooting

2026-03-05T15:52:44Z

Admin: /* Asterisk */

==Problems/Troubleshooting==

[[Image:warning.png|50px]]<big><big><big>'''[[I HAVE A PROBLEM]]!!!'''</big></big></big>[[Image:warning.png|50px]]

 
===Asterisk===

* [[Cannot Connect From Certain IP]]
* [[How to get crash info from core file with GDB]]
* [[How to resolve long PDD]]
* [[Scheduling destruction of SIP dialog]]
* [[Correct auth, but based on stale nonce received from]]
* [[IAX2 Call rejected, CallToken Support required]]
* [[sip show peers does not show devices]]
* [[DTMF problems]]
* [[Call hangs after 30 seconds]]
* [[Call hangs after 30 minutes]]
* [[Troubleshooting RINGING]]
* [[chan_sip.c:1786 __sip_xmit: sip_xmit of 0x81cbc78]]
* [[Wrong time in voice mail messages]]
* [[Failed to write frame]]
* [[Call failed]]
* [[rtcp halted Invalid argument]]
* [[no samples for g729tolin]]
* [[Asterisk can't connect to MySQL database]]
* [[Out of idle IAX2 threads]]
* [[Asterisk displays wrong time]]
* [[SIP Error Codes]]
* [[Call rejected by IP: No authority found]]
* [[Unable to forward voice frame]]
* [[CallerID not passed]]
* [[DID is not working]]
* [[Calls are not recorded]]
* [[Fax is not received]]
* [[200 MOR can't determine who is calling | MOR can't determine who is calling]]
* [[Retrieved 0 adv.rates, max adv.rate: 0.000000, total event price: 0.000000]]
* [[No reply to our critical packet]]
* [[One-way audio or not audio at all]]
** [[One way audio problems]]
* [[Voicemail]]
** [[No sound on Voicemail or Playback]]
** [[Voicemail does not work]]
* [[Dropping extra frame of G.729 since we already have a VAD frame at the end]]
* [[Comfort noise support incomplete in Asterisk (RFC 3389)]]
* [[mysql_reconnect: mor: Unknown connection error: (2006) MySQL server has gone away]]
* [[MOR Call dropped upon connection]]
* [[Starting asterisk: Cannot find your TTY]]
* [[False ANSWER| False Answer - False Ring]]
* [[Unable to allocate RTCP socket: Too many open files in system]]
* [[Echo]]
* [[Asterisk stops working with Internet loss]]
* [[Asterisk ended with exit status 1 Asterisk died with code 1]]
* [[Unknown signalling method 'pri_cpe']]
* [[ERROR: Could not open H.323 listener port on 1720]]
* [[sip_poke_noanswer: Peer 'XXX' is now UNREACHABLE!]]
* [[Unknown RTP codec 127 received]]
* [[determine_firstline_parts: Bad request protocol Packet]]
* [[Maximum retries exceeded on transmission]]
* [[RTCP Read too short]]
* [[Peer is not dynamic]]
* [[AMI Connection]]
* [[H323 problems]]
* '''Devices'''
** [[I cannot register Device]]
*** [[Registration from 'SOME DEVICE' failed for 'IP' - Not a local domain]]
*** [[Unable to find key 'XXX' in family 'SIP/Registry']]
*** [[Registration from 'sip:XXX@23.45.67.89' failed for '34.56.67.89' - No matching peer found]]
*** [[Peer is trying to register, but not configured as host=dynamic]]
** [[Device can't dial out]]
*** [[No path to translate from XXX to YYY]]
*** [[Call rejected by IP: No such context/extension]]
*** [[mor_authorize: Too low balance for more simultaneus calls!!!]]
** [[Device can't be reached]]
*** [[Unable to create channel of type 'XXX' (cause 3 - No route to destination)]]
** [[Device is not receiving video]]
** [[Device in Callshop can dial when not LOGGED IN]]
** [[Device ring non standard]]
* '''Zaptel'''
** [[Zaptel YELLOW alarm]]
** [[Unable to open master device '/dev/zap/ctl']]
* [[Cant dial to *9901]]
* [[Remote host can't match request NOTIFY]]

 

=== System ===
* [[Balance troubleshooting]]
* [[System sends email every hour on 1st day of the month]]
* [[How to forward port using Putty]]

 

===GUI===
* [[How correctly extract tar.gz file?]]
* [[How to remove calling cards (ccshop) shop from GUI]]
* [[System uses too much memory]]
* [[Can't open MOR GUI]]
* [[Graphs does not appear]]
* [[Can't open phpMyAdmin]]
* [[Can't send email]]
* [[Can't initiate web callback]]
* [[Can't setup callback]]
* [[Vouchers are not accepted]]
* [[Why_MOR_does_not_allow_to_delete_users | Cannot delete device/user]]
* [[lib/transaction/simple.rb:46: warning: already initialized constant Messages]]
* [[We're sorry, but something went wrong]]
* [[GUI Error - Errno::ENETUNREACH]]
* [[GUI Error - SystemExit]]
* [[GUI Error - Sender address rejected]]
* [[GUI Error - Email Username and Password not accepted]]
* [[GUI Error - Email SMTP server timeout]]
* [[GUI Error - Message refused]]
* [[GUI Error - Email SMTP]]
* [[GUI Error - Ruby Gems]]
 

===MySQL===

* [[How to repair MySQL table]]
* [[Incorrect key file for table '/tmp/#sql_xxxx.MYI'; try to repair it ]]
* [[Data truncated for column]]
* [[DB Tips]]

 

===Installation===

* [[rails: command not found]]
* [[yaml.rb:133: BUG Segmentation fault]]

 
== Other ==
* [[OpenVPN]]

M4 Source Transformation

2026-03-04T19:25:34Z

Admin: /* See also */

=Source Transformation rules=

Source Transformation rules are used to manipulate the Source (CallerID) number (cut prefix, add prefix). Only the Number part of CallerID will be changed, the Name part will not be changed. Rules can be set in [[M4 Termination Points | Termination Points]] or [[M4 Origination Points | Origination Points]] Source Transformation input field. There are 3 different Source Transformation rules:

'''1. Add prefix'''

To add something to every number, just enter what to add.

'''2. Cut prefix'''

To cut something from a number, write - (minus) character and then what to cut. For example, -00 will cut 00 from the beginning of the number (only if the number starts with 00).

'''3. Replace prefix'''

To cut something from the number and add something else (replace), write - (minus) character followed by what to cut, then + (plus) character and what to add. For example, -00+8 will remove the leading 00 and add the digit 8 in front (00 will be replaced by 8).

 

=Multiple rules=

It is possible to define multiple Source Transformation rules in a single line. It is done by separating rules with the | character:

-A+B|-C+D|-X|Z

Rules are checked in the order they are written, and the first matching rule will be applied. If one rule is applied, then other rules will be skipped. This means that some rules do not make sense; for example, the 00|-6+370 rule will always add 00 to the front of the number, and the second rule will be skipped. 

The number of rules is limited only by the length of the input field (255 characters).

 

=Examples=

{| border="1" cellpadding="5" cellspacing="0"
| '''Incoming Source Number''' || '''Source Transformation''' || '''Outgoing Source number''' || '''Comment'''

|-
| +86123456789 || -\+ || 86123456789 || cut + in front of number
|-
| 86123456789 || 00 || 0086123456789 || simple rule just adds 00 in front of number
|-
| 003706123456789 || -00 || 3706123456789 || if the number starts with digits 00, then cut them
|-
| 003706123456789 or +3706123456789 || <nowiki>-\+|-00</nowiki> || 3706123456789 || cut + or 00 in front of number
|-
| 86123456789 || -8+370 || 3706123456789 || cut number 8 and add 370. If the number does not start with 8, then nothing will be added
|-
| 03706123456789 || <nowiki>-00+370|-0</nowiki> || 3706123456789 || Source Transformation contains multiple rules, but the first rule is skipped because the number starts with 0 and not 00. The second rule is applied, and 0 is cut from the number
|-
| 3706123456789 || <nowiki>-00+370|-0|+</nowiki> || +3706123456789 || Source Transformation contains multiple rules, but the first and second rules are skipped. The last rule simply adds + to the number
|-
| 86123456789 || <nowiki>-8+370|00</nowiki> || 3706123456789 || Source Transformation contains multiple rules, but the first rule is applied, and other rules are skipped
|-
| 86123456789 || <nowiki>-8+\+370</nowiki> || +3706123456789 || if the number starts with the digit 8, then cut it and add +370. Note that + is escaped by using the \ character
|}

 
== Remove + from incoming CLI/CallerID/Source Number (client sends CLI with + in front) ==
 
'''What this does''' 
When a client (connection/trunk) sends Caller ID (CLI) with a leading <code>+</code> (e.g. <code>+37061234567</code>), you can strip that <code>+</code> in M4 so the system sees and uses the number without the prefix (e.g. <code>37061234567</code>).

 
'''How to do it in M4''' 
Use '''Source Transformation''' for the relevant connection point (the client that sends the CLI with <code>+</code>).

In the '''Transformation Rule:''' field ('''Old format''' should be selected) set <code>-\+</code> (to remove from + the start of the CLI).

[[File:M4 plus from cli.png]]

After saving, incoming CLI from that client will have the leading <code>+</code> removed before further processing.

 
'''Note''': If you use both Cut and Add, the value in Add is inserted after the cut. To only remove the <code>+</code>, use Cut: <code>+</code> and Add: empty.

 

= Regexp Rules =

Number transformation can also be done using Regexp. More information: [[M4 Regexp Examples]]

 

=See also=

* [[M4 Termination Points]]
* [[M4 Origination Points]]
* [[M4 Destination Transformation]]

M4 Source Transformation

2026-03-04T19:23:49Z

Admin: /* Remove + from incoming CLI/CallerID/Source Number (client sends CLI with + in front) */

File:M4 plus from cli.png

2026-03-04T19:23:20Z

Admin:

M4 Source Transformation

2026-03-04T19:07:36Z

Admin: /* Remove + from incoming CLI/CallerID/Source Number (client sends CLI with + in front) */

=Source Transformation rules=

Source Transformation rules are used to manipulate the Source (CallerID) number (cut prefix, add prefix). Only the Number part of CallerID will be changed, the Name part will not be changed. Rules can be set in [[M4 Termination Points | Termination Points]] or [[M4 Origination Points | Origination Points]] Source Transformation input field. There are 3 different Source Transformation rules:

'''1. Add prefix'''

To add something to every number, just enter what to add.

'''2. Cut prefix'''

To cut something from a number, write - (minus) character and then what to cut. For example, -00 will cut 00 from the beginning of the number (only if the number starts with 00).

'''3. Replace prefix'''

To cut something from the number and add something else (replace), write - (minus) character followed by what to cut, then + (plus) character and what to add. For example, -00+8 will remove the leading 00 and add the digit 8 in front (00 will be replaced by 8).

 

=Multiple rules=

It is possible to define multiple Source Transformation rules in a single line. It is done by separating rules with the | character:

-A+B|-C+D|-X|Z

Rules are checked in the order they are written, and the first matching rule will be applied. If one rule is applied, then other rules will be skipped. This means that some rules do not make sense; for example, the 00|-6+370 rule will always add 00 to the front of the number, and the second rule will be skipped. 

The number of rules is limited only by the length of the input field (255 characters).

 

=Examples=

{| border="1" cellpadding="5" cellspacing="0"
| '''Incoming Source Number''' || '''Source Transformation''' || '''Outgoing Source number''' || '''Comment'''

|-
| +86123456789 || -\+ || 86123456789 || cut + in front of number
|-
| 86123456789 || 00 || 0086123456789 || simple rule just adds 00 in front of number
|-
| 003706123456789 || -00 || 3706123456789 || if the number starts with digits 00, then cut them
|-
| 003706123456789 or +3706123456789 || <nowiki>-\+|-00</nowiki> || 3706123456789 || cut + or 00 in front of number
|-
| 86123456789 || -8+370 || 3706123456789 || cut number 8 and add 370. If the number does not start with 8, then nothing will be added
|-
| 03706123456789 || <nowiki>-00+370|-0</nowiki> || 3706123456789 || Source Transformation contains multiple rules, but the first rule is skipped because the number starts with 0 and not 00. The second rule is applied, and 0 is cut from the number
|-
| 3706123456789 || <nowiki>-00+370|-0|+</nowiki> || +3706123456789 || Source Transformation contains multiple rules, but the first and second rules are skipped. The last rule simply adds + to the number
|-
| 86123456789 || <nowiki>-8+370|00</nowiki> || 3706123456789 || Source Transformation contains multiple rules, but the first rule is applied, and other rules are skipped
|-
| 86123456789 || <nowiki>-8+\+370</nowiki> || +3706123456789 || if the number starts with the digit 8, then cut it and add +370. Note that + is escaped by using the \ character
|}

 
== Remove + from incoming CLI/CallerID/Source Number (client sends CLI with + in front) ==
 
'''What this does''' 
When a client (connection/trunk) sends Caller ID (CLI) with a leading <code>+</code> (e.g. <code>+37061234567</code>), you can strip that <code>+</code> in M4 so the system sees and uses the number without the prefix (e.g. <code>37061234567</code>).

 
'''How to do it in M4''' 
Use '''Source Transformation''' for the relevant connection point (the client that sends the CLI with <code>+</code>). In the rule that applies to the incoming source (CallerID/CLI):

# Set <code>-\+</code> (to remove from + the start of the CLI).

After saving, incoming CLI from that client will have the leading <code>+</code> removed before further processing (e.g., CLI groups, routing, or display).

 
'''Note''': If you use both Cut and Add, the value in Add is inserted after the cut. To only remove the <code>+</code>, use Cut: <code>+</code> and Add: empty.

 

= Regexp Rules =

Number transformation can also be done using Regexp. More information: [[M4 Regexp Examples]]

 

=See also=

* [[M4 Termination Points]]
* [[M4 Origination Points]]
* [[M4 Destination Transformation | Destination Transformation]]

M4 Source Transformation

2026-03-04T19:02:05Z

Admin:

=Source Transformation rules=

Source Transformation rules are used to manipulate the Source (CallerID) number (cut prefix, add prefix). Only the Number part of CallerID will be changed, the Name part will not be changed. Rules can be set in [[M4 Termination Points | Termination Points]] or [[M4 Origination Points | Origination Points]] Source Transformation input field. There are 3 different Source Transformation rules:

'''1. Add prefix'''

To add something to every number, just enter what to add.

'''2. Cut prefix'''

To cut something from a number, write - (minus) character and then what to cut. For example, -00 will cut 00 from the beginning of the number (only if the number starts with 00).

'''3. Replace prefix'''

To cut something from the number and add something else (replace), write - (minus) character followed by what to cut, then + (plus) character and what to add. For example, -00+8 will remove the leading 00 and add the digit 8 in front (00 will be replaced by 8).

 

=Multiple rules=

It is possible to define multiple Source Transformation rules in a single line. It is done by separating rules with the | character:

-A+B|-C+D|-X|Z

Rules are checked in the order they are written, and the first matching rule will be applied. If one rule is applied, then other rules will be skipped. This means that some rules do not make sense; for example, the 00|-6+370 rule will always add 00 to the front of the number, and the second rule will be skipped. 

The number of rules is limited only by the length of the input field (255 characters).

 

=Examples=

{| border="1" cellpadding="5" cellspacing="0"
| '''Incoming Source Number''' || '''Source Transformation''' || '''Outgoing Source number''' || '''Comment'''

|-
| +86123456789 || -\+ || 86123456789 || cut + in front of number
|-
| 86123456789 || 00 || 0086123456789 || simple rule just adds 00 in front of number
|-
| 003706123456789 || -00 || 3706123456789 || if the number starts with digits 00, then cut them
|-
| 003706123456789 or +3706123456789 || <nowiki>-\+|-00</nowiki> || 3706123456789 || cut + or 00 in front of number
|-
| 86123456789 || -8+370 || 3706123456789 || cut number 8 and add 370. If the number does not start with 8, then nothing will be added
|-
| 03706123456789 || <nowiki>-00+370|-0</nowiki> || 3706123456789 || Source Transformation contains multiple rules, but the first rule is skipped because the number starts with 0 and not 00. The second rule is applied, and 0 is cut from the number
|-
| 3706123456789 || <nowiki>-00+370|-0|+</nowiki> || +3706123456789 || Source Transformation contains multiple rules, but the first and second rules are skipped. The last rule simply adds + to the number
|-
| 86123456789 || <nowiki>-8+370|00</nowiki> || 3706123456789 || Source Transformation contains multiple rules, but the first rule is applied, and other rules are skipped
|-
| 86123456789 || <nowiki>-8+\+370</nowiki> || +3706123456789 || if the number starts with the digit 8, then cut it and add +370. Note that + is escaped by using the \ character
|}

 
== Remove + from incoming CLI/CallerID/Source Number (client sends CLI with + in front) ==
 
'''What this does''' 
When a client (connection/trunk) sends Caller ID (CLI) with a leading <code>+</code> (e.g. <code>+37061234567</code>), you can strip that <code>+</code> in M4 so the system sees and uses the number without the prefix (e.g. <code>37061234567</code>).

 
'''How to do it in M4''' 
Use '''Source Transformation''' for the relevant connection point (the client that sends the CLI with <code>+</code>). In the rule that applies to the incoming source (CallerID/CLI):

# Set '''Cut''' to <code>+</code> (the character to remove from the start of the CLI).
# Leave '''Add''' empty so nothing is added after the cut.

After saving, incoming CLI from that client will have the leading <code>+</code> removed before further processing (e.g. CLI groups, routing, or display).

 
'''Note''': If you use both Cut and Add, the value in Add is inserted after the cut. To only remove the <code>+</code>, use Cut: <code>+</code> and Add: empty.

 
= Regexp Rules =

Number transformation can also be done using Regexp. More information: [[M4 Regexp Examples]]

 

=See also=

* [[M4 Termination Points]]
* [[M4 Origination Points]]
* [[M4 Destination Transformation | Destination Transformation]]

M4 Source Transformation

2026-03-04T19:01:48Z

Admin:

=Source Transformation rules=

Source Transformation rules are used to manipulate the Source (CallerID) number (cut prefix, add prefix). Only the Number part of CallerID will be changed, the Name part will not be changed. Rules can be set in [[M4 Termination Points | Termination Points]] or [[M4 Origination Points | Origination Points]] Source Transformation input field. There are 3 different Source Transformation rules:

'''1. Add prefix'''

To add something to every number, just enter what to add.

'''2. Cut prefix'''

To cut something from a number, write - (minus) character and then what to cut. For example, -00 will cut 00 from the beginning of the number (only if the number starts with 00).

'''3. Replace prefix'''

To cut something from the number and add something else (replace), write - (minus) character followed by what to cut, then + (plus) character and what to add. For example, -00+8 will remove the leading 00 and add the digit 8 in front (00 will be replaced by 8).

 

=Multiple rules=

It is possible to define multiple Source Transformation rules in a single line. It is done by separating rules with the | character:

-A+B|-C+D|-X|Z

Rules are checked in the order they are written, and the first matching rule will be applied. If one rule is applied, then other rules will be skipped. This means that some rules do not make sense; for example, the 00|-6+370 rule will always add 00 to the front of the number, and the second rule will be skipped. 

The number of rules is limited only by the length of the input field (255 characters).

 

=Examples=

{| border="1" cellpadding="5" cellspacing="0"
| '''Incoming Source Number''' || '''Source Transformation''' || '''Outgoing Source number''' || '''Comment'''

|-
| +86123456789 || -\+ || 86123456789 || cut + in front of number
|-
| 86123456789 || 00 || 0086123456789 || simple rule just adds 00 in front of number
|-
| 003706123456789 || -00 || 3706123456789 || if the number starts with digits 00, then cut them
|-
| 003706123456789 or +3706123456789 || <nowiki>-\+|-00</nowiki> || 3706123456789 || cut + or 00 in front of number
|-
| 86123456789 || -8+370 || 3706123456789 || cut number 8 and add 370. If the number does not start with 8, then nothing will be added
|-
| 03706123456789 || <nowiki>-00+370|-0</nowiki> || 3706123456789 || Source Transformation contains multiple rules, but the first rule is skipped because the number starts with 0 and not 00. The second rule is applied, and 0 is cut from the number
|-
| 3706123456789 || <nowiki>-00+370|-0|+</nowiki> || +3706123456789 || Source Transformation contains multiple rules, but the first and second rules are skipped. The last rule simply adds + to the number
|-
| 86123456789 || <nowiki>-8+370|00</nowiki> || 3706123456789 || Source Transformation contains multiple rules, but the first rule is applied, and other rules are skipped
|-
| 86123456789 || <nowiki>-8+\+370</nowiki> || +3706123456789 || if the number starts with the digit 8, then cut it and add +370. Note that + is escaped by using the \ character
|}

 
== Remove + from incoming CLI/CallerID/Source Number (client sends CLI with + in front) ==
 
'''What this does''' 
When a client (connection/trunk) sends Caller ID (CLI) with a leading <code>+</code> (e.g. <code>+37061234567</code>), you can strip that <code>+</code> in M4 so the system sees and uses the number without the prefix (e.g. <code>37061234567</code>).

 
'''How to do it in M4''' 
Use '''Source Transformation''' for the relevant connection point (the client that sends the CLI with <code>+</code>). In the rule that applies to the incoming source (CallerID/CLI):

# Set '''Cut''' to <code>+</code> (the character to remove from the start of the CLI).
# Leave '''Add''' empty so nothing is added after the cut.

After saving, incoming CLI from that client will have the leading <code>+</code> removed before further processing (e.g. CLI groups, routing, or display).

'''Note''': If you use both Cut and Add, the value in Add is inserted after the cut. To only remove the <code>+</code>, use Cut: <code>+</code> and Add: empty.

 
= Regexp Rules =

Number transformation can also be done using Regexp. More information: [[M4 Regexp Examples]]

 

=See also=

* [[M4 Termination Points]]
* [[M4 Origination Points]]
* [[M4 Destination Transformation | Destination Transformation]]

MOR Manual

2026-03-04T11:58:41Z

Admin: /* Number Manipulation */

<html>
<div align="center">
<iframe width="640" height="360" src="https://www.youtube.com/embed/R65ufpHOz_g" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</div>
</html>

<mkmeta>Detailed instructions how to use MOR Class 5 Softswitch</mkmeta>
<div align="center">
 
<center>MOR is a Class 5 Softswitch with Billing and Routing with extended functionality, increased stability, and professional support directly from the developers. It enables VoIP providers to offer various services.</center>

</div>
 
= Introduction =
* [[Introduction]] [[Image:flag_esp.jpg|alt="flag"|link=|right|link=Introduction (es)]]
* [[Who is this product designed for]]
* [[MOR Functionality]]
* [[Supported Business Models]]
* [[MOR Admin Interface|Admin Interface]]
* [[How to make first call|How to make a first call]] [[Image:flag_rus.jpg|alt="flag"|link=|right|link=How to make first call (ru)]]
 

= Concepts/Definitions =
* [[MOR Terminology]]
* [[Billing Concepts]] [[Image:flag_rus.jpg|right|alt="flag"|link=|link=Billing Concepts (ru)]]
* [[Billing Logic]]
* [[Call explained]]
* [[E.164]]
* [[Rounding]]
* [[Multi-Tax system]]
* [[What is a PIN?]]
* [[ASR/ACD]]
* [[Margin and Markup]]
* [[What are callgroups and pickupgroups|What are callgroups and pickupgroups?]]
* [[Balance and Credit]]
* [[Local Calls]]
* [[Prepaid Logic]]
* [[Authentication]]
* [[Fax over VoIP]]

 

= Configuration =
* [[mor.conf]]
* [[Performance Suggestions]]
* [[Configuration from GUI]]
** [[reCAPTCHA]]
** [[Payments configuration]]
** [[Default device settings]]
** [[Default_user|Default user settings]]
** [[Accountant permissions]]
** [[Logo change]]
** [[Currencies]]
** [[Translations]]
** [[Global_date_format | Global date format]]
** [[Remove Manual link from admin GUI]]
* [[Voicemail]]
* [[Multi Server support]]
* [[MOR White-labeling|White-labeling]]
* Emails
** [[Configuration_from_GUI#Emails|Email settings]]
** [[Emails|Mass Emails]]
** [[Email variables]]
* [[WebRTC]]
* [[Time Zone list]]
* [[MOR SIP Header Transformations]]
* [[MOR STIR/SHAKEN]]
* [[PJSIP Codec negotiation]]

 

= [[MOR Number Manipulation | Number Manipulation]] =
* [[MOR Localization | Localization]]
** [[MOR Location Groups | Location Groups]]
* [[MOR Device Rules | Device Rules]]
** [[MOR Device Rule Groups | Device Rule Groups]]
* [[MOR Provider Rules | Provider Rules]]
* [[DID handling by Localization]]
* [[MOR Number Manipulation Examples | Number Manipulation Examples]]
* [[Block wrong short numbers with Localization]]
* [[MOR - LCR/Tariff change based on call prefix]]
* [[Prefix finder]]
* [[MOR Prelocalization]]

 

=[[Users]] =
* [[User Details]]
** [[Warning balance]]
** [[User Blocking]]
* [[Hide Users]]
* [[Why MOR does not allow to delete users|Why MOR does not allow users to be deleted]]
* [[How to create User and Device|How to create a User and Device]]
* [[MOR_forgot_user_password|How to reset lost GUI password]]
 

= [[Devices]] =
* [[Device settings]]
** [[H323 Device settings]]
** [[Extension lines]]
** [[Ring several devices at same time]]
** [[How to create User and Device|How to create a User and Device]]
** [[Allowed Addresses]]
* [[Devices Bulk Create]]
* [[Trunks]]
* [[CLIs (Incoming CallerIDs)]]
** [[ANI/CLI ban system]]
* [[Duplicate call prevention]]
* [[Allow loss calls]]
* [[Device groups]]
* [[Call Flow]]
* [[Which codecs should I choose for devices|Which codecs should I choose for devices?]]
**[[Change_Audio/Video_Codecs_priority| Codecs priority]]
* [[Authentication|How to configure IP Authentication for Device]]
* [[Registration_Status|Device registration status]]
* [[MOR Device Rules]]
* [[Feature Codes]]
* [[Hide Device Password]]
* [[Disallow duplicate device usernames]]
* [[Disallow users to change their email]]

 

= [[Providers]] =

(also known as terminators, suppliers, vendors or trunks)

* [[Terminators]]
* [[Provider with several IP|Provider with several IPs]]
* [[H323 Provider settings]]
* [[Provider with ANI]]
* [[Configure Provider which can make calls]]
* [[Configure Provider with dynamic IP]]
* [[Simultaneous call limitation]]
* [[NO ANSWER/BUSY interpretation for providers]]
* [[Provider_Deviations|Provider Deviations]]
* [[Provider AGI script]]
* Provider Configuration
** [[Net2phone configuration | Net2phone]]
** [[Broadvoice configuration | Broadvoice]]
** [[Eutelia]]
** [[IXC]]
** [[Configuring DIDWW | DIDWW]]
** [[Vitelity]]
** [[Vono]]
** [[How_to_add_Voicetrading_Provider|Voicetrading]]
** [[Portech GSM as Provider | Portech]]
** [[DID Logic]]
** [[Voxbeam]]

 

= [[Tariffs]] =
* [[Directions and Destinations]]
** [[Destinations Groups]]
** [[Destination Groups Policy]]
** [[Block some Destination to User|Block a Destination to a User]]
** [[Export and bulk import of unassigned destinations]]
* [[Day setup]]
* [[Bulk change Tariffs for Users]]
* [[Wholesale Tariff | Wholesale]]
** [[Entering Rates for Wholesale Tariff]]
** [[Rate import from CSV]]
** [[Blocked Rates]]
* Retail
** [[Advanced Rates | Advanced (Retail) Rates]]
*** [[Entering Rates for Retail Tariff]]
*** [[Advanced Rates for Users| Advanced (Retail) Rates for Users]]
** [[Custom Rates]]
* [[Tariff Transformation]]
** [[Make Retail Tariff from Wholesale Tariff explained]]
* [[Why User can't check his Rates]]

 

= Call Routing =
* [[LCR]]
* [[LCR Logic]]
* [[How to add Provider to LCR]]
* [[Call Routing by price]]
* [[Call Routing by priority (Manual LCR)]]
* [[Call routing per destination basis]]
** [[How to route call to specific Destination through specific Provider]]
** [[How to block calls]]
** [[Blocked_Countries | How to block countries]]
** [[Block some Destination to User|Block a Destination to a User]]
* [[MOR - LCR/Tariff change based on call prefix]]
* [[Routing by Percent]] or Weight-based routing
* [[Why call was not routed through other provider/trunk?|Why was a call not routed through another provider/trunk?]]
* [[Intelligent Internal Routing]]
* Advanced [[extensions_mor_custom.conf]]

 

= DIDs =
* [[DID Management]]
** [[Assign DID to Trunk]]
* [[Work flow for DID]]
* [[DID Billing]]
** [[DID Billing Time explained]]
* [[DIDs Usage]]
* [[Personal DIDs]]
* [[Example - Configuring DID to ring some Device]]
* [[PBX Function External DID]]
* [[Ring-Groups]]
* [[DID with VoxBone using his URI]]
* [[Forward DID to External Number]]
* [[How to charge DID on a monthly basis]]
* [[DID handling by Localization]]
* [[DID Blocking]]
* [[Dial Plans]]
** [[Authorization by PIN]]
** [[Authorization by ANI]]
** [[Calling Card Dial Plan]]
** [[Callback Dial Plan]]
** [[IVR Dial Plan]]
** [[STATISTICS - Various - DIDs]]

 

= [[Accounting]] =
* [[Services]]
** [[Flat-Rates]]
* [[Subscriptions]]
* [[Invoices]]
** [[Invoice configuration]]
** [[Pay Invoice with balance deduction]]
** [[Invoice by CallerID]]
* [[Payments]]
* [[Vouchers]]

 

= Reporting =
* [[Active Calls]]
* [[Last Calls]]
* [[Local Calls Stats]]
* [[Users Calls]]
* [[Users Finances]]
* [[Loss Making Calls]]
* [[DIDs Report]]
* [[Providers Statistics]]
* [[Providers Calls]]
* [[Statement Of Account]]
* [[Aggregate]]
* [[First Activity]]
* [[Quick Stats]]
* [[Simultaneous Calls stats]]
* [[Calls by Source]]
* [[Login Stats]]
* [[Profit Stats]]
* [[Country Stats]]
* [[Hangup Cause Report]]
* [[Graphs]]
* [[Google Maps integration]]
** [[Get Google Maps key]]
* [[Balance in phone]]
* [[Privacy to hide Destination ends]]

 

= Troubleshooting =

* [[Frequently_Asked_Questions_(FAQ) | Frequently Asked Questions]]
* [[Action log]]
* [[Call Tracing]]
* [[Integrity Check]]
* [[Hangupcause Codes]]
** [[H323 hangupcause codes]]
** [[Hangupcause Sounds]]
** [[Different code send to User compared to received from Provider]]
* [[Call Info]]
** [[Call log explanation]]
* [[SIP debug info]]
* [[Provider connection testing]]
* [[Asterisk CLI]]
** [[Watch active calls/channels in Asterisk server from CLI]]
** [[Get Asterisk CLI output for specific call]]
* [[MOR's Core version]]
* [[Lots of calls made by System Admin user]]
* [[Renew Devices]]
* [[Email log]]
* [[MOR forward Q.850 Reason header]]
 

= Maintenance =

* [[How to restart Asterisk server]]
* [[Upgrade MOR GUI]]
* [[Lost MOR GUI admin password]]
* [[MOR Server Speedup]]
* [[Second Admin account]]
* [[Asterisk keepalive script]]

 

= Security =
* [[How to be secure using MOR]]
* [[MOR Change default passwords]]
* [[Blocking SIP Scanners]]
* [[MOR iptables Chains]]
* [[MOR two factor authentication]]
* [[How to set up SSL certificate with Let's Encrypt]]

 

= Testing =

* [[VoIP Bandwidth Calculator]]

 

= Payment gateways =

* [[Payment_Gateway_Addon | Payments Gateway Addon]]
 

= Other functionality =
* [[SIP Header Manipulation]]
* [[IVR system]]
** [[IVR for Calling Cards]]
** [[IVR Greeting for DID]]
* [[Callback]]
** [[WEB Callback]]
** [[Callback over Email]]
** [[MOR API callback init | API Callback_init]]
** [[Callback setup example]]
* [[PBX Functions]]
** [[Voicemail]]
** [[Dial Local]]
** [[PBX Function External DID|External DID]]
* [[Fax2Email]]
* [[Recordings Addon | Recordings]]
* [[PhoneBook]]
* [[Speed Dials]]
* [[Backup system]]
* [[Data import]]
* CDR
** [[CDR Import]]
** [[CDR Rerating]]
** [[CDR Disputes|CDR Disputes]]
* [[Online registration]]
** [[Online registration customization]]
* [[Quick Forwards]]
** [[Quickforwards rules]]
* [[Transfers with MOR]]
* [[GUI on Mobile Devices]]
* [[PBX connection to MOR]]
** [[MOR and Trixbox]]
* [[MOR API]]
** [[API Configuration]]
* [[Cron actions]]

 

= [[MOR Addons|'''MOR Addons''']] =
* [[Limited Addons]]
* [[Automatic Tariff Import]]
* [[Auto-Dialer Addon]]
* [[Call Shop Addon]]
* [[Callback|Callback Addon]]
* [[Calling Cards Addon]]
* [[Mobile Number Portability Addon]]
* [[Monitorings Addon]]
** [[Spy_real-time_calls|Spy real-time calls]]
** [[Alerts]]
** [[Alert Groups]]
** [[Alert Schedules]]
** [[Dynamic Blacklist Functionality]]
* [[Payment Gateway Addon]]
* [[Recordings Addon]]
* [[Reseller Addon]]
* [[Reseller Pro Addon]]
* [[PBX_Functions_Addon | PBX Functions Addon]]

 

= Tutorials =
* [[Usual configuration sequence]]
** [[How to make first call]]
* [[How to create User and Device]]
* [[Dial Local | How to setup Dial Local function]]
* [[Calling Card setup example | How to setup Calling Cards]]
** [[How to setup Access Number to TopUp Card by CallerID]]
* [[Callback setup example | How to setup Callback]]
* [[Conference with MOR + Trixbox | How to setup Conferences using Trixbox]]
* [[How to forward the Call when Device is offline]]
* IVRs
** [[IVR for Calling Cards | How to setup IVR for Calling Cards]]
* DIDs
** [[Example - Configuring DID to ring some Device | How to configure DID to ring some Device]]
** [[Forward DID to External Number | How to forward DID to External Number]]
** [[How to charge DID on a monthly basis]]
** [[IVR Greeting for DID|How to add Greeting for DID]]
* [[How to configure 911 service]]
* [[Block some Destination to User | How to block a Destination to a User]]
* [[How to make several connections from one IP]]
* [[How to be secure using MOR]]
* [[How to change GUI port]]
* [[How to change qualify packets frequency]]
* [[MOR 10CC]]
* [[VitalPBX interconnection with MOR]]

 

= Old Manuals =
* [http://packets.kolmisoft.com/packets/docs/MOR_X4_Manual.pdf MOR X4 Manual]
* [http://packets.kolmisoft.com/packets/docs/MOR_X3_Manual.pdf MOR X3 Manual]
* [http://packets.kolmisoft.com/packets/docs/MOR_12_Manual.pdf MOR 12 Manual]
* [http://packets.kolmisoft.com/packets/docs/MOR_11_Manual.pdf MOR 11 Manual]
* [http://packets.kolmisoft.com/packets/docs/MOR_10_Manual.pdf MOR 10 Manual]
* [[Material for testing users]]

MOR Manual

2026-03-04T11:58:30Z

Admin: /* Number Manipulation */

<html>
<div align="center">
<iframe width="640" height="360" src="https://www.youtube.com/embed/R65ufpHOz_g" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</div>
</html>

<mkmeta>Detailed instructions how to use MOR Class 5 Softswitch</mkmeta>
<div align="center">
 
<center>MOR is a Class 5 Softswitch with Billing and Routing with extended functionality, increased stability, and professional support directly from the developers. It enables VoIP providers to offer various services.</center>

</div>
 
= Introduction =
* [[Introduction]] [[Image:flag_esp.jpg|alt="flag"|link=|right|link=Introduction (es)]]
* [[Who is this product designed for]]
* [[MOR Functionality]]
* [[Supported Business Models]]
* [[MOR Admin Interface|Admin Interface]]
* [[How to make first call|How to make a first call]] [[Image:flag_rus.jpg|alt="flag"|link=|right|link=How to make first call (ru)]]
 

= Concepts/Definitions =
* [[MOR Terminology]]
* [[Billing Concepts]] [[Image:flag_rus.jpg|right|alt="flag"|link=|link=Billing Concepts (ru)]]
* [[Billing Logic]]
* [[Call explained]]
* [[E.164]]
* [[Rounding]]
* [[Multi-Tax system]]
* [[What is a PIN?]]
* [[ASR/ACD]]
* [[Margin and Markup]]
* [[What are callgroups and pickupgroups|What are callgroups and pickupgroups?]]
* [[Balance and Credit]]
* [[Local Calls]]
* [[Prepaid Logic]]
* [[Authentication]]
* [[Fax over VoIP]]

 

= Configuration =
* [[mor.conf]]
* [[Performance Suggestions]]
* [[Configuration from GUI]]
** [[reCAPTCHA]]
** [[Payments configuration]]
** [[Default device settings]]
** [[Default_user|Default user settings]]
** [[Accountant permissions]]
** [[Logo change]]
** [[Currencies]]
** [[Translations]]
** [[Global_date_format | Global date format]]
** [[Remove Manual link from admin GUI]]
* [[Voicemail]]
* [[Multi Server support]]
* [[MOR White-labeling|White-labeling]]
* Emails
** [[Configuration_from_GUI#Emails|Email settings]]
** [[Emails|Mass Emails]]
** [[Email variables]]
* [[WebRTC]]
* [[Time Zone list]]
* [[MOR SIP Header Transformations]]
* [[MOR STIR/SHAKEN]]
* [[PJSIP Codec negotiation]]

 

= [[MOR Number Manipulation | Number Manipulation]] =
* [[MOR Localization | Localization]]
** [[MOR Location Groups]]
* [[MOR Device Rules | Device Rules]]
** [[MOR Device Rule Groups | Device Rule Groups]]
* [[MOR Provider Rules | Provider Rules]]
* [[DID handling by Localization]]
* [[MOR Number Manipulation Examples | Number Manipulation Examples]]
* [[Block wrong short numbers with Localization]]
* [[MOR - LCR/Tariff change based on call prefix]]
* [[Prefix finder]]
* [[MOR Prelocalization]]

 

=[[Users]] =
* [[User Details]]
** [[Warning balance]]
** [[User Blocking]]
* [[Hide Users]]
* [[Why MOR does not allow to delete users|Why MOR does not allow users to be deleted]]
* [[How to create User and Device|How to create a User and Device]]
* [[MOR_forgot_user_password|How to reset lost GUI password]]
 

= [[Devices]] =
* [[Device settings]]
** [[H323 Device settings]]
** [[Extension lines]]
** [[Ring several devices at same time]]
** [[How to create User and Device|How to create a User and Device]]
** [[Allowed Addresses]]
* [[Devices Bulk Create]]
* [[Trunks]]
* [[CLIs (Incoming CallerIDs)]]
** [[ANI/CLI ban system]]
* [[Duplicate call prevention]]
* [[Allow loss calls]]
* [[Device groups]]
* [[Call Flow]]
* [[Which codecs should I choose for devices|Which codecs should I choose for devices?]]
**[[Change_Audio/Video_Codecs_priority| Codecs priority]]
* [[Authentication|How to configure IP Authentication for Device]]
* [[Registration_Status|Device registration status]]
* [[MOR Device Rules]]
* [[Feature Codes]]
* [[Hide Device Password]]
* [[Disallow duplicate device usernames]]
* [[Disallow users to change their email]]

 

= [[Providers]] =

(also known as terminators, suppliers, vendors or trunks)

* [[Terminators]]
* [[Provider with several IP|Provider with several IPs]]
* [[H323 Provider settings]]
* [[Provider with ANI]]
* [[Configure Provider which can make calls]]
* [[Configure Provider with dynamic IP]]
* [[Simultaneous call limitation]]
* [[NO ANSWER/BUSY interpretation for providers]]
* [[Provider_Deviations|Provider Deviations]]
* [[Provider AGI script]]
* Provider Configuration
** [[Net2phone configuration | Net2phone]]
** [[Broadvoice configuration | Broadvoice]]
** [[Eutelia]]
** [[IXC]]
** [[Configuring DIDWW | DIDWW]]
** [[Vitelity]]
** [[Vono]]
** [[How_to_add_Voicetrading_Provider|Voicetrading]]
** [[Portech GSM as Provider | Portech]]
** [[DID Logic]]
** [[Voxbeam]]

 

= [[Tariffs]] =
* [[Directions and Destinations]]
** [[Destinations Groups]]
** [[Destination Groups Policy]]
** [[Block some Destination to User|Block a Destination to a User]]
** [[Export and bulk import of unassigned destinations]]
* [[Day setup]]
* [[Bulk change Tariffs for Users]]
* [[Wholesale Tariff | Wholesale]]
** [[Entering Rates for Wholesale Tariff]]
** [[Rate import from CSV]]
** [[Blocked Rates]]
* Retail
** [[Advanced Rates | Advanced (Retail) Rates]]
*** [[Entering Rates for Retail Tariff]]
*** [[Advanced Rates for Users| Advanced (Retail) Rates for Users]]
** [[Custom Rates]]
* [[Tariff Transformation]]
** [[Make Retail Tariff from Wholesale Tariff explained]]
* [[Why User can't check his Rates]]

 

= Call Routing =
* [[LCR]]
* [[LCR Logic]]
* [[How to add Provider to LCR]]
* [[Call Routing by price]]
* [[Call Routing by priority (Manual LCR)]]
* [[Call routing per destination basis]]
** [[How to route call to specific Destination through specific Provider]]
** [[How to block calls]]
** [[Blocked_Countries | How to block countries]]
** [[Block some Destination to User|Block a Destination to a User]]
* [[MOR - LCR/Tariff change based on call prefix]]
* [[Routing by Percent]] or Weight-based routing
* [[Why call was not routed through other provider/trunk?|Why was a call not routed through another provider/trunk?]]
* [[Intelligent Internal Routing]]
* Advanced [[extensions_mor_custom.conf]]

 

= DIDs =
* [[DID Management]]
** [[Assign DID to Trunk]]
* [[Work flow for DID]]
* [[DID Billing]]
** [[DID Billing Time explained]]
* [[DIDs Usage]]
* [[Personal DIDs]]
* [[Example - Configuring DID to ring some Device]]
* [[PBX Function External DID]]
* [[Ring-Groups]]
* [[DID with VoxBone using his URI]]
* [[Forward DID to External Number]]
* [[How to charge DID on a monthly basis]]
* [[DID handling by Localization]]
* [[DID Blocking]]
* [[Dial Plans]]
** [[Authorization by PIN]]
** [[Authorization by ANI]]
** [[Calling Card Dial Plan]]
** [[Callback Dial Plan]]
** [[IVR Dial Plan]]
** [[STATISTICS - Various - DIDs]]

 

= [[Accounting]] =
* [[Services]]
** [[Flat-Rates]]
* [[Subscriptions]]
* [[Invoices]]
** [[Invoice configuration]]
** [[Pay Invoice with balance deduction]]
** [[Invoice by CallerID]]
* [[Payments]]
* [[Vouchers]]

 

= Reporting =
* [[Active Calls]]
* [[Last Calls]]
* [[Local Calls Stats]]
* [[Users Calls]]
* [[Users Finances]]
* [[Loss Making Calls]]
* [[DIDs Report]]
* [[Providers Statistics]]
* [[Providers Calls]]
* [[Statement Of Account]]
* [[Aggregate]]
* [[First Activity]]
* [[Quick Stats]]
* [[Simultaneous Calls stats]]
* [[Calls by Source]]
* [[Login Stats]]
* [[Profit Stats]]
* [[Country Stats]]
* [[Hangup Cause Report]]
* [[Graphs]]
* [[Google Maps integration]]
** [[Get Google Maps key]]
* [[Balance in phone]]
* [[Privacy to hide Destination ends]]

 

= Troubleshooting =

* [[Frequently_Asked_Questions_(FAQ) | Frequently Asked Questions]]
* [[Action log]]
* [[Call Tracing]]
* [[Integrity Check]]
* [[Hangupcause Codes]]
** [[H323 hangupcause codes]]
** [[Hangupcause Sounds]]
** [[Different code send to User compared to received from Provider]]
* [[Call Info]]
** [[Call log explanation]]
* [[SIP debug info]]
* [[Provider connection testing]]
* [[Asterisk CLI]]
** [[Watch active calls/channels in Asterisk server from CLI]]
** [[Get Asterisk CLI output for specific call]]
* [[MOR's Core version]]
* [[Lots of calls made by System Admin user]]
* [[Renew Devices]]
* [[Email log]]
* [[MOR forward Q.850 Reason header]]
 

= Maintenance =

* [[How to restart Asterisk server]]
* [[Upgrade MOR GUI]]
* [[Lost MOR GUI admin password]]
* [[MOR Server Speedup]]
* [[Second Admin account]]
* [[Asterisk keepalive script]]

 

= Security =
* [[How to be secure using MOR]]
* [[MOR Change default passwords]]
* [[Blocking SIP Scanners]]
* [[MOR iptables Chains]]
* [[MOR two factor authentication]]
* [[How to set up SSL certificate with Let's Encrypt]]

 

= Testing =

* [[VoIP Bandwidth Calculator]]

 

= Payment gateways =

* [[Payment_Gateway_Addon | Payments Gateway Addon]]
 

= Other functionality =
* [[SIP Header Manipulation]]
* [[IVR system]]
** [[IVR for Calling Cards]]
** [[IVR Greeting for DID]]
* [[Callback]]
** [[WEB Callback]]
** [[Callback over Email]]
** [[MOR API callback init | API Callback_init]]
** [[Callback setup example]]
* [[PBX Functions]]
** [[Voicemail]]
** [[Dial Local]]
** [[PBX Function External DID|External DID]]
* [[Fax2Email]]
* [[Recordings Addon | Recordings]]
* [[PhoneBook]]
* [[Speed Dials]]
* [[Backup system]]
* [[Data import]]
* CDR
** [[CDR Import]]
** [[CDR Rerating]]
** [[CDR Disputes|CDR Disputes]]
* [[Online registration]]
** [[Online registration customization]]
* [[Quick Forwards]]
** [[Quickforwards rules]]
* [[Transfers with MOR]]
* [[GUI on Mobile Devices]]
* [[PBX connection to MOR]]
** [[MOR and Trixbox]]
* [[MOR API]]
** [[API Configuration]]
* [[Cron actions]]

 

= [[MOR Addons|'''MOR Addons''']] =
* [[Limited Addons]]
* [[Automatic Tariff Import]]
* [[Auto-Dialer Addon]]
* [[Call Shop Addon]]
* [[Callback|Callback Addon]]
* [[Calling Cards Addon]]
* [[Mobile Number Portability Addon]]
* [[Monitorings Addon]]
** [[Spy_real-time_calls|Spy real-time calls]]
** [[Alerts]]
** [[Alert Groups]]
** [[Alert Schedules]]
** [[Dynamic Blacklist Functionality]]
* [[Payment Gateway Addon]]
* [[Recordings Addon]]
* [[Reseller Addon]]
* [[Reseller Pro Addon]]
* [[PBX_Functions_Addon | PBX Functions Addon]]

 

= Tutorials =
* [[Usual configuration sequence]]
** [[How to make first call]]
* [[How to create User and Device]]
* [[Dial Local | How to setup Dial Local function]]
* [[Calling Card setup example | How to setup Calling Cards]]
** [[How to setup Access Number to TopUp Card by CallerID]]
* [[Callback setup example | How to setup Callback]]
* [[Conference with MOR + Trixbox | How to setup Conferences using Trixbox]]
* [[How to forward the Call when Device is offline]]
* IVRs
** [[IVR for Calling Cards | How to setup IVR for Calling Cards]]
* DIDs
** [[Example - Configuring DID to ring some Device | How to configure DID to ring some Device]]
** [[Forward DID to External Number | How to forward DID to External Number]]
** [[How to charge DID on a monthly basis]]
** [[IVR Greeting for DID|How to add Greeting for DID]]
* [[How to configure 911 service]]
* [[Block some Destination to User | How to block a Destination to a User]]
* [[How to make several connections from one IP]]
* [[How to be secure using MOR]]
* [[How to change GUI port]]
* [[How to change qualify packets frequency]]
* [[MOR 10CC]]
* [[VitalPBX interconnection with MOR]]

 

= Old Manuals =
* [http://packets.kolmisoft.com/packets/docs/MOR_X4_Manual.pdf MOR X4 Manual]
* [http://packets.kolmisoft.com/packets/docs/MOR_X3_Manual.pdf MOR X3 Manual]
* [http://packets.kolmisoft.com/packets/docs/MOR_12_Manual.pdf MOR 12 Manual]
* [http://packets.kolmisoft.com/packets/docs/MOR_11_Manual.pdf MOR 11 Manual]
* [http://packets.kolmisoft.com/packets/docs/MOR_10_Manual.pdf MOR 10 Manual]
* [[Material for testing users]]

MOR Prelocalization

2026-03-04T11:58:11Z

Admin:

MOR Localization

2026-03-04T11:57:55Z

Admin:

= Description =

 
<big><big><big>'''Localization transforms received number to E.164 format number.'''</big></big></big>

 
The main idea of localization is: '''No matter how the user dials the number (destination), when localized it should be in E.164 format.'''

Localization has nothing in common with the numbers you send to providers. It operates with numbers received from the caller.

 
Depending on the device's physical location, it is often important to allow users to dial numbers in different formats to reach a destination. For this purpose, each device has a field called '''Location''', which describes the device's physical location and defines rules for how the device can dial a destination. In other words, each device IS in (or belongs to) some Location where specific dialing rules apply.

'''Location describes where a caller IS - not where he is calling to!'''

By default, a device has the location 'Global'. Global rules apply to ALL devices. If a device belongs to some other location and the dialed destination has some rule for this destination, then global rules are not activated – they have a lower priority in location rules.

You can access Localization settings in '''SETTINGS –> Billing –> Functions –> Localization'''.

In the main window, you can see the available Locations:

[[Image:localization1.png]]

At first, there is only the Global location. You can't delete this location. It's the default for all devices.

You can add a new Location by entering this Location's name in the field at the bottom of the table:

[[Image:localization2.png]]

and clicking [[Image:add.png]]:

[[Image:localization3.png]]

 
== Clone ==

Additionally, you can make a copy of your current Localization rules by clicking the copy icon:

[[Image:Localization_copy_function.png]]

 

== Rules ==

In the Rules column, click the Rules icon to access the Location's rules:
 
[[Image:Editbutton.png]]
 
[[File:Localization_rules.png]]
 

'''Destination Rules''' – Changes Destination number.

'''CallerID Rules''' – Changes source number.

'''Combined Rules''' – Change Destination number and Source number. Please note that both Destination and Source cells must be matched to apply Combined Rules. Special symbols * and # do not work in combined rules.

'''Priority of rules that are applied first:'''
* 1) CallerID Rules
* 2) Combined Rules
* 3) Destination Rules

 
Note that if the match is found in "Combined Rules", "Destination Rules" are skipped entirely.

 
=== Removing or adding a prefix ===

To remove a prefix from the dialed number (destination), add a '''Destination Rule''': set '''Cut''' to the prefix you want to remove and '''Add''' to the replacement (if any). You do not need to change the call's owner.

 
To remove a prefix from the caller ID (source), use a '''CallerID Rule''' with '''Cut''' and '''Add''' in the same way.

 
The '''Change Call's owner''', '''Route to DID''', '''Change CallerID Name''', '''Change User LCR to this LCR''', and '''Change User Tariff to this Tariff''' fields are optional; use them only when you need that specific behaviour. They are not required to remove or add a prefix – only '''Cut''' and '''Add''' are needed for that.

 
=== Rule fields ===

The following settings should be explained for rules:

* '''Name''' – just for informational purposes.
* '''Cut''' – what prefix should be cut from the number.
* '''Add''' – what prefix should be added to the number.
* '''Min Len''' – the minimum length of the number to which the rule is being applied.
* '''Max Len''' – the maximum length of the number to which the rule is being applied.
* '''Change User Tariff to this Tariff''' – optional; which Tariff to apply when this rule is applied. Used in special cases, for example [[MOR - LCR/Tariff change based on call prefix | here]]. Leave empty in most cases; not required to remove or add a prefix.
* '''Change User LCR to this LCR''' – optional; which LCR to apply when this rule is applied. Used in special cases, for example [[MOR - LCR/Tariff change based on call prefix | here]]. Leave empty in most cases; not required to remove or add a prefix.
* '''Route to DID''' – optional; allows routing calls to DID according to localization rules. Not required to remove or add a prefix.
* '''Change CallerID Name''' – optional; changes the caller ID name when this rule is applied. Not required to remove or add a prefix.
* '''Change Call's owner''' – optional; changes the owner of the call depending on the incoming tech prefix. Use only when you need to route the call to a specific user; no prefix is required to remove or add.
* '''Enter edit mode''' - lets you change all rules at one time.

When you have entered all the necessary values (Cut or Add can be left empty), click [[Image:add.png]].

For example:
* The normal Lithuania MOB prefix is 3706.
* The user's device is located in Vilnius, Lithuania (displayed as "Lithuania Vilnius").
* By current Lithuanian regulations, the local customer can dial 9-digit numbers starting with 86 to reach Mobile subscribers.

To describe this situation, we create the following rule:

[[Image:localization_5_2.png]]

Rules can be enabled or disabled by clicking the [[Image:check.png]] icon or [[Image:cross.png]] in the '''Enabled?''' column.
* [[Image:edit.png]]- This icon allows you to edit the details of the rule.
* [[Image:cross.png]]- This icon allows you to delete the rule.

Now, in the main '''Localization''' window:

[[Image:localization6.png]]

click on [[Image:view.png]] in the '''Devices''' column to access '''Devices''' in Global '''Location''':

[[Image:localization7.png]]

Here, all Devices with a selected location are listed. Choose other locations for the selected Device and click on [[Image:check.png]] icon to activate this change. The device will be assigned to the selected Location.

[[Image:localization8.png]]

'''NOTE''': It's possible to change a device's Location in the Device settings ('''SETTINGS –> Users –> Devices''').

Now our device belongs to Location "Lithuania Vilnius". And if we dial a mobile number in the Lithuanian format, for example, 863042439, MOR cuts 86 (leaving 3042439) and adds 3706. The result is 37063042439, which is E.164 compatible and can be billed correctly by MOR.

'''NOTE''': Make sure that after localization, your number is always E.164 compatible. [[Call Tracing]] can help you do this.

'''NOTE''': You cannot delete a rule if it is assigned to a device.

 

= Special cases =

 
== Cut everything till Hash ==

With rule '''Cut: *#''' it is possible to cut everything till # (# included) in the dialed destination:

[[Image:Loc_cut_till_hash_2.png]]

For example:

* Dialed number: 1aaaaaaaaa#37063042439
* After Localization: 37063042439

Please note that if the dialed number is #37063042439, the call will not go through, because MOR rejects destinations with # in front of it.

This function can be used in fancy MNP (Mobile Number Portability) schemes and perhaps elsewhere.

 
NOTE: The '''Add''' value still can be used to add any value after '''Cut''' is used on the Destination.

 
== Cut any digits after a specific prefix ==

Works only with Destination and Combined rules.

Cut pattern accepts "x" which indicates any digit:

'''Cut: 12xxx''' 
will cut '''first 5 digits''' from the number which starts with digits "12".

If there are two rules like

'''Cut: 12xxx'''

'''Cut: 1234x'''

and a number

'''12345'''

then the rule '''Cut: 1234x''' will be selected because it matches most of the digits exactly.

Example1:

If we have a rule

'''Cut: 12xxx'''

'''Add: 99'''

Then all the following dialled numbers

1200012345

1257812345

1298712345

will be modified to

9912345

 

Example2:

If we have a rule
'''Cut: 123xxx78'''

'''Add: 78'''

Then all numbers starting from 12300078 till 12399978 will be localised to start with 78

 

== Change LCR/Tariff when CallerID is empty ==

 
This is an '''optional''' feature for special cases (e.g. applying a different LCR or Tariff when the caller ID is missing).

To change LCR/Tariff when CallerID is empty, set the following in Source Localization:

'''Cut: *''' 
'''Min Len: 0''' 
'''Max Len: 0''' 

and then choose the LCR/Tariff you want to set for calls without CallerID.

 

= Reseller localizations =
The reseller is not using the admin's global localization rules. Instead, he can now copy the rules and modify them to suit his needs. All newly created resellers have those global rules copied automatically from the admin. This feature can be disabled by the admin in [[Reseller_Settings|Reseller Settings]].
 
[[File:Copy_rules.png]]
 
'''IMPORTANT''': Fields "Change User Tariff to this Tariff" and "Change User LCR to this LCR" will not be copied.
 
"Default location" does not act as "Global location" on the reseller's account. Only the rules set in the device's settings will be applied.
 

= Route to DID =

 
This is an '''optional''' feature. Admin and Reseller PRO users can route calls to a DID according to localization rules.
 
[[File:Localization9.png]]
 
Start typing the DID number, and you will see all the DIDs that start with that number. If the DID you need is not there, enter more digits - only the first 20 DIDs starting with that number are shown.

 
= Change owner of call depending on incoming prefix =

 
This is an '''optional''' feature for routing the call to a specific user based on the incoming tech prefix.

It is now possible to change the call owner based on the incoming tech prefix.

* Open the localization menu to find the "Change Call's Owner" field.
[[File:localization8_5.png]]
 
* Enter the incoming prefix that needs to be cut in the "Cut" section.
* Afterwards, choose a user from the drop-down list and the device to which the call should be assigned.
[[File:Change_owner2.png]]
* This feature is also available for resellers.
* Admin can assign the call to ANY user on the system (even to those that do not belong to the admin).

 

= See also =

* [[MOR Number Manipulation]]
** [[MOR Device Rules]]
** [[MOR Provider Rules]]
** [[DID handling by Localization]]
** [[MOR Number Manipulation Examples]]
* [[MOR Prelocalization]]
* [[MOR Location Groups]]
* [http://www.wtng.info/wtng-reg.html World Telephone Numbering Guide]

MOR Location Groups

2026-03-04T11:57:40Z

Admin: Admin moved page Location Groups to MOR Location Groups

= Description =

Used with [[MOR_Localization#Rules | Source Combined Rules]]. Helps reduce the number of rules.

== Configuration ==

Click on Location Groups.
 
[[Image:Location_groups_menu.png]]
 
Create groups:
 
[[Image:Location_groups.png]]
 
Create rules:
 
[[Image:Location_groups_rules.png]]
 

== Assign Location Group ==

Choose your Location Group in [[MOR_Localization#Rules | Source Combined Rules]]:
 
[[Image:Location_groups_combined.png]]
 

= Origin Based Rating (OBR) | Call Charging on Location Base =

Origin-Based Rating (OBR) is a billing mechanism that takes into account both the origination (where the call begins) and termination (where the call ends)of a call when calculating billing.

In OBR, the cost of terminating a call depends on the country or region from which the call originated. This means that the terminating provider, often a mobile operator, applies additional fees or surcharges to the standard termination rates based on the caller's country code or geographic location.

Essentially, OBR involves charging different rates for terminating calls based on the originating country, allowing telecom providers to adjust their fees accordingly. This method can result in varying call costs depending on the point of origin, enabling a more nuanced billing structure in the telecommunications industry.

Origin-Based Rating (OBR) is supported by MOR, and here we will cover the following cases:

# Call from EU to EU (Greece as an example)
# Call from non-EU to EU (Greece as an example)
# Call from non-EU to non-EU country

In #1 and #2, the Greek number belongs to provider A with NRN 589000, and the Greek destination number is in the format 302XXXXXXXXX, which is made by [[MOR Prelocalization]].

Later, MNP adds Provider NRN 589000 to the 302XXXXXXXXX, and the call with Destination 589000302XXXXXXXXX comes to MOR Core Localization for further analysis. And here we will take care of it.

 
== Case #1 - Call from EU to EU (Greece as an example) ==

[[File:location_groups2.png]]

With this rule, we determine that the call with Destination starting with 589000302 and CallerID from the EU should be routed to LCR10, and Tariff10 should be used. Only one rule covers all of Europe's CallerIDs, which are described in the Localization Group EU.

 

== Case #2 - Call from non-EU to EU (Greece as an example) ==

[[File:location_groups3.png]]

With this rule, we determine that calls with a destination that starts with 589000302 and a CallerID from non-EU countries should be routed to LCR20, and Tariff200 should be used. Only one rule covers the whole of non-Europe's CallerIDs, which are described in the Localization Group non-EU.

 
== Case #3 - Call from non-EU to non-EU country ==

Here, no special rule is necessary. A simple destination rule can be used to change the tariff and/or LCR.

 

=See also=
* [[MOR Localization]]
* [[MOR Prelocalization]]

MOR Manual

2026-03-04T11:57:02Z

Admin: /* Number Manipulation */

<html>
<div align="center">
<iframe width="640" height="360" src="https://www.youtube.com/embed/R65ufpHOz_g" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</div>
</html>

<mkmeta>Detailed instructions how to use MOR Class 5 Softswitch</mkmeta>
<div align="center">
 
<center>MOR is a Class 5 Softswitch with Billing and Routing with extended functionality, increased stability, and professional support directly from the developers. It enables VoIP providers to offer various services.</center>

</div>
 
= Introduction =
* [[Introduction]] [[Image:flag_esp.jpg|alt="flag"|link=|right|link=Introduction (es)]]
* [[Who is this product designed for]]
* [[MOR Functionality]]
* [[Supported Business Models]]
* [[MOR Admin Interface|Admin Interface]]
* [[How to make first call|How to make a first call]] [[Image:flag_rus.jpg|alt="flag"|link=|right|link=How to make first call (ru)]]
 

= Concepts/Definitions =
* [[MOR Terminology]]
* [[Billing Concepts]] [[Image:flag_rus.jpg|right|alt="flag"|link=|link=Billing Concepts (ru)]]
* [[Billing Logic]]
* [[Call explained]]
* [[E.164]]
* [[Rounding]]
* [[Multi-Tax system]]
* [[What is a PIN?]]
* [[ASR/ACD]]
* [[Margin and Markup]]
* [[What are callgroups and pickupgroups|What are callgroups and pickupgroups?]]
* [[Balance and Credit]]
* [[Local Calls]]
* [[Prepaid Logic]]
* [[Authentication]]
* [[Fax over VoIP]]

 

= Configuration =
* [[mor.conf]]
* [[Performance Suggestions]]
* [[Configuration from GUI]]
** [[reCAPTCHA]]
** [[Payments configuration]]
** [[Default device settings]]
** [[Default_user|Default user settings]]
** [[Accountant permissions]]
** [[Logo change]]
** [[Currencies]]
** [[Translations]]
** [[Global_date_format | Global date format]]
** [[Remove Manual link from admin GUI]]
* [[Voicemail]]
* [[Multi Server support]]
* [[MOR White-labeling|White-labeling]]
* Emails
** [[Configuration_from_GUI#Emails|Email settings]]
** [[Emails|Mass Emails]]
** [[Email variables]]
* [[WebRTC]]
* [[Time Zone list]]
* [[MOR SIP Header Transformations]]
* [[MOR STIR/SHAKEN]]
* [[PJSIP Codec negotiation]]

 

= [[MOR Number Manipulation | Number Manipulation]] =
* [[MOR Localization | Localization]]
* [[MOR Device Rules | Device Rules]]
** [[MOR Device Rule Groups | Device Rule Groups]]
* [[MOR Provider Rules | Provider Rules]]
* [[DID handling by Localization]]
* [[MOR Number Manipulation Examples | Number Manipulation Examples]]
* [[Block wrong short numbers with Localization]]
* [[MOR - LCR/Tariff change based on call prefix]]
* [[Prefix finder]]
* [[MOR Prelocalization]]

 

=[[Users]] =
* [[User Details]]
** [[Warning balance]]
** [[User Blocking]]
* [[Hide Users]]
* [[Why MOR does not allow to delete users|Why MOR does not allow users to be deleted]]
* [[How to create User and Device|How to create a User and Device]]
* [[MOR_forgot_user_password|How to reset lost GUI password]]
 

= [[Devices]] =
* [[Device settings]]
** [[H323 Device settings]]
** [[Extension lines]]
** [[Ring several devices at same time]]
** [[How to create User and Device|How to create a User and Device]]
** [[Allowed Addresses]]
* [[Devices Bulk Create]]
* [[Trunks]]
* [[CLIs (Incoming CallerIDs)]]
** [[ANI/CLI ban system]]
* [[Duplicate call prevention]]
* [[Allow loss calls]]
* [[Device groups]]
* [[Call Flow]]
* [[Which codecs should I choose for devices|Which codecs should I choose for devices?]]
**[[Change_Audio/Video_Codecs_priority| Codecs priority]]
* [[Authentication|How to configure IP Authentication for Device]]
* [[Registration_Status|Device registration status]]
* [[MOR Device Rules]]
* [[Feature Codes]]
* [[Hide Device Password]]
* [[Disallow duplicate device usernames]]
* [[Disallow users to change their email]]

 

= [[Providers]] =

(also known as terminators, suppliers, vendors or trunks)

* [[Terminators]]
* [[Provider with several IP|Provider with several IPs]]
* [[H323 Provider settings]]
* [[Provider with ANI]]
* [[Configure Provider which can make calls]]
* [[Configure Provider with dynamic IP]]
* [[Simultaneous call limitation]]
* [[NO ANSWER/BUSY interpretation for providers]]
* [[Provider_Deviations|Provider Deviations]]
* [[Provider AGI script]]
* Provider Configuration
** [[Net2phone configuration | Net2phone]]
** [[Broadvoice configuration | Broadvoice]]
** [[Eutelia]]
** [[IXC]]
** [[Configuring DIDWW | DIDWW]]
** [[Vitelity]]
** [[Vono]]
** [[How_to_add_Voicetrading_Provider|Voicetrading]]
** [[Portech GSM as Provider | Portech]]
** [[DID Logic]]
** [[Voxbeam]]

 

= [[Tariffs]] =
* [[Directions and Destinations]]
** [[Destinations Groups]]
** [[Destination Groups Policy]]
** [[Block some Destination to User|Block a Destination to a User]]
** [[Export and bulk import of unassigned destinations]]
* [[Day setup]]
* [[Bulk change Tariffs for Users]]
* [[Wholesale Tariff | Wholesale]]
** [[Entering Rates for Wholesale Tariff]]
** [[Rate import from CSV]]
** [[Blocked Rates]]
* Retail
** [[Advanced Rates | Advanced (Retail) Rates]]
*** [[Entering Rates for Retail Tariff]]
*** [[Advanced Rates for Users| Advanced (Retail) Rates for Users]]
** [[Custom Rates]]
* [[Tariff Transformation]]
** [[Make Retail Tariff from Wholesale Tariff explained]]
* [[Why User can't check his Rates]]

 

= Call Routing =
* [[LCR]]
* [[LCR Logic]]
* [[How to add Provider to LCR]]
* [[Call Routing by price]]
* [[Call Routing by priority (Manual LCR)]]
* [[Call routing per destination basis]]
** [[How to route call to specific Destination through specific Provider]]
** [[How to block calls]]
** [[Blocked_Countries | How to block countries]]
** [[Block some Destination to User|Block a Destination to a User]]
* [[MOR - LCR/Tariff change based on call prefix]]
* [[Routing by Percent]] or Weight-based routing
* [[Why call was not routed through other provider/trunk?|Why was a call not routed through another provider/trunk?]]
* [[Intelligent Internal Routing]]
* Advanced [[extensions_mor_custom.conf]]

 

= DIDs =
* [[DID Management]]
** [[Assign DID to Trunk]]
* [[Work flow for DID]]
* [[DID Billing]]
** [[DID Billing Time explained]]
* [[DIDs Usage]]
* [[Personal DIDs]]
* [[Example - Configuring DID to ring some Device]]
* [[PBX Function External DID]]
* [[Ring-Groups]]
* [[DID with VoxBone using his URI]]
* [[Forward DID to External Number]]
* [[How to charge DID on a monthly basis]]
* [[DID handling by Localization]]
* [[DID Blocking]]
* [[Dial Plans]]
** [[Authorization by PIN]]
** [[Authorization by ANI]]
** [[Calling Card Dial Plan]]
** [[Callback Dial Plan]]
** [[IVR Dial Plan]]
** [[STATISTICS - Various - DIDs]]

 

= [[Accounting]] =
* [[Services]]
** [[Flat-Rates]]
* [[Subscriptions]]
* [[Invoices]]
** [[Invoice configuration]]
** [[Pay Invoice with balance deduction]]
** [[Invoice by CallerID]]
* [[Payments]]
* [[Vouchers]]

 

= Reporting =
* [[Active Calls]]
* [[Last Calls]]
* [[Local Calls Stats]]
* [[Users Calls]]
* [[Users Finances]]
* [[Loss Making Calls]]
* [[DIDs Report]]
* [[Providers Statistics]]
* [[Providers Calls]]
* [[Statement Of Account]]
* [[Aggregate]]
* [[First Activity]]
* [[Quick Stats]]
* [[Simultaneous Calls stats]]
* [[Calls by Source]]
* [[Login Stats]]
* [[Profit Stats]]
* [[Country Stats]]
* [[Hangup Cause Report]]
* [[Graphs]]
* [[Google Maps integration]]
** [[Get Google Maps key]]
* [[Balance in phone]]
* [[Privacy to hide Destination ends]]

 

= Troubleshooting =

* [[Frequently_Asked_Questions_(FAQ) | Frequently Asked Questions]]
* [[Action log]]
* [[Call Tracing]]
* [[Integrity Check]]
* [[Hangupcause Codes]]
** [[H323 hangupcause codes]]
** [[Hangupcause Sounds]]
** [[Different code send to User compared to received from Provider]]
* [[Call Info]]
** [[Call log explanation]]
* [[SIP debug info]]
* [[Provider connection testing]]
* [[Asterisk CLI]]
** [[Watch active calls/channels in Asterisk server from CLI]]
** [[Get Asterisk CLI output for specific call]]
* [[MOR's Core version]]
* [[Lots of calls made by System Admin user]]
* [[Renew Devices]]
* [[Email log]]
* [[MOR forward Q.850 Reason header]]
 

= Maintenance =

* [[How to restart Asterisk server]]
* [[Upgrade MOR GUI]]
* [[Lost MOR GUI admin password]]
* [[MOR Server Speedup]]
* [[Second Admin account]]
* [[Asterisk keepalive script]]

 

= Security =
* [[How to be secure using MOR]]
* [[MOR Change default passwords]]
* [[Blocking SIP Scanners]]
* [[MOR iptables Chains]]
* [[MOR two factor authentication]]
* [[How to set up SSL certificate with Let's Encrypt]]

 

= Testing =

* [[VoIP Bandwidth Calculator]]

 

= Payment gateways =

* [[Payment_Gateway_Addon | Payments Gateway Addon]]
 

= Other functionality =
* [[SIP Header Manipulation]]
* [[IVR system]]
** [[IVR for Calling Cards]]
** [[IVR Greeting for DID]]
* [[Callback]]
** [[WEB Callback]]
** [[Callback over Email]]
** [[MOR API callback init | API Callback_init]]
** [[Callback setup example]]
* [[PBX Functions]]
** [[Voicemail]]
** [[Dial Local]]
** [[PBX Function External DID|External DID]]
* [[Fax2Email]]
* [[Recordings Addon | Recordings]]
* [[PhoneBook]]
* [[Speed Dials]]
* [[Backup system]]
* [[Data import]]
* CDR
** [[CDR Import]]
** [[CDR Rerating]]
** [[CDR Disputes|CDR Disputes]]
* [[Online registration]]
** [[Online registration customization]]
* [[Quick Forwards]]
** [[Quickforwards rules]]
* [[Transfers with MOR]]
* [[GUI on Mobile Devices]]
* [[PBX connection to MOR]]
** [[MOR and Trixbox]]
* [[MOR API]]
** [[API Configuration]]
* [[Cron actions]]

 

= [[MOR Addons|'''MOR Addons''']] =
* [[Limited Addons]]
* [[Automatic Tariff Import]]
* [[Auto-Dialer Addon]]
* [[Call Shop Addon]]
* [[Callback|Callback Addon]]
* [[Calling Cards Addon]]
* [[Mobile Number Portability Addon]]
* [[Monitorings Addon]]
** [[Spy_real-time_calls|Spy real-time calls]]
** [[Alerts]]
** [[Alert Groups]]
** [[Alert Schedules]]
** [[Dynamic Blacklist Functionality]]
* [[Payment Gateway Addon]]
* [[Recordings Addon]]
* [[Reseller Addon]]
* [[Reseller Pro Addon]]
* [[PBX_Functions_Addon | PBX Functions Addon]]

 

= Tutorials =
* [[Usual configuration sequence]]
** [[How to make first call]]
* [[How to create User and Device]]
* [[Dial Local | How to setup Dial Local function]]
* [[Calling Card setup example | How to setup Calling Cards]]
** [[How to setup Access Number to TopUp Card by CallerID]]
* [[Callback setup example | How to setup Callback]]
* [[Conference with MOR + Trixbox | How to setup Conferences using Trixbox]]
* [[How to forward the Call when Device is offline]]
* IVRs
** [[IVR for Calling Cards | How to setup IVR for Calling Cards]]
* DIDs
** [[Example - Configuring DID to ring some Device | How to configure DID to ring some Device]]
** [[Forward DID to External Number | How to forward DID to External Number]]
** [[How to charge DID on a monthly basis]]
** [[IVR Greeting for DID|How to add Greeting for DID]]
* [[How to configure 911 service]]
* [[Block some Destination to User | How to block a Destination to a User]]
* [[How to make several connections from one IP]]
* [[How to be secure using MOR]]
* [[How to change GUI port]]
* [[How to change qualify packets frequency]]
* [[MOR 10CC]]
* [[VitalPBX interconnection with MOR]]

 

= Old Manuals =
* [http://packets.kolmisoft.com/packets/docs/MOR_X4_Manual.pdf MOR X4 Manual]
* [http://packets.kolmisoft.com/packets/docs/MOR_X3_Manual.pdf MOR X3 Manual]
* [http://packets.kolmisoft.com/packets/docs/MOR_12_Manual.pdf MOR 12 Manual]
* [http://packets.kolmisoft.com/packets/docs/MOR_11_Manual.pdf MOR 11 Manual]
* [http://packets.kolmisoft.com/packets/docs/MOR_10_Manual.pdf MOR 10 Manual]
* [[Material for testing users]]

MOR Prelocalization

2026-03-04T11:56:00Z

Admin: /* How to enable it */

MOR Prelocalization

2026-03-04T11:55:37Z

Admin: /* How to enable it */

Prelocalization allows to do '''additional''' [http://wiki.kolmisoft.com/index.php/Localization Localization] before any other action in MOR. Prelocalization is applied to incoming calls (calls to DID numbers) too.

 
= Purpose =

'''<big>Prelocalization allows for greatly reducing the number of Localization rules.</big>''' 

MNP routing and EU/Non-EU discrimination require many rules to work. 
When calls come in from clients that can have one of the following formats (Greek example):
* 210XXXXXXX (national format)
* 30210XXXXXXX(E.164 format)
* +30210XXXXXXX (International format)
* 0030210XXXXXXX (international format) 
If prelocalization does not exist, then each rule applied to localization must be repeated for every dialing type, thus increasing the overall number of rules. 
This is why prelocalization is needed: we avoid adding the same rule multiple times to cover all client dialing types. 
 
Example: In an MNP environment, prefixes are added to the destination numbers. These prefixes have to be removed using localization rules. 
If the prefix added is 569000, then we will need 4 rules in order to solve this, although with prelocalization, we would only need one rule 
 
Without prelocalization rule:

[[File:prelocalization_example1.png]]
 
If prelocalization rules exist, then before MNP prefix is added, or before localization is hit, number would already be localized e.g. 302XXXXXXXXX so we would only need 1 rule instead 4 for one prefix. 
Prelocalization greatly reduces the number of rules needed, so if it exist we would only need the following rule for the same case: 

[[File:prelocalization_example2.png]]

 

=How to enable it=
''' From X17 Core version 27.0.33, this is no longer needed, continue with [[Prelocalization#Configuration]]'''

!!! Please note that if your '''extensions_mor.conf''' contains '''_[A-Z0-9]!''' instead of '''_X.''' then all extensions described bellow should also be set to '''_[A-Z0-9]!'''

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)

If you are using [[Mobile Number Portability Addon]], then this line should go BEFORE the MNP addon line and should look like this:

exten => _X.,1,AGI(mor_prelocalization) ;<--------------------------------------- ADD THIS LINE HERE ----------- !!!!
exten => _X.,n,AGI(mor_mnp)
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,Set(TIMEOUT(digit)=10)
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)

If you are using a system with a Proxy solution, then this line should go AFTER proxy_settings and BEFORE MNP addon (if it is used):

exten => _X.,1,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,AGI(mor_prelocalization) ;<---------Prelocalization line should go after proxy and before mnp (if it is used)---------- !!!!
exten => _X.,n,AGI(mor_mnp)
exten => _X.,n,Set(__MOR_SIP_TO=${SIP_HEADER(To)})
exten => _X.,n,Set(TIMEOUT(response)=20)
exten => _X.,n,Set(TIMEOUT(digit)=10)
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_id = 17
prelocalization_global_rules = 1

Asterisk reload is required:

asterisk -rx "more reload"

=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 (X17 and older)=

Prelocalization output is written to the 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

 

=See also=
* [[MOR Localization]]
* [[Location Groups]]

MOR Localization

2026-03-04T11:54:31Z

Admin:

= Description =

 
<big><big><big>'''Localization transforms received number to E.164 format number.'''</big></big></big>

 
The main idea of localization is: '''No matter how the user dials the number (destination), when localized it should be in E.164 format.'''

Localization has nothing in common with the numbers you send to providers. It operates with numbers received from the caller.

 
Depending on the device's physical location, it is often important to allow users to dial numbers in different formats to reach a destination. For this purpose, each device has a field called '''Location''', which describes the device's physical location and defines rules for how the device can dial a destination. In other words, each device IS in (or belongs to) some Location where specific dialing rules apply.

'''Location describes where a caller IS - not where he is calling to!'''

By default, a device has the location 'Global'. Global rules apply to ALL devices. If a device belongs to some other location and the dialed destination has some rule for this destination, then global rules are not activated – they have a lower priority in location rules.

You can access Localization settings in '''SETTINGS –> Billing –> Functions –> Localization'''.

In the main window, you can see the available Locations:

[[Image:localization1.png]]

At first, there is only the Global location. You can't delete this location. It's the default for all devices.

You can add a new Location by entering this Location's name in the field at the bottom of the table:

[[Image:localization2.png]]

and clicking [[Image:add.png]]:

[[Image:localization3.png]]

 
== Clone ==

Additionally, you can make a copy of your current Localization rules by clicking the copy icon:

[[Image:Localization_copy_function.png]]

 

== Rules ==

In the Rules column, click the Rules icon to access the Location's rules:
 
[[Image:Editbutton.png]]
 
[[File:Localization_rules.png]]
 

'''Destination Rules''' – Changes Destination number.

'''CallerID Rules''' – Changes source number.

'''Combined Rules''' – Change Destination number and Source number. Please note that both Destination and Source cells must be matched to apply Combined Rules. Special symbols * and # do not work in combined rules.

'''Priority of rules that are applied first:'''
* 1) CallerID Rules
* 2) Combined Rules
* 3) Destination Rules

 
Note that if the match is found in "Combined Rules", "Destination Rules" are skipped entirely.

 
=== Removing or adding a prefix ===

To remove a prefix from the dialed number (destination), add a '''Destination Rule''': set '''Cut''' to the prefix you want to remove and '''Add''' to the replacement (if any). You do not need to change the call's owner.

 
To remove a prefix from the caller ID (source), use a '''CallerID Rule''' with '''Cut''' and '''Add''' in the same way.

 
The '''Change Call's owner''', '''Route to DID''', '''Change CallerID Name''', '''Change User LCR to this LCR''', and '''Change User Tariff to this Tariff''' fields are optional; use them only when you need that specific behaviour. They are not required to remove or add a prefix – only '''Cut''' and '''Add''' are needed for that.

 
=== Rule fields ===

The following settings should be explained for rules:

* '''Name''' – just for informational purposes.
* '''Cut''' – what prefix should be cut from the number.
* '''Add''' – what prefix should be added to the number.
* '''Min Len''' – the minimum length of the number to which the rule is being applied.
* '''Max Len''' – the maximum length of the number to which the rule is being applied.
* '''Change User Tariff to this Tariff''' – optional; which Tariff to apply when this rule is applied. Used in special cases, for example [[MOR - LCR/Tariff change based on call prefix | here]]. Leave empty in most cases; not required to remove or add a prefix.
* '''Change User LCR to this LCR''' – optional; which LCR to apply when this rule is applied. Used in special cases, for example [[MOR - LCR/Tariff change based on call prefix | here]]. Leave empty in most cases; not required to remove or add a prefix.
* '''Route to DID''' – optional; allows routing calls to DID according to localization rules. Not required to remove or add a prefix.
* '''Change CallerID Name''' – optional; changes the caller ID name when this rule is applied. Not required to remove or add a prefix.
* '''Change Call's owner''' – optional; changes the owner of the call depending on the incoming tech prefix. Use only when you need to route the call to a specific user; no prefix is required to remove or add.
* '''Enter edit mode''' - lets you change all rules at one time.

When you have entered all the necessary values (Cut or Add can be left empty), click [[Image:add.png]].

For example:
* The normal Lithuania MOB prefix is 3706.
* The user's device is located in Vilnius, Lithuania (displayed as "Lithuania Vilnius").
* By current Lithuanian regulations, the local customer can dial 9-digit numbers starting with 86 to reach Mobile subscribers.

To describe this situation, we create the following rule:

[[Image:localization_5_2.png]]

Rules can be enabled or disabled by clicking the [[Image:check.png]] icon or [[Image:cross.png]] in the '''Enabled?''' column.
* [[Image:edit.png]]- This icon allows you to edit the details of the rule.
* [[Image:cross.png]]- This icon allows you to delete the rule.

Now, in the main '''Localization''' window:

[[Image:localization6.png]]

click on [[Image:view.png]] in the '''Devices''' column to access '''Devices''' in Global '''Location''':

[[Image:localization7.png]]

Here, all Devices with a selected location are listed. Choose other locations for the selected Device and click on [[Image:check.png]] icon to activate this change. The device will be assigned to the selected Location.

[[Image:localization8.png]]

'''NOTE''': It's possible to change a device's Location in the Device settings ('''SETTINGS –> Users –> Devices''').

Now our device belongs to Location "Lithuania Vilnius". And if we dial a mobile number in the Lithuanian format, for example, 863042439, MOR cuts 86 (leaving 3042439) and adds 3706. The result is 37063042439, which is E.164 compatible and can be billed correctly by MOR.

'''NOTE''': Make sure that after localization, your number is always E.164 compatible. [[Call Tracing]] can help you do this.

'''NOTE''': You cannot delete a rule if it is assigned to a device.

 

= Special cases =

 
== Cut everything till Hash ==

With rule '''Cut: *#''' it is possible to cut everything till # (# included) in the dialed destination:

[[Image:Loc_cut_till_hash_2.png]]

For example:

* Dialed number: 1aaaaaaaaa#37063042439
* After Localization: 37063042439

Please note that if the dialed number is #37063042439, the call will not go through, because MOR rejects destinations with # in front of it.

This function can be used in fancy MNP (Mobile Number Portability) schemes and perhaps elsewhere.

 
NOTE: The '''Add''' value still can be used to add any value after '''Cut''' is used on the Destination.

 
== Cut any digits after a specific prefix ==

Works only with Destination and Combined rules.

Cut pattern accepts "x" which indicates any digit:

'''Cut: 12xxx''' 
will cut '''first 5 digits''' from the number which starts with digits "12".

If there are two rules like

'''Cut: 12xxx'''

'''Cut: 1234x'''

and a number

'''12345'''

then the rule '''Cut: 1234x''' will be selected because it matches most of the digits exactly.

Example1:

If we have a rule

'''Cut: 12xxx'''

'''Add: 99'''

Then all the following dialled numbers

1200012345

1257812345

1298712345

will be modified to

9912345

 

Example2:

If we have a rule
'''Cut: 123xxx78'''

'''Add: 78'''

Then all numbers starting from 12300078 till 12399978 will be localised to start with 78

 

== Change LCR/Tariff when CallerID is empty ==

 
This is an '''optional''' feature for special cases (e.g. applying a different LCR or Tariff when the caller ID is missing).

To change LCR/Tariff when CallerID is empty, set the following in Source Localization:

'''Cut: *''' 
'''Min Len: 0''' 
'''Max Len: 0''' 

and then choose the LCR/Tariff you want to set for calls without CallerID.

 

= Reseller localizations =
The reseller is not using the admin's global localization rules. Instead, he can now copy the rules and modify them to suit his needs. All newly created resellers have those global rules copied automatically from the admin. This feature can be disabled by the admin in [[Reseller_Settings|Reseller Settings]].
 
[[File:Copy_rules.png]]
 
'''IMPORTANT''': Fields "Change User Tariff to this Tariff" and "Change User LCR to this LCR" will not be copied.
 
"Default location" does not act as "Global location" on the reseller's account. Only the rules set in the device's settings will be applied.
 

= Route to DID =

 
This is an '''optional''' feature. Admin and Reseller PRO users can route calls to a DID according to localization rules.
 
[[File:Localization9.png]]
 
Start typing the DID number, and you will see all the DIDs that start with that number. If the DID you need is not there, enter more digits - only the first 20 DIDs starting with that number are shown.

 
= Change owner of call depending on incoming prefix =

 
This is an '''optional''' feature for routing the call to a specific user based on the incoming tech prefix.

It is now possible to change the call owner based on the incoming tech prefix.

* Open the localization menu to find the "Change Call's Owner" field.
[[File:localization8_5.png]]
 
* Enter the incoming prefix that needs to be cut in the "Cut" section.
* Afterwards, choose a user from the drop-down list and the device to which the call should be assigned.
[[File:Change_owner2.png]]
* This feature is also available for resellers.
* Admin can assign the call to ANY user on the system (even to those that do not belong to the admin).

 

= See also =

* [[MOR Number Manipulation]]
** [[MOR Device Rules]]
** [[MOR Provider Rules]]
** [[DID handling by Localization]]
** [[MOR Number Manipulation Examples]]
* [[MOR Prelocalization]]
* [[Location Groups]]
* [http://www.wtng.info/wtng-reg.html World Telephone Numbering Guide]

MOR Prelocalization

2026-03-04T11:54:22Z

Admin:

Prelocalization allows to do '''additional''' [http://wiki.kolmisoft.com/index.php/Localization Localization] before any other action in MOR. Prelocalization is applied to incoming calls (calls to DID numbers) too.

 
= Purpose =

'''<big>Prelocalization allows for greatly reducing the number of Localization rules.</big>''' 

MNP routing and EU/Non-EU discrimination require many rules to work. 
When calls come in from clients that can have one of the following formats (Greek example):
* 210XXXXXXX (national format)
* 30210XXXXXXX(E.164 format)
* +30210XXXXXXX (International format)
* 0030210XXXXXXX (international format) 
If prelocalization does not exist, then each rule applied to localization must be repeated for every dialing type, thus increasing the overall number of rules. 
This is why prelocalization is needed: we avoid adding the same rule multiple times to cover all client dialing types. 
 
Example: In an MNP environment, prefixes are added to the destination numbers. These prefixes have to be removed using localization rules. 
If the prefix added is 569000, then we will need 4 rules in order to solve this, although with prelocalization, we would only need one rule 
 
Without prelocalization rule:

[[File:prelocalization_example1.png]]
 
If prelocalization rules exist, then before MNP prefix is added, or before localization is hit, number would already be localized e.g. 302XXXXXXXXX so we would only need 1 rule instead 4 for one prefix. 
Prelocalization greatly reduces the number of rules needed, so if it exist we would only need the following rule for the same case: 

[[File:prelocalization_example2.png]]

 

=How to enable it=
''' From X17 Core version 27.0.33, this is no longer needed, continue with [[Prelocalization#Configuration]]'''

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

!!! Please note that if your '''extensions_mor.conf''' contains '''_[A-Z0-9]!''' instead of '''_X.''' then all extensions described bellow should also be set to '''_[A-Z0-9]!'''

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)

If you are using [[Mobile Number Portability Addon]], then this line should go BEFORE the MNP addon line and should look like this:

exten => _X.,1,AGI(mor_prelocalization) ;<--------------------------------------- ADD THIS LINE HERE ----------- !!!!
exten => _X.,n,AGI(mor_mnp)
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,Set(TIMEOUT(digit)=10)
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)

If you are using a system with a Proxy solution, then this line should go AFTER proxy_settings and BEFORE MNP addon (if it is used):

exten => _X.,1,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,AGI(mor_prelocalization) ;<---------Prelocalization line should go after proxy and before mnp (if it is used)---------- !!!!
exten => _X.,n,AGI(mor_mnp)
exten => _X.,n,Set(__MOR_SIP_TO=${SIP_HEADER(To)})
exten => _X.,n,Set(TIMEOUT(response)=20)
exten => _X.,n,Set(TIMEOUT(digit)=10)
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_id = 17
prelocalization_global_rules = 1

Asterisk reload is required:

asterisk -rx "more reload"

=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 (X17 and older)=

Prelocalization output is written to the 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

 

=See also=
* [[MOR Localization]]
* [[Location Groups]]

MOR Location Groups

2026-03-04T11:52:59Z

Admin:

MOR Device Rule Groups

2026-03-04T11:52:45Z

Admin:

= Description =

Device Rule Group is simply a group of [[MOR Device Rules]] which can be assigned to device. This allows easy sharing of common rules between devices, without copying same rules to different devices over and over again. For each device, Device rules consist of rules assigned to Device directly and rules from assigned Device Rule Group. Direct Device rules have higher priority than rules from Device Rule Group.

 

= Usage =
Device Rule Groups is available under '''Billing->Users->Devices->Device Rule Groups''' 

[[File:Device_Rule_Groups1.png]] 

Here you can list of Device Rule Groups and create a new Group: 

[[File:Device_Rule_Groups2.png]] 

Clicking on Rules Icon opens Rules page where you can actually enter desired rules for that Group:

[[File:Device_Rule_Groups3.png]] 

Device Rule Group can be assigned to device by clicking on already assigned device in Device Rule Group Device list and selecting another group, or in Device Edit window, as shown bellow:

[[File:Device_Rule_Groups4.png]] 

=See also=
* [[MOR Device Rules]]
* [[MOR Localization]]
* [[MOR Prelocalization]]

MOR Prelocalization

2026-03-04T11:52:30Z

Admin: Admin moved page Prelocalization to MOR Prelocalization

Prelocalization allows to do '''additional''' [http://wiki.kolmisoft.com/index.php/Localization Localization] before any other action in MOR. Prelocalization is applied to incoming calls (calls to DID numbers) too.

 
= Purpose =

'''<big>Prelocalization allows to greatly reduce the number of Localization rules.</big>''' 

MNP routing and EU/NonEU discrimination need a lot of rules in order to work. 
When calls come in from clients that can have one of the following formats (Greek example):
* 210XXXXXXX (national format)
* 30210XXXXXXX(E.164 format)
* +30210XXXXXXX (International format)
* 0030210XXXXXXX (international format) 
If prelocalization does not exist, then each rule applied to localization must be repeated for every dialing type, thus increasing the overall amount of rules. 
This is why prelocalization is needed, so we will avoid adding same rule multiple times in order to cover all dialing types from clients. 
 
Example: In MNP environment prefixes are added to the destination numbers. These prefixes have to be removed using localization rules. 
If prefix added is 569000 then we will need 4 rules in order to solve this although with prelocalization we would only need one rule 
 
Without prelocalization rule:

[[File:prelocalization_example1.png]]
 
If prelocalization rules exist, then before MNP prefix is added, or before localization is hit, number would already be localized e.g. 302XXXXXXXXX so we would only need 1 rule instead 4 for one prefix. 
Prelocalization greatly reduces amount of rules needed so if it exist we would only need following rule for the same case: 

[[File:prelocalization_example2.png]]

 

=How to enable it=
''' From X17 Core version 27.0.33, this is no longer needed, continue with [[Prelocalization#Configuration]]'''

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

!!! Please note that if your '''extensions_mor.conf''' contains '''_[A-Z0-9]!''' instead of '''_X.''' then all extensions described bellow should also be set to '''_[A-Z0-9]!'''

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)

If you are using [[Mobile Number Portability Addon]], then this line should go BEFORE MNP addon line and should look like this:

exten => _X.,1,AGI(mor_prelocalization) ;<--------------------------------------- ADD THIS LINE HERE ----------- !!!!
exten => _X.,n,AGI(mor_mnp)
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,Set(TIMEOUT(digit)=10)
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)

If you are using system with Proxy solution, then this line should go AFTER proxy_settings and BEFORE MNP addon (if it is used):

exten => _X.,1,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,AGI(mor_prelocalization) ;<---------Prelocalization line should go after proxy and before mnp (if it is used)---------- !!!!
exten => _X.,n,AGI(mor_mnp)
exten => _X.,n,Set(__MOR_SIP_TO=${SIP_HEADER(To)})
exten => _X.,n,Set(TIMEOUT(response)=20)
exten => _X.,n,Set(TIMEOUT(digit)=10)
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_id = 17
prelocalization_global_rules = 1

Asterisk reload is required:

asterisk -rx "more reload"

=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 (X17 and older)=

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

 

=See also=
* [[MOR Localization]]
* [[Location Groups]]

MOR Manual

2026-03-04T11:51:58Z

Admin:

<html>
<div align="center">
<iframe width="640" height="360" src="https://www.youtube.com/embed/R65ufpHOz_g" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</div>
</html>

<mkmeta>Detailed instructions how to use MOR Class 5 Softswitch</mkmeta>
<div align="center">
 
<center>MOR is a Class 5 Softswitch with Billing and Routing with extended functionality, increased stability, and professional support directly from the developers. It enables VoIP providers to offer various services.</center>

</div>
 
= Introduction =
* [[Introduction]] [[Image:flag_esp.jpg|alt="flag"|link=|right|link=Introduction (es)]]
* [[Who is this product designed for]]
* [[MOR Functionality]]
* [[Supported Business Models]]
* [[MOR Admin Interface|Admin Interface]]
* [[How to make first call|How to make a first call]] [[Image:flag_rus.jpg|alt="flag"|link=|right|link=How to make first call (ru)]]
 

= Concepts/Definitions =
* [[MOR Terminology]]
* [[Billing Concepts]] [[Image:flag_rus.jpg|right|alt="flag"|link=|link=Billing Concepts (ru)]]
* [[Billing Logic]]
* [[Call explained]]
* [[E.164]]
* [[Rounding]]
* [[Multi-Tax system]]
* [[What is a PIN?]]
* [[ASR/ACD]]
* [[Margin and Markup]]
* [[What are callgroups and pickupgroups|What are callgroups and pickupgroups?]]
* [[Balance and Credit]]
* [[Local Calls]]
* [[Prepaid Logic]]
* [[Authentication]]
* [[Fax over VoIP]]

 

= Configuration =
* [[mor.conf]]
* [[Performance Suggestions]]
* [[Configuration from GUI]]
** [[reCAPTCHA]]
** [[Payments configuration]]
** [[Default device settings]]
** [[Default_user|Default user settings]]
** [[Accountant permissions]]
** [[Logo change]]
** [[Currencies]]
** [[Translations]]
** [[Global_date_format | Global date format]]
** [[Remove Manual link from admin GUI]]
* [[Voicemail]]
* [[Multi Server support]]
* [[MOR White-labeling|White-labeling]]
* Emails
** [[Configuration_from_GUI#Emails|Email settings]]
** [[Emails|Mass Emails]]
** [[Email variables]]
* [[WebRTC]]
* [[Time Zone list]]
* [[MOR SIP Header Transformations]]
* [[MOR STIR/SHAKEN]]
* [[PJSIP Codec negotiation]]

 

= [[MOR Number Manipulation | Number Manipulation]] =
* [[MOR Localization | Localization]]
* [[MOR Device Rules | Device Rules]]
** [[MOR Device Rule Groups | Device Rule Groups]]
* [[MOR Provider Rules | Provider Rules]]
* [[DID handling by Localization]]
* [[MOR Number Manipulation Examples | Number Manipulation Examples]]
* [[Block wrong short numbers with Localization]]
* [[MOR - LCR/Tariff change based on call prefix]]
* [[Prefix finder]]

 

=[[Users]] =
* [[User Details]]
** [[Warning balance]]
** [[User Blocking]]
* [[Hide Users]]
* [[Why MOR does not allow to delete users|Why MOR does not allow users to be deleted]]
* [[How to create User and Device|How to create a User and Device]]
* [[MOR_forgot_user_password|How to reset lost GUI password]]
 

= [[Devices]] =
* [[Device settings]]
** [[H323 Device settings]]
** [[Extension lines]]
** [[Ring several devices at same time]]
** [[How to create User and Device|How to create a User and Device]]
** [[Allowed Addresses]]
* [[Devices Bulk Create]]
* [[Trunks]]
* [[CLIs (Incoming CallerIDs)]]
** [[ANI/CLI ban system]]
* [[Duplicate call prevention]]
* [[Allow loss calls]]
* [[Device groups]]
* [[Call Flow]]
* [[Which codecs should I choose for devices|Which codecs should I choose for devices?]]
**[[Change_Audio/Video_Codecs_priority| Codecs priority]]
* [[Authentication|How to configure IP Authentication for Device]]
* [[Registration_Status|Device registration status]]
* [[MOR Device Rules]]
* [[Feature Codes]]
* [[Hide Device Password]]
* [[Disallow duplicate device usernames]]
* [[Disallow users to change their email]]

 

= [[Providers]] =

(also known as terminators, suppliers, vendors or trunks)

* [[Terminators]]
* [[Provider with several IP|Provider with several IPs]]
* [[H323 Provider settings]]
* [[Provider with ANI]]
* [[Configure Provider which can make calls]]
* [[Configure Provider with dynamic IP]]
* [[Simultaneous call limitation]]
* [[NO ANSWER/BUSY interpretation for providers]]
* [[Provider_Deviations|Provider Deviations]]
* [[Provider AGI script]]
* Provider Configuration
** [[Net2phone configuration | Net2phone]]
** [[Broadvoice configuration | Broadvoice]]
** [[Eutelia]]
** [[IXC]]
** [[Configuring DIDWW | DIDWW]]
** [[Vitelity]]
** [[Vono]]
** [[How_to_add_Voicetrading_Provider|Voicetrading]]
** [[Portech GSM as Provider | Portech]]
** [[DID Logic]]
** [[Voxbeam]]

 

= [[Tariffs]] =
* [[Directions and Destinations]]
** [[Destinations Groups]]
** [[Destination Groups Policy]]
** [[Block some Destination to User|Block a Destination to a User]]
** [[Export and bulk import of unassigned destinations]]
* [[Day setup]]
* [[Bulk change Tariffs for Users]]
* [[Wholesale Tariff | Wholesale]]
** [[Entering Rates for Wholesale Tariff]]
** [[Rate import from CSV]]
** [[Blocked Rates]]
* Retail
** [[Advanced Rates | Advanced (Retail) Rates]]
*** [[Entering Rates for Retail Tariff]]
*** [[Advanced Rates for Users| Advanced (Retail) Rates for Users]]
** [[Custom Rates]]
* [[Tariff Transformation]]
** [[Make Retail Tariff from Wholesale Tariff explained]]
* [[Why User can't check his Rates]]

 

= Call Routing =
* [[LCR]]
* [[LCR Logic]]
* [[How to add Provider to LCR]]
* [[Call Routing by price]]
* [[Call Routing by priority (Manual LCR)]]
* [[Call routing per destination basis]]
** [[How to route call to specific Destination through specific Provider]]
** [[How to block calls]]
** [[Blocked_Countries | How to block countries]]
** [[Block some Destination to User|Block a Destination to a User]]
* [[MOR - LCR/Tariff change based on call prefix]]
* [[Routing by Percent]] or Weight-based routing
* [[Why call was not routed through other provider/trunk?|Why was a call not routed through another provider/trunk?]]
* [[Intelligent Internal Routing]]
* Advanced [[extensions_mor_custom.conf]]

 

= DIDs =
* [[DID Management]]
** [[Assign DID to Trunk]]
* [[Work flow for DID]]
* [[DID Billing]]
** [[DID Billing Time explained]]
* [[DIDs Usage]]
* [[Personal DIDs]]
* [[Example - Configuring DID to ring some Device]]
* [[PBX Function External DID]]
* [[Ring-Groups]]
* [[DID with VoxBone using his URI]]
* [[Forward DID to External Number]]
* [[How to charge DID on a monthly basis]]
* [[DID handling by Localization]]
* [[DID Blocking]]
* [[Dial Plans]]
** [[Authorization by PIN]]
** [[Authorization by ANI]]
** [[Calling Card Dial Plan]]
** [[Callback Dial Plan]]
** [[IVR Dial Plan]]
** [[STATISTICS - Various - DIDs]]

 

= [[Accounting]] =
* [[Services]]
** [[Flat-Rates]]
* [[Subscriptions]]
* [[Invoices]]
** [[Invoice configuration]]
** [[Pay Invoice with balance deduction]]
** [[Invoice by CallerID]]
* [[Payments]]
* [[Vouchers]]

 

= Reporting =
* [[Active Calls]]
* [[Last Calls]]
* [[Local Calls Stats]]
* [[Users Calls]]
* [[Users Finances]]
* [[Loss Making Calls]]
* [[DIDs Report]]
* [[Providers Statistics]]
* [[Providers Calls]]
* [[Statement Of Account]]
* [[Aggregate]]
* [[First Activity]]
* [[Quick Stats]]
* [[Simultaneous Calls stats]]
* [[Calls by Source]]
* [[Login Stats]]
* [[Profit Stats]]
* [[Country Stats]]
* [[Hangup Cause Report]]
* [[Graphs]]
* [[Google Maps integration]]
** [[Get Google Maps key]]
* [[Balance in phone]]
* [[Privacy to hide Destination ends]]

 

= Troubleshooting =

* [[Frequently_Asked_Questions_(FAQ) | Frequently Asked Questions]]
* [[Action log]]
* [[Call Tracing]]
* [[Integrity Check]]
* [[Hangupcause Codes]]
** [[H323 hangupcause codes]]
** [[Hangupcause Sounds]]
** [[Different code send to User compared to received from Provider]]
* [[Call Info]]
** [[Call log explanation]]
* [[SIP debug info]]
* [[Provider connection testing]]
* [[Asterisk CLI]]
** [[Watch active calls/channels in Asterisk server from CLI]]
** [[Get Asterisk CLI output for specific call]]
* [[MOR's Core version]]
* [[Lots of calls made by System Admin user]]
* [[Renew Devices]]
* [[Email log]]
* [[MOR forward Q.850 Reason header]]
 

= Maintenance =

* [[How to restart Asterisk server]]
* [[Upgrade MOR GUI]]
* [[Lost MOR GUI admin password]]
* [[MOR Server Speedup]]
* [[Second Admin account]]
* [[Asterisk keepalive script]]

 

= Security =
* [[How to be secure using MOR]]
* [[MOR Change default passwords]]
* [[Blocking SIP Scanners]]
* [[MOR iptables Chains]]
* [[MOR two factor authentication]]
* [[How to set up SSL certificate with Let's Encrypt]]

 

= Testing =

* [[VoIP Bandwidth Calculator]]

 

= Payment gateways =

* [[Payment_Gateway_Addon | Payments Gateway Addon]]
 

= Other functionality =
* [[SIP Header Manipulation]]
* [[IVR system]]
** [[IVR for Calling Cards]]
** [[IVR Greeting for DID]]
* [[Callback]]
** [[WEB Callback]]
** [[Callback over Email]]
** [[MOR API callback init | API Callback_init]]
** [[Callback setup example]]
* [[PBX Functions]]
** [[Voicemail]]
** [[Dial Local]]
** [[PBX Function External DID|External DID]]
* [[Fax2Email]]
* [[Recordings Addon | Recordings]]
* [[PhoneBook]]
* [[Speed Dials]]
* [[Backup system]]
* [[Data import]]
* CDR
** [[CDR Import]]
** [[CDR Rerating]]
** [[CDR Disputes|CDR Disputes]]
* [[Online registration]]
** [[Online registration customization]]
* [[Quick Forwards]]
** [[Quickforwards rules]]
* [[Transfers with MOR]]
* [[GUI on Mobile Devices]]
* [[PBX connection to MOR]]
** [[MOR and Trixbox]]
* [[MOR API]]
** [[API Configuration]]
* [[Cron actions]]

 

= [[MOR Addons|'''MOR Addons''']] =
* [[Limited Addons]]
* [[Automatic Tariff Import]]
* [[Auto-Dialer Addon]]
* [[Call Shop Addon]]
* [[Callback|Callback Addon]]
* [[Calling Cards Addon]]
* [[Mobile Number Portability Addon]]
* [[Monitorings Addon]]
** [[Spy_real-time_calls|Spy real-time calls]]
** [[Alerts]]
** [[Alert Groups]]
** [[Alert Schedules]]
** [[Dynamic Blacklist Functionality]]
* [[Payment Gateway Addon]]
* [[Recordings Addon]]
* [[Reseller Addon]]
* [[Reseller Pro Addon]]
* [[PBX_Functions_Addon | PBX Functions Addon]]

 

= Tutorials =
* [[Usual configuration sequence]]
** [[How to make first call]]
* [[How to create User and Device]]
* [[Dial Local | How to setup Dial Local function]]
* [[Calling Card setup example | How to setup Calling Cards]]
** [[How to setup Access Number to TopUp Card by CallerID]]
* [[Callback setup example | How to setup Callback]]
* [[Conference with MOR + Trixbox | How to setup Conferences using Trixbox]]
* [[How to forward the Call when Device is offline]]
* IVRs
** [[IVR for Calling Cards | How to setup IVR for Calling Cards]]
* DIDs
** [[Example - Configuring DID to ring some Device | How to configure DID to ring some Device]]
** [[Forward DID to External Number | How to forward DID to External Number]]
** [[How to charge DID on a monthly basis]]
** [[IVR Greeting for DID|How to add Greeting for DID]]
* [[How to configure 911 service]]
* [[Block some Destination to User | How to block a Destination to a User]]
* [[How to make several connections from one IP]]
* [[How to be secure using MOR]]
* [[How to change GUI port]]
* [[How to change qualify packets frequency]]
* [[MOR 10CC]]
* [[VitalPBX interconnection with MOR]]

 

= Old Manuals =
* [http://packets.kolmisoft.com/packets/docs/MOR_X4_Manual.pdf MOR X4 Manual]
* [http://packets.kolmisoft.com/packets/docs/MOR_X3_Manual.pdf MOR X3 Manual]
* [http://packets.kolmisoft.com/packets/docs/MOR_12_Manual.pdf MOR 12 Manual]
* [http://packets.kolmisoft.com/packets/docs/MOR_11_Manual.pdf MOR 11 Manual]
* [http://packets.kolmisoft.com/packets/docs/MOR_10_Manual.pdf MOR 10 Manual]
* [[Material for testing users]]

LCR

2026-03-04T11:51:40Z

Admin:

=Description=

LCR (Least Cost Routing) is a set of Providers that should be used to send a call when trying to dial any destination - for example, by the cheapest rate.

The correct name for such a function is a Routing Table because the function supports other ways of routing, not just finding the cheapest route.

By default LCR supports fail-over. That is, if one provider fails, the next one is dialed. This is completely invisible for the caller and lets you increase the chances of the user reaching his destination. If one Provider is not capable of delivering a call, the system will try to use the remaining [[How_to_add_Provider_to_LCR | Providers]].
 
==Fail-over explanation==

=== Use only first Provider in the row ===

This option can allow/deny failover for LCR.

When it is enabled it only allows the first Provider in the Routing Table/LCR to be used.

Please note that when using ANI Authentication, a second query is made to get LCR info.
If this option is set to "Yes" on the first query, the second query will not change it.

In other words - if the first LCR denies Failover, the second ANI LCR can't enable Failover.

This is by design to avoid situations where the misconfiguration can create loops in the call flow.

=== Examples ===

With such configuration:
 
[[image:lcr_fo_case1.png]]
 
System will do following:

* system tries to use "Kolmisoft PREMIUM";

* if above fails, system tries to use "Kolmisoft STANDARD";

* end.
 
With such configuration:
 
[[image:lcr_fo_case2.png]]
 
System will do following:
* system tries to use "Kolmisoft PREMIUM";

* end.

NOTE: if the original User is being changed by ANI, and if the original User has "Use only first Provider in the row" set to YES on its LCR, then even if resulting User LCR has "Use only first Provider in the row" set to NO, the system will act as it is set to YES. (See description above why it is so)
 
With such configuration:
 
[[image:lcr_fo_case3.png]]
 
The system will do the following:
* system tries to use "Kolmisoft PREMIUM";

* if above fails, the system tries to use "Kolmisoft STANDARD";

* if above fails, the system tries to use provider "112" even if its rate is higher than User rate;

* end.

It is possible to change User's tariff when the Failover provider is used. By default, the current User's tariff is used.
 
[[File:failover_provider_user_tariff.png]]
 

=Usage=

Go to '''SETTINGS –> Billing –> LCR'''
 
[[File:lcr_path.png]]
 
Here you can see the list off all LCRs
 
[[File:lcr_main.png]]
 
* Name – name of LCR.
* Order – type of routing mode.
* Providers – quantity of providers in LCR. Click on it to [[How_to_add_Provider_to_LCR | Add Providers to LCR]]
* [[Call_routing_per_destination_basis | By destination]]
* Usage Details – the list of Users and Card Groups where this LCR is used.
* [[LCR make tariff | Make Tariff from LCR Providers to CSV]] – feature that gets you a CSV with the MIN/MAX prices selected from the list of Providers in LCR. Click on the [[Image:excel.png]] icon and the download should start automatically. (De-activated provider will be taken into CSV. "by Destination" will not be taken into CSV)
* LCR copy – press on icon to make LCR copy.
 
==Supported routing modes==

* [[Call Routing by price|By Price]] - cheapest first (Least Cost Routing).
* [[Call Routing by priority (Manual LCR) | By priority]].
* [[Routing by Percent| By percent]] or Weight-based routing.

The user has one base LCR, so that all his calls are routed by some preset rule.

It is possible to route different destinations for a User using [[Call routing per destination basis]].
 
==Creation==
Press [[Image:icon_add.png]]'''New LCR''' to create LCR.
 
=== VIDEO: How to create LCR ===

<html>
<iframe width="640" height="360" src="https://www.youtube.com/embed/7sCaBH35hXc" frameborder="0"></iframe>
</html>

 
==Additional Configuration==

Go to LCRs list and press [[image:icon_edit.png]] icon.
 
[[File:lcr_time_periods.png]]
 
'''First Providers percent limit''' - visible when order by Price is selected. If the following Providers will have higher prices by this percent compared to the first Provider, these Providers will be skipped. 0 value disables the use of this setting. 
'''Minimal Rate Margin Percent''' - use only those Providers which generate profit (per minute) equal or higher than defined percentage value in this field. For example, if you pay to your Provider 1 EUR/min and your Minimal Rate Margin Percent is set to 50%, then only calls with a user rate equal to or higher than 1.5 EUR/min are allowed to call. After 1 min of call, you will pay 1 EUR to your provider, and the user will pay you 1.5 EUR. Your profit will be 0.5 EUR which is 50% more of what you paid to your Provider. If your Minimal Rate Margin is -30%, then you allow some losses in your calls. If you pay 1 EUR to your Provider after 1 minute of call, then the user should pay you 0.7 EUR or more. You will pay 1 EUR and you will get 0.7 EUR which is 30% less than what you paid.
 
===LCR Time Periods===

Sometimes there is such demand to change LCR for some time period. This functionality gives you the ability to do that. In the LCR Edit page time periods can be set.

The time period defines the exact time period LCR will be active. There is a limit of five periods in one LCR. The rest of the time will be used the main LCR.

The timezone in Time Periods is in the Server's (Linux) timezone.
 
'''Examples'''

# Select '''Date''' from 1 of January to 28 of February and choose '''Hour : Minute''' from 09:00 to 18:59. Selected LCR will be used from 1 of January till 28 of February at time from 09:00 till 18:59.
# Select just '''Hour : Minute''' from 19:00 to 08:59 and selected LCR will be used every day at time from 19:00 till 08:59.
# Select '''Weekday''' from Monday to Friday and choose '''Hour : Minute''' from 13:00 to 15:59. Selected LCR will be used every week from Monday till Friday at time from 13:00 till 15:59.
# Select '''Date''' from 1 of January to 31 of January and '''Weekday''' from Monday to Monday. Selected LCR will be used every Monday in January.

If two periods overlap, then it is an undefined condition. There is no algorithm to prioritize one line over another. Avoid the overlap to ensure that the right LCR is used.
 

===LCR Loss Calls===
It is possible to enable Loss Calls per LCR. The default setting - unchecked.
 
[[File:LCR_loss_calls.png]]
 
This setting allows you to decide whether you want to allow users a provider if the provider's rate to a destination is higher than the user's rate.

By allowing such a call, you will pay more to the provider than the user pays to you for it, which means that you will take a loss on the call.

==Copying LCRs between resellers==

Sometimes you need to make a LCR which takes quite a long time to make. If you have made a similar one before you can just copy it and change appropriate details.

Go to '''SETTINGS''' -> '''Billing''' -> '''LCR''' -> '''Copy LCR'''
 
[[File:lcr_copy_path.png]]
 
You will see this window:
 
[[File:lcr_copy.png]]
 
Choose ''Original LCR reseller'' and ''Cloned LCR reseller'' and click ''Clone'' button.

Please note that LCR will not be allowed to copy if reseller B is not allowed to use Providers which are used by Reseller A.
 
=See also=

* [[LCR Logic]]
* [[How to add Provider to LCR]]
* [[Call Routing by price]]
* [[Call Routing by priority (Manual LCR) | Call Routing by priority ]]
* [[Routing by Percent | Call Routing by percent]] or Weight-based routing
* [[Call routing per destination basis]]
* [[MOR - LCR/Tariff change based on call prefix]]
* [[Why call was not routed through other provider/trunk?|Why was a call not routed through another provider/trunk?]]
* [[LCR_make_tariff|Make Tariff from LCR Providers to CSV]]

Tariffs

2026-03-04T11:51:31Z

Admin:

<html>
<div align="center">
<iframe width="640" height="360" src="https://www.youtube.com/embed/q3M72nsN4Ts" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</div>
</html>

=Description=

Tariffs are sets of rates (prices) to different destinations. There are three types of tariffs: providers wholesale (inbound), users wholesale (outbound) and users retail (outbound).
 
===Tariff types===

There are three types of tariffs – '''Wholesale''', '''Retail''' and '''By Provider'''. Note that Tariffs for [[Providers]] type are also Wholesale. The difference between '''wholesale''' and '''retail''' tariffs is in the way rates are set for destinations.

In wholesale tariffs, rates can be set to every destination possible (by prefix). In retail tariffs, destinations are grouped, which makes it possible to have lower rates. Wholesale and retail tariffs are used in different situations, and each type has its advantages and disadvantages.

The advantage for wholesale providers is the possibility of entering different rates for different destinations (prefixes). It is useful to set this tariff when you resell services to other providers.

If your clients are retail end-users, it is better to use the retail tariff. They are easier to manage and understand for the final user.

By Provider Tariff type is dynamic and adds fixed markup on top of the Provider's rates per Destination.
 

=Usage=

Go to '''SETTINGS –> Billing –> Tariffs'''.
 
[[File:tariffs_path.png]]
 
You will see full list of all types of tariff:
 
[[File:tariffs.png]]
 
* Click on [[Image:icon_add.png]]'''New tariff''' to create new tariff. 
* [[Image:excel.png]]'''Destinations CSV''' exports all destinations list. 
* Click on [[image:icon_edit.png]]'''Change Tariff for Users''' to [[Bulk change Tariffs for Users]].
* Search applied for searching tariffs where chosen prefix has rate.
* You can see two numbers in Rates count, for example 251/251. First number shows active rates number, the second number shows total rates number.
 
===Wholesale Tariffs for Providers and for Users===

As you can see in picture above there are ability to manage [[Image:coins.png]] '''[[Entering Rates for Wholesale Tariff | Rates ()]]''' manually, [[Image:excel.png]][[Rate import from CSV|Import from CSV]], [[Rates Update|update Rates]] by Destination mask, delete all Rates form Tariff. Also you can [[Make Retail Tariff from Wholesale Tariff explained | Make user retail tariff]] from wholesale tariff or make new wholesale tariff from old one. When Tariff has [[Rate Effective From | Effective From]] Rates then Active Rates will be taken. Check your tariff rates by exporting CSV files. Click on [[Image:Details-icon.png]] icon to see list of places, where this Tariff is assigned.
 
'''Effective From date''' 

Wholesale's Tariff Rates lists has column named [[Rate Effective From | Effective from]] which shows the date when the rate specified becomes active. This date cannot be changed or created in GUI, it can be added to GUI through [[Rate import from CSV |Tariff import]]
 
===Retail Tariffs===

As you can see in picture above there is an ability to manage [[Image:coins.png]] '''[[Entering Rates for Retail Tariff | Rates]]''' manually and to delete all rates from tariff. Check your tariff rates by exporting CSV files. Click on [[Image:Details-icon.png]] icon to see list of places, where this tariff is assigned.
 
Click on '''Make User Retail Tariff''' to make a new Retail Tariff from current.
 
[[File:MakeRetailTariff.png]]
 
*Tariff name: New tariff name
*Add Rate amount to all Minutes: Add a value to current rates. It is possible to add a Percentage or Value, for example, 10% or 0.1. Input length is limited to 20 characters.
*Add Rate amount to all Events: Add a value to all Events. Events and Minutes are also a part of [[Advanced Rates]]. Input length is limited to 20 characters.
 

===By Provider Tariffs (Dynamic Tariff Type) ===

'''Dynamic User Tariff by Provider Tariff''' allows to avoid repetitive work with Rates import for End Users every time Provider changes his Price sheets. When this Tariff is assigned to User, his rates will depend on Provider's rates. You can manage User's billing by changing delta value and delta percent in this type of Tariff. For example, if you set delta percent to be 10%, then User will be billed by Provider's rate plus 10% of that rate. Your profit will be 10% of your selfcost.
Click on [[Image:Details-icon.png]] icon to see list of places, where this tariff is assigned.
 

=From Accountant=

Accountant must have [[Accountant permissions]] to manage Admins Tariffs.
 
=From Reseller/Reseller PRO=

Resellers have their own tariffs list and they are able to manage them independent from Admin.
 
=See also=

* [[Entering Rates for Wholesale Tariff]]
* [[Entering Rates for Retail Tariff]]
* [[Advanced Rates]]
* [[Rate import from CSV]]
* [[Importing Tariffs from CSV with wrong Regional Settings]]
* [[Make Retail Tariff from Wholesale Tariff explained]]
* [[Bulk change Tariffs for Users]]
* [[Day setup]]
* [[MOR - LCR/Tariff change based on call prefix]]
* [[Change Tariff for Connection Points]]
* [[How to copy a Tariff]]

MOR Localization

2026-03-04T11:51:08Z

Admin:

= Description =

 
<big><big><big>'''Localization transforms received number to E.164 format number.'''</big></big></big>

 
The main idea of localization is: '''No matter how the user dials the number (destination), when localized it should be in E.164 format.'''

Localization has nothing in common with the numbers you send to providers. It operates with numbers received from the caller.

 
Depending on the device's physical location, it is often important to allow users to dial numbers in different formats to reach a destination. For this purpose, each device has a field called '''Location''', which describes the device's physical location and defines rules for how the device can dial a destination. In other words, each device IS in (or belongs to) some Location where specific dialing rules apply.

'''Location describes where a caller IS - not where he is calling to!'''

By default, a device has the location 'Global'. Global rules apply to ALL devices. If a device belongs to some other location and the dialed destination has some rule for this destination, then global rules are not activated – they have a lower priority in location rules.

You can access Localization settings in '''SETTINGS –> Billing –> Functions –> Localization'''.

In the main window, you can see the available Locations:

[[Image:localization1.png]]

At first, there is only the Global location. You can't delete this location. It's the default for all devices.

You can add a new Location by entering this Location's name in the field at the bottom of the table:

[[Image:localization2.png]]

and clicking [[Image:add.png]]:

[[Image:localization3.png]]

 
== Clone ==

Additionally, you can make a copy of your current Localization rules by clicking the copy icon:

[[Image:Localization_copy_function.png]]

 

== Rules ==

In the Rules column, click the Rules icon to access the Location's rules:
 
[[Image:Editbutton.png]]
 
[[File:Localization_rules.png]]
 

'''Destination Rules''' – Changes Destination number.

'''CallerID Rules''' – Changes source number.

'''Combined Rules''' – Change Destination number and Source number. Please note that both Destination and Source cells must be matched to apply Combined Rules. Special symbols * and # do not work in combined rules.

'''Priority of rules that are applied first:'''
* 1) CallerID Rules
* 2) Combined Rules
* 3) Destination Rules

 
Note that if the match is found in "Combined Rules", "Destination Rules" are skipped entirely.

 
=== Removing or adding a prefix ===

To remove a prefix from the dialed number (destination), add a '''Destination Rule''': set '''Cut''' to the prefix you want to remove and '''Add''' to the replacement (if any). You do not need to change the call's owner.

 
To remove a prefix from the caller ID (source), use a '''CallerID Rule''' with '''Cut''' and '''Add''' in the same way.

 
The '''Change Call's owner''', '''Route to DID''', '''Change CallerID Name''', '''Change User LCR to this LCR''', and '''Change User Tariff to this Tariff''' fields are optional; use them only when you need that specific behaviour. They are not required to remove or add a prefix – only '''Cut''' and '''Add''' are needed for that.

 
=== Rule fields ===

The following settings should be explained for rules:

* '''Name''' – just for informational purposes.
* '''Cut''' – what prefix should be cut from the number.
* '''Add''' – what prefix should be added to the number.
* '''Min Len''' – the minimum length of the number to which the rule is being applied.
* '''Max Len''' – the maximum length of the number to which the rule is being applied.
* '''Change User Tariff to this Tariff''' – optional; which Tariff to apply when this rule is applied. Used in special cases, for example [[MOR - LCR/Tariff change based on call prefix | here]]. Leave empty in most cases; not required to remove or add a prefix.
* '''Change User LCR to this LCR''' – optional; which LCR to apply when this rule is applied. Used in special cases, for example [[MOR - LCR/Tariff change based on call prefix | here]]. Leave empty in most cases; not required to remove or add a prefix.
* '''Route to DID''' – optional; allows routing calls to DID according to localization rules. Not required to remove or add a prefix.
* '''Change CallerID Name''' – optional; changes the caller ID name when this rule is applied. Not required to remove or add a prefix.
* '''Change Call's owner''' – optional; changes the owner of the call depending on the incoming tech prefix. Use only when you need to route the call to a specific user; no prefix is required to remove or add.
* '''Enter edit mode''' - lets you change all rules at one time.

When you have entered all the necessary values (Cut or Add can be left empty), click [[Image:add.png]].

For example:
* The normal Lithuania MOB prefix is 3706.
* The user's device is located in Vilnius, Lithuania (displayed as "Lithuania Vilnius").
* By current Lithuanian regulations, the local customer can dial 9-digit numbers starting with 86 to reach Mobile subscribers.

To describe this situation, we create the following rule:

[[Image:localization_5_2.png]]

Rules can be enabled or disabled by clicking the [[Image:check.png]] icon or [[Image:cross.png]] in the '''Enabled?''' column.
* [[Image:edit.png]]- This icon allows you to edit the details of the rule.
* [[Image:cross.png]]- This icon allows you to delete the rule.

Now, in the main '''Localization''' window:

[[Image:localization6.png]]

click on [[Image:view.png]] in the '''Devices''' column to access '''Devices''' in Global '''Location''':

[[Image:localization7.png]]

Here, all Devices with a selected location are listed. Choose other locations for the selected Device and click on [[Image:check.png]] icon to activate this change. The device will be assigned to the selected Location.

[[Image:localization8.png]]

'''NOTE''': It's possible to change a device's Location in the Device settings ('''SETTINGS –> Users –> Devices''').

Now our device belongs to Location "Lithuania Vilnius". And if we dial a mobile number in the Lithuanian format, for example, 863042439, MOR cuts 86 (leaving 3042439) and adds 3706. The result is 37063042439, which is E.164 compatible and can be billed correctly by MOR.

'''NOTE''': Make sure that after localization, your number is always E.164 compatible. [[Call Tracing]] can help you do this.

'''NOTE''': You cannot delete a rule if it is assigned to a device.

 

= Special cases =

 
== Cut everything till Hash ==

With rule '''Cut: *#''' it is possible to cut everything till # (# included) in the dialed destination:

[[Image:Loc_cut_till_hash_2.png]]

For example:

* Dialed number: 1aaaaaaaaa#37063042439
* After Localization: 37063042439

Please note that if the dialed number is #37063042439, the call will not go through, because MOR rejects destinations with # in front of it.

This function can be used in fancy MNP (Mobile Number Portability) schemes and perhaps elsewhere.

 
NOTE: The '''Add''' value still can be used to add any value after '''Cut''' is used on the Destination.

 
== Cut any digits after a specific prefix ==

Works only with Destination and Combined rules.

Cut pattern accepts "x" which indicates any digit:

'''Cut: 12xxx''' 
will cut '''first 5 digits''' from the number which starts with digits "12".

If there are two rules like

'''Cut: 12xxx'''

'''Cut: 1234x'''

and a number

'''12345'''

then the rule '''Cut: 1234x''' will be selected because it matches most of the digits exactly.

Example1:

If we have a rule

'''Cut: 12xxx'''

'''Add: 99'''

Then all the following dialled numbers

1200012345

1257812345

1298712345

will be modified to

9912345

 

Example2:

If we have a rule
'''Cut: 123xxx78'''

'''Add: 78'''

Then all numbers starting from 12300078 till 12399978 will be localised to start with 78

 

== Change LCR/Tariff when CallerID is empty ==

 
This is an '''optional''' feature for special cases (e.g. applying a different LCR or Tariff when the caller ID is missing).

To change LCR/Tariff when CallerID is empty, set the following in Source Localization:

'''Cut: *''' 
'''Min Len: 0''' 
'''Max Len: 0''' 

and then choose the LCR/Tariff you want to set for calls without CallerID.

 

= Reseller localizations =
The reseller is not using the admin's global localization rules. Instead, he can now copy the rules and modify them to suit his needs. All newly created resellers have those global rules copied automatically from the admin. This feature can be disabled by the admin in [[Reseller_Settings|Reseller Settings]].
 
[[File:Copy_rules.png]]
 
'''IMPORTANT''': Fields "Change User Tariff to this Tariff" and "Change User LCR to this LCR" will not be copied.
 
"Default location" does not act as "Global location" on the reseller's account. Only the rules set in the device's settings will be applied.
 

= Route to DID =

 
This is an '''optional''' feature. Admin and Reseller PRO users can route calls to a DID according to localization rules.
 
[[File:Localization9.png]]
 
Start typing the DID number, and you will see all the DIDs that start with that number. If the DID you need is not there, enter more digits - only the first 20 DIDs starting with that number are shown.

 
= Change owner of call depending on incoming prefix =

 
This is an '''optional''' feature for routing the call to a specific user based on the incoming tech prefix.

It is now possible to change the call owner based on the incoming tech prefix.

* Open the localization menu to find the "Change Call's Owner" field.
[[File:localization8_5.png]]
 
* Enter the incoming prefix that needs to be cut in the "Cut" section.
* Afterwards, choose a user from the drop-down list and the device to which the call should be assigned.
[[File:Change_owner2.png]]
* This feature is also available for resellers.
* Admin can assign the call to ANY user on the system (even to those that do not belong to the admin).

 

= See also =

* [[MOR Number Manipulation]]
** [[MOR Device Rules]]
** [[MOR Provider Rules]]
** [[DID handling by Localization]]
** [[MOR Number Manipulation Examples]]
* [[Prelocalization]]
* [[Location Groups]]
* [http://www.wtng.info/wtng-reg.html World Telephone Numbering Guide]

Mobile Number Portability Addon

2026-03-04T11:50:52Z

Admin:

[http://en.wikipedia.org/wiki/Mobile_number_portability Mobile number portability (MNP)] enables mobile telephone users to retain their mobile telephone numbers when changing from one mobile network operator to another.

MNP Addon for MOR allows the system owner to check if the number belongs to another network and, if so, route it through different providers or bill it with a different price.

The current implementation allows saving numbers in a MySQL database on any server (not necessarily the local server).

Before each call, MOR MNP Addon checks the dialed number and, if it is found in the database, adds a prefix to it.

By prefixing MOR, you can set different routing (LCR) or billing (Tariff) for this number. [[MOR Localization | Localization rules]] should be used to perform these actions.

Detailed technique is described here: [[MOR - LCR/Tariff change based on call prefix]]

Kolmisoft cannot create a unique database for all MNP services across all countries worldwide. MOR admin has to

manually enter numbers in the MNP database (process described below) in order for this solution to work. 'mor_mnp' database has

to contain only the necessary data (telephone numbers).

 
= Installation =

Do such steps:

1. Update MOR scripts:
rm -fr /usr/src/mor
svn co http://svn.kolmisoft.com/mor/install_script/trunk/ /usr/src/mor
2. Run MNP installation script:
/usr/src/mor/sh_scripts/install_mnp.sh
3. Depending on MOR version: 

'''MOR X16 (or older)'''

Run the script, which will update Asterisk extlines to work with the MNP database:
/usr/src/mor/test/scripts/asterisk/mnp_cfgs.sh

'''MOR X17 (or later)'''

Starting from MOR X17, enable MNP in /etc/asterisk/mor.conf

mnp_enabled = 1
asterisk -rx "mor reload."

 
== How to see if MNP works ==

Open Asterisk CLI. During the call, check the very first lines shown in the CLI. In about the 10th line, you should be able to see lines like that:

'''MOR X16 (or older)'''

-- Launched AGI Script /var/lib/asterisk/agi-bin/mor_mnp
mor_mnp:
mor_mnp: MOR MNP AGI script started.
mor_mnp: Successfully connected to the database.
mor_mnp: Extension: 37012312345
mor_mnp: New extension: 37012312345
mor_mnp: MOR MNP AGI script stopped.
mor_mnp:

'''MOR X17 (or later)'''

In the call log, the following line should be visible:

[2023-01-17 15:32:03] NOTICE[10659][C-00000007]: app_mor_various.c:4088 _mor_log: Checking number 37012312345 in MNP database

Also, check the output of '''asterisk -rx "mor show status"''', you should see MNP status:

MNP enabled: 1, MNP active: 1

MNP enabled - shows if MOR core is aware of MNP existence. 
MNP active - shows if MOR core successfully connected to MNP database. 

If you cannot see it. Something is wrong with the configuration.

 

= Upgrade/Update =

After [[Upgrade_MOR_GUI |MOR Upgrade]] or Update run /usr/src/mor/test/scripts/asterisk/mnp_cfgs.sh
 

= Database =

Config to DB in: ''/usr/local/mor/mor_mnp.conf''

It should be a MySQL database mor_mnp:

DROP TABLE IF EXISTS `numbers`;
CREATE TABLE `numbers` (
`number` varchar(50) NOT NULL,
`prefix` varchar(20) NOT NULL,
PRIMARY KEY (`number`),
UNIQUE KEY `number` (`number`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

 

Make sure you have set the correct MySQL permissions for the mor_mnp database, and that local or remote Asterisk has the correct settings in /usr/local/mor/mor_mnp.conf. If your number is still not recognized, double-check if you have it in your mor_mnp database!

An example of how to set MySQL permissions:

GRANT REPLICATION SLAVE , REPLICATION CLIENT ON * . * TO 'mor'@'localhost' IDENTIFIED BY 'mor' WITH MAX_QUERIES_PER_HOUR 0
MAX_CONNECTIONS_PER_HOUR 0 MAX_UPDATES_PER_HOUR 0 MAX_USER_CONNECTIONS 0 ;

GRANT ALL PRIVILEGES ON `mor_mnp` . * TO 'mor'@'localhost' WITH GRANT OPTION ;
 
= How to use MNP =

You need to insert two values in mor_mnp database. These values are a number and a prefix.
 
To manage the mor_mnp database, you can use PhpMyAdmin:

<nowiki>http://<your server IP>/mordbadmin</nowiki>

PhpMyAdmin login details can be found in the file /root/phpMyAdminPassword
 
If after logging in to PhpMyAdmin, the MySQL login page will appear, use these details to log in to MySQL:

username: mor

password: mor
 
Now click "_mnp (1)" menu item on the left to select mor_mnp database.

"numbers" menu item will appear after that.

Click on the "numbers" menu item to manage the number table.

Now, click on the "Insert" tab at the top of the page.

The field number and prefix will appear.

Enter desired values and click "Go" to insert these values.

Done!
 

 
= Number localization =

In situations when a number can be dialed in multiple ways, you can set '''mnp_prefixes''' variable in '''/usr/local/mor/mor_mnp.conf'''. 

For example, if number 123456789 can be dialed with the following prefixes '''00370'''123456789, '''370'''123456789, '''8'''123456789, then you can set '''mnp_prefixes''' variable with the following prefixes:

mnp_prefixes = 00370,370,8

Then you will be able to upload only a single number 123456789 into the MNP database, and this number will be matched when the client dials '''00370'''123456789, '''370'''123456789 or '''8'''123456789.

 
= MNP tags in SIP INVITE =

MNP tags (npdi and rn) can be enabled by setting '''Enable MNP tags''' to '''yes''' in Provider configuration. 

If MNP tags are enabled and MNP lookup was successful, then npdi and rn tags will be added to SIP INVITE:

INVITE sip:DST_NUMBER;npdi;rn=MNP_NUMBER@IP SIP/2.0

here:

* DST_NUMBER - localized destination number, for example, +370123456789
* MNP_NUMBER - localized destination number with MNP prefix, for example +370'''999'''123456789

If the number is not found in the MNP database, then only the npdi tag will be added to SIP INVITE:

INVITE sip:DST_NUMBER;npdi@IP SIP/2.0

here:

* DST_NUMBER - localized destination number, for example, +370123456

'''Note''' that only SIP INVITE requests will be modified. Other SIP headers (such as TO, FROM) are not affected by '''Enable MNP tags''' setting.

 
= How to import numbers from CSV =

There is no such option to import numbers from CSV in the MOR GUI, but numbers can be imported directly to the MNP database.

This procedure is described here:

1. You need to have a CSV file on your server, and the file should look like this:

...
37012312345;9991
37012312344;9991
37112312343;9992
37112354321;9992
...

2. Open MySQL CLI:

mysql mor_mnp

3. Create a temporary table and import a CSV file into it:

CREATE TABLE temp (col_1 VARCHAR(50) default NULL , col_2 VARCHAR(20) default NULL);

LOAD DATA LOCAL INFILE '/home/mnpnumbers.csv' IGNORE INTO TABLE temp FIELDS TERMINATED BY ';' ;

4. Copy data from the temporary table to 'numbers' table:

<nowiki>INSERT INTO numbers (number,prefix) SELECT TRIM(REPLACE(col_1, '\r', '')), TRIM(REPLACE(col_2, '\r', '')) FROM temp
WHERE ( TRIM(REPLACE(col_1, '\r', '')) REGEXP '^[0-9]+$' = 1) and (TRIM(REPLACE(col_2, '\r', '')) REGEXP '^[0-9]+$' = 1) ;</nowiki>

NOTE: This query skips values that contain non-numeric characters.

For example row

...
+370123123456;9997
...

will not be imported to 'numbers' table.

5. Delete temporary table:

DROP TABLE temp;

Done. Numbers are imported to 'numbers' table.
 

== Automatic import script ==

Script downloads compressed (ZIP) CSV with a list of numbers from the SFTP server and imports in with default prefix to the MNP database. Current ZIP file required. Only SFTP is supported. The script does not import prefixes from CSV. CSV should contain an only list of numbers.

The script is located in /usr/src/mor/sh_scripts/mnp_numbers_import.sh

Script uses the same configuration file /usr/local/mor/mor_mnp.conf. Options which are specific to this script:

download_url = sftp.server.com:/path/to/file.zip #some remote location of a number file (for sftp)
username = ftpuser #user name to connect to a remote server
password = ftppassword #password for a user to connect to a remote server
default_prefix = 0009 #default prefix for numbers (current version does not support prefix import)

'''Note:''' 
If you are using the MOR X18+ version on Rocky Linux 9 and an FTP server on an older operating system, then these errors can occur using the script:
Unable to negotiate with xxx.xxx.xxx.xxx port 22: no matching host key type found. Their offer: ssh-rsa,ssh-dss

ssh_dispatch_run_fatal: Connection to xxx.xxx.xxx.xxx port 22: error in libcrypto

The best way is to upgrade the FTP server to a new operating system. If you do not want to upgrade your FTP server, then you can use another option to run this command on the MOR Rocky Linux 9 server:
update-crypto-policies --set DEFAULT:SHA1

 

= How to configure external MNP database =

Skip this step if your MOR billing installation is on one server. 

Locate mor_mnp.conf file 

cd /usr/local/mor 

Edit the file with your favorite text editor, for example: 

mcedit mor_mnp.conf 

You should see similar values, '''mind the gaps in the file, they should be exactly the same as in the example below''': 

host = localhost
db = mor_mnp
user = mor
secret = mor
port = 3306
server_id = 1
show_sql = 0
debug = 1
mnp_prefixes = 00370,370,8

Change the values to the ones you need: 

host - your database IP address 
server_id - your Asterisk server id, same as in /etc/asterisk/mor.conf
 

= How can I add a specific prefix on a call to the ported number? =

It's possible to add a specific prefix to the call in this way:
* Create a duplicated provider (for example, you have "Provider A (no MNP) and "Provider A (with MNP)")
* Create [[MOR Provider Rules | Provider Rules]] for that provider by adding a prefix 060
* MOR will route numbers in the MNP database through that provider according to the [[MOR Provider Rules | Provider Rules]].

 

=See also=
* [[MOR Addons]]
* [http://en.wikipedia.org/wiki/Least-cost_routing#Impact_of_mobile-number_portability_in_VOIP_and_LCR_environments Impact of MNP in VOIP and LCR environments]

LCR make tariff

2026-03-04T11:50:41Z

Admin:

=About=
This feature allows you to make tariff from LCR. Tariff is exported to CSV file and contains both MIN and MAX rates
 
==How to make Tariff from LCR?==

1. Go to '''SETTINGS - Billing -> LCR''':
 
[[File:Lcr_path.png]]
 
2. Click on of the [[Image:excel.png]] icon to generate the tariff
 
[[File:lcr_main.png]]
 
3. You will get a file to download. Inside there will be text like this:
Afghanistan,Afghanistan proper,93,FIX,1,2
Albania,Albania proper,355,FIX,3,4
Algeria,Algeria proper,213,FIX,4,5
American Samoa,American Samoa proper,1684,FIX,1,2
Andorra,Andorra proper,376,FIX,1,1
Angola,Angola proper,244,FIX,2,2
Anguilla,Anguilla proper,1264,FIX,3,5
Antarctica,,672,FIX,1,3

Let's take the first line:

Afghanistan,Afghanistan proper,93,FIX,1,2

1 will be MIN rate, 2 will be MAX rate

Notice: Exported file contains both MIN and MAX rates.
 
= Zero Rates =

By default zero rates (rate = 0.0) are not included in the output file.

It can be changed by checking '''Show zero rates in LCR tariff export''', in '''SETTINGS - Functionality - Tariffs/Rates''':
 
[[File:lcrtariffzerorates.png]]
 
=See also=

* [[LCR Logic]]
* [[How to add Provider to LCR]]
* [[Call Routing by priority (Manual LCR)]]
* [[Call routing per destination basis]]
* [[MOR - LCR/Tariff change based on call prefix]]
* [[Routing by Percent]] or Weight-based routing
* [[Why call was not routed through other provider/trunk?|Why was a call not routed through another provider/trunk?]]