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+.
Wideband Switching Issue 3 March 1996 3-1255 To reduce the possibility of glare, the DEFINITY switch should be administered so that each side of the ISDN-PRI interface select channels from o p posite ends of the interface. In other words, one end should be administered to select B-channels from the high side (DS0 channel 23) and the other a dministered to select B-channels from the low side (DS0 channel 1) so as not to interfere with each other. In a ddition, there are algorithms in the switch’s operating code which attempt to gain control of channels closest to the starting DS0 so that Wideband channels are contiguous. For examp le, if the user side is provisioned to start at the high side (DS0 23) and DS0 22 is idle but DS0 23 is active, DS0 22 should be reselected for the next c all. This is known as linear trunk hunting. The DEFINITY switch uses the linear trunk hunt method and only the d irection of hunt is a dministrable. See the DEFINITY Communications System Generic 3 Version 4 Implementation , 555-230-655, or DEFI NI TY Com munications System Generic 3 V2/V3 Implementation, 555-230-653, for a dditional details. Blocking Blocking occurs when the number of B-channels required to make a call are not available. Narrow band (64 Kbps) calls require only one channel so blocking is less likely than with Wideband calls which require multiple B-channels. Blocking also occurs for Wideband calls when bandwidth is not available in the appropriate format (that is, fixed, floating, or flexible, see earlier description). To avoid this situation, the DEFINITY switch selects trunks for both Wideband and narrowband calls to maximize availability of idle fixed channels for H0, H11, and H12 calls and idle floating channels for NXDS0 calls. The strategy for preserving idle channels to minimize blocking depends on the channel type. The chances for blocking are reduced if the flexible algorithm is used. Interactions The following features interact with Wideband Switching: nAdministered Connections Provides call initiation for Wi deband Access Endpoints (WAEs). All administered connections that originate from WAEs use the entire bandwidth administered for the WAE. The destination of an Ad ministered Connection can be a PRI Endpoint. nAutomatic Circuit Assurance (ACA) Treats Wi deband calls as single trunk calls so that only a single ACA referral call is ma de if an ACA referral call is required. The referral call is on the lowest B-channel associated with the Wideband call.
Feature Descriptions 3-1256Issue 3 March 1996 nCall Detail Recording (CDR) Wideband calls trigger CDR record s containing the Wideband Bearer Capability Class (BCC) and the call bandwidth. Both access endpoints and PRI endpoints involved in a call are treated as line-side entities in that they do not trigger a standard CDR record. Intra-switch CDR may b e used to trig ger intra-switch records involving PRI endpoints. However, the intra-switch CDR c a pability is automatically disabled as soon as a trunk is involved with the call. Therefore, trunk-to-endpoint and endpoint-to-trunk calls must b e handled by trunk group administration using standard CDR records. nCall Management System (CMS) Wideband calls may be carried over trunks that are measured by the CMS but Wideband endpoints are not measured by CMS. nCall Vectorin g Wideband endpoints may use a vector directory number when dialing. In other words, PRI endpoints may dial a Vector Directory Number (VDN) when Vector Routes lead to other Wi deband endpoints. For example PRI endpoint 1001 dials VDN 500. VDN 500 points to Vector 1. Vector 1 can point to other PRI endpoints such as route-to 1002, or route-to 1003, or busy. This is only used by certain specific applications. Typ ically when an incoming Wideband call to a DEFI NI TY switch wants to hunt for an available Wideband endpoint, the call could route-to a VDN which would then send the call to the first available Wideband endpoint according to the vector routing program. nClass of Restriction (COR) The COR identifies calling and called party privileges for the Wideband endpoint(s). Administer the COR in such a way that Account Codes are not required. Also, Forced Entry of Ac count Codes should be turned off for Wideband endpoints. nClass of Service (COS) The COS determines the class of features that a Wid e band endpoint can activate. Administer the COS in such a way as to block the activation of Call Forwarding. nFacility and Non-Facility Associated Signaling Non-Facility Associated Signaling with or without the D-channel b ackup (DCBU) requires administration via Signaling Groups for trunk-side Wideband interfaces (not supported on the line-side). nFacility Busy Indication It is possible to administer a Busy Indicator b utton for a Wideband endpoint extension but the button does not accurately track the endpoint status.
Wideband Switching Issue 3 March 1996 3-1257 nFacility Test Calls Facility Test Calls can be used to perform loop-back testing of the Wideband call facility. nGeneralized Route Selection Generalized Route Selection supports a Wideband Bearer Capability Class (BCC) to identify Wideband calls. The Generalized Route Selection feature searches a routing pattern for a p reference that has the Wi deband BCC. Routing preferences that sup port Wi deband BCC also support other BCCs to allow different call types to share the same trunk group. nIntegrated Services Digital Network — Primary Rate Interface Standard ISDN-PRI interfaces can be administered for Wideband switching. nLeave Word Calling Dialing a Wideband endpoint extension as part of the Leave Word Calling feature a pplies an intercept to the activator. nSubnet Trunkin g Subnet Trunking is accomplished via Generalized Route Selection and Routing Pattern administration. Administration NOTE: Refer to the DEFI NI TY Com munications System Generic 3 Version 4 Imp lementation , 555-230-655, or DEFINITY Communications System Generic 3 V2/V3 Implementation , 555-230-653, for procedures describing how to administer DEFINITY system features to include Wideband Switching; most importantly see the section on administering ISDN-PRI. The following forms have to be administered for Wideband service: nAccess Endpoint nPRI En d point nTrunk Group (ISDN-PRI) nRouting Patterns Access Endpoint Access endpoint administration is required to support Wideband access endpoints (WAEs). WAEs are administered by defining the starting DS0 and the number of DS0s that comprise the WAE.
Feature Descriptions 3-1258Issue 3 March 1996 PRI Endpoint PRI endpoints are administered to define the number of DS0s to b e associated with an extension. The PRI endpoint’s numb er of DS0s (that is, the width) is limited by the type of ISDN-PRI interface but is always between 1 and 31. If the PRI endpoint is administered for a width narrower than the maximum numb er of B-channels supported by the line-side facility, then multiple PRI end points can be administered within that same line-side facility. The p arameters H0, H11, H12, and NXDS0 must be administered to identify the algorithm that the PRI en dpoint uses to provide Wideband service. If the NXDS0 algorithm is administered, then administration to identify it as floating or flexible (on the “ PRI-End point” form contiguous y/n)is also required. All combinations of these are allowed exc ept floating NXDS0 with H0. Other parameters can be administered for each PRI endpoint; they include: COR, COS, and whether Auto Restoration should apply to calls originating from the PRI endpoint. Trunk Groups Trunk group administration is required to specify the Wid e band service(s) that are to be supported by each trunk group. The parameters H0, H11, H12, and NXDS0 must be administered to identify the algorithm that the trunk group uses to provide Wideband service. If the NXDS0 algorithm is administered, then administration to identify it as floating or flexible (on the “Trunk Group” form contiguous y/n)is also required. All combinations of these are allowed exc ept floating NXDS0 with H0. In a ddition, the trunk search direction must be administered for the direction that a trunk group searches B-channels within its facilities (descend — ascend or ascend — desc end). Routing Patterns Routing parameter administration must be performed to specify the Wi deband Bearer Capability Class (BCC). This administration allows Generalized Route Selection (GRS) to allow Wideband traffic to choose specific trunk preferences, namely those trunks supporting Wideband network services. In no way does this administration imply that Wideband and narrowband traffic must be carried separately. In fact, any combination of narrowband BCC can be optioned with the Wi deband BCC. Customer Option Form Wideband switching must also be administered using the ‘‘Customer O ption’’ form. The other Wideband parameter a dministration is only performed if Wideband switching is administered for the switch.
Wideband Switching Issue 3 March 1996 3-1259 Hardware and Software Requirements Wideband software is optional. The TN464C (Universal DS1) circuit pack or later must be used on both the line-side and network side of the switch for any facility that carries Wideband traffic. The only other a dditional hardware/software required for Wi deband switching is that the PRI en d points must a dhere to the ISDN-PRI Wideband interface requirements and to PRI line-side requirements.
Feature Descriptions 3-1260Issue 3 March 1996 World Class Basic Rate Interface (BRI) Feature Availability Available with G3V4 a n d later releases Description World Class BRI (WCC BRI) provides an international BRI platform that offers multiple p rotocol options to meet specific country and application requirements. It provides access to Video Conferencing, Desktop Video Conferencing, Data Transmission, and other non-voice based applications that use BRI as a communication interface. Voice access is not supported for G3V4 though voice features are not blocked for WCC BRI terminals. WCC BRI devices must b e administered as the new typ e “wcbri.” WCC BRI users select a country protocol for each terminal that will use the feature. This selection determines both the c o deset modifications required to meet the national standards as well as the terminal initialization procedures if required. WCC BRI supports the following country protocols: nBellcore National ISDN-1 protocol in the Unite d States (TR268) nNational p rotocols in Australia (AUSTEL TS013, Telecom Australia TPH 1962), Japan (NTT BRI) a n d Singapore (FETEX 150 TIF 218) nETSI NET 3 protocol (ETS 300 102) for use in most of Europ e. WCC BRI supports multipoint (up to two devices per port) only for the Bellcore National ISDN-1 Country Protocol option. Considerations All d evices administered on the same port must b e of the same Country Protocol. All devices connected to the same DEFI NI TY s y st em m ust use the same companding mode as the system TDM bus. Interactions nASAI ASAI will continue to be a c cesse d via current ASAI a dministration. ASAI should not be accessed via “wcbri” typ e administration.
World Class Basic Rate Interface (BRI) Issue 3 March 1996 3-1261 Administration The system administrator must specify in the “End pt Init?” field on the “ Data Module” or “Station” forms whether the administered WCC BRI device sup ports Bellcore NI-1 endpoint initialization procedures. This field should be set to “y” for all Bellcore NI-1 devices, and the field should be set to “n” for all other WCC BRI devices (Australia, Japan, Singapore and ETSI). If the “Endpt Init” field is set to “y” then the administrator must also specify an Endpoint ID. In conjunction with the SPID, the En d pt ID allows for multipoint configuration conformance to Bellcore terminal initialization procedures. A Country Protocol also must be specified for each terminal. Hardware and Software Requirements WCC BRI requires a TN556B or later suffix BRI p ort circuit pack. A TN2198 two-wire BRI port circuit pack can be used in place of the TN556. In this case an NT1 is also required. WCC BRI supports terminals conforming to country protocols sp ecified under “Description”.
Feature Descriptions 3-1262Issue 3 March 1996 World Class Tone Detection Feature Availability This feature is available with G3i-Global and Generic V2 and later releases. Description World Class Tone Detection allows the DEFINITY switch to identify and handle different typ es of call progress tones, depending on the system administration. The tone detector and identification is used to display on Data Terminal Dialing and for deciding when to send digits on trunk calls through Abbreviated Dialing, ARS, AAR, and Data Terminal Dialing. n‘‘Tone detect mode 1’’ designates countries that use the same tone plan as Italy. n‘‘Tone detect mode 2’’ designates countries that use the same tone plan as Australia. n‘‘Tone detect mode 3’’ designates countries that use the same tone plan as the United Kingdom. n‘‘Tone detect mode 4’’ designates countries that use dial tones between 345 Hz and 625 Hz. n‘‘Tone detect mode 5’’ designates countries that use dial tones between 345 Hz and 1190 Hz. n“Tone detect mode 6” designates countries that use the same dial tone plan as the United States. nThe ‘‘level of tone detection precise’’ is used in countries whose tone plan matches the tone board’s tone detect mode. nThe ‘‘level of tone detection medium’’ is used in countries that, except for the continuous dial tone and discontinuous other tones, have tones with characteristics that do not match those expected by the tone detector board’s detect mode. nThe ‘‘level of tone detection broadband’’ is used in countries that have a discontinuous dial tone. Considerations When the administered Level of Tone Detection is ‘‘me dium’’ or ‘‘broadband,’’ multiple-line Data Terminal Dialing is disabled. Interactions The following features interact with the World Class Tone Detection feature.
World Class Tone Detection Issue 3 March 1996 3-1263 nData Call Setup Multiple-Line Data Terminal Dialing is supported ONLY if the administered Level of Tone Detection is ‘‘precise’’. nThe feedback displayed by Data Terminal Dialing in resp onse to received tones is affected by settings of World Class Tone Detection. nAbbreviated Dial, AAR, ARS, and Data Terminal Dialing can specify a wait for d ial tone in outpulsing digits over a trunk. The World Class Tone Detection feature should be configured to match the characteristics of the dial tone that will be detected. Administration Administration of World Class Tone Detection consists of two distinct parts: tone detection level and tone detection algorithm. System Aministrators a d dress how tone detection occurs and when it occurs in the outpulsing sequence. The following specific items are administered: n“ Level of Tone Detection” and “Off Premises Tone Detection Timeout” fields are ad ministered on the “Feature-Related System Parameters” form. n“Tone Detection Mode,” “ Dial Tone Validation Timer” (for Tone Detection mode 4 and 5 only), “ Outpulse Without Tone y/n,”and “Interdigit Pause” fields are administered on the “System-Parameters Country-Options” form. nThe “AAR/ARS Route Pattern” forms allows insertion of special characters “ + ” and “!” that indicate when to wait for a dial tone. nThe “ Ab breviated Dialing” form allows entry of ~w and ~ W that also indicate when to wait for a dial tone. Hardware and Software Requirements Tone Detection Modes 1, 2, and 3 are meaningful only if the system tone detectors are TN420Bs or greater. Modes 4 and 5, the Dial Tone Validation Timer, and the Interdigit Pause are meaningful only if the system tone detectors are TN744C-Tone Detector/Call Classifier, TN420C-Tone Detector, or TN2182-Tone Clock/Detector/Generator. Tone d etection for countries using the same tone plan as the United States is also available using an alternate tone detector. TN420B only recognizes Tone Detection Modes 1,2,and 3. TN420C, TN744C, and TN2182 recognize modes 1,2,3,4,5,and Dial Tone Validation and Interdigit Pause. TN2182 an d TN744C recognize mo de 6. TN748C provides precise tone detection for the United States tone plan.
Feature Descriptions 3-1264Issue 3 March 1996 World Class Tone Generation Feature Availability This feature is available with G3i-Global, all Generic V2, and later releases. Description Allows administrators to specify the base call progress tone set to be generate d by the system and to then customize the set by selecting different values for frequency and cadence for up to 6 individually administrable tones. Considerations If a particular tone (for examp le, conference tone) is not d efined for the administered base tone g eneration set (and not administered via the individual tone administration), silence will be used. Interactions Brief call waiting tones are o ptimal b ecause, while the tone is sounding, speech cannot be heard on the call. (For G3i-Global, G3V2, and later releases, the system administrator can administer system so that repeated tones are heard.) Administration The base tone generation set and individual tones, along with companding “Mode” , “Analog Ringing Cadence”, and “Digital Loss Plan” fields are administrable on Pages 1 through 7 of the “System-Parameters Country-O ptions” form by the system technician, the local installer and a remote installer. Hardware and Software Requirements Any DEFINITY system Tone Generation board can b e used. Some boards are capable of producing all North American and international tones. The TN768 g enerates tones only for North America. The TN780 can generate almost all the tones re quired for the world. The TN2182 can generate more tones than the TN780 and adds support for Hong Kong and France.