Avaya Message Networking Help

Transcription

1 1of 27 Avaya Message Networking Help Home Search the Help Print Back Fwd Close Getting Started Admin Maintenance Reference Home > Reference > Printable Guides > Installation Printable Guide Installation Printable Guide This print guides is a collection of Message Networking Help system topics provided in an easy-to-print format for your convenience. Please note that some of the procedures link to tasks that are not included in the PDF file. The online system contains all Message Networking documentation and is your primary source of information. This printable guide contains the following topics: Topic Page Number Installation checklist 1 Review installation prerequisites 2 Gather required tools and materials 6 Verify initial switch and LAN administration 6 Review demarcation points 7 Maintaining system security during installation 8 Connect peripheral devices 8 Connect the Analog-line interface cards 9 Connect the LAN cables 10 Restore power to the system 10 Log into the system from the console 11 Install switch connection software 11 Check voice, modem, and network addressing 12 Initial administration checklist 15 Perform acceptance testing 16 Installation checklist This installation checklist provides descriptions of the required procedures, in sequence, to use when you install an assembled, loaded, and tested (ALT) Avaya Message Networking system. You can use the Installation Printable Guide for the Message Networking that includes all of the first-time installation processes in order. Note: If you need to install a feature for the customer on an ALT system, contact your project manager to verify the requirements, and then contact your remote support center. The following table provides a checklist for system installation. Task Description Comments and links 1. Review Installation planning and prerequisites. This section includes: General precautions

2 Site preparation Environmental considerations Installation area considerations Weight and space considerations Power requirements 2. Gather the required tools and materials. 3. Verify initial switch and LAN administration in preparation for the new system. Switch connection is only required on analog systems. 4. Review demarcation points. All systems, application dependent. 5. Review security issues. All systems. 6. Unpack and check the shipment contents. 7. Place the chassis in the designated operating area. Ensure sufficient air space around it, and turn the stabilizing feet out to the side. Open boxes as instructed to reuse packing materials. Note: If stabilizing feet have not been installed, use a Phillips screwdriver to fasten the four stabilizing feet to the bottom of the chassis. 8. Connect peripheral devices. This includes monitor, keyboard, and modem. 9. Connect the analog-line interface cards (voice cards). This step is required for Message Networking systems using analog. 10. Connect the LAN cable. 11. Restore power to the system. 12. Log into the system from the console, and check the monitor display. 13. Install the switch connection software. 14. Check voice system, modem, and network addressing. 15. Perform Initial system administration. System status Install modem/terminal software Network addressing Follow the initial system administration procedure for a complete listing of pages and screens to be completed. 16. Perform System acceptance testing. Installation prerequisites This topic covers the following items: Intended audience 2of 27

3 Safety and security alert labels General precautions Site preparation Environmental considerations Installation area considerations Weight and space considerations Power requirements Shipment contents Saving packing materials Intended audience This topic is intended primarily for the on-site technical personnel who are responsible for installing the system and performing initial administration and acceptance testing. However, the general precautions are intended for both installers and system administrators. Safety and security alert labels This topic uses the following symbols to call your attention to potential problems that could cause personal injury, damage to equipment, loss of data, service interruptions, or breaches of toll fraud security. Caution: Indicates the presence of a hazard that, if not avoided, can or will cause minor personal injury or property damage, including loss of data. Warning!: Indicates the presence of a hazard that, if not avoided, can cause death or severe personal injury. General precautions Note: The following applies for Message Networking installations in Sweden, Finland, and Norway only. Message Networking system relies on a ground connection through the main plug with an earth contact. Because of unreliable earthing concerns in Sweden, Finland and Norway, Message Networking must be installed by service personnel in a restricted access location. A restricted access location is defined as a location to which access can be gained only by service personnel or customers who have been instructed about the reasons for the restricted access and any safety precautions that must be taken. In these cases, access to the Message Networking system is gained by the use of a tool (such as a lock and key) or other means of security. Caution: Lithium battery(ies) are included with this system. Do not puncture, mutilate, or dispose of battery(ies) in fire. Danger of explosion if battery is incorrectly replaced. Replace only with the same or equivalent type recommended by manufacturer. Dispose of used batteries in accordance with the manufacturer's instructions and your local regulations. ATTENTION: Il y a danger d explosion s IL y a remplacement incorrect de la batterie. Remplacer uniquement avec une batterie du même type ou d un type équivalent recommandé par le constructeur. Mettre au rebut les batteries usagées conformément aux instructions du fabricant. Site preparation This section describes physical requirements for the installation site, which include: Environmental considerations Installation area considerations Weight and space considerations Power requirements 3of 27

