response group - Routing method fails both for simultaneous and longest idle RRS feed

  • Question

  • Dear tech net

    Over the weekend something really strange has happened.

    I have several response groups, some with 2 some with 4 members, or more

    One of the groups even had ring simultaneously setting.

    Last Friday it was ringing fine, today only for one of them.

    I removed the person that it was nor ringing for from the group for 10 minute, deleted %appdata%.. trace and sip folders, added him back in the response group and than it worked again.

    The same situation occurred with a group than had Longest Idle  setting.

    In each case the user had the status "Available"

    But is this going to happen for all response groups? Can this be investigated? I would not like this to happen to all response groups, even worst to happen to more groups in the same time. What could cause this?

    Monday, July 17, 2017 1:19 PM


All replies

  • Hi Ion.

    how looks your environment. Your FE server has the correct hardware requirements like cpu, memory, harddisk?

    regards Holger Technical Specialist UC

    Tuesday, July 18, 2017 3:52 AM
  • Hello Holger

    Yes, it has 32GB RAM, Intel Xeon E5 at 2.6GHZ, 2 processors. It's a virtual machine.

    From what I know from a consultant it meets Microsoft Best Practises.

    Thank you

    Tuesday, July 18, 2017 6:12 AM
  • Hi Ion Vlad Orascu,

    Based on your description, did you mean the issue only happen to the specific user, and after you delete user profile it works again, is that right?

    In my opinion, it won’t influence other response group, but to be on the safe side, we suggest you check if there are any event IDs in SFB FE server side, if possible, please provide it for us to do troubleshooting.

    Moreover, I will share a document about how to troubleshooting response group for your reference


    Alice Wang

    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, July 18, 2017 7:31 AM
  • Hello Alice

    thank you for the document you shared, I have not read it before and now I understand some thing better.

    I'll check the logs and let you know if I find something suspicious

    The problem appears to be fixed for the moment 

    Tuesday, July 18, 2017 7:14 PM