I guess it could be a bad key but the failure rates on the dongles are in the %0.2 range - a lot of dongles that get sent back as "broken" are fine on testing. The most common issue with the write through capabilities is the parallel port configuration but it sounds like you've hit on that already.
If you're in a jam you can install Unity without the key in demo mode and then add the key on to open the licenses - this works so long as you don't need languages/features not in the demo mode (i.e. a different TTS engine). If it's reading the key OK but just can't write through to it, this will work temproarily (presumably you'll still want to try a new key if you think that's the case).
It's checked every so often but Unity wont shut down on you till midnight I believe - it SHOULD wait 72 hours before shutting down when the key goes missing when you're not started in demo mode but I believe there was a problem with that - as long as you don't leave it out over night you'll be fine.
Also, I assume the production system is the same version (i.e. 2.4.6). If it's a 3.x system, do NOT do this... the version will be written to it during the 2.4.6 update and the key will no longer work on your 3.x system - not good.
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...