Creating an Aria Domain R P/N

Transcription

1 Avaya Inc Murphy Ranch Road Milpitas CA (408) Part Number Creating an Aria Domain R P/N Purpose Affected Platforms Description Octel service personnel require the correct procedure for creating an Aria Domain. Octel Overturet 250 and 350 message servers. This instruction describes the procedure for creating an Aria Domain that includes up to six Octel Overture 250 and Octel Overture 350 message servers (also called servers) in any combination. No other products can be configured in an Aria Domain. Each server in the Aria Domain is called a domain node. Make sure that you follow this entire procedure on each domain node. Use the checklist at the end of this document to confirm that all steps have been completed on all domain nodes. Document Contents This document contains the following sections: - Setting Up Prerequisites - Identifying Aria Domain Nodes - Collapsing Nodes (to be performed as needed) - Setting Up Octel Digital Networking - Setting Up NameNet (to be performed as needed) - Converting FMFs (Follow-Me-Forward Mailboxes; to be performed as needed) - Modifying NameNet Entries - Setting Up the Aria Domain - Solutions for FMF Conversion Errors - Conversion Checklist Page 1 of 22

2 Setting Up Prerequisites Verify the following setup requirements on all servers to be included in the Aria Domain. Use the checklist at the end of this document to keep track of the requirements for all the domain nodes. 1. Before beginning this procedure, upgrade each domain node to Aria 2.X. Caution! Both software sides A and B must be at Aria 2.X. Refer to the appropriate 250 or 350 upgrade procedures in the Aria 2.0 Release Manual, P/N If you are performing a load balance on an Octel Overture 350 and configuring the resulting two servers in a domain, provide all system managers in the network with node-profile information for the new server. An Octel Overture 250 cannot be load-balanced. 2. On the system manager terminals for all servers to be included in the Aria Domain, use menu 13.7 to verify that the following required feature options are enabled. (A Y preceding the feature-option number indicates that it is enabled.) Networking Connectivity Octel Digital Networking In addition, NameNet must be enabled on a server before it can be added to an Aria Domain. 3. During this procedure, you will configure Octel Digital Networking and, if necessary, set up or modify NameNet parameters on all domain nodes in the Aria Domain. Refer to Volume IV of the System Manager Manual, Aria 2.0 before beginning this procedure. 4. Obtain or confirm the following subscriber information: - Confirm with the system manager that mailbox numbers and alias addresses are unique throughout all the servers to be included in the Aria Domain. - Confirm with the system manager that mailbox-number length is the same on all servers to be included in the Aria Domain. - If converting follow-me-forward mailboxes (FMFs) to NameNet entries, ask the system manager for the estimated number of FMFs created for each node on all servers to be included in the Aria Domain. - Ask the system manager whether NameNet is already set up on the servers to be included in the Aria Domain. NameNet must be enabled on a server before it can be added to the Aria Domain. Page 2 of 22

