- sr-users - kamailio.org

wiresharking TLS problem
by Rex Lin (林昱頡) 27 Mar '17

27 Mar '17

hi all wondering if any of you has the experience of TLS decrypting, SIP client has problem while calling each other, but we are using TLS for communication protocol.....facing problem debugging it..... Best Regards, Rex Lin

3 3

Regex module having trouble with large regex expressions in kamailio 4.4.5
by Tim Balmer 24 Mar '17

24 Mar '17

Hi, I discovered some strange behavior from the regex module yesterday (kamailio version 4.4.5). For example we have the phone number 0033755500381 that we try to match with the following kamailio code: #!define REGEX_FF_NEG_INTERNATIONAL "6" ... if (pcre_match_group("$rU", REGEX_FF_NEG_INTERNATIONAL)) { # Do something } When the content of our regex groups file is like this: [6] ^(\+|00)3(0690|0693|0694|0695|0697|0698|0699|36|37|4160|46|47|51160|511691|511693|511696|511891|511893|511896|513|516091|5160921|516093|516096|516391|516392|516393|516396|516591|516592|516593|516596|516691|5166921|516693|516696|5191|5192|5193|5196|538|54388|543 89|546|5475|5477|548|567117|5672|5677|5679|5692|5694|5696|5698|5699|5795|5796|5797|5799|58299|584|5850|5948|5987|5988|5989|59988|59989|620|630|631|670|706|712|725|728|774|776|8591|8592|8595|8597|8598|8599|8620|8621|8630|8631|8640|8641|8643|8649|8650|8651|8660| 8661|8664|8670|8671|869814|906698|93) The above if statment is not matching, although it should match according to any regex validator (for example https://regex101.com/ ) But when I split the above regex in smaller parts, like this: [6] ^(\+|00)306(90|93|94|95|97|98|99) ^(\+|00)336 ^(\+|00)337 ^(\+|00)34160 ^(\+|00)346 ^(\+|00)347 ^(\+|00)351(160|1691|1693|1696|1891|1893|1896|3|6091|60921|6093|6096|6391|6392|6393|6396|6591|6592|6593|6596|6691|66921|6693|6696|91|92|93|96) ^(\+|00)3538 ^(\+|00)354(388|389|6|75|77|8) ^(\+|00)356(7117|72|77|79|92|94|96|98|99) ^(\+|00)357(95|96|97|99) ^(\+|00)358(299|4|50) ^(\+|00)359(48|87|88|89|988|989) ^(\+|00)3620 ^(\+|00)363(0|1) ^(\+|00)3670 ^(\+|00)3706 ^(\+|00)3712 ^(\+|00)372(5|8) ^(\+|00)377(4|6) ^(\+|00)385(91|92|95|97|98|99) ^(\+|00)386(20|21|30|31|40|41|43|49|50|51|60|61|64|70|71|9814) ^(\+|00)3906698 ^(\+|00)393 Then the exact same regex module call as before does result in a match as expected. So to me it looks like the regex module is having trouble with large regex expressions, I did check the logs but there is nothing strange there, that means also the large expression is correctly loaded according to the logs while in fact it is not working. Checked the regex module documentation but there I cannot find any limits regarding to the size of invididual expressions. Is it me missing something or did I discover a bug in de regex module? Best Regards, Tim Balmer Edutel BV

2 2

Re: [SR-Users] Question on the debug change level command with 5.0.x
by Federico Cabiddu 24 Mar '17

24 Mar '17

No, you don't. The debugger module, among other things, allows to set the debug level per module. Regards, Federico On 23 Mar 2017 6:31 pm, "Ginhoux, Patrick" <patrick.ginhoux(a)fr.unisys.com> wrote: Hi, Thanks you so much; it works fine as expected. Now have I to keep the ‘debugger’ module lines in my config ? Cordialement Patrick GINHOUX *De :* sr-users [mailto:sr-users-bounces@lists.sip-router.org] *De la part de* Federico Cabiddu *Envoyé :* jeudi 23 mars 2017 17:38 *À :* Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org> *Objet :* Re: [SR-Users] Question on the debug change level command with 5.0.x Hi, you have to load the cfg_rpc module (http://www.kamailio.org/docs/ modules/5.0.x/modules/cfg_rpc.html). Then you can run kamcmd cfg.set_now_int core debug <LEVEL>. Regards, Federico On Thu, Mar 23, 2017 at 5:24 PM, Ginhoux, Patrick < patrick.ginhoux(a)fr.unisys.com> wrote: Hi, Previously, in my kamailio.cfg 3.3.1, the debug level is set using the ‘debug’ option. Then with the MI_FIFO module it was simple to change debug level on the flight using the simple command ‘kamctl fifo debug <new value>’. Moving to kamailio 5.0.x, there is no more MI_FIFO module. In the kamailio.cfg, I still have the ‘debug’ option set; so I’m looking for the command to use to change the debug level. I look at the debugger module that seems the solution. So I add the following lines in y script: debug=4 loadmodule "debugger.so" modparam("debugger", "log_level", 1) modparam("debugger", "mod_hash_size", 5) modparam("debugger", "mod_level_mode", 1) Then I try to use the following commands : This one retrieves the debug level set by the debug=4) : [root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.get_mod_level core 4 This one changed the debug level for the core module [root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.set_mod_level core 2 200 ok Same commands can be used for each of the module loaded: [root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.get_mod_level tm 4 [root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.set_mod_level tm 2 200 ok [root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.get_mod_level dispatcher 4 [root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.set_mod_level dispatcher 2 200 ok Each command only applies to a specific module. I don’t find a ‘global’ command that I could use in the same manner as the old ‘kamctl fifo debug’ command. Is there something I missed in my config ? Cordialement Patrick GINHOUX _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

2 1

Question on the debug change level command with 5.0.x
by Ginhoux, Patrick 23 Mar '17

23 Mar '17

Hi, Previously, in my kamailio.cfg 3.3.1, the debug level is set using the 'debug' option. Then with the MI_FIFO module it was simple to change debug level on the flight using the simple command 'kamctl fifo debug <new value>'. Moving to kamailio 5.0.x, there is no more MI_FIFO module. In the kamailio.cfg, I still have the 'debug' option set; so I'm looking for the command to use to change the debug level. I look at the debugger module that seems the solution. So I add the following lines in y script: debug=4 loadmodule "debugger.so" modparam("debugger", "log_level", 1) modparam("debugger", "mod_hash_size", 5) modparam("debugger", "mod_level_mode", 1) Then I try to use the following commands : This one retrieves the debug level set by the debug=4) : [root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.get_mod_level core 4 This one changed the debug level for the core module [root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.set_mod_level core 2 200 ok Same commands can be used for each of the module loaded: [root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.get_mod_level tm 4 [root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.set_mod_level tm 2 200 ok [root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.get_mod_level dispatcher 4 [root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.set_mod_level dispatcher 2 200 ok Each command only applies to a specific module. I don't find a 'global' command that I could use in the same manner as the old 'kamctl fifo debug' command. Is there something I missed in my config ? Cordialement Patrick GINHOUX

