Home
>
ATT
>
Communications System
>
ATT DEFINITY Communications System Generic 3V4 Instructions Manual
ATT DEFINITY Communications System Generic 3V4 Instructions Manual
Have a look at the manual ATT DEFINITY Communications System Generic 3V4 Instructions Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 164 ATT manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
ASAI and Call Routingbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Receiving a Valid Route Select (CS3/30) The switch cancels/terminates any outstanding Route Requests for the call after receiving the first valid Route Select message 2. The switch sends a Route End with cause CS3/30 (Call redirected) to all other outstanding routing associations for the call. Call Drops With Outstanding Route Requests (CS3/86) If the call drops (for example, caller abandons, vector disconnect timeout occurs, or a non-queued call encounters a ``stop step, or adjunct cleared call), all outstanding Route Requests are cancelled (cause value CS0/86 Ð Call has been terminated). Route Ð NAKs and Aborts Route Requests may be individually rejected (Route Request Ð NAK) or aborted (ABORT) by the adjunct without effect on other outstanding Route Requests. Vector Disconnect Timer Expires (CS0/86) When the Vector Disconnect Timer times out, all outstanding Route Requests are cancelled. Route End(s) is sent with cause CS0/86 Ð Call disconnected. Invalid number/domain (CS0/28) The destination address in the Route Select is invalid. Permission denied (CS3/43) Lack of calling permission, for example, for an ARS call, insufficient Facility Restriction Level (FRL). For a direct-agent call, the originators COR or the destination agents COR does not allow direct-agent calling. Recovery on timer expiry (CS0/102) This occurs when vector processing encounters any steps other than ``wait, ``announcement, ``goto vector, ``goto step, or ``stop after the adjunct routing command has been issued, or if processing times out at the wait step. See the DEFINITY Communications System Generic 3 Feature Description , 555-230-220, and the DEFINITY Communications System Generic 3 Call Vectoring/EAS Guide , 555-230-520, for more information. aaaaaaaaaaaaaaaaaaa 2. A valid Route Select is defined as a Route Select containing all the appropriate parameters (information elements). The contents of the information elements do not need to be correct. 7-10 Issue 4 September 1995
ASAI and Call Routingbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Agent not a member of split (CS3/11) Upon routing to an agent (for a direct-agent call), the agent is not a member of the specified split. Agent not logged in (CS3/15) Upon routing to an agent (for a direct-agent call), the agent is not logged in. ACK (Positive Acknowledgment) Parameters bbbbbbbbbbbbbbb None for this capability Denial (NAK) Causesbbbbbbbbbbbbbbb None for this capability Protocol Error (NAK) Causebbbbbbbbbbbbbbb None for this capability Considerationsbbbbbbbbbbbbbbb If a non-ISDN PRI call is routed successfully, the Called Party Number provided in the pertinent Event Report is the same number provided by the adjunct as the new destination of the call in the Route Select. If the call is an ISDN-PRI call, then the Called Party Number provided in the Event Reports is the original called number provided in the ISDN setup message. Issue 4 September 1995 7-11
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb bbbbb ASAI and Request Feature Capabilities 8 bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb This chapter describes the Request Feature Capabilities Group. These capabilities allow the adjunct to request or cancel switch-controlled features. The following capabilities are available: Request FeatureThis capability lets the adjunct invoke or cancel switch-controlled features. U-Abort (User Abort)See Chapter 3, ``Common Capabilities. Issue 4 September 1995 8-1
ASAI and Request Feature Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Request Feature Capability Groupbbbbbbbb An adjunct uses this capability to request invocation of one of the following switch features: ACD Agent Features Ð Login Ð Logout Ð Work mode changes Call Forwarding Send All Calls (SAC) Information Flowbbbbbbbbbbbbbbb The adjunct expects a response to its request. The switch either acknowledges or denies the request. Request Feature Parametersbbbbbbbbbbbbbbb feature_idSpecifies the feature to be invoked: Agent Login (login agent to ACD split) Agent Logout (logout agent from ACD split) Change agent work mode (change work mode of ACD agent to another mode) Call Forwarding Send All Calls feature_paramsSpecifies parameters specific to each feature: ACD agent login Ð Login identifier (password) Ð ACD split extension Ð Agent extension Ð [optional] Work mode (corresponds to initial work mode; if not specified, defaults to Auxiliary work) After call work, Auto in, Manual in, Auxiliary work 8-2 Issue 4 September 1995
ASAI and Request Feature Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb ACD agent logout Ð ACD split extension Ð Agent extension ACD agent change of work mode Ð ACD split extension Ð Agent extension Ð Work mode After call work, Auto in, Manual in, Auxiliary work Activate Call Forwarding Ð Forwarding extension Ð Forwarded to number Cancel Call Forwarding Ð Forwarding extension Activate Send All Calls Ð Extension (Activates SAC at this number) Cancel Send All Calls (SAC) Ð Extension (Deactivates SAC at this number) ACK (Positive Acknowledgement) Parameters bbbbbbbbbbbbbbb None for this capability Denial (NAK) Causesbbbbbbbbbbbbbbb The switch issues the following reason as the cause for not invoking the requested feature: Switching Equipment Congestion (CS0/42) The switch is not accepting the request at this time because of processor overload. The adjunct or user may wish to retry the request but should not do so immediately. Requested facility (capability) not subscribed/provisioned (CS0/50) The user has not subscribed for the specific capability. Mandatory information element (parameter) missing (CS0/96) A required parameter is not present in the request. Issue 4 September 1995 8-3
ASAI and Request Feature Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Resources not available (CS3/40) The request cannot be executed due to a lack of available switch resources. Invalid number (CS0/28) An invalid ACD split or agent extension value has been designated in the request. Invalid association (CS0/81) The association is already in existence. Agent not member of split (CS3/11) The agent making the request is not a member of the specified split. Incorrect number of agent login digits (CS3/14) Agent not logged in (CS3/15) The agent is not logged in (applies only to agent login). Agent logged into another split (CS3/13) The agent is already logged into the maximum number of splits. In same state (CS3/16) The request puts the agent in the same state that he or she is currently in. User Busy (CS0/17) The agent is busy on another call. For the particular extension, the agent is active (talking) on a call when a login request is made Ð an agent cannot be logged in when in the active state. Also, if the station user goes off-hook, dials one digit to begin making a call, and then the adjunct sends a login feature request for that particular user, the switch denies the request. Service/Feature not available (CS3/63) The feature is not available for the extension entered as the split extension. Note that an invalid split extension can be a valid nonsplit extension (such as an agent extension) on the switch, but it is still denied. Temporary Failure (CS0/41) System failure Agent state inconsistent with request (CS3/12) A work mode change is requested for a non-ACD agent or the ACD agent station is maintenance busy or out of service. Split not Administered Correctly (CS3/41) A request has been denied by the switch to log in, log out, manual-in or change work mode to auxiliary work or after-call-work for a member of the auto-available split. Change work mode is accepted for a member of the auto-available split only when the mode is to change to auto-in. Feature Request Rejected (CS3/53) This value is generated whenever the switch cannot return queried feature information even though the feature information may be defined for the specified extension. 8-4 Issue 4 September 1995
ASAI and Request Feature Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Service or Option Not Implemented (CS3/79) This value is returned when the queried feature has not been defined for the specified extension. Protocol Error (NAK) Causebbbbbbbbbbbbbbb The switch issues the following cause for generating a protocol processing error(s): Protocol error (CS0/111) The Q.932 protocol has been violated. NOTE: For more information regarding protocol errors and a complete list of reason codes (cause values), see the DEFINITY Communications System CallVisor ASAI Protocol Reference, 555-230-221. Considerationsbbbbbbbbbbbbbbb For nonadjunct-controlled ACD splits, agent login, logout, or change of work mode may be done manually via the voice set or the adjunct. Agents active in adjunct-controlled splits must be logged in or logged out and change work modes via the controlling adjunct. Login over ASAI is accepted only if the agent meets certain state conditions. These state conditions must be the same as if it is being done manually via a voice terminal. For example, if an agent is busy on a call, login is denied. An agent receives a logout denial if he or she is the last agent logged into the split and there are calls currently in the queue, unless the split is vector- controlled. If the split is vector-controlled, the last agent can log out even with a call in queue. Changes of work modes are accepted if they are allowed via a voice terminal. For the agent login request, the switch reads only the first 16 bytes, but it does not restrict the input of additional bytes. Issue 4 September 1995 8-5
ASAI and Request Feature Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb The following summarizes how ASAI work mode changes perform when an agent is busy (either on an active or held call, or being alerted): auto-in to auto-in the request is ACKD auto-in to manual-in the request is ACKD auto-in to aux-work the request is NAKD (cause = User Busy CS0/17) auto-in to after-call-work the request is NAKD (cause = User Busy CS0/17) manual-in to manual-in the request is ACKD manual-in to auto-in the request is ACKD manual-in to aux-work the request is NAKD (cause = User Busy CS0/17) manual-in to after-call-work request is NAKD (cause = User Busy CS0/17) aux-work to aux-work the request is ACKD aux-work to manual-in the request is NAKD (cause = User Busy CS0/17) aux-work to auto-in the request is NAKD (cause = User Busy CS0/17) aux-work to after-call-work the request is NAKD (cause = User Busy CS0/17) after-call-work to after-call-work the request is ACKD after-call-work to manual-in the request is NAKD (cause = User Busy CS0/17) after-call-work to auto-in the request is NAKD (cause = User Busy CS0/17) after-call-work to after-call-work the request is NAKD (cause = User Busy CS0/17) When an agent does not have auto-answer configured, they are not considered busy when they are: off-hook and idle, or off-hook and in a dialing mode on a call appearance. However, if auto-answer is configured, the agent is busy whenever one or more call appearances are not idle (in other words, they are busy when in a dialing state). (Generic 3r Only) Agents in auto-available splits receive a denial if the following request is made to: Log in Log out Manual-in Change work mode to auxiliary work or after-call-work for a member of the auto-available split Change work mode is accepted for a member of the auto-available split only when the mode is to change to auto-in. 8-6 Issue 4 September 1995
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb bbbbb ASAI and Value Query Capabilities 9 bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb This chapter describes the Value Query Capability Group. The capabilities available in this group allow the adjunct to request and receive information about the status or value of switch-controlled features and services. The following capabilities are available: Value QueryThis capability lets the adjunct ask for information about switch resources. Value Query ResponseThis capability lets the switch split an answer into multiple messages to the adjunct for long replies. U-Abort (User Abort)See Chapter 3, ``Common Capabilities. Issue 4 September 1995 9-1