3 - The Call Sender feature is not operable for messages sent among domain nodes. Call Sender continues to work for subscribers within the same server. To provide a consistent interface to subscribers, you might want to disable the feature for all subscribers within the domain. To do so, enter N in the Call Sender: field in Menu 7 - Class of Service Profile, for all subscriber classes of service on every domain node. - Ask the system manager if calling groups are used in call-processing applications to restrict callers destinations. If they are, advise the system manager that calling groups do not restrict callers among servers within the domain. For example, a caller to server 1 is not restricted by calling groups from reaching a mailbox (or its associated extension) on server 2. - For any application such as ECP that allows a caller to leave a message in a type 0 mailbox, that mailbox must reside on the same node as the application, otherwise the mailbox will not be recognized. 5. If the Aria Domain is integrated with multiple networked switches, extension assignments must be unique throughout all the switches. For full functionality of the Aria Domain feature, all of the networked switches must support supervised transfers. Supervised transfers allow digits to be sent to indicate the called party (mailbox number) on another node within the Aria Domain. 6. Converting FMFs to NameNet entries is an optional step in creating an Aria Domain. During the FMF conversion on each server, subscribers recorded names are retrieved from the other nodes in the Aria Domain. The retrieval process can be lengthy, if many names are to be retrieved from each node. Therefore, schedule the FMF conversion to take place during low-traffic hours. 7. Call Detail Recordst (CDR) events are logged for every follow-me-forward mailbox that is converted to a NameNet entry and for every name-retrieval call during the NameNet setup. The CDR buffer can fill up rapidly and overflow during the FMF conversion. To prevent loss of data for PC/CDR or DecisionProt applications, download the CDR buffers from all servers to a PC/CDR or DecisionPro PC before beginning the FMF conversion. 8. If you need to collapse nodes, call the Octel Technical Assistance Center (TAC) to have the service bit enabled. If you do not need to collapse nodes, you do not need to have the service bit enabled. 9. You must have access to a printer when purging FMFs and converting them to NameNet directory entries. The FMFs that are deleted (or not deleted, and why) are recorded, using the printer. Page 3 of 22

4 Identifying Aria Domain Nodes You must configure all servers in the Aria Domain as domain nodes. That is, every server defined as a domain node on one server must also be defined as a domain node on all the other servers in the Aria Domain. On each server to be included in the Aria Domain, determine the following for the other domain-node servers: - Octel Networking node numbers - Node names - On-switch extension numbers that the server dials to transfer callers to other servers in the Aria Domain. (If necessary, consult the appropriate Configuration Note for your PBX integration.) - Node serial numbers Enter the appropriate information for each domain node in the following tables. Domain Node Server 1: Name or Location: Octel Networking Node Number Node Name Extension* * Used for Automated Attendant transfers to other servers within the domain. Domain Node Server 2: Name or Location: Octel Networking Node Number Node Name Extension* * Used for Automated Attendant transfers to other servers within the domain. Node Serial Number Node Serial Number Page 4 of 22

5 Domain Node Server 3: Name or Location: Octel Networking Node Number Node Name Extension* * Used for Automated Attendant transfers to other servers within the domain. Domain Node Server 4: Name or Location: Octel Networking Node Number Node Name Extension* * Used for Automated Attendant transfers to other servers within the domain. Domain Node Server 5: Name or Location: Octel Networking Node Number Node Name Extension* * Used for Automated Attendant transfers to other servers within the domain. Domain Node Server 6: Name or Location: Octel Networking Node Number Node Name Extension* * Used for Automated Attendant transfers to other servers within the domain. Node Serial Number Node Serial Number Node Serial Number Node Serial Number Page 5 of 22

6 Collapsing Nodes If multiple node profiles on one server in the domain point to another single server in the domain, the multiple nodes must be collapsed into a single node. For example, if nodes 20, 21, 22, and 23 on server 1 all point to a server named CAMPUS-A, nodes 21, 22, and 23 must be collapsed into node 20 on server 1. Collapsing existing nodes consists of the following two major steps: 1. Emptying network-message queues 2. Running the Collapse Nodes utility Use the procedures in the following sections to collapse nodes on each domain node that has multiple node profiles pointing to another domain node. If you do not need to collapse nodes, proceed to the next section, Setting Up Octel Digital Networking. 1. Empty the network-message queues for the nodes that will be collapsed, and for the node that will remain. For example, if network nodes 1, 2, and 3 point to a single server, and you are collapsing nodes 2 and 3 into node 1, empty the network-message queues for all three nodes. On one of the servers to be included in the domain, empty the networkmessage queues for all nodes to be collapsed, as follows: 1.1. Log into the system manager terminal (SMT) From the Main Menu, access Menu 15 - Network Management Enter 1 to select the Octel Networking Administration menu (menu 15.1) Enter 5 to select List Valid Node Numbers on the Network (menu ) Enter 0 at the Select Node: field to display all nodes Enter 9 at the Select Message Queue: field to display all messages in the queue Identify the multiple nodes pointing to another single server in the domain, and write down their node numbers. Note whether they have network messages queued for delivery. On this server, repeat this step for every other server in the domain Press Ctrl+C to return to the Octel Networking Administration menu (menu 15.1) Enter 3 to select the Node Profile menu (menu ) For each domain node that has messages queued for delivery, perform the following: Page 6 of 22

