That means something that COBRAS is looking for in the contact rules (transfer rules on call handlers/users) is not in Connection for 7.0(2) - but COBRAS is designed to "carry on" in such cases and your export should be fine - the errors there are for the developers to know to run them down - I'll have to install a 7.0(2) system and see what property it's looking for that's not there in that old version that got added along the way...
Ran some tests this morning with the latest Export against 7.0(2) and saw no errors like this - from your log output I suspect you're running an older Export version (i.e. there's no thread information in there which means that's the older single threaded version). You might want to try getting the most recent version off it's home page and trying it if you're concerned about the backup.
If the most recent 8.x line of the COBRAS Export for Connection still throws the same errors then send me the entire log file it creates off list (lindborg at cisco dot com).
ah, I assumed you were talking about Unity Connection 7.0(2) - which is what I tested - COBRAS export for Connection has multiple threading support and the log contains thread notes - the COBRAS Backup for Unity is single threaded - I'll have to spin up a 7.0(2) Unity installation to test that config... regardless, your backup should be ok.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...