In this section:


IMPORTANT

Ribbon recommends using the Transparency Profile to configure transparency on the SBC Core for new deployments, as well as applying additional transparency configurations to existing deployments. Do not use IP Signaling Profile flags in these scenarios because the flags will be retired in upcoming releases.

Refer to the SBC SIP Transparency Implementation Guide for additional information.


Event Transparency

The SBC transparently passes the following content types associated with the specified MMTel services:

Table 1: Content Types for Event Transparency

Service NameMethodEvent NameContent Type

CDIV

SUBSCRIBE

comm-div-info

application/comm-div-info-filter+xml

CDIV

NOTIFY

comm-div-info

application/comm-div-info-ntfy+xml

CCBS

SUBSCRIBE

(O-AS subscribes to T-AS if the user is Busy)

Call-Completion


CCBS

NOTIFY

(O-AS subscribes to T-AS if the user is Busy)

Call-Completion


application/call-completion

CCBS

Publish

(If the CCBS service fails, O-AS sends Publish with closed as state to T-AS)

Presence

application/pidf+xml


Message Body Transparency

The SBC transparently passes the following content-types associated with the specified MMTel services:

Table 2: Content Types for Message Body Transparency

Service NameRequest/ResponseContent-Type

CCBS

 486 Response

Message/externalbody

AOC

INFO,BYE, and 200 OK for INVITE, 18x Response

INVITE, 200 OK for BYE

vnd.etsi.aoc+xml

CW

INVITE

application/vnd.3gpp.cw+xml

(MIME Body)

MCID

INFO

application.vnd.etsi.mcid+xml

CRSINVITEapplication/vnd.3gpp.crs+xml
CUGINVITEapplication/vnd.etsi.cug+xml
USSDINVITE, INFO, BYEapplication/vnd.3gpp.ussd


Header Transparency

The SBC transparently passes Recv-Info and Info-Package headers to support MMTel Services.

The following MMTel supplementary services use 199 response code:

  • Communication Completion Services (CCNR in particular)
  • Customized Alerting Tones (CAT)

Refer to Supplementary Services topic for a list of MMTel supplementary services.

  • No labels