Specifications
Configuration and Maintenance Manual
86
Troubleshooting Tables
The troubleshooting tables located on the following pages provide a description of some basic
problems or errors, a corresponding probable cause, and the corrective action you should take.
Some trunk line(s) came
up (trunkalert)
“Enterprise info” Messages = “trunk
lines $linecode ($resultCode) came up
HH:MM:SS MM/DD/YYYY”
Trunk(s) ID are now in service at the
specified time.
Table 9: E-mail Invitation Characters
Problem or Error Probable Cause Corrective Action
Some characters in the e-mail
invitation do not display correctly for
all languages.
The user has Outlook 2003 or
settings are not configured in
Outlook 2007 and 2010 to convert
the characters correctly.
Change the international settings in
Outlook for the UTF-8 mailto
protocol. Refer to the Mitel
Collaboration Advanced User Help
for details.
Table 10: Using the OFT with Windows 7
Problem or Error Probable Cause Corrective Action
The Mitel Conferencing tab in
Outlook does not retain the server
URL and user password.
Windows 7 includes enhancements
to security that require
Administrator privileges to write to
the folder where the OFT
information is saved.
Unless the user has the necessary
privileges, they will need to type the
server URL and user password
every time they want to access
MCA conferencing through their
Outlook calendar.
Table 11: Log On Problems
Problem or Error Probable Cause Corrective Action
When trying to log on by typing the
user name and password the
screen returns to the log on page.
Internet Explorer cookies are case
sensitive. When the user logs on,
the cookie is not set up with the
same case and the user is denied
access.
Make sure the cookie and
username/password use the same
case.
The user logs on successfully but is
returned to the log on page when
attempting to perform any action
within MCA.
The URL does not match the URL in
the Internet Explorer cookies. It is
likely that the URL used to connect
to MCA is only a partial of the
required URL.
Make sure the cookie uses the
entire URL.
Table 8: Conferencing Error Messages for Alarm/Alert Conditions (continued)
Message Subject Description
(Sheet 2 of 2)