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/.
Dmitri Soloviev dmi3sol at gmail.comThank you but there are few things still unclear: - why at A-bis interface BSC issues ip.accessMDCX with ip=0.0.0.0? is there anything configured improperly? - so, UDP port is BSC side is predicted. but an endpoint at BTS side is dynamically allocated.. is there a way to inform osmo-BSC_mgcp, or it just replies to RTP from BTS? On Sun, Aug 25, 2013 at 4:02 PM, Holger Hans Peter Freyther < holger at freyther.de> wrote: > On Sun, Aug 25, 2013 at 02:51:12PM +0400, Dmitri Soloviev wrote: > > Hi list, > > > > But it seems two interfaces are working completely independent: > > yes, they just share one secret on how to go from endpoint number > to rtp port. > > > holger > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20130825/484f4f59/attachment.htm>