Please enable JavaScript to view this site.

IP Office Basic Edition - Basic Edition Manager R11.1

This menu is accessed from the System page by selecting Update Trunk Configurations.

This menu is accessed from the Admin Tasks list by selecting Trunks.

If a trunk with the Line Type of Analog Trunk is selected in the list of installed trunks, its settings are displayed below the list of installed trunks. IP Office Manager can be used to apply an existing trunk template to an analog trunk.

Installed Trunks
This table displays information about the trunk cards installed in the phone system. Selecting a trunk in the list displays its trunk settings below the list.

Line Number: Information only, not editable.

Line Type: Not Editable
This value indicates the type of trunk. The menu fields and sub-menus will vary depending on the Line Type.

Line Subtype
This option is not used for analog trunks.

Card/Module
Indicates the card slot or expansion module being used for the trunk device providing the line. 1 to 4 match the slots on the front of the phone system from left to right. Expansion modules are numbered from 6 upwards.

Number of Channels
The number of channels supported by a trunk depends on the Line Type and Line Subtype. Each channels can be used for a separate external call (incoming or outgoing) and can be represented by a line appearance button.

For analog trunks, each trunk supports just one call (one channel).

Advanced Setup
This hot link option calls up a further window that is used to display and edit additional settings for the selected trunk and its trunk channels.

Analog Trunk Setup

Appearance ID: Default = Auto-assigned
This number is used to uniquely identify the telephone line or channel. The number can be assigned to programmable buttons on extensions to allow the users to make and answer calls on that line or channel.

Hold Disconnect Time: Default = 500ms
Also known as Disconnect Clear or Reliable Disconnect. This is a method used by the analog line provider to signal that the call has ended.

Coverage Destination: Default = None. System Mode = Key System
This option sets where incoming calls should alert in addition to alerting on those extension that have a line appearance button programmed for the line. When the phone system is in night service mode, calls alert at the members of the Night Service group.


None
If set to None, incoming calls will only alert on user extensions with line appearance buttons that match the line's Appearance ID.


Extension
Route incoming calls to a particular extension.


Phantom Extension
IP Office Release 6.1+ supports phantom extensions. One of these can be selected as the destination for calls.


Hunt Group
Incoming calls can be routed to one of the 6 rotary hunt groups.


Calling Group
For systems with their System Mode set to PBX System, incoming calls can be routed to one of the 4 collective calling groups.


Operator Group
For systems with their System Mode set to PBX System, incoming calls are routed to the Operator Group.


Voicemail
Route incoming calls to the systems voicemail to collect messages. This requires the caller to know the mailbox number and passcode.

Unique Line Ringing: Default = 1. Software level = 6.1+.
Selects the ring pattern that should be used for calls when alerting on an extension. Calls forwarded, sent to call coverage or to a hunt group will always use the line ring pattern. Calls direct to an extension will use the line ringing pattern unless the user has Override Line Ringing set. Not used for calls presented to the user as a member of the Operator group. This feature is also not used for BST phones.

 

 

Performance figures, data and operation quoted in this document are typical and must be specifically confirmed in writing by Avaya before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments at its own discretion. The publication of information in this document does not imply freedom from patent or any other protective rights of Avaya or others. All trademarks identified by ™, ® or © are registered trademarks or trademarks respectively are the property of their respective owners.

Use of this site indicates acceptance of its cookies and analytics, and acceptance of the Avaya privacy policy.

© 2020 AVAYA
Issue 10.a.–
Thursday, July 23, 2020