OK, first, I updated that page with a 2nd script that will run with 3.1(x) and 4.0(x) versions of Unity - if you're not, be sure you save target as and copy it localy, run it and wait for it to finish loading before hitting the button - it can take a second or two to load the ActiveX control for the DOH access. It'll normally ask you if you want to load the ActiveX control (if you have security stuff turned on in IE).
You'll see both a version for 2.x and early 3.0(x) versions as well as 3.1(x) and 4.x versions out here:
http://www.ciscounitytools.com/Script_CallHandlerDump.htm
The problem was sometime in late 3.0(x), early 3.1(x) they changed the security context for logging onto the DOH... you had to use the fancy new "logonselective" instead of the old "logon" routine. It seems to work fine on my 4.0(4) box at home and I'm sure it'll work back through 3.1(x) versions as well.
As for an import/export tool for handlers - this is actually a bit more work than it sounds - I went down that path in 2.x land and it turned out to be a bit of a black hole. Since handlers can reference and are referenced by other objects in the DB, pulling just the handlers out and restoring them onto another system does a bit of violence to the database which is tough to clean up nicely. It's a chunk of work that I intended to add to the Audio Text Manager application but never got around to it - I don't get many requets for it and with resources spread thin, I jump on the biggest fires first...
