System and method for implementing an end office switch with enhanced functionality using an operating system independent distributed self-contained dynamic logic system

[0002] The present application claims the benefit of U.S. Provisional Patent Application, assigned serial No. 60/161,388, filed Oct. 26, 1999, which is hereby incorporated by reference in its entirety.

[0003] The present invention generally relates to telephone network functionality, and more particularly, to a system and method for implementing class 5 end office switch functionality with extensions to interface with enhanced services such as voice response circuits, subscriber databases, and carrier databases. The system and method of the present invention are particularly suited for implementation between the physical circuit capabilities (signaling, Dual Tone Multi-Frequency (DTMF), call progress tone generation, and detection) and the transit networks within a telephone network.

[0004] High capacity end office switches, such as the Lucent 5ESS or the Nortel DMS-100/250, have very complex call models which are implemented in software consisting of millions of lines of code. These switching interfaces are designed to comply with standards set by Telcordia Technologies and the International Telecommunication Union (ITU). Telcordia Technologies (formerly Bellcore i.e., Bell Communications Research) is an industry consortium responsible for specifying telecommunications technology generic requirements for North America. The ITU (formerly CCITT i.e. Consultative Committee on International Telegraphy and Telephony) is a United Nations Agency within which governments and the private sector coordinate global telecom networks and services standards recommendations. Compliance with these standards guarantees that most of the standard telephone features will interoperate correctly in mixed manufacturer networks. The sheer size of the complex high-availability software applications that must conform to industry standards requirements makes adding new feature functionality difficult in these products.

[0005] Many of the standard Intelligent Network (IN) features (e.g., Automatic Recall (*69), Automatic Callback (*66 i.e., Bellcore TR-NWT-000227), (*66 i.e., Bellcore TR-NWT-0002215), Conditional Call Forwarding (*40, *42, *72 i.e., Bellcore TR-TSY-000580 and TR-TSY-000586); etc.) use digit sequences which are sometimes difficult to remember and have limited feedback mechanisms to indicate an error condition or guide inexperienced users. Because of this poor, yet simple human interface, some of the sophisticated features are not fully utilized. For example, features that require the user to program conditionals and number lists such as conditional call forwarding, speed dial, and selective call rejection are seldom used to their full potential. The introduction of new readily available technologies such as text to speech, voice processing, voice recognition, and the world-wide-web would be difficult to integrate without standards for interoperability.

[0006] Adding new features requires extensive development and testing initiatives due to the complexities of individual features and the large number of feature interactions that occur between different features. In addition, interacting with callers using voice recognition, or voice response circuits is not possible unless adjunct processing is utilized, since the vast install base of end office switches were not designed to perform these tasks.

[0007] Changes in dialing related features, such as equal access carrier selection, often requires software development and modifications by the switch manufacturer (e.g. Lucent, Nortel, etc.). In order to have true intelligence, many of the features require “network support.” “Network support,” generally implies that messaging between end office switches is required to properly implement the feature. “Network support” requires agreed upon interoperability standards to make features work. This often delays new feature introduction at central office locations that contain a mix of vendor products.

[0008] IN solutions based on “event triggers” managed by service control point (SCP) network elements, require standards based network deployments. These solutions provide distributed features controlled from centrally located SMPs. A SCP is often implemented by a subscribing customer database. To date, very simple applications and call flows have been developed based on the IN architecture.

[0009] Due to deregulation, wide spread availability, and improvements in technology, many non-traditional solutions are being considered for local telephone use, including cable telephone, and wireless services. It is highly desirable for each non-traditional implementation of local telephone service to include all standard phone system functionality, as well as, enhanced services such as voice recognition, voice processing, and text to speech translation.

[0010] In an attempt to satisfy modern customer demands and requirements, administrators of today's switching systems have attempted to integrate different types of computer hardware and operating systems into the central offices. Until now, this mixed environment of computer hardware and operating systems has prevented the distribution of new software applications, which would provide new enhanced features to customers and take full advantage of existing equipment capabilities.

[0011] In order to overcome some of the shortcomings of the traditional standards based network, and to achieve the objects and advantages of the present invention, the invention utilizes a programmable network Edge Switching Point (ESP), a Service Control Point (SCP), and a Service Management Point (SMP). The invention is a system and method for delivering class 5 office functionality with enhanced services such as embedded voice response and voice recognition utilizing a distributed self-contained logic system inserted between the physical circuit capabilities (signaling, tone generation, tone detection), and the transit networks. New sophisticated subscriber features can be activated simply by distributing call-processing logic to edge switching points. Although similar in capabilities to the IN architecture, this logic system is completely self-contained and does not require “network support.” The logic is managed by an SMP. The SMP distributes and manages different versions of the logic as desired by the administrator of the system. The inputs to the logic system are signaling events and subscriber data. The outputs are call establishment requests, tone generation primitives, and tone detection primitives. The signaling inputs include traditional analog loopstart signals such as off-hook, flash-hook, on-hook, as well as GR-303 messages like SETUP, CALL PROCEEDING, ALERTING, CONNECT, CONNECT ACKNOWLEDGE, DISCONNECT, RELEASE, and RELEASE COMPLETE. Call establishment requests include all of the necessary signaling data to establish a network call using any of the following ISUP call setup message parameter elements: Automatic Number Identification (ANI), Dialed Number Identification Service (DNIS), Redirect, Presentation Indicator, Progress Indicator, Automatic Number Identification Information Integers (ANI-II i.e., type of station), and Carrier Identification Code (CIC).

[0012] The logic system was developed using a machine independent software language capable of being installed or updated from a central location. In addition, the language must be of the type that can be parsed and compiled to make subsequent execution efficient, as call processing is a real time application. Software programming and scripting languages that meet these requirements include Java, Java Script, Practical Extraction and Reporting Language, otherwise known as Pathologically Eclectic Rubbish Lister or PERL, and Python. All of these languages have mathematical and string processing capabilities as well as structured programming controls. Each of the above languages is either compiled or interpreted into universal operation code that is operating system and machine independent. Should the logic require dynamic modification, and/or request that a remote feature execute locally, the new logic can be retrieved, parsed, and executed as required. The logic can be distributed via Transmission Control Protocol/Internet Protocol (TCP/IP) as either an American Standard Code for Information Interchange (ASCII) text script file or machine independent compiled applets from a SMP to various SCPs and ESPs. It is important to note that the distributed logic of the present invention is not limited to the software languages previously recited.

[0013] It is an objective of this invention to implement a class 5 switch by receiving and processing edge switch events and sending switching primitive commands in order to setup and tear down calls on a routing network. The logic system which embodies the class 5 switch may be dynamically loaded, and may include innovative extensions to interface and operate with voice response circuits, SCPs, and traditional database architectures. These extensions provide new features and enhanced user interfaces for existing features.

[0014] New sophisticated features will be available by distributing the logic to switching end-points. The solution also scales because the high number of trigger interaction points are managed by the distributed logic, instead of round trip communications to a SCP, as defined in the IN architecture.

[0015] The system and method of the present invention allows for many different types or instances of complete call processing logic simultaneously, allowing different behavior for different user groups and individual users. The logic was further designed so that it may invoke another instance of the logic to permit feature behavior changes in real time for individual users as required.

[0016] Another advantage inherent in the present invention is the ability to deploy new or changed features easily and rapidly. The system and method of the present invention provides centralized distribution of logic to process events with real time updating at multiple remote locations. The system further provides a generalized database access mechanism with large scalability, as well as, a logic system which uses high level programming concepts, such as, control structures, scalar arithmetic, operators, regular expression string manipulation and pattern matching, and structured object-oriented constructs.

[0017] Another advantage of the present invention is that the system provides an “intercept” trigger and line interaction layer between network interfaces and class 4 switching software. The system further provides a user modifiable state table for feature development.

