Home > Mitel > Communications System > Mitel Voice Processing Solutions Instructions Manual

Mitel Voice Processing Solutions Instructions Manual

    Download as PDF Print this page Share this page

    Have a look at the manual Mitel Voice Processing Solutions Instructions Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 55 Mitel manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.

    							Modi~ a Network Node Table Entry 
    Page 1 of 2 
    VoiceMemo Release 6.06.OA and later 
    Use this procedure to modify an entry in the Nenvork Node Table. When prompted 
    for a new value, you can press Enter to retain the current settings of any parameter. 
    Step 
    1. Reach the Network Node Access Table Maintenance menu. 
    2. Identify the node that you want to modify. 
    Select: (M) Modify a node entry 
    Prompt: 
    Node number: 
    Response: The number of the node entry you want to modify. This number can 
    be from 
    1 to 8191. 
    3. 
    Enter the new name of the node.. 
    P~-ompt: 
    Node name: 
    Response: The new name of the node. This name can be up to 12 alphanumeric 
    characters, including spaces. Press Enter to keep the current name. 
    4. For all MESA-Net entries, specify that this is not an AMIS connection. 
    Prompt: 
    Analog AMIS Connection (Y/N): 
    Response: N. 
    5. Specify whether this is a MESA-Net TCP/IP connection. 
    Prompt: 
    TCP/IP Connection (Y/N): 
    Response: Y if the node can be accessed using MESA-Net TCP/IP 
    N if the no&e cannot be accessed using MESA-Net TCl?/IP. 
    * 
    6. If you answered Y to the TCP/IP connection prompt, enter the IP address.. 
    Prompt: 
    IP Address: 
    Response: New II? address of the node 
    7. If you answered N to the TCP/IP connection prompt, enter the dial string for the . 
    node. 
    P7-0772pt: String: 
    Response: The string of alphanumeric characters required to access the node. 
    This string can be up to 
    16 alphanumeric characters. If required, use 
     
    for CR (carriage return) and 
     for CR/LF. Reference 
    vlenu Map 13  
    						
    							Cl?5722 
    Page 2 of 2 
    Release G.OA and later 
    Step 
    Reference 
    8. Specify whether the node can be accessed by local node. 
    Prompt: 
    Access (Y/N): 
    Response: Y for almost all remote nodes. 
    N for the local node, and any remote nodes that you do not want 
    accessed from the local node. 
    9. If you have installed the Parallel Links optional feature, set the length of time that 
    the existing connection or connections must be open before a parallel connection is 
    established. 
    prompt: Parallel link delay [15] 
    Response: The number of minutes a link must be open before a new link is 
    established. If you enter 0, a new link is created as soon as the previous 
    link succeeds. 
    10. If you have installed the Parallel Links optional feature, set the maximum number of 
    parallel links that can be open between the local node and the remote node. 
    prompt: Maximum parallel links [l]: 
    Response: The number, 1-8, of parallel links that the node can establish with 
    another node. Do not exceed the number of physical links that both 
    nodes can support. 
    11. Repeat steps 2 through 10 to modify more node entries, or press Enter to indicate 
    that you have finished modifyingnode entries. 
    12. List the Network Node Table on screen to check yoz work. 
    Select: 
    (L) List the node table  
    						
    							When a user addresses a message, the VoiceMemo software must be able to identify 
    the address as either a local mailbox or a remote mailbox. If it is a remote mailbox, 
    the VoiceMemo software must be able to identify the correct remote node and the 
    correct mailbox on that node. 
    The Dialing Plan identifies the message address as either a local mailbox or a remote 
    mailbox. The Digits Translation Table determines the correct node of the remote 
    mailbox and how to derive the mailbox number from the address entered. Figure 
    6-l shows how these two filters work together. 
    User 
    extension Series 6 Server 
    I 
    82100 
    tr 
    Consults Dialing Plan 
    3 3 3 3 3 3 3N53 
    I 82 100 is 
    a valid 
    network number 
    Consults DiaitsTranslationTable 
    Prefix Node Digits to’Absorb 
    81 1 2 
    82 
    2 2 
    83 3 2 
    82 = Node 2 
    Digits to Absorb = 2 
    Mailbox = 100 
    5116taM 
    ure 6-1 Example of 
    G-1  
    						
    							Configuring the Dialing Plan 
    You MESA-Net network will be much easier to maintain and expand if you carefully 
    plan you network addressing in advance. You must consider any existing switch 
    extension numbering and VoiceMemo dialing plans, and then create dialing plans on 
    all nodes that allow easy access to all other nodes. 
    Use the Planning Network Addressing Worksheet to gather the information that you 
    need to create a network addressing scheme that meets your present and future 
    needs. Study the sample worksheet and descriptions below, and then copy the blank 
    worksheet at the end of this chapter and fill in the information for your network. Be 
    sure to include an entry for your local node. 
    Node Number ? 
    III 
    Node Name Isan Jo” 
    Mailboxes Start With 1 2 3 4 5 6 7 8 9 
    00 
    Length of Mailbox Numbers _ _ 3 3 _ _ _ __ _ 
    Node Number 2 
    0 Mai1boxes;tat-t With 1 2 3 @ 08 7 8 9 
    Node Name Ch’Ga@ 
    / Length of Mailbox Numbers - _ _ 5 5 _V _ _ _ 
    Figure 6-l Sample Planning Network 
    rksheet 
    Worksheet 
    Node Number: The number of the node for this entry. Each MESA-Net node on 
    the network must be represented by a unique number. You can use numbers from 
    1 
    to 8 191, but the maximum number of nodes is 1500. 
    Node Name: The name or location of the node. 
    G-2  
    						
    							Configuring the Dialing Plan 
    Mailboxes Start with: Circle the numbers that are used at the node as the first digit 
    in user mailboxes. For example, if mailboxes at a node are in the 3000 and 4000 
    range, circle 3 and 4. 
    Length of Mailbox Numbers: For each number that you circled, write in the 
    number of digits in mailboxes that start with that number. If mailboxes have 
    variable lengths, write V. 
    The Digits Translation Table is the “sorting machine” or “routing table” for network 
    messages. When a user addresses a message to a remote mailbox, MESA-Net 
    compares the mailbox address to the prefures listed in the Digits Translation Table. 
    The Digits Translation Table tells where the message is going, and how many digits 
    the remote node must delete (“absorb”) to find the destination mailbox. 
    The following excerpt from a Digits Translation Table indicates that any mailbox 
    addresses that begin with 21 or 22 are to be routed to node 2 (Chicago), and any 
    addresses that begin with 23 are to be routed to node 8 (Dallas). In addition, the 
    remote nodes must strip off rcyo digits (the prefer) to find the destination mailbox 
    number. 
    Node Node Digits To 
    Prefix Number Name Absorb 
    21 2 Chicago 2 
    22 2 Chicago 2 
    23 8 Dallas 2 
    Centigram recommends that the table be the same in each node. You can enter your 
    local npde number in this table. If some nodes are not allowed to communicate with 
    certain remote nodes, then use the GC%&S feature to properly segregate those 
    communities of interest. 
    (See the VoiceMemo Reference and Conjguration Manual 
    for more information on GCOS.) 
    e Prefixes 
    All network messages are routed by the node prefxes in the Digits Translation Table. 
    Node pref=es are the leading digits of network mailbox numbers that are unique to a 
    node. In the sample Digits Translation Table above, the pref= 23 uniquely 
    identifies node 8; only network addresses at node 8 begin with the digits 23 
    The length of an individual pref= depends on whether you are using access codes 
    (see below) and whether mailboxes on two or more nodes share the first, second, 
    third, fourth, etc. digits. Each prefer consists of a number of shared leading digits, 
    plus one digit that is found only in the mailboxes of a single node. 
    6-3  
    						
    							Configuring the Dialing Plan 
    Example: 
    The San Jose node has the following dialing plan: 
    4,Nh,N4,N4,4,4,4,4,4 
    This means that the remote mailbox numbers that San Jose can access begin with 2, 
    3, or 4, and consist of four digits. 
    The Chicago node (Node 2) uses mailbox numbers 2000 to 2999, and 3000 to 3250 
    The New York node (Node 4) uses mailbox numbers 3260 to 3999, and 4000 to 
    4499 
    The Dallas node (Node 6) uses mailboxes 4500 to 4999 
    G-4  
    						
    							Configuring the Dialing Plan 
    Because none of the nodes have overlapping mailbox numbers, the digits to absorb 
    count is 0 for all prefures. The San Jose Digits Translation Table would look like 
    this: 
    Node 
    Prefix Number 
    2 2 
    30 2 
    31 2 
    320 2 
    321 2 
    322 2 
    323 2 
    324 2 
    325 2 
    326 4 
    327 4 
    328 4 
    329 4 
    33 4 
    34 4 
    35 4 
    36 4 
    37 4 
    38 4 
    39 4 
    40 4 
    41 4 
    42 4 
    43 4 
    44 4 
    45 6 
    46 6 
    49 6 
    48 6 
    49 6 Node Digits To 
    Name Absorb 
    Chicago 0 
    Chicago 0 
    Chicago 0 
    Chicago 0 
    Chicago 0 
    Chicago 0 
    Chicago 0 
    Chicago 0 
    Chicago 0 
    New York 0 
    New York 0 
    New York 0 
    New York 0 
    New York 0 
    New York 0 
    New York 0 
    New York 0 
    New York 0 
    New York 0 
    New York 0 
    New York 0 
    New York 0 
    New York 0 
    New York 0 
    New York 0 
    Dallas 0 
    Dallas 0 
    Dallas 0 
    Dallas NT 0 
    Dallas 0 
    If a message is made for remote mailbox 3267, MESA-Net checks the table, sees that 
    prefer 326 matches this mailbox, adds a flag to the message that tells the remote node 
    to absorb no leading digits from the incoming mailbox number, then adds the 
    message to the queue for node 4. 
    Note the variation in the number of digits needed to make a prefer unique to a node. 
    Chicago is the only node using mailboxes that begin with 2, so that prefz only needs 
    to be one digit. Chicago and New York both uses mailboxes in the 3200 series, so 
    these prefures must be taken out to the third digit to be unique. 
    Another thing that is noteworthy about this dialing plan is that no remote mailbox 
    numbers overlap, either with each other or with local San Jose mailboxes. New 
    York, Chicago, and Dallas could use mailbox numbers that begin with 1, 5, 6, 7, 8, 
    G-5  
    						
    							Configuring the Dialing Plan 
    and 9, but users on the San Jose system cannot send messages to these mailboxes 
    through MESA-Net. The digits to absorb feature can be used to add flexibility to 
    the dialing plan. 
    igits To Absorb 
    You assign a Digits To Absorb number to each prefer in the Digits Translation 
    Table. The number of digits can be from 0 to 10. After MESA-Net matches the 
    destination mailbox number to a prefer, it attaches the corresponding Digits To 
    Absorb count to the message. The remote node deletes the specified number of 
    leading digits to convert the network mailbox number to a local mailbox number. 
    You must configure each node to send Digits To Absorb counts that allow remote 
    nodes to translate network mailbox numbers to valid local mailbox numbers. 
    Digits to Absorb and local Mailboxes 
    If local mailbox numbers match a dialing plan position that contains an N, then 
    there must be a prefix entry in the Digits Translation Table that has the local node 
    number. 
    If every node on the network uses the same dialing plan, all mailboxes must be the 
    same length. For example, if every node on a network uses the dialing plan 
    NZNZNZNZNZNZN7,NZNZ users on every node are permitted to make 
    messages for local or remote mailboxes that have 7 digit numbers only. Since 
    MESA-Net does not absorb digits from local mailboxes, all local mailboxes on every 
    system must be 7 digits; therefore, no digit absorption is possible throughout the 
    network. The following section shows a way to formulate a network-wide‘ dialing 
    plan to avoid this limitation. 
    Using the Digits to Absorb Feature to Create “Access Codes’” 
    Thejdigits to absorb feature can simp&fjl Digit Translation Table configuration by 
    allowing each node administrator to formulate “access codes” for the other nodes on 
    the system. A user enters the access code for the node before entering the mailbox 
    number of the recipient when making a message for a remote mailbox. For example, 
    if the access code for Boston is 82 and the mailbox you want to reach is 100, you 
    would enter 82 100. 
    You can implement this feature with the either N or the I? character in the dialing 
    plan. With the N implementation, users will enter just the access code and mailbox. 
    With the I? implementation, users will enter a “nenvork” access code digit, 
    identifying that a network message is being made, then a “node” access code, 
    identifying the destination node, then the destination mailbox number. 
    The access codes are prefures in the Digits Translation Table; the associated digits to 
    absorb count tells the remote node to delete the access code to obtain the local 
    mailbox number. Problems with mailbox number overlap between remote nodes are 
    G-G  
    						
    							Configuring the Dialing Plan 
    avoided, since’the “real” mailbox number (the local mailbox number on the remote 
    node) is obtained after the message is sent. 
    bsorb Feature to Create Same- 
    If you want users to always enter the same number of digits for all network addresses, 
    you can use the Node Prefures and the Digits to Absorb feature in the Digits 
    Translation Table to “pad out” the mailbox numbers for nodes that use shorter 
    extensions. For example, if node 2 uses 3-digit extensions and node 6 uses 4-digit 
    extensions, you can create prefures for node 2 that are one digit longer than the 
    prefures for node 6. You also set the Digits to Absorb count for node 2 to be one 
    digit greater than the Digits to Absorb for node 6. The sample Digits Translation 
    Table below shows this kind of configuration. 
    Node Node 
    Digits To 
    Prefix Number Name Absorb 
    211 2 Chicago 3 
    22 6 Dallas 2 
    reatin 
    When you initially configure MESA-Net software on your Centigram server, you 
    must set the dialing plans so that users can send network messages. You must set the 
    dialing plan of every line group (VoiceMemo, Receptionist II, and so on) from 
    which users will be allowed to send network messages. If any line group has more 
    than one application, such as Receptionist II and an integration, remember to change 
    all of the dialing plans. Do not change PBX dialing plans for Enhanced SMDI line 
    groups. 
    If the dialing plan for a particular application is not changed, a user who calls in on 
    the lind group dedicated to that application will be unable to make messages for 
    remote mailboxes. For example, Messa@ Delivery uses the dialing plan specified for 
    the Pager Application. When Message Delivery calls a user at a pre-programmed 
    telephone number because there is an unplayed message in the mailbox, the user 
    enters the mailbox passcode and is logged into the mailbox. 
    If the Pager Application dialing plan is -not changed to match the Network Dialing 
    Plan, the user will be unable to make messages to remote mailboxes. To 
    communicate with remote mailboxes, the user must call the standard VoiceMemo 
    number, where he or she will log in under the VoiceMemo application 
    When you configure the dialing plans for MESA-Net messaging, you must choose to 
    use a network prefer digit, direct network addressing digits, or a star-prefix dialing 
    plan. 
    6-7  
    						
    All Mitel manuals Comments (0)

    Related Manuals for Mitel Voice Processing Solutions Instructions Manual