Last Calls

Last Calls

STATISTICS –> Calls –> Last Calls shows the most recent calls in the system. It is used in Troubleshooting.



Last Calls search is available both for users and administrators. You can make search by User, Device, call Status, Hangup Couse, Provider, DID Provider, Source, Destination or DID.
There is possible to find calls by Reseller. Reseller in any DIDs lets one search for all calls made through specific reseller's DID or range of DIDs.
You can search calls by Calling Cards information with Card number, Card PIN or Card ID parameters. End user can see these fields only when he is the distributor for at least one Calling Card. Card PIN will not be visible if option Hide Calling Card PIN is checked in Calling Cards settings.
DID Provider searches for calls made through specific DID provider while Provider shows you calls made only through specific call provider.

Please note that when occurs a call where DID is involved it consists of two legs (call from DID to MOR and call from MOR to Destination). They will be shown seperately in Last Calls list.

Faster Page Loading

Functionality can be enabled in STATISTICS -> Setup -> Settings -> Visual tabby checking Count Last Calls total values only after click option.

It allows to load table data separately from total data which highly increases page loading time.

When functionality is active click bottom table row in order to calculate total values.

CSV

Using the "Export to CSV" icon you can export your currently displayed calls into CSV

PDF

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) - usually called LEG A. Based on routing rules, call may be canceled(in case there is no suficcient funds, no appropriate rule etc.) or one more call leg may be created - from UAS to destination another UAC (LEG B). 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 (LEG A - OK, LEG B - FAILED)
  

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 we would say that there was only one call which was connected.
  
  

If user A is interested only in calls made, information, about how many attempts were made to call user B, has no interest for him. Majority of users will be interested only in call duration, who terminated the call etc.
Hence this is how call information is represented in call statistics, trying not to overwhelm users with too much technical details, only information about successful call is presented, ignoring details about made call legs (FAILED or NOT, etc). Provided you want to check the information on FAILED and connected call LEGS, you can use the Call Info page.

Search usage

Destination field allows to search by Exact destination, by first digits and by matching pattern.

Examples:

• 370123 will return all calls where number is "370123";

• 370% will return all calls where number begins with "370";

• %70% will return all calls where number contains "70".

See also

• Troubleshooting
• Reporting
• Call list
• Providers Calls