AudioCodes Mediant 500 MSBR, Руководство пользователя

Страница: 497 / 1248

Version 7.2 497 Mediant 500 MSBR
User's Manual 27. Routing

Always Use Routing Table: Even if a proxy server is used, the SIP Request-URI
host name in the outgoing INVITE message is obtained from this table. Using this
feature, you can assign a different SIP URI host name for different called and/or
calling numbers. This feature is enabled using the AlwaysUseRouteTable parameter.

IP Profiles: IP Profiles can be assigned to destination addresses (also when a proxy
is used).

Alternative Routing (when a proxy isn't used): An alternative IP destination
(alternative routing rule) can be configured for specific calls ("main" routing rule).
When the "main" route fails (e.g., busy), the device can send the call to the alternative
route. You must configure the alternative routing rules in table rows (indices) that are
located anywhere
below the "main" routing rule. For example, if you configure a
"main" routing rule in Index 4, the alternative routing rule can be configured in Index 6.
In addition, you must configure the alternative routing rules with identical matching
characteristics (e.g., destination prefix number) as the "main" routing rule, but
assigned with different destination IP addresses. Instead of an IP address, you can
use an FQDN to resolve into two IP addresses. For more information on alternative
routing, see Alternative Routing for Tel-to-IP Calls on page 511.

Advice of Charge (AOC): AOC is a pre-billing feature that tasks the rating engine
with calculating the cost of using a service (Tel-to-IP call) and relaying that information
to the customer. AOC, which is configured in the Charge Codes table, can be applied
per Tel-to-IP routing rule.
Note:
•
Instead of using the table for Tel-to-IP routing, you can employ a third-party
Routing server to handle the routing decisions. For more information, see
Centralized Third-Party Routing Server on page 257.
•
You can configure up to three alternative routing rules per "main" routing rule in
the Tel-to-IP Routing table.
•
By default, the device applies telephone number manipulation (if configured) only
after processing the routing rule. You can change this and apply number
manipulation before processing the routing rule (see the RouteModeTel2IP
parameter).
•
When using a proxy server, it is unnecessary to configure routing rules in the Tel-
to-IP Routing table unless you require one of the following:
√
Alternative routing (fallback) when communication with the proxy server fails.
√
IP security, whereby the device routes only received calls whose source IP
addresses are configured in the table. Enable IP security using the
SecureCallsFromIP parameter.
√
Filter Calls to IP feature. The device checks the table before a call is routed to
the proxy server. However, if the number is not allowed (i.e., the number is not
specified in the table or a Call Restriction routing rule is configured), the call is
rejected.
√
Obtain different SIP URI host names (per called number).
√
Assign IP Profiles to calls.
√
For the table to take precedence over a proxy server for routing calls, you need
to configure the PreferRouteTable parameter to 1. The device checks the
'Destination IP Address' field in the table for a match with the outgoing call; a
proxy is used only if a match is not found.
The following procedure describes how to configure Tel-to-IP routing rules through the
Web interface. You can also configure it through ini file (Prefix) or CLI (configure voip >
gateway routing tel2ip-routing).