Home
>
ATT
>
Communications System
>
ATT DEFINITY Communications System Generic 3 Instructions Manual
ATT DEFINITY Communications System Generic 3 Instructions Manual
Have a look at the manual ATT DEFINITY Communications System Generic 3 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+.
CallVisor Adjunct/Switch Ap plications Interface (ASAI) Issue 3 March 1996 3-517 group causes an Alerting Event Report to be sent to all domain-c ontrol associations for the terminating group. For the member of the g roup that answers the call, a Connected Event Report is returned to the answering member domain controller(s) with the station which answered the call. All the domain controllers for the other group members (non-answering members without TEG buttons) receive a Call Redirected Event Report. When a button TEG member goes on hook but the TEG itself does not drop from the call, no event is sent b ut the state of that party c hanges from the connected state to the bridged state. The Disconnect/Drop Event Report is not sent to each member’s associations until the entire TEG drops from the call as opp ose d to an individual member going on hook. Members that are not connected to the call while the call is connected to another TEG member are in the bridged state. When the only connected member of the TEG transitions to the held state, the state for all memb ers of the TEG changes to the held state even if they were previously in the bridged state. There is not event report sent to the brid ged user associations for this transition. All memb ers of the TEG may be individually ‘‘domain controlled.’’ Each receives appropriate events as applicable to the controlled station. Third Party Call Control requests work normally if invoked over the station domain. However, Third Party Selective Hold, Third Party Merge, Third Party Reconnect, and Third Party Selective Drop are not permitted on parties in the brid g ed state and may also b e more restrictive if the exclusion option is in effect from a station associated with the TEG. Third Party Auto Dial or Third Party Make Call requests cannot specify the TEG group extension and the originator. TEGs can only receive calls, not originate them. If a Party Query ID is requested while the TEG is alerting or on hold, one party member is reported for the group with the extension number specified as the TEG group extension. If a Calls Query is requested on an extension while the TEG call is active, only one call appearance is associated with the particular call identifier. nTimed Reminder Monitored and controlled calls (including calls originated and route d with CallVisor ASAI) extended b y an attendant and not answered are redirected back to the attendant when the timed reminder interval expires. See the Attendant Call Waitin g feature for events returned to the adjunct. Ve ctoring causes all other timers to be ignored. nTransfer Manual transfer from domain-controlled station is allowed subject to the feature’s restrictions. The Hold Event Report is provided as a result of the first button p ush. The Transfer Event Report is provided as a result of the second button push, and only if the transfer is successfully completed.
Feature Descriptions 3-518Issue 3 March 1996 The Transfer Event Report is sent to all active associations for the resultant call. For ad d itional information on the Transfer interactions, refer to Conference/Transfer feature interaction bullet item in this section. nTrunk-to-Trunk Transfer When this feature is enabled, adjunct-monitored or controlled calls (except switch classified calls) transferred from trunk-to-trunk are allowed. nVoice Message Retrieval A station user hears ‘‘Please call message for more messages’’ when the message waiting indicator is activate d by an adjunct using the Set Value capability. If the voice terminal display is used to retrieve messages, and if the Message Waiting Indicator is activated by an adjunct using the Set Value Capability, then the voice terminal d isp lays: ‘‘You have adjunct messages.’’ nVuStats Concurrent operation of VuStats and ASAI-Accessed BCMS reduces the operator’s c a pabilities of both. nWait-Answer Supervision Timer (WAST) Starting with G3V4, if an alerting call is successfully redirected, the WAST is cancelled. Administration The CallVisor ASAI feature is administered on a per-system basis. The following items require administration: nSystem Parameters/Customer Options Form On this form, the CallVisor ASAI Interface option must be enabled. In a d dition, the following CallVisor ASAI Capability Groups (previously described in this feature description) are also o ptioned on the form: —Adjunct Call Control Group — Allows the adjunct to invoke the Third Party Call Control capabilities. —Adjunct Routing Group — Allows the adjunct to provide adjunct routing information to the switch for incoming calls. —Domain Control Group — Allows an adjunct to control calls and receive event reports for station sets and receive logout event reports for adjuncts in a given ACD split. —Event Notification Group — Allows the adjunct to request incoming call notification and enables the switch to send event reports about such calls. —Request Feature Group — Allows the a djunct to request features such as change work mo des, login/logout, Send All Calls, and Call Forwarding.
CallVisor Adjunct/Switch Ap plications Interface (ASAI) Issue 3 March 1996 3-519 —Set Value Group — Allows the adjunct to request status changes for Message Waiting lam ps (that is, control the on/off state of the lamps), and billing changes for 900-type calls. Note that billing changes require that the Flexible Billing option b e enabled on page 1 of the System-Parameters Customer Options form. A T&T-AS A I Links — Allows an AT&T ASAI enabled adjunct to activate a proprietary link. Table 3-49 shows which capabilities are automatically available when CallVisor ASAI is enabled. Table 3-49. Automatically Enabled CallVisor ASAI Capabilities CapabilityCall Control GroupAdjunct Routing GroupDomain Control GroupEvent Notif. GroupRequest Feature GroupSet Value Group Event Re ports X X X - Agent Login - Ag ent Logout X 1 - Alerting X X X - Answered X X - Busy/Unavailable X X X - Call En ded Event (FAC message)X - Call Initiate d X - Call Offered to DomainX - Call Originated - Call Redirected X X - Call Conferenced X X X - Connected X X X - Cut-Through X X X - Denial/Reorder X X X - Disconnect/Drop X X X - Hold X X X - Queued X X X - Reconnected X X X - Call Transferred X X X - Trunk Seized X X X
Feature Descriptions 3-520Issue 3 March 1996 Request Feature X Notification Request X Notification Cancel X Notification Ended X Route En d X Route Request X Route Select X Set ValueX Stop Call Notification X Third Party Answer X Third Party Auto Dial X Third Party Call Ende dX Third Party Clear Call X Third Party Domain ControlX Third Party Domain Control Ende dX Third Party Make Call X Third Party Merge X X Third Party ReconnectXX Third Party Relinquish ControlXX Third Party Selective HoldXX Third Party Selective DropXX Table 3-49. Automatically Enabled CallVisor ASAI Capabilities — Continued CapabilityCall Control GroupAdjunct Routing GroupDomain Control GroupEvent Notif. GroupRequest Feature GroupSet Value Group
CallVisor Adjunct/Switch Ap plications Interface (ASAI) Issue 3 March 1996 3-521 NOTE: By enabling the CallVisor ASAI option(s), the following c a pabilities are automatically enabled as well, regardless of the groups selected: Value Query (includes Response Continued Capability), Abort, Heart Beat, Restart Procedure, Susp end/Resume Alarm. nHunt Group Form If an ACD split is to be adjunct controlled, the “ Controlling Adjunct” field of this form must be a dministered as only available with ASAI or ‘‘asai’’ (if the CallVisor ASAI Request Feature Group option has been enabled on the System Parameters Customer Options form). If the “ Controlling Adjunct” field is administered as asai, an “ ASAI Link Extension” field appears. This field should contain the extension of the administered CallVisor ASAI BRI link extension (see ‘Station form administration). nCall Vector Form The CallVisor ASAI Link Extension must be administered for the a djunct routing step on the ‘Call Vector’ form. nClass of Restriction Form Direct Agent Calling is allowed only if both the originator and the destination a gent have a Class of Restriction (COR) that allows Direct Agent Calling. nTrunk Group Form Trunk Groups must be administered to pass or receive CPN/BN calling party information if the ASAI a p plication expects or requires CPN/BN information. 1. Login and logout are only provided for Domain Control of ACD Split; all other event reports are provided for Domain Control of stations. Third Party, Re direct CallXX Third Party, Send DTMF SignalsXX Third Party Take ControlX Table 3-49. Automatically Enabled CallVisor ASAI Capabilities — Continued CapabilityCall Control GroupAdjunct Routing GroupDomain Control GroupEvent Notif. GroupRequest Feature GroupSet Value Group
Feature Descriptions 3-522Issue 3 March 1996 For an OCM application using network answer supervision, those trunks which support network answer supervision should have the “Answer Supervision” field set to ‘‘yes.’’ For trunks that do not receive real answer, the “ Answer Supervision Timeout” field determines when the ASAI event connect is sent. nStation Form A CallVisor ASAI endpoint must be a dministered with station type ‘‘ASAI’’ or ‘‘asai,’’ or ‘‘AT&T-ASAI link.’’ A maximum of four/eight (depending on system) CallVisor ASAI endpoints can be assigned. An additional station type is AT&T-adjunct. nSpecial Information Tone Each “ Special Information Tone (SIT)” field [ there are a total of six different SITs] and one Answering Machine Detection (AMD) Treatment must be administered as either dropped or answered. When a particular SIT is detected by the call classifier circuit pack, the switch acts in accordance with the choices indicated on this form. For more d etailed information on the administration of CallVisor ASAI, see DEFI NI TY Com munications System Generic 3 Version 4 Implementation, 555-230-655, or DEFI NIT Y Com munications System Generic 3 V2/V3 Implementation , 555-230-653 or DEFINITY Communications System Generic 3 CallVisor ASAI Technical Reference, 555-230-220. Hardware and Software Requirements The TN744 Call Classifier or the TN2182 Tone Clock is required for switch call classification and is also used by on-switch call prompting. Each port on the circuit pack acts as a touch-tone receiver or call classifier and is capable of detecting tones, including Special Information Tones. NOTE: This call classification only works if the p u blic network provides similar tones to those used in the United States. Each ASAI-BRI Interface Link requires a port on a TN556 ISDN-BRI circuit pack. Up to eight ports may b e assigned for G3v and four for G3v/s/i. Each ASAI-DEFINITY LAN Gateway Link requires the ED-IE546-70 (with TN2208 and TN2170 circ uit packs, tape and disk drives, and software to support this transport mechanism). There is a limit of 4 links per LAN Gateway. The G3s and G3i systems must be equip ped with the TN778 packet control circuit pack and a TN771 Maintenanc e-Test circuit pack. If EPNs are present, TN570B expansion interface boards are required. ASAI Interface software RTU (right to use) with the DEFI NI TY G3 g eneric software is required.
CDR Account Code Dialing Forced Entry of A ccount Codes Issue 3 March 1996 3-523 CDR Account Code Dialing Forced Entry of Account Codes Feature Availability This feature is available with all Generic 3 releases except for G3vs/G3s ABP. NOTE: The Ca ll De tai l Recording (CDR) feature was previously called the ‘‘SMDR Account Code Dialing’’ feature. Description Allows c ertain calls to b e associated with a particular project or account number. This is accomplished by dialing specified account c o des before making outgoing calls. This information is recorded by the CDR feature and can be used later for accounting and/or billing purposes. Requires users to dial an account code when making certain types of outgoing calls. The conditions under which dialing of account codes is required depends on system administration. To associate an account code with a particular call, a user first dials a CDR access code. The user then dials the desired account code, which can contain up to 15 d i gits. The user then dials the desired trunk access code, or ARS access code. CDR Account Code Dialing can be optional or mandatory (forced). Forced entry of a c count codes can be assigned for any of the following: nDesignated Toll Calls ‘‘Toll calls’’ are d efined by the administered toll analysis ta ble. Each ‘‘Dialed String’’ entry in the toll analysis table that is designated as a toll call can also be administered to require forced entry of account codes. If the system is administered to require forced entry of account codes, and a specific number or ‘‘Dialed String’’ is administered to require forced entry of a c count codes, any system user must dial an account code before dialing that number. This includes all calls made by ARS, or TAC. nToll Calls Ma de By Users With a Specific COR If forced entry of account codes is assigned to a specific COR, any voice terminal assigned that COR must dial an account code before making toll calls. nDesignated Toll Calls Made By Users With a Specific COR If forced entry of account codes is assigned to a specific COR, any voice terminal assigned that COR must dial an account code before making toll calls that are administered to require forced entry of account codes.
Feature Descriptions 3-524Issue 3 March 1996 nAll Calls Made on a Trunk Group With a Specific COR Any trunk group that is assigned a COR with forced entry of account codes cannot be accessed until an account code is dialed. If a call is being routed via ARS, account code checking is not done on the trunk group’s COR. Any time an account code is required and the user does not enter an account code, intercept tone is heard. An account c o de is never required for the following: nAttendant originated call nBusy verification of a trunk by an attendant or voice terminal user nDistributed Communications System (unless required by the trunk group’s COR) nPCOL nRemote Access Without Barrier Codes nTrunk-to-Trunk Connections Considerations CDR Account Code Dialing provides an easy method of allocating the costs of specific calls to the correct project, department, and so on. Call information is recorded by the CDR feature for this purpose. Account Code length can be up to 15 digits. However, not all CDR formats support 15 d i gits. The maximum decreases if an authorization code is dialed. The validity of the entered account codes cannot be checked by the system. Interactions The following features interact with the CDR Account Code Dialing feature. nAuthorization Codes Authorization codes are recorded on all CDR printouts exc ept for the 59-character, CDRU, and ISDN CDRU formats, without regard to account code length. For the non-ISDN and the ISDN LSU formats, authorization codes are recorded on CDR printouts if the account code length does not exceed six d i gits. For Enhanced LSU, the account code length must not exceed six d i gits. nARS If a trunk group is accessed via ARS, the trunk group’s COR is not used to determine if an account code needs to be entered.
CDR Account Code Dialing Forced Entry of A ccount Codes Issue 3 March 1996 3-525 nBusy Verification of Terminals and Trunks An attendant or voice terminal user is never required to enter an account code when making a busy verification. nCall Forwarding Calls cannot be forwarded to a destination where a user is required to enter an account code. nLast Numb er Diale d The CDR access code and account c o de dialed are stored as part of the Last Number Dialed. However, some digits may b e lost d ue to the limit on the number of digits stored for this feature. nCDR CDR does not record the correct account code if the length of the a ccount code is changed during an active call. For examp le, if the account c o de length is 5, a user dials 12345, and the account code length is changed during the call to 2, the CDR record shows only the first 2 digits (12) of the account code. Administration CDR Account Code Dialing is administered by the System Manager. The following items require administration for forced entry of account codes: nWhether or not all toll calls require account code entry (per system) nWhether or not each individual COR requires account code entry nWhether or not each Dialed String in the Toll Analysis table requires account code entry Hardware and Software Requirements No a d ditional hardware is required. Optional CDR Account Code Dialing software is required.
Feature Descriptions 3-526Issue 3 March 1996 Centralized Attendant Service (CAS) Feature Availability This optional feature is available with all Generic 3 releases except G3vs/G3s ABP. Description Allows services performe d by attendants in a private network of switching systems to be concentrated at a c entral, or main, location. Each branch in a CAS has its own LDN or other type of access from the public network. Incoming trunk calls to the branch, as well as attendant-seeking voice terminal calls, are routed to the centralized attendants over RLT. The C AS attendants are located at the main location. The main location c an b e a DEFI NI TY s yst em Generic 1 or 3, a DEFINITY s yste m Generic 2.1, System 85, a DIMENSION PBX, or a System 75 (V3). The CAS main PBX operates independently of the CAS branch PBXs. The operation for CAS main PBX traffic is identical to a stand-alone PBX. Each branch in a network with CAS is connected to the main by way of RLTs. These trunks serve three basic functions: nPaths for sending incoming attendant seeking trunk calls at the branch to the centralized attendant to be processed and extend e d back to their destinations at the branch (both parts of a call use the same trunk) nPaths for returning timed-out waiting and held calls from the branch to the main nPaths for routing calls from voice terminals in the branch to the centralized attendant at the main RLTs can be seized only from the branch switch and are used only for CAS calls and CAS signaling. After processing by a centralized attendant, CAS calls are extend e d back over the same RLT to, for example, the requested extension number or outgoing trunk. The RLT is then dropped and becomes available for other calls toward the centralized attendants. Two queues are associated with CAS calls, one at the main and one at the branch. When idle RLTs are available from the branch to the main, RLTs are seized and CAS calls are placed in the attendant queue at the main along with other attendant-seeking calls. If all RLTs are in use, the branch switch puts calls to the attendant in a RLT trunk queue at the branch. The length of RLT trunk queue can vary from 1 to 100 and is set during administration of the RLT group. Backup service provides for all CAS c alls to be sent to a backup extension in the local branch if all RLTs are maintenance busy or out of service, or if a Backup