Location information overview

External location information

For external party numbers, the Cisco CDR Reporting and Analytics app parses phone numbers, gets country codes, area codes and exchange.  From those the app gets a wealth of other information, like zip code, LATA, lat and long and other fields.

Internal location information

For internal extensions, you can use the Sites features (see below!).

Using External Location Information

Displaying the fields in Browse Calls

These fields are enabled by default. To see them in Browse Calls, simply add them with the field picker.

1. Click Edit Fields in the upper right.
2. Find the field you want to add either by scrolling around, or use the filter field.
3. Click to add fields to the Selected Fields list.
4. Click and drag to rearrange the fields on the right.
5. Remove extra fields by clicking their “x”.
   

To find potentially interesting fields

• In the app click the “Home” in the upper left.
  
• In the bottom half of the home screen pick “Location fields”
  

See our blog post on the Field Gallery for more information.

Simple Filtering by Location Fields in Browse Calls

In the search filters box, you can work all sorts of wonders.  For instance, here we typed in callingPartyCountry="Canada"

Similarly, you could

• Filter to multiple locations, like callingPartyState="Ohio" OR callingPartyState="Kentucky"
• Exclude a location, like NOT finalCalledPartyCountry="United States"

These search filters follow you though to General Report if you click the “Graph calls over time” link in the upper right.

Simple Filtering by Location Fields in General Report

Much like the above, there’s a search filters box you can add various parameters into.  Here we are using callingPartyCountry!="United States"

NOT callingPartyCountry!="United States" vs. callingPartyCountry!="United States" is covered near the end of our regular User Tips if you want to know the difference.

Using Location as “over” or “split by” fields

A different way to look at that data is over callingPartyState.  You could easily use *any* of the fields here, give them a try!

Note we left a search filter in place – this is fine!

Or even more fun, split by one of the fields.  This means we go back to over time but then splits the resulting columns up by the split by field.  Well, a picture is worth a thousand words:

---

Using Sites for Internal Locations

Sites are location information for internal subnets.

See here on how to enable them and create some sites, then hop back here when you’ve got it set up and see below on use cases!

Sites has both its own special page in our app, but also can be used as generic search, filter, split or group by fields.

Sites special page

Browse > Sites

As shown before, here’s what you might get if you Browse > Sites

Site Detail

Clicking on any row in Browse > Sites will take you to a page that gives you the peak concurrency between that site and other sites.  It will also give you any unusual call terminations for those calls.

Filtering by Sites Fields in Browse Calls

Use the search filters box to filter Browse Calls for a particular site, orig_site or dest_site, or any of the other fields like your supplied latitude or longitude.

Here we add a search term of site="Sundries"

Similarly, you could

• Filter to multiple sites, like site="Sundries" OR site="Haberdashery"
• Exclude sites, like NOT site="Haberdashery"

These search filters follow you though to General Report if you click the “Graph calls over time” link in the upper right.

Filtering by Sites Fields in General Report

Just like in Browse Calls, you can use the search box.  Here we use a search term of site="Sundries"

Similarly, you could

• Filter to multiple sites, like site="Sundries" OR site="Haberdashery"
• Exclude sites, like NOT site="Haberdashery"

These search filters follow you though to Browse Calls if you click the “see calls” link in the upper right.

Using it as a “over” or “split by” field

Another way is to use it in the over field.  This is usually better as a column chart because it will then make buckets of each site and count how many were in each bucket.

And the last example is of using it in the split by field.  Here, instead of building buckets like above, we just split the overall totals into “by site”.  A picture is worth a thousand words here.

There are other ways you can use this information too, we’ve only give you the tip of the iceberg in this documentation.

If you have any comments at all about the documentation, please send it in to docs@sideviewapps.com.