- sr-users - kamailio.org

Kamilio new user - help get going
by Kenneth Knudsen 17 Jul '17

17 Jul '17

Hi I have been watching numerous videos on youtube in search of how to configure Kamilio ! I know we I need the Sip Server, but don't know how to get it configured. The installation is obvious with the commands as a root user. Brief description of the project: Have quite a few customers we want to move from PSTN (AT&T primarily) to a Voip/Sip solution. So instead of setting up 1 FreePBX and 1 public ip, we would rather use 1 public IP to many FreePBX servers on the backend. I haven't been able to find one video on how to configure this SIP server, and was hoping somebody here might have some clues to lead me in the right direction. I found one company that would help us, but they said at least 20 hours just to configure the first customer/freePBX installation. If we could get help setting up the first we should be able to figure out the ones to come later. Any help would be appreciated... We know the product is awesome, we have the keys but don't know how to run the thing or even get it started !! Kind regards, Kenneth Knudsen

6 11

Clarification on redis_cmd in ndb_redis module
by vivek＠advaitamtech.com 17 Jul '17

17 Jul '17

Hi, Am using redis_cmd in kamailio.cfg to perform redis operations. I would like to know if redis_cmd() creates new connection everytime I call it in kamailio.cfg?. Since am using redis_cmd() multiple times to access few data's. Also, is calling redis_free() necessary to avoid connections being open? I am facing an error of number of open files exceeded. This error is caused by ndb_redis module. But cannot confirm due to which part of redis. Thanks, Vivek

2 1

Need help to send INVITE to multiple client based on REGISTRATION status
by amit Kumar 15 Jul '17

15 Jul '17

Hi All, Following are the requirement which we want to achieve through Kamailio. Our "voip client" will not be register in advance.When Kamailio get INIVITE request for particular "voip client"(multiple client), we send push notification to make "voip client"(multiple client) alive and get it register for to Kamailio. Meanwhile INIVITE request will wait. the moment, "voip client" get register, Kamailio will send INIVITE to all the client despite their *registration time/status*.for example - if first client get register with in T+1 second,that should also get INVITE and another client get register in T+2 second that should also get INVITE. Could you please help me if this is possible in Kamailio. I have done some code walk through and have the basic idea to save the INVITE transaction(similar to suspend and continue), later point of time when i get the register request, I will use functionality like t_lookup_request and and lookup(which in turn append_branch) and call the t_realy () again. Please let me know if this is correct approach or if there is some other way to solve this. Thanks, Amit

2 1

Database connection handles vs. processes
by Alex Balashov 13 Jul '17

13 Jul '17

Hi, By way of illustration, I have one server with children=8, a single UDP listener, and 23 processes total: -- 21117 attendant 21118 udp receiver child=0 sock=xxx.xxx.xxx.xxx:5060 21119 udp receiver child=1 sock=xxx.xxx.xxx.xxx:5060 21120 udp receiver child=2 sock=xxx.xxx.xxx.xxx:5060 21121 udp receiver child=3 sock=xxx.xxx.xxx.xxx:5060 21122 udp receiver child=4 sock=xxx.xxx.xxx.xxx:5060 21123 udp receiver child=5 sock=xxx.xxx.xxx.xxx:5060 21124 udp receiver child=6 sock=xxx.xxx.xxx.xxx:5060 21125 udp receiver child=7 sock=xxx.xxx.xxx.xxx:5060 21126 slow timer 21127 timer 21128 MI FIFO 21129 ctl handler 21130 RTIMER USEC EXEC 21131 RTIMER USEC EXEC 21132 RTIMER USEC EXEC 21133 RTIMER USEC EXEC 21134 RTIMER USEC EXEC 21135 RTIMER USEC EXEC 21136 RTIMER USEC EXEC 21137 Dialog KA Timer 21138 Dialog Clean Timer 21139 tcp main process # kamcmd -s /tmp/kamailio_ctl ps | wc -l 23 -- This appears to result in 23 total database connections to the Postgres server: -- # lsof -n | grep -i '^kam' | grep IPv4 | grep TCP | grep -i :postgres | wc -l 23 -- But I have another Kamailio server that has three listeners, two UDP and one TCP, and children=24, i.e. -- children=24 listen=udp:xxx.xxx.xxx.xxx:5060 listen=udp:yyy.yyy.yyy.yyy:5060 listen=tcp:zzz.zzz.zzz.zzz:5060 -- I am given to understand that the total number of worker processes there will be (children_setting * listeners), i.e. 72 in this case, plus some number of rtimer and supervisory processes, as in my case. And true enough: -- # kamcmd -s /tmp/kamailio_ctl ps | wc -l 86 # kamcmd -s /tmp/kamailio_ctl ps | sed 's/65.254.44.195/yyy.yyy.yyy.yyy/g' | sed 's/65.254.44.194/zzz.zzz.zzz.zzz/g' 22065 main process - attendant 22069 udp receiver child=0 sock=zzz.zzz.zzz.zzz:5060 22070 udp receiver child=1 sock=zzz.zzz.zzz.zzz:5060 22071 udp receiver child=2 sock=zzz.zzz.zzz.zzz:5060 22073 udp receiver child=3 sock=zzz.zzz.zzz.zzz:5060 22074 udp receiver child=4 sock=zzz.zzz.zzz.zzz:5060 22076 udp receiver child=5 sock=zzz.zzz.zzz.zzz:5060 22079 udp receiver child=6 sock=zzz.zzz.zzz.zzz:5060 22080 udp receiver child=7 sock=zzz.zzz.zzz.zzz:5060 22082 udp receiver child=8 sock=zzz.zzz.zzz.zzz:5060 22085 udp receiver child=9 sock=zzz.zzz.zzz.zzz:5060 22086 udp receiver child=10 sock=zzz.zzz.zzz.zzz:5060 22089 udp receiver child=11 sock=zzz.zzz.zzz.zzz:5060 22091 udp receiver child=12 sock=zzz.zzz.zzz.zzz:5060 22093 udp receiver child=13 sock=zzz.zzz.zzz.zzz:5060 22095 udp receiver child=14 sock=zzz.zzz.zzz.zzz:5060 22097 udp receiver child=15 sock=zzz.zzz.zzz.zzz:5060 22099 udp receiver child=16 sock=zzz.zzz.zzz.zzz:5060 22100 udp receiver child=17 sock=zzz.zzz.zzz.zzz:5060 22103 udp receiver child=18 sock=zzz.zzz.zzz.zzz:5060 22105 udp receiver child=19 sock=zzz.zzz.zzz.zzz:5060 22107 udp receiver child=20 sock=zzz.zzz.zzz.zzz:5060 22109 udp receiver child=21 sock=zzz.zzz.zzz.zzz:5060 22111 udp receiver child=22 sock=zzz.zzz.zzz.zzz:5060 22113 udp receiver child=23 sock=zzz.zzz.zzz.zzz:5060 22115 udp receiver child=0 sock=yyy.yyy.yyy.yyy:5060 22117 udp receiver child=1 sock=yyy.yyy.yyy.yyy:5060 22119 udp receiver child=2 sock=yyy.yyy.yyy.yyy:5060 22121 udp receiver child=3 sock=yyy.yyy.yyy.yyy:5060 22123 udp receiver child=4 sock=yyy.yyy.yyy.yyy:5060 22125 udp receiver child=5 sock=yyy.yyy.yyy.yyy:5060 22127 udp receiver child=6 sock=yyy.yyy.yyy.yyy:5060 22129 udp receiver child=7 sock=yyy.yyy.yyy.yyy:5060 22131 udp receiver child=8 sock=yyy.yyy.yyy.yyy:5060 22132 udp receiver child=9 sock=yyy.yyy.yyy.yyy:5060 22135 udp receiver child=10 sock=yyy.yyy.yyy.yyy:5060 22137 udp receiver child=11 sock=yyy.yyy.yyy.yyy:5060 22139 udp receiver child=12 sock=yyy.yyy.yyy.yyy:5060 22141 udp receiver child=13 sock=yyy.yyy.yyy.yyy:5060 22143 udp receiver child=14 sock=yyy.yyy.yyy.yyy:5060 22145 udp receiver child=15 sock=yyy.yyy.yyy.yyy:5060 22147 udp receiver child=16 sock=yyy.yyy.yyy.yyy:5060 22149 udp receiver child=17 sock=yyy.yyy.yyy.yyy:5060 22151 udp receiver child=18 sock=yyy.yyy.yyy.yyy:5060 22153 udp receiver child=19 sock=yyy.yyy.yyy.yyy:5060 22155 udp receiver child=20 sock=yyy.yyy.yyy.yyy:5060 22156 udp receiver child=21 sock=yyy.yyy.yyy.yyy:5060 22159 udp receiver child=22 sock=yyy.yyy.yyy.yyy:5060 22161 udp receiver child=23 sock=yyy.yyy.yyy.yyy:5060 22163 slow timer 22165 timer 22167 secondary timer 22168 ctl handler 22169 RTIMER USEC EXEC 22170 RTIMER USEC EXEC 22172 RTIMER USEC EXEC 22173 RTIMER USEC EXEC 22175 Dialog Clean Timer 22176 TIMER NH 22177 TIMER NH 22178 TIMER NH 22179 tcp receiver (generic) child=0 22180 tcp receiver (generic) child=1 22182 tcp receiver (generic) child=2 22184 tcp receiver (generic) child=3 22186 tcp receiver (generic) child=4 22188 tcp receiver (generic) child=5 22190 tcp receiver (generic) child=6 22192 tcp receiver (generic) child=7 22194 tcp receiver (generic) child=8 22196 tcp receiver (generic) child=9 22198 tcp receiver (generic) child=10 22200 tcp receiver (generic) child=11 22202 tcp receiver (generic) child=12 22204 tcp receiver (generic) child=13 22206 tcp receiver (generic) child=14 22208 tcp receiver (generic) child=15 22210 tcp receiver (generic) child=16 22212 tcp receiver (generic) child=17 22214 tcp receiver (generic) child=18 22216 tcp receiver (generic) child=19 22218 tcp receiver (generic) child=20 22220 tcp receiver (generic) child=21 22223 tcp receiver (generic) child=22 22225 tcp receiver (generic) child=23 22227 tcp main process -- But, for some reason, the number of database connections to Postgres seems to be considerably higher than the number of total processes: -- # lsof -n | grep '^kam' | grep TCP | grep IPv4 | grep ':postgres' | wc -l 114 -- This is not due to orphaned/unterminated Kamailio processes. There's only one process lineage: -- |-kamailio(22065)-+-kamailio(22069) | |-kamailio(22070) | |-kamailio(22071) | |-kamailio(22073) | |-kamailio(22074) | |-kamailio(22076) | |-kamailio(22079) | |-kamailio(22080) | |-kamailio(22082) | |-kamailio(22085) | |-kamailio(22086) | |-kamailio(22089) | |-kamailio(22091) | |-kamailio(22093) | |-kamailio(22095) | |-kamailio(22097) | |-kamailio(22099) | |-kamailio(22100) | |-kamailio(22103) | |-kamailio(22105) | |-kamailio(22107) | |-kamailio(22109) | |-kamailio(22111) | |-kamailio(22113) | |-kamailio(22115) | |-kamailio(22117) | |-kamailio(22119) | |-kamailio(22121) | |-kamailio(22123) | |-kamailio(22125) | |-kamailio(22127) | |-kamailio(22129) | |-kamailio(22131) | |-kamailio(22132) | |-kamailio(22135) | |-kamailio(22137) | |-kamailio(22139) | |-kamailio(22141) | |-kamailio(22143) | |-kamailio(22145) | |-kamailio(22147) | |-kamailio(22149) | |-kamailio(22151) | |-kamailio(22153) | |-kamailio(22155) | |-kamailio(22156) | |-kamailio(22159) | |-kamailio(22161) | |-kamailio(22163) | |-kamailio(22165) | |-kamailio(22167) | |-kamailio(22168) | |-kamailio(22169) | |-kamailio(22170) | |-kamailio(22172) | |-kamailio(22173) | |-kamailio(22175) | |-kamailio(22176) | |-kamailio(22177) | |-kamailio(22178) | |-kamailio(22179) | |-kamailio(22180) | |-kamailio(22182) | |-kamailio(22184) | |-kamailio(22186) | |-kamailio(22188) | |-kamailio(22190) | |-kamailio(22192) | |-kamailio(22194) | |-kamailio(22196) | |-kamailio(22198) | |-kamailio(22200) | |-kamailio(22202) | |-kamailio(22204) | |-kamailio(22206) | |-kamailio(22208) | |-kamailio(22210) | |-kamailio(22212) | |-kamailio(22214) | |-kamailio(22216) | |-kamailio(22218) | |-kamailio(22220) | |-kamailio(22223) | |-kamailio(22225) | `-kamailio(22227) -- Yet, for some reason, some of the processes have two established DB connections from different ports: -- kamailio 22220 root 3u IPv4 189895303 0t0 TCP 127.0.0.1:46550->127.0.0.1:postgres (ESTABLISHED) kamailio 22220 root 86u IPv4 189895067 0t0 TCP 127.0.0.1:46458->127.0.0.1:postgres (ESTABLISHED) kamailio 22223 root 3u IPv4 189895315 0t0 TCP 127.0.0.1:46556->127.0.0.1:postgres (ESTABLISHED) kamailio 22223 root 86u IPv4 189895067 0t0 TCP 127.0.0.1:46458->127.0.0.1:postgres (ESTABLISHED) kamailio 22225 root 3u IPv4 189895321 0t0 TCP 127.0.0.1:46560->127.0.0.1:postgres (ESTABLISHED) kamailio 22225 root 86u IPv4 189895067 0t0 TCP 127.0.0.1:46458->127.0.0.1:postgres (ESTABLISHED) kamailio 22227 root 86u IPv4 189895067 0t0 TCP 127.0.0.1:46458->127.0.0.1:postgres (ESTABLISHED) -- ... while others don't ... -- kamailio 22111 root 3u IPv4 189894820 0t0 TCP 127.0.0.1:46326->127.0.0.1:postgres (ESTABLISHED) kamailio 22113 root 3u IPv4 189894828 0t0 TCP 127.0.0.1:46332->127.0.0.1:postgres (ESTABLISHED) kamailio 22115 root 3u IPv4 189894834 0t0 TCP 127.0.0.1:46334->127.0.0.1:postgres (ESTABLISHED) kamailio 22117 root 3u IPv4 189894842 0t0 TCP 127.0.0.1:46338->127.0.0.1:postgres (ESTABLISHED) kamailio 22119 root 3u IPv4 189894848 0t0 TCP 127.0.0.1:46340->127.0.0.1:postgres (ESTABLISHED) -- So, this gives rise to two questions in my mind: 1. I don't seem to understand the relationship between the number of database connection handles and the total number of child processes. I had always assumed that only SIP workers and other processes specialised into a role with possible "database involvement" (e.g. rtimer, async workers, etc.) would hold database connections. 2. What's going on in the second scenario such that some processes have two connections? Both servers running: -- # kamcmd -s /tmp/kamailio_ctl core.version kamailio 4.4.6 (x86_64/linux) becbde -- Insights much appreciated! -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

5 12

What happens to calls when Kamailio restarts?
by Samuel F. 13 Jul '17

13 Jul '17

Hi, I have a question regarding calls and Kamailio restarts. Suppose Kamailio crashes (and started again), is restarted or failed over to a different server (same IP). What then happens with calls? Let's suppose the following scenario: - 1000 calls active on the machine - Some are in call setup, some are in call, some are in teardown phases - The proxy is stateful - The proxy forwards calls from B2BUA machines to an ITSP (outbound only) - Uses record-routing - Uses loose routing What will be the likely outcome of the restart with regards to the calls in the different phases and accounting for said calls? All the best, Samuel

4 6

Subst_body M Audio
by Nicolas Breuer 13 Jul '17

13 Jul '17

Hello, I'm trying to replace the M part in the SDP Body. Seems not working as expected ( I changed the "s" part without problems ) Code : if ( subst_body('/(^m=.*)/m=testing of rewrite.\r/') ) { $var(s)=""; }; Here's the incoming body message c=IN IP4 217.112.180.235. t=0 0. m=audio 49152 RTP/AVP 8 9 18 101. a=rtpmap:8 PCMA/8000. a=rtpmap:9 G722/8000. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. After subst. ( note the .10840 on the m line) c=IN IP4 217.112.180.10. t=0 0. m=testing of rewrite..10840 a=rtpmap:8 PCMA/8000. a=rtpmap:9 G722/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=nortpproxy:yes.

2 3

issue sending http_async_client POST request
by Abdul Basit 13 Jul '17

13 Jul '17

Hi folks, I am using kamailio -v version: kamailio 5.0.2 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled on 10:02:27 Jul 4 2017 with gcc 4.9.2 I was trying to send http POST request to my web server example.com following example Example 1.12. http_async_query() usage <https://www.kamailio.org/docs/modules/5.0.x/modules/http_async_client.html#…> https://www.kamailio.org/docs/modules/5.0.x/modules/http_async_client.html according to that we should send parameters in body like # POST $http_req(body) = "{'r_uri':'" + $rU + "', 'f_uri':'" + $fU + "'}"; http_async_query("http://example.com/test.php", "HTTP_REPLY"); But its not working out of the box as described with error message from server: INFO: <script>: route[HTTP_REPLY]: status 400 INFO: <script>: route[HTTP_REPLY]: body Insufficient parameters. I even tried adding additional parameters $http_req(hdr) = "Content-Type: application/x-www-form-urlencoded"; $http_req(method) = "POST"; But again it didn't work. I tried the alternative way which worked fine. # POST $http_req(body) = "r_uri=$rU&f_uri=$fU"; http_async_query("http://example.com/test.php", "HTTP_REPLY"); Is there any issue with documentation or i am missing something for POST request? -- regards, abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445

3 4

issue sending http_async_client POST request
by Abdul Basit 13 Jul '17

13 Jul '17

Hi folks, I am using I was trying to send http POST request to my web server example.com following example Example 1.12. http_async_query() usage <https://www.kamailio.org/docs/modules/5.0.x/modules/http_async_client.html#…> https://www.kamailio.org/docs/modules/5.0.x/modules/http_async_client.html according to that we should send parameters in body like # POST $http_req(body) = "{'r_uri':'" + $rU + "', 'f_uri':'" + $fU + "'}"; http_async_query("http://example.com/test.php", "HTTP_REPLY"); But its not working out of the box as described with error message from server: INFO: <script>: route[HTTP_REPLY]: status 400 INFO: <script>: route[HTTP_REPLY]: body Insufficient parameters. I even tried adding additional parameters $http_req(hdr) = "Content-Type: application/x-www-form-urlencoded"; $http_req(method) = "POST"; But again it didn't work. I tried the alternative way which worked fine. # POST $http_req(body) = "r_uri=$rU&f_uri=$fU"; http_async_query("http://example.com/test.php", "HTTP_REPLY"); Is there any issue with documentation or i am missing something for POST request? -- regards, abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445

