Announcement

Collapse
No announcement yet.

Intermittent last caller attributes

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Furious
    replied
    Originally posted by Ultrajones View Post
    Yes, the caller attribute device was updated after the triggers were processed. I modified the HS3 version of the plug-in to update the attributes before checking the caller attribute triggers.

    Regards,
    Ultrajones
    Spoke too soon, had 2 calls today which didn't fire the events due to not having a valid string value:
    Code:
    Aug-20 18:47:16	 	Info	string group is None
    Aug-20 14:10:17	 	Info	string group is None
    This is running version 3.0.5341.13686

    Leave a comment:


  • Furious
    replied
    Sorry, just catching up after vacation - thanks for looking into this and fixing

    Leave a comment:


  • Ultrajones
    replied
    Yes, the caller attribute device was updated after the triggers were processed. I modified the HS3 version of the plug-in to update the attributes before checking the caller attribute triggers.

    Regards,
    Ultrajones

    Leave a comment:


  • Furious
    started a topic Intermittent last caller attributes

    Intermittent last caller attributes

    Hi,
    just thought I'd drop a post with regards to the occasional problem I'm seeing. I have a script that triggers on all calls, and then pulls in the data to make decisions on how to handle the call.
    99% of the time, works fine. Script extracts strings from the devices, no problem.
    Just occasionally, all but the last caller attributes are returned.

    The script literally does this:
    callergroup=hs.DeviceString(78)

    When it doesn't work, what is stamped in the log is:
    Code:
    Jul-25 16:59:33	 	Info	string group is None
    Any ideas? The variable being set is the last of the caller ID devices (so kind of discounts it's running before all the devices get updated), and the script never fails to get the name and number. Also, it's not the string of the previous caller, just "None".
    Conversely, the last caller attributes device actually shows the correct attributes.
    I'll add a sleep into the script to give it an extra chance, just wondered if you could check the plugin side to see if anything could cause it?
Working...
X