We are using OTRS as ticketing system for support requests, and since it is an internal system only, we wanted to give the opportunity to our employees (requesters) to state their ticket's priority. The OTRS client interface allows that, but can't add a CC: address, which is wanted by our users, so we decided to try to develop an Office Add-in that would do the job.
I know that we could have used the built-in prorities (Normal, Low, Important) in Outlook, but we wanted 6 levels. Priorities are important to us because we wanted to have escalation and reports to monitor if the agents are answering and solving tickets in an efficient manner. So we made 6 SLAs and postmaster filters in OTRS, and the form adds text at the bottom of the message (i.e. SLA=1). The filter recognizes this text and sets the appropriate header, so the SLA is present in the ticket when it is created. We also made a GenericAgent job to match the OTRS priority to the SLA of tickets.
Just to let you know that I did a basic test with asterisk on an OpenVZ VE and it works. We only tested SIP connectivity (it would probably be complex to have Zaptel support and I don't really need it). We were able to connect to a VoIP provider using SIP (unlimitel) and music on hold works.
The only thing I had to change to make it work is to comment out this line in /usr/sbin/safe_asterisk:
#TTY=9 # TTY (if you want one) for Asterisk to run on
(I guess there is no TTY9 (console # 9) on openVZ since it is a virtual machine and TTY9 is usually a physical console (monitor)).
I'll soon put my asterisk server in a VE, I'll let you know how it goes. I also use Unlimitel and ATAs to link my PSTN line and cordless phones.
I don't know why but despite all of my searches, I haven't been able to find a good tutorial on how to deploy KeePass with an enforced configuration (set parameters that users cannot change).
First, deployment: You can deploy the .msi and the related files using GPO, for example. But there is an easier way: simply copy the KeePass folder that contains the .exe to a network share. Make sure only admins (only admin accounts, not your regular account). have write access to this share, all other users read-only. To do that you can install KeePass on your computer temporarily an copy the folder that is in the Program Files folder.
Second, configuration enforcement: execute the local version of KeePass that you installed for step one. Set the parameters as you would like them, then close KeePass. A configuration file will be created in C:\Users\$username\AppData\Roaming\KeePass\KeePass.config.xml. You can create a copy of this file that you will name KeePass.config.enforced.xml …