You can view CDRs from the main menu of the StarLeaf Portal. You can download the CDRs as a comma-separated file.

Record ID

An ID, which is unique per call leg.

Sequence ID

An ID, which is unique per call sequence. Examples of a sequence include all the legs of a scheduled or ad hoc conference, an initial call and transfer leg, or a fallback to videomail.


INITIALA point-to-point call, or the point-to-point call before an ad hoc conference.
CONSULTThe consultation before forwarding a call, or before adding someone to a conference.
CONFERENCEEA user added to a conference ad hoc, after an initial point-to-point call.
SCHEDULED_CONFERENCEEA user dialing in to a conference that has been scheduled through the Portal.
TRANSFERREDThe point-to-point call after a transfer has taken place. This is always seen after a CONSULT entry.
REFERĀ and REFERREDREFER is when a Skype for Business endpoint asks a StarLeaf registered endpoint to join a Skype for Business meeting. REFERRED is the resulting call

Call Outcome

CONNECTEDThe connected to the remote endpoint was established successfully.
NO_ANSWERThe remote endpoint rung, but was not answered.
  1. If Termination Reason (see below) is OK, then the caller rang someone in their own organization, but hung up before the callee answered.
  2. If Termination Reason is NO_ANSWER, the callee did not pick up during the ringing period.
NOT_CONNECTEDThe call was not connected.
  1. If Termination Reason is OK, the call may have been a consultation call, but the caller completed the transfer before the callee answered, or the caller rung someone outside their organization, but hung up before the call was answered.
  2. If Termination Reason is BUSY, the far end returned a busy tone.
  3. If Termination Reason is UNAVAILABLE, a call has been attempted to a number that does not exist, or is not contactable through the public Internet.
CONNECTED_NO_MEDIAThe call connected, but no media was ever established.
  1. If Termination Reason is OK, then one of the participants hung up before the audio and/or video media channel was connected.
  2. If Termination Reason is either MEDIA_ERROR or RMT_MEDIA_ERROR then there was an error (see table below).
MOVED_INTO_CONFERENCEThe user dialed into the conference, and the conference was active, so they were moved into it successfully. One of these legs appears for each user who successfully joins a StarLeaf scheduled conference.
ENDED_IN_WAITING_ROOMThe user dialed into a conference, but hung up before any other user joined. The conference only starts once either the host, or a second participant joins (depending on conference settings in the StarLeaf Portal).
NOTIFIEDThe callee has StarLeaf app for iPad logged in, but did not answer the call. Their iPad now has a missed call notification.
REJECTEDThe callee pressed the ‘reject’ or ‘send to mailbox’ button on the StarLeaf user interface.

Terminated Reason

OKThe call disconnected after a successful connection.
DISCONNECTEDThe call ended due to a disconnection. This may have been due to a loss of network connection.
NO_ANSWERThe remote endpoint did not answer the call while it was ringing.
UNAVAILABLEThe remote endpoint was unavailable. It may not exist, or may be offline.
BUSYThe remote endpoint returned a busy response. It may have been in another call.
DENIEDThe remote endpoint denied the call. This can only occur if the remote endpoint is a legacy system or PSTN provider.
MEDIA_ERRORThere was a failure to negotiate appropriate media streams for the call, or a media processing failure in the StarLeaf platform.
RMT_MEDIA_ERRORThere was a media negotiation error at one of the endpoints. For example a StarLeaf app client may not have a microphone plugged in.
REJECTEDThe call was rejected by the far end. This may be due to the ‘Ignore call’ button being pressed.