Mixed TCH/F and TCH/H issues

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/OpenBSC@lists.osmocom.org/.

Alexander Chemeris alexander.chemeris at gmail.com
Tue Sep 17 06:44:35 UTC 2013


Hi Andreas,

On Mon, Sep 16, 2013 at 5:27 PM, Andreas Eversberg <andreas at eversberg.eu> wrote:
> Alexander Chemeris wrote:
>>  * LCR was connected to the MNCC socket, but in the case of
>> TCH/F->TCH/H call I didn't see it coming to LCR at all.
>
> the case you described is a bit weird. as long as you use the "-m"
> option of openbsc, you will get the mncc socket to be connected (as your
> logs show). then every call setup is routed to LCR.
>
> i cannot see a problem, since there are so many calls. it would help, if
> you start all applications, then do one call (which does not connect)
> and get a set of logs.

Wireshark logs in the archive have only two calls (one in each
direction). You should be able to relate them to logs, correlating
Wireshark timestamps and timestamps in logs. You could enable absolute
time display in Wireshark for that purpose.

-- 
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru




More information about the OpenBSC mailing list