[PATCH] openbsc: unhardwire MGCP endpoint id

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/.

Holger Freyther holger at freyther.de
Fri Aug 28 15:46:59 UTC 2015


> On 28 Aug 2015, at 17:12, Mike McTernan (wavemobile) <mike.mcternan at wavemobile.com> wrote:
> 
> Hi Folks,
>  
> At present endpoint IDs are assumed to end with @mgw when trying to find/match non-e1 endpoint ids.  Unless the MGCP peer supports compatible configuration, DNS or a hosts file may need to be setup to meet the hardwired host name requirement in the openBsc MGCP, and then we can still only run one BSC.
>  
> The attached patch makes a simple change to use either the configured local_ip or source_addr, matching logic used in SDP responses.  It also improves the error message when an endpoint can’t be found.
> 

the cellmgr-ng had a more complete object model (vtrunks, e1 id..) but what about simplifying
the code and just checking for the ‘@‘? If somebody addresses us. E.g. the hostname on the
existing deployments is not ‘mgw’ and unless I am missing something neither cfg->local_ip
nor cfg->source_addr hold “mgw” as name?

Any reason not to remove the hostname check?

holger




More information about the OpenBSC mailing list