Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 2

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: addressed B. Scoggins content.

Add_workflow_for_techpubs
AUTH1
JIRAIDAUTHSBX-57145
REV5
REV6
REV3
REV1

The SBC is enhanced to use the Max-Forwards header value received from the end-user.

 

The default value for rfc7332ValidateMaxForwards is disable. If rfc7332ValidateMaxForwards is enabled, the SBC will use the Max-Forwards header value received from the end-user, and decrements this header value by 1 before forwarding it to the other end-user. If the value received from the end-user is 0 or 1, the SBC will discard that request with an error response of "483 - Too Many Hops."

 

This feature will be supported only if rfc7332ValidateMaxForwards is enabled through a CLI command on the Ingress side.

 

The RFC 7332 flag option is defined below.

 

Command Syntax

 

To set the flag:

Code Block
languagenone
% set addressContext <addressContext -name> zone <zone -name>  sipTrunkGroup < TG- name> signaling rfc7332ValidateMaxForwards <Enable<disable |Disable> enable>


Command Parameters

Caption
0Table
1RFC Flags Parameters
3RFC Flags Parameters
Length/
ParameterRangeDefaultDescriptionMandatory/
Optional
rfc7332ValidateMaxForwards1disable

Flag to enable or disable Max-Forwards header support.

  • disable (default) – disables
Flag to disable
  • Max-Forwards header support.
  • enable – When enabled, the SBC uses the Max-Forwards header value received from the end-user, and decrements this header value by 1 before forwarding it to the other end-user.
O
 

 

Configuration Example

Code Block
% set addressContext default zone ZONE_IAD  sipTrunkGroup TG_IAD signaling rfc7332ValidateMaxForwards enable

Pagebreak