" /> partyStatus from call monitoring events - Genesys CTI User Forum

Author Topic: partyStatus from call monitoring events  (Read 1266 times)

Offline aptklassen

  • Newbie
  • *
  • Posts: 9
  • Karma: 0
partyStatus from call monitoring events
« on: August 25, 2020, 09:35:40 PM »
Advertisement
I am using PSDK 9.x

I apologize as I am probably doing something stupid but for call monitoring events like EventCallPartyState there is a method
to get the PartyState. I can see the value from the json dump of the message that the values returned appear to be incorrect
e.g. 2057 or 2569. When I try to match them with the tserver PartyState enum there is no match. I did notice that if I mask
off the upper bits of the value it might match something valid. Is that what I am supposed to do or am I using the wrong
PartyState enum for these values?

Thanks for any ideas,
Andrew

Offline aptklassen

  • Newbie
  • *
  • Posts: 9
  • Karma: 0
Re: partyStatus from call monitoring events
« Reply #1 on: August 28, 2020, 12:46:45 AM »
You all probably know this but it looks like each set of 4 bits in the party state define groups of defines
which can be set independently. So in my case, the least significant 4 bits indicated queued and the upper bits I indicated routing and treatment.