1 0

Call is not placing in kamailio
by Logeshwaran G 13 Jul '17

13 Jul '17

Dear Team, I have installed Kamailio-5.0, and i have included subscriber table as well. Two users have successfully registered but cant able to place the call in between the users. Kindly help me for placing the call. Thanks in Advance, Logesh

2 9

RTPProxy - lookup request failed
by Marian Piater 12 Jul '17

12 Jul '17

Hello, I have a problem with RTPProxy. Scenario: SS7 (PSTN) ---> ASTERISK BOX --> Kamailio --> UAC In case of incoming call from PSTN, when called party answer the call after 60 seconds of ringing, then the call is without audio and in this case I see in the log this message: Creating session Jul 11 11:24:32 b2b-voice-sipproxy-v3 rtpproxy[731]: INFO:handle_command: new session 766d0e006d8969d36c628e363ea7c3e1(a)upc.cz, tag as7a7c86ae;1 requested, type strong Jul 11 11:24:32 b2b-voice-sipproxy-v3 rtpproxy[731]: INFO:handle_command: new session on a port 52902 created, tag as7a7c86ae;1 Jul 11 11:24:32 b2b-voice-sipproxy-v3 rtpproxy[731]: INFO:handle_command: pre-filling caller's address with XXX.XXX.XXX.XXX:32740 Answer after approx 60 seconds Jul 11 11:25:40 b2b-voice-sipproxy-v3 rtpproxy[731]: INFO:handle_command: lookup request failed: session 766d0e006d8969d36c628e363ea7c3e1(a)upc.cz, tags as7a7c86ae;1/l0g9iusua2;1 not found Jul 11 11:25:40 b2b-voice-sipproxy-v3 rtpproxy[731]: INFO:handle_delete: forcefully deleting session 1 on ports 35196/36656 Kamailio log (answer) Jul 11 11:25:40 b2b-voice-sipproxy-v3 kamailio[5268]: INFO: <script>: UID:766d0e006d8969d36c628e363ea7c3e1@upc.cz -- ONREPLY_ROUTE: rtpproxy_manage(co) Jul 11 11:25:40 b2b-voice-sipproxy-v3 kamailio[5268]: ERROR: rtpproxy [rtpproxy.c:2536]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy It looks like there is somewhere 60 seconds session timeout. But I don't know where. When the call is answered during first 60 seconds, then everything is OK and we have both audio. Kamailio reply route configuration: onreply_route[REPLYROUTE] { # #-- On-replay block routing -- # xlog("L_INFO","UID:$ci -- ONREPLY_ROUTE1: $rm $si avp $avp(s:131) $avp(s:132)"); if(has_body("application/sdp")) { xlog("L_INFO","UID:$ci -- ONREPLY_ROUTE: rtpproxy_manage(co)"); rtpproxy_manage("co"); } if ((isflagset(FLT_NATS) || isbflagset(FLB_NATB)) && status=~"(183)|(2[0-9][0-9])"){ xlog("L_INFO","UID:$ci -- ONREPLY_ROUTE1: force_rtp_proxy"); append_hf("P-hint: onreply_route|force_rtp_proxy \r\n"); } if (isbflagset(FLB_NATB)) { xlog("L_INFO","UID:$ci -- ONREPLY_ROUTE1: P-hint: Onreply-route - fixcontact"); append_hf("P-hint: Onreply-route - fixcontact \r\n"); fix_nated_contact(); } exit; } Some parameters settings. modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722") modparam("rtpproxy", "extra_id_pv", "$avp(extra_id)") modparam("rtpproxy", "rtpproxy_disable_tout", 20) modparam("rtpproxy", "rtpproxy_tout", 2) modparam("tm", "disable_6xx_block", 1) modparam("tm", "fr_timer", 5000) ## 5 seconds. modparam("tm", "restart_fr_on_each_reply", 0) modparam("tm", "auto_inv_100_reason", "Trying") modparam("dialog", "dlg_flag", 4) modparam("dialog", "rr_param", "rtp") modparam("dialog", "default_timeout", 7230) modparam("dialog", "dlg_match_mode", 1) modparam("dialog", "db_mode", 1) modparam("dialog", "enable_stats", 1) modparam("dialog", "send_bye", 1) modparam("dialog", "lreq_callee_headers", "TH: dlh\r\n") modparam("rr", "enable_full_lr", 1) modparam("rr", "append_fromtag", 1) modparam("rr", "enable_double_rr", 1) RTPproxy is installed from Debian package: /usr/bin/rtpproxy -s udp:127.0.0.1 7722 -u rtpproxy rtpproxy -p /var/run/rtpproxy/rtpproxy.pid -F -l XXX.XXX.XXX.XXX -d DBUG LOG_LOCAL0 Any advice? Thanks

3 9

Re: [SR-Users] Setup IMS core Network When Network behind nat
by Mojtaba 12 Jul '17

12 Jul '17

Hi. I found where was my problem. I had a misunderestanding. I used public domaim as outbound proxy and i could register to ims. On 11 Jul 2017 15:00, "Mojtaba" <mespio(a)gmail.com> wrote: > Hi Daniel. > Let me describe more clearly the network. Let me suppose these > configurations: > Private IMS Domain: kamailio0ims.test (192.168.100.200) > username: bob(a)kamailio-ims.test > secret: bob > outboundproxy: pcscf.kamailio-ims.test (192.168.100.101) > With these informations, all things works correctly. > Now suppose we have one public IP with predefined > domain(sbc.ims-domain.com) that is set on PCSCF.(This node has two ip > address, one private ip and on public ip), > How can the bob register to network like as before?because the domain > sbc.ims-domain.com is not validate on IMS network. > should i use the sems-sbc? becuase in this situation the private > domain is not reachables. > If it is needed, let me to describe more. > Thanks > > > > On Tue, Jul 11, 2017 at 2:24 PM, Daniel-Constantin Mierla > <miconda(a)gmail.com> wrote: > > Hello, > > > > do you want the entire platform to be behind a single public ip, or each > > node in the network to run on a private ip but have also a public ip > > associated? > > > > Cheers, > > Daniel > > > > > > On 11.07.17 11:31, Mojtaba wrote: > >> Hello, I am working on IMS core network. In this network we have these > >> node with private IP: > >> P-CSCF: 192.168.100.101(pcscf.kamailio-ims.test) > >> I-CSCF: 192.168.100.102(icscf.kamailio-ims.test) > >> S-CSCF: 192.168.100.103(scscf.kamailio-ims.test) > >> HSS: 192.168.100.200(hss.kamailio-ims.test) > >> I have two default users (bob and alice) and all things right great. > >> Now i want use this network with one public IP behind nat. Let me know > >> What should i do? > >> In one way i could use SEMS-SBC and set public IP on it, How should i > >> config sems-sbc to work correctly? > >> Thanks.With Regads. > >> M.ES.S > >> > >> _______________________________________________ > >> Kamailio (SER) - Users Mailing List > >> sr-users(a)lists.kamailio.org > >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > > > -- > > Daniel-Constantin Mierla > > www.twitter.com/miconda -- www.linkedin.com/in/miconda > > Kamailio Advanced Training - www.asipto.com > > Kamailio World Conference - www.kamailioworld.com > > > > > > -- > --Mojtaba Esfandiari.S >

2 1

New Diameter IMS Module : can we use it as SWx interface
by Igor Potjevlesch 11 Jul '17

11 Jul '17

Dear Kamailio users, Recently has been added to Kamailio two new modules : CDP and CDP_AVP There is not the TS 29.273 in it but I wanted to know if we can use it to emulate SWx interface? or add it with a non-hardcoded solution? I have seen the kamailio conference online and one session told about emulate IMS HSS with those two modules. Is someone tried to do it and want to share is experience with me ? Some DIAMETER functions in these modules are closed from the SWx. Best regards Igor Potjevlesch --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus

2 1

Setup IMS core Network When Network behind nat
by Mojtaba 11 Jul '17

11 Jul '17

Hello, I am working on IMS core network. In this network we have these node with private IP: P-CSCF: 192.168.100.101(pcscf.kamailio-ims.test) I-CSCF: 192.168.100.102(icscf.kamailio-ims.test) S-CSCF: 192.168.100.103(scscf.kamailio-ims.test) HSS: 192.168.100.200(hss.kamailio-ims.test) I have two default users (bob and alice) and all things right great. Now i want use this network with one public IP behind nat. Let me know What should i do? In one way i could use SEMS-SBC and set public IP on it, How should i config sems-sbc to work correctly? Thanks.With Regads. M.ES.S

2 1

Siremis updates
by Daniel-Constantin Mierla 11 Jul '17

11 Jul '17

Hello, there is some ongoing work on Siremis (web management interface for kamailio) to make it fully compatible with Kamailio 5.0.x as well as update some of its legacy components: - https://github.com/asipto/siremis So I thought to start a discussion here and see if some of those changes are going to impact too much existing installations or what are the best options to use for the future. Done so far: 1) implemented the JSONRPC client using UDP and unix domain sockets, to work in pair with jsonrpcs module as a replacement for removed MI interface. The old JSONRPC over HTTP is still an option. 2) charts system has been migrated from open flash chart (ofc) to echarts (pure html5/javascript) -- therefore no more requiring to enable flash in browser. Configuration is the same and the charts should look pretty similar. If you upgrade, apart of different html view for the charts, the config files should not be changed. If you notice something broken, open an issue on github project linked above. Planned to be done: 3) Relocate siremis/modules/ser to siremis/modules/sipadmin -- this purely for more suggestive name for the admin module related to the SIP services offered by Kamailio, and be in pair with the module sipuser. This is mainly search and replace over php and xml files, however, it is going to impact if you developed your own internal extensions for siremis and placed them in the 'ser' module. It will require that you do the same search+replace 4) Review existing database tables views and add fields for missing columns. 5) Add views for other database tables. First in my mind being the table for rtpengine module. If you use some modules with tables not yet managed by siremis, reply and list them to set a list of priorities. Should have other things to report about siremis and are not yet listed on project's issue tracker, let's discuss here. Testing and feedback for 1) and 2) are very appreciated! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com

1 1

deb nightly-builds not being built
by Victor Seva 10 Jul '17

10 Jul '17

We are having some issues with our building infrastructure so packages are not being built. We are working on it, please be patient. Cheers, Victor

2 3

m_dump sends multiple messages
by Rahul Mehta 10 Jul '17

10 Jul '17

hello, when m_dump() function is called as user gets online, the function i.e=m_dump() sends multiple copies of same message,can anyone please provide way to stop m_dump() sending multiple copies of same message. I am providing the code of m_dump function if (m_dump("$fu")) { xlog("L_INFO","MSILO: offline messages dumped - if they were\n"); }else{ xlog("L_INFO","MSILO: no offline messages dumped\n"); };

2 1

kamctl v5 issues sending rpc from jsonrpc_exec_ex
by Abdoul Osséni 10 Jul '17

10 Jul '17

Hello, Got this error : ERROR: jsonrpcs [jsonrpcs_mod.c:1323]: jsonrpc_exec_ex(): method callback not found [dlg.end_dlg 3660 9594] Regards

2 3

domain vs uid_domain module
by Huber Andreas 10 Jul '17

10 Jul '17

Hi, I was comparing the documentation of the "uid_domain" and "domain" modules and I was wondering what is the main difference between the two modules. While the "uid_domain" module has more documentation, it seems to me that both modules are offering very similar functionality, or am I missing something ? Also I found it curious that the documentation of the "uid_domain" module uses "domain" as the module name in all its examples for the module configuration. E.g. modparam("domain", "domain_table", "new_name") But when I try to use the "uid_domain" module, I actually have to specify the parameters as : modparam("uid_domain", "domain_table", "new_name") The same question also applies to the "uid_auth_db" module that resembles closely the "auth_db" module in the documentation, but not in the implementation. Kind Regards, Andreas

2 1

app_lua reload - what exactly gets reloaded?
by Sebastian Damm 10 Jul '17

10 Jul '17

Hi, we have written some logic for a project in lua. There is a small function that gets called from Kamailio, but the main logic is done in a self-written module. That module does initialize some values from database on the first request that comes in. Now when reloading app_lua from kamcmd or via jsonrpc, I don't see the log output generated when initializing. In the debug log, I can see that the reload is taking place, but the variables and state seem to not get reset. What does the reload command actually reload? Best Regards, Sebastian

2 7

How to delay messages when msilo messages are dumped
by Rahul Mehta 10 Jul '17

10 Jul '17

Hello, We are facing scenario when msilo dump function is called the user's device gets hanged/crash as messages are sent together to the user who gets online,please provide solution how to delay the messages which are send to the user when 'm_dump' function is called. I am providing the code of m_dump function if (m_dump("$fu")) { xlog("L_INFO","MSILO: offline messages dumped - if they were\n"); }else{ xlog("L_INFO","MSILO: no offline messages dumped\n"); };

2 1

Random Proxy Crash, Restarted OK Anything Here For Concern?
by JR Richardson 10 Jul '17

10 Jul '17

Hi All, I have a basic proxy up and running for over 6 months without issue, had a random crash, not sure why. Restarted kamailio process and it's working as expected. Any clue is the log to indicate what might have happened? ----snip---- Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13416]: : <core> [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already freed pointer (0x7fa1e1ebd658), called from <core>: mem/shm_mem.c: sh_realloc(88), first free <core>: mem/shm_mem.c: sh_realloc(88) - aborting Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13415]: ALERT: <core> [main.c:775]: handle_sigs(): child process 13416 exited by a signal 6 Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13415]: ALERT: <core> [main.c:778]: handle_sigs(): core was not generated Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13415]: INFO: <core> [main.c:790]: handle_sigs(): INFO: terminating due to SIGCHLD Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13423]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13420]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13424]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13419]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13421]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13422]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13418]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13417]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13415]: ERROR: ctl [ctl.c:379]: mod_destroy(): ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: Operation not permitted (1) ----snip---- RTPProxy also running on the server was not affected. root@sip-router3-ve206:/var/log# kamailio -V version: kamailio 4.1.0 (x86_64/linux) 350d2e 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, DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 350d2e compiled on 16:41:38 Dec 17 2013 with gcc 4.4.5 Yes, I know it's an older version but I prefer not to upgrade unless absolutely necessary. I'm sure this was a random event, not too concerned but since it is a production server, I'm obligated to investigate. Thanks. JR -- JR Richardson Engineering for the Masses Chasing the Azeotrope

3 2

remove_hf_re error on startup
by Grant Bagdasarian 07 Jul '17

07 Jul '17

Hi, I'm trying to remove all custom headers starting with X-, except a certain header, but Kamailio won't start due to an error. ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:455 remove_hf_re("^(?!X-ThisHeaderShouldNotBeRemoved)X-.*") or remove_hf_re("^(?!X- ThisHeaderShouldNotBeRemoved)X-") This is valid regex according to https://regex101.com/ Any idea's why this won't compile? Regards, Grant

3 3

How to convert ipv6 to ipv4 address inside message body
by Narayan P 07 Jul '17

07 Jul '17

Hi, I am using kamailio as outbound proxy integrated with rtpproxy.I have done the configuration of ipv6 to ipv4 network. But when 183 session progress came ,kamailio is sending its ipv6 address to pjsip client inside sdp body.So that it is not accepting and 488 error message is giving. How to convert ipv6 to ipv4 inside kamailio so that pjsip can accept. Below is the sip trace from client. 20:49:20.152 pjsua_app.c .....Call 0 state changed to EARLY (183 Session progress) 20:49:20.152 pjsua_media.c .....Call 0: updating media.. 20:49:20.152 pjsua_media.c ......pjmedia_stream_info_from_sdp() failed for call_id 0 media 0: Unsupported address family (PJ_EAFNOTSUP) 20:49:20.152 pjsua_media.c ......Error updating media call00:0: Unsupported address family (PJ_EAFNOTSUP) 20:49:20.152 pjsua_call.c .....Unable to create media session: No active media stream after negotiation (PJMEDIA_SDPNEG_ENOMEDIA) [status=220048] 20:49:20.152 pjsua_core.c ........TX 418 bytes Request msg CANCEL/cseq=12308 (tdta0x7f0b28008400) to UDP 2001:db8:bad:a55::2:5070: CANCEL sip:919035438928@185.122.206.62 SIP/2.0 Via: SIP/2.0/UDP [2001:DB8:BAD:A55:0:0:0:2]:5077;rport;branch=z9hG4bKPj8pbyM6u7jh2tBncOqhPSbPMA8mK4RaIz Max-Forwards: 70 From: sip:OTT919620649614@185.122.206.62;tag=YZDJ3TTb4kDIO2.0Bvuw8nrkTTNPBwtm To: <sip:919035438928@185.122.206.62> Call-ID: 7otfmBr7j6wvfhjlApd0xcHOPp6wsII6 CSeq: 12308 CANCEL Route: <sip:[2001:db8:bad:a55::2]:5070;lr> Content-Length: 0 --end msg-- 20:49:20.154 pjsua_core.c .RX 457 bytes Response msg 200/CANCEL/cseq=12308 (rdata0x7f0b28001d08) from UDP 2001:db8:bad:a55::2:5070: SIP/2.0 200 canceling Via: SIP/2.0/UDP [2001:DB8:BAD:A55:0:0:0:2]:5077;rport=5077;branch=z9hG4bKPj8pbyM6u7jh2tBncOqhPSbPMA8mK4RaIz;received=2001:DB8:BAD:A55:0:0:0:2 From: sip:OTT919620649614@185.122.206.62;tag=YZDJ3TTb4kDIO2.0Bvuw8nrkTTNPBwtm To: <sip:919035438928@185.122.206.62>;tag=6374de6d95f421336d5241fc0a072275-2b9b Call-ID: 7otfmBr7j6wvfhjlApd0xcHOPp6wsII6 CSeq: 12308 CANCEL Server: kamailio (5.0.0-dev5 (x86_64/linux)) Content-Length: 0 --end msg-- 20:49:20.310 pjsua_core.c .RX 380 bytes Response msg 487/INVITE/cseq=12308 (rdata0x7f0b28001d08) from UDP 2001:db8:bad:a55::2:5070: SIP/2.0 487 Request Terminated Via: SIP/2.0/UDP [2001:DB8:BAD:A55:0:0:0:2]:5077;rport=5077;branch=z9hG4bKPj8pbyM6u7jh2tBncOqhPSbPMA8mK4RaIz;received=2001:DB8:BAD:A55:0:0:0:2 From: <sip:OTT919620649614@185.122.206.62>;tag=YZDJ3TTb4kDIO2.0Bvuw8nrkTTNPBwtm To: <sip:919035438928@185.122.206.62> CSeq: 12308 INVITE Call-ID: 7otfmBr7j6wvfhjlApd0xcHOPp6wsII6 Content-Length: 0 --end msg-- 20:49:20.310 pjsua_core.c ..TX 412 bytes Request msg ACK/cseq=12308 (tdta0x7f0b2800cf40) to UDP 2001:db8:bad:a55::2:5070: ACK sip:919035438928@185.122.206.62 SIP/2.0 Via: SIP/2.0/UDP [2001:DB8:BAD:A55:0:0:0:2]:5077;rport;branch=z9hG4bKPj8pbyM6u7jh2tBncOqhPSbPMA8mK4RaIz Max-Forwards: 70 From: sip:OTT919620649614@185.122.206.62;tag=YZDJ3TTb4kDIO2.0Bvuw8nrkTTNPBwtm To: <sip:919035438928@185.122.206.62> Call-ID: 7otfmBr7j6wvfhjlApd0xcHOPp6wsII6 CSeq: 12308 ACK Route: <sip:[2001:db8:bad:a55::2]:5070;lr> Content-Length: 0 --end msg-- 20:49:20.311 pjsua_app.c .....Call 0 is DISCONNECTED [reason=488 (Not Acceptable Here)] 20:49:20.311 pjsua_app_comm ..... [DISCONNCTD] To: <sip:919035438928@185.122.206.62>;tag=GB-1498835320600 Call time: 00h:00m:00s, 1st res in 361 ms, conn in 0ms #0 audio deactivated 20:49:20.311 pjsua_media.c .....Call 0: deinitializing media.. 20:49:20.311 pjsua_media.c .......Media stream call00:0 is destroyed 20:49:21.311 pjsua_aud.c !Closing sound device after idle for 1 second(s) 20:49:21.311 pjsua_app.c .Turning sound device OFF 20:49:21.311 pjsua_aud.c .Closing default sound playback device and default sound capture device Any suggestion will be highly appreciated. Thanks, Narayan

3 2

SUBSCRIBE not work with public ip kamailio
by Nguyen Tran Nhan 07 Jul '17

07 Jul '17

Hello, I am using Kamailio with SEMS and rtpproxy for public ip address. I got issue that SUBSCRIBE message does not work. SUBSCRIBE works well with private ip address. Anyone face with this issue? Thanks, Nhan

2 5

Dialog List cannot be listed using kamcmd
by Muhammad Zaka 07 Jul '17

07 Jul '17

Hi We have over 400 active dialogs and I wanted to list all of them but it doesn't list any : - root@kamailio:~# kamcmd dlg.list ERROR: reply too big The command works fine when we have few dialogs. Is there any way to list all the active dialogs? Many Thanks Regards Muhammad Zaka

3 4

Kamilio doesn't start up with pymongo in the Kemi Python script..
by Muhammad Zaka 06 Jul '17

06 Jul '17

Hi all, In kamailio 5.0.1 with kemi interface for python I am trying to use pymongo to import Mongo Client interface for python but the kamailio service fails to start up properly. kamailio-kemi-python.py import sys import struct import Router.Logger as Logger import KSR as KSR from pymongo import MongoClient Case - I : No forking and no children in kamailio.cfg kamailio.cfg fork=no children=0 Kamailio service fails with the following error: - Jun 20 15:12:32 sbc99-kam-dev kamailio: ERROR: app_python [python_support.c:142]: python_handle_exception(): mod_init: Unhandled exception in the Python code:#012Traceback (most recent call last):#012 File "/etc/kamailio/kamailio-kemi-python.py", line 19, in <module>#012 from pymongo import MongoClient#012 File "/usr/local/lib/python2.7/dist-packages/pymongo/__init__.py", line 87, in <module>#012 from pymongo.mongo_client import MongoClient#012 File "/usr/local/lib/python2.7/dist-packages/pymongo/mongo_client.py", line 52, in <module>#012 from pymongo.client_options import ClientOptions#012 File "/usr/local/lib/python2.7/dist-packages/pymongo/client_options.py", line 23, in <module>#012 from pymongo.pool import PoolOptions#012 File "/usr/local/lib/python2.7/dist-packages/pymongo/pool.py", line 121, in <module>#012 ('type', platform.system()),#012 File "/usr/lib/python2.7/platform.py", line 1333, in system#012 return uname()[0]#012 File "/usr/lib/python2.7/platform.py", line 1300, in uname#012 processor = _syscmd_uname('-p','')#012 File "/usr/lib/python2.7/platform.py", line 1035, in _syscmd_uname#012 rc = f.close()#012IOError: [Errno 10] No child processes Case - II : Forking in kamailio.cfg fork=yes children=32 With forking Kamailio service fails with the following error: - Jun 20 15:19:07 sbc99-kam-dev kamailio: INFO: <core> [core/tcp_main.c:4665]: init_tcp(): using epoll_lt as the io watch method (auto detected) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: jsonrpcs [jsonrpcs_sock.c:197]: jsonrpc_dgram_mod_init(): the socket /var/run/kamailio/kamailio_rpc.sock already exists, trying to delete it... Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: rr [rr_mod.c:175]: mod_init(): outbound module not available Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: pike [pike.c:99]: pike_init(): PIKE - initializing Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: pike [ip_tree.c:81]: init_lock_set(): probing 256 set size Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== from Python mod init Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.__init__ Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [core/udp_server.c:203]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(-127) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19708]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(1) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19709]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(2) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19710]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(3) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19711]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(4) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19712]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(5) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19713]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(6) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19714]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(7) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19715]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(8) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19716]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(9) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19717]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(10) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19718]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(-1) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19719]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(-1) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19720]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(-1) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19722]: INFO: jsonrpcs [jsonrpcs_sock.c:429]: jsonrpc_dgram_process(): a new child 0/19722 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(0) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19723]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(-2) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19723]: INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [main.c:759]: handle_sigs(): terminating due to SIGCHLD Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19709]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19722]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19708]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19723]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19716]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19717]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19715]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19719]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19714]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19720]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19713]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19721]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(-4) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19718]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 8 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 9 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 13 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 14 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 16 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 17 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 18 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 20 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 21 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 22 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19710]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19711]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19712]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 25 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 23 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 19 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 10 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 11 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 12 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Is there any pointers of what am I missing or is it kamailio bug? Many Thanks Regards Muhammad Zaka

2 5

SQL replication stops
by Brian Jenkins 05 Jul '17

05 Jul '17

Hello, When we reload Kamailio Kam stops impacting our sql replication. We are running 3.3.0. Has anyone seen this issue before. -- Brian Jenkins Network Operation

2 1

Reload an individual entry into a hash table from database
by Jonathan Hunter 05 Jul '17

05 Jul '17

Hi Guys, We are currently building a wholesale platform to route numbers to particular carriers, and we are looking to do this with hash tables. We will potentially have 100s of thousands of numbers we will need to lookup and query as to where to route them, and one idea is to populate them in a database, we would then load these values into a hash table which will be defined in the kamailio configuration file for us to query in realtime when an Invite arrives. The backend database will be modified constantly, so we would have the need to reload the hash table on demand. I can see there is the ability to reload a whole hash table, sht_reload, but is there an option to reload for an individual entry which has been added to the database, and we therefore want it in the hash table? I dont see anything in documentation (forgive me if I have missed it), is there an option to reload just an individual key entry from the database into cache? Thanks Jon

2 1

Re: [SR-Users] host to get name of local server
by Daniel-Constantin Mierla 05 Jul '17

05 Jul '17

I haven't looked at its implementation, so be careful if it does DNS (or system call) query every time it is used, it may slow down the processing, in that case you can just store in another variable and use it instead. Cheers, Daniel On 05.07.17 17:01, Henry Fernandes wrote: > I ended up using $HN(). > > https://www.kamailio.org/wiki/cookbooks/4.2.x/pseudovariables#hn_key_-_host… > > > > > > > From: Daniel-Constantin Mierla <miconda(a)gmail.com > <mailto:miconda@gmail.com>> > Reply-To: "miconda(a)gmail.com <mailto:miconda@gmail.com>" > <miconda(a)gmail.com <mailto:miconda@gmail.com>> > Date: Monday, July 3, 2017 at 1:03 AM > To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org > <mailto:sr-users@lists.kamailio.org>>, Henry Fernandes > <henry(a)usinternet.com <mailto:henry@usinternet.com>> > Subject: Re: [SR-Users] host to get name of local server > > Hello, > > > On 29.06.17 18:11, Henry Fernandes wrote: >> We have multiple Kamailio 4.4.x servers and I am setting up stats >> tracking. I would like to track the stats for each individual >> Kamailio server separately like so: >> >> kamailio_1.sip.register.count >> kamailio_2.sip.register.count >> kamailio_3.sip.register.count >> >> The problem is that we use one common file (in version control) for >> our Kamailio configuration. Thus, I can’t just hardcode the hostname >> into the file because it will be the same for each server. >> >> Does anyone have a solution for me? Is there a variable that >> provides the hostname or is there something else I can do? >> >> Ideally, I’d love to be able to do something like this. >> >> statsd_incr($host_name + “.sip.register.count"); >> >> > > one option would be to define it via command line parameter with -A > option. Your start script can set it using the usual shell scripts. > > Cheers, > Daniel > -- > Daniel-Constantin Mierla > www.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio Advanced Training - www.asipto.com > Kamailio World Conference - www.kamailioworld.com -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com

1 0

host to get name of local server
by Henry Fernandes 05 Jul '17

05 Jul '17

We have multiple Kamailio 4.4.x servers and I am setting up stats tracking. I would like to track the stats for each individual Kamailio server separately like so: kamailio_1.sip.register.count kamailio_2.sip.register.count kamailio_3.sip.register.count The problem is that we use one common file (in version control) for our Kamailio configuration. Thus, I can’t just hardcode the hostname into the file because it will be the same for each server. Does anyone have a solution for me? Is there a variable that provides the hostname or is there something else I can do? Ideally, I’d love to be able to do something like this. statsd_incr($host_name + “.sip.register.count");

2 2

kamcmd dialogs count
by Arek Łazarczyk 05 Jul '17

05 Jul '17

Hi, I have a problem with kamcmd, for now i use kamctl fifo profile_get_size to get dialogs count to pass to nrpe and futher to nagios. Since fifo is deprecated, and i want to migrate to kamailio v5.0, i must change my method of counting dialogs to kamcmd dlg.profile_get_size. Problem is that i have dialog profiles values starting with 0, so kamctl fifo profile_get_size caller 004 returns correct vaule, but kamcmd dlg.profile_get_size caller 004 returns 0, i think that kamcmd converts 004 to just 4 on fly. Is there any way to prevent such behavior ? Thx4help in advance. Best regards, AŁ.

2 3

Kamailio Crashing inconsistently
by hemanth＠advaitamtech.com 05 Jul '17

05 Jul '17

Hello, I am using Kamailio 4.4, Kamailio is crashing inconsistently, I am not able find the root cause of the issue, Error which i get for the process which crashed at multiple occations kamailio[9137]: : <core> [mem/q_malloc.c:145]: qm_debug_frag(): BUG: qm_*: prev. fragm. tail overwritten(6363e160b12, abcdefed)[0x7f205db59070:0x7f205db590a8]! Memory allocator was called from tm: h_table.c:152. Fragment marked by tm: t_reply.c:1903. kamailio[21724]: : <core> [mem/q_malloc.c:134]: qm_debug_frag(): BUG: qm_*: fragm. 0x7f1fe804a1e8 (address 0x7f1fe804a220) end overwritten (4ae8cfaec87c0a27, 192f1270797ac90b)! Memory allocator was called from tm: h_table.c:179. Fragment marked by core: msg_translator.c:2153. kamailio[21950]: : <core> [mem/q_malloc.c:134]: qm_debug_frag(): BUG: qm_*: fragm. 0x7fe541a2cd68 (address 0x7fe541a2cda0) end overwritten (c0082c06, abcdefed)! Memory allocator was called from tm: h_table.c:179. Fragment marked by core: msg_translator.c:2153. kamailio[23200]: : <core> [mem/q_malloc.c:134]: qm_debug_frag(): BUG: qm_*: fragm. 0x7f1fae7fa260 (address 0x7f1fae7fa298) end overwritten (3a46e86e1b362938, 7260f1875617e)! Memory allocator was called from tm: h_table.c:179. Fragment marked by core: msg_translator.c:2153. There are 2 cores generated whenever it crashes, I have given the backtrace of the core generated, (gdb) bt #0 0x00007fe16aca4c37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007fe16aca8028 in __GI_abort () at abort.c:89 #2 0x000000000066b4ac in qm_debug_frag (qm=0x7fe160bc2000, f=0x7fe160ec9108, file=0x7fe1684dc84e "tm: h_table.c", line=179) at mem/q_malloc.c:147 #3 0x000000000066e255 in qm_free (qmp=0x7fe160bc2000, p=0x7fe160ec9140, file=0x7fe1684dc84e "tm: h_table.c", func=0x7fe1684dcb00 <__FUNCTION__.10973> "free_cell_helper", line=179, mname=0x7fe1684dc250 "tm") at mem/q_malloc.c:480 #4 0x00007fe16840cab9 in free_cell_helper (dead_cell=0x7fe160f09e50, silent=0, fname=0x7fe1684eeb8c "timer.c", fline=648) at h_table.c:179 #5 0x00007fe1684584a7 in wait_handler (ti=1156027084, wait_tl=0x7fe160f09ed0, data=0x7fe160f09e50) at timer.c:648 #6 0x000000000063a329 in timer_list_expire (t=1156027084, h=0x7fe160c3faf0, slow_l=0x7fe160c42da8, slow_mark=776) at timer.c:874 #7 0x000000000063a79d in timer_handler () at timer.c:939 #8 0x000000000063ac3d in timer_main () at timer.c:978 #9 0x00000000004c2550 in main_loop () at main.c:1683 #10 0x00000000004c9211 in main (argc=13, argv=0x7ffe6bf7da98) at main.c:2627 (gdb) bt #0 0x00007fe16aca4c37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007fe16aca8028 in __GI_abort () at abort.c:89 #2 0x000000000066b02c in qm_debug_frag (qm=0x7fe160bc2000, f=0x7fe160ec8de0, file=0x7fe1684dc84e "tm: h_table.c", line=179) at mem/q_malloc.c:136 #3 0x000000000066e255 in qm_free (qmp=0x7fe160bc2000, p=0x7fe160ec8e18, file=0x7fe1684dc84e "tm: h_table.c", func=0x7fe1684dcb00 <__FUNCTION__.10973> "free_cell_helper", line=179, mname=0x7fe1684dc250 "tm") at mem/q_malloc.c:480 #4 0x00007fe16840cab9 in free_cell_helper (dead_cell=0x7fe160ed6a28, silent=1, fname=0x7fe1684dc9c1 "h_table.c", fline=449) at h_table.c:179 #5 0x00007fe16840e491 in free_hash_table () at h_table.c:449 #6 0x00007fe168436141 in tm_shutdown () at t_funcs.c:90 #7 0x00000000005c0a50 in destroy_modules () at sr_module.c:811 #8 0x00000000004b6449 in cleanup (show_status=1) at main.c:525 #9 0x00000000004b7ad6 in shutdown_children (sig=15, show_status=1) at main.c:667 #10 0x00000000004ba428 in handle_sigs () at main.c:759 #11 0x00000000004c343e in main_loop () at main.c:1744 #12 0x00000000004c9211 in main (argc=13, argv=0x7ffe6bf7da98) at main.c:2627 Thanks & Regards Hemanth

2 3

kamailio LTE HSS
by Ibrahim Almahi 04 Jul '17

04 Jul '17

Dear Expert Fellows,Good Day, I'm wonder whether kamailio developed an open source based LTE HSS handles both IMS and LTE procedures "LTE Attach, Location Update, Authentication, ....". If it's not yet developed, is there any plan for it in the near future. Thanks and have a nice day. Ibrahim Almahi966594996362

3 3

Kazoo module json library kamailio 4.4.1
by Grant Bagdasarian 04 Jul '17

04 Jul '17

Hi, Could someone please tell me which json library I have to install in order for the kazoo module to compile? I've tried many different json library, none of them work. It keeps complaining: make all CC (gcc) [M kazoo.so] kz_trans.o In file included from kz_trans.c:53:0: kz_json.h:12:18: fatal error: json.h: No such file or directory #include <json.h> ^ compilation terminated. ../../Makefile.rules:97: recipe for target 'kz_trans.o' failed make[1]: *** [kz_trans.o] Error 1 Makefile:511: recipe for target 'modules' failed make: *** [modules] Error 1 There is another thread regarding this same issue, but no solution was provided by the creator of the thread. Any ideas? Regards, Grant

3 5

Re: [SR-Users] sr-users Digest, Vol 146, Issue 2
by Narayan P 04 Jul '17

04 Jul '17

Hi Sebastian, Thanks for your reply. Today I am trying to install rtpengine as suggested by you.Could you please tell me from which part of the script I need to add rtpengine functions as my client is getting 183 from kamailio as of now. My architecture is like this, external ipv4 network(port 5060)----------rtpproxy(ipv4)--kamailio(ipv6)(port 5070)----------client(ipv4)(port 5077) Please look at the attached wireshark capture. Highly appreciate any suggestion as always. Thanks, Narayan ________________________________ From: sr-users <sr-users-bounces(a)lists.kamailio.org> on behalf of sr-users-request(a)lists.kamailio.org <sr-users-request(a)lists.kamailio.org> Sent: Monday, July 3, 2017 10:00:02 AM To: sr-users(a)lists.kamailio.org Subject: sr-users Digest, Vol 146, Issue 2 Send sr-users mailing list submissions to sr-users(a)lists.kamailio.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users or, via email, send a message with subject or body 'help' to sr-users-request(a)lists.kamailio.org You can reach the person managing the list at sr-users-owner(a)lists.kamailio.org When replying, please edit your Subject line so it is more specific than "Re: Contents of sr-users digest..." Today's Topics: 1. Re: host to get name of local server (Daniel-Constantin Mierla) 2. Re: remote ip address of sender and receiver (Daniel-Constantin Mierla) 3. Re: remote ip address of sender and receiver (Daniel-Constantin Mierla) 4. Re: Question regarding calling a shell script from kamailio (Daniel-Constantin Mierla) 5. Re: Compiling errors (Daniel-Constantin Mierla) 6. Re: evapi module and async_relay (Daniel-Constantin Mierla) 7. Re: Using lock() correctly (Sebastian Damm) 8. Re: call forward on no answer (Daniel-Constantin Mierla) 9. Re: How to convert ipv6 to ipv4 address inside message body (Sebastian Damm) 10. Re: UAC auth for incoming call (Daniel-Constantin Mierla) 11. Re: drouting / do_routing / prefix unknown (Daniel-Constantin Mierla) 12. Re: Using lock() correctly (Daniel-Constantin Mierla) 13. Re: Using lock() correctly (Sebastian Damm) 14. Re: Using lock() correctly (Daniel-Constantin Mierla) ---------------------------------------------------------------------- Message: 1 Date: Mon, 3 Jul 2017 09:03:16 +0200 From: Daniel-Constantin Mierla <miconda(a)gmail.com> To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org>, Henry Fernandes <henry(a)usinternet.com> Subject: Re: [SR-Users] host to get name of local server Message-ID: <9c3f6b62-d79f-1376-b0f5-1ccbb69e37c1(a)gmail.com> Content-Type: text/plain; charset="windows-1252" Hello, On 29.06.17 18:11, Henry Fernandes wrote: > We have multiple Kamailio 4.4.x servers and I am setting up stats > tracking. I would like to track the stats for each individual > Kamailio server separately like so: > > kamailio_1.sip.register.count > kamailio_2.sip.register.count > kamailio_3.sip.register.count > > The problem is that we use one common file (in version control) for > our Kamailio configuration. Thus, I can’t just hardcode the hostname > into the file because it will be the same for each server. > > Does anyone have a solution for me? Is there a variable that provides > the hostname or is there something else I can do? > > Ideally, I’d love to be able to do something like this. > > statsd_incr($host_name + “.sip.register.count"); > > one option would be to define it via command line parameter with -A option. Your start script can set it using the usual shell scripts. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda<http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda> Kamailio Advanced Training - www.asipto.com<http://www.asipto.com> Kamailio World Conference - www.kamailioworld.com<http://www.kamailioworld.com>

2 2

missing request username on register
by 赵国杰 04 Jul '17

04 Jul '17

Hello all, I have two kamailio servers(A and B) with exact same config using the same mysql db. I can register to A but not B. Server B complained: ERROR: <script>: fu is sip:851968556538527744@104.198.52.31, ru is sip:104.198.52.31, rU is <null> After capture the udp packet on both server using ngrep, the REGISTER they received are both good except A returns 200 OK and B returns 403 Not relaying. I don't have a clue what went wrong. How come the $rU is null when all the headers in REGISTER are valid? Can someone please point me the direction? Thanks Jesse

2 4

contact issue on kamailio with sipml/jssip over wss
by David Villasmil 04 Jul '17

04 Jul '17

Hello guys, So i've setup kamailio 5 with wss. Registration goes ok, but when trying to call, SIPML as well as jsSIP send garbage as Contact header, something like: Contact: <sip:0ku6du26@7j65fcf53i2k.invalid ;transport=ws>;reg-id=1;+sip.instance="<urn:uuid:8b49ac42-2039-4122-9f5b-6f4e9f471f52>";expires=600 so when it passes through: if (is_method("REGISTER")) { fix_nated_register(); } else { if (!add_contact_alias()) { xlog("L_ERR", "Error aliasing contact <$ct>\n"); sl_send_reply("400", "Bad Request"); exit; } } (taken from several examples i've found around) add_contact_alias() fails because it tries to find whether the ip address in the contact header is different from the received ip, and if not, it adds the received ip as a parameter... so the call doesn't work... I assume there's a way around this, can anyone help? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 ᐧ

2 2

Using lock() correctly
by Sebastian Damm 03 Jul '17

03 Jul '17

Hi, for a project I need to make sure, I have a setup where I get mirror-traffic into Kamailio which has to do something with it. To work correctly, I need to make sure, the initial INVITE is processed correctly before any reply to the same call. So I thought I use lock() and unlock() for it. This is what the relevant kamailio.cfg part looks like: request_route { xlog("L_INFO", "Got new packet $rm: $si => $Ri\n"); route(li); } onreply_route { xlog("L_INFO", "Got new packet $rm: $si => $Ri - Reply Code $rs\n"); route(li); } route[magic] { lock("$ci"); xlog("L_INFO", "Obtained lock, calling lua...\n"); if(!lua_run("handle_packet")) { xlog("L_ERR", "SCRIPT: failed to execute lua function!\n"); } unlock("$ci"); xlog("L_INFO", "Lua finished, released lock...\n"); drop; exit; } And this is what the log says: Jun 28 13:27:04 busch /usr/sbin/kamailio[18836]: INFO: <script>: Got new packet INVITE: 172.20.21.247 => 172.20.21.4 Jun 28 13:27:04 busch /usr/sbin/kamailio[18836]: INFO: <script>: Obtained lock, calling lua... Jun 28 13:27:04 busch /usr/sbin/kamailio[18836]: INFO: app_lua [app_lua_sr.c:98]: lua_sr_log(): some logging Jun 28 13:27:04 busch /usr/sbin/kamailio[18837]: INFO: <script>: Got new packet INVITE: 172.20.21.4 => 172.20.21.247 - Reply Code 407 Jun 28 13:27:04 busch /usr/sbin/kamailio[18837]: INFO: <script>: Obtained lock, calling lua... Jun 28 13:27:04 busch /usr/sbin/kamailio[18837]: INFO: <script>: Lua finished, released lock... Jun 28 13:27:04 busch /usr/sbin/kamailio[18836]: INFO: app_lua [app_lua_sr.c:98]: lua_sr_log(): some more logging As far as I understand the documentation, the second packet should wait for the lock on the Call-ID before executing the lua function. So process 18836 should finish its lua execution before 18837 can do anything further. Did I completely misunderstand the lock() function? I'm using Kamailio 5.0.2. Thanks for helping me understand what Kamailio is doing here. Best Regards, Sebastian

2 14

drouting / do_routing / prefix unknown
by Jean Cérien 03 Jul '17

03 Jul '17

Hello I am using Kamailio 5.0.2, with module drouting to do prefix based routing. 1. When I call do_routing and the prefix is not known, the r-uri remains unchanged. Is there a way to detect that the prefix is unknown, other than r-uri remains unchanged ? 2. I have the following parameters modparam("drouting", "db_url",DBURL) modparam("drouting", "sort_order", 0) modparam("drouting", "use_domain", 0) modparam("drouting", "force_dns", 1) # modparam("drouting", "enable_keepalive", 1) If I enable keep alive, I get the following error: Jun 20 22:37:17 kamailio1 kamailio: ERROR: <core> [core/modparam.c:141]: set_mod_param_regex(): parameter <enable_keepalive> of type <2> not found in module <drouting> yet, the documentation leads me to think that it should work: *NOTE: this option is only compatible with <em>sort_order</em> 0 currently. With sort_order value of 1 or 2, destinations status will simply be ignored.* Thanks for your help J.

2 1

UAC auth for incoming call
by Юрий Гончаров 03 Jul '17

03 Jul '17

Hello kamailio users, I use uac module. Registration and outbound calls from Kamailio are fine. How can I check if INVITE sent from remote part not spoofed.

2 1

call forward on no answer
by frédéric Gaisnon 03 Jul '17

03 Jul '17

Hello, In my Platform i have a kamailio used as pseudo SBC and a kamailio used as Proxy (AS trigger) (cpl are applied on this instance). When I make a call and callee doesn't answer that call my SBC detects the timeout and generates a 408 to Proxy (according to fr_inv_timer) , but it generates CANCEL too. Is it possible to deactivate these CANCEL? if not what is the configuration in order to be able to trigger CFNA? Regards, Frédéric

2 1

evapi module and async_relay
by Diego Nadares 03 Jul '17

03 Jul '17

Hi guys, Anybody knows if evapi sends messages to the clients immediately when async_relay is called? The normal behavior is 1 or 2 netstrings per message but I see that sometimes it starts to enqueue and starts sending for example 4, 5, 15, 30, 52.....327, 645 per message. Cheers, Diego

3 5

Compiling errors
by Yasin CANER 03 Jul '17

03 Jul '17

2 3

Question regarding calling a shell script from kamailio
by Anuradha Selvarajan 03 Jul '17

03 Jul '17

Hello, I am using fork.cfg file and I want to call a shell script (which has curl commands extracting value from database and returns the value) and use the value in the fork.cfg. How can I do it? Appreciate your help! Thanksm Anu

3 3

remote ip address of sender and receiver
by vuleetu 03 Jul '17

03 Jul '17

Hi, all Is there any way to get remote ip address of both sender($si) and receiver(?)? I am configuring kamailio with multiple rtpproxy sets. Basically, rtpproxy set will be choosed based on the country those ip addresses of caller and callee belong to. Lets say if caller and callee are both in US, set 1 will selected. If they are not in the same country, set 2 will be selected. I dont know if there is any way to do that. Best regards Fisher

2 1

IOS 10 and SIP
by Kjeld Flarup 01 Jul '17

01 Jul '17

Rumours is that Apple no longer accepts apps which can do persistent connections in the background. To my best knowledge that means that IOS no longer supports SIP incoming calls. The app should now use Push Notifications, but SIP does not support this. Anybody faced this problem? Is the solution to call an external program when processing an Invite? This leaves some issues. 1. Should we wait some seconds before proceeding or wait until the Push notification has been processed, to give the app time to register. We cannot start to send invites, before we have a correct registration. An old registration may change ports when the app wakes up and makes a new register via NAT. 2. How do we know, if a given user should have a push notification? 3. Which information do we need to be able to send the push notification? 4. Does this give a penalty to Android users, because we have to wait for IOS? -- Med venlig hilsen / Best regards Kjeld Flarup (Christensen) M.Sc E.E, Teknisk chef Viptel ApS, Hammershusvej 16C, DK-7400 Herning Telefon: +45 46949949, Telefax: +45 46949950, http://viptel.dk

5 7

[mohqueue] MOH service / A case with MOH queue
by Issam Hambouz 30 Jun '17

30 Jun '17

Hello! I am exploring mohqueue module and have few questions: - Could it be used to provide MOH service for SIP endpoints? I am aware that its main functionality is to queue calls (along playing a MOH for queued calls) and provides a mechanism to retrieve calls (FIFO), but I had the impression, reading several emails in this group, that it can be used in a way to provide MOH whenever a call is put on-hold -- I tried to use it with the re-INVITE received when a call is put on-hold, but got a log message stating that it works with initial INVITEs only (something like that) - On a test setup (Kamailio 4.2.3 / 2.0.0), I was able to reach the queue / listen to the MOH but encountered a strange case where the call gets automatically removed from the queue after 4-5 seconds (can be seen removed from kamailio.mohqcalls as well) Jun 12 22:58:30 - DEBUG: mohqueue [mohq_funcs.c:2369]: mohq_debug(): mohq_process: Processing INVITE, queue (demo) Jun 12 22:58:30 - DEBUG: mohqueue [mohq_funcs.c:2369]: mohq_debug(): create_call: Added call (<sip:6010@10.110.3.57>;tag=c97a6b26-2bfe-4271-9db1-cee38ea96c47) to queue (demo) Jun 12 22:58:30 - DEBUG: mohqueue [mohq_funcs.c:2369]: mohq_debug(): first_invite_msg: Making offer for RTP link for call (<sip:6010@10.110.3.57 >;tag=c97a6b26-2bfe-4271-9db1-cee38ea96c47) Jun 12 22:58:30 - DEBUG: mohqueue [mohq_funcs.c:2369]: mohq_debug(): first_invite_msg: Sent RINGING for call (<sip:6010@10.110.3.57 >;tag=c97a6b26-2bfe-4271-9db1-cee38ea96c47) Jun 12 22:58:30 - DEBUG: mohqueue [mohq_funcs.c:2369]: mohq_debug(): send_rtp_answer: Answering RTP link for call (<sip:6010@10.110.3.57 >;tag=c97a6b26-2bfe-4271-9db1-cee38ea96c47) Jun 12 22:58:30 - DEBUG: mohqueue [mohq_funcs.c:2369]: mohq_debug(): start_stream: Starting RTP link for call (<sip:6010@10.110.3.57 >;tag=c97a6b26-2bfe-4271-9db1-cee38ea96c47) Jun 12 22:58:30 - DEBUG: mohqueue [mohq_funcs.c:2369]: mohq_debug(): send_rtp_answer: Responded to INVITE with RTP for call (< sip:6010@10.110.3.57>;tag=c97a6b26-2bfe-4271-9db1-cee38ea96c47) Jun 12 22:58:35 ERROR: mohqueue [mohq_funcs.c:1243]: invite_cb(): invite_cb: INVITE failed for call (<sip:6010@10.110.3.57 >;tag=c97a6b26-2bfe-4271-9db1-cee38ea96c47)! Jun 12 22:58:35 DEBUG: mohqueue [mohq_funcs.c:2369]: mohq_debug(): delete_call: Deleting call (<sip:6010@10.110.3.57>;tag=c97a6b26-2bfe-4271-9db1-cee38ea96c47) from queue (demo) -- route[MOH] is called first at the beginning of request_route() route[MOH] { if (has_totag()) return; if (mohq_process ()) { xlog ("mohqueue: mohq_process"); exit; } } -- Looking at the SIP trace, all seems ok, except receiving a 404 response after BYE (that's me hanging up after few seconds from getting the above error message) Your comments and hints are appreciated! Thank you Issam

3 3

Add extra headers on HTTP requests in Kamailio v5
by Joel Serrano 30 Jun '17

30 Jun '17

Hi all, Is there a way to add extra headers with http_client_query() from http_client module? In current http_query() from utils module, according to the doc, you can add a custom header: *4. Functions* *4.1. http_query(url, [post-data], [header-data], result)* *...* *If you want to add additional headers to the request, you have to define the “header”-data, that should be submitted in that request as the third parameter. If this parameter is empty, it is not set.* *...* and I have that working with the following: http_query("https://example.com/api", "param1=value1&param2=value2", "Cookie: apikey=super_secret_api_key", "$var(call_info)"); The problem is that http_query() is removed in Kamailio v5, and the http_client_query() only has the ability to add specifically the content-type header: *4. Functions* *4.1. http_connect(connection, url, [content_type, data,] result)* *...* *content_type - Used only when posting data with HTTP POST. An Internet Media type, like "application/json" or "text/plain". Will be added to the HTTP request as a header.* *...* Is there another way to add a custom header to a http request with the http_client module? Any workarounds for this? Thanks, Joel.

2 1

remote ip address of sender and receiver
by vuleetu 30 Jun '17

30 Jun '17

Hi, all Is there any way to get remote ip address of both sender($si) and receiver(?)? I am configuring kamailio with multiple rtpproxy sets. Basically, rtpproxy set will be choosed based on the country those ip addresses of caller and callee belong to. Lets say if caller and callee are both in US, set 1 will selected. If they are not in the same country, set 2 will be selected. I dont know if there is any way to do that. Best regards Fisher

3 5

Segfault on kamailio 5.0.2. Suddenly stops processing traffic, then generates a core when restarting
by Joel Serrano 29 Jun '17

29 Jun '17

Hi all, I'm running into a weird situation with our newly deployed Kamailio servers. These servers are only doing SSL offloading and load balancing between another set of servers. Debian v9.0 + Kamailio v5.0.2 (from kamailio50 repository). After some time of running, kamailio suddenly stops responding to any request but the proccess is still alive. When we restart the service, a core is generated. I have opened an issue in GitHub: https://github.com/kamailio/kamailio/issues/1172 I'm attaching the backtrace here too in case anyone can take a look at it, unfortunately I'm lost right now. In dmesg I saw: [138953.744199] kamailio[12052]: segfault at 7efaf32f51b8 ip 00007efcf3b5df69 sp 00007ffe325dc0c0 error 4 in libcrypto.so.1.1[7efcf39f6000+265000] Thanks, Joel.

2 2

get online user from api
by 赵国杰 28 Jun '17

28 Jun '17

Hello all, I want to know how many users are currently registered to my kamailio server. I understand can be used to achieve this. I'm wondering if there's RESTful or RPC interface that can be requested by external service. Thanks, Jesse

4 4

Kamailio 4.3 to 4.4
by Laura 27 Jun '17

27 Jun '17

Dear List, I'm planning to upgrade from kamailio 4.3.7 to 4.4.x I am looking on www to see if there are any upgrade or modification to the kamailio db schema but i havenpt found any good details. Anyone here that must did the upgrade and can give me some information or url to check about it ? Thanks for any reply. Laura

2 1

Detect network range in UDP traffic
by Emanuele Gambaro 27 Jun '17

27 Jun '17

Hi to all I have the following scenario (Kamailio 5 and rtpproxy) *) Bob on a wifi network calls Alice *) During the call, Bob losts his wifi network (and so also changes his IP address) *) The RTP flow is interrupted With asterisk, disabling “Strict RTP” option, the flow does not interrupts: Asterisk detect the new IP address and sends the audio packets to the new IP address. It is possible to setup this behavior also with Kamailio? -- Emanuele Gambaro --- email: emanuele.gambaro(a)pynlab.com skype: sarbyn_work OpenPGP Key: https://goo.gl/fdeVnI

