Do you know how many calls failed to setup on your network today? There are literally dozens of reasons calls fail. You need to have insight into how many calls in your enterprise are not connecting and why. The Q.850 Cause Codes provide insight into why calls fail. Here are a few examples:

• Code 1: Unassigned Number
• Code 3: No Route to Destination
• Code 27: Destination Out of Order
• Code 44:  Requested Circuit/Channel Unavailable
• Code 135: Out of Bandwidth

Below is a Traffic Analyst display highlighting a network that consistently shows in excess of 8,000 failed calls per weekday.  The legend outlines the many different codes that occurred during this recent two-week period.

Let’s focus on the most common problem of Unassigned Number (code 1) failures.  A quick filter of that code shows the daily detail in chart below.  The secondary chart shows the hourly breakout for a single day.  A large number of these failure types typically indicate potential inbound call hack attempts.  Do you know how many intrusion attempts are hitting your network?  For this network, it is clear that the barrage of calls is consistently occurring day after day and throughout each day. 

Another click of the mouse drills directly to the call detail records to showcase the calls for this particular hour are all inbound calls originating from the same number, calling a common number and there are several calls each second.  Clearly this appears to be an inbound hack attempt! 

This is just a single example of how having the visibility into your call failures is critical.  Other problems you may uncover might be looping conditions, channel failures at your service provider, equipment failures and much more. 

Traffic Analyst simplifies network administration so your engineering staff can troubleshoot network issues you may not even be aware exist today.  Contact us today to learn more about Total Caller Experience^® and putting Traffic Analyst to work for you.