Cisco MCS-7825-H3-IPC1 Service Manual page 193

Chapter 5 Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Table 5-34 Cisco SIP Normalization (continued)
Display Name
MessageRollback
msgAddContentBody
msgAddHeader
msgAddHeaderUriParameter
msgAddHeaderValueParameter
msgApplyNumberMask
msgBlock
msgConvertDiversionToHI
OL-22523-01
Description
This counter indicates the number of times that the system automatically rolled back
a message. The system rolls back the message by using the error handling that is
specified in the Script Execution Error Recovery Action field in the SIP
Normalization Script Configuration window in Cisco Unified CM Administration.
When an execution error occurs, Cisco Unified CM automatically restores the
message to the original content before applying additional error handling actions. If
error handling specifies rollback only, no further action is taken beyond rolling back
to the original message before the normalization attempt. For the other possible
Script Execution Error Recovery Actions, message rollback always occurs first,
followed by the specified action, such as disabling the script, resetting the script
automatically, or resetting the trunk automatically.
This counter represents the number of times that the script added a content body to
the message. If you are using the msg:addContentBody API in the script, this
counter increases each time that the msg:addContentBody API executes
successfully. If the counter behavior is not as expected, examine the script logic for
errors.
This counter represents the number of times that the script added a SIP header to the
message. If you are using the msg:addHeader API in the script, this counter
increases each time that the msg:addHeader API executes successfully. If the
counter behavior is not as expected, examine the script logic for errors.
This counter represents the number of times that the script added a SIP header URI
parameter to a SIP header in the message. If you are using the
msg:addHeaderUriParameter API in the script, this counter increases each time that
the msg:addHeaderUriParameter API executes successfully. If the counter behavior
is not as expected, examine the script logic for errors.
This counter represents the number of times that the script added a SIP header value
parameter to a SIP header in the message. If you are using the
msg:addHeaderValueParameter API in the script, this counter increases each time
that the msg:addHeaderValueParameter API executes successfully. If the counter
behavior is not as expected, examine the script logic for errors.
This counter represents the number of times that the script applied a number mask
to a SIP header in the message. If you are using the msg:applyNumberMask API in
the script, this counter increases each time that the msg:applyNumberMask API
executes successfully. If the counter behavior is not as expected, examine the script
logic for errors.
This counter represents the number of times that the script blocked a message. If
you are using the msg:block API in the script, this counter increases each time that
the msg:block API executes successfully. If the counter behavior is not as expected,
examine the script logic for errors.
This counter represents the number of times that the script converted Diversion
headers into History-Info headers in the message. If you are using the
msg:convertDiversionToHI API in the script, this counter increases each time that
the msg:convertDiversionToHI API executes successfully. If the counter behavior is
not as expected, examine the script logic for errors.
Cisco Unified Communications Manager Managed Services Guide
Performance Monitoring in RTMT
5-39