Kolmisoft Wiki - User contributions [en]

MOR Block and Hide Devices

2017-10-11T06:29:35Z

Reda: moved Hide Devices to Block and Hide Devices

MOR does not allow to delete Devices that have Calls, instead you may block and hide Device. This feature is also useful if you want to disable Device temporarily. Blocked and hidden Devices cannot make or receive Calls.

==How to block and hide Device==

Change setting '''Block and Hide Device''' in Device configuration:

[[File:Mor_hide_device_general.png]]

When set to '''yes''', Device will be blocked and hidden and will not be able to make or receive Calls. 

Alternatively you can click Block/Unblock and Hide/Unhide icon in Device list:

[[File:Mor_hide_device_user_list.png]]

Blocked and hidden Device will not be displayed in Device List and you will not be able to select this Device in various Device dropdowns throughout MOR.

==Where to find blocked and hidden Devices==

Go to '''SETTINGS''' –> '''Users''' –> '''Devices''' -> '''Blocked Devices'''

[[File:Mor_hide_device_menu.png]]

Here you will be able to see a list of blocked and hidden Devices:

[[File:Mor_hide_device_list.png]]

==How to unblock and unhide Device==

To unblock and unhide Device, go to Blocked Devices page '''SETTINGS''' –> '''Users''' –> '''Devices''' -> '''Blocked Devices''' and you may click Block/Unblock and Hide/Unhide icon or go to Device configuration and set
'''Block and Hide Device: No''' 

Unblocked and unhidden Device will become active and will be able to make and receive Calls.

==Permissions to block and hide Device==

* Accountants are able to block/unblock and hide/unhide Devices with a '''Manage Devices''' Permission. 
* If an Accountat has a '''Manage Users''' Permission disabled, but the '''Manage Devices''' Permission is on, the Blocked Devices list is reachable via direct link '''/billing/devices/hidden_devices'''.
* Resellers may block/unblock and hide/unhide Devices without any Permission. 
* Users are not able to block/unblock and hide/unhide Devices.

MOR Block and Hide Devices

2017-10-09T12:40:49Z

Reda:

MOR Block and Hide Devices

2017-10-09T12:39:58Z

Reda: /* Permissions to Block and Hide Device */

MOR does not allow to delete Devices that have Calls, instead you may hide Device. This feature is also useful if you want to disable Device temporarily. Hidden Devices cannot make or receive Calls.

==How to block and hide Device==

Change setting '''Block and Hide Device''' in Device configuration:

[[File:Mor_hide_device_general.png]]

When set to '''yes''', Device will be blocked and hidden and will not be able to make or receive Calls. 

Alternatively you can click Block/Unblock and Hide/Unhide icon in Device list:

[[File:Mor_hide_device_user_list.png]]

Blocked and hidden Device will not be displayed in Device List and you will not be able to select this Device in various Device dropdowns throughout MOR.

==Where to find blocked and hidden Devices==

Go to '''SETTINGS''' –> '''Users''' –> '''Devices''' -> '''Blocked Devices'''

[[File:Mor_hide_device_menu.png]]

Here you will be able to see a list of blocked and hidden Devices:

[[File:Mor_hide_device_list.png]]

==How to unblock and unhide Device==

To unblock and unhide Device, go to Blocked Devices page '''SETTINGS''' –> '''Users''' –> '''Devices''' -> '''Blocked Devices''' and you may click Block/Unblock and Hide/Unhide icon or go to Device configuration and set
'''Block and Hide Device: No''' 

Unblocked and unhidden Device will become active and will be able to make and receive Calls.

==Permissions to block and hide Device==

* Accountants are able to block/unblock and hide/unhide Devices with a '''Manage Devices''' Permission. 
* If an Accountat has a '''Manage Users''' Permission disabled, but the '''Manage Devices''' Permission is on, the Blocked Devices list is reachable via direct link '''/billing/devices/hidden_devices'''.
* Resellers may block/unblock and hide/unhide Devices without any Permission. 
* Users are not able to block/unblock and hide/unhide Devices.

MOR Block and Hide Devices

2017-10-09T12:39:32Z

Reda: /* Where to find hidden Devices */

MOR does not allow to delete Devices that have Calls, instead you may hide Device. This feature is also useful if you want to disable Device temporarily. Hidden Devices cannot make or receive Calls.

==How to block and hide Device==

Change setting '''Block and Hide Device''' in Device configuration:

[[File:Mor_hide_device_general.png]]

When set to '''yes''', Device will be blocked and hidden and will not be able to make or receive Calls. 

Alternatively you can click Block/Unblock and Hide/Unhide icon in Device list:

[[File:Mor_hide_device_user_list.png]]

Blocked and hidden Device will not be displayed in Device List and you will not be able to select this Device in various Device dropdowns throughout MOR.

==Where to find blocked and hidden Devices==

Go to '''SETTINGS''' –> '''Users''' –> '''Devices''' -> '''Blocked Devices'''

[[File:Mor_hide_device_menu.png]]

Here you will be able to see a list of blocked and hidden Devices:

[[File:Mor_hide_device_list.png]]

==How to unblock and unhide Device==

To unblock and unhide Device, go to Blocked Devices page '''SETTINGS''' –> '''Users''' –> '''Devices''' -> '''Blocked Devices''' and you may click Block/Unblock and Hide/Unhide icon or go to Device configuration and set
'''Block and Hide Device: No''' 

Unblocked and unhidden Device will become active and will be able to make and receive Calls.

==Permissions to Block and Hide Device==

* Accountants are able to block/unblock and hide/unhide Devices with a '''Manage Devices''' Permission. 
* If an Accountat has a '''Manage Users''' Permission disabled, but the '''Manage Devices''' Permission is on, the Blocked Devices list is reachable via direct link '''/billing/devices/hidden_devices'''.
* Resellers may block/unblock and hide/unhide Devices without any Permission. 
* Users are not able to block/unblock and hide/unhide Devices.

MOR Block and Hide Devices

2017-10-09T12:39:07Z

Reda: /* How to hide Device */

MOR does not allow to delete Devices that have Calls, instead you may hide Device. This feature is also useful if you want to disable Device temporarily. Hidden Devices cannot make or receive Calls.

==How to block and hide Device==

Change setting '''Block and Hide Device''' in Device configuration:

[[File:Mor_hide_device_general.png]]

When set to '''yes''', Device will be blocked and hidden and will not be able to make or receive Calls. 

Alternatively you can click Block/Unblock and Hide/Unhide icon in Device list:

[[File:Mor_hide_device_user_list.png]]

Blocked and hidden Device will not be displayed in Device List and you will not be able to select this Device in various Device dropdowns throughout MOR.

==Where to find hidden Devices==

Go to '''SETTINGS''' –> '''Users''' –> '''Devices''' -> '''Blocked Devices'''

[[File:Mor_hide_device_menu.png]]

Here you will be able to see a list of blocked and hidden Devices:

[[File:Mor_hide_device_list.png]]

==How to unblock and unhide Device==

To unblock and unhide Device, go to Blocked Devices page '''SETTINGS''' –> '''Users''' –> '''Devices''' -> '''Blocked Devices''' and you may click Block/Unblock and Hide/Unhide icon or go to Device configuration and set
'''Block and Hide Device: No''' 

Unblocked and unhidden Device will become active and will be able to make and receive Calls.

==Permissions to Block and Hide Device==

* Accountants are able to block/unblock and hide/unhide Devices with a '''Manage Devices''' Permission. 
* If an Accountat has a '''Manage Users''' Permission disabled, but the '''Manage Devices''' Permission is on, the Blocked Devices list is reachable via direct link '''/billing/devices/hidden_devices'''.
* Resellers may block/unblock and hide/unhide Devices without any Permission. 
* Users are not able to block/unblock and hide/unhide Devices.

MOR Block and Hide Devices

2017-10-09T12:37:44Z

Reda: /* How to unblock and unhide Device */

MOR does not allow to delete Devices that have Calls, instead you may hide Device. This feature is also useful if you want to disable Device temporarily. Hidden Devices cannot make or receive Calls.

==How to hide Device==

Change setting '''Hide Device''' in Device configuration:

[[File:Mor_hide_device_general.png]]

When set to '''yes''', Device will be hidden and will not be able to make or receive Calls. 

Alternatively you can click Hide/Unhide icon in Device list:

[[File:Mor_hide_device_user_list.png]]

Hidden Device will not be displayed in Device List and you will not be able to select this Device in various Device dropdowns throughout MOR.

==Where to find hidden Devices==

Go to '''SETTINGS''' –> '''Users''' –> '''Devices''' -> '''Blocked Devices'''

[[File:Mor_hide_device_menu.png]]

Here you will be able to see a list of blocked and hidden Devices:

[[File:Mor_hide_device_list.png]]

==How to unblock and unhide Device==

To unblock and unhide Device, go to Blocked Devices page '''SETTINGS''' –> '''Users''' –> '''Devices''' -> '''Blocked Devices''' and you may click Block/Unblock and Hide/Unhide icon or go to Device configuration and set
'''Block and Hide Device: No''' 

Unblocked and unhidden Device will become active and will be able to make and receive Calls.

==Permissions to Block and Hide Device==

* Accountants are able to block/unblock and hide/unhide Devices with a '''Manage Devices''' Permission. 
* If an Accountat has a '''Manage Users''' Permission disabled, but the '''Manage Devices''' Permission is on, the Blocked Devices list is reachable via direct link '''/billing/devices/hidden_devices'''.
* Resellers may block/unblock and hide/unhide Devices without any Permission. 
* Users are not able to block/unblock and hide/unhide Devices.

MOR Block and Hide Devices

2017-10-09T12:37:27Z

Reda: /* Where to find hidden Devices */

MOR does not allow to delete Devices that have Calls, instead you may hide Device. This feature is also useful if you want to disable Device temporarily. Hidden Devices cannot make or receive Calls.

==How to hide Device==

Change setting '''Hide Device''' in Device configuration:

[[File:Mor_hide_device_general.png]]

When set to '''yes''', Device will be hidden and will not be able to make or receive Calls. 

Alternatively you can click Hide/Unhide icon in Device list:

[[File:Mor_hide_device_user_list.png]]

Hidden Device will not be displayed in Device List and you will not be able to select this Device in various Device dropdowns throughout MOR.

==Where to find hidden Devices==

Go to '''SETTINGS''' –> '''Users''' –> '''Devices''' -> '''Blocked Devices'''

[[File:Mor_hide_device_menu.png]]

Here you will be able to see a list of blocked and hidden Devices:

[[File:Mor_hide_device_list.png]]

==How to unblock and unhide Device==

To unblock and unhide Device, go to Blocked Devices page '''SETTINGS''' –> '''Users''' –> '''Devices''' -> '''Blocked Devices''' and you may click Block/Unblock and Hide/Unhide icon or go to Device configuration and set
'''Block and Hide Device: No''' 

Unblocked and Unhidden Device will become active and will be able to make and receive Calls.

==Permissions to Block and Hide Device==

* Accountants are able to block/unblock and hide/unhide Devices with a '''Manage Devices''' Permission. 
* If an Accountat has a '''Manage Users''' Permission disabled, but the '''Manage Devices''' Permission is on, the Blocked Devices list is reachable via direct link '''/billing/devices/hidden_devices'''.
* Resellers may block/unblock and hide/unhide Devices without any Permission. 
* Users are not able to block/unblock and hide/unhide Devices.

MOR Block and Hide Devices

2017-10-09T12:36:58Z

Reda: /* Where to find hidden Devices */

MOR does not allow to delete Devices that have Calls, instead you may hide Device. This feature is also useful if you want to disable Device temporarily. Hidden Devices cannot make or receive Calls.

==How to hide Device==

Change setting '''Hide Device''' in Device configuration:

[[File:Mor_hide_device_general.png]]

When set to '''yes''', Device will be hidden and will not be able to make or receive Calls. 

Alternatively you can click Hide/Unhide icon in Device list:

[[File:Mor_hide_device_user_list.png]]

Hidden Device will not be displayed in Device List and you will not be able to select this Device in various Device dropdowns throughout MOR.

==Where to find hidden Devices==

Go to '''SETTINGS''' –> '''Users''' –> '''Devices''' -> '''Blocked Devices'''

[[File:Mor_hide_device_menu.png]]

Here you will be able to see a list of hidden Devices:

[[File:Mor_hide_device_list.png]]

==How to unblock and unhide Device==

To unblock and unhide Device, go to Blocked Devices page '''SETTINGS''' –> '''Users''' –> '''Devices''' -> '''Blocked Devices''' and you may click Block/Unblock and Hide/Unhide icon or go to Device configuration and set
'''Block and Hide Device: No''' 

Unblocked and Unhidden Device will become active and will be able to make and receive Calls.

==Permissions to Block and Hide Device==

* Accountants are able to block/unblock and hide/unhide Devices with a '''Manage Devices''' Permission. 
* If an Accountat has a '''Manage Users''' Permission disabled, but the '''Manage Devices''' Permission is on, the Blocked Devices list is reachable via direct link '''/billing/devices/hidden_devices'''.
* Resellers may block/unblock and hide/unhide Devices without any Permission. 
* Users are not able to block/unblock and hide/unhide Devices.

MOR Block and Hide Devices

2017-10-09T12:36:26Z

Reda: /* How to unhide Device */

MOR does not allow to delete Devices that have Calls, instead you may hide Device. This feature is also useful if you want to disable Device temporarily. Hidden Devices cannot make or receive Calls.

==How to hide Device==

Change setting '''Hide Device''' in Device configuration:

[[File:Mor_hide_device_general.png]]

When set to '''yes''', Device will be hidden and will not be able to make or receive Calls. 

Alternatively you can click Hide/Unhide icon in Device list:

[[File:Mor_hide_device_user_list.png]]

Hidden Device will not be displayed in Device List and you will not be able to select this Device in various Device dropdowns throughout MOR.

==Where to find hidden Devices==

Go to '''SETTINGS''' –> '''Users''' –> '''Devices''' -> '''Hidden Devices'''

[[File:Mor_hide_device_menu.png]]

Here you will be able to see a list of hidden Devices:

[[File:Mor_hide_device_list.png]]

==How to unblock and unhide Device==

To unblock and unhide Device, go to Blocked Devices page '''SETTINGS''' –> '''Users''' –> '''Devices''' -> '''Blocked Devices''' and you may click Block/Unblock and Hide/Unhide icon or go to Device configuration and set
'''Block and Hide Device: No''' 

Unblocked and Unhidden Device will become active and will be able to make and receive Calls.

==Permissions to Block and Hide Device==

* Accountants are able to block/unblock and hide/unhide Devices with a '''Manage Devices''' Permission. 
* If an Accountat has a '''Manage Users''' Permission disabled, but the '''Manage Devices''' Permission is on, the Blocked Devices list is reachable via direct link '''/billing/devices/hidden_devices'''.
* Resellers may block/unblock and hide/unhide Devices without any Permission. 
* Users are not able to block/unblock and hide/unhide Devices.

MOR Block and Hide Devices

2017-10-09T12:34:27Z

Reda: /* Permissions to Hide Device */

MOR does not allow to delete Devices that have Calls, instead you may hide Device. This feature is also useful if you want to disable Device temporarily. Hidden Devices cannot make or receive Calls.

==How to hide Device==

Change setting '''Hide Device''' in Device configuration:

[[File:Mor_hide_device_general.png]]

When set to '''yes''', Device will be hidden and will not be able to make or receive Calls. 

Alternatively you can click Hide/Unhide icon in Device list:

[[File:Mor_hide_device_user_list.png]]

Hidden Device will not be displayed in Device List and you will not be able to select this Device in various Device dropdowns throughout MOR.

==Where to find hidden Devices==

Go to '''SETTINGS''' –> '''Users''' –> '''Devices''' -> '''Hidden Devices'''

[[File:Mor_hide_device_menu.png]]

Here you will be able to see a list of hidden Devices:

[[File:Mor_hide_device_list.png]]

==How to unhide Device==

To unhide Device, go to Hidden Devices page '''SETTINGS''' –> '''Users''' –> '''Devices''' -> '''Hidden Devices''' and you may click Hide/Unhide icon or go to Device configuration and set '''Hide Device: No''' 

Unhidden Device will become active and will be able to make and receive Calls.

==Permissions to Block and Hide Device==

* Accountants are able to block/unblock and hide/unhide Devices with a '''Manage Devices''' Permission. 
* If an Accountat has a '''Manage Users''' Permission disabled, but the '''Manage Devices''' Permission is on, the Blocked Devices list is reachable via direct link '''/billing/devices/hidden_devices'''.
* Resellers may block/unblock and hide/unhide Devices without any Permission. 
* Users are not able to block/unblock and hide/unhide Devices.

