Jump to: navigation, search

GVP MCP:vrmrecorder:sip-securerouteset

m (1 revision imported)
Line 1: Line 1:
----
+
{{PubOption
__NOTOC__
 
 
 
<!-- ==================== -->
 
<!-- DO NOT EDIT -->
 
=Published=
 
{{Optionstmp
 
|internalformid=1 (DO NOT EDIT THIS VALUE)
 
|fromxml=true
 
|docstatus=Published
 
|fromxml=true
 
|parameter=sip.securerouteset
 
|urlparameter=sip-securerouteset
 
|displayname=VRMRecorder Secure Route Set
 
 
|hidden=false
 
|hidden=false
|default=
 
 
|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}}
 +
{{DraftExtended}}
 +
{{OptionCreate
 +
|component=GVP_MCP
 +
|compshort=GVP_MCP
 +
|prodshort=GVP
 +
|configobject=Application
 
|section=vrmrecorder
 
|section=vrmrecorder
|urlsection=vrmrecorder
+
|parameter=sip.securerouteset
|groupid=grpMedia
 
|groupname=Media Processing
 
|format=string
 
|prodshort=GVP
 
|component=GVP_MCP
 
|compshort=MediaControlPlatform
 
}}
 
[[Category:GVP_MCP_options]]
 
 
 
<!-- DO NOT EDIT -->
 
<!-- ==================== -->
 
 
 
==Extended Description==
 
 
 
{{Extended
 
|internalformid=1 (DO NOT EDIT THIS VALUE)
 
|docstatus=
 
|mandatory=
 
|introduced=
 
|modified=
 
|discontinued=
 
|feature=
 
|relatedoptions=
 
|relatedlinks=
 
|configobject=
 
|moredesc=
 
 
}}
 
}}
  
=Draft=
+
[[Category:GVP_MCP_options]]
 
 
{{Optionstmp
 
|internalformid=2 (DO NOT EDIT THIS VALUE)
 
|docstatus=
 
|parameter=
 
|displayname=
 
|hidden=
 
|default=
 
|valid=
 
|takeseffect=
 
|shortdesc=
 
|section=
 
|groupid=
 
|groupname=
 
|format=
 
|prodshort=
 
}}
 
 
 
==Extended Description==
 
 
 
{{Extended
 
|internalformid=2 (DO NOT EDIT THIS VALUE)
 
|docstatus=
 
|mandatory=
 
|introduced=
 
|modified=
 
|discontinued=
 
|feature=
 
|relatedoptions=
 
|relatedlinks=
 
|configobject=
 
|moredesc=
 
}}
 

Revision as of 03:23, October 31, 2016


View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

sip.securerouteset

Default Value:
Valid Values: A valid secure routeset must have the format as specified in its description
Changes Take Effect: At start/restart


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.

Draft Option

No draft option

Comments or questions about this documentation? Contact us for support!