-
Notifications
You must be signed in to change notification settings - Fork 4
/
sems.txt
316 lines (278 loc) · 8.66 KB
/
sems.txt
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
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
[prev in list] [next in list] [prev in thread] [next in thread]
List: sems
Subject: Re: [Sems] SEMS as SBC in front of kamailio
From: <kai.ohnacker () cbc ! de>
Date: 2015-05-20 10:01:46
Message-ID: 5A4C35A70604964FBD46890CC952D954259EABFF () MANA1 ! netrtlsrv ! com
[Download message RAW]
Hello,
thanks for the example and the explaining Stefan. I change the example to my setup \
and try to make a call.
If I call from external to internal network the call establish and voice is \
transmitted. (Sometimes the connection goes down) A Call from internal to external \
does not work. On the destination side, the incoming call (from internal to external) \
displays no audio codec and the call finished after 5 seconds. In the SIP header the \
CSeq shows a Bye sequence. I change the expire timers to higher and lower value, but \
the behavior was the same.
One further information from the debugging information is that the uac_auth.conf \
can't be found in /usr/local/etc/sems/etc/. And yes, there is no uac_auth.conf file. \
:-) Do I need a uac_client.conf file?
What could be the problem of my config?
Thanks for helping.
Cheers, Kai
-----Ursprüngliche Nachricht-----
Von: Stefan Sayer [mailto:stefan.sayer@frafos.com]
Gesendet: Montag, 18. Mai 2015 13:17
An: Ohnacker, Kai [CBC]; sems@lists.iptel.org
Betreff: Re: AW: [Sems] SEMS as SBC in front of kamailio
Hello,
there's indeed some misunderstandings regarding profile configuration,
but there's also some configuration items that you seem to have
invented (enable_reg_lookup ??). While you may have now figured it out
by yourself, here FTR a set of configurations. You right, though, if
you're saying that the configuration is a bit convoluted. My testing
setup is
SEMS listening at 192.168.6.110:5060 ("external interface")
SEMS listening at 192.168.5.110:5080 ("internal interface")
registrar at 192.168.5.110:5060
clients registering to username@192.168.6.110, I'm setting the RURI
domain so that my registrar does accept it.
Note that this works only with SEMS master
(apparently-eternally-to-be-1.6, from
https://github.com/sems-server/sems.git)
sems.conf
--------------
interfaces=intern,extern
sip_ip_intern=192.168.5.110
sip_port_intern=5080
media_ip_intern=192.168.5.110
rtp_low_port_intern=10000
rtp_high_port_intern=20000
sip_ip_extern=192.168.6.110
sip_port_extern=5060
media_ip_extern=192.168.6.110
rtp_low_port_extern=20000
rtp_high_port_extern=30000
public_ip_extern=192.168.6.110
# sig_sock_opts_extern=force_via_address
# tcp_connect_timeout_extern=1000
# tcp_idle_timeout_extern=900000
application=sbc
-----------------
sbc.conf
-----------------
profiles=exin,inex,reg
# load one regex-mapping for method, one for interface (here: received IP)
regex_maps=method_map,interface_map
# first try method (REGISTER), then map on received interface (here:
received IP)
active_profile=$M($m=>method_map),$M($Ri=>interface_map)
-----------------
method_map.conf
-----------------
REGISTER=>reg
-----------------
interface_map.conf
-----------------
192\.168\.5\.110=>inex
192\.168\.6\.110=>exin
-----------------
reg.sbcprofile.conf
-----------------
# registration cache
enable_reg_caching=yes
# register upstream every 3600 sec
min_reg_expires=3600
# and make UA re-register every 60 sec
max_ua_expires=60
next_hop=192.168.5.110:5060
# setting RURI here to registrar, in order to make my registrar accept it
# if it's DNS name, the registrar should accept it without modification
RURI=sip:192.168.5.110
-----------------
exin.sbcprofile.conf
-----------------
# SIP NAT handling: recommended if dealing with far end NATs
dlg_nat_handling=yes
# destination IP[:port] for outgoing requests
next_hop=192.168.5.110:5060
#10.99.250.26:5060
## RTP relay
# enable RTP relaying (bridging):
enable_rtprelay=yes
# setting RURI domain here to proxy (in case of domain name, not
necessary...)
RURI=sip:$rU@192.168.5.110
-----------------
inex.sbcprofile.conf
-----------------
enable_reg_caching=yes
-----------------
hth
Stefan
kai.ohnacker@cbc.de wrote on 05/12/2015 09:47 AM:
> Hello Stefan,
> sorry for spaming, I've forgot to include the third profile.
>
> Now the complete configure.
>
> "I try to make the setup like you said, but the SEMS server in the middle response \
> with 501 Not Implemented if a client is trying to register.
> My config is:
>
> -----sbc.conf-----
> profiles=sst_b2b, exin, inex, reg
> active_profile=$M($RI=>exin), $M($Rn=>inex)
>
> -----exin.conf-----
> REGISTER=>reg
>
> # SIP NAT handling: recommended if dealing with far end NATs
> dlg_nat_handling=yes
>
> # destination IP[:port] for outgoing requests
> next_hop=10.99.250.26:5060
>
> ## RTP relay
> # enable RTP relaying (bridging):
> enable_rtprelay=yes
>
> -----inex.conf-----
> enable_reg_lookup=yes
>
> -----reg.conf-----
> # registration cache
> enable_reg_caching=yes
> # register upstream every 3600 sec
> min_reg_expires=3600
> # and make UA re-register every 60 sec
> max_ua_expires=60
>
> sems.conf
> load_plugins=wav;uac_auth;registrar_client;reg_agent;sbc;session_timer; \
> conference;reg;exin;inex application = conference
>
> Perhaps I do not understand the profile syntax in the right way?"
>
> Cheers,
> Kai
>
> -----Ursprüngliche Nachricht-----
> Von: sems-bounces@lists.iptel.org [mailto:sems-bounces@lists.iptel.org] Im Auftrag \
> von kai.ohnacker@cbc.de
> Gesendet: Montag, 11. Mai 2015 11:27
> An: stefan.sayer@frafos.com; sems@lists.iptel.org
> Betreff: Re: [Sems] SEMS as SBC in front of kamailio
>
> Hey Stefan,
>
> thanks for you answer.
> I try to make the setup like you said, but the SEMS server in the middle response \
> with 501 Not Implemented if a client is trying to register.
> My config is:
>
> -----sbc.conf-----
> profiles=sst_b2b, exin, inex, reg
> active_profile=$M($RI=>exin), $M($Rn=>inex)
>
> -----exin.conf-----
> REGISTER=>reg
>
> # SIP NAT handling: recommended if dealing with far end NATs
> dlg_nat_handling=yes
>
> # destination IP[:port] for outgoing requests
> next_hop=10.99.250.26:5060
>
> ## RTP relay
> # enable RTP relaying (bridging):
> enable_rtprelay=yes
>
> -----inex.conf-----
> enable_reg_lookup=yes
>
>
> Perhaps I do not understand the profile syntax in the right way?
>
> Cheers,
> Kai
>
> -----Ursprüngliche Nachricht-----
> Von: Stefan Sayer [mailto:stefan.sayer@frafos.com]
> Gesendet: Freitag, 8. Mai 2015 16:40
> An: Ohnacker, Kai [CBC]; sems@lists.iptel.org
> Betreff: Re: [Sems] SEMS as SBC in front of kamailio
>
> Hello Kai,
>
> kai.ohnacker@cbc.de wrote on 05/07/2015 03:08 PM:
> > Hello,
> >
> >
> >
> > I'm working actually on a project with a kamailio as registrar,
> > redirect and proxy server. For NATing I want to use SEMS and the
> > server shall work as a SBC, which forwards all messages (REGISTER,
> > INVITE etc.) from the external to the internal interface (SEMS work
> > with 2 interfaces) and vice versa. I configure the external/ internal
> > IP sockets in the sems.conf and load the required plugins. But what
> > are the next steps? Perhaps there is somewhere a howto, which guide me
> > through this process?
> >
> > The infrastructure is: Kamailio (private network) ---- Firewall/ NAT
> > ---- SEMS (DMZ - public network) ---- Firewall ---- internet (public
> > network)
> >
>
> For INVITEs you will need two profiles, one in each direction
> (UA->SEMS->Kamailio and Kamailio->SEMS->UA). For REGISTERs coming from
> the UAs you will need one more profile.
>
> The very first Paragraph in doc/Readme.sbc.txt gives some examples for
> selecting profiles, e.g. on regex; as key you can e.g. use source IP
> ($si) or also local/received IP ($Ri) or also the interface ($Rf, $Rn
> or $RI).
>
> For the REGISTERs, you need to activate registration caching using
> enable_reg_caching=yes.
>
> For the INVITE-profile towards Kamailio, you need to activate NAT
> handling (dlg_nat_handling, enable_rtprelay, ...), and set the next
> hop to Kamailio.
>
> For the INVITE profile coming from Kamailio, you need to activate the
> reg cache lookup, this will set the RURI/next hop from the reg cache.
>
> There is quite some more options that can be set in the profiles, I'd
> recommend to have a look at Readme.sbc.txt.
>
> hth
> Stefan
>
> >
> >
> >
> >
> > Cheers,
> >
> > Kai
> >
> >
> >
> > _______________________________________________
> > Sems mailing list
> > Sems@lists.iptel.org
> > http://lists.iptel.org/mailman/listinfo/sems
> >
>
> _______________________________________________
> Sems mailing list
> Sems@lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/sems
>
_______________________________________________
Sems mailing list
Sems@lists.iptel.org
http://lists.iptel.org/mailman/listinfo/sems
[prev in list] [next in list] [prev in thread] [next in thread]
Configure | About | News | Add a list | Sponsored by KoreLogic