McDewey

Original Call CDR Field Names 10010 lastRedirectDn 0 origCause_Value 16 dest_CauseValue 162 origCalledPartyRedirectReason 162 lastRedirectRedirectReason 19 origCalledPartyRedirectOnBehalfOf 19 lastRedirectRedirectOnBehalfOf 0 origTerminationOnBehalfOf 12 destTerminationOnBehalfOf 19 joinOnBehalfOf 60 duration Redirecting Number Transformation When the redirecting number transformation feature is enabled, original called and last redirecting number are transformed before it sends out in outgoing setup message. Redirecting Number Transformation Example 1. CCM1 - Phone A [ 180000 ] , Phone B [ 180001 ] , Phone C [ 180002 ] 2. SIP trunk is configured on CCM1 pointing to SIP Gateway 3. Phone B has external mask set as +9111XXXX 4. Phone C has external mask set as +9122XXXX On SIP trunk, redirecting party CSS is configured which has the partitions P1 and there is a Calling Party transformation pattern associated with P1. This pattern has external phone number mask enabled. Scenario A - calls Phone B ---- CFA - Phone C CFA --- SIP Trunk --- SIP Gateway B - Original Called Party, C - Last Redirecting Party There are 2 diversion headers corresponding to original and last redirecting party that is sent out in outgoing SIP INVITE message and these diversion headers have transformed redirecting number, that is, +91110001 and +91220002. These values are also stored in CDR records. Transformed original called number will be stored in outpulsedOriginalCalledPartyNumber and transformed last redirecting number will be stored in outpulsedLastRedirectingNumber. Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs 348 CDR Records Redirecting Number Transformation