osmo-mgw

mirror of https://gitea.osmocom.org/cellular-infrastructure/osmo-mgw.git synced 2025-10-23 08:12:01 +00:00

Go to file

Holger Hans Peter Freyther f3316e30d6 mgcp: Use the right bind addresses for NET and BTS

This API is a bit unfortunate as the caller will also
access the endpoint directly. E.g. like this:

        output = bsc_mgcp_rewrite(...,
                      mgcp_net_src_addr(endp),
                      endp->net_end.local_port, -1,

In terms of "terminology" the "net" was meant to be bad
internet and the "bts" is the local and trusted network
segment. With this terminology the "bts" would be the
call-agent/MGW and "net" where the BSCs will send data
to but that is not the case and terminology actuallys
refers to:

	* net: The addresses exposed to the entity that
	made the MGCP call
	* bts: The system where we get our data for the
	local audio flow.

Fix the method but leave the API as it is. Use the net_end
in the net_src method and the bts_end in the bts_src method.

2015-10-12 09:37:35 +02:00

debian

debian: Attempt to fix packaging and point to a meaningful readme

2015-09-24 16:45:21 +02:00

hlrsync

hlrsync: Sync SMS from the web db to the hlr.

2009-08-14 21:33:34 +02:00

linux-kernel

new kernel patch for multiple virtual interfaces

2009-08-10 23:36:53 +02:00

openbsc

mgcp: Use the right bind addresses for NET and BTS