2 2

Presence + RLS + XCAP
by Paul Smith 23 Mar '17

23 Mar '17

Longer version of this got blocked by the mail list earlier today… and I have dug a bit deeper since then… I am trying to SUBSCRIBE to a resource-list (rls.so) but the rls_handle_subscribe() is returning with a “list not found" Mar 23 16:36:11 presence kamailio[12536]: DEBUG: rls [subscribe.c:211]: rls_get_service_list(): No rl document found Mar 23 16:36:11 presence kamailio[12536]: DEBUG: <core> [db_res.c:81]: db_free_columns(): freeing 2 columns Mar 23 16:36:11 presence kamailio[12536]: DEBUG: <core> [db_res.c:85]: db_free_columns(): freeing RES_NAMES[0] at 0x7f70b50ebee8 Mar 23 16:36:11 presence kamailio[12536]: DEBUG: <core> [db_res.c:85]: db_free_columns(): freeing RES_NAMES[1] at 0x7f70b50afb90 Mar 23 16:36:11 presence kamailio[12536]: DEBUG: <core> [db_res.c:94]: db_free_columns(): freeing result names at 0x7f70b50eaf98 Mar 23 16:36:11 presence kamailio[12536]: DEBUG: <core> [db_res.c:99]: db_free_columns(): freeing result types at 0x7f70b50cc0a0 Mar 23 16:36:11 presence kamailio[12536]: DEBUG: <core> [db_res.c:136]: db_free_result(): freeing result set at 0x7f70b50cc2d0 Mar 23 16:36:11 presence kamailio[12536]: DEBUG: rls [subscribe.c:634]: rls_handle_subscribe(): list not found - searched for uri <sip:org1a-contacts@**MYDOMAIN**> I have tried various permutations of xml docs in the xcap table for the rls-service and resource-list but nothing have not yet managed to get a success from the rls_handle_subscribe() Latest version of data in my mysql database / xcap table: | 3 | org1a-contacts | **MYDOMAIN** | <?xml version="1.0" encoding="UTF-8" standalone="no"?><resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists"><list name="team"><entry uri="sip:1002@**MYDOMAIN**"/><entry uri="sip:1001@**MYDOMAIN**"><display-name>bob</display-name></entry><entry uri="sip:1003@**MYDOMAIN**"><display-name>test1</display-name></entry><entry uri="sip:1006@**MYDOMAIN**"><display-name>test1006</display-name></entry><entry uri="sip:1007@**MYDOMAIN**"><display-name>test1007</display-name></entry><entry uri="sip:1008@**MYDOMAIN**"><display-name>test1008</display-name></entry><entry uri="sip:1009@**MYDOMAIN**"><display-name>test1009</display-name></entry> <entry uri="sip:1005@**MYDOMAIN**"><display-name>testing1005</display-name></entry> <entry uri="sip:org1a@**MYDOMAIN**"><display-name>testingorg1a</display-name></entry> <entry uri="sip:org1c@**MYDOMAIN**"><display-name>testingorg1c</display-name></entry> <entry uri="sip:dnd1002-6@presence.byphone.co.uk"><display-name>1002 dnd</display-name></entry></list></resource-lists> | 4 | sr-1490270411-10960-2 | 0 | /xcap-root/resource-lists/users/sip:org1a-contacts@**MYDOMAIN**/index | 0 | | 4 | org1a-contacts | **MYDOMAIN** | <?xml version="1.0" encoding="UTF-8" standalone="no"?><rls-services xmlns="urn:ietf:params:xml:ns:rls-services"><service uri="sip:org1a-contacts@**MYDOMAIN**"><list name="org1a-contacts"><rl:entry uri="1000_6@**MYDOMAIN**"/><rl:entry uri="org1c@**MYDOMAIN**"/></list><packages><package>presence</package></packages></service></rls-services> | 8 | sr-1490285288-12551-1 | 0 | /xcap-root/rls-services/users/sip:org1a-contacts@**MYDOMAIN**/index | 0 | Is there a reference doc somewhere with an example of a successful SUBSCRIBE and associated XCAP docs for a resource-list? Thanks Paul

1 0

failed to find append_branch
by Anuradha Selvarajan 23 Mar '17

23 Mar '17

