Specifies a numeric string of up to 25 characters that indicates the calling party number if the calling party is identified If the v4 address does not exist for the originating device, this field equals 0. Identifies the v4 IP address of the device that originates the call signaling.įor Cisco Unified IP Phones, this field specifies the v4 address of the phone.įor PSTN calls, this field specifies the v4 address of the H.323 gateway.įor intercluster calls, this field specifies the v4 address of the remote Unified Communications Manager.ĭefault - 0. Originates, or a zero value for FXS or FXO trunks.įor H.323 gateways, the span number remains unknown, and this field contains the call leg ID of the originator.įor calls that did not originate at a gateway, the value specifies zero.ĭefault - This field gets populated based on these rules. Identifies the server, or node within a cluster, to which the originator of the call is registered at the time that the callįor calls that originate at a gateway, this field indicates the B-channel number of the T1, PRI, or BRI trunk where the call Identifies the date and time when the user goes off the hook or the date and time that the H.323 SETUP message is receivedįor an incoming call. If the leg of a call persistsĪcross several subcalls and CDRs (as during a call transfer), this value remains constant. Be aware that this value is unique within a cluster. Identifies the originating leg of a call.
#Cisco cucm 8.6 data dictionary plus#
The value gets retrieved after a Unified Communications Manager restart, and the new globalCallId_callId value begins with this number plus x. Value gets written to disk periodically (for every x number of calls). Redesign ensures that the field retains a unique value, at least for a certain number of days. For Release 5.x and later releases, GlobalCallId Of CAR to correlate CMRs with CDRs and to correlate conference call CDRs. Because of this behavior, problems can occur with customer billing applications and the ability In Release 4.x and earlier releases, although the GlobalCallId field is time-based, the field gets reused underĬonditions of heavy traffic. Noteįor Unified Communications Manager Release 5.x and later releases, the value in the GlobalCallId CDR field survives over Unified Communications Manager restarts. The Global Call ID consists of two fields: globalCallID_callId globalCallID_callManagerId.Īll records that are associated with a standard call have the same Global Call ID in them. When Unified Communications Manager restarts, it checks the file for the current globalCallID_callId number and assigns the next 1000th number to the next GlobalCallID_callId. A value gets assigned for each call, successful or
Values get chosen sequentially when a call begins. The system allocates this identifier independently The Global Call ID comprises two fields: globalCallID_callId globalCallID_callManagerId.Īll records that are associated with a standard call have the same Global Call ID in them.ĭefault - Ensure that this field is populated.ĭesignates a unique call identity value that is assigned to each call. The following valid values apply:ĭefault - For CDRs, this field always remains 1.ĭesignates a unique Unified Communications Manager identity. Table describes all fields in the current CDRs in the order in which theyĭefines the type of record. This chapter defines all fields in the current CDRs in the order Cisco Call Detail Records Field Descriptions
0 kommentar(er)
