Beginning in release 7.2.3R1, the SBC provides an Enhanced Local Redirection feature. In redirected call scenarios, this capability ensures that the SBC applies the same processing to the redirected INVITE message as it applied to the original egress INVITE message. This feature is controlled by a redirect flag called "Enhanced Local Redirection" which is included in the egress IP attributes of IP Signaling Profiles (IPSP). When you enable the Enhanced Local Redirection flag:

  • All headers sent in the original egress INVITE message are sent in the redirected INVITE message.
  • When constructing the redirected INVITE message and the the Contact header of the 3xx response contains headers: 
    • If the Contact contains additional types of headers, the SBC adds these headers to the redirected INVITE message. 
    • If the Contact includes the same type of header, the SBC gives precedence to the contents of the header in the Contact over the header in the original egress INVITE message. 
  • When performing crankback on redirect messages, the SBC uses the crankback profile attached to the ingress trunk group associated with the call. 
Note

You cannot enable the "Enhanced Local Redirection" flag in the IPSP if the "Force Requery For Redirection" redirect flag is enabled. These two types of handling are mutually exclusive.

Refer to Egress IP Attributes - SIP - CLI or Redirect - Flags (EMA) for information on configuring the Enhanced Local Redirection flag.