Once the CPN Substitution feature has been enabled, it will apply to all calls made on the telephone system that are made using a supported method.

Using an Alternate Database

If required, the stored procedure that is called by the CPN Substitution feature can be changed. By changing the stored procedure being called, a custom stored procedure can be written to perform the CPN lookup on a different database if required by the customer.

To change the stored procedure used, the following configuration value must be changed in the ‘_Configuration’ table within the MCS’s database:

• ConfigurationName = ‘Stored_Procedure‘
• ConfigurationArea = 36

The default value for this configuration is ‘_AS_SearchAreaCodeMapping‘.

The stored procedure that this is changed to, needs to have the following parameter structure:

CREATE PROCEDURE [dbo].[_AS_SearchAreaCodeMapping]

(

       @AreaCode as varchar(15),

       @SourceExtension as varchar(15) = '',

       @SourceAgent as varchar(15) = '',

       @CallingPartyNumber as varchar(20) = '' output,

       @CallingPartyName as varchar(100) = '' output

)

The @CallingPartyNumber and @CallingPartyName should be populated with the required values. If either of the values are set to null or blank, the number and name will not be set and the CPN details configured on the telephone system against the extension making the call will be used.

Command Timeout

When using the CPN Substitution feature, a default timeout of 2 seconds is used for any searches of the CPN Substitution table. If a query reaches this timeout it will fail and the calling party name/number configured against the extension will be used. The command timeout can be increased if required by changing the following configuration value in the ‘_Configuration’ table within the MCS’s database:

ConfigurationName = ‘CommandTimeout‘

ConfigurationArea = 36

ConfigurationValue = 2 <- this is the default value, in seconds