Incoming Call Routing - Avaya IP Office Basic Edition Manual

2.1.2 Incoming Call Routing

Key System Mode
For an incoming external call on a line, the following options control where the call is presented:
·
Coverage Destination
The Coverage Destination setting of each line can be used to select whether an incoming call on that line is also
presented to one of the following options in addition to alerting on any matching line appearances.
·
For PRI and BRI trunks, it is not possible to know on which of the trunk's channels incoming calls will
arrive. Therefore in most cases, the coverage destination and other settings of each line on the trunk
should be set to the same values.
·
Coverage Extension
The call alerts on an intercom or call appearance button of a selected line coverage extension. The user's call
coverage, VMS coverage and call forwarding settings are applied to the call. Any extension can be used as the
destination including a phantom extension.
·
Hunt Group
The call is presented, in sequence, to each of the available members of a selected hunt group until answered.
Any of the 6 sequential hunt groups can be used as the destination.
·
Line Appearance Buttons
The call will alert on any line appearance buttons that matches the line. Each line has a line number which can be
assigned to line appearance buttons on users' phones. Users can answer the call by pressing the alerting line
appearance button on their phone.
·
Number of Lines
By default, all analog lines in the system are assigned to line appearance buttons when the system is installed.
Lines are assigned for all users starting from button 03 upwards in order of line numbering.
·
Line Assignment
Through individual user button programming, any programmable button can be configured as a line
appearance for a particular line.
·
Auto Attendant Coverage
Each line can be configured to send unanswered calls to an auto attendant after a set delay (which can be set to 0
for immediate answer). This can be set to operate when the system is in day and or night service. This is done
using the VMS Schedule, VMS Delay - Day, VMS Delay - Night and VMS Auto Attendant settings of each
line.
The following methods can be used to override the normal call routing detailed above:
·
DID Mapping
For PRI and T1 trunks, if the incoming call matches a configured DID and or ICLID number, the Coverage
Destination setting for the DID/ICLID match is used rather than the line's Coverage Destination. DID mapping
cannot be done through the phone based administration menus.
·
SIP Call by Call Table
For SIP trunks, if the incoming call matches a configured URI, it is presented to the extension or group specified in
the SIP line's Call by Call Table. SIP call control cannot be done through the phone based administration menus.
·
Night Service Group
Switching on night service changes the alerting for some lines and the delayed auto attendant coverage (VMS
Schedule) operation.
PBX System Mode
Incoming call routing in PBX System mode is similar to that in Key System mode except for the following:
·
Calling Groups
183
These additional 4 groups are available as a destination for calls. They can be selected as the destination in the
Coverage Destination selection of trunks and in DID Mapping/SIP Call-by-Call tables.
·
Operator Group
193
This additional group is available as a destination for calls in DID Mapping and SIP Call-by-Call settings. In PBX
mode, this group is the default Coverage Destination and is shown in Line Coverage Extension as the value 75. If
coverage to the Operator Group is not desired, assign an extension to the line coverage extension or assign the
line to the hunt group using group call distribution. Getting incoming calls on the line to the voicemail collect
requires using system web management.
Phone Based Administration
IP Office Basic Edition
75
77
273
Comments on this document? infodev@avaya.com
- Issue 6a (Thursday, February 22, 2018)
Page 58