2 2

Question about sip call setup : three-way handshake
by Abdoul Osséni 27 Jun '17

27 Jun '17

Hello, During three-way handshake (SIP call setup - INVITE-200 OK - ACK) and before generating or sending the final 200 OK call, is there a way to confirm the caller is still available (no network issue)? I want to detect broken connections (ex. the uac uses 3G network) before generating/sending/forwarding the final 200 OK. Thanks. Regards Abdoul

4 8

How to forward DTMF (in RTP package) to conference within SEMS
by Nguyen Tran Nhan 27 Jun '17

27 Jun '17

I am using Kamailio + Sems + Rtpproxy for conference call. Once user join to conference, if user send dtmf, sems is detected but it does not forward DTMF (in RTP) to all user in conference. I think rtprelay_dtmf_detection should be configured? Do you have any idea to help? Thanks, Nhan

2 1

Print current route
by David Villasmil 26 Jun '17

26 Jun '17

Hello guys, Is is possible to log the current (function) route? Something like route[WHATEVER]{ xlog("$curroute: Hello World\n"); } and it would print: WHATEVER: Hello World Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 ᐧ

2 3

auth users using inmemory lookups
by Grant Bagdasarian 26 Jun '17

26 Jun '17

Hello, We're currently using the auth_db module and calling the function auth_check to check the Authorization header and authenticate the request. We moved most of our code to in-memory lookups (using htable), since we do not want our Kamailio servers to be DB dependent. Just to be sure, if we move the authentication to in-memory lookups we should use the auth module and call the pv_auth_check function instead right? The passwords in our users table are all stored in MD5, so we basically just have to put this table in a htable, and call the pv_auth_check and pass it the hashed password and the flag 1? Regards, Grant

