Monitoring an organization
Managing Cloud Monitoring the CloudLast updated October 24, 2017
If enabled on an organization’s StarLeaf account, the Portal displays call detail records (CDRs) to administrators. CDRs provide the details of caller, called party, the bit rate of the call, and how the call disconnected. CDRs can be downloaded from the Portal as a CSV file. If CDRs are enabled on an account, an administrator is also able to view details of current calls in progress.
An example of CDRs is shown below.
To see more information about a particular CDR, click .
To download all CDRs as a CSV file, click.
- : A unique identifier that the Cloud gives to each call or conference. A call or conference includes more than one call leg
- :A unique identifier for a point-to-point call or for a call leg of a conference. This is the identifier required by technical support to uniquely identify a particular call leg
: The type of call leg. This is one of:
- initial: a leg in a point-to-point call
- consultation: the initial call is on hold and one of the initial callers is talking to a third person, possibly with the intention of transferring the call or creating a conference
- transferred: the initial call has been transferred
- conferencee: this is a call leg in a conference
- : When the call started (that is, when the call connected) and the time that the call ended
- : If the call was initiated by a StarLeaf device, the caller is the directory number of the user who made the call and that user’s name. If the caller is not using a StarLeaf device then this is another type of caller identifier depending on the calling device. For example, it could be a telephone number or a name from the far end
- : If the call was answered by a StarLeaf device, this is the directory number of the user who answered the call and that user’s name. If the call is answered by another device, the Cloud displays an identifier for the device it believes answered the call. If this is a conference call, the conference owner’s details are used
: Whether or not the call was answered successfully. The outcome can be any one of:
- Not connected
- Not answered
- Answered successfully
- Answered elsewhere
- Answered, but terminated before media negotiation completed
- Ended whilst waiting in queue
- Moved into conference
- Ended whilst in waiting room
The StarLeaf Portal can display monthly usage reports (for the current 3-month period) for each organization. These comprise:
- Number of calls per day (showing point-to-point, QuickMeet, and scheduled conference calls)
- Number of call minutes per day (showing point-to-point, QuickMeet, and scheduled conference calls)
- Users with the greatest call usage
- Room systems with the greatest call usage
The StarLeaf Portal can send email notifications about the state of hardware endpoints that are registered with the StarLeaf Cloud. On a per-organization basis, you can configure a list of email addresses that receive notifications. The email notifications will alert you when StarLeaf room systems connect and disconnect. Additionally, for H.323 endpoints, notifications will alert you for failed or rejected registrations (for example, if H.460 is not available for an endpoint).
This feature is not enabled by default. Contact StarLeaf technical support if you would like to receive endpoint monitoring notifications.