...
For each message type, there is a Response code similar to HTTP, with 1xx being informational, 2xx/3xx being success, and 4xx, 5xx, 6xx indicating a failure.
Supported Equipment
VSM summarizes this data for
- Session Managers
- Session Border Controllers
- Audio Codes
- Ribbon Edge Series (SWe Lite,1000,2000)
- Cisco Unified Border Element (CUBE) coming soon
The SIP Response Summary dashlet summarizes this data over a 24 hour period, showing a break-down across
...
When the dashet is set to Huge size then the view includes anomaly detection by Response.
Supported Equipment
VSM summarizes this data for
- Session Managers
- Session Border Controllers
- Audio Codes
- Ribbon Edge Series (SWe Lite,1000,2000)
- Cisco Unified Border Element (CUBE) coming soon
Dashboard examples
| 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. 
|
|
...