Page History

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.

Include Page

	_callData_max_size
	_callData_max_size

Command Syntax

To The command syntax to configure the sipRecMetadataProfile, execute the following command is shown below:

Code Block

language	none

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

To The command syntax to attach the sipRecMetadataProfile to the SRS Trunk Group , execute the following commandis shown below:

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

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

Command Parameters

Caption

0	Table
1	SIPREC Metadata Profile parameters

Parameter	Length/Range	Default	Description	M/O
`sipRecMetadataProfile <variable>`	Up to 23 characters	N/A	Indicates the name of the profile and specifies the SIP headers that are included in the SRS call.	M
`version`	0 to 1	0	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 characters	N/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 characters	N/A	Indicates XML tag name for the configured SIP header.	O
`state`	N/A	disabled	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

language	none

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

Pagebreak

Space shortcuts

Page tree

Versions Compared

Old Version 1

New Version Current

Key

Command Syntax

Command Parameters