Using calling plan licenses that are available presently in only few countries.It’s possible to enable Online Users for Call Queues and Auto Attendants (Queue Agents, Operators) in two different ways:

This announcement will enable such organizations to also benefit by using these online features, and also remove the dependency on Exchange for Auto Attendants. It’s a great news, as presently a lot of environments are hybrid, with many voice features kept on premises. Marina started the presentation with an important news - the support of the hybrid tenant configurations coming soon. Marina Kolomiets and Irena Andonova walked you through design, provisioning, licensing requirements, and use Call Queues and Auto Attendant concept across online and hybrid topologies.

Auto Attendant: Provides automated call answering and route calls using numeric keypad entries and voice recognition, offering features like Directory Search and multi-level menu options.

Call Queues: Provides automatic call distribution that allows organizations to handle calls at scale and distribute incoming calls based on customized rules.

Key Microsoft Phone System Cloud Services concept for this session are: These services, Auto Attendants and Call Queues, are the main interfaces for the callers to reach people and departments in your organization over the phone. This refers to the Usage property of the PSTN usage settings, which contains the list of PSTN usages.A good understanding of the Microsoft Phone System Cloud Services capabilities in Office 365 for incoming call routing is required to properly and quickly route callers to the correct destination, all without human intervention. Note the syntax of the replace value: $a.Usage. The second line calls the Set-CsVoicePolicy cmdlet to modify the voice policy for site Redmond.Ī value is passed to the PstnUsages parameter to replace the current list of usages for the policy with the list contained in the global set of PSTN usages. The first line in this example calls the Get-CsPstnUsage cmdlet to retrieve the global set of PSTN usages for the organization and save that set in the variable $a. Set-CsVoicePolicy -Identity site:Redmond -PstnUsages example modifies the voice policy for site Redmond so that all the PSTN usages defined for the organization are applied to this policy. The Identity parameter is a positional parameter, therefore if you put the identity value first in the list of parameters you don't need to explicitly state that it's the Identity.) - Example 2 - $a = Get-CsPstnUsage (Note that the Identity parameter is not explicitly specified. This command also removes 'Local' from the list of PSTN usages for this policy. Examples - Example 1 - Set-CsVoicePolicy UserVoicePolicy2 -AllowSimulRing $false -PstnUsages example sets the AllowSimulRing property to False for the per-user policy UserVoicePolicy2, meaning any users assigned this policy are not enabled for simultaneous ring, a feature that determines whether a second phone (such as a mobile phone) can be set to ring every time the user's office phone rings. Use this cmdlet to change the settings that enable and disable many of these features. Voice policies are used to manage such Enterprise Voice-related features as simultaneous ringing (the ability to have a second phone ring each time someone calls your office phone) and call forwarding. This cmdlet modifies an existing voice policy. In this article Syntax Set-Cs Voice Policy This cmdlet was introduced in Lync Server 2010.

Skype for business 2013 call park