Showing posts with label Function Enhancements. Show all posts
Showing posts with label Function Enhancements. Show all posts

Saturday

Messaging | Feature/Function Enhancements

VMSs were introduced to the market in the early 1980s, and originally worked as stand-alone systems behind PBX systems. Although the first VMSs were designed and marketed by third-party suppliers, several of the leading PBX manufacturers eventually entered the market with products of their own design. Rolm and AT&T were among the first PBX manufacturers to enter the voice messaging market with products designed to work behind their own communications systems, although they could also be engineered as stand-alone systems to work behind other suppliers’ PBX systems.

Northern Telecom, one of the leading PBX suppliers, came late to the VMS market during the late 1980s, but when it introduced Meridian Mail it became the first messaging system to be fully integrated within the PBX system design. Meridian Mail used the Meridian 1 processing and switching network backplane for supporting PBX station user messaging applications. The Meridian Mail Module was installed as another cabinet stack in the Meridian 1 and tightly integrated within the overall PBX system design. Instead of using analog station interfaces and a dedicated data signaling link between the PBX system and adjunct voice messaging cabinet, Meridian Mail ports appeared to the Meridian 1 switching network as just another station port, and signaling between the Meridian Mail Module and the Meridian 1 common control complex was transmitted over the internal system processor bus. AT&T followed Northern Telecom’s example and later redesigned its Audix VMS as a multiple card slot equipment module to be installed within its Definity PBX system. The Definity Audix option offered most of the features and functions available on the larger, stand-alone Audix (later Intuity Audix) system at a reduced price.

During the early 1990s VMSs were redesigned to support integrated messaging applications with e-mail servers. The concept of a UMS designed to support voice and e-mail messaging, with both message mediums sharing a common directory and storage system, was also introduced in the early 1990s. Although demand for the enhanced messaging system designs has been limited to date, there are many productivity and cost benefits attributable to using one mailbox for all types of messages and having a single interface to the mailbox from either a telephone or PC client.

Recognizing the competitive advantage of bundling messaging applications within the PBX system, several recent start-up companies with PBX client/server designs, such as Altigen and NBX (since acquired by 3Com), integrated a UMS application running off the main system server that also provided basic PBX communications features and functions. Recently, Avaya integrated the capabilities of a full-function Intuity Audix system into the main call processing board of its small Definity One PBX system and included the Intuity Integrated Messaging appli- cation on the same board. The Altigen, 3Com, and Avaya PBX systems with the bundled messaging capabilities are designed for small/intermediate customer line size requirements, and the message storage capacities and access ports are limited. PBX systems designed for large and very large customer port requirements would not be able to integrate the messaging application into the main common control complex without affecting the basic communications responsibilities of the system. Dedicated messaging application servers will likely be the optimal solution for higher-end PBX customers, even when IP-PBX client/server system designs become standard by the end of this decade.

Figure 1: Avaya speech access with unified messenger architecture.

Friday

Mobile Communications | Features/Function Enhancements

The first wireless PBX options were announced in 1992. The first to announce was Ericsson, a leading PBX supplier who has also been a dominant competitor in wireless communications, Ericsson introduced a wireless adjunct controller to work behind its MD-110 PBX. A few months later an unknown company called Spectralink introduced its wireless adjunct option designed to work behind any PBX system. Although the Ericsson and Spectralink systems were based on different radio transmission frequencies and used different voice encoding formats, the basic features and functions were similar. Both wireless communications options supported multiple-zone coverage areas and features such as roaming and handoff between coverage zones. In addition to a controller cabinet that linked to the main PBX system, the infrastructure included radio transmission transceivers linked to the controller over standard, unshielded, twisted-pair telephony wiring and provided the interface between the wireless telephone handsets and the PBX system. The adjunct controller served as a mere gateway between PBX and the station users. It was the PBX system that continued to provide all communications services and function to the wireless station users, including dial tone, call processing, and switching functions (Figure 1).


Figure 1: Wireless PBX design.


