Versions Compared

Old Version 3

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
AUTH2UserResourceIdentifier{userKey=8a00a0c85bb25531015bc4122a4f0003, userName='null'}
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca7f046c8a00a0c880e94aad0181077fa2530009, userName='null'}
JIRAIDAUTHSBX-92360123973
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e98a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c94702568a00a0c880e94aad0181077fa2530009, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5308028a00a0c880e94aad0181077fa2530009, userName='null'}


Panel
Table of Contents
maxLevel3


The SBC supports Text over Internet Protocol (ToIP), including the inter-working between ToIP and the Text Telephone (TTY) protocols employed in Code Division Multiple Access (CDMA) wireless networks and wire-line VoIP networks (using Baudot).

The support is applicable for SBC deployments in to SBC 5400, 7000, SWe (virtual and cloud environments (I-SBC and D-SBC).

The following interworkings and related transcodings are supported:

Table 1: Supported Interworkings and Transcoding

InterworkingTranscoding

T.140 to TTY

  • AMR-NB to EVRC/EVRC-B
  • AMR-WB to EVRC/EVRC-B
T.140 to Baudot
  • AMR-NB to G711A/U
  • AMR-WB to G711A/U

), and CNe.

The T.140 protocol supports the following codecs: AMR-WB, AMR-NB, EVS, G.711, G.722, and Opus.

The following interworkings and related transcodings are also supported:

Image Added

TTY to Baudot supportEVRC/EVRC-B to G711

Info
iconfalse
titleNote
  • The SBC supports pass-through for all the text transmission protocols mentioned above.
  • The SBC performs T.140 to TTY/Baudot Interworking only when the call is transcoded. However, the SBC does not add DSP/transcoding resource just to perform this interworkingtext interworking.
  • The SBC does not voluntarily insert a "m=text" line, even though the t140Call flag is enabled on the egress trunk group. The SBC only relays the "m=text line", or interworks with TTY/Baudot, if the ingress SDP contains a valid "m=text" line.


Info
iconfalse
titleNote

The following limitations apply:

  • Ribbon supports only 45.45 bps Baudot.
  • Maximum buffering for T.140 packets is approximately 30 seconds.


Info
iconfalse
titleNote

To configure this feature, ensure that the t140Call parameter is set to enable, by using the following syntax:

% set profiles media packetServiceProfile <profile_name> flags t140Call enable

RTCP Generation For T.140 Pass-Through Calls

Based on PSP configuration, the SBC has the capability to generate RTCP for T.140 pass-through media streams if RTCP is not received from other peer. The interval for which the SBC monitors the RTCP packets for T140 stream from endpoints are also defined. If RTCP is not received within the interval, the SBC starts RTCP generation. 

For more information, refer to Packet Service Profile - CLI.

Text Transcoding Control

Users can control text transcoding using the flag g711T140BaudotAdapt.pagebreak

Command Syntax

set profiles media packetServiceProfile <psp_name> flags g711T140BaudotAdapt <disable | enable>
commit

Command Parameters

Parameter

Default

Description

M/O

g711T140BaudotAdapt

Disable

When this flag is enabled, the SBC can introduce a DSP resource into the call path when the audio codecs are same and while the RTT to Baudot interworking is needed.

  • disable (default)
  • enable

Info
titleNote

This flag only affects the behavior for G.711-G.711 calls for which one leg has T.140 (one m-line with T.140) with a valid port.
As well, the SBC will ignore this flag when the HDPreferred {*}Flag is enabled under PSP.


O

Configuration Example

set profiles media packetServiceProfile <default_PSP> flags g711T140BaudotAdapt <enable>
commit

Support for Issue: "Codec not supporting RTT with DSP insertion but no text adaptation"

In the following example, the Caller (UA-A) provides two streams in its SDP: one for the audio and one for the Real-Time Text media line. Their respective media description is also provided: audio G.729 is specified as the first codec in the intersected Pack Service Profile, and text with t140 subtype on the second stream, but the user could choose ANY codec whose RRT the SBC does not support). A list of codecs could follow G.729. When the Call Recipient rejects the T.140 (using port 0), the SBC knows that it must set the DSP to perform transcoding and that no adaptation can take place (no Baudot to/from T.140 adaptation is possible since G.729 does not support T.140).

Info

For this scenario, the DSP is inserted even though there is no text adaptation. In order to have text adaptation, the offer will always start (first codec in the intersected PSP) with a codec for which the SBC supports T.140 (e.g. AMR, AMR-WB, etc.).