tree 78d97f9540eb50e1abc5c4bfb025963bc5a652c7
parent d74cce266bbc6ec519376601a2004f4fa8155b64
author Holger Hans Peter Freyther <holger@moiji-mobile.com> 1444635455 +0200
committer Holger Hans Peter Freyther <holger@moiji-mobile.com> 1444635455 +0200

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.