Difference between revisions of "Last Calls"
| Line 32: | Line 32: | ||
When call is initiated by the caller, at least one call leg is created - from user agent client(UAC) to user agent server(UAS). based on routing rules, call may be canceled(in case there is no suficcient funds, no appropriate rule etc.) or at least one more call leg may be created - from UAS to destination another UAC. Many call legs may be created depending on routing rules and whether call to destination was succesfull. For instance:<br> | When call is initiated by the caller, at least one call leg is created - from user agent client(UAC) to user agent server(UAS). based on routing rules, call may be canceled(in case there is no suficcient funds, no appropriate rule etc.) or at least one more call leg may be created - from UAS to destination another UAC. Many call legs may be created depending on routing rules and whether call to destination was succesfull. For instance:<br> | ||
1. User A dials user B<br> | 1. User A dials user B<br> | ||
call leg from user A to PBX is created<br> | * call leg from user A to PBX is created<br> | ||
PBX can route call to user B<br> | * PBX can route call to user B<br> | ||
call leg from PBX to user B is created<br> | * call leg from PBX to user B is created<br> | ||
when user B answer these two legs are bridged<br> | * when user B answer these two legs are bridged<br> | ||
there we have two bridged legs and one call<br> | * there we have two bridged legs and one call<br> | ||
2. User A dials user B.<br> | 2. User A dials user B.<br> | ||
call leg from user A to PBX is created<br> | * call leg from user A to PBX is created<br> | ||
PBX cannot route call to destination and the call is canceled<br> | * PBX cannot route call to destination and the call is canceled<br> | ||
there we have one failed call and one call leg<br> | * there we have one failed call and one call leg<br> | ||
3. User A dials user B<br> | 3. User A dials user B<br> | ||
call leg from user A to PBX is created<br> | * call leg from user A to PBX is created<br> | ||
PBX can route call to user B through provider C<br> | * PBX can route call to user B through provider C<br> | ||
C fails to route the call<br> | * C fails to route the call<br> | ||
but PBX can route the call through another provider D<br> | * but PBX can route the call through another provider D<br> | ||
D succeeds in routing the call<br> | * D succeeds in routing the call<br> | ||
user B answers<br> | * user B answers<br> | ||
there we have three call legs, two of them were bridged and again we would say that there was only one call.<br><br> | * there we have three call legs, two of them were bridged and again we would say that there was only one call.<br><br> | ||
If user A is interested only in made calls, information, about how many atemps were made to call user B, is no interest for him. Majority of users will be interested only in call duration, who terminated the call etc.<br> | If user A is interested only in made calls, information, about how many atemps were made to call user B, is no interest for him. Majority of users will be interested only in call duration, who terminated the call etc.<br> | ||
| Line 54: | Line 54: | ||
<br><br> | <br><br> | ||
= See also = | = See also = | ||
* [[MOR_Manual#Troubleshooting | Troubleshooting]] | * [[MOR_Manual#Troubleshooting | Troubleshooting]] | ||
* [[MOR_Manual#Reporting | Reporting]] | * [[MOR_Manual#Reporting | Reporting]] | ||
Revision as of 08:55, 14 November 2011
Last Calls
STATISTICS –> Calls –> Last Calls shows the most recent calls in the system. It is used in Troubleshooting.
Search
This option is available starting from MOR 9
Starting from MOR 9 a search bar was added for Last Calls statistics.
CSV
This option is available starting from MOR 9
Using the "Export to CSV" icon you can export your currently displayed calls into CSV
This option is available starting from MOR 9
Using the "Export to PDF" icon you can export your currently displayed calls into PDF
Call information representation
When call is initiated by the caller, at least one call leg is created - from user agent client(UAC) to user agent server(UAS). based on routing rules, call may be canceled(in case there is no suficcient funds, no appropriate rule etc.) or at least one more call leg may be created - from UAS to destination another UAC. Many call legs may be created depending on routing rules and whether call to destination was succesfull. For instance:
1. User A dials user B
- call leg from user A to PBX is created
- PBX can route call to user B
- call leg from PBX to user B is created
- when user B answer these two legs are bridged
- there we have two bridged legs and one call
2. User A dials user B.
- call leg from user A to PBX is created
- PBX cannot route call to destination and the call is canceled
- there we have one failed call and one call leg
3. User A dials user B
- call leg from user A to PBX is created
- PBX can route call to user B through provider C
- C fails to route the call
- but PBX can route the call through another provider D
- D succeeds in routing the call
- user B answers
- there we have three call legs, two of them were bridged and again we would say that there was only one call.
If user A is interested only in made calls, information, about how many atemps were made to call user B, is no interest for him. Majority of users will be interested only in call duration, who terminated the call etc.
Hence how call information is represented in call statistics, trying not to overwhelm user with to much technical detail, only information about call is presented, ignoring details about made call legs. Though this information is available, you can read more http://wiki.kolmisoft.com/index.php/Call_Info
