Skip to main content
 
 
Splunk Lantern

Failed calls by destination and gateway

 

The table below explains in detail the steps of a Splunk Enterprise or Splunk Cloud Platform search to see failed calls organized by destination and outbound network gateway. For more information, review the use case monitoring key telecommunications service metrics.

Some commands, parameters, and field names in the searches below may need to be adjusted to match your environment.  In addition, to optimize the searches shown below, you should specify an index and a time range when appropriate.

Splunk recommends that customers look into using data models, report acceleration, or summary indexing when searching across hundreds of GBs of events in a single search. The searches provided here are a good starting point, but depending on your data, search time range, and other factors, more can be done to ensure that they scale appropriately.   

Splunk Search Explanation
| sourcetype=<call detail records> Search only your telephony data.
| eval _time = start Extract the timestamp and put it in a field called "start".
| lookup <cdr disposition mapping file> disposition

Enrich the search results with clearer descriptions of the dispositions.

If your lookup file does not contain the disposition column, adjust the search to match the names in your lookup.

| search disposition=FAILED OR disposition=CONGESTED Search for failed call events, identified with a disposition of FAILED or CONGESTED.
| eval Description=if(match(disposition,"CONGESTED"),"Route Error",description) If the disposition is "CONGESTED", return a value of "Route Error". Otherwise, return the description for the disposition.

| rex field=src "(?<srcCountry>\d+)(?=\d{10})"

| rex field=dst "(?<dstCountry>\d+)(?=\d{10})"

Extract the source (src) country code, then the destination (dst) country code.

This example assumes that the country code is what precedes a 10 digit number.

| lookup <country code to name mapping file> phoneCode AS dstCountry OUTPUTNEW countryName as dstCountryName ISO2 AS dstCountryCode

Enrich the results by adding a country name and iso code, based on the dstCountry field extracted.

If the column names in your lookup file differ from those shown here, adjust the search to match the names in your lookup.

| stats count values(dst) AS Destination values(disposition) AS Disposition values(Description) AS Description values(_time) AS Time BY partyBiD dst Calculate a count of each destination, disposition, description, and time of the placed call. Then, sort the results first by routed path and then by destination.
| rename partyBiD AS "Routed Path" Rename the field as shown for better readability.
| table Time Destination Description "Routed Path" count Display the results in a table with columns in the order shown.