codec t9n: comment
Change-Id: Ia881a1624496b56d6237e45cff3b7bac04394cf9
diff --git a/src/libmsc/codec_sdp_cc_t9n.c b/src/libmsc/codec_sdp_cc_t9n.c
index d5d2ad5..7813a7c 100644
--- a/src/libmsc/codec_sdp_cc_t9n.c
+++ b/src/libmsc/codec_sdp_cc_t9n.c
@@ -121,6 +121,10 @@
* 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,