User Activity

User Activity

In this statistics you can get some informations about the extension activities. The data are computed based on the cdr and sc_simplecdr table.

An answered call is a call from cdr table having disposition=ANSWERED and userfield containing [outbound] string.

• Outbound Answered - Qty : number of calls dialed by the extension (realsrc) and answered by the remote party
• Outbound Answered - Duration : sum of the time talking with the remote party (sum of billsec)
• Outbound Answered - Avg Duration : average duration for an answered call (avg of billsec)
• Outbound Answered - Cost : sum of costs associated to selected calls (sum of cc_costs)

• Outbound Busy - Qty : number of calls dialed by the extension (realsrc) and reported Busy from the remote party
• Outbound No Answer - Qty : number of calls dialed by the extension (realsrc) and reported No Answer from the remote party
• Outbound Failed - Qty : number of calls dialed by the extension (realsrc) and reported Failed from the remote party
• Outbound Congestion - Qty : number of calls dialed by the extension (realsrc) and reported Congestion from the remote party

• Outbound TOTAL - Qty : sum of all previous Qty of calls

The SMS are counted from the sm_smslogs table

• Outbound SMS - Qty : number of entries for the extension (sm_realsrc) with the OUT direction and response "DELIVERED"

The Inbound calls are counted using the sc_simplecdr table. There is a very big difference about the disposition in the cdr table and the disposition in the sc_simplecdr. For the cdr, a call is answered when it is answered from a SIP point of view. IN the sc_simplecdr a call is answered when it is bridged with another leg. So in short, a queue playing MOH to the caller is answered for the cdr, but not for the sc_simplecdr.