The routing rule detail panel provides the ability to create and modify individual rules. Since the structure of conditions is complex, the user will need to utilize a different set of panels to change the conditions associated with a rule.
Routing rules are not needed in cases where there is one cluster running SIP. Rules are only applied to the initial message of a SIP conversation and not all SIP traffic. To view this administrative console page, click proxy_server_name.
Enables a rule to be removed from consideration without requiring that it be deleted. This field is checked by default.
| Information | Value |
|---|---|
| Data type | Boolean |
| Default | true |
| Setting recommendations | none |
| Setting dependencies | none |
The name of the cluster that the SIP message will be routed to if the message attributes match the conditions.
| Information | Value |
|---|---|
| Data type | String |
| Default | First cluster in the list. |
| Range | List of existing clusters or “null cluster” to indicate that a request should be rejected. |
| Setting recommendations | None |
| Setting dependencies | None |