- sr-users - kamailio.org

Implementation of RFC 5393
by Guillaume 21 Oct '15

21 Oct '15

Hi guys, What do you think about the RFC 5393 on loop detection and amplification attack protection? The RFC is short and still a proposed standard but don't you think it could be useful to prevent loop and amplification attack? Because even if the max-forward field reduces the loop to ~70 hosts (in most cases) with some techniques we could fork the message up to 2^70 messages (as described in the RFC) to crash the servers. Basically the server has to do 2 things: * check if it is not already in the via of the message * the previous check is not enough as a B2BUA could have replace the via headers, so the RFC introduces a new field called max-breadth to limit the forking. I have not seen a lot of implementation of this RFC on the free SIP software and I think it could be a good way to improve kamailio making a module for it (the easier way to implement this feature I think). In fact I'm in a research internship about VoIP security and I have time to develop such a module for kamailio if you think it's a good idea (I'm looking for some security improvements in free software solutions so if you have other idea don't hesitate to tell me). Cheers, Tetram

3 4

pua_dialoginfo publish sent without recieved etag (intermittent)
by Asgaroth 21 Oct '15

21 Oct '15

Hi All, I've come accross an intermittent issue where an initial publish is sent to our presence server, proxy recieves the subsequent 200 with etag, but the following publish sent does not contain the sip-if-match header of the recieved 200, which ends up causing trouble with BLF on our test devices, it also has the added side affect of not being cleared out of the presentity table, these entries need to be manually removed. This does not occur all the time, I can use the same phone and make several calls before this issue occurs. It is not limited to a device type, we've tried with panasonic, polycom, cisco, zoiper, yealink and linksys devices, all exhibit the same sporadic behaviour. I've attached an example sip trace of the publish messages where this happens, you can see the second publish doesnt have the sip-if-match header whose content should be that of the sip-etag in the previous 200 to the initial publish. I'm not sure if there is something I am misunderstanding here, a configuration issue, or if this is indeed a bug. Both the proxy and the presence server are running kamailio v4.3.3. Any pointers/suggestions/guidance would be appreciated. If you need any additional info, please dont hesitate to ask. Thanks

2 2

Sending ReINVITE from Kamailio
by Grant Bagdasarian 21 Oct '15

21 Oct '15

Hello, Is it possible to have Kamailio send a ReINVITE every X minutes to determine if a session is still active? I know it's a proxy and doesn't have B2BUA capabilities, but there was a module which allowed Kamailio to generate SIP messages, but I can't find it anymore. If Kamailio is not the place to do this, which component in the voip network should be responsible for this? Are there perhaps other ways to poll for session state in Kamailio? Regards, Grant

3 4

Re: [SR-Users] MySQL Connect Errors
by John Billings 20 Oct '15

20 Oct '15

Both boxes are running Debian 8. I’m still looking at the mysql logs, but I haven’t found anything relevant, yet. > On Oct 14, 2015, at 5:00 AM, sr-users-request(a)lists.sip-router.org wrote: > > Hello, > > do you have centos+selinux? Because I heard about a lot of limits with > the combination of the two. > > Have you checked the mysqld syslog messages, anything relevant there? > > Cheers, > Daniel >

3 2

Far end NAT traversal
by NITESH BANSAL 20 Oct '15

20 Oct '15

Hello, I would really appreciate if someone can point me to some documentation for Far end nat traversal in Kamailio. Thanks,Nitesh

3 2

Dialog timeout if record route have both strict and loose route
by Arun Kumar 20 Oct '15

20 Oct '15

