Page 410 of 1814 Call Detail Recording Enhancement553-2901-301 Standard 9.00 January 2002Multi-party Operations“Recovery of Misoperation on Call Transfer” interacts with the CDREnhancement feature. The following table explains the interaction betweenthis feature and the CDR Enhancement feature.Busy VerificationThe following table explains the interaction between Busy Verification andthe CDR Enhancement feature.Feature packagingFor stand-alone and network non-PPM environments, the following softwarepackage is required:• Call Detail Recording Enhancement (CDRX) package 259, which isdependent on:— Call Detail Recording (CDR) package 4;— Call Detail Recording Teletype Terminal (CTY) package 5; and— New Format Call Detail Recording (FCDR) package 234.CDR Enhancement – Multi-party Operations InteractionIn this scenario, A calls an outgoing CO and transfers to B. B transfers to Cand C does not answer. After a pre-defined number of rings, the call isrecalled back to B. If B does not answer after a pre-defined number of rings,the call is dropped. All sets are 500 sets.An “S” record is generated against A at transfer completion time. An “X”record is generated against B at transfer completion time. An “E” record isgenerated against C when C does not answer after a pre-defined number ofrings and the call is recalled back to B. An “N” record is generated against“B” when the call is dropped.CDR Enhancement – Busy Verification InteractionIn this example, A calls an outgoing CO trunk, and transfers to B. B is talkingto the outgoing CO. The attendant performs a Busy Verification on B.An “S” record is generated against A at transfer completion time. An “X”record is generated against B when the attendant presses the Busy Verifykey and dials B’s DN. An “E” record is generated against B, if the attendantdisconnects before B. An “E” record is generated against the conference DNif B disconnects before the attendant. An “E” record is generated against theconference DN if the far end trunk disconnects first.