After the initial wireless system announcements from Ericsson and Spectralink, several other leading PBX suppliers developed and intro- duced their own wireless system options by the mid-1990s. These options were designed to work behind their own communications systems. Among those that developed proprietary wireless communications options were AT&T, Northern Telecom, NEC, Alcatel, and Tadiran. Throughout the 1990s several of the wireless system suppliers upgraded or overhauled their original system designs. The original systems operating in the 800-MHz frequency ranges migrated to 900 MHz and/or 1900 MHz. Ericsson, for example, went through two system redesigns and eventually abandoned its last version to focus on premises cellular systems as an extension of their network-based offerings.

Market demand for wireless PBX system options has been less than originally forecasted. Several reasons have been given for poor shipment levels: the cost to install and operate a wireless station subscriber behind a PBX system could be several times greater than a wired station; there are severe traffic capacity limitations within each coverage zone; and the technology standards are continually changing. For example, the typical price for a proprietary wireless handset is more than $500 at a time when network cellular telephones can be purchased for less than $100.

Evolving mobile communications capabilities behind a PBX system are likely to be based on enterprise mobility servers that link a network carrier’s cellular infrastructure with a PBX system. Ericsson’s Digital Wireless Office System (DWOS) is an example of an enterprise cellular communications solution that supports network carrier cellular telephones behind a PBX system, with a mobility server as the link between the premises and off-premises communications system. Ericsson, in fact, plans to port its MD-110 PBX features and function to its DWOS mobility server and market a fully integrated PBX/cellular communications system. Other leading PBX suppliers, such as Alcatel and Siemens, offer mobile communications option similar to DWOS and also may integrate PBX functions into the mobility server. The future boundary between premises and network communications systems and services will be blurred when the new mobile communications offerings are generally available.

Monday

Computer Telephony Integration (CTI) | Features/Function Enhancements

CTI had its origins in the early 1980s when AT&T was the first PBX manufacturer to use an adjunct applications processor to provide a message center and directory system function behind its Dimension PBX. Unanswered calls were forwarded to a message center agent who could do a directory lookup for the person being called and enter a message into a computer terminal. The message was then forwarded to a printer close to the called party. The connection between the PBX and the applications processor was a physical link, and no enhanced PBX voice functions were provided. This was CTI in its most rudimentary form.

The concept of enhancing the PBX system with an adjunct applications processor, with physical and logical connectivities between the two independent systems, was not realized until the late 1980s. The first true CTI options were available almost concurrently on two PBX systems. The NEC NEAX2400 and the Intecom IBX offered an Open Applications Interface (OAI) option for third-party application software developers to design applications running on an adjunct client or server to enhance the performance capabilities of the core PBX system. Both suppliers’ OAI option included an intelligent signaling link between the PBX and the adjunct applications processing system. The intelligent signaling link provided a communications path for the PBX system to send system status and message packets to the applications processor and provided the means to transmit the software application program commands back to the PBX. The applications programming interface included with the OAI software developer’s toolkit was proprietary to each system and required software developers to write different programs for different systems. The PBX manufacturers initiated the first CTI implementations, and customer demand for the NEC and Intecom offerings was limited.

When the first CTI industrywide standards were being developed in the late 1980s and early 1990s, it was the major computer companies, such as DEC and IBM, that took the initiative, not the PBX manufacturers. Most of the early CTI implementations were host-based applications, such as predictive dialing and agent screen pops for outbound calling centers. The PBX manufacturers focused on first-party desktop CTI applications by providing a physical/logical link between their digital telephones and desktop PC clients. The client software applications supported a variety of PC telephony features and functions, including directories, screen pops, PBX feature/function activation, on-screen dialing, and call logs/notes. Client/server CTI applications were initially driven by Novell, which promoted its Telephony Services Application Programming Interface (TSAPI) standard. The CTI standard in Europe was developed by the European Computer Manufacturers Association (ECMA) and was known as Computer Services Telephony Applications (CSTA). Microsoft developed its own desktop CTI standard, Telephony Applications Programming Interface (TAPI), that was later enhanced to support client/server applications, and supplanted Novell’s TSAPI as the most popular CTI platform (Figure 1).