7 Enter the node number for the domain node Enter 2 from menu to access the Weekday Schedule menu (menu ) Set up a weekday delivery window with the following parameters. If all five windows are already established, write down the current parameters of one window, then modify that window. Begin: 8:00a End: 8:00a Interval: 0 - Immediate Priority: A - Administrative Message Press Send to save the new weekday delivery schedules Press any key to return to the Node Profile menu (menu ) Enter 3 to access the Weekend Schedule menu Set up a weekend delivery window with the same parameters as for the weekday delivery window (step ). If all five windows are already established, write down the current parameters of one window, then modify that window Press Send to save the new weekend delivery schedules Press any key to return to the Node Profile menu (menu ) On this server, repeat steps through for every other domain node with multiple node profiles that has messages queued for delivery Return to the List Valid Node Numbers on the Network screen (menu ) periodically to monitor the network-message queues to the nodes When the network-message queues are empty, use the following procedure to prevent additional network messages from being queued for the nodes: From the Octel Networking Administration menu (menu 15.1), enter 3 to access the Node Profile menu (menu ) and change the node profiles Enter the node number for the first node to be collapsed in the Node Number: field Select 1 for the Change Node Profile menu (menu ) Change the Transmission Type: field to 2 -Disabled/Msgs Returned. Page 7 of 22

8 Press Send twice to save the modified node profile Press any key to return to the Node Profile menu (menu ) On this server, repeat steps through for all nodes you are collapsing Delete the weekday and weekend schedules set up in step If schedules were modified rather than added, reenter the schedules previous values. 2. The Collapse Nodes utility consolidates Octel Networking node profiles that contain the same serial numbers and numbers of mailbox digits into a master node profile, if the total number of prefixes in the master node and nodes to be collapsed is 200 or fewer. The utility then deletes the unneeded node profiles. Use the following guidelines to run the Collapse Nodes utility: - The utility takes the server off line; no calls can be processed while it is running. - Run the utility on only domain nodes (the servers to be included in the Aria Domain), and only where the domain nodes have multiple node profiles set up to another domain node. - Network-message queues for the nodes that are being collapsed must be empty. To verify that the queues are empty, refer to step 1 on page 6. Do not run the Collapse Nodes utility without verifying that the networkmessage queues are empty. Run the Collapse Nodes utility as follows: 2.1. Log into the SMT Access the debug prompt (>) in one of the following ways: - At the Main Menu, enter the date in the format mmdd at the Enter Selection: field. For example, enter 0109 for January 9. - From Menu 20 - Service Operations, enter the number for the SMT Debug Utilities option At the > prompt, enter reformat to access the Reformat menu Enter 1 to select Collapse Nodes Enter Y at the ENTER Y TO CONFIRM NODE COLLAPSING CONVERSION: prompt. The following messages are displayed until all ports are clear: WAITING FOR ALL OTHER TERMINALS TO LOGOUT... WAITING FOR ALL PORTS TO CLEAR... Page 8 of 22

