In this section:

Related articles:

Use the Retry Profile to configure a trigger/action rule to specify that when a particular error response code (and optional warning code) is received (the trigger), the SBC performs a fallback action (fallback SRTP to RTP, fallback to IPV4 or fallback to IPV6). 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. 

Command Syntax

% set profiles services retryProfile <retryProfile name>
	attemptRecordGeneration <disabled | enabled>
	state <disabled | enabled>
	triggerActionRule <1-16>
		action <1-16>
			actionType <fallBackSrtpToRtp | fallBackToIPV4 | fallBackToIPV6>
		sipResponseCode <300-699>
		sipWarningCode <300-399>

Command Parameters

The Retry Profile parameters are described in the following table.

Retry Profile Parameters

ParameterLength/RangeDescription
retryProfile
1 to 23 characters<retryProfile name> – The name of the Retry Profile. This profile is used to configure a trigger/action rule to specify that when a particular error response code (and optional warning code) is received (the trigger).
attemptRecordGeneration N/A

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

  • disabled (default)
  • enabled

state

N/A

The administrative state of this Retry Profile.

  • disabled (default)
  • enabled

triggerActionRule

1-16

<rule index> – The 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.

  • action <action index> – The action index for this triggerActionRule. Up to 16 actions can be assigned to a triggerActionRule. Each action contains an actionType as specified below.
    • actionType  – The action(s) to take against the specified trigger.
      • fallBackSrtpToRtp
      • fallBackToIPV4
      • fallBackToIPV6
  • sipResponseCode (300-699) – List up to 16 SIP response codes that will trigger the specified action for this triggerActionRule.
  • sipWarningCode (300-399) – Optionally list up to 16 SIP warning codes received in the Warning header for this triggerActionRule.

NOTE: An action can include more than one actionType. However, it does not support both IPv4 and IPv6 addresses at the same time.

Command Examples

set profiles services retryProfile rp1 triggerActionRule 2 sipResponseCode 301 sipWarningCode 333 action 2 actionType fallBackSrtpToRtp
commit
set profiles services retryProfile rp1 attemptRecordGeneration enabled state enabled
commit
 
show profiles services retryProfile
retryProfile rp1 {
    state                   enabled;
    attemptRecordGeneration enabled;
    triggerActionRule 2 {
        sipResponseCode [ 301 ];
        sipWarningCode  [ 333 ];
        action 2 {
            actionType fallBackSrtpToRtp;
        }
    }
}
> show table profiles services retryProfile
                       RULE    SIP RESPONSE     SIP WARNING       ACTION                                    ATTEMPT RECORD   
NAME        STATE      INDEX   CODE             CODE              INDEX   ACTION TYPE                       GENERATION
---------------------------------------------------------------------------------------------------------------------------
retryProf1  disabled   1       [ 401 488 489 ]  [ 301 302 308 ]   1       fallBackSrtpToRtp,fallBackToIPV6  enabled
                                                                  2       fallBackToIPV4                    enabled
                       2       [ 501 503 504 ]  -                 1       fallBackSrtpToRtp                 enabled
                                                                  2       fallBackToIPV6                    disabled