This task is far easier than some others, because we have a special page just for gateway concurrency!
Click Report then Call concurrency and gateway utilization, as shown below. The bottom section will show you any calls that were dropped due to capacity related reasons. The rest of it may be interesting too.
These searches are often the basis of custom alerts that we can help you set up, too. Those tend to being rather tricky and fiddly, but we’ve done a few so we can help you walk through those if you ask nicely!
Another way to find and look at that data
That was so easy we should do a second part.
Head to Browse Calls. You should have the field cause_description in your output. If you don’t, click the Edit Fields button and add it!
Let’s now put in the same causes that the above chart picks out as indicating capacity problems by; into the search filters field add
cause_description="No circuit/channel available" OR cause_description="Requested circuit/channel not available"
(Coming in version 5.2.8 is a new field you can use to include all call failures, call_failed=1 )
Change your time frame, and also don’t forget to change the “get only” filter if you need to!
Any of those can be clicked on to get more call information (such as it is), or you can click the »graph calls over time button to take that set of criteria to General Report and build your own version of our above chart!
Just so you know I’m not lying, here’s a custom version where instead of charting the count over time, I chart the countover gateway to get a list over the past 7 days of how many calls were dropped for each gateway. This was just a couple of clicks past the above Browse Calls example (though I did expand the time frame so I can show more than one gateway).