How do I use Call Logs?

Our Call Logs feature allows you to access information about your recent calls. Here you can find call detail records that will help you investigate and troubleshoot calls. 

Accessing Call Logs

1. Log into the Bandwidth Dashboard.
2. In the top navigation bar, select Insights and click Voice.

Note: If you’re unable to view Call Logs, please ensure that your user has the Voice Insights role enabled.

3. Next, you may refine your search for Call Logs using the following filters: 

• • Sub-Account
  • From Start Time
  • To Start Time
  • From Number(s) 
  • To Number(s)
  • Call ID
  • Result
  • SIP
  • Direction
  • Hang Up Source

Note: Your results will include up to a maximum of 10,000 records from the past 30 days without filtering. Please use the search filters to refine the results. If your search has more than 10,000 records, you’ll see the following error message.

Understanding Call Logs fields

You may be familiar with these fields from other reporting you use at Bandwidth. An explanation for each field is listed below for your convenience: 

• Call ID: The unique ID associated with the call. This is the SIP Call ID; it won’t match the call ID you receive when using the voice APIs to initiate a call.
• Start Time: The date and time the call connected or failed to connect.
• Duration: The duration of the call.
• SIP Response: The SIP response associated with the call. This includes a code and a short description that will indicate whether the call was successful or the reason the call didn’t complete.
• Result: This indicates whether a call is complete or incomplete.
• From: This phone number is the sender.
• To: This phone number is the receiver.
• Direction: This indicates whether the call is inbound or outbound.
• Hang Up Source: This indicates whether the call was ended by the called party, calling party, or Bandwidth. 
• Attestation Level: This indicates the attestation level set by the originating service provider. For more information on STIR/SHAKEN, see our support article.
• Call Type: This is the type of voice product associated with this call.
• Cost: This is the estimated cost for the call.

Navigating Call Logs

Close and open filters

If you’d like to close the filters to have more space for the list of calls, click Close Filter. 

To open the filters, click Filter.

Adjust timezone

While all calls are recorded in UTC, we understand that our customers operate in different time zones. Your timezone may already automatically match your browser settings but you can also click Timezone and use the drop-down menu to select your preferred timezone.

Adjust table settings

If you’d like to display or hide specific fields, click Settings at the top of the page and use toggles under Default Columns to make your adjustments. You can also enable additional Call Type and Cost fields under Additional Columns. 

Download Call Logs 

To download your filtered call logs, click Download. 

Understanding the hang up source

There are two primary sources of the hang up:

• Calling party – this indicates the user who initiated the call terminated the call.
• Called party – this indicates the user who was called terminated the call. 

On some rare occasions, Bandwidth Internal will be listed as the source of the hang up. This indicates that an internal Bandwidth error may have terminated the call. 

Understanding attestation level

With STIR/SHAKEN, SIP headers will include a level of confidence indicator from the originating service provider to signal whether the party originating the call has the right to use the number via the attestation field. 

There are 3 levels of attestation that can be indicated by the originating service provider:

• Full (A) Attestation - the service provider has authenticated the customer originating the call and they’re authorized to use the calling number.
• Partial (B) Attestation - the service provider has authenticated the customer originating the call but can't verify they’re authorized to use the calling number.
• Gateway (C) Attestation - the service provider has authenticated from where it received the call, but can't authenticate the call source (e.g., International Gateway call).