Hello, I am a new user to kamailio. I am trying to use the fork.cfg to send sip registration to 2 destination. I get the following error but I have added loadmodule tm.so, why am I still getting this error? Mar 22 15:53:48 emps116 kamailio[14065]: ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command append_branch (params 1) Mar 22 15:53:48 emps116 kamailio[14065]: : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/fork.cfg, line 45, column 43: unknown command, mi Mar 22 15:53:48 emps116 kamailio[14065]: ERROR: bad config file (1 errors) Mar 22 15:53:48 emps116 kamailio[14065]: loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules Mar 22 15:53:48 emps116 kamailio[14065]: loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules/ Mar 22 15:53:48 emps116 kamailio[14065]: INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Mar 22 15:53:48 emps116 systemd[1]: kamailio.service: Control process exited, code=exited status=255 Mar 22 15:53:48 emps116 systemd[1]: Failed to start Kamailio (OpenSER) - the Open Source SIP Server. My script looks like this (default one): mpath="/usr/lib/x86_64-linux-gnu/kamailio/modules" loadmodule "sl.so" loadmodule "tm.so" . . . . route{ # for testing purposes, simply okay all REGISTERs if (method=="REGISTER") { log("REGISTER"); sl_send_reply("200", "ok"); exit; }; # try these two destinations first in parallel; the second # destination is targeted to sink port -- that will make ser # wait until timer hits seturi("sip:nobody@kamailio.org"); append_branch("sip:parallel@kamailio.org"); # if we do not get a positive reply, continue at reply_route[1] #t_on_failure("1"); # forward the request to all destinations in destination set now t_relay(); } Appreciate any help! Thanks Anu

3 3

Presence + RLS + XCAP
by Paul Smith 23 Mar '17

23 Mar '17

Hi I am struggling to figure out how to build and test an integrated presence server with Resource-List (rls.so) and XCAP (xcap_server.so). I am confused about what is meant to happen and how to debug it. Not sure if I am suffering from incompatibilities, configuration errors, or bugs… I have not found an up to date guide on configuring an integrated presence, rls, xcap server so I have used old tutorials, module documentation and some course code review … but I’m pretty confused now! I am using Snom phones and Jitsi (on Mac) to test. I have a kamailio Registrar which proxies all presence messages to the separate kamailio 4.2 Presence server. REQUIREMENT : Contact Presence ============================= I would like to get a SUBSCRIBE from the Snom phone to subscribe to a contact-list resource list, and to receive a NOTIFY with all of the presence states for those contacts. Relevant snom settings? Contact List URI: this generates a SUBSCRIBE with event:presence I believe that: ========== presence module should be managing the individual user presence and dialog states xcap module should allow me to use HTTP / curl to edit the resource lists rls module should be managing the mapping from a resource list subscription to the individual presence states and generating the aggregated NOTIFY messages. each device should then be able to SUBSCRIBE to a resource list uri and then receive an aggregated NOTIFY for all of the watched entities. Current status: =========== SUBSCRIBE sip:org1a-contacts@*****.co.uk <sip:org1a-contacts@*****.co.uk> SIP/2.0 v: SIP/2.0/UDP 192.168.1.15:59594;branch=z9hG4bK-qllzlgs3xf43;rport f: <sip:org1a@*****.co.uk <sip:org1a@*****.co.uk>>;tag=wwasqc6lmb t: <sip:org1a-contacts@****.co.uk <sip:org1a-contacts@****.co.uk>> i: 313439303236383530323234313530-x3hlb3j6b5ef CSeq: 1 SUBSCRIBE Max-Forwards: 70 User-Agent: snomD375/8.9.3.46 m: <sip:org1a@192.168.1.15:59594 <sip:org1a@192.168.1.15:59594>>;reg-id=1 Event: presence Accept: application/pidf+xml, application/rlmi+xml, multipart/related Supported: eventlist Expires: 3600 l: 0 … auth handshake SIP/2.0 202 OK Record-Route: <sip:10.210.160.13;r2=on;lr=on;ftag=wwasqc6lmb;nat=yes <sip:10.210.160.13;r2=on;lr=on;ftag=wwasqc6lmb;nat=yes>> Record-Route: <sip:**pubip**;r2=on;lr=on;ftag=wwasqc6lmb;nat=yes <sip:**pubip**;r2=on;lr=on;ftag=wwasqc6lmb;nat=yes>> v: SIP/2.0/UDP 192.168.1.15:59594;received=**recvip**;branch=z9hG4bK-8wufiv1ua3ne;rport=60554 f: <sip:org1a@****.co.uk <sip:org1a@****.co.uk>>;tag=wwasqc6lmb t: <sip:org1a-contacts@*****.co.uk <sip:org1a-contacts@*****.co.uk>>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-d30e i: 313439303236383530323234313530-x3hlb3j6b5ef CSeq: 2 SUBSCRIBE Expires: 3600 Contact: <sip:10.210.160.16:5060;transport=udp <sip:10.210.160.16:5060;transport=udp>> Server: kamailio (4.2.0 (x86_64/linux)) Content-Length: 0 … and then the snom receives an empty NOTIFY. NOTIFY sip:org1a@192.168.1.15:58325 <sip:org1a@192.168.1.15:58325> SIP/2.0 Via: SIP/2.0/UDP 109.104.108.18;branch=z9hG4bKc54a.20db45097fb44595ccd5a30827ca2a62.0 Via: SIP/2.0/UDP 10.210.160.16;rport=5060;branch=z9hG4bKc54a.40150886000000000000000000000000.0 To: <sip:org1a@****.co.uk <sip:org1a@****.co.uk>>;tag=sx4ne9jpcl From: <sip:org1a-contacts@*****.co.uk <sip:org1a-contacts@*****.co.uk>>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-ed89 CSeq: 2 NOTIFY Call-ID: 313439303237323938323235353133-2du221e6okvf Content-Length: 0 User-Agent: kamailio (4.2.0 (x86_64/linux)) Max-Forwards: 69 Event: presence Contact: <sip:10.210.160.16:5060;transport=udp;alias=10.210.160.16~5060~1 <sip:10.210.160.16:5060;transport=udp;alias=10.210.160.16~5060~1>> Subscription-State: active;expires=3600 The Subscription is showing up in the watchers table, not the rls_watchers table, so I believe it is being rejected by the rls_handle_subscribe() and then parsed by the presence module. Is that correct? There is noting in rls_watchers or rls_presentity tables. Should there be? I have a rows in the XCAP table for the Resource-List curl -d @/tmp/contacts-resource-list.xml -vvv -X PUT http://109.104.108.23:5060/xcap-root/resource-lists/users/sip:org1a-contact… <http://109.104.108.23:5060/xcap-root/resource-lists/users/sip:org1a-contact…> relevant row in xcap table: | 3 | org1a-contacts | *****.co.uk <http://co.uk/> | <?xml version="1.0" encoding="UTF-8" standalone="no"?><resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists"><list name="team"><entry uri="sip:1002@****.co.uk <http://co.uk/>"/><entry uri="sip:1001@****.co.uk <http://co.uk/>"><display-name>bob</display-name></entry><entry uri="sip:1003@****.co.uk <http://co.uk/>"><display-name>test1</display-name></entry><entry uri="sip:1006@****co.uk <http://co.uk/>"><display-name>test1006</display-name></entry><entry uri="sip:1007@****co.uk <http://co.uk/>"><display-name>test1007</display-name></entry><entry uri="sip:1008@h****.co.uk <http://co.uk/>"><display-name>test1008</display-name></entry><entry uri="sip:1009@****.co.uk <http://co.uk/>"><display-name>test1009</display-name></entry> <entry uri="sip:1005@****.co.uk <http://co.uk/>"><display-name>testing1005</display-name></entry> <entry uri=“sip:org1a@****.co.uk <http://co.uk/>"><display-name>testingorg1a</display-name></entry> <entry uri=“sip:org1c@****.co.uk <http://co.uk/>"><display-name>testingorg1c</display-name></entry></list></resource-lists> | 4 | sr-1490270411-10965-2 | 0 | /xcap-root/resource-lists/users/sip:org1a-contacts@****co.uk/index <http://co.uk/index> | 0 | I have rows in the presence table for the entities that I want to track e.g. | | | 2889 | org1c | ****.co.uk <http://co.uk/> | presence | a.1490270411.10942.42.1083 | 1490277099 | 1490273499 | <?xml version="1.0 " encoding="UTF-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:im="urn:ietf:params:xml:ns:pidf:im" entity=“pres:org1c@*****.co.uk <http://co.uk/>"> <tuple id="snom370-000413260935"> <status><basic>open</basic> <im:im <im:im>>Available</im:im> </status> <contact priority="1.00">sip:org1c@****.co.uk <http://co.uk/></contact> <note xml:lang="en">Available</note> </tuple></presence> I am running kamaiio 4.2 Question : Should I have an resource-services row too? Or does rls.so infer the relationship using the URI? When I use jitsi to manipulate its contact list it only inserts 2 rows into the xcap table and I cannot get a SIP Subscribe to connect to that resource list either. Question : What should the curl PUT commands and XML docs look like to build a valid RLS service (is there a good example anywhere)? Question : Is there an example config or doc anywhere showing how to build integrated presence, rls, xcap? Question : Has anyone got this working with Snom and or other handsets… the standards and implementations seem vague / inconsistent? Note: There is another Snom setting (Extension Monitoring Call Pickup List URI:) which produces a SUBSCRIBE with Event:dialog but which should allow a button/lamp/callpickup/BLF for the buddy contact. I’d like to get that working too, but recognise that rls.so does not handle dialog messages by default, so I’m starting with Presence... Paul Paul Smith 1 Lanyon Quay, Belfast, BT1 3LG UK: 02890270050 RoI: 1800855111 paul.smith(a)claritytele.com <mailto:paul.smith@claritytele.com%0b> www.claritytele.com <http://claritytele.com/> This email and any attachment, is confidential. If you have received this in error, please delete it from your system, do not use or disclose the information in any way, and notify me immediately. The contents of this message may contain personal views which are not the views of Clarity Telecom, unless specifically stated. > >> >>

1 0

Status of db_cassandra
by Markus Bönke 23 Mar '17

23 Mar '17

Hello, We are thinking about to use kamailio as a sip registrar with cassandra as db backend. As I can see in the documentation for kamailio 5.0 it is only tested with Casandra 1.1.6 and 1.0.1, current version is 3.10 in the meantime. Is anyone using this module with newer versions of Cassandra? Is it stable? Thanks and regards Markus

4 6

looks like dp_translate with pvs in repl_exp is badly broken
by Juha Heinanen 23 Mar '17

23 Mar '17

when match_exp of dp 100 is ^#test and repl_exp is sip:$rU@$rd this code: xlog("L_INFO", "****** ru = $ru\n"); dp_translate(100, "$rU/$var(res)"); xlog("L_INFO", "****** res = $var(res)\n"); produces: Mar 22 08:21:17 lohi /usr/bin/sip-proxy[7543]: INFO: ****** ru = sip:#test@test.tutpro.com Mar 22 08:21:17 lohi /usr/bin/sip-proxy[7543]: INFO: ****** res = sip:$rU@$rd -- juha

4 6

getting source IP from Contact header
by Ali Taher 22 Mar '17

22 Mar '17

Hello everyone, I'm trying to get the host part from the contact header in the sip invite packet. Following is the contact header format: Contact: <sip:user_name@192.168.1.1:5060> What I want as result is 192.168.1.1 I searched among the pseudovairables and found $ct variable which reference to the body of contact header. (<sip:user_name@192.168.1.1:5060>) Is there a way to get directly the host (192.168.1.1) without applying transformation at the level of $ct. If not what transformation can achieve it. Thanks in advance. Regards, Ali

3 2

Alternative of SIPp for WebRTC2SIP load-test
by Jade SZ 21 Mar '17

21 Mar '17

Hi Guys, SIPp is great in testing pure SIP udp/tcp/tls but I was wondering if there is a similar tool for stress testing Kamailio websocket2sip. I am trying to load-test webrtc2sip kamailio's implementation closest to the real scenario. One way would be to fork multiple process of webrtc2sip client in loop. But would really like to hear how are kamailio webrtc users/community load-testing it for benchmarking their servers. Also roughly how much CPS they have achieved using single kamailio with webrtc enabled (share server specs as well) Thanks in advance. Regards, JSZ

2 1

do we need high available IP for S-CSCF?
by Valentin Christoph 21 Mar '17

21 Mar '17

Hi all, Maybe I need a small hint. I have got a configuration of 2 S-CSCF instances (both kamailio 4.4.5 with S-CSCF configuration, each on a separate virtual machine) in load sharing mode (50:50). Both instances work on the same "scscf" data base, so that it is only one S-CSCF from a logical point of view. Now I get into troubles with registration: * P-CSCF sends REGISTER to first S-CSCF * First S-CSCF answers with 401 Unauthorized an challenges the UE. So far everything OK. * Second REGISTER is sent to second S-CSCF (DNS SRV Load Balancing). * Second S-CSCF answers again with 401 Unauthorized (Error) * This goes back and forth until UE gives up to register This problem exists sporadically (approx. every fifth registration). Now the question: is it worth to debug this configuration or should we rather switch to high available IP configuration (if we want to use kamailio)? What's your opinion/experiences? Thanks Christoph The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.

1 0

Siremis 4.3.0 with Apache 2.4
by kai.ohnacker＠cbc.de 21 Mar '17

21 Mar '17

Hello Community, I installed the Kamailio 4.4 and try to install the Siremis GUI based on apache 2.4. If I try to start the Siremis Wizard, the Webserver display the following line: "location.href='$url'"; exit; } ?>". The starting page of apache 2.4 is working fine, but the /siremis page doesn't. Due the installation I take the dedicated apache 2.4 commands. Are there some further requirements? Some ideas? OS: Ubuntu 16.04 Thanks a lot. Cheers, Kai

