In this section:

This section specifies the Redirect Flag parameters for Egress Ip Attributes.

To View and Edit Redirect - Flags

On SBC main screen, go to Configuration > System Provisioning > Category: Trunk Provisioning > Ip Signaling Profile > Egress Ip Attributes > Redirect > Flags. The Flags window is displayed.

DEFAULT_H323

On the Flags window, choose the Ip Signaling Profile as DEFAULT_H323 to view the Flags parameters for H323 Trunk Group.

Figure 1: Trunk Provisioning - Egress Ip Attributes H323 Redirect-Flags

There are no Flags parameters for DEFAULT_H323 type of Egress Ip Attributes.

DEFAULT_SIP

On the Flags window, choose the Ip Signaling Profile as DEFAULT_SIP to view the Flags for SIP Trunk Group.

Figure 2: Trunk Provisioning - Egress Ip Attributes SIP Redirect-Flags

The following fields are displayed:

Table 1: Egress Ip Attributes SIP Redirect-Flags Parameters

Parameter

Description

Skip Crankback Profile And Always Crankback

Enable this flag to force any 4xx–6xx SIP response code to cause crankback so the next potential contact or 3xx response is tried. If disabled, only the response codes specified in default SBC crankback profile cause the call to crank back.

The options are:  

  • enable
  • disable (default)
Force Requery For Redirection

(applies to Invite requests only) Use flag to re-query ERE with contact information received in a 3xx response for redirection-type scenarios.

The options are:

  • enable
  • disable (default)
Relay Unused Contact Params

When enabled, Contact parameters received in 3xx responses that are not consumed/processed locally by the SBC (see NOTE below) can now be passed through to the R-URI of subsequent INVITE request.

The options are:

  • enable
  • disable (default) 

The following are the parameters that are consumed/processed locally by the SBC and excluded from this relay mechanism:

  • dtg
  • tgrp
  • trunk-context
  • cic
  • npdi
  • npi
  • rn
  • bgid
  • bgt
  • user
  • phone-context


Honor Embedded Headers in3xx

Enable flag to allow processing embedded headers in 3xx Contact headers for the trunk group that received the 3xx.

The options are:

  • enable
  • disable (default)
  • Ensure "Force Re-query for Redirection" flag associated with the specified IPSP is enabled when using this feature.
  • Embedded PAI Header is present in the redirected INVITE only if “Include Embedded PAI” flag is enabled in this IPSP.
  • A 3xx with embedded headers over GW-GW is rejected with '403 Forbidden' message when "Honor embedded headers in 3xx" enabled.

Make the required changes and click Save at the right hand bottom of the panel to save the changes made.


  • No labels