Project

General

Profile

Osmo-sip-connector » History » Version 77

laforge, 03/23/2018 10:37 AM
update sip+bsc+msc graph with OsmoMGW

1 1 msuraev
h1. Osmo-sip-connector
2
3 63 dexter
{{>toc}}
4
5 18 dexter
h2. Introduction
6
7 64 dexter
osmo-sip-connector translates between MNCC and SIP protocols and hereby replaces the old LCR based approach. Osmo-sip-connector does not handle RTP by itself, an external SIP-PBX server which can accept SIP-Trunks is still required. The following image illustrates how the network components are laid out:
8 1 msuraev
9 74 laforge
h2. osmo-sip-connector with [[OsmoNITB:]]
10
11 64 dexter
{{graphviz_link()
12
digraph G{
13 76 laforge
  "osmo-sip-connector" [color="red"];
14 64 dexter
  rankdir = LR;
15
  MS -> BTS [label = "Um"];
16
  BTS -> "osmo-nitb" [label = "Abis"];
17
  "osmo-nitb" -> "osmo-sip-connector" [label = "MNCC"];
18 66 dexter
  "osmo-sip-connector" -> "PBX" [label = "SIP"];
19
  "BTS" -> "PBX" [label = "RTP"];
20 64 dexter
}
21
}}
22
23 74 laforge
h2. osmo-sip-connector with [[OsmoBSC:]] and [[OsmoMSC:]]
24
25
{{graphviz_link()
26
digraph G{
27
  rankdir = LR;
28 1 msuraev
  "osmo-sip-connector" [color="red"];
29 77 laforge
  OsmoMGWB [label="OsmoMGW\n(BSC)"];
30
  OsmoMGWM [label="OsmoMGW\n(MSC)"];
31 74 laforge
  MS -> BTS [label = "Um"];
32
  BTS -> OsmoBSC [label = "Abis"];
33
  OsmoBSC -> OsmoMSC [label = "AoIP" ];
34 1 msuraev
  OsmoMSC -> "osmo-sip-connector" [label = "MNCC"];
35
  "osmo-sip-connector" -> "PBX" [label = "SIP"];
36 77 laforge
  BTS -> OsmoMGWB [label = "RTP"];
37
  OsmoMGWB -> OsmoMGWM [label = "RTP"];
38
  OsmoMGWM -> "PBX" [label = "RTP"];
39
  OsmoBSC -> OsmoMGWB [label = "MGCP" ];
40
  OsmoMSC -> OsmoMGWM [label = "MGCP" ];
41
  { rank = same; OsmoBSC; OsmoMGWB; }
42
  { rank = same; OsmoMSC; OsmoMGWM; }
43 74 laforge
}
44
}}
45 64 dexter
46 75 laforge
{{include(cellular-infrastructure:MacroBinaryPackages)}}
47
48
h2. Manuals
49
50
Unfortunately, contrary to other Osmocom network elements, there is no user manual available yet at http://ftp.osmocom.org/docs/latest/
51
52 65 dexter
h2. Howto
53 8 dexter
54 64 dexter
This howto was created and tested using Debian 8.7.1. It is assumed, that a working installation of osmo-nitb already exists. In the following steps we will show how to integrate that existing installation with Asterisk using osmo-sip-connector.
55 71 dexter
56 72 dexter
Note: All configuration files discussed below can also be found in the attachement section
57 41 dexter
58 21 dexter
h3. Preparations
59
60 57 dexter
As we assume that we use an existing and working osmo-nitb configuration as a starting point most of the relevant dependencies are already installed. However, we still miss osmo-sip-connector and Asterisk as a major components.
61 23 dexter
62 28 dexter
* Install dependancies:
63 21 dexter
The extension we are about to make requires to install some additional packages.
64
<pre>
65
sudo apt-get install libsofia-sip-ua-glib-dev
66
sudo apt-get install asterisk
67 1 msuraev
</pre>
68 21 dexter
69 28 dexter
* Install osmo-sip-connector:
70 21 dexter
The installation of osmo-sip-connector is as straight forward as you know it already from other osmocom projects:
71
<pre>
72
git clone git://git.osmocom.org/osmo-sip-connector.git
73
cd osmo-sip-connector/
74
autoreconf -fi
75
./configure
76
make
77
sudo make install
78
</pre>
79 27 dexter
80
81 37 dexter
h3. Osmo-sip-connector configuration
82 1 msuraev
83 57 dexter
In this section we illustrate how equip osmo-nitb with a SIP-trunk interface using osmo-sip-connector. The steps are not necessarly Asterisk dependant, the result would work with any PBX software that supports sip-trunk connections.
84 40 dexter
85 28 dexter
* Osmo-nitb:
86 27 dexter
Osmo-nitb does not require any change of of its configuration. The connection between osmo-sip-connector is configured using the command line option “-M”:
87
<pre>
88 1 msuraev
osmo-nitb -c ./openbsc.cfg -d option –debug=DRLL:DCC:DMM:DRR:DRSL:DNM -M /tmp/bsc_mncc
89
</pre>
90
The “-M” option disables the internal call control handler of osmo-nitb and offers an unix domain socket, where an external call control handler can be connected. In the described situation this will be osmo-sip-connector.
91 28 dexter
92 50 dexter
* osmo-sip-connector:
93 61 dexter
Osmo-sip connector acts as a translator between the classic ISDN call control (mncc) and SIP. The configuration is rather simple.
94 28 dexter
<pre>
95
app
96
mncc
97
  socket-path /tmp/bsc_mncc