2 2

No cdr after Kamailio 5.0 restart
by Kordován Szabolcs 21 Mar '17

21 Mar '17

Hi, I use acc module for create cdr into db and also make acc log into db. After restart Kamailio cdr won't be created but acc log will be inserted into db. In the syslog also I see just the acc log. The dialog will be remove from db. I have read many threads. I know that it should work. Thanks for help! Regards, Szabolcs >From my configs: #!define FLT_ACC 1 #!define FLT_ACCMISSED 2 #!define FLT_ACCFAILED 3 modparam("acc", "db_url", DBURL) modparam("acc", "db_flag", FLT_ACC) modparam("acc", "db_missed_flag", FLT_ACCMISSED) modparam("acc", "db_extra", "src_user=$fU;src_domain=$fd;dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;src_ip=$si") modparam("acc", "log_level", 3) modparam("acc", "log_flag", FLT_ACC) modparam("acc", "log_missed_flag", FLT_ACCMISSED) modparam("acc", "report_ack", 1) modparam("acc", "report_cancels", 1) modparam("acc", "early_media", 1) modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) modparam("acc", "acc_prepare_always", 1) modparam("acc", "time_mode", 1) modparam("acc", "time_attr", "seconds") modparam("acc", "time_exten", "microsecs") modparam("acc", "reason_from_hf", 1) modparam("acc", "cdr_enable", 1) modparam("acc", "cdr_expired_dlg_enable", 1) modparam("acc", "cdr_start_on_confirmed", 1) modparam("acc", "cdrs_table", "acc_cdrs") modparam("acc", "cdr_on_failed", 1) modparam("acc", "cdr_extra", "callid=$ci;src_user=$dlg_var(fU);src_domain=$dlg_var(fd);dst_ouser=$dlg_var(tU);dst_user=$dlg_var(rU);dst_domain=$dlg_var(rd);src_ip=$dlg_var(si);peer_in=$dlg_var(peerin);peer_out=$dlg_var(peerout)") request_route { <------> <------>$var(loose) = loose_route(); <------>$var(check_trans) = t_check_trans(); <------>sip_trace(); <------>setflag(FLT_SIPTRACE); <------>dlg_manage(); <------># handle retransmissions <------>if(t_precheck_trans()) { <------> xlogl("LOG_LOCAL0", "L_ALERT", "================== kamaty $rm route $ci ==== $rm ==== precheck_trans exit\n"); <------> exit; <------>} <------>if(is_method("OPTIONS")) {. <------> # send reply for each options request. <------> sl_send_reply("200", "ok");. <------> exit();. <------>} <------># CANCEL processing <------>if (is_method("CANCEL")) { <------><------>if (t_check_trans()) { <------><------> route(RELAY); <------><------>} <------><------>exit; <------>} <------>if ( is_method("ACK") ) { <------><------>if ( $var(check_trans) ) { <------><------> route(RELAY); <------><------>} <------><------>exit; <------>} <------>if (is_method("BYE")) { <------> if ($var(loose)) { <------><------>setflag(FLT_ACC); # do accounting ... <------><------>setflag(FLT_ACCFAILED); # ... even if the transaction fails <------><------>setflag(FLT_ACCMISSED); <------><------>route(RELAY); <------> <-->exit; <------> } <------> exit; <------>} etc.

5 10

Re: [SR-Users] ht_db_load_table(): key type must be string (type=6)
by Ginhoux, Patrick 21 Mar '17

21 Mar '17

Hi, There was a mistake in the file attached ; the short kamailio.cfg file (that makes kamailio to start) was not the correct one; attached the correct one. Have anyone an idea of this problem ? Cordialement Patrick GINHOUX De : Ginhoux, Patrick Envoyé : lundi 20 mars 2017 17:58 À : Kamailio users (sr-users(a)lists.sip-router.org) <sr-users(a)lists.sip-router.org> Objet : RE: ht_db_load_table(): key type must be string (type=6) Hi, To figure out what causes this issue, I work to shorten my kamailio.cfg to contains loadmodule/modparam instructions for the htable module only. My first attempt (see kamailio.cfg.ok) shows that the problem doesn't occur. In the second attempt (see kamailio.cfg.ko) I add instructions previously removed from the original .cfg file. I have determined that, depending on the instructions that follows the "modparam("htable", "fetch_rows", 1000)" line, the "key type must be string (type=6)" error occurs or not. In this ko file, if I comment out the following sequence, the error occurs : modparam("htable", "fetch_rows", 1000) #!!ifdef FIXED_ROUTING #modparam("htable", "htable", "mbxrangeHash=>size=4;dbtable=mbxrange;") #!!else #modparam("htable", "htable", "abpqHash=>size=12;dbtable=abpq;") #modparam("htable", "htable", "zabpqHash=>size=12;dbtable=zabpq;") #!!endif modparam("htable", "htable", "propertiesHash=>size=4;dbtable=properties;") I hope my explanation is clearn and there are people who can help me on this problem that causes kamailio to not start. Cordialement Patrick GINHOUX De : Ginhoux, Patrick Envoyé : vendredi 17 mars 2017 15:46 À : Kamailio users (sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org>) <sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org>> Objet : ht_db_load_table(): key type must be string (type=6) Hi, Now the kamailio installation is completed, I try to start kamailio but got an error on a modparam line. By looking at the kamailio.cfg (with debug mode) it looks like the instruction is not correct : modparam("htable", "fetch_rows", 1000) [root@vm-vse02-siprouter1 ~]# systemctl status kamailio.service -l kamailio.service - SYSV: Kamailio is a fast, reliable and flexible SIP Server. Loaded: loaded (/etc/rc.d/init.d/kamailio) Active: failed (Result: exit-code) since Fri 2017-03-17 15:38:13 CET; 17s ago Process: 1526 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, status=1/FAILURE) Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: pike [pike.c:99]: pike_init(): PIKE - initializing Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: pike [ip_tree.c:81]: init_lock_set(): probing 256 set size Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: cfgutils [cfgutils.c:767]: mod_init(): no hash_file given, disable hash functionality Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: ERROR: htable [ht_db.c:276]: ht_db_load_table(): key type must be string (type=6) Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: ERROR: <core> [core/sr_module.c:968]: init_mod(): Error while initializing module htable (/usr/lib64/kamailio/modules/htable.so) Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Mar 17 15:38:13 vm-vse02-siprouter1 kamailio[1526]: Starting kamailio: Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: kamailio.service: control process exited, code=exited status=1 Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: Failed to start SYSV: Kamailio is a fast, reliable and flexible SIP Server.. Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: Unit kamailio.service entered failed state. [root@vm-vse02-siprouter1 ~]# modparam("htable", "fetch_rows", "1000") [root@vm-vse02-siprouter1 ~]# systemctl status kamailio.service -l kamailio.service - SYSV: Kamailio is a fast, reliable and flexible SIP Server. Loaded: loaded (/etc/rc.d/init.d/kamailio) Active: failed (Result: exit-code) since Fri 2017-03-17 15:26:21 CET; 3s ago Process: 1452 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, status=1/FAILURE) Mar 17 15:26:20 vm-vse02-siprouter1 systemd[1]: Starting SYSV: Kamailio is a fast, reliable and flexible SIP Server.... Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: Not starting : invalid configuration file! Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) ERROR: <core> [core/modparam.c:141]: set_mod_param_regex(): parameter <fetch_rows> of type <1> not found in module <htable> Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) CRITICAL: <core> [core/cfg.y:3404]: yyerror_at(): parse error in config file //etc/kamailio/kamailio.cfg, line 308, column 41: Can't set module parameter Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) WARNING: <core> [core/cfg.y:3378]: warn_at(): warning in config file //etc/kamailio/kamailio.cfg, line 971, column 6-13: constant value in if(...) Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: ERROR: bad config file (1 errors) Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Mar 17 15:26:21 vm-vse02-siprouter1 systemd[1]: kamailio.service: control process exited, code=exited status=1 Mar 17 15:26:21 vm-vse02-siprouter1 systemd[1]: Failed to start SYSV: Kamailio is a fast, reliable and flexible SIP Server.. Mar 17 15:26:21 vm-vse02-siprouter1 systemd[1]: Unit kamailio.service entered failed state. [root@vm-vse02-siprouter1 ~]# The documentation shows that fetch_rows is an integer : fetch_rows (integer) How many rows to fetch at once from database. Default value is 100. Example 1.12. Set fetch_rows parameter ... modparam("htable", "fetch_rows", 1000) So how to explain the first error. Have you any thoughts on this case ? Cordialement Patrick GINHOUX

1 0

Re: [SR-Users] ht_db_load_table(): key type must be string (type=6)
by Ginhoux, Patrick 20 Mar '17

20 Mar '17

Hi, To figure out what causes this issue, I work to shorten my kamailio.cfg to contains loadmodule/modparam instructions for the htable module only. My first attempt (see kamailio.cfg.ok) shows that the problem doesn't occur. In the second attempt (see kamailio.cfg.ko) I add instructions previously removed from the original .cfg file. I have determined that, depending on the instructions that follows the "modparam("htable", "fetch_rows", 1000)" line, the "key type must be string (type=6)" error occurs or not. In this ko file, if I comment out the following sequence, the error occurs : modparam("htable", "fetch_rows", 1000) #!!ifdef FIXED_ROUTING #modparam("htable", "htable", "mbxrangeHash=>size=4;dbtable=mbxrange;") #!!else #modparam("htable", "htable", "abpqHash=>size=12;dbtable=abpq;") #modparam("htable", "htable", "zabpqHash=>size=12;dbtable=zabpq;") #!!endif modparam("htable", "htable", "propertiesHash=>size=4;dbtable=properties;") I hope my explanation is clearn and there are people who can help me on this problem that causes kamailio to not start. Cordialement Patrick GINHOUX De : Ginhoux, Patrick Envoyé : vendredi 17 mars 2017 15:46 À : Kamailio users (sr-users(a)lists.sip-router.org) <sr-users(a)lists.sip-router.org> Objet : ht_db_load_table(): key type must be string (type=6) Hi, Now the kamailio installation is completed, I try to start kamailio but got an error on a modparam line. By looking at the kamailio.cfg (with debug mode) it looks like the instruction is not correct : modparam("htable", "fetch_rows", 1000) [root@vm-vse02-siprouter1 ~]# systemctl status kamailio.service -l kamailio.service - SYSV: Kamailio is a fast, reliable and flexible SIP Server. Loaded: loaded (/etc/rc.d/init.d/kamailio) Active: failed (Result: exit-code) since Fri 2017-03-17 15:38:13 CET; 17s ago Process: 1526 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, status=1/FAILURE) Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: pike [pike.c:99]: pike_init(): PIKE - initializing Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: pike [ip_tree.c:81]: init_lock_set(): probing 256 set size Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: cfgutils [cfgutils.c:767]: mod_init(): no hash_file given, disable hash functionality Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: ERROR: htable [ht_db.c:276]: ht_db_load_table(): key type must be string (type=6) Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: ERROR: <core> [core/sr_module.c:968]: init_mod(): Error while initializing module htable (/usr/lib64/kamailio/modules/htable.so) Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Mar 17 15:38:13 vm-vse02-siprouter1 kamailio[1526]: Starting kamailio: Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: kamailio.service: control process exited, code=exited status=1 Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: Failed to start SYSV: Kamailio is a fast, reliable and flexible SIP Server.. Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: Unit kamailio.service entered failed state. [root@vm-vse02-siprouter1 ~]# modparam("htable", "fetch_rows", "1000") [root@vm-vse02-siprouter1 ~]# systemctl status kamailio.service -l kamailio.service - SYSV: Kamailio is a fast, reliable and flexible SIP Server. Loaded: loaded (/etc/rc.d/init.d/kamailio) Active: failed (Result: exit-code) since Fri 2017-03-17 15:26:21 CET; 3s ago Process: 1452 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, status=1/FAILURE) Mar 17 15:26:20 vm-vse02-siprouter1 systemd[1]: Starting SYSV: Kamailio is a fast, reliable and flexible SIP Server.... Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: Not starting : invalid configuration file! Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) ERROR: <core> [core/modparam.c:141]: set_mod_param_regex(): parameter <fetch_rows> of type <1> not found in module <htable> Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) CRITICAL: <core> [core/cfg.y:3404]: yyerror_at(): parse error in config file //etc/kamailio/kamailio.cfg, line 308, column 41: Can't set module parameter Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) WARNING: <core> [core/cfg.y:3378]: warn_at(): warning in config file //etc/kamailio/kamailio.cfg, line 971, column 6-13: constant value in if(...) Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: ERROR: bad config file (1 errors) Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Mar 17 15:26:21 vm-vse02-siprouter1 systemd[1]: kamailio.service: control process exited, code=exited status=1 Mar 17 15:26:21 vm-vse02-siprouter1 systemd[1]: Failed to start SYSV: Kamailio is a fast, reliable and flexible SIP Server.. Mar 17 15:26:21 vm-vse02-siprouter1 systemd[1]: Unit kamailio.service entered failed state. [root@vm-vse02-siprouter1 ~]# The documentation shows that fetch_rows is an integer : fetch_rows (integer) How many rows to fetch at once from database. Default value is 100. Example 1.12. Set fetch_rows parameter ... modparam("htable", "fetch_rows", 1000) So how to explain the first error. Have you any thoughts on this case ? Cordialement Patrick GINHOUX

1 0

ACC - Cdr enabled
by Diego Nadares 20 Mar '17

20 Mar '17

Hi guys, I have configured to use cdr with extra fields modparam("acc", "cdr_extra", * "sip_code=$rs;sip_reason=$rr;"* "hangup_src=$dlg_var(hangup_disposition);" "prefix=$dlg_var(prefix);gos=$dlg_var(gos);endpoint_type=$ dlg_var(endpoint_type);" "ip_a=$dlg_var(ip_a);ip_b=$dlg_var(ip_b);" Is this the right way to always save the hangup cause? Or is another better way? Because, when call is finished with a bye both fields are empty. The other thing is that I need to save, start_time and end_time with seconds.microseconds (1490013250.601707). Is this possible? Thanks! Diego

2 5

Is File Sharing between two Extensions Possible?
by Shahid Mehmood 20 Mar '17

20 Mar '17

Dear all, I want to share (any kind of) files between two extensions. Is it possible? If it is, then how ??? please elaborate with example. -- Shahid Mehmood

1 0

cisco spa502g issues
by ben＠wtf.com.au 19 Mar '17

19 Mar '17

Hi guys, we have a bunch of SIP phones behind a fire wall, with our kamalio server out on the internet. Most of them are the older SPA92x series, but we have some new SPA502g's. We have no problems calling between 92x and 502's. How ever the 502's calling each other do not get voice path. I have noticed that the phones REGISTER differently: AOR:: 5546@<our domain> Contact:: sip:5546@<OUR OFFICE IP>:1032 Q= Expires:: 180 Callid:: 4754c4f9-c67e1018(a)10.0.41.29 Cseq:: 43112 User-agent:: Cisco/SPA502G-7.6.2a State:: CS_DIRTY Flags:: 0 Cflag:: 0 Socket:: udp:<OUR SR IP>:5060 Methods:: 6815 AOR:: 5590(a)sip.skunkworks.net.au Contact:: sip:5590@10.0.41.14:5060 Q= Expires:: 1154 Callid:: 24435738-224b06db(a)10.0.41.14 Cseq:: 8012 User-agent:: Linksys/SPA921-5.1.8 Received:: sip:<OUR OFFICE IP>:1026 State:: CS_SYNC Flags:: 0 Cflag:: 64 Socket:: udp:<OUR SR IP>:5060 Methods:: 4767 The older 921 has its private IP in the contact, where as the newer 502 has the external IP of our office in the contact. Our file wall is a Watchguard T-10 (latest updates etc) with the SIP-ALG running. Any thoughts on where to start looking ? Cheers, Ben.

3 4

Generate extra cdr per dialog
by Diego Nadares 18 Mar '17

18 Mar '17

Hi Guys, I'm using acc module for accounting with the following conf: .... modparam("acc", "cdr_enable", 1) modparam("acc", "cdr_expired_dlg_enable", 1) modparam("acc", "cdr_start_on_confirmed", 1) modparam("acc", "cdr_facility", "LOG_LOCAL1") modparam("acc", "cdr_end_id", "end_time_dt") modparam("acc", "cdr_extra", "sip_code=$rs;sip_reason=$rr;" "hangup_src=$dlg_var(hangup_disposition);" "prefix=$dlg_var(prefix);gos=$dlg_var(gos);endpoint_type=$dlg_var(endpoint_type);" "ip_a=$dlg_var(ip_a);ip_b=$dlg_var(ip_b);" .... It works fine. At the end of the call the cdr is generated ok. BUT In MANAGE_FAILURE, If the first call failed and if there are more dests, we are generating a new call in the same dialog (Some of the dialog vars like ip_a, ip_b can change for the new dest ) I would like to generate both cdrs, the one that failed and the new one (with some dlg vars with new data). if(rtjson_next_route() && t_check_status("503")) { $avp(current_route) = $avp(current_route)+1; t_on_branch("MANAGE_BRANCH"); t_on_failure("MANAGE_FAILURE"); route(RELAY); exit; } Right now just the last call cdr is saved. I all ready made this work with db_acc (transaction oriented) but I think in my case it will be more reliable with cdr (dialog oriented). Thanks in advance! Diego.

1 1

f_malloc WARNINGS in syslog
by Diego Nadares 17 Mar '17

17 Mar '17

Hi Guys, I'm seeing a lot of warnings in my syslog. Is this normal? Or maybe I am doing something wrong in my cfg? .... Mar 16 17:11:47 dwsipm03 ./kamailio[26226]: WARNING: <core> [mem/f_malloc.c:444]: fm_malloc(): fm_malloc(0x7f68e5199010, 8) called from nathelper: nathelper.c: nh_timer(2078) Mar 16 17:11:47 dwsipm03 ./kamailio[26226]: WARNING: <core> [mem/f_malloc.c:527]: fm_malloc(): fm_malloc(0x7f68e5199010, 8) returns address 0x7f68e52a2d50 Mar 16 17:11:47 dwsipm03 ./kamailio[26226]: WARNING: <core> [mem/f_malloc.c:588]: fm_free(): fm_free(0x7f68e5199010, 0x7f68e52a2d50), called from nathelper: nathelper.c: nh_timer(2222) Mar 16 17:11:47 dwsipm03 ./kamailio[26226]: WARNING: <core> [mem/f_malloc.c:607]: fm_free(): fm_free: freeing block alloc'ed from nathelper: nathelper.c: nh_timer(2078) ..... Mar 16 17:15:44 dwsipm03 ./kamailio[26210]: WARNING: <core> [mem/f_malloc.c:607]: fm_free(): fm_free: freeing block alloc'ed from core: xavp.c: xavp_new_value(94) Mar 16 17:15:44 dwsipm03 ./kamailio[26210]: WARNING: <core> [mem/f_malloc.c:588]: fm_free(): fm_free(0x7f68d9d51000, 0x7f68da069ca8), called from tm: h_table.c: free_cell_helper(246) Mar 16 17:15:44 dwsipm03 ./kamailio[26210]: WARNING: <core> [mem/f_malloc.c:607]: fm_free(): fm_free: freeing block alloc'ed from tm: h_table.c: build_cell(317) Mar 16 17:15:44 dwsipm03 ./kamailio[26210]: WARNING: <core> [mem/f_malloc.c:588]: fm_free(): fm_free(0x7f68d9d51000, 0x7f68da031f00), called from tm: h_table.c: free_cell_helper(150) .... Thanks in advance. Diego

2 2

ht_db_load_table(): key type must be string (type=6)
by Ginhoux, Patrick 17 Mar '17

17 Mar '17

Hi, Now the kamailio installation is completed, I try to start kamailio but got an error on a modparam line. By looking at the kamailio.cfg (with debug mode) it looks like the instruction is not correct : modparam("htable", "fetch_rows", 1000) [root@vm-vse02-siprouter1 ~]# systemctl status kamailio.service -l kamailio.service - SYSV: Kamailio is a fast, reliable and flexible SIP Server. Loaded: loaded (/etc/rc.d/init.d/kamailio) Active: failed (Result: exit-code) since Fri 2017-03-17 15:38:13 CET; 17s ago Process: 1526 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, status=1/FAILURE) Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: pike [pike.c:99]: pike_init(): PIKE - initializing Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: pike [ip_tree.c:81]: init_lock_set(): probing 256 set size Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: cfgutils [cfgutils.c:767]: mod_init(): no hash_file given, disable hash functionality Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: ERROR: htable [ht_db.c:276]: ht_db_load_table(): key type must be string (type=6) Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: ERROR: <core> [core/sr_module.c:968]: init_mod(): Error while initializing module htable (/usr/lib64/kamailio/modules/htable.so) Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Mar 17 15:38:13 vm-vse02-siprouter1 kamailio[1526]: Starting kamailio: Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: kamailio.service: control process exited, code=exited status=1 Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: Failed to start SYSV: Kamailio is a fast, reliable and flexible SIP Server.. Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: Unit kamailio.service entered failed state. [root@vm-vse02-siprouter1 ~]# modparam("htable", "fetch_rows", "1000") [root@vm-vse02-siprouter1 ~]# systemctl status kamailio.service -l kamailio.service - SYSV: Kamailio is a fast, reliable and flexible SIP Server. Loaded: loaded (/etc/rc.d/init.d/kamailio) Active: failed (Result: exit-code) since Fri 2017-03-17 15:26:21 CET; 3s ago Process: 1452 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, status=1/FAILURE) Mar 17 15:26:20 vm-vse02-siprouter1 systemd[1]: Starting SYSV: Kamailio is a fast, reliable and flexible SIP Server.... Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: Not starting : invalid configuration file! Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) ERROR: <core> [core/modparam.c:141]: set_mod_param_regex(): parameter <fetch_rows> of type <1> not found in module <htable> Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) CRITICAL: <core> [core/cfg.y:3404]: yyerror_at(): parse error in config file //etc/kamailio/kamailio.cfg, line 308, column 41: Can't set module parameter Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) WARNING: <core> [core/cfg.y:3378]: warn_at(): warning in config file //etc/kamailio/kamailio.cfg, line 971, column 6-13: constant value in if(...) Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: ERROR: bad config file (1 errors) Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Mar 17 15:26:21 vm-vse02-siprouter1 systemd[1]: kamailio.service: control process exited, code=exited status=1 Mar 17 15:26:21 vm-vse02-siprouter1 systemd[1]: Failed to start SYSV: Kamailio is a fast, reliable and flexible SIP Server.. Mar 17 15:26:21 vm-vse02-siprouter1 systemd[1]: Unit kamailio.service entered failed state. [root@vm-vse02-siprouter1 ~]# The documentation shows that fetch_rows is an integer : fetch_rows (integer) How many rows to fetch at once from database. Default value is 100. Example 1.12. Set fetch_rows parameter ... modparam("htable", "fetch_rows", 1000) So how to explain the first error. Have you any thoughts on this case ? Cordialement Patrick GINHOUX

1 0

Error on <ds_probing_threshhold> of type <2> not found in module <dispatcher> and SCTP API Not initialized
by Ginhoux, Patrick 17 Mar '17

17 Mar '17

Hi, I'm migrating my kamailio.cfg from the 3.3.1 release to 5.0.0 and encounter the following errors : Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: Starting SYSV: Kamailio is a fast, reliable and flexible SIP Server.... Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: Not starting : invalid configuration file! Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) ERROR: <core> [core/modparam.c:141]: set_mod_param_regex(): parameter <ds_probing_threshhold> of type <2> not found in module <dispatcher> Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) CRITICAL: <core> [core/cfg.y:3404]: yyerror_at(): parse error in config file //etc/kamailio/kamailio.cfg, line 295, column 49: Can't set module parameter Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) WARNING: <core> [core/cfg.y:3378]: warn_at(): warning in config file //etc/kamailio/kamailio.cfg, line 971, column 6-13: constant value in if(...) Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: ERROR: bad config file (1 errors) Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: kamailio.service: control process exited, code=exited status=1 Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: Failed to start SYSV: Kamailio is a fast, reliable and flexible SIP Server.. Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: Unit kamailio.service entered failed state. Below the extract of my kamailio.cfg file : modparam("dispatcher", "list_file", DISPATCHER_FILE) modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_probing_threshhold",3) modparam("dispatcher", "flags", 2) modparam("dispatcher", "attrs_avp", "$avp(dsattrs)") modparam("dispatcher", "dst_avp", "$avp(dsdst)") modparam("dispatcher", "grp_avp", "$avp(dsgrp)") modparam("dispatcher", "cnt_avp", "$avp(dscnt)") modparam("dispatcher", "ds_hash_size", 8) modparam("dispatcher", "ds_ping_interval", 10) modparam("dispatcher", "force_dst", 1) For the dispatcher error : I don't find any change (eg in the Changelog for 5.0.0.) regarding the dispatcher module. So is it a bug in the dispatcher module or have I to change it to something else ? For the SCTP API error : I don't know what to do here. Thanks to people that can help me on these 2 errors Cordialement Patrick GINHOUX

2 3

Configuration to fetch SIP response body.
by vivek＠advaitamtech.com 17 Mar '17

17 Mar '17

Hi, Is there any configuration to fetch SIP response body received?. My requirement is to fetch the SIP response body and save it into database. Thanks, Vivek

3 3

Search for kamailio PERL module for 5.0 level
by Ginhoux, Patrick 17 Mar '17

17 Mar '17

Hi, I'm a beginner in the use of kamailio product, so I try below to explain my problem with my words: 1) PERL module issue : Some years ago a SIP Router proxy running RedHat 6.2 was developped using the kamailio version 3.3 and the following packages used : kamailio-3.3.2-1.1.1.x86_64.rpm kamailio-snmpstats-3.3.2-1.1.1.x86_64.rpm kamailio-mysql-3.3.2-1.1.1.x86_64.rpm kamailio-perl-3.3.2-1.1.1.x86_64.rpm We have the project to migrate this SIP Proxy to RedHat 7.1 and used the latest Kamailio v5.0.0 Release: kamailio-5.0.0-24.1.x86_64.rpm kamailio-mysql-5.0.0-24.1.x86_64.rpm kamailio-snmpstats-5.0.0-24.1.x86_64.rpm However I don't find the kamalio-perl package for RedHat 7.1. I see that the perl module has been renamed to 'app_perl' but I don't find it either for kamailio 5.0.0. 2) Kamailio.cfg script Our proxy used the kamailio.cfg from the sample of the 3.3.3 release. So can I reuse the same 3.3.3 kamailio.cfg file with the 5.0.0 release or should I migrate (rewrite it) from the 5.0.0 sample ? So I'm looking for some help on these issues. Is there people that had this case ? Thanks in advance for any answer. Cordialement Patrick GINHOUX PS : I just create my account today but don't get the email to validate it.

2 6

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users