diff options
| author | Neels Hofmeyr <nhofmeyr@sysmocom.de> | 2022-09-12 03:41:05 +0200 |
|---|---|---|
| committer | Neels Hofmeyr <nhofmeyr@sysmocom.de> | 2022-09-23 19:11:51 +0200 |
| commit | b3be16e152676ca57bdadff56dc42bb54867f4cd (patch) | |
| tree | 06fd428d4fd84e34c3bd003ccf318d30d6c1734e | |
| parent | 1b4667820e4fce1556730697e9455e5f793801a6 (diff) | |
codec t9n: comment
Change-Id: Ia881a1624496b56d6237e45cff3b7bac04394cf9
| -rw-r--r-- | src/libmsc/codec_sdp_cc_t9n.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/src/libmsc/codec_sdp_cc_t9n.c b/src/libmsc/codec_sdp_cc_t9n.c index 200bd8584..790202c0e 100644 --- a/src/libmsc/codec_sdp_cc_t9n.c +++ b/src/libmsc/codec_sdp_cc_t9n.c @@ -121,6 +121,10 @@ const struct codec_mapping codec_map[] = { * to match this entry, and it ends in an aborted call due to no codec match. * If the peer offers plain "AMR/8000" and we reply with "AMR/8000 fmtp:octet-align=1", * then everything works out happily, */ + /* XXX what?? 3GPP TS 26.103 says "The bandwidth efficient mode of RFC 4867 shall be used. To + * offer the bandwidth-efficient mode, the octet-align parameter should be omitted in SDP." + * How can it work when we send bw-efficient AMR but said octet-aligned in the SDP?? + */ .fmtp = "octet-align=1", }, .mgcp = CODEC_AMR_8000_1, |