You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Back to Table of Contents

Back to Configuration

Back to Configuration - System Provisioning

Back to Category - Trunk Provisioning

Back to System Provisioning - Ip Signaling Profile

Back to Ip Signaling Profile - Egress Ip Attributes

Back to Egress Ip Attributes - Sip Headers And Parameters

Additional section:

In this section:

The SBC support inter-working between Diversion header and History-Info header based on RFC 6044. In addition to handling the History-Info header in SIP messages in the dotted notation of indexes, SBC is enhanced to handle cause as specified in RFC 4458 or Reason header as specified in RFC 4244.

The IP Signaling Profile flag, "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.

This feature is supported across GW-GW, where the SBC is the egress node.

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.

To View and Edit Call Forwarding

On SBC main screen, go to Configuration > System Provisioning > Category: Trunk Provisioning > Ip Signaling Profile > Egress Ip Attributes > Sip Headers And Parameters > Call Forwarding. The Call Forwarding window is displayed.

DEFAULT_H323

On the Call Forwarding window, choose the Ip Signaling Profile as DEFAULT_H323 to view the Call Forwarding for H323 Trunk Group.

Trunk Provisioning - Egress Ip Attributes H323 Call Forwarding

There are no Call Forwarding parameters for DEFAULT_H323 type of Egress Ip Attributes.

DEFAULT_SIP

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

The following fields are displayed:

Egress Ip Attributes Call Forwarding

Parameter

Description

Diversion History Info Interworking

 Enable flag to allow interworking between Diversion and History-Info header as per RFC 6044. The 

Unable to show "metadata-from": No such page "_space_variables"
supports up to 12 History-Info entries and 10 Diversion entries. When this flag is disabled, only the first and last entries are maintained when History-Info or diversion transparency is disabled.

  • disable (default)
  • enable

 

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.


Data Mapping

 Use this parameter to define how to map the diversion or redirecting data. Options are:

  • none – No Diversion information is egressed.
     
  • diversion – Diversion information is sent out as SIP Diversion Header.
  • pkHeaders – Diversion information is sent out as proprietary PK Headers.
Diversion Header Transparency

 When enabled, the ingress Diversion header is passed through unchanged. Call forwarding data mapping transparency applies to Diversion header only.

  • disable (default)
  • enable

Make the required changes and click Save at the right hand bottom of the panel to save the changes made.

  • No labels