Hello, just getting in to setting up response groups which at first worked fine but now when I try and select the address of a workflow to choose where my unanswered calls go, I get the error:

One or more selected contacts cannot receive your calls. Either the contact is outside of your organization, is an automated service, or is not running your version of Lync

As I say this used to work fine. I type the sip address of the workflow and it does get resolved but I'm not able to select it. Any ideas?

Edit: Forgot to add, I can call the response group from my Lync client, I just can't set it as my call forward.

• Edited by shandersh Monday, December 02, 2013 1:42 PM Extra information

Is this Lync 2013 Client?

This works in the latests version of the Lync 2013 according to my test.

It is 2 steps if the RGS contact is not already in forwarding list. First you need to add a new number/contact (in this case the RGS contact), then select it as forwarding destination.

Hi,

how did you configure the forwarding? is it for the Line URI or SIP URI? Try the SIP Uri

This is a Lync 2010 client and I'm using the SIP URI - I don't have any number associated with the hunt group.

I would attach a screenshot but I'm not able! On my client I go to the call forwarding settings -> Call forward to -> New number or contact and then type the SIP URI in the box.

Many thanks!

• Edited by shandersh Monday, December 02, 2013 3:42 PM More info

Can you set the call forwarding to some other user instead of the RGS contact? just want to rule out any client side issues

Yes I can, I can even forward to federated users from other organisations!

have you tried adding the RGS contact as a contact in your buddy list as assign forward to it? other than manually specifying it?

Thanks for your help so far.

Just tried that, I select it from the list and get the same error.

how about trying lync 2013 client registered to your Lync 2010 server and see what happens?

Just trying to get a copy of the client although this is a problem on every client I have tried and it worked last week - I can't figure out what has changed.

OK. run the Logging on the client and simulate the scenario. Open the log using the Snooper tool and check the "Messages" for that communication segment. It'll give you an idea what's going on.

It should be this hard. but something really fishy going on there.