9 2.6. In the Master Node Number: field, enter the node number that will remain after the utility is run. A screen similar to the one in Figure 1 appears. Node Collapsing Utility Master Node Number: 20 Node Name: CAMPUS-A Node Serial #: # of Digits: 4 Collapsing Node Number(s): Node Node Node Node Number Name Number Name [Y] 21 CAMPUS-B [Y] 22 CAMPUS-C [Y] 23 CAMPUS-D Figure 1. Example of Node Collapsing Utility Screen. The server displays the Node Name:, Node Serial #:, and# of Digits: fields, with entries for the master node. Then, under the Collapsing Node Number(s): heading, the server lists up to 20 potentially collapsible nodes that have the same serial number and number of mailbox digits as the master node. (If there are more than 20 such nodes, run the utility again later.) A Y precedes each entry in the Node Number column, indicating that this node is to be collapsed. Nodes that have matching serial numbers but different number-of-digit lengths are preceded by an N. The server checks that the total number of prefixes in the master node and in all nodes to be collapsed is 200 or fewer. If more than 200 prefixes would be consolidated in the master node, an N precedes those node numbers that cause the total to exceed Change Y to N for any particular node or nodes that should not be collapsed, then press Enter to reach the end of the screen and begin the utility Enter Y at the Enter Y to begin Node Collapsing or N to exit prompt. If any node to be collapsed has messages in its network queue, a warning is displayed on the SMT, indicating that the messages will be returned to senders. The following messages appear as the utility is running: Page 9 of 22

10 Starting Conversion. Please wait... Moving Prefixes to Master Node. Converting NameNet entries. Converting Mailboxes... Deleting Collapsing Nodes. Conversion done. Press any key to continue Press any key to return to the debug prompt Press Ctrl+C to return to the Main Menu. Repeat the Collapse Nodes procedure (empty network queues and run the Collapse Nodes utility) as necessary on every server to be included in the Aria Domain. Note that the collapsed nodes are deleted over a period of at least 4 hours, from the beginning of the next even hour. You can check the status of these nodes in menu If the collapsed nodes are not deleted after approximately 6 hours, enter the primary system-manager mailbox and delete all network-diagnostic messages pertaining to the collapsed nodes. Continue monitoring menu until the nodes are deleted (no longer indicated as undergoing deletion). Setting Up Octel Digital Networking Using the System Manager Manual, Aria 2.0, set up Octel Digital Networking on all servers to be included in the Aria Domain. On all servers, confirm that the following parameters for each domain-node profile (menu ) are set as follows: Node-Profile Parameter Node Type Fallback Setting 2 - Octel Digital Networking 0 - None Important: Although fallback from Octel Digital Networking transmission to Octel Analog Networking transmission is allowed, it is not recommended for an Aria Domain. Message delivery using analog networking is up to 20 times slower than delivery using digital networking. If the network used for digital networking fails, if fallback is enabled, and if too few analog ports are allowed to deliver networked messages among the domain nodes during fallback, messages will quickly back up in the queue awaiting an available port and message delivery times will increase significantly. The network failure could appear to be a problem with the message server. Page 10 of 22

11 Setting Up NameNet If NameNet was already set up on all servers, proceed to the next section, Converting FMFs. Use the following procedure to calculate the number of user records required for the servers in the Aria Domain: 1. Log into the SMT. 2. Access the debug prompt (>) in one of the following ways: - At the Main Menu, enter the date in the format mmdd at the Enter Selection: prompt. For example, enter 0109 for January 9. - From Menu 20 - Service Operations, enter the number for the SMT Debug Utilities option. 3. Enter reformat at the > prompt. 4. Turn on continuous printing, as follows: - Wyse 50: Press Ctrl+Shift+Print simultaneously. - HP 700/43: Press Copy Pr. 5. Enter 0 to select Validity check user records. 6. Enter Y at the ENTER Y TO CONFIRM USER RECORD VALIDITY CHECK: prompt. 7. While the validity-check utility is running, calculate the number of user records needed for the server s NameNet directory to support the Aria Domain nodes: 7.1. Divide the estimated number of currently assigned FMFs by Round the resulting number up to the nearest integer Add 50 to the number found in step 7.2. The resulting number is the number of user records needed by the NameNet directory to support the Aria Domain servers. * 8. When the validity-check utility finishes, the total number of records available is displayed. Compare this number with the number found in step 7.3. If the number of available records is fewer than the number of needed user records, contact the TAC to have the server s user-record space expanded. * One user record contains up to 84 NameNet entries. Therefore, dividing the estimated number of FMFs by 84 obtains the minimum number of user records required to convert the FMFs. To allow for expansion of the NameNet directory, a buffer of 50 user records is added to the number found in step 7.2. Page 11 of 22

