Concurrency & Utilization

Screenshot showing the Call Concurrency and Gateway Utilization page as a line chart of peak call concurrency over time split by gateway, above a panel of calls dropped because no circuit or channel was available.

The Call Concurrency and Gateway Optimization was built to answer very specific but important questions about utilization across trunks, gateways, sites, types of devices, and more.

To understand capacity, chart concurrency.

The Cisco CDR Reporting & Analytics app gives you concurrency analytics that are built in from the start. Get specific data around common questions like: What does peak utilization look like over the last 30 days for our legacy trunk at HQ?

Get a Free Trial

Is this you? Just a few Concurrency & Utilization issues that can be answered with Sideview.

You wish you could easily see trunks and gateways in CUCM that are getting near capacity.

You think you could probably get rid of a PRI, but you’re not sure.

A team is saying they’re being crushed by calls all day, and you wish you had a chart to show management.

Which teams and agents aren’t using their provided jabber devices or hardphones.

You’ve made a lot of changes and don’t know what the peak concurrency is now for key numbers.

SIP trunks are working well but you don’t have good charts to prove this to anyone.

You don’t know whether efforts to save money and reduce PRI usage are actually working.

Have another concurrency & utilization issue that you need to tackle?

Talk to an Expert

Whether using a scalpel or a sledge hammer, do it with data.

Our Cisco CDR Reporting & Analytics App Lets You…

Build dashboards to monitor concurrency and utilization.
See when calls are dropping due to capacity limits.
Set up automatic alerts when you’re nearing limits.
Analyze concurrency and even percent utilization over anything, by anything.

Because it’s such a common question, we built the Call Concurrency and Gateway Optimization page to answer many of your questions about concurrency and utilization at the gateway level.

Screenshot showing the Chart page charting max concurrency over time split by cause_description, as a stacked column chart, for a single hunt pilot

You thought we were kidding? Here’s a chart of concurrency (not call volume!) for the incoming calls to a single huntPilotDN over time, split by the call termination reason.

Screenshot showing the Chart page charting max concurrency over time for the gateway PVC-VGW3, split by dest_device_type, as a stacked column chart.

You still thought we were kidding? 5 clicks from the previous entry and I’m now looking at the concurrency of calls coming through one group of gateways split by the destination device type. So happy these sorts of ad-hoc charts are useful, or else they’d not let me have so much fun making them.