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+.
Generalized Route Selection (GRS) Issue 3 March 1996 3-757 BCC and ITC Determination on Calls from ISDN-PRI Trunks to Endpoints (GRS not Involved) NOTE: The system does not use ITCs when terminating to an endpoint. Considerations nACCUNET and SDDN Services The system will be able to use ARS ta bles to route c alls to these networks. For exam ple, BCC 1 is a 56 k b ps service. If an ACCUNET 56 kbps Service trunk group is in a routing pattern that uses GRS, BCC 1 should b e set to yes. nSDI Service The system will be able to support the AT&T Switched Digital International (SDI) Service, which requires 64 kb ps unrestricted service for Mode 0 calls or 64 kbps restricted or unrestricted rate adapted to 56 kbps for Mode 1 calls. SDI will reject calls encoded as 64 kbps restricted without rate a daptation. Table 3-66. Calls from ISDN-PRI Trunks to Endpoints Originating Terminating Endpoint BCC BCC BCC 0 BCC 1 BCC 2 BCC 3 BCC 4 BCC 0 P P PM P P BCC 1 PPPPP BCC 2 PPPPP BCC 3 PPPPP BCC 4 PPPPP Legend P Allow the call, and (1) if it is a voice originated call, let the calling user decide whether the terminating endpoint is the correct endpoint or not based on audible feedb a ck (for example, data tone), or (2) if it is a data call, the data handshake procedure will establish or drop the call based on the compatibility of the endpoints. PM Insert a pooled modem and terminate the call to the endpoint. The ITC defaults to restricted in this case.
Feature Descriptions 3-758Issue 3 March 1996 nIntegrated Access on Non-ISDN-PRI Trunks The T1 carrier access to the AT&T serving office will allow sharing of the same trunk group for voice and data calls. For example, the same trunk group may carry both voice calls (requires a BCC of 0) and Mode 1 data calls (requires a BCC of 1). This situation requires the trunk group preferences in the ARS routing pattern to be administered with a ‘‘yes’’ for both BCC 0 and BCC 1. nVoice and Voice-Grade Data Calls Voice and voice-grade data calls cannot be routed separately if voice-grade data calls are assigned BCC 0. Voice-grade data calls could be assigned BCC 2. nModem Pooling A system originating a data call over a public or private network is responsible for inserting the pooled modem (when needed). Since the originating switch knows the speed of the call, it can insert the a ppropriate pooled modem. Since tandem switches do not know the sp eed of the call, they cannot make the d e cision on the type of pooled modem needed. Interactions The following features interact with the Generalized Route Selection feature. nAutomatic Route Selection (ARS) and Automatic Alternate Routing (AAR) In ARS/AAR, routing is b ased on the d ialed number, the Facility Restriction Level of the call originator, the partitioning group number, and the time-of-d ay. In GRS, routing of c alls is ad d itionally based on the BCC and ITC to distinguish voice from data calls. For all trunks, ISDN-PRI as well as non-ISDN-PRI, the BCC and ITC are checked to see if the route selected is compatible. nAAR/ARS Partitioning It is possible to perform GRS administration for each partition separately by using different routing patterns. nInterworking Generalized Route Selection will support interworking; that is, the routing patterns may contain a com bination of ISDN-PRI and non-ISDN-PRI trunking facilities. For non-ISDN-PRI trunking facilities, the BCC and ITC are d etermined by (default) a dministration. For ISDN-PRI trunking facilities, the BCC and ITC are determined by the information received on the signaling channel (D-channel) of the trunk.
Generalized Route Selection (GRS) Issue 3 March 1996 3-759 nCall by Call Service Selection For each preference in a routing pattern, the customer may optionally administer an IXC code and a Network Specific Facility parameter to be used when an outgoing call is made using an ISDN-PRI facility. Call by Call (CBC) Service Selection allows the dynamic identification of a s pecific service type request on a per call basis. For CBC Service Selection feature, the trunk group is administered as CBC. This allows the customer to pool several types of services together and assigns the service type to them on a call basis. nData Pre-Indication When the Data button is pressed on DCP voice terminals, the switch uses the BCC and ITC of the associated data module. nElectronic Tandem Network (ETN) Services To provide ETN services, the ISDN-PRI trunks can be used to interc onnect any combination of the following switches: System 85 R2V4, DEFI NI TY system Generic 1, Generic 2, or Generic 3. (An ETN is a network of privately owned trunk and switching facilities that can provide a cost-effective alternative to toll calling between locations.) The ETN Traveling Class Mark (TCM) will be passed between the tandem nodes by the TCM information element of the SETUP message on the ISDN-PRI facilities. (Traveling Class Marks represent the Facilities Restriction Level and are used by the distant tandem switch to determine the best available facility consistent with the user’s calling privileges.) The Satellite Hop Control (Conditional Routing) Count and End-to-End Connectivity message, which is used in System 85 R2V2 or Generic G2, is tan d e m i nto t he SE TUP message without being analyzed. For non-ISDN-PRI tandem trunks, the TCM is outpulsed after the destination address. Administration The following a d ditional items are administered by the System Manager for GRS. nRouting pattern BCCs — For each trunk group in the Routing Pattern, there will be an indication of what BCCs can use that preference. The values are 0, 1, 2, 3, and 4. More than one BCC may b e supported by one trunk group preference. The BCCs assigned to a trunk group in a Routing Pattern may or may not be the same value assigned to the same trunk group in another Routing Pattern. The ” ITC (Information Transfer Capability)” field administers the typ e of traffic (restricted, unrestricted, or both) that this routing preference may carry. This field is displayed and administrable if at least one of the BCC data p references is set to y. If only BCC 0 is set to y, then the “ITC” field is not displayed. The value of the “ ITC” field may be set to rest (restricted), unre (unrestricted), or both. The d efault is rest.
Feature Descriptions 3-760Issue 3 March 1996 The “ BCIE (Bearer Capability Information Element)” field specifies how to create the Information Transfer Capability c o depoint in the Bearer Capability IE of the SETUP message. This field only a p plies to ISDN-PRI trunks and is displayed and administrable if the “ITC” field is administered as both. The value both p rovides extra flexibility for managing facilities in a mixed unrestricte d/restricted environment. The value of the “ BCIE” field may b e set to ept (endpoint), unr (unrestricted), or both. The default is ept. If the “BCIE” field is set to ept, the ITC of the originating endpoint is used to encode the SETUP message. If the “ BCIE” field is set to unre, then unrestricted is encoded in the SETUP message. nTrunk Group BCCs — Each non-ISDN-PRI, data, AVD, or RBAVD trunk group is administered a BCC to identify the type of traffic on the trunks in that group. The “ ITC (Information Transfer Capability)” field is provided for non-ISDN trunk groups only. This field is displayed and administrable only if the “ Comm Type” field is administered as data, avd, or rbavd and the “ BCC” field is not set to 0. The value of the “ ITC” field may be set to rest (restricted) or unre (unrestricted). The default is rest. nAccess Endpoint BCCs — For access endpoints where the “Communication Type” field is set to 56K-data or 64K-data, the “ ITC (Information Transfer Capability)” field is displayed and administrable. The value of this field may be set to restricted or unrestricted. The default is restricted. nStation BCCs — For all non-ISDN endpoints, the “ ITC (Information Transfer Capability)” field is displayed and administrable on the Station Data Mo dule Page. The value of this field may be set to restricted or unrestricted. The default is restricted. This field is not displayed for voice-only stations and BRI stations. For BRI stations, the Default ITC (Information Transfer Cap a bility) is displayed and administrable on the Station Data Module Page. This field administers the ITC for BRI data modules that originate an administered connection (AC). The value of this field may b e set to restricted or unrestricted. The default is restricted. nData Module BCCs — For all non-ISDN endpoints specified as ‘‘p dm,’’ data-line, netcon, or tdm, the “ ITC (Information Transfer Capability)” field is displayed and administrable. The value of this field may b e set to restricted or unrestricted. The default is restricted. For BRI data modules, the Default ITC (Information Transfer Cap a bility) is displayed and administrable. This field administers the Information Transfer Capability for BRI d ata modules that originate an administered connection (AC). The value of this field may be set to restricted or unrestricted. The default is restricted.
Generalized Route Selection (GRS) Issue 3 March 1996 3-761 For endpoints (DCP d ata mo dules, voice terminals, and so on) a read-only “BCC” field appears on the screen form for that endpoint. This field reflects the endpoint’s current BCC which is determined automatically by switch software. Hardware and Software Requirements No a d ditional hardware is required. O ptional AAR, ARS, and ISDN-PRI services software is required.
Feature Descriptions 3-762Issue 3 March 1996 Go to Cover Feature Availability Go to Cover is available with all Generic 3 releases. Description Allows users, when making a call to another internal extension, to send the call directly to coverage. Go to Cover is activated by pressing a Go to Cover button. This button can be used only after the call is ringing. Details of how Go to Cover is used in conjunction with Call Coverage are given in the Call Coverage feature description elsewhere in this chapter. Consideration Go to Cover gives the calling party the option to send calls directly to coverage. Interactions The following features do not redirect to coverage unless the caller presses the Go to Cover button: nIntercom — Automatic nIntercom — Dial nPriority Calling Go to Cover can only be used if the called party is assigned a call coverage path; that is, the called party must have alternate answering positions assigned. Administration Go to Cover is administered on a per-voice terminal basis by the System Manager. The only administration required is to assign a Go to Cover button. Hardware and Software Requirements No a d ditional hardware or software is required.
Hold Issue 3 March 1996 3-763 Hold Feature Availability Hold is available with all Generic 3 releases. Description Allows voice terminal users to disconnect from a call temp orarily, use the voice terminal for other call purposes, and then return to the original call. Multi-appearance Voice Terminal Hold Multi-appearance voice terminals have a Hold button for activating the Hold feature. Multi-appearance voice terminal users can hold a call on each call appearance. To hold a call, a user, while active on a call, simply presses the hold button and the call is held at the call appearance being used for the call. Single-line Voice Terminal Hold Two types of Hold (soft hold and hard hold) are provided for single-line voice terminal users. With soft hold, the user can hold the current call, consult with another party or activate/deactivate a feature, and return to the soft held call. This type of hold is used to conference or transfer a call that includes the held call. Hard hold can be used to hold the current call and then p erform operations that do not include the held call. These operations could include calling another party, answering a waiting call and transferring or conferencing the waiting call with another party, activating or deactivating features, and so on. To activate soft hold, a user, while active on a call, presses the Recall button or flashes the switchhook. The user can then conference or transfer the call that is on hold. If the user dials another party and presses the Recall b utton or flashes the switchhook a second time, the held call is conferenced with the user and the other party. For a call transfer, the system ignores any subsequent presses of the Recall b utton or flashing of the switchhook. If the user is the controller of a conference call, and presses the Recall b utton or flashes the switchhook, the last party added to the conference is drop p ed. The user can transfer the call by hanging up after conferencing the call. To activate hard hold, a user, while active on a call, presses the Recall button or flashes the switchhook. The user then dials the Answer Hold-Unhold access code. This puts the call on hard hold. The user can then perform any operation that does not involve the held call. When the user wants to return to the hard held call, the user should go on hook. The held call rings the voice terminal and can then be answered.
Feature Descriptions 3-764Issue 3 March 1996 If a user has a call waiting and activates hard hold, the current call is placed on hard hold and the waiting call is answered automatically. Considerations With the Hold feature, voice terminal users can temporarily d isconnect from one call and handle another call. For exam ple, a b usy voice terminal user who receives another call c an p lace the first call on hold and answer the second call. This results in fewer missed calls. The Hold feature can also be used when a user receives a call and needs to make another call to obtain information for the calling party. A call involving an attendant cannot be held by a single-line voice terminal user. A call involving an attendant can be held by a multiappearance voice terminal user, unless the user attempts a conference or transfer of the call. A call dialed by a single-line voice terminal can be dropped within the first ten seconds (after dialing is completed) by flashing the switchhook. One p arty on hold can hear music if the Music-on-Hold feature is provided. The music is removed when the voice terminal user reenters the call. Interactions The following features interact with the Hold feature. nAutomatic Callback A single-line voice terminal user cannot receive an Automatic Callback call while it has a call on Hold. nBrid ged Call Ap pearance Any user, active on a bridged call, can place the call on hold. If a call on a bridged call a p pearance is placed on hold and no other users with a bridged call appearance of the same extension number are connected to the call, the status lamp at the Bridged Ap pearance button indicates that the call is on hold. If the primary extension or another bridged appearance is connected to the call, the status lamp at all brid g ed appearances indicates an active status for the call. nInteraction with Multi-Appearance Conference/Transfer nInteraction with Priority Calling It is possible to receive priority ringing and have a call on soft hold.
Hold Issue 3 March 1996 3-765 nLW C A held multiappearance voice terminal user can activate LWC toward the holding user. A single-line voice terminal user cannot activate LWC toward another user while a call is on soft hold. nPersonal Central Office Line When a user, active on a PCOL call, puts the call on Hold, the lamp flutters or winks the same as a call appearance lamp for hold-button. When a user, active on a PCOL call, puts the call on Hold, the status lamp associated with the PCOL b utton d oes not track the b usy/idle status of the PCOL. Administration The Hold feature is administered by the System Manager. The only administration required is to assign the Answer Hold-Unhold feature access code. Hardware and Software Requirements No a d ditional hardware or software is required.
Feature Descriptions 3-766Issue 3 March 1996 Hold - Automatic Feature Availability This feature is available with G3i-Global, G3rV1, all G3V2, and later releases. Description System-Wi de A dministrable Hold—Automatic (hereinafter referred to as Automatic Hold) is a station/attendant feature. The system comes with this feature turned off by default. The feature is described for stations as well as the attendant because of the similarity of the o peration. Automatic Hold allows attendants and Multi-Function station set users to alternate easily between two (or more) calls. For exam ple, depression of a second call appearance automatically p uts the active call (if any) on hold, and makes the second call appearance active. If the Automatic Hold feature is disabled (the default), the active call appearance is dropped. The ability to ad minister the Automatic Hold feature allows the customer to enable and disable the Automatic Hold Feature on a system-wide basis. A user of a multibutton station may p lace on Automatic-Hold as many calls as the number of call-appearances minus one. The controlling station can have only one ’soft’ auto-held call at a time. A ’soft’ hold is the state of a line after the conference or transfer button has b een pressed but before either process is comp leted. The controlling station is guaranteed the a bility to reenter any auto-held call later unless the auto-held party or parties disconnect or the auto-held tone times out. Considerations When Automatic Hold is disabled, if the Multi-Function Digital Telephone (MFDT) selects an inactive call appearance while there is still a call on an active call appearance, the active call is dropped. If Automatic Hold is enabled, when the MFDT selects an inactive call appearance while there is a call on an active call appearance, the active call is put on Hard-Hold. This is the same as if the MFDT had depressed the HOLD button and then selected a call a p pearance. Whenever only the Automatic Hold feature is involved, for example, when the attendant on an active loop presses a second loop, the active call is placed in Hard-Hold. Soft-Hold allows the attendant to extend calls and conference calls together. The Held Call Timed Reminder does not ap ply to conference calls and is not initiate d when a conference is placed on hold. The net result is that the attendant