...
| Section |
|---|
| Column |
|---|
| Example 1 - System Outage: 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. 
|
| Column |
|---|
| Example 2 - Security issue: 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
|
| Column |
|---|
| Example 3 - Configuration issue: 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. 
|
|
Anomoly Detection on Huge size
SIP Response Summary (Huge) with anomaly detection
Troubleshooting
Image ModifiedNot seeing any SIP response code data?
- Check SIP Tracing is enabled within the configuration of your Session Manager or Session Border Controller.
- Further help configuring SIP Tracer is available here.
- Note for v8.0 of Avaya SBCs there is a known issue enabling the SIP Tracer, where clicking the checkbox on the SBC does not save.
- Ensure any firewalls or network security allows the SIP Traces to route to the VSM Collector IP address on UDP port 514.
- Still having issues? Contact your Business Partner or Virsae support.
...