- sr-users - kamailio.org

Kamailio start up fails with strange IO Error on RHEL 7.1
by M S 26 Oct '15

26 Oct '15

Hi, I have been trying to setup Kamailio v4.3.3 rev. e275bc on RHEL 7.1 64bit. It has been very difficult to resolve all dependencies initially due to RHEL's extremely limited repositories and libraries support, but nevertheless I am finally able to successfully compile kamailio with all essential modules on it. However, now kamailio fails to start up and gives this strange error, -- 36(3335) CRITICAL: <core> [io_wait.c:526]: init_io_wait(): could not alloc epoll array 36(3335) CRITICAL: <core> [tcp_main.c:4523]: tcp_main_loop(): exiting... 0(3250) ALERT: <core> [main.c:725]: handle_sigs(): child process 3335 exited normally, status=255 0(3250) INFO: <core> [main.c:743]: handle_sigs(): terminating due to SIGCHLD -- I have never seem this error before nor i can find any info related to it anywhere on internet. So, i doubt it is due to any missing dependency. Any idea what may be the cause of this? Thank you.

2 6

Unable to Update Headers in failure route which were build in request route
by Sunil More 26 Oct '15

26 Oct '15

Hi All, I am trying to have a failover route where if a initial relay fails , i can forward the same request to a second provider. I am using a certain set of headers that help to authenticate over my providers. I am trying to update those headers. However update and removal both fail. The headers are still present. Please help me understand if i am wrong. Here's the code. ..... route(GET_CREDENTIALS); } remove_hf_re("X-*"); append_hf("X-Src-IP: Trusted\r\n", "Call-ID"); append_hf("X-Identity: $hdr(X-Calling-User)\r\n", "Call-ID"); append_hf("X-Auth-ID: $avp(siptrunk_username)\r\n", "Call-ID"); $avp(realm) = $fd; $rd = $avp(siptrunk_domain); $var(duri) = "sip:"+$rU+"@"+$avp(siptrunk_proxy); $du = $var(duri); t_on_failure("UAC_AUTH"); if(!t_relay()) { sl_reply_error(); exit; } } failure_route[UAC_AUTH] { if(t_check_status("(4|5)[0|8][0|2|3|4|6|8]")){ xlog("L_INFO","failover testing"); revert_uri(); route(FAILOVER); } if (t_check_status("40[17]")) { xlog("got challenged \n"); uac_auth(); xlog("L_INFO", "Return code is $retcode"); $rd = $avp(siptrunk_proxy); t_on_failure("UAC_AUTH"); t_relay(); } } route[FAILOVER]{ xlog("L_INFO","doing failover now.. "); if($avp(failover_routing_id)!=$null) { $avp(outbound_routing_id)=$avp(failover_routing_id); xlog("L_INFO","Failover carrier credentials are.."); route(GET_CREDENTIALS); #not adding headers now remove_hf_re("X-*"); append_hf("X-Src-IP: Trusted\r\n", "Call-ID"); append_hf("X-Identity: $hdr(X-Calling-User)\r\n", "Call-ID"); append_hf("X-Auth-ID: $avp(siptrunk_username)\r\n", "Call-ID"); $avp(realm) = $fd; $rd = $avp(siptrunk_proxy); $var(duri) = "sip:"+$rU+"@"+$avp(siptrunk_proxy); $du = $var(duri); xlog("L_INFO","Destination Uri from failover is : $du"); t_on_failure("UAC_AUTH2"); if(!t_relay()) { sl_reply_error(); exit; } exit; } } failure_route[UAC_AUTH2] { if(t_check_status("(4|5)[0|8][0|2|3|4|6|8]")){ xlog("L_INFO","Failover failed. cancelled call "); exit; } if (t_check_status("40[17]")) { xlog("got challenged \n"); uac_auth(); xlog("L_INFO", "Return code is $retcode"); $rd = $avp(siptrunk_proxy); t_relay(); } exit; } Thanking You, Sunil More

3 2

issue with sending "delete" to rtpengine for cancelled branch
by Vasiliy Ganchev 26 Oct '15

26 Oct '15

Hi folk! Have an issue, and do not see the obvious way how to solve it, maybe i'm missing something. The call scenario: UA-A (hard phone, no rtpengine) call ->> UA-B (has 2 registration: hard phone (no rtpengine) and WebRTC based web phone (here the rtpengine is called, in branch_route)) When Kamailio fork call to UA-B, for the branch with WebRTC UA, I do rtpengine_manage (rtpengine receive command "offer" and allocate 4 ports). If UA-B answer via hard phone, Kamailio Cancel branch to WebRTC phone, and here I need to do rtpengine_manage (to send "delete" command to rtpengine). But as I see Kamailio CANCEL all nonanswered branches automatically (I see no place where to call rtpengine_delete) Any suggestion how to cope with such issue? cheers! -- View this message in context: http://sip-router.1086192.n5.nabble.com/issue-with-sending-delete-to-rtpeng… Sent from the Users mailing list archive at Nabble.com.

1 1

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

25 Oct '15

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

3 5

important message
by brettlist＠nemeroff.com 22 Oct '15

22 Oct '15

Hello! New message, please read <http://vivamous.com/youth.php?lkb> brettlist(a)nemeroff.com

2 1

important message
by brettlist＠nemeroff.com 22 Oct '15

22 Oct '15

Hello! New message, please read <http://stillbontechnology.com/smiling.php?h98ha> brettlist(a)nemeroff.com

1 0

important message
by brettlist＠nemeroff.com 22 Oct '15

22 Oct '15

Hello! New message, please read <http://janatyachar.org/woman.php?mq> brettlist(a)nemeroff.com

1 0

important message
by brettlist＠nemeroff.com 22 Oct '15

22 Oct '15

Hello! New message, please read <http://moverdubai.net/having.php?tky> brettlist(a)nemeroff.com

1 0

important message
by brettlist＠nemeroff.com 22 Oct '15

22 Oct '15

Hello! New message, please read <http://lapeste.org/land.php?eiz> brettlist(a)nemeroff.com

1 0

important message
by brettlist＠nemeroff.com 22 Oct '15

22 Oct '15

Hello! New message, please read <http://igoasia.org/wish.php?9w> brettlist(a)nemeroff.com

1 0

msilo dump with non 2xx answer
by Péter Barabás 22 Oct '15

22 Oct '15

Hi, I set instant message store&forward in kamailio using MSILO module. It works fine in many cases. We have special message handing (encryption in "session"), i do not go into detail since it is not necessarily to solve the problem. So there are situations, when the offline receiver should get a MESSAGE and will acknowledge with 4xx status code, like 493: the original message is stored in silo table and when the receiver will be online, it will be dumped and he will send 493. Question: how can I delete the message from silo table with MSILO (since it is not 2xx) and how can i forward this ack message to the original sender instead kamailio? Thanks. Dr. Péter Barabás Director of Software Development Arenim Technologies AB.

3 4

Kamailio and FreeSwitch - ClueCon Weekly Conference Call
by Daniel-Constantin Mierla 21 Oct '15

21 Oct '15

On Wednesday, October 21, 2015, at 17:00GMT (12:00CT, 18:00 London, 19:00 Berlin), the Cluecon weekly conference call will focus on Kamailio and FreeSwitch. I will be joining the call, answering the questions about Kamailio and its options to integrate with FreeSwitch. Expect the FreeSwitch core developers to be around to handle the questions about their project. Participation is open for anyone, you can dial in for audio or video sessions using a SIP phone or webrtc capable browser: - sip:888@conference.freeswitch.org - https://cantina.freeswitch.org/vc More dial in options (e.g., PSTN) are presented at: - https://freeswitch.org/confluence/display/FREESWITCH/ClueCon+Weekly+Confere… Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com

1 1

MSILO module
by Safdar Khan 21 Oct '15

21 Oct '15

How can i store messages in silo table not only offline also online.Demo code will be appreciated.waiting for response.

2 3

htable never
by Juha Heinanen 21 Oct '15

21 Oct '15

i noticed that entries that i had added to htable at sip proxy start in event_route [htable:mod-init], e.g., $sht(htable=>app_srv::sbc::<null>) = "sip:SBC:SEMS_PORT"; had disappeared from htable after some (don't know exactly how long) time. i have not specified any autoexpire for that table: modparam("htable", "htable", "htable=>size=HTABLE_SIZE;dbtable=htable;") after restart of sip proxy they reappeared in htable like this: # sip-proxy_ctl htable.get htable 'app_srv::sbc::<null>' { item: { name: app_srv::sbc::<null> value: sip:127.0.0.1:5090 flags: 2 expire: NEVER } } what could explain the disappearance? -- juha

3 3

Implementation of RFC 5393
by Guillaume 21 Oct '15

21 Oct '15

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

3 4

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

21 Oct '15

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

2 2

Sending ReINVITE from Kamailio
by Grant Bagdasarian 21 Oct '15

21 Oct '15

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

3 4

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

20 Oct '15

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

3 2

Far end NAT traversal
by NITESH BANSAL 20 Oct '15

20 Oct '15

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

3 2

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

20 Oct '15

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

2 3

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

19 Oct '15

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

2 1

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

19 Oct '15

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

2 1

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

19 Oct '15

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

2 1

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

19 Oct '15

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

2 3

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

19 Oct '15

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

3 2

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

19 Oct '15

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

2 1

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

19 Oct '15

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

1 0

call-limit peer
by Angel Elena 19 Oct '15

19 Oct '15

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

2 1

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

19 Oct '15

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

1 0

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

19 Oct '15

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

1 0

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

16 Oct '15

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

1 0

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

16 Oct '15

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

3 13

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

16 Oct '15

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

1 0

routing based on TLS auth
by Max 16 Oct '15

16 Oct '15

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

2 1

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

16 Oct '15

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

1 0

Strange TLS problem
by Pete Kelly 14 Oct '15

14 Oct '15

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

2 2

setflag and hash table variables
by Asgaroth 14 Oct '15

14 Oct '15

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

2 3

debian jessie and dependencies
by nadie 14 Oct '15

14 Oct '15

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

2 4

Kamailio vs RTPEngine Performance
by M S 13 Oct '15

13 Oct '15

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

1 0

Capturing Kamailio retransmissions in routing script
by Olle E. Johansson 13 Oct '15

13 Oct '15

Hi! Is there a simple way to log outbound retransmissions by tm in the routing script? I would like to be able to see retransmissions. /O

2 1

evapi tcp parsing??
by Jayesh Nambiar 13 Oct '15

13 Oct '15

Hello, I'm exploring the evapi module for my kamailio to interface with an external node.js app for third party stuff like AAA, billing engine tasks, notifications and so on. I followed and took some ideas from the rtjson and evapi tutorial found here( http://kb.asipto.com/kamailio:k43-async-sip-routing-nodejs) to build the node.js app consuming events. When I stress tested the scenario using SIPp and tried sending a lot of events at 300-350cps from Kamailio, I noticed that at times the client is receiving 2-3 events in a single message together although I do event_sync_relay once per SIP message received and have netstrings enabled. I believe this is a typical behavior of TCP and needs to be handled by the client using some kind of Netstring handler. Please correct me if I'm wrong. And hence I'd like to know what particularly needs to be taken care of while writing a client that is listening for events on raw tcp socket and how does kamailio handle this situation while receiving messages over TCP socket?? Does kamailio recognize the end of netstring properly on evapi:message-received and give exactly one message to take care of on every "message-received" event or should that be handled in the script somewhere !! I also referred cgrates client over evapi example which is written in GO, but I couldnt find them handling TCP streams clearly either. I'd really appreciate some expert suggestion here to make an informed decision on using the evapi module for a large scale solution. Thanks, - Jayesh

3 26

How to get runtime configuration?
by Magnus Nordström 13 Oct '15

13 Oct '15

Hi, Is there any command to get the runtime configuration from kamailio? I tried "kamctl monitor" but there was not a lot of information. For example I need information about what tcp_conn_wq_max is set to. Best regards, Magnus Nordström

3 2

Re: [SR-Users] Lost 180 Ringing Response
by John Billings 13 Oct '15

13 Oct '15

> Hello, > > look at: > > http://kamailio.org/docs/modules/stable/modules/tm.html#tm.p.cancel_b_method > > Maybe one or another value for that parameter is suiting better your use > case. Thank you for the suggestion. This looked promising, but the cancel_b_method parameter is already at the default value of one. I also tried changing the value to two and got a similar result. This may sound crazy, but it almost seems like the problem happens only when kamailio is processing unrelated INVITES at the same time.

2 1

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

13 Oct '15

2 1

Persistence of enable/disable for uacreg
by DanB 13 Oct '15

13 Oct '15

Hey Guys, I was wondering how does enable/disable flag for uac registration gets persistence, since I could not spot it in the mysql tables. Is that just temporary in-memory and on next restart/refresh does not longer take effect? Thanks, DanB

2 2

rfc: event route when kamailio starts
by Daniel-Constantin Mierla 12 Oct '15

12 Oct '15

Hello, based on a recent discussion with Alex Balashov (at Kazoocon this week), I pushed a patch that enables the execution of event_route[core:worker-one-init] when kamailio is started. It would be more like an alternative for event_route[htable:mod-init], for the cases when htable is not used, but also should ensure that all the modules are initialized. Moreover, because most of the modules close connection in mod init, I though of doing it when child one (udp receiver) initialization for all modules is finished, which means that all is ready for runtime, still this is before receiving any packet. On the other hand, forking is done by main process, so other children can start listening for sip. More or less what I want to ask here is whether the forking of the other children should wait until the event_route[core:worker-one-init] is finished (e.g., what is done in this event route is important before any sip packet is routed) or just leave it like it is. Worth to say that some modules do special processing in child init of worker one, like usrloc module loads the records from database to memory, which means that overall start of kamailio could be slower. Also, if there are time consuming actions in the event_route[core:worker-one-init], getting to the stage of routing sip packets will take longer. What would you find important, fork the other processes so routing sip will happen as soon as possible, or block until execution ofevent_route[core:worker-one-init] is finished. I guess that making it cusomizable in some way would be a solution, but knowing what use cases would be important may help in reducing the complexity to get it enabled. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com

3 2

Dialog keep alive options are with error parsing headers
by José Seabra 12 Oct '15

12 Oct '15

Hello there, I'm using dialog module to send keep alive options to callee and caller in order to detect if dialog still up, but when kamailio generates the OPTION and parse it, gives the following errors: [root@c4-compute02-srv1 kamailio]# 37(1587) DEBUG: dialog [dlg_hash.c:614]: dlg_lookup(): ref dlg 0x7f89134c1d40 with 1 -> 3 37(1587) DEBUG: dialog [dlg_hash.c:616]: dlg_lookup(): dialog id=2210 found on entry 2350 37(1587) DEBUG: dialog [dlg_req_within.c:427]: dlg_send_ka(): sending OPTIONS to caller 37(1587) DEBUG: tm [uac.c:249]: t_uac_prepare(): DEBUG:tm:t_uac: next_hop=< sip:unknown@62.28.197.25:5060> 37(1587) DEBUG: <core> [dns_cache.c:3293]: dns_srv_sip_resolve(): (62.28.197.25, 0, 0), ip, ret=0 37(1587) DEBUG: tm [uac.c:150]: dlg2hash(): DEBUG: dlg2hash: 14692 37(1587) DEBUG: <core> [parser/msg_parser.c:606]: parse_msg(): SIP Request: 37(1587) DEBUG: <core> [parser/msg_parser.c:608]: parse_msg(): method: <OPTIONS> 37(1587) DEBUG: <core> [parser/msg_parser.c:610]: parse_msg(): uri: < sip:unknown@62.28.197.25:5060> 37(1587) DEBUG: <core> [parser/msg_parser.c:612]: parse_msg(): version: <SIP/2.0> 37(1587) DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK4693.2af96e95000000000000000000000000.0>; state=16 37(1587) DEBUG: <core> [parser/parse_via.c:2642]: parse_via(): end of header reached, state=5 37(1587) DEBUG: <core> [parser/msg_parser.c:496]: parse_headers(): parse_headers: Via found, flags=2 37(1587) DEBUG: <core> [parser/msg_parser.c:498]: parse_headers(): parse_headers: this is the first via 37(1587) DEBUG: <core> [parser/parse_addr_spec.c:172]: parse_to_param(): DEBUG: add_param: tag=90d40279ee5745d8851aa989e6fadfc2 37(1587) DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=29 37(1587) DEBUG: <core> [parser/msg_parser.c:173]: get_hdr_field(): DEBUG: get_hdr_field: <To> [64]; uri=[sip:unknown@62.28.197.6] 37(1587) DEBUG: <core> [parser/msg_parser.c:175]: get_hdr_field(): DEBUG: to body [<sip:unknown@62.28.197.6>] 37(1587) DEBUG: <core> [parser/msg_parser.c:153]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <0> <OPTIONS> 37(1587) DEBUG: <core> [parser/msg_parser.c:187]: get_hdr_field(): DEBUG: get_hdr_body : content_length=0 *37(1587) ERROR: <core> [parser/msg_parser.c:96]: get_hdr_field(): ERROR: get_hdr_field: bad header* 37(1587) DEBUG: <core> [parser/msg_parser.c:280]: get_hdr_field(): get_hdr_field: error exit *37(1587) INFO: <core> [parser/msg_parser.c:338]: parse_headers(): ERROR: bad header field [VC* *]* 37(1587) DEBUG: topoh [topoh_mod.c:232]: th_prepare_msg(): parsing headers failed37(1587) DEBUG: <core> [parser/msg_parser.c:606]: parse_msg(): SIP Request: 37(1587) DEBUG: <core> [parser/msg_parser.c:608]: parse_msg(): method: <OPTIONS> 37(1587) DEBUG: <core> [parser/msg_parser.c:610]: parse_msg(): uri: < sip:unknown@62.28.197.25:5060> 37(1587) DEBUG: <core> [parser/msg_parser.c:612]: parse_msg(): version: <SIP/2.0> 37(1587) DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK4693.2af96e95000000000000000000000000.0>; state=16 37(1587) DEBUG: <core> [parser/parse_via.c:2642]: parse_via(): end of header reached, state=5 37(1587) DEBUG: <core> [parser/msg_parser.c:496]: parse_headers(): parse_headers: Via found, flags=2 37(1587) DEBUG: <core> [parser/msg_parser.c:498]: parse_headers(): parse_headers: this is the first via 37(1587) DEBUG: <core> [parser/parse_addr_spec.c:172]: parse_to_param(): DEBUG: add_param: tag=90d40279ee5745d8851aa989e6fadfc2 37(1587) DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=29 37(1587) DEBUG: <core> [parser/msg_parser.c:173]: get_hdr_field(): DEBUG: get_hdr_field: <To> [64]; uri=[sip:unknown@62.28.197.6] 37(1587) DEBUG: <core> [parser/msg_parser.c:175]: get_hdr_field(): DEBUG: to body [<sip:unknown@62.28.197.6>] 37(1587) DEBUG: <core> [parser/msg_parser.c:153]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <0> <OPTIONS> 37(1587) DEBUG: <core> [parser/parse_addr_spec.c:172]: parse_to_param(): DEBUG: add_param: tag=e34d43e164ad4b7392dc9c6e1058a983 37(1587) DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=29 37(1587) DEBUG: dialog [dlg_cseq.c:215]: dlg_cseq_msg_sent(): traking cseq updates 37(1587) DEBUG: dialog [dlg_hash.c:671]: internal_get_dlg(): ref dlg 0x7f89134c1d40 with 1 -> 4 37(1587) DEBUG: dialog [dlg_hash.c:674]: internal_get_dlg(): dialog callid='13208317017c42128fbf00e1685ee1b3' found on entry 2350, dir=2 37(1587) DEBUG: dialog [dlg_cseq.c:233]: dlg_cseq_msg_sent(): request not going downstream (2) 37(1587) DEBUG: dialog [dlg_hash.c:846]: dlg_unref(): unref dlg 0x7f89134c1d40 with 1 -> 3 37(1587) DEBUG: dialog [dlg_req_within.c:452]: dlg_send_ka(): keep-alive sent to caller 37(1587) DEBUG: dialog [dlg_req_within.c:427]: dlg_send_ka(): sending OPTIONS to callee I'm using the following dialog configuration: modparam("dialog","db_url", DBURL) modparam("dialog","db_mode", 0) modparam("dialog","enable_stats", 1) modparam("dialog","dlg_flag", DLG_FLAG) modparam("dialog","profiles_with_value","concurrentcalls") modparam("dialog", "detect_spirals", 1) modparam("dialog","dlg_match_mode", 2) modparam("dialog", "initial_cbs_inscript", 0) modparam("dialog", "default_timeout", 3600) modparam("dialog", "send_bye", 1) modparam("dialog", "timeout_avp", "$avp(s:timeout_dlg)") modparam("dialog", "track_cseq_updates", 1) modparam("dialog", "ka_timer", 10) modparam("dialog", "ka_interval", 30) I'm also using topoh module. Anyone can help me to identify if I'm doing the proper configuration? Thank you for your support Best Regards José Seabra

3 9

Startup Route in Kamailio
by Sunil More 12 Oct '15

12 Oct '15

Hi All, I am new to Kamailio world. I am trying to initialize some details at Kamailio startup, this requires some database queries from a few tables. I have read about the htable event, however sql queries are not working in this route. I have come upon following errors. Please suggest a solution for this. Route used: event_route[htable:mod-init] { xlog("L_INFO", "********Initailising the startup route ******\n"); sql_xquery("cb","SELECT id, media_server_port, name FROM domains","ra"); } error : Oct 8 13:28:32 P172 /usr/local/kamailio/sbin/kamailio[28735]: INFO: <script>: ********Initailising the startup route ****** Oct 8 13:28:32 P172 kamailio: ERROR: <core> [daemonize.c:303]: daemonize(): Main process exited before writing to pipe Thanking You, Sunil More Ph : 9503338275

2 1

Familiar topic about Kamailio with Asterisk behind NAT
by Dirk Teurlings - SIGNET B.V. 09 Oct '15

09 Oct '15

Hi, I found some existing topics on this but failed to get a solutions out of them. We're running into some issues with client devices connecting to our private addresses. The way it is setup now: CLIENTS <-> (NAT) <-> INTERNET <-> KAMAILIO(4.2.5) with RTPPROXY(v1) <-> PRIVATE LAN <-> ASTERISK (v1.8) Our Kamaialio and Asterisk are in a private address range, but Kamailio also has a public interface. Most of the clients (about 95%) work well with this setup, but a couple don't. We have one case now where the CLIENT tries to connect to the private address of ASTERISK. And of course, that doesn't work. I'm kind of stuck as to where I need to fix this. I tried using the externaddr option in Asterisk to solve it on that end. But that didn't help anything. The NAT options in Kamailio are not really suited for this, as they tend to fix client NAT problems. Any pointer or help would be greatly appriciated. Cheers, Dirk

8 16

[pua] Question to DB Mode 0
by Maciej Marczyński 09 Oct '15

09 Oct '15

Hi Guys, I have a question regarding pua module parameter 'db mode'. I run Kamailio (4.3.2) with sqlite and I tried to set the parameter to 0 but even then I received: > ERROR: db_sqlite [dbase.c:489]: db_sqlite_commit(): sqlite commit failed: NOT NULL constraint failed: pua.call_id > ERROR: db_sqlite [dbase.c:138]: db_sqlite_cleanup_query(): finalize failed: NOT NULL constraint failed: pua.call_id > ERROR: pua [pua.c:1179]: db_update(): while inserting in db table pua > > As far as I checked the documentation, it says that '0' means: > high speed memory based storage Does it still writes to DB anyway (on timer or whatever?) or just keep it in memory? Is there any way to disable writing to DB? The second thing is the reason of the ERRORs above. Why does pua think that my call_id is null? If you need any more information please let me know. Best regards and have a good weekend, Maciej

3 7

Siremis debug window
by Infinicalls Infinicalls 08 Oct '15

08 Oct '15

Hi, I have installed Siremis and modified it for public user registration. I have added a new user. When I try to log in it opens up a new (debug) window and prints "1". It doesn't allow me to log in. But I can log in as admin;admin. And siremis/user/register doesn't load properly. It redirects to the login page again. Kindly let me know how do I solve this. regards Ganesh Kumar

2 8

MySQL Connect Errors
by John Billings 08 Oct '15

08 Oct '15

We are using kamailio 4.2.0 with auth_db enabled and connected to a MySQL server. Occasionally, in the middle of the night when there is no activity we get the following errors out of the blue (the last three lines are repeated indefinitely). According to the MySQL site <http://dev.mysql.com/doc/refman/5.0/en/error-lost-connection.html>, this can be caused by a connect timeout that is too short (We verified that Aborted_connects is steadily rising). The kamailio server is right next to the database server so there is no network latency. We increased the db_mysql timeout_interval parameter, but we still see MySQL’s Aborted_connects counter incrementing. So it’s like kamailio is still timing out on connection attempts. Ideas? Thanks. Oct 1 02:34:49 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Oct 1 02:34:49 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: auth_db [authorize.c:175]: get_ha1(): failed to query database Oct 1 02:34:55 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'reading authorization packet', system error: 11 Oct 1 02:34:55 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Oct 1 02:34:55 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: auth_db [authorize.c:175]: get_ha1(): failed to query database Oct 1 02:35:01 sip-proxy1 /usr/sbin/kamailio[9264]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'reading authorization packet', system error: 11 Oct 1 02:35:01 sip-proxy1 /usr/sbin/kamailio[9264]: ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Oct 1 02:35:01 sip-proxy1 /usr/sbin/kamailio[9264]: ERROR: auth_db [authorize.c:175]: get_ha1(): failed to query database Oct 1 02:35:01 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'reading authorization packet', system error: 11 Oct 1 02:35:01 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Oct 1 02:35:01 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: auth_db [authorize.c:175]: get_ha1(): failed to query database Oct 1 02:35:07 sip-proxy1 /usr/sbin/kamailio[9264]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'reading authorization packet', system error: 11 Oct 1 02:35:07 sip-proxy1 /usr/sbin/kamailio[9264]: ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Oct 1 02:35:07 sip-proxy1 /usr/sbin/kamailio[9264]: ERROR: auth_db [authorize.c:175]: get_ha1(): failed to query database Oct 1 02:35:07 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'reading authorization packet', system error: 11 Oct 1 02:35:07 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Oct 1 02:35:07 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: auth_db [authorize.c:175]: get_ha1(): failed to query database Oct 1 02:35:11 sip-proxy1 /usr/sbin/kamailio[9264]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Host ‘X.X.X.X' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts' Oct 1 02:35:11 sip-proxy1 /usr/sbin/kamailio[9264]: ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Oct 1 02:35:11 sip-proxy1 /usr/sbin/kamailio[9264]: ERROR: auth_db [authorize.c:175]: get_ha1(): failed to query database Oct 1 02:35:11 sip-proxy1 /usr/sbin/kamailio[9264]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Host 'X.X.X.X' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts' ...

2 1

TM not ending transactions
by Daniel Tryba 08 Oct '15

08 Oct '15

Running 4.3.x (both .1 and .2) I have seen it happening twice sofar that dialogs (the module) will not end, resulting in to calls failing due to call limits based on active dialogs. Accounting logged a BYE for all these calls. kamcmd tm.stats shows an increasing number of current/waiting transactions (as grphed in attachment). Has anyone seen this problem?

3 7

Questions about LCR
by Scott C. Fertig 08 Oct '15

08 Oct '15

Hello, Sorry to bother and if I sound like a newb thats because I am kind of new (but im trying =) ) I am having some issues getting started using LCR and was wondering if anyone could point me in the right direction and/or let me know what I am doing wrong. I began setting up the other day using kamailio (4.4.0-dev5) from git (maybe I picked the wrong version?) and am struggling to get lcr to work properly. So far I have been able to get the module to load, added the route to the config and have added some LCR values. Inbound calling is working perfectly to a registered device which is great so far. This is my config for the LCR: http://pastebin.com/LUF0Pgr1 I have the following values in my database for LCR: http://pastebin.com/bDpQug0J I was not sure if dumping all the text in the email would be appropriate if needed please let me know to resend with the configs in the email. Whats strange to me is that even with the xlog I do not get any messages to syslog at all, I have defined WITH_DEBUG, debug level at 3, and log facility set to LOG_LOCAL0 (Sorry if I'm bringing up multiple issues) Anyways back on point, I'm wondering if this is related to the avp's listed, I am not sure what the avps referenced are supposed to represent, when I try to dump all the avps I get a empty list, and it is querying the usr_preference table for these. Is there something I need to add within this table, or is there perhaps something wrong with my configuration? [root@localhost kamailio]# kamctl avp list database engine 'MYSQL' loaded Control engine 'FIFO' loaded Query: SELECT uuid,username,domain,attribute,type,value FROM usr_preferences ; Dumping AVPs Thank you!

