The identity of the party who actually answers the call, as opposed to the identity of the party to whom the call was directed, is displayed. The call may be answered by someone other than to whom it was directed as a result of a call pick-up, hunt group call or a call forward feature being invoked at the destination system. The identity is given as either the directory number (including node ID) of the called party or, when the call is rerouted outside of the MSDN/DPNSS or MSAN/APNSS network, the trunk number of the local digital trunk.
The attendant individual trunk access feature allows the attendant to seize a nominated analog or digital trunk and dial digits over it in order to verify the trunk's "serviceability". The attendant identifies the trunk by its associated trunk number.
The attendant serial call feature allows the attendant to have a call originating on a DPNSS or APNSS trunk extended to a destination within the system environment, and automatically returned to the console after the call is completed so the originating caller may be connected to another party by the attendant. The operation of this feature is identical to the operation of the serial call feature involving non-APNSS or non-DPNSS trunks.
The attendant can set a serial call against any destination within the network. Route optimization is not applied to serial calls. See Serial call for more information.
If an outgoing call fails, a message indicating the cause of the failure is received by the originating system. This system then follows a clearing sequence. Display telephones and attendant consoles display a call failure indication: BUSY, OUT OF SERVICE, UNASSIGNED NUMBER. All sets receive appropriate tones depending upon the type of failure. Following a call failure, the control and speech path to the called station is released.
If an incoming call fails, a reason for failure is determined by the system and a clearing reason is returned to the originating system. The originating system interprets the clearing reason and acts accordingly.
Call forwarding in the outgoing direction to a station on another system is subject to the normal Call Forwarding conditions and Class Of Service (COS) restrictions; i.e., the station must have Call Forwarding - External Destination as one of its COS options. Incoming calls follow the call forwarding programmed for Call Forwarding - External Source.
See Call Forward in the Features Reference for conditions and programming.
Calls can be placed on hold, transferred, or conferenced. See Hold, Transfer, or Conference in the Features Reference for conditions and programming instructions.
Call split allows a user involved in a three-party conference to speak privately with one of the other parties. In an MSAN or MSDN network, only devices directly connected to the system on which the conference was formed can access this feature.
See Conference Split in the Features Reference for conditions and programming instructions.
The callback on busy/no answer feature allows a caller, who encounters a busy condition or whose call is not answered by the called party, to set up a callback. The calling station will be rung when the busy station becomes idle (i.e., goes on-hook).
The following conditions apply to this feature:
Both originating and terminating systems must have the DPNSS callback feature enabled.
When a callback matures, the station to which the callback was set will follow any call forwarding which may be in effect at that station.
Callback may be applied to stations only.
Callbacks mature only when both parties are idle.
Callbacks are automatically canceled after a programmable period.
The callback is canceled if the originating station completes a call to the station to which the callback was applied or if the station to which the callback was set completes a call to the originating station.
Callback may not be applied to a station with the Do Not Disturb feature already activated.
If a Callback is set to a station, and that station sets Do Not Disturb, the callback will not mature until Do Not Disturb is removed.
If a callback is set up from a station with Do Not Disturb activated, the callback will override the Do Not Disturb feature.
Feature Access Codes form: Assign a single digit access code to callback. First digit conflict between callback and other Feature Access codes is permitted with the exception of override and camp-on.
See CallBack in the Features Reference.
The callback with digit modification feature ensures that the callback feature will work in networks with non-uniform numbering plans, provided that the ARS Node Identities form has been properly completed
Note: The actual digit strings that must be dialed to reach another node in a DPNSS network must be programmed in the ARS Digits field of the ARS Node Identities form. If alternative digit strings should be dialed to reach a particular node, they must be programmed as a separate entry. Up to 5 Local Node Identifiers may be programmed for the local system, and up to 50 Remote Node Leading Digits entries may be programmed for the remote systems in the network.
See CallBack in the Features Reference for conditions, programming and operation.
The Called Line Identity feature displays the identity and state of the called party on the calling party's display telephone or attendant console. The identity is given as either the directory number (including node ID) of the called party or, when the call is completed outside the network, the trunk number of the local digital trunk. The state can be either "Ringing" or "Busy". If the call is transferred the display is updated.
This feature allows an internal caller to Camp-on to a busy extension. As soon as the busy extension becomes free, the caller is connected automatically. See Camp-on in the Features Reference for conditions, programming and operation.
The conferencing of digital trunks is allowed within the limits specified on the System Options form. See Conference in the Features Reference for conditions, programming and operation.
