Versions Compared

Old Version 4

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c880e94aad0181077fa2530009, userName='null'}
JIRAIDAUTHSBX-124027
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c880e94aad0181077fa2530009, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c880e94aad0181077fa2530009, userName='null'}



Panel

In this section:

Table of Contents
maxLevel3



Info
iconfalse

Related articles:

Children Display



Excerpt


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

To View and Edit Redirect

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

DEFAULT_H323

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

Figure 1: Trunk Provisioning - Egress Ip Attributes H323 Redirect

Image Modified

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

372pxDEFAULT_SIP

On the Redirect window, choose the Ip Signaling Profile as DEFAULT_SIP to view the Redirect the Redirect for SIP Trunk Group.Figure 2: Trunk Provisioning - Egress Ip Attributes SIP Redirect

The following fields are displayed:


Table 1: Egress Ip Attributes SIP Redirect ParametersParameters Table:

Parameter

Description

Mode

Use this object to control SIP redirection:

  • Accept Redirection – (default) Multiple redirection are allowed.
  • Allow Single Redirect Attempt – Only a single Redirect is allowed per route. Additional Redirects cause crankback to be performed.
  • Reject Redirection – If a Redirect is received, crank back is performed.
  • Stop Hunt – Prevent Prevent call attempts on subsequent trunk groups if 3xx is received following an Invite Invite and the SBC fails to establish the call with all the contacts from 3xx.
Info
titleNote

You must use "Stop Hunt" in conjunction with the egress IP Signaling Profile control "forceRequeryForRedirectionForce Requery For Redirection".

Available_since
TypeAvailable Since
Release10.1.4

Contact Handling

Select one of the following to control processing of contacts received in SIP Redirects:

  • Merge Received Contacts – Contacts received in Redirects are ordered by q-value and inserted at the head of the list of untried contacts.
  • Purge Existing Contacts – Contacts received in Redirects are ordered by q-value and replace untried contacts.


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