" /> Attached Data Sticking with Desktop - Genesys CTI User Forum

Author Topic: Attached Data Sticking with Desktop  (Read 3928 times)

Todd

  • Guest
Attached Data Sticking with Desktop
« on: January 01, 1970, 12:00:00 AM »
Advertisement
We have a custom desktop that seems to be holding on to attached data on transfers. Here's the scenario. The agent receives a call, transfers that call and data to another agent. Once the caller is gone, if that agent direct dials another extension (even after another call is received!), the call data from the earlier transferred call goes with the direct dial to the desktop. Anyone seen this before or know what the cause of this is? I'm wondering if we aren't completing our transfers correct, but everything looks okay.

Vic

  • Guest
Attached Data Sticking with Desktop
« Reply #1 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Look at your TServer log, and probably you will see that it is your desktop that is holding on to the attached data and not TServer. Attacheddata is managed on perconnid basis inside TServer, so, you would not have the same attach data with the new call unless your desktop fails to recognize that this is a new call and drop the old data.

    Alan Sharp

    • Guest
    Attached Data Sticking with Desktop
    « Reply #2 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Todd Also check that your custom desktop isn't using the 'TSetDefaultUserData' method of a line control wrongly... If you set the default data with this command, but dont clear it later, the same default data will go with any request subsequently made by the application

    cumi

    • Guest
    Attached Data Sticking with Desktop
    « Reply #3 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • ...hm looks very strange to me...would say the privous call is not gone correctly, but if you make a direct call (not a transfer or consult) it doesn't metters.

    The attached data is held in memory (StatServer, TServer), until the ACW is finished. But, as I know, the softphone can not access it. Of course, the softphone can "memorize" it and use it later. This can be a bug.

    Are you using a custom SP or the genesys one?