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/gerrit-log@lists.osmocom.org/.
neels gerrit-no-reply at lists.osmocom.orgneels has submitted this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/17532 ) Change subject: manual: add SCCPlite section ...................................................................... manual: add SCCPlite section Change-Id: I8eddc47353d6afd756865321a9e97f6cee4ce2d7 --- M doc/manuals/chapters/running.adoc 1 file changed, 32 insertions(+), 1 deletion(-) Approvals: laforge: Looks good to me, but someone else must approve neels: Looks good to me, approved Jenkins Builder: Verified diff --git a/doc/manuals/chapters/running.adoc b/doc/manuals/chapters/running.adoc index fe99780..eeefa6c 100644 --- a/doc/manuals/chapters/running.adoc +++ b/doc/manuals/chapters/running.adoc @@ -73,7 +73,9 @@ === Configure primary links -==== Configure SCCP/M3UA to connect to an MSC's _A_ interface +==== Connect to an MSC's _A_ interface + +===== Configure SCCP/M3UA (AoIP) OsmoBSC acts as client to contact an STP instance and establish an SCCP/M3UA link. @@ -96,6 +98,35 @@ This configuration is explained in detail in <<cs7_config>>. +===== Configure SCCPlite + +Traditionally, OsmoBSC implemented only an SCCPlite based A-interface, an +ad-hoc standard encapsulating BSSAP in an IPA Multiplex. Since 2017, OsmoBSC +supports primarily a proper 3GPP compliant SCCP/M3UA A-interface known as AoIP, +by a new libosmo-sigtran implementation. In 2018, SCCPlite compatibility was +added to libosmo-sigtran, re-enabling the option of using an SCCPlite based +A-interface. For details, see the OsmoSTP manual, chapter "IPA / SCCPlite +backwards compatibility". + +Here is an example configuration of OsmoBSC for SCCPlite, assuming the BSC at +point-code 1.23.3 and an SCCPlite MSC listening on 127.0.0.1:5000 with own +point-code 0.23.1: + +---- +cs7 instance 0 + point-code 1.23.3 + asp asp-clnt-msc-0 5000 0 ipa + remote-ip 127.0.0.1 + as as-clnt-msc-0 ipa + asp asp-clnt-msc-0 + routing-key 0 1.23.3 + point-code override dpc 0.23.1 + sccp-address remote_msc + point-code 0.23.1 +msc 0 + msc-addr remote_msc +---- + ==== Configure MGCP to connect to an MGW OsmoBSC uses a media gateway (typically OsmoMGW) to direct RTP streams. By -- To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/17532 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-bsc Gerrit-Branch: master Gerrit-Change-Id: I8eddc47353d6afd756865321a9e97f6cee4ce2d7 Gerrit-Change-Number: 17532 Gerrit-PatchSet: 5 Gerrit-Owner: neels <nhofmeyr at sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge at osmocom.org> Gerrit-Reviewer: neels <nhofmeyr at sysmocom.de> Gerrit-MessageType: merged -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20200330/fec36c3a/attachment.htm>