Hot Desking allows a number of users to share one or more
hot desk sets. When a user logs in to a hot desk set, the system associates
the user's settings
See Hot Desking for information on conditions, programming, and feature operation.
Interworking relates to the ability of systems (operating with different levels of MSDN or MSAN functionality) to work together in an MSAN network or a mixed MSAN/MSDN network. To do this the networked systems have the ability to pass on messages which are not understood (transparent messages). The messages may then be understood by another system in the chain. The last system in the chain may act upon, reject, or ignore the message, depending on the message type, the context of the call, and the capabilities of the system. The Interworking example shows a configuration where interworking is necessary. A message associated with supplementary service X is sent from PBX A to PBX B. PBX B does not have an implementation of supplementary service X and therefore passes the message transparently to PBX C. PBX C, being the last in the chain, would reject or ignore the message if it did not have an implementation of supplementary service X.
Note that a mixed MSAN/MSDN network will not allow the connection of a MSDN/DPNSS network data call to an MSAN/APNSS network.
The "Last Number Redial" feature allows the user to have the system redial the last external number dialed, when either the last number redial code is dialed or the Redial key (consoles and multiline telephones) is pressed. An external number is defined as one which makes use of the system's Automatic Route Selection (ARS) feature. This feature uses ARS to select routes, so the digit strings used in network calls are treated as external digit strings for the last number redial feature.
The purpose of this feature is to prevent calls from passing through the same node repeatedly, creating a looping effect and tying up network resources. When this feature is enabled, each call placed in an MSDN/DPNSS or MSAN/APNSS network will be forwarded with a maximum limit restricting the number of systems that the call may pass through. The call will be dropped if it has exceeded that number when it arrives at a transit system.
The maximum number of transit systems is 25, therefore the maximum allowable network hops is 26.
If loop avoidance is not supported at the originating system, but is supported at a transit system, the transit system starts the network hops count.
If loop avoidance is not supported at a transit system the limit number will be ignored and passed on to the next system. The maximum number of allowable hops will not include hops through systems which do not support loop avoidance.
The number of allowable network hops is programmable and may differ from one network to another, from one system to another, and from one route to another in the same network. The maximum number of network hops per call is specified in the Trunk Groups form, in the 'Maximum Network Hops per Call' field. The maximum allowable value is 26, which is also the default value. This field must not be programmed for analog routes.
When a network call exceeds the number of allowable hops, it is dropped. telephones display "ERROR" and the user hears reorder tone. A log is written to record this event.
When a network call is call-forwarded to another system, the loop avoidance count is forwarded with the call.
When a network call is transferred to another system, the loop avoidance count is reset to a number specified by the transferring system.
When the Stepback feature is invoked at a transit system, the loop avoidance count is reset to the value it previously had at that system.
The Malicious Call Trace feature provides network-wide tagging capability of malicious calls. Every time the Tag Call feature is invoked, a Malicious Call Indication (MCI) request is sent, and two SMDR records are generated: the standard SMDR call record, and an MCI SMDR record.
See Malicious Call Trace for a detailed description.
Meet Me Answer lets you respond to a Group Page that you missed, even if you do not know the identity or location of the person that paged you. Each page group has one Meet Me Answer timer; you could have up to 15 minutes to respond to the most recent page by using the Meet Me Answer feature.
See Meet Me Answer in the Features Reference for conditions, programming, and operation.