Hi dialog timeout is occurred if 200 ok having mixed loose and strict routing entries in record route header conf file attached INVITE sip:123456789@22.22.22.22:5060 SIP/2.0 Via: SIP/2.0/UDP 176.204.26.157:63939 ;rport;branch=z9hG4bKPjvAKLQD72G88kpqC2IJwbmTcXUlHGULcW Max-Forwards: 70 From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22 Contact: <sip:123455555@176.204.26.157:63939;ob> Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14602 INVITE Route: <sip:11.11.11.11:345;lr> Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 User-Agent: zeo-iphone Opcode: 19815 Content-Type: application/sdp Content-Length: 320 v=0 o=- 3653999880 3653999880 IN IP4 10.220.83.191 s=pjmedia b=AS:25 t=0 0 a=X-nat:0 m=audio 4000 RTP/AVP 18 96 c=IN IP4 10.220.83.191 b=TIAS:8000 a=rtcp:4001 IN IP4 10.123.11.223 a=sendrecv a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-16 a=X-adapter:some value SIP/2.0 407 Proxy Authentication required Via: SIP/2.0/UDP 11.11.11.11:345;branch=z9hG4bK3d4f.6f8dff1ec0806cb23f56d847d5fe3934.0,SIP/2.0/UDP 176.204.26.157:63939 ;rport=63939;branch=z9hG4bKPjvAKLQD72G88kpqC2IJwbmTcXUlHGULcW;received=176.204.26.157 From: <sip:123455555@22.22.22.22>;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: <sip:123456789@22.22.22.22> Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14602 INVITE Proxy-Authenticate: Digest nonce="6b24dc6996de20028c78dbeaf13edc55",realm="22.22.22.22",opaque="",stale=FALSE,algorithm=MD5 Content-Length: 0 ACK sip:123456789@22.22.22.22:5060 SIP/2.0 Via: SIP/2.0/UDP 176.204.26.157:63939 ;rport;branch=z9hG4bKPjvAKLQD72G88kpqC2IJwbmTcXUlHGULcW Max-Forwards: 70 From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22 Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14602 ACK Route: <sip:11.11.11.11:345;lr> Content-Length: 0 INVITE sip:123456789@22.22.22.22:5060 SIP/2.0 Via: SIP/2.0/UDP 176.204.26.157:63939 ;rport;branch=z9hG4bKPjmWCyQQWaKBZC0fGKfS2LCXCIklN-UIHI Max-Forwards: 70 From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22 Contact: <sip:123455555@176.204.26.157:63939;ob> Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14603 INVITE Route: <sip:11.11.11.11:345;lr> Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 User-Agent: zeo-iphone Opcode: 19815 Proxy-Authorization: Digest username="123455555", realm="22.22.22.22", nonce="6b24dc6996de20028c78dbeaf13edc55", uri=" sip:123456789@22.22.22.22:5060", response="554a1da255084f7a95d3b6e7a0c48933", algorithm=MD5 Content-Type: application/sdp Content-Length: 320 v=0 o=- 3653999880 3653999880 IN IP4 10.220.83.191 s=pjmedia b=AS:25 t=0 0 a=X-nat:0 m=audio 4000 RTP/AVP 18 96 c=IN IP4 10.220.83.191 b=TIAS:8000 a=rtcp:4001 IN IP4 34.220.83.191 a=sendrecv a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-16 a=X-adapter:some value SIP/2.0 100 Trying Via: SIP/2.0/UDP 11.11.11.11:345;branch=z9hG4bK4d4f.b793c28bbb6684da0ad60d4320be2d6b.0,SIP/2.0/UDP 176.204.26.157:63939 ;rport=63939;branch=z9hG4bKPjmWCyQQWaKBZC0fGKfS2LCXCIklN-UIHI;received=176.204.26.157 From: <sip:123455555@22.22.22.22>;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: <sip:123456789@22.22.22.22> Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14603 INVITE Content-Length: 0 SIP/2.0 183 Session progress Via: SIP/2.0/UDP 11.11.11.11:345;branch=z9hG4bK4d4f.b793c28bbb6684da0ad60d4320be2d6b.0,SIP/2.0/UDP 176.204.26.157:63939 ;rport=63939;branch=z9hG4bKPjmWCyQQWaKBZC0fGKfS2LCXCIklN-UIHI;received=176.204.26.157 From: <sip:123455555@22.22.22.22>;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: <sip:123456789@22.22.22.22>;tag=GB-1445011078679 CSeq: 14603 INVITE Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh Contact: <sip:22.22.22.22:5060> Content-Type: application/sdp Record-Route: <sip:22.22.22.22:5060;lr>,<sip:11.11.11.11:345;lr> Content-Length: 298 v=0 o=- 3653999880 3653999880 IN IP4 50.56.154.204 s=zeodialer c=IN IP4 50.33.154.204 b=AS:25 t=0 0 m=audio 53128 RTP/AVP 18 96 c=IN IP4 50.33.154.204 b=TIAS:8000 a=rtpmap:18 G729/8000 a=sendrecv a=fmtp:18 annexb=no a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-16 a=X-adapter:some value SIP/2.0 183 Session Progress Record-Route: <sip:22.22.22.22:5060;lr>,<sip:11.11.11.11:345> Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14603 INVITE Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,UPDATE P-Early-Media: sendrecv Contact: <sip:22.22.22.22:5060> Via: SIP/2.0/UDP 11.11.11.11:345;branch=z9hG4bK4d4f.b793c28bbb6684da0ad60d4320be2d6b.0,SIP/2.0/UDP 176.204.26.157:63939 ;rport=63939;branch=z9hG4bKPjmWCyQQWaKBZC0fGKfS2LCXCIklN-UIHI;received=176.204.26.157 To: <sip:123456789@22.22.22.22>;tag=GB-1445011078679 Content-Type: application/sdp From: <sip:123455555@22.22.22.22>;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu Content-Length: 212 v=0 o=- 1426744035 1426744035 IN IP4 50.56.154.204 s=Nexge c=IN IP4 50.22.154.204 t=0 0 m=audio 53128 RTP/AVP 18 96 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:96 telephone-event/8000 a=ptime:20 SIP/2.0 200 OK Record-Route: <sip:22.22.22.22:5060;lr>,<sip:11.11.11.11:345> Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14603 INVITE Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,UPDATE Contact: <sip:22.22.22.22:5060> Via: SIP/2.0/UDP 11.11.11.11:345;branch=z9hG4bK4d4f.b793c28bbb6684da0ad60d4320be2d6b.0,SIP/2.0/UDP 176.204.26.157:63939 ;rport=63939;branch=z9hG4bKPjmWCyQQWaKBZC0fGKfS2LCXCIklN-UIHI;received=176.204.26.157 To: <sip:123456789@22.22.22.22>;tag=GB-1445011078679 Content-Type: application/sdp From: <sip:123455555@22.22.22.22>;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu Content-Length: 212 v=0 o=- 1426744035 1426744035 IN IP4 50.56.154.204 s=Nexge c=IN IP4 50.33.44.204 t=0 0 m=audio 53128 RTP/AVP 18 96 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:96 telephone-event/8000 a=ptime:20 ACK sip:11.11.11.11:345 SIP/2.0 Via: SIP/2.0/UDP 176.204.26.157:63939 ;rport;branch=z9hG4bKPjldbprXw3ybGOxoeKWwvtdxLmNp8jXsOX Max-Forwards: 70 From: sip:123455555@22.22.22.22;tag=E9YwhssbjdD63KZpXep-UCmOxshWrcwu To: sip:123456789@22.22.22.22;tag=GB-1445011078679 Call-ID: VlaYDWuM5COSfEIqydwAxFM76TLv7Syh CSeq: 14603 ACK Route: <sip:22.22.22.22:5060;lr> Route: <sip:22.22.22.22:5060> Content-Length: 0

