Avaya

Message Networking Help
Home | Search  
Print | Back | Fwd | Close  
Getting Started Admin Maintenance Reference
Home > Maintenance > Troubleshooting Message Networking > General troubleshooting

General troubleshooting

This topic provides information you can use to troubleshoot general Message Networking issues.

Static on SMTP messages

Possible cause
Action
Probable fix
If SMTP messages being sent via a sound card have static, the users' microphone settings might be the cause.
Check users' microphone settings.
Adjust users' microphone settings.

SMTP/MIME messages fail

There are a number of reasons why SMTP/MIME messages may fail to be delivered. Some possible causes are provided in the following table.

Possible cause
Action
Probable fix
The sender is not recognized because an incorrect User ID or Domain Name is used in the Message Networking configuration.
  1. Display Last SMTP Dialog.
  2. Select Incoming.
  3. Compare the user name in the Remote:MAIL From: line against the User ID on the Subscriber Parameter page for the subscriber sending the message.
  4. Compare the domain name in the Remote:MAIL From: line against the Domain Name field on the Subscriber Parameter page for the subscriber sending the message.
  5. Compare the domain name in the Remote:MAIL From: line against the Domain Name field on the Remote Machine Parameters page for the remote machine on which the sending subscriber resides.
  • If the User ID on the Subscriber Parameters page for the sending subscriber does not match the user name shown in the Remote:MAIL From: line on the Display Last SMTP Dialog page, modify the User ID to match the user name.
  • If the Domain Name on the Subscriber Parameters page for the sending subscriber does not match the domain name shown in the Remote:MAIL From: line on the Display Last SMTP Dialog page, modify the Domain Name on the Subscriber Parameters page to match the domain name.
  • If the Domain Name on the Remote Machine Parameters page for the remote machine on which the sending subscriber resides does not match the domain name shown in the Remote:MAIL From: line on the Display Last SMTP Dialog page, modify the Domain Name on the Remote Machine Parameters page to match the domain name.
The wrong MTA was specified on the Remote Machine Parameter page.
  1. Display the last SMTP dialog.
  2. Select Outgoing.
  3. Review the activity.
  • For outgoing activity, if all that displays is NM:QUIT, Message Networking was not able to establish any connection with the remote machine:
    • If the remote machine uses an MTA, the MTA address might be incorrect on the Remote Machine Parameters page, or the MTA might be down.
    • The DNS for this domain might be configured incorrectly.
The MTA for the remote machine does not handle email for the address.
  1. Display Last SMTP Dialog.
  2. Select Outgoing.
  3. Review the activity.
  • For outgoing activity, if there is a Remote: line that indicates that the MTA was unable to relay the message for the address:
    • The MTA address might be incorrect on the Remote Machine Parameters page, or the MTA might be down.
    • The MTA might not be configured to handle email for that address.

Latin American Spanish voice or text prompts are in Castilian Spanish

Possible cause
Action
Probable fix
The language ID used by Modular Messaging Release 2 for Latin American Spanish is the same as the language ID used by Modular Messaging Release 3 for Castilian Spanish.

If both a Modular Messaging Release 2 system and a Modular Messaging Release 3 system are connected to the same Message Networking system, and the Modular Messaging Release 2 system sends an LDAP update that includes language IDs for subscribers using Latin American Spanish, those subscribers' Language IDs will be incorrectly set for Castilian Spanish on the Message Networking system.

Verify the language ID of the subscriber experiencing the issue.
Correct the Language ID of the subscriber experiencing the issue.

 

Top of page

Home | Search | Print | Back | Fwd | Close
©2006 Avaya Inc. All rights reserved.
Last modified 14 April, 2006