Figure 1: CTI system designs


CTI is used behind a PBX system to provide features and functions not available in the generic communications software package. Many of the CTI applications have limited market potential for which PBX developers cannot afford to expend resources. Desktop and client/server CTI was envisioned by many within the industry has a means to replace the proprietary telephone instrument. Instead of buying an expensive voice terminal with limited feature button and display capabilities, the PC client and monitor would serve as the station user interface to the PBX system for all system operations, including dialing, call screening, call answering, and feature implementation. Despite substantial marketing efforts, customers resisted using CTI PC telephony as a substitute for high-performance telephone instruments. Station users were reluctant to learn new programming tools, the ergonomics were poor, the cost was too high, and the PC reliability factor was unacceptable. Desktop CTI shipments behind PBX systems have been negligible, with annual shipment levels less than 2 percent of total station shipments. The only PBX market segment in which CTI gained a foothold was call centers because the evolving call center process became heavily dependent on computer technology, and ACD agents were already using PC clients to handle the typical caller transaction. About 25 percent of call centers are currently implementing CTI.

In the late 1990s several recent PBX market entrants attempted to design and market enterprise communications systems based on CTI client/server architecture principles: an applications processor served as the call processing manager, and station user desktops were analog telephones logically working with PC telephony clients. The desktop PC telephony applications software was included in the system price, and CTI links were used to provide third-party applications not included in the generic software package. These systems did not support multiple-line appearance digital telephones and found limited market appeal. One manufacturer who first attempted to market a pure client/server design, Vertical Networks, recognized the value of digital, multiline, display telephones, and downplayed the CTI attributes of its system when it belatedly marketed a traditional PBX-like digital telephone.

The new IP softphones, available from most longtime and new PBX suppliers, is a proprietary version of desktop CTI, although it is not marketed as such. The PBX system’s call processing manager, be it a traditional proprietary common control complex or a third-party server, functions as a server to the PC client desktop. It is forecasted that IP softphones will become more popular throughout the remainder of this decade, although desktop telephone instruments will remain the dominant voice terminal type.

Wednesday

ACD-based Call Centers | Features/Function Enhancements

The fundamental function of a call center is to direct calls to a group of answering positions, equitably distribute the calls among the group members, and minimize the caller’s time in queue waiting for an agent. ACD is the general term used to describe this telephony function and was introduced as a PBX feature in the early 1980s. The early PBX-based ACD software options had limited flexibility in screening, routing, and queuing calls, and the MIS reporting function was minimal. ACD was developed as an enhanced version of the Uniform Call Distribution (UCD) feature, which itself was an enhanced version of Hunting.

ACD systems in the early 1980s were used only in very formal incoming call center environments, and annual shipments were limited to several hundred systems. In the early 1980s the only PBX system with an ACD capability that was competitive with stand-alone ACD systems was the Rockwell Wescom 580. Rockwell was also the leading manufacturer of stand-alone ACD systems at the time; its Galaxy ACD was the leading system in the market in terms of features and functions. The Rolm CBX had a basic ACD package, but most PBXs could offer little more than UCD for distributing calls. By the mid-1980s the market for ACD systems was growing almost 50 percent annually, and many PBX manufacturers looked at the call center application market for potential high profit margins. The first PBX manufacturer to offer a sophisticated ACD option that could compete with the Rockwell Galaxy ACD was AT&T. When AT&T introduced its latest version of System 85 in 1987, the ACD call screening, routing, and queuing functions were based on a new customer programming tool called Call Vectoring. Call Vectoring consisted of a series of programming commands that defined call coverage and treatment operations for each incoming call with flow charting methods. A new advanced MIS reporting system, based on an adjunct computer working behind the System 85, offered customers dozens of reports for call center management and monitoring. Supervisor positions, linked to the MIS reporting processing system consisted of GUI workstations displaying real-time call center information. The AT&T announcement marked a major change in the direction of PBX-based call centers.

