Defining a Charging Server

To define a charging server:

From the navigation pane, select Charging Servers.
The content tree displays the Charging Servers group.
Select the Charging Servers group.
The Charging Server Administration page opens in the work area.
Click Create Charging Server.
The New Charging Server page opens.
(Required) Enter the Name for the charging server.
The name can only contain the characters A through Z, a through z, 0 through 9, period (.), hyphen (-), and underline (_).
Enter the Description/Location.
Free-form text that identifies the charging server within the network. Enter up to 250 characters.
(Required) Enter the Host Name.
The FQDN (fully qualified domain name assigned) to the charging server.
Enter the Port number on which the charging server is listening for messages.
If left blank, port 3868 is used.
Select the Transport protocol used to communicate with the charging server:
Available options include:
- tcp
  Transmission Control Protocol (used with TACACS+)
- udp
  User Datagram Protocol (used with RADIUS)
  
  Note: If you configure the Transport protocol as udp, you cannot configure the AAA Protocol as diameter.
- sctp
  Stream Control Transmission Protocol
Select the Authentication, Authorization, and Accounting (AAA) Protocol used to communicate with the charging server.
Available options include:
- diameter
  Diameter (see About Diameter Protocol for more information)
- radius
  RADIUS (see About RADIUS Protocol for more information)
  
  RADIUS uses UDP Transport protocol.
Select if transport Security is used to communicate with the charging server.
Click Save.

The charging server is displayed on the Charging Server Administration page.

After you define charging servers, you can select them as default charging servers when configuring an MPE device (see Configuring MPE Protocol Options) or use them in policy actions in the Policy Wizard (see Policy Wizard Reference).