GVP MCP:sip:transport-staticroutelist
(Karlabel used the OptionEdit action.) |
|||
Line 6: | Line 6: | ||
|shortdesc=Specifies a list of static routes. Each route group is separated by |. Each static route group is a list of IP addresses separated by comma. Within the route group, each IP address could substitute each other as an alternate route destination if sending a SIP request to one of the IP address fails. For example, 10.0.0.1,10.0.0.2|10.0.10.1,10.0.10.2 specified two static route groups, and each group specified two routes that are alternative to each other. Default value is an empty list. | |shortdesc=Specifies a list of static routes. Each route group is separated by |. Each static route group is a list of IP addresses separated by comma. Within the route group, each IP address could substitute each other as an alternate route destination if sending a SIP request to one of the IP address fails. For example, 10.0.0.1,10.0.0.2|10.0.10.1,10.0.10.2 specified two static route groups, and each group specified two routes that are alternative to each other. Default value is an empty list. | ||
}} | }} | ||
− | {{DraftOption}} | + | {{DraftOption |
+ | |hidden=false | ||
+ | |default= | ||
+ | |valid=Can be an empty string or a valid "|" separated list of static routes. Check the description for further details. | ||
+ | |takeseffect=At start/restart | ||
+ | |shortdesc=Specifies a list of static routes. Each route group is separated by |. Each static route group is a list of IP addresses separated by comma. Within the route group, each IP address could substitute each other as an alternate route destination if sending a SIP request to one of the IP address fails. For example, 10.0.0.1,10.0.0.2|10.0.10.1,10.0.10.2 specified two static route groups, and each group specified two routes that are alternative to each other. Default value is an empty list. | ||
+ | }} | ||
Revision as of 07:30, March 13, 2019
View in ref guide.
Edit this option Publish this option Clear draft content
Published Option
Draft Option
Comments or questions about this documentation? Contact us for support!