For more information on ECS configurations, see the Enhanced Charging Services Administration Guide.
Step 2
Step 3
Step 4
Step 5 Save your configuration as described in the Verifying and Saving Your Configuration chapter.Important: Commands used in the configuration examples in this section provide base functionality to the extent that the most common or likely commands and/or keyword options are presented. In many cases, other optional commands and/or keyword options are available. Refer to the Command Line Interface Reference for complete information regarding all commands.
• [600-00-7526] Enhanced Charging Bundle 1 1k Sessions license
• [600-00-7574] Enhanced Charging Bundle 2 1k Sessions license—to enable and configure Diameter and DCCA functionality with ECSFor information on how to install licenses, see the Managing License Keys section of the Software Management Operations chapter in the Administration and Configuration Guide.
• Note that only Administrator and Config-administrator-level users can provision ECS functionality. Refer to the Configuring System Settings chapter of the System Administration and Configuration Guide for additional information on administrative user privileges.interface <interface_name>
• ACS must be enabled in Optimized mode, wherein ACS functionality is managed by SessMgrs. The require active-charging optimized-mode command enables ACS in Optimized mode.
• The require active-charging optimized-mode command must be a part of the boot configuration. If configured after booting, the configuration must be saved and the system rebooted for the change to take effect.active-charging service <service_name> [ -noconfirm ]The following is the sequence of configurations necessary to source data to the inPilot application:
Step 1
Step 3
Step 4
Step 7
Step 8 Save your configuration as described in the Verifying and Saving Your Configuration chapter.active-charging service <service_name>rulebase <rulebase_name>active-charging service <service_name>edr-format <edr_format_name> [ -noconfirm ]attribute <attribute> { [ format { MM/DD/YY-HH:MM:SS | MM/DD/YYYY-HH:MM:SS | YYYY/MM/DD-HH:MM:SS | YYYYMMDDHHMMSS | seconds } ] [ localtime ] | [ { ip | tcp } { bytes | pkts } { downlink | uplink } ] priority <priority> }event-label <event-label> priority <priority>
• For information on EDR format configuration and rule variables, refer to the EDR Format Configuration Mode Commands chapter of the Command Line Interface Reference.active-charging service ecs_svc1edr-format edr_flow_formatactive-charging service ecs_svc1edr-format edr_http_formatshow active-charging edr-format name <edr_format_name>active-charging service <service_name>ruledef <ruledef_name>
• The rule-application routing command specifies the ruledef type. If not specified, by default, the system configures the ruledef as a charging ruledef.
• For information on all the protocol types, expressions, operators, and conditions supported, refer to the Ruledef Configuration Mode Commands chapter of the Command Line Interface Reference.active-charging service <service_name>rulebase <rulebase_name> [ -noconfirm ]flow end-condition timeout normal-end-signaling session-end edr <edr_format_name>active-charging service ecs_svc1show active-charging rulebase name <rulebase_name>active-charging service <service_name>charging-action <charging_action_name> [ -noconfirm ]content-id <content_id>billing-action [ edr <edr_format> [ wait-until-flow-ends ] | egcdr | exclude-from-udrs | radius ] +flow idle-timeout <idle_timeout>show active-charging charging-action name <charging_action_name>context <context_name>file name <file_name> rotation volume <file_size_bytes> rotation time <file_complete_seconds> storage-limit <storage_limit_bytes> headers reset-indicator edr-format-name trap-on-file-delete compression gzip file-sequence-number rulebase-seq-numcdr [ push-interval <interval> | remove-file-after-transfer | transfer-mode { pull | push primary { encrypted-url <enc_url> | url <url> } [ secondary { encrypted-secondary-url <enc_sec_url> | url <sec_url> } ] } + | use-harddisk ]
• The <context_name> must be the context specified for accounting.
• The cdr use-harddisk command is only available on the ASR 5000 platform.
• The cdr use-harddisk command specifies storing files on the hard disk. The reporting server will download these files through the SPIO interface on the SMC and will delete the files after successful retrieval.
• The edr-format-name keyword must be configured to distinguish between different EDRs.cdr-push { all | local-filename <file_name> }
• <file_name> must be absolute path of the local file to push.
• The user must be configured in the local context with administrative privileges to download and delete EDRs from the hard disk. The ftp nocli options restrict access to FTP only.sample-interval <minutes>transfer-interval <minutes>file <file_number>header format <format_string>remotefile format <format_string>
• <ip_address> specifies the IP address of the inPilot server.
• For more information on commands for bulkstats configuration on the chassis, refer to the Bulk Statistics Configuration Mode Commands chapter in the Command Line Interface Reference Guide.
• For more information on variable descriptions for bulkstats schema configuration, refer to the Statistics and Counters Reference Guide or WEM Online Help.For viewing the sample bulkstats configuration file, refer to Sample Bulkstats Schema Configuration appendix.configure [File URL]Where, File URL is the path of bulkstats configuration file.
![]() |
Cisco Systems Inc. |
Tel: 408-526-4000 |
Fax: 408-527-0883 |