12 9. Turn off continuous printing, as follows: - Wyse 50: Press Ctrl+Shift+Print simultaneously. - HP 700/43: Press Copy Pr. 10. Press Ctrl+C until the SMT returns to the Main Menu. 11. Repeat the above steps in this section on all servers to be included in the Aria Domain. 12. On each server, set up NameNet, using Volume IV of the System Manager Manual, Aria 2.0. Make sure that the value in the Total Entries Allocated: field in menu , NameNet Directory Utilization, is greater than the estimated number of FMFs. Converting FMFs If follow-me-forward mailboxes (FMFs) were set up to simulate network dial-by-name, use the procedure in this section to convert them to NameNet entries. If FMFs were not used, proceed to the next section, Modifying NameNet Entries. FMFs that were set up to simulate network dial-by-name are not needed, once the Aria Domain is set up. Run the conversion utility in menu to delete FMFs and convert them to NameNet directory entries. The conversion utility can convert up to 4000 mailboxes at one time. Run the utility as many times as needed to convert all FMFs. FMFs that contain personal-group distribution lists are not deleted by the conversion utility. To convert them, do one of the following: - Delete the personal-group distribution lists from the mailbox and run the conversion utility again. - Delete the mailbox and add the NameNet entry manually. To prevent an FMF from being converted, do one of the following before running the conversion utility: - Remove the mailbox forwarding in menu Establish a personal-group distribution list in the mailbox. Convert FMFs as follows: 1. Log into the SMT. 2. From the Main Menu, access menu 15 - Network Management. Page 12 of 22

13 3. Enter 3 to select the NameNet Directory Administration menu (menu 15.3). 4. Enter 2 to select the Review NameNet Directory Utilization menu (menu ). 5. Verify that there are enough NameNet directory entries allocated in menu to support the estimated number of entries to be generated by the conversion. The number of entries required was calculated in the Setting Up NameNet section. Increase the number of entries, if necessary, up to 40, Press Ctrl+C until the SMT returns to the Main Menu. 7. Verify that the printer is attached to the SMT and is on line. The printer automatically prints information during the conversion. 8. From the Main Menu, access menu 13 - System Maintenance. 9. Enter 14 to access the utility to purge and convert FMFs (menu 13.14). A screen similar to the one shown in Figure 2 appears. Menu 13 - System Maintenance Purge and Convert Follow-Me-Forward Mailboxes CAMPUS4 WARNING!! This utility purges ALL the Follow-Me-Forward mailboxes directed to the destination network node. A printer must be On-Line before proceeding. **** IF YOU ARE NOT SURE OF WHAT YOU ARE DOING, PRESS BREAK NOW!! **** If any subscribers are using Follow-Me-Forward Mailboxes for temporary message forwarding, they will have to re-establish the mailboxes following the use of this function. Node: 35 Node Name: BUILDING 3 Serial Number: Purge and convert ALL Follow-Me-Forward mailboxes (Y/N): Y Confirm Deletion (Y/N): Y Figure 2. FMF Conversion Utility. 10. In the Node: field, enter the number of one of the domain nodes. The node name and serial number are displayed for confirmation. If you enter a node number that does not have NameNet capability, the following error message is displayed: This node does not support NameNet Directory Entries. If this error message is displayed, verify that the destination server for which the conversion is being performed is at Aria 2.X, then send a message to a mailbox on that node to force the sending and destination servers to confirm Page 13 of 22

