J129_SIP_1_0_0_0_Beta R4_GA ReadMe_working draft

J129_SIP_1_0_0_0_Beta R4_GA ReadMe_working draft
Avaya IP Phone J100 Series SIP Release 1.0.0.0.43 Readme
Avaya J129 IP Phone and J100 Series SIP 1.0.0.0 Software
This file is the Readme document for the Avaya J100 Series SIP Release 1.0.0.0 software.
This file describes the contents of the December 2016 release software distribution package.
Avaya J100 Series SIP Release 1.0.0.0 software is supported on the J129 IP Phone used
with Avaya Aura® and IP Office™.
The information in this document is accurate as of the issue date and subject to change.
Please refer to the Advisements in this file for important information prior to
deploying this software.
Call Platform Compatibility
The Avaya J129 IP Phone using Avaya IP Phone SIP Release 1.0.0.0 software is supported
with:

Avaya Aura® Platform 6.2 FP4, 7.0.0, and 7.0.1

IP Office™ 10.0 SP2
Feature support in J129 IP Phones with SIP 1.0.0.0 software
Below are the feature highlights for the new J129 IP phone with SIP 1.0.0.0 software:



















One line phone, supports two concurrent calls
3 Context Sensitive Soft Keys
Handsfree speaker and handset
Codec support G.711, G.722, G.726, G.729, Opus
Supports AST-SIP for enhanced features and integration with Avaya Aura®
Recent Call Log (100 entries) / Aura Contact List (250 entries)
Built in volume boost control in Handset for Hearing Impaired
Mute Key with Mute Alerting
Dual 10/100 Mbps Ethernet ports to support co-located PC
Power over Ethernet Class 1
Survivability and failover
TLS 1.2 (SHA2-256) / SRTP / Encrypted SRTCP
Security certificate support (direct download (PKCS12), SCEP, OCSP, certificate
validation during TLS handshake)
HTTP/HTTPS
VLAN
LLDP
802.1X
Advanced diagnostics capability
ASBCE support
Copyright Avaya 2016 All rights reserved
Issued 20 December 2016
Page 1 of 12
Avaya IP Phone J100 Series SIP Release 1.0.0.0.43 Readme
Documentation for J100 Series SIP 1.0.0.0
The following documentation is new for this release:
Using Avaya J129 IP Phone
https://downloads.avaya.com/css/P8/documents/101033160
Avaya J129 IP Phone Quick Reference
http://downloads.avaya.com/css/P8/documents/101033162
Installing and Administering Avaya J129 IP Phone
https://downloads.avaya.com/css/P8/documents/101033171
IP Office™ Platform 10.0 - SIP Telephone Installation Notes
https://downloads.avaya.com/css/P8/documents/101028340
J100 Series SIP 1.0.0.0 (1.0.0.0.43) Package Content
The J100 Series SIP 1.0.0.0 software package (J100-IPT-SIP-R1_0_0_0-120616.zip)
contains all the files necessary to install the J129 IP phone.



FW_S_J129_R1_0_0_0_43.bin – The SIP 1.0.0.0 application binary file.
J100Supgrade.txt – This file is downloaded by the IP phones and instructs the phone
on how to upgrade to this version of software.
Fourteen predefined language files for phone display:















Mlf_J129_BrazilianPortuguese.xml
Mlf_J129_CanadianFrench.xml
Mlf_J129_CastilianSpanish.xml
Mlf_J129_Chinese.xml
Mlf_J129_Dutch.xml
Mlf_J129_English.xml
Mlf_J129_German.xml
Mlf_J129_Hebrew.xml
Mlf_J129_Italian.xml
Mlf_J129_Japanese.xml
Mlf_J129_Korean.xml
Mlf_J129_LatinAmericanSpanish.xml
Mlf_J129_ParisianFrench.xml
Mlf_J129_Russian.xml
Eight extended Korean ring tone files:
 KoreanRT1.xml
 KoreanRT2.xml
 KoreanRT3.xml
 KoreanRT4.xml
 KoreanRT5.xml
 KoreanRT6.xml
 KoreanRT7.xml
 KoreanRT8.xml
Copyright Avaya 2016 All rights reserved
Issued 20 December 2016
Page 2 of 12
Avaya IP Phone J100 Series SIP Release 1.0.0.0.43 Readme



