Avaya E129 SIP Deskphone Release 1.25.1.1 Readme
Using the E129 config file
The config file includes configurations to enhance phone behaviors to Avaya Aura
environment. It is recommended to use this file even if the administrator did not make any
changes.
E129 supports only one audio stream with G729 codec
E129 supports only one audio stream using codec G729. Customers that are using solely
G.729 codec need to note that they will not be able to make local conference call managed
by the E129 phone and will need to use Avaya Aura conference server for making such calls.
SRTP configuration
In order to use secured RTP (SRTP) the Aura Communication Manager or the Avaya SBC
(ASBCE) must be configured not to enforce SIPS.
Working in an environment where both RTP and SRTP are used, E129 should be configured
for “SRTP Mode” “Enabled But Not Forced”.
Working in an environment strict to SRTP only the crypto suite on Communication Manager
should not contain the “None” option and E129 should be configured for “SRTP Mode”
“Enabled And Forced”.
The E129 phone does not support the option of AES_CM_128_HMAC_SHA1_32.
Using multiple devices with the same extension
In order to use the E129 as part of multiple devices serving the same extension this
extension should be configured on the Aura System Manager as multiple registration group.
Using E129 keypad lock feature
The keypad lock feature can be used to secure the phone while the user is away. It is
important to note that it is possible to unlock the phone only when it is in idle state.
Presence is not supported
The E129 doesn’t support the presence features and does not publish its presence status.
Do not use this option in the WebUI menus.
Session Manager Firewall – potential for service outage (Applies only to SM
6.3.0/6.3.1)
Starting with Avaya Aura
®
Session Manager 6.3, the SIP firewall function will be enabled by
default. The SIP firewall will be turned on for new installations and for upgrades from
systems where the SIP firewall had not been previously configured. Due to the default
values chosen for firewall rules, SIP endpoint users that engage in more than 10 call related
feature invocations within a 5 minute interval will encounter a brief service outage. Evidence
of this can be seen in the System Manager Alarm logs. Call origination, hold/un-hold,
transfer, conference and park/un-park are some examples of call related feature invocations
that count toward this limit. If you have users that fit this traffic profile, it is recommended
Copyright Avaya 2014 All rights reserved
Issued 7 April 2014 Page 5 of 13
