You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -42,10 +42,11 @@ You can create new AAs by using the New-CsAutoAttendant cmdlet; each newly creat
42
42
>
43
43
> - -EnableMainLineAttendant
44
44
> - -MainlineAttendantAgentVoiceId
45
+
> - -AutoRecordingTemplateId
45
46
46
47
**NOTES**:
47
48
48
-
- To setup your AA for calling, you need to create an application instance first using `New-CsOnlineApplicationInstance` cmdlet , then associate it with your AA configuration using `New-CsOnlineApplicationInstanceAssociation` cmdlet.
49
+
- To setup your AA for calling, you need to create an application instance first using [New-CsOnlineApplicationInstance](new-csonlineapplicationinstance.md) cmdlet , then associate it with your AA configuration using [New-CsOnlineApplicationInstanceAssociation](new-csonlineapplicationinstanceassociation.md) cmdlet.
49
50
- The default call flow has the lowest precedence, and any custom call flow has a higher precedence and is executed if the schedule associated with it is in effect.
50
51
- Holiday call flows have higher priority than after-hours call flows. Thus, if a holiday schedule and an after-hours schedule are both in effect at a particular time, the call flow corresponding to the holiday call flow will be rendered.
51
52
- The default call flow can be used either as the 24/7 call flow if no other call flows are specified, or as the business hours call flow if an "after hours" call flow was specified together with the corresponding schedule and call handling association.
This example creates two new AAs named _Main auto attendant_ and _Customer Support Auto Attendant_. Both AAs share the same Christmas holiday schedule. This was done by reusing the Schedule ID of the _Christmas_ holiday when creating the call handling associations for those two AAs using New-CsAutoAttendantCallHandlingAssociation cmdlet.
219
+
This example creates two new AAs named _Main auto attendant_ and _Customer Support Auto Attendant_. Both AAs share the same Christmas holiday schedule. This was done by reusing the Schedule ID of the _Christmas_ holiday when creating the call handling associations for those two AAs using [New-CsAutoAttendantCallHandlingAssociation](new-csautoattendantcallhandlingassociation.md) cmdlet.
219
220
220
-
We can see when we ran the Get-CsOnlineSchedule cmdlet at the end, to get the _Christmas Holiday_ schedule information, that the configuration IDs for the newly created AAs have been added to the `AssociatedConfigurationIds` properties of that schedule. This means any updates made to this schedule would reflect in both associated AAs.
221
+
We can see when we ran the [Get-CsOnlineSchedule](get-csonlineschedule.md) cmdlet at the end, to get the _Christmas Holiday_ schedule information, that the configuration IDs for the newly created AAs have been added to the `AssociatedConfigurationIds` properties of that schedule. This means any updates made to this schedule would reflect in both associated AAs.
221
222
222
-
Removing an association between an AA and a schedule is as simple as deleting the CallHandlingAssociation of that schedule in the AA you want to modify. Please refer to [Set-CsAutoAttendant](https://learn.microsoft.com/powershell/module/microsoftteams/set-csautoattendant) cmdlet documentation for examples on how to do that.
223
+
Removing an association between an AA and a schedule is as simple as deleting the CallHandlingAssociation of that schedule in the AA you want to modify. Please refer to [Set-CsAutoAttendant](set-csautoattendant.md) cmdlet documentation for examples on how to do that.
The Auto Recording template ID to apply to the Auto attendant.
297
+
298
+
> [!NOTE]
299
+
> 1. Requires that Mainline attendant be enabled.
300
+
> 1. The template must not have an audio file configured.
301
+
302
+
```yaml
303
+
Type: String
304
+
Parameter Sets: (All)
305
+
Aliases:
306
+
307
+
Required: False
308
+
Position: Named
309
+
Default value: None
310
+
Accept pipeline input: False
311
+
Accept wildcard characters: False
312
+
```
313
+
293
314
### -CallFlows
294
315
295
316
The CallFlows parameter represents call flows, which are required if they are referenced in the CallHandlingAssociations parameter.
296
317
297
-
You can create CallFlows by using the [`New-CsAutoAttendantCallFlow`](https://learn.microsoft.com/powershell/module/microsoftteams/new-csautoattendantcallflow) cmdlet.
318
+
You can create CallFlows by using the [New-CsAutoAttendantCallFlow](new-csautoattendantcallflow.md) cmdlet.
The CallHandlingAssociations parameter represents the call handling associations.
314
335
The AA service uses call handling associations to determine which call flow to execute when a specific schedule is in effect.
315
336
316
-
You can create CallHandlingAssociations by using the `New-CsAutoAttendantCallHandlingAssociation` cmdlet.
337
+
You can create CallHandlingAssociations by using the [New-CsAutoAttendantCallHandlingAssociation](new-csautoattendantcallhandlingassociation.md) cmdlet.
The DefaultCallFlow parameter is the flow to be executed when no other call flow is in effect (for example, during business hours).
333
354
334
-
You can create the DefaultCallFlow by using the [`New-CsAutoAttendantCallFlow`](https://learn.microsoft.com/powershell/module/microsoftteams/new-csautoattendantcallflow) cmdlet.
355
+
You can create the DefaultCallFlow by using the [New-CsAutoAttendantCallFlow](new-csautoattendantcallflow.md) cmdlet.
Specifies the users to which call transfers are not allowed through directory lookup feature.
406
429
If not specified, no user in the organization is excluded from directory lookup.
407
430
408
-
Dial scopes can be created by using the [`New-CsAutoAttendantDialScope`](https://learn.microsoft.com/powershell/module/microsoftteams/new-csautoattendantdialscope) cmdlet.
431
+
Dial scopes can be created by using the [New-CsAutoAttendantDialScope](new-csautoattendantdialscope.md) cmdlet.
Specifies the users to which call transfers are allowed through directory lookup feature.
441
464
If not specified, all users in the organization can be reached through directory lookup.
442
465
443
-
Dial scopes can be created by using the [`New-CsAutoAttendantDialScope`](https://learn.microsoft.com/powershell/module/microsoftteams/new-csautoattendantdialscope) cmdlet.
466
+
Dial scopes can be created by using the [New-CsAutoAttendantDialScope](new-csautoattendantdialscope.md) cmdlet.
The LanguageId parameter is the language that is used to read text-to-speech (TTS) prompts.
460
483
461
-
You can query the supported languages using the [`Get-CsAutoAttendantSupportedLanguage`](https://learn.microsoft.com/powershell/module/microsoftteams/get-csautoattendantsupportedlanguage) cmdlet.
484
+
See [Get-CsMainlineAttendantSupportedLanguages](get-csmainlineattendantsupportedlanguages.md) for a list of languages supported with Mainline attendant.
485
+
486
+
See [Get-CsAutoAttendantSupportedLanguage](get-csautoattendantsupportedlanguage.md) for a list of languages supported with Auto attendant.
The TimeZoneId parameter represents the AA time zone. All schedules are evaluated based on this time zone.
528
553
529
-
You can query the supported timezones using the [`Get-CsAutoAttendantSupportedTimeZone`](https://learn.microsoft.com/powershell/module/microsoftteams/get-csautoattendantsupportedtimezone) cmdlet.
554
+
See [Get-CsAutoAttendantSupportedTimeZone](get-csautoattendantsupportedtimezone.md) for a list of supported time zones.
0 commit comments