2 3

kamctl rtpproxy nh_show_rtpp not working
by amar Smart Telecom 19 Oct '15

19 Oct '15

Dear all, I have installed Kamailio and Rtpproxy. Following is the process (ps) info: "kamailio 648 1 0 Oct08 ? 00:00:05 /usr/bin/rtpproxy -s udp:127.0.0.1 7722 -u kamailio kamailio -p /var/run/rtpproxy/rtpproxy.pid -l 192.168.58.25" But when I give command: " kamctl mi nh_show_rtpp" it returns following: "500 command 'nh_show_rtpp' not available" What could be the problem? Thanks, Amar.

2 1

RtpProxy socket timeout not working
by Arun Kumar 19 Oct '15

19 Oct '15

Hi Rtp Session timeout notification is not working , we tried with kamailio 4.2 with rtpproxy 2.0 / 1.3 beta/1.2 releases , i think kamailio rtpproxy is not submitting session timeout socket to rtpproxy kamailio 4.2.0 ----------------------------------- modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722") modparam("rtpproxy", "timeout_socket", "xmlrpc:http://127.0.0.1:5060/RPC") ............... rtpproxy_manage(); ................ RtpProxy ------------------------- RTPProxy 2.0 RTPProxy 1.3 Beta with patch given by *Daniel* RTPProxy 1.2 rtpproxy -F -s udp:127.0.0.1:7722 -d DBUG -f -i -T 10 RTPRoxy Log ---------------------------------------------------- DBUG:get_command: received command "4242_9 Uc0,8,101 2479e562440c023d 192.168.1.103 6074 5410ef73;1" INFO:handle_command: new session 2479e562440c023d, tag 5410ef73;1 requested, type strong INFO:handle_command: new session on a port 45984 created, tag 5410ef73;1 INFO:handle_command: pre-filling caller's address with 192.168.1.103:6074 DBUG:doreply: sending reply "4242_9 45984 " DBUG:get_command: received command "4242_10 Lc0,101 2479e562440c023d 192.168.1.102 4002 5410ef73;1 ADqH-A-mLLN0th2gGoopYMK1cy.-ozDf;1" INFO:handle_command: lookup on ports 45984/36756, session timer restarted INFO:handle_command: pre-filling callee's address with 192.168.1.102:4002 DBUG:doreply: sending reply "4242_10 36756 " INFO:rxmit_packets: callee's address latched in: 192.168.1.102:4002 (RTP) INFO:rxmit_packets: callee's address latched in: 192.168.1.102:4003 (RTCP) INFO:rxmit_packets: caller's address latched in: 192.168.1.103:6075 (RTCP) INFO:rxmit_packets: caller's address latched in: 192.168.1.103:6074 (RTP) INFO:process_rtp: session timeout INFO:remove_session: RTP stats: 328 in from callee, 5 in from caller, 333 relayed, 0 dropped INFO:remove_session: RTCP stats: 3 in from callee, 4 in from caller, 7 relayed, 0 dropped INFO:remove_session: session on ports 45984/36756 is cleaned up Kamailio RTP log ----------------------------------------------- 3(4242) DEBUG: rtpproxy [rtpproxy_funcs.c:148]: check_content_type(): type <application/sdp> found valid 3(4242) DEBUG: rtpproxy [rtpproxy.c:2704]: force_rtp_proxy(): proxy reply: 45984 for more log please see attachment

