Project

General

Profile

Osmo-sip-connector » History » Version 74

laforge, 10/21/2017 03:16 PM

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
  rankdir = LR;
14
  MS -> BTS [label = "Um"];
15
  BTS -> "osmo-nitb" [label = "Abis"];
16
  "osmo-nitb" -> "osmo-sip-connector" [label = "MNCC"];
17 66 dexter
  "osmo-sip-connector" -> "PBX" [label = "SIP"];
18
  "BTS" -> "PBX" [label = "RTP"];
19 64 dexter
}
20
}}
21
22 74 laforge
23
h2. osmo-sip-connector with [[OsmoBSC:]] and [[OsmoMSC:]]
24
25
{{graphviz_link()
26
digraph G{
27
  rankdir = LR;
28
  MS -> BTS [label = "Um"];
29
  BTS -> OsmoBSC [label = "Abis"];
30
  OsmoBSC -> OsmoMSC [label = "AoIP" ];
31
  OsmoMSC -> "osmo-sip-connector" [label = "MNCC"];
32
  "osmo-sip-connector" -> "PBX" [label = "SIP"];
33
  "BTS" -> "PBX" [label = "RTP"];
34
}
35
}}
36 64 dexter
37 65 dexter
h2. Howto
38 8 dexter
39 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.
40 71 dexter
41 72 dexter
Note: All configuration files discussed below can also be found in the attachement section
42 41 dexter
43 21 dexter
h3. Preparations
44
45 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.
46 23 dexter
47 28 dexter
* Install dependancies:
48 21 dexter
The extension we are about to make requires to install some additional packages.
49
<pre>
50
sudo apt-get install libsofia-sip-ua-glib-dev
51
sudo apt-get install asterisk
52 1 msuraev
</pre>
53 21 dexter
54 28 dexter
* Install osmo-sip-connector:
55 21 dexter
The installation of osmo-sip-connector is as straight forward as you know it already from other osmocom projects:
56
<pre>
57
git clone git://git.osmocom.org/osmo-sip-connector.git
58
cd osmo-sip-connector/
59
autoreconf -fi
60
./configure
61
make
62
sudo make install
63
</pre>
64 27 dexter
65
66 37 dexter
h3. Osmo-sip-connector configuration
67 1 msuraev
68 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.
69 40 dexter
70 28 dexter
* Osmo-nitb:
71 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”:
72
<pre>
73 1 msuraev
osmo-nitb -c ./openbsc.cfg -d option –debug=DRLL:DCC:DMM:DRR:DRSL:DNM -M /tmp/bsc_mncc
74
</pre>
75
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.
76 28 dexter
77 50 dexter
* osmo-sip-connector:
78 61 dexter
Osmo-sip connector acts as a translator between the classic ISDN call control (mncc) and SIP. The configuration is rather simple.
79 28 dexter
<pre>
80
app
81
mncc
82
  socket-path /tmp/bsc_mncc
83
sip
84
  local 10.9.1.110 5069
85
  remote 10.9.1.110 5060
86
</pre>
87 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:
88 28 dexter
<pre>
89
osmo-sip-connector -c ./osmo-sip-connector.cfg
90
</pre>
91 1 msuraev
92 32 dexter
93 1 msuraev
h3. Asterisk configuration
94
95
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.
96
97
* Set up the sip-trunk towards osmo-sip-connector:
98
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:
99
<pre>
100
[GSM]
101
type=friend
102
host=10.9.1.110
103
dtmfmode=rfc2833
104
canreinvite=no
105 37 dexter
disallow=all
106 32 dexter
allow=gsm
107 57 dexter
context=gsmsubscriber
108 32 dexter
port=5069
109 36 dexter
</pre>
110 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.
111 32 dexter
112
113
* Set up a dialplan to route calls:
114
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:
115
<pre>
116
[gsmsubscriber]
117
exten=>_XXXXX,1,Dial(SIP/GSM/${EXTEN})
118
exten=>_XXXXX,n,Playback(vm-nobodyavail)
119
exten=>_XXXXX,n,HangUp
120
</pre>
121
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.
122 53 dexter
123 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. 
124
125 36 dexter
126 69 dexter
h3. Use Kamailio as an alternative to Asterisk
127 67 dexter
128 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.
129
130
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.
131 67 dexter
132
*Note:* in attached kamailio.cfg, for 64bit systems, you may need to adjust
133
<pre>
134
mpath="/usr/lib/x86_64-linux-gnu/kamailio/modules/"
135
</pre>
136
137
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
138
139 70 dexter
See also https://www.kamailio.org
140 73 dexter
141
142
h2. Attachements
Add picture from clipboard (Maximum size: 48.8 MB)