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

Performance Monitoring in RTMT
Table 5-34 Cisco SIP Normalization (continued)
Display Name
msgConvertHIToDiversion
msgModifyHeader
msgRemoveContentBody
msgRemoveHeader
msgRemoveHeaderValue
msgSetRequestUri
msgSetResponseCode
msgSetSdp
ptAddContentBody
ptAddHeader
Cisco Unified Communications Manager Managed Services Guide
5-40
Chapter 5 Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Description
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.
This counter represents the number of times that the script modified a SIP header in
the message. If you are using the msg:modifyHeader API in the script, this counter
increases each time that the msg:modifyHeader 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 removed a content body
from the message. If you are using the msg:removeContentBody API in the script,
this counter increases each time that the msg:removeContentBody 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 removed a SIP header
from the message. If you are using the msg:removeHeader API in the script, this
counter increases each time that the msg:removeHeader 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 removed a SIP header
value from the message. If you are using the msg:removeHeaderValue API in the
script, this counter increases each time that the msg:removeHeaderValue 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 modified the request URI
in the message. If you are using the msg:setRequestUri API in the script, this
counter increases each time that the msg:setRequestUri 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 modified the response
code and/or response phrase in the message. If you are using the
msg:setResponseCode API in the script, this counter increases each time that the
msg:setResponseCode 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 set the SDP in the
message. If you are using the msg:setSdp API in the script, this counter increases
each time that the msg:setSdp 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 content body to
the PassThrough (pt) object. If you are using the pt:addContentBody API in the
script, this counter increases each time that the pt: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
PassThrough (pt) object. If you are using the pt:addHeader API in the script, this
counter increases each time that the pt:addHeader API executes successfully. If the
counter behavior is not as expected, examine the script logic for errors.
OL-22523-01