User's Manual

Avaya Branch Gateway Manager 10.0 Page 238
15-601011 Issue 29r (Friday, November 02, 2012)B5800 Branch Gateway
5.4.11.1 Incoming Call Routing
Incoming SIP calls are routed using Incoming Call Routes in the same way as call arriving on other external trunks.
The following Incoming Call Route fields are used to determine which route is the best match for a call.
· 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.
· 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 entry can be used to achieve the match, records being read from left to right. For IP addresses only full entry
matching is supported.
The fields Bearer Capability and Incoming Sub Address are not used for matching of incoming SIP calls. The remain
Incoming Call Route fields, including those voice recording, as used as for all call types.
· If the wildcard * is used in the SIP trunk's Local URI, Contact and Display fields, that SIP trunk will accept any
incoming SIP call. The incoming call routing is still performed by the system incoming call routes based on
matching the values received with the call or the URI's incoming group setting. For outgoing calls using this SIP
URI, all valid short code CLI manipulations are used (transforming calling party number to ISDN will be ignored).
348