Jump to: navigation, search

GVP MCP:mpc:voipmetrics-enable
 
Line 4: Line 4:
 
|valid=Choose between: 0 or 1
 
|valid=Choose between: 0 or 1
 
|takeseffect=At start/restart
 
|takeseffect=At start/restart
−
|shortdesc=When enabled, MCP will collect several metrics defined in RFC 3611 for each audio session. The metrics can be divided into local and remote. For local metrics, MCP collects some of them by exchanging RTCP messages between itself and the remote party while some are calculated locally from ongoing activities. For remote metrics, the remote party, if supporting RFC 3611, will report MCP about its metrics periodically and MCP will record them whenever it receives an update. At the end of each audio session, MCP users also have an option to publish the local and remote metrics to a destination. Refer to voipmetrics.* configuration under sip section for more information.
+
|shortdesc=When enabled, MCP will collect several metrics defined in RFC 3611 for
 +
each audio session. The metrics can be divided into local and remote.
 +
For local metrics, MCP collects some of them by exchanging RTCP messages
 +
between itself and the remote party while some are calculated locally
 +
from ongoing activities.
 +
For remote metrics, the remote party, if supporting RFC 3611, will report MCP
 +
about its metrics periodically and MCP will record them whenever it receives
 +
an update.
 +
 
 +
At the end of each audio session, MCP users also have an option to publish
 +
the local and remote metrics to a destination. Refer to voipmetrics.*
 +
configuration under sip section for more information.
 +
 
 
}}
 
}}
 
{{DraftOption}}
 
{{DraftOption}}

Latest revision as of 16:01, June 29, 2020



View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

voipmetrics.enable

Default Value: 0
Valid Values: Choose between: 0 or 1
Changes Take Effect: At start/restart


When enabled, MCP will collect several metrics defined in RFC 3611 for each audio session. The metrics can be divided into local and remote. For local metrics, MCP collects some of them by exchanging RTCP messages between itself and the remote party while some are calculated locally from ongoing activities. For remote metrics, the remote party, if supporting RFC 3611, will report MCP about its metrics periodically and MCP will record them whenever it receives an update.

At the end of each audio session, MCP users also have an option to publish the local and remote metrics to a destination. Refer to voipmetrics.* configuration under sip section for more information.

Draft Option

No draft option

This page was last edited on June 29, 2020, at 16:01.
Comments or questions about this documentation? Contact us for support!