Related Configuration Options

The following configuration options support the Account Code feature:

accode-data

Default Value: none
Valid Values:
none—T-Server does not map the switch account codes to the call user data.
udata—T-Server attaches reported account codes as user data, using the key defined by the accode-name option. T-Server then sends requests to set account codes to the switch, when such user data keys are used in client requests AttachUserData or UpdateUserData.
ext—T-Server attaches user data as extensions to all call events and does not intercept user data update requests with the reserved keys.
Changes Take Effect: Immediately
Related Feature: Account Codes

Specifies whether T-Server has to map the switch account codes to call user data (value udata), to extensions (value ext) or will not map switch account codes (value none).

Note: T-Server uses the reserved keys sent in any call-related client-request Extensions attribute, regardless of the value of this option. The only exception is when the configuration option is set to udata and the user data in the request contains the account code.

accode-name

Default Value: AccountCode
Valid Values: Any valid key name
Changes Take Effect: Immediately
Related Feature: Account Codes

Specifies the data key name under which T-Server attaches the account code to the call, as either user data or extensions.

accode-privateservice

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately Related Feature: Account Codes

Enables or disables the use of TPrivateService and EventPrivateInfo for handling the Account Code feature.