Project

General

Profile

Cellmgr ng » History » Version 2

zecke2, 02/19/2016 10:48 PM

1 1 zecke2
2 2 zecke2
h2. The cellmgr_ng project
3 2 zecke2
4 2 zecke2
5 1 zecke2
The cellmgr_ng was initially written to allow to hook a BTS/BSC behind a traditional E1 link
6 1 zecke2
with MTPL1, MTPL2, MTPL3 to a soft switch supporting the the ipaccess protocol. The MTPL1
7 1 zecke2
and MTPL2 is handled by a vendor solution right now, everything starting from MTPL3 is
8 1 zecke2
available in source. The code supports interfacing with the hardware encoders and can send
9 1 zecke2
and receive RTP with AMR and is controlled with the MGCP protocol.
10 1 zecke2
11 2 zecke2
12 2 zecke2
h3. Applications ===
13 2 zecke2
 cellmgr_ng ====
14 1 zecke2
This application implements forwarding of SCCP from the MTPL3 linkset to the IPA protocol,
15 1 zecke2
it supports connection tracking to work around implementation problems of various BSCs
16 1 zecke2
and to handle the event of network disconnection without taking the MTP Linkset down.
17 1 zecke2
18 2 zecke2
19 2 zecke2
h4. udt_relay
20 2 zecke2
21 1 zecke2
A simple version of the cellmgr_ng that just relays between the MTPL3 linkset and the
22 1 zecke2
connection to a MSC or similiar system.
23 1 zecke2
24 2 zecke2
25 2 zecke2
h4. osmo_stp
26 2 zecke2
27 1 zecke2
This a Signalling Transfer Point or a Media Gateway. It can handle a MTP L3 linkset and
28 1 zecke2
a M2UA connection. Right now it does not support fail over in M2UA but this can be added
29 1 zecke2
easily. It has basic support for ISUP blocking/unblocking/reset.
30 1 zecke2
31 2 zecke2
32 2 zecke2
h4. mgcp_mgw
33 2 zecke2
34 2 zecke2
Use the [[OpenBSC]] MGCP Protocol and Network implementation and interface with the
35 1 zecke2
hardware to provide the gateway from E1/T1 to IP/RTP.
Add picture from clipboard (Maximum size: 48.8 MB)