i've noticed that when replicating, the subscriber information gets replicated immediately pretty much but the recordings do not. they take quite a few minutes before they're synch'ed over to the secondary server.
try to check a short time later for the recordings.
Remember that 4.0.5, there a lot of problems with Failover.. you must make sure you are all the current patches for Unity with this version. SP and a few other patches seem to stablize 4.0.5. Out of the box, 4.0.5 runs fine, but if you want to run failover, you must install the patches.
You can try and look into the SQL replication process if you are good at SQL. You may see SQL login errors, or just plain and simple, Failover is not configured correctly.
Another good test I have found is that, yes the greetings are not replicating over, but if you try and configure for instance Caller Input settings on a greeting, these do not replicate also, which throws the red flag up, SQL is not running correctly or replcating to it's partner.
If your licensing is not replicating either, then you can pretty much just uninstall Failover and reinstall it again and try it from scratch. (failover wizard). I have battle 4.0.5 many times and always loose. I end up calling TAC and they battle for a couple hours also.
Another good one to check is your NIC cards they are running as Fault Talerent and not load balancing. This will throw SQL replication off as well. Try it using 1 NIC card in each server and see this fixes it. (quick test)
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: email@example.com 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 ...