McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 263

↗ View in doc context
page
263
source
cucm/v15/reporting-billing-admin-guide/reporting-billing-admin-guide.md
chunk_id
cucm::v15::reporting-billing-admin-guide::reporting-billing-admin-guide::267

C H A P T E R 10 CDR Examples This chapter provides examples of the call detail records (CDRs) that the Unified Communications ManagerRelease system generates for all call types. You can use this information for post-processing activities such as generating billing records and network analysis. When you install your system, the system enables CDRs by default. You can enable or disable CDRs at any time that the system is in operation. You do not need to restart Unified Communications Manager for the change to take effect. The system responds to all changes within a few seconds. • AAC Calls, on page 252 • Abandoned Calls, on page 254 • Ad Hoc Conference Linking, on page 256 • Agent Greeting Calls, on page 266 • Barge, on page 267 • Call Monitoring, on page 269 • Call Park, on page 271 • Call Pickup, on page 273 • Call Recording, on page 275 • Call Secured Status, on page 277 • Calling Party Normalization, on page 278 • Calls with Busy or Bad Destinations, on page 279 • cBarge, on page 280 • Client Matter Code (CMC), on page 282 • Conference Calls, on page 283 • Conference Now Calls, on page 287 • Conference Drop Any Party, on page 289 • DTMF Method, on page 290 • End-to-End Call Trace, on page 291 • Forced Authorization Code (FAC), on page 295 • Forwarded or Redirected Calls, on page 297 • Hunt List Support, on page 299 • H.239, on page 302 • iLBC Calls, on page 303 • Intercompany Media Engine, on page 306 • Immediate Divert (to Voice-Messaging System), on page 310 • IMS Application Server, on page 312 Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs 251

Image 1 from page 263