Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- Technology and Support
- DevNet
- DevNet Collaboration
- Collaboration Knowledge Base
- Duplicate CDR Records
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
744
Views
0
Helpful
0
Comments
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 01-25-2014 10:27 AM
This document was generated from CDN thread
Created by: Michael Nelson on 27-01-2013 11:28:19 PM
We are seeing duplicate or very similiar CDRs being returned by CTX and need to understand why we are seeing them.
The following is a example request and response from our production system. In this example, the records are not technically the same, but we are not sure how this same endpoint could have completed 2 calls in the the given time interval.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cdr="http://cdr.api.ctc.txbu.cisco.com">
<soapenv:Header/>
<soapenv:Body>
<cdr:getCallDetailRecords>
<!--Optional:-->
<endTimeFrom>2013-01-16T20:49:39+0000</endTimeFrom>
<!--Optional:-->
<endTimeTo>2013-01-16T20:49:40+0000</endTimeTo>
<!--Zero or more repetitions:-->
<callTypeList>DIRECTDIAL</callTypeList>
<!--Optional:-->
<companyScope>INTER_COMPANY</companyScope>
<!--Optional:-->
<firstIndex>0</firstIndex>
<!--Optional:-->
<numberOfRecords>100</numberOfRecords>
</cdr:getCallDetailRecords>
</soapenv:Body>
</soapenv:Envelope>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<ns2:getCallDetailRecordsResponse xmlns:ns2="http://cdr.api.ctc.txbu.cisco.com">
<return>
<callDetailRecords>
<callType>DIRECTDIAL</callType>
<callee>18668451379</callee>
<calleeAlternateIdentities>12.120.222.217</calleeAlternateIdentities>
<calleeRegion>Americas</calleeRegion>
<calleeServiceProvider>VERIZON</calleeServiceProvider>
<caller>14084249412</caller>
<callerAlternateIdentities>12.120.217.10</callerAlternateIdentities>
<callerOrganization>CTCS_Enterprise</callerOrganization>
<callerRegion>Americas</callerRegion>
<callerServiceProvider>ATT</callerServiceProvider>
<companyScope>INTER_COMPANY</companyScope>
<disconnectCauseCode>21</disconnectCauseCode>
<disconnectCauseStr>"Call rejected"</disconnectCauseStr>
<duration>0</duration>
<endTime>2013-01-16T20:49:39.000Z</endTime>
<guid>97AC5B3A988-7F2E4DD38FB-ACC3B88F55F-805707EAF4F</guid>
<id>8cf85e573c31cc83013c451fd3894a5f</id>
<serverIP>12.120.222.217</serverIP>
<serverName>lslilt04ctx</serverName>
<startTime>2013-01-16T20:49:39.000Z</startTime>
</callDetailRecords>
<callDetailRecords>
<callType>DIRECTDIAL</callType>
<callee>18668451379</callee>
<calleeAlternateIdentities>12.120.222.216</calleeAlternateIdentities>
<calleeRegion>Americas</calleeRegion>
<calleeServiceProvider>VERIZON</calleeServiceProvider>
<caller>14084249412</caller>
<callerAlternateIdentities>12.120.217.10</callerAlternateIdentities>
<callerOrganization>CTCS_Enterprise</callerOrganization>
<callerRegion>Americas</callerRegion>
<callerServiceProvider>ATT</callerServiceProvider>
<companyScope>INTER_COMPANY</companyScope>
<disconnectCauseCode>21</disconnectCauseCode>
<disconnectCauseStr>"Call rejected"</disconnectCauseStr>
<duration>0</duration>
<endTime>2013-01-16T20:49:39.000Z</endTime>
<guid>FB199E3423B-93EE7ED4DFD-434C47B0B36-BDDECD39640</guid>
<id>8cf85e573c31cc83013c451fd58d4a78</id>
<serverIP>12.120.222.216</serverIP>
<serverName>lslilt03ctx</serverName>
<startTime>2013-01-16T20:49:39.000Z</startTime>
</callDetailRecords>
<totalNumberFound>2</totalNumberFound>
</return>
</ns2:getCallDetailRecordsResponse>
</env:Body>
</env:Envelope>
Here is another example and in this case the records are identical except for the ID.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cdr="http://cdr.api.ctc.txbu.cisco.com">
<soapenv:Header/>
<soapenv:Body>
<cdr:getCallDetailRecords>
<!--Optional:-->
<endTimeFrom>2013-01-16T01:49:34+0000</endTimeFrom>
<!--Optional:-->
<endTimeTo>2013-01-16T01:49:35+0000</endTimeTo>
<!--Zero or more repetitions:-->
<callTypeList>DIRECTDIAL</callTypeList>
<!--Optional:-->
<companyScope>INTRA_COMPANY</companyScope>
<!--Optional:-->
<firstIndex>0</firstIndex>
<!--Optional:-->
<numberOfRecords>100</numberOfRecords>
</cdr:getCallDetailRecords>
</soapenv:Body>
</soapenv:Envelope>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<ns2:getCallDetailRecordsResponse xmlns:ns2="http://cdr.api.ctc.txbu.cisco.com">
<return>
<callDetailRecords>
<callType>DIRECTDIAL</callType>
<callee>11111111471</callee>
<calleeOrganization>BP Corporation</calleeOrganization>
<calleeRegion>Americas</calleeRegion>
<calleeServiceProvider>ATT</calleeServiceProvider>
<caller>11111111430</caller>
<callerOrganization>BP Corporation</callerOrganization>
<callerRegion>Americas</callerRegion>
<callerServiceProvider>ATT</callerServiceProvider>
<companyScope>INTRA_COMPANY</companyScope>
<disconnectCauseCode>16</disconnectCauseCode>
<disconnectCauseStr>Normal call clearing</disconnectCauseStr>
<duration>2798</duration>
<endTime>2013-01-16T01:49:34.000Z</endTime>
<guid>219983</guid>
<id>8cf85e573c31cc83013c4131b8c53e99</id>
<serverIP>12.120.217.140</serverIP>
<serverName>sjc02-att-cm-1</serverName>
<startTime>2013-01-16T01:02:56.000Z</startTime>
</callDetailRecords>
<callDetailRecords>
<callType>DIRECTDIAL</callType>
<callee>11111111471</callee>
<calleeOrganization>BP Corporation</calleeOrganization>
<calleeRegion>Americas</calleeRegion>
<calleeServiceProvider>ATT</calleeServiceProvider>
<caller>11111111430</caller>
<callerOrganization>BP Corporation</callerOrganization>
<callerRegion>Americas</callerRegion>
<callerServiceProvider>ATT</callerServiceProvider>
<companyScope>INTRA_COMPANY</companyScope>
<disconnectCauseCode>16</disconnectCauseCode>
<disconnectCauseStr>Normal call clearing</disconnectCauseStr>
<duration>2798</duration>
<endTime>2013-01-16T01:49:34.000Z</endTime>
<guid>219983</guid>
<id>8cf85e573c31cc83013c4168a7417eb9</id>
<serverIP>12.120.217.140</serverIP>
<serverName>sjc02-att-cm-1</serverName>
<startTime>2013-01-16T01:02:56.000Z</startTime>
</callDetailRecords>
<totalNumberFound>2</totalNumberFound>
</return>
</ns2:getCallDetailRecordsResponse>
</env:Body>
</env:Envelope>
Subject: RE: Duplicate CDR Records
Replied by: John Yontz on 28-01-2013 06:53:12 PM
Hi Mike,
I consulted with the development team on each of the two duplicate CDR cases you mentioned, and here is our analysis:
INTER_COMPANY DIRECTDIAL
Our theory is that somehow the call may be directed to both engine servers separately. To further anaylze:
1. Can you send logs from both the engine and admin servers. We want logs from when this happened so if logs from the record you show below have already rolled-over, can you send us logs from a more recent occurrence of this. You can send us logs through the usual channel.
2. Is this observed only for the case where call was rejected with reason 21?
3. Is this observed only for calls from/to a specific endpoint.
4. Is this observed only for calls from/to a particular route.
INTRA_COMPANY DIRECTDIAL
These CDRs are imported from the CUCM as part of a background periodic task. Our theory is that the CUCM is sending duplicates and CTX is not detecting them as duplicates, perhaps because of some subtle difference in the data received from CUCM that is not exposed in the CDR API. Please send us admin server logs for around that time period, and we can further diagnose.
Thanks
- John
Subject: RE: Duplicate CDR Records
Replied by: Michael Nelson on 29-01-2013 11:23:30 AM
Regarding INTER_COMPANY DIRECTDIAL and questions 2 and 3:
2. All of the examples we have seen appear to all have been rejected with reason 21.
3. They are not all from the same endpoint.
Created by: Michael Nelson on 27-01-2013 11:28:19 PM
We are seeing duplicate or very similiar CDRs being returned by CTX and need to understand why we are seeing them.
The following is a example request and response from our production system. In this example, the records are not technically the same, but we are not sure how this same endpoint could have completed 2 calls in the the given time interval.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cdr="http://cdr.api.ctc.txbu.cisco.com">
<soapenv:Header/>
<soapenv:Body>
<cdr:getCallDetailRecords>
<!--Optional:-->
<endTimeFrom>2013-01-16T20:49:39+0000</endTimeFrom>
<!--Optional:-->
<endTimeTo>2013-01-16T20:49:40+0000</endTimeTo>
<!--Zero or more repetitions:-->
<callTypeList>DIRECTDIAL</callTypeList>
<!--Optional:-->
<companyScope>INTER_COMPANY</companyScope>
<!--Optional:-->
<firstIndex>0</firstIndex>
<!--Optional:-->
<numberOfRecords>100</numberOfRecords>
</cdr:getCallDetailRecords>
</soapenv:Body>
</soapenv:Envelope>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<ns2:getCallDetailRecordsResponse xmlns:ns2="http://cdr.api.ctc.txbu.cisco.com">
<return>
<callDetailRecords>
<callType>DIRECTDIAL</callType>
<callee>18668451379</callee>
<calleeAlternateIdentities>12.120.222.217</calleeAlternateIdentities>
<calleeRegion>Americas</calleeRegion>
<calleeServiceProvider>VERIZON</calleeServiceProvider>
<caller>14084249412</caller>
<callerAlternateIdentities>12.120.217.10</callerAlternateIdentities>
<callerOrganization>CTCS_Enterprise</callerOrganization>
<callerRegion>Americas</callerRegion>
<callerServiceProvider>ATT</callerServiceProvider>
<companyScope>INTER_COMPANY</companyScope>
<disconnectCauseCode>21</disconnectCauseCode>
<disconnectCauseStr>"Call rejected"</disconnectCauseStr>
<duration>0</duration>
<endTime>2013-01-16T20:49:39.000Z</endTime>
<guid>97AC5B3A988-7F2E4DD38FB-ACC3B88F55F-805707EAF4F</guid>
<id>8cf85e573c31cc83013c451fd3894a5f</id>
<serverIP>12.120.222.217</serverIP>
<serverName>lslilt04ctx</serverName>
<startTime>2013-01-16T20:49:39.000Z</startTime>
</callDetailRecords>
<callDetailRecords>
<callType>DIRECTDIAL</callType>
<callee>18668451379</callee>
<calleeAlternateIdentities>12.120.222.216</calleeAlternateIdentities>
<calleeRegion>Americas</calleeRegion>
<calleeServiceProvider>VERIZON</calleeServiceProvider>
<caller>14084249412</caller>
<callerAlternateIdentities>12.120.217.10</callerAlternateIdentities>
<callerOrganization>CTCS_Enterprise</callerOrganization>
<callerRegion>Americas</callerRegion>
<callerServiceProvider>ATT</callerServiceProvider>
<companyScope>INTER_COMPANY</companyScope>
<disconnectCauseCode>21</disconnectCauseCode>
<disconnectCauseStr>"Call rejected"</disconnectCauseStr>
<duration>0</duration>
<endTime>2013-01-16T20:49:39.000Z</endTime>
<guid>FB199E3423B-93EE7ED4DFD-434C47B0B36-BDDECD39640</guid>
<id>8cf85e573c31cc83013c451fd58d4a78</id>
<serverIP>12.120.222.216</serverIP>
<serverName>lslilt03ctx</serverName>
<startTime>2013-01-16T20:49:39.000Z</startTime>
</callDetailRecords>
<totalNumberFound>2</totalNumberFound>
</return>
</ns2:getCallDetailRecordsResponse>
</env:Body>
</env:Envelope>
Here is another example and in this case the records are identical except for the ID.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cdr="http://cdr.api.ctc.txbu.cisco.com">
<soapenv:Header/>
<soapenv:Body>
<cdr:getCallDetailRecords>
<!--Optional:-->
<endTimeFrom>2013-01-16T01:49:34+0000</endTimeFrom>
<!--Optional:-->
<endTimeTo>2013-01-16T01:49:35+0000</endTimeTo>
<!--Zero or more repetitions:-->
<callTypeList>DIRECTDIAL</callTypeList>
<!--Optional:-->
<companyScope>INTRA_COMPANY</companyScope>
<!--Optional:-->
<firstIndex>0</firstIndex>
<!--Optional:-->
<numberOfRecords>100</numberOfRecords>
</cdr:getCallDetailRecords>
</soapenv:Body>
</soapenv:Envelope>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<ns2:getCallDetailRecordsResponse xmlns:ns2="http://cdr.api.ctc.txbu.cisco.com">
<return>
<callDetailRecords>
<callType>DIRECTDIAL</callType>
<callee>11111111471</callee>
<calleeOrganization>BP Corporation</calleeOrganization>
<calleeRegion>Americas</calleeRegion>
<calleeServiceProvider>ATT</calleeServiceProvider>
<caller>11111111430</caller>
<callerOrganization>BP Corporation</callerOrganization>
<callerRegion>Americas</callerRegion>
<callerServiceProvider>ATT</callerServiceProvider>
<companyScope>INTRA_COMPANY</companyScope>
<disconnectCauseCode>16</disconnectCauseCode>
<disconnectCauseStr>Normal call clearing</disconnectCauseStr>
<duration>2798</duration>
<endTime>2013-01-16T01:49:34.000Z</endTime>
<guid>219983</guid>
<id>8cf85e573c31cc83013c4131b8c53e99</id>
<serverIP>12.120.217.140</serverIP>
<serverName>sjc02-att-cm-1</serverName>
<startTime>2013-01-16T01:02:56.000Z</startTime>
</callDetailRecords>
<callDetailRecords>
<callType>DIRECTDIAL</callType>
<callee>11111111471</callee>
<calleeOrganization>BP Corporation</calleeOrganization>
<calleeRegion>Americas</calleeRegion>
<calleeServiceProvider>ATT</calleeServiceProvider>
<caller>11111111430</caller>
<callerOrganization>BP Corporation</callerOrganization>
<callerRegion>Americas</callerRegion>
<callerServiceProvider>ATT</callerServiceProvider>
<companyScope>INTRA_COMPANY</companyScope>
<disconnectCauseCode>16</disconnectCauseCode>
<disconnectCauseStr>Normal call clearing</disconnectCauseStr>
<duration>2798</duration>
<endTime>2013-01-16T01:49:34.000Z</endTime>
<guid>219983</guid>
<id>8cf85e573c31cc83013c4168a7417eb9</id>
<serverIP>12.120.217.140</serverIP>
<serverName>sjc02-att-cm-1</serverName>
<startTime>2013-01-16T01:02:56.000Z</startTime>
</callDetailRecords>
<totalNumberFound>2</totalNumberFound>
</return>
</ns2:getCallDetailRecordsResponse>
</env:Body>
</env:Envelope>
Subject: RE: Duplicate CDR Records
Replied by: John Yontz on 28-01-2013 06:53:12 PM
Hi Mike,
I consulted with the development team on each of the two duplicate CDR cases you mentioned, and here is our analysis:
INTER_COMPANY DIRECTDIAL
Our theory is that somehow the call may be directed to both engine servers separately. To further anaylze:
1. Can you send logs from both the engine and admin servers. We want logs from when this happened so if logs from the record you show below have already rolled-over, can you send us logs from a more recent occurrence of this. You can send us logs through the usual channel.
2. Is this observed only for the case where call was rejected with reason 21?
3. Is this observed only for calls from/to a specific endpoint.
4. Is this observed only for calls from/to a particular route.
INTRA_COMPANY DIRECTDIAL
These CDRs are imported from the CUCM as part of a background periodic task. Our theory is that the CUCM is sending duplicates and CTX is not detecting them as duplicates, perhaps because of some subtle difference in the data received from CUCM that is not exposed in the CDR API. Please send us admin server logs for around that time period, and we can further diagnose.
Thanks
- John
Subject: RE: Duplicate CDR Records
Replied by: Michael Nelson on 29-01-2013 11:23:30 AM
Regarding INTER_COMPANY DIRECTDIAL and questions 2 and 3:
2. All of the examples we have seen appear to all have been rejected with reason 21.
3. They are not all from the same endpoint.
Labels:
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
Customers Also Viewed These Support Documents