Login fails after phone upgrade,
when Avaya Session Manager
uses Identity certificate signed by
Avaya SIP Root CA, TLSSRVRID
is 1 in the 46xxsettings.txt
file or in the DHCP SSON Option
43
Cause: TLSSRVRID is enforced on any connection on R7.1.0 and on
connections where SIP Root CA certificate is being used. Identity
certificates signed by Avaya SIP root CA certificate are not unique
and therefore if TLSSRVRID is set to 1 the SIP registration/PPM fails.
Resolution:
• Set TLSSRVRID to 0 if Avaya SIP Root CA is used.
• Replace the identity certificate of the session manager or PPM to a
new one where the SIP domain, defined by SIPDOMAIN, is found in
the Subject Alternative Name and the SIP controller IP address or
host name is found in the common name or Subject Alternative
Name.
Multiple call appearances on
incoming call.
Cause: Provisioning problem.
Resolution: On the off-pbx-telephone station-mapping form, set the
Bridged Calls field to "none".
A blank screensaver appears and
the phone does not immediately
respond to pressing the Phone
button
Cause: The server IP Address in the LOGO parameter is invalid or
unavailable.
Resolution: Correct/change the LOGO parameter in the settings file.
SRTP provisioning
SRTP is now supported (with TLS). To use SRTP, the network region codec set must have media
encryption set up for each region that calls may traverse.
When SRTP is provisioned in Communication Manager, the default cryptosuite used is
‘aescm128-hmac80’. The phone also assumes that no encryption is an option provisioned in
Communication Manager. If Communication Manager is provisioned with the cryptosuite
aescm128-hmac80, then the following entry must be in the 46xxsettings.txt file:
SET MEDIAENCRYPTION "1,9"
If some other encryption set is required, the string must be set appropriately in the 46xxsettings.txt
file.
Troubleshooting
January 2020 Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP 150
Comments on this document? infodev@avaya.com
To Next Page
Loading...
