Please enable JavaScript to view this site.

IP Office Basic Edition - Web Manager R11.1

> Configuration Menus > System > SIP Trunks

SIP Channel List

Scroll Prev Up Next More

This menu is accessed by selecting System and then SIP Trunks from the menu bar. Select the trunk required and click on Details. Click on the web edit icon edit icon in the Channel Setup panel.

web sip channels

Channel
Channel number, cannot be edited.

Appearance ID
Appearance ID numbers can be used to associate each channel a Line Appearance button on phones that support button programming. That button can then be used to make and answer calls using the channel. The line appearance ID for each channel is automatically assigned to those channels that have their Direction set as Bothways.

Display Name: Default = Use Authentication Name
This field sets the 'Name' value for SIP calls.

Authentication Name
When making a call, some service providers will often send an authentication challenge to validate the call before it is connected. This challenge requires the INVITE is re-submitted with Authentication data, including a network account name (provided by the service provider during installation). The network account name is the “Auth name”. It can be blank, in which case the Local URI is used.

Password: Default = Blank.
This value is provided by the SIP ITSP.

! WARNING - Reboot Required
Changing this setting requires the system to be rebooted for the change to take effect. Rebooting the system will end all calls currently in progress.

Details
Clicking on Details will display the additional settings for the selected SIP trunk channel.
web sip channel

Appearance ID
Appearance ID numbers can be used to associate each channel a Line Appearance button on phones that support button programming. That button can then be used to make and answer calls using the channel. The line appearance ID for each channel is automatically assigned to those channels that have their Direction set as Bothways.

Direction: Default = Bothways
Sets the allowed operation mode of the line. For systems running in Key mode, a line can be set to either Bothway (incoming and outgoing) or Incoming Call by Call (incoming only). For a system running in PBX mode, a line can be set to either Bothway (incoming and outgoing) or Call by Call (incoming and outgoing).

! WARNING - Reboot Required
Changing this setting requires the system to be rebooted for the change to take effect. Rebooting the system will end all calls currently in progress.

Bothway
When set to Bothway, incoming calls are presented to line appearance buttons matching the channels Appearance ID and to the channels Coverage Destination if set. For Key mode systems, outgoing calls are routed to the channel by pressing the matching line appearance button selection or by automatic line selection. In addition, on PBX mode systems, outgoing calls can be routed to the channel by including the line appearance in the ARS Selector that matches the dialed digits.

Incoming Call by Call
For systems running in Key mode, when set to Incoming Call by Call, incoming calls are routed using the Call by Call table. The Appearance ID, Coverage Destination and Ring Pattern fields are greyed-out as those settings are not applied. The trunk channel is not used for outgoing calls.

Call by Call
For systems running in PBX mode, when set to Call by Call, incoming calls are routed using the Call by Call table. The Appearance ID, Coverage Destination and Ring Pattern fields are greyed-out as those settings are not applied. In PBX mode, call by call entries can be used given ARS selector numbers (see below) which allow the trunk channel to also be used for outgoing calls.

Local URI:
The user part of the SIP URI. This specifies the contents of the FROM field when making a call (sending an INVITE).

! WARNING - Reboot Required
Changing this setting requires the system to be rebooted for the change to take effect. Rebooting the system will end all calls currently in progress.

Anonymous:
Withhold the calling parties information.

! WARNING - Reboot Required
Changing this setting requires the system to be rebooted for the change to take effect. Rebooting the system will end all calls currently in progress.

Registration Required
When selected, each local URI with unique Authentication credentials will register independently.

P-Assert-ID
If this field is configured, the channel can be used in SIPConnect Option 1 model for separating Public and Private PSTN identity (Sipconnect technical recommendation v 10, section 12.1.1). You can only use Explicit CLI configurations over SIP if using Option1 model for identity. In this case, calls over this channel will always have a fixed P-Assert-ID, but the From field may vary.

Coverage Destination: Default = None.
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
A phantom extension 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 Mode set to PBX, incoming calls can be routed to one of these 4 ring all groups.


Operator Group
For systems with their Mode set to PBX, 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.

! WARNING - Reboot Required
Changing this setting requires the system to be rebooted for the change to take effect. Rebooting the system will end all calls currently in progress.

The Coverage Destination is not used for SIP trunks with their direction set to Incoming Call by Call.

Ring Pattern: Default = 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.

! WARNING - Reboot Required
Changing this setting requires the system to be rebooted for the change to take effect. Rebooting the system will end all calls currently in progress.

Delay - Day: Default = 2. Range = 0 to 6 (number of rings).
Set the number of rings before an unanswered call should be redirected the selected auto attendant when the system is not running in night service mode and the VMS Schedule is set to Always or Days Only.

Delay - Night: Default = 2. Range = 0 to 6 (number of rings).
Sets the number of rings before an unanswered call should be redirected to the selected auto attendant when the system is running in night service mode and the VMS Schedule is set to Always or Night Only.

Schedule: Default = Never.
This option determines when the VMS Delay settings above should be used and unanswered calls redirected to the selected auto attendant. The options are:

Always
Redirect calls when the system is in both day and night service modes.

Day Only
Redirect calls only when the system is not in night service.

Night Only
Redirect calls only when the system is in night service.

Never
Do not redirect calls.

Auto Attendant: Default = Auto Attendant 1.
This field allows selection of which auto attendant is used.

 

 

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.

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