User's Manual
to logically sort table of contents in groups and items. Avaya recommends starting the first item
in a group at 1 and incrementing by 1.
An authorized of an entry typically found in this field is as follows: 1.
WTC_Language_str
This field contains a 4-byte language code. Refer to the documentation of the Table:
eWEB_USER_AUTH on page 391 for a list of language codes. This field contains a number,
and when combined with WTC_Group_n, and WTC_Item_n, results in a key, which is not
duplicated within a site.
This field specifies the language used in the field WTC_Text_str, and in the PHP script of HTML
documents defined in WTC_Link_str.
This field allows the table of contents to be multilingual. With the correct definition, English
users see the table of contents in English, Dutch users in Dutch, and so on.
To implement a new language:
1. Define the appropriate language code in the eWEB_USER_AUTH table.
2. Translate the descriptions of the links in the eWEB_TOC table.
3. Edit the eWeb_mri.php file that is located in C:\SOPHO Messenger@Net\Web
\htdocs.
4. Provide an additional section for the new language. The eWeb_mri.php is provided
in English (2909), and Dutch (2963).
An authorized of an entry typically found in this field is as follows: 2909.
WTC_Text_str
This field specifies the text that the web user sees in the table of contents. Avaya recommends
using the same language as specified in the field WTC_Language_str.
An authorized of an entry typically found in this field is as follows: Welcome (in English - 2909)
or Welkom (in Dutch - 2963).
WTC_Link_str
This field specifies the hyperlink associated with the table of contents. If blank, the hyperlink
is inactive. This is typically used to logically group menu options in different sections, and define
such empty link for the header of each section. See the sample in Table 58: Valid WTC_Link_str
values on page 387 for more information.
Table: eWEB_TOC
386 DECT Messenger Installation and Commissioning — Book 2 March 2012
Comments? infodev@avaya.com