7 Oct
2016
7 Oct
'16
8:10 p.m.
On Thu, Oct 06, 2016 at 08:20:03PM +0200, Neels Hofmeyr wrote:
Can you please clarify. When you say "on 1.5.4" you mean that you used
a SDK/toolchain from 201310-nightly. However, did you also run a
201310-nightly filesystem on the BTS at that time?
The recent changes in libosmo-abis require the use of a more recent
libortp. The filesystem + SDK of 201310-nightly contains that later
version and should thus be expected to work.
What is of course not supposed to work is a filesystem (including ortp
binary) of 201310-stable or -testing with a osmo-bts binary built on a
SDK/toolchain from 201310-nightly.
Please confirm that this is not the case in your testing.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
I have not
ignored anything, I've pointed to commit which I suspect
could have broken voice (as you rightfully pointed out it's in
libosmo-abis). Could you clarify if reverting this commit in
libosmo-abis fixes the voice for sysmobts master? Or in addition to
reverting c77c2a6aa13accbc558888ab788d1148eb9aeb1a in libosmo-abis I've
got to checkout some later commit in sysmobts?
If reverting commit in libosmo-abis indeed fixes voice for sysmobts sdk
1.5.4 than please send patch for review (add me as reviewer).
These are two distinct issues. The one with no voice at all happens on 1.5.4
and is fixed by gerrit #1011.