2 1

Kamctl cannot add user to pgsql
by Pavlo Karbovnyk 19 Oct '15

19 Oct '15

Good Day All. I run into following problem: (It may be helpful for other people how have similar problem) kamctl add 1000 password database engine 'PGSQL' loaded Control engine 'FIFO' loaded is_user: user counter=0 <--- showing counter=0 check_db_alias: alias counter= <--- showing counter= nothing INFO: user '1000' already exists as alias ============================================================ how to fix it : in kamctl locate a function check_db_alias() { ..... CNT=`$DBROCMD "$QUERY" | $EGREP -v ERROR | $LAST_LINE` ..... } replace with CNT command with following: check_db_alias() { ..... CNT=`$DBROCMD "$QUERY" "$DBRAWPARAMS" | $EGREP -v ERROR | $LAST_LINE` ..... } ============================================================ after this kamctl add 1000 password database engine 'PGSQL' loaded Control engine 'FIFO' loaded is_user: user counter=0 check_db_alias: alias counter=0 pgsql_query: /usr/bin/psql -A -q -t -P fieldsep=' ' -h localhost -U kamailio kamailio -c 'insert into subscriber (username, domain,ha1,ha1b,password) values ('1000','127.0.0.1','6fda0594de6ea94b03a12fdd998758ae','31e118ac5b09f07 1858740d6125d901d','');' new user '1000' added Regards Pavlo.

2 1

Weight balancing with dispatcher module
by Ben Bliss 19 Oct '15

19 Oct '15

Hi, I am having issues getting the dispatcher to work using weighting. I have been digging through old posts to the list, and tried all that I have found, but am still having no luck at all. So, information... version: kamailio 4.2.4 (amd64/freebsd) be62bd flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_MALLOC, USE_PTHREAD_MUTEX, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, select, kqueue. id: be62bd Dispatcher configuration... modparam("dispatcher", "db_url", DBURL) modparam("dispatcher", "table_name", "dispatcher") modparam("dispatcher", "flags", 3) modparam("dispatcher", "force_dst", 1) modparam("dispatcher", "dst_avp", "$avp(AVP_DST)") modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)") modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)") Dialplan config.. route[DISPATCH] { if(!ds_select_dst("1", "9")) { send_reply("404", "No destination"); exit; } xlog("L_DBG", "--- SCRIPT: going to <$ru> via <$du>\n"); t_on_failure("RTF_DISPATCH"); return; I am loading the values from a database, which are being loaded fine, and appear to be being formatted correctly aswell.. +----+-------+-------------------------+-------+----------+------------+----------------------+ | id | setid | destination | flags | priority | attrs | description | +----+-------+-------------------------+-------+----------+------------+----------------------+ | 1 | 1 | sipx.x.x.106:5060 | 8 | 1 | weight=100 | | | 2 | 1 | sip:x.x.x.107:5060 | 8 | 1 | weight=0 | | +----+-------+-------------------------+-------+----------+------------+----------------------+ The IP's are public, so i've masked them... The following is from kamcmd.. { NRSETS: 1 RECORDS: { SET: { ID: 1 TARGETS: { DEST: { URI: sip:x.x.x.107:5060 FLAGS: AP PRIORITY: 1 ATTRS: { BODY: weight=0 DUID: MAXLOAD: 0 WEIGHT: 0 } } DEST: { URI: sip:x.x.x106:5060 FLAGS: AP PRIORITY: 1 ATTRS: { BODY: weight=100 DUID: MAXLOAD: 0 WEIGHT: 100 } } } } } } However, when any call is placed, it will always goto the server ending 107 (with weight 0, which means, as far as I understand, it should be ignored). I've tried with ; after the weights, this made no change either. When set to round robin, or via priority, it appears to work fine. Any ideas? -- Kind Regards, --------- Ben

2 3

kamailio cfg file with user db authentication and rtpproxy
by amar Smart Telecom 19 Oct '15

19 Oct '15

Dear all, Can you pls mail me a working Kamailio cfg file which has: "Sip user db authentication" and "rtpproxy for all calls" Thank you, Amar.

3 2

Link between presence module and subscriber table
by Loïc Boissy 19 Oct '15

19 Oct '15

Hello, l would like to send a SIP message (NOTIFY for example) to a specific user when a new account is created in the kamailio database. Is it possible to do that? Best regards Loïc

2 1

Re: [SR-Users] call-limit peer
by Angel Elena 19 Oct '15

19 Oct '15

Ok, now I check dlg_manage settings. Thanks -------------------------------- Ángel Elena Medina _o) craem(a)craem.net / \\ http://blog.craem.net _(___V @craem_ -------------------------------- -----Mensaje original----- De: ycaner <yasin.caner(a)netgsm.com.tr> Enviado: Lun 19-10-2015 08:22 Asunto: Re: [SR-Users] call-limit peer Para: sr-users(a)lists.sip-router.org; > Hello; > with dialog module using dont forget set dlg_manage or setting flags. > or you can do it with pike limit for only INVITE methods. > > > > > -- > View this message in context: > http://sip-router.1086192.n5.nabble.com/call-limit-peer-tp142403p142407.html > Sent from the Users mailing list archive at Nabble.com. > > _______________________________________________ > 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 >