4 Environmental considerations Place the Message Networking system in an area where the environmental conditions shown in the following table are maintained. Operating state Temperature Humidity Operating Non-operating (in storage or being shipped) +10 to +35ºC (+50 to +95ºF) -20 to +60ºC (-4 to+140ºf) 20 to 80%, noncondensing 20 to 80%, noncondensing Installation area considerations Caution: Observe the following when determining where to place the Message Networking system: Use only the power cord assembly provided to connect the Message Networking to an AC main outlet. Install the Message Networking system within 6 feet (2m) of a grounded AC main outlet. Do not use extension cords with the Message Networking system. Ensure that the AC main outlet to be used to power the Message Networking system (via the power cord) is a grounded outlet. If you are unsure of the ground integrity of the outlet, have a trained and certified electrician check the outlet. Consideration must be given to the connection of the Message Networking system to a branch circuit with respect to overload or overcurrent protection. Check the Message Networking ratings to ensure that, together with other equipment connected to the same branch circuit, an overcurrent or overload condition does not exist. Maintain an air-distribution system that provides adequately cooled, filtered, and humidity-controlled air. Do not install the Message Networking system such that the ventilation or fan openings will be blocked. Note: The following applies for Message Networking installations in Sweden, Finland, and Norway only. Message Networking relies on a ground connection through the main plug with an earth contact. Because of unreliable earthing concerns in Sweden, Finland and Norway, the Message Networking must be installed by Service Personnel in a restricted access location. A restricted access location is defined as a location to which access can be gained only by service personnel or customers who have been instructed about the reasons for the restricted access and any safety precautions that must be taken. In these cases, access to the Message Networking is gained by the use of a tool (such as a lock and key) or other means of security. Weight and space considerations The following table lists the approximate weight, height, width, and depth of each system. Weight Height Width Depth 29 lb (13 kg) 19 in. (49 cm) 9 in. (23 cm) with stabilizing feet 18 in. (46 cm) Add 3 inches (7.6 cm) to accommodate a rear chassis cable support bracket. If required, add 4 inches (10.2 cm) to accommodate a 356B adapter and mounting clip. 4of 27

5 The following table lists the approximate weight, height, width, and depth for the monitor and keyboard. Peripheral Weight Height Width Depth Monitor 27 LB (12.2 kg) 14 in. (35 cm) 14 in. (36 cm) 15.4 in. (39 cm) Keyboard 5 LB (2.3 kg) 2.5 in. (6.4 cm) 19 in. (48 cm) 8 in. (20.5 cm) A monitor is not necessarily ordered and shipped for each system. The weight and space considerations listed are for those shipments that include a Sampo 15-inch monitor. Power requirements The following table lists the power requirements for the system. Attribute Requirement Volts AC (VAC) Hertz (Hz) 60 Phase Amps (US) AMPS (International) Input cords Unit input receptacles Maximum Power Output Heat Dissipation Single 5A (maximum) NEMA 5 15P plug; 6 ft (2 m) long IEC320 inlet 200 W 682 BTU In addition to the above power requirements, you must also: Locate each unit within 6 feet (2 meters) of its power receptacle. Keep the communication cables separate from the power cables. Install communication and power cables in accordance with National Electrical Codes (NEC). Caution: Use only shielded cables and equipment with the system to maintain safe levels of electromagnetic compatibility. Shipment contents The customer should have received boxes containing the computer, keyboard, and monitor (if ordered). Be sure that you have the following items packed in the box or boxes: The chassis. Turn out the stabilizing feet on the bottom of the computer case. One 6-foot to 8-foot (2-meter to 3-meter) power cord (depending on country in which you are doing the installation) The keyboard with onboard mouse and split connector cord One 4-pin RJ-11 cable for each voice port purchased One LAN cable 5of 27

6 One monitor and power cord, if ordered One maintenance modem and required cables Saving packing materials Save the shipping carton and all packing materials to use in case you have to return the system to the manufacturer. If you ordered multiple systems, saving one carton and one set of packing materials should be sufficient. Packing materials include: Antistatic bags Cardboard and foam inlays Note: The packing materials can also include a plastic bag designed to protect the system from moisture during shipment. Discard this bag. It is not reusable. Also save the shipping cartons for the keyboard and monitor. Gather required tools and materials This topic lists the tools, test equipment, installation worksheets, and documentation you must have to install and test the system. Tools The following tools are recommended for installing the system: A medium-width flat blade screwdriver A No. 2 Phillips screwdriver A small pair of needle nose pliers A small pair of wire cutters A sharp, pointed instrument such as a ballpoint pen Caution! Do not use the point of a lead pencil. The graphite can damage a circuit card and cause problems such as electrical shorts. Test equipment Use the following test equipment when you install a system: A volt/ohm meter. Two telephones that are connected through the switch, if the Message Networking system requires analog. The two test telephones must be placed so that you can easily see the monitor while you are using them. Installation worksheets Your project manager or systems consultant will give you a series of worksheets prior to the installation. These worksheets have been completed with input from the customer. Documentation Use the Message Networking online Help and documentation CD during installation of a system. The Message Networking documentation provides information on installation prerequisites and procedures necessary to perform hardware installation, initial administration, acceptance testing, and troubleshooting. Verify initial switch and LAN administration This topic describes the switch and LAN administration that must be done before you arrive on site. 6of 27

