When an administrator adds a new station in Avaya Aura® Communication Manager (CM) using the add station command without specifying a template, the system populates the configuration fields with default values. According to official Avaya documentation for administering CM, the default value assigned to the Class of Service (COS) field is 0. The COS profile is a critical setting that determines which system features are authorized for the station user. While administrators typically change this to a custom COS that aligns with the user's role, the initial system default is always 0.

A. 3: This is a valid, assignable COS value but is not the system's default for a newly created station.

B. 2: This is a valid, assignable COS value but is not the system's default for a newly created station.

C. 1: While COS 1 is often the first custom profile configured by administrators, it is not the default value assigned by Communication Manager.

1. Avaya Aura® Communication Manager Documentation Library, Administering Avaya Aura® Communication Manager, Release 7.1, Document Number 03-300509, Issue 15, November 2018.

Page 138, Chapter "Administering stations", Section "Station fields": In the description for the add station screen, the entry for the Class of Service field explicitly states, "The default value is 0."

2. Avaya Aura® Communication Manager Documentation Library, Feature Description and Implementation for Avaya Aura® Communication Manager, Release 7.0, Document Number 555-245-205, Issue 10, May 2015.

Page 431, Chapter "Feature Reference", Section "Class of Service (COS)": This document defines COS, stating, "Each station, attendant console, and data module is assigned a Class of Service (COS) group number from 0 to 127." This confirms the valid range, for which 0 is the established default.