Home
>
ATT
>
Communications System
>
ATT DEFINITY Communications System Generic 3V4 Instructions Manual
ATT DEFINITY Communications System Generic 3V4 Instructions Manual
Here you can view all the pages of manual ATT DEFINITY Communications System Generic 3V4 Instructions Manual. The ATT manuals for Communications System are available online for free. You can easily download all the documents as PDF.
Page 101
ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Busy Condition For calls placed to off-PBX destinations, the busy results from the call classifier detecting either precise or imprecise busy tones or the ``DISConnect/cause=user busy (CS0/17 Ð User Busy) message returned by an ISDN-PRI facility. A Third Party Call Ended is sent in these cases to the adjunct with cause value CS0/17 Ð User Busy. For calls placed to on-PBX destinations, the busy condition is the result of the ``busy...
Page 102
ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Switch Operation for Switch-Classified Call Setup This section details the switch actions for each stage of call setup. After the initial alert event is reported, the switch waits for the call to be classified as answered or dropped. The Alerting Event Report is sent to the adjunct only for the first ringing occurrence. If network answer supervision is received before the classifier detects answer, the classifier is disconnected....
Page 103
ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb For G3V3 and later, an ASAI adjunct may request Answering Machine Detection (AMD) for a switch-classified call. If AMD is requested for a call, the receipt of Network Answer Supervision or the ISDN CONNECT message is no longer sufficient to classify the outcome of a call. Further classification by the call classifier is required. If an answering machine is detected, a cause value is sent in either the Answered or the Call Ended...
Page 104
ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb If the destination has a display, the originating group (for example, the hunt group) is displayed as the calling party. This call cannot be picked up by a pickup group user. Negative Acknowledgement (NAK) of a Switch-Classified Call A Third Party Make Call (switch-classified) request is denied if: The ``type field in the Domain IE (which codes the dest_route_select) does not specify ``trunk (cause=CS0/100). The switch cannot obtain...
Page 105
ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb extensions. Valid destinations are on-PBX extensions (including VDNs) and off- PBX numbers. All trunk types (including ISDN-PRI) are supported as facilities for reaching called endpoints for outbound User-Classified calls. Call progress feedback messages are reported as events across the BRI ASAI interface. Answer supervision and call classifiers are not used for this type of call. Parameters for User-Classified Calls This list...
Page 106
ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb UUI from a Third Party Make Call will be sent in any ISDN PRI setup for the call, in the Alerting and Call Offered Event Reports, and in a Route Request, if one is made. Call Classification for User-Classified Calls All call-progress audible tones are provided to the originating user at the calling endpoint (except that user does not hear dial tone or touch tones). Call progress feedback is sent to the adjunct in event reports. For...
Page 107
ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb that VDN. If the calling endpoint has a display set, the display shows the called endpoints extension and name (if the called endpoint is on-PBX), or the name of the Trunk Group (if the called endpoint is off-PBX). Originators may be ACD agents in various work modes. User-Classified Call Destination If the destination is an on-PBX station user, the user receiving such a call receives alerting (according to whether the call was...
Page 108
ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb The call could not be originated because of lack of resources (cause=CS3/40). A UUI Information Element longer than 32 bytes was received (cause=CS0/100). The originator is not a valid station extension (cause=CS0/28) A service circuit is requested (cause=CS3/80) Answering Machine Detection is requested (cause=CS3/80) A call placed to a called endpoint whose COR does not allow the call to end will return intercept treatment to the...
Page 109
ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb split_paramMust be present and contain a valid split extension; dest_addr must be logged into this split. priority_calling[optional] If present, originates the call as a priority call. If not present, it defaults to nonpriority. max_ringsN/A (Ignored) direct_agent_callMust be present supervisor_assistMust not be present uui_info[optional] The switch supports receiving UUI in the Third Party Make Call request from the adjunct. If an...
Page 110
ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb Direct-Agent Call Originator In order for the call to be placed, the calling endpoints voice set must have an available call appearance for origination and must not be in the talking state on any of the other call appearances. The calling endpoint is allowed to have a call on hold. The originator may go off-hook first, and then issue the Third Party Make Call request. The switch will originate the call on the call appearance with...