...
The MTSI client functionality is required when SBC the
is deployed as:
- MGCF providing interworking between an MTSI client and a non-MTSI client (that is, a CS UE).
- Access Access SBC media gateway.
| Caption |
|---|
|
|
...
supports AMR Initial codec mode as per 3GPP26.114 specification. When AMR or AMR-WB is used, to avoid congestion on the link and to improve inter-working with CS GERAN,
SBC the limits the initial codec mode for a session to a lower mode until at least one frame-block. On enabling "Initial codec mode" while creating AMR Codec Entry, an AMR call starts with a lowest mode rate or second lowest mode rate until it receives a CMR request from the U.E to adapt the mode rate to a different value. If disabled, the AMR call starts with the highest mode rate within the negotiated mode-set.
The
SBC also supports the following functionality:
- AMR to AMR transcoding for both restricted and unrestricted mode set
- AMR to non-AMR transcoding
- AMR attributes such as
mode-change-period, mode-change-capability and mode-change-neighbor.
| Note |
|---|
The SBC does not support the following AMR attributes:- CRC
- Robust-Sorting
- Interleaving
|
...
supports RTCP bandwidth interworking by negotiating RR and RS bandwidth parameters. However,
SBC the does not allow using RTCP in a peer-to-peer voice call. This can be disabled at the MTSI client by setting RS=0 and RR=0 during call setup. But when a call is HELD, MTSI clients can enable RTCP to prevent the triggers of RTP inactivity.
The
SBC supports enabling the RTCP for point-to-point calls only when the call is HELD based on PSX configuration flag.
...