1 0

call-limit peer
by Angel Elena 19 Oct '15

19 Oct '15

Hi everybody. I have a kamailio 4.0 running with rtpproxy and debian 7.8, and I need limit calls by IP. My kamailio.cfg: # ----------------------------------------- #------------------------------------------ loadmodule "dialog.so" modparam("dialog", "dlg_flag", 4) modparam("dialog", "enable_stats",1) modparam("dialog", "hash_size", 4096) modparam("dialog", "profiles_with_value","callquota") modparam("dialog", "default_timeout", 300) modparam("dialog", "dlg_match_mode", 2) modparam("dialog", "detect_spirals", 1) modparam("dialog", "db_mode", 0) In my route outside, I have: get_profile_size("callquota", "$avp(s:tag)", "$var(SIZE)"); xlog ("L_INFO", ".... $avp(s:tag) ..... CALLQUOTA .... $var(SIZE)..... \n "); On $avp(s:tag) is the client code-peer/ip. When I view the logs... the result: Oct 18 22:18:03 sipproxy /usr/local/sbin/kamailio[19724]: INFO: <script>: .... 4012 ..... CALLQUOTA .... 0..... Always, the result is '0'. Is correct my configuration ? thanks -------------------------------- Ángel Elena Medina _o) craem(a)craem.net / \\ http://blog.craem.net _(___V @craem_ --------------------------------

2 1

Re: [SR-Users] Changing a user's password in the Kamailio routing logic
by Surendra.P 19 Oct '15

19 Oct '15

Hello mike, you can achieve it by doing DB update query using sqlops module. If you want to change the user's password dynamically under a certain condition, just invoke a update query to the DB using sqlops. Hope it solves your issue. Regards Surendra Hi all, I was wondering if there was a way to change a user's password from within the routing logic section of kamailio.cfg (i.e. like do what 'kamctl password' does, but in the routing logic)? Thank, Mike ******

1 0

Re: [SR-Users] Auth module Issue:UA getting challanged thrice when load
by Surendra.P 19 Oct '15

19 Oct '15

