Monthly Archives: November 2015

Call Forwarding Added Back to Skype for Business for iOS

In my previous article: I noted that many features were removed from the Lync iOS application for iPhone and iPad when it was upgraded to the Skype for Business application.  One of my most used features, call forwarding, was pulled.  This feature has now been officially put back in place.


As you can see, it’s where you would expect it to be below.  This is a very welcome re-addition to the application, but I feel, and Microsoft I believe understands, that there’s still a long way to go.  In the new “mobile first” world, I also feel we’re a bit behind in this department.



I’m still patiently waiting for my second most used feature, PowerPoint sharing, to be added back in.  At the moment, we can use desktop sharing instead.  However, if the presenter isn’t one who works with your firm, asking for them to switch to desktop sharing for their slide deck can be embarrassing.


Once we’re back on par with some of the features we had in the past, I’m excited to see some added new functionality.  I’m hoping to see seamless transfers of audio between the smartphone and other clients and more feature parity with the full client (including e911).

Let me know your thoughts as well, but remember, real feedback should go to Microsoft at

Lync and Skype Response Groups; Alert Time vs Queue Time-out


I realize that there are other blogs that discuss this, and my apologies to the owners, but TechNet itself isn’t so clear and this comes up in the forums regularly.  I wanted to clarify just what is Lync and Skype for Business Response Group (RGS) group alert time vs queue time-out as well as discuss their relationship.   I feel it is best to do so through the use of scenarios. Please feel free to comment below if you feel I missed something.

Group Alert Time

This setting is simply how long the entire group will be tried in seconds before it gives up.  It does not mean how long each group member’s phone will ring.  This setting becomes more clear when we look at it in relationship to the queue.

Queue Time-out

This setting is the total amount of time all groups in the queue will be tried.  There are scenarios where the time in the queue is actually longer than the queue time-out is set, and this can be observed in scenario B below.

Scenarios and Examples

It’s easier to explain this through the use of individual scenarios, so I will attempt to outline this below.

Scenario A – Single group in a queue with queue time-out set to be longer than group alert time

In this scenario, the group will ring for the alert time seconds defined in the group and stop.  Since the queue time-out has not been reached, the group will ring again.  This will repeat until the time-out has been reached.  This scenario is handy for when you want the call to fail to another member of the group after a set time-frame.  For example, if you have a four-member group set as round robin, with an alert time of 10 seconds, and your queue time-out is forty seconds, each available member of the group will hear the phone ring assuming nobody picks up.

Scenario B – Single group in a queue with queue time-out set to be shorter than group alert time

In this scenario, even though the time-out is reached the ringing will continue until the group’s alert time has been reached.  For example, if the queue time-out is 10 seconds, but the group’s alert time is 30 seconds, the phone will ring for 30 seconds before the queue acts on the time-out.  This is typically due to a misconfiguration rather than a planned scenario.

Scenario C – Multiple groups in a queue with queue time-out set to be longer than the sum of the group alert times

In this scenario, multiple groups are set up and ordered within the queue.  The first group will be tried until it’s alert time is reached, and since the queue time-out has not been reached, the next group will then be tried.  After each group is tried, a check to see if we’re past the time-out is made.  Since we are not, the first group will be tried again and so-on.

Scenario D – Multiple groups in a queue with queue time-out set to be shorter than the sum of the group alert times

In this scenario, multiple groups are again set up and ordered within the queue.  The first group will be tried until it’s alert time is reached (similar to scenario B, this can extend the queue time-out), and a check is made to see if we’re past the time-out.  If so, we perform our time-out call action.  If not, we move to the next group and try it for it’s full alert time.  At the end, we check to see if we’ve passed the time out and move forward.


Hopefully that cleared a few things up for a few searchers out there, if so or if not leave a comment below.



Yes, Analog Is Still a Big Deal, Enter the AudioCodes MediaPack 1288

It’s a new world, it’s a new model, SIP is king and Unified Communications has supplanted standalone telephony.  We are always connected, we have endless choice for effective communication,  we can start large video conferences from a disposable device in our pockets, we live in the future.  So why am I so excited about this new high density analog gateway from AudioCodes?

In a perfect world, analog would be dead, but we live in the real world with legacy processes EmergencyLight
and systems that need to be brought forward.  Large enterprises, higher education, healthcare, and other organizations still have analog needs that need to be filled in a UC world.  Imagine a university campus filled with emergency blue light call boxes, press a button and you’re on the line with police.  That’s analog. Imagine rooms upon rooms filled with hospitality phones that are extremely costly to replace or have no good SIP equivalent.  More analog.  Until now, the high density analog options for Skype for Business or Lync were rough.  The biggest supported gateway had a mere 24 ports.  Sure, you could maintain many gateways but the complexity multiplies.  It sadly came up that maintaining a trunk to a legacy TDM system was often a reasonable answer.

But finally we have a new option, the AudioCodes MediaPack 1288.  This 3U device can start with 144 analog FXS ports and scale to 216 or 288 depending on the number of line-cards (up to 4) added.  Each of those line cards has three 50-pin champ connectors which can connect to a punch down block or an RJ11 adaptor.  For those emergency phones, it supports long haul connections over 4 and a half miles (your ethernet cable won’t make it).   When you’re used to stacking gateways and maintaining multiple routes, this unit means the world.

For fun, here’s a sneak peek at the unit below with a single line-card. I have to make this clear, this picture is unofficial and the look may change by GA, meaning yours might look a bit different.


If you’re looking for more info, AudioCodes’ site has the specs: