What syntax is correct for Filters section in Statserver?

Hello All,

I am trying to see Reason code in CCPulse.

Agent using GAD 7.6 with SIP server.

What syntax is correct for Filters section in Statserver?

  1. Lunch=PairExists (“ReasonCode”,"Lunch”)

  2. Lunch=PairExist (“Not ReadyReasonCode”, “Lunch”)

  3. Lunch=PairExists (“ReasonCode”,“39”)

  4. Lunch=PairExist (“ReasonCode”,“Lunch”)

  5. Lunch=PairExists (“ReasonCode”, 39)

Thanks

You can check that on TServer logs for a correct handling of your scenario

1 Like

(Never met anyone called CCPulse before… I wonder if that is a Forename or a Surname… :slight_smile: )

You need to determine if you are attaching a KVP or using the in-built Options you have developed for GAD. The following are correct, for the correct setting/attached data types;

Using attached data (KVP):

Lunch=PairExist (“ReasonCode”,“Lunch”)

Using a GAD NotReady Code:

Lunch=(Reason = “Lunch”)

As cavagnaro says - check your TServer logs and see if you have either of the above, as the correct handling for you…

Tony

Hi,

The best approach would be checking logs of TServer as suggested by Cavagnaro and Tony.

Support of reason codes in GDesktop is a bit strange when it comes to attaching reason code to a call. There are two modes available that determine the way how reason codes are attached:

  • default mode - let’s have Action Code “Lunch” with code “1” defined in CME. Following key is attached to a call

    message RequestAgentNotReady
    AttributeAgentWorkMode 0 (Unknown)
    AttributeExtensions [2] 00 00..
    AttributeThisQueue ‘…’
    AttributeReferenceID 13325
    AttributeReason [12] 00 01 00 00..
    ‘Lunch’ ‘1’
    AttributeThisDN ‘…’

  • advanced mode - should support “standard” way of attaching reason code (key “ReasonCode”, value is a number) but that configuration isn’t supported on all switches

See “GDesktop 7.6 Deployment Guide”, chapter “Configuring NotReady Reasons and Work Modes” for more information.

Hope it helps you
René

3 Likes