Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 2

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH2
AUTH1
JIRAIDAUTHSBX-71651
REV5
REV6
REV3
REV1

Panel

In this section:

Table of Contents

 

 

 

The SBC supports SIPREC when the SIPREC specifications were in early drafts (draft-ietf-siprec-xx-06). With the implementation of this feature, the SIPREC standard has evolved to RFCs (RFC 7245, RFC 7865, RFC 7866, and RFC 8068), and provides capability for supporting "dynamically programmable" selection of metadata content.

  • The profile sipRecMetaDataProfile is introduced to the services to provide the capability to configure the headers that are mapped from the target call leg to the XML and the corresponding metadata XML element name.
  • In case of a basic call, all information is copied from the initial-INVITE message on the leg where the tap is, to the metadata XML. However, "To" header and "to-tag" is copied additionally from the local information (as to-tag does not present in the INVITE).
  • In case of SIPREC trigger during REFER based transfer, irrespective of where the SIPREC tap is, all information is copied from the initial-INVITE of the new call leg towards the transfer target (C party).
  • In case of CLI triggered recording, the existing implementation of sending predefined information in metadata XML remains same (gcid, call-id, from, to). The new configuration of header-metadata mapping is not considered in this scenario.

 

Command Syntax

To configure the sipRecMetadataProfile, execute the following command:

Code Block
languagenone
% set profiles services sipRecMetadataProfile <sipRecMetadataProfile>
    version <0..1>
    sipHeader <sipHeader>
        sipToXmlTagName <sipToXmlTagName>
    state <disabled | enabled>

 

To attach the sipRecMetadataProfile to the SRS Trunk Group, execute the following command:

Code Block
% set addressContext <addressContext> zone <zone> sipTrunkGroup <sipTrunkGroup> services sipRecMetadataProfile <sipRecMetadataProfile>
Info

 The sipRecMetadataProfile must be attached to the sipTrunkGroup towards the SRS.


Command Parameters

Caption
0Table
1SIPREC Metadata Profile parameters
ParameterLength/RangeDefaultDescriptionM/O
sipRecMetadataProfile <variable> Up to 23 charactersN/AIndicates the name of the profile and specifies the SIP headers that are included in the SRS call.M
version0 to 10

Indicates the SIPREC metadata profile version.

The options are:

  • 0(default): When the version is set as 0, the SBC supports backward compatibility and pre-defined metadata for passing proprietary call specific information from the SRC to the SRS.
  • 1: When the version is set as 1, the SBC supports dynamic configuration of the metadata variables.
O

sipHeader <variable>

Up to 31 charactersN/A

Indicates the SIP header, which are included in the SRS call.

Note: Maximum 32 SIP headers can be created in one sipRecMetadataProfile.

O

sipToXmlTagName <variable>

Up to 31 charactersN/AIndicates XML tag name for the configured SIP header.O
stateN/Adisabled

Indicates the admin state of the SIPREC metadata profile.

The options are:

  • disabled (default)
  • enabled
O

Command Examples

Configuring sipRecMetadataProfile and attaching it to the SRS Trunk Group:

Code Block
languagenone
% set profiles services sipRecMetadataProfile SRMP_ING version 1 sipHeader P-Preferred-Identity sipToXmlTagName xPPreferredIdentity
% set profiles services sipRecMetadataProfile SRMP_ING state enable

 


Pagebreak