User's Manual

Avaya Branch Gateway Manager 10.0 Page 350
15-601011 Issue 29r (Friday, November 02, 2012)B5800 Branch Gateway
5.12.1 Standard
Incoming call routes are used to match call received with destinations. Routes can be based on the incoming
line group, the type of call, incoming digits or the caller's ICLID. If a range of MSN/DID numbers has been
issued, this form can be populated using the MSN Configuration tool (see MSN Configuration ).
· Default Blank Call Routes
By default the configuration contains two incoming calls routes; one set for Any Voice calls (including analog modem)
and one for Any Data calls. While the destination of these default routes can be changed, it is strongly recommended
that the default routes are not deleted.
· Deleting the default call routes, may cause busy tone to be returned to any incoming external call that does not
match any incoming call route.
· Setting any route to a blank destination field, may cause the incoming number to be checked against system short
codes for a match. This may lead to the call being rerouted off-switch.
· Calls received on IP, S
0
and QSIG trunks do not use incoming call routes. Routing for these is based on incoming
number received as if dialed on-switch. Line short codes on those trunks can be used to modify the incoming digits.
· If there is no matching incoming call route for a call, matching is attempted against system short codes and finally
against voicemail nodes before the call is dropped.
· SIP Calls
For SIP calls, the following fields are used for call matching:
· Line Group ID
This field is matched against the Incoming Group settings of the SIP URI (Line | SIP URI ). This must be an
exact match.
· Incoming Number
This field can be used to match the called details (TO) in the SIP header of incoming calls. It can contain a number,
SIP URI or Tel URI. For SIP URI's the domain part of the URI is removed before matching by incoming call routing
occurs. For example, for the SIP URI [e-mail] , only the user part of the URI, ie. mysip, is used for
matching.
· The Call Routing Method setting of the SIP line can be used to select whether the value used for incoming
number matching is taken from the To Header or the Request URI information provided with incoming calls on
that line.
· Incoming CLI
This field can be used to match the calling details (FROM) in the SDP header of incoming SIP calls. It can contain a
number, SIP URI, Tel URI or IP address received with SIP calls. For all types of incoming CLI except IP addresses a
partial record can be used to achieve the match, records being read from left to right. For IP addresses only full
record matching is supported.
Usability
· Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system.
Incoming Call Matching Fields
The following fields are used to determine if the Incoming Call Route is a potential match for the incoming call. By default
the fields are used for matching in the order shown starting with Bearer Capability.
· Bearer Capability: Default = Any Voice
The type of call selected from the list of standard bearer capabilities: Any, Any Voice, Any Data, Speech, Audio
3K1, Data 56K, Data 64K, Data V110, Video.
· Line Group ID: Default = 0. Range = 0 to 99999.
Matches against the Incoming Line Group to which the trunk receiving the call belongs.
For Server Edition systems, the default value 0 is not allowed. You must change the default value and enter the
unique Line Group ID for the line.
· Incoming Number: Default = Blank (Match any unspecified)
Matches to the digits presented by the line provider. A blank record matches all calls that do not match other records.
By default this is a right-to-left matching.
· * = Incoming CLI Matching Takes Precedence
· – = Left-to-Right Exact Length Matching
Using a - in front of the number causes a left-to-right match. When left-to-right matching is used, the number match
must be the same length. For example -96XXX will match a DID of 96000 but not 9600 or 960000.
127
239
239