System is 1500 R9.1.5 VMPro, IP and Dig phones, SIP Trunks, 150+ stations, Xima Chronicall w/ Recording.
Has anyone seen this (below) alarm before? System appears to be running fine.
IVRConfig::GetRecord: Possible Bad PBX Configuration - record len=16094, stream(02F8F9E0 len=2045), Ignoring 4 bytes - abort loading!
Alarm came after reboot. We did have issue with VMPro password not matching up with password in security settings about 2 weeks ago (post reboot)....not sure if it is related to this but worth mentioning now.
This is a very large IPO with many changes made weekly for years now. I am concerned that config file may be getting corrupted. I'd hate to have to rebuild this complex config from scratch. I plan or exporting config to a CSR file for safe measure.
Is there any other measure we can take in case config file is truly corrupted?
Has anyone seen this (below) alarm before? System appears to be running fine.
IVRConfig::GetRecord: Possible Bad PBX Configuration - record len=16094, stream(02F8F9E0 len=2045), Ignoring 4 bytes - abort loading!
Alarm came after reboot. We did have issue with VMPro password not matching up with password in security settings about 2 weeks ago (post reboot)....not sure if it is related to this but worth mentioning now.
This is a very large IPO with many changes made weekly for years now. I am concerned that config file may be getting corrupted. I'd hate to have to rebuild this complex config from scratch. I plan or exporting config to a CSR file for safe measure.
Is there any other measure we can take in case config file is truly corrupted?
