Revision as of 12:30, 6 March 2008

This section describes features already implemented into development version of MOR PRO v0.6. When MOR PRO v0.6 will be released all this info will go to the manual.

MOR PRO v0.6 is scheduled to be released on 2008.03.31

Allow loss calls

Allow loss calls - this setting let's you decide - do you want to allow user to use some provider if provider's rate to some destination is lower then user's rate. Allowing such call you will pay more to provider then user pays you for such call - that means you will take loss on such call. If this setting is no (default) - cheaper providers will not be used in dialing.

CID control by DIDs

This setting let's you control what CID user can enter in his devices. These CID numbers should be from the set of device's DIDs. It is mainly used when user's PBX is connected over trunk and many DIDs are routed to this Trunk. Calls coming out from this PBX must have CallerID Number from the set of DIDs assigned to this Trunk (PBX). If CID from DIDs is checked - system checks if device's cid number is from dids assigned to this device. If no dids are assigned - this value is ignored. In order for this setting to be active - CID Name/Number fields must be empty to allow user enter any CID number he wants. If CID from DIDs is checked and user enters any CID (not from his DIDs) - system will change his CID by his first available DID (selected from database by lowest id).

Tariff analysis

Using this tool you can select the tariffs (wholesale) which you want to compare. Click on desired tariffs and select currency in which you want to compare tariffs. When you selected tariffs press on Generate CSV icon to get CSV file. In this file you can see all selected tariffs with their rates for ALL destinations. In 4 last columns you will find MIN and MAX rates for each destination with their providers. This let's you compare tariffs on the fly. The final section shows Total/Min/Max rates for each tariff. Using these values let's you see which tariff is the most expensive/cheap. NOTE: Min + Max can be not equal to Total because same provider can have MIN and MAX rates for some prefix if there're no more providers for this prefix (destination).

Destinations CSV

This link in Tariffs window gets you CSV file with all Destinations/Directions. It is suitable for rate entering and importing back to MOR.

API

API waits for HTML POST to get request data. Then it returns result in XML.

MOR API <- more details

Addons

New addons introduced in MOR PRO v0.6

MOR Addons <- more details

Invoice by CallerID

This type of invoice groups all calls by CallerID.

It looks like this:

Client number: 37052058393

Number Date Duration Rate Price Destination
37063042439 2007-12-01 16:21:03 00:00:20 0.7597 0.2532 Lithuania
...
37068723423 2007-12-14 12:50:17 00:00:22 0.7597 0.2785 Lithuania
                    Lithuania 150.4886 LTL (Without VAT)
                    Total: 150.4886 LTL (Without VAT)

Client number: 37063042438

Number Date Duration Rate Price Destination
37068723423 2007-12-01 14:45:14 00:03:20 0.7597 2.5322 Lithuania
...
37065017476 2007-12-13 21:31:14 00:04:11 0.7597 3.1779 Lithuania
                    Lithuania 26.9805 LTL (Without VAT)
                    Total: 26.9805 LTL (Without VAT)

                    Monthly fee - test memo2 10.0000 LTL (Without VAT)
                    TOTAL TO PAY: 187.4692 LTL

Hide users

As it is not allowed to delete users who have at least 1 call - after some time such 'non-active' users accumulate and we need to do something to them to have clear control panel.

For that reason we just Hide them. They remain active - nothing changes for them - except we do not see them in the GUI.

Later you can find them in SETTINGS - Users - Hidden. You can unhide them if you wish anytime.

To hide a user go to his details and select Hidden. To unhide - Not hidden.

Hangupcause codes

MOR application saves hangupcause codes to DB so it is easy to check what was the error and why call failed.

These codes can be seen in calls window (Hangup Cause column) when selected to show 'All', 'Busy', 'No Answer', 'Failed' or 'Missed' calls.

Standard hangup codes can be found here.

MOR specific codes:

Code	Cause
200	MOR can't determine who is calling
201	User is blocked
202	Reseller is blocked
203	No rates for user
204	No suitable providers found
205	MOR PRO not authorized to work on this computer
206	server_id is not set in mor.conf file
210	Balance > 0, but not enough to make call 1s in length
211	Low balance for user
212	Too low balance for more simultaneous calls
213	Low balance for DID owner
214	Too low balance for DID owner for more simultaneous calls
215	Low balance for reseller
216	Too low balance for reseller for more simultaneous calls

Active Calls

On main window in Quick Stats it is possible to see Active Calls - these are the calls, which are in the system at this moment.

It it possible to press on it and new window opens - with detailed Active Calls.

You can get to this window in STATISTICS - Various - Realtime - Active Calls.

In this window all active calls are presented with more details, such as: Start Date, Duration, Src, Dst.

In order to see correct duration on multi-server systems, all time on servers should be synchronized.

In order to see Active Calls in GUI, in file /etc/asterisk/mor.conf you should have:

active_calls=1

NOTE: local calls are not visible on MOR GUI, only calls to/from outside

*97 voicemail without entering username

