Writing some data to IPCC dbs

Unanswered Question
Aug 29th, 2008

Hi,

I want to create and configure Outbound Campaign from my c# application without using ICM Campaign Manager tool. To do that first I looked the awdb adn logger db tables and found the right tables. Then I created the sample campaing on awdb tables by using my program. But I need to reflect that data to loggerdb as well and as I know I cant add data directly to logger db.

Does anyone have any idea how ı can do that?

Mickey

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Loading.
jbayuka Thu, 09/04/2008 - 13:39

The Call Routers are "paired" with the Loggers and can read/write only to their own Logger for configuration and historical data over the Private Network locally. In the event that the failure is caused by the loss of a Private NIC card in the Call Router, and that Call Router is the enabled side, it will not be able to write any historical data to the Logger nor will any configuration changes be able to be made to the Logger database.

MickeyKnox Fri, 09/05/2008 - 00:11

Hi, thanks for the replies. My question is how can I write data with my external c# application to Outbound Option tables on awdb and loggerdb. Regards...

cvenour Fri, 09/05/2008 - 04:54

If your goal is to add records to a campaign, then you are best off having your application create flat files. You can then configure an Import Rule to automatically read from a specific folder (local or over the network). You can then handle these incrementally added contact records as any other contact record.

Regards,

Corey.

MickeyKnox Mon, 09/08/2008 - 01:17

No, actually my goal is to write new campaign user interface to configure OO campaigns..

Regards..

Edward Umansky Mon, 09/08/2008 - 19:55

Writing directly to any of the ICM configuration databases is not supported. The ICM db relies on a number of change keys to keep data consistent across the system. Even if it was supported, correctly adding anything directly to the db would not be trivial. If done wrong you run the risk of corrupting the entire system. I'm afraid you're stuck with the provided user interface, unless Cisco is willing to provide you with their internal API's.

Actions

This Discussion