7 Initial switch administration Note: Switch administration is required for Message Networking systems supporting analog. Before you begin the installation, the switch at the customer site must be administered to support the following situations: You must be able to test each channel connected to the Message Networking system before assigning the channels to Message Networking or another application. During this testing, you must be able to call each channel individually using the ChanTran option. You must be able to test the Message Networking system with two test subscribers. To use analog ports, a hunt group must be assigned with a number of stations, in the right order, equal to the number of analog ports that you require for Message Networking. The pilot number of the hunt group must be DID and must be restricted. Before you arrive on site, all of the initial switch administration must be complete unless otherwise specified by contract. Verify that this initial switch administration is complete before you begin work on the Message Networking system. Initial LAN administration Determine if you need to notify the LAN administrator to arrange for administration of the LAN for the system. Some LANs may be administered prior to your arrival on site. Other LANs require that the administration for a new machine be done at the time of installation because an open connection may cause the LAN to fail. Note: Avaya is not responsible for the installation, administration, or test of communications between customer PCs and the LAN. Review demarcation points A demarcation point defines the extent of Avaya's responsibilities for a product. Beyond this point, the customer is responsible for providing overall service. Generally, Avaya is responsible for all Avaya-provided equipment. When installing a Message Networking system, you must be aware of the demarcation points for: Switches not maintained by Avaya LAN connectivity Demarcation points for switches not maintained by Avaya Avaya service technicians dispatched for Message Networking system installation are not responsible for making any direct connections to switches not maintained by Avaya. Note: Avaya recommends joint acceptance testing for systems integrated with switches that are not maintained by Avaya. For additional information concerning the extent of the installation, see the contract between the customer and Avaya. Demarcation point for LAN connectivity The demarcation point for the TCP/IP is the point of connection into the LAN circuit card. The customer is responsible for: The LAN cable The connector at the end of the cable for connection to the Message Networking system LAN administration not performed on the Message Networking system Maintenance of the TCP/IP addresses and administration of the Message Networking system after 7of 27

8 cutover, unless otherwise specified by contract The IP address, subnet mask, and gateway information for administration on the Message Networking system Avaya service technicians dispatched for Message Networking system installation are not responsible for troubleshooting the customer's LAN. Maintaining system security during installation During an installation, security of the customer's system is your responsibility. You must take the following precautions to protect: Password security System security Password security To protect password security: Change the passwords for the sa, icftp, and craft logins before you begin the verification and acceptance of the Message Networking system. Do not leave written passwords laying out or allow anyone to see them. At the first opportunity, give the passwords directly to the customer's designated representative. If you suspect that the security of any password has been compromised, notify your project manager or system administrator. System security To protect system security during the installation: Remove all test subscribers and test mailboxes from the system when the procedures instruct you to do so. Always log off the system if you will be leaving it unattended, even for a short period of time. Tip: Unassigned mailboxes are mailboxes that have an extension, but no subscriber assignment. For additional information about system security, see Security. Connecting peripheral devices This section describes how to make the connections between the system and the following peripheral devices: Monitor Keyboard and mouse Modem Connecting the monitor A monitor is available for purchase for use with the Message Networking system or the customer can supply a monitor. Two cables connect the monitor to the system: Video cable connector: The video cable connector has a video input connector at one end. The other end of the cable is permanently attached to the monitor. Power cable: The power cable for the monitor connects to a standard AC outlet. To connect the monitor cables: 1. Plug the video cable connector from the monitor directly into the video connector located on the back of the chassis. 2. Tighten the thumbscrews on the video cable connector with your fingers or with a small flat blade 8of 27

