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/.
Don Fanning don at 00100100.netOne additional note to this... it will segfault as soon as i go off hook on the MT. On Fri, Jun 8, 2012 at 12:22 PM, Don Fanning <don at 00100100.net> wrote: > Erg... Got an issue with LCR+SIP > > When placing a MT call from a SIP client I get a segfault. > This is using the latest OpenBSC/LCR from GIT and asterisk 1.8 without any > special patching. > > Pastebin for LCR output: http://pastebin.com/WDeApEak > > On a side note, I swear I had this noted somewhere but can't find it. > Using the LCR+SIP+Asterisk bridging, what extension/context does LCR ring > Asterisk? In the mISDN based routing, you would tell it a context... with > SIP bridging, it doesn't use it. So what do I tell my asterisk so it can > handle the outgoing call? > > Thanks, > -Don > > > On Tue, May 15, 2012 at 12:40 AM, Holger Hans Peter Freyther < > holger at freyther.de> wrote: > >> On 05/14/2012 06:58 PM, Arturo Rivas wrote: >> >> Hi, >> please once more in a different order >> >> 0.) State which versions of software (asterisk, lcr, openbsc) >> 1.) First output of applying patches (where does the patch come from?) >> 2.) Then output of configure/make >> >> > >> > *rivas at ubuntu:~/openbsc/lcr$ git apply --verbose >> lcrOpenBSC.patchChecking >> > patch gsm_bs.cpp... >> > error: while searching for: >> >> So in your case applying the patch does not work, most likely as LCR has >> catched up and you don't need the patch anymore. >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20120608/3e03633d/attachment.htm>