FreeCalypso > hg > freecalypso-tools

comparison doc/TCH-bit-access @ 946:8f7c50e1fa3b

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
doc/TCH-bit-access: refer to Speech-codec-selection in freecalypso-docs
author Mychaela Falconia <falcon@freecalypso.org>
date Tue, 06 Jun 2023 04:28:21 +0000
parents 3de3b34189be
children 1f2459a776d7
comparison
equal deleted inserted replaced
945:4c601097d23f 946:8f7c50e1fa3b
191 with a speaker & mic user connection (as opposed to TCH tap modes), our current 191 with a speaker & mic user connection (as opposed to TCH tap modes), our current
192 FreeCalypso firmwares do support AMR when running on Calypso C035 silicon with 192 FreeCalypso firmwares do support AMR when running on Calypso C035 silicon with
193 DSP ROM version 3606. (DSP ROM version 3416 together with the respective patch 193 DSP ROM version 3606. (DSP ROM version 3416 together with the respective patch
194 version also appears to have working AMR, at least in light testing, although 194 version also appears to have working AMR, at least in light testing, although
195 of course we do NOT recommend it for production use.) Therefore, if you wish 195 of course we do NOT recommend it for production use.) Therefore, if you wish
196 to play with EFR, you need to tell the network (via the Bearer Capabilities 196 to play with EFR, you need to tell the network (via the Bearer capability
197 information element in CC messages) that your MS does not support AMR, and if 197 information element in CC messages) that your MS does not support AMR, and if
198 you wish to play with FR1, you need to tell the network that your MS only 198 you wish to play with FR1, you need to tell the network that your MS only
199 supports FR1 and no others. 199 supports FR1 and no others.
200 200
201 The outstanding issue here is that we need to implement some mechanism in our 201 Please refer to Speech-codec-selection article in freecalypso-docs for more
202 FreeCalypso firmwares, probably a custom AT command, that will modify the 202 information and specific instructions.
203 Bearer Capabilities IE (artificially restrict the set of supported codecs) on a
204 per-call basis. Until we implement the necessary support, the only current way
205 to create such codec-restricted operation is by writing a /pcm/MSCAP file into
206 FFS with the desired bit mask of supported codecs - but this method is hugely
207 inconvenient because this file is read only on fw boot, thus every modification
208 requires a full reboot cycle.