Specifies whether the 100rel option tag is included in the SIP INVITE header field.
The options are the following:
A
AADS_URL
When you specify the URL, the phone obtains the configuration from the Avaya Aura Device Services (AADS) and uses this configuration to enable the Single sign-on (SSO) feature.
The phone ignores the GUESTLOGINSTAT and ENABLE_PHONE_LOCK parameters, when you specify AADS_URL.
The URL can be 0-255 ASCII characters without space. The data type is String. The AADS URL is an HTTPS protocol. For example,https://example.com:443/acs/resources/configurations
Note:
Avaya J129 IP Phone does not support the SSO feature.
AADS_CONTACT_URL
Null
Specifies the URL path of the HTTPS server to find and access the contact management system from AADS. The valid value is a string of 0 to 255 ASCII characters without spaces. This field is empty by default.
ACOUSTIC_EXPOSURE_PROTECT_MODE_DEFAULT
Specifies the long-term acoustic exposure protection mode default setting.
The options are the following:
Note:
Avaya J129 IP Phone does not support long-term acoustic exposure protection.
ADMIN_LOGIN_ATTEMPT_ALLOWED
10
Specifies the allowed number of failed attempts to enter the access code before the local or craft procedures gets locked. Valid values are from 1 to 20.
ADMIN_LOGIN_LOCKED_TIME
10
Specifies the duration for lockout when a user reaches the maximum attempts limit for accessing the Administration menu.
Valid values are from 5 minutes to 1440 minutes.
ADMIN_PASSWORD
27238
Specifies an access code for accessing the Admin menu.
Valid values are from 6 to 31 alphanumeric characters including upper case, lower case characters and special characters. However, double quote character (“) cannot be used for a value of this parameter.
Note:
If this parameter length is set below 6 or above 31 alphanumeric characters, then the parameter is treated as not defined.
If this parameter is set in the 46xxsettings.txt file, then it replaces PROCPSWD parameter.
If you set ADMIN_PASSWORD in the Avaya Aura® System Manager you require at least Avaya Aura® System Manager 7.1.0.
Setting this parameter through PPM is more secure because this file can usually be accessed and read by anyone on the network. Setting the value in this file is intended primarily for configurations with versions of phone or if server software that do not support setting this value from the server.
AGCHAND
1
Specifies the status of Automatic Gain Control (AGC) for the handset.
The options are the following:
AGCHEAD
1
Specifies the status of Automatic Gain Control (AGC) for the headset.
The options are the following:
AGCSPKR
1
Specifies the status of Automatic Gain Control (AGC) for the speaker.
The options are the following:
AGTGREETINGSTAT
Specifies whether the Agent Greetings feature is enabled or not.
The options are the following:
AGTGREETLOGOUTDEL
Specifies whether the phone deletes agent greeting messages upon the agent logout.
AGENTGREETINGSDELAY
Specifies delat time in milliseconds between call pickup and agent greeting message playback start.
Valid values are 0-3000
ALLOW_DND_SAC_LINK_CHANGE
0
Specifies if the user is allowed to change the DND and SAC button link. If the change is allowed, the menu to set the DND and SAC link is displayed.
The options are the following:
Important:
This parameter is not supported from firmware version 4.0.8.0 and later. For firmware version 4.0.8.0 and later, the parameter DND_SAC_LINK provides the enhanced functionality.
Note:
Avaya J129 IP Phone does not support this feature.
ALWAYS_FAVORITES_FOR_BUTTON_MODULES
Specifies whether the Always Favorites on Button Module feature is enabled or not.
The options are the following:
ALLOW_GUEST_SESSION_PERSISTENCE
Specifies whether a Guest Login session continues after the phone reboots.
This parameter controls the behavior of the phone when a guest user is logged in and the phone reboots. Depending on the configuration you set, the phone either restores the Guest Login session or logs in the primary user.
The options are the following:
Note:
This parameter is not applicable to SSO Guest Login.
APPLICATION_HEADER_APPEARANCE_CONTEXT
Specifies whether appearances context will be shown on the Application Header Line in Phone List View. This Application Header context relies on SHORT_FORM_USER_ID and DISPLAY_NAME to display the Application Header line context appropriately.
The options are the following:
0: appearances context will not be shown on the Application Header Line (default)
1: appearances context will be shown on the Application Header Line
If this parameter is enabled but both SHORT_FORM_USER_ID and DISPLAY_NAME are null, then the userid of the registered SIP user will be displayed.
If the Agent login and logout feature is enabled on Avaya J159 IP Phone, the value for this parameter must be 0.
Note:
Avaya J129 IP Phone does not support this parameter.
APPNAME_IN_USE
Null
Used to check which firmware version is installed on the phone to perform a corresponding action, for example:IF $APPNAME_IN_USE SEQ 4.0.2.0.11 GOTO CROSSGRADE
ASTCONFIRMATION
Specifies the number of seconds that the phone waits to validate an active subscription when it subscribes to the avaya-cm-feature-status package.
Valid values are
.
AUDASYS
Specifies the current setting for audible alerting and whether users can change this setting.
Valid values:
The values 4 to 19 turns on audible alerting and sets the volume levels from 1 (minimum) to 16 (maximum). User cannot adjust the ringer volume.
AUDIOENV
Specifies the audio environment index and enables you to customize the phone's audio performance.
Valid values are
.
This parameter affects settings for AGC dynamic range, handset and headset noise reduction thresholds, and headset transmit gain. Always consult Avaya before changing this parameter.
This parameter affects settings for AGC dynamic range and handset noise reduction thresholds. Always consult Avaya before changing this parameter.
AUDIOPATH
Specifies the audio path for the phone.
The options are the following:
AUDIOSTHD
Specifies the level of sidetone in the headset.
The options are the following:
Note:
Avaya J129 IP Phone does not support this parameter.
AUDIOSTHS
Specifies the level of sidetone in the handset.
The options are the following:
AUTH
Specifies whether the phones use only HTTPS file servers to download the configuration and software files. The phone sets the value of AUTH to 1 only when the parameter value is supplied to the phone from an HTTPS server.
Valid values:
If the current value of AUTH is
, reset the phone to defaults.
AUTHCTRLSTAT
Specifies if the enhanced debugging capabilities can be activated from the SSH server by the Avaya technicians only.
The options are the following:
The parameter must be set to
when the debugging period completes.
AUTO_SELECT_ANY_IDLE_APPR
Specifies that any idle call appearance (primary or bridged) can be automatically selected. This parameter works along with the parameter CONF_TRANS_ON_PRIMARY_APPR.
The options are the following:
.
.
Note:
Avaya J129 IP Phone does not support this feature.
AUTO_UNMUTE
Specifies whether the call is not in a muted state when the transducer is changed. This feature is applied on all types of calls.
The options are the following:
Note:
Only Avaya J159 IP Phone and Avaya J169/J179 IP Phone supports this feature.
AUTOINTERCOM_CALL_LOG_MODE
Specifies whether the phone logs an auto-answered and auto-muted auto-intercom call as an answered call or a missed call. If there is no defined user action during this call, the phone logs this call as a missed call. You can specify if pressing the Mute button is the required user action or the user can press any key on the phone to log the call as an answered call.
If the user does not press the required key, the phone logs the call as a missed call.
The following are the valid options:
AUTOMATIC_UPDATE_DAYS
Specifies the days of automatic update. This parameter is applicable only when AUTOMATIC_UPDATE_POLICY is set to value 2 or 3.
Mon, Tue, Wed, Thu, Fri, Sat, Sun for weekly update.
xMon, xTue, xWed, xThu, xFri, xSat, xSun for monthly update. where x is the occurrence of the month. For example: 2Mon, means second Monday of the month.
The phone uses the default value if you set invalid values.
Example for weekly update SET AUTOMATIC_UPDATE_DAYS "Sun"
Example for monthly update SET AUTOMATIC_UPDATE_DAYS "1Sun"
AUTOMATIC_UPGRADE_INSTALL_DATE_TIME
Specifies the date and time after which the new firmware is downloaded and installed. After this date and time is reached, the phone uses the settings of AUTOMATIC_UPDATE_DAYS and AUTOMATIC_UPDATE_WINDOW to trigger firmware download reboot. If this parameter value is not set, then the phone uses AUTOMATIC_UPDATE_POLICY, AUTOMATIC_UPDATE_DAYS, and AUTOMATIC_UPDATE_WINDOW to trigger the firmware download.
AUTOMATIC_UPGRADE_INSTALL_DATE_TIME is applicable if AUTOMATIC_UPDATE_POLICY is set to 1, 2, or 3.
The format is YYYY-MM-DDThh:mm, where:
YYYY is 4 digit numeric value for year, MM is 2 digit numeric value for month
DD is 2 digit numeric value for date, which is 1 to 31
T is the time separator
hh is 2 digit numeric value for hours of the day which is 00 to 23
mm is 2 digit numeric value for minutes of the hour, which is 00 to 59
For example: SET AUTOMATIC_UPGRADE_INSTALL_DATE_TIME 2015-04-12T23:20
This parameter applies to the phone local time as defined by the following parameters:
GMTOFFSET
DAYLIGHT_SAVING_SETTING_MODE
DSTOFFSET
DSTSTART
DSTSTOP
AUTOMATIC_UPDATE_REBOOT_PROMPT
Specifies if the user is prompted for confirmation when the phone detects a new software update that requires a reboot.
Reboot is triggered immediately for configuration changes that require a reboot. Update policy parameters such as AUTOMATIC_UPDATE_POLICY, AUTOMATIC_UPDATE_DAYS, AUTOMATIC_UPDATE_WINDOW, and AUTOMATIC_UPGRADE_INSTALL_DATE_TIME are updated without a reboot.
The options are the following:
AUTOMATIC_UPDATE_POLICY
Specifies the automatic update frequency.
The options are the following:
AUTOMATIC_UPDATE_WINDOW
Specifies the window for the automatic update of the phone. Value m, n specifies the hours to Start and End the window for automatic update, where m, n are numeric values ranging from 0 to 23. For example, 3,4 means the automatic update Starts and Ends between 3 AM and 4 AM.
Each phone picks a random time between this specified window.
The time is in 24hr format.
For example SET AUTOMATIC_UPDATE_WINDOW "23,0"
Sets one hour window from 11 PM to 00 AM for the automatic update.
AWAY_TIMER
Controls whether the phone reports an away state.
The options are the following:
AWAY_TIMER_VALUE
Specifies the number of minutes of idle time after which the phone assumes that the user is away from the phone.
The range is
BACKGROUND_IMAGE
Specifies a list of custom background images that you can upload to the provisioning server. Users can set these background images on their phone.
The phone supports up to 5 background images with the following limitations:
Software version 4.0.11 and earlier support the .jpeg format. Software version 4.0.12 and later support the .jpg format.
The file size can be up to 256 KB.
The file names are case sensitive.
Avaya J139 IP Phone, Avaya J159 IP Phone, Avaya J169/J179 IP Phone screen resolution is 320x240 pixels. Avaya J169/J179 IP Phone and and Avaya J189 IP Phone color depth is 16 bits. and Avaya J189 IP Phone screen resolution is 800x480 pixels. Avaya J169/J179 IP Phone phones support grayscale color spaces and other color display phones support yCbCr color spaces.
The file names must be comma-separated without intervening spaces. You can define absolute URLs, absolute paths, relative paths, macros, or file names for the image files.
An absolute URL. For example, http://username:password@provisioning.example.com:8088/path/image1.jpg
If the server requires credential authentication, the credentials must be defined in the URL string.
An absolute path that ignores HTTPDIR or TLSDIR. For example,/path/image1.jpg
A relative path that is appended to HTTPDIR or TLSDIR. For example,path/image1.jpg
Macros. The actual values replace the macros. For example,
"$SERIALNO"is replaced with the phone serial number in uppercase.
"$MACADDR"is replaced with the phone MAC address in lowercase without intervening colons.
"$MODEL4"is replaced with the four-character phone model number in uppercase.
File name.
For example, SET BACKGROUND_IMAGE "background_example1.jpg,background_example2.jpg"
BACKGROUND_IMAGE_DISPLAY
Specifies the background image to be displayed on the phone.
The default value is empty. The value is separated by commas without any intervening spaces.
To select one of the seven built-in default images, specify a value from 0 to 6.
0: To select default image 1.
1: To select default image 2.
2: To select default image 3.
3: To select default image 4.
4: To select default image 5.
5: To select default image 6.
6: To select default image 7.
You can define a file name if BACKGROUND_IMAGE is defined with the same file name.
Note:
If BACKGROUND_IMAGE_SELECTABLE is set to 1, then the end user may override this setting.
Note:
Avaya J129 IP Phone does not support this feature.
BACKGROUND_IMAGE_DISPLAY_JEM
Specifies the background image to be displayed on the Avaya J100 Expansion Module.
The default value is empty.
To select one of the seven built-in default images, specify a value from 0 to 6.
0: To select default image 1.
1: To select default image 2.
2: To select default image 3.
3: To select default image 4.
4: To select default image 5.
5: To select default image 6.
6: To select default image 7.
You can define a file name if BACKGROUND_IMAGE_JEM is defined with the same file name.
Note:
If the parameter is not defined, then the phone will use Default image 1.
BACKGROUND_IMAGE_JEM
Specifies a list of background images for the Avaya J100 Expansion Module display.
Avaya J100 Expansion Module supports up to 5 background images with the following limitations:
The expansion module supports only the .jpg formal.
The maximum file size is 256 KB.
The file names are case sensitive.
The color depth is limited to 16 bits.
The Avaya J100 Expansion Module has a resolution of 272 x 480 pixels.
The file names must be comma-separated without intervening spaces. You can define absolute URLs, absolute paths, relative paths, macros, or file names for the image files.
An absolute URL. For example, http://username:password@provisioning.example.com:8088/path/image1.jpg
If the server requires credential authentication, the credentials must be defined in the URL string.
An absolute path that ignores HTTPDIR or TLSDIR. For example,/path/image1.jpg
A relative path that is appended to HTTPDIR or TLSDIR. For example,path/image1.jpg
Macros. The actual values replace the macros. For example,
"$SERIALNO"is replaced with the phone serial number in uppercase.
"$MACADDR"is replaced with the phone MAC address in lowercase without intervening colons.
"$MODEL4"is replaced with the four-character phone model number in uppercase.
File name.
For example, SET BACKGROUND_IMAGE_JEM "jem_background_example1.jpg,jem_background_example2.jpg"
BACKGROUND_IMAGE_JEM_FOLLOW_PRIMARY
Specifies whether the Avaya J100 Expansion Module background image always follows the primary display or can have a separate background image.
The options are:
BACKGROUND_IMAGE_SELECTABLE
Enables the end user to select background images.
The options are the following:
0: The user can not use a background images from the phone UI.
1: The user can select a background images from the phone UI.
Note:
Avaya J129 IP Phone does not support this feature.
BACKGROUND_IMAGE_SELECTABLE_JEM
Specifies whether the user can select a background image.
The options are:
0: The end user is not allowed to choose the Avaya J100 Expansion Module background image. The value set by an administrator is used.
1: The end user is allowed to choose the Avaya J100 Expansion Module background image.
BACKGROUND_IMAGE_SECONDARY
Specifies a list of background images for the secondary display. The phone supports up to 5 background images with the following limitations:
Software version 4.0.11 and earlier support the .jpeg format. Software version 4.0.12 and later support the .jpg format.
The maximum file size is 256 KB.
The file names are case sensitive.
The file names must be comma-separated without intervening spaces. You can define absolute URLs, absolute paths, relative paths, macros, or file names for the image files.
An absolute URL. For example, http://username:password@provisioning.example.com:8088/path/image1.jpg
If the server requires credential authentication, the credentials must be defined in the URL string.
An absolute path that ignores HTTPDIR or TLSDIR. For example,/path/image1.jpg
A relative path that is appended to HTTPDIR or TLSDIR. For example,path/image1.jpg
Macros. The actual values replace the macros. For example,
"$SERIALNO"is replaced with the phone serial number in uppercase.
"$MACADDR"is replaced with the phone MAC address in lowercase without intervening colons.
"$MODEL4"is replaced with the four-character phone model number in uppercase.
File name.
For example, SET BACKGROUND_IMAGE_SECONDARY "secondary_background_example1.jpg,secondary_background_example2.jpg"
Note:
This parameter is supported only by Avaya J159 IP Phone and Avaya J189 IP Phone.
BACKGROUND_IMAGE_DISPLAY_SECONDARY
Specifies the background image to be displayed on the Secondary screen. The file name will be one of the file names listed in BACKGROUND_IMAGE_SECONDARY.
The default value is empty. The value is separated by commas without any intervening spaces.
To select one of the seven built-in default images, specify a value from 0 to 6.
0: To select default image 1.
1: To select default image 2.
2: To select default image 3.
3: To select default image 4.
4: To select default image 5.
5: To select default image 6.
6: To select default image 7.
You can define a file name if BACKGROUND_IMAGE_SECONDARY is defined with the same file name.
Note:
If BACKGROUND_IMAGE_SELECTABLE_SECONDARY is set to 1 then the end user may override this setting.
BACKGROUND_IMAGE_SELECTABLE_SECONDARY
Enables the end user to select background images for the secondary screen.
The options are the following:
0: The user can not use a background images from the phone UI.
1: The user can select a background images from the phone UI.
This parameter overrides the value configured using BACKGROUND_IMAGE_DISPLAY_SECONDARY parameter
Note:
This parameter is supported only in Avaya J159 IP Phone
BACKLIGHT_SELECTABLE
Specifies whether backlight timer is selected by the administrator (BAKLIGHTOFF) or user.
The options are the following:
0: To set Backlight Timer value from the 46xxsettings.txt file.
1: To set Backlight Timer value according to user settings.
Note:
Only Avaya J169/J179 IP Phone supports this feature.
BAKLIGHTOFF
Specifies the number of minutes of idle time after which the display backlight will be turned off.
Phones with gray-scale displays do not completely turn backlight off, they set it to the lowest non-off level.
Valid values are 0 through 999.
A value of
For ENERGY STAR compliance on applicable phones, a value of 20 is recommended.
BLOCK_CERTIFICATE_WILDCARDS
Specifies whether the endpoint will accept server identity certificates with wildcards.
The options are the following:
BLOCK_PPM_CONTACTS_SEARCH
Specifies whether the user can select System contacts (PPM contacts) to be included in a search as part of the Contact Search feature.
Valid values are:
BLUETOOTHSTAT
Specifies whether the user is given an option to enable the Bluetooth.
The options are the following:
Note:
This parameter is supported only in Avaya J159 IP Phone, Avaya J179 IP Phone, and Avaya J189 IP Phone
BRANDING_VOLUME
Specifies the volume level at which the Avaya audio brand is played.
The options are the following:
BRURI
Provides the capability to send a phone report to a server with the URI of the server defined by this parameter. To send the report, go to Main MenuAdminDebugPhone report.
BUTTON_MAPPINGS
Specifies a list of Button and Status pairs that change the operation of some of the buttons on the phone.
Button and Status pairs are separated by commas without any intervening spaces.
Valid button values are
,
.
Valid Status values are
.
The options are the following:
BUSY_INDICATOR_LED_PROFILE
Specifies if the LED state and the Busy indicator icon on the phone screen synchronize when the monitoring station views the status of monitored stations.
Valid values:
If the monitored station is idle, the Busy indicator icon on the monitoring station is Green and the LED is off.
If the monitored station is busy, the Busy indicator icon on the monitoring station is Red and the LED is Green.
C
CALL_DECLINE_POLICY
Specifies whether the user can decline the incoming call. You can enable and disable the feature using the following options:
The options are:
0: The feature is disabled, the Decline soft key does not appear on the phone screen for an incoming call. This is the default value.
1: 486 method is used. By selecting this value you enable the Call decline policy for the user. 486 method indicates that the call ringing location is not available to take the call.
2: 603 method is used. By selecting this value you enable the Call decline policy for the user. 603 method indicates that no location is available to take the call.
CALLFWD_CHAIN_ORDER
The "Forwarded by" details that are shown for incoming calls that have been forwarded by another user. Specifies which user information to be displayed on an incoming call if there are multiple forwards before being received as an incoming call.
The options are the followings:
Note:
Avaya J129 IP Phone does not support this feature.
CALL_ON_OFFHOOK
Specifies the call is placed when the user goes off-hook while highlighting a call target in selected applications.
You can also provide access to enable or disable the user from changing the feature settings.
If you enable CALL_ON_OFFHOOK, the phone ignores the values of the parameter EDIT_DIALING_FROM_CALL_LOG .
If the forced value is not set, you can give the access to user to change this setting in the Phone menu.
The options are:
Note:
Avaya J129 IP Phone does not support the call on off-hook feature.
CALLFWDDELAY
Sets the number of ring cycles before the call is forwarded to the forward or coverage address. The default delay is one ring cycle.
CC_INFO_TIMER
Specifies the duration, in hours, of the subscription to the SIP CC-Info event package.
Valid values are 1 through 24.
Valid values are 0 through 24. The default value is 8.
When the value is 0, the subscription doesn't expire. Use value 0 for the Service Observer feature through CTI.
CERT_WARNING_DAYS
Specifies the number of days before the expiration of a certificate that a warning will first appear on the phone screen. Certificates include trusted certificates, OCSP certificates and identity certificate. Log and syslog message will also be generated. The warning will reappear every seven days. Valid values are from 0 to 99.
The options are the following:
CERT_WARNING_DAYS_EASG
Specifies how many days before the expiration of EASG product certificate that a warning should first appear on the phone screen. Syslog message will be also generated. Valid values are from 90 to 730.
CLDISPCONTENT
Specifies whether the name, the number, or both will be displayed for Call Log entries.
The options are the following:
Note:
Avaya J129 IP Phone and Avaya J139 IP Phone do not support this parameter.
CODEC_PRIORITY
OPUS,G722,G711U,G711A,G726,G729
Specifies the priority order for all codecs, supported by the phones.
Valid value is a string of correct codec names, separated by a comma with no blank spaces. For example:
SET CODEC_PRIORITY OPUS,G722,G711U,G711A,G726,G729
If values are entered incorrectly or the phone does not support the listed codec, the value is ignored.
CONF_TRANS_ON_PRIMARY_APPR
Determines conference and transfer setup whether to use idle primary call appearance or idle bridged call appearance.
The options are the following:
Note:
Avaya J129 IP Phone does not support this feature.
CONFERENCE_FACTORY_URI
Specifies the URI for Avaya Aura Conferencing.
Valid values contain zero or one URI, where a URI consists of a dial string followed by @, and then the domain name, which must match the routing pattern configured in System Manager for Adhoc Conferencing.
Depending on the dial plan, the dial string can need a prefix code, such as a 9 to get an outside line. The domain portion of the URI can be in the form of an IP address or an FQDN.
The value can contain 0 to 255 characters. The default value is null.
CONFERENCE_TYPE
Determines the selection of the Conference Method.
The options are the following:
If the parameter is set to a value that is outside the range then default value is selected.
CONFIG_SERVER_SECURE_MODE
Specifies whether HTTP or HTTPS is used to access the configuration server.
The options are the following:
CONTACT_NAME_FORMAT
Specifies how contact names are displayed.
The options are the following:
CONTACT_SEARCH_MODE
0
Specifies the AADS contact search mode configured by the administrator.
When you configure the basic mode, the search requires basic parameters, such as name or extension number of the contact, whereas the advanced search requires additional parameters, such as the location or department of the contact.
When you configure the Forced Basic or Forced Advanced mode, you restrict the user from searching either with the basic or the advanced search mode from the phone user interface.
Valid values:
CONTROLLER_SEARCH_INTERVAL
Specifies the number of seconds the phone waits to complete the maintenance check for monitored controllers.
Valid values are 4 through 3600.
CONNECTION_REUSE
Specifies whether the phone will use two UDP, TCP, or TLS connection (for both outbound and inbound) or one UDP, TCP, or TLS connection.
The options are the following:
Note:
On Avaya J129 IP Phone, only
COUNTRY
Used for network call progress tones.
For Argentina use keyword
For Australia use keyword
For Brazil use keyword
For Canada use keyword
For France use keyword
For Germany use keyword
For Italy use keyword
For Ireland use keyword
For Mexico use keyword
For Spain use keyword
For United Kingdom use keyword
For United States use keyword
Country names with spaces must be enclosed in double quotes.
CURRENT_LOGO
Null
Specifies if custom logo or wallpaper is selected for display.
The CURRENT_LOGO is used in the following cases:
The phone is not registered to Avaya Aura® Session Manager.
The phone is registered to Avaya Aura® Session Manager and
there is no information stored for the current logo file for this specific user, and
there is no support of Profile Settings in the Endpoint Template. This is supported by Avaya Aura® System Manager 6.3.8 and later.
Note:
Only Avaya J169/J179 IP Phone supports this parameter.
CUSTOMIZATION_MODE
Specifies the customization mode.
The options are the following:
D
DATEFORMAT
Specifies the format for dates displayed in the phone. The phone screen displays mm or dd in topline and Recents application. yy or yyyy is displayed only on the phone ScreenSaver when Date is enabled. Only / — . separators are supported.
Use
Use
Use
Use
From the software version 4.1.0 and later, Avaya J139 IP Phone, Avaya J159 IP Phone, Avaya J169/J179 IP Phone, and Avaya J189 IP Phone supports the following values:
%m/%d (Default)
%d/%m
%m.%d
%d.%m
%m-%d
%d-%m
%o-%d
If you enter any character without preceding with %, the phone displays the same.
For example, the phone topline to read mm/dd ,and the ScreenSaver to read mm/dd/yy set %m/%d/%y. Similarly for dd-mm, and dd-mm-YYYY, set %d-%m-%Y
DAYLIGHT_SAVING_SETTING_MODE
Specifies daylight savings time setting for phone.
The options are the following:
DELETE_DES_CERT
Specifies whether the installed identity certificate for profile DES will be deleted.
Valid values:
DELETE_MY_CERT
Specifies whether the installed identity certificate, using SCEP or PKCS12 file download, will be deleted.
DELETE_PKCS12_CERT
Specifies whether the installed identity certificate for profile PKCS12#1 will be deleted.
Valid values:
When parameter value is
DELETE_PKCS12_2_CERT
Specifies whether the installed identity certificate for profile PKCS12#2 will be deleted.
Valid values:
When parameter value is
DELETE_PKCS12_3_CERT
Specifies whether the installed identity certificate for profile PKCS12#3 will be deleted.
Valid values:
When parameter value is
DELETE_SCEP_CERT
Specifies whether the installed identity certificate for profile SCEP#1 will be deleted.
Valid values:
When parameter value is
DELETE_SCEP_2_CERT
Specifies whether the installed identity certificate for profile SCEP#2 will be deleted.
Valid values:
When parameter value is
DELETE_SCEP_3_CERT
Specifies whether the installed identity certificate for profile SCEP#3 will be deleted.
Valid values:
When parameter value is
DES_STAT
Specifies if DES discovery is to be attempted during the boot process if there is no configuration file server provisioned on the phone.
The options are the following:
DHCPSTAT
Specifies whether DHCPv4, DHCPv6 or both are used if IPv6 support is enabled by IPV6STAT.
Note:
DHCPv4 is always enabled in IPv4 only and dual mode. DHCPv4 is disabled in IPv6 only mode.
The options are the following:
1: run DHCPv4 only.
2: run DHCPv6 only.
3: run both DHCPv4 and DHCPv6.
DHCPSTD
Specifies whether DHCP complies with the IETF RFC 2131 standard and continues to use the expired DHCP lease.
The options are the following:
DHCPSTDV6
Specifies whether DHCPv6 will comply with the IETF RFC 8415 standard and immediately stop using an IPv6 address if the address valid lifetime expires, or whether it will enter an extended rebinding state.
The options are the following:
DIALPLAN
Specifies the dial plan used in the phone.
Dialplan accelerates dialing by eliminating the need to wait for the INTER_DIGIT_TIMEOUT timer to expire.
The value can contain 0 to 1023 characters. The default value is null.
DIGIT_MAPPING
Specifies a digit map the phone uses to match digits to ensure a complete number is dialed, to transform dialed digits, and block numbers from being dialed. ',' is used for rules separation.
Valid value is a string of alphanumeric rules. If a rule uses incorrect characters, the phone ignores it.
The preferred way of configuring this parameter is through the web interface.
DIRUSERNAME
Null
Specifies the LDAP client username.
The following characters are allowed:
0–9
a-z
A-Z
The preferred way of configuring this parameter is through the web interface.
Note:
Avaya J129 IP Phone does not support this parameter.
DIRPASSWORD
Null
Specifies the LDAP client password.
The following characters are allowed:
0–9
a-z
A-Z
The preferred way of configuring this parameter is through the web interface.
Note:
Avaya J129 IP Phone does not support this parameter.
DIRSECURE
Specifies whether to use TLS or TCP for the LDAP server.
The options are the following:
For example, SET DIRSECURE 1
There is a difference between STARTTLS and LDAPS: STARTTLS uses the same port as the LDAP protocol. The DIRSRVRPRT parameter value must be the same as the port configured for the LDAP (not for LDAPS) protocol on the server side.
The LDAPS protocol uses a port different from LDAP. The value for DIRSRVRPRT needs to correspond to server port for the LDAPS connection.
Note:
Avaya J129 IP Phone does not support this parameter.
DIRAUTHTYPE
Specifies the kind of authentication that is used if the value of the DIRUSERNAME parameter is not null.
The options are the following:
If a connection is established over TLS (DIRSECURE is set to 1 or 2), DIGEST-MD5 or PLAIN authentication mechanisms are supported.
If the connection established over TCP (DIRSECURE is set to 0) DIGEST-MD5 is the only supported mechanism.
Note:
Avaya J129 IP Phone does not support this parameter.
DIRENABLED_PLATFORM
Determines whether the LDAP directory search is enabled on the phone.
The options are the following:
Note:
Avaya J129 IP Phone does not support this parameter.
DIRNAME_FIELDS
cn
Specifies the attributes and their order, shown in the search results. Users can view other attributes, pressing the Details soft key.
The attributes, specified in this parameter must be a subset of the attributes, specified in DIRNAME_FIELDS.
For example, SET DIRNAME_FIELDS "cn,sn"
In this example, each match on a search result list displays a last name and a first name.
Note:
Avaya J129 IP Phone does not support this parameter.
DIRNUMBER_FIELDS
telephoneNumber
Specifies the LDAP fields that contain a callable number. The first number listed becomes the primary number.
For example, SET DIRNUMBER_FIELDS "telephoneNumber, mobile, DoD SIP URI"
Note:
Avaya J129 IP Phone does not support this parameter.
DIRSEARCH_FIELDS
cn,sn,telephoneNumber
Specifies LDAP search attributes. The exact number and names of the search attributes depend on the LDAP server configuration and can vary from one LDAP directory to another.
When configuring this parameter, you must use attribute names that coincide with the selected LDAP server attribute names.
For example, SET DIRSEARCH_FIELDS "givenName,mail,middle initials, telephoneNumber, sn,mobile, department, Rank, office,DoD SIP URI"
Note:
Avaya J129 IP Phone does not support this parameter.
DIRSECURE
1
Specifies whether to use TLS or TCP for LDAP. To authenticate the server, startTLS is used. ldaps:// is not supported. You need to configure startTLS for the secure LDAP connection.
The options are the following:
For example, SET DIRSECURE 1
Note:
Avaya J129 IP Phone does not support this parameter.
DIRSHOW_FIELDS
cn,sn,telephoneNumber,Mail
Specifies LDAP detail show fields. The phone returns the attributes, specified in this parameter, for each match found for a search query.
You can use this parameter to map the specified LDAP keywords. This mapping defines the way the phone displays show fields.
For example, SET DIRSHOW_FIELDS “dn=Distinguished Name, rank, gn=First Name, office=Office, middle initials=Middle Initial, Display Name=Full Name, sn=Last Name, job title=Job, cn=Common Name, o=Office, c=Country, department=Department, street=Street, mail=Mail Box, l, telephoneNumber=PhoneNumber, st, mobile=Mobile , postalCode=Postal code, facsimileTelephoneNumber=Fax, DoD SIP URI=Number”
In this example, the format is as follows:
SET DIRSHOW_FIELDS "[LDAP Attributes]=[Field Names], [LDAP Attribute 1]=[Field Name1]"
Note:
Avaya J129 IP Phone does not support this parameter.
DIRSRVR
Null
Specifies the IP address or a fully qualified domain name (FQDN) of the LDAP directory server.
The valid value is an IPv6, IPv4 address in the dotted decimal format or a FQDN.
For example, SET DIRSRVR 192.168.161.54 or SET DIRSRVR domain.com
Note:
Avaya J129 IP Phone does not support this parameter.
DIRSRVRPRT
389
Specifies the port number for the LDAP directory server.
Valid values are positive integers from 1 to 65535.
For example, SET DIRSFVFRT 389
Note:
Avaya J129 IP Phone does not support this parameter.
DIRTOPDN
Null
Specifies the LDAP search base.
For example, SET DIRTOPDN "dc=global, dc=avaya, dc=com"
Note:
Avaya J129 IP Phone does not support this parameter.
Specifies mapping of LDAP fields to local contact fields. If there is no rule for at least one contact number, the entire contact mapping is disabled.
Local contact field names can be assigned from the following: "firstName"
"nickname"
"URI"
"extension"
"email"
"department"
"zipCode"
"country"
for number types:
"work"
"home"
"mobile"
"other"
Note:
Avaya J129 IP Phone does not support this parameter.
DIR_LDAP_DESCRIPTION
LDAP Directory
Specifies a custom label to be used for the LDAP directory in the Contacts application.
Valid value is a text string.
DISCOVER_AVAYA_ENVIRONMENT
Specifies dynamic feature set discovery
The options are the following:
Note:
Set the parameter to
DIR_LDAP_DESCRIPTION
“LDAP Directory
Specifies a custom label to be used for the LDAP directory in the Contacts application.
Valid value is a text string.
Note:
Avaya J129 IP Phone does not support this parameter.
DISPLAY_MODE
Specifies the display mode that you set for the phone.
Valid values:
DISPLAY_NAME
Null
Specifies the custom Caller ID displayed on the call appearance for the host and the remote phone.
Valid value is a text string of non-ASCI symbols, up to 255 characters long. For example:
SET DISPLAY_NAME "John Smith"
The following symbols are not valid values: ";<>/&
Note:
IP Office does not support this parameter.
DISPLAY_SSL_VERSION
Specifies whether OpenSSL and OpenSSH versions are displayed in the Administration menu.
The options are the following:
DND_SAC_LINK
Specifies whether to activate the SendAllCall when user enables DoNotDisturb.
The value of this parameter is used if the ALLOW_DND_SAC_LINK_CHANGE is set to 0
The options are the following:
Note:
Avaya J129 IP Phone does not support this feature.
DNSSRVR
Specifies a character string that will be appended to parameter values that are specified as DNS names, before the name is resolved.
The value can contain 0 to 255 characters. The default value is null.
This parameter can be set through:
DHCP
The settings file.
Setting this parameter through the settings file overwrites any values set through DHCP.
DOMAIN
Specifies a character string that will be appended to parameter values that are specified as DNS names, before the name is resolved.
The value can contain 0 to 255 characters. The default value is null.
This parameter can be set through:
DHCP
The settings file.
Setting this parameter through the settings file overwrites any values set through DHCP.
DOT1X
Specifies the 802.1X pass-through operating mode.
Pass-through is the forwarding of EAPOL frames between the phone's ethernet line interface and its secondary (PC) ethernet interface
The options are the following:
DOT1XEAPS
Specifies the authentication method to be used by 802.1X.
Valid values are:
If you select MD5, PEAP, or TTLS, configure the parameters FORCE_DOT1XID and FORCE_DOT1XPSWD. Otherwise, the phone prompts you to provide the inputs for DOT1XID and DOT1XPSWD on the administration menu.
If you select PEAP, the phone only supports the PEAP Phase 2 authentication method MSCHAPv2.
If you select TLS, configure the parameter FORCE_DOT1XID_TLS. Otherwise, the phone prompts you to provide the input for DOT1XID_TLS on the administration menu.
DOT1XEAPTLSONLYWITHCERT
Specifies whether the phone activates 802.1x EAP-TLS when there is an identity certificate installed.
DOT1XSTAT
Specifies the 802.1X supplicant operating mode.
The options are the following:
DSCPAUD
Specifies the layer 3 Differentiated Services (DiffServ) Code Point for audio frames generated by the phone.
Valid values are from 0 to 63.
This parameter can also be set through the LLDP, which overwrites any value in the settings file.
DSCPAUD_FL
Specifies the DSCP value for flash precedence or priority level voice call.
Valid values are from 0 to 63.
DSCPAUD_FO
Specifies the DSCP value for flash Override precedence or priority level voice call.
Valid values are from 0 to 63.
Note:
Only Avaya J129 IP Phone supports this feature.
DSCPAUD_IM
Specifies the DSCP value for immediate precedence or priority level voice call.
Valid values are from 0 to 63.
Note:
Only Avaya J129 IP Phone supports this feature.
DSCPAUD_PR
Specifies the DSCP value for priority precedence or priority level voice call.
Valid values are from 0 to 63.
Note:
Only Avaya J129 IP Phone supports this feature.
DSCPMGMT
Specifies the DSCP value for OA&M management packet.
Valid values are from 0 to 63.
Note:
Only Avaya J129 IP Phone supports this feature.
DSCPSIG
Specifies the layer 3 Differentiated Services (DiffServ) Code Point for signaling frames generated by the phone.
Valid values are 0 through 63.
This parameter can also be set through LLDP, which overwrites any value set in the settings file.
DSTOFFSET
Specifies the time offset in hours of daylight savings time from local standard time.
From the software version 4.1.0 and later, the phone support values: -1, 0, 1, or 2. The default value is 1.
For the software version earlier than 4.1.0, the phone support values: 0, 1, or 2. The default value is 1.
DSTSTART
Specifies when to apply the offset for daylight savings time.
The date and time for applying the offset can be set in the following formats:
odddmmmht: for example, 2SunMar2L which corresponds to the second Sunday in March at 2 AM local time;
Dmmmht: for example, 10Mar5L which corresponds to March 10 at 5 AM local time.
DSTSTOP
Specifies when to stop applying the offset for daylight savings time.
You can set the date and time when the offset is stopped in the following formats:
odddmmmht: for example, 1SunNov2L which corresponds to the first Sunday in November at 2 AM local time;
Dmmmht: for example, 7Nov5L which corresponds to November 7 at 5 AM local time.
DTMF_PAYLOAD_TYPE
Specifies the RTP payload type to be used for RFC 2833 signaling.
Valid values are 96 through 127.
DUAL_IPPREF
DUAL_IPPREF controls the following:
The selection of SSON either from DHCPv4 or DHCPv6 server, when phone is in dual mode.
Whether an IPv4 or IPv6 addresses returned by DNS would be tried first during dualmode operation.
DHCP clients use DUAL_IPPREF to decide which SSON configuration attributes to apply for DHCPv4 / DHCPv6 interworking in dual mode.
The options are the following:
E
EASG_SITE_AUTH_FACTOR
Specifies Site Authentication Factor code associated with the EASG site certificate being installed. Valid values are 10 to 20 character alphanumeric string.
EASG_SITE_CERTS
Specifies list of EASG site certificates which are used by technicians when they don't have access to the Avaya network to generate EASG responses for SSH login. The URLs must be separated by commas without any intervening spaces. Valid values are 0 to 255 ASCII characters.
EEESTAT
Specifies Energy-Efficient Ethernet (802.3az) is enabled on PHY1 and PHY2.
This parameter is supported by only Avaya J129 IP Phone.
The options are the following:
0: EEE is disabled on both PHY1 and PHY2.
1; EEE is enabled on both PHY1 and PHY2.
EDIT_DIALING_FROM_CALL_LOG
Specifies whether edit dialing is enabled for calls initiated from the Call Logs.
The options are the following:
Note:
Avaya J129 IP Phone does not support Edit Dialing From Call Log feature.
ELD_SYSNUM
Controls whether Enhanced Local Dialing algorithm will be applied for System Numbers-Busy Indicators and Auto Dials.
The options are the following:
Note:
Avaya J139 IP Phone does not support Busy Indicator feature.
ENABLE_3PCC_ENVIRONMENT
1
Specifies that the phone is working in the Third-party call control setup environment.
The options are the following:
0: Disabled
1: Enabled
Set the parameter to
ENABLE_MD5
Specifies whether the J100 phone supports the MD5 algorithm for SIP Digest Authentication.
The options are the following:
The phone supports additional digest authentication methods as defined by RFC 8760, including the following:
SHA-256
SHA-512/256
Before disabling this parameter, ensure that your server is configured to request at least 1 of the above methods.
Note:
The phone selects the first supported digest authentication method from the list of methods provided by the server.
ENABLE_MD5 can be configured through:
The web interface
46xxsettings.txt file
AADS
ENABLE_NIGHT_MODE
Specifies whether the Night mode soft key is available on the phone UI.
The options are the following:
0: Do not allow
1: Allow
Note:
Only Avaya J179 IP Phone supports Night mode feature.
ENABLE_TIMEZONE
Specifies if the phone uses the TIMEZONE parameter to determine the phone local time.
The values are:
From the software version 4.1.0 and later, Avaya J139 IP Phone, Avaya J159 IP Phone, Avaya J169/J179 IP Phone, and Avaya J189 IP Phone supports the ENABLE_TIMEZONE parameter.
ENABLE_AVAYA_ENVIRONMENT
Specifies whether the phone is configured to be used in an Avaya (SES) or a third-party proxy environment.
The options are the following:
ENABLE_BLIND_TRANSFER
Specifies that whether the blind transfer is enabled or not.
The options are the following:
Avaya J129 IP Phone does not support this feature.
ENABLE_CALL_LOG
Specifies if call logging and associated menus are available on the phone.
The options are the following:
ENABLE_CONTACTS
Specifies if the contacts application and associated menus are available on the phone.
The options are the following:
Note:
The parameter is set to
.
ENABLE_DIGIT_MAPPING
Specifies if the phone uses DIGIT_MAPPING parameter for dial plan configuration, if the parameter is disabled DIALPLAN and ELD parameters are used.
The options are the following:
ENABLE_EARLY_MEDIA
Specifies if the phone sets up a voice channel to the called party before the call is answered.
The options are the following:
Setting this parameter to
ENABLE_EXCHANGE_REMINDER
Specifies whether or not exchange reminders will be displayed.
The options are the following:
Note:
Avaya J129 IP Phone does not support this feature.
ENABLE_FEATURE_INVOCATION_TARGET_SELECTION
This parameter is used to enable or disable the feature target selection.
The options are:
ENABLE_G711A
Specifies if the G.711 a-law codec is enabled.
The options are the following:
ENABLE_G711U
Specifies if the G.711 mu-law codec is enabled.
The options are the following:
ENABLE_G722
Specifies if the G.722 codec is enabled.
The options are the following:
ENABLE_G726
Specifies if the G.726 codec is enabled.
The options are the following:
ENABLE_G729
Specifies if the G.729A codec is enabled.
The options are the following:
ENABLE_GDPR_MODE
Specifies if Global data Protection Regulations (GDPR) are applied on the phone. If on, it generally ensures that the phones stores unencrypted private data for no longer than 24 hours.
The options are the following:
Avaya J129 IP Phone does not support this parameter.
ENABLE_HSTS
Specifies whether the phone sends the HTTP Strict Transport Security (HSTS) header in the HTTP response. If you enable this value, the phone sends the header only when the web UI is accessed over the HTTPS.
The options are the following:
ENABLE_IPOFFICE
Specifies whether the J100 phone can operate in 2 different modes with IP Office. The first mode allows native support of the J100 phone with IP Office with a limited feature set. The second mode allows support of the J100 phone with additional feature support driven by the IP Office proxy.
The options are the following:
Avaya J129 IP Phone supports value 0 and 1.
Avaya J139 IP Phone, Avaya J159 IP Phone and Avaya J169/J179 IP Phone support value 0 and 2.
ENABLE_ENHANCED_CALL_INFO
Specifies if the phone displays the additional call information. You can enable the LDAP lookup for the additional information.
The valid values are:
0: Disabled (Default)
1: LDAP lookup for incoming caller ID
2: LDAP lookup for outgoing caller ID
3: LDAP lookup for both incoming & outgoing caller ID
The phone can display the additional information after you configure the LDAP server with the required settings and configure a valid value for ENHANCED_CALL_INFO_FIELDS.
Avaya J129 IP Phone does not support this parameter.
ENHANCED_CALL_INFO_FIELDS
Specifies the additional information that the phone displays for an incoming call or outgoing call or for both. The value is a comma separated string. The format is:[LDAP ATTRIBUTE 1]=[LABEL 1],[LDAP ATTRIBUTE 2]=[LABEL 2]
Enable ENABLE_ENHANCED_CALL_INFO to specify ENHANCED_CALL_INFO_FIELDS parameter.
The default value is empty.
Avaya J129 IP Phone does not support this parameter.
ENHANCED_CALL_INFO_DISPLAYNAME
Specifies the name of the LDAP attribute, for example, dn. The phone displays this name as the name of for an incoming call or outgoing call or for both.
Enable ENABLE_ENHANCED_CALL_INFO to specify ENHANCED_CALL_INFO_DISPLAYNAME parameter.
The default value is empty.
Avaya J129 IP Phone does not support this parameter.
ENABLE_MLPP
Specifies that whether the Multiple Level Precedence and Preemption (MLPP) is enabled or not.
The options are the following:
ENABLE_MODIFY_CONTACTS
Specifies if the list of contacts and the function of the contacts application can be modified on the phone.
The options are the following:
ENABLE_MULTIPLE_CONTACT_WARNING
Specifies if a warning message must be displayed if there are multiple phones registered on a user's behalf.
The options are the following:
Note:
Multiple registered phones can lead to service disruption.
ENABLE_OOD_MSG_TLS_ONLY
Specifies if an Out-Of-Dialog (OOD) REFER must be received over TLS transport to be accepted.
The options are the following:
Note:
A value of
ENABLE_OOD_RESET_NOTIFY
Specifies whether the phone supports out of dialog (OOD) SIP NOTIFY message with Event:resync or Event:check-sync only. The events are used to remotely restart the phone once all calls end.
The options are the following:
ENABLE_OPUS
Specifies if the OPUS codec capability of the phone is enabled or disabled.
The options are the following:
Note:
Supported only in J189 phone.
ENABLE_PHONE_LOCK
Specifies whether the phone displays a soft key and a feature button for the user to lock the phone manually.
The options are the following:
Note:
ENABLE_PHONE_LOCK parameter controls the Phone Lock configuration. When you set the parameter to
ENABLE_PPM_SOURCED_SIPPROXYSRVR
The parameter is only available in an Avaya Aura® environment.
Enables PPM as a source of SIP proxy server information.
The options are the following:
ENABLE_PRECEDENCE_SOFTKEY
Specifies that whether the precedence soft key is enabled or not on the idle line appearances on Phone Screen.
The options are the following:
Note:
Only Avaya J129 IP Phone supports this feature.
ENABLE_PRESENCE
Specifies if presence will be supported.
The options are the following:
Note:
This parameter is set to
ENABLE_PUBLIC_CA_CERTS
1
Specifies whether the out-of-the-box phone can validate server certificates against a list of well-known public Certificate Authority certificates
The options are the following:
ENABLE_RECORDING
Specifies if audio debug recording is enabled for users.
The options are the following:
ENABLE_RANDOM_RTP_PORT
Specifies whether the random RTP port is enabled.
The options are the following:
ENABLE_RFC5922
Specifies to enable or disable the RFC5922 certificate validation.
The options are the following:
ENABLE_REDIAL
Specifies if Redial softkey is available.
The options are the following:
ENABLE_REDIAL_LIST
Specifies if the phone redials last number or displays list of recently dialed numbers.
The options are the following:
Note:
Avaya J129 IP Phone do not support this feature.
ENABLE_REMOVE_PSTN_ACCESS_PREFIX
Enables phone to perform digit manipulation during failure scenarios. This parameter enables removal of PSTN access prefix from the outgoing number.
The options are the following:
ENABLE_SHARED_CONTROL_PROMPT
Specifies whether or not the shared control confirmation dialogue is displayed. When enabled, a shared control connection must be accepted by the user before it can be used.
The options are:
Note:
This field is only supported in the Aura environment.
ENABLE_SHOW_EMERG_SK
Specifies whether an Emerg softkey, with or without a confirmation screen, is displayed when the phone is registered. All emergency numbers are always supported.
The options are the following:
Note:
The parameter is set to
ENABLE_SHOW_EMERG_SK_UNREG
Specifies whether an Emerg softkey, with or without a confirmation screen, is displayed when the phone is not registered.
All emergency numbers will always be supported.
The options are the following:
Note:
The parameter is set to
ENABLE_SIP_USER_ID
0
Specifies the display of the user ID input field on the Login Screen.
The options are the following:
0: Disabled
1: Enabled
ENABLE_SIPURI_HOST_VALIDATION
Specifies allowing to accept SIP URI with unrecognized host part in INVITE message.
The options are the following:
0: Does not allow
1: Allows
ENABLE_SPEAKER_EMERG
Specifies if the phone automatically switches to the speaker transducer when the user activates an emergency call when pressing the Emerg soft key or dialing the emergency number.
The options are the following:
0: The transducer does not automatically switches to the speaker.
1: The transducer automatically switches to the speaker.
ENABLE_STRICT_USER_VALIDATION
Specifies that the validation is done for the To header and Request-URI against AOR and Contact header during phone registration.
The options are the following:
0: No validation.
1: Validates the phone registration.
ENABLE_USBHEADSET
Specifies whether the USB headset feature is enabled or not.
The options are the following:
ENABLE_USBKEYBOARD
It enables or disables the USB keyboard support.
This parameter ignores the other values if the value is set to 1 (enabled by default).
The options are the following:
Note:
This feature is available only on the Avaya J159 IP Phone and Avaya J189 IP Phone.
ENABLE_USBSTICK
It enables or disables the USB stick support.
This parameter ignores the other values if the value is set to 1 (enabled by default).
The options are the following:
Note:
This feature is available only on the Avaya J159 IP Phone and Avaya J189 IP Phone.
ENABLE_WEBSERVER
1
Enables or disables the web server to configure the phones in a web browser.
The options are the following:
0: Disable
1: Enable
ENABLE_WMLPUSH_ALEDISPLAY_NAMERTING
Specifies the behavior of WML browser during incoming call.
The options are the following:
Note:
This feature is available only on the Avaya J159 IP Phone, Avaya J169/J179 IP Phone, and Avaya J189 IP Phone
ENCRYPT_SRTCP
Specifies whether RTCP packets are encrypted or not. SRTCP is only used if SRTP is enabled using MEDIAENCRYTIONRTCP. ENCRYPT_SRTCP parameter controls RTCP encryption for RTCP packets exchanged between peers. RTCP packets sent to Voice Monitoring Tools are always sent unencrypted.
The options are the following:
ENFORCE_SIPS_URI
Specifies if a SIPS URI must be used for SRTP.
The options are the following:
ENABLE_SUMMARIZED_CALL_LOG
Specifies whether the phone displays the summarized calls on the Recents application.
The options are:
ENHDIALSTAT
Specifies if the algorithm defined by the parameter is used during certain dialing behaviors.
The options are the following:
Note:
The parameter is set to
ENTRYNAME
Specifies if the calling party name, or the VDN or the skill name must be used in History entries.
The options are the following:
Note:
Avaya J129 IP Phone does not support this parameter.
EVENT_NOTIFY_AVAYA_MAX_USERS
Specifies the maximum number of users to be included in an event notification message from CM/AST-II or Avaya Aura® Conferencing 6.0 or later.
Valid values are 0 through 1000.
This parameter is used only for development and debugging purposes.
EXCHANGE_AUTH_USERNAME_FORMAT
Specifies the necessary format of the username for http authentication.
The options are the following:
Note:
Only Avaya J129 IP Phone supports this feature.
EXCHANGE_AUTH_METHOD_DEFAULT
Specifies the Exchange authentication method configured by administrator.
When you configure Basic (Forced) or OAuth (Forced) method, it is the active authentication method. The phone user is not allowed to change the authentication method from phone user interface.
When you configure non-forced method, phone user can change the authentication method from the phone user interface and configure the active authentication method.
The options are the following:
0: Basic authentication (Default)
1: OAuth authentication
2: Basic authentication- forced
3: OAuth authentication- forced
Note:
Avaya J129 IP Phone does not support this feature.
EXCHANGE_EMAIL_DOMAIN
Specifies the Exchange email domain.
The value can contain 0 to 255 characters.
Note:
Only Avaya J129 IP Phone supports this feature.
EXCHANGE_NOTIFY_SUBSCRIPTION_PERIOD
Specifies the number of seconds between re-syncs with the Exchange server.
Valid values are 0 through 3600.
Note:
Avaya J159 IP Phone and Avaya J169/J179 IP Phone support this parameter.
EXCHANGE_REMINDER_TIME
Specifies the number of minutes before an appointment at which a reminder will be displayed.
Valid values are 0 through 60.
Note:
Avaya J159 IP Phone and Avaya J169/J179 IP Phone support this parameter.
EXCHANGE_REMINDER_TONE
Specifies whether or not a tone will be generated the first time an Exchange reminder is displayed.
The options are the following:
Note:
Avaya J159 IP Phone and Avaya J169/J179 IP Phone support this parameter.
EXCHANGE_SERVER_LIST
Specifies a list of one or more Exchange server IP addresses.
Addresses can be in dotted-decimal or DNS name format, separated by commas without any intervening spaces.
The list can contain up to 255 characters.
EXCHANGE_SERVER_MODE
Specifies the protocol to be used to contact Exchange servers.
The options are the following:
Note:
Avaya J169/J179 IP Phone supports this parameter.
EXCHANGE_SERVER_SECURE_MODE
Specifies if HTTPS should be used to contact Exchange servers.
The options are the following:
Note:
Avaya J129 IP Phone does not support this feature.
EXCHANGE_SNOOZE_TIME
Specifies the number of minutes in which a reminder must be displayed again after it is temporarily dismissed.
Valid values are 0 through 60.
Note:
Avaya J129 IP Phone does not support this feature.
EXCHANGE_USER_ACCOUNT_DEFAULT
Specifies the Exchange user account configured by administrator. This parameter is only applicable when authentication method is OAuth.
If phone user hasn't configured any user name on the phone user interface then value configured in this parameter would be used.
The valid value is a string of up to 255 characters. The default value is empty.
Note:
Avaya J129 IP Phone does not support this feature.
EXCHANGE_USER_DOMAIN
Specifies the domain for the URL used to obtain Exchange contacts and calendar data. The parameter is used as a part of the user authentication.
The value can contain 0 to 255 characters.
You can change the value by using the Admin menu on the phone.
F
FAILED_SESSION_REMOVAL_TIMER
Specifies the number of seconds the phone displays a session line appearance and generates re-order tone after an invalid extension is dialed and user does not press the End Call soft key.
Valid values are 5 through 999.
FAST_RESPONSE_TIMEOUT
Specifies the number of seconds the phone will wait before terminating an INVITE transaction if no response is received.
Valid values are 0 through 32.
Value of
FILTER_LDAP_CONTACTS_WITHOUT_NUMBERS
Specifies whether the phone's filter contacts without numbers is enabled.
The options are the following:
FIPS_ENABLED
Specifies whether only FIPS-approved cryptographic algorithms will be supported.
The options are the following:
FORBIDDEN_SESSION_REMOVAL_TIMER
Specifies the duration of an off-hook session before a call automatically ends. This is valid when there are no call appearances available on the called or remote party.
Valid values are from 5 to 20 seconds.
FORCE_DOT1XID
Specifies the username ID the phone provides to the 802.1x authentication server.
This parameter is valid when you configure DOT1XEAPS as MD5 or PEAP.
Valid value is a string ranging from 1-31 characters. A valid value overwrites any other configuration made through the Administration menu or the web interface.
The default value is
If the value contains
are replaced by the same values as
but in upper case.
FORCE_DOT1XID_TLS
Specifies the Ethernet 802.1x identity.
This parameter is valid when you configure DOT1XEAPS as TLS.
Valid value is a string ranging from 1-31 characters. A valid value overwrites any other configuration made through the Administration menu or the web interface.
The default value is
If the value contains
are replaced by the same values as
but in upper case.
Note:
Avaya J129 IP Phone does not support this feature.
FORCE_DOT1XPSWD
Null
Specifies the password the phone provides to the 802.1x authentication server.
This parameter is valid when you configure DOT1XEAPS as MD5 or PEAP.
Valid value is a string ranging from 1-31 characters. A valid value overwrites any other configuration made through the Administration menu or the web interface.
The default value is Null.
If the value contains
If the value contains
are replaced by the same values as
but in upper case.
FORCE_HTTP_AUTH_USERNAME
Null
Specifies the username for HTTP provisioning server authentication.
The valid value is a string of up to 255 ASCII characters without any intervening spaces.
Double quotes (“”) must not be used in a username string, when you configure this parameter through the 46xxsettings.txt file.
The following symbols are not supported when provisioning the credentials with the DHCP Option 242:
Double quote mark (“”)
Apostrophe (’)
Comma (,)
Equal sign (=)
FORCE_HTTP_AUTH_PASSWORD
Null
Specifies the password for HTTP provisioning server authentication.
The valid value is a string of up to 255 ASCII characters without any intervening spaces.
Double quotes (“”) must not be used in password string, when you configure this parameter through the 46xxsettings.txt file.
The following symbols are not supported when provisioning the credentials with the DHCP Option 242:
Double quote mark (“”)
Apostrophe (’)
Comma (,)
Equal sign (=)
FORCE_SIP_EXTENSION
Replaces User ID entered by the user during login.
FORCE_SIP_PASSWORD
Replaces password entered by the user during login.
FORCE_SIP_USERNAME
Replaces the user field entered by the user during login.
FORCE_WEB_ADMIN_PASSWORD
Specifies the password to access the phone through Web as Administrator.
Valid values are 8 to 31 alphanumeric characters.
FQDN_IP_MAP
Specifies a comma separated list of name or value pairs where the name is an FQDN and the value is an IP address. The IP address may be IPv6 or IPv4 but the value can only contain one IP address. String length is up to 255 characters without any intervening spaces inside the string. The purpose of this parameter is to support cases where the server certificate Subject Common Name or Subject Alternative Names includes FQDN, instead of IP address, and the SIP-TLS or HTTP-TLS connection is using an IP address directly. This parameter is supported with phone service running over TLS, however, the main use case is for Avaya Aura SM/PPM services. This parameter does not provide an alternative to a DNS lookup or reverse DNS lookup. If the phone is attempting to connect to an FQDN address then a DNSSRVR address must be defined to enable the phone to perform a DNS lookup on the FQDN address.
G
G726_PAYLOAD_TYPE
Specifies the RTP payload type to be used for the G.726 codec.
Valid values are 96 through 127.
GMTOFFSET
Specifies the time offset from GMT in hours and minutes.
The format begins with an optional + or - (+ is assumed if omitted), followed by 0 through 12 (hours), followed by a colon (:), followed by 00 through 59 (minutes).
GROUP
Specifies specifically-designated groups of phones by using IF statements based on the GROUP parameter.
The value of GROUP can be set manually in a phone by using the GROUP local craft procedure.
The value of GROUP can be set manually in a phone by using the GROUP local admin procedure.
The default value of GROUP in each phone is 0, and the maximum value is 999.
GUESTDURATION
Specifies the duration (in hours) before a Guest Login or a visiting user login is automatically logged off if the phone is idle.
Valid values are integers from 1 to 12.
Note:
This parameter is not supported by Avaya J129 IP Phone.
GUESTLOGINSTAT
Specifies whether the Guest Login feature is available to users.
The options are:
Note:
This parameter is not supported by Avaya J129 IP Phone.
GUESTWARNING
Specifies the number of minutes, before time specified by GUESTDURATION, that a warning of the automatic log off is initially presented to the Guest or Visiting User.
Valid values are integers from 1 to 15.
Note:
This parameter is not supported by Avaya J129 IP Phone.
H
HANDSET_PROFILE_DEFAULT
Specifies the number of the default handset audio profile.
Valid values are 1 through 20.
HANDSET_PROFILE_NAMES
Null
Specifies an ordered list of names to be displayed for handset audio profile selection. The list can contain 0 to 255 UTF-8 characters.
Names are separated by commas without any intervening spaces. Two commas in succession indicate a null name, which means that the default name should be displayed for the corresponding profile. Names might contain spaces, but if any do, the entire list must be quoted. There is no way to prevent a profile from being displayed.
HEADSET_PROFILE_DEFAULT
Specifies the number of the default headset audio profile.
Valid values are 1 through 20.
Note:
Avaya J129 IP Phone does not support this feature.
HEADSET_PROFILE_NAMES
Specifies an ordered list of names to be displayed for headset audio profile selection.
The list can contain 0 to 255 UTF-8 characters.
Names are separated by commas without any intervening spaces. Two commas in succession indicate a null name, which means that the default name is displayed for the corresponding profile. Names can contain spaces, but if any do, the entire list must be quoted. There is no way to prevent a profile from being displayed.
Note:
Avaya J129 IP Phone does not support this feature.
HEADSYS
Specifies whether the phone goes on-hook if the headset is active when the disconnect message is received.
The options are the following:
HELD_URL
Null
Specifies the Location Information Server (LIS) URL that the phone sends a HELD request to determine the physical location information in the PIDF-Lo format.
The URL can be HTTP or HTTPS.
The URL must be a string data type between 0 and 255 ASCII characters without intervening spaces.
HELD_URL can be configured through:
The web interface
46xxsettings.txt file
DHCP SSON 242
AADS
HELD_RETRY
300
Specifies the interval, in seconds, that the phone waits before retrying a HELD request after encountering specific errors.
Valid values are 60 to 3600 seconds.
HELD_RETRY can be configured through:
The web interface
46xxsettings.txt file
DHCP SSON 242
AADS
HELD_PERIODIC_TIMER
60
Specifies the frequency, in minutes, at which the phone will send a request to the LIS server to check if its location information has changed.
This parameter is only used when LLDP_ENABLED is enabled and HELD_URL is defined.
Note:
This field is only supported in the Aura environment.
Valid values are 30 to 1440 minutes.
HELD_PERIODIC_TIMER can be configured through:
The web interface
46xxsettings.txt file
DHCP SSON 242
AADS
HOMEIDLETIME
Specifies the number of minutes of idle time after which the Home screen is displayed.
Valid values are 0 through 30.
A value of
HOTLINE
Specifies a hotline number that the phone dials automatically when the phone goes off-hook.
Valid values can contain up to 30 dialable characters ranging from 0 to 9, asterisk (*), and pound (#).
HTTPEXCEPTIONDOMAINS
Specifies a list of one or more domains, separated by commas without any intervening spaces, for which HTTPPROXY is not used.
The value can contain 0 to 255 characters. The default value is null.
HTTPDIR
Specifies the path to the configurations and data files in HTTP and HTTPS GET operations during device bootup. This path is relative to the root of the HTTPS file server, to the directory in which the device configuration and data files are stored. If $MACADDR and/or $MODEL4 and/or $SERIALNO macro is present in the configured path then such macro is replaced with its actual value.
The value can contain 0 to 127 ASCII characters without space.
HTTPPORT
Sets the TCP port used for HTTP file downloads from non-Avaya servers.
Values range from 0 to 65535.
HTTPPROXY
Specifies the address of the HTTP proxy server used by SIP phones to access an SCEP server that is not on the enterprise network.
Valid value can contain zero or one IP address in dotted decimal or DNS name format, optionally followed by a colon and a TCP port number.
The value can contain 0 to 255 characters.
HTTPSRVR
Specifies zero or more HTTP server IP addresses to download configuration script files. The addresses must be separated by commas without any intervening spaces. The format of specifying IP addresses are:
Dotted decimal
Colon-hex
DNS name
The parameter can be set by using LLDP.
Valid values contains 0 to 255 ASCII characters.
I
ICMPDU
Specifies if ICMP Destination Unreachable messages are generated.
The options are the following:
ICMPRED
Specifies if received ICMP Redirect messages are processed.
The options are the following:
IGNORE_CONTACT_HEADER_DISPLAY_NAME
Specifies if the phone is allowed to use a display name from the Contact header when there is no display name in the PAI or From headers.
The options are the following:
IGNORE_LINE_KEY
Specifies if the action of Softkey1 on the phone screen is performed or ignored when the user’s call appearance is on an active call and the user presses the line key associated with the active call.
The options are the following:
Note:
Avaya J129 IP Phone does not support this feature.
INCOMING_CALL_POPUP_DEFAULT
Specifies the mode for incoming call popup notification. The settings apply to incoming calls on primary call appearances, bridged call appearances, and shared call appearances.
If the forced value is not set, you can allow the user to change this setting in the User menu.
The options are the following:
The Incoming call popup is disabled. The end user can change this setting in the user menu.
The incoming call popup is enabled. The end user can change this setting in the user menu.
The administrator can enforce this configuration.. The end user cannot change this setting in the user menu.
The administrator can enforce this configuration.. The end user cannot change this setting in the user menu.
INGRESS_DTMF_VOL_LEVEL
Specifies the power level of tone, expressed in dBm0.
Values can range from -20dBm to -7dBm.
INTER_DIGIT_TIMEOUT
Specifies the number of seconds that the phone waits after a digit is dialed before sending a SIP INVITE.
Valid values are 1 through 10.
IP_TTL
Specifies the time to live (TTL) value for IP packets that the phone sends. The parameter is valid for IPv4 and IPv6 networks.
Valid values are 1 through 255.
IPV6DADXMITS
Specifies whether Duplicate Address Detection is performed on tentative addresses, as specified in RFC 4862.
The options are the following:
IPV6STAT
Specifies whether IPv6 will be supported or not.
The options are the following:
K
KEYUSAGE_REQUIRED
0
Specifies whether the server certificate is checked for the presence of a Key Usage extension. When enabled, a server certificate is rejected if the Key Usage extension is missing.
The options are the following:
0: Key Usage checking is disabled
1: Key Usage checking is enabled
KEEP_CURRENT_CA
1
Specifies whether the current active line on the phone screen still highlights after the call on the selected line ends.
The options are the following:
L
L2Q
Specifies if layer 2 frames generated by the telephone have IEEE 802.1Q VLAN tags.
The options are the following:
Note:
This parameter can also be set through:
Local admin procedure
A name equal to value pair in DHCPACK message
SET command in a settings file
DHCP option 43
LLDP
L2QAUD
Specifies the layer 2 priority value for audio frames generated by the telephone.
Valid values are 0 through 7.
Note:
This parameter can also be set through:
SET command in a settings file
LLDP. Setting this parameter though LLDP overwrites any values in the settings file.
L2QSIG
Specifies the layer 2 priority value for signaling frames generated by the phone.
Valid values are 0 through 7.
Note:
This parameter can also be set through:
SET command in a settings file
LLDP
AADS
Setting this parameter through LLDP or AADS overwrites values in the settings file.
L2QVID
Specifies the layer 2 priority value for video frames generated by the phone.
Valid values are 0 through 7.
L2QVLAN
Specifies the voice VLAN ID to be used by IP phones.
Valid values are 0 through 4094.
Note:
This parameter can also be set through:
Local admin procedure
A name equal to value pair in DHCPACK message
SET command in a settings file
DHCP option 43
LLDP
LANGUAGES
Specifies the language files that you optionally download to the phone. The language files must be in the .xml format.
Note:
From Avaya J100 Series IP Phones Release 4.1.9 and later, the firmware embeds all supported language files. The phone does not need to download the language files from the provisioning server. However, you must specify the LANGUAGES parameter to list the languages available to the user. The LANGUAGES parameter can also specify a custom language file name. The phone then downloads custom language from the provisioning server.
The file names must be comma-separated without intervening spaces. You can define absolute URLs, absolute paths, relative paths, macros, or file names for the language files.
An absolute URL. For example, http://username:password@provisioning.example.com:8088/path/Mlf_J159_CanadianFrench.xml
An absolute path that ignores HTTPDIR or TLSDIR. For example,/path/Mlf_J159_CanadianFrench.xml
A relative path that is appended to HTTPDIR or TLSDIR. For example,path/Mlf_J159_CanadianFrench.xml
Macros. The actual values replace the macros. For example,
"$SERIALNO"The phone serial number. The value must be uppercase.
"$MACADDR"The phone MAC address. The value must be lowercase without intervening colons.
"$MODEL4"The four-character phone model number. The letters in the values must be uppercase.
File name.
For example, SET LANGUAGE "Mlf_J159_CanadianFrench.xml,Mlf_J159_Spanish.xml"
LLDP_ENABLED
Specifies whether LLDP is enabled.
The options are the following:
LOCAL_DIAL_AREA_CODE
Specifies if user must dial area code for calls within same area code regions.
The options are the following:
Note:
This parameter is supported when the phone is failed over.
LOCALLY_ENFORCE_PRIVACY_HEADER
The parameter is only available in an Avaya Aura® environment.
Specifies whether the phone displays Restricted instead of CallerId information when a Privacy header is received in a SIP INVITE message for an incoming call.
The options are the following:
LOCK_MODE
Specifies the source of the PIN that unlocks the phone. When Single sign-on is (SSO) is active, the value is 1.
The options are the following:
When the value is 1, the phone requires a re-login for the user to set a PIN. When you change the value, the phone requires a re-login to apply the changes.
LOG_CATEGORY
Specifies a list of categories of events to be logged through syslog and locally.
This parameter must be specified to log events below the Error level.
The list can contain up to 255 characters.
Category names are separated by commas without any intervening spaces.
LOG_DIALED_DIGITS
Specifies if the call log will contain digits dialed by a user or information about a remote party when the user dials a FAC code.
The FAC code is identified by * or # entered as a first character.
The options are the following:
LOGOS
Specifies a list of tuples describing the logo or the wallpaper to be used as the phone display background.
Only full path URLs are supported.
For 9611G, 9621G and 9641G, the maximum size in pixels are: 217 x 130, 232 x 140 and 232 x 140 respectively with color depth 16 bit and JPG file type.
GIF is presented without animation.
Note:
Only Avaya J169/J179 IP Phone supports this parameter.
LOGSRVR
Specifies one address for a syslog server in dotted-decimal formatl (IPv4), colon-hex format (IPv6, if supported), or DNS name format.
The value can contain 0 to 255 characters.
LOGSRVR_SECURE
Specifies if the phone uses secure or non-secure syslog transport mode by default.
The options are the following:
Selected value is available as Default option in Administrator menu
LOGUNSEEN
Specifies whether the phone logs the incoming calls that did not notify on the phone as missed calls.
The options are:
M
MATCHTYPE
Specifies how an incoming or outgoing phone number is compared with the contacts on the phone to display the contact name.
MAX_TRUSTCERTS
Specifies the maximum number of trusted certificates files defined by this parameter that can be downloaded to the phone. MAX_TRUSTCERTS enforces the number of certificates. Valid values are from 1 to 10.
MEDIA_ADDR_MODE
Specifies the IP address of the endpoint when both IPv4 and IPv6 addresses are provided. This parameter is used for SIP signalling.
The options are the following:
MEDIA_NEG_PREFERENCE
Specifies the address family preference used by a dual mode answer in non-Avaya environment. This parameter is not applicable for single mode phones.
The options are the following:
MEDIA_PRESERVATION
1
Supports media preservation when ENABLE_IPOFFICE is set to 2.
The options are the following:
0: Phone tries to preserve a call for a duration specified by PRESERVED_CALL_DURATION settings parameter.
1: Phone does not preserve a call. As soon as the phone detects link failure to IP Office, the phone drops a call and makes re-registration attempt.
MEDIAENCRYPTION
Specifies which media encryption (SRTP) options are supported.
3 options can be specified in a comma-separated list.
The options must match those specified in Avaya Aura® Communication Manager IP-codec-set form.
The list of media encryption options is ordered from high (left) to the low (right) options. The phone publishes this list in the SDP-OFFER or chooses from SDP-OFFER list according to the list order defined in MEDIAENCRYPTION.
Avaya Aura® Communication Manager (CM) has the capability to change the list order in the SDP-OFFER (for audio only) when it passes through CM.
Do not use unauthenticated media encryption (SRTP) files.
MLPP_MAX_PREC_LEVEL
1
Specifies the maximum allowed precedence level for the user.
The options are the following:
Note:
Only Avaya J129 IP Phone supports this feature.
MLPP_NET_DOMAIN
Null
Specifies the MLPP network domain.
The options are the following:
MP_ENABLED
Specifies if the Multicast Paging feature is enabled on the phone.
This is the basic parameter for this feature. If this parameter is not set, other parameters listed below will be ignored.
The options are the following:
MP_GROUPS_TO_LISTEN
Null
Defines the list of Multicast Paging groups that the phone listens to. A maximum of 10 paging groups can be listed.
The paging groups should be separated with a comma (“,”), and should be listed in the following format:IP:port:priority:label
where
IP is the multicast IP address of an MP group;
Port is the IP port of a Multicast Paging group, the valid value is an even integer ranging from 1024 to 65534;
Priority is the priority of a group. Allowed values are 1 through 16, with smaller values indicating a higher priority;
Label is a group label which is displayed in notification messages when the incoming page from this group is played.
All the above-listed settings are required.
For example,SET MP_GROUPS_TO_LISTEN “239.0.0.0:1208:1:Security,239.1.2.3:1210:4:Sales”
MP_GROUPS_TO_SEND
Null
Defines the list of Multicast Paging groups which the phone can send pages to. Priority is not set for these groups. A maximum of 10 paging groups can be listed.
The paging groups should be separated with a comma (“,”) and should be listed in the following format:IP:port:label
IP, Port, and Label denote the same as the corresponding MP_GROUPS_TO_LISTEN values. All these settings are required.
For example,SET MP_GROUPS_TO_SEND “239.0.0.0:1208:Sales,239.1.2.3:1210:Team”
MP_CODEC
Specifies a codec which will be used to code and decode Multicast Paging transmissions.
The options are the following:
1:
2:
3:
MP_PACKET_SIZE
Specifies the size of an RTP packet in milliseconds. The valid values are 10 through 80.
The value must be valid for the selected codec and therefore must not be changed unless necessary.
MSGNUM
Specifies the phone number to be dialed automatically when the user presses the Message button. The phone number connects to the user’s voice mail system.
Note:
This parameter is applicable in Avaya Aura environment. In case of IP Office and third party environment, use the parameter PSTN_VM_NUM.
MTU_SIZE
Specifies the maximum transmission unit (MTU) size transmitted by the phone.
Valid values are 1496 or 1500. Use 1496 for older Ethernet switches.
MUTE_ON_REMOTE_OFF_HOOK
Controls the speakerphone muting for a remote-initiated (a shared control or OOD-REFER) speakerphone off-hook.
The options are the following:
The value is applied to the phone only when the phone is deployed with a Avaya Aura® Communication Manager 6.2.2 and earlier releases. If the phone is deployed with Avaya Aura® Communication Manager 6.3 or later, the setting is ignored. Instead the feature is delivered through PPM. The Turn on mute for remote off-hook attempt parameter is enabled in the station form through the Avaya Aura® Session Manager or Avaya Aura® Communication Manager (SAT) administrative interfaces.
Note:
This parameter is set to
MYCERTCAID
Specifies an identifier for the CA certificate with which the SCEP certificate request is to be signed, if the server hosts multiple Certificate Authorities.
The value can contain zero to 255 ASCII characters.
The parameter is only available in an Avaya Aura® environment.
MYCERTCN
Specifies the Common Name (CN) used in the SUBJECT of an SCEP certificate request.
The value must be a string that contains either
(which is replaced by the phone MAC address in lower case), but it can contain other characters as well, including spaces.
but in upper case.
In order to use enhanced certificate renewal in SMGR 8.1.3 and later, the value of MYCERTCN parameter must remain unchanged from the one used in existing identity certificate. Enhanced certificate renewal fails if this value is changed. If a new value is explicitly desired, then either remove the parameter SCEP_ENTITY_CLASS or remove the existing certificate by using DELETE_MY_CERT parameter and re-install a new one.
The value can contain eight (
MYCERTDN
Specifies the part the SUBJECT of an SCEP certificate request that is common for all phones.
The value must begin with a / and can include Organizational Unit, Organization, Location, State and Country.
In order to use enhanced certificate renewal in SMGR 8.1.3 and later, the value of MYCERTDN parameter must remain unchanged from the one used in existing identity certificate. Enhanced certificate renewal fails if this value is changed. If a new value is explicitly desired, then either remove the parameter SCEP_ENTITY_CLASS or remove the existing certificate by using DELETE_MY_CERT parameter and re-install a new one.
The value can contain Zero to 255 ASCII characters.
Note:
/ must used as a separator between components. Commas do not work with some servers.
MYCERTKEYLEN
Specifies the bit length of the public and private keys generated for the SCEP certificate request.
The value is a 4 ASCII numeric digits. The phone supports the values 2048 and 4096. Invalid values are ignored.
The 4096 key size delays boot-up during the initial key generation and certificate enrollment.
MYCERTRENEW
Specifies the percentage of the identity certificate's validity interval after which renewal procedure is initiated.
For example: if you set the MYCERTRENEW 90, certificate validity is 365 days, the renewal time is calculated as = (365)-(365*90%)= 36.5 days before the expiry.
Valid values are 1 through 99.
MYCERTURL
Specifies the URL of the SCEP server for obtaining an identity certificate.
The URL can be HTTP or HTTPS.
The valid values can range from Zero to 255 ASCII characters.
MYCERTWAIT
Specifies the phone's behavior if the SCEP server indicates that the certificate request is pending for manual approval.
The options are the following:
N
NO_DIGITS_TIMEOUT
Specifies the number of seconds the phone waits for a digit to be dialed after going off-hook and before generating a warning tone.
Valid values are 1 through 60.
O
OCSP_ACCEPT_UNK
Specifies whether in cases where certificate revocation status for a specific certificate cannot be determined to bypass certificate revocation operation for this certificate.
The options are the following:
OCSP_CACHE_EXPIRY
Specifies the time interval for the OCSP cache expiry in minutes. OCSP response cache expiry uses nextUpdate value in OCSP response message. If nextUpdate is not present, then OCSP_CACHE_EXPIRY parameter value is used.
Valid range is from 60 to 10080
OCSP_ENABLED
Specifies that OCSP is used to check the revocation status of the certificates.
The options are the following:
OCSP_HASH_ALGORITHM
Specifies the hashing algorithm for OCSP request.
The options are the following:
OCSP_NONCE
Specifies whether a nonce is added in OCSP requests and expected in OCSP responses.
The options are the following:
OCSP_TRUSTCERTS
Specifies a list of OCSP trusted certificates. These certificates are used as the signing authority to verify the revocation status of a digital certificate, when the OCSP responder has a different CA than the root CA of the certificate.
This parameter supports 0 to 255 ASCII characters. The file names or URLs must be comma separated values without intervening spaces. You can use a maximum of six certificates.
Important:
You must define the authentication credentials in the OCSP_TRUSTCERTS URL or use a relative path for authentication.
OCSP_URI
Specifies the URI of an OCSP responder. The URI can be an IP address or hostname. Valid values contain 0 to 255 ASCII characters, zero or one URI.
OCSP_URI_PREF
Specifies the preferred URI for use in an OCSP request when more than one source is available.
The options are the following:
1: Use the OCSP_URI and then the OCSP field of the Authority Information Access (AIA) extension of the certificate.
2: Use the OCSP field of the Authority Information Access (AIA) extension of the certificate and then the OCSP_URI.
OCSP_USE_CACHE
Specifies that the OCSP caching is in use.
The options are the following:
OFF_HOOK_ALERT_TIMER
Specifies the length of the alert timer in seconds
The options are the following:
OFF_HOOK_ALERT_EXTENSION
Null
Specifies the extension that the phone calls when off-hook alert is initiated. The phone disables the off-hook alert feature automatically if this value is empty. The extension number can be a string. The default value is null.
OPUS_PAYLOAD_TYPE
Dynamically specifies the RTP payload type to be used for OPUS codec. The parameter is used when the media request is sent to the far-end in an INVITE or 200 OK when INVITE with no Session Description Protocol (SDP) is received. The range is between 96 to 127.
OUTBOUND_SUBSCRIPTION_REQUEST_DURATION
Specifies the duration in seconds requested by the phone in SUBSCRIBE messages, which can be decreased depending on the response from the server.
Valid values are 60 through 31536000 (one year). The default value is
OVERRIDE_SOFTKEY_IDLE
0
Specifies if the phone shows default softkeys for CA lines in an IDLE state.
The options are the following:
OVERRIDE_SOFTKEY_ACTIVE
0
Specifies if the phone shows default soft keys for CA lines in an ACTIVE state.
The options are the following:
OVERRIDE_SOFTKEY_INCOMING
0
Specifies if the phone shows default soft keys for CA lines in an INCOMING state.
The options are the following:
OVERRIDE_SOFTKEY_INCOMING_VISUAL
0
Specifies if the phone shows default soft keys for CA lines in an INCOMING_VISUAL state.
The options are the following:
OVERRIDE_SOFTKEY_HELD
0
Specifies if the phone shows default soft keys for CA lines in an HELD state.
The options are the following:
OVERRIDE_SOFTKEY_OUTGOING
0
Specifies if the phone shows default soft keys for CA lines in an OUTGOING state.
The options are the following:
OVERRIDE_SOFTKEY_ACTIVE_PAGETARGET
0
Specifies if the phone shows default soft keys for CA lines in an ACTIVE_PAGE state.
The options are the following:
OVERRIDE_SOFTKEY_DIALING
0
Specifies if the phone shows default soft keys for CA lines in a Dialing state.
The options are the following:
OVERRIDE_SOFTKEY_DIALTONE
0
Specifies if the phone shows default soft keys for CA lines in an Dialtone state.
The options are the following:
OVERRIDE_SOFTKEY_CONFERENCE_DIALING
0
Specifies if the phone shows default soft keys for CA lines in an Conference Dialing state.
The options are the following:
OVERRIDE_SOFTKEY_CONFERENCE_OUTGOING
0
Specifies if the phone shows default softkeys for CA lines in an Conference Outgoing state.
The options are the following:
OVERRIDE_SOFTKEY_CONFERENCE_CONSULT
0
Specifies if the phone shows default soft keys for CA lines in an Conference Consult state.
The options are the following:
OVERRIDE_SOFTKEY_CONFERENCE_ACTIVE
0
Specifies if the phone shows default soft keys for CA lines in an Conference Consult state.
The options are the following:
OVERRIDE_SOFTKEY_TRANSFER_DIALING
0
Specifies if the phone shows default soft keys for CA lines in an Transfer Dialing state.
The options are the following:
OVERRIDE_SOFTKEY_TRANSFER_OUTGOING
0
Specifies if the phone shows default soft keys for CA lines in an Transfer Outgoing state.
The options are the following:
OVERRIDE_SOFTKEY_TRANSFER_CONSULT
0
Specifies if the phone shows default soft keys for CA lines in an Transfer Consult state.
The options are the following:
P
PHNCC
Specifies the country code for United States. The value is
Valid values 1 through 999.
PHNDAC
Dial access code - will be applied if the dialed number length + the length of the Dial access code length equals the national number length. This calculation does not include an outside line access code. It is different from PHNLAC since PHNLAC is applied when the phone number length is more than ext number length and less than national number length.
PHNDPLENGTH
Specifies the internal extension number length.
If your extension is 12345, and your dial plan length is 5.
The maximum extension length is 13. This value must match the extension length set on your call server.
Valid values are 3 through 13.
PHNEMERGNUM
Specifies an emergency phone number to be dialed if the associated button is selected.
Valid values can contain up to 30 dialable characters (0 to 9, *, #).
PHNIC
Specifies the international access code.
For the United States, the value is
Valid values are from 0 to 4 dialable characters (0-9,*,#).
PHNLAC
Phone's Local Area Code indicates the phone's local area code, which along with the parameter LOCAL_DIAL_AREA_CODE, allows users to dial local numbers with more flexibility. PHNLAC is a string representing the local area code the phone.
Note:
This parameter is supported when the phone is failed over.
PHNLD
Specifies the long distance access code.
Valid values are 0 through 9 and empty string.
If long distance access code is not needed then set the parameter to null.
PHNLDLENGTH
Specifies the national phone number length. For example, 800-555-1111 has a length of 10.
Valid values are 5 through 15.
PHNMUTEALERT_BLOCK
Specifies if the Mute Alert feature is blocked or unblocked.
The options are the following:
PHNNUMOFSA
Specifies the number of session appearances the phone must support.
Valid values are 1 through 10.
Note:
The value of PHNNUMOFSA is overridden when the phone downloads the call appearances from Personal Profile Manager (PPM).
PHNOL
Specifies the outside line access code. This is the number you press to make an outside call.
Valid values are 0 to 2 dialable characters (0-9, *, #).
PHONEKEY
Specifies the list of pre-configured keys.
Note:
Do not use this parameter to configure line or custom keys.
Specifies whether the user can adjust the ringer volume when the phone is locked.
The options are the following:
Note:
This parameter is applicable only when the AUDASYS value is set to 1, 2, or 3.
PHONE_LOCK_BLOCK_INCOMING_CALLS
Specifies whether the phone displays an incoming call while the phone is locked.
The options are the following:
PHONE_LOCK_GUEST_LOGIN
Specifies whether a guest user can log in to a phone when the primary user has locked it.
The primary user can lock the phone by pressing the Lock soft key or when the PHONE_LOCK_IDLETIME expires.
The options are the following:
Note:
This setting is available only if GUESTLOGINSTAT is set to 1.
This parameter is not supported by Avaya J129 IP Phone.
PHONE_LOCK_IDLETIME
Specifies the interval of idle time in minutes, after which the phone automatically locks.
Valid values are 0 through 10,080.
Valid values are from 0 to 10080.
The options are the following:
When you set the parameter to
Note:
When you set ENABLE_PHONE_LOCK parameter to
.
PHONE_LOCK_PASSWORD_FAILED_ATTEMPTS
Specifies the number of consecutive failed attempts that you permit to unlock the phone. After the maximum is reached, the user will be blocked from further attempts for a period of time before being allowed to attempt again.
If you set the value to
PHONE_LOCK_PASSWORD_LOCKED_TIME
Specifies the length of time that you set where the user will be blocked from attempting to unlock the phone if the user exceeds the maximum number of failed unlock attempts.
The value ranges between 5–1440 minutes.
PHONE_LOCK_PIN
Specifies the PIN that you set for the user to enter it to unlock the phone.
The value can be only digits, ranging between 4–20 characters.
PHY1STAT
if you do not set any value here, the SIP password can be used for unlocking the phone.
PHY1STAT
Specifies the speed and duplex settings for the Ethernet line interface.
The options are the following:
PHY2_AUTOMDIX_ENABLED
Specifies whether auto-MDIX is enabled on PHY2.
The options are the following:
PHY2PRIO
Specifies the layer 2 priority value to be used for frames received on the secondary Ethernet interface when VLAN separation is enabled. The parameter is not supported when VLANSEPMODE is 1.
Valid values are 0 through 7.
Note:
J129 does not support this parameter.
PHY2STAT
Specifies the speed and duplex settings for the secondary (PC) Ethernet interface.
The options are the following:
PHY2TAGS
Determines whether or not VLAN tags are stripped on Ethernet frames going out of the Computer (PC) port.
The options are the following:
Note:
This parameter is configured through the settings file.
PHY2VLAN
Specifies the value of the 802.1Q VLAN ID used by frames forwarded to and from the secondary (PHY2) Ethernet interface when VLAN separation is enabled.
Valid values are 0 through 4094.
Note:
The parameter is configured through the following:
Specifies the number of retries for entering PKCS12 file password. If user failed to enter the correct PKCS12 file password after PKCS12_PASSWD_RETRY retries, then the phone will continue the startup sequence without installation of PKCS12 file. Valid values are from 0 to 100.
The options are the following:
For certificate profile 2 and 3, use PKCS12_2_PASSWD_RETRY and PKCS12_3_PASSWD_RETRY.
PKCS12URL,
PKCS12_2_URL
, PKCS12_3_URL
Specifies the URL to be used to download a PKCS #12 file containing an identity certificate and its private key. Valid values contain 0 to 255 ASCII characters, zero or one URL. The value can be a string that contains either $SERIALNO or $MACADDR, but it may contain other characters as well. If $MACADDR is added to the URL, then the PKCS12 file name on the file server includes MAC address without colons. PKCS12 file download is preferred over SCEP if PKCS12URL is defined.
The options are the following:
Null: (Default) Specifies that the PKCS#12 identity certificate download is disabled.
0 – 255 characters.
To specify the URL for certificate profile 2 and 3, use PKCS12_2_URL and PKCS12_3_URL.
PKCS12_USAGE
Specifies the list of services for which the certificate assigned to the PKCS12#1 profile is applied.
Valid values:
In case the usage value is set to
You can set the value to
. For example:
When value is set to
PKCS12_2_USAGE
Specifies the list of services for which the certificate assigned to the PKCS12#2 profile is applied.
Valid values:
In case the usage value is set to
PKCS12_3_USAGE
Specifies the list of services for which the certificate assigned to the PKCS12#3 profile is applied.
Valid values:
In case the usage value is set to
PLAY_TONE_UNTIL_RTP
Specifies whether locally-generated ringback tone stops as soon as SDP is received for an early media session, or whether it will continue until RTP is actually received from the far-end party.
The options are the following:
PRESENCE_ACL_CONFIRM
Specifies the handling of a Presence ACL update with pending watchers.
The options are the following:
This parameter is not supported in IP Office environment as presence is not supported.
PRESERVED_CALL_DURATION
Specifies the time interval in minutes if ENABLE_IPOFFICE is set to 2 and if MEDIA_PRESERVATION is set to 1.
The time interval can be from 10 minutes to 120 minutes.
PRIVACY_SLAAC_MODE
Specifies the preference for Privacy Extensions.
The options are the following:
PRIMARY_LINE_EXTENSION
Specifies the default label for primary line call appearances and is applied if the user did not customize the label.
For example:
SET PRIMARY_LINE_EXTENSION "Primary line"
The default value is null.
From the software version 4.0.5 and later, Avaya J139 IP Phone, Avaya J159 IP Phone, and Avaya J169/J179 IP Phone support the PRIMARY_LINE_EXTENSION parameter.
From the software version 4.0.6 and later, Avaya J189 IP Phone supports the PRIMARY_LINE_EXTENSION parameter.
From the software version 4.1.7 and later, Avaya J129 IP Phone supports the PRIMARY_LINE_EXTENSION parameter.
PROCPSWD
Specifies an access code to access the local (craft) procedures.
Specifies an access code to access the admin menu procedures.
Valid values contain 0 through 7 ASCII numeric digits. The default value is
Note:
Setting this parameter through PPM is more secure because this file can usually be accessed and read by anyone on the network. Setting the value in this file is intended primarily for configurations with versions of phone or if server software that do not support setting this value from the server.
For enhanced security, use ADMIN_PASSWORD instead of PROCPSWD.
PROCSTAT
Specifies whether local (craft) procedures can be used to configure the phone.
Specifies whether local administrative procedures can be used to configure the phone.
The options are the following:
PROVIDE_CF_RINGTONE
Specifies if the call forward ringtone option is provided to the user.
The options are the following:
PROVIDE_EXCHANGE_CALENDAR
Specifies if menu items for exchange calendar are displayed.
The options are the following:
PROVIDE_EXCHANGE_CONTACTS
Specifies if menu items for exchange contacts are displayed.
The options are the following:
PROVIDE_KEY_REPEAT_DELAY
Specifies how long a navigation button must be held down before it begins to auto-repeat, and if an option is provided by which the user can change this value.
The options are the following:
Note:
Avaya J129 IP Phone does not support this feature.
PROVIDE_LOGOUT
Specifies if user can log out from the phone.
The options are the following:
Note:
This parameter is set to
PROVIDE_NETWORKINFO_SCREEN
Specifies if the Network Information menu is displayed on the phone.
The options are the following:
PROVIDE_OPTIONS_SCREEN
Specifies if Options & Settings menu is displayed on phone.
The options are the following:
PROVIDE_PRIMARY_RINGTONE
Specifies if the user menus related to the ringtones are displayed on the phone user interface and the web interface.
The options are the following:
PSTN_VM_NUM
Specifies the dialable string that is used to call into the messaging system. For example, when you press the Message Waiting button.
Note:
This parameter is supported when the phone is failed over.
PUSHCAP
Controls the modes of individual Push types.
The value is a 3, 4 or 5 digit number, of which each digit controls a Push type and can have a value of 0, 1 or 2.
The options are the following:
The Push types controlled by each digit (11111) are the following:
||||+- The rightmost digit controls Top line Push requests.
|||+-- The next digit to the left controls display (WML browser) Push requests.
||+--- The next digit to the left controls receive audio Push requests.
|+---- The next digit to the left controls transmit audio Push requests.
+----- The next digit to the left controls phonexml Push requests.
Note:
The display Push request (the WML browser) is supported only by the Avaya J159 IP Phone, Avaya J169/J179 IP Phone, and Avaya J189 IP Phone.
PUSHPORT
Specifies the TCP port number to be used by the HTTP server in the phone for push.
Valid values are 80 through 65535.
PUSH_MODE
Specifies the combination of secure and non-secure Push to be used.
The Push mode ranges from 0-2 and is of the following types:
Note:
If PUSH_MODE= 2 (Both) subscribe using secure Push is attempted first, and if it fails, subscribe over non-secure is attempted.
PUSHPORT_SECURE
Specifies the port for listening to the secure Push request. The secure push uses HTTPS.
Q
QLEVEL_MIN
Specifies the minimum quality level for which a low local network quality indication will not be displayed.
The options are the following:
Note:
Avaya J129 IP Phone does not support this parameter.
QTP_BUTTON_COMPRESS
Specifies the range of features which can be assigned to Quick Touch Panel on phone screen. Features and Autodials configured on SMGR buttons 4 through 24 will show up on the QTP, up to a maximum of 8 buttons. Call Appearances and Bridged Call Appearances will be excluded from QTP.
The options are the following:
SIP phones do not support call status updates for the soft keys on QTP. The phones do not display any call indication, for example, an incoming call. You must not put call appearances on QTP because the call state display is very limited.
To remove Bridged Call Appearances and Call Appearances from QTP, set QTP_BUTTON_COMPRESS to 1.
R
RDS_INITIAL_RETRY_ATTEMPTS
Specifies the number of retries after which the phone abandons its attempt to contact the PPM server.
Valid values are 1 through 30.
RDS_INITIAL_RETRY_TIME
Specifies the number of seconds that the phone waits for the first time before trying to contact the PPM server again after a failed attempt. Each subsequent retry is delayed by double the previous delay.
Valid values are 2 through 60.
RDS_MAX_RETRY_TIME
Specifies the maximum delay interval in seconds after which the phone abandons its attempt to contact the PPM server.
Valid values are 2 through 3600.
RECORDINGTONE_INTERVAL
Specifies the number of seconds between call recording tones.
Valid values are 1 through 60.
RECORDINGTONE_VOLUME
Specifies the volume of the call recording tone in 5dB steps.
The options are the following:
Note:
Avaya J129 IP Phone does not support this parameter.
RECOVERYREGISTERWAIT
Specifies a number of seconds. If no response is received to a REGISTER request within the number of seconds specified by WAIT_FOR_REGISTRATION_TIMER, the phone tries again after a randomly selected delay of 50% to 90% of the value of RECOVERYREGISTERWAIT.
Valid values are 10 through 36000.
REDIRECT_TONE
Specifies the tone to play when a call goes to coverage.
Valid values are from 1 to 4.
REGISTERWAIT
Specifies the number of seconds between re-registrations with the current server. Valid values are from 30 to 86400.
RESTART_FROM_LOGIN
Specifies if the phone displays the Restart soft key from the Login screen. When the user presses the Restart soft key, the phone prompts to confirm the restart. Upon user confirmation, the phone restarts.
The options are the following:
Note:
Avaya J129 IP Phone does not support restarting the phone from the Login screen.
REUSETIME
Specifies the number of seconds that the DHCP is attempted:
With a VLAN ID of zero. True when L2Q is set to 1.
With untagged frames. True if L2Q is set to 0 or 2.
Before reusing the IP address and the associated address information that the phone had the last time it successfully registered with a call server.
While reusing an address, DHCP enters the extended rebinding state described above for DHCPSTD.
Valid values are 0 and 20 to 999. The default value is 60. A zero value means that DHCP will try forever, and there will be no reuse.
Note:
This parameter does not apply to DHCPv6.
RINGTONES
Specifies a list of display names, file names, or URLs for custom ringtone files to be downloaded and offered to users.
The list can contain 0 to 1023 UTF-8 characters. The default value is null.
Values are separated by commas without any intervening spaces. Each value consists of a display name, an equals sign, and a file name or URL. Display names can contain spaces, but if any do, the entire list must be quoted. Ring tone files must be single-channel WAV files coded in ITU-T G.711 u-law or A-law PCM with 8-bit samples at 8kHz.
RINGTONES_UPDATE
Specifies if the phone queries the file server to determine if there is an updated version of each custom ring tone file each time the phone starts up or resets.
The options are the following:
RINGTONESTYLE
Specifies the style of ring tones that are offered to the user for personalized ringing when Classic is selected, as opposed to Rich.
The options are the following:
RTCP_XR
Specifies whether and how VoIP Metrics Report Block as defined in RTP Control Protocol Extended Report is sent.
The options are the following:
You can configure the voice monitoring server using the parameter RTCPMON.
When you set RTCP_XR to value 1 or 2, the voice RTCP XR report is sent to RTCPMON.
RTCPMON
Specifies the IP or DNS address for the RTCP monitor (VMM server) in dotted-decimal format or DNS name format.
You can set this parameter only if the environment is not an Avaya environment. The values can range from 0 through 255 characters.
RTCPMONPERIOD
Specifies the interval, in seconds, for sending out RTCP monitoring reports. Valid values are from 5 to 30 seconds.
RTCPMONPORT
Specifies the RTCP monitor port number.
You can set this parameter only if the environment is not an Avaya environment. The values can range from 0 through 65535. Default is 5005.
RTP_PORT_LOW
Specifies the lower limit of the UDP port range to be used by RTP or RTCP and SRTP or SRTCP connections.
The values can range from 1024 through 65503.
RTP_PORT_RANGE
Specifies the range or number of UDP ports available for RTP or RTCP and SRTP or SRTCP connections.
This value is added to RTP_PORT_LOW to determine the upper limit of the UDP port range.
The values can range from 32 through 63487.
S
SCEPPASSWORD
Specifies a challenge password to use with SCEP. The value of SCEPPASSWORD, if non-null, is included in a challengePassword attribute in SCEP certificate signing requests.
If the value contains
is replaced by the phone serial number in upper case. If the value contains
is replaced by the phone MAC address in lower case without the colon separators.
In order to use enhanced certificate renewal in SMGR 8.1.3 and later, SCEPPASSWORD value cannot be empty nor it can be set to a variable such as
.
If you want to renew or enrollment using standard SCEP protocol, parameter SCEP_ENTITY_CLASS must be removed.
SCEPENCALG
Specifies SCEP Encryption Algorithm.
The options are the following:
0: DES
1: AES-256
Note:
Avaya J129 IP Phone supports this parameter.
SCEP_ENTITY_CLASS,
Specifies to use the enhanced SCEP enrollment request. The value of entity-class is set in SMGR.
SCEP_USAGE
Specifies the list of services for which the certificate assigned to the SCEP#1 profile is applied.
Valid values:
In case the usage value is set to
SCEP_2_USAGE
Specifies the list of services for which the certificate assigned to the SCEP#2 profile is applied.
Valid values:
In case the usage value is set to
SCEP_3_USAGE
Specifies the list of services for which the certificate assigned to the SCEP#3 profile is applied.
Valid values:
In case the usage value is set to
SCREENSAVER_CLOCK_ENABLE
Specifies whether to present clock on the screensaver. User can override the configuration in the settings menu.
The options are the following:
0: Clock is not presented on screensaver.
1: Clock is presented on screensaver.
SCREENSAVER_IMAGE
N/A
Specifies a list of custom screensaver images that you can upload to the provisioning server. Users can set these images on their phone.
The phone supports up to 5 images with the following limitations:
Software version 4.0.11 and earlier support the .jpeg format. Software version 4.0.12 and later support the .jpg format.
The file size can be up to 256 KB.
The file names are case sensitive.
Avaya J139 IP Phone, Avaya J159 IP Phone, Avaya J169/J179 IP Phone screen resolution is 320x240 pixels. Avaya J169/J179 IP Phone and and Avaya J189 IP Phone color depth is 16 bits. and Avaya J189 IP Phone screen resolution is 800x480 pixels. Avaya J169/J179 IP Phone phones support grayscale color spaces and other color display phones support yCbCr color spaces.
The file names must be comma-separated without intervening spaces. You can define absolute URLs, absolute paths, relative paths, macros, or file names for the image files.
An absolute URL. For example, http://username:password@provisioning.example.com:8088/path/image1.jpg
If the server requires credential authentication, the credentials must be defined in the URL string.
An absolute path that ignores HTTPDIR or TLSDIR. For example,/path/image1.jpg
A relative path that is appended to HTTPDIR or TLSDIR. For example,path/image1.jpg
Macros. The actual values replace the macros. For example,
"$SERIALNO"is replaced with the phone serial number in uppercase.
"$MACADDR"is replaced with the phone MAC address in lowercase without intervening colons.
"$MODEL4"is replaced with the four-character phone model number in uppercase.
File name.
For example, SET SCREENSAVER_IMAGE "screensaver_example1.jpg,screensaver_example2.jpg"
SCREENSAVER_SLIDESHOW_INTERVAL
0
Specifies if the J100 supports displaying a screen saver slide show. Value defines the duration in seconds to display each slide show image. Slide show images display as defined by SCREEN_SAVER_IMAGE_DISPLAY or SCREENSAVER_IMAGE_DISPLAY_SECONDARY or SCREENSAVER_IMAGE_DISPLAY_JEM.
The user can override this configuration in the user settings menu depending on the value of SCREENSAVER_IMAGE_SELECTABLE.
The valid values are:
0: disabled (default)
1-999: enabled
SCREENSAVER_IMAGE_DISPLAY
N/A
Enables the administrator to display the required screen saver image.
The default value is empty. The value is separated by commas without any intervening spaces.
To select one of the seven built-in default images, specify a value from 0 to 6.
0: To select default image 1.
1: To select default image 2.
2: To select default image 3.
3: To select default image 4.
4: To select default image 5.
5: To select default image 6.
6: To select default image 7.
To select a custom screen saver image, you can define a file name from the list of file names defined in SCREENSAVER_IMAGE.
To select a custom screen saver image slide show, you can define a comma-separated list of file names from the list of file names defined in SCREENSAVER_IMAGE.
Note:
If SCREENSAVER_IMAGE_SELECTABLE is set to 1, then the end user may override this setting.
SCREENSAVER_IMAGE_DISPLAY_JEM
Specifies the screen saver image to be displayed on the Avaya J100 Expansion Module.
The default value is empty. The value is separated by commas without any intervening spaces.
To select one of the seven built-in default images, specify a value from 0 to 6.
0: To select default image 1.
1: To select default image 2.
2: To select default image 3.
3: To select default image 4.
4: To select default image 5.
5: To select default image 6.
6: To select default image 7.
To select a custom screen saver image, you can define a file name from the list of file names defined in SCREENSAVER_IMAGE_JEM.
To select a custom screen saver image slide show, you can define a comma-separated list of file names from the list of file names defined in SCREENSAVER_IMAGE_JEM.
Note:
If the parameter is not defined, then the phone uses Default image 1.
SCREENSAVER_IMAGE_JEM
Specifies a comma-separated list of screensaver images for the Avaya J100 Expansion Module display.
Avaya J100 Expansion Module supports up to 5 screensaver images with the following limitation:
The expansion modules support the .jpg format files.
The maximum file size is 256 KB.
The file names are case sensitive.
The color depth is limited to 16 bits.
The Avaya J100 Expansion Module has a resolution of 272 x 480 pixels.
You can define absolute URLs, absolute paths, relative paths, macros, or file names for the image files.
An absolute URL. For example, http://username:password@provisioning.example.com:8088/path/image1.jpg
If the server requires credential authentication, the credentials must be defined in the URL string.
An absolute path that ignores HTTPDIR or TLSDIR. For example,/path/image1.jpg
A relative path that is appended to HTTPDIR or TLSDIR. For example,path/image1.jpg
Macros. The actual values replace the macros. For example,
"$SERIALNO"is replaced with the phone serial number in uppercase.
"$MACADDR"is replaced with the phone MAC address in lowercase without intervening colons.
"$MODEL4"is replaced with the four-character phone model number in uppercase.
File name.
For example, SET SCREENSAVER_IMAGE_JEM "screensaver_jem_example1.jpg,screensaver_jem_example2.jpg"
.
SCREENSAVER_IMAGE_JEM_FOLLOW_PRIMARY
Specifies whether the Avaya J100 Expansion Module screen saver image always follows the primary display or can have a separate screen saver image.
The options are:
SCREENSAVER_IMAGE_SELECTABLE
Enables the end user to select and change the screen saver images.
The options are the following:
0: End user can not select and change the screen saver images from the settings menu.
1: End user can select and change the screen saver images from the settings menu.
SCREENSAVER_IMAGE_SELECTABLE_JEM
Specifies whether the user can select a screen saver image.
The options are:
0: The end user is not allowed to choose the Avaya J100 Expansion Module screen saver image. The value set by an administrator is used.
1: The end user is allowed to choose the Avaya J100 Expansion Module screen saver image.
SCREENSAVER_IMAGE_SECONDARY
Specifies a list of screensaver images for the secondary screen.
The phone supports up to five images with the following limitations:
Software version 4.0.11 and earlier support the .jpeg format. Software version 4.0.12 and later support the .jpg format.
The file size can be up to 256 KB.
The file names are case sensitive.
The file names must be comma-separated without intervening spaces. You can define absolute URLs, absolute paths, relative paths, macros, or file names for the image files.
An absolute URL. For example, http://username:password@provisioning.example.com:8088/path/image1.jpg
If the server requires credential authentication, the credentials must be defined in the URL string.
An absolute path that ignores HTTPDIR or TLSDIR. For example,/path/image1.jpg
A relative path that is appended to HTTPDIR or TLSDIR. For example,path/image1.jpg
Macros. The actual values replace the macros. For example,
"$SERIALNO"is replaced with the phone serial number in uppercase.
"$MACADDR"is replaced with the phone MAC address in lowercase without intervening colons.
"$MODEL4"is replaced with the four-character phone model number in uppercase.
File name.
For example, SET SCREENSAVER_IMAGE_SECONDARY "secondary_screensaver_example1.jpg,secondary_screensaver_example2.jpg"
Note:
Avaya J159 IP Phone and Avaya J189 IP Phone support this parameter.
SCREENSAVER_IMAGE_DISPLAY_SECONDARY
Specifies the screen saver image to be displayed on the Secondary screen. The file name will be one of the file names listed in SCREENSAVER_IMAGE_SECONDARY.
The default value is empty. The value is separated by commas without any intervening spaces.
To select one of the seven built-in default images, specify a value from 0 to 6.
0: To select default image 1.
1: To select default image 2.
2: To select default image 3.
3: To select default image 4.
4: To select default image 5.
5: To select default image 6.
6: To select default image 7.
To select a custom screen saver image, you can define a file name from the list of file names defined in SCREENSAVER_IMAGE_SECONDARY.
To select a custom screen saver image slide show, you can define a comma-separated list of file names from the list of file names defined in SCREENSAVER_IMAGE_SECONDARY.
Note:
If SCREENSAVER_IMAGE_SELECTABLE_SECONDARY is set to 1, then the end user may override this setting.
Note:
Avaya J159 IP Phone and Avaya J189 IP Phone support this parameter.
SCREENSAVER_IMAGE_SELECTABLE_SECONDARY
Enables the end user to select screen saver images for the secondary screen.
The options are the following:
0: The user can not use a screen saver images from the phone UI.
1: The user can select a background images from the phone UI.
This parameter overrides the value configured using SCREENSAVER_IMAGE_DISPLAY_SECONDARY parameter.
Note:
Avaya J159 IP Phone and Avaya J189 IP Phone supports this parameter.
SCREENSAVERON
Specifies the number of minutes of idle time after which the screen saver is displayed.
If an image file is downloaded based on the LOGOS and CURRENT_LOGO parameter, it is used as the screen saver. Otherwise, the built-in Avaya one-X(TM) screen saver is used.
Valid values are 0 through 999. The default value is 240 (4 hours).
A value of 0 means that the screen saver will not be displayed automatically when the phone is idle.
SCROLLING_MODE
0
Specifies the scrolling mode used on the phone.
The options are the following:
0: Line scrolling mode is used.
1: Page scrolling mode is used.
SDPCAPNEG
Specifies if SDP capability negotiation is enabled.
The options are the following:
SECURECALL
Specifies if an icon will be displayed when SRTP is being used.
The options are the following:
Note:
This parameter is supported by phone software version R6.2 up to R7.0.0. This parameter is obsolete from release R7.0.0. For an end-to-end secure call indication feature, use Avaya Aura® platform 7.0 and later.
SEND_DTMF_TYPE
Specifies if DTMF tones are sent in-band as regular audio, or out-of-band using RFC 2833 procedures.
The options are the following:
SERVER_CERT_RECHECK_HOURS
Specifies the number of hours after which certificate expiration and OCSP will be used, if OCSP is enabled, to recheck the revocation and expiration status of the certificates that were used to establish a TLS connection. Valid values are from 0 to 32767.
The options are the following:
SHARED_CONTROL_LOSS_DURATION_WITHOUT_PROMPT
The duration in minutes specifies how long after a Shared Control connection is lost before the phone accepts a new connection without prompting for confirmation.
The valid value range is 0 - 60 (minutes). Where 0 indicates that the shared control confirmation popup is always displayed after the shared control connection is restored.
SHORTCUT_ACTION_CONTACT, SHORTCUT_ACTION_AUTODIAL
Specifies the action performed if the user presses an Autodial key or selects a contact on the Phone screen during an active call.
Note:
Avaya J129 IP Phone does not support this feature.
SHOW_CALLER_ID_VALIDATION
Specifies whether the phone displays caller ID validation information.
Valid values:
For the Avaya J129 IP Phone, value
. The phone does not display the Unknown caller ID validation status.
SHOW_CALLER_ID_VALIDATION_ON_CA
Specifies whether the CA/BCA lines display caller ID validation information.
Valid values:
SHOW_LAST_EXTENSION
Specifies whether to display last extension after logout.
The options are the following:
SIG
Specifies the type of software to be used by the phone by controlling which upgrade file is requested after a power-up or a reset.
The options are the following:
0: Download the upgrade file for the same signaling protocol that is supported by the current software (default)
1: Download 96x1Hupgrade.txt (for H.323 software)
2: Download 96x1Supgrade.txt (for SIP software)
SIG_PORT_LOW
Specifies the minimum port value for SIP signaling. (1024 -65503).
SIG_PORT_RANGE
Specifies the range or number of SIP signaling ports. This value is added to SIG_PORT_LOW to determine the upper limit of the SIP signaling port range (32-64511).
SIGNALING_ADDR_MODE
Specifies the SIP controller IP address from SIP_CONTROLLER_LIST_2. This parameter is used by SIP signaling on a dual mode phone.
The single IPv4 mode phone ignores SIGNALING_ADDR_MODE and SIP_CONTROLLER_LIST_2 and selects the SIP controller's IP addresses from SIP_CONTROLLER_LIST.
The single IPv6 mode phone ignores SIGNALING_ADDR_MODE and SIP_CONTROLLER_LIST and selects the SIP controller's IPv6 addresses from SIP_CONTROLLER_LIST_2.
The options are the following:
SIMULTANEOUS_REGISTRATIONS
Specifies the number of Session Managers with which the phone simultaneously register.
Valid values are 1, 2, 3, 4 or 5. The default value is 3.
Valid values are 1, 2, or 3.The default value is 3.
Note:
This parameter is set to
SIP_CONTROLLER_LIST
Specifies a list of SIP controller designators, separated by commas without any spaces. The list is used on IPv4-only and dual mode phones if SIP_CONTROLLER_LIST_2 is not provided. Controller designator has the following format: host[:port][;transport=xxx] where
host is an proxy address in dotted-decimal or DNS name format.
[:port] is an optional port number.
[;transport=xxx] is an optional transport type where xxx can be TLS, TCP, or UDP.
For example, SIP_CONTROLLER_LIST="10.138.251.56:5060;transport=tcp"
SIP_CONTROLLER_LIST_2
This parameter replaces SIP_CONTROLLER_LIST for dual mode phones. It contains the list of SIP Proxy or Registrar servers separated by comma when the SIP device is configured for the dual-stack operation.
SIP_CONTROLLER_LIST_2 is used on IPv6-only phones to provide the list of SIPv6 servers. SIPv4 servers are ignored in IPv6-only mode.
Valid values are 0 to 255 characters in the dotted decimal or colon-hex format.
The SIP Proxy list has the following format: host[:port][;transport=xxx] where
host is IP addresses in dotted-decimal format or hex format.
[:port] is the port number. The default values are 5060 for TCP and 5061 for TLS.
[;transport=xxx] is the transport type and xxx is either TLS or TCP. The default value is TLS.
For example, SIP_CONTROLLER_LIST_2="10.16.26.88:5060;transport=tcp"
SIP_CRLF_PING_ENABLE
0
Specifies if the phone sends RFC 5626 SIP double CRLF Keep Alive ping for SIP connections that use TCP or TLS.
If the SIP server fails to support RFC 5626, the phone performs a SIP registration for each detected failed SIP ping.
This parameter does not apply if the SIP transport is UDP.
Specifies the number of seconds the phone waits before sending a SIP Keep Alive ping, when SIP_CRLF_PING_ENABLE is enabled.
Valid value is a number between 10-900.
SIP_PORT_SECURE
Specifies the destination TCP port for SIP messages sent over TLS.
Valid values are 1024 through 65535. The default value is 5061.
The parameter is used in non-Avaya environment. In Avaya environment, this parameter is overwritten by PPM configuration.
SIPDOMAIN
Specifies the domain name to be used during SIP registration.
The value can contain 0 to 255 characters. The default value is null.
SIPPORT
Specifies the port the phone opens to receive SIP signaling messages.
Valid values are 1024 through 65535. The default value is 5060.
SIPREGPROXYPOLICY
Specifies if the phone attempts to maintain one or multiple simultaneous registrations.
The options are the following:
Note:
This parameter is supported only in IP Office environment.
SKILLSCREENTIME
Specifies the duration, in seconds, that the Skills screen is displayed.
Valid values are 0 through 60. The default value is 5.
A value of 0 means that the Skills screen in not removed automatically when the agent logs in.
Note:
Avaya J129 IP Phone and Avaya J139 IP Phone do not support this feature.
SLMCAP
Specifies if the SLA Monitor agent is enabled for packet capture.
The options are the following:
SLMCTRL
Specifies whether the SLA Monitor agent is enabled for phone control.
The options are the following:
SLMPERF
Specifies whether the SLA Monitor agent is enabled for phone performance monitoring.
The options are the following:
SLMPORT
Specifies the UDP port that will be opened by the SLA Monitor agent to receive discovery and test request messages.
Valid values are 6000 through 65535. The default value is 50011.
Note:
If default port is not used, both the SLA Mon agent and the server must be configured with the same port. This parameter impacts the phone's SLA Mon agent configuration. A corresponding configuration must also be made on the SLA Mon server agentcom-slamon.conf file.
SLMSRVR
Specifies the IP address and the port number of the SLA Mon server in the aaa.bbb.ccc.ddd:n format.
Set the IP address of the SLA Mon server in the aaa.bbb.ccc.ddd format to restrict the registration of agents only to that server.
Specifying a port number is optional. If you do not specify a port number, the system takes 50011 as the default port. If the value of the port number is 0, than any port number is acceptable.
The IP address must be in the dotted decimal format, optionally followed by a colon and an integer port number from 0 to 65535.
To use a non-default port, set the value in the aaa.bbb.ccc.ddd:n format, where aaa.bbb.ccc.ddd is the IP addressof the SLA Mon server.
Note:
If default port is not used, both the SLA Mon agent and server must be configured with the same port. SLMSRVR impacts the phone's SLA Mon agent configuration. A corresponding configuration must also be made on the SLA Mon server agentcom-slamon.conf file.
SLMSTAT
Specifies if the SLA Monitor agent is enabled or not.
The options are the following:
SMGR_AUTO_FAVORITE
Specifies whether all the Avaya Aura System Manager (SMGR) configured features and supported Autodials irrespective of adding it to favorite or not, are available on the phone screen. Use Avaya Aura 8.0.0.0 or earlier.
The options are the following:
Note:
The phone does not support the display of Autodials without a number.
Avaya J129 IP Phone does not support this feature.
SNMPADD
Specifies a list of source IP addresses from which SNMP query messages will be accepted and processed.
Addresses can be in dotted-decimal format (IPv4), colon-hex format (IPv6, if supported), or DNS name format, separated by commas without any intervening spaces.
The list can contain up to 255 characters. The default value is null.
SNMPSTRING
Specifies a security string that must be included in SNMP query messages for the query to be processed.
Valid values contain 0 through 32 ASCII alphanumeric characters.
The default value is null. Null disables SNMP.
SNTP_SYNC_INTERVAL
Specifies the time interval, in minutes, during which the phone attempts to synchronize its time with configured NTP servers. Valid values are from 60 to 2880 minutes.
SNTPSRVR
Specifies a list of addresses of SNTP servers.
Addresses can be in dotted-decimal or DNS name format, separated by commas without any intervening spaces.
The list can contain up to 255 characters.
SOFTKEY_ACTIVE_PAGETARGET
Specifies the custom soft key for the call appearance lines in an Active Page target state. You can provide the soft key attributes and labels, which a phone displays during a page call, along with standard soft keys.
For example:
SET SOFTKEY_ACTIVE_PAGETARGET "type=dtmf;action=AnswerDigitSequence;label=Answer"ADD SOFTKEY_ACTIVE_PAGETARGET "type=function;action=endcall;label=End"
SOFTKEY_ACTIVE
Null
Specifies the custom soft key for the call appearance lines in an Active state. You can provide the soft key attributes and labels, which a phone displays during an active call, along with standard active call soft keys.
For example:
SET SOFTKEY_ACTIVE "type=dtmf;action=##*3;label=Park"ADD SOFTKEY_ACTIVE "type=dtmf;action=*34;label=Record"
SOFTKEY_HELD
Null
Specifies the custom soft key for the call appearance lines in an Held state. You can provide the soft key attributes and labels, which a phone displays during an outgoing call, along with standard soft keys.
For example:
SET SOFTKEY_HELD "type=function;action=endcall;label=drop"ADD SOFTKEY_HELD "type=function;action=endcall;label=finish"
SOFTKEY_CONFIGURATION
0,1,2
Specifies which feature will show up on which soft key on the Avaya J129 IP Phone screens.
The features are defined as follows:
0 = Redial
1 = Contacts
2 = Emergency
3 = Recents
4 = Voicemail
SOFTKEY_IDLE
Null
Specifies the custom soft key for the call appearance lines in an Idle state. You can provide the soft key attributes and labels, which a phone displays during idle, along with standard soft keys.
For example:
SET SOFTKEY_IDLE "type=function;action=newcall;label=call"ADD SOFTKEY_IDLE "type=function;action=emergency;label=emergency2"
SOFTKEY_INCOMING
Null
Specifies the custom soft key for the call appearance lines in an Incoming state. You can provide the soft key attributes and labels, which a phone displays during an incoming call, along with standard soft keys.
For example:
SET SOFTKEY_INCOMING "type=function;action=newcall;label=call"ADD SOFTKEY_INCOMING "type=function;action=decline;label=reject"
SOFTKEY_INCOMING_VISUAL
Null
Specifies the custom soft key for the call appearance lines in an Incoming Visual state. You can provide the soft key attributes and labels, which a phone displays during an incoming call, along with standard soft keys.
For example:
SET SOFTKEY_INCOMING_VISUAL "type=function;action=newcall;label=call"ADD SOFTKEY_INCOMING_VISUAL "type=function;action=redirect;attr1=65324;label=divert"
SOFTKEY_OUTGOING
Null
Specifies the custom soft key for the call appearance lines in an Outgoing state. You can provide the soft key attributes and labels, which a phone displays during an outgoing call, along with standard soft keys.
For example:
SET SOFTKEY_OUTGOING "type=function;action=endcall;label=drop"ADD SOFTKEY_OUTGOING "type=function;action=autocbck;label=AutoCbck"
SOFTKEY_DIALING
Null
Specifies the custom soft key for the call appearance lines in an Dialing state. You can provide the soft key attributes and labels, which a phone displays during an outgoing call, along with standard soft keys.
For example:
SET SOFTKEY_DIALING "type=function;action=redial;label=dial"ADD SOFTKEY_DIALING "type=function;action=endcall;label=finish"
SOFTKEY_DIALTONE
Null
Specifies the custom soft key for the call appearance lines in a Dialtone state. You can provide the soft key attributes and labels, which a phone displays during an outgoing call, along with standard soft keys.
For example:
SET SOFTKEY_DIALTONE "type=function;action=redial;label=dial"ADD SOFTKEY_DIALTONE "type=function;action=endcall;label=finish"
SOFTKEY_CONFERENCE_DIALING
Null
Specifies the custom soft key for the call appearance lines in a Conference Dialing state. You can provide the soft key attributes and labels, which a phone displays during an outgoing call, along with standard soft keys.
For example:
SET SOFTKEY_CONFERENCE_DIALING "type=function;action=clear;label=drop"ADD SOFTKEY_CONFERENCE_DIALING "type=function;action=endcall;label=finish"
SOFTKEY_CONFERENCE_OUTGOING
Null
Specifies the custom soft key for the call appearance lines in a Conference Outgoing state. You can provide the soft key attributes and labels, which a phone displays during an outgoing call, along with standard soft keys.
For example:
SET SOFTKEY_CONFERENCE_OUTGOING "type=function;action=cancel;label=drop"ADD SOFTKEY_CONFERENCE_OUTGOING "type=function;action=autocbck;label=AutoCbck"
SOFTKEY_CONFERENCE_CONSULT
Null
Specifies the custom soft key for the call appearance lines in a Conference Consult state. You can provide the soft key attributes and labels, which a phone displays during an outgoing call, along with standard soft keys.
For example:
SET SOFTKEY_CONFERENCE_CONSULT "type=function;action=cancel;label=drop"ADD SOFTKEY_CONFERENCE_CONSULT "type=function;action=endcall;label=finish"
SOFTKEY_CONFERENCE_ACTIVE
Null
Specifies the custom soft key for the call appearance lines in a Conference Active state. You can provide the soft key attributes and labels, which a phone displays during an outgoing call, along with standard soft keys.
For example:
SET SOFTKEY_CONFERENCE_ACTIVE "type=function;action=cancel;label=drop"ADD SOFTKEY_CONFERENCE_ACTIVE "type=function;action=endcall;label=finish"
SOFTKEY_TRANSFER_DIALING
Null
Specifies the custom soft key for the call appearance lines in a Transfer Dialing state. You can provide the soft key attributes and labels, which a phone displays during an outgoing call, along with standard soft keys.
For example:
SET SOFTKEY_TRANSFER_DIALING "type=function;action=clear;label=drop"ADD SOFTKEY_TRANSFER_DIALING "type=function;action=endcall;label=finish"
SOFTKEY_TRANSFER_OUTGOING
Null
Specifies the custom soft key for the call appearance lines in a Transfer Outgoing state. You can provide the soft key attributes and labels, which a phone displays during an outgoing call, along with standard soft keys.
For example:
SET SOFTKEY_TRANSFER_OUTGOING "type=function;action=cancel;label=drop"ADD SOFTKEY_TRANSFER_OUTGOING "type=function;action=autocbck;label=AutoCbck"
SOFTKEY_TRANSFER_CONSULT
Null
Specifies the custom soft key for the call appearance lines in a Transfer Consult state. You can provide the soft key attributes and labels, which a phone displays during an outgoing call, along with standard soft keys.
For example:
SET SOFTKEY_TRANSFER_CONSULT "type=function;action=cancel;label=drop"ADD SOFTKEY_TRANSFER_CONSULT "type=function;action=endcall;label=finish"
SP_DIRSRVRPORT
Sets the TCP port number of the LDAP Directory Server.
The default port number is 389.
SP_DIRTOPDN
Sets the Directory Topmost Distinguished Name.
This value must be set to a non-null value to enable the LDAP application. The default is null, but DIRTOPDN should be set to the LDAP root entry.
SPACES_ACCESS_MODE
Specifies the authentication mode that can be used by the phone when connecting to Avaya Spaces.
The options are:
Connections to Avaya Spaces uses the embedded public certificates and any certificates defined in the TRUSTCERTS. It ignores ENABLE_PUBLIC_CA_CERTS.
Note:
This parameter is not supported on Avaya J129 IP Phone.
SPACES_DIRECT_NUMBER_DEFAULT
You can define a direct number to use when attempting a call to Avaya Spaces. If the user does not select an Avaya Spacesdirect number then this defined direct number is used.
The value is a dialable string, length can be up to 32 characters. Can contain the following: 0 to 9 digits, minus (-), parenthesis (()), comma (,), pound (#), asterisk (*), plus (+).
Note:
This parameter is not supported on Avaya J129 IP Phone.
SPACES_DIRECT_NUMBER_PROVIDE
Specifies if the end user is allowed to select a direct number for a voice call to Avaya Spaces.
The options are:
Note:
WLAN_COUNTRY is used to determine the location of the phone. The phone displays phone numbers based on this location. If you set the parameter WLAN_COUNTRY to a country that does not exist in the list of numbers provided by Avaya Spaces, then the phone number of the US is shown.
This parameter is not supported on Avaya J129 IP Phone.
SPEAKERSTAT
Specifies the operation of the speakerphone.
The options are the following:
Note:
This parameter is not supported on Avaya J129 IP Phone.
SSH_ALLOWED
Specifies if SSH is supported.
The options are the following:
SSH_BANNER_FILE
Specifies the file name or URL for a custom SSH banner file.
If the value is null, english banner is used for SSH.
The value can contain 0 to 255 characters.
SSH_IDLE_TIMEOUT
Specifies the idle time in minutes after which an SSH connection is terminated.
Valid values are 0 through 32767.
A value of 0 means that the connection will not be terminated.
SSO_CUSTOMIZE_LOGIN_START_HELP
Specifies the help text that the phone displays when the user presses the Help soft key from the Single Sign On (SSO) Login screen.
To include line breaks in the text, insert "\n" in the string as required.
The default value is empty. If you do not set any help information, the phone displays the existing help text.
The valid value is a string up to 255 characters.
SSO_CUSTOMIZE_LOGIN_PROGRESS_HELP
Specifies the help text that the phone displays when the user presses the Help soft key from the Single Sign On (SSO) screen with the QR code or the Link.
To include line breaks in the text, insert "\n" in the string as required.
The default value is empty. If you do not set any help information, the phone displays the existing help text.
The valid value is a string up to 255 characters.
SUBSCRIBE_LIST_NON_AVAYA
Specifies comma separated list of event packages to subscribe to after registration.
Possible values are:
,
,
,
. The values are case insensitive.
For IPO the recommended value shall be
,
SUBSCRIBE_SECURITY
Specifies the use of SIP or SIPS for subscriptions.
The options are the following:
For IP office environment, the applicable values are 0 and 1.
SUBSCRIBELIST
Specifies a list of URIs to which the phone will send a subscribe message after the phone successfully registers with a call server, or when a subscribe push request is received with a type attribute all. The message is an HTTP GET for the URI with the phone's MAC address, extension number, IP address and model number appended as query values).
The list can contain up to 255 characters. Values are separated by commas without any intervening spaces.
If the value is set to null, subscribe messages are not sent.
SYMMETRIC_RTP
Specifies if the phone must discard received RTP or SRTP datagrams if their UDP source port number is not the same as the UDP destination port number included in the RTP or SRTP datagrams of that endpoint.
The options are the following:
SYSLOG_ENABLED
Specifies if sending Syslog messages is enabled or not.
The options are the following:
Note:
The phone does not display the Secure call icon, if you set the parameter value to 1.
SYSLOG_LEVEL
Specifies the severity level of syslog messages.
Events with the selected severity level and above will be logged. The lower numeric severity values correspond to higher severity levels.
The options are the following:
SYSTEM_LANGUAGE
Contains the name of the default system language file used in the phone. The file name should be one of the files listed in the LANGUAGES parameter.
If no file name is specified, or if the file name does not match one of the LANGUAGES values, the phone uses the built-in English text strings.
Valid values range from 0 to 32 ASCII characters.
The file name must end in .xml format.
T
TCP_KEEP_ALIVE_INTERVAL
Specifies the number of seconds that the telephone waits before re-transmitting a TCP keep-alive (TCP ACK) message.
Valid values are from 5 through 60.
TCP_KEEP_ALIVE_STATUS
Specifies if the phone sends TCP keep alive messages.
The options are the following:
TCP_KEEP_ALIVE_TIME
Specifies the number of seconds that the telephone waits before sending out a TCP keep-alive (TCP ACK) message.
Valid values are from 10 through 3600
TEAM_BUTTON_REDIRECT_INDICATION
Specifies if the redirection indication must be shown on a team button on the monitored station, if it is not a redirect destination of the monitored station.
The options are the following:
Note:
Avaya J129 IP Phone and Avaya J139 IP Phone do not support this feature.
TEAM_BUTTON_RING_TYPE
Specifies the alerting pattern to use for team buttons.
Valid values are 1 through 8. The default value is 1.
Note:
Avaya J129 IP Phone and Avaya J139 IP Phone do not support Team Button feature.
TEAM_BUTTON_LED_PROFILE
Specifies if the LED state and the Team button icon on the phone screen synchronize when the monitoring station views the status of monitored stations.
Valid values:
If the monitored station is idle, the Team button icon on the monitoring station is Green and the LED is Red.
If the monitored station is busy, the Team button icon on the monitoring station is Red and the LED is Green.
If the monitored station is idle, the Team button icon on the monitoring station and the LED are Green.
If the monitored station is busy, the Team button icon on the monitoring station and the LED are Red.
TEAM_BUTTON_INCOMING_CALL_INDICATION_MODE
Specifies the audible and visual indication mode for the Team button.
This parameter controls how the J100 phone provides audible and visual alerts when there is an incoming call associated with the Team button feature.
When you configure the Force option, you restrict the user from setting the Team button incoming call indication mode from the user interface.
The options are the following:
TIMEFORMAT
Specifies the format for time displayed in the phone.
The TIMEFORMAT parameter is value is applied from the 46xxsettings.txt file on the very first installation, and after resetting parameters to defaults and when 3rd party servers don't backup the settings.
The options are the following:
TIMEZONE
Specifies timezone configuration in Olson name format.
For more information about timezone name format and for a list of time zones, see Time Zone database
The default value is Etc/GMT, which means +00:00.
You can set a time zone value only if you enable the parameter ENABLE_TIMEZONE.
From the software version 4.1.0 and later, Avaya J139 IP Phone, Avaya J159 IP Phone, Avaya J169/J179 IP Phone, and Avaya J189 IP Phone supports the TIMEZONE parameter.
TLS_VERSION
Specifies the TLS version used for all TLS connections.
Note:
PUSH and SLA monitor agent ignores TLS_VERSION value 0 and uses value 1.
The valid values:
0: TLS version 1.0 is the minimum permitted value.
1: TLS version 1.2 is the minimum permitted value.
2: TLS version 1.3 is the minimum permitted value.
TLSDIR
Specifies the path to the configurations and data files in HTTPS GET operations during device bootup. This path is relative to the root of the HTTPS file server, to the directory in which the device configuration and date files are stored. If $MACADDR and/or $MODEL4 and/or $SERIALNO macro is present in the configured path then such macro is replaced with its actual value.
Valid values can contain 0 to 127 ASCII characters, without any spaces.
TLSPORT
Specifies the TCP port used for HTTPS file downloads from non-Avaya servers.
Valid values are from 0 to 65535.
TLSSRVR
Specifies zero or more HTTPS server IP addresses, which is used to download configuration script files. The IP addresses can be specified in dotted-decimal, or DNS name format separated by commas without any intervening spaces. Valid values contain 0 to 255 ASCII characters, including commas. This parameter can also be changed through LLDP.
TLSSRVRID
Specifies how a phone evaluates a certificate trust.
The options are the following:
TPSLIST
Specifies a list of URI authority components (optionally, including scheme and path components) to be trusted.
A URI received in a push request is only used to obtain push content, if it matches one of these values.
The list can contain up to 255 characters.
Values are separated by commas without any intervening spaces.
If the value of TPSLIST is null, push is disabled.
TRUSTCERTS
Specifies a list of names of files that contain copies of CA certificates (in PEM format) that are downloaded, saved in non-volatile memory, and used by the telephone to authenticate received identity certificates.
The list can contain up to 255 characters. ## Values are separated by commas without intervening spaces.
U
UPDATE_DIALED_NUMBER_ON_ANSWER
Specifies whether displayed dialed number is updated or not based the number provided in 200 OK after an answer.
The options are the following:
USBPOWER
Controls USB power when power is provided to the USB interface.
The options are the following:
Note:
This parameter is supported only in Avaya J159 IP Phone and Avaya J189 IP Phone
USE_CONTACT_IN_REFERTO
Specifies which transfer target address should be used in Refer-To a header of REFER SIP request on attended transfer.
The options are the following:
USE_EXCHANGE_CALENDAR
Specifies whether the Calendar synchronizes with the Microsoft Exchange.
The options are the following:
Note:
Avaya J169/J179 IP Phone supports this parameter.
USER_STORE_URI
Specifies the URI path of IP Office for storing user data.
Note:
If the value of this parameter is set to null, then the addition, deletion, and modification of Contacts is disabled.
USE_QUAD_ZEROES_FOR_HOLD
Specifies how Hold will be signaled in SDP.
The options are the following:
UUIDISPLAYTIME
Specifies the duration, in seconds, that the UUI Information screen is be displayed.
Valid values are 5 through 60.
Note:
Avaya J129 IP Phone and Avaya J139 IP Phone do not support this feature.
V
VLANSEP
Specifies whether VLAN separation is enabled by the built-in Ethernet switch while the phone is tagging frames with a non-zero VLAN ID.
When VLAN separation is enabled, only frames with a VLAN ID that is the same to the VLAN ID used by the phone (as well as priority-tagged and untagged frames) is forwarded to the phone.
Also, if the value of PHY2VLAN is non-zero, only frames with a VLAN ID that is the same to the value of PHY2VLAN (as well as priority-tagged and untagged frames) is forwarded to the secondary (PHY2) Ethernet interface. Tagged frames received on the secondary Ethernet interface will have their VLAN ID changed to the value of PHY2VLAN and their priority value changed to the value of PHY2PRIO.
The options are the following:
0: Disabled.
1: Enabled if L2Q, L2QVLAN and PHY2VLAN are set appropriately (default).
Note:
J129 phone does not support this parameter.
VLANSEPMODE
Specifies whether full VLAN separation is be enabled by the built-in Ethernet switch while the telephone is tagging frames with a non-zero VLAN ID. This VLAN separation is enabled when: VLANSEP=1, L2QVLAN and PHY2VLAN have non-zero values, L2Q is auto (0) or (1) tagging.PHY2PRIO is not supported when VLANSEPMODE is 1.
The options are the following:
Note:
This parameter is configured through the settings file.
VLANTEST
Specifies the number of seconds that the phone waits prior to failing back to a different VLAN ID if no response is received from the DHCP server.
Valid values are 0 through 999.
A value of zero means that DHCP tries with a non-zero VLAN ID forever.
Note:
This parameter is configured through:
The settings file
A name equal to value pair in DHCPACK message
VOLUME_UPDATE_DELAY
Specifies the minimum interval, in seconds, between backups of the volume levels to PPM service when the phone is registered to Avaya Aura® Session Manager.
If there is no change to volume levels, there will be no backup to PPM service.
Valid values are 2 through 900. The default value is 2.
W
WAIT_FOR_CALL_OPERATION_RESPONSE
Specifies the time in seconds before providing the user a notification that there is a call operation in progress. This parameter is applicable to all server environments.
Example: User goes off-hook, the phone sends an invite. If there is no response from the proxy for three (default value) seconds, the phone will display the notification.
Valid values range from 0 to 4.
0: the notification is disabled
1 – 4: the number of seconds before the popup display
WAIT_FOR_INVITE_RESPONSE_TIMEOUT
Specifies the maximum number of seconds that the phone waits for another response after receiving a SIP 100 Trying response.
Valid values are 30 through 180.
WAIT_FOR_REGISTRATION_TIMER
Specifies the number of seconds that the phone waits for a response to a REGISTER request.
If no response message is received within this time, registration will be retried based on the value of RECOVERYREGISTERWAIT.
Valid values are 4 through 3600.
WAIT_FOR_UNREGISTRATION_TIMER
Specifies the number of seconds the phone waits before assuming that an un-registration request is complete.
Un-registration includes termination of registration and all active dialogs.
Valid values are 4 through 3600.
WARNING_FILE
Specifies the file name or URL for a custom single-channel WAV file coded in ITU-T G.711 u-law or A-law PCM with 8-bit samples at 8kHz to be used as a call recording warning instead of the built-in English warning.
The value can contain 0 to 255 characters.
WBCSTAT
Specifies whether a wideband codec indication is displayed when a wideband codec is used.
The options are the following:
Note:
Avaya J129 IP Phone does not support this feature.
WEB_ADMIN_PASSWORD
Specifies the password to access the phone through a web browser as an administrator.
The value set from the web server interface has a higher priority than that of the settings file.
If the Web admin password is changed using the web server, then the web admin password set through settings file is not used until either the web admin password is set to default through the phone admin menu or the phone is reset to default.
Valid values are from 8 to 31 alphanumeric characters including upper, lower and special characters.
WEB_HTTP_PORT
Specifies the port on which the Web Server running on the phone will be accessed using HTTP.
Valid values are 0, 80, 1024 to 65535.
WEB_HTTPS_PORT
Specifies the port on which the Web Server running on the phone will be accessed using HTTPS.
Valid values are 443, 1024 to 65535.
WEBSERVER_ON_HTTP
Specifies whether HTTP access to the web server is enabled or disabled.
To access WEB Server using HTTP set ENABLE_WEBSERVER and WEBSERVER_ON_HTTP to 1.
To access WEB Server using HTTPS set ENABLE_WEBSERVER to 1 and use factory installed identity certificate or install the identity certificates using WEB/SCEP/PKCS12 file download.
The options are the following:
0: Web Server is not accessible through HTTP.
1: Web Server is accessible through HTTP.
WLAN_MAX_AUTH_FAIL_RETRIES
Specifies the number of times the phone will retry a secure connection upon receiving (possibly successive) auth failures.
The valid values range from 0 to 4.
WMLEXCEPT
Specifies zero or more IP addresses or domains for which the HTTP or HTTPS proxy server specified by WMLPROXY will not be used.
The values are separated by commas without any intervening spaces.
The value can contain up to 255 characters.
Only Avaya J159 IP Phone, Avaya J169/J179 IP Phone, and Avaya J189 IP Phone support this parameter.
WMLHOME
Specifies the URL of a WML page to be displayed by default in the WML browser and if the Home softkey is selected in the browser.
The URL can be HTTP or HTTPS.
The allowed value contains not more than one URL of up to 255 characters.
Only Avaya J159 IP Phone, Avaya J169/J179 IP Phone, and Avaya J189 IP Phone support this parameter.
Note:
If the value is set to default, the WML browser is disabled.
WMLIDLETIME
Specifies the idle time in minutes after which the web page set as the value of WMLIDLEURI will be displayed.
The allowed value is a positive integer from 1 to 999.
Only Avaya J159 IP Phone, Avaya J169/J179 IP Phone, and Avaya J189 IP Phone support this parameter.
Note:
If WMLIDLEURI is set to null, the web page will not be displayed when the phone is idle.
WMLIDLEURI
Specifies the URL for a WML page to be displayed when the telephone has been idle for the time interval in minutes specified by the WMLIDLETIME parameter.
The URL can be HTTP or HTTPS.
The allowed value contains not more than one URL of up to 255 characters.
Only Avaya J159 IP Phone, Avaya J169/J179 IP Phone, and Avaya J189 IP Phone support this parameter.
WMLPORT
Specifies the TCP port number of the HTTP or HTTPS proxy server set as the WMLPROXY value.
Allowed values are from 0 to 65535.
Only Avaya J159 IP Phone, Avaya J169/J179 IP Phone, and Avaya J189 IP Phone support this parameter.
WMLPROXY
Specifies the IP addresses or domains for which the HTTP or HTTPS proxy server set as the WMLPROXY value will not be used.
The URL can be HTTP or HTTPS.
Allowed values can contain up to 255 characters and must be separated by commas without any intervening spaces.
Only Avaya J159 IP Phone, Avaya J169/J179 IP Phone, and Avaya J189 IP Phone support this parameter.
WMLEXCEPT
Specifies the IP addresses or domains for which the HTTP or HTTPS proxy server set as the WMLPROXY value to be used.
Allowed values can contain up to 255 characters and must be separated by commas without any intervening spaces.