AudioCodes Mediant 4000 SBC User Manual page 507

User's Manual
Parameter
[IP2IPRouting_DestType]
Version 7.2
(IP2IPRouting_DestIPGroupName) parameter. For more information
on the actual address, see the 'Destination IP Group' parameter.

[1] Dest Address = The SIP dialog is sent to the address configured
in the following parameters: 'Destination Address', 'Destination Port'
and 'Destination Transport Type'.

[2] Request URI = The SIP dialog is sent to the address indicated in
the incoming Request-URI. If the parameters 'Destination Port' and
'Destination Transport Type' are configured, the incoming Request-
URI parameters are overridden and these parameters take
precedence.

[3] ENUM = An ENUM query is sent to include the destination
address. If the parameters 'Destination Port' and 'Destination
Transport Type' are configured, the incoming Request-URI
parameters are overridden and these parameters take precedence.

[4] Hunt Group = Used for call center survivability. For more
information, see ''Configuring Call Survivability for Call Centers'' on
page 581.

[5] Dial Plan = (For Backward Compatibility Only - see Note
below) The IP destination is determined by a Dial Plan index of the
loaded Dial Plan file. The syntax of the Dial Plan index in the Dial
Plan file is as follows: <destination / called prefix number>,0,<IP
destination>
Note that the second parameter "0" is ignored. An example of a
configured Dial Plan (# 6) in the Dial Plan file is shown below:
[ PLAN6 ]
200,0,10.33.8.52
routed to destination 10.33.8.52
201,0,10.33.8.52
300,0,itsp.com
routed to destination itsp.com
Once the Dial Plan is defined, you need to assign it (0 to 7) to the
routing rule as the destination in the 'Destination Address' parameter,
where "0" denotes [PLAN1], "1" denotes [PLAN2], and so on.

[7] LDAP = LDAP-based routing. Make sure that the Routing Policy
assigned to the routing rule is configured with the LDAP Server
Group for defining the LDAP server(s) to query.

[9] Routing Server = Device sends a request to a third-party routing
server for an appropriate destination (next hop) for the matching call.

[10] All Users = Device checks whether the Request-URI (i.e.,
destination user) in the incoming INVITE is registered in its' users'
database, and if yes, it sends the INVITE to the address of the
corresponding contact specified in the database. If the Request-URI
is not registered, the call is rejected.

[11] IP Group Set = The device employs load balancing and routes
the call to one of the IP Groups in the IP Group Set, assigned using
the 'IP Group Set' parameter (below).

[12] Destination Tag = The device routes the call to an IP Group
determined by Dial Plan tags. The tag is specified in the 'Routing Tag
Name' parameter (below). For more information, see Using Dial Plan
Tags for Routing Destinations on page 551.

[13] Internal = Instead of sending the incoming SIP dialog to another
destination, the device replies to the sender of the dialog with a SIP
response code or a redirection response, configured by the 'Internal
507
Description
; called prefix 200 is
; called prefix 300 is
25. Routing SBC
Mediant 4000 SBC