Configure Diameter Re-Auth-Request Behavior
Perform this task to enable Diameter Diameter Re-Auth-Request (RAR) capabilities and to configure the request behavior.
About this task
You can change the default RAR settings by running the create_config.py script. By default, an initial RAR is sent 3600 seconds after a session is created, additional RARs are sent 60 seconds after an initial RAR, and the maximum number of RAR requests to send without receiving a response is 1. The default amount of time to wait after the last RAR retry was sent before removing an inactive Gy, Gx, or Sy session is 172800 seconds.
For information about Diameter RAR capabilities, see MATRIXX Diameter Integration. For information about the global configuration questions, see the discussion about global system configuration in MATRIXX Configuration.
Procedure
-
Log into the server as a user with
sudo permissions and change to user
mtx
.For example:ssh server_ip_address
sudo su - mtx
-
Go to the ${MTX_CUSTOM_DIR} directory:
cd_custom_dir
- Open the create_config.info file with a text editor.
-
To enable RAR
functionality for the following situations, change the appropriate answer to y
(yes).
- Send a RAR for a specific context on expiration
of QVT for that context (with
Rating-Group
andService-Identifier
): Global:Do you want a RAR to be sent after quota expires (y/n)? - Answer y to the following questions to RAR to the session (without
Rating-Group
andService-Identifier
):- Global:Session:Charging:Notify:When an offer is purchased for a subscriber (y/n)?
- Global:Session:Charging:Notify:When an offer is purchased for a group (y/n)?
- Global:Session:Charging:Notify:When an offer is cancelled for a subscriber(y/n)?
- Global:Session:Charging:Notify:When an offer is cancelled for a group (y/n)?
- Global:Session:Charging:Notify:When an offer is purchased by a subscriber and granted to a tier group (y/n)?
- Global:Session:Charging:Notify:When the status of a subscriber or a device is changed (y/n)?
- Global:Session:Charging:Notify:When the status of a group is changed (y/n)?
-
Global:Should Gy sessions be terminated when Sy SNA indicates failure (y/n)?
Note: ASR messages are sent for all Ro charging sessions (voice and data).
- Send a RAR for a specific context on expiration
of QVT for that context (with
-
To customize the RAR
behavior that is enabled, change the answers to the following questions.
- Diameter: Do you want to allow routing by the realm name if a preferred connection is not available (y/n)?
- Global:Session:Charging:Notify:How long (in seconds) to wait after the QVT expires?
- Global:Session:Charging:Notify:How long (in seconds) to wait after the most recent activity before the first attempt?
- Global:Session:Charging:Notify:How many attempts?
- Global:Session:Charging:Notify:How long (in seconds) to wait after the most recent activity before the first attempt?
- Save and close the file.
What to do next
If the engine is not in production and is not online, follow the procedure for configuring the primary engine.