After the AT&T announcement, other PBX manufacturers began development of similar ACD and MIS reporting options for their communications systems. By the mid-1990s the typical PBX/ACD offering was based on an adjunct application server required to run sophisticated call routing and treatment software, provide advanced MIS reports, and support supervisor PC client positions. Customers with complex call center application requirements would likely link the PBX/ACD system to a CTI application server to provide features such as screen pops, an coordinated voice/data screen transfer. An IVR would likely serve as a front-end system to screen calls and pass call-prompted data to the PBX/ACD program for analysis. New ACD features that improved call center efficiency and customer satisfaction levels included skills-based routing and agent skill profiling and mapping (Figure 2-4).

By 2000 PBX/ACDs dominated the call center market, accounting for more than 80 percent of total agent shipments. During the next few years the traditional voice-centric call center will migrate toward a mixed-media model that integrates the traditional ACD system with email distribution systems and Internet-based Web sites. The emerging IP-PBX system will be able to support the new-generation mixed-media agent position, which will handle incoming and outgoing voice calls, respond to e-mails, and chat with Web surfers on-line. Despite the changes in technology and the mix of voice calls, e-mail, and on-line chat, the fundamental functions of the new contact center system will be the same as those of the original ACD systems: equitable distribution of calls to agents and minimized response times for customer inquiries.

Saturday

Networking | Features/Function Enhancements

PBX networking has evolved dramatically during the past 25 years. The earliest PBX networking arrangements consisted of two switch nodes linked by a dedicated, private line facility (E&M tie trunk) to save on long distance toll charges. The primary benefit was cost savings. When customers began to use multiple long distance carriers in the late 1970s it became necessary for PBX systems to analyze each placed long distance call to determine which carrier service should handle the call.

The preferred carrier service was usually the lowest priced for the call. A new PBX feature was developed and known by several names, including least cost routing (LCR), ARS, and most economical route selection (MERS). Implementing the feature required the system administrator to enter the call destination route and routing pattern data into a database that would price each call based on tariff pricing data. The tariff data was obtained through a service bureau and needed to be updated regularly.

The benefit to the customer was to reduce long distance toll expenses. Expensive calling routes were restricted to callers only with permitted network classes of service levels; callers with the lowest service level rating could place calls only when the lowest cost route was available.

Also in the late 1970s, AT&T announced its Electronic Tandem Network (ETN) offering, and PBX networks acquired a greater degree of complexity and functionality. ETN was a private tandem network consisting of a meshed network of private line facilities linking tandem switch PBX nodes, main PBX nodes, and satellite systems. In-band signaling techniques supported a network dialing plan and automatic alternate routing between nodes within the network. In addition to cost-savings benefits using fixed tariff private line carrier facilities, customers enjoyed greater control over network operation and use. All of this was initially done with the use of narrowband analog trunking facilities.

The next step up the evolutionary PBX networking ladder was establishing an intelligent network signaling to support transparent feature/function operations between discrete locations served by independent PBX systems. AT&T’s Distributed Communications System (DCS) offering was introduced in 1982 for its Dimension PBX. The first intelligent signaling link required an expensive private data circuit; analog private lines were used to carry voice traffic. The DCS intelligent networking solution allowed customers to use simplified dialing plans (i.e., four- or five-digits) for calls across PBX systems; supported transport of caller name/number display information between telephone desktops working behind different switching nodes; and provided a basic level of transparency within the network for many of the most commonly used station features, such as call transfer, call forwarding, and multiparty conferencing. Shared applications were also supported across a network of PBX systems, such as centralized voice messaging.

