Osmocom Open Build Service

osmo-sip-connector.spec Changed

osmo-sip-connector_1.6.2.1.c65f.202303220007.dsc -> osmo-sip-connector_1.6.2.3.95312.202303230005.dsc Changed

@@ -2,7 +2,7 @@
 Source: osmo-sip-connector
 Binary: osmo-sip-connector, osmo-sip-connector-dbg, osmo-sip-connector-doc
 Architecture: any all
-Version: 1.6.2.1.c65f.202303220007
+Version: 1.6.2.3.95312.202303230005
 Maintainer: Osmocom team <openbsc@lists.osmocom.org>
 Homepage: https://osmocom.org/projects/osmo-sip-conector/wiki
 Standards-Version: 3.8.4
@@ -14,8 +14,8 @@
  osmo-sip-connector-dbg deb debug extra arch=any
  osmo-sip-connector-doc deb doc optional arch=all
 Checksums-Sha1:
- b1a26ca3a22cc13a0955fba5e58b62a8c033488a 68116 osmo-sip-connector_1.6.2.1.c65f.202303220007.tar.xz
+ d2b0307ee3348d0105066b2b472a8378be1b0f6f 68520 osmo-sip-connector_1.6.2.3.95312.202303230005.tar.xz
 Checksums-Sha256:
- 2fbd89a4a603007c7bb5a1eaf2880e922dd1e4a6453b69adb8ce6cf37545888c 68116 osmo-sip-connector_1.6.2.1.c65f.202303220007.tar.xz
+ a8776b585d00d4a06fef52bd7cdffbb8e917ce353b2ed4e4ff034312fdc82a29 68520 osmo-sip-connector_1.6.2.3.95312.202303230005.tar.xz
 Files:
- 6e951df0557dffca4c48169e708f56a6 68116 osmo-sip-connector_1.6.2.1.c65f.202303220007.tar.xz
+ 33dfb1854cae6101d8b96a9a43d36b3e 68520 osmo-sip-connector_1.6.2.3.95312.202303230005.tar.xz

osmo-sip-connector_1.6.2.1.c65f.202303220007.tar.xz/.tarball-version -> osmo-sip-connector_1.6.2.3.95312.202303230005.tar.xz/.tarball-version Changed

osmo-sip-connector_1.6.2.1.c65f.202303220007.tar.xz/contrib/osmo-sip-connector.spec.in -> osmo-sip-connector_1.6.2.3.95312.202303230005.tar.xz/contrib/osmo-sip-connector.spec.in Changed

osmo-sip-connector_1.6.2.1.c65f.202303220007.tar.xz/debian/changelog -> osmo-sip-connector_1.6.2.3.95312.202303230005.tar.xz/debian/changelog Changed

osmo-sip-connector_1.6.2.1.c65f.202303220007.tar.xz/debian/control -> osmo-sip-connector_1.6.2.3.95312.202303230005.tar.xz/debian/control Changed

@@ -17,7 +17,7 @@
 
 Package: osmo-sip-connector
 Architecture: any
-Depends: osmocom-nightly (= 202303220007), ${shlibs:Depends}, ${misc:Depends}
+Depends: osmocom-nightly (= 202303230005), ${shlibs:Depends}, ${misc:Depends}
 Description: MNCC to SIP bridge for osmo-nitb
  Use the osmo-nitb MNCC interface and bridge it to SIP.
 
@@ -25,7 +25,7 @@
 Architecture: any
 Section: debug
 Priority: extra
-Depends: osmocom-nightly (= 202303220007), osmo-sip-connector (= ${binary:Version}), ${misc:Depends}
+Depends: osmocom-nightly (= 202303230005), osmo-sip-connector (= ${binary:Version}), ${misc:Depends}
 Description: Debug symbols for the osmo-sip-connector
  Make debugging possible
 
@@ -33,7 +33,7 @@
 Architecture: all
 Section: doc
 Priority: optional
-Depends: osmocom-nightly (= 202303220007), ${misc:Depends}
+Depends: osmocom-nightly (= 202303230005), ${misc:Depends}
 Description: ${misc:Package} PDF documentation
  Various manuals: user manual, VTY reference manual and/or
  protocol/interface manuals.

osmo-sip-connector_1.6.2.1.c65f.202303220007.tar.xz/doc/manuals/chapters/overview.adoc -> osmo-sip-connector_1.6.2.3.95312.202303230005.tar.xz/doc/manuals/chapters/overview.adoc Changed

@@ -8,7 +8,7 @@
 === About OsmoSIPConnector
 
 OsmoSIPConnector translates between Mobile Network Call Control (MNCC)
-used in the GSM newtwork and Voice over IP SIP call control messages so that
+used in the GSM network and Voice over IP SIP call control messages so that
 speech calls can traverse through the mobile network to SIP and vice versa. It
 has the following interfaces:
 
@@ -16,6 +16,27 @@
 - SIP towards the PBX
 - The Osmocom typical telnet VTY interface.
 
+The SIP implemented by osmo-sip-connector can be characterized as follows:
+
+Only a SIP trunk is supported; it will appear to the remote SIP server (PBX) like
+another PBX (or a public network) interfaced via a trunk.  Specifically, this means
+there is no SIP REGISTER or any form of authentication supported.  You
+will need to configure the SIP peer to implicitly authorize the trunk by
+its IP address / port.
+
+osmo-sip-connector handles only the signaling translation between GSM CC
+and SIP, but does not handle RTP. The RTP user plane is passed
+transparently from the MSC-colocated osmo-mgw to the SIP side. This also
+means that no transcoding is performed. The RTP streams contain whatever
+cellular specific codec you have configured your network to use for this
+call (FR, EFR, HR, AMR).  Hence, **the SIP peer must support the
+codecs you have configured on your MSC/BSC**
+
+As the osmo-sip-connector attaches to the external MNCC socket of
+OsmoMSC, running osmo-sip-connector will disable the internal call
+routing of OsmoMSC, see the related OsmoMSC documentation.  All mobile
+originated calls originating in GSM will be passed to the SIP connector.
+
 Find the OsmoSIPConnector issue tracker and wiki online at
 
 - https://osmocom.org/projects/osmo-sip-connector

Changes of Revision 276