9 screwdriver. 3. Plug the female end of the power cable into the monitor. 4. Plug the male end of the power cable into a grounded AC outlet. Connecting the keyboard and mouse A purple, 6-pin female DIN receptacle is located in the back of the system. The male plug is provided with the keyboard. Both of the connector assemblies are keyed to provide proper alignment. The mouse provided with the Message Networking system is onboard the keyboard. The connector for the provided mouse splits off from the keyboard cable. A female DIN receptacle is located in the back of the system, next to the keyboard receptacle. The mouse receptacle is green. If the customer chooses, the customer can provide a standard mouse and plug the mouse cable into the mouse receptacle. Connecting the modem A serial modem is provided with Message Networking for remote maintenance. Complete the following procedure to connect the serial modem to the Message Networking system. After you connect the modem, you must install the modem in the Message Networking web-based interface. Note: A USB modem is also available for purchase with the system. If you are using a USB modem or a customer-supplied serial modem, follow the manufacturer's instructions to connect the modem to the system. Then use the Install Modem/Software page to install the Message Networking system modem software. To connect the supplied serial modem: 1. Verify that dip switches 3 and 8 are in the down position (this should be the default). If you want the ability to dial in to the modem, set dip switch 5 to the up position. If you do not want to allow dialing in to the modem, leave dip switch 5 in the down position. 2. Connect the 25-pin end of the provided 25-pin to 9-pin cable to the modem. A 25-pin extension cable is also provided for use if needed. 3. Connect the 9-pin end of the 25-pin to 9-pin cable to COM2 on the back of the Message Networking system. 4. Plug one end of an analog telephone cord into the TELCO jack on the modem. 5. Plug the other end of the analog telephone cord into an analog telephone jack. 6. Plug the modem's power supply into the modem's power jack and into an electrical outlet. 7. Turn on the modem's power and then verify that the light on the front panel of the modem is lit. Once the modem is connected, you must install it in the Message Networking system software. Activate the Modem instructs you to do that after you log in to the system for the first time. Connecting the Analog-line interface cards This topic provides the basic information you need to connect the analog-line interface cards installed in the Message Networking system to the switch. Analog-line interface cards are required on Message Networking systems using analog. The Message Networking system supports a maximum of three analog-line interface cards. Each card has four RJ-11 jacks on its bracket (see Back view of platform for reference); each RJ-11 jack supports one voice channel. The analog-line voice cards are installed from bottom to top beginning in slot 4 (the first three are blank) and are numbered as follows: The first installed board is in slot 4 (fourth slot from the bottom). The board's RJ-11 jacks support ports 1 through 4, numbered from right to left, which correspond to channels 0 to 3. The second installed board is in slot 5 (fifth slot from the bottom). The board's RJ-11 jacks support ports 5 through 8, numbered from right to left, which correspond to channels 4 to 7. The third installed board is in slot 6 (sixth slot from the bottom). The board's RJ-11 jacks support ports 9 through 12, numbered from right to left, which correspond to channels 8 to 11. 9of 27

10 Warning! Damage from electrostatic discharge is possible. See Protecting against ESD damage for more information. To connect the analog-line interface cards to the switch: 1. Plug a telephone cable into each RJ-11 jack on the first card. 2. Plug the other end of each telephone cable into the RJ-11 interface adapter from the switch wall field, circuit pack, or demarcation connector. 3. Repeat steps 1 and 2 for each installed card. Connecting the LAN cable To connect the LAN cable: 1. Shut down the system. Note: The LAN cable used must be a CAT5 cable. 2. Attach the LAN cable to the LAN connector on the Message Networking system. 3. Reboot the system. 4. Test the TCP/IP connection or, if you are done, click Return to Main. Restoring power to the system To restore power: 1. If necessary, attach the power cord and the monitor cord to the system. 2. Plug the power cord into the PC's power outlet (see Back view of platform). 3. Turn on the monitor's power switch. The power lamp on the monitor should be lit. 4. Press the power button on the front of the PC. The green lamp on the front of the PC should be lit. 10 of 27

11 Logging into the system from the console This topic assumes that the system just arrived from the factory and you have cabled the components together, or that you have successfully installed or updated the system software. To log in to the system from the console: 1. After you have powered up the machine, at the console, log in as craft or sa with the corresponding default password. When prompted, change the default password. 2. As soon as you log in, the system displays the Netscape browser with the Administration menu. If you have logged in with the highest access, rather than craft, sa, or icftp, type webadmin to display the web-based administration pages. Once you log in, verify that the monitor displays system information well enough to do initial administration. If the Sampo Alphascan 511 monitor isn't purchased with the system, any 15" or greater monitor can be connected and will function properly, although some additional configuration steps may be necessary. If the display is poor, perform the following process after powering up: 1. Log off of the console. If the display is so poor that you cannot see the mouse pointer well enough to exit or log off, you can exit by pressing Ctrl+Alt+Backspace simultaneously. 2. Log in at the console as monitor with the password of monitor. 3. On the text-based display, look for the name of the monitor you are using. Use the down arrow or PageDown keys to scroll through the list of many available monitors, or try typing the first letter of the brand name. 4. Use the Tab key to move between the menu and the buttons, if necessary. 5. Highlight the name of the monitor that most closely matches the customer's monitor, and then press Enter. The monitor screen flashes during testing and adjusting, and then the cursor returns to the login prompt. 6. Log in to the system with craft or sa, as appropriate, and see if the display has improved. 7. If the display is still poor, relogin as monitor, and select the Generic monitor setting, which is the first one on the list. 8. If there is still no improvement, the customer must supply a different monitor. Install switch connection software This topic provides information on installing the software required to support the connection between the switch and the Message Networking system. Note: You can only have one switch connection software package installed on the system at one time. If one package is already installed and you want to install a different package, you must remove the first package before installing the second package. To install switch connection software: 1. Log on as craft (for a new installation) or sa (if restoring a system). 2. Start at the Administration menu, and select Utilities > Software Management > Software Installation. 3. Switch connection software is included on the Message Networking software CD. Obtain the CD, then follow the on-screen instructions to insert the CD. 4. Click CD (or another installation media if applicable). 5. The system warns you that system data should be backed up. If necessary, perform a system backup. If the system is new, no data needs to be backed up. The system displays a list of packages available on the CD, including the two switch integration packages: SWINSet and LANSet. The following table lists the supported switches provided in each switch integration package. LANSet Switch connection package Switch System 75/DEFINITY System 85/DEFINITY 11 of 27

12 SWINSet NEC NEAX 240 Rolm 8000, 9000, 9751 Nortel Telecom SL-1 Nortel Telecom Meridian-1 Nortel Telecom Meridian-SL1 Mitel SX ESS DMS Select the switch integration package you want to install. 7. Press PageDown to see the bottom of the page, and click Install selected packages. The system displays a list of packages to be installed. 8. Review the list, then click Proceed with installation. The system begins the installation and displays installation status messages. The installation is complete when the pointer changes from a wristwatch to an X. 9. After the software is installed, press PageDown to see the bottom of the status page. 10. If the software was installed successfully, remove the CD from the CD drive. 11. Click Restart the System. After the system restarts, it displays the message: Press Enter to return to prompt Press Enter, then log in. 13. If the system is to be moved or shipped, stop the voice system and power off the system. If system data is to be restored, go to Performing a restore. Note: During system administration, you will select the switch connected to the Message Networking system and perform switch administration. Checking voice, modem, and network addressing This section assumes that the system just arrived from the factory and you have cabled the components together, or that you have successfully installed or updated the system software. If you need to install or updated software, select Installation information for Message Networking under Getting Started from the Message Networking Index and then select the appropriate installation procedure. Checking the voice system status The voice system automatically starts, but make sure that it is running. You can view the system status, which includes information on the state of the voice system. To view system status: 1. Start at the Administration menu and select System Configuration and Status > System Status. After a short wait, the system displays the System Status page. 2. Scroll down the System Status page to verify that the voice system (messaging software) is running. Look for the entry "Voice System is Up." If the voice system is not up, start the messaging software by selecting Utilities from the main menu. 3. Click Return to Main to return to the Administration menu. 12 of 27

