Page History
| Add_workflow_for_techpubs | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Panel | ||||
|---|---|---|---|---|
In this section:
|
| Panel |
|---|
Related Articles:
|
Overview
The SBC Core is enhanced to support supports text media streams based on the T.140 codec. A new The t140Call flag t140Call is added to the Packet Service Profile to support T.140 calls.
The SBC supports:
- Calls with only T.140 stream.
- T.140 stream pass-through when it is part of multiple stream sessions (audio and Video calls).
- Updated answer in 200 OK for T.140 streams.
- Direct Media calls with T.140 streams.
- Late media pass-through calls with T.140 streams.
- Downstream forking calls with T.140 streams.
- Ring Back Tone (RBT) call flows, all types of direct media, LI, SRTP/DTLS pass-through calls with T.140 streams.
The following session modifications are supported for the T.140 sessions:
- Addition and/or removal of T.140 streams.
- Modification triggered due to change in T.140 stream attributes.
- Modification triggered due to changes in session attributes for non-T.140 stream related attributes.
| Note |
|---|
The SBC does not validate, prioritize, or purge any codec or attributes received for the text media. Any validation required is performed by the endpoints. |
Text Codecs SIP
The SBC Core relays text codec by default using dynamic payloads.
Text Codecs T.140
The SBC supports the following codec for Text call scenarios (that is, Text - Text calls with an audio and video stream).
| Caption | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
| Pagebreak |
|---|
Overview
Content Tools