[0018] Another significant advantage of the present invention is that it provides a complete set of user interface controls for use at the intercept logic system layer, including Dual Tone Multi-Frequency (DTMF) detection, Frequency Shift Keying (FSK) data bursts (from other FSK generating equipment and to the telephone subscriber's equipment e.g., caller ID display unit), tone generation, voice prompting, voice recording, and speech recognition.

[0019] The invention can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the concepts of the present invention. Where diagrams could not be captured on a single page, circles identified with a reference numeral, describe connectivity from FIG. to FIG..

[0020] FIG. 1 is a block diagram illustrating the location of the Dynamic Logic System (DLS) of the present invention within a modem end office (EO) in the Public Switched Telephone Network (PSTN) and the telephone station states, events, and digital protocol messages used to interact with the DLS.

[0021] FIG. 2 is a block diagram illustrating the high-level inputs and outputs of the DLS introduced in FIG. 1.

[0022] FIG. 3 is a block diagram further illustrating a system configured to distribute and support the DLS of FIG. 2.

[0023] FIG. 4 is a message sequence chart illustrating how the logic of the DLS of FIG. 2 interacts with the different functional interfaces of an EO switch for the three different configurations shown in FIG. 1.

[0024] FIGS. 5-27 present different portions of a flowchart illustrating station outbound call event processing as further described below.

[0025] FIG. 5 is a flowchart illustrating a station outbound call, a first branch after a station validity check, and a branch on event.

[0026] FIG. 6 is a flowchart illustrating outbound call processing upon a failure event.

[0027] FIG. 7 is a flowchart illustrating outbound call processing upon a station off-hook event.

[0028] FIG. 8 is a flowchart illustrating outbound call processing upon a single digit report or a timeout.

[0029] FIG. 9 is a flowchart illustrating outbound call processing upon a multiple digit report or timeout.

[0030] FIG. 10 is a flowchart illustrating outbound call processing upon an answer event.

[0031] FIG. 11 is a flowchart illustrating outbound call processing upon an attention event.

[0032] FIG. 12 is a flowchart illustrating outbound call processing upon a station on-hook event.

[0033] FIG. 13 is a flowchart illustrating outbound call processing upon a guarded release event.

[0034] FIG. 14 is a flowchart illustrating outbound call processing upon an out-of-service/in-service (OOS/IS) event.

[0035] FIG. 15 is a flowchart illustrating outbound call processing upon a name resolve event.

[0036] FIG. 16 is a flowchart illustrating outbound call processing upon an operator event.

[0037] FIG. 17 is a flowchart illustrating outbound call processing upon a get long distance number event.

[0038] FIG. 18 is a flowchart illustrating outbound call processing upon an international number event.

[0039] FIG. 19 is a flowchart illustrating outbound call processing upon a get carrier event.

[0040] FIG. 20 is a flowchart illustrating outbound call processing upon a get local number event.

[0041] FIG. 21 is a flowchart illustrating outbound call processing upon an N11 feature event.

[0042] FIG. 22 is a flowchart illustrating outbound call processing upon a supplementary feature event.

[0043] FIG. 23 is a flowchart illustrating outbound call processing upon a speed dial event.

[0044] FIG. 24 is a flowchart illustrating outbound call processing upon a route call event.

[0045] FIG. 25 is a flowchart illustrating outbound call processing upon a disable call-waiting event.

[0046] FIG. 26 is a flowchart illustrating outbound call processing upon a malicious trace event.

[0047] FIG. 27 is a flowchart illustrating outbound call processing upon a dial by name event.

[0048] FIGS. 28-30 present portions of a flowchart illustrating station inbound call event processing as described below.

[0049] FIG. 28 is a flowchart illustrating the start of an inbound call, a first branch after a station validity check, and a branch on event.

[0050] FIG. 29 is a flowchart illustrating inbound call processing upon an OOS/IS event.

[0051] FIG. 30 is a flowchart illustrating inbound call processing upon a seize event.

[0052] [1] Advanced PERL Programming by Sriram Srinivansan published by O'Reilly & Associates, Inc.

[0053] [2] Programming PERL by Wall, Christiansen and Schwartz by O'Reilly & Associates, Inc.

[0054] To illustrate the environment of the system and method of the present invention, reference is made to FIG. 1. FIG. 1 is a block diagram illustrating three possible configurations that might be used in the End Office (EO) portion of a Public Switched Telephone Network (PSTN) 8. The PSTN 8 may include local loop equipment, edge switching components, and a class 4 toll routing network.

[0055] Telephone equipment may be integrated with EO switching components via a FXS loop-start circuit 1, a GR-303 Remote Digital Terminal (RDT) 5, or a Voice Over Internet Protocol (VoIP) router 11. It is important to note that for the three different configurations shown in FIG. 1, the voice circuit or data link may be implemented on any of the common Digital Signal Hierarchy (DSH) (e.g., DS1/T1, DS3/T3 etc.) or SONET/Synchronous Digital Hierarchy (SDH) (e.g. OC1, OC3/STM-1 etc.) signals.

[0056] Signaling between the FXS loop-start circuit 1 and a digital matrix switch 2 may be implemented using off-hook, on-hook, and flash-hook signals from the FXS loop-start circuit 1 to the digital matrix switch 2. Similarly, release and ringing signals may be integrated from the digital matrix switch 2 to the FXS loop-start circuit 1.

[0057] Signaling information between a GR-303 RDT 5 and the digital matrix switch 2 is transferred via a combination of a GR-303 Integrated Digital Terminal (IDT) 6 using non-standard Q.931 messages to setup and tear down timeslot allocation and robbed bit signaling for call control. SETUP and RELEASE COMPLETE messages flow from the GR-303 RDT 5 to the GR-303 IDT 6. Conversely, CONNECT and RELEASE messages flow from the GR-303 IDT 6 to the GR-303 RDT 5. Flash-hook signals flow from the GR-303 RDT 5 directly to the digital matrix switch 2, and ringing signals flow from the digital matrix switch 2 directly to the GR-303 RDT. To complete signal transmittal between the GR-303 RDT 5 and the digital matrix switch 2, off-hook and on-hook signals may be further integrated from GR-303 IDT 6 to the digital matrix switch 2. Conversely, a release signal may be integrated to traverse the gap between these two components in the opposite direction.

[0058] Signaling between a VoIP router 11 and a Media Gateway Control Protocol (MGCP) or H.323 VoIP interface 12 integrated with the digital matrix switch 2 may be completed by SETUP and RELEASE COMPLETE signals configured to transmit from the VoIP router 11 to the VoIP interface. Conversely, CONNECT and RELEASE messages may be further configured in the opposite direction between these components. Alternatively, a packet data link may bridge the gap between an embedded tone detector/generator 13 integrated with the VoIP router 11 and the VoIP interface 12. The two-way packet data link may be an Asynchronous Transfer Mode (ATM), 100baseT, OC3, or OC12 link.

[0059] Having described the local loop equipment interface with the EO switching components, reference is now directed to the remaining EO switching components illustrated in FIG. 1. In this regard, the network access side of the digital matrix switch 2 may include a Signaling System Number 7 (SS7) signaling stack 3, a plurality of tone detector/generator circuits 7, and a plurality of voice response circuits 9. In addition, the network access side of the digital matrix switch 2 may include an interface to a DLS 14 consistent with the system and method of the present invention. The DLS 14 operates at the interface between the physical connections to the telephonic interfaces (local loop equipment previously described) and a routing network.

[0060] Signaling between the EO switching components and the class 4 routing network and central equipment may be accomplished via a Signal Transfer Point (STP) 4 in communication with the SS7 signaling stack 3. Alternatively, a tandem transit switch 10 may be integrated to the digital matrix switch 2 via a DS1, a DS3, an OC3, or an OC12 voice circuit.

[0061] Having described that portion of a PSTN 8 illustrated in FIG. 1, reference is now directed to FIG. 2. FIG. 2 further illustrates the DLS 14 introduced in FIG. 1. A End Office (EO) system may comprise an Edge Switching Point (ESP) 20, a Service Management Point (SMP) 28, and a Service Control Point (SCP) 32. The SMP 28 may be configured to dynamically distribute logic 35 programmed to implement class 5 functionality through the ESP 20 at the digital matrix switch 2 (see FIG. 1). As further illustrated in FIG. 2, the SMP 28 may be configured to dynamically update or modify logic 35. Having been provided with a plurality of functional programs, the logic 35 may interface with the ESP 20, enhanced services (ES) 26, the SCP 32, a Time-Out Queue (TOQ) 23, and the Transit Network (TN) 30 to connect and service customers integrated with the local loop equipment of the PSTN 8 (not shown). The logic 35 as illustrated in FIG. 2, may be programmed to receive ESP events 21, TOQ events 22, and Transit Network (TN) events 29. Logic 35 may be further programmed to both send and receive ESP primitives 24, ES primitives 27, SCP primitives 33, TOQ primitives 25, and TN primitives 31.

[0062] Having introduced the hardware and interfaces of the DLS 14 in FIG. 2, reference is now directed to FIG. 3, which further illustrates a network hardware configuration that may be used to implement and maintain the operating system independent distributed self-contained dynamic logic system. In this regard, the DLS 14 may comprise the SMP 28 and the logic 35. As shown in FIG. 3, the ESP 20, the SMP 28, and the SCP 32 may be implemented with computers in communication with each other on a network 40. The network 40 may be a computer network capable of data packet transfer using TCP/IP or alternatively, the SS7 protocol. The logic 35 may control an ESP 20 and may be used to control a digital matrix switch 2 at an EO in the PSTN 8 (not shown).

[0063] The SMP 28 may be a standard computer capable of running the SCO-Unix Openserver 5.0 Operating System. The SMP 28 may also contain disk drives and SCSI disk controllers to enable persistent storage of data and service logic. The SMP 28 may be further integrated with an external data storage device capable of storing and retrieving the logic 35 under control of the SMP 28. The SMP 28 provides for management and distribution of the logic 35 of the DLS 14 in order to control the ESP 20.

[0064] The ESP 20 may be a standard computer capable of running the SCO-Unix Openserver 5.0 Operating System. The ESP 20 may also contain disk drives and SCSI disk controllers to enable persistent storage of data and the logic 35 of the DLS 14. The ESP 20 may be configured to manage the line interfaces and protocols and receives instruction from the SMP 28.

[0065] The ESP 20 may be implemented with a Cisco AS5300 access server modified to perform the methods described herein. To perform voice response, and voice recognition functionality, a series of Natural MicroSystems AG-Dual Span T1 Voice Processing cards (not shown) may be used. The AS5300 access server terminates digital bearer channels and provides direct conversion to packet networks for voice traffic.

[0066] The SCP 32 may be a standard computer capable of running the SCO-Unix Openserver 5.0 Operating System. The SCP 32 may be configured with disk drives and SCSI disk controllers to enable persistent storage of data. The SCP 32 may be further integrated with an external data storage device capable of storing and retrieving user data 43 under the control of the SCP 32. In this regard, the SCP 32 may provide subscriber data storage as further described herein.

[0067] It should be noted that the user database information which may be stored in the SCP 32, the distributed logic 35, and the SMP 28 for distribution to control one or more ESPs 20 may be embodied in any computer-readable medium for use or transport. In the context of this document, a “computer-readable medium” can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic) having one or more wires, a portable computer diskette (magnetic), a random access memory (RAM) (electronic), a read-only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM, EEPROM or Flash memory) (electronic), an optical fiber (optical), and a portable compact disc read-only memory (CD-ROM) (optical). Note that the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in computer memory.

[0068] The system and method of the present invention delivers class 5 functionality with embedded voice response and voice recognition utilizing a distributed self-contained logic system inserted between the physical circuit capabilities (signaling, tone generation, tone detection), and the transit networks. Although similar in capabilities to the IN architecture, this logic system is completely self-contained and does not depend nor utilize traditional IN network triggers. The logic 35 of the DLS 14 is managed by the SMP 28. The SMP 28 distributes and manages different versions of the logic 35 as required to implement the many combinations of selected services requested by individual telephone service customers. As previously described in relation to FIG. 2, the inputs to the logic 35 are signaling events and SCP 32 user data, the outputs are call establishment requests, tone generation primitives, and tone detection primitives (not shown). The signaling inputs include traditional analog loopstart signals such as off-hook, flash-hook, on-hook, as well as GR-303 messages like SETUP, CALL PROCEEDING, ALERTING, CONNECT, CONNECT ACKNOWLEDGE, DISCONNECT, RELEASE, and RELEASE COMPLETE. Call establishment requests include all of the necessary signaling data to establish a network call using any of the following ISUP call setup message parameter elements: Automatic Number Identification (ANI), Dialed Number Identification Service (DNIS), Redirect, Presentation Indicator, Progress Indicator, Automatic Number Identification Information Integers (ANI-II i.e., type of station), and Carrier Identification Code.

