" /> What syntax is correct for Filters section in Statserver? - Genesys CTI User Forum

Author Topic: What syntax is correct for Filters section in Statserver?  (Read 4210 times)

CCpulse

  • Guest
What syntax is correct for Filters section in Statserver?
« on: May 19, 2008, 12:27:30 PM »
Advertisement
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



Marked as best answer by on April 20, 2025, 09:58:24 PM

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
You can check that on TServer logs for a correct handling of your scenario

tony

  • Guest
Re: What syntax is correct for Filters section in Statserver?
« Reply #2 on: May 19, 2008, 03:40:45 PM »
[i](Never met anyone called CCPulse before... I wonder if that is a Forename or a Surname... :) )[/i]

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;

[b]Using attached data (KVP):[/b]

Lunch=PairExist ("ReasonCode","Lunch")

[b]Using a GAD NotReady Code:[/b]

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

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Re: What syntax is correct for Filters section in Statserver?
« Reply #3 on: May 20, 2008, 03:22:34 PM »
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

  [font=Courier]message RequestAgentNotReady
  AttributeAgentWorkMode 0 (Unknown)
  AttributeExtensions [2] 00 00..
  AttributeThisQueue '...'
  AttributeReferenceID 13325
  AttributeReason [12] 00 01 00 00..
    'Lunch'  '1'
  AttributeThisDN '...'[/font]

- 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é