Another issue that has been seen over the past week is failures with the following information in the PDF report Session Details section:
Connection attempt 1 failed for: <SEID> 0 -- com.avaya.jconnect.applicationapi.ConnectionFailed Exception
Connection attempt 2 failed for: <SEID> 0 -- com.avaya.jconnect.applicationapi.ConnectionFailed Exception
Connection attempt 3 failed for: <SEID> 0 -- com.avaya.jconnect.applicationapi.ConnectionFailed Exception
Failed all connections attempts for <SEID>
Where SEID = (xxx)xxx-xxxx - your device's solution element identifier.
In reviewing the PIE/SAL polling data for the SEID's Asset, one of the causes of this is that the Avaya Product Connect system cannot reach the device through the SAL gateway (or modem bank). For SAL, it is worthwhile checking your
Managed Elements list in your SAL Gateway and ensure it has all the information that was used to provision the products via the GRT tool.
For information on how to provision the products in the Managed Elements list in SAL, see the
SAL Gateway Implementation Guide (Pages 69-75 - Managed Element Configuration)
Thanks,
Roberto