2 1

Problem with t_relay() and VPN tunnel
by Carlos Ruiz Diaz 24 Jun '17

24 Jun '17

Hi, I have two SIP servers, *A* and *B*, connected each other though a OPENVPN tunnel. The server *B* needs to t_relay() every SIP message containing the method MESSAGE to the server *A* but these messages never reach destination. I have tested the tunnel connectivity and works fine. I wrote a Perl script (located in *B*) that sends SIP MESSAGES to Kamailio (located in *A*) trying to figure out what is happening but these messages are received by *A* and processed correctly but when *B* does the same from Kamailio, it is never received. Here is the route part of kamailio.cfg in *B*: Observation: ($rU == "1004") result is *true* * if(is_method("MESSAGE")) { if($rU == "1004") { xlog("L_INFO","En 1004"); rewritehost("10.8.0.1"); if (!t_relay()) xlog("L_INFO","MIO Error en t_relay"); t_reply("200", "Ok"); xlog("L_INFO","MIO despues rewrite"); exit; } .....* The perl script that WORKS: *$msg = 'MESSAGE sip:1004@192.168.1.2:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.2 From: "2002" <sip:2002@192.168.1.2 <sip%3A2002(a)192.168.1.2>>;tag=1837944796 To: <sip:1004@192.168.1.2 <sip%3A1004(a)192.168.1.2>> Call-ID: 19722852989(a)192.168.1.2 CSeq: 15773 MESSAGE Contact: <sip:2002@**PublicIP-protected**:5060> Max-Forwards: 29 User-Agent: DBL Content-Type: text/plain Content-Length: 34 +595981[protected] hello from kamailio '; use IO::Socket; my $sock = IO::Socket::INET->new( Proto=>'udp', PeerHost=>'192.168.2.102', PeerPort=>'5060'); print "Sending msg $msg\n"; $sock->send($msg) or die "error sending $!\n"; *Please help! Thanks in advance. Carlos.

3 3

How to get the count of active calls handled in kamailio.
by vivek＠advaitamtech.com 23 Jun '17

23 Jun '17

Hi, I would like to know how many active calls are handled in kamailio server at a given point of time(concurrent calls). In the few older post it was mentioned to use "dialog" module for these statistics. In dialog module , there is a function called "active_dialogs" , which solves my requirement. But it is not clear how to use it. Can anybody help me out in this? Thanks, Vivek.

3 2

Kamailio v4.3.7 Released
by Daniel-Constantin Mierla 23 Jun '17

23 Jun '17

Hello, Kamailio SIP Server v4.3.7 stable release is out. This is a maintenance release of an old stable branch, 4.3, that includes fixes since release of v4.3.6. There is no change to database schema or configuration language structure that you have to do on installations of v4.3.x. Important note: unless some major regression is discovered in the near future, this is the latest release to be done from branch 4.3, which is no longer to be officially maintained. Therefore it is strongly advised to consider upgrading to 4.4.x or 5.0.x series. For more details about version 4.3.7 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2017/06/kamailio-v4-3-7-released/ RPM, Debian/Ubuntu packages will be available soon as well. Note: the latest stable branch is 5.0, at this moment with its latest release v5.0.2. See more details about it at: * https://www.kamailio.org/w/kamailio-v5-0-0-release-notes/ Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/miconda - http://www.linkedin.com/in/miconda

1 0

Re: [SR-Users] How to get the count of active calls handled in kamailio.
by Angel Elena 23 Jun '17

23 Jun '17

You can view active dialogs with: kamctl mi dlg_list for less info kamctl mi dlg_list | grep from-uri or another header.. -------------------------------- Ángel Elena Medina _o) craem(a)craem.net / \\ http://blog.craem.net _(___V @craem_ -------------------------------- -----Mensaje original----- De: vivek(a)advaitamtech.com Enviado: Vie 23-06-2017 12:27 Asunto: [SR-Users] How to get the count of active calls handled in kamailio. Para: sr-users(a)lists.sip-router.org; > Hi, > > > I would like to know how many active calls are handled in kamailio server at a > given point of time(concurrent calls). > > > In the few older post it was mentioned to use "dialog" module for these > statistics. > > > In dialog module , there is a function called "active_dialogs" , which solves > my requirement. But it is not clear how to use it. Can anybody help me out in > this? > > > Thanks, > > Vivek. > > > _______________________________________________ > > Kamailio (SER) - Users Mailing List > > sr-users(a)lists.kamailio.org > > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > > >

1 0

Releasing Kamailio v4.3.7
by Daniel-Constantin Mierla 23 Jun '17

23 Jun '17

Hello, I am planning to release Kamailio v4.3.7 very soon, likely tomorrow, based on the last version of branch 4.3. This should mark the end of official maintenance for branch 4.3, so if no major regression discovered in following few weeks, it will be the last release in 4.3 series. If there is something you know it needs to be pushed in branch 4.3, write back to mailing list. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com

1 1

Better place to change the FROM header for every INVITE
by Emanuele Gambaro 22 Jun '17

22 Jun '17

Hi I need to change the FROM header for every invite and replace the caller username with another data taken from mysql database. Which is the best place in kamailio routes to do a uac_replace_from ? It is correct to change the FROM header before the dialog creation, in “RELAY” route, just before the t_relay()? Thank you -- Emanuele Gambaro --- email: emanuele.gambaro(a)pynlab.com skype: sarbyn_work OpenPGP Key: https://goo.gl/fdeVnI

2 1

Help detecting t.38 and routing accordingly
by Tim Bowyer 22 Jun '17

22 Jun '17

Hi All, Trying to work out a way to detect and re-route inbound calls which negotiate or contain t.38 SDP to answer/process faxes efficiently. Plan is to put Kamailio in front of a quantity of FreeSwitch servers - most virtual, others physical. Virtual servers will handle inbound faxes which negotiate t.38, and physical servers will answer ulaw/alaw faxes with mod_spandsp. The bulk of inbound faxes negotiate t.38, but in order to scale our inbound system we need some way to work out which way to send the calls prior to the dispatcher. Many thanks for your help in advance, Tim

3 4

Kamailio IMS NAT issue: PRACK/ACK RURI changing in P-CSCF
by Mojtaba 22 Jun '17

22 Jun '17

Is it not better to use SEMS as SBC in the front of your network? And all P/S/I/CSCF have the private IP address. Thanks --Mojtaba Esfandiari.S

2 4

cpl.load
by frédéric Gaisnon 21 Jun '17

21 Jun '17

Hi, In latest kamailio version "cpl.load" command is obsolete. What is the procedure to import CPL into mysql database? Regards, Frédéric Gaisnon

2 1

maybe found a bug in TM module - how to proceed?
by Valentin Christoph 21 Jun '17

21 Jun '17

Hi all, I am using kamailio 4.4.5 in an IMS setup as S-CSCF. I have got problems when trying to deliver an INVITE request to a distinct PSI at an AS. I receive the SIP response "555 AS Contacting Failed - iFC terminated dialog". I collected tshark traces and synchronously WITH_DEBUG kamailio logs. I think, I have found the root cause in the source code of the TM module and would like to issue an official bug report. How to proceed? All the Best 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.

2 2

SIP-Trunk Kamailio and Asterisk
by Володимир Іванець 21 Jun '17

21 Jun '17

Hello everyone, I'm doing some custom Kamailio configuration to achieve few things but seem to be stuck with SIP trunks. I'm currently using Kamailio 4.4.5 and here is what I have at the moment: *1.* Asterisk 11.25.1 servers behing Kamailio using RealTime for SIP peers. *2.* Route that checks if packet was sent from one of configured SIP trunks. This part works correctly: *route[FROMPSTN] {* * xlog("== FROMPSTN ==\n");* * $var(socket) = $si + ":" + $sp;* * xlog("**** $var(socket)\n");* * xlog("**** $(sht(trunks_kamailio=>$var(socket)))\n");* * if ($(sht(trunks_kamailio=>$var(socket))) != $null) {* * xlog("**** From $(sht(trunks_kamailio=>$var(socket))) PSTN\n");* * return 1;* * }* * xlog("**** Not from PSTN\n");* * return -1;* *}* *3.* Here is a fragment that sends INVITE packet to *TOASTERISK* route if it was received from one of trunks. I have 4444444444(a)XXX.XXX.XXX.XXX hardcoded for now, and in my configuration 4444444444 and XXX.XXX.XXX.XXX represent my real caller id number and carrier's IP address: *if(route(FROMPSTN)) {* * uac_replace_from("sip:4444444444@XXX.XXX.XXX.XXX");* * route(TOASTERISK);* *}* *4.* TOASTERISK basically has folloving fragment that load balances traffic between Asterisk nodes: *if(!ds_select_dst("0", "4")) {* * xlog("**** Call was not sent to none of Asterisk hosts\n");* * if(!is_method("REGISTER")) {* * xlog("**** Method is not REGISTER\n");* * send_reply("404", "No destination");* * }* * xlog("**** Dispatcher fail\n");* * exit;* *}* So when I'm making a call to my test number, I can see following incomming packet in Asterisk from Kamailio. From header has correct caller id number and carrier's IP address (192.168.88.5 is Kamailio's internal IP address): [image: Вбудоване зображення 1] And when Asterisk tries to find a maching peer for this incoming call, it is using Kamailio's instead of Carrier's IP address. So it is actually finds one of peers (101-XXXXXXX) that is being authenticated on Kamailio as many others: [image: Вбудоване зображення 2] I'm not sure if Asterisk is just using packet's source IP to lookup for corresponding peer or something else from it's content. I will really appreciate any help on this. Thanks a lot!

1 1

Cannot login Siremis
by Trent 20 Jun '17

20 Jun '17

Hey. Just installed Kamailio onto CentOS 6 using the available YUM repos., and Siremis (v4.4). I seem to be having the same issue as this was reported https://github.com/asipto/siremis/issues/3 I have retried the Siremis install again as suggested, and I still cannot login with the same results that person has: click login and nothing is occurring, except for the text appearing which states "Processing Login." There is no error in the httpd error_log file. Anything else to look for? Thanks!

2 2

Kamilio doesn't start up with pymongo in the Kemi Python script..
by Muhammad Zaka 20 Jun '17

20 Jun '17

Hi all, In kamailio 5.0.1 with kemi interface for python I am trying to use pymongo to import Mongo Client interface for python but the kamailio service fails to start up properly. kamailio-kemi-python.py import sys import struct import Router.Logger as Logger import KSR as KSR from pymongo import MongoClient Case - I : No forking and no children in kamailio.cfg kamailio.cfg fork=no children=0 Kamailio service fails with the following error: - Jun 20 15:12:32 sbc99-kam-dev kamailio: ERROR: app_python [python_support.c:142]: python_handle_exception(): mod_init: Unhandled exception in the Python code:#012Traceback (most recent call last):#012 File "/etc/kamailio/kamailio-kemi-python.py", line 19, in <module>#012 from pymongo import MongoClient#012 File "/usr/local/lib/python2.7/dist-packages/pymongo/__init__.py", line 87, in <module>#012 from pymongo.mongo_client import MongoClient#012 File "/usr/local/lib/python2.7/dist-packages/pymongo/mongo_client.py", line 52, in <module>#012 from pymongo.client_options import ClientOptions#012 File "/usr/local/lib/python2.7/dist-packages/pymongo/client_options.py", line 23, in <module>#012 from pymongo.pool import PoolOptions#012 File "/usr/local/lib/python2.7/dist-packages/pymongo/pool.py", line 121, in <module>#012 ('type', platform.system()),#012 File "/usr/lib/python2.7/platform.py", line 1333, in system#012 return uname()[0]#012 File "/usr/lib/python2.7/platform.py", line 1300, in uname#012 processor = _syscmd_uname('-p','')#012 File "/usr/lib/python2.7/platform.py", line 1035, in _syscmd_uname#012 rc = f.close()#012IOError: [Errno 10] No child processes Case - II : Forking in kamailio.cfg fork=yes children=32 With forking Kamailio service fails with the following error: - Jun 20 15:19:07 sbc99-kam-dev kamailio: INFO: <core> [core/tcp_main.c:4665]: init_tcp(): using epoll_lt as the io watch method (auto detected) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: jsonrpcs [jsonrpcs_sock.c:197]: jsonrpc_dgram_mod_init(): the socket /var/run/kamailio/kamailio_rpc.sock already exists, trying to delete it... Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: rr [rr_mod.c:175]: mod_init(): outbound module not available Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: pike [pike.c:99]: pike_init(): PIKE - initializing Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: pike [ip_tree.c:81]: init_lock_set(): probing 256 set size Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== from Python mod init Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.__init__ Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [core/udp_server.c:203]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(-127) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19708]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(1) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19709]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(2) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19710]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(3) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19711]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(4) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19712]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(5) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19713]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(6) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19714]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(7) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19715]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(8) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19716]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(9) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19717]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(10) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19718]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(-1) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19719]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(-1) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19720]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(-1) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19722]: INFO: jsonrpcs [jsonrpcs_sock.c:429]: jsonrpc_dgram_process(): a new child 0/19722 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(0) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19723]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(-2) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19723]: INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19703]: INFO: <core> [main.c:759]: handle_sigs(): terminating due to SIGCHLD Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19709]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19722]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19708]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19723]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19716]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19717]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19715]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19719]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19714]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19720]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19713]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19721]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: INFO: <core> [core/kemi.c:86]: sr_kemi_core_info(): ===== kamailio.child_init(-4) Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19718]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 8 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 9 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 13 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 14 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 16 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 17 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 18 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 20 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 21 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 22 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19710]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19711]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19712]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 25 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 23 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 19 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 10 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 11 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 12 Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Jun 20 15:19:07 sbc99-kam-dev /usr/sbin/kamailio[19724]: ERROR: <core> [core/io_wait.h:1040]: io_wait_loop_epoll(): epoll_wait(5, 0x7efdd80797c0, 0, 5000): Invalid argument [22] Is there any pointers of what am I missing or is it kamailio bug? Many Thanks Regards Muhammad Zaka

1 0

app_lua and sqlops returns error
by Sebastian Damm 20 Jun '17

20 Jun '17

Hi, I'm developing some routing logic with Kamailio 5.0.1 and app_lua. I've integrated my lua script and now I'm trying to use sqlops within the script. I want to use the reconnect stuff of sqlops instead of implementing it by myself. This is what the Kamailio config looks like: [..] loadmodule "db_mysql.so" loadmodule "sqlops.so" loadmodule "app_lua.so" [..] modparam("sqlops", "sqlcon", "ca=>mysql://kamailio:foobar@127.0.0.1/kamailio") modparam("app_lua", "reload", 1) modparam("app_lua", "register", "sqlops") modparam("app_lua", "load", "/etc/kamailio/playground.lua") ####### Routing Logic ######## # Main SIP request routing logic request_route { route(everythinginlua); } onreply_route { route(everythinginlua); } route[everythinginlua] { if(!lua_run("handle_packet")) { xlog("L_ERR", "SCRIPT: failed to execute lua function!\n"); } drop; exit; } The lua script looks like this: -- Start of script function handle_packet() sr.log("L_INFO", "Got packet method "..sr.pv.get("$rm")) local status = sr.sqlops.sql_query("ca", "SELECT * FROM table", "fooresult") sr.err("sql query returned status "..status) end -- End of script Now when a packet comes in, I see the following in the log file: Jun 14 11:19:59 busch /usr/sbin/kamailio[13254]: ERROR: app_lua [app_lua_sr.c:104]: lua_sr_log(): Got packet method REGISTER Jun 14 11:19:59 busch /usr/sbin/kamailio[13254]: ERROR: app_lua [app_lua_api.c:713]: app_lua_run_ex(): error from Lua: /etc/kamailio/playground.lua:4: attempt to call field 'sql_query' (a nil value) Jun 14 11:19:59 busch /usr/sbin/kamailio[13254]: ERROR: app_lua [app_lua_api.c:726]: app_lua_run_ex(): error executing: handle_packet (err: 2) Jun 14 11:19:59 busch /usr/sbin/kamailio[13254]: ERROR: <script>: SCRIPT: failed to execute lua function! Looks to me as if the functions of sqlops don't get exported to my lua script. According to the documentation, after specifying the "register" modparam, I should be able to access those functions. What am I missing? Thanks in advance Sebastian

2 4

Re: [SR-Users] re.subst does not work with $var?
by Pranathi Venkatayogi 19 Jun '17

19 Jun '17

Any input please? How do I use these methods with $var... I get the same behavior when I use avp_subst as well. From: Pranathi Venkatayogi Sent: Thursday, June 15, 2017 6:22 PM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Subject: re.subst does not work with $var? I am trying to replace "domain1" with "domain2" in the msrp(body). Following stmt works where in I specify domain strings as literals. var(modBody) = $(msrp(body){re.subst,/()(domain1)()/domain2/g}); I am having trouble making the same work with $var variables. See below - this code does not do the replacement - $var(domain1) = "()(domain1)()"; $var(domain2) = "domain2"; var(modBody2) = $(msrp(body){re.subst,/$var(domain1)/$var(domain2)/g}); Any clue/ideas or is it by design? Thanks, Pranathi Venkatayogi System Developer II (520) 745-9447 x4466 www.cyracom.com<http://www.cyracom.com/> Join us: [cid:image001.gif@01D1C9C9.C4E8B6D0] <https://www.facebook.com/pages/CyraCom-LLC/134704783312720> [cid:image002.gif@01D1C9C9.C4E8B6D0] <https://twitter.com/cyracom> [cid:image003.gif@01D1C9C9.C4E8B6D0] <http://www.linkedin.com/company/cyracom> [cid:image004.gif@01D1C9C9.C4E8B6D0] <http://www.cyracom.com/blog/> [cid:image005.png@01D1C9C9.C4E8B6D0] DISCLAIMER: This e-mail and any attached content may contain confidential or privileged material delivered for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender immediately by reply e-mail and delete all copies of this message. It is the recipient's responsibility to scan this e-mail and any attachments for viruses. The content of this e-mail message, including any attachments, does not comprise a contract or a portion of a contract, and so does not bind CyraCom International, Inc. or any of its agents or subsidiaries. CyraCom, LLC and Voiance Language Services, LLC are wholly owned subsidiaries of CyraCom International, Inc.

1 0

two way routing
by Jean Cérien 19 Jun '17

19 Jun '17

Hello I am looking at the following configuration: 1/ voip providers, with different external sip servers, will send calls to kamailio, that will dispatch them to asterisk servers, with load balancing & failover. The IP of the asterisk servers are known and fixed. 2/ the asterisk servers will also place calls, going through kamailio, that will dispatch them to the voip provider sip servers, based on R-URI / Prefix. I've achieved #1 with dispatcher module, I've seen carrierroute module that can achieve #2, but I dont really grasp how to put the two together. I have the feeling that #1 can also be done with carrierroute, and that I only need to check if the 'from' domain is one my asterisk, and chose a different routing table, but I dont see how to do that is that a valid approch ? where should I look to do that ? thanks J.

3 7

Multiple FreeSWITCH servers behind kamailio-websocket
by Karsten Horsmann 19 Jun '17

19 Jun '17

Hello List, is there any howto about webrtc loadbalance in combination with kamailio and FreeSWITCH? I want to share one WSS address/endpoint to multiple FreeSWITCH backends. Or is there any other best practice? My callflow is mostly that my internal SIP Servers called my registered webrtc clients. Would be nice to get some input. -- Kind Regards *Karsten Horsmann*

5 7

How to change MSRP from sip address?
by Pranathi Venkatayogi 19 Jun '17

19 Jun '17