[0069] The logic 35 of the DLS 14 was developed using a machine independent software language capable of being installed or updated from a central location. In addition, the language must be of the type that can be parsed and compiled to make subsequent execution efficient, as call processing is a real time application. Software programming and scripting languages that meet these requirements include Java, Java Script, Pathologically Eclectic Rubbish Lister (PERL), and Python. All of these languages have mathematical and string processing capabilities as well as structured programming controls. Each of the above languages is either compiled or interpreted into universal operation code that is operating system and machine independent. Should the logic 35 require dynamic modification, and/or request that a remote feature execute locally, the new logic 35′ (not shown) can be retrieved, parsed, and executed as required. The logic 35 can be distributed via Transmission Control Protocol/Internet Protocol (TCP/IP) as either an American Standard Code for Information Interchange (ASCII) text script file or machine independent compiled applets from a SMP 28 to control an ESP 20. It is important to note that the distributed logic 35 of the present invention is not limited to the software languages previously recited. In one embodiment of the present invention, the logic 35 is implemented using the PERL programming language. The DLS 14 disclosed herein is based on embedding a PERL interpreter between signaling events from a Class 5 switching endpoint and a Class-4 routing or transit network. The PERL interpreter is embedded [1], which means it is compiled into the C programming language software application which controls the digital matrix switch 2 (not shown). All telephony signaling events are passed to the PERL script in order to provide communication and event management with the ESP 20. Additionally, the PERL script may receive TN events 29 from the Class-4 routing and transit network. A station request is one example of a TN event 29. In addition, extensions were made to the PERL interpreter [1] which included a new set of commands for interacting with the ESP 20.

[0070] Embedding is a method of integrating a PERL language interpreter directly into an existing software application. Thus, the PERL source code is compiled into the application (or dynamically linked at run time) to produce a single executable entity for run time execution. Embedding provides a very efficient mechanism for calling or executing PERL instructions from within the software application.

[0071] Extending is a method of adding new functionality to the PERL language. These new commands can be used inside a PERL script which permits the PERL script to process telephony events as in the system of the present invention.

[0072] The logic 35 may be configured to provide a user modifiable state table for feature development. In this regard, the logic 35 of the DLS 14 is easily modified using any ASCII text editor.

[0073] A. LOGIC INPUTS

[0074] Logic 35 inputs may consist of SCP 32 data and events. In this regard, the SCP 32 data may contain user identification information associating a particular customer with a particular station on the digital matrix switch 2. In addition to user identification information, each station may be associated with a number of user selectable service features such as Caller Identification (CallerID), call waiting (CW), and the like. Events are characterized by user generated signaling changes such as on-hook, off-hook, flash-hook, or DTMF generated digit.

[0075] 1. DATA

[0076] There are two kinds of data, static and dynamic. Static data requires service provider administrative intervention to alter. Dynamic data is user modifiable and may be automatically updated under certain conditions and is retained until subsequently modified. An example of static data may include directory numbers associated with network edge physical end-points. An example of dynamic data might include a last number redial, which changes each time a number is dialed. The dynamic data could be stored in volatile memory, while static data should be committed to non-volatile storage means such as a hard disk drive.

[0077] Each station may be provided with a permanently stored forwarding Directory Number (DN). The DN may be used to populate a Default Call Forward Field, which overrides the Call Forward Busy and Call Forward Ring No Answer fields, which may be supplied by a system administrator. The UNCONDITIONAL forward supersedes all other forward numbers, and is only maintained through a screen interface. In addition, supplementary feature indicators for Call-Waiting, and Call-Transfer may be stored either statically or dynamically.

[0078] a. STATION DATA

[0079] Each station represents a network end-point address representing a physical end point. Examples of these addresses include:

[0080] 1. IDT: RDT: CRV. Defines an endpoint in a GR-303 signaling environment. This addressing scheme identifies a unique station location based on the physical equipment. The IDT (or Digital Subscriber Line Access Multiplexer (DSLAM)) is the central office integrated data terminal interface, while the RDT is the remote digital terminal. The CRV (station) is one of 2048 possible logical timeslot addresses on each RDT.

[0081] 2. TCP/IP Address. Defines an endpoint in a VoIP network. This address would contain four numbers separated by periods to indicate parts of an address. A typical TCP/IP address might look like 132.147.160.100.

[0082] 3. SPAN: CHANNEL. May define an endpoint in a small programmable switch environment when FXS Loopstart signaling is used where the span represents the T1 or T3 circuit identifier, and the channel represents the time slot offset within the span.

[0083] 4. Time Slot. May define an endpoint in a small programmable switch environment like that provided by the Cisco VCO-4K switch described in this application.

[0084] 5. Loop: Shelf: Card: Offset. A hierarchical addressing scheme for referencing hardware within a central office switching system.

[0085] Each end-point address may have data, state, and features associated with it. The data may include the different telephone numbers associated with the end-point. In this regard, telephone numbers may be used to map outbound calls to physical addresses. Other data might include forwarding numbers, billing numbers, accounting numbers, and possibly name and address data of the party using the end-point. End-point state information may include a service state for the end-point (in-service, out-of-service) and application related states like collecting digits, and releasing. Feature data might include indicators of which class features are enabled or disabled.

[0086] The following data definition may be used with the system and method of the present invention. Database index keys are indicated with a “**” in the “Contents” field.

[0087] The station data is indexed by both physical addresses and telephone number addresses. Thus, when a call is generated by a physical end-point, the features can be accessed directly, and the restricted numbers and speed dial numbers can be accessed directly as well. For calls directed to end-points, the telephone directory numbers may be used as efficient data search keys to obtain the end-point addresses for routing of the telephone call. The following table (Table 7) is a definition in the “C” programming language of the data structures defined above. A Call Reference Value (CRV) is considered a station when GR-303 signaling is used.

[0088] 2. EVENTS

[0089] The programmable logic 35 disclosed herein is used to process events. Events originate from several locations in the system of the present invention. More specifically, events originate from an edge station device, the class 4 routing or transit network 30, the integrated time-out queue 23 from within logic 35, and from ES processing ports.

[0090] Event processing is a mechanism for receiving an indication that a particular state change has occurred, followed by a stream of logic which may result in waiting for the next event. The logic stream processes the event, sets time-outs, and establishes an application state. As application states are determined, and transitions between application'states occur, the logic 35 will queue transmit primitives to both the edge station device and the class-4 routing or transit network.

[0091] a. EDGE SWITCH POINT EVENTS

[0092] The following events are defined to originate in the network edge device. These events are directly generated by the “station” for which EO functionality is provided. All ESP events 21 are directed towards the logic 35.

[0093] ESP_call_arrival(port_address, Station ID)

[0094] This event is a “trigger” sent from the ESP 20 to the logic 35 to indicate that a call has arrived. The port_address refers to the actual physical hardware address for the edge originated call. This is the address used for all tone detection, generation, and switching activities. The RDT:CRV address components are used to identify the subscriber endpoint in GR-303 originated calls. For cases when the GR-303 signaling is not used, the source address for identifying the subscriber is the actual hardware address indicated by the “port address” argument. The top 8 bits of the port address may be placed into the RDT field, and the bottom 8 bits may be placed into the CRV. This ensures that a RDT:CRV pair exists for every call. Upon receipt of this port address, the logic 35 generates a map to associate the physical port with the logical RDT:CRV address. This permits all subsequent events to be based on a RDT:CRV pair that defines the actual unique caller instance.

[0095] ESP_digits_received(STATION ID,Digit String)

[0096] This event is a “trigger” sent from the ESP 20 to the logic 35 to indicate that a digit has arrived. The digit string may contain one or more digits. The digits are utilized by the logic 35 to determine what to do.

[0097] ESP_flash_detected(STATION ID)

[0098] This event is a “trigger” sent from the ESP 20 to the logic 35 to indicate a “flash” has arrived.

[0099] ESP_answer(STATION ID)

[0100] This event is a “trigger” sent from the ESP 20 to the logic 35 to indicate an “answer” was detected on the previously placed call.

[0101] ESP_tone_complete(STATION ID)

[0102] This event is a “trigger” sent from the ESP 20 to the logic 35 to indicate a tone has completed playing. This may be used to trigger either a subsequent tone or the next event, such as, a recorded announcement.

[0103] ESP_released(STATION ID)

[0104] This event is a “trigger” sent from the ESP 20 to the logic 35 to indicate that the station is now on-hook.

[0105] ESP_port_parked(STATION ID)

[0106] This event is a “trigger” sent from the ESP 20 to the logic 35 to indicate that the other side of a connected call has released.

[0107] ESP_port_oos(STATION ID)

[0108] This event is a “trigger” sent from the ESP 20 to the logic 35 to indicate that the port which was carrying a particular station call has gone out-of-service.

[0109] b. CLASS-4 ROUTING OR TRANSIT NETWORK EVENTS

[0110] The Transit Network Event (TNE) may be used for sending and receiving calls from a transit network. The transit network may be implemented by a SS7 based Class-4 switching network.

[0111] TNE_station_wanted(STATION ID,Reference)

[0112] The ESP 20 sends this event from the routing network to the logic 35 when the transit network desires to complete a call to a signaling endpoint managed. The reference number may be used for future commands used to control the pending call.

[0113] c. TIME-OUT QUEUE EVENTS

[0114] This event is used for injecting an artificial event to check for or guard the arrival of anticipated events. The TOQ event 22 may also be used to provide an orderly transition for time-based features.

[0115] TOQ_timeout(STATION ID)

[0116] This event is a “trigger” indicating that a previously registered time-out has actually expired. Individual applications may take action based on the current state information associated with the application.

[0117] B. LOGIC OUTPUTS—PRIMITIVES

[0118] Both the ESP 20 and the Class-4 routing or transit network 30 may be controlled by primitive operations that were added to the PERL language via extensions. These primitives may be executed by the logic 35 as a response to received events and the current defined cumulative state based on previously received events. The sequence of primitives can be modified easily since the language is flexible and dynamically interpreted.

[0119] 1. EDGE SWITCH POINT PRIMITIVES

[0120] Edge switch point primitives 24 (see FIG. 2) are a mechanism for the logic 35 to provide specialized services at the EO switch.

[0121] ESP_switch_listen(port address)

[0122] This primitive may queue the attachment of a DTMF or touch-tone digit detector to the port.

[0123] ESP_Switch_connect_tone(port address, tone, cycles, report)

[0124] This primitive may indicate the attachment of a tone to the port for a particular number of cycles. An option to report when the tone is complete is provided.

[0125] ESP_Switch_disconnect_tone(port address)

[0126] This primitive may indicate the disconnection of a tone from a port.

[0127] ESP_Switch_ignore(port address)

[0128] This primitive may indicate the removal of a DTMF or touch-tone digit detector from a port.

[0129] ESP_Switch_collect_digits(port address, digits, time-out)

[0130] This primitive may indicate the detection of an exact amount of digits within a particular time-out.

[0131] ESP_Switch_play_prompt(port address, prompt)

[0132] This primitive may indicate the playing of a prompt to a port for providing special messages.

