Difference between revisions of "Call Tracing"

From Kolmisoft Wiki
Jump to navigationJump to search
 
(34 intermediate revisions by 9 users not shown)
Line 1: Line 1:
=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 user will be able to dial out. To setup MOR is not so trivial (we are trying to change this with this manual and GUI improvements). It often happens for users to miss some important detail trying to make everything work. Now Call Tracing will save a lot of head-scratching and we hope will help for a lot of beginners.
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.


<big>'''Important! This function is for testing Dialing OUT. DID testing is not implemented yet.'''</big>
'''NOTE''' that Accountant can use this functionality with Call Tracing Usage permission.
 
 
This function can be found in '''SETTINGS – Billing – Function – Call Tracing'''. It can be quickly accessed in Users menu (SETTINGS – Users) also. Just press [[Image:icon_call_tracing.png]] icon for some user.
 
In the first window we have to select which user we want to check:
 


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


= User testing =  
= User testing =  


Next window shows us did we configure everything properly for selected user. Let's look at each section separately.  
The next window shows us whether we have configured everything properly for the selected User. Let's look at each section separately.  
 
The first one shows info special for user:


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


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.




Here we see [[Image:icon_cross.png]] 4 errors which does not let user to operate. Let's say we want to make user to make calls. So we will go through each one of 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:


1. This error tells us that user is Blocked and it will not be able to make calls. We should go to [[User Details]] and unblock him.
*  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.


2. Balance and Credit for this user are empty. And user type is Prepaid. That means he has no funds to cover the call fees. There are several ways how to go about this:
3. The User has no Devices. A Device is necessary in order to dial out. Just create one for this User.


*  If user is postpaid – he should use some payment method to increase his balance. [[PayPal]], [[Payments | Manual Payment]] and other ways are good to do this.
'''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.
*  We can change user type to postpaid and then we should adjust his credit. Maybe it is unlimited, maybe some limit exists. But that will allow user to dial out.


3. We see that user has assigned some tariff and type of tariff. Type of tariff is just for informational purposes. Here 'Explanation' tells us that tariff is empty. That is the reason why user will not be able to dial out. User can dial out only to these destinations which have rates. Currently none of them has. You need to put some rates to the existing tariff or assign non-empty tariff to this user.
4. User has no devices. Device is necessary to dial out. Just create one for this user.
After solving all these issues we should see:


After solving all these issues, we should see:
<br><br>
[[Image:calltracing3.png]]
[[Image:calltracing3.png]]
We can proceed with next section which is about LCR:
[[Image:calltracing4.png]]
It tells us that LCR we assigned to the user has no Providers. We should fix it. When at least one Provider is in the LCR assigned to the User we should see:
[[Image:calltracing5.png]]
This error happens when all providers in LCR are disabled. We need to have at least 1 active provider in order for user to be able to dial-out:
[[Image:calltracing6.png]]
Now none of our active providers has any rates. We should add rates to the provider's tariff. We can press directly on the Tariff to go to its rates and add some of them. After that we should see:
[[Image:calltracing7.png]]
To summarize all this section you should check for [[Image:icon_cross.png]] and read error descriptions. After fixing them you should see [[Image:icon_check.png]]. That means problem is solved and you can proceed. If at the bottom of the page you see:
[[Image:calltracing8.png]]
That means you still have unresolved issues. After all issues are solved you should see:
[[Image:calltracing9.png]]
When you see this green message you know that your user is configured properly. He is not blocked, he has enough money in his balance to pay for the call, his tariff has some rates for some destinations (so only these destinations are available to dial), he has some devices to use for dialing. Also his LCR has active providers with not empty tariffs.
You can proceed.
<br><br>
<br><br>


= Device testing =  
= Device testing =  


Following section let's us choose device, call date and enter destination which we want to test. For example:
The following section lets us choose a Device, Source, Server, Destination and a Call Time we want to test. For example:
 
<br><br>
[[Image:calltracing10.png]]
[[Image:Calltracing3.png]]
 
<br><br>
 
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.
 
This data means that we are testing virtual call from device SIP/1004 to number 863042438 on 2009 August 26th 00:00.
 
When we press '''Press this button to continue''' we will go to the next page and we will see something like:
 
[[Image:calltracing11.png]]
 
 
 
'''Details''' section shows us just informational info. We knew this info before so it is not important.
 
[[Image:calltracing12.png]]
 
 
 
If you see direction as Unknown that means your number is not in E.164 compatible format. Edit [[Localization]] rules to transform your number to E.164 number format.
 
'''Localization''' section is much more important.
 
Here we see device's Location, Applied rule and result after localization.
 
 
<big>'''IMPORTANT! Software can't read user's mind so it can't know where user is dialing.'''</big>
 
 
This can be illustrated by this example:
 
User dials 863042438. After Localization we see that number is still: 863042438. Which means it's somewhere in China. But it's wrong because user dialed Lithuanian number in local format! What does it mean? It means that [[Localization]] is not configured properly. MOR can't show you error here because there's no way to tell if it's ok or not.
 
You should decide for yourself. What MOR can do – just to show you all info it can get from the call and it does that.
 
So in order to proceed with example we have to set correct [[Localization]] rule for this number format. After doing this we will see:
 
[[Image:calltracing13.png]]
 
 
 
Now everything is ok. Localized destination is E.164 compatible. Now MOR understands that it's Lithuania as it should be.
 
If we get following window:
 
[[Image:calltracing14.png]]
 
 
 
That means we do not have rates or custom rates for dialed destination. After adding them we should see:
 
[[Image:calltracing15.png]]
 
 
 
This window also shows us that we do not have custom rate for this destination. But it's enough to have simple rate for destination to be able to dial out or vice versa.
 
We can proceed to the providers:
 
[[Image:calltracing16.png]]
 
 
 
We can see that our provider does not have rate for this destination. After fixing it we should see:
 
[[Image:calltracing17.png]]
 
 
 
That's it. Now real call should go out without problems.
 
 


When we click '''Trace Call''', we will go to the next page and we will see something like:
<br><br>
[[Image:New_mor_call_tracing.png]]
<br><br>
Call Tracing Log will show self explanatory warnings, errors (in red colored text), other messages, and an informative summary.
<br><br>
<br><br>
= Conclusion =
To summarize Call Tracing – it is very important to configure Localization properly.
You will see using Call Tracing what is happening and where the call is going.
When rates for user and provider are checked using localized destination. When all data are in place – there's no obstacle for call to be send to provider.


'''IMPORTANT!''' Green message at the end of Call Tracing does not mean call will be successful! It only means that MOR will send call to provider. What string it will send to provider you can see in last table. Applied Provider Rule parameters (Cut and Add) are also visible in the table. MOR can't know if provider accepts your dial string or not.
=From Accountant=


That depends how you configured [[Provider Rules]]. Call Tracing shows you formatted number which is sent to provider but you should decide is it correct or not.
Accountant must have '''Call tracing usage''' permission in [[Accountant_permissions | Accountant permissions group]] to use this functionality.
If call fails - check [[Users Calls]] or [[Providers Calls]] and check [[Hangupcause Codes]] to find a reason why call failed.

Latest revision as of 08:58, 3 October 2017

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 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:

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:

Calltracing2.png

Here we see three errors 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 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:

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:

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:

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 group to use this functionality.

Retrieved from "https://wiki.kolmisoft.com/index.php?title=Call_Tracing&oldid=22786"