-
Notifications
You must be signed in to change notification settings - Fork 909
/
usrloc_admin.xml
1788 lines (1712 loc) · 48.7 KB
/
usrloc_admin.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
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding='ISO-8859-1'?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
<!-- Include general documentation entities -->
<!ENTITY % docentities SYSTEM "../../../../doc/docbook/entities.xml">
%docentities;
]>
<!-- Module User's Guide -->
<chapter>
<title>&adminguide;</title>
<section>
<title>Overview</title>
<para>
The User location module keeps a user location table and
provides access to the table for other modules. The module exports no
functions that can be used directly from routing scripts.
</para>
<section id="usrloc.o.contact-matching-algs">
<title>Contact matching</title>
<para>
How the contacts are matched (for the same AOR - Address of Record) is an
important aspect of the usrloc module, especially in the context of NAT
traversal - this raises more problems since contacts from different
phones of the same user may overlap (if both are behind NATs with the same
configuration) or the re-register contact of the same phone may be
seen as a new one (due different binding via NAT).
</para>
<para>
The SIP RFC 3261 publishes a matching algorithm based only on the
contact string with Call-id and Cseq extra checking (if the Call-ID
is the same, it must have a higher Cseq number, otherwise it is invalid).
But as argued above, this is not enough in NAT traversal context,
so the &kamailio; implementation of contact matching offers more algorithms:
</para>
<itemizedlist>
<listitem>
<para>
<emphasis>Contact based only</emphasis> - it is strict RFC 3261
compliancy - the Contact URI is matched as string and extra checked
via Call-ID and cseq (if Call-ID is the same, it must have a
higher cseq number, otherwise it is invalid).
</para>
</listitem>
<listitem>
<para>
<emphasis>Contact and Call-id based</emphasis> - it is an extension
of the first case - the contact and Call-ID must be matched as
string; the cseq must be higher than the previous one - so be
careful how you deal with REGISTER retransmissions in this
case.
</para>
</listitem>
<listitem>
<para>
<emphasis>contact and path based</emphasis> - it is an extension
of the first case - the contact and path must be matched as
string; the cseq must be higher than the previous one - so be
careful how you deal with REGISTER retransmissions in this
case.
</para>
</listitem>
<listitem>
<para>
<emphasis>Call-id only based</emphasis> - it is not
according to RFC3261, as it will check the Call-ID only
(independent of the Contact-Header or Path).
</para>
</listitem>
</itemizedlist>
<para>
To find out how to control/select the contact matching algorithm, please see the
module parameter matching_mode - <xref linkend="usrloc.p.matching_mode"/>.
</para>
</section>
</section>
<section>
<title>Dependencies</title>
<section>
<title>&kamailio; Modules</title>
<para>
The following modules must be loaded before this module:
<itemizedlist>
<listitem>
<para>
<emphasis>Optionally a database module</emphasis>.
</para>
</listitem>
</itemizedlist>
</para>
</section>
<section>
<title>External Libraries or Applications</title>
<para>
The following libraries or applications must be installed before
running &kamailio; with this module loaded:
<itemizedlist>
<listitem>
<para>
<emphasis>None</emphasis>.
</para>
</listitem>
</itemizedlist>
</para>
</section>
</section>
<section>
<title>Parameters</title>
<section id="usrloc.p.nat_bflag">
<title><varname>nat_bflag</varname> (int)</title>
<para>
The index of the branch flag to be used as NAT marker (if the contact
is or not natted). This is a branch flag and it will be imported and
used by all other modules depending of usrloc module.
</para>
<para>
<emphasis>
Default value is <quote>not set</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>nat_bflag</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "nat_bflag", 3)
...
</programlisting>
</example>
</section>
<section id="usrloc.p.user_column">
<title><varname>user_column</varname> (string)</title>
<para>
Name of database column containing usernames.
</para>
<para>
<emphasis>
Default value is <quote>username</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>user_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "user_column", "username")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.domain_column">
<title><varname>domain_column</varname> (string)</title>
<para>
Name of database column containing domains.
</para>
<para>
<emphasis>
Default value is <quote>domain</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>user_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "domain_column", "domain")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.contact_column">
<title><varname>contact_column</varname> (string)</title>
<para>
Name of database column containing contacts.
</para>
<para>
<emphasis>
Default value is <quote>contact</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>contact_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "contact_column", "contact")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.expires_column">
<title><varname>expires_column</varname> (string)</title>
<para>
Name of database column containing expires value.
</para>
<para>
<emphasis>
Default value is <quote>expires</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>expires_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "expires_column", "expires")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.q_column">
<title><varname>q_column</varname> (string)</title>
<para>
Name of database column containing q values.
</para>
<para>
<emphasis>
Default value is <quote>q</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>q_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "q_column", "q")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.callid_column">
<title><varname>callid_column</varname> (string)</title>
<para>
Name of database column containing Call-ID values.
</para>
<para>
<emphasis>
Default value is <quote>callid</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>callid_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "callid_column", "callid")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.cseq_column">
<title><varname>cseq_column</varname> (string)</title>
<para>
Name of database column containing Cseq.
</para>
<para>
<emphasis>
Default value is <quote>cseq</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>cseq_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "cseq_column", "cseq")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.methods_column">
<title><varname>methods_column</varname> (string)</title>
<para>
Name of database column containing supported methods.
</para>
<para>
<emphasis>
Default value is <quote>methods</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>methods_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "methods_column", "methods")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.flags_column">
<title><varname>flags_column</varname> (string)</title>
<para>
Name of database column to save the internal flags of the record.
</para>
<para>
<emphasis>
Default value is <quote>flags</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>flags_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "flags_column", "flags")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.cflags_column">
<title><varname>cflags_column</varname> (string)</title>
<para>
Name of database column to save the branch/contact flags of the record.
</para>
<para>
<emphasis>
Default value is <quote>cflags</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>cflags_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "cflags_column", "cflags")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.user_agent_column">
<title><varname>user_agent_column</varname> (string)</title>
<para>
Name of database column containing user-agent values.
</para>
<para>
<emphasis>
Default value is <quote>user_agent</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>user_agent_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "user_agent_column", "user_agent")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.received_column">
<title><varname>received_column</varname> (string)</title>
<para>
Name of database column containing the source IP, port, and protocol from the REGISTER
message.
</para>
<para>
<emphasis>
Default value is <quote>received</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>received_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "received_column", "received")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.socket_column">
<title><varname>socket_column</varname> (string)</title>
<para>
Name of database column containing the received socket information (IP:port)
for the REGISTER message.
</para>
<para>
<emphasis>
Default value is <quote>socket</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>socket_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "socket_column", "socket")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.path_column">
<title><varname>path_column</varname> (string)</title>
<para>
Name of database column containing the Path header.
</para>
<para>
<emphasis>
Default value is <quote>path</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>path_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "path_column", "path")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.ruid_column">
<title><varname>ruid_column</varname> (string)</title>
<para>
Name of database column containing the Kamailio record unique id.
</para>
<para>
<emphasis>
Default value is <quote>ruid</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>ruid_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "ruid_column", "myruid")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.instance_column">
<title><varname>instance_column</varname> (string)</title>
<para>
Name of database column containing the SIP instance ID (GRUU - RFC5627).
This is a unique device identifier - UUID.
</para>
<para>
<emphasis>
Default value is <quote>instance</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>instance_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "instance_column", "myinstance")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.reg_id_column">
<title><varname>reg_id_column</varname> (string)</title>
<para>
Name of database table column containing the value for reg-id.
</para>
<para>
<emphasis>
Default value is <quote>reg_id</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>reg_id_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "reg_id_column", "r_id")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.server_id_column">
<title><varname>server_id_column</varname> (string)</title>
<para>
Name of database table column containing the value for server id.
</para>
<para>
<emphasis>
Default value is <quote>server_id</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>server_id_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "server_id_column", "srv_id")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.connection_id_column">
<title><varname>connection_id_column</varname> (string)</title>
<para>
Name of database table column containing the value for connection id.
</para>
<para>
<emphasis>
Default value is <quote>connection_id</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>connection_id_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "connection_id_column", "con_id")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.keepalive_column">
<title><varname>keepalive_column</varname> (string)</title>
<para>
Name of database table column containing the value for keepalive status.
</para>
<para>
<emphasis>
Default value is <quote>keepalive</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>keepalive_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "keepalive_column", "kalive")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.partition_column">
<title><varname>partition_column</varname> (string)</title>
<para>
Name of database table column containing the value for partition id.
</para>
<para>
<emphasis>
Default value is <quote>partition</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>partition_column</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "partition_column", "part")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.use_domain">
<title><varname>use_domain</varname> (int)</title>
<para>
If the domain part of the user should be also saved and used for
identifying the user (along with the username part). Useful in
multi domain scenarios. Non 0 value means true.
</para>
<para>
<emphasis>
Default value is <quote>0 (false)</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>use_domain</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "use_domain", 1)
...
</programlisting>
</example>
</section>
<section id="usrloc.p.desc_time_order">
<title><varname>desc_time_order</varname> (int)</title>
<para>
If the user's contacts should be kept timestamp ordered; otherwise the
contact will be ordered based on q value.
Non 0 value means true.
</para>
<para>
<emphasis>
Default value is <quote>0 (false)</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>desc_time_order</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "desc_time_order", 1)
...
</programlisting>
</example>
</section>
<section id="usrloc.p.timer_interval">
<title><varname>timer_interval</varname> (int)</title>
<para>
Number of seconds between two timer runs. The module uses a timer to
delete expired contacts, synchronize with database, send keepalives
and other tasks, that need to be run periodically.
</para>
<para>
<emphasis>
Default value is 60.
</emphasis>
</para>
<example>
<title>Set <varname>timer_interval</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "timer_interval", 120)
...
</programlisting>
</example>
</section>
<section id="usrloc.p.db_url">
<title><varname>db_url</varname> (string)</title>
<para>
&url; of the database that should be used.
</para>
<para>
<emphasis>
Default value is <quote>&defaultdb;</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>db_url</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "db_url", "&exampledb;")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.db_mode">
<title><varname>db_mode</varname> (int)</title>
<para>
The usrloc module can utilize a database for persistent contact storage.
If a database is used, the location database (contacts) will survive
machine restarts or software crashes. The disadvantage is that accessing
a database can be very time consuming. Therefore, usrloc module implements
four database accessing modes:
</para>
<itemizedlist>
<listitem>
<para>
0 - This disables database completely. Only memory will be used.
Contacts will not survive restart. Use this value if you need a
really fast usrloc and contact persistence is not necessary or
is provided by other means.
</para>
</listitem>
<listitem>
<para>
1 - Write-Through scheme. All changes to usrloc are immediately
reflected in database too. This is very slow, but very reliable.
Use this scheme if speed is not your priority but need to make
sure that no registered contacts will be lost during crash or
reboot.
</para>
</listitem>
<listitem>
<para>
2 - Write-Back scheme. This is a combination of previous two
schemes. All changes are made to memory and database
synchronization is done in the timer. The timer deletes all
expired contacts and flushes all modified or new contacts to
database. Use this scheme if you encounter high-load peaks
and want them to process as fast as possible. The mode will
not help at all if the load is high all the time. Also, latency
of this mode is much lower than latency of mode 1, but slightly
higher than latency of mode 0.
</para>
</listitem>
<listitem>
<para>
3 - DB-Only scheme. No memory cache is kept, all operations being
directly performed with the database. The timer deletes all
expired contacts from database - cleans after clients that didn't
un-register or re-register. The mode is useful if you configure
more servers sharing the same DB without any replication at SIP
level. The mode may be slower due the high number of DB operation.
For example NAT pinging is a killer since during each ping cycle
all natted contact are loaded from the DB; The lack of memory
caching also disable the statistics exports.
</para>
</listitem>
<listitem>
<para>
4 - This uses database to load records at startup but uses only
memory during the runtime. Records are not written back at all,
not even at shutdown. Useful for scenarios when registrations are
replicated to a node that does the storage in database during
runtime.
</para>
</listitem>
</itemizedlist>
<warning>
<para>
In case of crash or restart contacts that are in memory only and
haven't been flushed yet will get lost. If you want minimize the
risk, use shorter timer interval.
</para>
</warning>
<para>
<emphasis>
Default value is 0.
</emphasis>
</para>
<example>
<title>Set <varname>db_mode</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "db_mode", 2)
...
</programlisting>
</example>
</section>
<section id="usrloc.p.db_load">
<title><varname>db_load</varname> (int)</title>
<para>
Determine if the usrloc module should load contacts from the database storage during module initialization
A value of 0 disable the loading from the database, this parameter is ignored if db_mode 4 is set
</para>
<para>
<emphasis>
Default value is 1.
</emphasis>
</para>
<example>
<title>Set <varname>db_load</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "db_load", 0)
...
</programlisting>
</example>
</section>
<section id="usrloc.p.db_insert_update">
<title><varname>db_insert_update</varname> (int)</title>
<para>
Determine if the usrloc module should do an update when a duplicate key is found while inserting
A value of 1 will activate update on duplicate key
</para>
<para>
<emphasis>
Default value is 0.
</emphasis>
</para>
<example>
<title>Set <varname>db_insert_update</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "db_insert_update", 1)
...
</programlisting>
</example>
</section>
<section id="usrloc.p.matching_mode">
<title><varname>matching_mode</varname> (int)</title>
<para>
What contact matching algorithm to be used. Refer to section
<xref linkend="contact-matching-algs"/> for the description of the
algorithms.
</para>
<para>
The parameter may take the following values:
</para>
<itemizedlist>
<listitem>
<para><emphasis>0</emphasis> - CONTACT ONLY based matching
algorithm.
</para>
</listitem>
<listitem>
<para><emphasis>1</emphasis> - CONTACT and CALLID based
matching algorithm.
</para>
</listitem>
<listitem>
<para><emphasis>2</emphasis> - CONTACT and PATH based
matching algorithm. This mode is like mode <emphasis>0</emphasis>
but allows for duplicate contacts from differing paths.
If no path is available, it defaults to mode 0.
</para>
</listitem>
<listitem>
<para><emphasis>3</emphasis> - CALLID only based
matching algorithm. This mode will discard any duplicate
registration coming through different paths.
</para>
</listitem>
</itemizedlist>
<para>
<emphasis>
Default value is <emphasis>0 (CONTACT_ONLY)</emphasis>.
</emphasis>
</para>
<example>
<title>Set <varname>matching_mode</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "matching_mode", 1)
...
</programlisting>
</example>
</section>
<section id="usrloc.p.cseq_delay">
<title><varname>cseq_delay</varname> (int)</title>
<para>
Delay (in seconds) for accepting as retransmissions register requests
with same Call-ID and Cseq. The delay is calculated starting from the
receiving time of the first register with that Call-ID and Cseq.
</para>
<para>
Retransmissions within this delay interval will be accepted and replied
as the original request, but no update will be done in location. If the
delay is exceeded, error is reported.
</para>
<para>
A value of 0 disable the retransmission detection.
</para>
<para>
<emphasis>
Default value is <quote>20 seconds</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>cseq_delay</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "cseq_delay", 5)
...
</programlisting>
</example>
</section>
<section id="usrloc.p.fetch_rows">
<title><varname>fetch_rows</varname> (int)</title>
<para>
The number of the rows to be fetched at once from database
when loading the location records. This value can be used
to tune the load time at startup. For 1MB of private memory (default)
it should be below 4000. The database driver must support
fetch_result() capability.
</para>
<para>
<emphasis>
Default value is <quote>2000</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>fetch_rows</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "fetch_rows", 3000)
...
</programlisting>
</example>
</section>
<section id="usrloc.p.hash_size">
<title><varname>hash_size</varname> (int)</title>
<para>
The number of entries of the hash table used by usrloc to store the
location records is 2^hash_size. For hash_size=4, the number of slots
of the hash table is 16.
</para>
<para>
<emphasis>
Default value is <quote>10</quote> (1024 slots).
</emphasis>
</para>
<example>
<title>Set <varname>hash_size</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "hash_size", 12)
...
</programlisting>
</example>
</section>
<section id="usrloc.p.preload">
<title><varname>preload</varname> (string)</title>
<para>
Preload location table given as value. A location table is loaded
based on fixup of registrar functions, therefore you need to use this
parameter only to load tables that are not used by registrar module
directly in configuration file.
</para>
<para>
<emphasis>
Default value is <quote>NULL</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>preload</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "preload", "location")
...
</programlisting>
</example>
</section>
<section id="usrloc.p.db_update_as_insert">
<title><varname>db_update_as_insert</varname> (int)</title>
<para>
Set this parameter if you want to do INSERT DB operations
instead of UPDATE DB operations. It is recommended to set this parameter
if you use Cassandra as a DB backend.
</para>
<para>
<emphasis>
Default value is <quote>0</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>db_update_as_insert</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "db_update_as_insert", 1)
...
</programlisting>
</example>
</section>
<section id="usrloc.p.db_check_update">
<title><varname>db_check_update</varname> (int)</title>
<para>
Set this parameter to 1 if you want to do DB INSERT if the number
of affected rows by contact DB UPDATE operation is 0. The
database module driver has to implement affected_rows() DB API
function, otherwise this parameter is ignored - e.g., MySQL and
Postgres DB connectors offer affected_rows().
</para>
<para>
<emphasis>
Default value is <quote>0</quote> (no DB INSERT).
</emphasis>
</para>
<example>
<title>Set <varname>db_check_update</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "db_check_update", 1)
...
</programlisting>
</example>
</section>
<section id="usrloc.p.timer_procs">
<title><varname>timer_procs</varname> (int)</title>
<para>
Number of timer processes to be started by module. Timer processes
take care of checking expired records and synchronization with
database. If set to 0, no dedicated timer is started, the one from
core will be used.
</para>
<para>
If the number of timer processes is greater than 1, the workload
of synchronization and record expiration is split up among the
multiple processes. (Each process is assigned a range of slots
from the internal hash table, and is responsible for cleanup and
storage on those slots.)
</para>
<para>
<emphasis>
Default value is <quote>0</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>timer_procs</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("usrloc", "timer_procs", 4)
...
</programlisting>
</example>
</section>
<section id="usrloc.p.xavp_contact">
<title><varname>xavp_contact</varname> (string)</title>
<para>