Held party notification feature
TECHNICAL FIELD 
     This invention relates to Private Branch Exchanges (PBX&#39;s) and, in particular, to held party notification facilities for a PBX. The invention further relates to facilities for immediately alerting a held party that a hold condition has been removed by an activating party, and that a voice connection has been re-established between the activating party and the held party. 
     BACKGROUND OF THE INVENTION 
     Private Branch Exchanges (PBX&#39;s) have increased in complexity and sophistication over the years and offer users a wide variety of features and capabilities that are activated by a user from multi-function station sets. Multi-function station sets typically have multiple call appearances which allow the user to have multiple active concurrent independent call connections. The user, however, can only talk on one call connection at a time. To maintain multiple active call connections, the user activates a &#34;hold feature&#34; to keep the remaining call connections active but in a &#34;non-talk&#34; state. The user can maintain several calls &#34;on-hold&#34; while conversing with another party or parties (e.g. conference connections). Although the hold feature is convenient to the user or activating party, the held party must aurally monitor the station&#39;s receiver for the return of the voice of the activating party to ascertain the conclusion of the hold interval and the re-establishment of the &#34;talk&#34; state. The held party, as a result of aural monitoring during the hold interval, suffers a number of inconveniences such as waiting an uncomfortably long period of time, wasting valuable time, and enduring restricted activity. 
     Many systems and devices have been proposed in an effort to alleviate these inconveniences to the held party. One such device applies soothing music on the station line during the hold interval so as to entertain the held party. Another system measures the time duration of the hold interval, and then drops the call connection after some period of time elapses. Other arrangements provide a &#34;winking&#34; lamp on the station of an activating party to serve as a reminder to the activating party that an existing call connection is &#34;on-hold&#34;. Despite the above-described attempts to alleviate the inherent annoyances to the held party, the held party must still aurally monitor the station&#39;s receiver for the entire hold interval to detect the activating party&#39;s voice which signals the resumption of the &#34;talk&#34; state connection between the held and activating parties. 
     Schemes have been proposed which eliminate the need for the held party to aurally monitor the receiver of the station set by providing an indication to the held party that signals the return of the activating party&#39;s voice and the conclusion of the hold interval. One such voice detection scheme is disclosed in U.S. Pat. No. 3,961,142 issued to George S. Caffine on Jun. 1, 1976. Caffine discloses an arrangement wherein each station is equipped with a hard-wired voice detection circuit which is activated by the held party during a hold state. The circuit monitors the held party&#39;s station line during the hold state to detect the presence of a voice signal thereon. An annunciation signal is generated by the detection circuit in response to the detection of voice on the station&#39;s line signaling the resumption of the &#34;talk&#34; state between the held party and the activating party. The voice detection circuit eliminates the need for the held party to aurally monitor the station&#39;s receiver. 
     There are several disadvantages associated with the Caffine and similar voice-detection arrangements. These arrangements typically disclose a hard-wired voice detection circuit which is dependent on the tip/ring architecture of an analog key system. This circuit detects electrical changes in the voltage applied to the tip/ring conductors and activates an annunciation signal in response to the detection of a voltage change. These voice detection arrangements are appropriate for analog environments where changes in electrical signals control the interconnections between stations; however such voice detection arrangements are inapplicable to digital environments where interconnections between stations occur in response to call processing algorithms which generate digital messages. Therefore, the application of these voice detection arrangements is limited to analog environments which are based on tip/ring architecture. 
     Another disadvantage of the voice detection arrangements is that the voice detection circuit links the detected changes in the electrical signals on the tip/ring conductors to the appearance of voice on the station line. Arrangements that rely on changes in electrical signals to indicate a particular condition are not reliable since changes in the electrical signals could occur as a result of noise appearing on a line. The noise could trigger the circuit and provide a false indication as to the appearance of voice on the station line. Additionally, the circuit does not discriminate the activating party&#39;s voice from other voices that can appear on the station&#39;s line. The circuit could then generate the annunciation signal in response to the &#34;music on-hold&#34; feature, cross-talk or the appearance of other conferees&#39; voices on the line where a conference connection exists. 
     A further disadvantage associated with these voice detection arrangements is that the voice detection circuit is not triggered until a voice signal is detected and therefore, if the activating party does not immediately speak at the conclusion of the hold interval--a delay in conversation between the activating and held parties occurs. One other disadvantage of these arrangements is that physical modification to an existing station set is required to provide this feature to a user. 
     Therefore, there exists a need to develop a held party notification arrangement which is independent of the tip/ring architecture, operates in the digital environment and provides an immediate and &#34;true&#34; notification to the held party that the hold condition has been removed and the &#34;talk&#34; state connection has been re-established. Additionally, an arrangement is desired that requires no hardware modification and is implemented in an economical manner. 
     SUMMARY OF THE INVENTION 
     To overcome the above-described disadvantages and inconveniences, the disclosed arrangement provides a held party notification feature for the digital PBX which immediately generates an indication (e.g. ring-ping) to the held party when the hold interval is concluded and the &#34;talk&#34; state connection has been re-established between the activating and held parties. 
     In a digital PBX, a control processor establishes and disengages connections between parties based on the application of call processing algorithms stored in the control processor. The algorithms are implemented to process service requests received from stations where each service request is associated with a specified algorithm. 
     To implement the held party notification feature, assume that two parties are connected but are in the non-talk state, i.e. party A places party B on-hold by depressing the hold button on a multi-function station set. Party B, the held party, may now set down the receiver and proceed with other activities during the hold interval. Party B does not need to aurally monitor the station&#39;s receiver during the hold interval. When party A wishes to resume &#34;talking&#34; with party B, party A depresses the call appearance button associated with the held call to remove the hold condition i.e. party A generates an &#34;un-hold&#34; service request. In response to this &#34;un-hold&#34; service request, the control processor implements an associated algorithm. This algorithm detects the current state, i.e. &#34;off-hook&#34; or &#34;on-hook&#34;, and status, i.e. &#34;talk&#34; or &#34;non-talk&#34;, of the station generating the service request. The appropriate current state and status of a requesting station for an &#34;un-hold&#34; service request is &#34;off-hook&#34; and &#34;non-talk&#34;. These conditions indicate the hold condition can be removed by the activating party and that the voice connection between the parties, A and B, can be reestablished. The control processor, in response to the detection of the &#34;un-hold&#34; service request, immediately identifies the held station (party B) and generates an, e.g. aural, indication to party B announcing the conclusion of the hold interval and the re-establishment of the talk-state. Party B can now pick up the receiver and, immediately, begin conversing with party A. 
     The disclosed held party notification feature algorithm monitors the state of the requesting station, i.e. the activating party&#39;s station, to detect the change from the &#34;hold&#34; to the &#34;un-hold&#34; condition. This feature does not rely on voice confirmation or voice-activated annunciators to indicate the conclusion of the hold interval. Additionally, the disclosed feature requires minimal software modification to an existing system, and does not require expensive and cumbersome hard-wired circuit modifications. Further, the disclosed arrangement provides a &#34;true&#34; indication of the conclusion of the hold interval because the control processor monitors the state and status of the activating party&#39;s station rather than relying on the detection of voice on the held party&#39;s station line. An annunciation, therefore, is not generated in response to noise or other phenomenon such as music-on-hold, cross-talk or other conferee&#39;s voices on the line. In the above arrangement, the held party suffers minimal inconveniences during the hold interval since aural monitoring of the station set&#39;s receiver is eliminated. 
    
    
     BRIEF DESCRIPTION OF THE DRAWING 
     The forgoing and other advantages of this invention will be apparent from the following detailed description of one possible exemplary embodiment thereof, which when read in conjunction with the accompanying drawings, in which; 
     FIG. 1 illustrates a typical Private Branch Exchange (PBX); 
     FIG. 2 illustrates a typical multi-function, multi-appearance station set of the digital type; 
     FIG. 3 illustrates a station status table comprising the memory of the control processor; 
     FIG. 4 illustrates a call status table comprising the memory of the control processor; and 
     FIGS. 5, 6, 7 and 8 illustrate a flowchart identifying the call processing steps required to implement the held party reminder feature for stations comprising the Private Branch Exchange (PBX). 
    
    
     DETAILED DESCRIPTION 
     FIG. 1 discloses a typical Private Branch Exchange (PBX) serving a plurality of station sets such as 100-0 through 100-n where each station set is connected by paths 101-0 through 101-n to an associated line port circuit 102-0 through 102-n. The associated port circuits 102-0 through 102-n serve as interfaces to switching network 105 and control processor 107 via scanner 106. 
     Line port circuits 102-0 through 102-n connect over paths 103-0 through 103-n to scanner 106. Scanner 106 connects over path 108 to control processor 107. Control processor 107 is of the stored-program type and controls the interconnections between the station sets 100-0 through 100-n of FIG. 1. Control processor 107 includes a main memory (not shown) which contains various call processing algorithms which are implemented in response to stimulus received from the associated stations. A stimulus may be an &#34;off-hook&#34; or an &#34;on-hook&#34; condition of an associated station. Scanner 106 operates under control of control processor 107. Scanner 106 scans over paths 103-0 through 103-n to detect the appearance of a stimulus indication (eg. &#34;on-hook&#34; or &#34;off-hook&#34;) generated at any one of the stations 100-0 through 100-n. The ports 102-0 through 102-n receive signals over leads 101-0 through 101-n from the associated stations 100-0 through 100-n. These signals as generated in response to a stimulus indicating the condition of the stations 100-0 through 100-5. Scanner 106 detects each change in stimulus (e.g. &#34;on-hook&#34; to &#34;off-hook&#34;) and applies an indication of the stimulus over path 108 to control processor 107. Control processor 107 responds to this indication and implements call processing algorithms in response to the received stimulus. Control processor 107 responds to station dial signals and generates control information to establish interconnections between the stations. Following the establishment of the interconnections, switching network 105 exchanges information, i.e. &#34;voice or data&#34;, between the stations associated with each interconnection. Switching network 105 is controlled by control processor 107 over path 109. 
     Control processor 107, as previously described, contains a number of call processing algorithms in its main memory. Each call processing algorithm comprises a list of stored instructions to administer routine call processing operations which originate and complete interconnections between the stations. Assume that processor 107 is presently responding to an incoming call where the calling party goes &#34;off-hook&#34; and dials digits which identify a called station. Processor 107 implements an appropriate call processing routine to identify the called station in response to the dialed digits and to provide ring-back to the calling station concurrently with ringing at the called station. Processor 107 controls the interconnection between the calling and the called station in response to the instructions of the call processing algorithm. 
     The main memory in processor 107 contains various feature processing algorithms in addition to routine call processing algorithms. These feature processing algorithms comprise lists of instructions that specify processing operations. Each feature processing algorithm is associated with a specific service request. A feature request is generated at stations 100-0 through 100-n in FIG. 1 by depressing a feature button appearing on each of the station sets as shown on FIG. 2. 
     FIG. 2 illustrates a typical multi-function, multi-appearance, 200 through 203, station set of the digital type. The illustrated station set can concurrently serve up to four active calls. A subscriber depresses a call appearance button followed by the &#34;dialing&#34; of digits to originate an outgoing call, and depresses a lit call appearance button to answer an incoming call. Additionally, the illustrated station set provides a subscriber with a number of feature buttons 204 through 207 where each button is associated with a specific feature. Such features may include conferencing, transfer, drop and hold. A subscriber activates a feature by depressing a feature button, e.g. 205 to generate a service request. In response to each service request, the routine call processing algorithm contained in the main memory of control processor 107 branches to an associated feature call processing routine to serve the service request. 
     Control processor 107 maintains in its main memory a number of status tables which are established during call processing. Processor 107 continually updates these tables to reflect the current state, e.g. &#34;on-hook&#34;, &#34;off-hook&#34;, &#34;talk&#34; and &#34;non-talk&#34;, associated with each of the station sets of FIG. 1. FIGS. 3 and 4 illustrate examples of these status tables. FIG. 3 illustrates a station status table which indicates the current state of each station 100-0 through 100-n. For example, the pre-hold station status table illustrates that station 100-0 is currently &#34;off-hook&#34;, i.e. 1, and that station 100-3 is currently &#34;on-hook&#34;, i.e. 1, a &#34;1&#34; is a positive indicator of an associated state. This station status table indicates the hook status of each station. FIG. 4 illustrates a call status table which indicates the current state of each station 100-0 through 100-n on an identified call connection. For example, as the pre-hold call status table illustrates, station 100-0 is in a &#34;talk&#34; state on call connection A, but in a &#34;non-talk&#34; state, i.e. hold on call connection B. Both the station status table and the call status table are continually updated to reflect the current state of each of the stations 100-0 through 100-n with respect to identified call connections. Further details of these tables are discussed subsequently. 
     The remainder of this description describes the feature processing algorithm associated with the held party notification feature. FIGS. 5, 6, 7 and 8 illustrate in flow chart form the steps required to implement the held party notification feature algorithm. Prior to describing the steps included in the implementation of the subject feature, the following describes the steps required by typical call processing to facilitate the operation of the feature. 
     Assume that the PBX of FIG. 1 is operating in a conventional manner such that a typical call processing routine is in progress. Call processing, as previously described, establishes and disengages connections between stations and services requests generated by station users. Processor 107 scans via scanner 106 each station 100-0 through 100-n to detect the generation of a stimulus and/or service request. Processor 107, in response to the receipt of a stimulus and/or service request, constantly updates the status tables to indicate the current state of each of the identified stations 100-0 through 100-n during the call processing operations. Call processing performs processing operations based on the information contained in these status tables. 
     Step 500 of FIG. 5 indicates that typical call processing operations are in progress and assumes that a number of interconnections between various ones of the station sets of FIG. 1 have been established. See the pre-hold station status table of FIG. 3 and pre-hold call status table of FIG. 4. In step 501, if no service request is generated by any of the stations 100-0 through 100-n, processor 107 returns to typical call processing operations prior to step 501. However, if a service request is generated from one of the stations 100-0 through 100-n by a user who depresses, for example, a feature button, such as button 204 illustrated on the station set of FIG. 2, conventional call processing branches to step 502 to a service request routine to serve the request. 
     Assume for the remainder of this description that station 100-0 is the station generating the request. It is understood that more than one station can generate a request and, that the control processor may service more than one request, concurrently. However, for ease of description assume that only one station, 100-0, is generating a service request at this time. Scanner 106 detects the generated service request over path 103-0 from station 100-0 via the associated line port circuit 102-0. Scanner 106 applies an indication of the service request over path 108 to processor 107. This indication includes information as to: (1) the identity of the station requesting the service; (2) the identity of the active call connection associated with the station requesting the service where, as previously described, each active call connection originating at a single station is assigned a specified identity; and (3) the type of service request generated by the station. In response to the receipt of this service request indication, processor 107 identifies the requesting station, station 100-0 at step 502 and then stores the identity of the requesting station in a location specified in its main memory, step 503. Following the identification of the requesting station, processor 107 identifies the call connection, i.e., connection A or B as shown on the pre-hold call status table of FIG. 4, associated with the requesting station, step 504. Processor 107 stores the identity of the call connection in a specified location of the main memory, step 505. Control processor 107, then, at step 506, identifies the type of service request generated by the identified requesting station. 
     Assume that the station set user 100-0 generated a service request other than hold, step 507, or un-hold, step 508. The hold and un-hold requests are described subsequently. In response to the &#34;other&#34; service request generated by the station set user depressing either button 205, 206 or 207 on the station set of FIG. 2, processor 107 bypasses steps 507 and 508 and goes to step 509, &#34;other&#34;. If the generated service request is unavailable to the user, step 509 returns to the typical call processing routine (step 500) to maintain the established call connection and continues scanning the requesting station until another service request is generated. However, if the service is available, step 509 diverts to an associated feature algorithm to process the received &#34;other&#34; service request. 
     Call processing diverts to D of FIG. 8. Following identification of the type of service request generated, processor 107 retrieves from its main memory the identity of the requesting station, step 800. Processor 107 then scans the previously described status tables of FIGS. 3 and 4 to detect the current state of the requesting station, step 801. The requesting station must be in the appropriate state to satisfy the request. If the station is not in the appropriate state, the service request is abandoned (step not shown). However, if the requesting station is in the appropriate state, processor 107 processes the service request according to the steps of the associated feature processing routine, step 802. No further details are provided since the processing of &#34;other&#34; feature requests comprises no part of the subject invention. The above merely indicates that the control processor responds to a variety of service requests. Following the processing of the &#34;other&#34; service request, processor 107 returns to point A of FIG. 5. Call processing continues until the next service request is generated, step 501, that requires specialized feature processing. 
     Assume that typical call processing is in progress and that processor 107 is scanning station 100-0 to detect a service request. Assume further that station 100-0 is currently in the states indicated on the pre-hold status tables of FIGS. 3 and 4: station 100-0 is currently &#34;off-hook&#34;, is included in call connections A and B, and is in a &#34;talk&#34; state on call connection A and a &#34;non-talk&#34; state on call connection B. As previously mentioned, since the user has a multi-appearance station set, a station user is capable of participating in more than one active call connection at one time, but can only converse on one call connection at a time. Assume that station 100-0 on call connection A is the requesting station and that a &#34;hold&#34; service request is generated in response to the user of station 100-0 depressing the hold button (204) on the station of FIG. 2. Assume further that control processor 107 has completed steps 501 through 506, as previously described, and identified the service request as a &#34;hold&#34; in step 507 of FIG. 5. If the hold feature is not available, processor 107 does not service the request and returns to step 500. However, assume that &#34;hold&#34; is available to the user and, therefore, processing proceeds on to point B of FIG. 6. 
     FIG. 6 illustrates the steps required to remove station set 100-0, hereinafter, the requesting station, from the &#34;talk&#34; state of call connection A while still maintaining an active call connection with station set 100-1, that is, station set 100-0 user puts the station set 100-1 user &#34;on-hold&#34;. In response to the &#34;hold&#34; service request, processor 107 retrieves the identity of the requesting station, station set 100-0, at step 600. Processor 107 then scans the pre-hold station status table of FIG. 3 to detect the station status of the requesting station, step 601. The pre-hold station status table indicates that the requesting station is currently &#34;off-hook&#34;, step 602. If the requesting station was not &#34;off-hook&#34;, that is, &#34;on-hook&#34;, the routine diverts to point A (FIG. 5) of the call processing routine to await another service request because the station is not in the appropriate state to satisfy the request. An &#34;on-hook&#34; further indicates that there is no existing active call connection. The hold feature is only operable when the requesting station is &#34;off-hook&#34; and the associated user desires to maintain an active call connection with the user at the associated connected station. 
     Processor 107, following validation of the &#34;off-hook&#34; state at step 602, retrieves the identity of the call connection associated with the requesting station, call connection A, from its main memory at step 603. Control processor 107, concurrently, scans the pre-hold call status table for the requesting station. The pre-hold call status table of FIG. 4 indicates that station set 100-0 is included in connections A and B, step 604. Multi-appearance station set users, as previously described, may participate in several active call connections at one time and therefore, the control processor must apply the connection-otherwise, a feature may be inadvertently applied to the wrong call connection of the requesting station. If the retrieved identified call connection does not match one of the call connections appearing in the call status table, the control processor abandons the &#34;hold&#34; routine at step 605 and processing returns to point A of FIG. 5 to await the next service request. The requesting station, currently, as illustrated in the pre-hold call status table of FIG. 4, has an associated call connection A which matches the retrieved identified call connection A. 
     Following the determination by processor 107 that the identified call connection is valid, step 605, processor 107 scans the pre-hold call status table of FIG. 4 to detect whether the requesting station is currently in the &#34;talk&#34; state, step 606. If the requesting station is not currently in a &#34;talk&#34; state, that is, &#34;non-talk&#34;, with respect to the identified connection, the &#34;hold&#34; service request is inapplicable since there is no voice connection to disengage, and therefore, processor 107 abandons the service request and returns to point A of FIG. 5. Assume, however, as the pre-hold call status table of FIG. 4 indicates, that the requesting station 100-0 associated with connection A is in the &#34;talk&#34; state, 1. Call processing then continues to step 607 in response to a validation of the correct state at step 606. Processor 107, at step 607, removes the requesting station 100-0 from the &#34;talk&#34; state of the identified call connection. Processor 107, concurrently, updates the call status table to reflect the current state of station 100-0 on connection A. Since an active call connection is still maintained, post-hold station status table of FIG. 3 still indicates that station 100-0 is &#34;off-hook&#34; and post-hold call status table of FIG. 4 indicates that station 100-0 is still on connection A, but is now in the &#34;non-talk&#34; state. Station set 100-1 is now on hold, indicating that there is no voice connection between station 100-0 and 100-1. Processor 107 has now served the &#34;hold&#34; service request and returns to typical call processing at point A of FIG. 5. This processing status is maintained until the next service request is generated. 
     As described above, the control processor in response to call processing operations monitors the station sets to detect service requests and, following the identification of the type of service request generated from the stations, call processing implements the appropriate feature processing routine to satisfy the request. The feature processing routine processes the service request based on the state of the requesting station as indicated by the status tables contained in the control processor&#39;s main memory. 
     Assume, now, the states indicated in the post-hold status tables of FIGS. 3 and 4 for station set 100-0 are current where station set 100-0 is &#34;off-hook&#34; and is maintaining an active &#34;non-talk&#34; connection with station 100-1 on identified call connection A. Station set 100-0 user has placed station set 100-1 user &#34;on-hold&#34;. During this hold interval, the station set 100-1 user merely sets down his receiver and waits for a notification indicating the removal of the hold condition by the station set 100-0 user. Assume further that station set 100-0 user has dropped out of the B call connection, which was, as the pre-hold call status table of FIG. 4 indicates, a conference call connection. It is not necessary, however, that station set 100-0 user completely disengage from the established call connection, call connection B, to re-engage in a voice connection on another call connection, call connection A. Station set 100-0 user can place as many parties on hold as there are active call connections, but only one active voice connection can exist at a time. However, for ease of description assume that only one call is &#34;on-hold&#34;, and that station set 100-0 user has completely disengaged from the established conference connection B. 
     Assume, now, that station set 100-0 user wishes to resume a &#34;talk&#34; state connection with station set 100-1 user who is currently &#34;on-hold&#34; and awaiting the resumption of the voice connection between the two parties. Assume further that station set 100-0 user generates an &#34;un-hold&#34; service request by depressing the call appearance associated with the held call. Processor 107 has identified the &#34;un-hold&#34; service request and completed steps 501 through 506 of FIG. 5 to reach step 508. If the service request was inappropriate, as previously described, then, typical call processing is resumed at step 500. However, since the &#34;un-hold&#34; service request is valid, i.e. a hold condition currently exists, processing proceeds to point C of FIG. 7. In response to the &#34;un-hold&#34; service request, control processor 107 begins processing at step 700 of FIG. 7. 
     Control processor 107 retrieves the identity of the requesting station, station set 100-0, from its main memory. Processor 107, then, scans the post-hold station status table of FIG. 3, to determine if station set 100-0 is off-hook, steps 701 and 702. As the post-hold station status table of FIG. 3 indicates, station 100-0 is currently &#34;off-hook&#34;, 1. If station set 100-0 user is &#34;on-hook&#34;, processor 107 abandons the service request and returns to point A of FIG. 5 to await another service request since the state of the requesting station is inappropriate for the generated service request. However since the appropriate state exists, processor 107 then proceeds to step 703 and retrieves the identity of the connection, A, from its main memory. Processor 107 concurrently scans the post-hold call status table of FIG. 4, step 704, to detect the identified connection of the requesting station. As the post-hold call status table indicates, station set 100-0 is associated with connection A which matches the identified call connection retrieved from the main memory, step 705. Again, this determination is to prevent a mis-service to the requesting station on the wrong connection such as if connection B were still associated with station set 100-0. If no match occurred, then, processing returns to point A of FIG. 5; however, a valid match exists. Processor 107, then, scans at step 706, the post-hold call status table of FIG. 4 to determine if station 100-0 on connection A is in the &#34;non-talk&#34; state, 1. If &#34;non-talk&#34; is not the current state, call processing returns to point A of FIG. 5 to await another service request since the appropriate state associated with the service request is not present. To service an &#34;un-hold&#34; service request, the &#34;non-talk&#34; state must exist because the purpose of an &#34;un-hold&#34; request is to re-establish a &#34;talk-state.&#34; As illustrated on FIG. 4 in the post-hold call status table, station 100-0 is in the &#34;non-talk&#34; state on connection A. Processor 107 proceeds to step 707 and returns the requesting station to the &#34;talk&#34; state on the identified connection A. At this point, the &#34;hold&#34; condition has been removed from the requesting station. Control processor 107, concurrently, updates a call status table (not shown) to reflect that the station set 100-0 user is now in the &#34;talk&#34; state on call connection A. 
     Steps 700 through 707 define the states for detecting when the station of an activating party is changed from a &#34;hold&#34; to an &#34;un-hold&#34; state, that is, removal of the hold condition. Following the removal of the hold condition, processor 107 immediately re-establishes a voice connection between the activating party and the held party, station 100-0 and station 100-1. The parties on the connection may now converse. However, the previously held party must be notified as to the re-establishment of the voice connection between the parties. The remaining steps, 708 through 710 of FIG. 7, cause the control processor to immediately generate a notification indication to the held party to signal the conclusion of the hold interval such that conversation between the parties may resume. 
     Control processor 107 scans the post-hold call status table to identify if any other stations are included in the identified call connection A, step 708. As the post-hold call status table indicates, station set 100-1 is included in the identified call connection A, step 709. Processor 107, in response to identifying a station included on the identified call connection, generates a notification indication, e.g. a &#34;ring-ping&#34;, to the identified station, step 710. This notification indicates that the hold condition has been removed and that the voice connection has been re-established. The &#34;ring-ping&#34; type of notification alerts the held party of the resumption of the &#34;talk&#34; state. It is well-known that a station of the type described in FIG. 2 includes a mechanism 208 responsive to signals from the control processor, to generate an audible ringing burst and therefore, no further details are described. In the present case, the held party does not rely on aural monitoring of the station&#39;s receiver to hear the voice of the activating party to determine when the talk state is resumed. 
     Processor 107 repeats steps 708 through 710 to notify each of the stations included on the connection. This process of sequential notification occurs, for example, in a conference call connection where several held parties are involved in the connection. If no further stations require notification, the call processing routine returns to point A of FIG. 5. Processor 107 then resumes typical call processing operations and awaits another service request from any of the station sets 100-0 through 100-n. 
     In the above described manner, a held party or parties need not aurally monitor the station&#39;s receiver for the voice of the activating party to signal the conclusion of the hold interval and the re-establishment of the voice connection. The held party merely sets down the station&#39;s receiver and continues other activities until a notification is generated at the conclusion of hold interval. The above described feature processing arrangement monitors the states of the requesting station to detect when an &#34;un-hold&#34; condition exists and then, provides immediate notification to the held party or parties indicating the removal of the hold condition. Notification may be provided via an audible, visual, or tactile indication.