I need to replace the "From" address of MSRP message with something different. I noticed that module does not allow one to set values from config file. What does it take to enable this functionality? Does anyone have a prototype I can leverage? Need to replace from domain with some other domain - Given: MSRP body is - From: cust3 <sip:cust3@devtranslation.sms-test.cyracom.com>#015#012To: <sip:agent1@xmpp.xgw.cyracomdev.com>#015#012DateTime: ..... Wanted: MSRP body is - From: cust3 <sip:cust3@new domain >#015#012To: <sip:agent1@xmpp.xgw.cyracomdev.com>#015#012DateTime: ..... Thanks, Pranathi Venkatayogi System Developer II (520) 745-9447 x4466 www.cyracom.com<http://www.cyracom.com/> Join us: [cid:image001.gif@01D1C9C9.C4E8B6D0] <https://www.facebook.com/pages/CyraCom-LLC/134704783312720> [cid:image002.gif@01D1C9C9.C4E8B6D0] <https://twitter.com/cyracom> [cid:image003.gif@01D1C9C9.C4E8B6D0] <http://www.linkedin.com/company/cyracom> [cid:image004.gif@01D1C9C9.C4E8B6D0] <http://www.cyracom.com/blog/> [cid:image005.png@01D1C9C9.C4E8B6D0] DISCLAIMER: This e-mail and any attached content may contain confidential or privileged material delivered for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender immediately by reply e-mail and delete all copies of this message. It is the recipient's responsibility to scan this e-mail and any attachments for viruses. The content of this e-mail message, including any attachments, does not comprise a contract or a portion of a contract, and so does not bind CyraCom International, Inc. or any of its agents or subsidiaries. CyraCom, LLC and Voiance Language Services, LLC are wholly owned subsidiaries of CyraCom International, Inc.

3 4

Call and Voice issues
by Momen Amin 18 Jun '17

18 Jun '17

Description Hello! I'm beginner, and i have installed Kamailio Proxy SIP Server on Ubuntu 14.04.5 LTS and using it to register many SIP Servers (Asterisk) I have some issues: 1- When i call another extension in not ringing. 2- Sometimes ringing but when call is get answered there is no voice. 3- I need to receive inbound calls from my Trunks, but i did not know how to make my proxy able to manage it. 4- I need to call some futures codes like (*45 & 555) but it is unable to call. Thanks to all My "kamailio.cfg": #!define WITH_TLS #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB #!define WITH_MULTIDOMAIN #!define WITH_PSTN # Kamailio (OpenSER) SIP Server v5.0 - default configuration script # - web: http://www.kamailio.org` # - git: http://sip-router.org # # Direct your questions about this file to: <sr-users(a)lists.sip-router.org> # # Refer to the Core CookBook at http://www.kamailio.org/wiki/ # for an explanation of possible statements, functions and parameters. # # Note: the comments can be: # - lines starting with #, but not the pre-processor directives, # which start with #!, like #!define, #!ifdef, #!endif, #!else, #!trydef, # #!subst, #!substdef, ... # - lines starting with // # - blocks enclosed in between /* */ # # Several features can be enabled using '#!define WITH_FEATURE' directives: # # *** To run in debug mode: # - define WITH_DEBUG # # *** To enable mysql: # - define WITH_MYSQL # # *** To enable authentication execute: # - enable mysql # - define WITH_AUTH # - add users using 'kamctl' # # *** To enable IP authentication execute: # - enable mysql # - enable authentication # - define WITH_IPAUTH # - add IP addresses with group id '1' to 'address' table # # *** To enable persistent user location execute: # - enable mysql # - define WITH_USRLOCDB # # *** To enable presence server execute: # - enable mysql # - define WITH_PRESENCE # # *** To enable nat traversal execute: # - define WITH_NAT # - install RTPProxy: http://www.rtpproxy.org # - start RTPProxy: # rtpproxy -l _your_public_ip_ -s udp:localhost:7722 # - option for NAT SIP OPTIONS keepalives: WITH_NATSIPPING # # *** To enable PSTN gateway routing execute: # - define WITH_PSTN # - set the value of pstn.gw_ip # - check route[PSTN] for regexp routing condition # # *** To enable database aliases lookup execute: # - enable mysql # - define WITH_ALIASDB # # *** To enable speed dial lookup execute: # - enable mysql # - define WITH_SPEEDDIAL # # *** To enable multi-domain support execute: # - enable mysql # - define WITH_MULTIDOMAIN # # *** To enable TLS support execute: # - adjust CFGDIR/tls.cfg as needed # - define WITH_TLS # # *** To enable XMLRPC support execute: # - define WITH_XMLRPC # - adjust route[XMLRPC] for access policy # # *** To enable anti-flood detection execute: # - adjust pike and htable=>ipban settings as needed (default is # block if more than 16 requests in 2 seconds and ban for 300 seconds) # - define WITH_ANTIFLOOD # # *** To block 3XX redirect replies execute: # - define WITH_BLOCK3XX # # *** To block 401 and 407 authentication replies execute: # - define WITH_BLOCK401407 # # *** To enable VoiceMail routing execute: # - define WITH_VOICEMAIL # - set the value of voicemail.srv_ip # - adjust the value of voicemail.srv_port # # *** To enhance accounting execute: # - enable mysql # - define WITH_ACCDB # - add following columns to database #!ifdef ACCDB_COMMENT ALTER TABLE acc ADD COLUMN src_user VARCHAR(64) NOT NULL DEFAULT ''; ALTER TABLE acc ADD COLUMN src_domain VARCHAR(128) NOT NULL DEFAULT ''; ALTER TABLE acc ADD COLUMN src_ip varchar(64) NOT NULL default ''; ALTER TABLE acc ADD COLUMN dst_ouser VARCHAR(64) NOT NULL DEFAULT ''; ALTER TABLE acc ADD COLUMN dst_user VARCHAR(64) NOT NULL DEFAULT ''; ALTER TABLE acc ADD COLUMN dst_domain VARCHAR(128) NOT NULL DEFAULT ''; ALTER TABLE missed_calls ADD COLUMN src_user VARCHAR(64) NOT NULL DEFAULT ''; ALTER TABLE missed_calls ADD COLUMN src_domain VARCHAR(128) NOT NULL DEFAULT ''; ALTER TABLE missed_calls ADD COLUMN src_ip varchar(64) NOT NULL default ''; ALTER TABLE missed_calls ADD COLUMN dst_ouser VARCHAR(64) NOT NULL DEFAULT ''; ALTER TABLE missed_calls ADD COLUMN dst_user VARCHAR(64) NOT NULL DEFAULT ''; ALTER TABLE missed_calls ADD COLUMN dst_domain VARCHAR(128) NOT NULL DEFAULT ''; #!endif ####### Include Local Config If Exists ######### import_file "kamailio-local.cfg" ####### Defined Values ######### # *** Value defines - IDs used later in config #!ifdef WITH_MYSQL # - database URL - used to connect to database server by modules such # as: auth_db, acc, usrloc, a.s.o. #!ifndef DBURL #!define DBURL "mysql://kamailio:kamailiorw@localhost/kamailio" #!endif #!endif #!ifdef WITH_MULTIDOMAIN # - the value for 'use_domain' parameters #!define MULTIDOMAIN 1 #!else #!define MULTIDOMAIN 0 #!endif # - flags # FLT_ - per transaction (message) flags # FLB_ - per branch flags #!define FLT_ACC 1 #!define FLT_ACCMISSED 2 #!define FLT_ACCFAILED 3 #!define FLT_NATS 5 #!define FLB_NATB 6 #!define FLB_NATSIPPING 7 ####### Global Parameters ######### ### LOG Levels: 3=DBG, 2=INFO, 1=NOTICE, 0=WARN, -1=ERR #!ifdef WITH_DEBUG debug=4 log_stderror=yes #!else debug=2 log_stderror=no #!endif memdbg=5 memlog=5 log_facility=LOG_LOCAL0 /* number of SIP routing processes */ children=8 /* uncomment the next line to disable TCP (default on) */ # disable_tcp=yes /* uncomment the next line to disable the auto discovery of local aliases * based on reverse DNS on IPs (default on) */ # auto_aliases=yes /* add local domain aliases */ /* uncomment and configure the following line if you want Kamailio to * bind on a specific interface/port/proto (default bind on all available) */ /* # listen=udp:10.0.0.10:5060 */ listen=udp:127.0.0.1:6000 listen=udp:XXX.XXX.XXX.XXX:6000 listen=tls:XXX.XXX.XXX.XXX:5061 /* port to listen to (default 5060 for udp, tcp, scrtp, or 5061 for tls)*/ # port=5060 #!ifdef WITH_TLS enable_tls=yes #!endif /* life time of TCP connection when there is no traffic * - a bit higher than registration expires to cope with UA behind NAT */ tcp_connection_lifetime=3605 ####### Custom Parameters ######### /* These parameters can be modified runtime via RPC interface * - see the documentation of 'cfg_rpc' module. * * Format: group.id = value 'desc' description * Access: $sel(cfg_get.group.id) or @cfg_get.group.id */ #!ifdef WITH_PSTN /* PSTN GW Routing * * - pstn.gw_ip: valid IP or hostname as string value, example: * pstn.gw_ip = "10.0.0.101" desc "My PSTN GW Address" * * - by default is empty to avoid misrouting */ pstn.gw_ip = "XXX.XXX.XXX.XXX" desc "PSTN GW Address" pstn.gw_port = "5060" desc "PSTN GW Port" #!endif #!ifdef WITH_VOICEMAIL /* VoiceMail Routing on offline, busy or no answer * * - by default Voicemail server IP is empty to avoid misrouting */ voicemail.srv_ip = "" desc "VoiceMail IP Address" voicemail.srv_port = "5060" desc "VoiceMail Port" #!endif ####### Modules Section ######## /* set paths to location of modules */ # mpath="/usr/local//lib64/kamailio/modules/" #!ifdef WITH_MYSQL loadmodule "db_mysql.so" #!endif loadmodule "jsonrpcs.so" loadmodule "kex.so" loadmodule "corex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "usrloc.so" loadmodule "registrar.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "ctl.so" loadmodule "cfg_rpc.so" loadmodule "acc.so" loadmodule "counters.so" #!ifdef WITH_AUTH loadmodule "auth.so" loadmodule "auth_db.so" #!ifdef WITH_IPAUTH loadmodule "permissions.so" #!endif #!endif #!ifdef WITH_ALIASDB loadmodule "alias_db.so" #!endif #!ifdef WITH_SPEEDDIAL loadmodule "speeddial.so" #!endif #!ifdef WITH_MULTIDOMAIN loadmodule "domain.so" #!endif #!ifdef WITH_PRESENCE loadmodule "presence.so" loadmodule "presence_xml.so" #!endif #!ifdef WITH_NAT loadmodule "nathelper.so" loadmodule "rtpproxy.so" #!endif #!ifdef WITH_TLS loadmodule "tls.so" #!endif #!ifdef WITH_ANTIFLOOD loadmodule "htable.so" loadmodule "pike.so" #!endif #!ifdef WITH_XMLRPC loadmodule "xmlrpc.so" #!endif #!ifdef WITH_DEBUG loadmodule "debugger.so" #!endif # ----------------- setting module-specific parameters --------------- # ----- jsonrpcs params ----- modparam("jsonrpcs", "pretty_format", 1) /* set the path to RPC fifo control file */ # modparam("jsonrpcs", "fifo_name", "/var/run/kamailio/kamailio_rpc.fifo") /* set the path to RPC unix socket control file */ # modparam("jsonrpcs", "dgram_socket", "/var/run/kamailio/kamailio_rpc.sock") # ----- ctl params ----- /* set the path to RPC unix socket control file */ # modparam("ctl", "binrpc", "unix:/var/run/kamailio/kamailio_ctl") # ----- tm params ----- # auto-discard branches from previous serial forking leg modparam("tm", "failure_reply_mode", 3) # default retransmission timeout: 30sec modparam("tm", "fr_timer", 30000) # default invite retransmission timeout after 1xx: 120sec modparam("tm", "fr_inv_timer", 120000) # ----- rr params ----- # set next param to 1 to add value to ;lr param (helps with some UAs) modparam("rr", "enable_full_lr", 0) # do not append from tag to the RR (no need for this script) modparam("rr", "append_fromtag", 0) # ----- registrar params ----- modparam("registrar", "method_filtering", 1) /* uncomment the next line to disable parallel forking via location */ # modparam("registrar", "append_branches", 0) /* uncomment the next line not to allow more than 10 contacts per AOR */ # modparam("registrar", "max_contacts", 10) /* max value for expires of registrations */ modparam("registrar", "max_expires", 3600) /* set it to 1 to enable GRUU */ modparam("registrar", "gruu_enabled", 0) # ----- acc params ----- /* what special events should be accounted ? */ modparam("acc", "early_media", 0) modparam("acc", "report_ack", 0) modparam("acc", "report_cancels", 0) /* by default ww do not adjust the direct of the sequential requests. * if you enable this parameter, be sure the enable "append_fromtag" * in "rr" module */ modparam("acc", "detect_direction", 0) /* account triggers (flags) */ modparam("acc", "log_flag", FLT_ACC) modparam("acc", "log_missed_flag", FLT_ACCMISSED) modparam("acc", "log_extra", "src_user=$fU;src_domain=$fd;src_ip=$si;" "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd") modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) /* enhanced DB accounting */ #!ifdef WITH_ACCDB modparam("acc", "db_flag", FLT_ACC) modparam("acc", "db_missed_flag", FLT_ACCMISSED) modparam("acc", "db_url", DBURL) modparam("acc", "db_extra", "src_user=$fU;src_domain=$fd;src_ip=$si;" "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd") #!endif # ----- usrloc params ----- /* enable DB persistency for location entries */ #!ifdef WITH_USRLOCDB modparam("usrloc", "db_url", DBURL) modparam("usrloc", "db_mode", 2) modparam("usrloc", "use_domain", MULTIDOMAIN) #!endif # ----- auth_db params ----- #!ifdef WITH_AUTH modparam("auth_db", "db_url", DBURL) modparam("auth_db", "calculate_ha1", yes) modparam("auth_db", "password_column", "password") modparam("auth_db", "load_credentials", "") modparam("auth_db", "use_domain", MULTIDOMAIN) # ----- permissions params ----- #!ifdef WITH_IPAUTH modparam("permissions", "db_url", DBURL) modparam("permissions", "db_mode", 1) #!endif #!endif # ----- alias_db params ----- #!ifdef WITH_ALIASDB modparam("alias_db", "db_url", DBURL) modparam("alias_db", "use_domain", MULTIDOMAIN) #!endif # ----- speeddial params ----- #!ifdef WITH_SPEEDDIAL modparam("speeddial", "db_url", DBURL) modparam("speeddial", "use_domain", MULTIDOMAIN) #!endif # ----- domain params ----- #!ifdef WITH_MULTIDOMAIN modparam("domain", "db_url", DBURL) /* register callback to match myself condition with domains list */ modparam("domain", "register_myself", 1) #!endif #!ifdef WITH_PRESENCE # ----- presence params ----- modparam("presence", "db_url", DBURL) # ----- presence_xml params ----- modparam("presence_xml", "db_url", DBURL) modparam("presence_xml", "force_active", 1) #!endif #!ifdef WITH_NAT # ----- rtpproxy params ----- modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722") # ----- nathelper params ----- modparam("nathelper", "natping_interval", 30) modparam("nathelper", "ping_nated_only", 1) modparam("nathelper", "sipping_bflag", FLB_NATSIPPING) modparam("nathelper", "sipping_from", "sip:pinger@kamailio.org") # params needed for NAT traversal in other modules modparam("nathelper|registrar", "received_avp", "$avp(RECEIVED)") modparam("usrloc", "nat_bflag", FLB_NATB) #!endif #!ifdef WITH_TLS # ----- tls params ----- modparam("tls", "config", "/usr/local//etc/kamailio/tls.cfg") #!endif #!ifdef WITH_ANTIFLOOD # ----- pike params ----- modparam("pike", "sampling_time_unit", 2) modparam("pike", "reqs_density_per_unit", 16) modparam("pike", "remove_latency", 4) # ----- htable params ----- /* ip ban htable with autoexpire after 5 minutes */ modparam("htable", "htable", "ipban=>size=8;autoexpire=300;") #!endif #!ifdef WITH_XMLRPC # ----- xmlrpc params ----- modparam("xmlrpc", "route", "XMLRPC"); modparam("xmlrpc", "url_match", "^/RPC") #!endif #!ifdef WITH_DEBUG # ----- debugger params ----- modparam("debugger", "cfgtrace", 1) modparam("debugger", "log_level_name", "exec") #!endif ####### Routing Logic ######## /* Main SIP request routing logic * - processing of any incoming SIP request starts with this route * - note: this is the same as route { ... } */ request_route { # per request initial checks route(REQINIT); # NAT detection route(NATDETECT); # CANCEL processing if (is_method("CANCEL")) { if (t_check_trans()) { route(RELAY); } exit; } # handle requests within SIP dialogs route(WITHINDLG); ### only initial requests (no To tag) # handle retransmissions if(t_precheck_trans()) { t_check_trans(); exit; } t_check_trans(); # authentication route(AUTH); # record routing for dialog forming requests (in case they are routed) # - remove preloaded route headers remove_hf("Route"); if (is_method("INVITE|SUBSCRIBE")) { record_route(); } # account only INVITEs if (is_method("INVITE")) { setflag(FLT_ACC); # do accounting } # dispatch requests to foreign domains route(SIPOUT); ### requests for my local domains # handle presence related requests route(PRESENCE); # handle registrations route(REGISTRAR); if ($rU==$null) { # request with no Username in RURI sl_send_reply("484","Address Incomplete"); exit; } # dispatch destinations to PSTN route(PSTN); # user location service route(LOCATION); } # Wrapper for relaying requests route[RELAY] { # enable additional event routes for forwarded requests # - serial forking, RTP relaying handling, a.s.o. if (is_method("INVITE|BYE|SUBSCRIBE|UPDATE")) { if(!t_is_set("branch_route")) t_on_branch("MANAGE_BRANCH"); } if (is_method("INVITE|SUBSCRIBE|UPDATE")) { if(!t_is_set("onreply_route")) t_on_reply("MANAGE_REPLY"); } if (is_method("INVITE")) { if(!t_is_set("failure_route")) t_on_failure("MANAGE_FAILURE"); } if (!t_relay()) { sl_reply_error(); } exit; } # Per SIP request initial checks route[REQINIT] { #!ifdef WITH_ANTIFLOOD # flood detection from same IP and traffic ban for a while # be sure you exclude checking trusted peers, such as pstn gateways # - local host excluded (e.g., loop to self) if(src_ip!=myself) { if($sht(ipban=>$si)!=$null) { # ip is already blocked xdbg("request from blocked IP - $rm from $fu (IP:$si:$sp)\n"); exit; } if (!pike_check_req()) { xlog("L_ALERT","ALERT: pike blocking $rm from $fu (IP:$si:$sp)\n"); $sht(ipban=>$si) = 1; exit; } } if($ua =~ "friendly-scanner|sipcli") { # silent drop for scanners - uncomment next line if want to reply # sl_send_reply("200", "OK"); exit; } #!endif if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; } if(is_method("OPTIONS") && uri==myself && $rU==$null) { sl_send_reply("200","Keepalive"); exit; } if(!sanity_check("1511", "7")) { xlog("Malformed SIP message from $si:$sp\n"); exit; } } # Handle requests within SIP dialogs route[WITHINDLG] { if (!has_totag()) return; # sequential request withing a dialog should # take the path determined by record-routing if (loose_route()) { route(DLGURI); if (is_method("BYE")) { setflag(FLT_ACC); # do accounting ... setflag(FLT_ACCFAILED); # ... even if the transaction fails } else if ( is_method("ACK") ) { # ACK is forwarded statelessy route(NATMANAGE); } else if ( is_method("NOTIFY") ) { # Add Record-Route for in-dialog NOTIFY as per RFC 6665. record_route(); } route(RELAY); exit; } if (is_method("SUBSCRIBE") && uri == myself) { # in-dialog subscribe requests route(PRESENCE); exit; } if ( is_method("ACK") ) { if ( t_check_trans() ) { # no loose-route, but stateful ACK; # must be an ACK after a 487 # or e.g. 404 from upstream server route(RELAY); exit; } else { # ACK without matching transaction ... ignore and discard exit; } } sl_send_reply("404","Not here"); exit; } # Handle SIP registrations route[REGISTRAR] { if (!is_method("REGISTER")) return; if(isflagset(FLT_NATS)) { setbflag(FLB_NATB); #!ifdef WITH_NATSIPPING # do SIP NAT pinging setbflag(FLB_NATSIPPING); #!endif } if (!save("location")) { sl_reply_error(); } exit; } # User location service route[LOCATION] { #!ifdef WITH_SPEEDDIAL # search for short dialing - 2-digit extension if($rU=~"^[0-9][0-9]$") { if(sd_lookup("speed_dial")) { route(SIPOUT); } } #!endif #!ifdef WITH_ALIASDB # search in DB-based aliases if(alias_db_lookup("dbaliases")) { route(SIPOUT); } #!endif $avp(oexten) = $rU; if (!lookup("location")) { $var(rc) = $rc; route(TOVOICEMAIL); t_newtran(); switch ($var(rc)) { case -1: case -3: send_reply("404", "Not Found"); exit; case -2: send_reply("405", "Method Not Allowed"); exit; } } # when routing via usrloc, log the missed calls also if (is_method("INVITE")) { setflag(FLT_ACCMISSED); } route(RELAY); exit; } # Presence server processing route[PRESENCE] { if(!is_method("PUBLISH|SUBSCRIBE")) return; if(is_method("SUBSCRIBE") && $hdr(Event)=="message-summary") { route(TOVOICEMAIL); # returns here if no voicemail server is configured sl_send_reply("404", "No voicemail service"); exit; } #!ifdef WITH_PRESENCE if (!t_newtran()) { sl_reply_error(); exit; } if(is_method("PUBLISH")) { handle_publish(); t_release(); } else if(is_method("SUBSCRIBE")) { handle_subscribe(); t_release(); } exit; #!endif # if presence enabled, this part will not be executed if (is_method("PUBLISH") || $rU==$null) { sl_send_reply("404", "Not here"); exit; } return; } # IP authorization and user authentication route[AUTH] { #!ifdef WITH_AUTH #!ifdef WITH_IPAUTH if((!is_method("REGISTER")) && allow_source_address()) { # source IP allowed return; } #!endif if (is_method("REGISTER") || from_uri==myself) { # authenticate requests if (!auth_check("$fd", "subscriber", "1")) { auth_challenge("$fd", "0"); exit; } # user authenticated - remove auth header if(!is_method("REGISTER|PUBLISH")) consume_credentials(); } # if caller is not local subscriber, then check if it calls # a local destination, otherwise deny, not an open relay here if (from_uri!=myself && uri!=myself) { sl_send_reply("403","Not relaying"); exit; } #!endif return; } # Caller NAT detection route[NATDETECT] { #!ifdef WITH_NAT force_rport(); if (nat_uac_test("19")) { if (is_method("REGISTER")) { fix_nated_register(); } else { if(is_first_hop()) { set_contact_alias(); } } setflag(FLT_NATS); } #!endif return; } # RTPProxy control and signaling updates for NAT traversal route[NATMANAGE] { #!ifdef WITH_NAT if (is_request()) { if(has_totag()) { if(check_route_param("nat=yes")) { setbflag(FLB_NATB); } } } if (!(isflagset(FLT_NATS) || isbflagset(FLB_NATB))) return; if(nat_uac_test("8")) { rtpproxy_manage("co"); } else { rtpproxy_manage("cor"); } if (is_request()) { if (!has_totag()) { if(t_is_branch_route()) { add_rr_param(";nat=yes"); } } } if (is_reply()) { if(isbflagset(FLB_NATB)) { if(is_first_hop()) set_contact_alias(); } } #!endif return; } # URI update for dialog requests route[DLGURI] { #!ifdef WITH_NAT if(!isdsturiset()) { handle_ruri_alias(); } #!endif return; } # Routing to foreign domains route[SIPOUT] { if (uri==myself) return; append_hf("P-hint: outbound\r\n"); route(RELAY); exit; } # PSTN GW routing route[PSTN] { #!ifdef WITH_PSTN # check if PSTN GW IP is defined if (strempty($sel(cfg_get.pstn.gw_ip))) { xlog("SCRIPT: PSTN routing enabled but pstn.gw_ip not defined\n"); return; } # route to PSTN dialed numbers starting with '+' or '00' # (international format) # - update the condition to match your dialing rules for PSTN routing if(!($rU=~"^(\+|00)[1-9][0-9]{3,20}$")) return; # only local users allowed to call if(from_uri!=myself) { sl_send_reply("403", "Not Allowed"); exit; } if (strempty($sel(cfg_get.pstn.gw_port))) { $ru = "sip:" + $rU + "@" + $sel(cfg_get.pstn.gw_ip); } else { $ru = "sip:" + $rU + "@" + $sel(cfg_get.pstn.gw_ip) + ":" + $sel(cfg_get.pstn.gw_port); } route(RELAY); exit; #!endif return; } # XMLRPC routing #!ifdef WITH_XMLRPC route[XMLRPC] { # allow XMLRPC from localhost if ((method=="POST" || method=="GET") && (src_ip==127.0.0.1)) { # close connection only for xmlrpclib user agents (there is a bug in # xmlrpclib: it waits for EOF before interpreting the response). if ($hdr(User-Agent) =~ "xmlrpclib") set_reply_close(); set_reply_no_connect(); dispatch_rpc(); exit; } send_reply("403", "Forbidden"); exit; } #!endif # Routing to voicemail server route[TOVOICEMAIL] { #!ifdef WITH_VOICEMAIL if(!is_method("INVITE|SUBSCRIBE")) return; # check if VoiceMail server IP is defined if (strempty($sel(cfg_get.voicemail.srv_ip))) { xlog("SCRIPT: VoiceMail routing enabled but IP not defined\n"); return; } if(is_method("INVITE")) { if($avp(oexten)==$null) return; $ru = "sip:" + $avp(oexten) + "@" + $sel(cfg_get.voicemail.srv_ip) + ":" + $sel(cfg_get.voicemail.srv_port); } else { if($rU==$null) return; $ru = "sip:" + $rU + "@" + $sel(cfg_get.voicemail.srv_ip) + ":" + $sel(cfg_get.voicemail.srv_port); } route(RELAY); exit; #!endif return; } # Manage outgoing branches branch_route[MANAGE_BRANCH] { xdbg("new branch [$T_branch_idx] to $ru\n"); route(NATMANAGE); } # Manage incoming replies onreply_route[MANAGE_REPLY] { xdbg("incoming reply\n"); if(status=~"[12][0-9][0-9]") { route(NATMANAGE); } } # Manage failure routing cases failure_route[MANAGE_FAILURE] { route(NATMANAGE); if (t_is_canceled()) exit; #!ifdef WITH_BLOCK3XX # block call redirect based on 3xx replies. if (t_check_status("3[0-9][0-9]")) { t_reply("404","Not found"); exit; } #!endif #!ifdef WITH_BLOCK401407 # block call redirect based on 401, 407 replies. if (t_check_status("401|407")) { t_reply("404","Not found"); exit; } #!endif #!ifdef WITH_VOICEMAIL # serial forking # - route to voicemail on busy or no answer (timeout) if (t_check_status("486|408")) { $du = $null; route(TOVOICEMAIL); exit; } #!endif }

