Archive

Archive for the ‘Clients’ Category

gnudialer

January 31, 2007 Leave a comment

At SSG we’ve recently implemented their first outbound call center. It is based on Gnudialer, an asterisk based outbound dialing system. Gnudialer is a little tricky to set up initially, but works very well, and the developers are quite helpful via their irc channel. The trick is to read all the readme files, and read them again.
The system runs on flat mySQL tables, which makes it pretty easy to report on. It also includes a rudimentary crm that does the trick. You can customize the script the agents see, including updatable data from the crm.

The initial trial was successful, and they will be ramping up to 60 agents within the next few months.

Advertisements
Categories: Asterisk, Clients, VoIP

MS SQL Server local file backup problem resolved

June 7, 2006 Leave a comment

I recently ran across a problem twice with backup maintenance plans in Microsoft SQL Server (2000+). The following error started to appear when the file backup job started to run:

… – Message: The job failed. Unable to determine if the owner (DOMAIN\Administrator) of job DB Backup Job for DB Maintenance Plan 'DB Maintenance Plan1' has server access (reason: Could not obtain information about Windows NT group/user 'DOMAIN\Administrator'/ [SQLSTATE 42000] (Error 8198)).

There seemed to be lots of people with the same problem but no solutions offered. Here's the solution that worked for us:

  1. Go to Administrative Tools -> Services. Click on SQLSERVERAGENT and select Properties from the Action menu. Click on the Log On tab. Select Local System Account. Click on the General Tab. Select Startup Type: Automatic and hit OK.
  2. In Enterprise Manager, go to Maintenance, and click on SQL Server Agent. Select Properties from the Action menu. Click on the Connection. Select Use Windows Authentication and hit OK (You may need to stop and restart the SQL Server service at this point).
  3. In Enterprise Manager, click on the name of the local server and select Edit SQL Server Registration properties… Select Use SQL Server Authentication (we used sa), and hit OK
  4. Delete the existing database plan and create a new one.