Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23

Publisher

Cisco Systems, Inc., served by the Internet Archive

URL

https://web.archive.org/web/20250323135843id_/https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/12_5_1/cdrdef/cucm_b_cdr-admin-guide-1251.pdf

Published

2025-03-23

Updated

unknown

Accessed

2026-09-15

HTTP status

200

License

Cisco proprietary documentation, all rights reserved; no-redistribution; short excerpts and locators only

Claims citing this source

• A transferred call in Unified CM generates three call detail records: one for the original call, one for the consultation call, and one for the final transferred call. fact in context
• The complete 12.5(1) call detail records guide is retrievable and hashable by this programme through the Internet Archive as a 244-page PDF of original bytes, although cisco.com itself refuses direct retrieval from this network with HTTP 403 on every documentation path. field-pattern in context
• One row of the Cisco-specific cause code table is internally inconsistent: the bad extension row gives a decimal value of 83886207 against a hexadecimal value of 0x1500007F, which is 352321663, and the decimal given is instead the marker used by the not found row. disputed in context
• A blind transfer and a consultation transfer are distinguished in the record set by the consultation record's duration: it is 0 for a blind transfer and non-zero for a consultation transfer, while every other marker on the three records is identical. field-pattern in context
• The originating cause is populated when the originating party releases the call and the destination cause when the terminating party releases it or the call is rejected, and an unpopulated cause field shows zero, so which of the two fields is non-zero says which end ended the call. fact in context
• Unified CM publishes call termination cause codes beyond the Q.850 set, marked Cisco specific in the table, including 125 out of bandwidth, 126 call split, 131 Call Control Discovery PSTN failover and a run of IME failure codes through 148. fact in context
• The final transferred record's destination leg identifier equals the consultation record's destination leg identifier in all four worked transfer examples, which is the link between the consultation and the surviving call. field-pattern in context
• The final transferred record's originating leg identifier is one of the original record's two leg identifiers, and which of the two it is depends on which party transferred, so a join from the original to the final record has to allow either. field-pattern in context
• Grouping a transfer's records on the global call identifier collects two of the three: in all four worked examples the original and the final transferred record share one global call identifier and the consultation record carries a different one. field-pattern in context
• Unified CM stores IP addresses as unsigned integers and the call detail record file displays them as signed integers, and recovering the address means converting to a 32-bit hexadecimal value and reversing the byte order. fact in context
• The final transferred record is the one whose join-on-behalf-of field is set to 10 meaning transfer, and that field is 0 on the original and consultation records. field-pattern in context
• For on-net call legs Unified CM determines the cause code value and for off-net legs the far-end switch determines it, so a cause on an off-net leg is a foreign network's statement carried through rather than Unified CM's own diagnosis. fact in context
• The Cisco-specific cause code table lists SIP 503 service unavailable twice with two different codes whose Q.850 low words differ, 41 temporary failure and 63 service or option not available unspecified, so one SIP status maps to two Unified CM cause codes. fact in context
• Every one of the 42 SIP rows of the Cisco-specific cause code table has a Q.850 cause value in the low 16 bits of its code, and the guide states the construction for one row by writing the loop-detected code as 0x42000000 plus EXCHANGE_ROUTING_ERROR. field-pattern in context
• On both the original and the consultation record of a transfer, the originating and destination cause values are set to 393216 meaning split and the originating and destination termination-on-behalf-of fields are set to 10 meaning transfer. field-pattern in context
• The Cisco-specific code 393216, hexadecimal 0x60000, is call split and the table records that it was formerly 126; it is set when a call terminates during a transfer because it was split off and was not part of the final transferred call. fact in context
• The high byte of a SIP-derived Unified CM cause code is not a fixed function of the SIP status code: across the 41 distinct status codes in the table the difference between the status code and the marker takes 6 different values, so decoding the SIP status out of a cause code needs the table rather than arithmetic. field-pattern in context

Cite this source record

APA

WarmTransfer. (2025, March 23). Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23. WarmTransfer. https://warmtransfer.net/knowledge/sources/archive-cucm-cdr-admin-guide-1251-book

BibTeX

@misc{warmtransfer-archive-cucm-cdr-admin-guide-1251-book,
  title  = {Call Detail Records Administration Guide for Cisco Unified Communications Manager Release 12.5(1), complete book, Internet Archive capture of 2025-03-23},
  author = {{WarmTransfer}},
  year   = {2025},
  url    = {https://warmtransfer.net/knowledge/sources/archive-cucm-cdr-admin-guide-1251-book},
  note   = {Cisco Systems, Inc., served by the Internet Archive, accessed 2026-09-15}
}