Hello Daniel, Thanks for your reply. I did some debugging, I found that I am getting error like this, earlier this log was in DBG mode, changed to error and then I ran the load.. "auth:pre_auth: Invalid nonce value received (ret 2)" Problem is that this issue getting simulated every time. I am using auth module version of kamailio 4.1.5 , since I checked with latest kamailio version 4.3.2 , I didn't find any differences in this module. Please find my finding below Auth/nonce.c:check_nonce() b_nonce2_len=calc_bin_nonce_md5(&b_nonce2, cfg, secret1, secret2, msg); if (!memcmp(&b_nonce.n.md5_1[0], &b_nonce2.n.md5_1[0], 16)) // here where condition is getting failed and it is returning 2. Regards Surendra Hello, are there any error messages in the syslog? Maybe setting debug level for auth modules to 3 and looking at logs will help to reveal what is happening. Be sure syslog is in async mode, otherwise it will slow down processing. Cheers, Daniel On 16/10/15 08:42, Surendra.P wrote: > > Hello Daniel, > > > > I have a concern regarding auth module, I am running > 2000 TPS for 1000000 subscribers, using SIPP. What I observed when > you run small load like 500 TPS, everything get passed, but for 2000 TPS > > With same subscriber.csv file some of the subscribers getting > challenged. May I this why auth module is behaving like this.. below > are the parameters which I configured in auth module > > > > modparam("auth", "nonce_expire", 3600), rest all parameters default > values. > > > > Regards > > Surendra >

1 0

Changing a user's password in the Kamailio routing logic
by Michael McVady 16 Oct '15

16 Oct '15

Hi all, I was wondering if there was a way to change a user's password from within the routing logic section of kamailio.cfg (i.e. like do what 'kamctl password' does, but in the routing logic)? Thank, Mike

1 0

Multiple crashes of Kamailio 4.2.1
by Igor Potjevlesch 16 Oct '15

16 Oct '15

Hello, 3 crashes occurred today (we never seen crashes on this server before) during a period of 20 minutes. I had a look to the coredumps. Here is a quick overview of the first entries of "bt full": core.27671 : #0 0x00007f5577048d65 in run_trans_callbacks_internal (cb_lst=0x7f5560abbd50, type=2, trans=0x7f5560abbce0, params=0x7fff3712acb0) at t_hooks.c:286 core.27656 : #0 0x00007f557700a048 in free_cell (dead_cell=0x7f5560abbce0) at h_table.c:175 core.27685 : #0 0x00007f5577048d65 in run_trans_callbacks_internal (cb_lst=0x7f5560abbd50, type=2, trans=0x7f5560abbce0, params=0x7fff3712acb0) at t_hooks.c:286 core.27689 : #0 0x00007f5577048d65 in run_trans_callbacks_internal (cb_lst=0x7f5560abbd50, type=2, trans=0x7f5560abbce0, params=0x7fff3712acb0) at t_hooks.c:286 core.27691 : #0 0x00007f5577048d65 in run_trans_callbacks_internal (cb_lst=0x7f5560abbd50, type=2, trans=0x7f5560abbce0, params=0x7fff3712acb0) at t_hooks.c:286 core.31977 : #0 0x00007f038e66fdee in free_cell (dead_cell=0x7f037811ebe0) at h_table.c:157 core.31994 : #0 0x00007f038e6ab65a in t_forward_nonack (t=0x7f037811ebe0, p_msg=0x7f038fdca438, proxy=0x0, proto=0) at t_fwd.c:1762 core.3700 : #0 0x000000000061697a in fm_insert_free (qm=0x7f19861fa000, frag=0x7f19864d53e8) at mem/f_malloc.c:245 core.3727 : #0 0x00000000006167a4 in fm_extract_free (qm=0x7f19861fa000, frag=0x7f19864f4cc8) at mem/f_malloc.c:208 I don't know how to proceed now. Can you help me to highlight the issue here? Thank you. Regards, Igor.

3 13

Re: [SR-Users] Auth module Issue:UA getting challanged thrice when load is high
by Daniel-Constantin Mierla 16 Oct '15

16 Oct '15

Hello, are there any error messages in the syslog? Maybe setting debug level for auth modules to 3 and looking at logs will help to reveal what is happening. Be sure syslog is in async mode, otherwise it will slow down processing. Cheers, Daniel On 16/10/15 08:42, Surendra.P wrote: > > Hello Daniel, > > > > I have a concern regarding auth module, I am running > 2000 TPS for 1000000 subscribers, using SIPP. What I observed when > you run small load like 500 TPS, everything get passed, but for 2000 TPS > > With same subscriber.csv file some of the subscribers getting > challenged. May I this why auth module is behaving like this.. below > are the parameters which I configured in auth module > > > > modparam("auth", "nonce_expire", 3600), rest all parameters default > values. > > > > Regards > > Surendra > > > > _______________________________________________ > 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 -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com

1 0

routing based on TLS auth
by Max 16 Oct '15

16 Oct '15

