Jump to: navigation, search

warning-level

Section: routing-point-presence
Default Value: 5
Valid Values: An integer or a double value.
Changes Take Effect: When the application is started or restarted.


The value at which a statistic is considered to be at the warning level.

statistic-text

Section: routing-point-presence
Default Value: interaction(s) waiting.
Valid Values: A string containing a valid time or number format according to Windows rules number format (https://msdn.microsoft.com/en-us/library/8kb3ddd4(v=vs.110).aspx). For example: "interaction(s) Q4001 {0:HH:mm:ss} average waiting time" or "interaction(s) Q4001 {0}% abandoned".
Changes Take Effect: When the application is started or restarted.
Modified: 8.5.109.25

Specifies the formatting to be used to display the Stat Server metric used for the presence of the displayed object. If no valid format is found in the option, the display format of the Stat Server metric is set automatically to TimeFormat if a time metric is recognized, or Percentage if a percentage is recognized. If a number metric is recognized or if the type of metric is not recognized, then a raw number format is used.

statistic-name

Section: routing-point-presence
Default Value: CurrNumberWaitingCalls
Valid Values: A valid name of a statistic server statistic queue.
Changes Take Effect: When the application is started or restarted.


The name of the statistic used to evaluate the presence for Routing Points.

object-ids

Section: routing-point-presence
Default Value: No default value
Valid Values: A comma separated list of DN identifiers that represent Routing Point objects
Changes Take Effect: When the application is started or restarted


A comma separated list of DN identifiers that represent Routing Point objects presented in Team Communicator for which this presence metric is applicable.

Object identifier format is: <DN Number>@<Switch Name> This key is optional. If it is absent from the section, the presence metric applies to all Routing Point objects that don't have explicit presence metric assignment.

error-level

Section: routing-point-presence
Default Value: 10
Valid Values: An integer or a double value.
Changes Take Effect: When the application is started or restarted.


The value at which a statistic is considered to be at the upper threshold level.

associated-statistic-type

Section: routing-point-presence
Default Value: No default value
Valid Values: A valid stat server statistic type
Changes Take Effect: When the application is started or restarted


Specifies the statistic type (from Stat Server reference) that is requested to display the presence metric when this metric is not calculated directly on the object displayed in Team Communicator, but on the objects referenced in option associated-object-ids.

This option is applicable only if associated-object-ids is also set.

associated-object-ids

Section: routing-point-presence
Default Value: No default value
Valid Values: A comma separated list of object identifiers
Changes Take Effect: When the application is started or restarted


A comma separated list of object identifiers that represent the objects that store the statistic requested from Stat Server that is displayed as the "presence metric" of the object displayed in Team Communicator.

The type of those objects must match the type specified by the value of the associated-statistic-type option.

If multiple values are specified by the value of the object-ids option, this option must contain the same number to associate the first object of object-ids with the first object of associated-statistic-type, the second object of the object-ids with the second object of associated-statistic-type and so on.

This option is applicable only if associated-statistic-type is also set.

Section routing-point-presence

Tip
For the most up to date Workspace Desktop Edition configuration options, see the Genesys Configuration Option Database.

The routing point presence options enable agents to view routing point statistics information in Team Communicator. Refer to the Enabling Team Communicator Calling Features and Enabling the E-Mail Channel for information about how to use these options.

This page was last edited on February 21, 2020, at 17:25.
Comments or questions about this documentation? Contact us for support!