Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring Transport Profiles

    A transport profile provides information for transporting the Charging Data Records (CDRs) from the charging data function (CDF) to the charging gateways or to local persistent storage. A transport profile can be associated with different charging profiles. You can define up to eight transport profiles.

    To configure transport profiles:

    1. Specify the name of the transport profile that you are configuring for the gateway called MBG1.
      [edit unified-edge gateways ggsn-pgw MBG1 charging]user@host# edit transport-profiles profile-name
    2. Specify a description for the profile.
      [edit unified-edge gateways ggsn-pgw MBG1 charging transport-profiles profile-name]user@host# set description string
    3. Configure offline charging in the transport profile.
      [edit unified-edge gateways ggsn-pgw MBG1 charging transport-profiles profile-name]user@host# edit offline charging-gateways
    4. Configure the order in which the charging gateways are selected. The charging gateway must be defined as a GTP Prime peer. The highest-priority peer is selected first as the active charging gateway. When the active charging gateway goes down, the next higher-priority peer is selected. If all the charging gateways are down and you have configured local persistent storage, then the CDRs are stored on the Routing Engine.
      [edit unified-edge gateways ggsn-pgw MBG1 charging transport-profiles transport-profile1 offline charging-gateways]user@host# set peer-order peer charging-gateway-peer-name
    5. Specify the time the CDF must wait before switching back to a higher-priority peer from a lower-priority peer that has become the active charging gateway.
      [edit unified-edge gateways ggsn-pgw MBG1 charging transport-profiles transport-profile1 offline charging-gateways]user@host# set switch-back-time seconds
    6. Specify that the persistent storage order is local (on the Routing Engine). You must configure the persistent storage order before CDRs can be stored locally on the Routing Engine.
      [edit unified-edge gateways ggsn-pgw MBG1 charging transport-profiles transport-profile1 offline charging-gateways]user@host# set persistent-storage-order local-storage
    7. Configure the CDR format version. The charging format implemented in the 3GPP Release 8 specifications (r8) is the default format version.
      [edit unified-edge gateways ggsn-pgw MBG1 charging transport-profiles transport-profile1 offline charging-gateways]user@host# set cdr-release (r99 | r7 | r8)
    8. Specify the number of CDRs in one DRT message.
      [edit unified-edge gateways ggsn-pgw MBG1 charging transport-profiles transport-profile1 offline charging-gateways]user@host# set cdr-aggregation-limit value
    9. Configure the maximum transmission unit (MTU) of the DRT message.
      [edit unified-edge gateways ggsn-pgw MBG1 charging transport-profiles transport-profile1 offline charging-gateways]user@host# set mtu value

    Published: 2011-11-16