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

Mike McTernan (wavemobile) mike.mcternan at wavemobile.com
Fri Aug 28 15:12:18 UTC 2015


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.

Please consider for inclusion to mainline.

Kind Regards,

Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20150828/e1db0a9e/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mgcp-endpoint-id.patch
Type: application/octet-stream
Size: 1313 bytes
Desc: mgcp-endpoint-id.patch
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20150828/e1db0a9e/attachment.obj>


More information about the OpenBSC mailing list