2 2

Lost 180 Ringing Response
by John Billings 07 Oct '15

07 Oct '15

Hi Everyone, We are using Kamailio 4.2.0 with TLS. It’s setup so multiple phones can register to the same account and they all ring together. It always works great unless one of the phones is on a slower Internet connection. Occasionally that phone will start ringing after another phone has already picked up the call. The problem is that the INVITE to the slow phone is not followed by a CANCEL. So the phone keeps on ringing for a long time. When there is no problem, the logs on the phone show: Receive: INVITE Send: 180 Ringing Received: CANCEL Send: 200 Ok When the phone keeps ringing: Delay: up to several seconds Receive: INVITE Send: 180 Ringing The problem never seems to happen if I wait until all of the phones have received the INVITE. So is the late 180 response not getting handled by the right session? Any ideas on how to track this down?

2 1

Re: [SR-Users] uac_req_send and reply timeout
by Paweł Sternal 07 Oct '15

07 Oct '15

On 07.10.2015 16:41, Daniel-Constantin Mierla wrote: > Hello, > > in the event route for uac_req_send() is practically during handling the > reply for what was sent before. Also, the uac_req_send() sends something > out of the processed sip message, so typically functions won't work > because they will be applied to the processed sip message. > > Maybe try setting the avp with the timeout value (see tm parameters), > might work, I haven't checked -- report the results, would be good to know. Unfortunately solution with fr_timer_avp also doesn't work. Only set globally fr_timer works. Well... there is always a solution. Thanks anyway. > Cheers, > Daniel Regards, Paweł

2 1

uac_req_send and reply timeout
by Paweł Sternal 07 Oct '15

07 Oct '15

Hi, It is posibility to set timeout for uac_req_send with setting "evroute" to 1. Yes, I found a solution without this set when using event_route[tm:local-request] [1] but with "evroute" option this don't work ofcorse. regards Pawel [1] http://lists.sip-router.org/pipermail/sr-users/2011-October/070695.html

2 1

SIREMIS Help
by Vojimir Raovic 07 Oct '15

07 Oct '15

Hi, Just wanted to see how to get SIREMIS user manaual? Regards, Voyimir [image: me]*Vojimir Raovic*, Principal Engineer & Co-founder *Office:* +61 8 9200 3500 | *Web:* www.norwoodsystems.com | *Twitter: * @norwoodsystems <http://twitter.com/norwoodsystems> *Direct:* +61 8 9200 3503 | *Mobile:* +61 450 019 775 [image: me][image: me] [image: me] NOTICE: If you are not an authorised recipient of this e-mail, please contact Norwood Systems immediately by return e-mail or by telephone on +61 8 9200 3500. In this case, you should not read, print, re-transmit, store or act in reliance on this e-mail or any attachments, and should destroy all copies of them. This e-mail and any attachments are confidential and may contain legally privileged information and/or copyright material of Norwood Systems or third parties. You should only re-transmit, distribute or commercialise the material if you are authorised to do so. Any legal privilege attaching to the contents of this e-mail or any attachments is expressly reserved and is not waived by any transmission to an unauthorised recipient. This notice should not be removed. *Please consider the environment before printing this e-mail.*

2 1

Recall: Kamailio B2BUA or Dual router ?
by Mark Henriksen 07 Oct '15

07 Oct '15

Mark Henriksen would like to recall the message, "[SR-Users] Kamailio B2BUA or Dual router ?".

1 0

Kamailio B2BUA or Dual router ?
by Mark Henriksen 07 Oct '15

07 Oct '15

Hello All I have been looking for answers and trying really hard to figure out if I can use Kamailio as a Dual Router (Inbound and Outbound using 2 IPs on 1 Eth "Amazon AWS") I can not seem to find information is this is possible using Kamailio or if am just plain "stupid" and can not read the Wiki well enough J Hope you can help //Mark

2 2

Kamailio as a LB with Asterisk and consul
by Sylvain Boily 06 Oct '15

06 Oct '15

Hello, I did a new small project with Asterisk to register it on consul (http://consul.io) to use a discovery service tools. The project is here : https://github.com/sboily/asterisk-consul-module This last day, i'm working to use kamailio as a loadbalancer for Asterisk and autoscale it. You can find example on my docker-compose.yml, contribs directory and README. It's not perfect, because i'm clearly not a kamailio expert, but it works. So, i'm looking about feeling to this dev, and i would expect some help from kamailio community to configure kamailio as a LB better ;) I will be at astricon, so if people want to share with me about this project, contact me. Have a good day Sylvain

2 2

creating debian package from source
by Thibault Gueslin 06 Oct '15

06 Oct '15

I have difficulties to install the debian package of kamailio I have build from source Creation works fine. (make cfg, configuration of proper debian in pkg/debian/deb , make deb) But kamailio tries to find module here : /usr/lib/x86_64-linux-gnu/kamailio/modules/ and modules are installed in /usr/lib64/ Of course, it works fine by specifying -L with actual path. I have tried also to download the source of debian package with same result. I have missed some steps. Thibault

1 0

Http authentification with JSON-RPC command
by Loïc Boissy 06 Oct '15

06 Oct '15

Hello, I would like to authorize JSON-RPC commands for a specific user. Is it possible to enable HTTP authentification on the xHTTP module? Thanks for your help. Best regards Loic BOISSY

3 3

Re: [SR-Users] diameter auth with round trip
by JB 06 Oct '15

06 Oct '15

Thanks for the suggestion about auth_diameter, do you think there would be an interest in the community if we were to do this modification on ims_auth or auth_diameter ? could it be integrated to trunk ? We do not want to publish our own fork of ims_auth or auth_diameter with that small change and maintain the code repository if it can be avoided, so it would be nice if we can put it in the trunk and forget about it. Plus it is more open source oriented to publish to main branch i feel :) JB 2015-10-03 23:53 GMT+02:00 JB <jbf.nospam(a)gmail.com>: > Hello all, we are working on a SIP solution using Kamailio. > > We want to secure our base of user credentials even in case of attack on > the SIP server, and for that reason we plan to use diameter authentication > as described in RFC http://www.rfc-base.org/txt/rfc-4740.txt > > Paragraph 6.2 describes a mode where the HSS answer with code > > DIAMETER_MULTI_ROUND_AUTH ,and then validate user credential after a second round trip. > > > This does NOT corresponds to what is done on Kamailio module ims_auth, where credentials (actually a hash of the credentials, but its enough to authenticate ) > > ) are pushed to kamailio, which does the computation of the expected answer (which corresponds to par 6.3 of the RFC 4740) > > Is there any kamailio module that would allow to use the method with DIAMETER_MULTI_ROUND_AUTH ? > > Thank you > > JB > >

2 1

diameter auth with round trip
by JB 06 Oct '15

06 Oct '15

Hello all, we are working on a SIP solution using Kamailio. We want to secure our base of user credentials even in case of attack on the SIP server, and for that reason we plan to use diameter authentication as described in RFC http://www.rfc-base.org/txt/rfc-4740.txt Paragraph 6.2 describes a mode where the HSS answer with code DIAMETER_MULTI_ROUND_AUTH ,and then validate user credential after a second round trip. This does NOT corresponds to what is done on Kamailio module ims_auth, where credentials (actually a hash of the credentials, but its enough to authenticate ) ) are pushed to kamailio, which does the computation of the expected answer (which corresponds to par 6.3 of the RFC 4740) Is there any kamailio module that would allow to use the method with DIAMETER_MULTI_ROUND_AUTH ? Thank you JB

2 1

Prepend values to PSTN gateway?
by Infinicalls Infinicalls 05 Oct '15

05 Oct '15

Hi, I am able to successfully connect to a PSTN gw from Kamailio. Now, he says I need to prepend a value (eg.123123) before the number(ENUM) and then only terminate the calls. Where do I add this? Can somebody help me? thanks Ganesh Kumar

3 3

Interoperability issues between browsers and mobile phones to place a call.
by Safdar Khan 05 Oct '15

05 Oct '15

Hi Daniel sir I have enabled web-sockets module into my kamailio sip server.I am trying to make call from web browsers and mobile phones. To make a call from web browser i am using sipml5 and as a mobile app i am using imsdroid. However i have done some search on net and i found nothing relevant. Any suggestions and help?.Waiting your response eagerly. Thank you

2 3

defaults missing from tcp ops module readme
by Juha Heinanen 05 Oct '15

05 Oct '15

after seeing some commits on tcpops module, i decided to check its readme and noticed that nothing is mentioned about the default values of parameters. it might be useful to tell that, e.g., if tcp_keepalive_enable is not set, then tcp_keepalive core parameter value tells what the status is. -- juha

2 2

problem with dispatcher load balancing
by Ding Ma 05 Oct '15

05 Oct '15

I'm trying to set up kamailio dispatcher to distribute calls to 2 asterisk servers. So far, the failover case seems ok, but I cannot get the dispatcher to distribute load. All calls are going to the last destination entry in the dispatcher table even if I have set the maxload attributes. I'm using algorithm 10 for load distribution. The number of calls sent to one asterisk is well above the maxload. Hope someone more experienced in dispatcher can review my config and give me some recommendations. Thanks in advance. Here is the content of dispatcher table in postgresql db. select * from dispatcher; id | setid | destination | flags | priority | attrs | description ----+-------+--------------------+-------+----------+---------------------------+------------- 1 | 1 | sip:10.0.1.31:5061 | 0 | 0 | duid=asterisk1;maxload=25 | Asterisk1 2 | 1 | sip:10.0.1.33:5061 | 0 | 0 | duid=asterisk2;maxload=25 | Asterisk2 (2 rows) Here are the dispatcher sections in kamailio.cfg. # ----- dispatcher params ----- #!ifdef WITH_DISPATCHER modparam("dispatcher", "db_url", DBASTURL) modparam("dispatcher", "table_name", "dispatcher") modparam("dispatcher", "force_dst", 1). # If flag 2 is set, then failover support is enabled. modparam("dispatcher", "flags", 3) # the last address in destination set is used as a final option to send the request to modparam("dispatcher", "use_default", 1) # load balancing fail over modparam("dispatcher", "dst_avp", "$avp(dsdst)") modparam("dispatcher", "grp_avp", "$avp(dsgrp)") modparam("dispatcher", "cnt_avp", "$avp(dscnt)") modparam("dispatcher", "dstid_avp", "$avp(dsdstid)") modparam("dispatcher", "attrs_avp", "$avp(dsattrs)") # PVs for hashing modparam("dispatcher", "hash_pvar", "$fU@$ci") # PVs to store results when calling ds_is_from_list modparam("dispatcher", "setid_pvname", "$var(setid)") modparam("dispatcher", "attrs_pvname", "$var(attrs)") # method to probe the gateways modparam("dispatcher", "ds_ping_method", "OPTIONS") modparam("dispatcher", "ds_ping_from", "sip:dispatcher@localhost") modparam("dispatcher", "ds_ping_interval", 30) modparam("dispatcher", "ds_probing_threshhold", 10) modparam("dispatcher", "ds_ping_reply_codes", "class=2;code=403;code=404;code=484;code=488;class=3") modparam("dispatcher", "ds_probing_mode", 1) # size of hash table storing data for call load dispatching, power of two modparam("dispatcher", "ds_hash_size", 10) # expiration time in seconds to remove the load on a destination if no BYE was received modparam("dispatcher", "ds_hash_expire", 3600) # expiration time in seconds to remove the load on a destination if no 200 OK for INVITE was received # and state updated with ds_load_update modparam("dispatcher", "ds_hash_initexpire", 60) modparam("dispatcher", "ds_hash_check_interval", 30) #!endif route[WITHINDLG] { if (has_totag()) { # sequential request withing a dialog should # take the path determined by record-routing #!ifdef WITH_DISPATCHER if(is_method("BYE|CANCEL") && ds_is_from_list("1", "3")) ds_load_update(); #!endif ...... } } route[FROMASTERISK] { #!ifdef WITH_DISPATCHER if(ds_is_from_list("1", "3")) { xlog("L_DBG","$rm from $fU@$si:$sp: Call from Asterisk cluster\n"); return 1; } return -1; #!else if ($si==$sel(cfg_get.asterisk.bindip)) { return 1; } return -1; #!endif } onreply_route[MANAGE_REPLY] { xdbg("incoming reply\n"); #!ifdef WITH_DISPATCHER if(is_method("INVITE") && ds_is_from_list("1", "3")) { if(status=~"2[0-9][0-9]") { ds_load_update(); } else if(status=~"[3-7][0-9][0-9]") { ds_load_unset(); } } #!endif if(status=~"[12][0-9][0-9]") route(NATMANAGE); } #!ifdef WITH_DISPATCHER failure_route[RTF_DISPATCH] { if (t_is_canceled()) { exit; } # next DST - only for 500 or local timeout if (t_check_status("500") or (t_branch_timeout() and !t_branch_replied())) { # mark the destination Inactive and Probing ds_mark_dst("IP"); # select the new destination if(ds_next_dst()) { t_on_failure("RTF_DISPATCH"); route(RELAY); exit; } else { # last available node failed to reply, no other destinations available send_reply("404", "No destination"); exit; } } } #!endif route[TOASTERISK] { #!ifdef WITH_DISPATCHER # ds_mark_dst("IP"); # Call load distribution if(!ds_select_dst("1", "10")) { sl_send_reply("500", "Service Unavailable"); xlog("L_INFO","$rm from $fU@$si:$sp: No destinations available for $rd\n"); exit; } xlog("L_DBG", "--- SCRIPT: going to <$ru> via <$du>\n"); t_on_failure("RTF_DISPATCH"); #!else $du = "sip:" + $sel(cfg_get.asterisk.bindip) + ":" + $sel(cfg_get.asterisk.bindport); #!endif route(RELAY); exit; } # Dispatcher detects a destination goes down event_route[dispatcher:dst-down] { xlog("L_ERR", "Destination down: $rm $ru ($du)\n"); } # Dispatcher detects a destination comes up event_route[dispatcher:dst-up] { xlog("L_ERR", "Destination up: $rm $ru\n"); }

2 10

Changed the bindport of Kamailio but still listening to older port
by amjad ali 04 Oct '15

04 Oct '15

Hi, I am scratching my head for one month to get this sorted and I have spent so many hours but couldn't figure out. Please help ! I have changed the bind port to 5099 but it is still listening to the previous port even I have rebooted the system. My Code is : kamailio.bindip = "192.168.1.105" desc "Kamailio IP Address"kamailio.bindport = "5099" desc "kamailio port" However, when I restart kamailio service it shows that it is still listening to 5060 (attached the screen shot) Regards,Amjad

2 1

Kamailio is not forwarding the call to asterisk
by amjad ali 04 Oct '15

04 Oct '15

Hi, I have kamailio and asterisk running on same machine. When I make an internal call, it routes the call to other extension. However, if I stop the asterisk service then the call still routes the same way to other extension. Is there a chance that kamailio does the call routing it self. Also, I cannot see any sip extension registered at asterisk when I run a command "Sip show peers" neither there is any activity in Asterisk's log. Regards,Amjad

2 1

Inconsistent string interpolation
by Sven Neuhaus 02 Oct '15

02 Oct '15

