Resolved—Known Issue with Response Group Service CDR Queries

Communications Server 2007 R2

Microsoft Office Communications Server 2007 R2 introduced the new Response Group Service and as a result added a few new queries to the Call Detail Record (CDR) reporting tool that is included with the Microsoft Office Communications Server 2007 R2 Resource Kit Tools. This article addresses a known issue with the Response Group Service CDR queries and shows before and after examples of the queries.

Author: Scott Stubberfield

Publication date: February 2010

Product version: Office Communications Server 2007 R2

In Communications Server 2007 R2 we introduced the new Response Group Service and as a result added a few new queries to the CDR reporting tool that is included with the Microsoft Office Communications Server 2007 R2 Resource Kit Tools. This article addresses a known issue with the Response Group Service CDR queries and shows before and after examples of the queries.

If a call is placed to the Response Group from a Communicator client, the call is listed correctly in the report. However, if the call is placed from a PSTN endpoint (via Mediation Server), the call is not listed. It turns out that the issue relates to the underlying SQL query that was included with the Archiving and CDR query tool.

Download the .xml file located at http://go.microsoft.com/fwlink/?LinkId=183643, and this should resolve the issue with the underlying queries. To take advantage of these queries, replace the downloaded .xml file with the default .xml file that is included in the \\Reskit\ArchivingCDRReporter directory.

If you had the Archiving and CDR report tool open before you replaced the .xml file, exit and restart the tool. After you restart the tool and review the CDR queries for the Response Group Service reports, you will see calls that were received from a PSTN endpoint that were previously excluded from the reports.

List of calls received by the Response Group Service

Figure 1 shows the details of all of the calls that have been received by the Response Group Service. Figure 2 shows an example of the report that now correctly lists all calls that were received, including those that were received via a Mediation Server.

Figure 1. Before: List of calls received by the Response Group Service

06d2e427-6af3-43e8-90ab-0a468b1e3f60

Figure 2. After: List of Calls received by the Response Group Service

e7833910-0a3d-4303-a504-78355d448c89

Total number of calls received by the Response Group Service

Figure 3 shows you a summary of all of the calls that have been received by the Response Group Service. Figure 4 shows an example of the report that now correctly lists all calls that were received, including those that were received via a Mediation Server. This updated report also shows some optimizing in how the summary data is presented.

Figure 3. Before: Total number of calls received by the Response Group Service

81dc73db-084b-4446-8f2a-b4ab7bb67a28

Figure 4. After: Total number of calls received by the Response Group Service

175d33ab-0183-4949-8229-581a66de7c89

List of calls successfully accepted by agents in the Response Group Service

Figure 5 shows you the details of all the calls that have been accepted by agents in the Response Group Service. Figure 6 shows an example of the report that now correctly lists all calls that were accepted, including those that were received via a Mediation Server.

Figure 5. Before: List of calls successfully accepted by agents in the Response Group Service

a59db2dd-5207-4bc0-aaad-6e2cfc66641f

Figure 6. After: List of calls successfully accepted by agents in the Response Group Service

9cd5e401-c2e8-49e5-b740-c5d08695bc85

Total number of calls successfully accepted by agents in the Response Group Service

Figure 7 shows you a summary of all of the calls that have been accepted by agents in the Response Group Service. Figure 8 shows an example of the report that now correctly lists all calls that were accepted, including those that were received via a Mediation Server. This report also shows some optimizing in how the summary data is presented.

Figure 7. Before: Total number of calls successfully accepted by agents in the Response Group Service

2c25db2b-3ede-4593-8e4d-44ad6bdd96db

Figure 8. After: Total number of calls successfully accepted by agents in the Response Group Service

efd8c0f9-ab66-4c0c-8bee-5ab332933da7

List of calls successfully transferred by the Response Group Service on queue time out or queue overflow

Figure 9 shows you a list of all of the calls that have been transferred by the Response Group Service on queue time out or on queue overflow. As you can see in Figure 9, the before version of this query incorrectly identified the transferred calls. Figure 10 shows an example of the report that now correctly lists only the calls that were transferred.

Figure 9. Before: List of calls successfully transferred by the Response Group Service on queue time out or queue overflow

6a30bdf5-280d-4ac3-8aec-daa21523b13c

Figure 10. After: List of calls successfully transferred by the Response Group Service on queue time out or queue overflow

0e28693d-da7b-4756-b2fe-7567917484d1

Total number of calls successfully transferred by the Response Group Service on queue time out or queue overflow

Figure 11 shows you a summary of all of the calls that have been transferred by the Response Group service on queue time out or on queue overflow. As you can see in Figure 11, the before version of this query incorrectly identified the transferred calls. Figure 12 shows an example of the report that now correctly lists only the calls that were transferred.

Figure 11. Before: Total number of calls successfully transferred by the Response Group Service on queue time out or queue overflow

2c75b3a4-6005-4751-b672-c6fccd468b37

Figure 12. After: Total number of calls successfully transferred by the Response Group Service on queue time out or queue overflow

881c698f-cd7e-43ee-b983-b9bb6ec3f835

Please keep in mind that this updated SQL query is provided ‘as-is’ similar to the entire Resource Kit application itself.

* Special thanks to Stéphane Cavin, Kangmo Kim, and Sam Gao for providing the updated xml file and for reviewing my write up of the issue.

To learn more, check out the following articles:

 
Show: