In this section:
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.
% set profiles services retryProfile <retryProfile name> attemptRecordGeneration <disabled | enabled> retrywithoutIdentity state <disabled | enabled> triggerActionRule <1-16> action <1-16> actionType <fallBackSrtpToRtp | fallBackToIPV4 | fallBackToIPV6> sipResponseCode <300-699> sipWarningCode <300-399>
The Retry Profile parameters are described in the following table.
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