Hello, I'm occasionally running into issues with inconsistent string interpolation in the kamailio.cfg. Here's the latest example. Take this line: $var(x) = "sip:+$var(abc)-$var(def)-$si@$Ri:$Rp"; Here, the values of the variables will NOT be interpolated into the string. Instead, I have to use this: $var(x) = "sip:+" + $var(abc) + "-" + $var(def) + "-" + $si + "@" + $Ri + ":" + $Rp; However, when I have an instruction such as: append_hf("P-Asserted-Identity: $var(x)\r\n"); Then string interpolation takes place (i.e. the value of $var(x) is put into the string. This is very confusing and error prone. Is it something that can be fixed? The behaviour should be consistent. -Sven

2 6

Kamailio v4.3.3 Released
by Daniel-Constantin Mierla 02 Oct '15

02 Oct '15

Hello, Kamailio SIP Server v4.3.3 stable release is out. This is a maintenance release of the latest stable branch, 4.3, that includes fixes since release of v4.3.2. There is no change to database schema or configuration language structure that you have to do on previous installations of v4.3.x. Deployments running previous v4.x.x versions are strongly recommended to be upgraded to v4.3.3. For more details about version 4.3.3 (including links and guidelines to download the tarball or from GIT repository), visit: * http://www.kamailio.org/w/2015/10/kamailio-v4-3-3-released/ RPM, Debian/Ubuntu packages will be available soon as well. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

[ims_auth] compute authenticate field in diameter server, not kamailio
by JB 02 Oct '15

02 Oct '15

Hello all, we are working on a SIP solution using Kamailio. We want to secure our base of user credentials even in case of attack on the SIP server, and for that reason we plan to use diameter authentication as described in RFC http://www.rfc-base.org/txt/rfc-4740.txt Paragraph 6.2 describes a mode where the HSS answer with code DIAMETER_MULTI_ROUND_AUTH ,and then validate user credential after a second round trip. This does NOT corresponds to what is done on Kamailio ims_auth, where credentials (actually a hash of the credentials, but its enough to authenticate ) ) are pushed to kamailio, which does the computation of the expected answer (which corresponds to par 6.3 of the RFC 4740) Is there any kamailio module that would allow to use the method with DIAMETER_MULTI_ROUND_AUTH ? Thank you JB

1 0

reSIProcate v1.10.0 released
by Daniel Pocock 02 Oct '15

02 Oct '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 The v1.10.0 release has been tagged and made available for download: https://www.resiprocate.org/files/pub/reSIProcate/releases/ and a direct link to the ChangeLog: https://github.com/resiprocate/resiprocate/blob/resiprocate-1.10/ChangeLog Debian, Fedora and Ubuntu packages are in the process of being updated. It is about 20 months since 1.9.0 and there have been many improvements. Highlights of the v1.10.0 release: - - repro SIP proxy now includes: - full presence server - PostgreSQL support - Include directive in the config file - - enhancements to the stack and proxy include: - WebSocket authentication may now use URL parameters instead of cookies, client certs or DIGEST - better Syslog support - TLS improvements (PFS, private key passphrases) - better assertion handling (resip_assert) - WSAPoll for Windows, allowing thousands of TCP connections - removing transports at runtime - added netns (Linux network namespace) support The RTC Quickstart Guide provides an overview of how to get started using repro, Kamailio and other popular SIP, XMPP and TURN products http://rtcquickstart.org Contributors to v1.10.0 include Alan Hawrylyshen, Alexander G. Pronchenkov, Byron Campen, Daniel Pocock, Daniel Tacalau, Dan Petrie, Dario Bozzali, Fedor Brunner, Gregor Jasny, Kevin Green, Reiner Herrmann, Robert Sparks, Scott Godin, Thomas Thorne, Vasil Kolev and Wolfgang Rosenauer. Please also see the hall of fame in Github: https://github.com/resiprocate/resiprocate/graphs/contributors which emphasizes the enormous and sustained contribution Scott Godin has made to this project and this release in particular. We are also very grateful to all those who contributed feedback through the mailing list, testing the beta packages in Debian and all past contributors to previous releases of the reSIProcate project. reSIProcate point releases are now announced on the low-volume resiprocate-announce mailing list, please subscribe if you would like to know when 1.10.1 comes along: http://list.resiprocate.org/mailman/listinfo/resiprocate-announce SHA256 checksums for the files: resiprocate-1.10.0.tar.gz c089686e183b8a739064731fa9e5002ab4d0bd6908cd8f5e648e021d76363c98 resiprocate-1.10.0.zip df4ba3902770390e7a0f9f6b13c5959292feba04785f01b9d044ad31325fa1e0 resiprocate-contrib-1.10.0.tar.gz 2f40c568644cbf1dd8628da0535dadd8d17367860234163d003fe0fbd75ba9a0 resiprocate-contrib-1.10.0.zip ef1c50b7c70b533c7bec1bfb071ca19ff9368a0b1e8a951e430e273b8d413715 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJWDlraAAoJEOm1uwJp1aqDCxgP/jlJBE0fTSp1FzohA5IRmrmQ rVQcKOB6pI6rWTMEwv8WuBs6sA7z/z94b2jbLYZRo/iwXXb85TbQXqnIQkyw5GAs l+F73B+rPyNYN46CZvjYv/rrscW8rxDPoein/t7uEzfATm1xgAZrIykWhZx42WV2 QUEjZDAXRm2Q2duIBfnxyTmhyFurWgHJhtxLzx6zCVnml/hWt8xslzkH1WYtfXuI 0ltGqNuVlYlhHCi2/BpaxHVdsPELhdiTHpIu88UgBSHI5gKiUBp38dhQttwJr+bt VWF9Ri+KQPbn7d5JGc8mPMeBTlYmJUgFY4s//eIU2pYRcxZ2w1/iim2SHewMpift 51C9Lmp6vSBycpCNPAQ6yQqJdAjIlTlY9eKJ2td+bCUw66Zlx10h3tqY4ka95o0s TfFporu6dpaIu3TSo+qVW8fhXuYmRh86NHLLi3+LCbZ9i6j5E71qor5mkz9x/xLM 7kWbVJKNJFTdbTsVjAKZ7uh4YFfkn3NcYEu+5zwF5Fm/z6ohE36sme12Lo0khjyq kTDhefATpFvZLxu2l0RBmG+NktOj/H2MJvbPVGPyEtHaam1BJaRPv4UMh6bldoR4 vsrt8cL31HhnWGTZS7M7/yg39Ge+JrTAHQD8wpdVh6nBzFTqb2n2WIk2swPICrLA v8lx2bBfol6NYvB0GhAT =R1HL -----END PGP SIGNATURE-----

1 0

Siremis-4.2.0 - error with Alias and login page
by Infinicalls Infinicalls 02 Oct '15

02 Oct '15

Hi, I tried installing siremis-4.2.0 following the step given.The Alias was not working. So, I installed it in the /html folder and the installation was completed. But the login page looked strange. There was no logo displayed and the submit button was not there. Mine is apache 4.2 on Ubuntu LTS 14. Kindly let me know how to solve this problem. thanks Ganesh Kumar

2 2

how to use data received from diameter answer(CCA) in kamailio config script
by SureshTummala 02 Oct '15

02 Oct '15

Hi, I want retrieve the data present in the Credit-Control-Answer response from diameter in kamailio configuration script. Is there any provision in kamailio 4.1.x (or) later? Any suggestions are appreciated. Regards,Suresh Tummala

4 3

FW: Your iptel.org Registration
by Bijal Desai 02 Oct '15

02 Oct '15

When I call on sip:bijaldesai@iptel.org, it is not working. Can you please guide me -----Original Message----- From: registrar(a)iptel.org [mailto:registrar@iptel.org] Sent: Tuesday, September 29, 2015 10:00 PM To: Bijal Desai <Bijal(a)ssminfotech.com> Subject: Your iptel.org Registration Thank you for registering with iptel.org. We are reserving the following SIP address for you: sip:bijaldesai@iptel.org To finalize your registration please check the following URL within 24 hours: http://serweb.iptel.org/user/reg/confirmation.php?nr=473f1e2fc74bfb3e9d28eb… (If you confirm later you will have to re-register.) Here are the details of your account: --------------------------------------------------------------------- Username: bijaldesai(a)iptel.org Password: Angel1987@ Email: bijal(a)ssminfotech.com Full Name: Bijal Desai Sip address: sip:bijaldesai@iptel.org (You can always retrieve these via the "Forgot Password" link on the signup page) -- This message is automatically generated by SerWeb.

2 1

Kamailio-Asterisk real-time integration with Dynamic IP
by Rudy Eschauzier 02 Oct '15

02 Oct '15

All, The Kamailio-Asterisk integration that is described here asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb [Asipto - SIP and VoIP Knowledge Base Site] is limited to Asterisk servers with a fixed IP address. The reason is that Kamailio identifies and authorizes traffic from Asterisk based on the source IP address. Attached is a patch to kamailio.cfg that adds support for dynamic Asterisk hosts. It introduces the option to define a fully-qualified domain name instead of the IP address to identify the Asterisk server. The host name can be dynamically updated to always point at the (changing) IP address of the Asterisk server. Defining WITH_ASTERISK_FQDN enables the new option. When WITH_ASTERISK_FQDN is set, Kamailio will perform a DNS search on the host name in the asterisk.bindhost variable. It will authorize incoming traffic if it originates from one of the IP addresses the DNS lookup returns (and matches the asterisk.bindport variable as before). Furthermore, the patch introduce the option to automatically set the IP address of the server that Kamailio is running on. This does away with the need to properly define kamailio.bindip on every server that the configuration is running on. This option is enabled by defining WITH_AUTOIP. With the suggested changes I have been able to successfully run an Asterisk server in my home, having a dynamic public IP address and connecting to the Kamailio proxy on a VPS server with a static IP addres. Please let me know if you have any comments or suggestions. Kind regards,Rudy Eschauzier. | | | | | | | | | | | asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb [...Table of Contents Kamailio 4.0.x and Asterisk 11.3.0 Realtime Integration using Asterisk Database Architecture Registration Call Initiation Requirements MySQL Insta... | | | | View on kb.asipto.com | Preview by Yahoo | | | | |

2 1

cnxcc module
by Максим Панчоха 02 Oct '15

02 Oct '15

Hello! I'm trying to set max call duration, but after 5 seconds call is continues. Kamailio version: 4.3.2 Here's part of my config file: #!define CC_FLAG 29 ... modparam("cnxcc", "credit_check_period", 1) modparam("cnxcc", "redis", "addr=127.0.0.1;port=6379;db=1") modparam("dialog", "hash_size", 2048) modparam("dialog", "default_timeout", 3600) modparam("dialog", "db_mode", 0) modparam("dialog", "dlg_flag", DLG_FLAG) ... if ((is_method("INVITE")) && (is_request()) && (!has_totag())) { route(CNXCC); } route[CNXCC] { setflag(DLG_FLAG); if (!is_method("INVITE")) return; $var(client) = $fU; $var(max_time) = 5; if (!cnxcc_set_max_time("$var(client)", "$var(max_time)")) { xlog("Error setting up credit control"); return; } } event_route[dialog:failed] { xlog("L_INFO", "********END CALL*********$DLG_lifetime*******************"); } event_route[dialog:end] { xlog("L_INFO", "******END CALL************$DLG_lifetime****************"); } event_route[dialog:start] { xlog("L_INFO", "***********************DIALOG STARTED****************************"); } event_route[cnxcc:call-shutdown] { $var(duration) = $TS - $dlg(start_ts); xlog("L_INFO", *****END CALL***BALANCE IS EMPTY************$var(duration)*************"); } Tell me please, where I made a mistake. Thank you for a response.

2 1

ERROR: mediaproxy [mediaproxy.c:1978] #347
by Ngoc 02 Oct '15

02 Oct '15

Hello supporter, I took a look kamailio and get the error: Sep 29 11:28:37 lvps46-163-74-198 /usr/local/sbin/kamailio[1738]: ERROR: mediaproxy [mediaproxy.c:1978]: EngageMediaProxy(): engage_media_proxy requires the dialog module to be loaded and configured. How to resolved this problem, please help me. Regards, --------------------------- Dinh Hong Ngoc Technical Lead Edge-works Software Co.,ltd Hall 5, Quang Trung Software City, Tan Chanh Hiep Ward, Dist. 12, Ho Chi Minh City, Vietnam. Email: ngoc.dinh(a)edge-works.net Phone: +84 8 54371075 | Mobile: +84 909 911 406 Site: http://www.edge-works.net

2 1

receive_fd(): EOF
by jery john 02 Oct '15

02 Oct '15

11(12454) : <core> [mem/q_malloc.c:149]: qm_debug_frag(): BUG: qm_*: fragm. 0x7f9e8fcb2448 (address 0x7f9e8fcb2478) end overwritten(c0c0c000, abcdefed)! 13(12456) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 20 0(12443) ALERT: <core> [main.c:784]: handle_sigs(): child process 12454 exited by a signal 6 0(12443) ALERT: <core> [main.c:787]: handle_sigs(): core was generated 0(12443) INFO: <core> [main.c:799]: handle_sigs(): terminating due to SIGCHLD 13(12456) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 12(12455) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 9(12452) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 10(12453) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 8(12451) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 4(12447) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 3(12446) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 7(12450) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 6(12449) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 5(12448) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 2(12445) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 1(12444) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 0(12443) INFO: <core> [sctp_core.c:48]: sctp_core_destroy(): SCTP API not initialized using kamailio 4.2 with modified tcp_read.c and tcp_main.c files for buffer manipulation both files attached gdb output Reading symbols from /usr/local/sbin/kamailio...done. warning: exec file is newer than core file. [New LWP 15502] warning: Error reading shared library list entry at 0x79e8c789480056e4 warning: Error reading shared library list entry at 0x482a50b70fd8458b Core was generated by `/usr/local/sbin/kamailio -f /usr/local/etc/kamailio/kamailio.cfg -P /var/run/ka'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x000000000061f73d in _shm_resize (p=0x61f729 <_shm_resize+541>, s=32767, file=0x3f <error: Cannot access memory at address 0x3f>, func=0x0, line=-1433800800) at mem/shm_mem.c:111 111 DBG("WARNING:vqm_resize: resize(0) called\n");

2 1

blf problem
by huseyin kalyoncu 01 Oct '15

01 Oct '15

Hi I am trying to implement BLF functionality as described in http://kb.asipto.com/kamailio:presence:k43-blf. I am using the same conf with the one in the tutorial except that i am using postgres database instead of mysql. The problem is BLF is not working with this config (presence server and proxy server are in the same kamailio with same IP). But when I separate presence server from proxy server (2 different kamilio boxes with different IPs) BLF working perfect. i can see PUBLISH & NOTIFY messages in the tcpdump output with the working configuration. But i can not see any PUBLISH messages in the tcpdump output with the original config (one with presence and proxy servers are same). My question in the normal working environment (when BLF working perfectly); should i see PUBLISH and NOTIFY messages in the tcpdump output when the presence and proxy servers are the same? thanks Huseyin

2 9

SIP and conntrackd experience?
by Grant Bagdasarian 01 Oct '15

01 Oct '15

Hello, Does anyone have experience with SIP and conntrackd? Our media and signaling is separated. Does this work for VPN connections where SIP is sent over the VPN but the media over public internet? Thanks, Grant

2 5

modifying $fu / $fU (R-URI From)
by Sven Neuhaus 01 Oct '15

01 Oct '15

Hello, I'm having some troubles with modifying $fU in my kamailio.cfg. The following line appears to have no effect: $fU = $(fU{s.substr,2,0}); I would expect it to remove the first two leading characters from $fU. Has anyone else seen this? I have the same issue with modifying $fu. We're not using the uac module. And we're using the latest stable version of Kamailio. Thanks, -Sven

4 4

out of memory Error
by Yasin CANER 01 Oct '15

01 Oct '15

3 15

Crash kamailio 4.3.1
by Thibault Gueslin 30 Sep '15

30 Sep '15

After upgrading to kamailio 4.3.1 and modifying the config, I get this crash very often: ... CRITICAL: <core> [pass_fd.c:275]: receive_fd(): EOF on 21 ALERT: <core> [main.c:728]: handle_sigs(): child process 9341 exited by a signal 11 ALERT: <core> [main.c:731]: handle_sigs(): core was not generated INFO: <core> [main.c:743]: handle_sigs(): terminating due to SIGCHLD INFO: <core> [main.c:794]: sig_usr(): signal 15 received INFO: <core> [main.c:794]: sig_usr(): signal 15 received INFO: <core> [main.c:794]: sig_usr(): signal 15 received ... Is it known ? or may be related to my config ? Thank you Thibault

3 23

db_text and caching/reloading
by Asgaroth 30 Sep '15

30 Sep '15

Hi, I am busy testing the db_text module for some modules who's configuration does not change that often. If I set the db_mode for db_text to 0 (caching), it appears that if I modify the file directly (in this case the address dbtext file) and then issue a "kamctl address reload" the updated contents are *not* reloaded. However, if I set db_mode to 1, then the contents of the db_text file automatically reload when I change it on the file system. Is it possible to run db_text in caching mode but to also force a reload if I manually update the underlying database file? Additionally, in kamctlrc, I had to add the following variable: DBTEXT_PATH="/etc/kamailio/db_text" Whereas the original example for db_text path in kamctlrc is as follows: # database path used by dbtext, db_berkeley or sqlite #DB_PATH="/etc/kamailio/db_text" Is this just a typo in the kamctlrc distribution or is the variable meant to be DB_PATH or DBTEXT_PATH? Thanks

1 3

ACK and BYE are forwarded statelessly (failed to parse Route HF)
by Miroslav Dunaev 30 Sep '15

30 Sep '15

Hello everyone, I have a setup where kamailio acts as UAC to a SIP provider. Kamailio is also configured to pass all incoming calls to an Asterisk. Here is a diagram: Phone<-->Asterisk(10.10.11.232)<--->(PRIV:10.10.11.238)Kamailio(PUB:44.44.44.148)<--->(194.213.29.92)SIP-provider. When a call comes in from the SIP-provider, it gets all the way to the phone. But when the SIP-provider sends BYE or ACK (during hungup event or 200OK/SDP asterisk response.). I get this errors in my kamailio log: siputils [checks.c:100]: has_totag(): totag found <core> [parser/parse_rr.c:49]: do_parse_rr_body(): parse_rr_body(): No body for record-route rr [loose.c:106]: find_first_route(): failed to parse Route HF rr [loose.c:929]: loose_route(): There is no Route HF tm [t_lookup.c:648]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found tm [t_lookup.c:1011]: t_check_msg(): DEBUG: t_check_msg: msg id=1 global id=0 T start=0xffffffffffffffff tm [t_lookup.c:466]: t_lookup_request(): t_lookup_request: start searching: hash=10101, isACK=1 tm [t_lookup.c:424]: matching_3261(): DEBUG: RFC3261 transaction matching failed ..... .... .... siputils [checks.c:100]: has_totag(): totag found tm [t_lookup.c:1312]: t_newtran(): DEBUG: t_newtran: msg id=2 , global msg id=1 , T on entrance=0xffffffffffffffff tm [t_lookup.c:466]: t_lookup_request(): t_lookup_request: start searching: hash=10101, isACK=1 tm [t_lookup.c:424]: matching_3261(): DEBUG: RFC3261 transaction matching failed tm [t_lookup.c:648]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found tm [t_funcs.c:279]: t_relay_to(): SER: forwarding ACK statelessly here is the link to: kamailio.cfg, ngrep -i any capture, debug_level6 log: http://labmir.com/kamailio/ Looking at the SIP ACK that comes from SIP provider I can see that they use strict routing. (i.e. TO field is set to kamailio's public IP that is next hop to them). Maybe I am wrong to judge that its not loose routing just because of the TO field. Anyways, because of (failed to parse Route HF) error, ACKs and BYEs are forwarded by kamailio statelessly, as a result kamailio uses wrong interface to forward them (SIP_dailog.txt line:233) and therefore asterisk never sees ACKs or BYEs. How can I make kamailio recognize ACKs and BYEs belonging to a dialog and pass them statefully through the right interface? It is worth to mention that I use exactly the same config with a different SIP-provider (which is peered to our PUB IP not registered through UAC like in this case) and it works flawlessly. Thank you, Mir

2 1

Anybody in Beijing interested in Kamailio related project cooperation ?
by Thierry Luo 29 Sep '15

29 Sep '15

很报歉通过这个邮件列表打扰大家。我们是一个创业团队，刚刚拿到投资，正在组建核心团队，现需要一位在OpenIMSCore （或Kamailio/OpenSIPS）方面有经验的C/C++开发工程师加盟，待遇优厚，期权可谈，职位在北京。请有意者速与 luoyongheng(a)nane.cn <mailto:luoyongheng@nane.cn> 联系。谢谢！打扰见谅！罗

1 0

Best practices for troubleshooting deadlocks?
by Alex Balashov 29 Sep '15

29 Sep '15

Hello, Very occasionally, we encounter what appear to be deadlocks in all UDP receiver threads. All Kamailio processes are running, but no SIP messages are being processed. On one of our high-volume installation, this happens extremely infrequently -- maybe once every month or two. On these occasions, the operator restarts the proxy before we get a chance to go in and figure out what's going on. So, I'm trying to provide the operator with a procedure to execute prior to restarting the proxy on these occasions, so that we can see a snapshot of where the receiver threads are stuck. As far as I can tell, unless Kamailio itself segfaults, there's no specific PID that one can attach GDB to in order to get an overhead snapshot of all the child processes. Here's what I came up with: --------------------------------------------- #!/bin/bash kamcmd -s /tmp/kamailio_ctl ps > thread_log.txt echo >> thread_log.txt while read PID; do gdb --pid=$PID<<EOF>>thread_log.txt set print elements 0 thread apply all bt full generate-core-file detach EOF done < <(kamcmd -s /tmp/kamailio_ctl ps | grep 'udp receiver' | awk '{print $1}') --------------------------------------------- As far as I can tell, this should give me the most ample visibility into the state of the threads, with further core dumps to inspect if follow-up is needed. Hopefully this will result in some fixes back to the project. However, if there are any other suggestions for information to grab in such a scenario, I'm all ears. Thanks in advance! -- Alex -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

3 5

Kazoo db_url required?
by Asgaroth 29 Sep '15

29 Sep '15

Hi, I am doing some tests with the kazoo module, I only want to use it for some amqp related tasks. In our particular case, we do not require kazoo to hook into the presence tables, however, if I do *not* set the db_url parameter for kazoo, then kamailio fails to start with the following error: /usr/sbin/kamailio[11557]: CRITICAL: kazoo [kazoo.c:361]: mod_child_init(): child_init: database not bound /usr/sbin/kamailio[11557]: ERROR: <core> [sr_module.c:900]: init_mod_child(): Error while initializing module kazoo (/usr/lib64/kamailio/modules/kazoo.so) Is it possible to run the kazoo module without specifying the db_url parameter, we only need it for sending/recieving amqp messages. Additionally, I noticed that the amqp_connection parameter has a max limit of 50 characters, is it possible to increase this at all? I had a case where my url was 64 characters long and kazoo would fail with max character limit exceeded for the module parameter. Any tips much appreciated. Thanks

1 2

Kamailio recvfrom out of bounds
by José Seabra 28 Sep '15

28 Sep '15

I have one kamailio server listening in 2 network interfaces, kamailio receives sip messages from interface A and then send it to destine through interface B. When we start kamailio service then run gdb for each kamailio network interface process, execute the command "bt full" the result is the following: *tmp = 0x5f801b994c4715bd <Address 0x5f801b994c4715bd out of bounds>* interface - A bt full #0 0x00007fb01bfa40c3 in recvfrom () from /lib64/libc.so.6 No symbol table info available. #1 0x000000000047f2ba in udp_rcv_loop () at udp_server.c:421 len = 13 buf = '\000' <repeats 65535 times> tmp = 0x5f801b994c4715bd <Address 0x5f801b994c4715bd out of bounds> from = 0x7faf9bf38bb8 fromlen = 16 ri = {src_ip = {af = 2309178400, len = 32765, u = {addrl = {5458819, 4284160}, addr32 = {5458819, 0, 4284160, 0}, addr16 = {19331, 83, 0, 0, 24320, 65, 0, 0}, addr = "\203KS\000\000\000\000\000\000_A\000\000\000\000"}}, dst_ip = {af = 2, len = 4, u = {addrl = {80026686, 0}, addr32 = {80026686, 0, 0, 0}, addr16 = {7230, 1221, 0, 0, 0, 0, 0, 0}, addr = ">\034\305\004", '\000' <repeats 11 times>}}, src_port = 55576, dst_port = 5060, proto_reserved1 = 0, proto_reserved2 = 0, src_su = {s = {sa_family = 32687, sa_data = "\000\000\200D\243\211\375\177\000\000\213\337D"}, sin = {sin_family = 32687, sin_port = 0, sin_addr = {s_addr = 2309178496}, sin_zero = "\375\177\000\000\213\337D"}, sin6 = {sin6_family = 32687, sin6_port = 0, sin6_flowinfo = 2309178496, sin6_addr = {__in6_u = {__u6_addr8 = "\375\177\000\000\213\337D\000\000\000\000\000p", <incomplete sequence \372\233>, __u6_addr16 = {32765, 0, 57227, 68, 0, 0, 21616, 39930}, __u6_addr32 = {32765, 4513675, 0, 2616874096}}}, sin6_scope_id = 32687}}, bind_address = 0x7faf9becd7d8, proto = 1 '\001'} __FUNCTION__ = "udp_rcv_loop" #2 0x0000000000525eae in main_loop () at main.c:1573 i = 0 pid = 0 si = 0x7faf9becd7d8 si_desc = "udp receiver child=0 sock=62.28.197.4:5060 \000\000\000\000\000\000\001\000\000\000\000\000\000\000\260\244r\023n\000\000\000\071\263q\000\000\000\000\000\020\243q\000\000\000\000\000\b\000\000\000\001\000\000\000\260\373\371\233\257\177\000\000\220E\243\211\375\177\000\000|\351O\000\000\000\000\000\000\266\253\023\257\177\000\000\260\244r\023\257\177\000" ---Type <return> to continue, or q <return> to quit--- nrprocs = 32 __FUNCTION__ = "main_loop" #3 0x000000000052c395 in main (argc=11, argv=0x7ffd89a34848) at main.c:2533 cfg_stream = 0x2296010 c = -1 r = 0 tmp = 0x7ffd89a35f61 "" tmp_len = 0 port = 0 proto = 32688 options = 0x725010 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ret = -1 seed = 1641321572 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x7ffd89a34710 p = 0x7fb01bf4c646 <intel_check_word+166> "H\205\300t\025\017\266P\003\017\266\312D9\371\017\204", <incomplete sequence \305> __FUNCTION__ = "main" interface B bt full #0 0x00007fb01bfa40c3 in recvfrom () from /lib64/libc.so.6 No symbol table info available. #1 0x000000000047f2ba in udp_rcv_loop () at udp_server.c:421 len = 45 buf = '\000' <repeats 65535 times> tmp = 0x13cb2f24296000e9 <Address 0x13cb2f24296000e9 out of bounds> from = 0x7faf9bf38bb8 fromlen = 16 ri = {src_ip = {af = 2309178400, len = 32765, u = {addrl = {5458819, 4284160}, addr32 = {5458819, 0, 4284160, 0}, addr16 = {19331, 83, 0, 0, 24320, 65, 0, 0}, addr = "\203KS\000\000\000\000\000\000_A\000\000\000\000"}}, dst_ip = {af = 2, len = 4, u = {addrl = {2764381246, 0}, addr32 = {2764381246, 0, 0, 0}, addr16 = {7230, 42181, 0, 0, 0, 0, 0, 0}, addr = ">\034Ť", '\000' <repeats 11 times>}}, src_port = 56136, dst_port = 5060, proto_reserved1 = 0, proto_reserved2 = 0, src_su = {s = {sa_family = 32687, sa_data = "\000\000\200D\243\211\375\177\000\000\213\337D"}, sin = {sin_family = 32687, sin_port = 0, sin_addr = {s_addr = 2309178496}, sin_zero = "\375\177\000\000\213\337D"}, sin6 = {sin6_family = 32687, sin6_port = 0, sin6_flowinfo = 2309178496, sin6_addr = {__in6_u = { __u6_addr8 = "\375\177\000\000\213\337D\000\000\000\000\000p", <incomplete sequence \372\233>, __u6_addr16 = {32765, 0, 57227, 68, 0, 0, 21616, 39930}, __u6_addr32 = {32765, 4513675, 0, 2616874096}}}, sin6_scope_id = 32687}}, bind_address = 0x7faf9becda08, proto = 1 '\001'} __FUNCTION__ = "udp_rcv_loop" #2 0x0000000000525eae in main_loop () at main.c:1573 ---Type <return> to continue, or q <return> to quit--- i = 0 pid = 0 si = 0x7faf9becda08 si_desc = "udp receiver child=0 sock=62.28.197.164:5060 \000\000\000\000\001\000\000\000\000\000\000\000\260\244r\023n\000\000\000\071\263q\000\000\000\000\000\020\243q\000\000\000\000\000\b\000\000\000\001\000\000\000\260\373\371\233\257\177\000\000\220E\243\211\375\177\000\000|\351O\000\000\000\000\000\000\266\253\023\257\177\000\000\260\244r\023\257\177\000" nrprocs = 32 __FUNCTION__ = "main_loop" #3 0x000000000052c395 in main (argc=11, argv=0x7ffd89a34848) at main.c:2533 cfg_stream = 0x2296010 c = -1 r = 0 tmp = 0x7ffd89a35f61 "" tmp_len = 0 port = 0 proto = 32688 options = 0x725010 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ---Type <return> to continue, or q <return> to quit--- ret = -1 seed = 1641321572 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x7ffd89a34710 p = 0x7fb01bf4c646 <intel_check_word+166> "H\205\300t\025\017\266P\003\017\266\312D9\371\017\204", <incomplete sequence \305> __FUNCTION__ = "main" [root@c4-srv1 kamailio]# kamctl stats shmem shmem:fragments = 2552 shmem:free_size = 2082764040 shmem:max_used_size = 66449600 shmem:real_used_size = 64719608 shmem:total_size = 2147483648 shmem:used_size = 54355992 Can anyone explain the meaning of *tmp = 0x5f801b994c4715bd <Address 0x5f801b994c4715bd out of bounds>* Best Regards José Seabra

2 6

Kamailio with Radius authentication
by Ciolpan Ionut-Marian 28 Sep '15

28 Sep '15

Hi, I want to implement Kamailio with Radius authentication. To be more exactly I want to register SIP users (PhonerLite and/or Jitsi) based on the credentials stored in radcheck table from radius database. First of all, I have tried to register SIP users based on the credentials stored in users file from /etc/raddb directory. In order to do this,I am using auth_radius module (you can find the content of my kamailio.cfg file in the attachements) but without success. All of the SIP users are registeres successfully even if they are not specified in users file. Can you provide me some help to achieve this task? and also, can you explain to me how should I do this authentication based on the credentials stored in radcheck table? The content of users file in /etc/raddb: usertest@mydomain_name Auth-Type := Digest, User-Password == "*89Lob?p" Reply-Message = "Authenticated" Thank you for any help you can provide ! Best regards PS: kamailio 4.0.5 freeradius 2.2.0 radclient 2.2.0 PPS: I managed to register SIP users based on the credentials stored in subscriber table from kamailio db.

2 10

Releasing Kamailio v4.3.3
by Daniel-Constantin Mierla 28 Sep '15

28 Sep '15

Hello, I am considering to release Kamailio v4.3.3 by end of this week, most likely of Friday, Oct 2. As usual, announce any issues that you are aware and not reported to sr-dev or bug tracker. Also, if some patch was no backported and you think it has to be, write to sr-dev mailing list. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com

1 0

GeoIP and multiple rtp
by Infinicalls Infinicalls 28 Sep '15

28 Sep '15

Hi, I have installed Kamailio in one instance and want to have multiple RTP instances for geo loadbalancing. I can understand that rtp_cluster will do that based on number of parameters, but geo_IP is missing. Can somebody tell me how do I go about with it? Is it possible to get with Kamailio's geoip module and "instruct" rtp? regards Ganesh Kumar

3 2

passing multiple values in mqueue
by Thibault Gueslin 28 Sep '15

28 Sep '15

I want to pass several arguments to a mqueue to process them asynchronously. (like in the example of sip sweet). How could it be done ? Other possibility is to generate a string and parse it in the lua script. But there should something more simple ? thibault

2 1

MSRP over Websockets
by vamsi 25 Sep '15

25 Sep '15

Hi, I am trying to configure MSRP over websocket and using Crocodilr-msrp client for connecting the same but when I try to transfer any file it gives me the below error. Any thoughts is appreciated. I am able to do audio, vedio and messaging using SIP-JSSIP client and working fine. Error - Log -------------- Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: tls [tls_server.c:208]: tls_complete_init(): Using initial TLS domain TLSc<default> (dom 0x7f35500d4858 ctx 0x7f355013d620 sn []) Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: tls [tls_domain.c:701]: sr_ssl_ctx_info_callback(): SSL handshake started Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: ERROR: <core> [tcp_main.c:2654]: tcpconn_1st_send(): connect 10.205.64.24:8084 failed (RST) Connection refused Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: ERROR: <core> [tcp_main.c:2664]: tcpconn_1st_send(): 10.205.64.24:8084: connect & send for 0x7f35501bca20 failed: Connection refused (111) Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: <core> [tcp_main.c:2858]: tcpconn_chld_put(): destroying connection 0x7f35501bca20 (24, -1) flags 0060 Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: ERROR: msrp [msrp_netio.c:178]: msrp_relay(): forwarding frame failed Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: exec: *** cfgtrace:request_route=[DEFAULT_EVENT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=1202 a=2 n=exit Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: <core> [tcp_read.c:1153]: ws_process_msg(): WebSocket Message: [[>>>#012??#011?i#036'?$Mu?Ik#022?#001,I?#005>t?'Z*?=q#012?#010jO?IsT?#031m#035?F/#027?[.#022?_*#011?]$#037?Q*#010?G/#027?\&#011?G+#021?]*#020?^*#034?#012n#007?#032lW?S1#010?Y0#025?\0#021?G,#023?Q.#037?Fm#011?Y*#022?G)#011?P)#021?\(#021?RjD?IsT?#031$#010?<<<]] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: websocket [ws_conn.c:429]: wsconn_get(): wsconn_get for id [22] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: websocket [ws_conn.c:437]: wsconn_get(): wsconn_get returns wsc [0x7f3550140930] refcnt [2] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: websocket [ws_frame.c:415]: decode_and_validate_ws_frame(): decoding WebSocket frame Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: websocket [ws_frame.c:456]: decode_and_validate_ws_frame(): supported non-control frame: 0x2 Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: websocket [ws_frame.c:555]: decode_and_validate_ws_frame(): Rx (decoded): MSRP u5xh2ntl SEND#015#012To-Path: msrps:// 10.205.64.24:8084/s.10458.4.561447274;tcp msrps:// 10.205.64.24:8084/s.10453.7.297645663;tcp msrp://i64fn3tc.invalid:2855/g14o60krz6;ws#015#012From-Path: msrp://grtsrfd0.invalid:2855/505z40k5b1;ws#015#012Message-ID: 3652053096.cr4l1e1q#015#012Success-Report: yes#015#012Failure-Report: yes#015#012Byte-Range: 2049-4096/68240#015#012Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document#015#012#015#012 Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: websocket [ws_frame.c:671]: ws_frame_receive(): Rx MSRP frame:#012MSRP u5xh2ntl SEND#015#012To-Path: msrps://10.205.64.24:8084/s.10458.4.561447274;tcp msrps://10.205.64.24:8084/s.10453.7.297645663;tcp msrp://i64fn3tc.invalid:2855/g14o60krz6;ws#015#012From-Path: msrp://grtsrfd0.invalid:2855/505z40k5b1;ws#015#012Message-ID: 3652053096.cr4l1e1q#015#012Success-Report: yes#015#012Failure-Report: yes#015#012Byte-Range: 2049-4096/68240#015#012Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document#015#012#015#012 Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f3550140930] refcnt [2] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f3550140930] refcnt [1] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: msrp [msrp_parser.c:171]: msrp_parse_fline(): MSRP FLine: [1] [MSRP] [u5xh2ntl] [SEND] [1] [] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: msrp [msrp_parser.c:327]: msrp_parse_headers(): MSRP Header: (0x7f3558c0d1b8) [To-Path] [2] [msrps://10.205.64.24:8084/s.10458.4.561447274;tcp msrps:// 10.205.64.24:8084/s.10453.7.297645663;tcp msrp://i64fn3tc.invalid:2855/g14o60krz6;ws] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: msrp [msrp_parser.c:327]: msrp_parse_headers(): MSRP Header: (0x7f3558c0c918) [From-Path] [1] [msrp://grtsrfd0.invalid:2855/505z40k5b1;ws] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: msrp [msrp_parser.c:327]: msrp_parse_headers(): MSRP Header: (0x7f3558c0ed80) [Message-ID] [4] [3652053096.cr4l1e1q] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: msrp [msrp_parser.c:327]: msrp_parse_headers(): MSRP Header: (0x7f3558c0ee10) [Success-Report] [7] [yes] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: msrp [msrp_parser.c:327]: msrp_parse_headers(): MSRP Header: (0x7f3558c1a868) [Failure-Report] [0] [yes] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: msrp [msrp_parser.c:327]: msrp_parse_headers(): MSRP Header: (0x7f3558c0c9a8) [Byte-Range] [5] [2049-4096/68240] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: msrp [msrp_parser.c:327]: msrp_parse_headers(): MSRP Header: (0x7f3558c107d8) [Content-Type] [8] [application/vnd.openxmlformats-officedocument.wordprocessingml.document] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: msrp [msrp_parser.c:356]: msrp_parse_headers(): MSRP Body: [2050] [[#012#012]] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: msrp [msrp_mod.c:468]: msrp_frame_received(): executing event_route[msrp:frame-in] (3) Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: <core> [parser/msg_par *********** Kamailio.cfg **************** #!ifdef WITH_MSRP event_route[msrp:frame-in] { msrp_reply_flags("1"); if ((($Rp == MY_WS_PORT || $Rp == MY_WSS_PORT) && !(proto == WS || proto == WSS)) && $Rp != MY_MSRP_PORT) { xlog("L_WARN", "MSRP request received on $Rp\n"); msrp_reply("403", "Action-not-allowed"); exit; } if (msrp_is_reply()) { msrp_relay(); } else if($msrp(method)=="AUTH") { if($msrp(nexthops)>0) { msrp_relay(); exit; } if (!www_authenticate("MY_DOMAIN", "subscriber", "$msrp(method)")) { if (auth_get_www_authenticate("MY_DOMAIN", "1", "$var(wauth)")) { msrp_reply("401", "Unauthorized", "$var(wauth)"); } else { msrp_reply("500", "Server Error"); } exit; } if ($hdr(Expires) != $null) { $var(expires) = (int) $hdr(Expires); if ($var(expires) < MSRP_MIN_EXPIRES) { msrp_reply("423", "Interval Out-of-Bounds", "Min-Expires: MSRP_MIN_EXPIRES\r\n"); exit; } else if ($var(expires) > MSRP_MAX_EXPIRES) { msrp_reply("423", "Interval Out-of-Bounds", "Max-Expires: MSRP_MAX_EXPIRES\r\n"); exit; } } else { $var(expires) = MSRP_MAX_EXPIRES; } $var(cnt) = $var(cnt) + 1; pv_printf("$var(sessid)", "s.$(pp).$(var(cnt)).$(RANDOM)"); $sht(msrp=>$var(sessid)::srcaddr) = $msrp(srcaddr); $sht(msrp=>$var(sessid)::srcsock) = $msrp(srcsock); $shtex(msrp=>$var(sessid)) = $var(expires) + 5; # - Use-Path: the MSRP address for server + session id $var(hdrs) = "Use-Path: msrps://MY_IP_ADDR:MY_MSRP_PORT/" + $var(sessid) + ";tcp\r\n" + "Expires: " + $var(expires) + "\r\n"; msrp_reply("200", "OK", "$var(hdrs)"); } else if ($msrp(method)=="SEND" || $msrp(method)=="REPORT") { if ($msrp(nexthops)>1) { if ($msrp(method)!="REPORT") { msrp_reply("200", "OK"); } msrp_relay(); exit; } $var(sessid) = $msrp(sessid); if ($sht(msrp=>$var(sessid)::srcaddr) == $null) { # one more hop, but we don't have address in htable msrp_reply("481", "Session-does-not-exist"); exit; } else if ($msrp(method)!="REPORT") { msrp_reply("200", "OK"); } msrp_relay_flags("1"); msrp_set_dst("$sht(msrp=>$var(sessid)::srcaddr)", "$sht(msrp=>$var(sessid)::srcsock)"); msrp_relay(); } else { msrp_reply("501", "Request-method-not-understood"); } } Thanks, Vamsi

2 3

Kamailio & VoLTE (powered by ng-voice) at ITU Telecom World in Budapest 2015
by Carsten Bock 25 Sep '15

25 Sep '15

Hi Everyone, We will have our own small LTE (and VoLTE enabled) network at the ITU Telecom World 2015 in Budapest. Since we are on the exhibitor list, we are pleased to share a complimentary Exhibition Visitor pass for you to visit our booth there (no. P07 in Hall F). Register at http://telecomworld.itu.int/take-part/attend/ following the guidelines, embedding the promotional code C-00001092 when prompted. Thanks, Carsten -- Carsten Bock CEO (Geschäftsführer) ng-voice GmbH Schomburgstr. 80 D-22767 Hamburg / Germany http://www.ng-voice.com mailto:carsten@ng-voice.com Office +49 40 5247593-0 Fax +49 40 5247593-99 Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284 Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/

1 0

RPC ul.dump
by Loïc Boissy 25 Sep '15

25 Sep '15

Hello, As mentionned in the doc, ul.dump command dumps the content of the location table. I use MULTIDOMAIN domain configuration, and i would like to use a RPC command to recover all contact present in my database (for all domains). Is there a solution to do that? Thanks you for you help. Loic BOISSY -- Visit Digigram at IBC2015 at Stand 8.C51, Sept. 11-15 in Amsterdam Register here <http://www.ibc.org/page.cfm/link=478> for your *FREE* pass with Digigram's Exhibitor Customer Code *4462*

3 5

Kamailio Asterisk MWI
by Ansuman Manna - Asergis Telecom 25 Sep '15

25 Sep '15

Hi, I am working on MWI (message waiting indication). I am using Kamailio as SIP registrar, Asterisk is for call routing. I can send notify to Kamailio from my VM server but thing is Kamailio is not handling the notify. If you have some suggestion about this. Regards, Ansuman Manna Software Developer Asergis Telecom Services Private Limited Office Tel: +91 11 6606 8400 Office Fax: +91 112554 5156 http://www.asergis.in <http://www.asergis.in>

3 3

Ragarding reginfo handling in kamailio
by Ram Anji 25 Sep '15

25 Sep '15

Hi, I am facing issue with reginfo handling in kamailio, I am getting proper notify when user is registered and deregistered properly. But i am not getting same when user's registration is expired[with out refresh/ when entry is removed from location], Can anyone suggest me how can i achieve this. I am using 4.3.1 kamailio Regards, Raman

2 1

OpenSev -> Kamailio Migration?
by Matthew Harris 25 Sep '15

25 Sep '15

Hello everyone! I am new to the VOIP world and currently researching a solution to upgrading or migrating from an antiquated openser sip server to kamailio. Has anyone ever had to do this? If so: What challenges should I expect to face? Warmest regards, Matt

2 1

SIP account.
by Grendell 25 Sep '15

25 Sep '15

Hi A few says ago I registered an account user name 08031955. However I have been unable to connect using 2 different SIP phones. Can you please check if this account is active yet. Can you advise if my user name has to include ....(a)iptel.org on the end of it? many thanks Graham Rendell

2 1

regEvent feature
by Stefan Ljung 25 Sep '15

25 Sep '15

(A continuation on an old thread) In the RFC 3680 it is described how a UE can subscribe to its own registration state(s). As soon as it's own registration state changes in any way - like a refresch registration - a NOTIFY is send to the subscribing terminal. What made me hopeful was when I in the Overview's use case section for the module pua_reginfo read the line: "A client could subscribe to it's own registration-status, so he would get notified as soon as his account gets administratively unregistered." That's in line with how I would like to use it - Is it in any way possible to achieve that in the Kamailio? /Stefan From: Stefan Ljung Sent: den 18 februari 2015 09:32 To: miconda(a)gmail.com Subject: RE: [SR-Users] Event reg - questions >From the pua_regInfo module description: Use cases for this might be: Keeping different Servers in Sync regarding the location database Get notified, when a user registers: A presence-server, which handles offline message storage for an account, would get notified, when the user comes online. A client could subscribe to it's own registration-status, so he would get notified as soon as his account gets administratively unregistered. ... So it's the last line I want to deploy. Maybe Im over-interpreting "A client could subscribe to it's own registration-status" I want to be able to simulate (As close a possible) a VoLTE clients reg events handling. Only the part between to and from the UE. So no PUBLISH is needed - Kamailio needs to notify the UE about its registration status. /Stefan From: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Sent: den 16 februari 2015 17:43 To: Kamailio (SER) - Users Mailing List; Stefan Ljung Subject: Re: [SR-Users] Event reg - questions Hello, afaik, the pua_reginfo is for publishing details of location records to another sip server node, main purpose being location replication. I don't think it is something for an end UA. If you want publishing online/offline states for an user based on its registration state, look at pua_usrloc module. On 12/02/15 15:17, Stefan Ljung wrote: I made a test configuration for trying the pua_regEvent module. There were two things I want to ask about. First - when the SUBSCRIBE to event 'reg' following a UEs registration to the Kamailio is responded with a NOTIFY - there was no body in the NOTIFY. I expected a XML body with registration status. Second - When the UE re-registers to Kamailio - I expected a NOTIFY to be send on the existing 'reg' subscription, but nothing happened. Or am I missing some configuration ? Here's some of the conf script: [..] modparam("pua_reginfo", "publish_reginfo", 0) Btw, with the above parameter value, the module is no longer sending PUBLISH requests, in other words, it is not informing the other peers that there is some update to location records. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com

2 1

Kamailio PSTN with User/Pass authentication
by Infinicalls Infinicalls 24 Sep '15

24 Sep '15

Hi, I am trying to add PSTN gw for terminating my calls. I have changed the IP in the kamailio.cfg file, but this provider wants digest auth and so I need to pass api/pass to them. Can somebody guide me how and where to add the username+pass to the config file. thanks regards Ganesh Kuamr

4 8

Re: [SR-Users] [Kamailio 4.2] Crash during burn-in test
by Daniel-Constantin Mierla 24 Sep '15

24 Sep '15

Hello, the first frames of the backtrace don't have the symbol table, do have other core files from where you can extract the bt full? Also, 4.2.3 is old in its series, newer versions in branch 4.2 were released. Can you update the latest version in branch 4.2 and reproduce again? That will rule out is not a side effect of an issue fixed after 4.2.3. You don't need to change anything in config or database, just grab the latest sources from branch 4.3 and install over the old binaries. Cheers, Daniel On 08/09/15 07:58, Jack Wang wrote: > Hi, > > The result of 'kamailio -v' is: > > version: kamailio 4.2.3 (arm/linux) 87ca6e-dirty > flags: STATS: Off, EXTRA_DEBUG, USE_TCP, USE_TLS, TLS_HOOKS, > USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, > SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_MALLOC, USE_FUTEX, > USE_PTHREAD_MUTEX, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, > USE_DST_BLACKLIST, HAVE_RESOLV_RES > MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, > BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB > poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. > id: 87ca6e -dirty > compiled on 16:15:00 Sep 4 2015 with arm-marvell-linux-gnueabi-gcc > > > It can be reproduced not only once, steps like wrote before. > > Following link is the result of `bt full` from the core file generated: > > https://gist.github.com/BroWater/dd759897f4b88672720a#file-gistfile1-txt > > FYI > > > > >Hello, > > > >can you give the exact version: kamailio -v? > > > >Also, the log message indicates that a core file was generated, sent the > >backtrace taken from gdb: > > > >gdb /path/to/kamailio /path/to/corefile > >bt full > > > >Could you reproduce the issue, or did it happen only once? > > > >Cheers, > >Daniel > > > >On 03/09/15 04:50, Jack Wang wrote: > >> > >> [Steps] > >> > >> 1. one MCU call multi-endpoints > >> 2. MCU hangup all endpoints > >> > >> repeatedly. And all through Kamailio proxy. > >> > >> [Results] > >> > >> For a while, Kamailio crashed. > >> > >> Followings are related logs: > >> > >> > >> ========================================== > >> > >> Sep 2 19:08:34 ./kamailio[3712]: : tm [t_fwd.c:1632]: > >> t_send_branch(): BUG: t_send_branch: retr. already started for > 0x41848fa0 > >> Sep 2 19:08:34 ./kamailio[3712]: ERROR: sl [sl_funcs.c:387]: > >> sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on > >> sending to next hop occurred (477/SL) > >> > >> At this point the related behavior is that Kamailio received two INFO > >> requests simultaneously. I wonder whether this is the cause. > >> And maybe it's related to the later crash? > >> > >> Sep 2 19:08:35 ./kamailio[3713]: CRITICAL: <core> [pass_fd.c:293]: > >> receive_fd(): EOF on 11 > >> Sep 2 19:08:35 ./kamailio[3703]: ALERT: <core> [main.c:784]: > >> handle_sigs(): child process 3704 exited by a signal 11 > >> Sep 2 19:08:35 ./kamailio[3703]: ALERT: <core> [main.c:787]: > >> handle_sigs(): core was generated > >> Sep 2 19:08:35 ./kamailio[3703]: : <core> [mem/f_malloc.c:586]: > >> fm_free(): BUG: fm_free: bad pointer 0x7239b6c4 (out of memory > >> block!), called from tm: h_table.c: free_cell(157) - aborting > >> > >> > >> Any suggestions? > >> > >> Thanks. > >> > >> ========================================== > >> > >> > >> _______________________________________________ > >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > >> sr-users at lists.sip-router.org <http://lists.sip-router.org> > >> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat

2 2

Re: [SR-Users] load 2 500 000 rows from dialplan
by Никитенко Виталий 24 Sep '15

24 Sep '15

>Hello > > >On 24/09/15 11:06, Никитенко Виталий wrote: >> Hi! >> I have kamailio-4.2.3. And in table dialplan there is 2 500 000 rows. When i started kamailio i see error >> >> ERROR: dialplan [dp_repl.c:74]: repl_exp_parse(): out of shm memory >> ERROR: dialplan [dp_db.c:393]: build_rule(): failed to compile replacing expression >> ERROR: dialplan [dp_db.c:111]: init_db_data(): failed to load database data >> ERROR: dialplan [dialplan.c:188]: mod_init(): could not initialize data >> ERROR: <core> [sr_module.c:968]: init_mod(): Error while initializing module dialplan (/usr/local/lib64/kamailio/modules/dialplan.so) >> >> then i set modparam("dialplan", "fetch_rows", 2500000) and started kamailio i see >> >> ERROR: db_mysql [km_dbase.c:422]: db_mysql_fetch_result(): no memory left >> ERROR: dialplan [dp_db.c:231]: dp_load_db(): failed to fetch >> ERROR: dialplan [dp_db.c:111]: init_db_data(): failed to load database data >> ERROR: dialplan [dialplan.c:188]: mod_init(): could not initialize data >> ERROR: <core> [sr_module.c:968]: init_mod(): Error while initializing module dialplan (/usr/local/lib64/kamailio/modules/dialplan.so) >> >> Please say me how i can load to memory 2500000 rows dialplan? >/usr/local/kamailio/sbin/kamailio -h | grep '\-[mM]' > -m nr Size of shared memory allocated in Megabytes > -M nr Size of private memory allocated, in Megabytes > >In you particular case, you need more shared memory (-M). > >Regards Thanks, it works!

1 0

load 2 500 000 rows from dialplan
by Никитенко Виталий 24 Sep '15

24 Sep '15

Hi! I have kamailio-4.2.3. And in table dialplan there is 2 500 000 rows. When i started kamailio i see error ERROR: dialplan [dp_repl.c:74]: repl_exp_parse(): out of shm memory ERROR: dialplan [dp_db.c:393]: build_rule(): failed to compile replacing expression ERROR: dialplan [dp_db.c:111]: init_db_data(): failed to load database data ERROR: dialplan [dialplan.c:188]: mod_init(): could not initialize data ERROR: <core> [sr_module.c:968]: init_mod(): Error while initializing module dialplan (/usr/local/lib64/kamailio/modules/dialplan.so) then i set modparam("dialplan", "fetch_rows", 2500000) and started kamailio i see ERROR: db_mysql [km_dbase.c:422]: db_mysql_fetch_result(): no memory left ERROR: dialplan [dp_db.c:231]: dp_load_db(): failed to fetch ERROR: dialplan [dp_db.c:111]: init_db_data(): failed to load database data ERROR: dialplan [dialplan.c:188]: mod_init(): could not initialize data ERROR: <core> [sr_module.c:968]: init_mod(): Error while initializing module dialplan (/usr/local/lib64/kamailio/modules/dialplan.so) Please say me how i can load to memory 2500000 rows dialplan?

2 1

JSONRPC commands
by Loïc Boissy 23 Sep '15

23 Sep '15

Hello I am trying to use JSONRPC-S Kamailio module to request for example the content of the location table. More generally, i would like to send RPC commands to my kamailio server using http request. For the moment, kamailio server always returns "400 bad request: corrupted packet". To send my request, i use curl. For example: curl --header 'Content-Type: application/json' --data-binary "{"id": 1, "jsonrpc": "2.0", "method": "ul.dump" }" http://XXX.XXX.XXX.XXX/RPC/ Is there specific syntax to respect? Kamailio server version is 4.3.2. Thank you in advance. Loic BOISSY -- Visit Digigram at IBC2015 at Stand 8.C51, Sept. 11-15 in Amsterdam Register here <http://www.ibc.org/page.cfm/link=478> for your *FREE* pass with Digigram's Exhibitor Customer Code *4462*

2 7

auth_radius module
by Marian Pandoranum 23 Sep '15

23 Sep '15

2 1

loose_route function select wrong next hop!
by Yasin CANER 22 Sep '15

22 Sep '15

3 4

Two suggestions
by 天 22 Sep '15

22 Sep '15

May this mailing list have a search function? This function will make us convient to find what we concern about. OpenIMSCore mailing list have this function, and I felt it Improved productivity. And the mailing list archive system seems to be operated manually. Can the mails be archived automatically? So it can be more instant to developers from asia. BR WangXinXin

2 2

What SIP stack does Kamailio or OpenIMSCore implements?
by 天 22 Sep '15

22 Sep '15

Hi, I am a rookie in SIP related area. I run into OpenIMSCore in recent days, and then I was introduced to Kamailio. Now I am wondering what SIP stack does Kamailio or OpenIMSCore implements? Or neither of them use a SIP stack? Can anybody help me on this? Thanks !

2 1

Re: [SR-Users] Question about in call both side redirection
by Андрей Ярин 22 Sep '15

22 Sep '15

sr-users-request(a)lists.sip-router.org пишет: > Hello On 04/09/15 07:57, ?????? ???? wrote: >> >Hello (sorry for my bad english) - i try to create voice record >> >service by request. User A call to user B. In call by pressing >> >combination like *55 Kamailio must redirect both sides to asterisk, >> >whitch create dynamic conference room with recording. As i understand >> >i need to use dlg_refer() from dialog module, but in log file i get: >> >Konsole output >> >Sep 4 10:45:14 voipc-node2 /usr/local/sbin/kamailio[18941]: ERROR: >> >dialog [dlg_req_within.c:85]: build_dlg_t(): no contact available >> >Sep 4 10:45:14 voipc-node2 /usr/local/sbin/kamailio[18941]: ERROR: >> >dialog [dlg_transfer.c:188]: dlg_refer_callee(): failed to create dlg_t >> > >> > >> >In script i try to refer with: >> >dlg_refer("callee","sip:100@10.10.9.209"); >> >dlg_refer("caller","sip:100@10.10.9.209"); >> > > in what context do you use the above actions? In other words, do you > execute them when you process a specific request? If yes, which one? > > Another question, how do you capture when *55 is pressed? Is dtmf sent > via sip info request? > > Cheers, > Daniel > > -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - > http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - > http://www.asipto.com Kamailio Advanced Training, Sep 28-30, 2015, in > Berlin - http://asipto.com/u/kat For now i try to use event_route[dialog:start] - i testing - can kamailio redirect both sides to external service, and will it work with event_route[dispatcher:dst-down]. If it will work, i will add SIP INFO processing for service codes -- Ярин Андрей Инженер ООО "И.С.-Телеком" 8(351)7786878 доб 113 8(351)2555724 доб 113 8(351)2555787 доб 113

2 2

carrierroute module cannot use prefix that start with +
by José Seabra 21 Sep '15

21 Sep '15

Hello there, I'm using carrierroute module to route calls based on prefix, everything was working until i tried use prefixes that start with +, kamailio core doesn't allow me use the + on carrierroute prefix, i get the following message from kamailio logs: INFO: carrierroute [cr_carrier.c:100]: add_domain_data(): adding domain 1 'main' to carrier 1 'carriers'35(17196) DEBUG: carrierroute [cr_carrier.c:101]: add_domain_data(): domain position 0 (domain_num=1, first_empty_domain=0)35(17196) INFO: carrierroute [cr_data.c:414]: get_domain_data_or_add(): added domain 1 'main' to carrier 1 'carriers'35(17196) INFO: carrierroute [cr_data.c:470]: add_route(): found carrier and domain, now adding route 35(17196) ERROR: <core> [dtrie.c:130]: dtrie_insert(): cannot insert non-numerical character 35(17196) ERROR: carrierroute [cr_domain.c:168]: add_route_to_tree(): cannot insert route flags into d-trie anyone can help in order allow use + in carrierroute prefix. Best regards José Seabra

3 4

dispatcher.list reversed by dispatch.c reindex_dests()
by Giovanni Maruzzelli 21 Sep '15

21 Sep '15

Hello, dispatcher gives me destination sets with entries in reverse order: I have installed from Kamailio deb repository packages version 4.3.2+jessie. # kamailio -V version: kamailio 4.3.2 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_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 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 4.9.2 I configured dispatcher: modparam("dispatcher", "use_default", 1) modparam("dispatcher", "list_file", "/etc/kamailio/dispatcher.list") modparam("dispatcher", "flags", 3) modparam("dispatcher", "dst_avp", "$avp(AVP_DST)") modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)") modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)") modparam("dispatcher", "sock_avp", "$avp(AVP_SOCK)") modparam("dispatcher", "ds_ping_interval", 5) modparam("dispatcher", "ds_probing_mode", 1) I have this dispatcher.list: 1 sip:192.168.1.144:5060 2 1 sip:192.168.1.145:5060 2 1 sip:192.168.1.146:5060 2 2 sip:192.168.1.146:5060 2 2 sip:192.168.1.145:5060 2 So, I expect dispatcher to have: set 1 first two destinations in distribution via hash on callid, and third destination as failover (192.168.1.146 <http://192.168.1.146:5060>) . set 2 all traffic on first destination, and if first fails, all traffic will failover to second destination (192.168.1.145 <http://192.168.1.146:5060>). Instead reindex_dests shuffle the sets upside down: DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/1] <sip: 192.168.1.144:5060> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/2] <sip: 192.168.1.145:5060> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/3] <sip: 192.168.1.146:5060> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [2/1] <sip: 192.168.1.146:5060> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [2/2] <sip: 192.168.1.145:5060> DEBUG: dispatcher [dispatch.c:494]: reindex_dests(): found [2] dest sets DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 2 sip: 192.168.1.145:5060 2 0 (,0,0) DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 2 sip: 192.168.1.146:5060 2 0 (,0,0) DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1 sip: 192.168.1.146:5060 2 0 (,0,0) DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1 sip: 192.168.1.145:5060 2 0 (,0,0) DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1 sip: 192.168.1.144:5060 2 0 (,0,0) DEBUG: dispatcher [dispatcher.c:347]: mod_init(): loaded dispatching list So, Kamailio give me set 1 and set 2 as per post-reindex_dests, and failover is 192.168.1.144 for set 1, and 192.168.1.146 for set 2. Is this the expected behavior? Am I doing something wrong in configuration? Thank you all in advance, -giovanni Sincerely, Giovanni Maruzzelli Cell : +39-347-2665618

2 3

Compiling Kamailio for Cubie/RaspberryPi/others ARM arch from main repos
by nadie 21 Sep '15

21 Sep '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 #!/bin/bash # Compiling Kamailio for Cubie/RaspberryPi/others ARM arch from main repos: echo 'deb-src http://deb.kamailio.org/kamailio43 jessie main' > /etc/apt/sources.list.d/kamailio.list wget -O- http://deb.kamailio.org/kamailiodebkey.gpg | sudo apt-key add - dpkg --add-architecture i386 apt-get update apt-get install bison debhelper erlang-dev gcj-jdk libconfuse-dev libdb-dev libev-dev libfreeradius-client-dev libgeoip-dev libhiredis-dev libjansson-dev libjson-c-dev liblua5.1-0-dev libmemcached-dev libmono-2.0-dev libmysqlclient-dev libperl-dev libpq-dev libpurple-dev librabbitmq-dev libreadline-dev libsasl2-dev libsctp-dev libsnmp-dev libsqlite3-dev libunistring-dev libval-dev libxml2-dev python-dev unixodbc-dev uuid-dev adduser python libc6 libncurses5 libpcre3 libreadline6 libtinfo5 snmpd mkdir kamailio && cd kamailio/ apt-get -b source kamailio dpkg --remove-architecture i386 rm /etc/apt/sources.list.d/kamailio.list apt-get update dpkg -i *.deb cd .. && rm -rf kamailio/ # end :-) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJV+BKUAAoJEG5DH1ilMeeenM8P/jqzMKtxmRheDDT4pqxzo9W1 lSNpg+UhYr5CC/IXCgGXkP5Sup87/qiAVYz/u902pS9hdIBfdbup2PUsvTX4QK+1 Dybxli9ym4Fup9m6MuB+VLIjkiOOwtGnvChbnPgjJnMxDjzBbDFEmositlfAeiFU XcyIfjYDndvd2+0a1UkTVVuGBEbY6BdVkANvINy2BkZUkolstTgVr7jirYUSTEsa U9M+lX98Dbau5gfvyx87a6CkcW8fyKCgZGBYqjBIyr1TrPgtGcXdcgC77iD2pziW wkU9DIRX0sOaIiAb76hX64SL8U9b+dJr2t17PXjiEEcVWuc7YtV2R0YURAfquw9O ycSh+PWFJgc1PZx5dFZlWceDXjdffnPiWt3Fys3HuVNWLY6iVfOSFv7sMcJ4NyaT N+u81Dr4T9blZ2yRmibRUzlmSlcq4at2yKE19/AsejphXI7mnaARuNlHZUq+4RY9 EF4zlr5zTHmPhvLoh7rjzqWGLmun4g7a7mCnbMDUKKbndqb24QKhO9czvkTvYLGR vbAK56kM96jh3OBLenjl58YzK4qBbJ5sM+UCw6DA5HnF+/jh+oK4zeKL28yqEaG0 SxS/xuG4xxi2wPvGJ36Rg6gIB5cHAxizGLMEPGUPTKCPhKLFIbtunabNu2gj+6nh bpe/fyLw0ZKHF8R4tifU =Ty41 -----END PGP SIGNATURE-----

2 2

Kamailio ACK retransmission
by Yasin CANER 21 Sep '15

21 Sep '15

1 0

Kamailio - Asterisk ACK retransmission problem
by Yasin CANER 21 Sep '15

21 Sep '15

1 0

Kamailio presence shared DB_text
by Ewgeny 21 Sep '15

21 Sep '15

Hi list! We use Kamailio 4.2 for presence BLF with DB_TEXT. And i want to make cluster with a few Kamailio's presences, to load balance. Can you please tell me - is that possible to use same shared DB_TEXT database with 2 or more Kamailio servers ? modparam("presence", "subs_db_mode", 3) modparam ("presence","dburl","/tmp/share/dbtext") 1-st server will handle SUBSCRIBE's and this Subscribe's should be accessible also from 2-nd server. Then PUBLISH'es will be sent to both servers in round robin algorithm. Will Kamailio's work with one shared DB or - i'll got some errors ? Maybe i'm wrong somewhere ? Thanks in advance. Kind regards Ewgeny

2 3

Proxy-Require: privacy error
by Chad 21 Sep '15

21 Sep '15

When a call comes in with a SIP header: "Proxy-Require: privacy" line kamailio throws this error: Aug 21 14:27:57 load1 /usr/sbin/kamailio[29447]: ERROR: <core> [parser/hf.c:224]: dump_hdr_field(): DEBUG: dump_hdr_field: type=18, name=Proxy-Require, body=privacy, parsed=(nil), next=0x7efc42f15150 Aug 21 14:27:57 load1 /usr/sbin/kamailio[29446]: ERROR: <core> [parser/hf.c:224]: dump_hdr_field(): DEBUG: dump_hdr_field: type=18, name=Proxy-Require, body=privacy, parsed=(nil), next=0x7efc42f0a7b0 Aug 21 14:27:58 load1 /usr/sbin/kamailio[29447]: ERROR: <core> [parser/hf.c:224]: dump_hdr_field(): DEBUG: dump_hdr_field: type=18, name=Proxy-Require, body=privacy, parsed=(nil), next=0x7efc42f13180 Aug 21 14:27:58 load1 /usr/sbin/kamailio[29446]: ERROR: <core> [parser/hf.c:224]: dump_hdr_field(): DEBUG: dump_hdr_field: type=18, name=Proxy-Require, body=privacy, parsed=(nil), next=0x7efc42f0dfb8 Anyone know why that happens or how to fix it? -- ^C Chad

2 5

Fw: Re: Busy Tone.. Call not coming
by Mr ankush 19 Sep '15

19 Sep '15

1 0

Dialog module isn't decreasing the profile size, and isn't entering on event routes
by José Seabra 18 Sep '15

18 Sep '15

Hi there, I'm using a dialog module in a small kamailio script that only does routing based on prefix, and relay the invite from one ipaddr to another ip addr (diferent interfaces) using $fs variavel. Now i was introducing the dialog module to limit the number of concurrent calls, and i noticed that it only can increasing the number of dialogs, and it isn't decreasing when receives the "BYE", I also noticed that when kamailio receives "BYE" the dialog event route for state "end" is not executed. To count the number of concurrent calls I'm using the following logic in main route: if (is_method("INVITE")) { setflag(FLT_ACC); # do accounting dlg_manage(); if(get_profile_size("concurrentcalls","local","$avp(s:size)")) { if($avp(s:size) != $null) { xlog("L_INFO", "Number of calls for this server : $avp(s:size) - ID=$ci\n"); if($avp(s:size) >= 15000) { xlog("L_INFO", "Concurrent_max calls exceeded $avp(s:size) for caller '$fU' - R=$ru ID=$ci\n"); sl_send_reply("503", "Channel limit exceeded\n"); exit; } } } set_dlg_profile("concurrentcalls","local"); } Please check out the attachment with logs. Best Regards -- José Seabra

2 5

Issue with too many "listen" statements
by Sven Neuhaus 18 Sep '15

18 Sep '15

Hi, we've observed a bug with Kamailio (we are using 4.3.1): When using more than 81 "listen" statements, Kamailio starts acting up. In our case, it handles ACK packets (that follow "200 OK" messages) incorrectly: It forwards them to itself (src ip == dst ip) in a garbled form (on the loopback interface). We need more than 80 "listen" statements at the moment so I hope there's a way to increase the limit substantially. The number of file handles has been set to 32000 btw. Regards, -Sven Neuhaus

2 6

Adding user to kamailio database
by Priyaranjan Nayak 17 Sep '15

17 Sep '15

Hi All, I wanted to use kamailio with authorization. How can I add public identity and private identity to kamailio database for a user ? Thanks Priyaranjan

2 1

Hex to Dec conversion
by Yufei Tao 17 Sep '15

17 Sep '15

Hi Daniel, I've tested the patch on top of v4.2.5 and it works. Thank you very much! Yufei

1 0

Re: [SR-Users] Hex to Dec conversion
by Yufei Tao 17 Sep '15

17 Sep '15

Hi, Thanks for the replies! The first thing I looked at was the encode/decode.hexa transformations but it only transforms between ASCII characters and Hex numbers. Then I used exec_avp to call a bash command (for example, 'echo $((0x123))' gives you 291) which works. But calling something external may not be optimal I thought? I found OpenSIPS has hex2dec and dec2hex transformations and wonder if we could have these in Kamailio as well? Cheers, Yufei

2 1

Authentication issue during registration
by Austin Einter 17 Sep '15

17 Sep '15

Hi All I have a typical requirement, where I have a forwarding SBC between an endpoint and kamailio as shown below. Endpoint ----> SBC ------> Kamailio >From endpoint I am sending REGISTER request. It reaches SBC. SBC sends the REGISTER request to Kamailio, Kamailio challenges it (401), and challenge response is received at endpoint through SBC. Next endpoint adds authorization header and sends REGISTER to SBC, SBC forwards it to Kamailio. Now Kamailio again responds with 401. When we analysed Kamailio logs, we can see Kamailio log authorization response token and response token that was sent by Endpoint are same. So my question is, why Kamailio sends 401 repeatedly even if it received proper Authorization header. Is it because Kamailio received REGISTER from IP address different from endpoint. Please guide, how can I avoid this issue. Thanks Austin

3 4

add to wishlist: htable.dump type of value
by Juha Heinanen 16 Sep '15

16 Sep '15

looks like htable.dump does not tell what is the type of the value, e.g. { entry: 53 size: 1 slot: { item: { name: foo::bar value: 0 } } } -- juha

2 7

Next IRC Devel Meeting - Sep 16, 2015
by Daniel-Constantin Mierla 16 Sep '15

16 Sep '15

Hello, I would like to propose organizing the next IRC devel meeting to sync on the plans for Kamailio short term evolution. A wiki page has been created to keep track of what should be discussed there. Feel free to add your suggestions there: * http://www.kamailio.org/wiki/devel/irc-meetings/2015b First proposed date is next week on Wednesday, September 16, at 14:00 UTC (15:00 London, 16:00 Berlin, ...). The date can be changed based on availability of people willing to attend -- add your preferred date and time there. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat

1 2

OT: IIT RTC Conference discount
by Daniel-Constantin Mierla 16 Sep '15

16 Sep '15

Hello, I have some discount code for IIT RTC Conference & Expo, taking place in Chicago, IL, USA, during October 6-8, 2015. It gives an 100USD discount, which can save a bit or make some of the available tickets completely free (like Expo Plus admission). Should someone be interested, contact me directly via email. More details about the event can be found at: * http://www.rtc-conference.com/ I will be at the event during Oct 7 and 8, presenting on the morning of Oct 8, if anyone here coming to the event or happening to be in Chicago area and want to meet and chat about Kamailio, drop me an email as well. Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com

1 0

assign_hf_value, hf_value_exists and exclude_hf_value broken in 4.3.2?
by Björn Bylander 15 Sep '15

15 Sep '15

Hello, 4.3.1 works well for us apart from the issue fixed by 93b297e16134b0e74cf83e3604da01355a52e700. Since 93b297e16134b0e74cf83e3604da01355a52e700 is included in 4.3.2 I tried upgrading one of our servers and now Kamailio won't even start as it apparently finds the way assign_hf_value, hf_value_exists and exclude_hf_value are used in our configuration to be incorrect. I enabled debug logging (WITH_DEBUG) and found the following: > 0(1894) DEBUG: <core> [route.c:872]: fix_actions(): fixing assign_hf_value() > 0(1894) ERROR: textopsx [textopsx.c:596]: fixup_hname_param(): ERROR: textops: cannot parse header near 'Privacy' > 0(1894) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:642 > 0(1894) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:644 > 0(1894) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:661 > ERROR: error -6 while trying to fix configuration Line 642 looks like this: assign_hf_value("Privacy", "id") Commenting it out leads to the following output: > 0(2217) DEBUG: <core> [route.c:872]: fix_actions(): fixing hf_value_exists() > 0(2217) ERROR: textopsx [textopsx.c:596]: fixup_hname_param(): ERROR: textops: cannot parse header near 'Privacy' > 0(2217) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:1016 > 0(2217) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:1019 > 0(2217) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:1023 > ERROR: error -6 while trying to fix configuration Line 1016 looks like this: if (hf_value_exists("Privacy", "none")) { Commenting it out leads to the following output: > 0(2292) DEBUG: <core> [route.c:872]: fix_actions(): fixing exclude_hf_value() > 0(2292) ERROR: textopsx [textopsx.c:596]: fixup_hname_param(): ERROR: textops: cannot parse header near 'Accept' > 0(2292) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:1020 > 0(2292) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:1023 > ERROR: error -6 while trying to fix configuration Lines 1020 and 1021 look like this exclude_hf_value("Accept", "application/media_control+xml"); exclude_hf_value("Accept", "application/x-broadworks-call-center+xml"); Commenting them out makes Kamailio start without complaining. Btw, "kamailio -c" thinks the configuration file is fine. So, is our use of assign_hf_value, hf_value_exists and exclude_hf_value incorrect (looking at the textopsx documentation I can't see how) or was a bug introduced with 4.3.2 which causes this behaviour? Regards, Björn Bylander

2 1

Kamailio challenges repeatedly
by Austin Einter 15 Sep '15

15 Sep '15

I am trying to register with Kamailio server from my custom endpoint. I have below call flows Register -> 401 Register -> 401 When I saw Kamailio log, I do not see any error. Looks auth response is fine. Then why 401 repeatedly. Log is given blow. Please guide to fix this issue. Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: auth_db [authorize.c:208]: get_ha1(): HA1 string calculated: 8749f9da135d71526725a337008df1d5 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: auth [api.c:211]: auth_check_response(): check_response: Our result = '4aa70d676021329550b3d17e17238fac' Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: auth [api.c:218]: auth_check_response(): check_response: Authorization is OK Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:81]: db_free_columns(): freeing 1 columns Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:85]: db_free_columns(): freeing RES_NAMES[0] at 0x7f8a24d5e1d0 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:94]: db_free_columns(): freeing result names at 0x7f8a24d7ceb0 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:99]: db_free_columns(): freeing result types at 0x7f8a24d7cef0 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:54]: db_free_rows(): freeing 1 rows Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_row.c:97]: db_free_row(): freeing row values at 0x7f8a24d5e260 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:62]: db_free_rows(): freeing rows at 0x7f8a24d5e218 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:136]: db_free_result(): freeing result set at 0x7f8a24d7ce18 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: auth [challenge.c:127]: get_challenge_hf(): build_challenge_hf: realm='10.10.64.125' Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: auth [challenge.c:269]: get_challenge_hf(): auth: 'WWW-Authenticate: Digest realm="10.10.64.125", nonce="VfbImFX2x2yEeE8kEuL2IXqW2TgKu+eC"#015#012' Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: sl [sl.c:296]: send_reply(): reply in stateless mode (sl) Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [msg_translator.c:206]: check_via_address(): check_via_address(10.3.2.18, 10.3.2.18, 0) Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [tcp_main.c:2283]: tcpconn_send_put(): tcp_send: send from reader (2650 (9)), reusing fd Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [tcp_main.c:2518]: tcpconn_do_send(): tcp_send: sending... Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [tcp_main.c:2552]: tcpconn_do_send(): tcp_send: after real write: c= 0x7f8a1c5dbe78 n=445 fd=9 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [tcp_main.c:2553]: tcpconn_do_send(): tcp_send: buf=#012SIP/2.0 401 Unauthorized#015#012Via: SIP/2.0/TCP 10.3.2.18:6970;branch=z9hG4bK1875333638#015#012From: < sip:262099922700000@10.10.64.125;user=phone>;tag=209355482#015#012To: < sip:+499922700000@10.10.64.125;user=phone>;tag=8345fd11d20ec1ca026994bf51313cb0.a2c6#015#012Call-ID: 1340939517(a)10.10.64.125#015#012CSeq: 3 REGISTER#015#012WWW-Authenticate: Digest realm="10.10.64.125", nonce="VfbImFX2x2yEeE8kEuL2IXqW2TgKu+eC"#015#012Server: kamailio (4.2.5 (x86_64/linux))#015#012Content-Length: 0#015#012#015#012 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) Sep 14 18:41:08 necs107 kamailio[2650]: message repeated 5 times: [ DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)]

2 1

Hex to Dec conversion
by Yufei Tao 14 Sep '15

14 Sep '15

Hi, I want to convert a Hex number string into a Dec number string, e.g. Hex number "123" into Dec number "291". What is the best way? I didn't find any transformation for this. Thank you! Yufei

5 4

Very high load average after upgrade to Kamailio v4.3.2
by M S 14 Sep '15

14 Sep '15

Hi, Over last weekend i upgraded one of my test servers from Kamailio v4.3.1-4d1b65 to latest stable release v4.3.2-07690f and now kamailio goes crazy even with single call (I am using same db and configuration of course). As soon as call establishes system load average (as seen in top command) starts increasing and soon it increases beyond 6.0 and system becomes completely unresponsive, sip messages are no longer being processed by kamailio service. Even after call hangup, system remains under high load. The "htop" indicates that IO Wait time has increased substantially. Any idea what is causing this? For now i have reverted by to v4.3.1-4d1b65 but can go to v4.3.2-07690f again if you need further info or testing. Thank you.

2 6

Concurrent calls after forked invite
by Lukas Hauser 14 Sep '15

14 Sep '15

Hello, I have two UACs registered to kamailio v4.0.4 with the same URI. (bob(a)example.com) Then a third registered UAC (alice(a)example.com) sends an invite to bob(a)example.com. Both bob UACs accept the call and respond with a 200 Ok. The statefull proxy now takes the first one and cancels the second one. In my case I need both responses to be send back to alice through the proxy. I want the Invite to be forked in parallel (works) and both calls to get connected concurrently (does not work). Is there such a feature in the statefull proxy? Can this be done using a stateless proxy? I stumbled on some proposal about a "New Dialog Module Design" [1]. This is excetly what I'm looking for. Is this still just a proposal? Thanks! Lukas PS: I also posted this question in stackoverflow [2] [1] http://www.kamailio.org/dokuwiki/doku.php/modules-new-design:dialog-module-… [2] http://stackoverflow.com/questions/32519551/kamailio-concurrent-calls-after…

2 1

ha1 password authentication without plain text password
by Nabeel 14 Sep '15

14 Sep '15

Hi, My SIP client only uses the 'ha1' password column from the database to authenticate users. It does not require the 'password' column. However, I am not able to register without having the plain text password present in the 'password' column in the database. I need to change this behaviour so that user registration will occur using only the ha1 encoded password column. How can I make this change? I tried commenting out and changing the 'password_column' attribute in the config but could not get it to work.

2 1

selecting memory manager at startup
by Daniel-Constantin Mierla 14 Sep '15

14 Sep '15

Hello, (cross-posting as it is relevant to user community as well). I just pushed a bunch of patches to master branch that will allow selecting the memory manger at kamailio startup, no longer needed to re-compile sources. There are two new command line parameters: * -x name: select the memory manager for shm * -X name: select the memory manager for pkg * if -x is provided but -X is not provided, then pkg uses same memory manager as shm * name can be: * fm - fast malloc (f_malloc) * qm - quick malloc (q_malloc) * default memory manager is fm (what was default so far) Both f_malloc and q_malloc are now compiled, selecting one or the other being possible. Other managers expected to be added in the list soon, especially TLSF, added not that long ago by Camille Oudot. Maybe reviving Doug Lea malloc (existing in dl_malloc.c) worth a try now that can be easily used. The debugging mode for each memory manager is controlled by DB_SR_MEMORY define via Makefile.defs -- right now it is enabled. All enabled memory mangers must be compiled either with or without DB_SR_MEMORY (it won't work to have one memory manger with DB_SR_MEMORY and another one without). Using system malloc for private (pkg) memory is possible by removing the define of PKG_MALLOC from Makefile.defs (same as it was before). This is a mode suitable for troubleshooting using external tools such as valgrind, because it does inline replacement of pkg_malloc() with malloc(), so those tools can track the place of allocation. I plan to add a system malloc custom manager, to allow selecting it with -X (system malloc won't work for shm management, because it is only for private memory). There is no performance impact at runtime, it is only the startup procedure that replaces the pointers to memory management functions. Hopefully with the new mechanism will be able to track easier memory issues -- e.g., qm malloc is better for troubleshooting, using it no longer requires recompilation, just starting kamailio with -x qm. Feedback, especially testing, will be very appreciated! Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat

1 0

no response, re-route calls to a different address
by Al S 14 Sep '15

14 Sep '15

Hi, Can we make Kamailio to re-route calls from an address that does not respond to a different address? Thanks,Al

3 4

Kamailio v4.3.2 Released
by Daniel-Constantin Mierla 10 Sep '15

10 Sep '15

Hello, Kamailio SIP Server v4.3.2 stable release is out. This is a maintenance release of the latest stable branch, 4.3, that includes fixes since release of v4.3.1. There is no change to database schema or configuration language structure that you have to do on previous installations of v4.3.x. Deployments running previous v4.x.x versions are strongly recommended to be upgraded to v4.3.2. For more details about version 4.3.2 (including links and guidelines to download the tarball or from GIT repository), visit: * http://www.kamailio.org/w/2015/09/kamailio-v4-3-2-released/ RPM, Debian/Ubuntu packages will be available soon as well. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Problem with registering softphones
by rasx0＠Safe-mail.net 10 Sep '15

10 Sep '15

Hello! New user here. I'm testing Kamailio installation in testing environment. SIP domain is reachable, Kamailio itself is working fine yet I have a problem with registering softphones. I've tried 3 sip apps and with only one I am able to register with server. Server itself is "vanilla", no changes made. There is user, domain, pwd defined and nothing else. App that successfully connects is X-Lite, after unchecking "Register with domain and receive calls" and checking "Set outbound as domain". Other apps are: Zoiper, Jitsi. After many "checks" and "unchecks" of literary every option I still can't get them to work with me. I'm looking for any kind of hints as of how to get it to register as well as where may I find kamailio logs?

2 1

Releasing Kamailio v4.3.2
by Daniel-Constantin Mierla 10 Sep '15

10 Sep '15

Hello, I am considering to release a new version from branch 4.3 later this week, on Thursday, September 10. If there are issues not yet reported, then use github tracker to do it: - https://github.com/kamailio/kamailio/issues Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat

2 7

No SDP offer answer -> therefore we can not do Rx AAR 1(875) ERROR
by Jan Devai 10 Sep '15

10 Sep '15

Hi Guys, can anybody help us find why we do not get SDP offer answer, see error below: dev_pcscf: 3(879) DEBUG: ims_qos [mod.c:643]: w_rx_aar(): No SDP offer answer -> therefore we can not do Rx AAR 1(875) ERROR: <script>: ACK ( sip:+4620950160102@ims.mnc004.mcc232.3gppnetwork.org <sip:+421950160102@ims.mnc003.mcc231.3gppnetwork.org> (10.50.21.133:5080) to sip:+4620950160101@ims.mnc004.mcc232.3gppnetwork.org;user=phone <sip:+421950160101@ims.mnc003.mcc231.3gppnetwork.org;user=phone>, 3FD60673-55F09407000575C3-18269700) Since we do not get the information the SubscriptionID should be imsi(a)mncxx.mccxx.3gppnetwork.org in our AAR and instead it is contructed as imsi@ip:port which creates a REJECTION in AAA. Any help about where to correct this fault, or where exactly in the code this reception happens and/or anything will be appreciated BIG TIME :-) Thank you Jan

2 1

MEM_JOIN_FREE
by Uri Shacked 09 Sep '15

09 Sep '15

Hi, Does MEM_JOIN_FREE is compiled by default in kamailio 4.X.X ? thanks, Uri

4 6

Kamailio systemd scripts
by Daniel-Constantin Mierla 09 Sep '15

09 Sep '15

Hello, anyone here familiar with systemd that can provide the scripts for kamailio? Systemd is default now on last debian, so would be good to have them as well as I want to close the issue 294: - https://github.com/kamailio/kamailio/issues/294 Any help will be appreciated. Follow up on this list or on the github issue tracker. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat

4 5

Dialog module issue
by Yuriy Gorlichenko 09 Sep '15

09 Sep '15

Hello. I try to manage by dialog module every signaling session, that goes through my proxy. I added newx mod params modparam("dialog", "timeout_avp", "$avp(i:10)") modparam("dialog", "dlg_flag", 4) modparam("dialog", "initial_cbs_inscript", 1) modparam("dialog", "profiles_with_value", "caller") modparam("dialog", "track_cseq_updates", 1) modparam("dialog", "ka_timer", 10) modparam("dialog", "ka_interval", 30 And at request route I added this for all invite methods if (is_method("INVITE")){ $dlg_ctx(timeout_route) = "DIALOG_END"; $avp(i:10)=43200; $dlg_ctx(timeout_bye) = 1; dlg_set_property("ka-src"); dlg_set_property("ka-dst"); dlg_manage(); xlog("L_INFO","Dialog manage is {$ct}\n"); ... } So after this As I think every session must be dialog managed session and every leg of call must be checked by keepalive OPTIONS packets but no one OPTIONS request generated wen session goes through my proxy. thanks

1 0

Using PSTN as "fallback"
by Michael Nielsen 09 Sep '15

09 Sep '15

I have Kamailio running and connected to a PSTN gateway. My subscribers are named ex. +442071234567 - same as their real GSM number from my PSTN gateway. I'm using the standard kamailio.cfg which ships with version 4.3. When I'm trying to dial SIP client to SIP client I would like to have Kamailio route the call internally if a subscriber exists with ex. +442071234567. If no subscriber exists with ex. +442071234567 it should send it to my PSTN gateway. As it is now it seems as if it are trying to both call "internally" and via the PSTN gateway. How should one fix this issue the best way?

3 5

Kamailio crash [receive_fd: EOF on 19]
by SamyGo 09 Sep '15

09 Sep '15

Hi, I'm randomly getting crash in my Kamailio with an error in log files like this: <core> [pass_fd.c:293]: receive_fd(): ERROR: receive_fd: EOF on 19 ALERT: <core> [main.c:775]: handle_sigs(): child process 6853 exited by a signal 11 ALERT: <core> [main.c:778]: handle_sigs(): core was generated INFO: <core> [main.c:790]: handle_sigs(): INFO: terminating due to SIGCHLD *Version of Kamailio is:* [root@kamailio /]#kamailio -V version: kamailio 4.1.4 (x86_64/linux) 39adca 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: 39adca compiled on 03:48:50 Aug 1 2014 with gcc 4.4.7 And gdb bt output is attached in text file. One thing out that is common in all the previous core files is this: #12 0x00000000004a54ab in receive_msg ( buf=0x924600 "INVITE sip:+17036833500@14.131.165.9:5073 SIP/2.0\r\nVia: SIP/2.0/UDP 14.55.2.43:5060;branch=z9hG4bK0eB8f68591a19b9b8f0\r\nFrom: \"Anonymous\" <sip:Anonymous@Anonymous.invalid>;tag=gK0e13e132\r\nTo: <sip:+170"..., len=1018, rcv_info=0x7fff3dbee970) at receive.c:212 #13 0x000000000053c9a8 in udp_rcv_loop () at udp_server.c:536 Does this mean that Kamailio can't understand the From Domain: Anonymous.invalid and hence crashes ? Thanks, Sammy

2 6

Best practise for limiting concurrent calls across a cluster
by jay binks 08 Sep '15

08 Sep '15

Hey all, So I have a cluster of Kamailio servers ( 4 servers currently, soon to be 8 ), I'm looking for suggestions about the BEST way to achieve concurrent call limiting on a per customer basis, across the whole cluster. Initially I mis-read the dialog module documentation and assumed that dialog would provide me this ability, when used with a database. however it seems that the dialog module does not pull data from the DB after the initial startup. I know I can use sql ops to increment and decrement using event_route[dialog:start] and event_route[dialog:end]. however the database I've chosen ( for other valid reasons ) does not have an atomic increment and decrement. I could add yet another DB, but that just adds more failure points. so lets forget my setup, Im wanting suggestions about the BEST setup for this sort of thing. while remaining fault tolerant, and preferably without relying on any single point of failure. Sincerely Jay

7 13

core parameter onsend_route_reply=1 doesn't execute onsend_route block for received replies
by Julia Boudniatsky 07 Sep '15

07 Sep '15

Hello, I set some logs in onsend_route and it works fine for requests. With setting core parameter onsend_route_reply=1 ( yes, on), i expect to see logs for replays also, but it not occurs. Is this a bug or I miss something? version: kamailio 4.2.6 (x86_64/linux) db77ac BR, Julia

2 4

Siremis 4.2 with PHP 5.6
by Patrick Bezensiertblubb 07 Sep '15

07 Sep '15

2 2

Kamailio + Rtpengine < - > Freeswitch + ZRTP
by Alexandru Covalschi 07 Sep '15

07 Sep '15

Hello! Was trying to perfrom subj interconnection via http://kb.asipto.com/freeswitch:kamailio-3.3.x-freeswitch-1.2.x-sbс <http://kb.asipto.com/freeswitch:kamailio-3.3.x-freeswitch-1.2.x-sbc> via that guide. Kamailio and FS are on same host on Amazon EC2. The issue is - when I have proxy_media=true on FS, ZRTP is OK, but the leg_b user can't hear anything (but his voice is transmitted OK). When I set proxy-media to false the voice is OK, but something is with ZRTP so Jitsi can't establish ZRTP handshake. When I set bypass-media=true on FS both ZRTP and voice established, but quality is sometimes bad and the delay is too big. Anyone has any ideas? Kamailio 4.3, FS 1.4 <http://kb.asipto.com/freeswitch:kamailio-3.3.x-freeswitch-1.2.x-sbc> <http://kb.asipto.com/freeswitch:kamailio-3.3.x-freeswitch-1.2.x-sbc> -- Alexandru Covalschi ABRISS-Solutions VoIP engineer and system administrator phone: +37367398493 web: http://abs-telecom.com/

2 1

Thoughts on setup with Kamailio and FreeSWITCH
by Michael Nielsen 07 Sep '15

07 Sep '15

Hello everyone... I'm testing various ways of setting up Kamailio and FreeSWITCH (as VAS-handler). I'm struggling a bit on what Kamailio should do and FreeSWITCH should do. My basic setup is to handle voicemails, internal calls between subscribers and outgoing calls to a SIP gateway to GSM. My idea is to have Kamailio handle all calls and routing between subscribers and the SIP gateway and only have FreeSWITCH handle voicemail (to save the audio file and e-mail it). How does that sound? Or should I route everything to FreeSWITCH via Kamailio and have FreeSWITCH route calls between subcsribers and SIP gateway as well? What are best practises etc...?

2 1

Question about in call both side redirection
by Андрей Ярин 07 Sep '15

07 Sep '15

Hello (sorry for my bad english) - i try to create voice record service by request. User A call to user B. In call by pressing combination like *55 Kamailio must redirect both sides to asterisk, whitch create dynamic conference room with recording. As i understand i need to use dlg_refer() from dialog module, but in log file i get: Konsole output Sep 4 10:45:14 voipc-node2 /usr/local/sbin/kamailio[18941]: ERROR: dialog [dlg_req_within.c:85]: build_dlg_t(): no contact available Sep 4 10:45:14 voipc-node2 /usr/local/sbin/kamailio[18941]: ERROR: dialog [dlg_transfer.c:188]: dlg_refer_callee(): failed to create dlg_t In script i try to refer with: dlg_refer("callee", "sip:100@10.10.9.209"); dlg_refer("caller", "sip:100@10.10.9.209"); -- Ярин Андрей Инженер ООО "И.С.-Телеком" 8(351)7786878 доб 113 8(351)2555724 доб 113 8(351)2555787 доб 113

2 1

Route all traffic from Kamailio to FreeSWITCH after inital checks...
by Michael Nielsen 07 Sep '15

07 Sep '15

I'm running the standard Debian 7 Kamailio 4.3 package. I've added the following to my kamailio.cfg: #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB #!define WITH_NAT #!define WITH_TLS #!define WITH_ANTIFLOOD After authentication, nat etc. is done is there an easy way to transfer everything else to FreeSWITCH? I've looked at the dispatcher module, but don't know where to put the "transfer" in kamailio.cfg?

3 4

Re: [SR-Users] webrtc
by Slava Bendersky 07 Sep '15

07 Sep '15

Hello Giovanni, I fixed webrtc call working right now. I checked debug again and I so 408 error. There was missing record_route() for first INVITE. Thank you for help. Slava. From: "Giovanni Maruzzelli" <gmaruzz(a)gmail.com> To: "sr-users" <sr-users(a)lists.sip-router.org> Sent: Saturday, 5 September, 2015 07:50:29 Subject: Re: [SR-Users] webrtc First thing, check that you can have a webRTC call directly with FreeSWITCH, without passing by Kamailio. If that works, and it does not work through Kamailio, then provide kamailio config, freeswitch config, and debug log from both. On Sat, Sep 5, 2015 at 12:51 AM, Slava Bendersky < volga629(a)skillsearch.ca > wrote: Hello Everyone, I am trying setup webrtc call with freeswitch. [root@canlvprx01 kamailio]# rpm -qa | grep kamailio kamailio-4.3.1-4.4.fc21.x86_64 Case: INTERNET eth0 | eth1 LAN | Web Browser ---->webrtc ----> kamailio ----> freeswitch Getting this error Sep 4 00:22:06 canlvprx01 /usr/sbin/kamailio[11820]: WARNING: <core> [forward.h:164]: msg_send(): TCP/TLS connection for WebSocket could not be found Sep 4 00:22:10 canlvprx01 /usr/sbin/kamailio[11817]: WARNING: <core> [forward.h:164]: msg_send(): TCP/TLS connection for WebSocket could not be found Sep 4 00:22:14 canlvprx01 /usr/sbin/kamailio[11818]: WARNING: <core> [forward.h:164]: msg_send(): TCP/TLS connection for WebSocket could not be found Tried check debug don't see any thing special. Any help thank you. Please let me know which logs will good to provide. Slava. _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Sincerely, Giovanni Maruzzelli Cell : +39-347-2665618 _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

1 0

Re: [SR-Users] webrtc
by Slava Bendersky 06 Sep '15

06 Sep '15

Hello Giovanni, Here SDP webrtc call traffic capture on kamailio side http://fpaste.org/264289/15798761/ password from paste: kamailio Slava. From: "Giovanni Maruzzelli" <gmaruzz(a)gmail.com> To: "sr-users" <sr-users(a)lists.sip-router.org> Sent: Saturday, 5 September, 2015 07:50:29 Subject: Re: [SR-Users] webrtc First thing, check that you can have a webRTC call directly with FreeSWITCH, without passing by Kamailio. If that works, and it does not work through Kamailio, then provide kamailio config, freeswitch config, and debug log from both. On Sat, Sep 5, 2015 at 12:51 AM, Slava Bendersky < volga629(a)skillsearch.ca > wrote: Hello Everyone, I am trying setup webrtc call with freeswitch. [root@canlvprx01 kamailio]# rpm -qa | grep kamailio kamailio-4.3.1-4.4.fc21.x86_64 Case: INTERNET eth0 | eth1 LAN | Web Browser ---->webrtc ----> kamailio ----> freeswitch Getting this error Sep 4 00:22:06 canlvprx01 /usr/sbin/kamailio[11820]: WARNING: <core> [forward.h:164]: msg_send(): TCP/TLS connection for WebSocket could not be found Sep 4 00:22:10 canlvprx01 /usr/sbin/kamailio[11817]: WARNING: <core> [forward.h:164]: msg_send(): TCP/TLS connection for WebSocket could not be found Sep 4 00:22:14 canlvprx01 /usr/sbin/kamailio[11818]: WARNING: <core> [forward.h:164]: msg_send(): TCP/TLS connection for WebSocket could not be found Tried check debug don't see any thing special. Any help thank you. Please let me know which logs will good to provide. Slava. _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Sincerely, Giovanni Maruzzelli Cell : +39-347-2665618 _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

1 0

Topoh configuration question
by Asgaroth 06 Sep '15

06 Sep '15

Hi all, I have a quick question with regards the topoh module, is it possible to have the topoh module only operate on a particular interface and direction. I have some edge proxies and I am trying out the topoh module, what I see happen is that messages originating from behind/inside the edge proxy is topoh'd out, which is exactly what I was looking for, but it appears to do the same for messages originating from the wild, so messages pushed in behind/inside the proxy is also encoded, which is not what I was expecting. Is it possible to configure the topoh module to activate for messages being sent out of the edge proxy into the "wild", but not the other way around, or, decode if it finds an encoded messages who's destination is "behind" the proxy. Any thoughts are much appreciated. Thanks

2 1

webrtc
by Slava Bendersky 05 Sep '15

05 Sep '15

Hello Everyone, I am trying setup webrtc call with freeswitch. [root@canlvprx01 kamailio]# rpm -qa | grep kamailio kamailio-4.3.1-4.4.fc21.x86_64 Case: INTERNET eth0 | eth1 LAN | Web Browser ---->webrtc ----> kamailio ----> freeswitch Getting this error Sep 4 00:22:06 canlvprx01 /usr/sbin/kamailio[11820]: WARNING: <core> [forward.h:164]: msg_send(): TCP/TLS connection for WebSocket could not be found Sep 4 00:22:10 canlvprx01 /usr/sbin/kamailio[11817]: WARNING: <core> [forward.h:164]: msg_send(): TCP/TLS connection for WebSocket could not be found Sep 4 00:22:14 canlvprx01 /usr/sbin/kamailio[11818]: WARNING: <core> [forward.h:164]: msg_send(): TCP/TLS connection for WebSocket could not be found Tried check debug don't see any thing special. Any help thank you. Please let me know which logs will good to provide. Slava.

2 1

Re: [SR-Users] CRITICAL log on kamailio startup
by Nuno Reis 04 Sep '15

04 Sep '15

Good morning. Has anyone seen this too? Looking forward to hear from you. BR, -- *Nuno Miguel Reis* | *Unified Communication** Systems* M. +351 913907481 | nreis(a)wavecom.pt WAVECOM-Soluções Rádio, S.A. Cacia Park | Rua do Progresso, Lote 15 3800-639 AVEIRO | Portugal T. +351 309 700 225 | F. +351 234 919 191 *GPS <http://maps.google.com/maps/ms?msa=0&msid=202333747613191340808.0004b4b227a…> | www.wavecom.pt <http://www.wavecom.pt/>** <http://www.wavecom.pt/>* <http://www.wavecom.pt/> <http://www.wavecom.pt/pt/> On Fri, Aug 14, 2015 at 1:41 AM, Nuno Reis <nreis(a)wavecom.pt> wrote: > Hi guys. > > I've noticed this CRITICAL log line on kamailio startup: > > CRITICAL: dialog [dlg_cb.c:137]: register_dlgcb(): DLGCB_CREATED type > registered after shutdown!?! > > > This line started to show up after upgrade from 4.2.x to 4.3 and now to > 4.3.1. > Everything seems to be working fine and a really don't see any harm > anywhere. > Could you please comment on this? > > Cheers, > > -- > > *Nuno Miguel Reis* | *Unified Communication** Systems* > M. +351 913907481 | nreis(a)wavecom.pt > WAVECOM-Soluções Rádio, S.A. > Cacia Park | Rua do Progresso, Lote 15 > 3800-639 AVEIRO | Portugal > T. +351 309 700 225 | F. +351 234 919 191 > *GPS > <http://maps.google.com/maps/ms?msa=0&msid=202333747613191340808.0004b4b227a…> > | www.wavecom.pt <http://www.wavecom.pt/>** <http://www.wavecom.pt/>* > > <http://www.wavecom.pt/> > <http://www.wavecom.pt/pt/> > > >

2 2

Sounds works differently on different clients.
by Michael Nielsen 04 Sep '15

04 Sep '15

This is my setup: Kamailio -> FreeSWITCH (for voicemail) ...SIP gateway for connecting GSM So every call is routed directly via Kamailio - between SIP clients and in/out from the GSM space. Testing with a cellular phone as one client and X-Lite on Mac OS X as the other - everything works. Testing with a cellular phone as one client and Bria on iOS as the other - everything works except there's no sounds coming into Bria. The person on the cellular can hear everything (sound coming from Bria), but Bria client cannot hear sound from cellular phone. Is it something to do with codec or could it be something else?

2 3

408 Request Timeout
by vamsi 04 Sep '15

04 Sep '15

I am an web developer and want to create a WEBRTC application. My knowledge level in SIP is beginner. I want my application to talk to kamailio and in process of setting up kamailio by following the below articles. http://nil.uniza.sk/sip/kamailio/configuring-kamailio-4x-websocket http://kamailio.org/docs/modules/4.3.x/modules/websocket.html I was able to connect (using try.jssp.net) to kamailio as multiple clients for initial setup and successfully able to get voice and video working. But I'm unable to send messages between clients and receive "408 Request Timeout" error. I have the presence and presence_xml modules loaded and have the # ----- mi_fifo params ----- modparam("mi_fifo", "fifo_name", "/var/run/kamailio/kamailio_fifo") # ----- ctl params ----- modparam("ctl", "binrpc", "unix:/var/run/kamailio/kamailio_ctl") Below is the log. Any help is appreciated. Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a76298] refcnt [2] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a76298] refcnt [1] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[AUTH] c=[/usr/local/etc/kamailio/kamailio.cfg] l=825 a=2 n=exit Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [xavp.c:446]: xavp_destroy_list(): destroying xavp list (nil) Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [receive.c:278]: receive_msg(): cleaning up Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [tcp_read.c:1153]: ws_process_msg(): WebSocket Message: [[>>>#012??#002?E?<<<]] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: websocket [ws_conn.c:429]: wsconn_get(): wsconn_get for id [2] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: websocket [ws_conn.c:437]: wsconn_get(): wsconn_get returns wsc [0x7f06a2a76298] refcnt [2] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: websocket [ws_frame.c:415]: decode_and_validate_ws_frame(): decoding WebSocket frame Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: websocket [ws_frame.c:456]: decode_and_validate_ws_frame(): supported non-control frame: 0x1 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: websocket [ws_frame.c:555]: decode_and_validate_ws_frame(): Rx (decoded): MESSAGE sip:abc123@ip-205-64-10.dqa.capitalone.com SIP/2.0#015#012Via: SIP/2.0/WS kjh0uotuqma6.invalid;branch=z9hG4bK9552000#015#012Max-Forwards: 69#015#012To: <sip:abc123@ip-205-64-10.dqa.capitalone.com>#015#012From: "xyz987" <sip:xyz987@ip-205-64-10.test.com:8088>;tag=c1joq54vne#015#012Call-ID: orel8as144p4ebuuf96n#015#012CSeq: 1977 MESSAGE#015#012Proxy-Authorization: Digest algorithm=MD5, username="xyz987", realm="ip-205-64-10.test.com", nonce="Vee3iFXntlzqK/kDTxUAIxwI55RzH/ll", uri=" sip:abc123@ip-205-64-10.test.com", response="0d513943ed7a0234b7016c5f4546b0b7"#015#012Content-Type: text/plain#015#012Allow: INVITE,ACK,CANCEL,BYE,UPDATE,MESSAGE,OPTIONS,REFER#015#012Supported: outbound#015#012User-Agent: JsSIP 0.7.4#015#012Content-Length: 13#015#012#015#012samplemsgwork Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: websocket [ws_frame.c:659]: ws_frame_receive(): Rx SIP message:#012MESSAGE sip:abc123@ip-10-255-54-20.test.com SIP/2.0#015#012Via: SIP/2.0/WS kjh0uotuqma6.invalid;branch=z9hG4bK9552000#015#012Max-Forwards: 69#015#012To: <sip:abc123@ip-10-255-54-20.test.com>#015#012From: "xyz987" < sip:xyz987@ip-10-255-54-20.test.com:8088>;tag=c1joq54vne#015#012Call-ID: orel8as144p4ebuuf96n#015#012CSeq: 1977 MESSAGE#015#012Proxy-Authorization: Digest algorithm=MD5, username="xyz987", realm="ip-10-255-54-20.test.com", nonce="Vee3iFXntlzqK/kDTxUAIxwI55RzH/ll", uri=" sip:abc123@ip-10-255-54-20.test.com", response="0d513943ed7a0234b7016c5f4546b0b7"#015#012Content-Type: text/plain#015#012Allow: INVITE,ACK,CANCEL,BYE,UPDATE,MESSAGE,OPTIONS,REFER#015#012Supported: outbound#015#012User-Agent: JsSIP 0.7.4#015#012Content-Length: 13#015#012#015#012samplemsgwork Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a76298] refcnt [2] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a76298] refcnt [1] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:606]: parse_msg(): SIP Request: Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:608]: parse_msg(): method: <MESSAGE> Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:610]: parse_msg(): uri: < sip:abc123@ip-10-255-54-20.test.com> Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:612]: parse_msg(): version: <SIP/2.0> Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK9552000>; state=16 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/parse_via.c:2642]: parse_via(): end of header reached, state=5 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:496]: parse_headers(): parse_headers: Via found, flags=2 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:498]: parse_headers(): parse_headers: this is the first via Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [receive.c:134]: receive_msg(): After parse_msg... Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [receive.c:177]: receive_msg(): preparing to run routing scripts... Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=506 a=5 n=route Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[REQINIT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=639 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[REQINIT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=634 a=25 n=mf_process_maxfwd_header Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: maxfwd [mf_funcs.c:85]: is_maxfwd_present(): value = 69 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[REQINIT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=644 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[REQINIT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=639 a=25 n=is_method Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[REQINIT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=648 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[REQINIT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=644 a=26 n=sanity_check Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=10 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:173]: get_hdr_field(): DEBUG: get_hdr_field: <To> [46]; uri=[sip:abc123@ip-10-255-54-20.test.com] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:175]: get_hdr_field(): DEBUG: to body [< sip:abc123@ip-10-255-54-20.test.com>#015#012] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:153]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <1977> <MESSAGE> Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:187]: get_hdr_field(): DEBUG: get_hdr_body : content_length=13 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:89]: get_hdr_field(): found end of header Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/parse_addr_spec.c:172]: parse_to_param(): DEBUG: add_param: tag=c1joq54vne Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=29 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: sanity [mod_sanity.c:248]: w_sanity_check(): sanity checks result: 1 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=529 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=509 a=25 n=nat_uac_test Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=514 a=55 n=force_rport Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=524 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=515 a=25 n=is_method Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=524 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=519 a=24 n=add_contact_alias Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: nathelper [nathelper.c:958]: add_contact_alias_0_f(): no contact header Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=529 a=5 n=route Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[NATDETECT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=846 a=55 n=force_rport Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[NATDETECT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=857 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[NATDETECT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=847 a=25 n=nat_uac_test Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[NATDETECT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=853 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[NATDETECT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=848 a=25 n=is_method Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[NATDETECT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=853 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[NATDETECT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=851 a=24 n=is_first_hop Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: siputils [sipops.c:159]: w_is_first_hop(): no 2nd via found - first hop Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[NATDETECT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=852 a=24 n=set_contact_alias Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[NATDETECT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=854 a=39 n=setflag Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[NATDETECT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=857 a=2 n=return Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=540 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=532 a=25 n=is_method Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=540 a=5 n=route Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[WITHINDLG] c=[/usr/local/etc/kamailio/kamailio.cfg] l=654 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[WITHINDLG] c=[/usr/local/etc/kamailio/kamailio.cfg] l=652 a=24 n=has_totag Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: siputils [checks.c:97]: has_totag(): no totag Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[WITHINDLG] c=[/usr/local/etc/kamailio/kamailio.cfg] l=652 a=2 n=return Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=549 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=545 a=24 n=t_precheck_trans Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=549 a=24 n=t_check_trans Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: tm [t_lookup.c:1011]: t_check_msg(): DEBUG: t_check_msg: msg id=4 global id=3 T start=(nil) Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: tm [t_lookup.c:466]: t_lookup_request(): t_lookup_request: start searching: hash=65389, isACK=0 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: tm [t_lookup.c:424]: matching_3261(): DEBUG: RFC3261 transaction matching failed Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: tm [t_lookup.c:648]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: tm [t_lookup.c:1080]: t_check_msg(): DEBUG: t_check_msg: msg id=4 global id=4 T end=(nil) Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=552 a=5 n=route Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[AUTH] c=[/usr/local/etc/kamailio/kamailio.cfg] l=833 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[AUTH] c=[/usr/local/etc/kamailio/kamailio.cfg] l=820 a=25 n=is_method Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [socket_info.c:563]: grep_sock_info(): checking if host==us: 31==12 && [ ip-10-255-54-20.test.com] == [10.205.64.10] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [socket_info.c:566]: grep_sock_info(): checking if port 8088 (advertise 0) matches port 8088 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [socket_info.c:563]: grep_sock_info(): checking if host==us: 31==12 && [ ip-10-255-54-20.test.com] == [10.205.64.10] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [socket_info.c:566]: grep_sock_info(): checking if port 8088 (advertise 0) matches port 8088 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [socket_info.c:563]: grep_sock_info(): checking if host==us: 31==12 && [ ip-10-255-54-20.test.com] == [10.205.64.10] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [socket_info.c:566]: grep_sock_info(): checking if port 8080 (advertise 0) matches port 8088 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [socket_info.c:563]: grep_sock_info(): checking if host==us: 31==12 && [ ip-10-255-54-20.test.com] == [10.205.64.10] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [socket_info.c:566]: grep_sock_info(): checking if port 5061 (advertise 0) matches port 8088 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [socket_info.c:563]: grep_sock_info(): checking if host==us: 31==12 && [ ip-10-255-54-20.test.com] == [10.205.64.10] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [socket_info.c:566]: grep_sock_info(): checking if port 4443 (advertise 0) matches port 8088 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[AUTH] c=[/usr/local/etc/kamailio/kamailio.cfg] l=828 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[AUTH] c=[/usr/local/etc/kamailio/kamailio.cfg] l=823 a=27 n=auth_check Sep 2 22:54:20 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:457]: wsconn_get_list(): wsconn_get_list Sep 2 22:54:20 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a775a8] prev => [(nil)] next => [0x7f06a2a76298] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a76298] prev => [0x7f06a2a775a8] next => [(nil)] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a775a8] id [1] ref++ Sep 2 22:54:20 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a76298] id [2] ref++ Sep 2 22:54:25 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:501]: wsconn_get_list(): wsconn_get_list returns list [0x7f06ab4f8350] with [2] members Sep 2 22:54:25 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:511]: wsconn_put_list(): wsconn_put_list [0x7f06ab4f8350] Sep 2 22:54:25 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a775a8] refcnt [2] Sep 2 22:54:25 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a775a8] refcnt [1] Sep 2 22:54:25 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a76298] refcnt [2] Sep 2 22:54:25 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a76298] refcnt [1] Sep 2 22:54:26 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [io_wait.h:598]: io_watch_del(): DBG: io_watch_del (0xa40820, 9, -1, 0x10) fd_no=2 called Sep 2 22:54:26 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [tcp_read.c:1450]: release_tcpconn(): releasing con 0x7f06a2a8c3b8, state 1, fd=9, id=2 Sep 2 22:54:26 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [tcp_read.c:1451]: release_tcpconn(): extra_data (nil) Sep 2 22:54:26 ip-10-255-54-20 kamailio[10178]: DEBUG: <core> [tcp_main.c:3243]: handle_tcp_child(): reader response= 7f06a2a8c3b8, 1 from 3 Sep 2 22:54:26 ip-10-255-54-20 kamailio[10178]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0x9fc580, 34, 2, 0x7f06a2a8c3b8), fd_no=23 Sep 2 22:54:26 ip-10-255-54-20 kamailio[10178]: DEBUG: <core> [tcp_main.c:3370]: handle_tcp_child(): CONN_RELEASE 0x7f06a2a8c3b8 refcnt= 1 Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:457]: wsconn_get_list(): wsconn_get_list Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a775a8] prev => [(nil)] next => [0x7f06a2a76298] Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a76298] prev => [0x7f06a2a775a8] next => [(nil)] Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a775a8] id [1] ref++ Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a76298] id [2] ref++ Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:501]: wsconn_get_list(): wsconn_get_list returns list [0x7f06ab4f8350] with [2] members Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:511]: wsconn_put_list(): wsconn_put_list [0x7f06ab4f8350] Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a775a8] refcnt [2] Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a775a8] refcnt [1] Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a76298] refcnt [2] Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a76298] refcnt [1] Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:457]: wsconn_get_list(): wsconn_get_list Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a775a8] prev => [(nil)] next => [0x7f06a2a76298] Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a76298] prev => [0x7f06a2a775a8] next => [(nil)] Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a775a8] id [1] ref++ Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a76298] id [2] ref++ Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:501]: wsconn_get_list(): wsconn_get_list returns list [0x7f06ab4f8350] with [2] members Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:511]: wsconn_put_list(): wsconn_put_list [0x7f06ab4f8350] Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a775a8] refcnt [2] Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a775a8] refcnt [1] Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a76298] refcnt [2] Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a76298] refcnt [1] Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:457]: wsconn_get_list(): wsconn_get_list Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a775a8] prev => [(nil)] next => [0x7f06a2a76298] Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a76298] prev => [0x7f06a2a775a8] next => [(nil)] Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a775a8] id [1] ref++ Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a76298] id [2] ref++ Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:501]: wsconn_get_list(): wsconn_get_list returns list [0x7f06ab4f8350] with [2] members Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:511]: wsconn_put_list(): wsconn_put_list [0x7f06ab4f8350] Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a775a8] refcnt [2] Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a775a8] refcnt [1] Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a76298] refcnt [2] Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a76298] refcnt [1] Sep 2 22:54:29 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:457]: wsconn_get_list(): wsconn_get_list Sep 2 22:54:29 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a775a8] prev => [(nil)] next => [0x7f06a2a76298] Sep 2 22:54:29 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a76298] prev => [0x7f06a2a775a8] next => [(nil)] Sep 2 22:54:29 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a775a8] id [1] ref++ Sep 2 22:54:29 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a76298] id [2] ref++ Sep 2 22:54:31 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:501]: wsconn_get_list(): wsconn_get_list returns list [0x7f06ab4f8350] with [2] members Sep 2 22:54:31 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:511]: wsconn_put_list(): wsconn_put_list [0x7f06ab4f8350] Sep 2 22:54:31 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a775a8] refcnt [2] Sep 2 22:54:31 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a775a8] refcnt [1] Sep 2 22:54:31 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a76298] refcnt [2] Sep 2 22:54:31 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a76298] refcnt [1] Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: tm [t_reply.c:1230]: t_should_relay_response(): ->>>>>>>>> T_code=0, new_code=408 Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: tm [t_reply.c:1748]: relay_reply(): DEBUG: relay_reply: branch=0, save=0, relay=0 icode=0 Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: <core> [msg_translator.c:158]: check_via_address(): (172.18.116.115, kjh0uotuqma6.invalid, 0) Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: <core> [mem/shm_mem.c:101]: _shm_resize(): WARNING:vqm_resize: resize(0) called Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: websocket [ws_conn.c:429]: wsconn_get(): wsconn_get for id [2] Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: websocket [ws_conn.c:437]: wsconn_get(): wsconn_get returns wsc [0x7f06a2a76298] refcnt [2] Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: websocket [ws_frame.c:751]: ws_frame_transmit(): Tx message:#012SIP/2.0 408 Request Timeout#015#012Via: SIP/2.0/WS kjh0uotuqma6.invalid;branch=z9hG4bK2462101;rport=59540;received=172.18.116.115#015#012To: <sip:abc123@ip-10-255-54-20.test.com>;tag=b44d120c617c843b219e52eae8b5e9ff-3dde#015#012From: "xyz987" <sip:xyz987@ip-10-255-54-20.test.com:8088>;tag=5qg1sitf3i#015#012Call-ID: orel8dhn00r81cega00f#015#012CSeq: 862 MESSAGE#015#012Server: kamailio (4.4.0-dev2 (x86_64/linux))#015#012Content-Length: 0#015#012#015#012 Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: websocket [ws_frame.c:150]: encode_and_send_ws_frame(): encoding WebSocket frame Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: websocket [ws_frame.c:181]: encode_and_send_ws_frame(): supported non-control frame: 0x1 Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: <core> [tcp_main.c:2211]: tcpconn_send_put(): tcp connection found (0x7f06a2a8c3b8), acquiring fd Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: <core> [tcp_main.c:2221]: tcpconn_send_put(): c=0x7f06a2a8c3b8, n=16 Sep 2 22:54:31 ip-10-255-54-20 kamailio[10178]: DEBUG: <core> [tcp_main.c:3476]: handle_ser_child(): read response= 7f06a2a8c3b8, 2, fd -1 from 5 (10164) Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: <core> [tcp_main.c:2251]: tcpconn_send_put(): after receive_fd: c= 0x7f06a2a8c3b8 n=8 fd=8 Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: <core> [tcp_main.c:2430]: tcpconn_do_send(): sending... Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: <core> [tcp_main.c:2464]: tcpconn_do_send(): after real write: c= 0x7f06a2a8c3b8 n=419 fd=8 Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: <core> [tcp_main.c:2465]: tcpconn_do_send(): buf=#012?~#001?SIP/2.0 408 Request Timeout#015#012Via: SIP/2.0/WS kjh0uotuqma6.invalid;branch=z9hG4bK2462101;rport=59540;received=172.18.116.115#015#012To: <sip:abc123@ip-10-255-54-20.test.com>;tag=b44d120c617c843b219e52eae8b5e9ff-3dde#015#012From: "xyz987" <sip:xyz987@ip-10-255-54-20.test.com:8088>;tag=5qg1sitf3i#015#012Call-ID: orel8dhn00r81cega00f#015#012CSeq: 862 MESSAGE#015#012Server: kamailio (4.4.0-dev2 (x86_64/linux))#015#012Content-Length: 0#015#012#015#012 Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a76298] refcnt [2] Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a76298] refcnt [1] Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:457]: wsconn_get_list(): wsconn_get_list Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a775a8] prev => [(nil)] next => [0x7f06a2a76298] Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a76298] prev => [0x7f06a2a775a8] next => [(nil)] Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a775a8] id [1] ref++ Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a76298] id [2] ref++ Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:501]: wsconn_get_list(): wsconn_get_list returns list [0x7f06ab4f8350] with [2] members Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:511]: wsconn_put_list(): wsconn_put_list [0x7f06ab4f8350] Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a775a8] refcnt [2] Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a775a8] refcnt [1] Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a76298] refcnt [2] Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a76298] refcnt [1]

2 2

Kamailio memmory leak after it does not receive response for CANCEL message
by Bui Minh Yen 03 Sep '15

03 Sep '15

Hi everyone, I am using Kamailio-4.1.5 and Kamailio-4.2.5 but with this both version I had a problem: Connection diagrams: SIP client ---- SBC --- Kamailio --- MGC/MGW --- GSM/PSTN subscriber Scenario: - Caller (SIP) make a new call to GSM (PSTN) subscriber - When GSM/PSTN is ringing or not ringing, Caller cancel call (Caller send CANCEL message) - But MGC does not send response message for CANCEL message - After about 120s (fr_inv_timer), Kamailio send 487 Request Terminated to SBC. >From this time, Kamailio have memory leak (tm does not free transactions) I reproduced this bugs 4-5 times and same problem is happen I attached capture file and log when I show shared memory (using kamcmd core.shmmem) and tm statistics (using kamcmd tm.stats). And time Kamailio start memory leak is 08-30-15-10:18:53 Could you help me solve this problem? Thank you so much! -- --------------------------- *Bui Thi Minh Yen*

2 2

A little offtop - a question about Kamailio Admin Book
by Alexandru Covalschi 03 Sep '15

03 Sep '15

Just wanted to ask when will http://www.asipto.com/sw/kamailio-admin-book/ become available in final version? Sorry for offtop, didn't know where to ask about that :) -- Alexandru Covalschi ABRISS-Solutions VoIP engineer and system administrator phone: +37367398493 web: http://abs-telecom.com/

2 1

registered4() is not adding xavp with details of the record
by Andrew Pogrebennyk 03 Sep '15

03 Sep '15

Hi, I was trying to use registered("location", "$ru", 0, 1) Last parameter is the flag according to http://kamailio.org/docs/modules/stable/modules/registrar.html#registrar.f.… flag values is as follows: 1 - set xavp_rcd with value from matched contact But I'm getting NULL instead of ruid.. While the same works after lookup("location"). So I took a quick look into the code and that confirms that registered4 does not add the xavp with details of the record (ruid), i.e. it does not do what the lookup_helper does. Is this done on purpose or an oversight? While fixing this it might be reasonable to introduce a new function for setting the XAVPs and call it from lookup and registered4 functions, especially since we are going to extend the attributes list beyond just ruid, but right now I'm struggling just to understanding how the XAVP should be built.. Ideas? Thanks, Andrew

2 1

during registration nonce expired, after backwards time shift
by Vasiliy Ganchev 03 Sep '15

03 Sep '15

Hi list! (sorry for sending first mail to wrong sub forum) Have a following issue: Server with Kamailio restart with wrong time (why - this is separate part of my investigations), timeshift e.g. for 2 hours in feature. After ntp daemon adjust correct time (move time backwards), Kamailio do not accept REGISTERs, pv_www_authenticate answer with code -4 (nonce expired) I've reade the description of: http://kamailio.org/docs/modules/4.2.x/modules/auth.html#auth.p.nonce_expire and http://kamailio.org/docs/modules/4.2.x/modules/auth.html#auth.p.nonce_auth_… This descriptions mention situation with backwards timeshift from future. As I understand, Kamailio do not authorise the registration, whose nonces where generated in future (before ntp shifted the time). But in my tests, Kamailio do not accept even REGISTER from UA, sent after time shift (with new nonces, that as I expected has to use correct time for nonce generation, and be authorised with no problem). Only Kamailio process restart help to cope with the issue. It looks like for nonce generating Kamailio use old time (in feature, that was before timeshift). I wander, does the Kamailio behave in described case - as is expected? If I am wrong in some of my assumptions, please point out. version: kamailio 4.2.5 Thank in advance! Cheers! -- View this message in context: http://sip-router.1086192.n5.nabble.com/during-registration-nonce-expired-a… Sent from the Users mailing list archive at Nabble.com.

2 12

[Kamailio 4.2] Crash during burn-in test
by Jack Wang 03 Sep '15

03 Sep '15

[Steps] 1. one MCU call multi-endpoints 2. MCU hangup all endpoints repeatedly. And all through Kamailio proxy. [Results] For a while, Kamailio crashed. Followings are related logs: ========================================== Sep 2 19:08:34 ./kamailio[3712]: : tm [t_fwd.c:1632]: t_send_branch(): BUG: t_send_branch: retr. already started for 0x41848fa0 Sep 2 19:08:34 ./kamailio[3712]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL) At this point the related behavior is that Kamailio received two INFO requests simultaneously. I wonder whether this is the cause. And maybe it's related to the later crash? Sep 2 19:08:35 ./kamailio[3713]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 11 Sep 2 19:08:35 ./kamailio[3703]: ALERT: <core> [main.c:784]: handle_sigs(): child process 3704 exited by a signal 11 Sep 2 19:08:35 ./kamailio[3703]: ALERT: <core> [main.c:787]: handle_sigs(): core was generated Sep 2 19:08:35 ./kamailio[3703]: : <core> [mem/f_malloc.c:586]: fm_free(): BUG: fm_free: bad pointer 0x7239b6c4 (out of memory block!), called from tm: h_table.c: free_cell(157) - aborting Any suggestions? Thanks. ==========================================

2 1

Change caller id with Kamailio
by Michael Nielsen 02 Sep '15

02 Sep '15

The same way I can change called party id with $rU, is there also a way to change the caller id of the person making the call?

2 2

Add country code on incoming calls - if not present
by Michael Nielsen 02 Sep '15

02 Sep '15

I've added a custom column in my subscriber table in MySQL - called country_code. This contains +44 etc. for subscribers. Is it possible to, if a subscriber has not entered either + or 00, to append the value from country_code of the specific subscriber to the dialled number? And if the user has dialled 00, to replace it with +.

3 7

Kamailio TLS handshake fails above 6500 TLS connections
by Priyaranjan Nayak 02 Sep '15

02 Sep '15

Hi All, We are trying to make 10000 tls connection with Kamailio server for SIP signaling.When I try beyond 6500 TLS connection then TLS handshake is failing.We are running the kamailio by using below command - kamailio -f kamailio.cfg -N 40 -m 1024 -M 16 NOTE: In kamailio.cfg, we have mentioned tls_max_connections=60000 Could you please guide me, how can I improve the tls connections with kamailio ? Thanks Priyaranjan

2 1

Information
by Reaz Baksh 02 Sep '15

02 Sep '15

Hello I'm looking for information on setting SER up on Ubuntu. I have it installed along with rtpproxy but cannot get any info from this site as all documentation links are not working. What I want to do is to receive a input rtp live stream and restream it out to various TV's and decoders. Is this possible with SER ? Thanks Reaz

2 1

Re: [SR-Users] unsupported route_type 64
by Admin 02 Sep '15

02 Sep '15

Here is the output from "event_route[evapi:message-received]" Aug 30 13:18:49 everest /usr/local/kamailio/sbin/kamailio[3897]: INFO: <script>: Message received in evapi: {"Event":"CGR_AUTH_REPLY","TransactionIndex":39453,"TransactionLabel":1341515504,"MaxSessionTime":60,"Suppliers":"","Error":""} Aug 30 13:18:49 everest /usr/local/kamailio/sbin/kamailio[3897]: INFO: <script>: Event received in evapi: "CGR_AUTH_REPLY" Aug 30 13:19:00 everest /usr/local/kamailio/sbin/kamailio[3891]: ERROR: tmx [t_var.c:521]: pv_get_tm_reply_code(): unsupported route_type 64 Thanks.

3 2

OT: some github stuff
by Daniel-Constantin Mierla 01 Sep '15

01 Sep '15

Hello, wondering if people here can shed some light on few github things: 1) is possible to have a multi-line project description (the text at the top of https://github.com/kamailio/kamailio)? Maybe a special format (I tried to add \n or <br />, but they were displayed as is, not interpreted). I would like to add a short note and a link to a page with commit guidelines (http://www.kamailio.org/wiki/devel/github-contributions), so new contributors make proper formatted commits. Displying it at the top will make it easy to spot, as opposity to adding to readme, which is shown at the bottom. 2) is there any specific content/marker to add to README to have it interpreted as markdown (without adding .md extensions)? Something like a special first or last line, ... It will be displayed nicer, but renaming will result in changing lot of other places (makefiles, deb/rpm specs, etc...) and somehow README is the traditional approach for the kind of this file name for Linux/Unix apps. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com

3 5

Add PSTN gateway with authentication credentials
by Michael Nielsen 01 Sep '15

01 Sep '15

I'm trying to use a PSTN gateway with Kamailio for outbound - and incoming - calls. Everything seems to be routed correctly, except the PSTN gateway denies the call due to missing authentication. How do I add credentials for my PSTN gateway in a secure way? Best regards, Michael

3 6

blocking call in between two kamailio proxy
by sscc 01 Sep '15

01 Sep '15

i have configered kamailio with two domains sscc1.tk and sscc2.tk. it listen on both domains. each domain has users registered with it. user in domain sscc1 1 can call to user in domain sscc2. i want to allow call in between users of same domai. and block call between user of domain sscc1 to domain sscc2. please help -- View this message in context: http://sip-router.1086192.n5.nabble.com/blocking-call-in-between-two-kamail… Sent from the Users mailing list archive at Nabble.com.

3 6

authorize a client in bulk registration
by Al S 01 Sep '15

01 Sep '15

My PBX registered in bulk to Kamailio successfully.PBX --> Register --> kamailioPBX <-- 401 with nonce value <-- kamailioPBX --> Register with nonce and md5 response values --> kamailioBOX <-- 200ok <-- kamailioHowever, when one of the PBX client sends an invite out, kamailio AUTH module does not authorize this client:client (813-111-1111) --> Invite --> kamailio What would be the right way to authorize a 10-digit client to send a call out when a bulk registration and not 10-digit registration is performed. Your assistance in this matter is greatly appreciatedThanks,Al

3 3

Kamailio TLS configuration
by Alexandru Covalschi 30 Aug '15

30 Aug '15

Hello! I'm having problems with Kamailio configuration with TLS. Or, maybe, that's my misunderstanding about how it should work. So, the issue - inbound TLS works just great, I can call everyone in my domain. I have PositiveSSL certificate, so I have such files: calist.crt AddTrustExternalCARoot.crt + COMODORSAAddTrustCA.crt + COMODORSADomainValidationSecureServerCA.crt divided by \n server.key - key server.crt - cert The configuration of tls.cfg [server:default] method = SSLv23 verify_certificate = no require_certificate = no private_key = /etc/ssl/sectel.io.ssl/sip/server.key certificate = /etc/ssl/sectel.io.ssl/sip/server.crt ca_list = /etc/ssl/sectel.io.ssl/sip/calist.crt #crl = /etc/kamailio/crl.pem (however with or without ca_list nothing changes) [client:default] verify_certificate = yes require_certificate = yes And with that configuration when I'm trying to call to ostel.co (public SIP service supporting TLS) from my server I get such error: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS write:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed Putting that in tls.cfg: [client:default] verify_certificate = no require_certificate = no Make everything work. Cross-domain calling is essential and I'm just trying to figure out - what's the problem? Is that my certificate, is that ostel.co certificate or it is just the way it should be? Thanks! -- Alexandru Covalschi ABRISS-Solutions VoIP engineer and system administrator phone: +37367398493 web: http://abs-telecom.com/

3 8

Re: [SR-Users] unsupported route_type 64
by Admin 30 Aug '15

30 Aug '15

Thank you for responding to my post. Here it is. include_file "kamailio-cgrates.cfg" request_route { ... switch ($fU) { case 1001: case 1006: $dlg_var(cgrReqType) = "*prepaid"; break; case 1002: $dlg_var(cgrReqType) = "*postpaid"; break; case 1003: $dlg_var(cgrReqType) = "*pseudoprepaid"; break; default: $dlg_var(cgrReqType) = "*rated"; } $dlg_var(cgrTenant) = "cgrates.org"; $dlg_var(cgrAccount) = $fU; $dlg_var(cgrDestination) = $rU; route(CGRATES_AUTH_REQUEST); # Will be answered in CGRATES_AUTH_REPLY #route(CGRATES_LCR_REQUEST); exit; } # Here will land requests after processing them with CGRateS. # Call RELAY or other routes following this route route[CGRATES_AUTH_REPLY] { if $var(CgrError) != "" { xlog("CGR_AUTH_ERROR: $var(CgrError)"); sl_send_reply("503","CGR_ERROR"); exit; } if $var(CgrMaxSessionTime) != -1 { if $var(CgrMaxSessionTime) == 0 { // Not enough balance, do not allow the call to go through sl_send_reply("403","Insufficient credit"); exit; } else if !dlg_set_timeout("$var(CgrMaxSessionTime)") { sl_send_reply("503","CGR_MAX_SESSION_TIME_ERROR"); exit; } } if $var(CgrSuppliers) != "" { # Enforce the supplier variable to the first one received from CGRateS $dlg_var(cgrSupplier) = $(var(CgrSuppliers){s.select,0,,}); } route(RELAY); } ==================================================================== # kamailio-cgrates.cfg # Kamailio-CGRateS related route blocks # Called on new connection over evapi, should normally be the case of CGRateS engine event_route[evapi:connection-new] { $sht(cgrconn=>cgr) = $evapi(srcaddr) + ":" + $evapi(srcport); # Detect presence of at least one connection } # Called when the connection with CGRateS closes event_route[evapi:connection-closed] { $var(connClosed) = $evapi(srcaddr) + ":" + $evapi(srcport); if $sht(cgrconn=>cgr) == $var(connClosed) { $sht(cgrconn=>cgr) = $null; } } # Message received from CGRateS, dispatch it to own route event_route[evapi:message-received] { json_get_field("$evapi(msg)", "Event", "$var(Event)"); route($(var(Event){s.rm,"})); # String characters are kept by json_get_field, remove them here } # Called by Kamailio on new dialog event_route[dialog:start] { route(CGR_CALL_START); } # Called by Kamailio on dialog end event_route[dialog:end] { route(CGR_CALL_END); } # Called by Kamailio on local disconnect event_route[tm:local-request] { route(CGR_CALL_END); } # Send AUTH_REQUEST to CGRateS route[CGRATES_AUTH_REQUEST] { # Auth INVITEs with CGRateS if $sht(cgrconn=>cgr) == $null { sl_send_reply("503","Charging controller unreachable"); exit; } evapi_async_relay("{\"event\":\"CGR_AUTH_REQUEST\", \"tr_index\":\"$T(id_index)\", \"tr_label\":\"$T(id_label)\", \"cgr_reqtype\":\"$dlg_var(cgrReqType)\", \"cgr_tenant\":\"$dlg_var(cgrTenant)\", \"cgr_account\":\"$dlg_var(cgrAccount)\", \"cgr_destination\":\"$dlg_var(cgrDestination)\", \"cgr_setuptime\":\"$TS\", \"cgr_computelcr\":\"true\"}"); } # Process AUTH_REPLY from CGRateS route[CGR_AUTH_REPLY] { json_get_field("$evapi(msg)", "TransactionIndex", "$var(TransactionIndex)"); json_get_field("$evapi(msg)", "TransactionLabel", "$var(TransactionLabel)"); json_get_field("$evapi(msg)", "MaxSessionTime", "$var(MaxSessionTime)"); json_get_field("$evapi(msg)", "Suppliers", "$var(Suppliers)"); json_get_field("$evapi(msg)", "Error", "$var(Error)"); $var(id_index) = $(var(TransactionIndex){s.int}); $var(id_label) = $(var(TransactionLabel){s.int}); $var(CgrMaxSessionTime) = $(var(MaxSessionTime){s.int}); $var(CgrSuppliers) = $(var(Suppliers){s.rm,"}); $var(CgrError) = $(var(Error){s.rm,"}); t_continue("$var(id_index)", "$var(id_label)", "CGRATES_AUTH_REPLY"); # Unpark the transaction } # Send AUTH_REQUEST to CGRateS route[CGRATES_LCR_REQUEST] { # Auth INVITEs with CGRateS if $sht(cgrconn=>cgr) == $null { sl_send_reply("503","Charging controller unreachable"); exit; } evapi_async_relay("{\"event\":\"CGR_LCR_REQUEST\", \"tr_index\":\"$T(id_index)\", \"tr_label\":\"$T(id_label)\", \"cgr_tenant\":\"$dlg_var(cgrTenant)\", \"cgr_account\":\"$dlg_var(cgrAccount)\", \"cgr_destination\":\"$dlg_var(cgrDestination)\", \"cgr_setuptime\":\"$TS\"}"); } # Process LCR_REPLY from CGRateS route[CGR_LCR_REPLY] { json_get_field("$evapi(msg)", "TransactionIndex", "$var(TransactionIndex)"); json_get_field("$evapi(msg)", "TransactionLabel", "$var(TransactionLabel)"); json_get_field("$evapi(msg)", "MaxSessionTime", "$var(MaxSessionTime)"); json_get_field("$evapi(msg)", "Suppliers", "$var(Suppliers)"); json_get_field("$evapi(msg)", "Error", "$var(Error)"); $var(id_index) = $(var(TransactionIndex){s.int}); $var(id_label) = $(var(TransactionLabel){s.int}); $var(CgrMaxSessionTime) = $(var(MaxSessionTime){s.int}); $var(CgrSuppliers) = $(var(Suppliers){s.rm,"}); $var(CgrError) = $(var(Error){s.rm,"}); t_continue("$var(id_index)", "$var(id_label)", "CGRATES_AUTH_REPLY"); # Unpark the transaction } # CGRateS request for session disconnect route[CGR_SESSION_DISCONNECT] { json_get_field("$evapi(msg)", "HashEntry", "$var(HashEntry)"); json_get_field("$evapi(msg)", "HashId", "$var(HashId)"); json_get_field("$evapi(msg)", "Reason", "$var(Reason)"); jsonrpc_exec('{"jsonrpc":"2.0","id":1, "method":"dlg.end_dlg","params":[$(var(HashEntry){s.rm,"}), $(var(HashId){s.rm,"})]}'); #$jsonrpl($var(reply)); } # Inform CGRateS about CALL_START (start prepaid sessions loops) route[CGR_CALL_START] { if $sht(cgrconn=>cgr) == $null { xlog("Charging controller unreachable"); exit; } evapi_async_relay("{\"event\":\"CGR_CALL_START\", \"callid\":\"$dlg(callid)\", \"from_tag\":\"$dlg(from_tag)\", \"h_entry\":\"$dlg(h_entry)\", \"h_id\":\"$dlg(h_id)\", \"cgr_reqtype\":\"$dlg_var(cgrReqType)\", \"cgr_tenant\":\"$dlg_var(cgrTenant)\", \"cgr_account\":\"$dlg_var(cgrAccount)\", \"cgr_destination\":\"$dlg_var(cgrDestination)\", \"cgr_answertime\":\"$TS\", \"cgr_supplier\":\"$dlg_var(cgrSupplier)\"}"); } # Inform CGRateS about CALL_END (stop debit loops, perform accounting if desired in this way) route[CGR_CALL_END] { if $sht(cgrconn=>cgr) == $null { xlog("Charging controller unreachable"); exit; } $var(callDur) = $TS - $dlg(start_ts); evapi_async_relay("{\"event\":\"CGR_CALL_END\", \"callid\":\"$dlg(callid)\", \"from_tag\":\"$dlg(from_tag)\", \"cgr_reqtype\":\"$dlg_var(cgrReqType)\", \"cgr_tenant\":\"$dlg_var(cgrTenant)\", \"cgr_account\":\"$dlg_var(cgrAccount)\", \"cgr_destination\":\"$dlg_var(cgrDestination)\", \"cgr_answertime\":\"$dlg(start_ts)\", \"cgr_duration\":\"$var(callDur)\", \"cgr_supplier\":\"$dlg_var(cgrSupplier)\", \"cgr_disconnectcause\":\"$T_reply_code\"}"); }

2 1

presence_dialoginfo- first NOTIFY - force_dummy_dialog
by evoip＠ukr.net 29 Aug '15

29 Aug '15

||Hello, we use Kamailio 4.2 with Presence_DIALOGINFO module for BLF notifications (blinking lamps on phone panel). Since version 4.1 Kamailio has a new module parametr " modparam("presence_dialoginfo", "force_dummy_dialog", 1)" - this option generate first NOTIFY to Subscribed phone (without PUBLISH message) and it's lamps became GREEN ( <state>terminated</state>). Without this module parametr the first NOTIFY won't be sent to phone and lamps will stay turned off until first PUBLISH will be handled by presence server. The first NOTIFY sip message with xml body look like this: NOTIFY sip:1005@22.22.22.22:1120 SIP/2.0. To: <sip:1005@11.11.11.11>;tag=867246696. From: <sip:9095@11.11.11.11>;tag=495949c4c25d687c77ca707bd10a0818-5171. CSeq: 2 NOTIFY. Call-ID: 662126467-5060-6(a)BJC.BGI.E.CDD. Route: <sip:10.60.1.3;r2=on;lr=on>, <sip:11.11.11.11;r2=on;lr=on>. Content-Length: 272. User-Agent: kamailio (4.2.3 (x86_64/linux)). Max-Forwards: 70. Event: dialog. Subscription-State: active;expires=600. Content-Type: application/dialog-info+xml. . <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="1" ух state="full" entity="sip:9095@10.60.1.3"> <dialog direction="recipient"> <state>terminated</state> </dialog> </dialog-info> Especially pay attention on XML body. But for some SIP phones this xml body with state = terminated is not enough to turn the BLF lamp on. (for example Grandstream phones). It requires one more or two more fields: "dialog id", "call-id". <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="28" state="full" entity="sip:9093@10.60.1.3"> <dialog id="830b4fd4-c75d-1233-ca9f-0050569560f4" call-id="830b4fd4-c75d-1233-ca9f-0050569560f4" direction="recipient"> <state>terminated</state> </dialog> </dialog-info> The question is how to modify this first NOTIFY XML body message to add "dialog id" and "call-id" to </dialog>. For example latest Kamailio Kazoo fixed that already. :) Kind Regards Ewgeny

4 8

unsupported route_type 64
by Admin 29 Aug '15

29 Aug '15

Hi, I am running Kamailio (4.4.0-dev2 (x86_64/linux)) with cgrates real-time billing application. At the end of a basic call (prepaid to postpaid), I receive the following error: ERROR:tmx [t_var.c:521]:pv_get_tm_reply_code():unsupported route_type 64 8(6740) DEBUG:tmx [t_var.c:526]:pv_get_tm_reply_code():reply code is <0> What does route_type 64 mean? I checked the archive posts (FS#456) and seemed to be fixed in branch 4.1 (part of 4.1.5). Thanks.

2 1

Parser error when enabling siptrace functionality
by Asgaroth 28 Aug '15

28 Aug '15

Hi All, I have a strange issue occuring, when I enable the siptrace functionality within the routing logic, I begin to get a bunch of parser error as show below. Is this normal behaviour or, more than likely, am I doing something wrong? I enable siptrace as follows: request_route { route("InitialMessageChecks"); sip_trace(); setflag(22); ... } event_route[tm:local-request] { sip_trace(); ... } When I enable this functions in the routing logic, I begin to see alot of the following messages in the log file: ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 39) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021® #023ÄÔ#002 ÊÂÕ#035mùLàU{#002> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 39) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021® #023ÄÔ#002 ÊÂÕ#035mùLàUÞž#002> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 35) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021® #023ÄÔ#002 ÊÂÕ#035mùLàU #011#003> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#006y|#023ÄN˜#036ÂÕ#035múLàUÅ±#012> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> Is there any way I can disable seeing these messages? What are these messages? Any thoughts are appreciated. Thanks

2 4

kamailio_fifo
by Sven Juhkam 28 Aug '15

28 Aug '15

After updating kamailio I get: ERROR: Error opening Kamailio's FIFO /var/run/kamailio/kamailio_fifo ERROR: Make sure you have the line 'modparam("mi_fifo", "fifo_name", "/var/run/kamailio/kamailio_fifo")' in your config ERROR: and also have loaded the mi_fifo module. Any solution? Best regards Sven

3 2

BLF state on register
by Loic Chabert 28 Aug '15

28 Aug '15

Hello everyone, I'm trying to reproduce BLF's asterisk fonctionnality with kamailio. With asterisk, on register, NOTIFY message has been sent to all suscribed users. So LED became green. How can i reproduce this function ? I have try to execute a "pua_set_publish()" on register route, but it's not work. My led stay "black", and no notify message has been sent. I have loaded presence, presence_xml, presence_mwi, presence_dialoginfo, pua, pua_dialoginfo, pua_usrloc. Any other module needed ? Thanks, Regards.

2 10

webrtc not working in different networks
by Achintha 28 Aug '15

28 Aug '15

Hi, I have configured kamailio 4.3.1 with mysql ,rtpproxy,websocket modules , then I tried to call through the two extensions using x-lite phone and get the capture. Call is connected. In that test rtp was going through the rtpproxy server, Then I configured jssip to test webrtc in this setup, call is connected I can communicate through the extensions both video and voice only in LAN. IN different networks call is connected but, voice is not hear (rtp not working). Kindly help me to configure this web rtc with kamailio. -- Best Regards.. Achintha

1 0

dmq_usrloc
by Kelvin Chua 28 Aug '15

28 Aug '15

is there any function to trigger replication? i enabled the module and dmq is working for my htables but usrloc is not replicating. "kamctl ul show" does not show anything i used ngrep to trace the KDMQ packets, i can see the frequent exchanges but nothing related to usrloc. am i doing something wrong? Kelvin Chua

3 13

multiple proxies
by Bruce Lefko 27 Aug '15

27 Aug '15

If I want to have multiple kamailio proxies in front of multiple media servers, can I balance them using plain old DNS behind a domain name? If I wanted a specific proxy to be notified about an entire SIP dialog I could set the record route to use the public IP of the proxy that received the initial INVITE. Could I leverage something like route53 tcp healthchecks to know if I should be failing over to another proxy?

3 2

multiple proxies
by Bruce Lefko 27 Aug '15

27 Aug '15

If I want to have multiple kamailio proxies in front of multiple media servers, can I balance them using plain old DNS behind a domain name? If I wanted a specific proxy to be notified about an entire SIP dialog I could set the record route to use the public IP of the proxy that received the initial INVITE. Could I leverage something like route53 tcp healthchecks to know if I should be failing over to another proxy?

1 0

kamailio presence server using db_mongodb as database
by José Seabra 27 Aug '15

27 Aug '15

Hello all, I would like to test my presence server using db_mongodb as database server instead of using mysql, but i don't find any documentation explaining how i can configure mongodb database(data structure) for presence or even for the other kamailio modules. Can someone guide me in this setup? Best Regards -- Cumprimentos José Seabra

2 12

Confusion about various TCP expiry and lifetime parameters
by M S 27 Aug '15

27 Aug '15

Hi, We have a bit of confusion regarding tcp_connecton_timeout core parameter. The documentation says, -- Lifetime in seconds for TCP sessions. TCP sessions which are inactive for longer than *tcp_connection_lifetime* will be closed by Kamailio. -- However we observe a strange behaviour. 1. The connection is NOT closed by Kamailio unless we additionally set "close_expired_tcp" parameter in usrloc module, 2. Secondly, if we set this parameter to a smaller value say 70 seconds while sip register expiry is 600 seconds (and close_expired_tcp parameter enabled in usrloc module), the connection still remains active (tested after keeping it idle for 120 seconds then sending a sip request on this connection, we expected the request to fail but it does not fails). 3. if we set this parameter to greater then sip register value, e.g. 610 seconds and set close_expired_tcp parameter in usrloc, then we observe disconnect after about 8-10 minutes. Whereas we expect it to continue since user is re-registering every 600 seconds. Can you guys explain why this is happening? What keeps a tcp connection active or makes it inactive? We are using websockets (which use TCP at lower layer) and we observe there is no websocket frame sent or received over the tcp connection, yet it remain active after tcp_connection_lifetime in case 2 above and becomes inactive in case 3. We are using Kamailio v4.3.1 SVN Rev. 4717b5 on Debian Wheezy 32bit OS. Please suggest. Thank you.

2 3

IMS Kamailio "477 Unfortunately error on sending to next hop occurred" code sent by the PCSCF
by Victor Huertas Garcia 26 Aug '15

26 Aug '15

Hello everybody, I have tried to perform a call between alice and bob (both registered in the same SCSCF and from the same PCSCF). The INVITE goes all the way as it is supposed: Alice-->PCSCF-->SBC-->SCSCF-->ICSCF-->SCSCF-->SBC-->PCSCF. But when it reaches PCSCF on Network to User direction, this SIP proxy answers with a "477 Unfortunately error on sending to next hop occurred" code just after an exchange with the RTP Proxy (Offer-Answer). At kamailio.cfg (which it is not change from the default config) this exchange is done under Route[RTPRPROXY] in the function: rtpengine_manage("trust-address replace-origin replace-session-connection ICE=remove"); Does anybody know why is complaining (see below) about the server on localhost while it is not configured so? Here you can find the logs from PCSCF: Aug 23 15:10:06 ims rtpengine[556]: [3D504184-55D9D43E00072478-7E0DE700] Received command 'offer' from 192.168.0.108:57522Aug 23 15:10:06 ims rtpengine[556]: [3D504184-55D9D43E00072478-7E0DE700] Creating new callAug 23 15:10:06 ims rtpengine[556]: [3D504184-55D9D43E00072478-7E0DE700] Replying to 'offer' from 192.168.0.108:57522Aug 23 15:10:06 ims /usr/sbin/kamailio[3313]: ERROR: *** cfgtrace:request_route=[RTPPROXY] c=[/etc/kamailio/pcscf/kamailio.cfg] l=813 a=2 n=returnAug 23 15:10:06 ims /usr/sbin/kamailio[3313]: ERROR: *** cfgtrace:request_route=[Term_Initial] c=[/etc/kamailio/pcscf/kamailio.cfg] l=1196 a=24 n=t_relayAug 23 15:10:06 ims /usr/sbin/kamailio[3313]: ERROR: <core> [udp_server.c:550]: udp_send(): sendto(sock,0x7f480e27ed70,1358,0,192.168.0.105:49284,16): Invalid argument(22)Aug 23 15:10:06 ims /usr/sbin/kamailio[3313]: CRITICAL: <core> [udp_server.c:555]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Here you can find the configuration from RTP proxy (/etc/default/ngcp-rtpengine-daemon) and you can see that I am not listening the localhost port at "INTERFACES": RUN_RTPENGINE=yes LISTEN_TCP=25060LISTEN_UDP=12222LISTEN_NG=22222LISTEN_CLI=9900INTERFACES="192.168.0.108"TIMEOUT=60SILENT_TIMEOUT=3600PIDFILE=/var/run/ngcp-rtpengine-daemon.pidFORK=yes# TOS=184TABLE=0# NO_FALLBACK=yes# PORT_MIN=30000# PORT_MAX=50000# REDIS=127.0.0.1:6379# REDIS_DB=1# B2B_URL=http://127.0.0.1:8090/# LOG_LEVEL=6# LOG_FACILITY=daemon# LOG_FACILITY_CDR=daemon# LOG_FACILITY_RTCP=daemon# NUM_THREADS=5# DELETE_DELAY=30# GRAPHITE=9006# GRAPHITE_INTERVAL=60# GRAPHITE_PREFIX=myownprefix# MAX_SESSIONS=5000 And finally the pcscf.cfg: # SIP / UDPlisten=udp:eth0:4060#listen=udp:127.0.0.1:4070listen=udp:127.0.0.1:4060# SIP / TCP (Monitoring)#listen=tcp:127.0.0.1:4060# SIP / TCP/TLS#listen=tls:109.239.57.200:5061# SIP / Websocket #!define MY_WS_PORT 80 listen=tcp:eth0:MY_WS_PORT # SIP / Websocket/TLS#!define MY_WSS_PORT 443#listen=tls:109.239.57.200:MY_WSS_PORT #alias=pcscf-1.imscore.orgalias=pcscf.home-domain.net#alias=proxy.imscore.org#alias=tls:"wss-proxy.imscore.org":443 # Port, where we listen to Traffic#!define PORT 4060 # NUEVO Workshop!#!define SBCPORT 5080#!define PCSCF_URL "sip:pcscf.home-domain.net"#!define TCP_PROCESSES 32 #!subst "/NETWORKNAME/home-domain.net/"#!subst "/HOSTNAME/pcscf.home-domain.net/"#!define HOSTNAME_IP pcscf.home-domain.net#!define HOSTNAME_ESC "pcscf\.home-domain\.net" # SIP-Address of capturing node, if not set, capturing is disabled.##!define CAPTURE_NODE "sip:10.1.8.55" # Allowed IPs for XML-RPC-Queries#!define XMLRPC_WHITELIST_1 "127.0.0.1"##!define XMLRPC_WHITELIST_2 "127.0.0.1"##!define XMLRPC_WHITELIST_3 "127.0.0.1" # Databases:#!define DB_URL "mysql://pcscf:heslo@127.0.0.1/pcscf"##!define DB_URL2 "con2=>mysql://pcscf:heslo@127.0.0.1/pcscf"##!define DB_URL "con1=>mysql://pcscf:heslo@192.168.5.1/pcscf"##!define DB_URL2 "con2=>mysql://pcscf:heslo@10.1.27.217/pcscf" #! Optional: Server-URL for Websocket-Requests##!define WEBSOCKET_WEBSERVER "phone.imscore.org" # NUEVO Workshop!#!subst "/ICID_VALUE_PREFIX/P-CSCFabcd/"#!subst "/ICID_GEN_ADDR/127.0.0.1/" # IP-Adress(es) of the RTP-Proxy##!define RTPPROXY_ADDRESS "udp:10.1.2.186:22222 udp:10.1.27.217:22222"#!define RTPPROXY_ADDRESS "udp:192.168.0.108:22222"## Several features can be enabled using '#!define WITH_FEATURE' directives:## *** To run in debug mode:# - define WITH_DEBUG## *** To enable nat traversal execute:# - define WITH_NAT# - define the connection to the RTP-Proxy: RTPPROXY_ADDRESS## *** To force alls calls through the RTP-Proxy# - this will automagically enable NAT-Traversal# - define FORCE_RTPRELAY## *** To enable IPv4/IPv6 Translation (RTPProxy)# - this will automagically enable NAT-Traversal# - define WITH_RTPIPV4## *** To enable TCP support execute:# - define WITH_TCP## *** To enable TLS support execute:# - adjust CFGDIR/tls.cfg as needed# - define WITH_TLS# - this will automagically enable TCP## *** To enable XMLRPC support execute:# - define WITH_XMLRPC# - this will automagically enable TCP## *** 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 enable the Rx-Interface:# - Configure Rx-Diameter-Interface in pcscf.xml# - define WITH_RX## *** To enable a Homer SIP-Capter-Node:# - define CAPTURE_NODE with a proper address## *** To enable support for the SEMS-SBC# - define WITH_SBC# - configure dispatcher-list with a set of SBC's## *** To enable support for Websocket# - define WITH_WEBSOCKET# - this will automagically enable TCP## Enabled Features for this host:#!define WITH_DEBUG#!define WITH_NAT#!define WITH_NATPING#!define FORCE_RTPRELAY##!define WITH_TLS#!define WITH_XMLRPC#!define WITH_ANTIFLOOD##!define WITH_RX##!define WITH_RX_REG##!define WITH_RX_CALL##!define WITH_TCP##!define WITH_SBC##!define WITH_RTPIPV4#!define WITH_SBC_CALL#!define WITH_REGINFO#!define WITH_WEBSOCKET#!define WITH_IMS_HDR_CACHE Thanks a lot for your attention

2 1

Kamailio dead after INVITE from SIPDROID
by Kowalski Piotr 3 - Hurt 26 Aug '15

26 Aug '15

Hello Community. We have openIMS nodes in our lab. We have Kamailio 4.0 based solution. I registered SIPDROID client (iptel) on Android and JITSI on WINDOWS. When I call from SIPDROID to JITSI following happens: SIP DROID - iptel - client - registration ok, but INVITE attempt towards JITSI (and other clients) does what's below: HSS (every 30 seconds): [root@hss1 kowalp00]# 2015-08-25 12:16:55,468 WARN de.fhg.fokus.diameter.DiameterPeer.transport.Communicator - run Read 3021 before Exception. 2015-08-25 12:16:56,980 ERROR de.fhg.fokus.diameter.DiameterPeer.peer.StateMachine - I_Snd_Conn_Req StateMachine: Peer scscf1.hss.ims.test.pl:3868 not responding to connection attempt 2015-08-25 12:17:26,985 ERROR de.fhg.fokus.diameter.DiameterPeer.peer.StateMachine - I_Snd_Conn_Req StateMachine: Peer scscf1.hss.ims.test.pl:3868 not responding to connection attempt SCSCF: Aug 25 12:24:18 scscf1 /usr/sbin/kamailio[8879]: INFO: <core> [main.c:854]: INFO: signal 15 received Aug 25 12:24:18 scscf1 /usr/sbin/kamailio[8865]: INFO: <core> [main.c:854]: INFO: signal 15 received Aug 25 12:24:18 scscf1 /usr/sbin/kamailio[8803]: INFO: snmpstats [snmpstats.c:410]: The SNMPStats module got the kill signal Aug 25 12:24:18 scscf1 /usr/sbin/kamailio[8803]: INFO: snmpstats [snmpstats.c:414]: Shutting down the AgentX Sub-Agent! Aug 25 12:24:18 scscf1 /usr/sbin/kamailio[8803]: ERROR: ctl [ctl.c:379]: ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: Operation not permitted (1) Aug 25 12:25:18 scscf1 /usr/sbin/kamailio[8803]: : <core> [main.c:697]: BUG: shutdown timeout triggered, dying... Kamailio becomes dead and needs restart. Clients become unregistered. A call from JITSI to SIPDROID it's fine. Any ideas? Piotr Kowalski Starszy Architekt Techniczny Tel. +48 22 699 50 93 Kom. +48 519 123 289 Orange Orange Polska Hurt Badania i Rozwój Sieci i Platform Usługowych Wydział Usług Konwergentnych Obrzeżna 7 /p. 309, 02-691 Warszawa Fax. +48 22 857 99 86 <http://www.hurt-orange.pl/> www.hurt-orange.pl - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Czy musisz drukować tę wiadomość? Pomyśl o środowisku. Korzystaj z e-faktury. Treść tej wiadomości jest własnością Orange Polska i zawiera informacje stanowiące tajemnicę przedsiębiorstwa Orange Polska. Jeżeli nie jesteście Państwo jej adresatem, bądź otrzymaliście ją przez pomyłkę, prosimy o powiadomienie o tym nadawcy oraz trwałe jej usunięcie. Orange Polska Spółka Akcyjna z siedzibą i adresem w Warszawie (02-326) przy Al. Jerozolimskich 160, wpisana do Rejestru Przedsiębiorców prowadzonego przez Sąd Rejonowy dla m.st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego pod numerem 0000010681; REGON 012100784, NIP 526-02-50-995; z pokrytym w całości kapitałem zakładowym wynoszącym 3.937.072.437 złotych.

2 1

Rewrite Invite w/o sdp
by Serge Yuriev 25 Aug '15

25 Aug '15

Hello, Our PBX (Cisco CallManager) uses "late offer" sending invites w/o sdp. After receiving provisional reply 18x it answers prack with sdp I'm trying to realize following scenario: 1 Pbx (invite no sdp) 2 kamailio hold and saves invite 3 send 183 to Pbx 4 get prack with sdp 5 construct new invite from saved one and sdp from prack 6 send it to calee Is this possible? How to save invite for future use? -- Serge via mobile

3 2

dispatcher gateway probing in 4.3
by Joseph Dickson 24 Aug '15

24 Aug '15

Greetings.. I'm fairly new to Kamailio, and am having fun so far... I'm using the latest 4.3 rpm version on Centos 7. I'm using Kamailio to front end a pair of FreeSwitch SBC boxes in an active/active config.. My plan is to use dispatcher to load balance calls between them. This is working fine.. the problem that I'm bumping into is that the gateway probing options in dispatcher seem not to fit my use case.. In addition to the two SBC gateways, I also have a few external gateways that I want to load balance between also using dispatcher. The problem is that I can't send options packets to these gateways -- they don't respond to them. This means I can't just configure dispatcher to probe all gateways (probing_method=1) because it will mark these gateways as inactive.. It looks like every other configuration of probing_method only probes a gateway until the state is determined, and then it stops probing. probing_method=2 does not appear to be used at all in the code.. Am I doing this wrong? Or is this just an area of dispatcher that needs some improvement? Looking at the code, I can probably add the functionality that I need, but I don't want to go that route if I'm just missing how this is usually done.. Thanks, -- *Joseph Dickson* E: jdickson(a)evolvetsi.com

3 5

Request timout - Change value
by Loic Chabert 24 Aug '15

24 Aug '15

Hello everybody, I'm using kamailio as a dispatcher in front of asterisk boxes and i use a failure route if asterisk box does not respond or send 500error. failure_route[RTF_DISPATCH]{ if(t_is_canceled()){ exit(); } if(t_check_status("500") || (t_branch_timeout() && !t_branch_replied())){ xlog("L_WARN","[$fU@$si:$sp]{$rm} Asterisk Box $du is down\n"); ds_mark_dst("ip"); if(ds_next_dst()){ xlog("L_WARN","[$fU@$si:$sp]{$rm} Sending to Asterisk Box - $du\n"); t_on_failure("RTF_DISPATCH"); route(RELAY); exit; } } } As you can see, i check if "t_branch_timeout() && !t_branch_replied()", but where has been stored timeout value ? How can i change it ? For exemple, i need to set 1s, and then, request expired. Thanks, Regards.

2 4

Dialog module - db_fetch_rows
by jay binks 24 Aug '15

24 Aug '15

Hey All, Im just after someone else thoughts on if this is a bug. After reading : http://kamailio.org/docs/modules/3.3.x/modules_k/dialog.html#idp148408 Im lead to understand that setting *modparam("dialog", "db_fetch_rows", 0)* should instruct the dialog module to write dialogs to the DB, but not bother loading them on startup. This sounds like what I'm after. However ever time I set the value to 0, dialogs are still loaded from the DB. a quick dig in the source takes me to the function select_entire_dialog_table in dlg_db_handler.c this chunk of code does not appear to properly implement " if fetch_num_rows == 0 then do nothing " Im after a couple of things from you guys. a) validation that my understanding of what SHOULD happen is correct b) possibly validating that I'm not crazy, and this is actually a bug :) -- Sincerely Jay

2 4

Ims Kamailio issue - "403 Forbidden - You must register first with a S-CSCF"
by Victor Huertas Garcia 23 Aug '15

23 Aug '15

Hello everybody, I have installed an IMS core using Kamailio and FHoSS. In this environment, I am able to successfully register Bob and Alice with the same S-CSCF. However, when I try to make a voice call between Bob and Alice it is not established. The code received is "403 Forbidden - You must register first with a S-CSCF". This code is generated by the P-CSCF because the Contact Header that is checked against the database ("location" table) it is not found. When I look up manually the "location" MySQL table, there are two things that surprise me: - The Contact header (AOR column content) that is included in the INVITE Requet URI when entering in the P-CSCF is present in the table. So why the pcscf_is_registered ("location") returns false? - When Bob registers two Contacts are stored, the first one is the one included in the REGISTER message generated from Bob IMS Client. However, the second Contact is the one present in the 200 OK message (coming from the S-CSCF) which is different from the one present in the REGISTER (the only thing different is the UDP port). Why the S-CSCF (with the default kamailio.cfg) doesn't the Contact header and changes the UDP port? Is this the standard behaviour? I don't think so... Thanks for your attention Regards,

2 3

A question to you, SIP providers: what is your policy on PBXes calling themselves
by Antonio Gómez Soto 23 Aug '15

23 Aug '15

Hello, This is question on PBX behavior, what is the right thing to do, and how do PBX's generally behave. If a user on a phone, dials a number, which happens to be configured on the same phone system (for example another tenant), there are two options: 1. The PBX notices this, and directly connects the phone to the DID on that system (breaking separation of tenants) 2. The PBX sends the call out on the SIP trunk, and the provider-routing sends the call back as an incoming call. What are the pros and cons of each option from the SIP provider point of view? How do PBX's generally behave? Thanks, Antonio PS: I reposted, because the original question was apparently not phrased in a clear way.

3 2

IPSec supporting open source SIP Server
by Priyaranjan Nayak 23 Aug '15

23 Aug '15

Hi All, I need one IPSec supported opensource SIP server for testing my sip client endpoint.Could you please tell me which SIP server supporting IPSec ? Thanks in advance. Thanks Priyaranjan

5 4

Re: [SR-Users] Presence and NAT
by Pramod Venugopal 21 Aug '15

21 Aug '15

I realize this last email has no useful information, so let me elaborate. I have a Kamailio server on AWS with an internal IP of 10.20.30.40 and it has an external elastic IP of 55.66.77.88. When a SIP client subscribes it sends the initial subscription to user@realm (where realm resolves to 55.66.77.88) , then it gets a notify with a new address <sip:10.20.30.40:5060;transport=udp> . The client attempts to refresh the subscription, but we are now sending the subscribes to this new contact which will time out. 300 seconds later, we subscribe again to user@realm and contacts show up. Other stuff like rtp, inbound/outbound calling all work properly. Pramod Venugopal pramod(a)dvnull.org From: sr-users on behalf of Pramod Venugopal Reply-To: "Kamailio (SER) - Users Mailing List" Date: Thursday, August 20, 2015 at 10:38 PM To: "Kamailio (SER) - Users Mailing List" Subject: [SR-Users] Presence and NAT Hello everyone, I have a Kamailio 4.2 system on Amazon AWS. When subscribing to presence the contact is sent out with the internal IP rather than the external public IP. The subscribes are being sent to it with the external hostname ( which resolves to the external IP ). Where would I be able to change the IP sent in the Contact header ? Pramod Venugopal pramod(a)perseus-tech.com _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

1 0

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