13 Activating the modem 1. Log in to the system with the craft login and password. 2. Start at the Administration menu and select Basic System Administration > Modem and Terminal Administration > Install Modem/Terminal Software. The Install Modem/Terminal Software page displays. 3. Complete the fields for the modem you are installing. See the online Help for additional information about each field. 4. Click Save at the bottom of the page. Notes: Alarm origination can only be set up on the COM2 port, so this port must be activated before you perform alarm management. If you purchase the Avaya Communication Manager Fault and Performance Manager, you must configure the Install Modem/Terminal Software page to comply with the MFPM modem as follows: Select Other in the Modem Type field. Select 9400 in the Speed field In the Modem Init String field, enter the following (entry is case-sensitive; all 0's are zeros): AT&F&M0Q2&C1&D2&R1&H0&U2&N2&K0S0=0S13=1Y0&W0 Establishing network addressing settings 1. Log in to the system as craft or sa. 2. Click Accept to accept the Netscape license agreement. 3. Start at the Administration menu, and select Basic System Administration > TCP/IP Administration > Network Addressing. 13 of 27

14 4. Complete the Network Addressing page using information from the configuration notes or the system administrator. See the online Help for additional information about each field. 5. Click Save at the bottom of the Network Addressing page. Note that the format of the Network Addressing page is slightly different on the console interface. For example, instead of a radio button with a dot to indicate DNS, the field is a color-shaded diamond. Accessing the Web-based administration pages After you configure the system's network addressing settings, you can access the system's Web-based administration: 1. From a separate system on the customer's LAN, use your favorite browser to enter the address where localhost is the name of the machine and localdomain is the name of the company's domain (for example, 2. Use the craft login (or sa if you are the system administrator) with the default password. 3. The first time you log in at the console, the system displays a Netscape license agreement. Click Accept to continue. 4. If you do not see the Avaya login page that asks for Login and Password, then make sure you have properly typed in the machine name. 14 of 27

15 As soon as you log in, the system displays the Administration menu in your browser. Perform initial system administration and acceptance testing Initial administration checklist The following table lists the procedures required for initial administration. The procedures appear in the sequence in which they are performed. Completed Task Verify feature options for the Message Networking system Administer the voice system Configure network addressing Administer the PPP server if you want to allow internal and external support teams to connect to the Message Networking system through a dial-up connection Administer the system parameters on the Message Networking system: Administer general system parameters Administer rescheduling parameters Administer serenade digital parameters Administer the switch connected to the Message Networking system. Add remote machines: Add a new INTUITY 4.0 or later remote machine Add a new AMIS Analog remote machine Add a new Aria Analog remote machine Add a new Serenade Analog remote machine Add a new Octel 100 remote machine Add a new UM Analog remote machine Add a new Aria Digital remote machine Add a new Serenade Digital remote machine Add a new VPIM remote machine Add a new SMTP/MIME Unified Messenger remote machine Add a new Avaya Modular Messaging remote machine Add a new Avaya Message Networking remote machine Add a new SMTP/MIME other remote machine Administer the Dial Plan Mapping for each remote machine Administer the AMIS Analog timing parameters Administer SMTP/MIME security Administer remote machine Directory Views Verify Message Networking administration: View the Remote Machines List View the Remote Machines Dial Plan List 15 of 27

16 Administer the Message Networking as a remote machine on each remote machine Perform connectivity tests Turn on remote updates Demand Remote Update and Demand Remote Push from applicable remote machines Verify the success of the Demand Remote Update and Demand Remote Push: Monitor the Octel Analog Networking Remote Updates Verify the Demand Remote Push through the remote machine Subscriber Reports. For more information, see the corresponding Octel Analog Networking remote machine Subscriber Reports documentation. Administer subscribers Change the sa password; also change the icftp password if you are using FTP Caution! It is critical that you change the sa password from the default to avoid unauthorized access to the system. Administer alarm management to activate alarm origination Perform acceptance testing Perform an attended backup Perform acceptance testing This topic provides the acceptance test procedures specific to the Message Networking system. You should complete acceptance testing after completing initial system administration Acceptance test procedures include: Testing voice ports Calling Message Networking ports Testing remote machine connectivity between the Message Networking system and remote machines Performing demand remote updates pull the subscriber ASCII names and voiced names from the remote machines onto the Message Networking system Sending a test message to a remote subscriber Testing voice ports To test a voice port without removing the analog-line interface card from service: 1. Start at the Administration menu, and select Diagnostics > Voice Equipment Diagnostics > Voice Port Loop Around Test. The system displays the Voice Port Loop Around Test page. 2. Complete the fields on the page. For information about the fields on this page, click Help. 3. Click Test. The system completes the diagnostics and displays the Voice Port Loop Around Test Results page. The results page indicates whether each test passed or failed. The result not tested appears next to any test you did not select under Test Type on the Voice Port Loop Around Test page. 4. Click Return to Main to return to the Administration menu. 16 of 27

17 Calling Message Networking ports To verify that the Message Networking ports are all functioning properly, dial each port individually to make sure that Message Networking answers. Testing remote machine connectivity This topic provides information on remote machine connectivity acceptance testing for Message Networking. Perform these tests after you complete Message Networking initial administration to verify remote machine connectivity. The following remote machine connectivity tests are available for Message Networking: AUDIX Digital Test Analog Test Aria Digital Test Serenade Digital Test SMTP Test LDAP Test Display Last SMTP Dialog AUDIX Digital test This topic provides information on testing connectivity to AUDIX Digital remote machines. You should perform this test as part of acceptance testing after you perform initial administration. To test connectivity between the Message Networking and an AUDIX Digital remote machine: 1. Start at the Message Networking Administration menu, and select Remote Machine Administration > Test Connections > AUDIX Digital Test. The system displays the AUDIX Digital Test page. 2. From the Remote Machine Name menu, select the name of the remote machine to which you want to test the connection. 3. Click Test. The system displays the results of the test: If the screen contains a message stating that the connection was successful, proceed to the next step. If the screen contains a message stating that the test failed, verify that the remote machine is administered correctly. 4. Click Return to Main to return to the Administration menu. Analog Test This topic provides information on testing connectivity to analog remote machines. You should perform this test as part of acceptance testing after you perform initial administration. To test connectivity between the Message Networking system and an analog remote machine: 1. Start at the Message Networking Administration menu, and select Remote Machine Administration > Test Connections > Analog Test. The system displays the Analog Test page. 2. From the Remote Machine Name menu, select the name of the remote machine to which you want to test the connection. 3. Click Test. The system displays the results of the test: 17 of 27

18 If the screen contains a message stating that the connection was successful, proceed to the next step. If the screen contains a message stating that the test failed, verify that the remote machine is administered correctly. 4. Click Return to Main to return to the Administration menu. Aria Digital test This topic provides information on testing connectivity to Aria Digital remote machines. You should perform this test as part of acceptance testing after you perform initial administration. To test connectivity between the Message Networking system and an Aria Digital remote machine: 1. Start at the Message Networking Administration menu, and select Remote Machine Administration > Test Connections > Aria Digital Test. The system displays the Aria Digital Test page. 2. From the Remote Machine Name menu, select the name of the remote machine to which you want to test the connection. 3. Click Test. The system displays the results of the test: If the screen contains a message stating that the connection was successful, proceed to the next step. If the screen contains a message stating that the test failed, verify that the remote machine is administered correctly. 4. Click Return to Main to return to the Administration menu. Note: If you experience problems communicating with an Aria Digital remote system, see Remote machine connection troubleshooting. Serenade Digital test This topic provides information on testing connectivity to Serenade Digital remote machines. You should perform this test as part of acceptance testing after you perform initial administration. To test connectivity between the Message Networking system and a Serenade Digital remote machine: 1. Start at the Message Networking Administration menu, and select Remote Machine Administration > Test Connections > Serenade Digital Test. The system displays the Serenade Digital Test page. 2. From the Remote Machine Name menu, select the name of the remote machine to which you want to test the connection. 3. Click Test. The system displays the results of the test: If the screen contains a message stating that the connection was successful, proceed to the next step. If the screen contains a message stating that the test failed, verify that the remote machine is administered correctly. 4. Click Return to Main to return to the Administration menu. Note: If you experience problems communicating with an Serenade Digital remote system, see Remote machine connection troubleshooting. SMTP test This topic provides information on testing connectivity to SMTP remote machines. You should perform this test as part of acceptance testing after you perform initial administration. 18 of 27

19 To test connectivity between the Message Networking system and an SMTP remote machine: 1. Start at the Administration menu. and select Remote Machine Administration > Test Connections > SMTP Test. The system displays the SMTP Test page. 2. From the Remote Machine Name menu, select the name of the remote machine to which you want to test the connection. 3. Use the Sender and Recipient fields to optionally specify sender and recipient addresses to use for the test. 4. If you want a test text message to be sent, select Yes in the Send a text test message field. 5. Click Test. The system displays the results of the test: If the screen contains a message stating that the connection was successful, proceed to the next step. If the screen contains a message stating that the test failed, verify that the remote machine is administered correctly. 6. Click Return to Main to return to the Administration menu. LDAP test This topic provides information on testing connectivity for LDAP. You should perform this test as part of acceptance testing after you perform initial administration. To test connectivity between the Message Networking system and a remote machine using LDAP: 1. Start at the Message Networking Administration menu, and select Remote Machine Administration > Test Connections > LDAP Test. The system displays the LDAP Test page. 2. From the Remote Machine Name menu, select the name of the remote machine to which you want to test the connection. 3. Click Test. The system displays the results of the test: If the screen contains a message stating that the connection was successful, proceed to the next step. If the screen contains a message stating that the test failed, verify that the remote machine is administered correctly. 4. Click Return to Main to return to the Administration menu. Display Last SMTP Dialog Use this page to view the latest incoming or outgoing message exchange attempt between the Message Networking system and an SMTP/MIME remote machine. This page can help you: Determine the domain name of a remote SMTP/MIME machine, which is helpful when completing the Domain Name field during SMTP/MIME remote machine administration. If you are trying to capture the domain name of a remote SMTP/MIME machine, request that a subscriber on that remote machine send a message to the Message Networking system. You can then use this page to view the activity between the machines and identify the correct domain name. Troubleshoot incoming or outgoing messages to SMTP/MIME machines to determine why a message is failing. Note that only the most recent exchange between the Message Networking system and any SMTP/MIME remote machine is displayed. You cannot specify an individual remote machine for which you want to view an exchange. To view the latest incoming or outgoing exchange between the Message Networking system and an SMTP/MIME remote machine: 19 of 27

20 1. Start at the Administration menu, and select Message Networking Administration > Remote Machine Administration > Test Connections > Display Last SMTP Dialog. The system displays the Display Last SMTP Dialog page. 2. From the Display The Last SMTP Dialog For menu, select whether you want to view the last Incoming Side (from an SMTP/MIME remote machine to the Message Networking system) or Outgoing Side (from the Message Networking system to an SMTP/MIME remote machine) exchange between Message Networking and an SMTP/MIME remote machine. 3. Click Display. The system displays the most recent inbound or outbound exchange between Message Networking and an SMTP/MIME remote machine, depending on the direction you selected. Lines beginning with Message Networking denote activity by the Message Networking system. Lines beginning with Remote denote activity by the SMTP/MIME remote machine. 4. Review the activity captured on the page: If you selected Incoming Side and are trying to determine the domain name of the remote SMTP/MIME machine, look for the line that displays the address of the subscriber who sent the incoming message. The portion of the subscriber's address after is the domain name for that SMTP/MIME remote machine. You should enter this domain name in the Domain Name field on the Remote Machine Parameters page. If you are attempting to troubleshoot the failure of an incoming or outgoing message, look for the line that displays the reason for the message failure. 5. Click Return to Main to return to the Administration menu. Performing remote updates This topic provides information on performing remote updates. These functions are used primarily at the time of system installation and should be executed only after installation or after a significant number of subscribers have been added. Do not perform this procedure during prime system hours. The two types of remote updates are as follows: Demand Remote Update allows subscriber records, including ASCII and voiced names, to be pulled over from INTUITY AUDIX, DEFINITY AUDIX, Serenade Analog, IP600, Aria Digital, DEFINITY ONE, Message Networking, and Avaya Modular Messaging (MM) remote machines on to the Message Networking system. Demand Remote Updates are only used for INTUITY AUDIX, DEFINITY AUDIX, IP600, Aria Digital, and DEFINITY One systems. Demand Remote Updates are not supported for Serenade Digital, Unified Messenger, Aria Analog, AMIS Analog, VPIM V2, or other SMTP remote machines. Demand Remote Push allows subscriber records, including ASCII and voiced names, to be pushed from an Avaya Message Networking to Octel Analog Networking or Aria Digital and Serenade Digital remote machines. Demand Remote Push updates are not supported for Octel 100, VPIM v2, INTUITY AUDIX, and SMTP/MIME, including Avaya Modular Messaging and Avaya Message Networking remote machines. Note: NameSend is the recommended procedure to use for updating names in Aria Digital and Serenade Digital. Names can be updated by range or by using the option for all. The following tasks are associated with remote updates: Turning on remote updates Performing a Demand Remote Update Performing a Demand Remote Push Monitoring AUDIX Digital remote updates Monitoring analog remote updates Monitoring Octel Analog Networking remote updates Monitoring Aria Digital remote updates Monitoring Serenade Digital remote updates Monitoring SMTP port activity 20 of 27

21 The following table summarizes the cases in which subscriber updates occur automatically for each type of remote machine. Protocol Remote machine updates Message Networking Message Networking updates remote machine AMIS N/A for adds and changes. N/A AUDIX Digital VPIM V2 Digital Octel Analog Networking When Message Networking attempts to deliver to a nonexistent subscriber on an AMIS remote machine, it fails the messages and deletes that subscriber from the Message Networking directory. When a subscriber is added, changed or deleted through administration, the Message Networking system is automatically notified. An update only occurs from a VPIM V2 machine to the Message Networking system when the sender sends a message to the other system. It is the sender's information that is updated on the Message Networking system. This functionality is determined by the remote machine. When Message Networking delivers a message to the remote machine, it does an ASCII match of the recipient (if ASCII Name Confirmation is set to Yes). If the recipient does not match, it fails the message and immediately requests a pull from the remote machine (when Updates In is set to Yes for that remote machine on the Remote Parameters page in Message Networking and the remote remote machine itself is administered for remote updates). If the ASCII name is a default on the Message Networking system, a comparison is not performed by Message Networking, the message is delivered, and the pull is immediately requested (when Updates In is set to Yes for that remote machine on the Remote Parameters page in Message Networking and the remote machine itself is administered for remote updates). If the subscriber does not exist on the remote machine but does on the Message Networking system, then the When Message Networking detects an add, change or delete of a subscriber, it pushes out the update to the AUDIX Digital remote machine. An update only occurs to a VPIM V2 machine when the sender sends a message to the other system. It is the sender's information that is updated on the receiving system. The update also includes the voiced name, if the subscriber has recorded it and if it is sent with the VPIM message. In addition, the update includes the alphabetic name for addressing alphabetically. This functionality is determined by the remote machine. When the remote machine delivers a message to the Message Networking system, it does an ASCII match on the recipient. If the recipient does not match, it fails the message and deletes the entry; the next time that subscriber is messaged, it requests a pull from Message Networking. If the ASCII name is a default on the Message Networking system, Message Networking always accepts the message (that is, it does not perform a name comparison); the Message Networking system then schedules a name pull. If a subscriber does not exist on the Message Networking system and that subscriber sends a message through Message Networking, the Message Networking system adds the subscriber as a default and then schedules a name pull. When Message Networking detects an add or change (not a delete) of a subscriber, it pushes out the update. 21 of 27

22 message is failed. The Message Networking defaults the ASCII name and nulls the voiced name of the subscriber. For any name pull to work, the remote machine must be set to Protocol Level 2 or 3. Aria Digital When Message Networking delivers a message to the remote machine, it requests that the remote machine perform an ASCII match on the recipient. If the recipient does not match, the remote machine fails the message, and Message Networking requests a pull from the remote machine. If the ASCII name is a default on the Message Networking system, a comparison is not requested, the message is delivered, and the pull is requested. If the subscriber does not exist on the remote machine but does on the Message Networking system, then the message is failed by the remote machine. Message Networking defaults the ASCII name and nulls the voiced name of the subscriber. Aria Digital can automatically push an add, change, or delete of a subscriber when the update occurs. When the remote machine delivers a message to Message Networking, the Message Networking system does an ASCII match on the recipient. If the recipient does not match, Message Networking fails the message and the remote machine deletes the entry; the next time that subscriber is sent a message, it requests a pull from the Message Networking system. When Message Networking detects an add, change, or delete of a subscriber, it pushes out the update. Serenade Digital When the Serenade Digital system delivers a message to the Message Networking system, it automatically pushes the sender's ASCII and voiced names (if the voiced name exists). The Serenade Digital system can automatically push an add or change, not a delete, of a subscriber when the update occurs. When Message Networking delivers a message to the remote machine, it does an ASCII match of the recipient (if the ASCII Name Confirmation flag is set to Yes). If the recipient does not match, Message Networking fails the message, defaults the ASCII name, and then nulls the voiced name. If the ASCII name is a default on the Message Networking system, a comparison is not performed, and the message is delivered. If the subscriber does not exist on the When Message Networking delivers a message to the Serenade Digital system, it automatically pushes the sender's ASCII and voiced names (done only when a voiced name exists). When Message Networking detects an add or change (not a delete) of a subscriber, it pushes out the update. When the remote machine delivers a message to the Message Networking system, it does an ASCII match on the recipient if addressed alphabetically. If the recipient does not match, the Serenade fails the message and deletes the entry. 22 of 27