The arrival of digital T1-carrier trunk services in the mid-1980s changed the rules for PBX networking because in-band signaling was replaced by out-of-band signaling, and new networking solutions became possible. The same digital trunk circuit used for voice traffic could also be used to support the intelligent signaling link between PBXs. Digital voice carrier services using T1-carrier circuits made out-of-band signaling a more economic and feasible solution for implementing an intelligent network of PBXs. Use of an out-of-band signaling channel allowed PBX systems to communicate with one another at a much higher level than before. The resulting intelligent network configuration could offer customers traditional network transmission costs savings and provide significant productivity gains and additional cost savings through the use of shared application features/functions.

Each PBX manufacturer’s intelligent networking solution was proprietary and caused problems for customers with a mix of PBX systems in their networks. An initiative was begun in the late 1980s in Europe by the leading PBX suppliers to create a standardized network signaling protocol to intelligently link dissimilar PBXs. The signaling standard is commonly known as Qsig, and was originally developed under the auspices of the ISDN Private Network Systems (IPNS) Forum. PBX systems that support Qsig can interwork intelligently with each other; support basic call set-up and tear-down across the network between dissimilar PBX system platforms; conform to a common dialing plan for limited digit dialing across PBXs; transmit and accept telephone display information, such as calling name and number, and call redirection data between desktops; and sup- port feature-transparent operations for a defined set of features, such as call forwarding, call transfer, conferencing, and network attendant service. Although most leading PBX suppliers support Qsig as part of their networking solutions, the degree of transparency between systems remains limited. Manufacturers must do continual testing of their systems to correct Qsig message and signaling problems.

PBX networking advancements in the late 1980s included support of ISDN PRI services. ISDN PRI service circuits became the preferred trunking solution for implementing an intelligent feature-transparent network because the D channel was a natural communications channel for handling signaling and control data across distributed PBXs. New PBX networking features based on ISDN PRI services included support of incoming ANI, and call-by-call service selection (CBCSS). CBCSS allows a PBX system administrator to define the communications service supported by individual ISDN PRI bearer communications channels. A single T1-carrier trunk circuit, supported by ISDN PRI service, could be used for a variety of services between the PBX system and the network exchange carrier’s central office switching system. For example, several bearer channels could be designated incoming DID trunks, others could be designated two-way CO trunks, and others could be designated clear channel data circuits. Using programming tools, the administrator could reconfigure the mix of trunk services on demand or by a schedule, or could even program the channels to reconfigure themselves based on real-time traffic conditions.

Network carrier services in the 1990s designed to support data communications were also supported by PBX systems. Nortel Networks redesigned its Magellan Passport Asynchronous Transfer Mode (ATM) switching system as a Meridian 1 gateway module to support a mix of voice, data, and video communications over broadband trunk carrier circuits. Lucent Technologies, NEC, and Siemens also introduced ATM network interface options for their respective PBX systems. One of the most important PBX networking advancements in the late 1990s was the introduction of external IP telephony gateways, closely followed by integrated IP trunk gateway port circuit cards. Lucent Technologies was the first to market an integrated IP trunk option and was closely followed by other market leaders, including Nortel Networks and Alcatel.

Tuesday

Video Communications | Features/Function Enhancements

The older generation of PBX station users may remember their first introduction to the videophone at the 1964 New York World’s Fair. Several generations of PBXs have come and gone since 1964, but PBX-based desktop video communications is still a work in progress for most customers. The first major attempts at desktop video communications behind a PBX system occurred during the early 1990s when ISDN BRI options became available. Using both BRI bearer communications channels per video call (128-Kbps transmission rate) provided a fair quality of service, but a killer application for the video option never materialized, and desktop video behind the PBX is rarely implemented today. Desktop video communications today is based primarily on LAN or supported by dedicated trunk circuit facilities.

