Zetafax using Windows TAPI

I have a scenario here at work where long distance calls require a 4 digit code to be entered after the phone number is dialed. Roughly, here’s how it goes:

pick up receiver -> 9,1 2223334444 -> wait for voice prompt -> 5555 (4 digit code)
So when setting up our new Zetafax server, I couldn’t find a way to configure this rule within the software. instead, I had to use Windows TAPI rules with the “calling card” options.
Just for reference, Windows TAPI only supports 255 or 256 prefix numbers per area code rule. Zetafax server, only supports 36. If you enter more than 36, the server configuration tool exits as if it had crashed. I called technical support, and the very rude lady on the phone, confirmed this limit, but lowered the number to 30 supported prefixes. She said the next release of Zetafax server would natively include rules like those in Windows TAPI, and also include an “exclude” list of prefixes, unlike TAPI’s “include” only option.
I really hope this makes sense, I googled this and couldn’t find an answer.
If you need explaining, feel free to send me an email.
-Rick Estrada

Open File – Security Warning

I pushed out an .exe this morning to all desktops, network wide, and received numerous complaints that when users tried to run the .exe, a popup would prompt for comfirmation before allowing it to run. Its title was:

Open File – Security Warning”

Of course, there is a checkbox to keep this prompt from reapearing, but we all know how end users can be…
So the ‘quick fix’ is to create or edit a group policy object and under “User Configuration > Administrative Templates > Windows Components > Attachment Manager”, enable “Inclusion list for low file types” and add .exe with the leading period.
After a gpupdate, the security prompt no longer came up.
-Rick Estrada