Route call from OpenBSC to real operator using osmocombb

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

robert robert.steve07 at gmail.com
Tue Feb 23 11:27:43 UTC 2016


I forgot to mention that the reason for the this failure is described in diagnostic as “CLIR not subscribed”. At each call setup there is a “CLIR invocation” although in the mobile.cfg file it is set to “no clir”. How can I remove this condition in LCR ?


Best regards,
Robert,




On Feb 22, 2016, at 10:57 AM, robert <robert.steve07 at gmail.com> wrote:

> 
> HI,
> 
> When I try to route calls, the osmo phone which is connected to the real network starts initiating the call but then immediately releases the connection with the following cause “Requested facility not subscribed”. Does anyone know what is causing this error ?
> 
> Best regards,
> Robert,
> 
> 
> 
> On Feb 14, 2016, at 10:13 PM, Harald Welte <laforge at gnumonks.org> wrote:
> 
>> On Sat, Feb 13, 2016 at 09:31:02AM +0100, Tomcsányi Domonkos wrote:
>>> As far as I know osmocomBB doesn’t have a SIP sink yet, you’d need to
>>> create the code for that.
>> 
>> You can connect OsmocomBB via its MNCC interface to LCR as a gsm-ms
>> channel.  This is similar to attaching OsmoNITB via its MNCC interface
>> as a gsm-bs channel to LCR.
>> 
>> So it should be no problem to connect both OsmoNITB and OsmocomBB
>> simultaneously to a single LCR instance and route calls vice-versa.
>> 
>> -- 
>> - Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
>> ============================================================================
>> "Privacy in residential applications is a desirable marketing option."
>>                                                 (ETSI EN 300 175-7 Ch. A6)
> 




More information about the baseband-devel mailing list