File:Mor hide device list.png

2017-10-09T12:32:39Z

Reda: uploaded a new version of "File:Mor hide device list.png"

File:Mor hide device list.png

2017-10-09T12:31:47Z

Reda: uploaded a new version of "File:Mor hide device list.png"

File:Mor hide device menu.png

2017-10-09T12:30:26Z

Reda: uploaded a new version of "File:Mor hide device menu.png"

File:Mor hide device menu.png

2017-10-09T12:28:56Z

Reda: uploaded a new version of "File:Mor hide device menu.png"

File:Mor hide device user list.png

2017-10-09T12:27:59Z

Reda: uploaded a new version of "File:Mor hide device user list.png"

File:Mor hide device general.png

2017-10-09T12:22:10Z

Reda: uploaded a new version of "File:Mor hide device general.png"

Device groups

2017-10-03T09:00:45Z

Reda:

It is possible to group devices. This feature is intended for branches of a company, so that each device will belong to a single company group.

This functionality is not widely used and we do not recommend using it unless you really need it.

'''Note''' that Accountant can use this functionality with Manage Devices and Manage Users permissions.

To access groups for each user in the Users window, click [[Image:icon_device_groups.png]] '''Dev.Groups''':
 
[[Image:device_groups.png]]
 
In this window you see all device groups for the selected user. Under each group, you see devices assigned to the group.

Once new groups are added, they can be deleted. However, the primary group cannot be deleted.

[[Image:icon_edit.png]] '''Edit Details''' – lets you change group name and address.
 
=See also=

* [[Device settings]]

Call Tracing

2017-10-03T08:58:49Z

Reda: /* MOR Call Tracing Overview */

<mkmeta>How to trace MOR Call</mkmeta>
= MOR Call Tracing Overview =

This function is for checking the setup of MOR in order to be sure a User will be able to dial out. To set MOR up isn't simple, but we are trying to make it easier with this manual and with improvements to GUI. It often happens that Users miss some important detail while trying to make everything work. Call Tracing will save a lot of head-scratching, and we hope it will be helpful for beginners.

This function can be found in '''SETTINGS –> Billing –> Function –> Call Tracing'''. It can be quickly accessed in the Users menu (SETTINGS –> Users) as well. Just click on the [[Image:icon_call_tracing.png]] icon for a User.

'''NOTE''' that Accountant can use this functionality with Call Tracing Usage permission.

In the first window, we have to select which User we want to check:
 
[[Image:calltracing1.png]]
 

= User testing =

The next window shows us whether we have configured everything properly for the selected User. Let's look at each section separately.

The first section shows information special to the User:
 
[[Image:calltracing2.png]]
 

Here we see three errors [[Image:icon_cross.png]] that prevent the User from operating. Let's say we want to allow a User to make Calls. We will go through each of the errors and fix them.

1. This error tells us that the User is Blocked and so unable to make Calls. We should go to [[User Details]] and unblock him.

2. Balance and Credit for this User are empty, and the User type is Prepaid. That means he has no funds to cover the Call fees. There are several ways to go about fixing this:

* If the User is postpaid, he should use some Payment method to increase his Balance. [[PayPal]] and [[Payments | Manual Payment]], among others, are good ways to do this.
* We can change the User type to Postpaid and then we should adjust his Credit. Maybe it is unlimited, maybe some limit exists. But this will allow the User to dial out.

3. The User has no Devices. A Device is necessary in order to dial out. Just create one for this User.

'''Note:''' We also see that the User has an empty Tariff assigned. That is the reason why the User will not be able to dial out. In addition, the User can dial out only to those destinations which have Rates. Currently none of them has. You need to add some Rates to the existing Tariff or assign a non-empty Tariff to this User.

After solving all these issues, we should see:
 
[[Image:calltracing3.png]]
 

= Device testing =

The following section lets us choose a Device, Source, Server, Destination and a Call Time we want to test. For example:
 
[[Image:Calltracing3.png]]
 
This data means that we are testing a virtual Call from an IP authenticated SIP Device to a number 37061111111 on 2017 September 5th 09:30.

When we click '''Trace Call''', we will go to the next page and we will see something like:
 
[[Image:New_mor_call_tracing.png]]
 
Call Tracing Log will show self explanatory warnings, errors (in red colored text), other messages, and an informative summary.
 

=From Accountant=

Accountant must have '''Call tracing usage''' permission in [[Accountant_permissions | Accountant permissions group]] to use this functionality.

Call Tracing

2017-10-03T08:48:15Z

Reda: /* MOR Call Tracing Overview */

<mkmeta>How to trace MOR Call</mkmeta>
= MOR Call Tracing Overview =

This function is for checking the setup of MOR in order to be sure a User will be able to dial out. To set MOR up isn't simple, but we are trying to make it easier with this manual and with improvements to GUI. It often happens that Users miss some important detail while trying to make everything work. Call Tracing will save a lot of head-scratching, and we hope it will be helpful for beginners.

This function can be found in '''SETTINGS –> Billing –> Function –> Call Tracing'''. It can be quickly accessed in the Users menu (SETTINGS –> Users) as well. Just click on the [[Image:icon_call_tracing.png]] icon for a User.

'''NOTE''' that accountant can use this functionality with Call Tracing Usage permission.

In the first window, we have to select which User we want to check:
 
[[Image:calltracing1.png]]
 

= User testing =

The next window shows us whether we have configured everything properly for the selected User. Let's look at each section separately.

The first section shows information special to the User:
 
[[Image:calltracing2.png]]
 

Here we see three errors [[Image:icon_cross.png]] that prevent the User from operating. Let's say we want to allow a User to make Calls. We will go through each of the errors and fix them.

1. This error tells us that the User is Blocked and so unable to make Calls. We should go to [[User Details]] and unblock him.

2. Balance and Credit for this User are empty, and the User type is Prepaid. That means he has no funds to cover the Call fees. There are several ways to go about fixing this:

* If the User is postpaid, he should use some Payment method to increase his Balance. [[PayPal]] and [[Payments | Manual Payment]], among others, are good ways to do this.
* We can change the User type to Postpaid and then we should adjust his Credit. Maybe it is unlimited, maybe some limit exists. But this will allow the User to dial out.

3. The User has no Devices. A Device is necessary in order to dial out. Just create one for this User.

'''Note:''' We also see that the User has an empty Tariff assigned. That is the reason why the User will not be able to dial out. In addition, the User can dial out only to those destinations which have Rates. Currently none of them has. You need to add some Rates to the existing Tariff or assign a non-empty Tariff to this User.

After solving all these issues, we should see:
 
[[Image:calltracing3.png]]
 

= Device testing =

The following section lets us choose a Device, Source, Server, Destination and a Call Time we want to test. For example:
 
[[Image:Calltracing3.png]]
 
This data means that we are testing a virtual Call from an IP authenticated SIP Device to a number 37061111111 on 2017 September 5th 09:30.

When we click '''Trace Call''', we will go to the next page and we will see something like:
 
[[Image:New_mor_call_tracing.png]]
 
Call Tracing Log will show self explanatory warnings, errors (in red colored text), other messages, and an informative summary.
 

=From Accountant=

Accountant must have '''Call tracing usage''' permission in [[Accountant_permissions | Accountant permissions group]] to use this functionality.

Call Tracing

2017-10-03T08:47:57Z

Reda: /* MOR Call Tracing Overview */

<mkmeta>How to trace MOR Call</mkmeta>
= MOR Call Tracing Overview =

This function is for checking the setup of MOR in order to be sure a User will be able to dial out. To set MOR up isn't simple, but we are trying to make it easier with this manual and with improvements to GUI. It often happens that Users miss some important detail while trying to make everything work. Call Tracing will save a lot of head-scratching, and we hope it will be helpful for beginners.

This function can be found in '''SETTINGS –> Billing –> Function –> Call Tracing'''. It can be quickly accessed in the Users menu (SETTINGS –> Users) as well. Just click on the [[Image:icon_call_tracing.png]] icon for a User.
'''NOTE''' that accountant can use this functionality with Call Tracing Usage permission.

In the first window, we have to select which User we want to check:
 
[[Image:calltracing1.png]]
 

= User testing =

The next window shows us whether we have configured everything properly for the selected User. Let's look at each section separately.

The first section shows information special to the User:
 
[[Image:calltracing2.png]]
 

Here we see three errors [[Image:icon_cross.png]] that prevent the User from operating. Let's say we want to allow a User to make Calls. We will go through each of the errors and fix them.

1. This error tells us that the User is Blocked and so unable to make Calls. We should go to [[User Details]] and unblock him.

2. Balance and Credit for this User are empty, and the User type is Prepaid. That means he has no funds to cover the Call fees. There are several ways to go about fixing this:

* If the User is postpaid, he should use some Payment method to increase his Balance. [[PayPal]] and [[Payments | Manual Payment]], among others, are good ways to do this.
* We can change the User type to Postpaid and then we should adjust his Credit. Maybe it is unlimited, maybe some limit exists. But this will allow the User to dial out.

3. The User has no Devices. A Device is necessary in order to dial out. Just create one for this User.

'''Note:''' We also see that the User has an empty Tariff assigned. That is the reason why the User will not be able to dial out. In addition, the User can dial out only to those destinations which have Rates. Currently none of them has. You need to add some Rates to the existing Tariff or assign a non-empty Tariff to this User.

After solving all these issues, we should see:
 
[[Image:calltracing3.png]]
 

= Device testing =

The following section lets us choose a Device, Source, Server, Destination and a Call Time we want to test. For example:
 
[[Image:Calltracing3.png]]
 
This data means that we are testing a virtual Call from an IP authenticated SIP Device to a number 37061111111 on 2017 September 5th 09:30.

When we click '''Trace Call''', we will go to the next page and we will see something like:
 
[[Image:New_mor_call_tracing.png]]
 
Call Tracing Log will show self explanatory warnings, errors (in red colored text), other messages, and an informative summary.
 

=From Accountant=

Accountant must have '''Call tracing usage''' permission in [[Accountant_permissions | Accountant permissions group]] to use this functionality.

MOR API card from group sell

2017-09-18T13:55:19Z

Reda: /* Parametres */

=Description=

[[MOR API]] sells Cards from Calling Card Group
 
=Usage=

* From '''MOR X4''' call: '''/api/card_from_group_sell'''
* For Backwards-compatibility old name 'buy_card_from_callingroup' is also usable. Call: '''/api/buy_card_from_callingroup'''
* Methods: POST, GET(if allowed, not recomended)
 
===Parametres===

Parameters which are '''included''' into hash:

* email - email address, to send information about bought card '''Optional'''.
* id - Calling Card Group ID in MOR database. '''Required'''.
* quantity - default 1. '''Optional'''.

'''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 parameters above and API_Secret_Key ([[MOR API hash construction | More described in Constructing hash]]). '''Required'''.
* u - username for authentication. '''Required'''.
* number - parameter that indicates which card is sold. If number parameter is send, then quantity parameter will be ignored. '''Optional'''.
* curr - parameter that lets change the currency of cards payment. Default currency is system currency. '''Optional'''.
 

===Request===

We have id = 6, quantity = 2, API Secret Key = 456789

We send:
HTML POST: http://<SERVER_IP>/billing/api/buy_card_from_callingroup?u=username&id=6&quantity=2&hash=37086d860581fabc278413cd1a417d5c079f6eba

'''NOTE that username are not included in hash'''
 
===Returns===

'''Success'''

<?xml version="1.0" encoding="UTF-8"?>
<page>
<cards>
<card>
<pin>...</pin>
<number>..</number>
<balance_without_vat>...</balance_without_vat>
<currency>...</currency>
</card>
<card>
<pin>...</pin>
<number>...</number>
<balance_without_vat>...</balance_without_vat>
<currency>...</currency>
</card>
</cards>
</page>
 
----

'''Errors'''

* <error>Bad login</error> - User supplied bad login or password.
* <error>Incorrect hash</error> - Hash was not correct. Check API_Secret_Key and order or params while concatenating hash_string.
* <error>Cardgroup was not found</error> - Use correct Calling Card Group ID .
* <error>Free cards was not found</error> - no free cards in Calling Card Group.
* <error>Card is already sold</error> - This card is already sold.

 

=See also=

* [[MOR API]]

MOR API card from group sell

2017-09-14T10:00:19Z

Reda: /* Parametres */

=Description=

[[MOR API]] sells Cards from Calling Card Group
 
=Usage=

* From '''MOR X4''' call: '''/api/card_from_group_sell'''
* For Backwards-compatibility old name 'buy_card_from_callingroup' is also usable. Call: '''/api/buy_card_from_callingroup'''
* Methods: POST, GET(if allowed, not recomended)
 
===Parametres===

Parameters which are '''included''' into hash:

* email - email address, to send information about bought card '''Optional'''.
* id - Calling Card Group ID in MOR database. '''Required'''.
* quantity - default 1. '''Optional'''.

'''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 parameters above and API_Secret_Key ([[MOR API hash construction | More described in Constructing hash]]). '''Required'''.
* u - username for authentication. '''Required'''.
* number - parameter that indicates which card is sold. If number parameter is send, then quantity parameter will be ignored. '''Optional'''.
* curr - parameter that lets change the currency of cards. '''Optional'''.
 

===Request===

We have id = 6, quantity = 2, API Secret Key = 456789

We send:
HTML POST: http://<SERVER_IP>/billing/api/buy_card_from_callingroup?u=username&id=6&quantity=2&hash=37086d860581fabc278413cd1a417d5c079f6eba

'''NOTE that username are not included in hash'''
 
===Returns===

'''Success'''

<?xml version="1.0" encoding="UTF-8"?>
<page>
<cards>
<card>
<pin>...</pin>
<number>..</number>
<balance_without_vat>...</balance_without_vat>
<currency>...</currency>
</card>
<card>
<pin>...</pin>
<number>...</number>
<balance_without_vat>...</balance_without_vat>
<currency>...</currency>
</card>
</cards>
</page>
 
----

'''Errors'''

* <error>Bad login</error> - User supplied bad login or password.
* <error>Incorrect hash</error> - Hash was not correct. Check API_Secret_Key and order or params while concatenating hash_string.
* <error>Cardgroup was not found</error> - Use correct Calling Card Group ID .
* <error>Free cards was not found</error> - no free cards in Calling Card Group.
* <error>Card is already sold</error> - This card is already sold.

 

=See also=

* [[MOR API]]

File:Cards batch management 1.png

2017-09-14T09:04:02Z

Reda: uploaded a new version of "File:Cards batch management 1.png"

Alert Schedules

2017-09-05T06:05:58Z

Reda:

=Description=

Alert Schedules lets you to set time intervals, when notification can be send. These Time Periods used in [[Alert Groups]].
 
=Usage=

Go to '''ADDONS –> Monitorings –> Alert Schedules'''
 
[[File:alert_schedules_path.png]]
 
Here you are able to see all list of Alert Schedules.

[[File:Alert_schedules.png]]

Insert data and click on [[Image:icon_add.png]] icon to create a schedule or click [[image:icon_edit.png]] icon to change existing schedule data.

Timeperiod for all days will be added as default timeperiod for new created schedule.

When editing the schedule, you can add timeperiods for every day of the week, aswell as the whole week at once.

Emails will be sent in the selected time onthe chosen day.

'''NOTE''' You can only add time periods in the edit window.
 

=See also=

* [[Alerts]]
* [[Alert Groups]]
* [[Alert Contacts]]

Alert Schedules

2017-09-05T06:04:55Z

Reda:

=Description=

Alert Schedules lets you to set time intervals, when notification can be send. These Time Periods used in [[Alert Groups]].
 
=Usage=

Go to '''ADDONS –> Monitorings –> Alert Schedules'''
 
[[File:alert_schedules_path.png]]
 
Here you are able to see all list of Alert Schedules.

[[File:Alert_schedules.png]]

Insert data and click on [[Image:icon_add.png]] icon to create a schedule or click [[image:icon_edit.png]] icon to change existing schedule data.

By creating the schedule, timeperiod for all days will be added as default timeperiod.

When editing the schedule, you can add timeperiods for every day of the week, aswell as the whole week at once.

Emails will be sent in the selected time onthe chosen day.

'''NOTE''' You can only add time periods in the edit window.
 

=See also=

* [[Alerts]]
* [[Alert Groups]]
* [[Alert Contacts]]

File:Alert schedules.png

2017-09-05T05:58:03Z

Reda: uploaded a new version of "File:Alert schedules.png"

PhoneBook

2017-08-16T12:47:41Z

Reda: /* Global PhoneBook */

