After an Avaya Aura® Communication Manager (CM) upgrade, a customer called Avaya support because their SIP telephones were unable to login. Support was able to confirm that the telephones had not…

Question

Options

• AProvide accurate licensing specification.
• BVerify version installed is compatible with existing versions.
• CTest all third-party equipment and software.
• DAccess support.avaya.com to verify customer systems compatibility.

• A
  4% (2)
• B
  85% (39)
• C
  9% (4)
• D
  2% (1)

Explanation

Verifying version compatibility (B) is the omitted step because SIP telephones that haven't been upgraded may rely on an older SIP protocol version or firmware handshake that the newly upgraded CM no longer supports - a classic compatibility mismatch that would prevent registration/login. Licensing (A) affects whether features are available, not whether phones can authenticate after an upgrade mismatch. Third-party equipment testing (C) is relevant to non-Avaya gear, but SIP phones are a core part of the Avaya ecosystem and should be covered under a version compatibility check, not a separate third-party test. Accessing support.avaya.com for compatibility (D) is a method used to perform compatibility verification, not a distinct pre-implementation step - it's the tool, not the step itself.

Memory tip: Think "upgrade one, upgrade all" - any time CM is upgraded, you must verify that every endpoint (including phones) is compatible with the new version before cutting over. If phones weren't upgraded, that's a version mismatch, making B the obvious omission.

No community discussion yet for this question.