Now user can dial *97 and he will get to his VoiceMail box only entering password (no username is required).

mor.conf configuration

New variables in /etc/asterisk/mor.conf:

Unique number for server identification

server_id=1

Should we add/update/delete active calls to/from DB?
This option is necessary for call-limit support

active_calls=1

Dial command settings for dialing out (using providers). More info.

dial_out_settings = r

Quick Forwards

Some DIDs can be assigned to Quick Forwards functionality. When it is done each user can enter different number to be forwarded when he calls some DID.

Main advantage of this function is to use limited number of DIDs to let different users to call these DIDs and be forwarded to different numbers (which are assigned by users).

Example

We have several DIDs assigned to Quick Forwards functionality:

1111111111
2222222222

Now we have 2 users with such CallerIDs:

User A with CallerID 8888888888
User B with CallerID 9999999999

User A set such forwards:

From DID 1111111111 forward to 3333333333
From DID 2222222222 forward to 4444444444

User B set such forwards:

From DID 1111111111 forward to 5555555555
From DID 2222222222 forward to 6666666666

When User A dials DID 1111111111 his CallerID (8888888888) is checked, user is recognized and call is automatically forwarded to number 3333333333
When User A dials DID 2222222222 his CallerID (8888888888) is checked, user is recognized and call is automatically forwarded to number 4444444444

When User B dials DID 1111111111 his CallerID (9999999999) is checked, user is recognized and call is automatically forwarded to number 5555555555
When User B dials DID 2222222222 his CallerID (9999999999) is checked, user is recognized and call is automatically forwarded to number 6666666666

IMPORTANT: Correct CallerID's should be set for users in order to recognize them. Only system admin can do that.

If system can't recognize the caller it asks to enter PIN number of the device.
If user is dialing DID which has not assigned Forward Number, user is asked to enter such nuber.

User can manipulate his Quick Forwards in his menu. He needs to login to GUI to change numbers.

Destination to create from CSV

When importing rates from CSV file now you can check which Destinations will be created automatically.

You can view them in separate window when you press List in step 4 in foeld Destinations to create.

Such destinations does not exist in MOR database and MOR will create them when importing rate file.

IMPORTANT! DO NOT FORGET TO ADD THEM TO APPROPRIATE DESTINATION GROUP LATER!!!

Integrity Check

This window test various properties of billing system and tells where potential problems can be.

It can be reached in SETTINGS - Billing - Functions - Integrity Check

Destinations not assigned to Destination Groups

This window shows Destinations which are not assigned to any Destination Group. This can lead to many problems such as incorrect billing and others.

Such Destinations appear after tariff rate import. It is necessary to assign these Destinations to correct Destination Groups just after new rates are imported.

Device details

This window show all fields from database table devices to some particular device. It is only read-only.

It can help to troubleshoot login problems for device.

VoiceMail configuration

This section can be found in SETUP - Settings - VoiceMail

VoiceMail Extension - describes by which local extensions local user can dial to retrieve his voicemail (system will ask him to enter his voicemail password which can be set in device's details)

If you want to setup VoiceMail (VM) on different server, then following settings are important:

VoiceMail Server active - turns VM server on/off, when on - all VM request will go to distabd VM server, when off - VM will be handled locally on Asterisk
VoiceMail Server connection/device - describes connection to VM server
VoiceMail Retrieve Extension - which extension to dial on distant VM server to retrieve voicemail for some extension

Example:

Let's say we have our server on IP 23.45.67.89 connected with SIP to our Asterisk.
We create separe user/device (vm_device) to describe this connection. Device's type is SIP, IP = 23.45.67.89, set other settings also (codecs/etc)
VoiceMail Retrieve Extension = 999

First action is when VM is recorded

So now when VM server is ON and user with device 201 get's a VM, call is redirected like this:

Dial(SIP/vm_device/201)

That means server on 23.45.67.89 will receive call to extension 201. Server SHOULD BE configured that way, tat it will process VM correctly when it receives such call.

Second action - retrieving VM

When user want to retrieve his VM on distant machine he dials VoiceMail Extension.

He is redirected like this:

Dial(SIP/vm_device/999#201

Again - distant server should know how to process such a request.

Let's say we have distant VM server based on Asterisk.

So in our example it's configuration in /etc/asterisk/extensions.conf should look like this:

[incoming]
# to retrieve VM
exten => _999#.,1,VoiceMailMain(${EXTEN:4})
exten => _999#.,2,Hangup

# to record VM
exten => _X.,1,VoiceMail(${EXTEN})
exten => _X.,2,Hangup

@@ Line 341: / Line 341: @@
 That means server on 23.45.67.89 will receive call to extension 201. Server SHOULD BE configured that way, tat it will process VM correctly when it receives such call.
-====Second action - retrieving VM====
+===Second action - retrieving VM===
 When user want to retrieve his VM on distant machine he dials '''VoiceMail Extension'''.

Difference between revisions of "MOR PRO v0.6 documentation"