Jump to: navigation, search

GVP MCP:mpc:cpa-carriermsg-readduration
 
(6 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
|valid=The number must be a non-negative integer, greater than or equal to 60 and less than or equal to 300
 
|valid=The number must be a non-negative integer, greater than or equal to 60 and less than or equal to 300
 
|takeseffect=Immediately
 
|takeseffect=Immediately
−
|shortdesc=Specifies the read duration. This is how many seconds we read from a carrier message file until we stop reading that file. This prevents MCP from reading carrier message files if they span far too long. Very long carrier message files can impact matching accuracy. This parameter does not govern HTTP request timeouts. A maximum read duration of 300 seconds for optimal matching accuracy and performance is enforced. A minimum of 60 seconds is required. Do not rely on this parameter to precisely measure how long to read each file. Always ensure that the read duration is longer than your longest carrier message file. After changing this parameter, the coefficients for all the carrier message will be recalculated again. Please give it some time to recalculate before attempting to make a call after changing this parameter.
+
|shortdesc=
 +
Specifies the read duration. This is how many seconds we read from a carrier message file until we stop reading that file.
 +
This prevents MCP from reading carrier message files if they span far too long. Very long carrier message files can impact matching accuracy.
 +
 
 +
This parameter does not govern HTTP request timeouts.
 +
 
 +
A maximum read duration of 300 seconds for optimal matching accuracy and performance is enforced.
 +
A minimum of 60 seconds is required.
 +
 
 +
Do not rely on this parameter to precisely measure how long to read each file.
 +
Always ensure that the read duration is longer than your longest carrier message file.
 +
 
 +
After changing this parameter, the coefficients for all the carrier message will be recalculated again.
 +
Please give it some time to recalculate before attempting to make a call after changing this parameter.
 +
 
 
}}
 
}}
 
{{DraftOption}}
 
{{DraftOption}}

Latest revision as of 15:48, June 29, 2020



View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

cpa.carriermsg.readduration

Default Value: 60
Valid Values: The number must be a non-negative integer, greater than or equal to 60 and less than or equal to 300
Changes Take Effect: Immediately


Specifies the read duration. This is how many seconds we read from a carrier message file until we stop reading that file. This prevents MCP from reading carrier message files if they span far too long. Very long carrier message files can impact matching accuracy.

This parameter does not govern HTTP request timeouts.

A maximum read duration of 300 seconds for optimal matching accuracy and performance is enforced. A minimum of 60 seconds is required.

Do not rely on this parameter to precisely measure how long to read each file. Always ensure that the read duration is longer than your longest carrier message file.

After changing this parameter, the coefficients for all the carrier message will be recalculated again. Please give it some time to recalculate before attempting to make a call after changing this parameter.

Draft Option

No draft option

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