DO NOT SHARE THESE DOCS WITH CUSTOMERS!

This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.

In this section:

Related articles:

 

Use the Retry Profile to configure a trigger action rule to specify that when particular response code(s) (and optional warning code(s)) are received (the trigger), the SBC performs a fallback action (fallback SRTP to RTP, fallback to IPV4, fallback to IPV6, or retry without identity). The SBC then reattempts an INVITE with the updated Session Description Protocol (SDP) offer based on the action configured for the received error response and warning code. 

To View Retry Profiles

On the SBC main screen, navigate to All > Profiles > Services > Retry Profile. The Retry Profile window is displayed.

Retry Profile

To Create a Retry Profile

To create a new Retry profile:

  1. Click New Retry Profile on the Retry Profile List window. The Create New Retry Profile window is displayed.

    Create New Retry Profile


  2. Use the following table to configure an initial trigger action rule and action for the profile and then click Save.  You can add more trigger action rules and actions to the profile. Refer to Retry Profile - Trigger Action Rule and Trigger Action Rule - Action for information on adding additional triggers and actions.

Retry Profile - Parameter Description Table

ParameterLength/RangeDescription
Name1 to 23 charactersThe name of the Retry Profile. This profile is used to configure a trigger/action rule to specify that when a particular response code (and optional warning code) is received (the trigger).
StateN/A

The administrative state of this Retry Profile.

  • Disabled (default)
  • Enabled
Attempt Record GenerationN/A

Enable this option to log an ATTEMPT record to the accounting file after each retry attempt.

  • Disabled (default)
  • Enabled
Trigger Action Rule  
Rule Index1-16A numeric index for this trigger action rule. Each rule contains a configurable SIP response code, an optional warning code, and an action to take against the trigger.
SIP Response Code300-699List up to 16 SIP response codes that will trigger the specified action for this Trigger Action Rule.
SIP Warning Code300-399Optionally list up to 16 SIP warning codes received in the Warning header for this Trigger Action Rule.
Action   
Action Index1-16A numeric index for this action. Up to 16 actions can be assigned to a Trigger Action Rule. Each action contains an Action Type (below).
Action TypeN/A

The action(s) to take against the specified trigger.

  • fallBackSrtpToRtp
  • fallBackToIPV4
  • fallBackToIPV6
  • retryWithoutIdentity (retry the same route without using identity management)

Note: An Action can include more than one Action Type. However, it does not support both IPv4 and IPv6 addresses at the same time.

 To Edit a Retry Profile

To edit a Retry profile:

  1. Click the radio button next to the name of the Retry profile you want to edit. The Edit Selected Retry Profile window opens.

  2. Make the required changes and click Save.

 To Copy a Retry Profile

 To copy a Retry profile and make changes to the copy:

  1. Click the radio button next to the name of the Retry profile you want to copy.

  2. Click Copy Retry Profile. The Copy Selected Retry Profile window opens.
  3. Make the required changes and click Save.

 To Delete a Retry Profile 

To delete a Retry profile: 

  1. Click the radio button next to the name of the Retry profile you want to delete.
  2. Click the delete icon (X) at the end of the row.
  3. Confirm the deletion when prompted.