14 that they are both at Aria 2.X. Do not continue this procedure until this handshake has been completed between the servers. Modifying NameNet Entries 11. Enter Y at the Purge and Convert ALL Follow-Me-Forward mailboxes (Y/N): prompt. 12. Enter Y at the Confirm Deletion (Y/N): prompt. All FMFs are displayed on the SMT and printed at the same time. If this scan of FMFs identifies any mailboxes that cannot be converted, a brief description of the problem is displayed in the Comments field, next to the mailbox. This mailbox cannot be converted until the appropriate action is taken and the conversion can be run again. Refer to Table 3 in the Solutions for FMF Conversion Errors section near the end of this document to correct the problems, then repeat the steps in this section to convert any remaining FMFs. 13. Enter Y at the Convert Follow-Me-Forward Mailboxes for node [node number]. Continue? (Y/N) prompt. The FMFs are converted to NameNet directory entries. The FMFs are displayed on the SMT and printed at the same time. If an error occurs when a mailbox is being converted, the utility skips to the next mailbox. An asterisk (*) is displayed next to the mailbox that could not be converted and a brief description of the problem is displayed in the Comments field, next to the mailbox. This mailbox cannot be converted until the appropriate action is taken and the conversion can be run again. If some FMFs are not converted or messages such as NameNet Directory Full are displayed, refer to Table 4 in the Solutions for FMF Conversion Errors section near the end of this document to correct the problems, then repeat the steps in this section to convert any remaining FMFs. 14. When the conversion is completed, press any key to return to menu If FMFs need to be converted for the other domain nodes on this server, repeat all the steps in this section for each domain node. NameNet entries for subscribers who are members of the Aria Domain must be permanent, so that recorded names are always available to subscribers when spelling the names of other Aria Domain subscribers. Page 14 of 22

15 To make NameNet entries for the domain-node subscribers permanent, perform the following steps on each server to be included in the domain: 1. From the Main Menu, access Menu 15 - Network Management. 2. Enter 3 to select the NameNet Directory Administration menu (menu 15.3). 3. Enter 3 to select the Update NameNet Directory User List menu (menu ). 4. Enter M for M(odify), to select the Modify Options menu. 5. Enter option 2 to select the modify screen for all NameNet entries by node, as shown in Figure 3. Menu 15 - Network Management - NameNet Directory User List - CAMPUS4 Node Number: Entry Type: Figure 3. NameNet Directory User List (Menu M, Option 2). 6. In the Node Number: field, enter the node number of the first domain node. 7. In the Entry Type: field, enter 1 to specify that all NameNet entries for the node are permanent. 8. Press Send to save the entries in the screen. 9. Press any key to return to menu Repeat steps 6 through 9 to modify the NameNet entries for the remaining domain nodes on this server. Repeat this procedure on each server to be included in the domain. Setting Up the Aria Domain Use the following two steps to set up the Aria Domain: 1. Modify the node profiles of the servers to be included in the Aria Domain. 2. Configure the Aria Domain parameters. Page 15 of 22

16 You must complete these steps on all of the servers to be included in the Aria Domain. 1. On each server, modify the node profiles of all the other servers to be included in the Aria Domain, using the following procedure. An example of a node profile, with the relevant parameters highlighted, is shown in Figure 4. Menu 15 - Octel Networking Administration CAMPUS 4 - Node Profile - Node Number: 25 Node Name: CAMPUS 1 Transmission Type: Node Type: 2 - Octel Digital Networking Number of Digits in a Mailbox: Serial Number: NameNet Type: 1 - Permanent Site ID: Phone Number: Ext: 3200 Dialing Sequence: Authorization Code: Access Type: Country: Max Simultaneous Analog Transmissions: Threshold: msgs, mins IP Address: Fallback: 0 - None Name Transmission Allowed: N Play Node Name: N ASCII Name Check: Node Response Allowed: System Manager Name: Mailbox Number: System Manager Phone Number: Ext: Figure 4. Example of Node Profile Screen (Menu ) From Menu 15 - Network Parameters, enter 1 to select the Octel Networking Administration menu (menu 15.1) Enter 3 to access the Define/Change Node Profile menu (menu ) Enter the node number of the node to be added to the Aria Domain Enter 1 to select the Change Node Profile screen (menu ) Modify the fields in the node profile of menu , as shown in Table 1. Page 16 of 22

