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/.
Sebastian Mauer mauimauer at gmail.comAttached is a dump of the communication between BSC and nanoBTS when attempting to make a call. Thanks for helping with figuring this out. Cheers, Sebastian On Fri, 30 Jul 2021 at 16:13, Pau Espin Pedrol <pespin at sysmocom.de> wrote: > > Hi, > > On 7/30/21 4:49 PM, Sebastian Mauer wrote: > > > lchan(0-0-2-TCH_F-0)[0xaaaadc432ba0]{WAIT_RLL_RTP_ESTABLISH}: > > (type=TCH_F) lchan-rtp failure in state WAIT_IPACC_CRCX_ACK: Received > > NACK on IPACC CRCX > > > You received a IPACC CRCX NACK from nanoBTS as an answer to IPACC_CRCX > (that's sent osmoBSc->nanoBTS to configure the RTP stream on the nanoBTS > side). > So it seems the nanoBTS is not liking the configuration you are > requesting to it? > Providing a pcap file containing Abis RSL would help understand better > by looking at what the IPACC CRCX contains. > I'd bet you are passing a loopback address to it or something similar, > probably due to wrong osmo-mgw configuration. > > -- > - Pau Espin Pedrol <pespin at 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 Director: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: dump_call_abis.pcap Type: application/octet-stream Size: 8846 bytes Desc: not available URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210730/0dcba690/attachment.obj>