The Definity was the last in a line of circuit based PBX hardware manufactured since the late 1980s by Avaya, then the former Enterprise Networks division of Lucent and AT&T’s Information Systems unit. The original Definity servers and switches can be enabled to use some versions of Avaya’s later Communication Manager (now known as the Aura) software by using a Media Server to control a Definity switch (or a media gateway in recent releases). The Definity/Communication Manager has about 700 telephony features, one of the largest feature-sets compared to a Nortel Meridian, NEC’s NEAX or Cisco’s CallManager.
Avaya Definity Background
The Definity name began in the late 1980s/early 1990s to replace the System 75 and System 85 branding. A product page on Lucent’s website circa 1998 referred to the Definity as “Definitive Solutions for an Infinite Number of Possibilities” allegedly referring to the name of the system. The Definity system was based on a terminal user interface with real English commands (i.e. “change station 1000″ to change the settings for extension 1000), with step by step call processes called “vectors” with Logo like programming commands.
System 85 would be renamed as the Definity Communications System Generic 2 and the System 75 would be broken up into two separate models. For the Intel based system the system was renamed as Definity Communications System Generic 1 (G1) and a RISC based system that would become G3r. The Definity releases in the 1990s would support native ISDN technology, as a growing standard in digital telephony.
Between Generic 2 (G2) and Generic 3 (G3), the G2 was a larger system with more call coverage, a larger dial plan, and more telephones can be connected to the G2 switch. However, many years later in later releases of the Communication Manager, the dial plan, the telephones connected, and attendant coverage caught up with the old G2 (System 85). The G2/System 85 was built for very reliable voice communications, and the system was built on top of a legacy architecture before data communications, modern personal computers, or Internet abilities. The G2′s legacy can be traced back to the mid 1970s when the AT&T Dimension was in place. When the System 85 was released about a decade after, the system was retooled from the old PCM/analog architecture to a digitally switched system.
In the late 1990s, the Generic 3 (the then System 75) became the new architecture for the Definity system, rebadged as the Definity Enterprise Communications Server (ECS). The G3 was the least system with legacy bloat, with the system being digitally based . A stripped-down model that was similar to the ECS was called the Definity Business Communications System (BCS), was targeted towards hotels and such. Version numbering on the ECS continued from the Definity G3r numbering, with the first branded release under ECS as Release 5 and continued as ECS Release 10 in 2001.

