Routing Query

The routing query is implemented via an IVR object with the following properties.

Function

The functionality of the object is as follows:

• The system uses the settings of the routing application to determine whether it is a test call.
  
  • For test calls, the test data source is used for the query. For production calls, the production data source is used.
    Note: A test call in the IVR is initiated with the setting "Test call number" in the master data of the routing application.
• The object implementation then calls the function EXEC pkg_rtma.set_mandant(x) to determine the client with the tenant ID set in the object.
• Finally, the specified query is executed. The query can contain any variables, for example $caller.

Requirements

Installed and configured Oracle Instant Client on the jtel server, for production (minimum) and test database (optional) See also Oracle ODBC Driver.

System parameters

The following system parameters influence the operation of the object:

DSN=nexus_prod;UID=prod_user;PWD=topsecret

DSN=nexus_prod;UID=prod_user;PWD=topsecret

Parameters

SELECT COUNT(*) AS RecordCount, MIN(pers.pers_kz_vip) AS isVIP 
FROM person pers, pat_kontakt kont 
WHERE pers.piz = kont.kont_piz AND kont_nummer = '$caller';

Variables

All fields returned from the query are stored in variables. Only the first record is saved if multiple hits are returned.

From the example above, the following variables are declared:

• nexus.RECORDCOUNT
• nexus.ISVIP

Note: Oracle always returns field names in uppercase via ODBC. The variables are accordingly created with capital letters, regardless of how they are written in the query itself.

Object outputs