1 0

Strange issue in registering users in Kamailio
by Mojtaba 17 Jun '17

17 Jun '17

Hello guys, Finally i found what was my problem. It was about ARP table size, becuase is set to 1024 record in ubuntu. when i try to register a lot of users with different source ip to kamailio (or other sip server like asterisk and etc), after some minutes, the arp table is fulled and these warrning may be issue: In kamailio: Jun 14 16:06:50 172-1-1-158 /usr/local/kamailio-5.0/sbin/kamailio[31864]: ERROR: <core> [core/tcp_read.c:1319]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f2518774590 r: 0x7f2518774610 Jun 14 16:06:50 172-1-1-158 /usr/local/kamailio-5.0/sbin/kamailio[31859]: ERROR: <core> [core/tcp_read.c:1319]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f2518d4ebf0 r: 0x7f2518d4ec70 Jun 14 16:06:50 172-1-1-158 /usr/local/kamailio-5.0/sbin/kamailio[31868]: ERROR: <core> [core/tcp_read.c:291]: tcp_read_data(): error reading: Connection reset by peer (104) ([192.168.13.227]:59948 -> Jun 14 16:06:50 172-1-1-158 /usr/local/kamailio-5.0/sbin/kamailio[31868]: ERROR: <core> [core/tcp_read.c:292]: tcp_read_data(): -> [192.168.0.221]:5060) Jun 14 16:06:50 172-1-1-158 /usr/local/kamailio-5.0/sbin/kamailio[31868]: ERROR: <core> [core/tcp_read.c:1319]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f25191387c0 r: 0x7f2519138840 J In Asterisk: Jun 16 00:59:09 asterisk11 kernel: [ 5042.988477] Neighbour table overflow [Jun 16 00:59:14] WARNING[2811] chan_sip.c: sip_xmit of 0x7f94fd08a4e0 (len 488) to 192.168.14.116:5060 returned -1: No buffer space available you should add some parameters in sysctl.conf in ubuntu: net.ipv4.neigh.default.gc_thresh1 = 512 net.ipv4.neigh.default.gc_thresh2 = 1024 net.ipv4.neigh.default.gc_thresh3 = 2048 Good luck With regards.Mojtaba Esfandiari.S -- --Mojtaba Esfandiari.S

1 0

Kamailio v4.4.6 Released
by Daniel-Constantin Mierla 16 Jun '17

16 Jun '17

Hello, Kamailio SIP Server v4.4.6 stable release is out. This is a maintenance release of the latest stable branch, 4.4, that includes fixes since the release of v4.4.5. There is no change to database schema or configuration language structure that you have to do on previous installations of v4.4.x. Deployments running previous v4.x.x versions are strongly recommended to be upgraded to v4.4.6. For more details about version 4.4.6 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2017/06/kamailio-v4-4-6-released/ RPM, Debian/Ubuntu packages will be available soon as well. Note: the latest stable branch is 5.0, at this moment with its latest release v5.0.2. See more details about it at: * https://www.kamailio.org/w/kamailio-v5-0-0-release-notes/ Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Planning Kamailio v4.4.6
by Daniel-Constantin Mierla 16 Jun '17

16 Jun '17

Hello, I backported a consistent set of patches to branch 4.4 and plan to release v4.4.6 in the next days. Should anyone be interested in that branch, it would be good to review and see if any relevant fix from newer branches is missing in order to assert the feasibility of backporting. If time allows, 4.4.6 can be out as soon as tomorrow afternoon, if not, sometime during following days. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com

2 3

Re: [SR-Users] Topos: contact header is not updated avec RE-INVITE
by Sergey Basov 16 Jun '17

16 Jun '17

