locked
Call onbehalf from a resonsegroup to another responsegroup RRS feed

  • Question

  • Today a user reported an interesting incident in our SfB environment.

    User A is member of Response Group A and he is calling on behalf another Response Group B. The call fails with the message: “Call was not completed or has ended.”

    Now user A is calling the Response Group B directly, then the call works fine.

    That raises the question: Is it supported (and actually working) to call on behalf of an response group another response group?

    We have a Skype for Business environment (fully patched).

    Wednesday, January 18, 2017 3:33 PM

Answers

  • Hi Joerg,

    Because user is a member of response group A, user could not be calling on behalf of another response group B, it is by design, thanks for your understanding and support.


    Best Regards,
    Jim Xu
    TechNet Community Support


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

    • Marked as answer by Joerg Burmann Thursday, January 19, 2017 11:57 AM
    Thursday, January 19, 2017 7:56 AM

All replies

  • Hi Joerg,

    Because user is a member of response group A, user could not be calling on behalf of another response group B, it is by design, thanks for your understanding and support.


    Best Regards,
    Jim Xu
    TechNet Community Support


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

    • Marked as answer by Joerg Burmann Thursday, January 19, 2017 11:57 AM
    Thursday, January 19, 2017 7:56 AM
  • Hi Joery,

    We are glad to hear our solution is helpful to you, if there are any issues in the feature, welcome to our forum to get help,

     


    Best Regards,
    Jim Xu
    TechNet Community Support


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

    Tuesday, February 7, 2017 8:10 AM