= Description =

PhoneBook has several purposes:

# If it recognizes the Caller, PhoneBook changes the CallerID Name.
# [[Speed Dials]] are configured in PhoneBook.
 
===When is PhoneBook applied?===

PhoneBook is applied when user call is authenticated. This means you have to use either Authentication by [[Dial_Plans | PIN or ANI]] dial plan if call comes from outside.
 
=== Definitions ===

* There are two types of PhoneBook: Global and Simple.
* There’s only one Global PhoneBook.
* Each user has his own Simple PhoneBook, except for the admin user, who is the owner of Global PhoneBook.
* A User's Simple PhoneBook has higher priority than Global PhoneBook. If a record is found in both the Simple and the Global PhoneBook, the record from the Simple PhoneBook will be used.
 
= Global PhoneBook =

Go to '''ADDONS –> PBX functions –> External DIDs –> PhoneBook'''
 
[[Image:phonebook_global_path.png]]
 
Here you will see list of all global contacts.
 
[[Image:phonebook_global.png]]
 
'''NOTE that This PhoneBook is managed by System Admin and Accountant with [[Accountant_permissions | a '''Manage PBX functions''' permission]] and is applicable to all system Users (e.g. Global).'''

A good use for it is to create some short numbers for Users to call for Support/Emergency/etc.

