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.
Solved! Go to Solution.
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
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
Unified Communications has always been an important part of companies' digital transformation efforts due to its ability to enable rich virtual collaboration and communication. But with COVID-19, we've reached a break-through point.
Join Bill Haskins, Sr. Analyst & Partner, Unified Communications at Wainhouse Research, and John Ruthven, CEO at IR discuss UC challenges companies are experiencing due to the COVOID-19 crisis.
Join webinarMembers | Likes |
---|---|
23 | |
23 | |
14 | |
10 | |
8 |