I would be thrilled if I was able to get 1-3 second delays for RSGs!
I have tested with a stopwatch from the time the RSG agent picks up the receiver to the time the call connects:
Aastra 6275IP and Polycom CX600 (Optimized for Lync), there is about a 9-10 second delay
Polycom VVX500 and Polycom VVX410 there is about a 6 second delay
Polycom VVX411 there is a 5 second delay.
Calls directly to the agent (non RSG) pick up immediately.
It's hard to believe that an enterprise "solution" from Microsoft has such a HUGE design flaw. I've argued back and forth with my boss who choose this "solution" before I arrived at the company and spent MONTHS of project deployment delays because he thinks it can be solved. I've consulted with three different companies...all said there will always be a delay.
If you don't need the flexibility of RSGs, considering using "team calling" which has no delays but rings multiple phones at the same time. You can set parameters like the hours (via Outlook), have it ring to teammates after a certain amount of rings etc.
Good luck, I feel your pain....
@JRFoster wrote:
Hi,
Is there documentation that outlines the required network bandwidth and latency when working as a Branch Office Extension in a S4B Response Group? Some of our users are seeing establishing times taking between 1-3 seconds. Using VVX 410s on the latest 5.5 release.
Thanks!
