Jump to: navigation, search

GVP MCP:sip:securerouteset
Line 4: Line 4:
 
|valid=A valid secure routeset must have the format as specify in its description
 
|valid=A valid secure routeset must have the format as specify in its description
 
|takeseffect=At start/restart
 
|takeseffect=At start/restart
−
|shortdesc=Defines a route set for secure SIP outbound calls. Secure SIP calls 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 outgoing calls. This will force the MCP to send the SIP messages via this defined route set.<br/><br/> Each element in the routeset should be separated by a comma. This parameter can be used to define outbound proxies. Note that this routeset does not apply to SIP REGISTER messages.<br/><br/> sip.securerouteset = &lt;sips:ip/host;priority&gt;, ... e.g. sip.securerouteset=&lt;sips:p1.example.com;lr&gt;,&lt;sips:p2.domain.com;lr&gt;,&lt;sip:IP_RM:SIP_Port_RM;lr&gt;<br/><br/> In this example, the MCP will route the request to p1.example.com, which will in turn route the message to p2.domain.com, and finally be redirected to its intended destination.<br/><br/> This option is not applicable for transfer outbound calls initiated using VoiceXML. A transfer outbound call will use the same route set from the call initiated the transfer.
+
|shortdesc=Defines a route set for secure SIP outbound calls. Secure SIP calls 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 outgoing calls. This will force the MCP to send the SIP messages via this defined route set.<br /><br /> Each element in the routeset should be separated by a comma. This parameter can be used to define outbound proxies. Note that this routeset does not apply to SIP REGISTER messages.<br /><br /> sip.securerouteset = &lt;sips:ip/host;priority&gt;, ... e.g. sip.securerouteset=&lt;sips:p1.example.com;lr&gt;,&lt;sips:p2.domain.com;lr&gt;,&lt;sip:IP_RM:SIP_Port_RM;lr&gt;<br /><br /> In this example, the MCP will route the request to p1.example.com, which will in turn route the message to p2.domain.com, and finally be redirected to its intended destination.<br /><br /> This option is not applicable for transfer outbound calls initiated using VoiceXML. A transfer outbound call will use the same route set from the call initiated the transfer.
 
}}
 
}}
 
{{DraftOption}}
 
{{DraftOption}}
 +
 
{{PubExtended}}
 
{{PubExtended}}
 
{{DraftExtended}}
 
{{DraftExtended}}
 +
 
{{OptionCreate
 
{{OptionCreate
 
|component=GVP_MCP
 
|component=GVP_MCP

Revision as of 05:58, August 29, 2017



View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

securerouteset

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


Defines a route set for secure SIP outbound calls. Secure SIP calls 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 outgoing calls. This will force the MCP to send the SIP messages via this defined route set.

Each element in the routeset should be separated by a comma. This parameter can be used to define outbound proxies. Note that this routeset does not apply to SIP REGISTER messages.

sip.securerouteset = <sips:ip/host;priority>, ... e.g. sip.securerouteset=<sips:p1.example.com;lr>,<sips:p2.domain.com;lr>,<sip:IP_RM:SIP_Port_RM;lr>

In this example, the MCP will route the request to p1.example.com, which will in turn route the message to p2.domain.com, and finally be redirected to its intended destination.

This option is not applicable for transfer outbound calls initiated using VoiceXML. A transfer outbound call will use the same route set from the call initiated the transfer.

Draft Option

No draft option

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