cancel
Showing results for 
Search instead for 
Did you mean: 

Fail to connect Avaya CM7 via SSH/5022 with Prognosis 10.5

Highlighted
PL IR Partner
IR Partner

Fail to connect Avaya CM7 via SSH/5022 with Prognosis 10.5

It found that it is unable to connect Avaya CM7 via SSH at port 5022 with Porgnosis 10.5 patch 6. We use work around to connect via Telnet at port 5023. While both SSH/5022 and Telnet/5023 fail in connect to CM8 since port 5023 is closed and unable to open in CM8. Please advise solution for 10.5 in enabling SSH access.

1 REPLY 1

Re: Fail to connect Avaya CM7 via SSH/5022 with Prognosis 10.5

Hello PL,

 

Avaya changed the codecs used for SSH connections for Avaya Communication Manager 7.x and 8.x. Prognosis 10.5 does not support the new codecs required for the SSH connections to newer Avaya Communication Manager versions.

 

Prognosis 11.6 will need to be used to monitor Avaya Communication Manager 8.x. Prognosis 11.6 also supports SSH connections to Avaya Communication Manager 7.x.

 

Thank you,
Scott Baldwin

 

Webinar: The Journey to Microsoft Teams - Readiness Phase (part 2)

Having looked at the planning phase in session one of this series, we will turn our focus to the readiness phase. The all important technical capabilities assessment, ensuring the network, endpoints and users are adequately prepared for the move.

Hear first hand from IR's Global Head of Information Systems and Technology, Jason Schwendinger, on how he has been tackling these issues.

Join webinar