17 Table 1. Menu Fields To Be Modified. Field Name Entry Purpose Node Type: 2 - Octel Digital This specifies that messages to the node will be transmitted using Digital Networking. Networking NameNet Type: 1 - Permanent Traffic-based NameNet entries for this node are permanent if the Message Traffic Based Entries: field in menu contains a Y. If this field contains an N, the NameNet Type: field has no effect. (You change the menu parameter to Y later in this procedure.) Ext.: On-switch extension number The server uses the on-switch extension entered here to dial the node. The Ext.: field is required by the Aria Domain to transfer callers to other domain nodes, whereas the Phone Number: field is required for normal Octel Networking traffic. IP Address: IP address An IP address must be specified, not the default of If an IP address is not specified, obtain it from the site s network administrator and enter it. Fallback: 0 - None Fallback is allowed but not recommended in an Aria Domain. Name Transmission Allowed: N Messages sent to the node are not prefaced by subscriber s recorded names, and therefore do not sound like networked messages to the recipients. Play Node Name: N Neither the node name, if recorded, nor the node number will be played for subscribers who use network addresses When menu is complete, Press Send to save the new parameters Press any key to return to menu Press Enter to return to the Node Number: field Repeat steps 1.3 through 1.8 for all of the remaining node profiles to be included in the Aria Domain. Page 17 of 22

18 2. To support the Aria Domain, new fields were added to the NameNet Directory Parameters menu (menu ). Figure 5 is an example of menu Values shown are default values; fields related to Aria Domain are highlighted. Menu 15 - Network Management - NameNet Directory Parameters - CAMPUS 4 NameNet Dial-by-Name: Y NameNet Dial-by-Name Active: Y Message Traffic Based Entries: Y Directory Full Alarm Threshold: 90 Critical Usage Threshold: 98 Aging Out Period (days): 30 Domain Enabled: N Domain Nodes: 1: 2: 3: 4: 5: Auto-Attendant Includes Access to Domain Nodes: N Domain Transfer Delay: 500 ms Figure 5. Example of NameNet Directory Parameters Screen (Menu ). To activate Aria Domain, perform the following steps on each server in the Aria Domain: 2.1. From the Main Menu, access menu 15 - Network Management Enter 3 to select NameNet Directory Administration (menu 15.3) Enter 1 to select the NameNet Directory Parameters screen (Figure 5) Complete the Aria Domain fields in menu , as shown in Table 2. Make sure that you modify node profiles and configure Aria Domain parameters on each server in the Aria Domain. Page 18 of 22

19 Table 2. Menu Fields To Be Completed. Field Name Entry Purpose NameNet Dial-by-Name: NameNet Dial-by-Name Active: Message Traffic Based Entries: YorN Y A Y entry activates NameNet dial-by-name, allowing callers to dial network addresses by name, including subscribers on other domain nodes. If value was previously N, the server must be rebooted to activate NameNet dial-by-name. Setting this parameter to Y is not required for an Aria Domain, but is recommended.... Used only for display of current setting of NameNet Dial-by-Name: field. When set to Y, the server adds NameNet directory entries when networked messages are sent to other nodes, including the domain nodes. Domain Enabled: Y Activates Aria Domain when set to Y. Domain Nodes Domain-node Specifies which network nodes should be treated 1: 2: 3: 4: 5: numbers as domain nodes on this server. Auto-Attendant Includes Access to Domain Nodes: Domain Transfer Delay: YorN Delay time, in ms Allows callers to be routed to extensions or mailboxes on any of the domain nodes. To prevent callers from routing themselves to any other domain-node destinations, enter N. The amount of time, in milliseconds, for the server to wait for the voice path to be established after a transfer to it is complete. Ensures that the caller hears the beginning of the mailbox greeting. Call a domain-node subscriber and listen for the beginning of the subscriber s greeting to determine the delay time required. Increase the delay length if the beginning of the greeting is clipped. Decrease the time if a long pause is heard after the transfer is completed, but before the greeting is played. Page 19 of 22

