How does Prognosis (11.5) behaves when the server it's running gets renamed and its IP address ges changed?
Can this cause issues to Prognosis? It's collectors? It's components (PGSQL, RabbitMQ, etc...)?
Here, I'm voluntarily focusing on the Prognosis application and excluding any third party devices or applications like CUCM, Avaya CM, etc... These will obviously have to be reconfigured to send CDRs, RTCP streams, traps, syslogs, etc... to the new server IP.
Solved! Go to Solution.
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 webinar