After the system is installed, the system administrator must enter the translation data into the system memory via the SAT. Translation data is taken from survey sheets and previous system records and provides a blueprint of what needs to be programmed into the system configuration. When entering the translation data into the system, the system administrator should periodically save the translations on tape. This creates a nonvolatile copy of the translation already entered into the system. If a power outage or system failure occurs, the translation data saved on the tape will not have to be entered again.
PBX system features should be entered into the switch in an ordered manner. The following is the recommended order in which data should be entered into the system:
-
Login and password (change password, if necessary)
-
Dial plan
-
Feature access codes (FACs)
-
System features (class of service and class of restriction)
-
Console parameters
-
Attendant consoles
-
System parameters
-
Voice terminals
-
Data modules
-
Network connection channels
-
Bridged line assignments
-
Group assignment (hunt groups, call coverage, pickup groups, etc.)
-
Trunk groups
-
Paging/code call zone assignments
-
ARS table
Before the customer database data is programmed into the system, the system administrator should review the system hardware configuration to assess the available port circuit interface boards and design layout. Many administration interface screens will require the administrator to input a port or slot identifier. A port or slot is an address that describes the physical location of the installed equipped. Port addresses consist of cabinet, port carrier, card slot, and port circuit card termination identifiers. Each hardware component has a multidigit identifier, and the combination of the hardware component identifiers is the port address.
Dial plan and FACs must be administered before voice terminals, hunt groups, pickup groups, coverage groups, and attendant consoles can be administered. Default values for the dial plan can be changed if they do not meet customer requirements. A standard dialing plan usually supports four- or five-digit extension numbers, but some customers may require more extension digits for system subscribers. For example, a seven-digit dial plan may be required for multisystem intelligent transparent private network configurations. Default FACs can also be changed, but the number of digits assigned to the FAC must agree with that of the dial plan.
The dial plan is used by the system to interpret dialed digits and know how many digits are expected for different call types, such as intercom calls or trunk calls. An important element of the dial plan is the first-digit table. The first digit dialed by a station user may have any one of the following codes: attendant, dial trunk access, extensions, feature access, and miscellaneous (used when more than one code begins with the same digit and requires a second-digit dial table).
Regarding first-digit dialing, North American station users are accustomed to dialing 9 for dial trunk access and 0 to reach an attendant console. In most of Western Europe, the first-digit dial trunk access code is 0, which usually proves confusing to American tourists. Many station users do not understand that access codes are programmable by system administrators, although most systems use the default values programmed by the manufacturer, such as 9 for trunk access in North America.
Miscellaneous codes are usually required when there might be a problem interpreting the first dialed digit. For example, when local 911 emergency services were first introduced, major PBX problems occurred. PBX systems that were programmed to recognize 9 as the first-digit dial trunk access code did not recognize the second dialed digit, 1, as a valid area or exchange code. System administrators were forced to reprogram their first digit tables to interpret a 911 call. Similarly, the revised North American Dialing Plan (NADP) introduced in the mid-1990s forced a reprogramming of the dial plan because trunk calls outside of the local area code required dialing a 1 before an area code for interpretation by local central office switches, and digit restrictions for the second area code digit (previously 0 or 1) were modified. Continuing changes in PSTN dialing requirements require constant updates of PBX dial plans.
Once the dial plan and FACs have been assigned, the system administrator can add voice terminals to the system. A variety of programming commands simplifies the configuration process. For example, the duplicate command can add the same types of voice terminals, instead of repetitive programming of similar information. The terminal extension number, location, type, and user name are entered on the display form with labeled blank fields. For an IP-PBX system, IP voice terminals require similar data entry for the voice station display screen, but also require entry of IP addresses, MAC addresses, and voice codec information. IP addresses are usually assigned by a DHCP server but can be manually administered. QoS programming for IP voice terminals is the responsibility of the LAN administrator, as is performance monitoring of IP telephony metrics, such as call delay and packet loss.
A common misconception is that IP-PBX systems don’t require traditional MAC administration because IP voice terminals can be initialized via a DHCP server or physically moved to different LAN connector outlets without administration programming. Despite these capabilities, subscriber and voice terminal parameters must be input for all IP peripherals. With regard to moves, IP-PBX system IP voice terminals require similar data entry for the voice station display screen, but also require the entry of IP addresses, MAC addresses, and voice codec information. IP addresses are usually assigned by a DHCP server but can be manually administered. All PBX systems support a customer station rearrangement feature that allows the movement of digital telephones between telecommunications outlets without administration intervention, exactly like an IP terminal.
Attendant consoles must be added one at a time, and for reliability, attendant consoles should not be assigned to the same circuit pack. Data modules can be assigned after voice terminal administration. Some data modules must be added during voice terminal administration if the voice terminal has a data module. Other data modules can be added separately.
Network connection channels are used to provide switched data access for the following features and functions:
-
CDR
-
SATs
-
Remote SATs
-
Property management system (PMS) link
-
PMS log printer
-
Journal printer
-
Recorded announcements
-
System printer
Group assignments can be programmed after voice terminals are added. The following groups can be administered:
-
Abbreviated dialing (system, group, enhanced)
-
Hunt groups
-
Call coverage answer groups
-
Pickup groups
-
Intercom groups
-
Terminating extension groups
-
Trunk groups
The ARS tables support network access to the PSTN and private networks. Trunk groups must be programmed to ARS. Access to private network facilities include the following network interface types:
-
DS1 interface
-
TTTN
-
Private tandem network
-
ISDN PRI
-
VPN
No comments:
Post a Comment