[0133] 2. CLASS-4 ROUTING OR TRANSIT NETWORK PRIMITIVES

[0134] Transit network primitives 31 (see FIG. 2) are a mechanism for the logic 35 to provide specialized services at the equal access end of an office switch.

[0135] TNE_process_call(port_address, RDT, CRV, CalledNumber, CallingNumber, Redirect, Reason, Progress, OLI, Presentation, Screening, CIC)

[0136] This primitive may be used to submit a call to the transit network for routing. All information required to route the call may be provided.

[0137] TNE_queue_outdial(reference)

[0138] This primitive may be used to direct the routing network to route a previously submitted call to the station.

[0139] TNE_requeue_outdial(reference, new_telnumber)

[0140] This primitive may be used to redirect the call for a particular station to another directory number as performed in call forwarding.

[0141] TNE_find_waiting_call(STATION ID)

[0142] This primitive may be used to locate a call for a station when a station owner “flashes” for call-waiting.

[0143] TNE_caller_gets_error(reference)

[0144] This primitive may be used to reject a call by reference for an invalid CRV.

[0145] TNE_caller_gets_busy(reference)

[0146] This primitive may be used to provide subscriber busy treatment for an inbound call to a station when the subscriber is on the phone.

[0147] TNE_connect_to_requestor(STATION ID, reference)

[0148] This primitive may be used to connect an inbound call to a station, with any previously connected caller going on hold. This may be used to toggle between calls when using call waiting.

[0149] TNE_connect_to_conference(Station ID, Conference ID)

[0150] This primitive may be used to connect an inbound or outbound call to a conference bridge.

[0151] TNE_conference_initiate(Station ID)

[0152] This primitive may be used to create a conference call (for up to 9 parties). The primitive returns a conference id used for further commands. The conference is automatically de-allocated when the station goes idle.

[0153] TNE_park_port(Station ID)

[0154] This primitive may be used to park the current station and any connected parties or conference.

[0155] TNE_release_port(Station ID)

[0156] This primitive may be used to hang-up stations when the station is already on hook. Thus, this is used to stop “ringing” a phone.

[0157] 3. DATABASE PRIMITIVES

[0158] Database or SCP primitives 33 (see FIG. 2) are used to retrieve user information required to provide specialized service at the EO switch. The data may be requested through the following methods.

[0159] Station_valid(STATION ID)

[0160] This primitive returns TRUE or FALSE indicating that service is to be provided or denied for the CRV.

[0161] Station_dial_capabilities(STATION ID)

[0162] This primitive returns a bit mask of dialing capabilities.

[0163] Station_features(STATION ID)

[0164] This primitive returns a bit mask of feature capabilities.

[0165] Station_speed_dial(STATION ID,Index)

[0166] This primitive returns a number to dial for a particular speed dial entry. The primitive returns an empty string if the index is not defined.

[0167] Station_spel_num_read(STATION ID, Special_number)

[0168] This primitive returns a full telephone number which is appropriate for the station based on the special number dialed. This is used to translate 911, 611, 411, and 311 to the various real network addresses.

[0169] Station_forward_default_read(STATION ID)

[0170] This primitive returns the default forwarding number for a station.

[0171] Station_forward_busy_read(STATION ID)

[0172] This primitive returns the call-forward busy number for a station.

[0173] Station_forward_no_answer_read(STATION ID)

[0174] This primitive returns a call-forward no answer number for a station.

[0175] Station_forward_unconditional_read(STATION ID)

[0176] This primitive returns the call-forwarding unconditional number for a particular station.

[0177] Station_local_cic_read(STATION ID)

[0178] This primitive returns a carrier indicator code for local outbound calls for a particular station.

[0179] Station_Id_cic_read(STATION ID)

[0180] This primitive returns a long distance carrier indicator code for long distance calls from a particular station.

[0181] Station_pres_indicator_read(STATION ID)

[0182] This primitive returns a default presentation indicator for outbound calls made by a station.

[0183] Station_billing_read(STATION ID)

[0184] This primitive returns a billing number to use for all calls made by this station.

[0185] Station_primary_dir_number_read(STATION ID)

[0186] This primitive returns a default directory number for a station, which becomes the ANI for all outbound calls made from this station.

[0187] Station_alt1_dir_number_read(STATION ID)

[0188] This primitive returns a first alternate number for this station used in distinctive ring situations.

[0189] Station_alt2_dir_number_read(STATION ID)

[0190] This primitive returns a second alternate number for this station used in distinctive ring situations.

[0191] Station_speed_dial_write(STATION ID,Index,Number)

[0192] This primitive updates a speed dial index with a particular telephone number for a station.

[0193] Station_forward_unconditional_write(STATION ID,Number)

[0194] This primitive updates a call-forwarding unconditional number for a station.

[0195] Station_find_by_name(digits)

[0196] This primitive finds a station based on a last name, first name entry in the database. The primitive reports the number of matches found and an array of possible matches.

[0197] 4. ENHANCED SERVICE PRIMITIVES

[0198] Enhanced service primitives 27 (see FIG. 2) are a mechanism for the logic 35 to provide enhanced voice directed services at the EO switch.

[0199] ES_play_prompt(STATION ID,prompt)

[0200] This primitive plays a prompt to a station.

[0201] ES_voice_recognition(STATION ID,vocabulary)

[0202] This primitive performs a voice recognition function on a station. The primitive returns two values, one is a index number which has meaning within the vocabulary. The second, is a score indicating how reliable the recognition was.

[0203] ES_text_to_speech(STATION ID,text)

[0204] This primitive turns the text into spoken speech for performing text-to-speech functionality. This could be used to speak names of calling parties, and possibly to speak messages to station owners.

[0205] ES_record_speech(STATION ID, minlength, maxlength)

[0206] This primitive records speech and returns a reference pointer to the recorded speech.

[0207] ES_playback_speech(STATION ID,reference)

[0208] This primitive plays the results of the ES record_speech( ) primitive to a subscriber.

[0209] ES_arbitrate_list(list)

[0210] This primitive uses enhanced service resource ports to present a list of possible choices (as in a possible list of names found in a directory name search). The caller may select one from the list presented.

[0211] 5. TIME-OUT QUEUE PRIMITIVES

[0213] TOQ primitives 25 (see FIG. 2) are a mechanism for the logic 35 to provide time-related responses at the EO switch.

[0214] Toq_insert(RDT:CRV, time-out value, time-out data);

[0215] This primitive provides a “future callback” which may contain the time-out data for determining what to do. The RDT:CRV becomes a “unique” key and is used to cancel the time-out if necessary.

[0216] Toq_remove(RDT:CRV)

[0217] This primitive provides for the removal and cancellation of all pending time-outs for the RDT:CRV.

[0218] C. FEATURES

[0219] To illustrate the invention, a list of Class-5 features is presented below. The list is representative of the standard Class-5 features supported and described in the above set of reference standards.

[0220] 1. 3 DIGIT NUMBERS OF A PATTERN—N11

[0221] These numbers will force an immediate connection to either a singular number, or routing to a number based on the ANI of the caller. Entries for specifying the location of these services may be stored in the call routing table.

[0222] 311 Non-Urgent Police/Fire

[0223] 411 Information

[0224] 611 Service

[0225] 911 Emergency

[0226] This feature provides means for connecting a particular station to the nearest police or fire dispatcher without knowing the number. The 311 service is identical to 911, with the exception that the call is assumed to be non-urgent. One other distinction is that, should the station end hang-up, the call is cleared.

[0227] Callers Experience:

[0228] The caller will pickup the telephone, and hear a dial tone. Upon dialing the first digit (a ‘3’), the dial tone will stop playing, and there will be silence on the line. The time-out before expecting another digit will be very long. The subsequent ‘1’ is entered, and when the second ‘1’ is entered, the call will immediately be connected to the appropriate police/fire number. If either side hangs up, the call is cleared.

[0229] Static Data Requirements:

[0230] Each station will need to be provisioned with a “Police/Fire Dispatch” number, or use a generic number based on a numbering plan area (NPA) more commonly known as an area code, or use a geographic determination of the correct location to dial.

[0231] This feature provides means for connecting a particular station to directory service without knowing the number. This service is identical to the 611 service, with the exception that a “release link” transfer option is supported through either “flash” or TCP/IP signaling from the operator service center.

[0232] Callers Experience

[0233] The caller will pickup the telephone, and hear a dial tone. Upon dialing the first digit (a ‘4’), the dial tone will stop playing, and there will be silence on the line. The time-out before expecting another digit will be very long. The subsequent ‘1’ is entered, and when the second ‘1’ is entered, the call will immediately be connected to the appropriate directory service number. If either side hangs up, the call is cleared. If the operator side “flashes”, then an address is collected and the callers call is re-routed. There is an equivalent mechanism for supporting TCP/IP.

[0234] Static Data Requirements

[0235] Each station will need to be provisioned with a “Directory Service” number, or use a generic number based on NPAINXX or geographic determination.

[0236] This feature provides means for connecting a particular station to customer service without knowing the number. The 611 call is assumed to be non-urgent, and all features are enabled for the duration of the call, including call waiting. The “presentation indicator” is always forced to forward the ANI to the customer service attendant.

[0237] Callers Experience:

[0238] The caller will pickup the telephone, and hear a dial tone. Upon dialing the first digit (a ‘6’), the dial tone will stop playing, and there will be silence on the line. The time-out before expecting another digit will be very long. The subsequent ‘1’ is entered, and when the second ‘1’ is entered, the call will immediately be connected to the appropriate customer service number. If either side hangs up, the call is cleared. During the call, call-waiting tone will be heard when an inbound call arrives for the station. When the tone is heard, a flash will place the customer service number on hold, and the station will be connected to the inbound call. Another “flash” returns the station to the customer service number.

[0239] Static Data Requirements:

[0240] Each station will need to be provisioned with a “Customer Service” number, or use a generic number based on NPA/NXX or geographic method.

[0241] This feature provides means for connecting a particular station to the nearest police or fire dispatcher without knowing the number. The call is assumed to be urgent. Should the station end hang-up, the call is not cleared, and the connection is maintained. This permits the station to be permanently connected to the 911 operator until the 911 operator releases the call.

[0242] Callers Experience:

[0243] The caller will pickup the telephone, and hear a dial tone. Upon dialing the first digit (a ‘9’), the dial tone will stop playing, and there will be silence on the line. The time-out before expecting another digit will be very long. The subsequent ‘1’ is entered, and when the second ‘1’ is entered, the call will immediately be connected to the appropriate police/fire number. Once the 911 operator hangs up, the call is cleared. Otherwise, the station remains connected to the 911 operator.

