User`s manual

MediaPack
SIP User's Manual 102 Document #: LTRT-65408
Table 5-17: Tel to IP Routing Table (continues on pages 101 to 102)
Parameter Description
Destination IP Address In each of the IP Address fields, enter the IP address (and optionally port number)
that is assigned to these prefixes. Domain names, such as domain.com, can be
used instead of IP addresses.
For example: <IP Address>:<Port>
To discard outgoing IP calls, enter 0.0.0.0 in this field.
Note: When using domain names, you must enter a DNS server IP address, or
alternatively define these names in the ‘Internal DNS Table’.
Profile ID Enter the number of the IP profile that is assigned to the destination IP address
defined in the ‘Destination IP Address’ field.
Status A read only field representing the quality of service of the destination IP address.
N/A = Alternative Routing feature is disabled.
OK = IP route is available
Ping Error = No ping to IP destination, route is not available
QoS Low = Bad QoS of IP destination, route is not available
DNS Error = No DNS resolution (only when domain name is used instead of an IP
address).
Charge Code An optional Charge Code (1 to 25) can be applied to each routing rule to associate
it with an entry in the Charge Code table (refer to Section
5.5.2.3.1 on page 88).
Parameter Name in ini File Parameter Format
Prefix
Prefix = <Destination Phone Prefix>, <IP Address>,<Src Phone Prefix>,<IP Profile
ID>,<Charge Code>
For example:
Prefix = 20,10.2.10.2,202,1,15
Prefix = 10[340-451]xxx#,10.2.10.6,*,1,1
Prefix = *,gateway.domain.com,*,20
Note 1: <destination / source phone prefix> can be single number or a range of
numbers. For available notations, refer to Section 5.5.3.1 on page 95.
Note 2: This parameter can appear up to 50 times.
Note 3: Parameters can be skipped by using the sign ‘$$’, for example:
Prefix = $$,10.2.10.2,202,1
Note 4: An optional IP ProfileID (1 to 9) can be applied to each routing rule.
5.5.5.3 IP to Hunt Group Routing
The IP to Hunt Group Routing Table is used to route incoming IP calls to groups of
channels called hunt groups. Calls are assigned to hunt groups according to any
combination of the following three options (or using each independently):
 Destination phone prefix
 Source phone prefix
 Source IP address
The call is then sent to the VoIP gateway channels assigned to that hunt group. The
specific channel, within a hunt group, that is assigned to accept the call is determined
according to the hunt group’s channel selection mode which is defined in the Hunt Group
Settings table (Section 5.5.8 on page 117) or according to the global parameter
‘ChannelSelectMode’ (refer to Table 5-8 on page 78). Hunt groups can be used on both
FXO and FXS gateways; however, usually they are used with FXO gateways.
Note: When a release reason that is defined in the ‘Reasons for Alternative IP to Tel
Routing’ table is received for a specific IPÆTel call, an alternative hunt group for that call is
available. To associate an alternative hunt group to an incoming IP call, assign it with an
additional entry in the ‘IP to Hunt Group Routing’ table (repeat the same routing rules with
a different hunt group ID). For detailed information on the ‘Reasons for Alternative Routing
Tables’, refer to Section 5.5.5.5 on page 106.