We'll be doing a COBRAS import soon from Unity 4.0.5 (with Exchange backend) to Connection 7.1.5. We have tied the new call managers (also version 7.1.5) and Connection servers via AXL, so all users can be imprted from CUCM into CUC. The end-users in CUCM are local (no ldap integration). All userID's in the call manager are based on the user extensions, while their mailbox aliases in Unity 4.0.5 are based on AD account names (FirstName+LastName). We have done an alias remap using the COBRAS Data viewer so that all the records that will be imported into Connection via COBRAS will have the same aliases as their corresponding user's UserID on the call manager.
So here is the question: Should we first import all the users into Connection from the Call Manager using the AXL connection and then do the COBRAS import (which would update all the mailbox properties and copy the messages over)? Or should we just do a COBRAS import and not do the AXL import at all? If we do the latter, when we're all set and done, will the users on Connection be in sync with the users on the call manager? This is the key for this whole process. When we're done, we don't want to see any users sitting in the "Import Users" area of the Connection server waiting to be imported.
A follow up question regarding this. We did an import to one of our smaller Unity servers (about 100 users) and everything seems fine. The only thing we have noticed so far is that the old messages that were copied over are being marked as "secure" (I thought that's what I heard). I had a test mailbox with 2 messages (1 read, and 1 new). After the import, I accessed that mailbox and listened to the new message and saved it. I then went back and listed to the 2 saved messages, and both of them were marked as secure. I then left a new message and listend to it and saved it, but this new message didn't indicate the same status (didn't hear the same recording about the message being secure).
Any ideas? Is this normal? The import process went OK without any errors (just 3 warning that were un-related).
That's actually due to a bug in the Connection header parsing logic that was fixed in the 8.x line - if the "IsSecure" flag appears it always marks the message as secure even if the value is "0" (meaning non secure).
An updated COBRAS import was put out the end of last week for a site that ran into the same issue on 7.1(3) - I have it on the temp page of the site, I'll be posting it to the main page later this week but it has been tested:
it's version 1.1.155. Give it a try on a test user and the messages should be not marked secure now (this version removes that header flag entirely if the message is not secure rather than marking it "0").
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...