Hi. I've got bunch of sip gateways to use and bunch of asterisk instances connecting to my Kamailio over TLS (own CA used). I'd like to match source with destination based on TLS authentication: * all the calls from asterisk A (TLS cert A) allowed via provider A * all the calls from asterisk B (TLS cert B) allowed via provider B ... * all the incoming calls from provider A forwarded to asterisk A (TLS cert A) * all the incoming calls from provider B forwarded to asterisk B (TLS cert B) ... * calls not coming from provider X or via TLS dropped. Providers are regular VoIP gateways (login:password, connection via SIP). I'm pretty sure this is possible with Kamailio but I'd appreciate any examples and pointers to modules I should use to implement this. Or detailed explanation of why this is a bad idea. Also, I'm not sure where it's better to place user database - should it be separate on per-asterisk basis? Central in Kamailio? No user db needed at all? cheers, Max.

2 1

Auth module Issue:UA getting challanged thrice when load is high
by Surendra.P 16 Oct '15

16 Oct '15

Hello Daniel, I have a concern regarding auth module, I am running 2000 TPS for 1000000 subscribers, using SIPP. What I observed when you run small load like 500 TPS, everything get passed, but for 2000 TPS With same subscriber.csv file some of the subscribers getting challenged. May I this why auth module is behaving like this.. below are the parameters which I configured in auth module modparam("auth", "nonce_expire", 3600), rest all parameters default values. Regards Surendra

1 0

Strange TLS problem
by Pete Kelly 14 Oct '15

14 Oct '15

Hi I am trying to use the [client] directives in tls.cfg for the first time. For my configuration I need to connect to 2 servers, both via TLS and both using different certs. I have defined an entry in tls.cfg like [client:1.2.3.4:5061] [client:5.6.7.8:5071] and I also have an entry in dispatcher tables for each server using the URI format sip:1.2.3.4:5061;transport=tls With this configuration, I expect dispatcher to send OPTIONS to each server, and Kamailio to resolve the host in dispatcher to the correct client section of tls.cfg and negotiate a connection. However this is not happening. Dispatcher module is trying to send OPTIONS as expected, and it is using TLS as expected but it is not using the correct [client] section from tls.cfg. Instead it is always falling back to [client:default], and if that is not present it then tries to look for some internal Kamailio defaults. Has anyone come across this issue before? Debug logs don't yield anything useful, however my suspicion is that Kamailio may be trying to match "sip:1.2.3.4:5061;transport=tls" from dispatcher module to "1.2.3.4:5061" from tls.cfg. Any help or advice would be appreciated Regards Pete

2 2

setflag and hash table variables
by Asgaroth 14 Oct '15

14 Oct '15

I originally sent this to sr-dev in error, I am resending to sr-users instead, thanks Hi All, Quick question, is it possible to use variables in the setflag function, I am trying to set a flag that is stored in a hash table using the setflag function, but I keep getting syntax errors. I am using kamailio 4.3.3. Here's what I am trying to do: htable core_setid defines a dispatcher setid key and its value is associated with a flag as follows: id:key:key_type:value_type:value:expires 1:102:0:1:7:0 so, simple hash table type with an integer key of value 7 and no expiry In dispatcher I have the following modparams set, so that ds_is_from_list() will set them if found: modparam("dispatcher", "setid_pvname", "$var(ds_setid)") modparam("dispatcher", "attrs_pvname", "$var(ds_setid_attrs)") Then in my routing logic I have the following code block: if ( ds_is_from_list() ) { if ( $sht(core_setid=>$var(ds_setid)) != $null ) { setflag( $sht(core_setid=>$var(ds_setid)) ); return; } else { send_reply("403", "No flag set for source"); exit; } } When I test this using kamailio -c -f <filename> I get the following error: 0(20629) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /shared/kamailio/etc/routing_logic.cfg, line 175, column 21-52: syntax error 0(20629) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /shared/kamailio/etc/routing_logic.cfg, line 175, column 21-52: missing '(' or ')'? 0(20629) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /shared/kamailio/etc/routing_logic.cfg, line 175, column 21-52: bad command: missing ';'? 0(20629) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /shared/kamailio/etc/routing_logic.cfg, line 175, column 53: bad command ERROR: bad config file (4 errors) If I change the setflag line to setflag(7), then I dont get the error. I was wondering if its possible to have hashtable variables as parameters to the setflag function, or am I going about this in the wron way. Any thoughts would be appreciated. Thanks

2 3

debian jessie and dependencies
by nadie 14 Oct '15

