Another week of work and some problems, to start! :-)
My IVR is almost concluded!
I have an IVR flow, for my company just waiting for to change the CTI Route Point, and GO!
The only bug, wich is not a problem wich I can resolve for now is that I can´t set a ring-back tone when a call from PSTN is redirected. The solution we found is to install CallManager 3.1 who has "Music on Hold".
This I will treat later!
Today I would like to have your expert opinion for the next case:
I want to implement a solution in my IVR, that when our clients digit (ParseInput) their client number they get access to a certain value.
I have created a simple MSAccess database, in the MCS7835, with two fields:
one stores the client number and other stores the desired value.
Also created a DataSource who points to the created database.
In the Application Engine Administration Page I configured the DataSource with the same name created in the MCS7835.
Finaly, in the IVR flow I have a DBRead, DBGet and DBRelease.
In the DBRead I found the problem, wich is:
I see the created DataSource, the database fields, but I am ALLWAYS GETTING 0 LINES when I test the SQL query!!!
The SQL query is properly constructed, and I have put data in the table of the database!
If you look in the AppAdmin web page, go to Engine, Trace Configuration, there are a couple traces you can turn on that have to do with the DB system. If you turn those on, call the IVR application again and go through the steps again, then look at the trace files. That could maybe shed some light on the problem for you.
The error message %MIVR-STEP_DBREAD-3-UNK indicates that you did not provide a database name in the script. Specify a database resource name as you defined in the Database configuration in AppAdmin using the DBReadStep Customizer in the Application Editor.
Congratulations on fixing it. That would certainly make sense that if the data source configuration in the ODBC control panel settings was using the wrong driver, that you would get error messages like that.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.