Example 1: In this example, everything looks normal - the vast majority of responses are 2xx, or successful responses with only a small percentage of authorization errors, which is to be expected.  Then at 8am there is an outage, causing a rapid spike of Internal Server Errors on Invites.

Example 2: This traffic was observed on an external facing SBC - 3/4 of all Invites were met with a Authorization 401, or 403 response code, indicating heavy security attacks requiring further input from engineers

Example 3: When filtering by message type, it can be seen that a large percentage of service messages are returning a 'Bad Request' error.  This is likely caused by an internal implementation error where something is querying the SIP server for a service response, but has been misconfigured.