Page History

Add_docset_workflowAPPRJIDSBX-29018AUTH1bscogginsDEV1dalvesLDEV1sgardellSVT1akaurLSVT1radaikalamAUTHJIDSBX-29018 

Overview

The

• Contact header information is used to form the R-URI of the redirected INVITE.
• Embedded Route header information is used for determining the egress IPTG and next hop of the redirected INVITE.
  • Route header with FQDN or IP Address pointing to SBC the

    Spacevars
    0 product

     (received FQDN matches configured FQDN of zone on which 3xx is received or received address matches Signaling Ports address) is removed.
  • Egress IPTG selection is based on the following criteria in the order shown.
    • Embedded Route header parameters presence.
      • dtg parameter if dtg is present.
      • tgrp parameter if tgrp and trunk-context are present and processTgrpContext is enabled and trunk-context points to SBCthe

        Spacevars
        0 product

        .
      • tgrp parameter if tgrp is present.
    • "skipDTGLookupForRouteHdr” flag.
      • Network Selector Table (NST) lookup (using embedded Route header content and zone on which the 3xx is received) if this flag is disabled (for the IPTG that received the 3xx).
      • PSX/ERE routing analysis (embedded Route header content is used as the called party information) if this flag is enabled.
  • Top-most Route Header not pointing to SBC is used for determining the next hop.
• Embedded From header information is used as the calling party. Embedded To header is the new To header in the redirected INVITE.
• All embedded headers received are present (in non-embedded form) in received order in the redirected INVITE (other than any removed Route header pointing to SBC and headers which replace the ingress INVITE headers).

...

For configuration details, seerefer to:

• CLI: egressIpAttributes Egress IP Attributes - SIP - CLI
• EMA: Redirect - Flags (EMA)

...