Hi there,
I'm cleaning up my cellar and I found a EGM 35 GSM A-Bis field test
equipment.
Manufacture: GN Nettest ELMI
Typ: EGM 35
It is meant to tap in a E1 line and decode messages and also the voice
streams between BSC and BS. Comes with headset :)
If any body has interest, I am happy to send pictures off-list.
Regards
Miguel
Hi.
I've just sent 4 patches to ML - that's cosmetic adaptation of work by Tobias Engel
(tobias/supplementary_services branch) from few years back to current master.
Not sure if I should put sign-off in the commits but I certainly don't claim to be
author of the code. Anyway, I'd like to see this pushed forward cause I think it's
useful functionality better suited for master branch - would be shame to let it bitrot :)
Comments and suggestions are appreciated as usual.
--
best regards,
Max, http://fairwaves.co
Hi
On 05.06.2015 15:15, ☎ wrote:
> Could you perhaps summarize what's happening around tests/gb/gprs_bssgp_test.c:229?
The line before the failing test is
rc = bssgp_tx_fc_bvc(&bctx, tag, bmax, rate, bmax_ms, rate_ms,
NULL, NULL);
The bssgp_tx_fc_bvc function will in general call gprs_ns_sendmsg ->
gprs_ns_tx -> nsip_sendmsg -> sendto. The sendto function had been
"replaced" by redefining it locally which worked at least with the
default ld up to ubuntu 14.04. (see Holger's replies).
The system's sendto will fail in the test, since the UDP socket has not
been configured. The local replacement (see gprs_bbsgp_test.c:37) will call
fprintf(stderr, "MESSAGE to 0x%08x, msg length %d\n%s\n",
dest_host, len, osmo_hexdump(buf, len));
so you just need to look into the stderr output to see, whether this is
a linker issue.
If yes, the issue will appear in more test programs, since that pattern
has been used many times.
If there is no way to trick the linker to use the "old" behaviour, those
test programs will have to be changed to use another mocking mechanism,
e.g. by using the --wrap feature (if it is supported by the linker), see
openbsc:openbsc/tests/sgsn/sgsn_test.c.
HTH
Jacob
>
> The test fails for me (and another person with ubuntu 15.04 x86_64) on OSMO_ASSERT(rc
>> = 0);
>
> This is 100% reproducible but I don't know much about Gb part so I'm not sure how to
> track this down properly. Any ideas/advices?
>
--
- Jacob Erlbeck <jerlbeck(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte
Pardon for multiple copies, but this is really curious: gbprocy test also fails for
me during OpenBSC build at gbproxy_test.c:1922 which also contains following
misterious comment:
/* TODO: The following breaks with the current libosmocore, enable it
* again (and remove the plain expect_msg), when the msgb_bssgph patch
* is integrated */
What is the status of this "msgb_bssgph patch" patch? Is there patchwork link available?
I suspect it's still unmerged because swapping the lines as instructed in comment
still results in crash with the latest libosmocore from git.
Commenting out both lines produce sane-looking output but the test expectedly fails
due to mismatch with expected output.
I wonder if should comment out the 2nd line until the libosmocore patch is merged or
perhaps consider merging the necessary patch?
22.05.2015 15:38, ☎ пишет:
> Hi.
>
> Anyone else experienced this with latest libosmocore from git?
>
> ./testsuite.at:124: $abs_top_builddir/tests/gb/gprs_bssgp_test
> stderr:
> MESSAGE to 0x7f0000ff, msg length 12
> 02 00 81 01 01 82 0b 56 04 82 0b 55
> All NS-VCs for NSEI 2901 are either dead or blocked!
> All NS-VCs for NSEI 2901 are either dead or blocked!
> BSSGP BVCI=0 Rx BVC STATUS, cause=Protocol error - unspecified
> BSSGP BVCI=1234 Rx BVC STATUS, cause=Unknown BVCI
> NSEI=2901/BVCI=2989 Cannot handle PDU type 34 for unknown BVCI, NS BVCI 2989
> Unable to resolve NSEI 4660 to NS-VC!
> Assert failed rc >= 0 gb/gprs_bssgp_test.c:229
> /home/user/source/libosmocore/tests/testsuite.dir/at-groups/19/test-source: line 25:
> 8497 Aborted (core dumped) $abs_top_builddir/tests/gb/gprs_
> bssgp_test
>
--
best regards,
Max, http://fairwaves.co
Hi everyone,
I was just wondering if it is possible to send '?' SMS through the VTY. I
was also wondering if someone could provide an example on how to send a
silent-sms, whenever I try to send one i get disconnected from the VTY.
Regards,
Mike