The Speed Dial feature is explained [[Speed_Dials#Speed_Dials_for_Users | here]].
 

= Simple PhoneBook =

Each user has his own Simple PhoneBook, which has higher priority than Global PhoneBook. For example, if records from Simple PhoneBook match those of Global PhoneBook, the record from Simple PhoneBook will be used. (Again, in other words - the user can overwrite the System Admin's PhoneBook record.)
 
Go to '''PERSONAL MENU –> Various –> PhoneBook
 
[[Image:personal_phonebook_path.png]]
 
Here you will see global and personal contacts list.
 
[[Image:speed_dial_for_user.png]]
 
'''NOTE''' that Record '123'. It is Global - that is, created by System Admin. A User can use it, but he can't manage it.

The Speed Dial feature is explained [[Speed_Dials#Speed_Dials_for_Users | here]].

== Using CallerID Name overwrite ==

When a number (CallerID Number) which is in PhoneBook calls in, MOR checks this number and sets the CallerID Name to the value from PhoneBook.

It’s visible on phones which support CallerID Name:
 
[[Image:callerid_name_from_phonebook.png]]
 
== See also ==

* [[Speed Dials]]
* [[PhoneBook]] API: [[MOR_API_phonebooks_get|List]], [[MOR_API_phonebook_edit|Edit]]

PhoneBook

2017-08-16T12:42:39Z

Reda: /* Simple PhoneBook */

= Description =

PhoneBook has several purposes:

# If it recognizes the Caller, PhoneBook changes the CallerID Name.
# [[Speed Dials]] are configured in PhoneBook.
 
===When is PhoneBook applied?===

PhoneBook is applied when user call is authenticated. This means you have to use either Authentication by [[Dial_Plans | PIN or ANI]] dial plan if call comes from outside.
 
=== Definitions ===

* There are two types of PhoneBook: Global and Simple.
* There’s only one Global PhoneBook.
* Each user has his own Simple PhoneBook, except for the admin user, who is the owner of Global PhoneBook.
* A User's Simple PhoneBook has higher priority than Global PhoneBook. If a record is found in both the Simple and the Global PhoneBook, the record from the Simple PhoneBook will be used.
 
= Global PhoneBook =

Go to '''ADDONS –> PBX functions –> External DIDs –> PhoneBook'''
 
[[Image:phonebook_global_path.png]]
 
Here you will see list of all global contacts.
 
[[Image:phonebook_global.png]]
 
'''NOTE that This PhoneBook is managed by System Admin and is applicable to all system Users (e.g. Global).'''

A good use for it is to create some short numbers for Users to call for Support/Emergency/etc.

The Speed Dial feature is explained [[Speed_Dials#Speed_Dials_for_Users | here]].
 
= Simple PhoneBook =

Each user has his own Simple PhoneBook, which has higher priority than Global PhoneBook. For example, if records from Simple PhoneBook match those of Global PhoneBook, the record from Simple PhoneBook will be used. (Again, in other words - the user can overwrite the System Admin's PhoneBook record.)
 
Go to '''PERSONAL MENU –> Various –> PhoneBook
 
[[Image:personal_phonebook_path.png]]
 
Here you will see global and personal contacts list.
 
[[Image:speed_dial_for_user.png]]
 
'''NOTE''' that Record '123'. It is Global - that is, created by System Admin. A User can use it, but he can't manage it.

The Speed Dial feature is explained [[Speed_Dials#Speed_Dials_for_Users | here]].

== Using CallerID Name overwrite ==

When a number (CallerID Number) which is in PhoneBook calls in, MOR checks this number and sets the CallerID Name to the value from PhoneBook.

It’s visible on phones which support CallerID Name:
 
[[Image:callerid_name_from_phonebook.png]]
 
== See also ==

* [[Speed Dials]]
* [[PhoneBook]] API: [[MOR_API_phonebooks_get|List]], [[MOR_API_phonebook_edit|Edit]]

IVR system

2017-08-16T12:17:17Z

Reda:

[[Image:ivr_example.png|right|500px]]This system makes it possible to configure advanced IVR ('''Interactive Voice Response''') systems.

This functionality can be used by system owner (admin), [[Reseller_Pro_Addon|Resellers PRO]] and Accountant with [[Accountant_permissions | a '''Manage PBX functions''' permission]].

From MOR x5 IVRs and IVR Time Periods are located in '''ADDONS -> PBX functions -> IVR''' and Voices can be found at '''SETTINGS''' -> '''Setup''' -> '''Voices'''

In MOR version x4 and lower IVRs and IVR Time Periods are located in '''SETTINGS-->billing-->DIDs-->IVR-->IVRs'''

 
== Definitions ==

* '''Voices''' – a set of audio files, such as male/female recordings, that together form a "voice" for the same IVR.
* '''Time Periods''' – a start date/time and end date/time that describe a time period.
* '''IVR''' – a set of IVR blocks.
** '''Blocks''' – a part of IVR in which the caller can take some action (press a button-extension, listen to a recording, etc). Basically block in IVR is "set of rules".
** '''Extensions''' – possible button presses (0-9, *, # and some other special cases).
** '''Actions''' – what action the system should take when a new Block is reached.

 
== Setup logic ==

* Create Voice
** Record and upload the necessary sound files to Voice.
* Create Time Period(s).
* Create IVR.
** Create and configure Block(s).
* Create the IVR Dial Plan.
* Assign this IVR Dial Plan to a DID.
* Call this DID to test it.

 
== Voices ==

'''SETTINGS''' -> '''Setup''' -> '''Voices''' for the System Admin, Reseller PROs and Accountants (with an [[Accountant_permissions|IVR > Manage IVR Voices]] permission).

Here it is possible to create several Voices. A Voice consists of a set of sound files. Usually all the sound files in one Voice are recorded by one person to keep the sound consistent.

Multiple operations can be performed with Voices:

* View a detailed list of the system Voices.
* Add a new sound Voice.
* View the sounds that have files in different Voices.
* Upload new sound files for Voices.
* Delete Voices and voice files from the system.

You cannot remove sounds that are currently used.

 

== Time Periods ==

Go to '''ADDONS -> PBX functions -> IVR''' –> Time Periods'''
 
[[File:ivr_time_perionds_path.png]]
 
Here you will see Time Periods list. Click [[Image:icon_add.png]]'''New Time Period''' to create new period or click on [[image:icon_edit.png]] icon to edit old one to set time periods.
 
[[File:ivr_time_perionds.png]]
 
Time period defines the exact time period IVR will be active. There is a limit of three periods in [[IVR Dial Plan]]. There is a fourth period, but it only consists of all the remaining time that is not covered by the previous three periods.
 
===Examples===
# Select '''Date''' from 1 of January to 28 of February and choose '''Hour : Minute''' from 09:00 to 18:59. Action will be active 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 action will be active 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. Action will be active every week from Monday till Friday at time from 13:00 till 15:59.
 
'''Note:''' time is in server's timezone

== IVR Structure ==

* '''IVR''' – consists of a set of IVR blocks.
** '''Blocks''' – part of IVR in which a caller can take some action (press a button-extension, listen to a recording, etc).
** '''Extensions''' – possible button presses (0-9, *, # and some other special cases).
** '''Actions''' – what action the system should take when an extension is activated.

The main part of IVR is '''Blocks'''. The whole of IVR is a set of Blocks. A Block can be considered as a part of IVR logic where a caller can take some action.

'''Extension''' is what the user does – presses a button (0-9, *, #), waits (Timeout), or presses any non-described extension – which can be described as an Invalid Extension. We explain this in detail later.

'''Actions''' are actions which will be activated when the caller comes to a Block.

 
=== Example ===

For example, here is a simple IVR:
* A caller calls a DID and IVR answers with a recording: "Thank you for calling SOME COMPANY. For sales press 1, for management press 2, to speak to a consultant please hold or press 3."

Here we have only one block: the user listens to the recording and can take some Action -> press some button (Extension) or wait (Wait is also Extension but is special - it is called Timeout).

If the user presses something different than 1, 2 or 3, the message will be played again. This is called an Invalid Extension, or (i) for short.

To summarize, we have the following situation:

* 1 Block.
* Extensions: 1, 2, 3, t (timeout), i (invalid).
* Actions: call to sales, call to management, call to a consultant, play recording again.

This example is to illustrate the main IVR building parts. We will show how they operate together to build a working IVR.

 
== Extensions ==

Extensions are button presses on the dialpad: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, * and # and two special extensions:

* t - means "timeout", when no extension is pressed in a determined time period.
* i - means "invalid". This extension becomes active when a caller presses some extensions that are not described in the IVR block configuration.

The 'i' (invalid) extension in the previous example could be triggered when buttons 4, 5, 6, 7, 8, 9, 0, *, # are pressed, because only 1, 2 and 3 are described.

 
== Actions ==

An Action is some (yes...) action which is executed when a new Block is reached.

Possible Actions:

* Playback – plays a sound file.
* Delay – delays execution by some seconds.
* Change Voice – changes IVR Voice.
* Hangup – finishes the call.
* Transfer to – transfers the call to:
** Another IVR
** DID
** Device
** Block
** Extension - in an opened text field you can enter anything.
* Conditional Transfer – if the Caller ID matches some defined value, the call is transferred to:
** Another IVR
** DID
** Device
** Block
** Extension - in an opened text field you can enter anything.
* Debug – text message to Asterisk CLI which helps debugging.
* Set Accountcode - sets ownership for the call to some other user.
* Set CallerID (Number) - Sets incoming call to IVR, callerID number to any desired value. Usage example can be found [[How_to_request_Authentication_by_PIN_when_call_comes_from_Banned_CallerID | here]]
* [[Random_play|Random Play]]
[[File:Ivr_play_random.png]]
 
This action plays a random sound file from the selected '''IVR Voice''' file group.
* Security Code - a caller is asked to enter a specified Security Code (maximum 10 digits). If the code is entered correctly IVR proceeds to the next step, otherwise the workflow is transferred to another block.

 
== Timeouts ==

=== Timeout digits ===

The maximum amount of time permitted between digits when the
user is typing in an extension. When this timeout expires
after the user has started to type in an extension, the
extension will be considered complete, and will be
interpreted. Note that if an extension typed in is valid,
it will not have to timeout to be tested, so typically at
the expiry of this timeout, the extension will be considered
invalid (and thus control would be passed to the 'i'
extension, or if none exists the call would be
terminated). The default timeout (in MOR IVR) is 3 seconds.

 
=== Timeout Response===

The maximum amount of time permitted after falling through a
series of priorities for a channel in which the user may
begin typing an extension. If the user does not begin typing an
extension in this amount of time, control will pass to the
't' extension if one exists, or if none exists, the call would be
terminated. Once the user begins to type an extension, Asterisk
will wait for digit timeout to be reached, and response timeout has
no effect. The default timeout (in MOR IVR) is 10 seconds.

 

== Deleting IVR ==

* If an IVR is not assigned to any Dial Plan, you can delete the IVR by clicking the [[Image:icon_delete.png]] icon near an IVR in the IVR menu.
* If the IVR is assigned to a Dial Plan, you need to unassign the IVR from the Dial Plan to be able to delete it.

 
== Setup Hints/Tips ==

* If you want to play a sound file, make sure you have set the correct Voice. By default, Voice = 'en'. If you have uploaded a sound file for a different Voice, select it before playing your Sound File:

[[Image:ivr_select_voice_before_playback.png]]

 
=See also=
* [[IVR for Calling Cards]]
* [[IVR Greeting for DID]]
* [[Dial Local]]
* [[I have a problem with IVR]]
* [[Sound files]]
** [[MOR IVR Samples]]
*[[IVR setup example]]

*[[Random_play|Random Play IVR Campaign]]

MOR BLF

2017-08-16T12:13:06Z

Reda: /* Permissions */

BLF (Busy Lamp Field) feature allows to monitor the state of another phone/user extension. Usually this is indicated by the LEDs on a phone.

This has to be configured manually from the phone (if phone supports BLF) and also in MOR GUI.

==Configuration in MOR==

Go to '''PBX Functions''' -> '''BLF''': 

[[File:Mor blf menu.png]]

Here you will see a list of BLF groups. Admin will see only groups that were created by himself. This applies to Resellers and Users. Only owners will see their groups in BLF list. 

[[File:Mor blf list.png]]

To create new BLF group press '''Add new BLF Group''': 

[[File:Mor blf new group.png]]

Here you will be able to give a name to your BLF Group and set a comment. 

When BLF Group is created, you will see '''Subscribed Devices''' and '''Assigned Devices''' columns. These columns will show many Devices are subscribed and assigned to BLF Group. 

Click phone icon under '''Assigned Devices''' and Assigned Device list will be displayed. 

[[File:Mor blf assign device list.png]]

Click '''Assign Device''' and assign Devices that you want to monitor. 

[[File:Mor blf assign device add new.png]]

When assigning Device, you need to specify '''BLF extension'''. This extension will be used in your phone settings. BLF extension can be the same as Device extension or any other alphanumeric extension. 

Next step is to subscribe Devices that will "watch" these assigned Devices. 

In BLF Group list click phone icon under '''Subscribed Devices''' and Subscribed Device list will be displayed 

[[File:Mor blf subscribe device list.png]]

Subscribed Device will be able to monitor Devices that are assigned to this group. More than one Device can be subscribed to BLF Group. Click '''Subscribe Device''' to subscribe new Device to this Group. 

[[File:Mor blf subscribe device add new.png]]

Select User and Device. 

Now BLF Group has subscribed and assigned Devices and is fully functional. 

'''BLF groups increase security by isolating Devices in a specific group so that only Devices that are subscribed to this group can see status of assigned Devices.''' 

Last step is to configure BLF on phone.

==Configuration on phone==

Different phones have different BLF configuration settings. Follow your phone’s manual instructions how to configure BLF. Below is configuration example for '''Linksys SPA942''' phone. 

===Linksys SPA942 configuration example===

Linksys SPA942 phone supports up to 4 extensions. To enable BLF functionality on Linksys SPA942 phone, you need to update phone’s firmware version to '''6.1.5a'''. If current phone's firmware version is lower than 5.2.5, then download and install 5.2.5 update before 6.1.5a.

Firmware update can be downloaded from CISCO website:

https://software.cisco.com/download/release.html?mdfid=282414124&softwareid=282463651&release=6.1.5a

To check current Linksys SPA942 firmware version, go to phone’s configuration panel and under Info tab you can see firmware version:

[[File:Linksys version.png]]

Once Linksys SPA942 firmware is updated to 6.1.5a version, you can configure BLF in MOR. To do so, follow example in [http://wiki.kolmisoft.com/index.php?title=MOR_BLF#Configuration_in_MOR Configuration in MOR].

Next step is to configure BLF on Linksys SPA942. Go to phone’s configuration panel, click Admin Login and then switch to advanced settings:

[[File:Linksys menu.png]]

After switching to advanced settings, go to Phone tab. You should see 4 extensions (Line Key 1-4). These represents keys on your phone.

[[File:Linksys blf settings.png]]

To enable BLF, set Extension to '''Disabled''', enter Short Name that will be displayed near buttons on the screen and enter the following line in Extended Function input:

fnc=blf+sd+cp;sub=1001@$PROXY;ext=1001@$PROXY

Change extension 1001 to '''BLF Extension''' configured in MOR GUI.

Last step is to set Server Type to '''Asterisk'''.

Press '''Submit All Changes''' and phone will be set up for BLF. Now you should see blinking button on configured extensions.

==Permissions==

BLF groups can be configured by Admin, Resellers, Accountants and Users. Resellers, Accountants and Users require BLF permission to do so. 

User BLF permissions can be found in '''SETTINGS''' -> '''Users''' -> '''User Permissions''' (''BLF'' permission) 

Reseller BLF permissions can be found in '''ADDONS''' -> '''Resellers''' -> '''Reseller permissions''' (''PBX functions'' permission) 

Accountant BLF permissions can be found in '''SETTINGS''' -> '''Setup''' -> '''Accountant permissions''' (''PBX functions'' permission)

Music on Hold

2017-08-16T12:07:26Z

Reda: /* Who can configure and use Music on Hold? */

= Description =

It is recorded music being played to fill the silence that would be heard by telephone callers who have been placed on hold. It is especially common in situations involving customer service. Any caller will hear music if it is set so.

NOTE: When Music On Hold (MOH) is playing - Ring signal is not played. Not possible to play MOH and then ring signal in the same call.

 
== Who can configure and use Music on Hold? ==

* Admin and accountant with [[Accountant_permissions | a '''Manage PBX functions''' permission]] can configure Music on Hold, create, update and delete sounds.
 

= Usage =

Go to '''ADDONS –> PBX functions –> Music On Hold''':
 
[[Image:moh-menu.png]]
 
Here you can see the list of current sound files added which will be played while the caller is on hold:
 
[[Image:moh-main.png]]
 
To create new record, click [[File:add.png]]'''Add new''' and type in name, description, choose [http://wiki.kolmisoft.com/index.php/IVR_system#IVR_Voices ivr sound files folder] and select if files in that folder are played randomly or in order:
 
[[Image:moh-create.png]]
 
You can also change details by clicking [[File:edit.png]] icon and delete music on hold by clicking [[File:delete.png]] icon.

When you have created Music on Hold, you can now assign the selected class to a [http://wiki.kolmisoft.com/index.php/Call_Queues Queue]. Simply go to '''Settings –> PBX functions –> Queues''' and assign class by selecting it from dropdown in '''Caller Options''' section:
 
[[File:caller-options.png]]
 

= See also =

* [[IVR system]]
* [[Call Queues]]

Ring-Groups

2017-08-16T11:56:51Z

Reda: /* Where to find Ring Groups? */

=About=

A ring group acts like any other Asterisk extension number except it rings a collection of Asterisk extensions which you specify. If you dial a ring group number, it will ring all of the Asterisk extensions associated with that ring group.
 

=Currently supported Dialing Strategies=

Currently MOR supports these Dialing Strategies:
*ringall

''If you need other dialing strategies to be implemented - please submit a ticket in Support system.''

 

==What is needed to setup a Ring Group?==
* At least one DID number, you can get one from [http://www.didww.com/ DIDWW]
 
==Where to find Ring Groups?==

'''Ring Groups''' are available for admin and accountant with [[Accountant_permissions | a '''Manage PBX functions''' permission]] and can be found in '''ADDONS –> PBX functions –> External DIDs –> Ring Groups''':
 
[[File:Ring groups path.png]]
 

==How to create a new Ring Group?==

1. Go to: '''SETTINGS -> Billing -> DIDs -> PBX functions -> Ring Groups'''

2. Press: [[File:add.png]] '''New Ring Group'''

3. New Ring Group setup will appear:

[[File:Ring_group_2.png]]

* '''Ring Group name:''' enter your Ring Group name here, for example "Sales ring group";
* '''Comment:''' (optional) enter your Ring Group description, for example "This is my Sales Ring group";
* '''This Ring Group will be reached by such local extension:''' Enter an extension, that will be used to dial this ring group
locally. Remember not to duplicate your [[Extension_lines | extensions!]];
* '''Extension belongs to PBX Pool:''' select PBX Pool. NOTE: duplicate Extensions can not be created in same PBX Pool.
* '''Ring Time (how long device will ring):''' Define how many seconds to ring the group of devices (default is 60 seconds);
* '''Options to use when dialing (Advanced):''' '''!!!ATTENTION!!!''' Do not use this field if you are not sure what you are doing. 
This field allows you to enter more advanced Dialing options.
More information can be found [http://www.voip-info.org/wiki/view/Asterisk+cmd+Dial#Dialmacros here];
* '''Dialing Strategy:''' Choose the ring strategy from the drop down list;
* '''CallerID Prefix:''' Define what callerID prefix should be added for the incoming call. For example, if your ring group is used for sales department, you can add a "sales" CallerID name;
* '''Route to DID if No Answer:''' Search for a DID number from the auto-complete list, to which route the call if none of the ring group devices answer the call. DID must be assigned to device or dialplan to be displayed in this list.
 

==How to add devices to a Ring Group?==
[[File:Ring_groups_3.png]]
 
* '''This Ring Group will be reached by such DIDs:''' Click on the [[File:Add_did_rg.png]] to assign a DID number from a drop down menu that will be used to call this Ring Group;
* '''Will ring these devices:''' Click on the [[File:Add_device_rg.png]] and choose [[Users | users]] with their [[Devices | devices]] which will be used in this Ring Group;
* '''Show Extension lines''' Click on this link in order to check the Extension lines which will be used when dialing. This is for information purposes only.
[[File:Extension_rg.png]]
 
* After you have successfully completed the configuration, you should see a similar result on the right hand side on the window (This is ONLY an example!!):
[[File:Ring_group.png]]

 
'''NOTE: Do not add Devices with Fax Detect to Ring group. Ring group will not work correctly in this case.'''

===Virtual device===

Adding a virtual device allows calling both to local devices and external numbers at the same time. Create a virtual device (click [[Devices| here]] for detailed information about devices) and then make a Call Flow for it. Click [[File:icon call flow.png]] to see a basic Call Flow and then click [[File:edit.png]] in the ''Before State'' line. Select Action: ''Forward'', Forward to: ''External number'', enter the number and click ''Change''.

[[File:Devices callflow.png]]

Device is now ready to be assigned to a Ring group. 

 
==Ring Group Device limit==

There is a limit of how many Devices can be added to Ring Group. There is no exact number of how many Devices can be added to Ring Group because this limit depends on Device extension length. You will be able to add more Devices with shorter extensions to Ring Group. 
Once limit is reached, you will see error message '''Ring Group is full, Device limit reached'''. 
This limit comes from Asterisk not being able to read more than 512 characters from dial string.
= See also =
* [[How to forward Ring Group to Voicemail if not answered]]

Ring-Groups

2017-08-16T11:54:36Z

Reda: /* Where to find Ring Groups? */

=About=

A ring group acts like any other Asterisk extension number except it rings a collection of Asterisk extensions which you specify. If you dial a ring group number, it will ring all of the Asterisk extensions associated with that ring group.
 

=Currently supported Dialing Strategies=

Currently MOR supports these Dialing Strategies:
*ringall

''If you need other dialing strategies to be implemented - please submit a ticket in Support system.''

 

==What is needed to setup a Ring Group?==
* At least one DID number, you can get one from [http://www.didww.com/ DIDWW]
 
==Where to find Ring Groups?==

'''Ring Groups''' are available for admin and accountant with [[Accountant_permissions | a '''Manage PBX functions''' permission]] and can be found in '''ADDONS –> PBX functions –> External DIDs –> Ring Groups''':
 
[[File:Ring groups path.png]]
 

==How to create a new Ring Group?==

1. Go to: '''SETTINGS -> Billing -> DIDs -> PBX functions -> Ring Groups'''

2. Press: [[File:add.png]] '''New Ring Group'''

3. New Ring Group setup will appear:

[[File:Ring_group_2.png]]

* '''Ring Group name:''' enter your Ring Group name here, for example "Sales ring group";
* '''Comment:''' (optional) enter your Ring Group description, for example "This is my Sales Ring group";
* '''This Ring Group will be reached by such local extension:''' Enter an extension, that will be used to dial this ring group
locally. Remember not to duplicate your [[Extension_lines | extensions!]];
* '''Extension belongs to PBX Pool:''' select PBX Pool. NOTE: duplicate Extensions can not be created in same PBX Pool.
* '''Ring Time (how long device will ring):''' Define how many seconds to ring the group of devices (default is 60 seconds);
* '''Options to use when dialing (Advanced):''' '''!!!ATTENTION!!!''' Do not use this field if you are not sure what you are doing. 
This field allows you to enter more advanced Dialing options.
More information can be found [http://www.voip-info.org/wiki/view/Asterisk+cmd+Dial#Dialmacros here];
* '''Dialing Strategy:''' Choose the ring strategy from the drop down list;
* '''CallerID Prefix:''' Define what callerID prefix should be added for the incoming call. For example, if your ring group is used for sales department, you can add a "sales" CallerID name;
* '''Route to DID if No Answer:''' Search for a DID number from the auto-complete list, to which route the call if none of the ring group devices answer the call. DID must be assigned to device or dialplan to be displayed in this list.
 

==How to add devices to a Ring Group?==
[[File:Ring_groups_3.png]]
 
* '''This Ring Group will be reached by such DIDs:''' Click on the [[File:Add_did_rg.png]] to assign a DID number from a drop down menu that will be used to call this Ring Group;
* '''Will ring these devices:''' Click on the [[File:Add_device_rg.png]] and choose [[Users | users]] with their [[Devices | devices]] which will be used in this Ring Group;
* '''Show Extension lines''' Click on this link in order to check the Extension lines which will be used when dialing. This is for information purposes only.
[[File:Extension_rg.png]]
 
* After you have successfully completed the configuration, you should see a similar result on the right hand side on the window (This is ONLY an example!!):
[[File:Ring_group.png]]

 
'''NOTE: Do not add Devices with Fax Detect to Ring group. Ring group will not work correctly in this case.'''

===Virtual device===

Adding a virtual device allows calling both to local devices and external numbers at the same time. Create a virtual device (click [[Devices| here]] for detailed information about devices) and then make a Call Flow for it. Click [[File:icon call flow.png]] to see a basic Call Flow and then click [[File:edit.png]] in the ''Before State'' line. Select Action: ''Forward'', Forward to: ''External number'', enter the number and click ''Change''.

[[File:Devices callflow.png]]

Device is now ready to be assigned to a Ring group. 

 
==Ring Group Device limit==

There is a limit of how many Devices can be added to Ring Group. There is no exact number of how many Devices can be added to Ring Group because this limit depends on Device extension length. You will be able to add more Devices with shorter extensions to Ring Group. 
Once limit is reached, you will see error message '''Ring Group is full, Device limit reached'''. 
This limit comes from Asterisk not being able to read more than 512 characters from dial string.
= See also =
* [[How to forward Ring Group to Voicemail if not answered]]

Ring-Groups

2017-08-16T11:52:07Z

Reda: /* Where to find Ring Groups? */

=About=

A ring group acts like any other Asterisk extension number except it rings a collection of Asterisk extensions which you specify. If you dial a ring group number, it will ring all of the Asterisk extensions associated with that ring group.
 

=Currently supported Dialing Strategies=

Currently MOR supports these Dialing Strategies:
*ringall

''If you need other dialing strategies to be implemented - please submit a ticket in Support system.''

 

==What is needed to setup a Ring Group?==
* At least one DID number, you can get one from [http://www.didww.com/ DIDWW]
 
==Where to find Ring Groups?==

'''Ring Groups''' are available for admin and accountant with [[Accountant_permissions | pbx functions permission]] and can be found in '''ADDONS –> PBX functions –> External DIDs –> Ring Groups''':
 
[[File:Ring groups path.png]]
 

==How to create a new Ring Group?==

1. Go to: '''SETTINGS -> Billing -> DIDs -> PBX functions -> Ring Groups'''

2. Press: [[File:add.png]] '''New Ring Group'''

3. New Ring Group setup will appear:

[[File:Ring_group_2.png]]

* '''Ring Group name:''' enter your Ring Group name here, for example "Sales ring group";
* '''Comment:''' (optional) enter your Ring Group description, for example "This is my Sales Ring group";
* '''This Ring Group will be reached by such local extension:''' Enter an extension, that will be used to dial this ring group
locally. Remember not to duplicate your [[Extension_lines | extensions!]];
* '''Extension belongs to PBX Pool:''' select PBX Pool. NOTE: duplicate Extensions can not be created in same PBX Pool.
* '''Ring Time (how long device will ring):''' Define how many seconds to ring the group of devices (default is 60 seconds);
* '''Options to use when dialing (Advanced):''' '''!!!ATTENTION!!!''' Do not use this field if you are not sure what you are doing. 
This field allows you to enter more advanced Dialing options.
More information can be found [http://www.voip-info.org/wiki/view/Asterisk+cmd+Dial#Dialmacros here];
* '''Dialing Strategy:''' Choose the ring strategy from the drop down list;
* '''CallerID Prefix:''' Define what callerID prefix should be added for the incoming call. For example, if your ring group is used for sales department, you can add a "sales" CallerID name;
* '''Route to DID if No Answer:''' Search for a DID number from the auto-complete list, to which route the call if none of the ring group devices answer the call. DID must be assigned to device or dialplan to be displayed in this list.
 

==How to add devices to a Ring Group?==
[[File:Ring_groups_3.png]]
 
* '''This Ring Group will be reached by such DIDs:''' Click on the [[File:Add_did_rg.png]] to assign a DID number from a drop down menu that will be used to call this Ring Group;
* '''Will ring these devices:''' Click on the [[File:Add_device_rg.png]] and choose [[Users | users]] with their [[Devices | devices]] which will be used in this Ring Group;
* '''Show Extension lines''' Click on this link in order to check the Extension lines which will be used when dialing. This is for information purposes only.
[[File:Extension_rg.png]]
 
* After you have successfully completed the configuration, you should see a similar result on the right hand side on the window (This is ONLY an example!!):
[[File:Ring_group.png]]

 
'''NOTE: Do not add Devices with Fax Detect to Ring group. Ring group will not work correctly in this case.'''

===Virtual device===

Adding a virtual device allows calling both to local devices and external numbers at the same time. Create a virtual device (click [[Devices| here]] for detailed information about devices) and then make a Call Flow for it. Click [[File:icon call flow.png]] to see a basic Call Flow and then click [[File:edit.png]] in the ''Before State'' line. Select Action: ''Forward'', Forward to: ''External number'', enter the number and click ''Change''.

[[File:Devices callflow.png]]

Device is now ready to be assigned to a Ring group. 

 
==Ring Group Device limit==

There is a limit of how many Devices can be added to Ring Group. There is no exact number of how many Devices can be added to Ring Group because this limit depends on Device extension length. You will be able to add more Devices with shorter extensions to Ring Group. 
Once limit is reached, you will see error message '''Ring Group is full, Device limit reached'''. 
This limit comes from Asterisk not being able to read more than 512 characters from dial string.
= See also =
* [[How to forward Ring Group to Voicemail if not answered]]

Ring-Groups

2017-08-16T11:50:29Z

Reda: /* Where to find Ring Groups? */

=About=

A ring group acts like any other Asterisk extension number except it rings a collection of Asterisk extensions which you specify. If you dial a ring group number, it will ring all of the Asterisk extensions associated with that ring group.
 

=Currently supported Dialing Strategies=

Currently MOR supports these Dialing Strategies:
*ringall

''If you need other dialing strategies to be implemented - please submit a ticket in Support system.''

 

==What is needed to setup a Ring Group?==
* At least one DID number, you can get one from [http://www.didww.com/ DIDWW]
 
==Where to find Ring Groups?==

'''Ring Groups''' are available for admin and accountant with [[pbx functions permission | Accountant_permissions]] and can be found in '''ADDONS –> PBX functions –> External DIDs –> Ring Groups''':
 
[[File:Ring groups path.png]]
 

==How to create a new Ring Group?==

1. Go to: '''SETTINGS -> Billing -> DIDs -> PBX functions -> Ring Groups'''

2. Press: [[File:add.png]] '''New Ring Group'''

3. New Ring Group setup will appear:

[[File:Ring_group_2.png]]

* '''Ring Group name:''' enter your Ring Group name here, for example "Sales ring group";
* '''Comment:''' (optional) enter your Ring Group description, for example "This is my Sales Ring group";
* '''This Ring Group will be reached by such local extension:''' Enter an extension, that will be used to dial this ring group
locally. Remember not to duplicate your [[Extension_lines | extensions!]];
* '''Extension belongs to PBX Pool:''' select PBX Pool. NOTE: duplicate Extensions can not be created in same PBX Pool.
* '''Ring Time (how long device will ring):''' Define how many seconds to ring the group of devices (default is 60 seconds);
* '''Options to use when dialing (Advanced):''' '''!!!ATTENTION!!!''' Do not use this field if you are not sure what you are doing. 
This field allows you to enter more advanced Dialing options.
More information can be found [http://www.voip-info.org/wiki/view/Asterisk+cmd+Dial#Dialmacros here];
* '''Dialing Strategy:''' Choose the ring strategy from the drop down list;
* '''CallerID Prefix:''' Define what callerID prefix should be added for the incoming call. For example, if your ring group is used for sales department, you can add a "sales" CallerID name;
* '''Route to DID if No Answer:''' Search for a DID number from the auto-complete list, to which route the call if none of the ring group devices answer the call. DID must be assigned to device or dialplan to be displayed in this list.
 

==How to add devices to a Ring Group?==
[[File:Ring_groups_3.png]]
 
* '''This Ring Group will be reached by such DIDs:''' Click on the [[File:Add_did_rg.png]] to assign a DID number from a drop down menu that will be used to call this Ring Group;
* '''Will ring these devices:''' Click on the [[File:Add_device_rg.png]] and choose [[Users | users]] with their [[Devices | devices]] which will be used in this Ring Group;
* '''Show Extension lines''' Click on this link in order to check the Extension lines which will be used when dialing. This is for information purposes only.
[[File:Extension_rg.png]]
 
* After you have successfully completed the configuration, you should see a similar result on the right hand side on the window (This is ONLY an example!!):
[[File:Ring_group.png]]

 
'''NOTE: Do not add Devices with Fax Detect to Ring group. Ring group will not work correctly in this case.'''

===Virtual device===

Adding a virtual device allows calling both to local devices and external numbers at the same time. Create a virtual device (click [[Devices| here]] for detailed information about devices) and then make a Call Flow for it. Click [[File:icon call flow.png]] to see a basic Call Flow and then click [[File:edit.png]] in the ''Before State'' line. Select Action: ''Forward'', Forward to: ''External number'', enter the number and click ''Change''.

[[File:Devices callflow.png]]

Device is now ready to be assigned to a Ring group. 

 
==Ring Group Device limit==

There is a limit of how many Devices can be added to Ring Group. There is no exact number of how many Devices can be added to Ring Group because this limit depends on Device extension length. You will be able to add more Devices with shorter extensions to Ring Group. 
Once limit is reached, you will see error message '''Ring Group is full, Device limit reached'''. 
This limit comes from Asterisk not being able to read more than 512 characters from dial string.
= See also =
* [[How to forward Ring Group to Voicemail if not answered]]

MOR API quickstats get

2017-08-01T11:05:29Z

Reda:

=Description=

Retrieves today's [[Quick Stats]] and [[Active Calls]] count 

Data can be retrieved for '''Admin''', '''Reseller''', '''Simple User'''

 

=Usage=

* Call: /api/quickstats_get '''(from MOR X7)'''
* Methods: POST, GET (if allowed, not recomended)
 
===Parameters===

* [[MOR API hash construction | hash]] - SHA1 hash constructed using API_Secret_Key ([[MOR API hash construction | More described in Constructing hash]]). '''Required''' (if setting '''Disable hash checking''' is not checked).

Parameters which are '''included''' into hash:
* u - username for authentication. '''Required'''.
'''Note that u is included in to the HASH only if u is not an Admin'''
 

===Request===

If API Secret Key = secret

You send:

HTML POST: http://<SERVER_IP>/billing/api/quickstats_get?u=admin&hash=e5e9fa1ba31ecd1ae84f75caaa474f3a663f05f4

 

===Returns===

'''Success:''' Everything is ok. You get the list of calls if there are any:

<?xml version="1.0" encoding="UTF-8"?>
<page>
<quickstats>
<today>
<calls> Calls count </calls>
<duration> Billsec in seconds </duration>
<revenue> Revenue today</revenue>
<self_cost> Expenditure today</self_cost>
<profit> Difference of revenue and expences</profit>
<margin> profit's part in the sell price</margin>
</today>
<active_calls>
<total> Active Calls count </total>
<answered_calls> Answered Calls count </answered_calls>
</active_calls>
</quickstats>
</page>

'''Errors:'''

* <error>API Requests are disabled</error> – '''Allow API globally''' setting is unchecked
* <error>GET Requests are disabled</error> – '''Allow GET API''' setting is unchecked
* <error>Access Denied</error> – User with such a username cannot use this method or such a username does not exist in the database or it was not specified
* <error>Incorrect hash</error> – Hash was not correct. Check API_Secret_Key and order of parameters while concatenating the hash_string
* <error>Cannot connect to Elasticsearch</error> – data is not reachable

Example:

<status>
<error>API Requests are disabled</error>
</status>
 
=See also=

* [[MOR API]]

DID Management

2017-07-25T10:44:38Z

Reda:

= Description =

DID is an external number to have incoming calls to your VoIP network reach a particular device. (This is a very simplified explanation that will serve for the moment. For a more extensive explanation, please check [http://www.voip-info.org/wiki/view/DID here]).

'''VERY IMPORTANT RULE: DIDs in MOR MUST be in E.164 format.'''

You can reach window, with list of all DIDs, in '''SETTINGS –> Billing –> DIDs''':
 
[[File:Dids updated.png]]
 
User/Dial Plan and Device show who will answer when dialing this DID.

Clicking on User or Device brings you to their settings. If you click on the [[Image:callflow.png]] icon, you will go to the device's [[Call Flow]] window.

In this page you can
*[[DID_Management#Add_new_DID(s) | Add new DID(s)]]
*Reach [[DID_Management#DID_bulk_management | Bulk management]]
*Export DIDs to CSV
*Reach page to change DID [[DID Billing | Rates]]
*Update DID [[DID_Management#Settings | settings]]
*Search only by DID Owner, when using search field called ''Owner'', or search by either DID Owner or DID Reseller at once, when using search field called ''User''.

*Hide Terminated DIDs. When option "Hide Terminated DIDs" is checked, terminated dids will be hidden until option is unchecked. Clear search button or relogin will not clear the checked option.
* Search by User type.
* Search by inclusive Balance range (only for Owners).
* Search by User status (only for Owners).

 

= Status =
[[Image:dids2.png|right]]
Status is very important. For every just-created DID, the status is Free.

A DID can have several statuses:

* '''Free''' – this status means that the DID is free to be reserved for any user/device. You can also Terminate it.
* '''Reserved''' – the DID is reserved but NOT actually used for a user. "Reserved" is useful at the negotiation stage before signing a contract. When a user decides to sign up, we Activate the DID. We can also make the DID Free.
* '''Active''' – the DID is assigned to a Device and is functional. We can Close it.
* '''Closed''' – the DID is no longer functional, so that all calls going to this DID will get Hangup. One important feature of this state: when a DID is Closed, it will be closed for a set time (the default is 90 days) in case the user changes his mind and decides to use this DID again. This is useful when a user is not paying for services, as we can suspend the DID by using Closed. MOR will make it Free after the Closed period runs out. You can manually make it Free or Terminate this DID.
* '''Terminated''' – the DID is no longer used in MOR. It remains only for historical purposes. You can make it Free if you want.

 

= Add new DID(s) =

In the main DIDs window, if you want to add new DID(s), click on [[Image:add.png]] '''New DID''':

[[Image:dids5.png]]

In this window you can:

# Select DID(s) [[DID_Management#Details | details]]
# Add one DID or series of DIDs
# [[ DID_Import_from_CSV | Import DID(s) from CSV file]]
 
'''NOTE:''' You should select the Provider which sold you this DID. DID Provider is ONLY for informational purposes. If you do not know which Provider to assign - create dummy Provider to represent company from which you buy DID. If this is fake DID - assign any Provider you want. If your DID Provider has several IP addresses (as DIDWW) and you configured several Providers in MOR - assign ANY configured Provider.

 
== VIDEO: How to create a DID ==

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

 

==Details==

*'''Provider''' – DID Provider is ONLY for informational purposes. If you do not know which Provider to assign - create dummy Provider to represent company from which you buy DID. If this is fake DID - assign any Provider you want. If your DID Provider has several IP addresses (as DIDWW) and you configured several Providers in MOR - assign ANY configured Provider.

*'''Language''' – option to set language for voice prompts in the Asterisk Dial Plan

*'''Call limit''' – describes how many simultaneous calls DID can '''receive'''. 0 (zero) means that calls are unlimited.

*'''Comment''' – option to save some notes about DID.

*'''[[Sound files | Sound file]]''' – here you can add [[IVR Greeting for DID]]


*'''Grace Time''' – if call duration is less than Grace Time, it will not be accounted, for example: '''Grace Time''' = 3s, call duration <= 3s, then price for the call = 0


*'''Timeout Digit''' – the maximum amount of time permitted between digits when the user is typing in a number. When this timeout expires after the user has started to type in a number, the number will be considered complete, and will be interpreted (sent to the system). Works both with entering destination and ANI/PIN.


*'''Timeout Response''' – the maximum amount of time permitted for user to START entering a number. If the user does not begin typing a number in this amount of time, system will notify that nothing was entered. Once the user begins to type a number, system will wait for Digit Timeout to be reached, and Response Timeout has no effect no more.


*'''CallerID Name Prefix''' – option to add a CallerID Name prefix to the incoming CallerID.


*'''Tone zone''' – option to set tone zones. Tone zone is a different ring tone depending on destination (country).


*'''Tariff for Calling Card''' – option to set a tariff for DID which will be applied for a calling card. It will not be important what tariff is assigned for that card's group.

 

= Settings =

If you want to edit a DID's settings, click on the [[Image:edit.png]] icon.
 
[[Image:dids4.png]]
 
The above window is for Free DID. You can:

# Change [[DID_Management#Details | details]]
# [[DID_Management#Reserve_DID_for_User | Reserve DID for User]].
# [[DID_Management#Assign_to_Dial_Plan | Assign to Dial Plan]].
# Terminate a DID.

 

==Reserve DID for User==

When a DID is assigned to a Device (Reserve for User first), you have a few different choices:

[[Image:dids3.png]]

Here you can:

# Change [[DID_Management#Details | details]].
# Assign DID to device. Here you can select different Devices for the same user. For select Trunk Device is next section.
# Assign DID to Trunk. Here you can select different Trunk Devices for the same user.
# Stop a DID subscription and reserve the DID for 90 days (by default) to this user in case he changes his mind and wants to get the DID back.

 
==Assign to Dial Plan==

When DID is assigned to [[Dial_Plans | Dial Plan]], in DID settings you can:
# Change [[DID_Management#Details | details]].
# Make DID free.

When you have [[Quickforwards_rules | Quickforward Rule]] for this DID, in DID edit you will see additional notice:

[[Image:DID_edit_collisions_with_qf_rule.png‎]]

 
= Delete DID =

At first, mark it as "not used" (Free). Then terminate it. When you do, you will see [[Image:delete.png]] next to the DID in the main DID window. By clicking on it, you can delete the DID.

 
= DID bulk management =
In the main DIDs window, click [[Image:edit.png]] Bulk Management and you will be able to perform various actions with a series of DIDs:
 
[[Image:dids6.png]]
 
Here you can choose which DIDs to update and what to do:
*'''Update''' - option to change some of DID details, Reserve DID for User (only free DIDs can be reserved) or Make DID free.
*'''Delete''' - option to delete DIDs by Provider or make DIDs Free/Terminated/Closed.
*'''Manage rates''' - option to change Rates for [[DID Billing]].
*'''[[Assign DID to Trunk]]'''.

*'''Reserve for User''' - option to reserve DID for User (only free DIDs can be reserved).
*'''Assign Dial Plan''' - option for Assign DID to [[Dial_Plans | Dial Plan]]
 

= Allowing Users to route their DIDs =
Since '''MOR X5''' users are able to route their DID to a Device or an External Server .
This functionality can be enabled in '''SETTINGS -> Setup -> Visual''' by checking the 'Allow User to assign DID to Device:' setting.

Once the functionality is enabled, the user will be able to see an Edit icon, in his DIDs list.
 
[[File:Dids_list_with_did_routing.png‎]]
 

By pressing the icon, the user will be redirected to a page where he will be able to route his DID either to one of his MOR Devices, or to a Device on an external server (eg. SIP/370xxxxxx@123.123.123.123).
 
[[File:Did_routing_panel.png‎]]
 

=See Also=

*[[DID Billing]]
*[[DIDs Usage]]
*[[MOR_API_did_create | Create DID through API]]
*[[MOR_API_did_device_assign | Assign Device to DID through API]]
*[[MOR_API_did_device_unassign | Unassign Device from DID through API]]
*[[Providers#Provider_Grace_Time|Provider Grace Time]]
*[[Grace_time|Device Grace Time]]
*[[Example - Configuring DID to ring some Device]]
*[[DID is not working]]
*[[ DID_Import_from_CSV | Import DID(s) from CSV file]]

DID Management

2017-07-25T10:42:26Z

Reda:

DID Management

2017-07-25T10:37:59Z

Reda:

= Description =

DID is an external number to have incoming calls to your VoIP network reach a particular device. (This is a very simplified explanation that will serve for the moment. For a more extensive explanation, please check [http://www.voip-info.org/wiki/view/DID here]).

'''VERY IMPORTANT RULE: DIDs in MOR MUST be in E.164 format.'''

You can reach window, with list of all DIDs, in '''SETTINGS –> Billing –> DIDs''':
 
[[File:Dids updated.png]]
 
User/Dial Plan and Device show who will answer when dialing this DID.

Clicking on User or Device brings you to their settings. If you click on the [[Image:callflow.png]] icon, you will go to the device's [[Call Flow]] window.

In this page you can
*[[DID_Management#Add_new_DID(s) | Add new DID(s)]]
*Reach [[DID_Management#DID_bulk_management | Bulk management]]
*Export DIDs to CSV
*Reach page to change DID [[DID Billing | Rates]]
*Update DID [[DID_Management#Settings | settings]]
*Search only by DID Owner, when using search field called ''Owner'', or search by either DID Owner or DID Reseller at once, when using search field called ''User''.

*Hide Terminated DIDs. When option "Hide Terminated DIDs" is checked, terminated dids will be hidden until option is unchecked. Clear search button or relogin will not clear the checked option.
* Search by User type.
* Search by inclusive Balance range (only for Owners).
* Search by User status (only for Owners).

 

= Status =
[[Image:dids2.png|right]]
Status is very important. For every just-created DID, the status is Free.

A DID can have several statuses:

* '''Free''' – this status means that the DID is free to be reserved for any user/device. You can also Terminate it.
* '''Reserved''' – the DID is reserved but NOT actually used for a user. "Reserved" is useful at the negotiation stage before signing a contract. When a user decides to sign up, we Activate the DID. We can also make the DID Free.
* '''Active''' – the DID is assigned to a Device and is functional. We can Close it.
* '''Closed''' – the DID is no longer functional, so that all calls going to this DID will get Hangup. One important feature of this state: when a DID is Closed, it will be closed for a set time (the default is 90 days) in case the user changes his mind and decides to use this DID again. This is useful when a user is not paying for services, as we can suspend the DID by using Closed. MOR will make it Free after the Closed period runs out. You can manually make it Free or Terminate this DID.
* '''Terminated''' – the DID is no longer used in MOR. It remains only for historical purposes. You can make it Free if you want.

 

= Add new DID(s) =

In the main DIDs window, if you want to add new DID(s), click on [[Image:add.png]] '''New DID''':

[[Image:dids5.png]]

In this window you can:

# Select DID(s) [[DID_Management#Details | details]]
# Add one DID or series of DIDs
# [[ DID_Import_from_CSV | Import DID(s) from CSV file]]
 
Example of DIDs list in CSV file:

442012345678
442087654321
442054987123

'''NOTE:''' You should select the Provider which sold you this DID. DID Provider is ONLY for informational purposes. If you do not know which Provider to assign - create dummy Provider to represent company from which you buy DID. If this is fake DID - assign any Provider you want. If your DID Provider has several IP addresses (as DIDWW) and you configured several Providers in MOR - assign ANY configured Provider.

 
== VIDEO: How to create a DID ==

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

 

==Details==

*'''Provider''' – DID Provider is ONLY for informational purposes. If you do not know which Provider to assign - create dummy Provider to represent company from which you buy DID. If this is fake DID - assign any Provider you want. If your DID Provider has several IP addresses (as DIDWW) and you configured several Providers in MOR - assign ANY configured Provider.

*'''Language''' – option to set language for voice prompts in the Asterisk Dial Plan

*'''Call limit''' – describes how many simultaneous calls DID can '''receive'''. 0 (zero) means that calls are unlimited.

*'''Comment''' – option to save some notes about DID.

*'''[[Sound files | Sound file]]''' – here you can add [[IVR Greeting for DID]]


*'''Grace Time''' – if call duration is less than Grace Time, it will not be accounted, for example: '''Grace Time''' = 3s, call duration <= 3s, then price for the call = 0


*'''Timeout Digit''' – the maximum amount of time permitted between digits when the user is typing in a number. When this timeout expires after the user has started to type in a number, the number will be considered complete, and will be interpreted (sent to the system). Works both with entering destination and ANI/PIN.


*'''Timeout Response''' – the maximum amount of time permitted for user to START entering a number. If the user does not begin typing a number in this amount of time, system will notify that nothing was entered. Once the user begins to type a number, system will wait for Digit Timeout to be reached, and Response Timeout has no effect no more.


*'''CallerID Name Prefix''' – option to add a CallerID Name prefix to the incoming CallerID.


*'''Tone zone''' – option to set tone zones. Tone zone is a different ring tone depending on destination (country).


*'''Tariff for Calling Card''' – option to set a tariff for DID which will be applied for a calling card. It will not be important what tariff is assigned for that card's group.

 

= Settings =

If you want to edit a DID's settings, click on the [[Image:edit.png]] icon.
 
[[Image:dids4.png]]
 
The above window is for Free DID. You can:

# Change [[DID_Management#Details | details]]
# [[DID_Management#Reserve_DID_for_User | Reserve DID for User]].
# [[DID_Management#Assign_to_Dial_Plan | Assign to Dial Plan]].
# Terminate a DID.

 

==Reserve DID for User==

When a DID is assigned to a Device (Reserve for User first), you have a few different choices:

[[Image:dids3.png]]

Here you can:

# Change [[DID_Management#Details | details]].
# Assign DID to device. Here you can select different Devices for the same user. For select Trunk Device is next section.
# Assign DID to Trunk. Here you can select different Trunk Devices for the same user.
# Stop a DID subscription and reserve the DID for 90 days (by default) to this user in case he changes his mind and wants to get the DID back.

 
==Assign to Dial Plan==

When DID is assigned to [[Dial_Plans | Dial Plan]], in DID settings you can:
# Change [[DID_Management#Details | details]].
# Make DID free.

When you have [[Quickforwards_rules | Quickforward Rule]] for this DID, in DID edit you will see additional notice:

[[Image:DID_edit_collisions_with_qf_rule.png‎]]

 
= Delete DID =

At first, mark it as "not used" (Free). Then terminate it. When you do, you will see [[Image:delete.png]] next to the DID in the main DID window. By clicking on it, you can delete the DID.

 
= DID bulk management =
In the main DIDs window, click [[Image:edit.png]] Bulk Management and you will be able to perform various actions with a series of DIDs:
 
[[Image:dids6.png]]
 
Here you can choose which DIDs to update and what to do:
*'''Update''' - option to change some of DID details, Reserve DID for User (only free DIDs can be reserved) or Make DID free.
*'''Delete''' - option to delete DIDs by Provider or make DIDs Free/Terminated/Closed.
*'''Manage rates''' - option to change Rates for [[DID Billing]].
*'''[[Assign DID to Trunk]]'''.

*'''Reserve for User''' - option to reserve DID for User (only free DIDs can be reserved).
*'''Assign Dial Plan''' - option for Assign DID to [[Dial_Plans | Dial Plan]]
 

= Allowing Users to route their DIDs =
Since '''MOR X5''' users are able to route their DID to a Device or an External Server .
This functionality can be enabled in '''SETTINGS -> Setup -> Visual''' by checking the 'Allow User to assign DID to Device:' setting.

Once the functionality is enabled, the user will be able to see an Edit icon, in his DIDs list.
 
[[File:Dids_list_with_did_routing.png‎]]
 

By pressing the icon, the user will be redirected to a page where he will be able to route his DID either to one of his MOR Devices, or to a Device on an external server (eg. SIP/370xxxxxx@123.123.123.123).
 
[[File:Did_routing_panel.png‎]]
 

=See Also=

*[[DID Billing]]
*[[DIDs Usage]]
*[[MOR_API_did_create | Create DID through API]]
*[[MOR_API_did_device_assign | Assign Device to DID through API]]
*[[MOR_API_did_device_unassign | Unassign Device from DID through API]]
*[[Providers#Provider_Grace_Time|Provider Grace Time]]
*[[Grace_time|Device Grace Time]]
*[[Example - Configuring DID to ring some Device]]
*[[DID is not working]]

DID Management

2017-07-25T10:36:28Z

Reda:

= Description =

DID is an external number to have incoming calls to your VoIP network reach a particular device. (This is a very simplified explanation that will serve for the moment. For a more extensive explanation, please check [http://www.voip-info.org/wiki/view/DID here]).

'''VERY IMPORTANT RULE: DIDs in MOR MUST be in E.164 format.'''

You can reach window, with list of all DIDs, in '''SETTINGS –> Billing –> DIDs''':
 
[[File:Dids updated.png]]
 
User/Dial Plan and Device show who will answer when dialing this DID.

Clicking on User or Device brings you to their settings. If you click on the [[Image:callflow.png]] icon, you will go to the device's [[Call Flow]] window.

In this page you can
*[[DID_Management#Add_new_DID(s) | Add new DID(s)]]
*Reach [[DID_Management#DID_bulk_management | Bulk management]]
*Export DIDs to CSV
*Reach page to change DID [[DID Billing | Rates]]
*Update DID [[DID_Management#Settings | settings]]
*Search only by DID Owner, when using search field called ''Owner'', or search by either DID Owner or DID Reseller at once, when using search field called ''User''.

*Hide Terminated DIDs. When option "Hide Terminated DIDs" is checked, terminated dids will be hidden until option is unchecked. Clear search button or relogin will not clear the checked option.
* Search by User type.
* Search by inclusive Balance range (only for Owners).
* Search by User status (only for Owners).

 

= Status =
[[Image:dids2.png|right]]
Status is very important. For every just-created DID, the status is Free.

A DID can have several statuses:

* '''Free''' – this status means that the DID is free to be reserved for any user/device. You can also Terminate it.
* '''Reserved''' – the DID is reserved but NOT actually used for a user. "Reserved" is useful at the negotiation stage before signing a contract. When a user decides to sign up, we Activate the DID. We can also make the DID Free.
* '''Active''' – the DID is assigned to a Device and is functional. We can Close it.
* '''Closed''' – the DID is no longer functional, so that all calls going to this DID will get Hangup. One important feature of this state: when a DID is Closed, it will be closed for a set time (the default is 90 days) in case the user changes his mind and decides to use this DID again. This is useful when a user is not paying for services, as we can suspend the DID by using Closed. MOR will make it Free after the Closed period runs out. You can manually make it Free or Terminate this DID.
* '''Terminated''' – the DID is no longer used in MOR. It remains only for historical purposes. You can make it Free if you want.

 

= Add new DID(s) =

In the main DIDs window, if you want to add new DID(s), click on [[Image:add.png]] '''New DID''':

[[Image:dids5.png]]

In this window you can:

# Select DID(s) [[DID_Management#Details | details]]
# Add one DID or series of DIDs
# [[ DID_Import_from_CSV | Import DID(s) from CSV file]]
 
Example of DIDs list in CSV file:

442012345678
442087654321
442054987123

'''NOTE:''' You should select the Provider which sold you this DID. DID Provider is ONLY for informational purposes. If you do not know which Provider to assign - create dummy Provider to represent company from which you buy DID. If this is fake DID - assign any Provider you want. If your DID Provider has several IP addresses (as DIDWW) and you configured several Providers in MOR - assign ANY configured Provider.

 
== VIDEO: How to create a DID ==

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

 

= Settings =

If you want to edit a DID's settings, click on the [[Image:edit.png]] icon.
 
[[Image:dids4.png]]
 
The above window is for Free DID. You can:

# Change [[DID_Management#Details | details]]
# [[DID_Management#Reserve_DID_for_User | Reserve DID for User]].
# [[DID_Management#Assign_to_Dial_Plan | Assign to Dial Plan]].
# Terminate a DID.

 

==Details==

*'''Provider''' – DID Provider is ONLY for informational purposes. If you do not know which Provider to assign - create dummy Provider to represent company from which you buy DID. If this is fake DID - assign any Provider you want. If your DID Provider has several IP addresses (as DIDWW) and you configured several Providers in MOR - assign ANY configured Provider.

*'''Language''' – option to set language for voice prompts in the Asterisk Dial Plan

*'''Call limit''' – describes how many simultaneous calls DID can '''receive'''. 0 (zero) means that calls are unlimited.

*'''Comment''' – option to save some notes about DID.

*'''[[Sound files | Sound file]]''' – here you can add [[IVR Greeting for DID]]


*'''Grace Time''' – if call duration is less than Grace Time, it will not be accounted, for example: '''Grace Time''' = 3s, call duration <= 3s, then price for the call = 0


*'''Timeout Digit''' – the maximum amount of time permitted between digits when the user is typing in a number. When this timeout expires after the user has started to type in a number, the number will be considered complete, and will be interpreted (sent to the system). Works both with entering destination and ANI/PIN.


*'''Timeout Response''' – the maximum amount of time permitted for user to START entering a number. If the user does not begin typing a number in this amount of time, system will notify that nothing was entered. Once the user begins to type a number, system will wait for Digit Timeout to be reached, and Response Timeout has no effect no more.


*'''CallerID Name Prefix''' – option to add a CallerID Name prefix to the incoming CallerID.


*'''Tone zone''' – option to set tone zones. Tone zone is a different ring tone depending on destination (country).


*'''Tariff for Calling Card''' – option to set a tariff for DID which will be applied for a calling card. It will not be important what tariff is assigned for that card's group.

 
==Reserve DID for User==

When a DID is assigned to a Device (Reserve for User first), you have a few different choices:

[[Image:dids3.png]]

Here you can:

# Change [[DID_Management#Details | details]].
# Assign DID to device. Here you can select different Devices for the same user. For select Trunk Device is next section.
# Assign DID to Trunk. Here you can select different Trunk Devices for the same user.
# Stop a DID subscription and reserve the DID for 90 days (by default) to this user in case he changes his mind and wants to get the DID back.

 
==Assign to Dial Plan==

When DID is assigned to [[Dial_Plans | Dial Plan]], in DID settings you can:
# Change [[DID_Management#Details | details]].
# Make DID free.

When you have [[Quickforwards_rules | Quickforward Rule]] for this DID, in DID edit you will see additional notice:

[[Image:DID_edit_collisions_with_qf_rule.png‎]]

 
= Delete DID =

At first, mark it as "not used" (Free). Then terminate it. When you do, you will see [[Image:delete.png]] next to the DID in the main DID window. By clicking on it, you can delete the DID.

 
= DID bulk management =
In the main DIDs window, click [[Image:edit.png]] Bulk Management and you will be able to perform various actions with a series of DIDs:
 
[[Image:dids6.png]]
 
Here you can choose which DIDs to update and what to do:
*'''Update''' - option to change some of DID details, Reserve DID for User (only free DIDs can be reserved) or Make DID free.
*'''Delete''' - option to delete DIDs by Provider or make DIDs Free/Terminated/Closed.
*'''Manage rates''' - option to change Rates for [[DID Billing]].
*'''[[Assign DID to Trunk]]'''.

*'''Reserve for User''' - option to reserve DID for User (only free DIDs can be reserved).
*'''Assign Dial Plan''' - option for Assign DID to [[Dial_Plans | Dial Plan]]
 

= Allowing Users to route their DIDs =
Since '''MOR X5''' users are able to route their DID to a Device or an External Server .
This functionality can be enabled in '''SETTINGS -> Setup -> Visual''' by checking the 'Allow User to assign DID to Device:' setting.

Once the functionality is enabled, the user will be able to see an Edit icon, in his DIDs list.
 
[[File:Dids_list_with_did_routing.png‎]]
 

By pressing the icon, the user will be redirected to a page where he will be able to route his DID either to one of his MOR Devices, or to a Device on an external server (eg. SIP/370xxxxxx@123.123.123.123).
 
[[File:Did_routing_panel.png‎]]
 

=See Also=

*[[DID Billing]]
*[[DIDs Usage]]
*[[MOR_API_did_create | Create DID through API]]
*[[MOR_API_did_device_assign | Assign Device to DID through API]]
*[[MOR_API_did_device_unassign | Unassign Device from DID through API]]
*[[Providers#Provider_Grace_Time|Provider Grace Time]]
*[[Grace_time|Device Grace Time]]
*[[Example - Configuring DID to ring some Device]]
*[[DID is not working]]

DID Management

2017-07-25T10:34:02Z

Reda:

= Description =

DID is an external number to have incoming calls to your VoIP network reach a particular device. (This is a very simplified explanation that will serve for the moment. For a more extensive explanation, please check [http://www.voip-info.org/wiki/view/DID here]).

'''VERY IMPORTANT RULE: DIDs in MOR MUST be in E.164 format.'''

You can reach window, with list of all DIDs, in '''SETTINGS –> Billing –> DIDs''':
 
[[File:Dids updated.png]]
 
User/Dial Plan and Device show who will answer when dialing this DID.

Clicking on User or Device brings you to their settings. If you click on the [[Image:callflow.png]] icon, you will go to the device's [[Call Flow]] window.

In this page you can
*[[DID_Management#Add_new_DID(s) | Add new DID(s)]]
*Reach [[DID_Management#DID_bulk_management | Bulk management]]
*Export DIDs to CSV
*Reach page to change DID [[DID Billing | Rates]]
*Update DID [[DID_Management#Settings | settings]]
*Search only by DID Owner, when using search field called ''Owner'', or search by either DID Owner or DID Reseller at once, when using search field called ''User''.

*Hide Terminated DIDs. When option "Hide Terminated DIDs" is checked, terminated dids will be hidden until option is unchecked. Clear search button or relogin will not clear the checked option.
* Search by User type.
* Search by inclusive Balance range (only for Owners).
* Search by User status (only for Owners).

 

= Status =
[[Image:dids2.png|right]]
Status is very important. For every just-created DID, the status is Free.

A DID can have several statuses:

* '''Free''' – this status means that the DID is free to be reserved for any user/device. You can also Terminate it.
* '''Reserved''' – the DID is reserved but NOT actually used for a user. "Reserved" is useful at the negotiation stage before signing a contract. When a user decides to sign up, we Activate the DID. We can also make the DID Free.
* '''Active''' – the DID is assigned to a Device and is functional. We can Close it.
* '''Closed''' – the DID is no longer functional, so that all calls going to this DID will get Hangup. One important feature of this state: when a DID is Closed, it will be closed for a set time (the default is 90 days) in case the user changes his mind and decides to use this DID again. This is useful when a user is not paying for services, as we can suspend the DID by using Closed. MOR will make it Free after the Closed period runs out. You can manually make it Free or Terminate this DID.
* '''Terminated''' – the DID is no longer used in MOR. It remains only for historical purposes. You can make it Free if you want.

 

= Add new DID(s) =

In the main DIDs window, if you want to add new DID(s), click on [[Image:add.png]] '''New DID''':

[[Image:dids5.png]]

In this window you can:

# Select DID(s) [[DID_Management#Details | details]]
# Add one DID or series of DIDs
# Import DID(s) from CSV file
 
Example of DIDs list in CSV file:

442012345678
442087654321
442054987123

'''NOTE:''' You should select the Provider which sold you this DID. DID Provider is ONLY for informational purposes. If you do not know which Provider to assign - create dummy Provider to represent company from which you buy DID. If this is fake DID - assign any Provider you want. If your DID Provider has several IP addresses (as DIDWW) and you configured several Providers in MOR - assign ANY configured Provider.

 
== VIDEO: How to create a DID ==

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

 

= Settings =

If you want to edit a DID's settings, click on the [[Image:edit.png]] icon.
 
[[Image:dids4.png]]
 
The above window is for Free DID. You can:

# Change [[DID_Management#Details | details]]
# [[DID_Management#Reserve_DID_for_User | Reserve DID for User]].
# [[DID_Management#Assign_to_Dial_Plan | Assign to Dial Plan]].
# Terminate a DID.

 

==Details==

*'''Provider''' – DID Provider is ONLY for informational purposes. If you do not know which Provider to assign - create dummy Provider to represent company from which you buy DID. If this is fake DID - assign any Provider you want. If your DID Provider has several IP addresses (as DIDWW) and you configured several Providers in MOR - assign ANY configured Provider.

*'''Language''' – option to set language for voice prompts in the Asterisk Dial Plan

*'''Call limit''' – describes how many simultaneous calls DID can '''receive'''. 0 (zero) means that calls are unlimited.

*'''Comment''' – option to save some notes about DID.

*'''[[Sound files | Sound file]]''' – here you can add [[IVR Greeting for DID]]


*'''Grace Time''' – if call duration is less than Grace Time, it will not be accounted, for example: '''Grace Time''' = 3s, call duration <= 3s, then price for the call = 0


*'''Timeout Digit''' – the maximum amount of time permitted between digits when the user is typing in a number. When this timeout expires after the user has started to type in a number, the number will be considered complete, and will be interpreted (sent to the system). Works both with entering destination and ANI/PIN.


*'''Timeout Response''' – the maximum amount of time permitted for user to START entering a number. If the user does not begin typing a number in this amount of time, system will notify that nothing was entered. Once the user begins to type a number, system will wait for Digit Timeout to be reached, and Response Timeout has no effect no more.


*'''CallerID Name Prefix''' – option to add a CallerID Name prefix to the incoming CallerID.


*'''Tone zone''' – option to set tone zones. Tone zone is a different ring tone depending on destination (country).


*'''Tariff for Calling Card''' – option to set a tariff for DID which will be applied for a calling card. It will not be important what tariff is assigned for that card's group.

 
==Reserve DID for User==

When a DID is assigned to a Device (Reserve for User first), you have a few different choices:

[[Image:dids3.png]]

Here you can:

# Change [[DID_Management#Details | details]].
# Assign DID to device. Here you can select different Devices for the same user. For select Trunk Device is next section.
# Assign DID to Trunk. Here you can select different Trunk Devices for the same user.
# Stop a DID subscription and reserve the DID for 90 days (by default) to this user in case he changes his mind and wants to get the DID back.

 
==Assign to Dial Plan==

When DID is assigned to [[Dial_Plans | Dial Plan]], in DID settings you can:
# Change [[DID_Management#Details | details]].
# Make DID free.

When you have [[Quickforwards_rules | Quickforward Rule]] for this DID, in DID edit you will see additional notice:

[[Image:DID_edit_collisions_with_qf_rule.png‎]]

 
= Delete DID =

At first, mark it as "not used" (Free). Then terminate it. When you do, you will see [[Image:delete.png]] next to the DID in the main DID window. By clicking on it, you can delete the DID.

 
= DID bulk management =
In the main DIDs window, click [[Image:edit.png]] Bulk Management and you will be able to perform various actions with a series of DIDs:
 
[[Image:dids6.png]]
 
Here you can choose which DIDs to update and what to do:
*'''Update''' - option to change some of DID details, Reserve DID for User (only free DIDs can be reserved) or Make DID free.
*'''Delete''' - option to delete DIDs by Provider or make DIDs Free/Terminated/Closed.
*'''Manage rates''' - option to change Rates for [[DID Billing]].
*'''[[Assign DID to Trunk]]'''.

*'''Reserve for User''' - option to reserve DID for User (only free DIDs can be reserved).
*'''Assign Dial Plan''' - option for Assign DID to [[Dial_Plans | Dial Plan]]
 

= Allowing Users to route their DIDs =
Since '''MOR X5''' users are able to route their DID to a Device or an External Server .
This functionality can be enabled in '''SETTINGS -> Setup -> Visual''' by checking the 'Allow User to assign DID to Device:' setting.

Once the functionality is enabled, the user will be able to see an Edit icon, in his DIDs list.
 
[[File:Dids_list_with_did_routing.png‎]]
 

By pressing the icon, the user will be redirected to a page where he will be able to route his DID either to one of his MOR Devices, or to a Device on an external server (eg. SIP/370xxxxxx@123.123.123.123).
 
[[File:Did_routing_panel.png‎]]
 

=See Also=

*[[DID Billing]]
*[[DIDs Usage]]
*[[MOR_API_did_create | Create DID through API]]
*[[MOR_API_did_device_assign | Assign Device to DID through API]]
*[[MOR_API_did_device_unassign | Unassign Device from DID through API]]
*[[Providers#Provider_Grace_Time|Provider Grace Time]]
*[[Grace_time|Device Grace Time]]
*[[Example - Configuring DID to ring some Device]]
*[[DID is not working]]

DID Management

2017-07-25T10:33:27Z

Reda:

= Description =

DID is an external number to have incoming calls to your VoIP network reach a particular device. (This is a very simplified explanation that will serve for the moment. For a more extensive explanation, please check [http://www.voip-info.org/wiki/view/DID here]).

'''VERY IMPORTANT RULE: DIDs in MOR MUST be in E.164 format.'''

You can reach window, with list of all DIDs, in '''SETTINGS –> Billing –> DIDs''':
 
[[File:Dids updated.png]]
 
User/Dial Plan and Device show who will answer when dialing this DID.

Clicking on User or Device brings you to their settings. If you click on the [[Image:callflow.png]] icon, you will go to the device's [[Call Flow]] window.

In this page you can
*[[DID_Management#Add_new_DID(s) | Add new DID(s)]]
*Reach [[DID_Management#DID_bulk_management | Bulk management]]
*Export DIDs to CSV
*Reach page to change DID [[DID Billing | Rates]]
*Update DID [[DID_Management#Settings | settings]]
*Search only by DID Owner, when using search field called ''Owner'', or search by either DID Owner or DID Reseller at once, when using search field called ''User''.

*Hide Terminated DIDs. When option "Hide Terminated DIDs" is checked, terminated dids will be hidden until option is unchecked. Clear search button or relogin will not clear the checked option.
* Search by User type.
* Search by inclusive Balance range (only for Owners).
* Search by User status (only for Owners).

 

= Status =
[[Image:dids2.png|right]]
Status is very important. For every just-created DID, the status is Free.

A DID can have several statuses:

* '''Free''' – this status means that the DID is free to be reserved for any user/device. You can also Terminate it.
* '''Reserved''' – the DID is reserved but NOT actually used for a user. "Reserved" is useful at the negotiation stage before signing a contract. When a user decides to sign up, we Activate the DID. We can also make the DID Free.
* '''Active''' – the DID is assigned to a Device and is functional. We can Close it.
* '''Closed''' – the DID is no longer functional, so that all calls going to this DID will get Hangup. One important feature of this state: when a DID is Closed, it will be closed for a set time (the default is 90 days) in case the user changes his mind and decides to use this DID again. This is useful when a user is not paying for services, as we can suspend the DID by using Closed. MOR will make it Free after the Closed period runs out. You can manually make it Free or Terminate this DID.
* '''Terminated''' – the DID is no longer used in MOR. It remains only for historical purposes. You can make it Free if you want.

 

= Add new DID(s) =

In the main DIDs window, if you want to add new DID(s), click on [[Image:add.png]] '''New DID''':

[[Image:dids5.png]]

In this window you can:

# Select DID(s) [[DID_Management#Details | details]]
# Add one DID or series of DIDs
# Import DID(s) from CSV file
 
Example of DIDs list in CSV file:

442012345678
442087654321
442054987123

'''NOTE:''' You should select the Provider which sold you this DID. DID Provider is ONLY for informational purposes. If you do not know which Provider to assign - create dummy Provider to represent company from which you buy DID. If this is fake DID - assign any Provider you want. If your DID Provider has several IP addresses (as DIDWW) and you configured several Providers in MOR - assign ANY configured Provider.

 
== VIDEO: How to create a DID ==

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

 

= Settings =

If you want to edit a DID's settings, click on the [[Image:edit.png]] icon.
 
[[Image:dids4.png]]
 
The above window is for Free DID. You can:

# Change [[DID_Management#Details | details]]
# [[DID_Management#Reserve_DID_for_User | Reserve DID for User]].
# [[DID_Management#Assign_to_Dial_Plan | Assign to Dial Plan]].
# Terminate a DID.

 

==Details==

*'''Provider''' – DID Provider is ONLY for informational purposes. If you do not know which Provider to assign - create dummy Provider to represent company from which you buy DID. If this is fake DID - assign any Provider you want. If your DID Provider has several IP addresses (as DIDWW) and you configured several Providers in MOR - assign ANY configured Provider.

*'''Language''' – option to set language for voice prompts in the Asterisk Dial Plan

*'''Call limit''' – describes how many simultaneous calls DID can '''receive'''. 0 (zero) means that calls are unlimited.

*'''Comment''' – option to save some notes about DID.

*'''[[Sound files | Sound file]]''' – here you can add [[IVR Greeting for DID]]


*'''Grace Time''' – if call duration is less than Grace Time, it will not be accounted, for example: '''Grace Time''' = 3s, call duration <= 3s, then price for the call = 0


*'''Timeout Digit''' – the maximum amount of time permitted between digits when the user is typing in a number. When this timeout expires after the user has started to type in a number, the number will be considered complete, and will be interpreted (sent to the system). Works both with entering destination and ANI/PIN.


*'''Timeout Response''' – the maximum amount of time permitted for user to START entering a number. If the user does not begin typing a number in this amount of time, system will notify that nothing was entered. Once the user begins to type a number, system will wait for Digit Timeout to be reached, and Response Timeout has no effect no more.


*'''CallerID Name Prefix''' – option to add a CallerID Name prefix to the incoming CallerID.


*'''Tone zone''' – option to set tone zones. Tone zone is a different ring tone depending on destination (country).


*'''Tariff for Calling Card''' – option to set a tariff for DID which will be applied for a calling card. It will not be important what tariff is assigned for that card's group.

 
==Reserve DID for User==

When a DID is assigned to a Device (Reserve for User first), you have a few different choices:

[[Image:dids3.png]]

Here you can:

# Change [[DID_Management#Details | details]].
# Assign DID to device. Here you can select different Devices for the same user. For select Trunk Device is next section.
# Assign DID to Trunk. Here you can select different Trunk Devices for the same user.
# Stop a DID subscription and reserve the DID for 90 days (by default) to this user in case he changes his mind and wants to get the DID back.

 
==Assign to Dial Plan==

When DID is assigned to [[Dial_Plans | Dial Plan]], in DID settings you can:
# Change [[DID_Management#Details | details]].
# Make DID free.

When you have [[Quickforwards_rules | Quickforward Rule]] for this DID, in DID edit you will see additional notice:

[[Image:DID_edit_collisions_with_qf_rule.png‎]]

 
= Delete DID =

At first, mark it as "not used" (Free). Then terminate it. When you do, you will see [[Image:delete.png]] next to the DID in the main DID window. By clicking on it, you can delete the DID.

 
= DID bulk management =
In the main DIDs window, click [[Image:edit.png]] Bulk Management and you will be able to perform various actions with a series of DIDs:
 
[[Image:dids6.png]]
 
Here you can choose which DIDs to update and what to do:
*'''Update''' - option to change some of DID details, Reserve DID for User (only free DIDs can be reserved) or Make DID free.
*'''Delete''' - option to delete DIDs by Provider or make DIDs Free/Terminated/Closed.
*'''Manage rates''' - option to change Rates for [[DID Billing]].
*'''[[Assign DID to Trunk]]'''.

*'''Reserve for User''' - option to reserve DID for User (only free DIDs can be reserved).
*'''Assign Dial Plan''' - option for Assign DID to [[Dial_Plans | Dial Plan]]
 

= Allowing Users to route their DIDs =
Since '''MOR X5''' users are able to route their DID to a Device or an External Server .
This functionality can be enabled in '''SETTINGS -> Setup -> Visual''' by checking the 'Allow User to assign DID to Device:' setting.

Once the functionality is enabled, the user will be able to see an Edit icon, in his DIDs list.
 
[[File:Dids_list_with_did_routing.png‎]]
 

By pressing the icon, the user will be redirected to a page where he will be able to route his DID either to one of his MOR Devices, or to a Device on an external server (eg. SIP/370xxxxxx@123.123.123.123).
 
[[File:Did_routing_panel.png‎]]
 

=See Also=

*[[DID Billing]]
*[[DIDs Usage]]
*[[MOR_API_did_create | Create DID through API]]
*[[MOR_API_did_device_assign | Assign Device to DID through API]]
*[[MOR_API_did_device_unassign | Unassign Device from DID through API]]
*[[Providers#Provider_Grace_Time|Provider Grace Time]]
*[[Grace_time|Device Grace Time]]
*[[Example - Configuring DID to ring some Device]]
*[[DID is not working]]

DID Management

2017-07-25T10:32:40Z

Reda:

= Description =

DID is an external number to have incoming calls to your VoIP network reach a particular device. (This is a very simplified explanation that will serve for the moment. For a more extensive explanation, please check [http://www.voip-info.org/wiki/view/DID here]).

'''VERY IMPORTANT RULE: DIDs in MOR MUST be in E.164 format.'''

You can reach window, with list of all DIDs, in '''SETTINGS –> Billing –> DIDs''':
 
[[File:Dids updated.png]]
 
User/Dial Plan and Device show who will answer when dialing this DID.

Clicking on User or Device brings you to their settings. If you click on the [[Image:callflow.png]] icon, you will go to the device's [[Call Flow]] window.

In this page you can
*[[DID_Management#Add_new_DID(s) | Add new DID(s)]]
*Reach [[DID_Management#DID_bulk_management | Bulk management]]
*Export DIDs to CSV
*Reach page to change DID [[DID Billing | Rates]]
*Update DID [[DID_Management#Settings | settings]]
*Search only by DID Owner, when using search field called ''Owner'', or search by either DID Owner or DID Reseller at once, when using search field called ''User''.

*Hide Terminated DIDs. When option "Hide Terminated DIDs" is checked, terminated dids will be hidden until option is unchecked. Clear search button or relogin will not clear the checked option.
* Search by User type.
* Search by inclusive Balance range (only for Owners).
* Search by User status (only for Owners).

 

= Status =
[[Image:dids2.png|right]]
Status is very important. For every just-created DID, the status is Free.

A DID can have several statuses:

* '''Free''' – this status means that the DID is free to be reserved for any user/device. You can also Terminate it.
* '''Reserved''' – the DID is reserved but NOT actually used for a user. "Reserved" is useful at the negotiation stage before signing a contract. When a user decides to sign up, we Activate the DID. We can also make the DID Free.
* '''Active''' – the DID is assigned to a Device and is functional. We can Close it.
* '''Closed''' – the DID is no longer functional, so that all calls going to this DID will get Hangup. One important feature of this state: when a DID is Closed, it will be closed for a set time (the default is 90 days) in case the user changes his mind and decides to use this DID again. This is useful when a user is not paying for services, as we can suspend the DID by using Closed. MOR will make it Free after the Closed period runs out. You can manually make it Free or Terminate this DID.
* '''Terminated''' – the DID is no longer used in MOR. It remains only for historical purposes. You can make it Free if you want.

 

= Add new DID(s) =

In the main DIDs window, if you want to add new DID(s), click on [[Image:add.png]] '''New DID''':

[[Image:dids5.png]]

In this window you can:

# Select DID(s) [[DID_Management#Details | details]]
# Add one DID or series of DIDs
# Import DID(s) from CSV file

 

Example of DIDs list in CSV file:

442012345678
442087654321
442054987123

'''NOTE:''' You should select the Provider which sold you this DID. DID Provider is ONLY for informational purposes. If you do not know which Provider to assign - create dummy Provider to represent company from which you buy DID. If this is fake DID - assign any Provider you want. If your DID Provider has several IP addresses (as DIDWW) and you configured several Providers in MOR - assign ANY configured Provider.

 
== VIDEO: How to create a DID ==

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

 

= Settings =

If you want to edit a DID's settings, click on the [[Image:edit.png]] icon.
 
[[Image:dids4.png]]
 
The above window is for Free DID. You can:

# Change [[DID_Management#Details | details]]
# [[DID_Management#Reserve_DID_for_User | Reserve DID for User]].
# [[DID_Management#Assign_to_Dial_Plan | Assign to Dial Plan]].
# Terminate a DID.

 

==Details==

*'''Provider''' – DID Provider is ONLY for informational purposes. If you do not know which Provider to assign - create dummy Provider to represent company from which you buy DID. If this is fake DID - assign any Provider you want. If your DID Provider has several IP addresses (as DIDWW) and you configured several Providers in MOR - assign ANY configured Provider.

*'''Language''' – option to set language for voice prompts in the Asterisk Dial Plan

*'''Call limit''' – describes how many simultaneous calls DID can '''receive'''. 0 (zero) means that calls are unlimited.

*'''Comment''' – option to save some notes about DID.

*'''[[Sound files | Sound file]]''' – here you can add [[IVR Greeting for DID]]


*'''Grace Time''' – if call duration is less than Grace Time, it will not be accounted, for example: '''Grace Time''' = 3s, call duration <= 3s, then price for the call = 0


*'''Timeout Digit''' – the maximum amount of time permitted between digits when the user is typing in a number. When this timeout expires after the user has started to type in a number, the number will be considered complete, and will be interpreted (sent to the system). Works both with entering destination and ANI/PIN.


*'''Timeout Response''' – the maximum amount of time permitted for user to START entering a number. If the user does not begin typing a number in this amount of time, system will notify that nothing was entered. Once the user begins to type a number, system will wait for Digit Timeout to be reached, and Response Timeout has no effect no more.


*'''CallerID Name Prefix''' – option to add a CallerID Name prefix to the incoming CallerID.


*'''Tone zone''' – option to set tone zones. Tone zone is a different ring tone depending on destination (country).


*'''Tariff for Calling Card''' – option to set a tariff for DID which will be applied for a calling card. It will not be important what tariff is assigned for that card's group.

 
==Reserve DID for User==

When a DID is assigned to a Device (Reserve for User first), you have a few different choices:

[[Image:dids3.png]]

Here you can:

# Change [[DID_Management#Details | details]].
# Assign DID to device. Here you can select different Devices for the same user. For select Trunk Device is next section.
# Assign DID to Trunk. Here you can select different Trunk Devices for the same user.
# Stop a DID subscription and reserve the DID for 90 days (by default) to this user in case he changes his mind and wants to get the DID back.

 
==Assign to Dial Plan==

When DID is assigned to [[Dial_Plans | Dial Plan]], in DID settings you can:
# Change [[DID_Management#Details | details]].
# Make DID free.

When you have [[Quickforwards_rules | Quickforward Rule]] for this DID, in DID edit you will see additional notice:

[[Image:DID_edit_collisions_with_qf_rule.png‎]]

 
= Delete DID =

At first, mark it as "not used" (Free). Then terminate it. When you do, you will see [[Image:delete.png]] next to the DID in the main DID window. By clicking on it, you can delete the DID.

 
= DID bulk management =
In the main DIDs window, click [[Image:edit.png]] Bulk Management and you will be able to perform various actions with a series of DIDs:
 
[[Image:dids6.png]]
 
Here you can choose which DIDs to update and what to do:
*'''Update''' - option to change some of DID details, Reserve DID for User (only free DIDs can be reserved) or Make DID free.
*'''Delete''' - option to delete DIDs by Provider or make DIDs Free/Terminated/Closed.
*'''Manage rates''' - option to change Rates for [[DID Billing]].
*'''[[Assign DID to Trunk]]'''.

*'''Reserve for User''' - option to reserve DID for User (only free DIDs can be reserved).
*'''Assign Dial Plan''' - option for Assign DID to [[Dial_Plans | Dial Plan]]
 

= Allowing Users to route their DIDs =
Since '''MOR X5''' users are able to route their DID to a Device or an External Server .
This functionality can be enabled in '''SETTINGS -> Setup -> Visual''' by checking the 'Allow User to assign DID to Device:' setting.

Once the functionality is enabled, the user will be able to see an Edit icon, in his DIDs list.
 
[[File:Dids_list_with_did_routing.png‎]]
 

By pressing the icon, the user will be redirected to a page where he will be able to route his DID either to one of his MOR Devices, or to a Device on an external server (eg. SIP/370xxxxxx@123.123.123.123).
 
[[File:Did_routing_panel.png‎]]
 

=See Also=

*[[DID Billing]]
*[[DIDs Usage]]
*[[MOR_API_did_create | Create DID through API]]
*[[MOR_API_did_device_assign | Assign Device to DID through API]]
*[[MOR_API_did_device_unassign | Unassign Device from DID through API]]
*[[Providers#Provider_Grace_Time|Provider Grace Time]]
*[[Grace_time|Device Grace Time]]
*[[Example - Configuring DID to ring some Device]]
*[[DID is not working]]

DID Management

2017-07-25T10:31:39Z

Reda:

= Description =

DID is an external number to have incoming calls to your VoIP network reach a particular device. (This is a very simplified explanation that will serve for the moment. For a more extensive explanation, please check [http://www.voip-info.org/wiki/view/DID here]).

'''VERY IMPORTANT RULE: DIDs in MOR MUST be in E.164 format.'''

You can reach window, with list of all DIDs, in '''SETTINGS –> Billing –> DIDs''':
 
[[File:Dids updated.png]]
 
User/Dial Plan and Device show who will answer when dialing this DID.

Clicking on User or Device brings you to their settings. If you click on the [[Image:callflow.png]] icon, you will go to the device's [[Call Flow]] window.

In this page you can
*[[DID_Management#Add_new_DID(s) | Add new DID(s)]]
*Reach [[DID_Management#DID_bulk_management | Bulk management]]
*Export DIDs to CSV
*Reach page to change DID [[DID Billing | Rates]]
*Update DID [[DID_Management#Settings | settings]]
*Search only by DID Owner, when using search field called ''Owner'', or search by either DID Owner or DID Reseller at once, when using search field called ''User''.

*Hide Terminated DIDs. When option "Hide Terminated DIDs" is checked, terminated dids will be hidden until option is unchecked. Clear search button or relogin will not clear the checked option.
* Search by User type.
* Search by inclusive Balance range (only for Owners).
* Search by User status (only for Owners).

 

= Status =
[[Image:dids2.png|right]]
Status is very important. For every just-created DID, the status is Free.

A DID can have several statuses:

* '''Free''' – this status means that the DID is free to be reserved for any user/device. You can also Terminate it.
* '''Reserved''' – the DID is reserved but NOT actually used for a user. "Reserved" is useful at the negotiation stage before signing a contract. When a user decides to sign up, we Activate the DID. We can also make the DID Free.
* '''Active''' – the DID is assigned to a Device and is functional. We can Close it.
* '''Closed''' – the DID is no longer functional, so that all calls going to this DID will get Hangup. One important feature of this state: when a DID is Closed, it will be closed for a set time (the default is 90 days) in case the user changes his mind and decides to use this DID again. This is useful when a user is not paying for services, as we can suspend the DID by using Closed. MOR will make it Free after the Closed period runs out. You can manually make it Free or Terminate this DID.
* '''Terminated''' – the DID is no longer used in MOR. It remains only for historical purposes. You can make it Free if you want.

 

= Add new DID(s) =

In the main DIDs window, if you want to add new DID(s), click on [[Image:add.png]] '''New DID''':

[[Image:dids5.png]]

In this window you can:

# Choose DID(s) [[DID_Management#Details | details]]
# Add one DID or series of DIDs
# Import DID(s) from CSV file

Example of DIDs list in CSV file:

442012345678
442087654321
442054987123

'''NOTE:''' You should select the Provider which sold you this DID. DID Provider is ONLY for informational purposes. If you do not know which Provider to assign - create dummy Provider to represent company from which you buy DID. If this is fake DID - assign any Provider you want. If your DID Provider has several IP addresses (as DIDWW) and you configured several Providers in MOR - assign ANY configured Provider.

 
== VIDEO: How to create a DID ==

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

 

= Settings =

If you want to edit a DID's settings, click on the [[Image:edit.png]] icon.
 
[[Image:dids4.png]]
 
The above window is for Free DID. You can:

# Change [[DID_Management#Details | details]]
# [[DID_Management#Reserve_DID_for_User | Reserve DID for User]].
# [[DID_Management#Assign_to_Dial_Plan | Assign to Dial Plan]].
# Terminate a DID.

 

==Details==

*'''Provider''' – DID Provider is ONLY for informational purposes. If you do not know which Provider to assign - create dummy Provider to represent company from which you buy DID. If this is fake DID - assign any Provider you want. If your DID Provider has several IP addresses (as DIDWW) and you configured several Providers in MOR - assign ANY configured Provider.

*'''Language''' – option to set language for voice prompts in the Asterisk Dial Plan

*'''Call limit''' – describes how many simultaneous calls DID can '''receive'''. 0 (zero) means that calls are unlimited.

*'''Comment''' – option to save some notes about DID.

*'''[[Sound files | Sound file]]''' – here you can add [[IVR Greeting for DID]]


*'''Grace Time''' – if call duration is less than Grace Time, it will not be accounted, for example: '''Grace Time''' = 3s, call duration <= 3s, then price for the call = 0


*'''Timeout Digit''' – the maximum amount of time permitted between digits when the user is typing in a number. When this timeout expires after the user has started to type in a number, the number will be considered complete, and will be interpreted (sent to the system). Works both with entering destination and ANI/PIN.


*'''Timeout Response''' – the maximum amount of time permitted for user to START entering a number. If the user does not begin typing a number in this amount of time, system will notify that nothing was entered. Once the user begins to type a number, system will wait for Digit Timeout to be reached, and Response Timeout has no effect no more.


*'''CallerID Name Prefix''' – option to add a CallerID Name prefix to the incoming CallerID.


*'''Tone zone''' – option to set tone zones. Tone zone is a different ring tone depending on destination (country).


*'''Tariff for Calling Card''' – option to set a tariff for DID which will be applied for a calling card. It will not be important what tariff is assigned for that card's group.

 
==Reserve DID for User==

When a DID is assigned to a Device (Reserve for User first), you have a few different choices:

[[Image:dids3.png]]

Here you can:

# Change [[DID_Management#Details | details]].
# Assign DID to device. Here you can select different Devices for the same user. For select Trunk Device is next section.
# Assign DID to Trunk. Here you can select different Trunk Devices for the same user.
# Stop a DID subscription and reserve the DID for 90 days (by default) to this user in case he changes his mind and wants to get the DID back.

 
==Assign to Dial Plan==

When DID is assigned to [[Dial_Plans | Dial Plan]], in DID settings you can:
# Change [[DID_Management#Details | details]].
# Make DID free.

When you have [[Quickforwards_rules | Quickforward Rule]] for this DID, in DID edit you will see additional notice:

[[Image:DID_edit_collisions_with_qf_rule.png‎]]

 
= Delete DID =

At first, mark it as "not used" (Free). Then terminate it. When you do, you will see [[Image:delete.png]] next to the DID in the main DID window. By clicking on it, you can delete the DID.

 
= DID bulk management =
In the main DIDs window, click [[Image:edit.png]] Bulk Management and you will be able to perform various actions with a series of DIDs:
 
[[Image:dids6.png]]
 
Here you can choose which DIDs to update and what to do:
*'''Update''' - option to change some of DID details, Reserve DID for User (only free DIDs can be reserved) or Make DID free.
*'''Delete''' - option to delete DIDs by Provider or make DIDs Free/Terminated/Closed.
*'''Manage rates''' - option to change Rates for [[DID Billing]].
*'''[[Assign DID to Trunk]]'''.

*'''Reserve for User''' - option to reserve DID for User (only free DIDs can be reserved).
*'''Assign Dial Plan''' - option for Assign DID to [[Dial_Plans | Dial Plan]]
 

= Allowing Users to route their DIDs =
Since '''MOR X5''' users are able to route their DID to a Device or an External Server .
This functionality can be enabled in '''SETTINGS -> Setup -> Visual''' by checking the 'Allow User to assign DID to Device:' setting.

Once the functionality is enabled, the user will be able to see an Edit icon, in his DIDs list.
 
[[File:Dids_list_with_did_routing.png‎]]
 

By pressing the icon, the user will be redirected to a page where he will be able to route his DID either to one of his MOR Devices, or to a Device on an external server (eg. SIP/370xxxxxx@123.123.123.123).
 
[[File:Did_routing_panel.png‎]]
 

=See Also=

*[[DID Billing]]
*[[DIDs Usage]]
*[[MOR_API_did_create | Create DID through API]]
*[[MOR_API_did_device_assign | Assign Device to DID through API]]
*[[MOR_API_did_device_unassign | Unassign Device from DID through API]]
*[[Providers#Provider_Grace_Time|Provider Grace Time]]
*[[Grace_time|Device Grace Time]]
*[[Example - Configuring DID to ring some Device]]
*[[DID is not working]]

File:Dids5.png

2017-07-25T10:26:57Z

Reda: uploaded a new version of "File:Dids5.png"

File:Dids5.png

2017-07-25T10:22:34Z

Reda: uploaded a new version of "File:Dids5.png": Reverted to version as of 13:51, 11 April 2013

File:Dids5.png

2017-07-25T10:21:35Z

Reda: uploaded a new version of "File:Dids5.png"

M4 API quickstats get

2017-07-25T08:25:56Z

Reda:

=Description=

Retrieves today's [[Quick Stats]] and [[Active Calls]] count 

Data can be retrieved for '''Admin''' and by '''Admin''' only.

 

=Usage=

* '''M2''' call: '''/api/quickstats_get'''
* Methods: POST, GET(if allowed, not recomended)
 
===Parameters===

* [[MOR API hash construction | hash]] - SHA1 hash constructed using API_Secret_Key ([[MOR API hash construction | More described in Constructing hash]]). '''Required''' (if setting '''Disable hash checking''' is not checked).
* u - username for authentication. '''Required'''.
 
===Request===

If API Secret Key = secret

You send:

HTML POST: http://<SERVER_IP>/billing/api/quickstats_get?u=admin&hash=e5e9fa1ba31ecd1ae84f75caaa474f3a663f05f4

'''* Note that username (u) is not included in the hash'''
 

===Returns===

'''Success:''' Everything is ok. You get the list of calls if there is any:

<?xml version="1.0" encoding="UTF-8"?>
<page>
<quickstats>
<today>
<calls> Calls count </calls>
<duration> billsec in seconds </duration>
<revenue> revenue today</revenue>
<self_cost> expenditure today</self_cost>
<profit> difference of revenue and expences</profit>
<margin> profit's part in the sell price</margin>
</today>
<active_calls>
<total> Active Calls count </total>
<answered_calls> Answered Calls count </answered_calls>
</active_calls>
</quickstats>
</page>

'''Errors:'''

* <error>API Requests are disabled</error> – '''Allow API globally''' setting is unchecked
* <error>GET Requests are disabled</error> – '''Allow GET API''' setting is unchecked
* <error>Access Denied</error> – user with such username cannot use this method
* <error>Bad login</error> – such username does not exist in the database or it was not specified
* <error>Incorrect hash</error> – Hash was not correct. Check API_Secret_Key and order or params while concatenating hash_string
* <error>Cannot connect to Elasticsearch</error> – data is not reachable

Example:

<status>
<error>API Requests are disabled</error>
</status>
 
=See also=

* [[M2 API]]

M4 API quickstats get

2017-07-25T08:25:10Z

Reda:

=Description=

Retrieves today's [[Quick Stats]] and [[Active Calls]] count 

Data can be retrieved for '''Admin''' and by '''Admin''' only.

 

=Usage=

* '''M2''' call: '''/api/quickstats_get'''
* Methods: POST, GET(if allowed, not recomended)
 
===Parameters===

* [[MOR API hash construction | hash]] - SHA1 hash constructed using API_Secret_Key ([[MOR API hash construction | More described in Constructing hash]]). '''Required''' (if setting '''Disable hash checking''' is not checked).
* u - username for authentication. '''Required'''.
 
===Request===

If API Secret Key = secret

You send:

HTML POST: http://<SERVER_IP>/billing/api/quickstats_get?u=admin&hash=e5e9fa1ba31ecd1ae84f75caaa474f3a663f05f4

'''* Note that username (u) is not included in the hash'''
 

===Returns===

'''Success:''' Everything is ok. You get the list of calls if there is any:

<?xml version="1.0" encoding="UTF-8"?>
<page>
<quickstats>
<today>
<calls> Calls count </calls>
<duration> billsec in seconds </duration>
<revenue> revenue today</revenue>
<self_cost> expenditure today</self_cost>
<profit> difference of revenue and expences</profit>
<margin> PROFIT's part in the SELL price</margin>
</today>
<active_calls>
<total> Active Calls count </total>
<answered_calls> Answered Calls count </answered_calls>
</active_calls>
</quickstats>
</page>

'''Errors:'''

* <error>API Requests are disabled</error> – '''Allow API globally''' setting is unchecked
* <error>GET Requests are disabled</error> – '''Allow GET API''' setting is unchecked
* <error>Access Denied</error> – user with such username cannot use this method
* <error>Bad login</error> – such username does not exist in the database or it was not specified
* <error>Incorrect hash</error> – Hash was not correct. Check API_Secret_Key and order or params while concatenating hash_string
* <error>Cannot connect to Elasticsearch</error> – data is not reachable

Example:

<status>
<error>API Requests are disabled</error>
</status>
 
=See also=

* [[M2 API]]

File:M2 admin quick stats.png

2017-07-25T08:16:26Z

Reda: uploaded a new version of "File:M2 admin quick stats.png"