14 Oct '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello. If you install mariadb instead mysql Oracle, and then, you want to install kamailio with kamailio-mysql-modules: No se satisfacen las dependencias de los siguientes paquetes: mariadb-client-core-10.0 : Entra en conflicto: mysql-client-5.5 pero se va a instalar 5.5.44-0+deb8u1. Rompe: virtual-mysql-client-core que es un paquete virtual. mysql-client-5.5 : Rompe: virtual-mysql-client que es un paquete virtual. Rompe: virtual-mysql-client-core que es un paquete virtual. mariadb-server-core-10.0 : Rompe: mysql-client-5.5 pero se va a instalar 5.5.44-0+deb8u1. mariadb-client-10.0 : Rompe: mysql-client pero se va a instalar 5.5.44-0+deb8u1. Rompe: mysql-client-5.5 pero se va a instalar 5.5.44-0+deb8u1. Rompe: virtual-mysql-client que es un paquete virtual. mariadb-server-10.0 : Rompe: mysql-client-5.5 pero se va a instalar 5.5.44-0+deb8u1. Las acciones siguientes resolverán estas dependencias Eliminar los paquetes siguientes: 1) mariadb-client-10.0 2) mariadb-client-core-10.0 3) mariadb-server 4) mariadb-server-10.0 5) mariadb-server-core-10.0 Thanks -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJWGzvRAAoJEG5DH1ilMeeeLl4P/iLDNNIhW73Sducag6IuJaM6 VWeKhCpvkEGxUUiAfL5Byktme058W6d1y7KDUyBzzMLZysNBxm4kJAX4fZjOQBpO 6e1np/qYXC/1A54hAKrjynPIMFpofCG3W6I2wCGp9nKHhq/ail++SW7aFqht6nus yF9h/0mJjv8wNkZuzf0BGuZdTJZUqVBbAOoWNNZHVfqQ20IjbAL2rgg/ahXLt8tv BoYVBnCQAAActmiA2ETF13R0ioJY5gLUorn2IW/sq/TQyXiABaskmxY68d/z2svc DmIB3JaCpOOMeccU4Ay2A6zmo+HuN5LcMuPu0b+sk3aHSWn6Wl4JWGozjdneiNpp +ksNTJYhJm6dCvhsj4RIw+ALf0/mDF14YV+n0z6OiaG5V1pEt7Z7nGyVBY3uDHR3 Xm9oYkj3CKYW5nOgpimHir9f+1qD457AWMRkHyIJrOXbth0lSodUg+KbAw1mUci5 D1E5bf47M7+CbmAi0t7uOSKh2J+oQq4pW3SzZYQbrnWQnIkwpmFy72Oqp7GBiSD7 rxxKUt0xBIVjnzGQzCgQdLfeYJt3sZ8V9cHvnEe7Tte2hLRLdnqskOhmMkGxNavJ ZKA7McTjWFyXJNJAJAowtBLHbarIxo5oREAma1nJ42xLv9KyIhXpVao472lVJZLz V9kMzZksd4yhvAHH2eyi =oZca -----END PGP SIGNATURE-----

2 4

Kamailio vs RTPEngine Performance
by M S 13 Oct '15

13 Oct '15

Hi, I was asked some interesting questions yesterday by a rather techy client related to Kamailio and RTPEngine performance. Q1: For Kamailio we have say 8 child processes, which means there are 8 threads per listen address to process sip messages, i.e. for example 8 INVITE messages at any instance of time can be processed by Kamailio. If say, one INVITE takes 200ms to be processed and send out to destination, then we can estimate processing power of kamailio to be 40 INVITE requests per second per listen address, right? Q2: If so, then assuming each INVITE requires to engage RTPEngine. How can we ensure that RTPEngine would be capable to handle these 40 INVITE requests? The only relevant parameter I see in RTPEngine daemon script is "NUM_THREADS" (default value 5). What does this represent? Does this analogs to children as in Kamailio? Q3: How does RTPEngine manages SRTP <=> RTP translation (e.g. if one endpoint is WebRTC and other is traditional SIP)? My understanding is that RTPEngine has a kernel module (assuming kernel module is installed) which also manages this conversion besides forwarding the media packets. The Linux kernel already has encoders / decoders for nearly all encryption algorithms which are utilized by RTPEngine for doing the conversion in kernel space, right? if not then how it is done? Q4: Continuing to Q2, If these NUM_THREADS process actual media packets (RTP or SRTP) then are these synchronous or asynchronous? I think these are asynchronous, just want to confirm (otherwise RTPEngine won't process more then e.g. 5 calls at a time). So, assuming asynchronous how many packets can be queue to each thread? This would help estimating RTPEngine throughput using various codecs in calls. (e.g. assuming G.711 codec we have 50pps, if each thread queue size is 1000 then each thread can process 1000/50=20 concurrent calls and whole RTPEngine would process 20x5=100 concurrent calls). Thank you.

1 0

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