Lucent Technologies attempted to revive interest in PBX-based video communications in the mid-1990s when it introduced two Definity PBX options designed to support voice calling features on video calls. The MultiMedia Communications Exchange (MMCX) was a server-based system designed to support H.323 mixed-media calling (voice, data, and video). The MMCX provided some basic calling features, including dial plan, conferencing, and call forwarding, to LAN-connected workstations used for video communications applications. The MMCX could also support traffic between PBX ports and LAN peripherals, and a Q signaling (Qsig) link would provide a higher level of PBX system features to the LAN workstations. Another PBX option was called MultiMedia Call Handler (MMCH), which was designed to apply a limited number of voice calling features to ISDN BRI video workstations conforming to H.320 standards. Neither the MMCX nor MMCH offerings gained market acceptance, although the MMCX product was later modified by Lucent and reintroduced as its first Internet telephony gateway product. The IP gateway was further redesigned as an internal IP trunk interface card for the Definity PBX. The concept of the MMCX, a call processing server for LAN workstations, could be considered an early version of today’s emerging IP-PBX systems. Although no IP telephones existed when the MMCX was announced, LAN-based voice communications using a video workstation equipped with a microphone and speaker were supported.

Wednesday

Data Communications | Features/Function Enhancements

Digital PBXs were supposed to be the enterprise data communications network backbone, but some things were not meant to be. The first PBX data communications options were introduced in the early 1980s. In 1980 Intecom was the first to offer a high-speed data module capable of transmission rates of up to 57.6 Kbps. This was at the time when most modems were operating below 9.6 Kbps, and 10-Mbps Ethernet was not yet introduced. After the Intecom announcement, most of the older PBX suppliers announced data module options for their systems with maximum transmission rates ranging from 9.6 to 64 Kbps (Figure 1).


Figure 1: Call center configuration.


Data communications options were available for integrated voice/data or stand-alone data ports. The integrated voice/data port option required a data module that attached to a digital telephone and provided a RS-232C or RS-449 interface for an adjunct data terminal. Asynchronous and synchronous interfaces were usually available from each PBX suppler. Stand-alone data modules were also available and may have required a port circuit card dedicated to data-only communications. The early data modules were priced at about $300 to $500 and required the more expensive digital telephones to work. Most PBX systems at the time were not designed to handle long call holding times and required extensive traffic engineering to support significant customer data requirements. When digital trunks were first available in the mid1980s, the tariffs were very high, and the PBX digital trunk interface cards were expensive compared with analog trunk interfaces. The cost of LAN equipment, at first significantly more expensive than PBX data option pricing, declined rapidly during the 1980s, making it a far more attractive data networking solution than a PBX. PBX data modules, once considered a high-speed option, were viewed as slow when compared with LAN transmission rates. Dreams of the PBX becoming the data networking solution died by the late 1980s when LAN technology matured and network routers first entered the market. Shipment levels of PBX data stations (integrated and stand-alone) never exceeded 3 percent of total annual shipments.

PBXs attempted to make a comeback in the early 1990s by offering a wideband data communications option using an ISDN primary rate interface (PRI) circuit card. By bonding multiple B channels together, a PBX could support transmission rates up to 1.5 Mbps to the desktop and across its digital trunk network. The cost to support the option, however, was seen as excessive because a single wideband port required a dedicated ISDN PRI port circuit card that could cost several thousand dollars. Fujitsu was the first to offer wideband data communications on its F9600 PBX, but customer demand was weak. Other PBX suppliers soon followed the Fujitsu announcement with their own ISDN PRI–based data communications option, but total sales of the option to date have failed to reach 1 percent saturation.

Another PBX system attempt to make a dent in the data communications market came in the mid-1990s when Intecom introduced an Ethernet hub and workstation interface option fully integrated into its port cabinet design. Broadband fiber optic loops between the distributed port cabinets handled intrasystem data traffic and could support Ethernet 10BaseT transmission standards. The broadband data communications option was priced higher than existing LAN interface and switching equipment and failed to find a market.

More than 20 years after the first attempts to position the PBX system as a data communications networking solution, sales of PBX data modules are negligible. The only appreciable data traffic transmitted across a PBX system today is analog-based data communications generated by modems. PBXs are used primarily as a back-up system when LANs are down for service or repair. Ironically, the often unreliable nature of enterprise LANs has made the PBX an invaluable spare data network solution, forcing many voice communications managers to install a significant number of analog ports in support of data modems for use in emergencies. PBX data solutions may not be high speed, but they are reliable.

