In this section:
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.
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.
The maximum size of the callData section in the metadata portion of the SIPREC INVITE sent towards SRS is 2,048 bytes.
The command syntax to configure the sipRecMetadataProfile
is shown below:
% set profiles services sipRecMetadataProfile <sipRecMetadataProfile> version <0..1> sipHeader <sipHeader> sipToXmlTagName <sipToXmlTagName> state <disabled | enabled>
The command syntax to attach the sipRecMetadataProfile to the SRS Trunk Group is shown below:
% set addressContext <addressContext> zone <zone> sipTrunkGroup <sipTrunkGroup> services sipRecMetadataProfile <sipRecMetadataProfile>
The sipRecMetadataProfile must be attached to the sipTrunkGroup towards the SRS.
Configuring sipRecMetadataProfile
and attaching it to the SRS Trunk Group:
% set profiles services sipRecMetadataProfile SRMP_ING version 1 sipHeader P-Preferred-Identity sipToXmlTagName xPPreferredIdentity % set profiles services sipRecMetadataProfile SRMP_ING state enable