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/.
Kristian Martens kristian.martens at ng4t.comHi Harald, thank you for your answer. Yes, the call agent requests a new connection to the MGW. And it gets an answer. Mostly it fails, and suddenly, one time, it was OK and I wanted to find out the reason for this strange behaviour (see attached pcap). I also wanted to have the log output inside the specific log file. So do I need to specify the log file section again in the osmo-bsc-mgcp.cfg as it is in osmo-bsc.cfg? Could this be the reason why I do not find MGCP log messages in it? Thanks, Kristian Am 06.12.2016 um 11:16 schrieb Harald Welte: > Hi Kristian, > > the log file looks fine. All "DMGCP" log lines, especially from > openbsc/src/libmgcp/*.c should now be visible. > > The big question now is: Does your MSC actually issue MGCP towards the > BSC? Do you get answers from the BSC (i.e. any sign of the BSC > processing them) but still you see no related log output? > > Regards, > Harald -- *Kristian Martens* Software Engineer Office: +49 30 65218529 / ng4T GmbH Siemensdamm 50 13629 Berlin Germany www.ng4t.com <http://www.ng4t.com> / Berlin-Charlottenburg, HRB 123546 Geschäftsführer Dr. Andreas Kallmann -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20161206/0df1b2a2/attachment.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: sysmo_fail_ok_mgcp.pcapng Type: application/octet-stream Size: 9932 bytes Desc: not available URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20161206/0df1b2a2/attachment.obj>