Request for Assistance in Storing Caller Information in a Separate Table for Dashboard Integration

[William C290]

Hi ...

We have integrated MSSQL Server with our ACCS environment, and as part of our process, every caller is required to enter their ID for authentication and login to the call center. To build our dashboard, we need to store the caller's information (such as Caller ID, name, and any relevant data) in a separate table within our MSSQL database.
We would like to inquire about the best method to save this caller information into a separate table, ensuring that we can access and display it easily in a DB view for the purpose of our dashboard integration.
Could you please provide guidance on how we can achieve this? Any recommendations on how to configure this within the ACCS system or MSSQL would be greatly appreciated.


Thank you for your support, and I look forward to your response.

 

[Mo. Abdullah]

I face the same issue, but all I know it will be achieved using Orchestration designer scripts. You will need to convert the IVR from Graphical flow to scripts.
i really don't know what these scripts are like or how to be done. still searching.

 

[William C290]

@Mo. Abdullah: Did you need this for Power Pi Integration?

 

[William C290]

@Mo. Abdullah :

To store caller information such as Caller ID, name, and other relevant data in a separate table in your MSSQL database for use in building a dashboard, you can follow these steps:



Step-by-Step Guide

1. Database Table Creation

First, create a new table in your MSSQL database to store the caller information. You can use the following SQL script to create the table:



CREATE TABLE CallerInfo ( CallerID VARCHAR(50) NOT NULL, CallerName VARCHAR(100), CallTime DATETIME, AdditionalData NVARCHAR(MAX), PRIMARY KEY (CallerID)



2. Integration with ACCS

To integrate Avaya Aura® Contact Center (ACCS) with your MSSQL database, you need to ensure that the ACCS system can communicate with the database. This typically involves configuring database connection settings within ACCS.



3. Data Insertion Logic

Implement the logic to insert caller information into the CallerInfo table. This can be done using a stored procedure or directly within your application code. Here is an example of a stored procedure:



CREATE PROCEDURE InsertCallerInfo

@callerID VARCHAR(50),

@CallerName VARCHAR(100),

@CallTime DATETIME,

@AdditionalData NVARCHAR(MAX)

AS

BEGIN

INSERT INTO CallerInfo (CallerID, CallerName, CallTime, AdditionalData)

VALUES (@callerID, @CallerName, @CallTime, @AdditionalData);

END;

4. Application Code

In your application code, call the stored procedure to insert data into the database. Here is an example using C#:





using System;

using System.Data.SqlClient;



public class CallerInfoService

{

private string connectionString = "your_connection_string_here";



public void InsertCallerInfo(string callerID, string callerName, DateTime callTime, string additionalData)

{

using (SqlConnection connection = new SqlConnection(connectionString))

{

SqlCommand command = new SqlCommand("InsertCallerInfo", connection);

command.CommandType = System.Data.CommandType.StoredProcedure;



command.Parameters.AddWithValue("@callerID", callerID);

command.Parameters.AddWithValue("@CallerName", callerName);

command.Parameters.AddWithValue("@CallTime", callTime);

command.Parameters.AddWithValue("@AdditionalData", additionalData);



connection.Open();

command.ExecuteNonQuery();

}

}

}

5. Dashboard Integration

Finally, integrate the data from the CallerInfo table into your dashboard. This can be done using various dashboard tools that support MSSQL, such as Power BI, Tableau, or custom web applications.



Source

This guidance is based on general database integration practices and does not directly reference specific Avaya documentation. If you need Avaya-specific integration details, please refer to the relevant Avaya documentation or contact Avaya support.



This answer is based on general integration practices and may require adjustments based on your specific environment and requirements. If you need detailed Avaya-specific instructions, please consult Avaya documentation or support.