|
|
Line 7: |
Line 7: |
| }} | | }} |
| {{DraftOption}} | | {{DraftOption}} |
| + | |
| | | |
| | | |
Line 13: |
Line 14: |
| | | |
| {{PubExtended}} | | {{PubExtended}} |
| + | |
| | | |
| | | |
Line 18: |
Line 20: |
| | | |
| {{DraftExtended}} | | {{DraftExtended}} |
| + | |
| | | |
| | | |
Revision as of 18:57, October 11, 2018
View in ref guide.
Edit this option Publish this option Clear draft content
Published Option
userouteonrecording
Default Value: true
Valid Values: Choose between: true or false
Changes Take Effect: Immediately/session
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.
Draft Option
No draft option