You are welcome. -- WBR Sergey Basov 15 июня 2017 г. 10:13 PM пользователь "Abdoul Osséni" < abdoul.osseni(a)gmail.com> написал: > Hello, yes, you were right. > > There was something wrong in my routing config. > See below, I remove the bad config. > > Thank you very much > > route[WITHINDLG] { > > …… > > …. > > if (loose_route()) { > > route(DLGURI); > > if (is_method("BYE")) { > > setflag(FLT_ACC); # do accounting ... > > setflag(FLT_ACCFAILED); # ... even if the > transaction fails > > } else if ( is_method("ACK") ) { > > # ACK is forwarded statelessy > > route(NATMANAGE); > > } else if ( is_method("NOTIFY") ) { > > # Add Record-Route for in-dialog NOTIFY as per RFC > 6665. > > record_route(); > > } > > else if ( is_method("INVITE") ) { > > # even if in most of the cases is useless, do RR > for > > # re-INVITEs alos, as some buggy clients do change route > set > > # during the dialog. > > xlog("Route with in Dialog: loose route $rU -> $fU\n"); > > record_route(); > > } > > route(RELAY); > > exit; > > } > > …… > > …. > > } > > > Regards > > > 2017-06-15 16:27 GMT+02:00 Sergey Basov <sergey.v.basov(a)gmail.com>: > >> Do you only change topoh to topos in your config? >> >> You can find my dump attached. There is duplicate packets this is issue >> of my capture architecture.. >> >> -- >> WBR >> Sergey Basov >> >> 15 июня 2017 г. 5:20 PM пользователь "Sergey Basov" < >> sergey.v.basov(a)gmail.com> написал: >> >> Its very strange... >> I have record routes from 1 side and from another side, they are stripped >> and restored normaly. >> >> On reinvite you have incorrect contact restored. >> >> I will look at my config. >> >> -- >> WBR >> Sergey Basov >> >> 15 июня 2017 г. 5:09 PM пользователь "Abdoul Osséni" < >> abdoul.osseni(a)gmail.com> написал: >> >> The record route is missing with topos module. Maybe it is that the >>> problem? >>> Regards. >>> >>> 2017-06-15 16:04 GMT+02:00 Abdoul Osséni <abdoul.osseni(a)gmail.com>: >>> >>>> >>>> I tried with an another uac (without +sip.instance="<urn:uuid:14d62 >>>> d4f-8426-486b-88ee-077b9ff1fae2>" in contact). Same issue. >>>> >>>> I checked my routing logic in Kamailio. Same configs describe ici : >>>> http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asteri >>>> sk-11.3.0-astdb?s[]=asterisk. >>>> >>>> >>>> [image: Images intégrées 1] >>>> >>>> Regards >>>> >>>> Abdoul. >>>> >>>> 2017-06-15 14:34 GMT+02:00 Sergey Basov <sergey.v.basov(a)gmail.com>: >>>> >>>>> I checked in my environment all ok. >>>>> Can you try without +sip.instance="<urn:uuid:14d62 >>>>> d4f-8426-486b-88ee-077b9ff1fae2>" in contact? >>>>> >>>>> -- >>>>> Best regards, >>>>> Sergey Basov e-mail: sergey.v.basov(a)gmail.com >>>>> >>>>> 2017-06-15 12:52 GMT+03:00 Abdoul Osséni <abdoul.osseni(a)gmail.com>: >>>>> >>>>>> >>>>>> Please find in attachment. >>>>>> >>>>>> - topos module is disabled >>>>>> - topoh module is enabled >>>>>> >>>>>> I have no issue -- the contact header is updated. >>>>>> >>>>>> I have only this issue when topos module is enabled but I will check >>>>>> again my routing logic in kamailio. >>>>>> >>>>>> Regards >>>>>> >>>>>> 2017-06-15 11:39 GMT+02:00 Sergey Basov <sergey.v.basov(a)gmail.com>: >>>>>> >>>>>>> I think you may have some error in your routing logic in kamailio... >>>>>>> >>>>>>> Can you try to disable topos module and try with topoh to see does >>>>>>> it handles contact modification properly? >>>>>>> >>>>>>> -- >>>>>>> Best regards, >>>>>>> Sergey Basov e-mail: sergey.v.basov(a)gmail.com >>>>>>> >>>>>>> 2017-06-15 12:07 GMT+03:00 Abdoul Osséni <abdoul.osseni(a)gmail.com>: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> Please find in attachment the pcap file. >>>>>>>> >>>>>>>> Regards >>>>>>>> >>>>>>>> Abdoul >>>>>>>> >>>>>>>> 2017-06-15 9:43 GMT+02:00 Sergey Basov <sergey.v.basov(a)gmail.com>: >>>>>>>> >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>> Can you send dump of the both side of call. >>>>>>>>> I using this module into production I have a lot of Re-Invites and >>>>>>>>> does not have this problem. >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Best regards, >>>>>>>>> Sergey Basov e-mail: sergey.v.basov(a)gmail.com >>>>>>>>> >>>>>>>>> 2017-06-15 10:18 GMT+03:00 Abdoul Osséni <abdoul.osseni(a)gmail.com> >>>>>>>>> : >>>>>>>>> >>>>>>>>>> Hello, >>>>>>>>>> >>>>>>>>>> I have an issue when loading topos module on Kamailio 5.0.2 >>>>>>>>>> version. >>>>>>>>>> >>>>>>>>>> root@proxy:/home/tcpdump# kamailio -V >>>>>>>>>> version: kamailio 5.0.2 (x86_64/linux) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> The call flow is: uac --> kamailio --> Asterisk >>>>>>>>>> >>>>>>>>>> 1) Invite from uac >>>>>>>>>> 2) Kamailio forward the invite to asterisk >>>>>>>>>> 3) asterisk send 200 OK to kamailio >>>>>>>>>> 4) kamailio send 200 OK to uac -> in the conctact header, i can >>>>>>>>>> see the IP address of kamailio >>>>>>>>>> 5) uac send ACK to kamailio and kamailio forward the ACK to >>>>>>>>>> Asterisk >>>>>>>>>> 6) uac send re-invite: "media change" to kamailio. >>>>>>>>>> 7) kamailio forward the re-invite to asterisk and asterisk send >>>>>>>>>> 200 OK to kamailio >>>>>>>>>> 8) kamailio send 200 ok to uac --> but the contact header >>>>>>>>>> contains IP of Asterisk and not kamailio: is it normal? >>>>>>>>>> >>>>>>>>>> Thank for you help. >>>>>>>>>> >>>>>>>>>> Regards >>>>>>>>>> -- >>>>>>>>>> Abdoul OSSENI >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Kamailio (SER) - Users Mailing List >>>>>>>>>> sr-users(a)lists.kamailio.org >>>>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Kamailio (SER) - Users Mailing List >>>>>>>>> sr-users(a)lists.kamailio.org >>>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Abdoul OSSENI >>>>>> Ingénieur Réseaux et systèmes chez THALES >>>>>> Co-Fondateur de ON SERVICES >>>>>> Tél : +33 601 135 167 >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Abdoul OSSENI >>>> Ingénieur Réseaux et systèmes chez THALES >>>> Co-Fondateur de ON SERVICES >>>> Tél : +33 601 135 167 >>>> >>> >>> >>> >>> -- >>> Abdoul OSSENI >>> Ingénieur Réseaux et systèmes chez THALES >>> Co-Fondateur de ON SERVICES >>> Tél : +33 601 135 167 >>> >> >> > > > -- > Abdoul OSSENI > Ingénieur Réseaux et systèmes chez THALES > Co-Fondateur de ON SERVICES > Tél : +33 601 135 167 >

1 0

re.subst does not work with $var?
by Pranathi Venkatayogi 15 Jun '17

15 Jun '17

I am trying to replace "domain1" with "domain2" in the msrp(body). Following stmt works where in I specify domain strings as literals. var(modBody) = $(msrp(body){re.subst,/()(domain1)()/domain2/g}); I am having trouble making the same work with $var variables. See below - this code does not do the replacement - $var(domain1) = "()(domain1)()"; $var(domain2) = "domain2"; var(modBody2) = $(msrp(body){re.subst,/$var(domain1)/$var(domain2)/g}); Any clue/ideas or is it by design? Thanks, Pranathi Venkatayogi System Developer II (520) 745-9447 x4466 www.cyracom.com<http://www.cyracom.com/> Join us: [cid:image001.gif@01D1C9C9.C4E8B6D0] <https://www.facebook.com/pages/CyraCom-LLC/134704783312720> [cid:image002.gif@01D1C9C9.C4E8B6D0] <https://twitter.com/cyracom> [cid:image003.gif@01D1C9C9.C4E8B6D0] <http://www.linkedin.com/company/cyracom> [cid:image004.gif@01D1C9C9.C4E8B6D0] <http://www.cyracom.com/blog/> [cid:image005.png@01D1C9C9.C4E8B6D0] DISCLAIMER: This e-mail and any attached content may contain confidential or privileged material delivered for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender immediately by reply e-mail and delete all copies of this message. It is the recipient's responsibility to scan this e-mail and any attachments for viruses. The content of this e-mail message, including any attachments, does not comprise a contract or a portion of a contract, and so does not bind CyraCom International, Inc. or any of its agents or subsidiaries. CyraCom, LLC and Voiance Language Services, LLC are wholly owned subsidiaries of CyraCom International, Inc.

1 0

Kamailio+Asterisk - Kamailio doesn't forward INVITE to 2nd Kamailio
by Marko Tirs 15 Jun '17

15 Jun '17

Hi all, I have here:Kamailio 1: 192.168.0.11Kamailio 2: 192.168.0.21Asterisk 1: 192.168.0.12 Asterisk1 is registered on Kamailio1 as User 100. Asterisk1 shouldn't be registered on Kamailio2. User 111 registered on Kamailio1User 211 registered on Kamailio2User 121 registered on Asterisk1 Test cases:---------------------111 calls 211 - OK211 calls 111 - OK121 calls 111 - OK121 calls 211 - Kamailio1 doesn't forward INVITE to Kamailio2, Asterisk gets 'Busy' !? Is the approach just to replace destination IP-address in $ru, depending from 1st digit, right? If not, what is the right approach to reach the remote users from Asterisk, which are registered on remote Kamailio and not on the local Kamailio? Thank youRegardsMarko My changes in kamailio.cfg in both kamailios (based on kamailio-basic.cfg) :--------------------------------------------------------------------------------------------------------------kamailio1.bindip = "192.168.0.11" kamailio2.bindip = "192.168.0.21" ...route { if (is_method("INVITE")) { if($rU=~"^1[0-9][0-9]$") { $ru = "sip:" + $rU + "@" + $sel(cfg_get.kamailio1.bindip) + ":5060"; } else if($rU=~"^2[0-9][0-9]$") { $ru = "sip:" + $rU + "@" + $sel(cfg_get.kamailio2.bindip) + ":5060"; } } ... sip.conf in Asterisk1:---------------------------------- register => 100:abc@192.168.0.124:5060/100 [100] type=friend host=192.168.0.11 secret=abc context=kamailio [121] type=friend secret=abc host=dynamic context=kamailio extensions.conf-------------------------------[kamailio] exten => _[1-4]XX,1,Dial(SIP/100/${EXTEN},30) exten => _[1-4]XX,n,Hangup()

2 2

Problem changing the SDP origin after a failure route
by Pascal Poudrier 15 Jun '17

15 Jun '17

2 2

Session timer issue
by sgy 15 Jun '17

15 Jun '17

Hi All, As I know, if session timer of request is less than server's Min-SE, the server will reply with its Min-SE, but the following packet confuse me, anyone can show me why? INVITE sip:1001@47.93.228.87 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.104:34260;branch=z9hG4bK-d87543-020579432b285a66-1--d87543-;rport Max-Forwards: 70 Contact: <sip:1000@101.40.128.122:34260> To: "1001"<sip:1001@47.93.228.87> From: "pc"<sip:1000@47.93.228.87>;tag=5a6d113b Call-ID: MDZjOGY5OGYzYWQ0YmE2MGJmN2U5Y2YwNDYzOTliNDI. CSeq: 1 INVITE Session-Expires: 95 Min-SE: 90 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO Content-Type: application/sdp Supported: timer User-Agent: eyeBeam release 1011d stamp 40820 Content-Length: 444 v=0 o=- 2 2 IN IP4 192.168.1.104 s=CounterPath eyeBeam 1.5 SIP/2.0 422 Session Timer Too Small Via: SIP/2.0/UDP 192.168.1.104:34260;branch=z9hG4bK-d87543-020579432b285a66-1--d87543-;rport=34260;received=101.40.128.122 To: "1001"<sip:1001@47.93.228.87>;tag=f27196751f2f83b7cedd2e1f5efe4626.6254 From: "pc"<sip:1000@47.93.228.87>;tag=5a6d113b Call-ID: MDZjOGY5OGYzYWQ0YmE2MGJmN2U5Y2YwNDYzOTliNDI. CSeq: 1 INVITE Min-SE: 60 Server: kamailio (5.1.0-dev3 (x86_64/linux)) Content-Length: 0 My config: modparam("dialog", "dlg_flag", 4) modparam("dialog", "db_url", DBURL) modparam("dialog", "db_mode", 1) modparam("dialog", "default_timeout", 80) modparam("dialog", "timeout_avp", "$avp(i:10)") modparam("sst", "timeout_avp", "$avp(i:10)") modparam("sst", "min_se", 60) modparam("sst", "sst_flag", 6) if (method=="INVITE") { if (sstCheckMin("1")) { xlog("L_ERR", "422 Session Timer Too Small reply sent.\n"); exit; } setflag(4); # set the dialog flag setflag(6); # Set the sst flag } -- Best Regards, Shengy

2 4

best practice to re-install rtpengine after jessie to stretch upgrade?
by Juha Heinanen 15 Jun '17

15 Jun '17

I made a test upgrade from Debian Jessie to Stretch while rtpengine 5.1.1 was running on Jessie. What is the best practice to get xt_RTPENGINE module installed in the new Stretch linux kernel, since it does not happen automatically. Should I reinstall rtpengine* packages or is there some better way? -- Juha

3 3

Does Kamailio send BYE if opposite side lost connection?
by Nguyen Tran Nhan 15 Jun '17

15 Jun '17

Hi all, I am working in basic call. I got common cause that opposite side (callee) lost connection and caller still hangging in the call. Is there any message to server to caller in this case? Thanks, Nhan

4 8

Topos: contact header is not updated avec RE-INVITE
by Abdoul Osséni 15 Jun '17

15 Jun '17

Hello, I have an issue when loading topos module on Kamailio 5.0.2 version. root@proxy:/home/tcpdump# kamailio -V version: kamailio 5.0.2 (x86_64/linux) The call flow is: uac --> kamailio --> Asterisk 1) Invite from uac 2) Kamailio forward the invite to asterisk 3) asterisk send 200 OK to kamailio 4) kamailio send 200 OK to uac -> in the conctact header, i can see the IP address of kamailio 5) uac send ACK to kamailio and kamailio forward the ACK to Asterisk 6) uac send re-invite: "media change" to kamailio. 7) kamailio forward the re-invite to asterisk and asterisk send 200 OK to kamailio 8) kamailio send 200 ok to uac --> but the contact header contains IP of Asterisk and not kamailio: is it normal? Thank for you help. Regards -- Abdoul OSSENI

2 1

Kamailio v5.0.2 Released
by Daniel-Constantin Mierla 14 Jun '17

14 Jun '17

Hello, Kamailio SIP Server v5.0.2 stable release is out! This is a maintenance release of the latest stable branch, 5.0, that includes fixes since the release of v5.0.1. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.0.x. Deployments running previous 5.0.x versions are strongly recommended to be upgraded to v5.0.2. For more details about version 5.0.2 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2017/06/kamailio-v5-0-2-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda

2 3

SUBSCRIBE within
by Annus Fictus 14 Jun '17

14 Jun '17

Hello, I'm using Kamailio in a Multi Domain setting. I have a problem with SUBSCRIBE within a Dialog With the first subscribe no problem: SUBSCRIBE -> 407 Proxy Auth -> SUBSCRIBE -> 200 OK In the 200 OK the Contact header contain the Kamailio IP so when the Softphone send another SUBSCRIBE within the dialog (at the IP present on the contact header) Kamailio answer whit a 404 Not Here because I use these lines: if (is_method("SUBSCRIBE") && is_uri_host_local()) { # in-dialog subscribe requests route(PRESENCE); exit; } So, as the softphone send the new SUBSCRIBE to Kamailio IP and not the Kamailio domain, Kamailio not use this block but: sl_send_reply("404","Not here"); exit; } My question is: Why Kamailio in the Contact Header of 200 OK of SUBSCRIBE use the public IP and not the domain? Regards

2 1

REDIS load problem - Kamailio 5.0.1 - db_redis not found
by Marko Tirs 14 Jun '17

14 Jun '17

Hi all, I'm trying to use the Redis database for authentication and later for accounting. I installed Redis on the server, I compiled Kamailio with ndb_redis and the module exists. When I try to start Kamailio I get following errors: 0(16737) ERROR: <core> [db.c:203]: db_bind_mod(): Module db_redis not found. Missing loadmodule? 0(16737) ERROR: auth_db [auth_db_mod.c:175]: mod_init(): unable to bind to a database driver 0(16737) ERROR: <core> [core/sr_module.c:968]: init_mod(): Error while initializing module auth_db (/usr/local/lib64/kamailio/modules/auth_db.so) ERROR: error while initializing modules Bellow are the relevant parts from config files. Is there any example of kamailio.cfg with Redis configuration and commands for authentication and accounting? Please help me to use Kamailio with Redis. Thank youRegardsMarko kamctlrc --------- DBENGINE=DBTEXT kamailio.cfg ------------- #!define WITH_REDIS #!define WITH_AUTH #!ifdef WITH_REDIS #!define DBURL "redis://localhost:6379/" #!endif #!ifdef WITH_AUTH loadmodule "auth.so" loadmodule "auth_db.so" #!endif #!ifdef WITH_REDIS loadmodule "ndb_redis.so" #!endif # ----- ndb_redis params ----- modparam("ndb_redis", "server", "name=srv1;addr=127.0.0.1;port=6379;db=1") # ----- auth_db params ----- #!ifdef WITH_AUTH modparam("auth_db", "db_url", DBURL) modparam("auth_db", "calculate_ha1", yes) modparam("auth_db", "password_column", "password") modparam("auth_db", "load_credentials", "") modparam("auth_db", "use_domain", MULTIDOMAIN) #!endif | | Virenfrei. www.avast.com |

2 4

Planning Kamailio v5.0.2
by Daniel-Constantin Mierla 14 Jun '17

14 Jun '17

Hello, I am considering to release Kamailio v5.0.2 sometime next week, likely on Wednesday or Thursday, Jun 14 or 15, 2017. Should anyone be aware of issues not listed yet on bug tracker from github.com/kamailio/kamailio, report them there as soon as possible to try to fix. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com

2 2

rtpengine: UDP: bad checksum in dmesg
by Abdoul Osséni 12 Jun '17

12 Jun '17

Hello, Since i installed rtpengine, I have many messages like "UDP: bad checksum". [383818.303391] UDP: bad checksum. From x.x.x.x:7272 to x.x.x.x:45898 ulen 58 [383819.671083] UDP: bad checksum. From x.x.x.x:7272 to x.x.x.x:45898 ulen 58 [383819.943360] UDP: bad checksum. From x.x.x.x:7272 to x.x.x.x:45898 ulen 58 [383821.516016] UDP: bad checksum. From x.x.x.x:7272 to x.x.x.x:45898 ulen 58 [383821.663985] UDP: bad checksum. From x.x.x.x:7272 to x.x.x.x:45898 ulen 58 Do you have any idea where to start investigating? Env: debian : - jessie - kernel : 3.16.0-4-amd64 - rtpengine : 5.3.0.0+0~mr5.3.0.0 - kamailio : 5.0.1 Regards -- Abdoul OSSENI

2 1

Strange issue in registering users in Kamailio
by Mojtaba 12 Jun '17

12 Jun '17

Does any person solve this problem? -- --Mojtaba Esfandiari.S

2 2

caller id display through pstn
by 赵国杰 12 Jun '17

12 Jun '17

Hello all. I have a kamailio server routing request to a pstn gw and I want to change the number displayed on callee side. Say the caller's user name is "test", and it calls the number 18512345678, and I want the incoming all number displayed on callee side to be 13587654321. How can I achieve this? Thanks, Jesse

3 3

user management of kamailio cluster
by zhaoguojie2010＠163.com 12 Jun '17

12 Jun '17

Hi all. I have 10 kamailio servers across the world. Each of them has a public ip which is also their SIP DOMAIN. When a user register on my service, I'd use their username and password to generate 10 sip accounts, one for each kamailio server so that they can register to any of them. So for each user I will have to insert 10 records in the subscriber table. Is there a better way to do this? Cheers Jesse

4 9

Strange issue in registering users in Kamailio
by Mojtaba 11 Jun '17

11 Jun '17

Hello, In now days i have a strange issue in registering users in kamailio. My senario is the following: I setup kamailio with basic configurations and i created 2000 users in mysql(from 10000 to12000). With registration senario with SIPP tool, i have not issue and every things works right,(Notice that we know SIPP uses the same source ip for all registration), But when i use Spirent Abacus 5000(Test solution for voice, VoLTE and IMS), the kamailio just register 1024 users and other users could not register to kamailio. Spirent Abacus 5000 use the different source ip for each registration. I have these error in syslog message: ERROR: sl [../../core/forward.h:201]: msg_send buffer(): udp_send failed one possible reason is the server is bound to localhost I set this parameter in kamailio configurations, but the issue dont solved: open_files_limits:2048 and in linux configuration: ulimit -n 999999 Please let me know how can i fixed it? With Regards. --Mojtaba Esfandiari.S

1 0

Strange issue in registering users in Kamailio
by Mojtaba 11 Jun '17

11 Jun '17

Hello, In now days i have a strange issue in registering users in kamailio. My senario is the following: I setup kamailio with basic configurations and i created 2000 users in mysql(from 10000 to12000). With registration senario with SIPP tool, i have not issue and every things works right,(Notice that we know SIPP uses the same source ip for all registration), But when i use Spirent Abacus 5000(Test solution for voice, VoLTE and IMS), the kamailio just register 1024 users and other users could not register to kamailio. Spirent Abacus 5000 use the different source ip for each registration. I have these error in syslog message: ERROR: sl [../../core/forward.h:201]: msg_send buffer(): udp_send failed one possible reason is the server is bound to localhost I set this parameter in kamailio configurations, but the issue dont solved: open_files_limits:2048 and in linux configuration: ulimit -n 999999 Please let me know how can i fixed it? -- --Mojtaba Esfandiari.S

1 0

Dialog module didn't work
by sgy 11 Jun '17

11 Jun '17

Hi All, I meet an issue: After enable dialog module, dialog module didn't store dialog info into "dialog" table, please refer to following infomation. kamailio.cfg: #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_ALIASDB #!define WITH_USRLOCDB #!define WITH_NAT #!define DBURL "mysql://root:password@localhost/kamailio" loadmodule "jsonrpcs.so" loadmodule "kex.so" loadmodule "corex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "usrloc.so" loadmodule "registrar.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "ctl.so" loadmodule "cfg_rpc.so" loadmodule "acc.so" loadmodule "counters.so" loadmodule "dialog.so" modparam("dialog", "dlg_flag", 4) modparam("dialog", "db_url", DBURL) modparam("dialog", "db_mode", 1) -- Best Regards, Shengy

2 2

Re: [SR-Users] LCR - too few dots/colons
by Juha Heinanen 11 Jun '17

11 Jun '17

Annus Fictus writes: > on ip_addr field the value is a normal IPv4 address like 1.2.3.4 > > The gw_uri_avp befor call next_gws is: > > '1|sip:|0|||253719602||5060||;transport=udp|0' That looks fine and these are just debug messages: > DEBUG: lcr [../../core/resolve.h:258]: str2ip(): str2ip: ERROR: too few > dots in [253719602] > DEBUG: lcr [../../core/resolve.h:355]: str2ip6(): str2ip6: ERROR: too > few colons in [253719602] The code first tries if address field (in this case 253719602) contains an ip 4 or 6 address string and, if not, takes int from the field and places it into addr struct: if (s.len > 0) { if ((ip = str2ip(&s)) != NULL) *addr = *ip; else if ((ip = str2ip6(&s)) != NULL) *addr = *ip; else { str2int(&s, &u); addr->af = AF_INET; addr->len = 4; addr->u.addr32[0] = u; } } else { addr->af = 0; } -- Juha

1 0

Strange issue in registering users in Kamailio
by Mojtaba 11 Jun '17

11 Jun '17

Hello, In now days i have a strange issue in registering users in kamailio. My senario is the following: I setup kamailio with basic configurations and i created 2000 users in mysql(from 10000 to12000). With registration senario with SIPP tool, i have not issue and every things works right,(Notice that we know SIPP uses the same source ip for all registration), But when i use Spirent Abacus 5000(Test solution for voice, VoLTE and IMS), the kamailio just register 1024 users and other users could not register to kamailio. Spirent Abacus 5000 use the different source ip for each registration. I have these error in syslog message: ERROR: sl [../../core/forward.h:201]: msg_send buffer(): udp_send failed one possible reason is the server is bound to localhost I set this parameter in kamailio configurations, but the issue dont solved: open_files_limits:2048 and in linux configuration: ulimit -n 999999 Please let me know how can i fixed it? With Regards. Moj --Mojtaba Esfandiari.S

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