Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

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=8a00a0c880e94aad0181077fa2530009, userName='null'}
JIRAIDAUTHSBX-131158
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ce1a0af8, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ce1a0af8, userName='null'}


Panel

In this section:

Table of Contents
maxLevel3



Info
iconfalse

Related articles:

Children Display



 

The

Spacevars
0series4
 platform platform supports inter-working between the Diversion header and the History-Info header based on RFC 6044. In addition to handling the History-Info header in SIP messages in the dotted notation of indexes, the
Spacevars
0product
 supports the SBC supports the Cause parameter as specified in RFC 4458 or the Reason header as specified header 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 of the target inter-working header, which needs to be sent out in the 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 information in outgoing INVITE.

This feature is supported across GW-GW, where the

Spacevars
0product
 is the egress node.

Note

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.

Include Page
Transparency_Profile_Note
Transparency_Profile_Note

To View and Edit Call Forwarding

On the

Spacevars
0product
 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.

Caption0Figure1

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.

Caption
0Figure
1Trunk Provisioning - Egress Ip Attributes SIP Call Forwarding

Image Modified

 


The following fields are displayed:

Caption0Table1Egress 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 

Spacevars
0product
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
  • Disabled (default)
enable
  • Enabled

NOTE:

Diversion History Info Interworking 

This flag is only visible when either the Diversion or History-Info header is selected as the egress call-forwarding header. When it is enabled, the Diversion and History-Info Transparency configuration

controls are ignored when it is enabled

controls are ignored. This parameter has precedence over

the others

these controls and the TG Signaling flag Accept History Info.

Data Mapping

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

none –
  • None – No Diversion information is egressed.
diversion
  • 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 the Diversion header only.

disable
  • Disabled (default)
  • enable
    •  
    • Enabled

    Make the required changes and click Save at the bottom right-hand

    bottom

    corner of the panel to save the changes made.

    pagebreak