[0244] Static Data Requirements:

[0245] Each station will need to be provisioned with a “Police/Fire Dispatch” number, or use a generic number based on NPA/NXX or geographic location.

[0246] 2. STANDARD CALLING

[0247] If a caller enters a normal 7 or 10 digit North American numbering plan (NANP) number or an international number, then the call will be completed to the desired destination. The inbound call interaction (creating a call-waiting condition) is shown, but wouldn't occur if the subscriber had disabled call-waiting, or the feature was administratively disabled. Thus, it is the responsibility of the EO logic to determine if the feature is to be available at time of use. This is required for the scenario when a subscriber is already engaged with an original call and a call-waiting call, and a subsequent call arrives which would result in a busy treatment to the last incoming call.

[0248] Callers Experience:

[0249] The caller will pickup the telephone, and hear a dial tone. Upon dialing the first digit, the dial tone will stop playing, and there will be silence on the line. The time-out before expecting another digit will be very long. The digits are entered. If a “local” pattern is detected by use of the logic 35 pattern matching, then the call is completed without delay. For numbers which are entered as international, a time-out or “#” is used to terminate digit collection. If either side hangs up, the call is cleared.

[0250] Outbound call restrictions may be applied when the call enters the “Outdial State”. If the call is to a restricted address (defined by the administrator on a subscriber basis), then failed call treatment is provided. Invalid phone numbers detected by the dial-plan, or valid destinations that are not allowed by the call type or carrier configuration are provided failed call treatment as well. Failed call treatment begins with a special intercept tone (SIT) followed by an announcement (different one for each failure) followed by a numeric code indicating diagnostic information.

[0251] Prefixing the number with a *70 will disable call waiting for the duration of the call. If call waiting is disabled, the inbound call is not introduced into the state diagram.

[0252] Prefixing the number with a *67 will set the outgoing presentation to block caller ID at the receiving end.

[0253] Static Data Requirements:

[0254] All outbound call restriction patterns for each station need to be stored in the database. Additionally, dial-plan resolution of telephone numbers needs to be supported for further validation. Local, long distance, and international call restrictions need to be checked.

[0255] For each station, both the default presentation indicator, and the override value must be retained. The override value is reset when the call is cleared.

[0256] For each station, both the default caller waiting availability and the call by call override value must be retained. The override value is reset when the call is cleared.

[0257] This feature provides means for connecting a particular station to an inbound call attempt without knowing the number. The call is assumed to be an outbound call like any other, but the number is retrieved from the static data store.

[0258] Callers Experience:

[0259] The caller will pickup the telephone, and hear a dial tone. Upon dialing the first digit (a ‘*’), the dial tone will stop playing, and there will be silence on the line. The time-out before expecting another digit will be very long. The subsequent ‘6’ is entered, and when the second digit, ‘9,’ is entered, the call will immediately be connected to the last inbound attempt (answered or unanswered) number. If either side hangs up, the call is cleared.

[0260] Should there be no “last inbound attempt number” registered in volatile memory, then the system will provide error treatment.

[0261] The *70 and *67 features can't be combined with the *69 feature. Thus, the default presentation indicators, and the default call-waiting status is used for all *69 calls. Carrier selections used include only the default carrier.

[0262] Static Data Requirements:

[0263] Each station will have temporarily stored the last inbound number attempted. This data will be kept in volatile memory, so that a system restart will “clear” the last inbound number.

[0264] This feature provides means for connecting a particular station to the last number dialed not knowing the number. The call is assumed to be an outbound call like any other, but the number is retrieved from the static data store.

[0265] Callers Experience:

[0266] The caller will pickup the telephone, and hear a dial tone. Upon dialing the first digit (a ‘*’), the dial tone will stop playing, and there will be silence on the line. The time-out before expecting another digit will be very long. Once the subsequent ‘9’ is entered, the call will immediately be connected to the last number dialed (not a feature number, but valid telephone number). If either side hangs up, the call is cleared.

[0267] Should there be no “last dialed number” registered in volatile memory, then the system will provide error treatment.

[0268] The *70 and *67 features can't be combined with the *9 feature. Thus, the default presentation indicators, and the default call-waiting status is used for all *9 calls. Carrier selections are not retained. Thus, only the default carrier is used.

[0269] Static Data Requirements:

[0270] Each station will have temporarily stored the last number outbound attempt. This data will be kept in volatile memory, so that a system restart will “clear” the last inbound number.

[0271] This feature provides means for setting the forwarding number.

[0272] Callers Experience:

[0273] The caller will pickup the telephone, and hear a dial tone. Upon dialing the first digit (a ‘*’), the dial tone will stop playing, and there will be silence on the line. The time-out before expecting another digit will be very long. The subsequent 2 digits are entered (72, 42, 68), and the caller will hear a secondary dial tone. This dial tone will indicate that the forwarding telephone number should be entered. Only valid telephone numbers can be entered. (*70, *67, *69, *9, and speed dial features do not function here). Carrier selection indicators are not permitted, thus only the default carrier is utilized for these destinations.

[0274] If the telephone number is valid, the caller will hear a “confirmation tone” which consists of three short tones. For *42 and *68, this will be followed by a subsequent dial tone requesting the caller to enter the number of rings (0-9) before forwarding. If the caller hangs up, the system wide default of RINGS BEFORE FORWARD is used, and the call forwarding is enabled. If a single digit (0,1,2,3,4,6,7,8,9) is entered, then the caller will hear a second confirmation tone. The call is then released.

[0275] NOTE: This behavior is slightly different from standard. First, the destination is not verified to ensure the destination is reachable. Second, the destination need not answer. Third, rings to forward may be set in the same step.

[0276] Static Data Requirements:

[0277] Each station will have permanently stored a forwarding directory number (DN). This forward destination will populate the Default Call Forward Field, which overrides the Call Forward Busy and Call Forward Ring No Answer that may be supplied by a system administrator. The UNCONDITIONAL forward supersedes all other forward numbers.

[0278] Terminate inbound calls for a subscriber on an endpoint based on a physical address stored for each subscriber. The mechanism will receive an inbound call from the network side (SS7) where the DNIS will be validated in the station database, and the associated subscriber will be validated for billing status. The call will be extended to the station with the ANI as part of the “outseizure” request.

[0279] Callers Experience:

[0280] Subsequent calls to an occupied station address (detected in ESP 20) will receive a BUSY tone if no supplementary services are enabled for the subscriber. For situations where a station is out-of-service or a subscriber has an invalid status, the caller will receive a SIT and an announcement of the condition. For stations with call waiting enabled, the caller will receive a RINGBACK at the station and the ESP 20 will generate a call-waiting tone. An optional FSK burst may be provided for callers with enhanced call waiting. If a flash signal is detected, and there is no caller waiting, and the TRANSFER feature is enabled, provide a dial-tone, collect an address, and then effect a transfer of the inbound call to the newly entered destination.

[0281] Alternatively, for a station with call waiting enabled, provide FORWARDING to call forwarding universal (CFU) or call forwarding destination (CFD) as follows:

[0282] 1. When the CFU number is registered for all calls to this station or

[0283] 2. When the CFD number is registered for all calls to this station.

[0284] When the CFU and CFD are undefined, provide FORWARDING when Busy is detected to the call forward busy (CFB) number registered. Similarly, provide FORWARDING when NO ANSWER is detected on the DEFINED NUMBER OF RINGS to the call forward no answer (CFNA) number registered.

[0285] 3. 3 DIGIT FEATURE REQUESTS OF A PATTERN *AX.

[0286] These feature selectors may be recognized and based on the feature, perform certain actions. The feature selectors may be modifiable and changeable to suit the local requirements.

[0287] *69 Extend a call to the last answered or unanswered inbound call.

[0288] *70 <address> Disable call-waiting for this address.

[0289] *57 Malicious call trace request (last inbound answered or unanswered call).

[0290] *73 Cancel call forwarding.

[0291] *72 <address> All calls forward (immediate).

[0292] *42 <address> Call forward on ring no answer override.

[0293] *68 <address> Call forward busy/ring no answer.

[0294] *74 <1 digit code><destination> Activate speed dial 2-9.

[0295] *75 <2 digit code><destination> Activate speed dial 20-49.

[0296] <1 digit code># Dial speed dial number.

[0297] <2 digit code># Dial speed dial number.

[0298] 4. OPTIONAL 7 DIGIT EQUAL ACCESS CARRIER SELECTION OF A PATTERN 10XXXXX

[0299] [101cccc]0[#, time-out] Operator assistance.

[0300] [101cccc]0<address> Collect or operator assisted call with valid local, national, or international address.

[0301] 5. A VALID PSTN ADDRESS: (Denoted above as <address>).

[0302] 011<international phone number>[#, TO] International call with optional carrier selection.

[0303] 1<10 digit national number> Long-distance call with optional carrier selection. 7 digit local address 1-5 digit extension[#, TO]

[0304] It is an objective of this invention to embody a class 5 switch by intercepting edge switch events, issuing switching primitives, and establishing and tearing down calls on a routing network. The logic 35 which embodies the class 5 switch will be dynamically loaded, and will include extensions to operate with voice response circuits 9, SCPs 32, and traditional database architectures. These extensions will provide many new features, and greatly enhanced user interfaces for existing features.

[0305] Complex feature creation and distribution will be possible by distributing this logic to switching end-points for use on demand. Thus complex IN like features will be created and distributed to end-office locations in a uniform manner. The solution scales because the high number of“trigger” interaction points are managed by the distributed logic 35, instead of round trip communications to an SCP 32, as defined in the IN architecture.

[0306] Configuration changes are “journalized” onto a persistent data storage device, such as a hard disk, on the SMP 28. This provides a permanent record of the configuration change should the SMP 28 lose power or get restarted. The change may have been submitted by any network element. The change may be a modification to a “PERL” source file, or the inclusion of a new “PERL” source file.

[0307] For example, if the SMP 28 receives a transaction which modifies a PERL script called “DLS.pl” to permit dialing “*SP” to reach the state police in addition to 911, the SMP 28 would write a journal entry to the hard disk. The configuration journal number would be incremented and assigned to this journal entry.

[0308] The method of transporting the PERL logic 35 source files to each ESP 20 is based on a polling algorithm. Each ESP 20 will periodically “ping” the SMP 28 with a data packet containing monitoring and operational statistics. The response to the “ping” provides information about which configuration changes need to be processed.

[0309] The network operates as follows. Messages on the network are based on a reliable datagram method such as common management interface protocol (CMIP) over TCAP or user datagram protocol (UDP). On startup, SMP 28 reads its configuration from its local database. Initially, there is no configuration at all. The ESP 20 periodically contacts the SMP 28 by sending a “ping” message in response to a reliable datagram. The “ping” contains the configuration journal number, as well as, operational statistics for monitoring purposes as illustrated in Table 8 below.

[0310] The SMP 28 responds to the ESP 20 with a message containing the information shown in Table 9 below.

[0311] The ESP 20 receives the response from SMP 28, and checks the configuration journal number. If the SMP 25 has a journal number that is greater than the ESP 20, then the ESP 20 must request sequentially all of the entries that have not been processed. Thus, if the ESP's 20 configuration journal entry number is 7, and the SMP 28 has a configuration journal number of 10, the ESP 20 must ask for and process configuration changes 8, 9, and 10. The above process repeats itself continually with a programmable interval between “ping” messages. The latency on updates of configuration data is based solely on the frequency of the “ping” message.

[0312] The configuration change mechanism may function as follows. When an ESP 20 or a SCP 32 discovers that its configuration database is on or more transactions behind the SMP 28, it sends requests to the SMP 28 for those particular journal entries. The SMP 28 replies with the entries and they are applied to the local database and served to other hosts on the network. Thus, all hosts (computing entities) will have a copy of the configuration database, which is exactly the same. When a “PERL” script changes, the source text file of the PERL program will be copied by the ESP 20 using either FTP or TFTP or a packet approach which might be stored in a local directory. Next, the ESP 20 will activate the change by:

[0313] 1. Checking to see if the PERL script is in use on the system.

[0314] 2. If the PERL script is not in use the change is executed.

[0315] 3. If the PERL script is in use, the ESP 20 will send a notification of DLS_CHANGE to all processes that require such notification. Those processes will then dynamically load the PERL script as required.

[0316] Having introduced the DLS 14 at a high level in FIG. 2, and further describing the DLS in FIG. 3, reference is now directed to FIG. 4 which illustrates how the logic of the DLS 14 of FIG. 2 is applied at the EO digital matrix switch 2 previously illustrated in FIG. 1. In this regard, a message sequence chart 40 may include a phone 62, a RDT 64, an RDT 66, an EO loop side of matrix switch 68, an equal access side of matrix switch 70, and a tandem transit 72. It is important to note that logic 35 of the DLS 14 previously introduced is applied at an edge device (not shown) between the physical connections to the telephonic interfaces and routing network interfaces. FIG. 4 illustrates the sequential functional interfaces necessary to establish a first two-party call, as well as, a second two-party call in response to an inbound call directed to a phone with a call-waiting feature enabled. Each of the functional interfaces in the sequence are illustrated as one scans FIG. 4 from left to right starting at the upper left hand portion of the illustration and proceeding to the bottom of the figure. More specifically, a user may initiate a first two-party call by signaling a call initiation request by lifting a receiver and sending an off-hook signal from the phone 62 to the RDT 64. The RDT 64 having received the off-hook signal sends a Q.931 setup signal to the IDT 66. The IDT 66 having received the Q.931 setup signal sends a timeslot request to the EO loop side of matrix switch 68. Having received the timeslot request signal, the logic 35 returns a timeslot assigned signal to the IDT 66 via the EO loop side of matrix switch 68. Having received the timeslot assigned signal from the logic 35 and the EO loop side of matrix switch 68, the IDT sends a Q.931 connect signal to the RDT 64. Having received the Q.931 connect signal from the IDT 66, the RDT 64 establishes a connection from the EO loop side of matrix switch 68 through to the phone 62. Once a phone connection is established, the logic 35 attaches a DTMF tone collector and applies a dial tone on the connection to the phone.

[0317] Having received a dial tone, the first digit depressed by a user of phone 62 results in a first digit report signal from the phone 62 to the EO loop side of matrix switch 68. The first digit report signal is detected by the logic 35. Upon receiving the first digit from the phone 62, the logic 35 removes the dial tone from the connection. After receiving the 2^ndto Nth digit report from the phone 62, at the EO loop side of matrix switch 68, the logic 35 processes and sends an outbound call request via the equal access side of matrix switch 70. The tandem transit network 72, having received the outbound call request locates and connects the desired remote station and awaits an indication that the complete address has been received at the remote switch serving the remote station.

[0318] Having received an indication that the address is complete, tandem transit network 72 sends an address complete signal to the logic 35 via the equal access side of matrix switch 70. The logic 35 then arranges for a ringback tone via the EO loop side of matrix switch 68 to the RDT 64. The ringback tone continues either until the destination party answers the call, or the phone 62 terminates the call attempt by placing the phone back on-hook. Once an answer signal is received from the tandem transit network 72 at the logic 35 via the equal side of matrix switch 70 the logic 35 establishes a talk path connection for the first two-party call.

[0319] A second two-party call in response to an inbound call directed to the phone 62 with a call-waiting feature enabled may be established as follows. First an inbound call signal is sent from the tandem transit network 72 to the logic 35 via the equal access side of matrix switch 70. The logic 35 having received the inbound call signal issues an ACM signal back to the tandem transit network 72. Simultaneously, the logic 35 issues a call-waiting tone via the EO loop side of matrix switch 68 via the established connection to the RDT 64. The call-waiting tone continues indefinitely until either the phone 62 issues a flash signal, or the inbound calling station returns the remote phone on-hook. Upon receiving a flash signal from phone 62, the logic 35 removes the inbound ringing signal from the remote caller by issuing a remove inbound ringing signal via the equal access side of matrix switch 70 to the transit tandem network 72. Next, the logic 35 issues an outbound hold signal between the same two devices. The logic 35 then establishes a talk path between phone 62 and the second calling party.

[0320] A. OUTBOUND CALLS

[0321] Calls originating from a station may have the following event processing logic performed by the logic 35. The flowcharts of FIGS. 5-27 show the architecture, functionality, and operation of a possible implementation of the logic 35. In this regard, each block represents a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks might occur out of the order noted in FIGS. 5-27. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. In this regard, FIGS. 5-27 illustrate the processing logic as applied by the system to process outbound calls.

[0322] FIG. 5 is a flowchart illustrating the start of an outbound call, a first branch after a station validity check, and a branch on event. In this regard, inbound call processing begins at start step 80. After the start step 80, the logic 35 detects a call processing event for a station 82 defined on the digital matrix switch 2. Upon detecting the call-processing event, the logic 35 performs a station validity check in step 84. If the validity check fails, processing transfers to failure 86, which will be illustrated and described in association with FIG. 6. If the validity check returns an affirmative response, processing continues with branch on event step 88. In general, inbound call-processing branches to a specific portion of the flowchart upon detection of a particular event. More specifically, upon detection of an ESP_call_arrival event, processing transfers to the station off-hook 90 portion of the flowchart as shown in FIG. 7; upon detection of an ESP_digits_received event, processing transfers to the single digit report or timeout 92 portion of the flowchart as shown in FIG. 8; upon detection of the second ESP_digits_received event, processing transfers to the multiple digit report or timeout 94 portion of the flowchart as shown in FIG. 9; upon detection of an ESP_answer event, processing transfers to the answer 96 portion of the flowchart as shown in FIG. 10; upon detection of an ESP_flash_detected event, processing transfers to the attention 98 portion of the flowchart as shown in FIG. 11; upon detection of an ESP_released event, processing transfers to the station on-hook 100 portion of the flowchart as shown in FIG. 12; upon detection of an ESP_port_parked event, processing transfers to the guarded release 102 portion of the flowchart as shown in FIG. 13; upon detection of an ESP_port_OOS event, processing transfers to the OOS/IS 104 portion of the flowchart as illustrated in FIG. 14.

[0323] Having described that portion of outbound call processing illustrated in FIG. 5, reference is now directed to FIG. 6. In this regard, FIG. 6 is a flowchart illustrating outbound call processing upon a failure event. In this regard, failure event processing starts with step 86 (see FIGS. 5, 8, 9, 15, 17, 18, 20, 23, 24, 27, and 28).

[0324] First, the logic 35 instructs the ESP_switch_connect_tone to play the special intercept tone in step 200. Next, the logic 35 branches on cause as described below. If the failure was an address failure, the logic 35 transfers processing to step 204 where the caller encounters a taped message as follows, “You have dialed an invalid number, please try again.” If the failure is a local failure, the logic 35 transfers processing to step 206 where the caller encounters a taped message as follows, “Local dialing not permitted.” If the failure is a long distance failure, the logic transfers control to step 208 where the caller encounters a taped message as follows, “Long distance dialing not permitted.” If the failure is an international failure, the logic 35 transfers processing control to step 210 where the caller encounters a taped message as follows, “International calls are not permitted.” Next, the logic 35 performs step 212 where a signal is sent to clear the tandem transit network.

[0325] The logic 35 then performs step 214 to clear the collected digits, step 216 to clear the data being collected, step 218 to clear the carrier, step 220 to play a dial tone for the calling station, and step 222 to collect digits related to a new attempted call. Having performed steps 200 through 222, the logic 35 performs step 159 wait for next event.

[0326] Having described outbound call processing upon encountering a failure event as illustrated in FIG. 6, reference is now directed to FIG. 7. In this regard, FIG. 7 is a flowchart illustrating outbound call processing for a station off-hook event. Station off-hook event processing starts with step 90 (see FIG. 5). Next, the logic 35 sets the ESP_switch_collect_tone in step 193, sets the ESP_switch_listen in step 195, and sets the station to “in use” in step 197. Last, the logic 35 performs step 159 wait for next event.

[0327] Having described outbound call processing upon encountering a station off hook event as illustrated in FIG. 7, reference is now directed to FIG. 8. In this regard, FIG. 8 illustrates outbound call processing upon encountering a single digit report or a timeout. Having encountered a single digit report or timeout in step 92, the logic 35 adds to the collected digits buffer in step 101. Next, a query is performed to determine if the caller is operating in the dial by name mode in step 103. If yes, the logic 35 determines if the last digit was a timeout in step 105. If yes, the logic performs the name resolve portion of the flowchart as illustrated starting with step 107 (see FIG. 15). If the last digit was not a timeout, the logic 35 performs a wait for next event in step 159.

[0328] If the caller is not operating in dial by name mode as queried in step 103, the logic 35 performs the following string comparisons. If the caller enters “0” followed by a timeout as detected in step 111, the logic 35 transfers call processing flow to step 113 (see FIG. 16) operator. If the caller enters “01([2-9]” as detected in step 115, the logic 35 removes the leading “0” for the operator assisted call in step 117 and transfers flow to step 131 (see FIG. 17) get long distance number. If the caller enters a “011[.]{7,17} {T#}” as detected in step 121, the logic 35 transfers processing to step 123 (see FIG. 18) international number. If the caller enters “10” as detected in step 125, the logic 35 transfers processing to step 127 (see FIG. 19) get carrier. If the caller enters “1[2-9]” as detected in step 129, the logic 35 transfers processing to step 131 (see FIG. 17) get long distance number. If the caller enters “[2-9][2-9]” as detected in step 133 or alternatively, “[2-9]1[2-9]” as detected in step 135, the logic 35 transfers processing to step 137 (see FIG. 20) get local number. If the caller enters “[2-9]11” as detected in step 139, the logic 35 transfers processing to step 141 (see FIG. 21) N11 feature. If the caller enters “*[0-8][0-9]” as detected in step 143 or alternatively, “*9” as detected in step 145, the logic transfers processing to step 147 (see FIG. 22) supplementary features If the caller enters “[2-9]#” as detected in step 149 or alternatively “[2-4][0-9]# as detected in step 151, the logic 35 transfers processing to step 153 (see FIG. 23) speed dial. If the caller has entered a string that does not have a possible match with the aforementioned string detection steps as described in relation to steps 111, 115, 121, 125, 129, 133, 135, 139, 143, 145, 149, or 151, processing continues with a query for a possible match in step 155. If no match is possible, the logic 35 transfers processing to step 157 (see FIG. 6) failure. Otherwise, if a partial string match exists, the logic 35 performs step 159 wait for next event.

[0329] Having described that portion of outbound call processing illustrated in FIG. 8, reference is now directed to FIG. 9. In this regard, FIG. 9 is a flowchart illustrating outbound call processing upon a multiple digit report or timeout. Having encountered a multiple digit report or timeout in step 94, the logic 35 first performs a timeout query in step 160. If a timeout is detected, the logic 35 transfers processing to step 86 (see FIG. 6) failure. Otherwise, the logic 35 adds digits to the collected digit buffer for the station in step 162. Next, the logic 35 branches on data being collected in step 164. If carrier data is collected in step 164, the logic 35 stores the carrier information in a state table in step 166. The logic 35, then performs step 168 where it clears the collected digits buffer and data collected. The logic 35 then performs step 159 wait for next event. If the logic detects destination data in step 164, the logic 35 performs step 170 where it validates the destination. Having validated the destination, the logic 35 checks to confirm that the station_dial_capabilities will permit the call in step 172. If no, the logic 35 transfers processing to step 86 (see FIG. 6) failure. If yes, the logic 35 routes the call by transferring control to step 174 (see FIG. 24).

[0330] Having described that portion of outbound call processing illustrated in FIG. 9, reference is now directed to FIG. 10. In this regard, FIG. 10 is a flowchart illustrating outbound call processing for an answer event. In this regard, answer event-processing starts with step 96 (see FIG. 5). The logic 35 sets the station mode to “in use” in step 199. Next, the logic 35 performs step 159 wait for next event.

[0331] Having described that portion of outbound call processing illustrated in FIG. 10, reference is now directed to FIG. 11. In this regard, FIG. 11 is a flowchart illustrating outbound call processing upon an attention event. Attention event processing starts at step 98 (see FIG. 5). Next, the logic 35 determines if the established outbound call is present in step 356. If the outbound call is present, the logic 35 determines if the conference feature is active for the station in step 358. If either of the queries in steps 356 or 358 is negative, the logic 35 responds by determining if the established call is present in step 360. If the established call is not present, the logic 35 performs step 159 wait for next event.

[0332] If the established call is present in step 360, the logic 35 determines if the waiting caller is present in step 362. If the waiting caller is present, the logic performs step 364 to park current calls. Next, the logic 35 performs step 366 to connect the waiting caller. Last, the logic performs step 159 wait for next event.

[0333] If the response to the query of step 358 is yes, the logic 35 responds by performing step 368 to create the conference call. Next, the logic 35 performs step 370 to connect the outbound leg to the conference. Then the logic 35 sets the conference-waiting bit for the station in step 372. Last, the logic 35 transfers processing to step 287 (see FIG. 25) disable call-waiting.

[0334] Having described that portion of outbound call processing illustrated in FIG. 11, reference is now directed to FIG. 12. In this regard, FIG. 12 is a flowchart illustrating outbound call processing upon encountering a station on-hook event. Station on-hook event processing starts with step 100 (see FIGS. 5, 14, and 29). Next, the logic 35 performs step 179 to reset all digit collection buffers and types. Having reset the digit collection buffers, step 181 is performed to set the call by call presentation indicator. Next, the logic clears the carrier in step 183 and clears all station timers in step 185. Last, the logic 35 performs step 159 wait for next event.

[0335] Having described that portion of outbound call processing illustrated in FIG. 12, reference is now directed to FIG. 13. In this regard, FIG. 13 is a flowchart illustrating outbound call processing upon a guarded release event. In this regard, guarded release event processing starts at step 102 (see FIGS. 5 and 28). Next, the logic 35 performs step 324 to play recorder. Then the logic 35 performs step 326 to initialize a timer, step 328 to play howler when the timer expires, step 330 to set a secondary timer to set the station out of service, and step 332 to mark the station out of service. Last, the logic 35 performs step 159 wait for next event.

[0336] Having described that portion of outbound call processing illustrated in FIG. 13, reference is now directed to FIG. 14. In this regard, FIG. 14 is a flowchart illustrating outbound call processing upon an out-of-service/in-service (OOS/IS) event. In this regard, OOS/IS event processing starts at step 104 (see FIG. 5). Next, the logic 35 performs a check to verify that no number is present in step 339. If no number is present, the logic 35 performs step 341 to release the other side of the switch. Next, or if a number was present upon performing the check in step 339, the logic 35 transfers processing to step 92 (see FIG. 12) station on-hook.

[0337] Having described that portion of outbound call processing illustrated in FIG. 14, reference is now directed to FIG. 15. In this regard, FIG. 15 is a flowchart illustrating outbound call processing upon a name resolve event. Name event processing starts at step 107 (see FIG. 8). Next, the logic 35 performs step 347 to resolve the name. Next, the logic performs step 349 to branch on matches possible. If no matches are possible, the logic transfers processing to step 86 (see FIG. 6) failure. If matches are possible, the logic 35 performs a load results query in step 351. If the response to the query is yes, then the logic 35 transfers processing to step 174 (see FIG. 24) route call. If no, the logic 35 determines if the ESP 20 is available in step 353. If the ESP 20 is not available, the logic 35 transfers processing to step 86 (see FIG. 6) failure. If the ESP 20 is available, the logic 35 performs step 355 to select the destination number from the list of available numbers by name for the station. The logic 35 then returns to step 349 where steps 86, 351, and 353 are repeated as appropriate until a failure is processed or a call is completed.

[0338] Having described that portion of outbound call processing illustrated in FIG. 15, reference is now directed to FIG. 16. In this regard, FIG. 16 is a flowchart illustrating outbound call processing upon an operator event. In this regard, operator event processing starts at step 113 (see FIG. 8). Next, the logic 35 performs step 318 where it sets the destination to the operator for the particular station. The logic 35 then performs step 320 where it sets the presentation indicator on. Next, the logic 35 disables call waiting in step 322. Last, the logic 35 performs step 174 (see FIG. 24) route call.

[0339] Having described that portion of outbound call processing illustrated in FIG. 16, reference is now directed to FIG. 17. In this regard, FIG. 17 is a flowchart illustrating outbound call processing for a get long distance number event. In this regard, get long distance number outbound call processing starts with step 131 (see FIG. 8). In this regard, the logic 35 determines whether long distance access is permitted for this station in step 187. If long distance access is not permitted, the logic 35 transfers processing to step 86 (see FIG. 6) failure. If long distance access is permitted, the logic 35 performs step 189 ESP_switch_ignore to ignore signals from the digital matrix switch 2 (see FIG. 1). Get long distance number processing continues with step 191 ESP_switch_collect_digits where the edge switch device is set to collect the individual digits of the long distance number. Last, the logic 35 performs step 159 wait for next event.

[0340] Having described that portion of outbound call processing illustrated in FIG. 17, reference is now directed to FIG. 18. In this regard, FIG. 18 is a flowchart illustrating outbound call processing for an international number. In this regard, international number outbound call processing starts with step 123 (see FIG. 8). Next, step 175 is performed to validate the number. Next, the logic 35 performs a query in step 177 to determine if international calls are permitted from the calling station. If international calls are not permitted, the logic 35 transfers processing to step 86 (see FIG. 6) failure. If international calls are permitted, the logic 35 transfers call processing to step 174 (see FIG. 24) route call.

[0341] Having described that portion of outbound call processing illustrated in FIG. 18, reference is now directed to FIG. 19. In this regard, FIG. 19 is a flowchart illustrating outbound call processing upon a get carrier event. In this regard, get carrier event processing starts at step 127 (see FIG. 8). Next, the logic 35 performs step 231 to disable single digit detection. The logic 35 continues by performing step 233 to record the seven digits already collected. Last, the logic 35 performs step 159 wait for next event.

[0342] Having described that portion of outbound call processing illustrated in FIG. 19, reference is now directed to FIG. 20. In this regard, FIG. 20 is a flowchart illustrating outbound call processing upon a get local number event. Get local number event processing starts with step 137 (see FIG. 8). In this regard, the logic 35 proceeds by performing a query whether to permit local dialing in step 235. If local dialing is not permitted, the logic 35 transfers processing to step 86 (see FIG. 6) failure. If local dialing is permitted, the logic 35 performs step 237 to disable single digit detection. Next, the logic 35 performs step 239 to collect seven digits from the buffer. Last, the logic 35 performs step 159 wait for next event.

[0343] Having described that portion of outbound call processing illustrated in FIG. 20, reference is now directed to FIG. 21. In this regard, FIG. 21 is a flowchart illustrating outbound call processing upon a N11 dial string. N11 event processing starts at step 141 (see FIG. 8). Upon determining that the caller has selected a “N11” feature, the logic 35 performs step 250 branch on the first digit. If the first digit is a “3,” as detected in step 252, the logic transfers processing to step 260 where the caller is connected to the non-urgent police/fire number for that caller's switch. If the first digit is a “4,” as detected in step 254, the logic 35 transfers processing to step 262 where the caller is connected to the information number for that caller's switch. If the first digit is a “6,” as detected in step 256, the logic 35 transfers processing to step 264 where the caller is connected to the service provider's service line. If the first digit is a “9,” as detected in step 258, the logic 35 transfers processing to step 266 where the caller is connected to the local police/fire emergency number for that caller's switch. Next, the logic 35 performs step 268 to enable the emergency police/fire operator to auto return should the caller hang-up. Having completed calls via steps 260, 262, 264 or step 268 after an emergency call; the logic 35 sets the presentation indicator on in step 270. Next, the logic 35 performs step 272 where it disables call waiting. Last, processing is transferred to step 174 (see FIG. 24) route call.

[0344] Having described that portion of outbound call processing illustrated in FIG. 21, reference is now directed to FIG. 22. In this regard, FIG. 22 is a flowchart illustrating outbound call processing upon a supplementary features event. Having detected a generic feature event request in step 147, the logic 35 proceeds by branching on service indicator in step 275. Upon detecting that the caller has dialed “*9” in step 277, the logic 35 performs step 279 where it loads the last number dialed. The logic 35 then transfers control to step 174 (see FIG. 24) Route call. Upon detecting that the caller has dialed “*69” in step 281, the logic performs step 283 where it loads the last inbound number as the destination number. The logic 35 then transfers processing to step 174 (see FIG. 24) route call. Upon detecting that the caller has dialed “*70” in step 285, the logic 35 transfers processing to step 287 (see FIG. 25) disable call-waiting. Upon detecting that the caller has dialed “*57” in step 289, the logic 35 transfers processing to step 291 (see FIG. 26) malicious trace. Upon detecting that the caller has dialed “*73” in step 293, the logic 35 cancels call forwarding in step 295. Upon detecting that the caller has dialed either “*72,” “*42,” or “*68,” (steps 297, 299, 301) the logic 35 forwards that call in step 303. Upon detecting that the caller has dialed either “*74” or “*75” in steps 305 and 307, the logic 35 adds speed calling in step 309. Upon detecting that the caller has dialed a “*2” in step 311, the logic 35 transfers control to step 241 (see FIG. 27) dial by name.

[0345] Having described that portion of outbound call processing illustrated in FIG. 22, reference is now directed to FIG. 23. In this regard, FIG. 23 is a flowchart illustrating outbound call processing upon a speed dial event. In this regard, speed dial event processing starts at step 153 (see FIG. 8). Having determined that the caller wishes to process a call with speed dialing, the logic 35 performs step 312 to determine which number to dial. Next, in step 314, the logic 35 performs a check to verify that the speed dial buffer location has a number stored in the buffer. If no number is found in the buffer, the logic 35 transfers processing to step 86 (see FIG. 6) failure. If a number is found in the speed dial buffer location, the logic 35 performs step 316 where it loads the destination number. Last, the logic 35 routes the call by transferring processing to step 174 (sec FIG. 24) route call.

[0346] Having described that portion of outbound call processing illustrated in FIG. 23, reference is now directed to FIG. 24. In this regard, FIG. 24 is a flowchart illustrating outbound call processing upon a route call event. Route call outbound call-processing starts with step 174 (sec FIGS. 9, 15, 16, 18, 21, 22, and 23). The logic 35 routes the outbound call by performing step 225 TNE_process_call where the dialed number is transferred to the tandem transit switch 10 (see FIG. 1). Next in step 227, the logic 35 performs a check to ensure that the call is successfully connected. If the call is not properly connected, the logic transfers processing to step 86 (see FIG. 6) failure. If the call is properly connected, the logic 35 performs step 229 to save the dialed number in the last outbound attempt buffer for the station. The logic 35 then performs step 159 wait for next event.

[0347] Having described that portion of outbound call processing illustrated in FIG. 24, reference is now directed to FIG. 25. In this regard, FIG. 25 is a flowchart illustrating outbound call processing upon a disable call-waiting event. In this regard, disable call-waiting event processing starts at step 287 (see FIGS. 11 and 22). Next, the logic 35 performs step 334 to set the call by call presentation indicator, step 336 to play a dial tone, and step 338 to collect single digits. Last, the logic 35 performs step 159 wait for next event.

[0348] Having described that portion of outbound call processing illustrated in FIG. 25, reference is now directed to FIG. 26. In this regard, FIG. 26 is a flowchart illustrating outbound call processing upon a malicious trace event. In this regard, malicious trace event processing starts at step 291 (see FIG. 22). Next, the logic 35 performs step 343 to play a recording as follows, “The previous call is being reported as malicious.” Then, the logic 35 performs step 345 to mark the last inbound call as “malicious.” Last, the logic 35 transfers processing to step 102 (see FIG. 13) guarded release.

[0349] Having described that portion of outbound call processing illustrated in FIG. 26, reference is now directed to FIG. 27. In this regard, FIG. 27 is a flowchart illustrating outbound call processing upon a dial by name event. In this regard, dial by name event processing starts at step 241 (see FIG. 22). First, the logic 35 determines if the dial by name mode is available to the station in step 243. If the dial by name mode is not available, the logic 35 transfers processing to step 86 (see FIG. 6) failure. If the station is permitted to dial by name, the logic 35 performs step 245 to enable single digit detection. Next, the logic 35 performs step 247 set to address by name for the station. Last, the logic 35 performs step 159 wait for next event.

[0350] B. INBOUND CALLS

[0351] Calls originating from a remote transit network may have the following independent event processing logic performed by the logic 35. The flow charts of FIGS. 28-31 show the architecture, functionality, and operation of a possible implementation of a portion of the logic 35. In this regard, each block represents a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks might occur out of the order noted. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. In this regard, FIGS. 28-31 illustrate the processing logic as applied to inbound calls.

[0352] FIG. 28 is a flowchart illustrating the start of an inbound call, a first branch after a station validity check, and a branch on event. In this regard, inbound call processing begins at start step 480. After the start step 480, the logic 35 detects a call processing event for a station 482 defined on the digital matrix switch 2. Upon detecting the call-processing event, the logic 35 performs a station validity check in step 484. If the validity check fails, processing transfers to step 86 failure as previously illustrated and described in association with FIG. 6. If the validity check returns an affirmative response, processing continues with branch on event step 488. In general, inbound call-processing branches to a specific portion of the flowchart upon detection of a particular event. More specifically, upon detection of an _ESP_port_OOS event, processing transfers to the OOS/IS 492 portion of the flowchart as shown in FIG. 29; upon detection of an ESP_port_released event, processing transfers to the OOS/IS 492 portion of the flowchart as shown in FIG. 29; upon detection of an TNE_station wanted (idle) event, processing transfers to the seize 498 portion of the flowchart as shown in FIG. 30; upon detection of a TNE_station_wanted (busy) event, processing transfers to the seize 498 portion of the flowchart as shown in FIG. 30; upon detection of a TOQ_timeout event, processing transfers to the seize 498 portion of the flowchart as shown in FIG. 30; upon detection of an ESP_port_parked event, processing transfers to the guarded release 102 portion of the flowchart as shown in FIG. 13.

[0353] Having described that portion of inbound call processing illustrated in FIG. 28, reference is now directed to FIG. 29. In this regard, FIG. 29 is a flowchart illustrating inbound call processing upon an OOS/IS event. Having transferred processing from step 492 (see FIG. 28), the logic 35 performs a check to see if the call is presently being serviced in 539. If yes, the logic releases the port in step 541 before performing the station on-hook portion of the flowchart starting with step 92 (see FIG. 12). If the response to the query in step 539 is negative, the logic 35 simply transitions to step 92 (see FIG. 12) station on-hook.

[0354] Having described that portion of inbound call processing illustrated in FIG. 29, reference is now directed to FIG. 30. In this regard, FIG. 30 is a flowchart illustrating inbound call processing upon a seize event. Seize event processing starts at step 498 as previously described with FIG. 28. Having entered this portion of the flowchart, the logic 35 performs a station_forward_unconditional_read validity check in step 499. If step 499 is successful, the logic 35 executes a TNE_requeue_outdial in step 501 to forward the call. After forwarding the call, the logic 35 executes a wait for next event in step 159. If step 499 is unsuccessful, the logic 35 performs a station idle check in step 503. If step 503 is successful, the logic 35 executes a TNE_queue_outdial in step 505 to complete the call. Having executed step 505, the logic 35, then executes a TOQ_insert in step 507 to set an answer timer. After setting the answer timer, the logic 35 executes a wait for next event in step 159. If step 503 is unsuccessful, the logic 35 checks the station features in step 509 to determine if the station is conFIG.d for call waiting. If step 509 is successful, the logic 35 executes an ESP_switch_connect_tone in step 511 to notify the user that a call is waiting. Next, the logic 35 executes a TOQ_insert in step 513 to set an answer timer. After setting the answer timer, the logic 35 executes a wait for next event in step 159. If step 509 is unsuccessful, the logic 35 performs a station_forward_busy_read check in step 515. If step 515 is successful, the logic 35 executes a TNE_requeue_outdial in step 517 to forward the call. The logic 35 then executes a wait for next event in step 159. If step 515 is unsuccessful, the logic 35 executes a TNE_caller_busy in step 519 to provide busy treatment to the inbound caller. After executing step 519, the logic 35 then executes a wait for next event in step 159.

[0355] Having described that portion of inbound call processing illustrated in FIG. 30, reference is now directed to FIG. 31. In this regard, FIG. 31 is a flowchart illustrating inbound call processing upon a ring no answer (RNA) event. Upon detecting a RNA event, the logic 35 performs a station being seized and unanswered check in step 520. Upon encountering a station seizure with no answer, the logic 35 performs a TNE_release_port event in step 522. Next, all other responses from the station seizure and no answer query of step 520 and after step 522, the logic 35 proceeds with a station_forward_no_answer_read in step 524. If the station_forward_no_answer_read is unsuccessful, the logic 35 responds with a wait for next event in step 159. Otherwise, the logic 35 performs a TNE_requeue_outdial to forward the call in step 526. After forwarding the call in step 526, the logic performs a wait for next event in step 159.

[0356] Having described that portion of inbound call processing illustrated in FIG. 30, reference is now directed to FIG. 31. In this regard, FIG. 31 is a flowchart illustrating inbound call processing upon This completes the description of in-bound call processing illustrated in FIGS. 28 through 31.

[0357] It should be emphasized that the above-described embodiments of the present invention, particularly, any “preferred” embodiments, are merely possible examples of implementations, merely set forth for the benefit of the reader for clearly disclosing to the reader the basic principles of the invention. Many variations and modifications may be made to the above-described embodiment(s) of the invention without departing substantially from the spirit and principles of the invention, and such variations and modifications have not been described herein for brevity sake and simplicity. All such variations and modifications are intended to be included herein within the scope of this disclosure and the present invention and are intended to be protected by the following claims.