Certificate file: av_prca_pem_2033.txt – Avaya Product Root CA certificate with an
expiration date of 2033
release.xml
A “signatures” subdirectory containing signature files and a certificate file.
System specific parameters should be entered into the 46xxsettings.txt file which is
available for separate download at http://support.avaya.com.
Advisements with J100 Series SIP 1.0.0.0 software
Deploying the J129 with IP Office natively
The J129 is supported with IP Office both natively and in a failover in an Avaya Aura
Centralized Branch configuration. IP phones that are supported with IP Office traditionally
have their configuration files deployed from the IP Office itself. However, with IP Office 10.0
SP2 the configuration file (settings file) must be deployed from a file server (HTTP or
HTTPS). In a future release of IP Office the settings file will be deployed from the IP Office
itself.
Presence
The J129 does not display presence in an Avaya Aura® network. The J129 publishes
presence information for other clients that support viewing presence.
VLAN separation
The J129 supports Full VLAN separation; it does not provide Partial VLAN separation. This is
controlled via a parameter VLANSEPMODE. Avaya recommends that voice and data traffic
be separated by VLANs and that voice traffic has its own VLAN.
SIP_CONTROLLER_LIST
This parameter consolidates SIP controller parameters for IP address, port, and transport
protocol into a single configuration parameter. The parameter setting should be a list of
controller
information
where
the
format
for
each
controller
entry
is
“host:port;transport=xxx” . The host should be specified only by an IP address. The use of
Fully Qualified Doman Names (FQDN) is not supported. This applies to all sources of the
SIP_CONTROLLER_LIST parameter which includes DHCP, LLDP, and the 46xxsettings.txt
file. It is not recommended that the SIP_CONTROLLER_LIST be manually configured on the
phone but if required then the administrator must first go into the Admin menu and change
the Proxy policy from “Auto” to “Manual”.
Copyright Avaya 2016 All rights reserved
Issued 20 December 2016
Page 3 of 12
Avaya IP Phone J100 Series SIP Release 1.0.0.0.43 Readme
Enhanced diagnostics
The J129 offers enhanced diagnostic capabilities such as port mirroring, sending the phone
report to a server and the ability to change the SSH capabilities.
Survivability – Failover support
The J129 offers the same failover support as the 9600 Series with Deskphone SIP software
product line when connected to Avaya Aura with SM, BSM, or IP Office as a backup server.
With the support for connectivity in a native IP Office environment survivability is supported
with two IP Office SIP proxies. In this case SIPREGPROXYPOLICY must be set to Alternate.
Features not supported on the J129 Phone
The following features are not supported by the J129: Exchange integration, WML browser,
Contact Center (CCElite), Contacts (while in IP Office native environment), URI dialing,
Bridge Call Appearance (except MDA), simultaneous display of caller name and number,
redial by list, conference roster list, missed call filtering, displaying presence, Push feature,
shared control with 1XC communicator/ACW, downloadable ringtones, Favorites, Personalize
labels, the following AST features: analog bridge appearance, Audix record, 3 rd party MWI,
auto intercom, autodial buttons, busy indicator, call pick-up, enhanced call forward, calling
party name unblock, dial intercom, directed pick-up, exclusion, extended pick-up, Hunt
group busy, limit call, priority calls, team buttons, whisper page.
Unresolved issues in J100 Series SIP 1.0.0.0 software
The following table includes unresolved issues with this release of software which were
known as of the issue date of this document.
External ID
Internal ID
SIP96X1-19647
SIP96X1-20316
SIP96X1-20758
SIP96X1-20927
SIP96X1-21274
SIP96X1-21275
SIP96X1-21296
Issue Description
User Interface
The Call forward icon is not shown on the phone
when there is a destination is configured for 3rd
party Call forwarding
Server field ID display does not index to the right
after clearing 8 characters
J129-IPO_Primary: Phone is displaying (for 2
second) “Join” soft key after select the “Merge” soft
key
Workaround: Wait for 2 seconds and the Join
Softkey gets disabled.
J129-IPO_Primary:Phone momentarily displays
limited service icon during volume adjustment
Phone always displays "Dial or select Party"
message on locked screen
Phone displays incorrect icon on UI for invalid
number
The LastName field is always displayed when user
inserts a symbol in the FirstName field in Contact
Search screen
Copyright Avaya 2016 All rights reserved
Issued 20 December 2016
Page 4 of 12
Avaya IP Phone J100 Series SIP Release 1.0.0.0.43 Readme
External ID
Internal ID
Issue Description
SIP96X1-22229
Missing softkeys with mixed codec and "Direct IP-IP
Audio Connections" set to "Yes" but "Initial IP-IP
Direct Media" is set to "No".
MATCHTYPE parameter does not work as expected
when adding a new contact after switching from
value=1 to value=2 (match at least 4 rightmost
digit)
Phone re-displays Contacts Detail Screen and reboot
after deleting that contact
Issue only occurs when user is deleting contacts at
a rate of more than 1 per sec
Korean language is not labeled in Korean if phone
language is Hebrew
Occasionally during sequential calls, the BCA icon
will appear and remain after call has ended.
Workaround: Logout and Log back in to clear BCA
Occasionally the phone does not display IP Address
in Admin mode when provisioning.
Workaround: The correct IP is visible via the
"Network Information" screen
Feature Invocation
Redial works even when both CAs are busy.
Phone does not allow contacts to be added as speed
dial entries until PPM update is complete
Phone fails to control local conference after
attempting to add another participant while failed
over to AudiCodes with OPUS.
Phone does not enable call-park feature when the
feature is activated from another MDA user
Not able to make a second call in a particular
scenario with automatic dialing configured
Workarounds:
1) Press the Ignore softkey instead of pressing the
phone button
2) Navigate to the Status Screen or to the User Menu
and make an outgoing call from there.
Phone displays is inconsistent while in the Configure
provisioning server screen.
Workaround: Currently the only valid user input
when the "provisioning server invitation" dialogue
box is shown is:
1) press of the softkey
2) press of the OK nav key (same as pressing the
leftmost softkey)
3) pressing the BACK hardkey (same as Cancel)
Bridge on function does not work with E164 MDA
extension phone
SIP96X1-22231
MIB browser displays value of “endptLANGINUSE”
incorrectly
SIP96X1-21586
SIP96X1-21744
SIP96X1-21774
SIP96X1-21775
SIP96X1-22081
SIP96X1-21855
SIP96X1-22629
SIP96X1-20961
SIP96X1-21314
SIP96X1-20771
SIP96X1-20779
SIP96X1-21277
SIP96X1-21611
SIP96X1-21896
SIP96X1-21982
Copyright Avaya 2016 All rights reserved
Issued 20 December 2016
Page 5 of 12
Avaya IP Phone J100 Series SIP Release 1.0.0.0.43 Readme
External ID
Internal ID
Issue Description
Security / Authentication
Phone does not display SCEP notifications while it is
SIP96X1-20372
downloading identity certificate from CA server
Phone does not display 802.1X Authentication failed
screen after receiving EAP-Failure frame from switch
Phone does not send EAPOL Start when setting
DOT1XSTAT to 2 and DOT1XEAP to TLS in
SIP96X1-21210
46xxsetting file. Phone displays “Authentication
SIP96X1-21081
failed.” and pauses after receiving 46xxsettings.txt
file.
Not able to view the identify certificate through the
SIP96X1-21285
MIB browser
The PC cannot access network when Supplicant is
disable and Pass-thru mode is On
Workaround:
SIP96X1-21285
If using 802.1X to authenticate to the network it
must be done by the J129 phone; it cannot be done
via the PC connected to the phone’s PC port.
Phone
will
not
lock
automatically
if
the
PHONE_LOCK_IDLETIME expires before the phone
SIP96X1-22255
has completed an automatic login
Workaround:
PHONE_LOCK_IDLETIME > 5 min.
User does not receive forced log out message while
SIP96X1-22458
the phone they are registered to is in a locked state
and the user is active in the Admin Menu
Survivability
J129-IPO_Primary: After FO-FB while on an active call, user
is not able to make a new call when placing the first call on
hold.
SIP96X1-21082
Workaround: End the existing call which was there when
the primary server became inactive and active again to make
new call.
Networking / Registration
SIP96X1-21088
SIP96X1-20743
Phone reboots a second time after the user
comments out the proxy address in settings file.
SIP96X1-21794
DHCPLEASERENEW displays as 0 in the MIB
SIP96X1-22009
SIP96X1-22301
The PC cannot access network when Supplicant is
disable and Pass-thru mode is On
Workaround: If using 802.1X to authenticate to the
network it must be done by the J129 phone; it
cannot be done via the PC connected to the phone’s
PC port.
Phone gets stuck on “Waiting for DHCP” screen after
factory reset when configured with invalid VLAN ID
and L2Q=1
Note: L2Q=0 (Autodiscovery) is the recommended
VLAN configuration
Copyright Avaya 2016 All rights reserved
Issued 20 December 2016
Page 6 of 12
Avaya IP Phone J100 Series SIP Release 1.0.0.0.43 Readme
External ID
Internal ID
IPOFFICE-115025
Issue Description
J129 cannot be configured with Hebrew language in
IPO_Primary mode.
Workaround: The settings file J100settings.txt
needs to be edited to "Mlf_J129_Hebrew.xml"
instead of "Mlf_J129_Mlf_J129_Hebrew.xml".
Appendix 1 – Supported Hardware
J100 Series SIP 1.0.0.0 software is supported on the following models of IP phones.
Comcode
700512392
Short
Description
J129
Model
Note
J129D01A
Ships with SIP 1.0.0.0 software.
Appendix 2 – Release History
The J100 Series SIP 1.0.0.0 is the first release of software for this product line.
Appendix 3 – New 46xxsettings.txt parameter
The following settings file parameters are new and updated from the 9600 Series with
Deskphone SIP software 7.0.1 software.
Parameter name
Default
value
Description
Source
CONTACT_NAME_FORMAT
0
Specifies how contact names are
displayed
0 - "Last Name, First Name" (Default)
1 - "First Name Last Name"
TLS_VERSION
0
0 - TLS v1.0 and up are permitted
1 - TLS v1.2 and up are permitted
Settings
file
ENCRYPT_SRTCP
0
0 - SRTCP is not supported
1 - SRTCP is supported
Settings
file
Contains one URL which specifies the
location where a PKCS #12 file can be
found for download.
Settings
file,
DHCP
PKCS12URL
““
Settings
file
Copyright Avaya 2016 All rights reserved
Issued 20 December 2016
Page 7 of 12
Avaya IP Phone J100 Series SIP Release 1.0.0.0.43 Readme
Parameter name
Default
value
Description
Source
PKCS12_PASSWD_RETRY
3
Number of PKCS#12 password retries
allowed
Integer 0~100
Settings
file,
DHCP
DELETE_MY_CERT
0
DELETE_MY_CERT must be defined to
allow the identity certificate to be
deleted
Settings
file
Settings
file
““
If TLS is used and server addresses are
defined with an IP address and the
server certificate contains only the
FQDN (typically in a remote worker
environment in the Internet) then a
static mapping of FQDNs to IP
addresses must be provided to the
phone for the purpose of validating an
FQDN identity found in a server
certificate.
A comma separated list of name/value
pairs where the name is an FQDN and
the value is an IP address.
Settings
file
24
Specifies the time interval in hours at
which the phone will periodically
recheck the expiration and revocation
status of the certificates that were used
to establish any existing TLS
connections. 0 – Periodic checking is
disabled. Range: 0-32767
Settings
file
““
Contains one or more trusted certificate
files in a comma separated list. Spaces
are not permitted in this parameter (in
filename or surrounding the comma
separators).
1
Specifies whether a nonce will be
included in OCSP requests and expected
in OCSP responses.
0 - Nonce is not added to OCSP request
1 - Nonce is added to OCSP request
Settings
file,
DHCP
Settings
file
0
Specifies whether OCSP will be used to
check revocation status of certificates.
Valid values include: 0 – disabled,
certificate revocation checking is not
performed. 1 – Enabled, certificate
revocation checking is performed.
FQDN_IP_MAP
SERVER_CERT_RECHECK
_HOURS
OCSP_TRUSTCERTS
OCSP_NONCE
OCSP_ENABLED
Copyright Avaya 2016 All rights reserved
Issued 20 December 2016
Page 8 of 12
Avaya IP Phone J100 Series SIP Release 1.0.0.0.43 Readme
Parameter name
OCSP_ACCEPT_UNK
OCSP_URI
OCSP_URI_PREF
OCSP_TRUSTCERTS
OCSP_HASH_ALGORITHM
OCSP_USE_CACHE
OCSP_CACHE_EXPIRY
Default
value
Description
Source
specifies whether the server certificate
can be accepted if the result of the
revocation check is indeterminate due
to missing revocation information
Settings
file
Specifies the locally configured URI of
an OCSP responder. Only one URI is
permitted and it can contain an IP
address or FQDN
Settings
file
Settings
file
1
Specifies the preferred URI to use for
OCSP requests if it is available from
more than one source. Valid values
include: 1 – Use of the OCSP_URI first
and then the OCSP field of the Authority
Information Access (AIA) extension of
the certificate being checked. 2 – Use of
OCSP field of the Authority Information
Access (AIA) extension of the certificate
being checked first and then OCSP_URI.
“ “
Specifies list of OCSP trusted
certificates which are used as OCSP
signing authority for the certificate that
its revocation status is being checked.
Settings
file
0
Specifies the hashing algorithm for
OCSP request.
0 - SHA-1 (default)
1 - SHA-256
Settings
file
0
Specifies if OCSP caching is used.
0 - Do not to use OCSP caching. Always
check with OCSP responder (default)
1 - Use OCSP cache caching.
Settings
file
2880
Specifies the cache expiry in minutes.
Valid values: 60 to 10080 (60 min to 7
days) with default 2880 (2 days)
Settings
file
1
““
0 - not to accept the certificate if
revocation status checking result is
indeterminate; 1 - accept the
certificate if revocation status
checking result is indeterminate.
Copyright Avaya 2016 All rights reserved
Issued 20 December 2016
Page 9 of 12
Avaya IP Phone J100 Series SIP Release 1.0.0.0.43 Readme
Parameter name
ADMIN_PASSWORD
ADMIN_LOGIN_ATTEMPT
_ALLOWED
SNTP_SYNC_INTERVAL
BRURI
ENABLE_IPOFFICE
Description
Source
Settings
file
PROCPS
WD
Password for device configuration
should consist of between 10 and 16
digits with alphanumeric including
Upper, lower and special character, and
at least 3 combinations of below shall
be used.
(1) Numeric (0-9)
(2) Alphabet Upper case (A-Z)
(3) Alphabet Lower case (a-z)
(4) Special character: ~!@#$%^&*_+=`|\(){}[]:;"'<>,.?/
Limits the number of incorrect
attempts...
Settings
file
10 mins
5 mins to 24 hours (in minutes)
Settings
file
0
0 – Does not display the version
1 – Displays the SSL version
Settings
file
Settings
file
1440
Specifies the time interval in minutes at
which the phone will attempt to
synchronize its time with configured
NTP servers.
Range: 60-2880
Settings
file
““
The J129 provides the capability to
send a phone report to a server
(with the URI of the server defined
by the BRURI parameter). In order
to send the report the administrator
must access the phone’s Admin
menu and select the send report
feature.
ENABLE_IPOFFICE indicates if the
J129 SIP phones are configured to
connect with an IP Office as their
primary SIP Sever. Values:
• 0 – not an IPO environment
(Default)
• 1 – IPO environment
It is preferable to set
DISCOVER_AVAYA_ENVIRONMENT
parameter to 0 when the phone is
set up in IP Office environment
Settings
file
10
ADMIN_LOGIN_LOCKED_TIME
DISPLAY_SSL_VERSION
Default
value
0
Copyright Avaya 2016 All rights reserved
Issued 20 December 2016
Page 10 of 12
Avaya IP Phone J100 Series SIP Release 1.0.0.0.43 Readme
Parameter name
ENABLE_OPUS
OPUS_PAYLOAD_TYPE
HANDSET_PROFILE_DEFAULT
HANDSET_PROFILE_NAMES
Default
value
Description
Source
Settings
file
1
Enable or disable OPUS codec
capability of phone. The parameter
is set by an administrator in the
settings file:
0: Disabled.
1:ENABLE_OPUS_WIDEBAND_18K
2:ENABLE_OPUS_NARROWBAND_16
K
3:ENABLE_OPUS_NARROWBAND_12
K
Settings
file
116
Specifies the RTP payload type to be
used for the OPUS codec.
Valid values are 96 through 127;
the default value is 116.
This parameter is used when media
offer is sent to the far end in an
INVITE (or 200 OK when INVITE
with no SDP is received).
Specifies the number of the default
handset audio profile.
Valid values are 1 through 20; the
default value is 1.
Settings
file
Specifies an ordered list of names to
be displayed for handset audio
profile selection.
The list can contain 0 to 255 UTF-8
characters; the default value is null
("").
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 may contain spaces, but if
any do, the entire list must be
quoted.
There is no way to prevent a profile
from being displayed.
Settings
file
1
““
Copyright Avaya 2016 All rights reserved
Issued 20 December 2016
Page 11 of 12
Avaya IP Phone J100 Series SIP Release 1.0.0.0.43 Readme
License Agreements
License agreements are available at https://support.avaya.com/Copyright. Please select J100 Series
IP Phone
2016 Avaya Inc. All Rights Reserved.
Notice
While reasonable efforts were made to ensure that the information in this document was
complete and accurate at the time of printing, Avaya Inc. can assume no liability for any
errors. Changes and corrections to the information in this document may be incorporated in
future releases.
Documentation disclaimer.
Avaya Inc. is not responsible for any modifications, additions, or deletions to the original
published version of this documentation unless such modifications, additions, or deletions
were performed by Avaya.
Link disclaimer
Avaya Inc. is not responsible for the contents or reliability of any linked Web site referenced
elsewhere within this Documentation, and Avaya does not necessarily endorse the products,
services, or information described or offered within them. We cannot guarantee that these
links will work all of the time and we have no control over the availability of the linked
pages.
Copyright Avaya 2016 All rights reserved
Issued 20 December 2016
Page 12 of 12
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising