forked from asipto/kamailio-devel-guide
-
Notifications
You must be signed in to change notification settings - Fork 0
/
c15timer.xml
293 lines (285 loc) · 6.96 KB
/
c15timer.xml
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
<chapter id="c15timer">
<title>Timer</title>
<para>
&kamailio; provides internal timers with millisecond precision. It offers developer API to:
</para>
<itemizedlist>
<listitem>
<para>
register functions to be run every 1 second or interval of multiple seconds
</para>
</listitem>
<listitem>
<para>
register functions to run every millisecond or interval of multiple milliseconds
</para>
</listitem>
<listitem>
<para>
start a new timer process
</para>
</listitem>
</itemizedlist>
<para>
The timer API is implemented in the files <emphasis role="strong">timer.{c,h}</emphasis>. If
you want to extend the timer API you have to start with those files. We focus on how to add
new functions to be run by timer. The timer is available after shared memory initialization.
</para>
<section id="c15data_types">
<title>Data Types</title>
<para>
The functions that can be given as callbacks for timer have the following prototypes:
</para>
<programlisting format="linespecific">
...
typedef unsigned long long utime_t;
typedef void (timer_function)(unsigned int ticks, void* param);
...
</programlisting>
<para>
Parameters are:
</para>
<itemizedlist>
<listitem>
<para>
ticks - number of second ticks elapsed at the moment of running the function
</para>
</listitem>
<listitem>
<para>
param - parameter given when registering the callback function
</para>
</listitem>
</itemizedlist>
</section>
<section id="c15functions">
<title>Timer API Functions</title>
<para>
Register a function to be executed by second-based timer:
</para>
<programlisting format="linespecific">
...
int register_timer(timer_function f, void* param, unsigned int interval);
...
</programlisting>
<para>
Parameters:
</para>
<itemizedlist>
<listitem>
<para>
f - callback function
</para>
</listitem>
<listitem>
<para>
param - parameter to callback function
</para>
</listitem>
<listitem>
<para>
interval - interval to execute the callback function
</para>
</listitem>
</itemizedlist>
<para>
Register a function to start a new timer process:
</para>
<programlisting format="linespecific">
...
int register_timer_process(timer_function f, void* param, unsigned int interval);
...
</programlisting>
<para>
Parameters:
</para>
<itemizedlist>
<listitem>
<para>
f - callback function
</para>
</listitem>
<listitem>
<para>
param - parameter to callback function
</para>
</listitem>
<listitem>
<para>
interval - interval to execute the callback function
</para>
</listitem>
</itemizedlist>
<para>
There are two functions that return the number of ticks elapsed since &kamailio; started,
one returning time in seconds and the other one returning the number of internal ticks.
</para>
<programlisting format="linespecific">
...
unsigned int get_ticks(void);
utime_t get_ticks_raw(void);
...
</programlisting>
</section>
<section id="c15example">
<title>Example of usage</title>
<para>
Next we will show how the module <emphasis role="strong">msilo</emphasis> register a timer
function to clean the stored messages. See
<emphasis role="strong">modules/msilo/msilo.c</emphasis>.
</para>
<programlisting format="linespecific">
...
#include "../../timer.h"
...
void m_clean_silo(unsigned int ticks, void *);
...
</programlisting>
<para>
Registration to the second-based timer is done in function
<emphasis role="strong">mod_init()</emphasis>.
</para>
<programlisting format="linespecific">
...
register_timer(m_clean_silo, 0, ms_check_time);
...
</programlisting>
<para>
Function implementation is:
</para>
<programlisting format="linespecific">
...
<![CDATA[
/**
* - cleaning up the messages that got reply
* - delete expired messages from database
*/
void m_clean_silo(unsigned int ticks, void *param)
{
msg_list_el mle = NULL, p;
db_key_t db_keys[MAX_DEL_KEYS];
db_val_t db_vals[MAX_DEL_KEYS];
db_op_t db_ops[1] = { OP_LEQ };
int n;
LM_DBG("cleaning stored messages - %d\n", ticks);
msg_list_check(ml);
mle = p = msg_list_reset(ml);
n = 0;
while(p)
{
if(p->flag & MS_MSG_DONE)
{
#ifdef STATISTICS
if(p->flag & MS_MSG_TSND)
update_stat(ms_dumped_msgs, 1);
else
update_stat(ms_dumped_rmds, 1);
#endif
db_keys[n] = &sc_mid;
db_vals[n].type = DB1_INT;
db_vals[n].nul = 0;
db_vals[n].val.int_val = p->msgid;
LM_DBG("cleaning sent message [%d]\n", p->msgid);
n++;
if(n==MAX_DEL_KEYS)
{
if (msilo_dbf.delete(db_con, db_keys, NULL, db_vals, n) < 0)
LM_ERR("failed to clean %d messages.\n",n);
n = 0;
}
}
if((p->flag & MS_MSG_ERRO) && (p->flag & MS_MSG_TSND))
{ /* set snd time to 0 */
ms_reset_stime(p->msgid);
#ifdef STATISTICS
update_stat(ms_failed_rmds, 1);
#endif
}
#ifdef STATISTICS
if((p->flag & MS_MSG_ERRO) && !(p->flag & MS_MSG_TSND))
update_stat(ms_failed_msgs, 1);
#endif
p = p->next;
}
if(n>0)
{
if (msilo_dbf.delete(db_con, db_keys, NULL, db_vals, n) < 0)
LM_ERR("failed to clean %d messages\n", n);
n = 0;
}
msg_list_el_free_all(mle);
/* cleaning expired messages */
if(ticks%(ms_check_time*ms_clean_period)<ms_check_time)
{
LM_DBG("cleaning expired messages\n");
db_keys[0] = &sc_exp_time;
db_vals[0].type = DB1_INT;
db_vals[0].nul = 0;
db_vals[0].val.int_val = (int)time(NULL);
if (msilo_dbf.delete(db_con, db_keys, db_ops, db_vals, 1) < 0)
LM_DBG("ERROR cleaning expired messages\n");
}
}
]]>
...
</programlisting>
<para>
The function deletes from database the messages that were succesfully delivered and the
messages that were stored for too long time in database and the recipient was not online
or not able to receive them.
</para>
</section>
<section id="c15dedicated_timer">
<title>Dedicated timer process</title>
<para>
Sometime might be better to have your own timer process, not to disturb the operations
done by other timer function - recommended when you are doing operation that may take a
while on timer basis.
</para>
<para>
You can create as many timer processes as you need - it takes two steps:
</para>
<itemizedlist>
<listitem>
<para>
in mod_init() tell to timer API how many processes you want to create
</para>
</listitem>
<listitem>
<para>
in child_init() for MAIN child, fork the timer processes with the callback function
</para>
</listitem>
</itemizedlist>
<programlisting format="linespecific">
...
/**
* init module function
*/
static int mod_init(void)
{
...
register_dummy_timers(1);
...
}
...
/**
* init module children
*/
static int child_init(int rank)
{
...
if (rank==PROC_MAIN)
{
if(fork_dummy_timer(PROC_TIMER, "MY MOD TIMER", 1 /*socks flag*/,
my_timer_callback, my_timer_param, 1 /*sec*/) < 0) {
LM_ERR("failed to register timer routine as process\n");
return -1; /* error */
}
}
...
}
...
</programlisting>
</section>
</chapter>