Cisco Cisco Expressway 维护手册
Call Detail Records (CDRs)
The system can capture CDRs if you enable the service (which is off by default), and can publish them as syslog
messages if you are using remote logging.
messages if you are using remote logging.
If you select Service only the system keeps the CDRs for 7 days, and these CDRs can only be read via the
Representational State Transfer (REST) API to the Expressway. If you select Service and logging, the local data is
exposed in the Event Log, and the CDRs are also sent as INFO messages to your syslog host.
Representational State Transfer (REST) API to the Expressway. If you select Service and logging, the local data is
exposed in the Event Log, and the CDRs are also sent as INFO messages to your syslog host.
How to Configure CDRs
To configure CDRs on Expressway:
1.
Go to Maintenance > Logging.
2.
In the Logging Options section, set the Call Detail Records field following the below guide.
CDR Mode
Description
Off
CDRs are not logged locally (default).
Service Only
CDRs are stored locally for 7 days and then deleted. The records are not
accessible via the web GUI.
accessible via the web GUI.
Services and Logging
CDRs are stored locally for 7 days and then deleted. The records are accessible
from the local event log and the external syslog server if external logging has
been enabled.
from the local event log and the external syslog server if external logging has
been enabled.
APIs to access CDRs
You can use the following secure REST APIs to gather the information you require.
■
get_all_records (returns all records up to seven days old).
■
get_records_for_interval (returns records from during the time specified).
■
get_records_for_filter (filters results using any combination).
■
get_all_csv_records (returns all records up to seven days old in csv format).
To access your desired API use the following URL: https://<Expressway_IP>/api/external/callusage/<API>
Examples
■
http://<Expressway_IP>/callusage/get_all_records
■
http://<Expressway_IP>/callusage/get_records_for_interval?fromtime=<fromtime>&totime=<to_time> (for
example http://10.50.157.80:8000/callusage/get_records_for_interval?fromtime=2014-05-
09%2000:00:00&totime=2014-05-10%2000:00:00)
example http://10.50.157.80:8000/callusage/get_records_for_interval?fromtime=2014-05-
09%2000:00:00&totime=2014-05-10%2000:00:00)
Input Parameters
Parameter Description
fromtime
The start time from which the CDR records are required. It must be entered in the format 'YYYY-
MM-DD HH:MI:SS’ (mandatory parameter).
MM-DD HH:MI:SS’ (mandatory parameter).
totime
The end time from which the CDR records are required. It must be entered in the format 'YYYY-
MM-DD HH:MI:SS’ (mandatory parameter).
MM-DD HH:MI:SS’ (mandatory parameter).
■
http://<Expressway_IP>/callusage/get_records_for_interval?fromtime=<fromtime>&totime=<to_time> (for
example http://10.50.157.80:8000/callusage/get_records_for_interval?fromtime=2014-05-
09%2000:00:00&totime=2014-05-10%2000:00:00)
example http://10.50.157.80:8000/callusage/get_records_for_interval?fromtime=2014-05-
09%2000:00:00&totime=2014-05-10%2000:00:00)
7
Cisco Expressway Serviceability Guide Maintain and Operate Guide