In a small departmental or branch office scenario, users may be averse to the small delay on answering introduced by Lync Response Groups and Lync Phone Edition devices. (more details on the RGS delay: When Can I Say Hello; RGS Delay Fix Suggestion; ) If you want a very simple ring group with no bells or whistles that avoids the RGS delay on answer, the below might be a work around for you.
- Setup a Lync User to use as your Hunt Group SIP address that you will send calls to (name the user what you want: email@example.com)
- Login to the user using the lync2010 client and Options | Call Forwarding | Edit my Team-Call Group Members and add those you want to ring at the same time.
- How soon to "0-at the same time"
- Now set "Simultaneously Ring" to "My Team-Call Group"
You can use the Lync/Exchange/AD user to set the hours via Outlook (or Outlook Web Access)
Using a Response Group to Add Flexible After Hours Scheduling
Commentor @AL has made an excellent suggestion on how to use a placeholder Response Group to get around the limitations of Outlook after hours schedule. Basically this methods uses RGS to get scheduling, but bypasses the inefficient RGS group ringing processing. Below are the steps:
Create a Response Group “Group” with no agents in it.
Now create a “Queue”, place the empty “Group” in it, and configure the below settings
- Enable Queue overflow = enabled
- maximum number of calls = 0
- call action = forward to SIP address
- SIP address = firstname.lastname@example.org (<-or your “hunt group” lync user)
Now create a Workflow/Response Group and place the above “Queue” in it. Now you will have the snappiness of TeamCall “huntgroups” plus the afterhours configurability of Workflow/Response Groups.
Note that using a Response Group to control your after hours is a benefit in that you have flexible, server based schedule, but it is a failure point if this is a remote branch.
Some Notes/Pros/Cons About The Work Around in this article:
- Only the member of the Team-Call group that answers gets a call record (good)
- the Ring Group "hunt group/dummy" user does not need to be logged in (good)
- Actually avoids some survivability issues that might come with Response Groups in a SBA WAN down scenario (good) (Read more: Click Here)
- Avoids “trombone” in a SBA scenario where PSTN comes into remote branch but RGS is hosted on Front End at main site. (good)
- Simplest way to administrate is log into user using Lync 2010 client (no web administration or Powershell) (not so cool)
- No dynamic login and logout of Ring Group by group members. (not as good)
- Open hours will depend on Outlook work hours which are quite a bit more limited than Lync RGS business hours and cannot be administrated via Powershell. (not so cool)
- There is a hard 20 end point limit in team call. (if a user has an IP phone and Lync client that is 2 end points) (See: http://social.technet.microsoft.com/Forums/en-US/ocsvoice/thread/9523eeae-4182-47f8-a2d7-28d987c81026)
- We have tested having the TeamCall “Unanswered Calls” going to an Exchange UM Attendant and this scenario seems to work fine.
- NOTE: TeamCall Group members cannot transfer TO a TeamCall Group they are a member of. So this means someone who is a part of our “hunt group”/teamcall can NOT transfer or forward calls to this number (not good)
NOTE: If the Lync User with TeamCall is not logged in, and call transferred to this user will goto Voicemail.
- Finally, be very careful and make sure all your objectives are met before implementing and/or recommending this work around.
I suspect there might be some other cons I didn’t think of, so feel free to comment!