Sunday

Basic Voice Call Station/System Features | Feature/Function Enhancements

Do station users really need six variations of call forwarding? Do managers still “buzz” their secretaries? Although PBXs have many call forwarding options and still retain the manual signaling (buzz) feature, the most significant station/system feature enhancements during the past two decades have been to improve incoming call coverage, support the needs of the new mobile workforce, and simplify the administration and maintenance operations of the system manager.

An important PBX feature developed in the days before voice messaging systems invaded the workplace was programmed call coverage. Programmed call coverage was a form of enhanced call forwarding, with some important distinctions. First introduced in 1983 by AT&T on the System 85 PBX, call coverage did not receive the market attention it deserved during the 1980s and 1990s, but renewed interest in personalized call screening and routing to improve communications service levels has revitalized the feature. Call coverage capabilities on current-generation PBX systems allow station users to define where incoming calls are directed when they are unable to answer the call and program the coverage path based on who is calling (CLID, Automatic Number Identification [ANI], internal calling number, call prompt), where the call originated (internal or external to the system), how it arrived into the system (trunk group ID), or when a call is placed (time of day, day of week). Building on the concept of call forwarding, personal call coverage programming redirects calls to a defined path of answering stations and will default to the called party’s voice mailbox only as a last resort. Calls will not be redirected to the forwarding position or voice mailbox of a station user defined in the call coverage path; the originally called party’s coverage path overrides intermediary station user call forwarding commands.

Call coverage tables and station user programming was not possible before the development of digital PBXs. The new CTI-based PBX system designs allows station users to program caller-specific call coverage paths based on identified callers. The personal call coverage function in these new-generation systems is supported at the station user desktop (a PC client softphone), not at the common control call processing system. The objective of personalized call coverage features is to reduce dependency on voice mail systems because a human answering station rather than a noninteractive machine might be preferred by the caller. Voice mailboxes should be the last option in a call coverage environment, not the first or only option.

The new mobile workforce includes station users who are rarely in the office and workers who do not have permanent desk assignments because they are constantly moving or their job function is not desk based. To support these mobile workers, it is necessary to dissociate a station user’s telephone directory number from a physical telephone instrument. Hoteling, a feature designed to support workers who work at different desks throughout the enterprise, allows station users to log into the system from a telephone and reassign their directory number to their chosen telephone. In addition to their telephone number, the individual’s station user profile (service levels, call restriction levels, group assignments) is also assigned to the physical telephone location. Account codes and call records are maintained for the station users for each telephone they use. When done using the telephone, after 1 hour, or 1 week, or 1 month, the station user logs out, freeing the telephone for the next mobile worker. Hoteling is becoming very popular in sales offices. The feature can significantly reduce system costs by optimizing common equipment hardware, telephone instrument, and cabling requirements and, more importantly, minimizing real estate requirements (fewer dedicated desks/telephones, less office space).

Today’s mobile workers who are rarely at a fixed telephone location also benefit from recent feature enhancements. The find-me feature allows station users to program their telephone to direct calls to other telephone numbers outside of the PBX system. More than one external number can be programmed. For example, on a no-answer call at the station user desktop, the call can be forwarded to another telephone number after a selected number of rings; if there is no answer at the external number, another telephone number is dialed, and the call is redirected. External telephone numbers likely to be programmed include cellular telephones, home, conference facility, remote office branch, or even a hotel. A relatively recent teleworker option available on some PBXs allows station users to bridge their line appearance to a telephone external to the system. The concept of the PBX as a mobility server can significantly improve call coverage, reduce lost or abandoned calls, and increase the number of successful call attempts between caller and called parties.

