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+.
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb bbbbb ASAI and Domain Control 5 bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb This chapter describes the Domain (Station or ACD Split/EAS skill) Call Control Capability Group. The adjunct uses these capabilities to control and monitor all calls at a station extension, to monitor selected calls only at that specific station, and to begin outbound calls from that station. Additionally, the adjunct may use this capability to receive Agent Logout Event Reports, and, starting with G3V4, Agent Login Event Reports, for a specified ACD split or EAS skill. Domain control capabilities are as follows: Third Party Domain Control Request for Station DomainWhen used with a station domain, the adjunct uses this initiating capability to ask the switch for event reports on calls at a specified domain (station extension). Third Party Domain Control Request for ACD Split/EAS Skill DomainAn adjunct may use this capability to receive Agent Logout Event Reports and, starting with G3V4, Agent Login Event Reports for a specified ACD split or EAS skill. Third Party AnswerThis capability allows an application to make a request on behalf of a station user to ``answer a ringing, bridged, or held call present at a station. Third Party Selective HoldThis controlling capability lets the adjunct put a specified call on hold at the extension being controlled. Issue 4 September 1995 5-1
ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Third Party ReconnectThe adjunct uses this controlling capability to reconnect a specified call at a controlled extension. Redirect CallThe adjunct uses this capability to re-route a call that is already alerting a station extension. Third Party MergeThe adjunct uses this controlling capability to merge two calls at a controlled extension. Third Party Selective DropThis controlling capability lets the adjunct drop a controlled extension from a given call. Third Party Auto DialThe adjunct uses this controlling capability to begin an outbound call on behalf of a station extension. Third Party Relinquish ControlThe adjunct uses this controlling capability to end an active domain-control association. Third Party Send DTMF SignalsThe adjunct uses this controlling capability to transmit a sequence of DTMF tones on behalf of the domain-controlled party on a specified call. Third Party Domain Control EndedThe switch uses this terminating capability when a domain-control association ends. Event ReportsSee Chapter 3, ``Common Capabilities. U-Abort (User Abort)See Chapter 3, ``Common Capabilities. NOTE: As previously stated, this capability group is actually a subsection of the ``Call Control Capability Group section in Chapter 4, but it is treated as a separate capability group in this chapter. 5-2 Issue 4 September 1995
ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Domain (Station) Control Descriptionbbbbbbbb Domain (station) Control allows an adjunct to receive event reports and control all calls beginning at or coming to a specific station extension. Without these capabilities, similar control and monitoring functions would require the adjunct to have adjunct control of the entire call. It allows the adjunct to control only the station extension associated with the Domain Control association instead of allowing control of all parties (extensions) on a call. When a call leaves the extension domain, event reports for the call over the domain-control association cease. Station Domainbbbbbbbbbbbbbbb A station domain is a valid station as specified in the dialing plan for which capabilities in the Domain Control subset can be requested. Station domains are limited to voice stations (including administered extensions without hardware) that are locally connected to the switch. It excludes, for example, the following: Data extensions Attendant console extensions Announcement extensions Off-PBX DCS/UDP extensions Any group-type extensions (hunt groups, ACD split or EAS skill extensions) VDNs One station domain maps to a physical set identified by a unique primary extension number (the number an administrator would give as a parameter in the display station command to display information for the station set). One station domain encompasses all call appearances at the physical station set, including all primary, bridged (from other primary extensions), TEG, and PCOL call appearances at the physical station set. Split Domainbbbbbbbbbbbbbbb A split domain is a valid ACD split or EAS skill extension specified on the Hunt Group form. Only the Agent Logout Event Report, and, starting with G3V4, the Agent Login Event Report, are provided for this domain. Third Party Call Control capabilities are not available for this domain. Issue 4 September 1995 5-3
ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Domain Call Control Capabilitiesbbbbbbbb The following capabilities have the same function within Domain Call Control as they do in the Call Control Capability Group. Third Party Merge Third Party Selective Hold Third Party Reconnect Redirect Call Third Party Selective Drop The following parameters allow the use of these capabilities over the Domain Control Capability Group. Call_idA call_id parameter is included in these capabilities for their use within a Domain Control association. Because a Domain Control association may control a number of calls, this parameter selects the call affected. An adjunct must always specify the call_id when requesting a Call Control Capability over a domain control association. The following table summarizes whether a specific Call Control request is or is not allowed based on the specified party state (bridge with multifunction station set principal is assumed and no exclusion feature active). Table 5-1. Call Control Acceptance in Various Party States bbbbbbbbbbbbbbbbbbbbb Domain Control Request Active St Held St Alerting St Idle St Dialing St Bridged St bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Third Party Auto Dial no 1yes2yes2yes3yes4yes3bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Third Party Answer yes yes yes no no yes bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Third Party Selective Drop yes no no no yes no bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Third Party Selective Hold yes yes no no no no bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Third Party Reconnect yes yes no no no no bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Third Party Merge(ctling pty) yes yes no no no no bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Redirect Call no no yes no no no bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbc c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c 1 User active on any call appearance or call2 On a call appearance other than the one in the given state3 User with at least one idle primary call appearance4 Call appearance selected for call originationbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb 5-4 Issue 4 September 1995
ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Third Party Domain (Station) Control Request bbbbbbbb An adjunct uses this capability to receive event reports and control calls at a specified extension. Information Flowbbbbbbbbbbbbbbb The adjunct expects a response to its request. The switch returns an acknowledgement to the application after the switch verifies that the station number is valid and the maximum number of controllers for the station has not been reached. Domain (Station) Control Request Parameters bbbbbbbbbbbbbbb domain[mandatory] This parameter identifies a valid local station. ACK (Positive Acknowledgement) Parameters bbbbbbbbbbbbbbb The switch responds to the adjuncts request with a list of call_ids, the party_id of the principals extension on the call, and the state of the principals extension on the call. Denial (NAK) Causesbbbbbbbbbbbbbbb The switch issues one of the following reasons as the cause for ending the association: Invalid association (CS0/81) The association does not exist. Invalid number/domain (CS0/28) An invalid address or extension number is present in the request. Service or Option Not Available (CS3/63) The maximum number of Domain Control Requests are in use for the domain. 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. Issue 4 September 1995 5-5
ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Protocol Error (NAK) Causebbbbbbbbbbbbbbb The switch issues the following cause for a protocol processing error: Protocol error (CS0/111) The Q.932 protocol has been violated or the capability invoked is not consistent with this association. For example, invoking the Third Party Domain Control request on a Call Control association is inconsistent. NOTE: For more information regarding protocol errors and a complete list of reason codes (cause values), see the DEFINITY Communications System Generic 3 CallVisor ASAI Protocol Reference , 555-230-221. 5-6 Issue 4 September 1995
ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Third Party Domain Control Request for ACD Split/EAS Skill Domain bbbbbbbb This capability allows the adjunct to receive event reports at a specified domain. Currently, only the Logout Event Report, and, starting with G3V4, the Login Event Report, are available. Third Party Call Control capabilities are not allowed for Third Party Domain Control for the ACD Split/EAS Skill Domain. Information Flowbbbbbbbbbbbbbbb The adjunct expects a response to its request. The switch returns an acknowledgement to the application after the switch verifies that the ACD split or EAS skill is valid. Domain Control Request for ACD Split/EAS Skill Domain Parameter bbbbbbbbbbbbbbb domain[mandatory] This parameter identifies the ACD split or EAS skill. ACK (Positive Acknowledgement) Parameters bbbbbbbbbbbbbbb None for this capability Denial (NAK) Causesbbbbbbbbbbbbbbb The switch issues one of the following reasons as the cause for ending the association: Invalid Association (CS0/81) The association is already in use. Invalid Number/Domain (CS0/28) The number contained in the request is an invalid parameter value. Service or Option Not Available (CS3/63) The maximum number of Domain Control requests are in use for the domain. 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. Issue 4 September 1995 5-7
ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Protocol Error (NAK) Causebbbbbbbbbbbbbbb The switch issues the following cause for a protocol processing error: Protocol error (CS0/111) The Q.932 protocol has been violated or the capability invoked is not consistent with this association. For example, invoking a Third Party Domain Control Request over a Call Control association is inconsistent. NOTE: For more information regarding protocol errors and a complete list of reason codes (cause values), see the DEFINITY Communications System Generic 3 CallVisor ASAI Protocol Reference , 555-230-221. Considerationsbbbbbbbbbbbbbbb The ``logout event is reported for split domain-controlled associations when an agent logs out of the split. This capability remains in effect for the split domain until either the adjunct invokes the Third Party Relinquish Control capability, or the switch invokes the Third Party Domain Control Ended capability. Call control and call-related events are not reported with this capability. Starting with G3V4, the ``login event is reported for split domain-controlled associations when an agent logs into the split. It is provided regardless of how the agent logs in (either manually through FACs or through ASAI). 5-8 Issue 4 September 1995
ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Third Party Answerbbbbbbbb This capability allows the adjunct to request, on behalf of a station user, that a ringing, bridged, or held call present at a station be ``answered. This is done by connecting a call by forcing the station off-hook, if the user is on-hook, or by cutting through the call to the head or handset, if the user is off-hook (listening to dial tone or being in the off-hook idle state). The effect is as if the station user selected the call appearance of the alerting, bridged, or held call and went off- hook. Information Flowbbbbbbbbbbbbbbb The adjunct expects a response to its request. The Third Party Answer request is acknowledged (ACK) by the switch if the switch is able to connect the specified call by either forcing the station off-hook (turning the speakerphone on) or waiting up to five seconds for the user to become off-hook. Third Party Answer Parametersbbbbbbbbbbbbbbb party_id[ignored] Indicates the alerting, bridged, or held party on the call that must be connected to the call. call_id[mandatory] Indicates the alerting, bridged, or held call that must be connected at the controlled station. ACK (Positive Acknowledgement) Parameters bbbbbbbbbbbbbbb None for this capability Denial (NAK) Causesbbbbbbbbbbbbbbb The switch issues one of the following reasons as the cause for ending the association: Invalid Association (CS0/81) The association does not exist. User Busy (CS0/17) The station is busy on a call or there are no idle call appearances available. No User Responding (CS0/18) The station user did not go off-hook within five seconds and is not capable of being forced off-hook. Issue 4 September 1995 5-9