locked
Response Group Settings RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi there,

    We have an operational Lync environment with a number of response groups set up which appear to be working as people are being called when call come in. However, when I try to go into the Response Group Settings via the Lync client I get the following message.

    You are not a member of any group. For assistance, contact your support team

    I am a member of at leat two response groups and I am called when calls come into these groups.

    I can't see any entries in the event logs.

    Any ideas how to troubleshoot this issue?

    Thanks

    Thursday, January 20, 2011 8:53 PM

Answers

  • Question
    Sign in to vote
    3
    Sign in to vote

    All right.

    Although I will underline the problem, I strongly advise you to wait for a fix (if one is released) with the upcoming CU.

    Apparently there is a difference between Topology Builder in RC and RTM. Versions prior to (and/or including) RC listed the following string "urn:application:Rgs" as shown (note the case.) In RTM, this same string is "urn:application:RGS".

    The problem is somehow related to case sensitivity. I have never spent time thinking as of why this will affect the query…  Modifying the .tbxml file (changing Rgs to capital), re-publishing the modified file and restarting the service resolves the issue.

    Again, if it is not “hysterical” emergency like in my case, do not fiddle with the .tbxml file because you can end up with more troubles one can imagine. If you have to edit it, DO NOT USE text editor. XML Notepad http://www.microsoft.com/downloads/en/details.aspx?familyid=72d6aa49-787d-4118-ba5f-4f30fe913628&displaylang=en does the job.

     

    Drago

    http://ocsdude.blogspot.com | MVP Snom OCS Edition
    • Marked as answer by wookie1 Friday, January 21, 2011 1:01 AM
    Thursday, January 20, 2011 11:10 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Did you by any chance migrated from RC to RTM?

     

    Drago

    http://ocsdude.blogspot.com | MVP Snom OCS Edition
    Thursday, January 20, 2011 9:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes we did although Enterprise voice was not deployed at that time.
    Thursday, January 20, 2011 9:39 PM
  • Question
    Sign in to vote
    3
    Sign in to vote

    All right.

    Although I will underline the problem, I strongly advise you to wait for a fix (if one is released) with the upcoming CU.

    Apparently there is a difference between Topology Builder in RC and RTM. Versions prior to (and/or including) RC listed the following string "urn:application:Rgs" as shown (note the case.) In RTM, this same string is "urn:application:RGS".

    The problem is somehow related to case sensitivity. I have never spent time thinking as of why this will affect the query…  Modifying the .tbxml file (changing Rgs to capital), re-publishing the modified file and restarting the service resolves the issue.

    Again, if it is not “hysterical” emergency like in my case, do not fiddle with the .tbxml file because you can end up with more troubles one can imagine. If you have to edit it, DO NOT USE text editor. XML Notepad http://www.microsoft.com/downloads/en/details.aspx?familyid=72d6aa49-787d-4118-ba5f-4f30fe913628&displaylang=en does the job.

     

    Drago

    http://ocsdude.blogspot.com | MVP Snom OCS Edition
    • Marked as answer by wookie1 Friday, January 21, 2011 1:01 AM
    Thursday, January 20, 2011 11:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    That has fixed the problem.

     

    Thanks for your help

    Friday, January 21, 2011 1:01 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Drago,

     

    Do you know if this fix made it into CU1?

     

    -Jamie

    Thursday, January 27, 2011 4:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Not that I am aware of. This should be handled by either Topology Builder or standalone application (which reads and modifies the topology), but there might be another way as well.

    In any case, the KB's did not mention this issue, so I will take that it has not been inclided. Hope MSFT will comment on this.

     

    Drago

    http://ocsdude.blogspot.com | MVP Snom OCS Edition
    Thursday, January 27, 2011 5:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We had this issue, and we never had RC code running. We migrated from OCS 2007 R2 to Lync RTM. Changing the case on the several instances of "urn:application:Rgs" as mentioned above, fixed the problem.

    Thanks, Drago!

    Thursday, February 23, 2012 3:02 AM