Avaya Calling Profile Settings

Last Updated : Apr 03, 2026 |
Prolog information
Metadata
Keywords:
You can use the following settings in the profiles you create for Avaya Calling. See Enabling Avaya Calling Support for the Customer Domain.

Connection Settings

Each profile must include values for the following settings:
Setting
Description
Name
This is the name of the profile. If you add multiple profiles, users will see and select the name during login. Maximum 14 characters. For example: "Name": "Office"
Address
Set to match to the address of the IP Office server. For example: "Address": "ipoffice.example.com"
  • For access from both internal and public networks, this FQDN should resolve to the ASBC public address (B1) on public DNS, and ASBC internal address (A1) on internal DNS.
AccountsToken
This setting controls whether the Chrome extension can use SSO login features:
  • "AccountsToken": true enables SSO login.
  • "AccountsToken": false disables SSO login.
LogDownload
This setting controls whether users can download extension logs from their Chrome extension. See Getting the Chrome Extension Logs.
  • "LogDownload": true enables log downloads.
  • "LogDownload": false disables log downloads.
STUNHost
The address of the STUN host used for WebRTC. For example, "STUNHost": "absce.example.com"
  • For access from both internal and public networks, the FQDN must resolve to the ASBCE public address on public DNS, and ASBCE internal address on internal DNS.
STUNPort
The standard STUN port is 3478. For example: "STUNPort": "3478"
AutoFailover
This setting controls whether the client should use the IP Office resiliency features:
  • If set to "AutoFailover": true, the client will log in to the secondary one-X Portal server when the primary one-X Portal is not available.
  • If set to "AutoFailover": false or not set, the client will not use resiliency.
DialRule
This settings controls how the dialing rules used by the Chrome extension are determined:
  • "DialRule": false enables users to configure their dialing rules in the Avaya Calling extension settings.
  • "DialRule": true uses the dialing rules defined by the settings in the table below.
  • Not including DialRule setting disabled dial rules.

Dialing Settings

If you include "DialRule": true in a profile, you can also use the following additional settings.
Setting
Description
OutsidePrefix
Set to match the prefix used on the telephone system for outgoing external calls. For example: "OutsidePrefix": "9"
CountryCode
Set to match the country code for call. For example: "CountryCode": "1" or "CountryCode": "44"
CityCode
Set to the match the area code for the profile users. If the profile covers multiple areas, you can use a common separated list of codes. For example: "CityCode": "555" or "CityCode": "555,777"
PbxPrefix
If the telephone system has its own prefix within a network, specify the prefix.
LongDistancePrefix
Specify the prefix added to external calls to indicate national (non-local) numbers. In North America this is usually 1. For example: "LongDistancePrefix": "1"
InternationalPrefix
Specify the prefixed added to eternal calls to indicate international numbers. In North America this is usually 011. For example: "InternationalPrefix": "011"
ExtensionLength
Specify the length of internal extension numbers. If necessary, you can use a comma separated list. For example: "ExtensionLength": "3,4"
NationalLength
Specify the length on national numbers, including the area code. If necessary, you can use a comma-separated list of lengths. For example: "NationalLength": "10,11"
RemoveAreaCode
In areas that allow local calls without the area code, set this value to true. For example: "RemoveAreaCode": true
ApplyToPlusNumber
Specifies whether the dialing rules apply to + format numbers. For example: "ApplyToPlusNumber": false
Related links
Enabling Avaya Calling Support for the Customer Domain