This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-commitlog@lists.osmocom.org/.
gitosis at osmocom.org gitosis at osmocom.orgThis is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Python scripting interface to the OsmoNITB MNCC interface".
The branch, master has been updated
via 983231a70dea18f4a38d6f45ad235f3c8a1ad92e (commit)
from ce184f83f0ebad256fe05be75c2b53d03a5ee158 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/mncc-python/commit/?id=983231a70dea18f4a38d6f45ad235f3c8a1ad92e
commit 983231a70dea18f4a38d6f45ad235f3c8a1ad92e
Author: Gerard Pinto <gerardfly9 at gmail.com>
Date: Sun Jun 4 21:04:56 2017 -0700
Bearer capability not provided during MO call using mncc-python, which results in GSM IE error (96) invalid mandatory information sent by Network -> MS (mncc-python)
Verified this error by GSMTAP using mncc-python interface OsmocomBB to network
Proposed Changes:
In case of MO call (_onmncc_setup_req) caller needs to provide bearer_cap speech version
Added mncc.bearer_cap in mncc_sock.py based on codecs = GSM48.AllCodecs
Added new field mncc.MNCC_F_BEARER_CAP in mncc.MNCC_SETUP_REQ, when call is initiated (MO) from MS -> network
Change-Id: If77851b86111d62d82221a886ed2391179080cca
-----------------------------------------------------------------------
Summary of changes:
gsm_call_fsm.py | 7 ++++---
mncc_sock.py | 12 ++++++++++++
2 files changed, 16 insertions(+), 3 deletions(-)
hooks/post-receive
--
Python scripting interface to the OsmoNITB MNCC interface