30 Jun
2009
30 Jun
'09
11:51 a.m.
Hello Andreas,
On Mon, 29 Jun 2009 23:37:51 +0200, "Andreas.Eversberg"
<Andreas.Eversberg(a)versatel.de> wrote:
this was the problem. finally got the measurement reports (--debug
....:DMEAS). you just need to add to misdn.c:
case DL_UNITDATA_IND:
and everything is fine.
Great, so this is solved.
I noticed one minor problem, its the meaning of the MEAS-VALID
flag. The spec says that "0" means "valid" and "1" is
"not valid".
So
if (!(meas_rep.flags & MEAS_REP_F_VALID))
should be changed or the parsing of the measurement result where this
flag is set.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
5 Jul
5 Jul
4:08 a.m.
New subject: MEAS REP inverted logic (was Re: AW: patches again)
Hi Dieter,
On Tue, Jun 30, 2009 at 09:51:20AM +0200, Dieter Spaar wrote:
I noticed one minor problem, its the meaning of the
MEAS-VALID
flag. The spec says that "0" means "valid" and "1" is
"not valid".
So
if (!(meas_rep.flags & MEAS_REP_F_VALID))
should be changed or the parsing of the measurement result where this
flag is set.
thanks. Rarther than this, I have changed it in parse_meas_rep, i.e. set
MEAS_REP_F_VALID is set if the bit is 0.
It's not yet in the public git repository yet, but in my local tree.
--
- 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)
5830
days inactive
5835
days old
1 comments
2 participants
participants (2)
-
Dieter Spaar -
Harald Welte