20 Solutions for FMF Conversion Errors When the conversion utility first scans FMFs to determine whether they can be converted, if it detects a mailbox that cannot be converted, a brief description of the problem is displayed in the Comments field for the mailbox. These problems, and the corrective actions to take before running the conversion utility again, are shown in Table 3. Table 3. FMF Problems and Solutions During Initial Scan. Problem Mailbox contains group list Network directory space low Solution Instruct the affected subscriber to remove all personal-group distribution lists from the mailbox. In menu , increase the NameNet directory size by increasing the value displayed in the Total Entries Allocated: field. The maximum number of entries for an Octel Overture 250 or 350 is 40,000. Maximum mailboxes converted The conversion utility can convert up to 4000 mailboxes at one time. Run the utility again to convert any remaining FMFs. System manager or general message mailbox Mailbox currently in use Port monitoring mailbox The FMF is currently specified in menu 1.2 as either a system manager mailbox or a general message mailbox. If these mailboxes are to remain forwarded, no change is necessary. If these mailboxes should be converted, access menu 1.2 and specify other mailboxes as the system-manager or general-message mailboxes. At the time the conversion was started, the subscriber was accessing the mailbox. Run the conversion utility again later, when traffic is at a minimum, to convert the mailbox. A port is being monitored by a forwarded mailbox (menu 2.2). If the mailbox is to remain forwarded, no change is necessary. If the mailbox should be converted, specify another mailbox as the port-monitoring mailbox. Page 20 of 22

21 Once the conversion utility begins converting FMFs, if a mailbox cannot be converted, a brief description of the problem is displayed in the Comments field for the mailbox. These problems, and the corrective actions to take before running the conversion utility again, are shown in Table 4. Table 4. FMF Problems and Solutions During Conversion. Problem Mailbox not deleted Address mapping table (AMT) full NameNet directory full Node disabled Node queue full Solution The NameNet entry was added, but the FMF was not deleted. Manually delete the mailbox in menu 10. The server software did not have enough addresses available. No mailboxes with this comment will be converted until there are available addresses and the conversion can be rerun. Delete any mailboxes that are not being used to create available addresses. Use menu to increase the NameNet directory size by increasing the value displayed in the Total Entries Allocated: field. The maximum number of entries for the Octel Overture 250 and 350 is 40,000. Transmission to the node is disabled in the node s profile. Change the Transmission Type: field in the node profile (menu ) to 0-Normal, then run the conversion utility again. The message queue of the specified node is full. Do one of the following: - Open a transmission window for immediate delivery of administrative messages to that node (menu ), or - Run the conversion utility after the network queue is emptied during the next scheduled transmission window. The node s network-queue activity can be monitored in menu Page 21 of 22

22 Conversion Checklist Use the following checklist to make sure that all conversion steps are performed on every server (domain node) in the Aria Domain. Step Task Server 1 Server 2 Server 3 Server 4 Server 5 Server 6 1 Server at Aria Release 2.X 2 Feature options enabled - Networking - Connectivity - Octel Digital Networking 3 Subscriber numbers unique (mailboxes, extensions, and alias addresses) 4 Mailbox-number lengths same 5 Networked-switches support supervised transfers (optional) 6 Server down-time scheduled * 7 CDR buffer downloaded (optional) 8 Service bit enabled * 9 Printer connected to SMT 10 Required documentation available 11 Domain nodes identified 12 Network-message queues emptied* 13 Nodes collapsed (optional) 14 Octel Digital Networking configured 15 Analog fallback disabled 16 NameNet set up [ 17 FMFs converted (optional) 18 NameNet entry types modified 19 Domain-node profiles modified 20 Aria Domain configured * Required only if nodes must be collapsed. [ Required only if NameNet is not already set up on all servers in the Aria Domain. Page 22 of 22