Problem:

We need to be able to see how many times an individual extension is "hit" / called and filter that data based on the site in which the call originated.

Example:

• Extension 999707 "Florida Forward" is set as Key-Press option #1 at two sites:
• 103-Austin
• 104-Dallas

We need to be able to see how many times key-press 1 (ext 999707) is hit from EACH site. When looking at the performance report in analytics for the 999707 extension, we can see the calls to the extension that originate from both sites, however, we cannot filter the data based on the site in which the call originated.

Currently, the only way to gather this data is to expand each call and manually record the originating site....

Solution:

Add a filter that allows for the filtering of calls based on Originating site.

NOTE: We could obviously build a virtual extension at each site and check the analytics for each and every one for those virtual extensions, but that is not an elegant solution for 100+ sites. A filter for a single extension makes much more sense.