GVP MCP:sip:userouteonrecording
| (6 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
|valid=Choose between: true or false | |valid=Choose between: true or false | ||
|takeseffect=Immediately/session | |takeseffect=Immediately/session | ||
| − | |shortdesc=When performing third-party recording, this configuration will specify if the Record-Route on the incoming INVITE should be used in Route header of the INVITE for third party recording (if present). The effect of this setting would be to re-use the same Resource Manager used for incoming requests, increasing the likelihood of reaching an active Resource Manager. This overrides vrmrecorder.sip.routeset when enabled. If set to false, then MCP will use vrmrecorder.sip.routeset if present, otherwise it will not set the Route header. | + | |shortdesc=When performing third-party recording, this configuration will specify if the Record-Route on the incoming |
| + | INVITE should be used in Route header of the INVITE for third party recording (if present). | ||
| + | The effect of this setting would be to re-use the same Resource Manager used for incoming requests, | ||
| + | increasing the likelihood of reaching an active Resource Manager. | ||
| + | This overrides vrmrecorder.sip.routeset when enabled. | ||
| + | If set to false, then MCP will use vrmrecorder.sip.routeset if present, otherwise it will not set the Route header. | ||
}} | }} | ||
{{DraftOption}} | {{DraftOption}} | ||
Latest revision as of 15:37, June 29, 2020
View in ref guide.
Edit this option Publish this option Clear draft content
Published Option
Draft Option
No draft option
This page was last edited on June 29, 2020, at 15:37.
Comments or questions about this documentation? Contact us for support!