Mitel Voice Processing Solutions Instructions Manual
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+.
Configuring the Dialing Plan sing etvvork Prefix A network prefu: dialing plan uses one number to indicate that the mailbox address that follows is a network address. For example, if 9 is the network prefix digit, users must press 9 and then the network mailbox address to send network messages. You specify a network prefer digit in the dialing plan with the letter I?, followed by the number of allowable digits in a network mailbox address (including the pref= digit). For example, if 9 is the network prefer digit and network mailbox addresses have 6 digits, the dialing plan might look like 0,0,0,4,4,4,0,0,P7 Notice that the I? is in the 9s position, and it allows for seven digits: the network pref= digit plus a six-digit network mailbox address. The system strips off the prefer digit before comparing the mailbox address to the Digits Translation Table. In other words, if a user addresses a message to 9234567, the system compares 234567 against the Digit Translation Table. In this example, if the sender attempts to address a message by pressing 9 and five digits (or any number other than six), the system says that the address is not valid. Local mailbox numbers cannot begin with the same digit as the pref= digit. The P character can make dialing plans very flexible, especially when adding MESA- Net to a Centigram server that has an established mailbox dialing plan. For example, if both the local node and remote nodes have mailboxes that begin with 6 and 7, the administrator can tell users to press 9 plus the mailbox number to make a message for a remote mailbox. The 6 and 7 positions in the dialing plan can still be used by local mailboxes, and the previously unused dialing plan position 9 is reserved for remote mailboxes. The system handles the mailbox 678 123 differently than 967Ef123. sing Variable-Length Network Addresses It is not uncommon for different nodes on a network to have mailboxes that do not have the same number of digits. For example, node 1 may have 4-digit mailboxes and node 2 may have 5-digit mailboxes. There are two ways to accommodate this situation in network addressing. If you want users to always enter the same number of digits for all network addresses, you can use the Digits to Absorb feature in the Digits Translation Table to “pad out” the shorter mailbox numbers. See the section on the Digits Translation Table for more information on this technique. The other alternative is to use the I? and V characters together in the dialing plan. (The V character indicates a variable-length mailbox number; see the VoiceMemo Reference and Conjguration Mamal for more information on the V character.) This 6-8
Configuring the Dialing Plan combination allows users to address messages by entering a network prefer digit followed by the minimum number of digits required to uniquely identify a remote node and mailbox. For example, if node 3 uses 5-digit mailbox numbers and node 4 uses 4-digit mailbox numbers, the following dialing plan on node 1 would allow addressing to mailboxes on both nodes: If the prefures i n the Digits Translation Table matched the node numbers, then a user could address a message to mailbox 44564 on node 3 by entering 9344564, and to mailbox 3445 on node 4 by entering 943445. ddressing by rea Code an You can also use the P character to allow addressing messages by area code and phone number. This type of dialing plan is useful when users have DID or Centrex- type service and callers are used to reaching them by dialing 7 or 10 digits (without going through an operator). It can alleviate conflicts between telephone/mailbox numbers on different nodes that share the same telephone number prefix (the first three digits of a seven digit telephone number). For example, two nodes may have telephone numbers that begin with 257. A dialing plan with I?1 1 in the 1s position would allow users to address network messages by entering 1 + the area code + the mailbox number, just as though they were dialing long-distance calls. The P in the dialing plan means that the 1 is dropped. The Digits Translation Table is configured to match the area codes -and route messages to the correct remote nodes. When a message reaches a remote node, the three area code digits are deleted, and the message is delivered to the local seven digit mailbox number. If you do not want to use a prefx digit for network addressing, or if you want to use fully integrated local and remote mailbox numbers, you can use direct network addressing digits. The N character in a dialing plan position indicates that mailbox addresses that begin with that digit are network mailboxes, and should be processed by the MESA-Net software. The N is always followed by the number of valid digits in the network mailbox address. For example, the following dialing plan indicates that addresses that start with 7 or 8 are &digit network addresses. 0,0,0,4,4,4,N6,N6,0 In this example, when a message is addressed to a mailbox number that begins with 7 or 8, the MESA-Net software finds the destination node by comparing the leading digits of the mailbox number with the prefxes stored in the Digits Translation Table. Those prefixes would start with 7 or 8; the first digit is not stripped off when you use the N character. G-V
Configuring the Dialing Plan Note that local mailbox numbers can also begin with 7 or 8, but they must have 6 digits, and the Digits Translation Table must contain prefures that match the local mailboxes with the local node number. If the node number in the table matches the local node number, the message is sent immediately to the local mailbox (local messages sent through a network dialing plan are not queued). Senders do not need a Network Class of Service to send local messages, even though the dialing plan position indicates a network mailbox destination. Billing and statistics are the same as for local messages sent through a conventional dialing plan. You can use this strategy is to create a same-length dialing plan for every node on the network, such as N7,N7,NZNZNZN7,NZNZN% This means that every time a message is made for a mailbox, the address is checked against the Digits Translation Table to find the destination node. The main advantage of this type of dialing plan is that a user enters the same number of digits to reach a mailbox on any node. reating a Uniform Network Dialing Plan You can use a uniform dialing plan if the mailbox numbers on each node have unique ranges (for example, mailbox numbers on node 2 are in the range of 3000 to 3500 and no other nodes have mailbox numbers in that range). The advantage of a uniform dialing plan is that users can simply dial the mailbox number to access remote mailboxes. The disadvantage is that you must take local mailboxes into account in the Digits Translation Table. Mailbox number distribution takes careful planning, since local mailbox numbers cannot conflict with mailbox numbers on any remote node. You can resolve conflicts by adding access codes to remote mailbox numbers, then using the digits to absorb feature to tell the receiving system to delete the access code to find the true mailbox number. The digits to absorb feature is described earlier in this chapter. sing a Star Prefi5 Dialing Plan Centigram Series 6 servers that do n8 have any open positions in the dialing plan may need to use a star pref= dialing plan for network addressing. The star prefL?r dialing plan provides the functionality of both the N and I? characters, although the functions have different names. If the I’ function were assigned to the 9 position in a star prefix dialing plan, a user would press 9* and then the network mailbox address to send a network message. See the VoiceMemo Reference and Conjguration Man&for more information on star prefer dialing plans. st il Transparent network messaging means that there is no difference to the user between sending a message to a remote mailbox and sending a message to a local mailbox. 6-10
‘I Configuring the Dialing Plan The user does not enter a network pref= when addressing a message, and the user hears the name confirmation of the mailbox owner. You can use broadcast mailboxes to achieve this transparency. A message broadcast mailbox automatically sends any messages that it receives to the mailboxes in its first distribution list. A name broadcast mailbox automatically sends the owner’s recorded name to the mailboxes in its distribution list number 9, to be used as the recorded name for those mailboxes. You enable these features in the FCOS of the broadcast mailboxes. See the KGceMemo Reference and Confguration Manual for more information on broadcast mailboxes. For complete network transparency, every user on every node must have a mailbox on every node. A user’s mailbox on the local node has name broadcast enabled, so that the user’s recorded name is broadcast to that user’s mailboxes on all other nodes. The user’s mailboxes on remote nodes all have message broadcast enabled, so that all messages made for that user are broadcast to the local node. Figure 6-2 shows this type of configuration. Messages Local Node Remote Node igure 6-2 ame an essage Broadcast ailboxes Users always address messages to mailboxes on their local node. Because the recipient mailbox is local, the sender hears the mailbox name confirmation. If the mailbox is configured as a broadcast mailbox for a user on a remote node, the mailbox forwards the message over the network to the local node of the recipient. G-11
Configuring the Dialing Plan ote: Broadcast mailboxes put an extra burden on system administrators. You must still configure the Digits Translation Table to provide the routing required for network messages. In addition, mailbox adds, moves and changes must be coordinated across the network, and the distribution lists in the broadcast mailboxes must be kept current. See Chapter 9 for information on adding remote mailbox addresses to distribution lists. Examples The following examples illustrate various ways of configuring network addressing to meet the needs of different networks. A network consists of four nodes: San Jose (Node l), Chicago (Node 2), New York (Node 4) and Dallas (Node 6). Before the MESA-Net optional feature was installed, the San Jose node had three digit local mailboxes that began with digits 3 through 8. If the administrator wants to retain this structure, she can use dialing plan position 9 for remote mailboxes. The following changes makes this possible: 0 The old San Jose dialing plan of 0,0,3,3,3,3,3,3,0 is changed to 0,0,3,3,3,3,3,3,N5. 0 The access codes for all remote nodes begin with 9 e Each prefix has a digits to absorb count of 2 _ 0 The Digits Translation Table for San Jose looks like this: Node Node Digits To Prefix Number Name Absorb 92 2 Chicago 2 94 4 New Ycpk 2 96 6 Dallas 2 The access code length depends on how many number combinations are needed to cover all the nodes on the system, but the codes should not be so long that it is a chore for users to send remote messages. In the example above, the access codes can be up to 8 digits, since mailbox numbers can be up to 11 digits, but it is unreasonable to expect system users to remember 8 digit access codes and 3 digit mailbox numbers. A very large network would require more positions for remote nodes to make this scheme workable. This method is useful for Series 6 servers like the one in the example, where MESA- Net software is installed on an established system that has a pool of users who have memorized many mailbox numbers and do not want them to change. It is also practical for Series 6 servers on which both MESA-Net and Receptionist II are G-12
Configuring the Dialing Plan installed. Mailbox numbers can match Receptionist II extension numbers without regard to the extension/mailbox structures of other nodes. Example 2: Access Codes and Variable Length Suppose one has the network shown below. The Chicago node (Node 2) has four digit mailboxes that start with 3, the New York node (Node 4) has six digit mailboxes starting with 4 or 5, and the Dallas node (Node 6) has three digit mailboxes that start with 5. Optimally, all these mailboxes must be served by the same dialing plan position. The access codes for all remote nodes can still begin with 9, as that digit is not part of any existing dialing scheme. Let’s analyze each node individually.. . San Jose Users on the San Jose node would like to enter the same number of digits to send messages to mailboxes on any of these three remote nodes, even though the destinaition mailbox numbers have different lengths. A digits absorbed count for each pref= is suddenly very useful. Sirree New York remote mailboxes already have six digits, the administrator decides that users will only need to enter a one digit access code (i.e. 9) to reach New York. The digits to absorb count for the New York node is 1. The pref=es listed for New York in the Digits Translation Table must include at least the first digit of all possible valid mailbox numbers on the node, to make all mailboxes accessible, and to make all prefxes unique. The dialing plan in San Jose is changed to 0,0,3,0,0,0,0,O,N7 to accommodate the New York node. Local mailboxes are unaffected by the change. To access the four-digit mailboxes on the Chicago node, the Digits Translation Table must have three digit prefixes (access codes) to conform with the seven-digit network dialing plan (three digit access code plus a four digit extension equals seven digits). The digits to absorb count is also 3 for all Chicago prefixes. The Dallas node uses three-digit mailboxes, so it needs a four digit access code to conform with the dialing plan. The digits to absorb count is 4 for all Dallas prefixes. G-13
P Configuring the Dialing Plan San Jose Digit Translation Table Node Node Digits To Prefix Number Name Absorb 221 2 Chicago 3 2222 6 Dallas 4 24 4 New York 1 25 4 New York 1 New York, Chicago, and Dallas The administrators for the New York, Chicago, and Dallas nodes all decide that users on their Centigram servers will address network messages with a prefer digit, a node access code, and variable length mailbox numbers. This eases their planning and maintenance burden. All three sites use 9 as the network prefer digit, so the dialing plan for New York is The Digit Translation Tables for all three nodes look follow the same pattern. The table for New York is shown below. Node Node Digits To Prefix Number Name Absorb 1 1 San Jose 1 2 2 Chicago 1 6 6 Dallas 1 When a user in New York wants to address a message to mailbox 325 in San Jose, he enters 9 1325. The New York node recognizes the address as a network address and stripsi off the 9 because of the I? character in the dialing plan. It then compares the remaming digits with the prefEes in &e Digits Translation Table and finds that the message is for San Jose. When the San Jose node receives the message, it strips of one digit and delivers the message to mailbox 325. G-14
Node Number Mailboxes Start With 1 2 3 4 5 6 7 8 9 1 Node Name 1 / Length of Mailbox Numbers _ _ _ _ _ _ _( _ _ Node Number Mailboxes Start With 1 2 3 4 5 6 7 8 9 I 1 Node Name Length of Mailbox Numbers _ _ _ _ _ _ _ _ _ Node Number q i Mailboxes Start With 1 2 3 4 5 6 7 8 9 f I -i.+ Node Name Length of Mailbox Numbers _ _1 _ _ _ _ _ _ _ Node Number 0 Mailboxes Start With 1 2 3 4 5 6 7 8 9 Node Name Length of Mailbox Numbers _ _ _ _ _ _ _ _ _
Release 6.OA Task Procedure et Digits Translation Table Create a New Prefix/Node Pair for the Digits Translation Table ........ CP 5724 Delete a Prefix/Node Pair from the Digits Translation Table.. ................. CP 5725 View the Digits Translation Table.. .......................................................... CP 5726 Modify a Pref=/Node Pair in the Digits Translation Table.. .................... CP 5727