Avaya Definity Hardware and Software
The Definity servers prior to Communication Manager use a proprietary operating system called Oryx/Pecos. The call processing, tone clocks, trunk and phone terminal connections as, well as other digital processing technologies was processed through circuit cards to ensure reliable telephone conversations. The most used setups for a Definity based system would range from small colleges, hospitals, public safety, large corporations or government, department stores, and specific locations that use call centers, because of the programming and administration and user interface that can meet a need for call center applications.
The Definity switches through the respected variants of the systems for many years sold ether in a single carrier cabinet (SCC) or a multi carrier cabinet (MCC.) SCC had about 14 slots and a user count up to about 120, and could be daisy chained to up to 5 carriers per node to about 450 users total per node. The MCC worked as a large mainframe, premise based carrier switch. The MCC contained about 200 slots for a total about 650 users per node. (In Aura Release 5, the SCC and MCC are officially discontinued for software support, with requirement to use a rack formed media gateway similar to the SCC.)
The primary switching unit was the Processor Port Network (PPN) that handled the Oryx/Pecos, and other essential services for the system. For satellite locations within a campus or elsewhere, an Expanded Port Network (EPN) would be used. This would act as a dumb switch, requiring the PPN to operate most of all the features. The respected switching unit could be used on a respective MCC/SCC carriers.
The voice mail system is known as AUDIX (or the Audio Information Exchange.) This was a precursor to modern unified messaging, first used on the System 75 and 85 systems. The AUDIX can handle messages between fax, voice and emails. The AUDIX name is still well known through the voice prompts, even though its branded as other names, such as Intuity Audix or Modular Messaging. Its also known that an everyday phone user would refer a Definity system as “AUDIX” even though the systems operate separate things.
The Communication Manager/Aura powered systems now use Linux as the operating system. Administrators can still access the traditional user friendly terminal administration, or use the web based administrative software, or use a desktop GUI program, the Avaya Site Administration (ASA). Linux knowledge is needed in some ways to configure the gateways and other now appliance based equipment that used to be traditional carrier equipment.
Because the CM based systems now run on applianced based equipment, the same idea of PPN and EPN is still the same. For the main call processing and services, an Enterprise Survivable Server (ESS) would be installed at the primary location of the system. If an event the ESS fails, a Local Survivable Processor (LSP) would be installed in locations that can operate the basic telephony services till the ESS is restored. This can be used for redundancy (like the older systems) or for disaster recovery.
The long time protocol that the Definity telephones connect the switch is called the Digital Communication Protocol or DCP. In later releases of Communication Manager, the system was reworked as SIP being the primary systemwide signaling protocol, while all previous legacy protocols would run under SIP.
Real-time Intelligent Call Routing for Small and Mid-size Businesses To stay competitive, busy contact centers need tools that enable them to monitor their processes in real time – making changes on-the-fly when necessary.
Zeacom, a Gold-level member in the Avaya DevConnect Program, provides an integrated solution that monitors contact centers in real time and delivers intelligent call routing. Zeacom Communications Center (ZCC) offers businesses the tools they need to manage information, improve customer service and boost staff productivity.
With sophisticated computer telephony integration (CTI) based routing features, ZCC dynamically reacts to caller demands and organizes incoming calls based on user defined parameters. Whether customers submit requests over the telephone, email, fax or the Internet, ZCC queues them all and empowers contact center agents to answer each query efficiently and cost-effectively. ZCC’s multimedia interaction modules are fully integrated into a comprehensive reporting package, giving contact center managers a complete picture of agent and call activity across all contact mediums. The Rich Presence functionality in ZCC provides employees with a bird’s eye view of the whereabouts of their colleagues – providing real-time information on staff availability, regardless of their location.
ZCC solutions work with the following Avaya products:
IP office – An intelligent communications solution specially designed to meet the communications challenges facing small and mid-size businesses.
Communication Manager – An open, scalable, and highly reliable telephony solution that provides centralized call control for a resilient, distributed network of media gateways and a wide range of analog, digital and IP-based communication devices.
Application enablement Services (AeS) – An enhanced set of Application Programming Interfaces (APIs), protocols and web services for application developers, ISVs and system integrators providing a new, open platform that supports existing applications and next generation applications and solutions.
Zeacom Communications Center integrates seamlessly with Avaya products, providing a single interface to effectively manage business communications across all media. The solution encompasses an array of features and functionality, including rich presence, sophisticated reporting and administration tools, resolution codes, worktime, queue blocking, alerts and wallboard control.
Intelligent call Routing – Offering complete control of phone, email, fax and web-based contact delivery, skills-based routing matches agent skills and experience to a number of different queues. Each call is delivered to the most appropriately skilled agent available. Similarly, value-based routing can direct high-value customers to the most appropriate agent.
Agent Desktop – Lets agents broaden their scope of customer contact to include email, chat, fax and web-based requests, as well as multiple phone calls. Managers can view real-time information on queue and agent performance, demand calls and change a queue’s operating mode.
Callback – Automated callback keeps a caller’s position in queue without requiring them to hold on the line, advancing the callback request through the queue before delivering it to an agent. Callback allows contact center management and agents to optimize traffic peaks and staffing lows.
Multimedia Queuing modules – Integrates all communication media into the contact center:
Reports – More than 200 customizable reports with meaningful and easy to analyze data about agents, call handling and system setup enable managers to measure contact center performance and administrators to monitor system operations. The on-board database collects ‘cradle-to-grave’ statistics on all types of communication within the contact center.