The The IP Signaling Profile flag, " This feature is supported across GW-GW, where the When a 3xx response is received with both Diversion and History-Info header, Diversion header processing is given priority within the received 3xx, irrespective of the Diversion or History-Info configuration on the new egress route where the call is redirected. Ribbon recommends using the Transparency Profile to configure transparency on the SBC Core for new deployments, as well as applying additional transparency configurations to existing deployments. Do not use IP Signaling Profile flags in these scenarios because the flags will be retired in upcoming releases. Refer to the SBC SIP Transparency Implementation Guide for additional information. On the The Call Forwarding window is displayed. On the Call Forwarding window, choose the IP Signaling Profile as DEFAULT_SIP to view the Call Forwarding for SIP Trunk Group. Trunk Provisioning - Egress IP Attributes SIP Call Forwarding Egress IP Attributes Call Forwarding Parameter Description Enable flag to allow interworking between Diversion and History-Info header as per RFC 6044. The NOTE: Diversion History Info Interworking is only visible when either Diversion or History-Info header is selected as the egress call forwarding header. Diversion and History-Info Transparency configuration controls are ignored when it is enabled. This parameter has precedence over the others. Use this parameter to define how to map the diversion or redirecting data. When enabled, the ingress Diversion header is passed through unchanged. Call forwarding data mapping transparency applies to Diversion header only. Make the required changes and click Save.Diversion History Info Interworking
", indicates to the egress side that the inter-working is accomplished as per the RFC 6044. In addition, the existing Redirecting Info flag of "Diversion" and "History-Info" will indicate to the egress the target inter-working header which needs to be sent out in INVITE message. The Diversion and History-Info headers received on the ingress side are transparently passed across to the egress where newly introduced flags determine the corresponding header to be used to pass on this information in outgoing INVITE.To View and Edit Call Forwarding
DEFAULT_SIP
Diversion History Info Interworking Data Mapping Diversion Header Transparency
Additional topics: