one-X Communicator (SIP) isn't getting buttons and sees no PPM in Session Manager

Description:
one-X Communicator isn't getting buttons and sees no PPM in Session Manager
 

Related Articles:

See the Avaya Mentor video:
https://support.avaya.com/public/index?page=content&id=VIDEO101212&actp=LIST
Avaya Mentor - How to export SSL Certificates from Avaya Aura System Manager for SIP endpoints on a Windows PC

Problem Clarification:

one-X Communicator isn't getting buttons and sees no PPM in Session Manager.  There may also be a delay while attempting to dial numbers.

Cause:

one-X Communicator file InstallConfig.xml needs to be modified.

Solution:

Create certificates:

In System Manager:
Services --> Inventory > Manage Elements: Search for "Type" "Session Manager"
Click on "More Actions" "Manage Trusted Certificates"
Scroll down until you see "Used for validating TLS client identity certificates" and "SECURITY_MODULE_SIP". Click the box corresponding to that line, and click "Export".
Next, on the main menu, click on "Services" --> "Security" "Authority" --> "CA Structure & CRLs" --> Download PEM file.

On the PC:
In Downloads (File Explorer), you should see default.cacert.pem and trust-cert.pem. Copy them to a convenient location, such as the Desktop.
Change the .pem extension on each file to .CRT

Install both of these files into the Trusted Root Store:

For each file, Right-click "Install Certificate".  Install them in the "Local Machine" (Certificate Store): "Place all certificates in the following store".
Click "Browse..." Select "Trusted Root Certification Authorities". Click "Install Certificate..." and "OK"

Disable hostname validation for one-X Communicator Only (This is done if you are installing certain certificates that are not trusted by a third-party vendor):

On the PC, go to C:\Program Files (x86)\Avaya\Avaya one-X Communicator.  Right-click on "InstallConfig.xml" (.xml may not be visible).  Edit with a flat-file editor such as Notepad or Notepad++.

Add the following line above the last line (</InstallConfig>):
<EnableHostnameValidation>false</EnableHostnameValidation>
Save the file.

Manufacturer Release notes:

Disclaimer: intlx Solutions Knowledge Base

The information contained in this knowledge base ("Content") is provided for informational purposes only and is intended to be a general resource. intlx Solutions does not guarantee the accuracy, completeness, or timeliness of the Content.

Use at Your Own Risk: By accessing and using the Content, you agree that you do so at your own risk. intlx Solutions assumes no responsibility for any errors or omissions in the Content, nor for any damages or losses you may suffer arising out of or related to the use of the Content.

Current Customers: If you are a current intlx Solutions customer and have questions or require further clarification on any information presented here, please do not hesitate to contact our support team directly. They are available to assist you and ensure you have the most up-to-date information specific to your needs.

Not a Customer? If you are not currently an intlx Solutions customer but are interested in learning more about our solutions and how we can help your business, please click here. We look forward to the opportunity to discuss your needs and explore how a partnership with intlx Solutions can benefit you.

Thank you for your understanding.

This article contains data that is aimed at helping fix an issue with a product. Please use this information at your own risk as intlx Solutions is not responsible for actions taken by the steps or procedures shown in these articles.