To understand the Button Label text template, it will help to open a Button Label text file and view it as you read this topic.
Button Label text files have two columns:
Column Name Contents
Button Feature This column lists the code name for each feature that you can assign to a phone button. Avaya Site Administration uses this column to match any button features you selected (when you added feature buttons to a phone) to the text that you want on the label.
Label Text This column contains the text that you want to appear on the button label. Some of the information in this column will print exactly as it appears in this column. However, $ signs are replaced by data that you entered into the specified field number when you assigned feature buttons for the given phone. For example, $2 will be replaced by whatever data you entered into the second field that the voice system displayed when you assigned the given feature button to the phone.
What the $ signs mean
When you assign certain feature buttons, the voice system requests additional information. The information you specify in these additional, feature-related fields gets substituted for the $ codes when you print the labels. For example, if you chose the "abrv-dial" code name (for the Abbreviated Dial feature) when you assigned a feature button to a phone, the voice system asked for two more pieces of information: List and Dialcode. The first field (corresponding to $1) is "abrv-dial". The second field
(corresponding to $2) is List. The third field (corresponding to $3) is Dialcode.
Code: What Avaya Site Administration substitutes:
EXT Extension of the station
$1 The first button data field, which is the code-name for the feature button. For example, abrv-dial. $2 The second button data field. For the abrv-dial
example, this correlates to the List field. $3 The third button data field. For the abrv-dial
For example, assume the Button Label text file contains the following entries: Button Feature Label Text call-appr 9079-$EXT abrv-dial AD $2 $3 abrv-dial 1 998 Login abrv-dial 1 999 Logoff
Avaya Site Administration would print the following button labels:
For a call-appr button on station 1000, Avaya Site Administration would print a label of
9079-1000.
For an abrv-dial button with List=2 and Dialcode=123, Avaya Site Administration would print a label of AD 2 123, since "abrv-dial 2 123" does not match any of the entries. For an abrv-dial button with list=1 and Dialcode=999, Avaya Site Administration would print a label of Logoff, since that matches the entry of "abrv-dial 1 999" in the Button Feature column.
How Avaya Site Administration creates button labels
Once you assign feature buttons to your phone, create a Button Label text file, tell Avaya Site Administration which phones you want to print button labels for and which Button Label text file to use, set up the button label layout, and click Print, then Avaya Site Administration merges information from the voice system into the format that you specified in the Button Label text file, and prints the labels.
To merge the information, Avaya Site Administration uses roughly the following procedure. For the purpose of illustration, we explain the process for only one feature button (the "abrv-dial" button, with List=1 and Dialcode=998), but Avaya Site
Administration performs this operation for all buttons assigned to a given phone. 1 Avaya Site Administration looks in the Button Feature column for an entry that
matches all of the button fields, concatenated as a single string and separated by spaces.
2 When Avaya Site Administration finds the appropriate entry in the Button Feature column, it looks in the Label Text column and if it sees any of the following codes, it substitutes the feature-related data for them.
In the above example, Avaya Site Administration would first look for abrv-dial 1
998. If it finds this entry, it will use the Label Text that is specified in the right column
of that row. For example, Login.
If it doesn’t find abrv-dial 1 998, it will search for abrv-dial. If this entry exists, Avaya Site Administration uses the entry specified in the right column of that row, substituting data for $ signs. For example, AD 1 998.
If it doesn’t find abrv-dial, Avaya Site Administration will use the value in the Button Feature column as the label text. For example, abrv-dial 1 998.
Printing button labels
1 In the Target System box on the toolbar, select the voice system from which you want to print button labels.
2 On the browser pane, click the Tasks tab. 3 On the Tasks tab, click General.
4 Click Print Button Labels.
5 If you have not created any button labels yet, the system will ask you if you want to create a button label text file. To do so, complete the following steps:
a) Click Yes.
b) Change the text in of the button labels as needed. c) When finished, click to close the button label text file. d) At the Save changes prompt, click Yes.
e) Click Print Button Labels again. 6 In the Print Button Labels screen, specify:
which set type you want to print button labels for.
which range of extensions you want to print labels for.
Avaya Site Administration will search the selected voice system for all extensions in the range you specified that match the set type you specified, and then present the results in the Button Label Printing screen.
7 Test print and adjust a sample label before attempting to print a large number of labels.
Note
Button labels print on the default printer configured for your computer, not a printer connected to the voice system.
8 After you have aligned the printing of one label correctly, print the rest of the button labels as described by clicking Help (F1) on the Button Label Printing screen.
Frequently Asked Question
Q. I want to print button labels for a phone that has a "spare" button label at the top. I can’t see a way to enter text for this "spare" label.
A. Correct. Some phones (like the 6400 series) have a button label at the top that, when you generate labels using information from the voice system, is reserved for the extension number of that phone. Some customers occasionally use button label templates without pulling information from the voice system, manually entering text for the labels. However, it is not possible to specify other content for the label that is reserved for the extension number.