Another category of mobile workers consists of station users who require a telephone away from the formal office environment. Known as teleworkers, these station users require their high-performance telephones to function away from the workplace and receive incoming calls redirected to their remote desktop. The original teleworker option was an off-premises extension (OPX) station using highly tariffed telephone trunk circuits to link remote analog station equipment to the main PBX system. Expensive and low-performance analog OPX stations have evolved into affordable and high-performance digital desktops. The same digital telephone supported behind the PBX at the office can be supported remotely with several options, including distance extender modules and analog trunk carrier facilities, ISDN BRI services and equipment, and the recently available IP workstation (hard telephone or PC client softphone).

The most important system feature enhancements during the past decades have been systems administration and maintenance tools. The early PBX management terminals required high-level programming skills and weeks of training. A typical station move, add, or change operation could require at least 15 minutes of keyboard entries. After booting up the systems management terminal the administrator was met by a blank monitor screen waiting for a programming command. There were no menus, on-screen help command, or point, click, and drag. Computer technology evolved during the 1980s and so did PBX management tools. By 1990 a systems management terminal had a basic graphical user interface (GUI), usually a menu selection list and formatted screens. By 2000 PBX management tools were accessed through a web browser via the Internet, and a sophisticated GUI simplified the administration process. Few keyboard entries are now required, and access to a common metadirectory server simplifies the initial station user directory entry.

Saturday

Messaging | Features/Function Enhancements

VMSs were introduced to the market in the early 1980s, and originally worked as stand-alone systems behind PBX systems. Although the first VMSs were designed and marketed by third-party suppliers, several of the leading PBX manufacturers eventually entered the market with products of their own design. Rolm and AT&T were among the first PBX manufacturers to enter the voice messaging market with products designed to work behind their own communications systems, although they could also be engineered as stand-alone systems to work behind other suppliers’ PBX systems.

Northern Telecom, one of the leading PBX suppliers, came late to the VMS market during the late 1980s, but when it introduced Meridian Mail it became the first messaging system to be fully integrated within the PBX system design. Meridian Mail used the Meridian 1 processing and switching network backplane for supporting PBX station user messaging applications. The Meridian Mail Module was installed as another cabinet stack in the Meridian 1 and tightly integrated within the overall PBX system design. Instead of using analog station interfaces and a dedicated data signaling link between the PBX system and adjunct voice messaging cabinet, Meridian Mail ports appeared to the Meridian 1 switching network as just another station port, and signaling between the Meridian Mail Module and the Meridian 1 common control complex was transmitted over the internal system processor bus. AT&T followed Northern Telecom’s example and later redesigned its Audix VMS as a multiple card slot equipment module to be installed within its Definity PBX system. The Definity Audix option offered most of the features and functions available on the larger, stand-alone Audix (later Intuity Audix) system at a reduced price.

During the early 1990s VMSs were redesigned to support integrated messaging applications with e-mail servers. The concept of a UMS designed to support voice and e-mail messaging, with both message mediums sharing a common directory and storage system, was also introduced in the early 1990s. Although demand for the enhanced messaging system designs has been limited to date, there are many productivity and cost benefits attributable to using one mailbox for all types of messages and having a single interface to the mailbox from either a telephone or PC client.

Recognizing the competitive advantage of bundling messaging applications within the PBX system, several recent start-up companies with PBX client/server designs, such as Altigen and NBX (since acquired by 3Com), integrated a UMS application running off the main system server that also provided basic PBX communications features and functions. Recently, Avaya integrated the capabilities of a full-function Intuity Audix system into the main call processing board of its small Definity One PBX system and included the Intuity Integrated Messaging appli- cation on the same board. The Altigen, 3Com, and Avaya PBX systems with the bundled messaging capabilities are designed for small/intermediate customer line size requirements, and the message storage capacities and access ports are limited. PBX systems designed for large and very large customer port requirements would not be able to integrate the messaging application into the main common control complex without affecting the basic communications responsibilities of the system. Dedicated messaging application servers will likely be the optimal solution for higher-end PBX customers, even when IP-PBX client/server system designs become standard by the end of this decade.


Figure 1: Avaya speech access with unified messenger architecture.
Related Posts with Thumbnails

Link Exchange