GVP MCP:vrmrecorder:sip-securerouteset
(9 intermediate revisions by 3 users not shown) | |||
Line 4: | Line 4: | ||
|valid=A valid secure routeset must have the format as specified in its description | |valid=A valid secure routeset must have the format as specified in its description | ||
|takeseffect=At start/restart | |takeseffect=At start/restart | ||
− | |shortdesc=Defines a route set for secure SIP connections to third party recorders. The URI for secure connections should specify the "sips:" scheme or "tls" transport. If the secure route set is defined, this route set will be inserted as the ROUTE header for all VRMRecorder secure SIP sessions. This will force the MCP to send the secure SIP messages via this defined route set. Please see "[sip] securerouteset" for format and other descriptions. The typical value for this would be the Resource Manager (RM)'s secure address, as all recorder requests go through the RM. | + | |shortdesc= |
+ | Defines a route set for secure SIP connections to third party recorders. The URI for secure connections should specify the "sips:" scheme or "tls" transport. | ||
+ | If the secure route set is defined, this route set will be inserted as the ROUTE header for all VRMRecorder secure SIP sessions. This will force the MCP to send the secure SIP messages via this defined route set. Please see "[sip] securerouteset" for format and other descriptions. The typical value for this would be the Resource Manager (RM)'s secure address, as all recorder requests go through the RM. | ||
+ | |||
+ | }} | ||
+ | {{DraftOption | ||
}} | }} | ||
− | |||
{{PubExtended}} | {{PubExtended}} | ||
− | {{DraftExtended}} | + | {{DraftExtended |
+ | }} | ||
{{OptionCreate | {{OptionCreate |
Latest revision as of 15:29, 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:29.
Comments or questions about this documentation? Contact us for support!