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.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
JIRAIDAUTHSBX-94503
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c86fbb89c0016ff0804098000f, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ceaa0c34, userName='null'}

The SBC includes an IPSP configurable flag to prevent relaying an end-to-end session refresh UPDATE/RE-INVITE locally (when the "End To End Update" and/or the "End To End Re Invite" flags are enabled) using the IPSP flag “Suppress E2ESession Refresh”.

When “Suppress E2ESession Refresh” is enabled, the SBC terminates processes the session refresh UPDATE & Re-INVITE without relaying it. The default value is "Disabled".

Note that an UPDATE request without an SDP and an UPDATE request with the same SDP are considered session refresh updates. These updates can exist in an early dialog established state or a call established state. Also, a Re-INVITE with the same SDP is considered as a session refresh Re-Invite.

Configuration details: