File: control

package info (click to toggle)
osmo-msc 1.13.0%2Bdfsg1-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 5,968 kB
  • sloc: ansic: 44,489; python: 1,046; makefile: 950; sh: 118
file content (49 lines) | stat: -rw-r--r-- 1,761 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
Source: osmo-msc
Section: net
Priority: optional
Maintainer: Debian Mobcom Maintainers <Debian-mobcom-maintainers@lists.alioth.debian.org>
Uploaders: Thorsten Alteholz <debian@alteholz.de>,
           Ruben Undheim <ruben.undheim@gmail.com>,
           Nate Doris <nate.doris@gmail.com>
Build-Depends: debhelper-compat (=13)
	, autoconf
	, automake
	, libtool
	, pkgconf
	, libdbi-dev
	, libdbd-sqlite3
	, libsmpp34-dev (>= 1.14.0)
	, osmo-libasn1c-dev (>= 0.9.28)
	, libosmocore-dev (>= 1.10.0)
	, libosmo-sccp-dev (>= 1.9.0)
	, libosmo-sigtran-dev (>= 2.1.0)
	, libosmo-abis-dev (>=2.0.0)
	, libosmo-mgcp-client-dev (>= 1.14.0)
	, libosmo-netif-dev (>= 1.5.0)
	, libosmo-ranap-dev (>= 1.7.0)
	, libosmo-gsup-client-dev (>= 1.9.0)
	, libsctp-dev
	, libssl-dev
	, libsqlite3-dev
	, help2man
Standards-Version: 4.7.0
Vcs-Browser: https://salsa.debian.org/debian-mobcom-team/osmo-msc
Vcs-Git: https://salsa.debian.org/debian-mobcom-team/osmo-msc.git
Homepage: https://osmocom.org/projects/osmomsc
Rules-Requires-Root: no

Package: osmo-msc
Architecture: any
Multi-Arch: foreign
Depends: ${misc:Depends}, ${shlibs:Depends}
Description: Osmocom's Mobile Switching Center for 2G and 3G mobile networks
 The Mobile Switching Center (MSC) is the heart of 2G/3G
 circuit-switched services.  It terminates the A-interface links from the
 Base Station Controllers (BSC) and handles the MM and CC sub-layers of
 the Layer 3 protocol from the phones (MS).
 .
 This Osmocom implementation of the MSC handles A interfaces via 3GPP
 AoIP in an ASP role.  It furthermore implements IETF MGCP against an
 external media gateway, such as OsmoMGW.  It does *not* implement MAP
 towards a HLR, but the much simpler Osmocom GSUP protocol, which can
 be translated to MAP if needed.