Viewing a List of Route Tables
SUMMARY STEPS
- Choose Configure > Route Tables.
- To delete a route table, do the following:
- To revert any changes you have made back to the state they were in at the time of the last commit, do the following:
DETAILED STEPS
Step 1 |
Choose Configure > Route Tables. The system displays the Route Tables page, containing the fields described in the section Route Table Fields. |
Step 2 |
To delete a route table, do the following:
|
Step 3 |
To revert any changes you have made back to the state they were in at the time of the last commit, do the following:
|
About Route Tables
You configure route tables to direct SIP requests to their appropriate destinations. Each route table consists of a set of keys that are matched based on the lookup policy.
For example, in one table, each key might represent the prefix of the phone number dialed. The table performs a task depending on the prefix dialed. In this example, the table is designed to respond to calls with a 404 message (not found) unless the phone number dialed begins with 510. Another table might be designed to respond to calls with a 404 message (not found) unless the phone number dialed begins with the escape sequence (91).
You can add, update, or delete route tables from the Route Tables page. You can also add, update, or delete routes.
Route Table Fields
The table lists the fields on the Route Tables page.
Parameter |
Description |
---|---|
State |
Can be one of the following:
|
Name |
Name of this route table. The valid characters are alphanumeric characters, dash, period, and underscore. |
Route Fields
The table lists the fields on the Route Table ‘<name of route>’ Routes page.
Note |
Depending on the route type that you choose, you will see some or all of these parameters. |
Parameter |
Description |
||
---|---|---|---|
State |
Can be one of the following:
|
||
Candidate Value |
|||
Key |
Specifies the route table lookup key number. The lookup key represents the portion of the SIP message that is being matched, and must be unique to the routing table. |
||
Route Type |
Can be one of the following:
|
||
Destination Route Type (Optional; only available if you choose a Route Type of destination or default-sip) |
|||
Destination Route Type |
The type of route. Can be either target destination, next hop, or both. |
||
Network |
Specifies the SIP network name. |
||
Target Destination (Optional; only available if you choose a Destination Route Type of target destination or both) |
|||
Host/Server Group |
Hostname or IP address of the target destination.
|
||
Port |
Port of the target destination. Values can be 1024 to 65535. |
||
Transport Type |
Can be one of the following:
|
||
Next Hop (Optional; only available if you choose a Destination Route Type of next hop or both) |
|||
SIP URI |
URI of the next hop. |
||
Route-Group Route Type (Optional; only available if you choose a Route Type of route-group) |
|||
Route Group |
The name of the route group. |
||
Response Route Type (Optional; only available if you choose a Route Type of response) |
|||
Response |
Specifies the response code to a lookup key in a routing table. |
||
Route-Policy Route Type (Optional; only available if you choose a Route Type of route-policy) |
|||
Lookup Route Policy |
Specifies the route lookup policy to be used in the routing table. |
||
Default SIP Route |
Simple routing following RFC 3263. |