/mcpValues Field Names 1 globalCallID_callId 100 origLegCallIdentifier 101 destLegIdentifier 2001 callingPartyNumber +12145551212 originalCalledPartyNumber +12145551212 finalCalledPartyNumber +12145551212 lastRedirectDn 16 origCause_Value 0 dest_CauseValue 60 duration 2145551212 outpulsedCalledPartyNumber Logical Partitioning Calls The Telecom Regulatory Authority of India (TRAI) requires that voice traffic over an enterprise data network and a PSTN network remain separate. The logical partitioning feature ensures that a single system can be used to support both types of calls as long as calls that pass through a PSTN gateway can never directly connect to a VoIP phone or VoIP PSTN gateway in another geographic location (geolocation). CDR Example for Call Termination Cause Code CCM_SIP_424_BAD_LOCATION_INFO A SIP trunk call goes from cluster1 to cluster2. The call contains a geolocation header but does not include an XML location. Cluster2 releases the call with a SIP Status code of 424 (bad location information [decimal value = 419430421]). Cause code CCM_SIP_424_BAD_LOCATION_INFO gets logged for calls that are cleared because of bad location information by the SIP trunk on the Unified Communications Manager. The remote endpoint on the SIP trunk can send the 424 SIP Status code for cases when the geolocation information is bad for some of the following reasons: • The geolocation header indicates the inclusion of PIDF-LO, but the message body does not carry this information. • The geolocation header has a CID header that refers to a URL, but no corresponding Content-IP header with the same URL exists. • The geolocation header has a URL other than the CID header (that is a SIP, or SIPS URL). Refer to additional CDR examples for more information on other call termination cause codes. Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs 321 CDR Records Logical Partitioning Calls