Jump to: navigation, search

Related Configuration Options

The following configuration options define what additional calls to or from an agent are classified as business calls:

bsns-call-dev-types

Default Value: +acdq +rp +rpq +xrp
Valid Values: Multiple flags can be specified using a space, comma or semicolon separated list:

  • +/-acdq—Turns on/off classification of call as business on ACD Queue
  • +/-rp—Turns on/off classification of call as business on Routing Point
  • +/-rpq—Turns on/off classification of call as business on Routing Queue
  • +/-xrp—Turns on/off classification of call as business on External Routing Point

Changes Take Effect: Immediately
Related Feature: Business-Call Handling

Specifies whether calls passing corresponding types of technical device are ignored for automatic call type promotion to business call type. This option does not affect application of DN Annex tab options or application of request extensions.

inbound-bsns-calls

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
Related Feature: Business-Call Handling

Specifies whether T-Server should consider all established inbound calls on an emulated agent as business calls.

inherit-bsns-type

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
Related Feature: Business-Call Handling

Determines whether a consult call that is made from a business primary call should inherit the business call attribute.

internal-bsns-calls

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
Related Feature: Business-Call Handling

Determines whether T-Server considers internal calls made from or to any agent as business calls.

outbound-bsns-calls

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
Related Feature: Business-Call Handling

Specifies whether T-Server should consider all established outbound calls on a emulated agent as business calls after being established.

This page was last edited on May 10, 2013, at 17:20.
Comments or questions about this documentation? Contact us for support!