locked
Response Group Calls not Presented to Agents from the same Server (PrimaryServerPrimaryRegistrar) RRS feed

  • Question

  • We are currently facing weird issue wherein calls to Response Group agents are not getting delivered whereas direct calls to these agents are working without any issues. These agents are from same server (PrimaryPoolPrimaryRegistrar) and we seeing LS User Services Event 32270 in every 5 minutes in this Front end Server. Set up is 3 Front end server and 1 Backend SQL without HA.

    Please suggest if anyone across this issue and have solution worked.

    


    Friday, February 7, 2020 11:58 PM

All replies

  • Hi Mathew,

    What is your agent? On-premise or online?

    Based on my knowledge, if an agent is moved from on-premise to online, response group calls will not be routed to that agent. In addition, if the front end server going down, any calls currently being handled by the active Match Making service on that Front End Server are also lost.

    We recommend you check if your response group application uses the following ports: port 5071 for SIP listening requests and port 8404 for interserver communications. For more details about requirements for response group application, please refer to:

    https://docs.microsoft.com/en-us/skypeforbusiness/plan-your-deployment/enterprise-voice-solution/response-group

    About the event ID, it seems that it cause by the overload workload on FE server or a failure of the SQL backend. To resolve this issue, you needed to stop the services on the entire pool at the same time and restart the SQL nodes. For more details about troubleshooting this issue, you can refer to:

    https://www.ucmadscientist.com/response-group-calls-not-presented-to-agents-due-to-sql-write-issues-event-id-32269-and-32270/

     

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

    Best Regards,
    Jimmy Yang

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
    Monday, February 10, 2020 7:08 AM
  • This is completely on-premise set up. 

    Regarding the solution that you shared "stop the services on the entire pool at the same time and restart the SQL nodes"  -  Is it to stop CSWindows services in all 3 FE servers and start the SQL nodes or shutdown the FE servers and then restart the SQL node. Both the cases, we need to bring the quorum back online. Let me know.

     

    Wednesday, February 12, 2020 5:09 AM
  • Hi Mathew!

    We recommend you shutdown the FE servers and then restart the SQL node.

    Best Regards,
    Jimmy Yang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Tuesday, February 18, 2020 9:13 AM
  • Hi,
    Is there any update on this case?
    Please feel free to drop us a note if there is any update.
    Have a nice day!

    Best Regards,
    Jimmy Yang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, February 21, 2020 11:16 AM