Problem in the communication with a real MSC

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/.

Holger Hans Peter Freyther holger at freyther.de
Thu Dec 16 18:01:29 UTC 2010


On 12/16/2010 01:15 PM, Luca Bertoncello wrote:
> Hi, List!


> 
> I think, it is not normal, that the communication with the MSC was lost.
> Both of them (OpenBSC and MSC) are on the same Gigabit network, so
> there is no connection problem...
> Any idea?

Well, who is closing the TCP connection? Is it the MSC that is unhappy? Is it
the BSC that is unhappy (e.g. you removed a log line talking about timeouts?)?
Do you see any other messages in wireshark? Which MSC is that>




> Another problem: I get very oft the error:
> 
> <0000> chan_alloc.c:441 (bts=1,trx=0,ts=0,ss=0) Recycling Channel.
> 
> Any idea?

Why do you think it is an error? It is a normal notice on channel release.
Actually you must be using on-waves/bsc-master as well.





More information about the OpenBSC mailing list