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+.
Call Detail Recording (CDR) Issue 3 March 1996 3-377 The new CDR outp ut formats are selecte d using System Parameters. PPM uses pulses transmitted over the trunk line from the serving CO at periodic intervals during the course of the outgoing call to determine call charges. NOTE: PPM is only provided by the central office in some countries; in p articular, not in the United States. Each pulse has an intrinsic value; at the end of the call, the sum of the pulses represents the charges for the call. The more exp ensive the call, the faster the sending rate of the pulses becomes. The TN465B Loop Start CO Trunk circuit pack is capable of detecting 16 kHz PPM p ulses. The pulses can occur at a maximum of once every 1.4 seconds during the call or, if the CO accumulates the total PPM c ount, they can occur up to three to five seconds after the call is dropped. In order to ensure that d elayed PPM data is received, the Outgoing Glare Guard Timer on the trunk group should b e a djusted accordingly. The PPM count may be output to Int-Direct, Int_Process, and Int_ISDN. PPM pulse detection is applicable for outgoing calls on CO, DIOD, The “ PPM” field on the ‘Trunk Group’ form should be set to ‘‘y’’ (yes) to enable the PPM detection and reporting functions. nResource Flag (one digit) (24-Word Records Only) NOTE: The field name for Customized CDR Record s for G3rV1, G3V2, and later releases is ‘‘res_flag.’’ This is a four b it field that exists in the 24-word and customized record for G3xV2 only. Two bits of the field are used presently. The rest of the bits are reserved for future use. This field also ap plies to intraswitch c alls. The new bits are defined as follows: — The ’’Circuit or Packet Switched Call’’ bit is used to identify whether the call was circuit switched or packet switched. A ‘‘0’’ value in this bit indicates that the call used circ uit switching. A ‘‘1’’ value in this bit indicates that the call used packet switching. — The ‘‘Conversion Devices Used’’ bit indicates whether or not the call used a conversion device. A ‘‘0’’ value in this b it indicates that the call did not use a conversion device. A ‘‘1’’ value in this bit indicates that call used a conversion device. — G3V1 has a 4-bit “Resource Flag” field of which only 1 bit is used to indicate whether or not a conversion device was used on the call (0 means no conversion device was used, and 1 means a conversion device was used. — For both releases the bits are interpreted as follows: Intra-switch CDR will not output this field.
Feature Descriptions 3-378Issue 3 March 1996 nSpace (one to forty characters) NOTE: The field name for Customized CDR for G3rV1, G3V2, and later releases is ‘‘space.’’ The ASCII b lank character is used to separate other CDR fields or to blank fill unused record locations. This field defaults to one character length in customized record s but can be incremented in size up to forty. The ASCII carriage return character followed by a line feed is used to terminate customized records. nTSC Flag (one digit) NOTE: The field name for G3rV1 and G3V2 Customized CDR Records is ‘‘tsc_flag.’’ This field distinguishes CDR record s pertaining to TSCs. When not equal to zero, this field will indicate the status of the TSC. Table 3-46 presents the TSC Flag encoding. Intra-switch CDR will not output this field. Table 3-46. Encoding for CDR TSC Flag Encoding Meaning 0 Circuit-switched call without TSC requests. 1 Reserved for future use. 2 Reserved for future use. 3 Reserved for future use. 4 Call Associated TSC requested, accepted in response to SETUP , n o congestion control (applicable to originating node). Call Associated TSC received and accepted via SETUP , n o congestion control (applicable to terminating node). 5 Call Associated TSC received and accepted via SETUP, c o ngestion c ontrol (applicable to terminating node). 6 Call Associated TSC requested, accepted after SETUP, n o congestion control (ap plicable to originating node). Call Associated TSC received and accepted after SETUP, no congestion control (ap p licable to terminating node). 7 Call Associated TSC received and accepted after SETUP, congestion control (ap plicable to terminating node). 8 Call Associated TSC requested, rejected (rejection came from outside the local switch).
Call Detail Recording (CDR) Issue 3 March 1996 3-379 nVector Directory Number (five digits) NOTE: The field name for G3rV1 and G3V2 Customized CDR Records is ‘‘vdn.’’ This field is only available on the customized record format. The CDR record will output the VDN extension number. CDR Output Devices The following adjuncts are available: nCAS Plus nCost Allocator nCDRP nCDRU-NCR nCDRU-S nCDRU-SE A system can have two output formats. A standard 232C interface is provided by the system’s processor circuit pack. This allows for direct connection of the CDR outp ut device to the system. If this 9 Call Associated TSC requested, rejected (rejection came from the local switch, that is, lack of resourc e). A Non Call Associated TSC received, accepted, no congestion control (applicable to terminating node). Non Call Associated TSC received, accepted, no congestion control (ap p licable to terminating node). B Non Call Associated TSC requested, accepted, congestion control (applicable to originating node). Non Call Associated TSC received, accepted, congestion control (applicable to terminating node). C Non Call Associated TSC requested, rejected (rejection came from outside the local switch). D Non Call Associated TSC requested, rejected (rejection came from the local switch, that is, lack of resource). E Reserve d for future use. F Reserve d for future use. Table 3-46. Encoding for CDR TSC Flag — Continued Encoding Meaning
Feature Descriptions 3-380Issue 3 March 1996 port is not used, additional interface equipment is required as described in the Hardware and Software Requirements p art of this feature d esc ription. The RS232 interface is only available with G3s/vs/i. The G3r must use a dditional eq uipment. The system can support two CDR output devices. One of these devices can use the direct EIA-232C connection; the other device will require the a dditional interface equipment. When a system has two CDR output formats, one format is administered as the primary CDR output format; the other format is a dministered as the secondary CDR out put format. The secondary output format is typically used for a local storage format (CDRU) to provide CDR data to NCOSS for assessing network performance or helping to find network problems. The primary and secondary ports work independently. Each p ort will work even if the link to the other port is down. If a link is down for more than a minute, some data may b e lost. However, the most recent 300 (G3i), or 1,900 (G3r) records are stored for the primary port even when a loss of records occurs. When the link comes back up, these records are output on a first-in, first-out basis. The following information applies to the p ort used for the Secondary CDR output device: nData going to the secondary port should be the same as that going to the primary port. However, CDR records sent to the secondary port can only be in the 18-Word CDRU format, Unformatted, INT-Direct and INT-Process. NOTE: If the CDR buffer is full, G3r provides a call record handling option to select which of the following occurs: — Calls are blocked with a reorder tone — Calls overwrites records — Calls are routed to an attendant as non-CDR calls G3i and G3vs/G3s overwrite the CDR records. nIf the system exp eriences problems in sending records to the primary CDR Output Device, the system discontinues sending records to the secondary port for two minutes. The secondary port should be run at the highest possible speed in ord er to prevent loss of information on the port. nIf more than 300 (G3i/G3vsV1/G3sV1), 300 (G3iV2), or 1,900 (G3r) have not been sent to the primary CDR p ort, the secondary port is busied out for two minutes. This makes system resources available to send data to the primary CDR port b efore the data is lost. The system will continue to busy out the secondary port for two-minute intervals until less than 200 records (1800 for G3r) remain to b e sent to the primary p ort. The system can store up to 300 (G3i), or 1,900 (G3r) CDR record s which are sent to the output devices.
Call Detail Recording (CDR) Issue 3 March 1996 3-381 A 1,200 bits/second rate may only be used over the c a ble for the TELE SE ER CDR u n i t, 9 4A LS U , o r printer, if the system line size is less than 1,000. If the system line size is greater than 1,000, a rate of at least 2,400 must be used with the 18-word CDR records. If the system line size is greater than 600, a rate of at least 2,400 must be used with the 24-word CDR record s. The time stamp on calls recorded by CDR is applied at the end of the call. Remove # from CDR Records One method of removing the # sign from CDR records is to eliminate the ARS/AAR analysis patterns requiring the inter-digit timeout to determine the pattern. For examp le, to remove the # from local d irectory assistance calls (411), delete the ARS analysis for the single digit “4” in the string. Until the inter-digit timeout occurs, the software d oes not know which pattern to match. By eliminating entry 1 (in this case), the inter-d i git timeout is no longer required for 411. Considerations Capacities The system c an store up to 300 (G3i), or 1,900 (G3r) CDR records for the primary port, which (when the link is down) are sent to the output devices when the link comes back up. Account Code Recording With forced entry or o ptional entry of the A ccount Code feature (FEAC), a CDR record is generated for a particular account number. The CDR access code (for example, 6) and the account number is dialed before the ARS, AAR, or TAC and called number are dialed. If the attendant is extending a call to a voice terminal, an account code can be dialed before the extension number is dialed. Voice terminal users cannot dial an account code when transferring a call to another voice terminal, unless they have console permissions. However, a voice terminal user transferring a call to a trunk can d ial an a c count code before d ialing the ARS or TAC. CDR Device Baud Rate Limits If the system line size is g reater than 1,000, the CDR d evice must sup p ort a b aud rate of at least 2,400 b ps when using 18-word CDR records. If the system line size is greater than 600, the CDR d evice must support a baud rate of at least 2,400 bps when using 24-word CDR records.
Feature Descriptions 3-382Issue 3 March 1996 Interactions The following interaction discussions assume CDR is activated. nAbbreviated Dialing When Abbreviated Dialing or a Facility Busy Indication button is used to make or complete a call, all d i gits outp ulsed (up to a maximum of 15) will a p pear on the CDR record. nAnswer Detection G3 provides Answer Detection using the TN744 Call Classifier circuit pack. This feature is assigned as an option per system and requires sufficient (8-port) TN744 circuit packs. The circ uit packs must b e engineered to handle the expected outgoing calls from end of outpulsing until either answer is detecte d b y the TN744 or actual Answer Supervision is received from the trunk. The time the answer is detected by the TN744 is used as the start of a call to record call duration in the CDR record. nAttendant Console If an attendant-assisted call involves an outg oing trunk, the primary extension of the voice terminal user requesting attendant service is recorded as the calling number, even if the attendant dialed the outside number. Condition Code 1 indicates the call was assisted by the attendant. If the attendant allows through dialing, the primary extension of the voice terminal user who dialed the number is recorded as the calling party. Condition Code 1 indicates that a trunk access code was extended by the attendant. Condition Code 7 indicates that a feature access code was extend e d by the attendant. On attendant-assisted calls that require an account c o de, the account code must b e entered before the trunk access code. If the attendant is redirecting an incoming call to a voice terminal, the attendant may dial an a c count code before dialing the extension number. It is not possible to option the attendant for intraswitch calls. -Intraswitch records are produced for an intraswitch optioned extension calling the attendant or for a call from the attendant to an intraswitch optioned extension. In the case of an attendant-assisted call involving an intraswitch extension, the calling number recorded is the extension of the party who called the attendant, and the dialed number recorded is the extension that the attendant extended the call to. The record will have a Condition Code 0. nAUDIX For remote AUDIX over DCS, if station A on node 1 forwards its calls to AUDIX on node 2, the CDR record is produced on each switch. The record from node 1 contains A as the dialed number. The record from
Call Detail Recording (CDR) Issue 3 March 1996 3-383 node 2 contains AUDIX as the dialed number. If the c alling number is on a different switch within the DCS network, or the call comes in over ISDN, the actual calling number is recorded in the “Calling Number” field, and the TAC of the trunk bringing the call into the local switch is recorded in the “Incoming Trunk Ac c ess Code” field of 24-word record s. If the forward ed call is an incoming call, then, as in all cases (other than vectoring) in which an incoming call is forwarded, transferred, or conferenced using an outgoing trunk, two separate CDR records are produced, one for incoming and one for outgoing trunk usage. The outgoing trunk usage record lists AUDIX as the Calling Number. nAuthorization Codes Authorization codes are recorded on CDR records if account codes do not exceed five digits for non-ISDN and ISDN LSU formats and four digits for Enhanced LSU formats. On the 59-character CDR International Processing and International Direct records, the authorization code is never recorded. nAAR and ARS CDR record s the following information for Automatic Route Selection (AR S): — Fact that an ARS call was made — Calling extension number — FRL of the calling extension — Called number — Type of trunk group used for the ARS call — Time of call completion — Call d uration (how long the parties talked) — IXC code, if any If CDR is suppressed for the trunk group actually used on an ARS call, an CDR record is not generated; otherwise, Condition Code 7 applies. The ARS access code is record ed in the “Access Code Dialed” field and the trunk access code for the trunk group actually used is recorded in the “Access Code Used” field. If an AAR call is placed to a busy trunk group and CDR is suppressed for that trunk group, the user hears reorder tone and the CDR output shows an ineffective call attempt. If an ARS call is an attendant assisted call (a voice terminal user calls the attendant, the attendant dials the ARS access code, and then releases the call), the CDR record shows the call with a Condition Code of 7 (ARS call) instead of a Condition Code of 1 (attendant assisted call). This occurs because CDR is not notified until after the trunk is seized and, in this case, the trunk is not seized until the voice terminal user dials the number.
Feature Descriptions 3-384Issue 3 March 1996 nAutomatic Callback When the Automatic Callback feature is used for an intraswitch call, no CDR record will be g enerated for the first call attempt or the ringbac k. However, if the caller or extension being called is optioned for intraswitch CDR, a record of the actual call will be outp ut provided the call is answered and completed. nACA ACA calls will generate intraswitch CDR if the terminating extension is monitored by CDR. The originating extension for ACA calls cannot be administered for intraswitch monitoring. nAutomatic Call Distribution (ACD) Either the hunt group extension number or individual hunt group member extension number (depending on administration) is record ed as the called number. nAutomatic Wakeup No CDR intraswitch records are generate d for wakeup calls. nBridged Call Appearance CDR does not record any information on the party who bridges onto a call. Instead, the number that was called appears in the “Dialed Number” field of the CDR record. The duration of the call is recorded when the last party drops off the call. This also app lies for intraswitch calls. If the calling user originates a call using a bridged appearance, CDR records the calling number of the bridged appearance extension and not the extension numb er of the original, calling station. nCall-By-Call Service Selection When a su ccessful call is made on a Call-By-Call Service Selection trunk, the network specific facility used on the call is translated into an INS number and recorded in the “ INS” field of the CDR record. If a Call-By-Call Service Selection call is unsuccessful because of an administered trunk usage allocation plan, the INS number is recorded in the “INS” field of the report with a condition code of ‘‘E.’’ nCall Coverage When an incoming or intraswitch call is answered by a covering voice terminal, the extension numb er dialed by the originating party is recorded as the dialed number. nCall Forwarding All Calls When a call is forwarded to another voice terminal, the extension number dialed by the calling party is recorded as the dialed number. There will b e only one record generated for a forwarded intraswitch call. In this record , the dialed number will be the same as the extension d ialed by the originating party.
Call Detail Recording (CDR) Issue 3 March 1996 3-385 If a DSI or ISDN-PRI trunk calls a station and the station is forwarded to another T1 trunk, the outgoing record will show the station being forward ed to the second T1 trunk rather than the first T1 trunk being forward ed to the second T1 trunk. nCall Park When a voice terminal user parks an incoming or intraswitch call, that user’s extension is record ed as the dialed number in the CDR record. Call duration in CDR reflects the entire time the incoming trunk is busy (incoming) or until the call ends (intraswitch). nCall Pickup When an incoming or intraswitch call is answered by another voice terminal user in the pickup group, the extension number dialed by the calling party is recorded as the dialed numb er. nCall Vectoring The ‘CDR-related System Parameters’ form can be administered so that the VDN extension will be used in place of the Hunt Group or Member extension. If administered to d o so, this overrides the ‘‘Call to Hunt Group - Record’’ option of CDR for incoming Call Vectoring calls. For incoming calls to a VDN, the duration of the call is recorded from the time answer supervision is returned. — If answer supervision is returned by the vector (via an announcement, collect, disconnect, or wait with music command), and the call never goes to another extension, then the VDN extension is record ed as the called number in the CDR record. — If the call terminates to a hunt group, then the VDN, hunt group, or agent extension is record ed as the called numb er as per the administration discussed above. — If the call terminates to a trunk, then the following two CDR records will be generated: 1. An incoming record with the VDN as the called number and the duration from the time answer supervision was provided to the incoming trunk. 2. An outgoing record containing the incoming trunk information as the calling number and the dialed d i gits and the outgoing trunk information as the called number. Outgoing vector calls generate ordinary outgoing CDR records with the originating extension as the calling numb er. If “member extensions” is administered on the ‘CDR System Parameters’ form and the call successfully completes to a station via the “route-to” command, the CDR record will show an incoming call to that station. No Ineffective Call Attempt records will be generated for Call Vectoring route to commands that are unsuccessful.
Feature Descriptions 3-386Issue 3 March 1996 If a vector interacts with an extension or group that has Call Forwarding All Calls active, normal Call Forwarding/CDR interactions a p ply. Some calls may originally look like intraswitch calls, b ut result in trunk calls (for example, a call from a station administered for intraswitch CDR to a VDN, which ends up an outgoing call on an outgoing trunk). Such calls will not generate intraswitch CDR records; the CDR record will have a condition code A - outgoing. nCall Waiting Termination Call d uration timing starts when the voice terminal answers an incoming call. nCAS If a CAS attendant extends a call for a user, and CDR is not assigned to the RLT trunk group, the user’s extension is recorded as the originator of the call. If the RLT trunk group does have CDR administered, the RLT trunk is recorded. If a CAS attendant answers a call but does not extend the call, no CDR records are ma de. nCO Trunks All incoming and outgoing calls on a CO trunk group will be recorded, if CDR is assigned and incoming calls are recorded. nConference For the purpose of CDR record ing, a call is considered a conference call if it contains at least one trunk which is eligible for CDR recording plus two or more non-attendant parties, or if it contains at least one party optioned for intraswitch CDR. Condition Code C applies to each CDR record made for a conference call. For a conference call, a separate CDR record is produced for each outgoing/incoming trunk serving the conference call. For the outgoing portion of a conference call involving multiple voice terminals, the voice terminal which requested outside dial tone to bring an outside party into the conference is recorded as the calling party. For the outg oing/incoming portion of a conference c all, the call d uration in CDR reflects the entire time the trunk was on the conference call. Trunk-to-trunk transfer calls are treated like conference calls for CDR purposes. A separate CDR record is produced for each trunk used in a trunk-to-trunk transfer. If the originator of the conference call is optioned for intraswitch CDR, each time the originator d ials a non-trunk party, a new CDR record is started. For examp le, Station A is o ptioned for intraswitch CDR and calls Station B. Station A conferences in Station C. Station A drops from the call. Station B or C drops from the call. Two CDR records are output with Condition Code C: one for the A to B call and one for the A to C call.