98
sip
99
  local 10.9.1.110 5069
100
  remote 10.9.1.110 5060
101
</pre>
102 57 dexter
Again, we have to setup a socket path. This path has to be the same as we provided with the commandline option “-M” for osmo-nitb earlier. For SIP we need to setup a remote and local IP-Address and port. In most cases, Asterisk and osmo-sip-connector will run on one and the same machine, so it is ovious that local and remote IP-Address are the same. The type of connection between osmo-sip-connector and Asterisk is a classic SIP-Trunk. For Asterisk it appears as just another PBX. Osmo-sip-connector is started via commandline as follows:
103 28 dexter
<pre>
104
osmo-sip-connector -c ./osmo-sip-connector.cfg
105
</pre>
106 1 msuraev
107 32 dexter
108 1 msuraev
h3. Asterisk configuration
109
110
The following section will discuss a minimal Asterisk configuration that is able to route calls between mobile phones. The described case assumes a freshly installed Asterisk with virgin configuration files. In the following we will edit extensions.conf and sip.conf which can be found in the /etc/asterisk directory. The example below is not special to GSM, its rather a normal SIP-trunk configuration.
111
112
* Set up the sip-trunk towards osmo-sip-connector:
113
The first that has to be taken care of is the connection to osmo-sip-connector. The following lines need be appended to sip.conf:
114
<pre>
115
[GSM]
116
type=friend
117
host=10.9.1.110
118
dtmfmode=rfc2833
119
canreinvite=no
120 37 dexter
disallow=all
121 32 dexter
allow=gsm
122 57 dexter
context=gsmsubscriber
123 32 dexter
port=5069
124 36 dexter
</pre>
125 51 dexter
The connection is named GSM, this name will be used later to reference the connection when routing outgoing calls. The context name “gsmsubscriber” references the context where mobile originated calls are routed into the dialplan.
126 32 dexter
127
128
* Set up a dialplan to route calls:
129
Now Asterisk and osmo-sip-connector are connected. The following example introduces a very basic dialplan configuration to route calls between mobile phones. The following example can be added to extensions.conf:
130
<pre>
131
[gsmsubscriber]
132
exten=>_XXXXX,1,Dial(SIP/GSM/${EXTEN})
133
exten=>_XXXXX,n,Playback(vm-nobodyavail)
134
exten=>_XXXXX,n,HangUp
135
</pre>
136
The name in “[]” is the context name which we already defined in sip.conf (“gsmsubscriber”). Every incoming call, that is entering through the “GSM” connection is directly routet to “[gsmsubscriber]”. The following three lines will check if the dialed number is exactly 5 digits long. When the check passes Asterisk dials that number through the “GSM” connection. This causes the call to be routed back through the “GSM” connection back to osmo-nitb. If the subscriber is not available, the call will fail and alternatively a voice message “vm-nobodyavail” will be played. Finally the call is hung up.
137 53 dexter
138 34 dexter
Note: In this example configuration security considerations are left out. It is up to the user to make sure that the SIP-Trunk interface is not reachable for unauthorized users. 
139
140 36 dexter
141 69 dexter
h3. Use Kamailio as an alternative to Asterisk
142 67 dexter
143 68 dexter
As already mentioned above it is also possible to use other SIP-PBX server than Astersik. One popular example is Kamailio. The attached kamailio.cfg matches the osmo-sip-connector configuration and conditions discussed above.
144
145
The configuration implements a SIP server which can be used to route calls between mobile phones. It also handles 2 special numbers 500 (routed to sip:music@iptel.org) and 600 (routed to sip:echo@iptel.org): by dialing them you can use echo test or hear nice music from your mobile.
146 67 dexter
147
*Note:* in attached kamailio.cfg, for 64bit systems, you may need to adjust
148
<pre>
149
mpath="/usr/lib/x86_64-linux-gnu/kamailio/modules/"
150
</pre>
151
152
N. B: Those numbers are meant only as an example for quick tests - please consider running your own Asterisk instance if you expect more than couple of calls, do not abuse http://www.iptel.org/service
153
154 70 dexter
See also https://www.kamailio.org
155 73 dexter
156
157
h2. Attachements
Add picture from clipboard (Maximum size: 48.8 MB)