This document describes some schedule and session establishment issues
for the Historical Report client with respect to the Cisco Customer Response
Solutions (CRS) server that generates historical reports.
Readers of this document should have knowledge of these topics:
The information in this document is based on these software and
The information in this document was created from the devices in a
specific lab environment. All of the devices used in this document started with
a cleared (default) configuration. If your network is live, make sure that you
understand the potential impact of any command.
For more information on document conventions, refer to the
Technical Tips Conventions.
As CRS runs, it stores call activity data in databases on the CRS
server or the Historical Reports Database Server, if one is set up. The Cisco
Historical Reports client is used to create historical reports based on this
To schedule a historical report means the Cisco CRS Historical Reports
client needs to be instructed to automatically generate the report in the
When you check the schedule for historical reports, watch these common
Complete this procedure to resolve these issues:
For daily reports, verify these possible issues:
Check the Daily radio button in the Occurs section,
indicated by the A arrow in Figure
Check the Every radio button and enter
1 on the blank field next to Every in the
Occurs section, as shown by the B arrow in
Check the No End Date radio button in the
Range of recurrence section, as indicated by the C arrow in
If a specific report only prints once, then quits, the most likely
reason is the No End Date radio button is not selected. This
radio button means the report will print indefinitely.
Figure 3: Schedule CRS Historical Reports
When scheduled historical reports fail to run, there are two common
HTTP proxy server
TCP port 6293 is blocked
The most common of the two issues is the HTTP proxy server. The HTTP
proxy server is not supported by the CRS server. The Historical Report client
must communicate with the CRS server directly. In such an environment, the CRS
server has to be excluded from the HTTP proxy server. The procedure
Start the Internet Explorer browser.
Select Tools from the menu
Click Internet Options ....
Select the Connections tab, indicated by the A arrow
in Figure 4.
Click LAN Settings, indicated by the B arrow in
Figure 4: Internet Options
Select the Use a proxy server for your
Click Advanced..., as shown in
Figure 5: Local Area Network (LAN)
Enter the IP address or the fully qualified domain name of the CRS
server in the Do not use proxy server for addresses beginning
with field in the Exceptions section, as shown in
Figure 6: Proxy Setting
The TCP port number used between the CRS server and the Historical
Report client can be either TCP port 80 or 6293, this depends on the report
generation method. If historical reports are generated through the Historical
Report client, the TCP port 80 on the CRS server has to be open and available
by default. However, when scheduled historical reports run, the TCP port 6293
has to be open and available. If a firewall exists between the CRS server and
the Historical Report client, a conduit for TCP port 80 or 6293 on the firewall
must be established.
You can test the TCP port availability, run
telnet. To test the TCP port 6293, complete this
Select Start >
Run telnet < IP address or Fully
Qualified Domain Name of the CRS server > 6293 to
check the TCP port 6293 availability, as shown by the A arrow in
Figure 7: Checking the Availability of TCP Port
If telnet fails with Connect
failed, as shown by B in Figure 7,
identify the reason and correct it, see
the Trace Route Utility.