January 2018 - sr-users

[Serusers] Digest Authentication with Tenor DX
by Ashutosh Kumar 29 Apr '25

29 Apr '25

Hi, Does someone have any idea/experience with Quintum DX radius server's support for digest mode authentication. The Access-Request packets sent by SER are getting an error back. Guide. Regards, Ashutosh Kumar Chetu, Inc. Ph : 1(305) 402 6724 - Witin US Ph : 91 120 5323340 - Outside US Fax:1 (305) 832 5987 For more information, please visit http://www.chetu.com

2 1

Re: [SR-Users] t_drop_replies not working with t_suspend in failure route
by Huber Andreas 03 Sep '21

03 Sep '21

Hi, We’re still using kamailio 4.4 but we’ll be migrating to 5.0 soon. Cool so it will be fixed when we migrate ! Thanks, Andreas From: sr-users [mailto:sr-users-bounces@lists.kamailio.org] On Behalf Of Federico Cabiddu Sent: vendredi 12 mai 2017 11:56 To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] t_drop_replies not working with t_suspend in failure route Hi, which version are you using? A similar case had been reported some months ago and it should be fixed in 5.0. Regards, Federico On Fri, May 12, 2017 at 11:44 AM, Huber Andreas <andreas.huber(a)nagra.com<mailto:andreas.huber@nagra.com>> wrote: Hello, We have a use case where we suspend a transaction in a failure_route to give UEs that might be woken by a push notification more time to REGISTER and join the INVITE. We’d like to drop the previous branches in this case. I tried using t_drop_replies() but it has no effect. The doc states that t_drop_replies() is only working if a new branch is added. And from my understanding t_suspend() adds a new branch. But is it possible that t_drop_replies() cannot be used with t_suspend()? Or am I missing something? Kind Regards, Andreas _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

2 1

need help with RTPProxy in bridged mode
by Grant Bagdasarian 04 Apr '20

04 Apr '20

Hello, I'm using RTPproxy for the first time in bridged mode and I can't get kamailio/rtpproxy to rewrite the c parameter to the correct public ip address of kamailio. The setup is as following: Carrier ------[fiber]------ Kamailio ---------[lan]--------- Freeswitch Kamailio is listening on two interfaces: 1) Private: 172.0.0.1 2) Public: 192.168.0.1 (since we have a dedicated fiber with our carrier, this is its public address) Freeswitch is listening on: 1) 172.0.0.2 Carrier is on: 1) 10.0.0.1 I've started an rtpproxy instance on the Kamailio box using: rtpproxy -s udp:127.0.0.1:7721 -u rtpproxy rtpproxy -p /var/run/rtpproxy/rtpproxy.pid -l 192.168.0.1 172.0.0.1 I've played around with rtpproxy_manage() and the various flags (ie, ei), but I can't get kamailio to set the correct public IP when the 200 OK has to be sent back to the carrier. It always sets it to its private address, instead of its public address. I'm using Kamailio 4.2 with sippy/rtpproxy 2.0. Could someone please point me into the right direction? Thanks! Grant

4 8

rtpproxy does not response, disable it
by Zodiac 03 Jan '20

03 Jan '20

Dear friends, I am working on a program on Kamailio and rtpengine proxy. I am wondering whether can I set Kamailio and rtpengine daemon on different physical machines. For example, I set Kamailio on a machine with IP address:10.109.247.80, and launch rtpengine daemon on another machine with interface parameter as 10.109.247.90 and ng port 7723. I set parameter in Kamailio.cfg with modparam(“rtpengine”, “rtpengine_sock”, “udp:10.109.247.90:7723”). Unfortunately I got debug message like this: ERROR: rtpengine [rtpengine.c:1710]: send_rtpp_command(): can't send command to a RTP proxy ERROR: rtpengine [rtpengine.c:1746]: send_rtpp_command(): proxy <udp:10.109.247.90:7723> does not respond, disable it ERROR: rtpengine [rtpengine.c:1616]: rtpp_test(): proxy did not respond to ping And, I also tried to set Kamailio and rtpengine daemon in a same machine,and use modparam(“rtpengine”, “rtpengine_sock”, “udp:localhost:7723”). And Kamailio can work functionally under this situation. rtpengine daemon can receive ping message from Kamailio and rtpengine daemon can work as suspected. So for the later case, is it supposed that Kamailio be in the same machine with same localhost address? Otherwise, what’s the reason for my ERROR? ------------------------------------ 北京邮电大学网络技术研究院网络与交换技术国家重点实验室田军 +86 18810315790 mozillafire(a)bupt.edu.cn ------------------------------------

5 10

tcp Free fragment not found
by Diego Nadares 04 Oct '18

04 Oct '18

Hi guys! We have four a scripts that sends dlg.list command to kamailio through xmlrpc. They are not executed simultaneously. Sometimes, we are getting the following errors: fm_search_defrag(): fm_search_defrag(0x7f212c25a000, 5273984); Free fragment not found!2017-05-26T13:54:20.438736-03:00 drwsip02 /usr/local/sbin/kamailio[19833]: ERROR: <core> [mem/f_malloc.c:498]: fm_malloc(): fm_malloc(0x7f212c25a000, 5273984) called from core: tcp_main.c: tcpconn_new(957), module: core; Free fragment not found!2017-05-26T13:54:20.439101-03:00 drwsip02 /usr/local/sbin/kamailio[19833]: ERROR: <core> [tcp_main.c:959]: tcpconn_new(): mem. allocation failure2017-05-26T13:54:20.439344-03:00 drwsip02 /usr/local/sbin/kamailio[19833]: ERROR: <core> [tcp_main.c:3985]: handle_new_connect(): tcpconn_new failed, closing socket I all ready increased this two variables: tcp_conn_wq_max=30000000 tcp_rd_buf_size=5273226 How can I see how much memory xmlrpc is using? Any advice will be appreciated. Thanks in advance! Diego

2 2

Kamctl Stats Update
by Noah Mehl 07 Aug '18

07 Aug '18

Hey all, I was wondering if the kamctl stats output could be updated to provide a bit more parseable JSON? For instance: # kamctl stats shmem | jq . { "jsonrpc": "2.0", "result": [ "shmem:fragments = 18", "shmem:free_size = 467187808", "shmem:max_used_size = 69694104", "shmem:real_used_size = 69683104", "shmem:total_size = 536870912", "shmem:used_size = 41048984" ], "id": 4300 } I would hope would be more like this: { "jsonrpc":"2.0", "result":[ { "shmem":[ { "fragments":18, "free_size":467187808, "max_used_size":69694104, "real_used_size":69683104, "total_size":536870912, "used_size":41048984 } ] } ], "id":4300 } I apologize in advanced because I don’t have the skillset to contribute such a feature. Thanks! ~Noah

5 8

No cdr after Kamailio 5.0.4 and 5.2 dev restart
by Kordován Szabolcs 27 Jul '18

27 Jul '18

Hi All, In March there was a discus about this issue. We tested the new 5.2 dev and 5.0.4 version of Kamailio and we experience that If we restart Kamailio during the call the cdr won't be stored in table acc_cdrs but the data will be inserted to table acc and data will be deleted from table dialog and dialog_vars. Did I omit the fix for it? Thanks for your help. Best regards, Szabolcs

2 3

Kamailio Behind TCP Load Balancer
by Colin Morelli 04 Jun '18

04 Jun '18

Hey all, I'm looking to put Kamailio behind a TCP load balancer that is SIP-unaware. My application is deployed in AWS and I'm tying to place Kamailio behind an ELB. For the most part, everything is fine. For my specific implementation I'm disabling UDP as a signaling transport and using only TLS. This enables me to not have to worry about a SIP-aware LB at the edge because replies to an incoming request will be sent over the existing established TCP socket (avoiding any crazy routing requirements). However - this poses an issue with source addresses. Does Kamailio support anything like the proxy protocol ( http://www.haproxy.org/download/1.5/doc/proxy-protocol.txt) for getting TCP stream information from a load balancer? Do I need to go back to exposing it directly to the world so that I can get source addresses? Thanks, Colin

3 4

Kamailio Websocket Questions
by Nagorny, Dimitry 17 Apr '18

17 Apr '18

Hi List, two questions regarding Kamailio Websockets: 1. How do I send INVITE request TO the listening Websocket? I usually used for UDP/TCP/TLS these format, but somehow this is not working for Websocket because it gets in an endless loop: if ($rU=~"^(\+|00|0)?[1-9][0-9]{4,20}$") { $ru = "sip:" + $rU + "@" + $sel(cfg_get.pstn.gw_ip) + ";user=phone;transport=udp"; force_send_socket(udp:MY_EXTERN_IP:MY_EXTERN_PORT); rtpengine_offer("internal trust-address RTP AVP"); route(RELAY); exit; } 2. Why do I get these errors every time my Websocket Client is registering, but it still works and DB is inserted with registered location: ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 22) ERROR: <core> [parser/msg_parser.c:690]: parse_msg(): ERROR: parse_msg: message=<HTTP/1.1 101 Switching Protocols#015#012Sia: SIP/2.0/TCP 10.250.5.17:51283#015#012Sec-WebSocket-Protocol: sip#015#012Upgrade: websocket#015#012Connection: upgrade#015#012Sec-WebSocket-Accept: 6uLXlD/aBrzu/j3PYP3DWO7rvLE=#015#012Server: kamailio (4.3.5 (x86_64/linux))#015#012Content-Length: 0#015#012#015#012> I am using Kamailio 4.3.5 + CentOS 7.2. I appreciate every help I can get. Best Regards Dimitry Nagorny Trainee

3 4

topos redis -> failed to store
by Abdoul Osséni 02 Apr '18

02 Apr '18

Hello list, I activated topos and topos_redis backend. Now, I have the following errors: Jan 6 07:34:11 sd-110402 /usr/local/sbin/kamailio[30288]: {1 102 NOTIFY 645f4b58537f9df53b9ce65f4937d652@163.172.83.169:5064} ERROR: topos [tps_storage.c:394]: tps_storage_record(): failed to store Jan 6 07:34:11 sd-110402 /usr/local/sbin/kamailio[30292]: {1 102 NOTIFY 5b678085378e62c12c6f18154501feb3@163.172.83.169:5064} INFO: topos_redis [topos_redis_storage.c:163]: tps_redis_insert_dialog(): no uuid for this message Jan 6 07:34:11 sd-110402 /usr/local/sbin/kamailio[30292]: {1 102 NOTIFY 5b678085378e62c12c6f18154501feb3@163.172.83.169:5064} ERROR: topos [tps_storage.c:394]: tps_storage_record(): failed to store Jan 6 07:34:18 sd-110402 /usr/local/sbin/kamailio[30287]: {1 102 NOTIFY 2799d4a61e9defbc66dc67735e1c6e6c@163.172.83.169:5064} INFO: topos_redis [topos_redis_storage.c:163]: tps_redis_insert_dialog(): no uuid for this message Jan 6 07:34:18 sd-110402 /usr/local/sbin/kamailio[30287]: {1 102 NOTIFY 2799d4a61e9defbc66dc67735e1c6e6c@163.172.83.169:5064} ERROR: topos [tps_storage.c:394]: tps_storage_record(): failed to store Jan 6 07:34:18 sd-110402 /usr/local/sbin/kamailio[30290]: {1 102 NOTIFY 760fe2ce3427748514441de25cade2e4@163.172.83.169:5064} INFO: topos_redis [topos_redis_storage.c:163]: tps_redis_insert_dialog(): no uuid for this message Jan 6 07:34:18 sd-110402 /usr/local/sbin/kamailio[30290]: {1 102 NOTIFY 760fe2ce3427748514441de25cade2e4@163.172.83.169:5064} ERROR: topos [tps_storage.c:394]: tps_storage_record(): failed to store Jan 6 07:34:33 sd-110402 /usr/local/sbin/kamailio[30291]: {1 102 NOTIFY 7464fc2b503427423b0aba925fb13bc7@163.172.83.169:5064} INFO: topos_redis [topos_redis_storage.c:163]: tps_redis_insert_dialog(): no uuid for this message Jan 6 07:34:33 sd-110402 /usr/local/sbin/kamailio[30291]: {1 102 NOTIFY 7464fc2b503427423b0aba925fb13bc7@163.172.83.169:5064} ERROR: topos [tps_storage.c:394]: tps_storage_record(): failed to store Jan 6 07:34:35 sd-110402 /usr/local/sbin/kamailio[30287]: {1 102 NOTIFY 581e88181527f4221fbc7f893a564d6a@163.172.83.169:5064} INFO: topos_redis [topos_redis_storage.c:163]: tps_redis_insert_dialog(): no uuid for this message Jan 6 07:34:35 sd-110402 /usr/local/sbin/kamailio[30287]: {1 102 NOTIFY 581e88181527f4221fbc7f893a564d6a@163.172.83.169:5064} ERROR: topos [tps_storage.c:394]: tps_storage_record(): failed to store Could you help me to fix it? Abdoul OSSENI

3 8

Re: [SR-Users] How to determine correct port to set in record-route header
by Pranathi Venkatayogi 30 Mar '18

30 Mar '18

Any help? From: Pranathi Venkatayogi Sent: Monday, January 23, 2017 2:35 PM To: 'Kamailio (SER) - Users Mailing List' <sr-users(a)lists.sip-router.org> Subject: How to determine correct port to set in record-route header Hi, I am using Kamailio behind NAT, unable to figure how to make it put “public ip” in Record-route header, I am manually inserting the hard-coded header myself as below. However now I am having trouble choosing the right port number in all scenarios. $var(dstPort) = 5061; if (dst_port==5060) { $var(dstPort) = 5060; } insert_hf("Record-Route: <sip:MY_PUBLICIP_ADDR:$var(dstPort);transport=tls;lr;nat=yes>\r\n", "Record-Route"); In one scenario I see the conflicting port numbers in “via” header vs “Record route”. The ACK is being set to port 5060 based on Record route header and is not being received by the callee. 2017-01-23 14:52:49.970233 [blink.exe 2780]: SENDING: Packet 11, +0:00:36.411867 10.0.27.108:58217 -(SIP over TLS)-> 172.31.211.31:5061 SIP/2.0 180 Ringing Via: SIP/2.0/TLS 63.149.103.72:5061;received=172.31.211.31;branch=z9hG4bK4799.7067bd2a48063748a4c353fa408eaefa.0 Via: SIP/2.0/UDP 10.0.16.52;rport=5060;branch=z9hG4bK4799.935a27c6ef5ad112225964cbe7c1be44.0;i=2 Via: SIP/2.0/TLS 10.11.200.12:51793;rport=51793;received=10.11.200.12;branch=z9hG4bKPj49f6aeca3f9b4155ab4c5304b544aa4d;alias Record-Route: <sip:63.149.103.72:5060;transport=tls;lr;nat=yes> Record-Route: <sip:10.0.16.52:5061;transport=tls;lr;nat=yes> Call-ID: 09ce10efa6a946bf9445ccc21857393e From: "cust1" <sip:cust1@devtranslation.sms-test.cyracom.com>;tag=95082caabecc42548c2fec5ccd29e5de To: <sip:spanish@translation.sms-test.cyracom.com>;tag=ec365cc8489b48a7bc5725d21b7d97a1 CSeq: 17422 INVITE Server: Blink 3.0.0 (Windows) Contact: <sip:20745891@10.0.27.108:58216;transport=tls> Allow: SUBSCRIBE, NOTIFY, PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, MESSAGE, REFER Content-Length: 0 Questions: 1. How can I let in-built record-route function automatically choose “public ip” so I can get rid of my manual insertion altogether. 2. If no option, what is the right way to choose the port on which packet is being received, so it is same as what is on “VIA”. 3. Any other pointers to improve the logic here?

3 3

authenticating to mongodb fails
by hdssdsdsdsfsdf hdssdsdsdsfsdf 21 Mar '18

21 Mar '18

When I connect using mongo, the credentials work: $ mongo kamailio -u "kam" -p "kam" MongoDB shell version v3.4.9 connecting to: mongodb://127.0.0.1:27017/kamailio MongoDB server version: 3.4.9 > db.subscriber.find() { "_id" : ObjectI ... But when I use the following DBURL in kamailio.cfg, kamailio fails to even login to mongo: #!define DBURL "mongodb://kam:kam@localhost/kamailio" If I disable mongodb authentication, kamailio starts up just fine again. Any idea what's going wrong here?

3 10

Need useful graphics ideas
by Karsten Horsmann 16 Mar '18

16 Mar '18

Hello List, I thought about some kind of Kamailio stats source (like registered users, calls active and some other things) to collect them into influx dB and draw them with grafana. How do you solved that? Timer based routes or statsd or whatever? Kind regards Karsten Horsmann

5 10

is_audio_on_hold() doesn't support rfc3264
by Julia Boudniatsky 13 Feb '18

13 Feb '18

FYI, After some tests found, that function "*is_audio_on_hold()*" (textops) *supports only rfc 254*3, where "hold" is indicated by setting the "c" destination addresses for the media streams to zero (0.0.0.0). The newest *rfc3264*, where "hold" is indicated by a=sendonly/inactive, *is not supported*. Kamailio version 4.4.6. Best regards, Julia

4 8

dmq_usrloc - which server?
by Alex Balashov 07 Feb '18

07 Feb '18

Hi, The Socket parameter of location entries is not replicated under dmq_usrloc. To make matters worse, the technical characteristics of the registrar module are such that I cannot straightforwardly modify the incoming Contact to add a rider indicating the server on which the register was received. The AoR domain is the same for all registrations received on any server in the DMQ mesh. To reach the registrants, I need to forward the registration to the correct server that corresponds to the true provenance of the registration. What is a reasonable way of finding out what that is? I don't see any method of injecting such values into the replicated contacts, as dmq_usrloc does not provide hooks for this. Thanks, -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

3 19

Issue with Socket selection on Forwarding ACK message
by Thomas Carvello 06 Feb '18

06 Feb '18

Hello, i have an issue with my Kamailio 4.1.9 configuration. This configuration is multi-homed, we have*two network* interfaces, one on a private network and on the public Internet. Kamailio is configured to listen on port 5060 and 5066 on both interfaces. We register two users Alice and Bob on the public Internet using port 5066. Both users are behind a NAT and we capture the SIP exchange on the proxy server. We have set the parameter mhomed=1 When Alice calls Bob, we have Alice Proxy Bob src=5063 dst=5066 INVITE ------------------> src=5066 ------ INVITE ---------------> dst=5060 dst=5066 <------- 200 OK -------------- src=5060 dst=5063 <------- 200 OK --------- src=5066 src=5063 dst=5066 -------- ACK -----------> *src=5060 (blocked by NAT)* ------ ACK-----x dst=5060 The ACK packet gets relayed with the wrong source port. Then the NAT rejects the packet and the call cannot be established. For some reason, when Bob calls Alice, the call is correctly established. Could it be because Bob happend to use 5060 as local port? Also, if we set nhomed=0 it works BUT we are not sure that multi homed is handled correctly. I was wondering if you have encounter this issue before? I have investigated the code for selection socket and what is the logic of this selection ? /*How does kamailo knows that it should choose 5066 as src port if the user is registered using port 5066 instead of 5066?* / Thank you for your time. Thomas

4 8

Fosdem dinner
by Daniel-Constantin Mierla 03 Feb '18

03 Feb '18

Hello, in the past 10 years or so, many of us met at Fosdem conference in Brussels (the edition this year happens during February 3-4) and had a dinner on Saturday evening. I know already couple of people from community that will go there, so the question is if there is any interest to organize again such event. If yes, it will be again on Saturday, on the evening of the 3rd of February. At the past editions, it turned into an all-RTC dinner, but we can consider to have it alone again (eventually with few other invited friends), if there are too many or people want a smaller meeting. Reply this week if you want to join, so we can estimate how many seats we need and have enough time to find a place that can accommodate us. More about Fosdem can be found at: - https://fosdem.org There is a devroom on Sunday with topics covering real time communications. I will have a presentation there. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

10 13

Case insensitive regexp in textops::search() function
by Andrey Deykunov 01 Feb '18

01 Feb '18

Hi, I have an htable containing some black list words (i.e. user IDs or phone models). To find matches of the words in every message I use the following script: sht_iterator_start("i1", "black_list"); while(sht_iterator_next("i1")) { if ( search($shtitval(i1)) ) { // do something } } sht_iterator_end("i1"); How can I modify search($shtitval(i1)) to get case insensitive matching? The example below does not work: sht_iterator_start("i1", "black_list"); while(sht_iterator_next("i1")) { $var(re) = $shtitval(i1) + "/i"; if ( search($var(re)) ) { // do something } } sht_iterator_end("i1"); Other possible modifications of $var(re) aren't working too. Thanks, Andrey

2 2

Partial/regex match on hash table key?
by Anthony Joseph Messina 31 Jan '18

31 Jan '18

Is is possible (without iterating through all entries in a hash table) to return the value based on a partial or regex match to the key? Something like... $var(one)=$sht(a=>*$var(two)) -- Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery F9B6 560E 68EA 037D 8C3D D1C9 FF31 3BDB D9D8 99B6

2 2

question about force_send_socket
by Fabian Borot 31 Jan '18

31 Jan '18

our kamailo has 2 IPs, a public (87.x.x.x) and a private (192.168.1.1). It is listening on all of them. For all calls it listens on the public IP but for some calls I need to forward the incoming INVITE to a server in the private network so I do a " force_send_socket(privateip:port)" before the route that forwards the INVITE to the server in the private network and that works. But then when the server in the private network replies with 302 I have to contact the servers inside the Contact header using the Public IP now so I do this hoping that it will switch back to the public IP: if (t_check_status("302")) { force_send_socket(PUBLIC_IP:5060); get_redirects("*"); t_relay(); } But it stays in the private, so the INVITEs to the servers inside the Contact header are sent from the Private IP and they are blocked. This would be the flow: customer INVITE -> kamailio(publicIP) kamailio (publicIP) 100 trying -> customer kamailio(privateIP) INVITE -> Server(privateIP) Server(privateIP) 302 redirect -> kamailio(privateIP) kamailio(privateIP) ACK -> Server(privateIP) after I would like this to happen kamailio(publicIP) INVITE -> Server1(publicIP) but instead this happens: kamailio(privateIP) INVITE -> Server1(publicIP) how can I switch back to the public IP to continue with this call flow? thank you

2 2

[4.2] how to send out BYE successfully to close a TCP/TLS connection which misses the connection ID?
by Jack Wang 31 Jan '18

31 Jan '18

For some reasons, My settings will cause kamailio to be restarted even if there were connections connected to it. And when one SIP client in a connection wanted to hangup the call with a WebRTC Client (SIP over websocket) after the proxy-restarting, local client was closed, however , the other side was not. >From the log below it seems that the connection missed. Jan 30 18:19:31 ./kamailio[27857]: WARNING: <core> [msg_translator.c:2777]: via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found Jan 30 18:19:31 ./kamailio[27857]: ERROR: tm [t_msgbuilder.c:1365]: assemble_via(): assemble_via: via building failed Jan 30 18:19:31 ./kamailio[27857]: ERROR: tm [t_msgbuilder.c:1545]: build_uac_req(): build_uac_req(): Error while assembling Via Jan 30 18:19:31 ./kamailio[27857]: ERROR: tm [uac.c:379]: t_uac_prepare(): t_uac: Error while building message So, Is it equivalent to connection ID missing? And is there any way to make Websocket found the connection? Btw, after proxy-restarting for seconds , I typed `sh kamctl stats` : websocket:ws_current_connections = 1 It showed that the WebRTC Client will re-connect automatically, So I think this connection could be found by proxy, Any suggestion? Thanks :)

1 2

Normal behaviour with loose_routing
by Loic Chabert 30 Jan '18

30 Jan '18

Hi list, I have a setup configurered has diagram below: UAC -> Proxy LB (proxy lb) -> Proxy Router/registrar (proxy B) -> Asterisk SBC My UAC is SIPP and sending a classic call scenario: INVITE - ACK - BYE. But i have some trouble to understand which queries should be loose routed and which queries should be dispatched by dispatcher module. My first invite request has been dispatched to proxy B by proxy LB. After that, ACK and BYE request should be loose_routed or should be dispatched as other request ? My proxy B is a statefull proxy, logging cdrs and other stuff ... >From my point of view, subsequent request should be loose_routed to keep dialog informations consistent. My subsequent requests have record-route headers. Should i use theses headers to route my calls ? Loose routing features only work with "Route" header ? What is the difference beetwen Route headers and Record-route headers ? Thanks in advance, Regards.

3 5

rtjson + uac + event - OK, ACK and BYE display name not updated
by Diego Nadares 30 Jan '18

30 Jan '18

Hi Guys, We are modifying "from" and "to" headers with rtjson module via a json struct. It works fine in INVITE, TRYING, RINGING and OK but not in the following messages. Kamailio It's changing ONLY "from" and "to" URI BUT NOT the DISPLAY NAME. I think it's the tm module but I can't figure out how to confirm this. Maybe I need to configure something else in my cfg or could it be a bug? My json struct that is handled by rtjson module response.routing = "serial"; //response.routing = "parallel"; response.routes = []; response.routes[0] = {}; response.routes[0].uri = "sip:1111111111@172.16.213.31:5060"; response.routes[0].headers = { // Headers to be modified "from": { "display": "1111111111", "uri": "sip:111111111@172.16.213.38" }, "to": { "display": "2222222222", "uri": "sip:2222222222@172.16.213.38" }, }; response.routes[0].headers.extra = {};//"X-Hdr-A: abc\r\nX-Hdr-B: bcd\r\n"; This is part of my cfg .... modparam("dialog","dlg_flag", FLD_START) modparam("uac","restore_mode","auto") modparam("uac", "restore_dlg", 1) .... # account only INVITEs if (is_method("INVITE") && !has_totag()) { setflag(FLT_ACC); # do accounting * setflag(FLD_START); # do accounting* setflag(FLT_ACCMISSED); setflag(FLT_ACCFAILED); } ..... >From source/Aleg: *From: sipp <sip:sipp@172.16.213.21:5060 <http://sip:sipp@172.16.213.21:5060>>;tag=1.* *To: sut <sip:5555555555@172.16.213.38:5060 <http://sip:5555555555@172.16.213.38:5060>>.* To dest/Bleg: *From: 1111111111 <sip:111111111@172.16.213.38 <sip%3A111111111(a)172.16.213.38>>;tag=1.* *To: 2222222222 <sip:2222222222@172.16.213.38 <sip%3A2222222222(a)172.16.213.38>>.* Incorrect display name in BYE and ACK: *From: sipp <sip:111111111@172.16.213.38 <sip%3A111111111(a)172.16.213.38>>;tag=1.* *To: sut <sip:2222222222@172.16.213.38 <sip%3A2222222222(a)172.16.213.38>>;tag=2.* interface: any filter: ( port 5060 ) and (ip or ip6) # U 2016/12/06 15:52:13.638731 172.16.213.21:5060 -> 172.16.213.38:5060 INVITE sip:5555555555@172.16.213.38:5060 SIP/2.0. Via: SIP/2.0/UDP 172.16.213.21:5060;branch=z9hG4bK-12775-1-0. *From: sipp <sip:sipp@172.16.213.21:5060 <http://sip:sipp@172.16.213.21:5060>>;tag=1.* *To: sut <sip:5555555555@172.16.213.38:5060 <http://sip:5555555555@172.16.213.38:5060>>.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 1 INVITE. Contact: "SIPP" <sip:sipp@172.16.213.21:5060>. Max-Forwards: 70. Subject: Performance Test. Content-Type: multipart/mixed;boundary=uniqueBoundary. Remote-Party-ID: <sip:sipp@172.16.213.21 >:5060;party=calling;id-type=subscriber;privacy=off;screen=no>. Content-Length: 549. . --uniqueBoundary. Content-Type: application/sdp. . v=0. o=user1 53655765 2353687637 IN IP4 172.16.213.21. s=-. c=IN IP4 172.16.213.21. t=0 0. m=audio 6000 RTP/AVP 8. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-11,16. . --uniqueBoundary. Content-Type: application/gtd. Content-Disposition: signal;handling=optional. . IAM,. CGN,04,y,1,y,4,1143617400. CIC,0000000573. CPC,09. CPN,02,y,1,52381660. FCI,n,n,n,n,y,n,n,u. GCI,f7140cc78a611601838a002128d7e512. NOC,0,n,1,n. PRN,q761*,AR*,oper2,1993. TMR,02. . --uniqueBoundary--. ................ # U 2016/12/06 15:52:13.734159 172.16.213.38:5060 -> 172.16.213.21:5060 SIP/2.0 100 trying -- your call is important to us. Via: SIP/2.0/UDP 172.16.213.21:5060;branch=z9hG4bK-12775-1-0. *From: sipp <sip:sipp@172.16.213.21:5060 <http://sip:sipp@172.16.213.21:5060>>;tag=1.* *To: sut <sip:5555555555@172.16.213.38:5060 <http://sip:5555555555@172.16.213.38:5060>>.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 1 INVITE. Server: kamailio (4.4.4 (x86_64/linux)). Content-Length: 0. . ................ # U 2016/12/06 15:52:13.878600 172.16.213.38:5060 -> 172.16.213.31:5060 INVITE sip:1111111111@172.16.213.31:5060 SIP/2.0. Via: SIP/2.0/UDP 172.16.213.38;branch=z9hG4bKabaa.840cc83114975a34a37b7af020d37b65.1. *From: 1111111111 <sip:111111111@172.16.213.38 <sip%3A111111111(a)172.16.213.38>>;tag=1.* *To: 2222222222 <sip:2222222222@172.16.213.38 <sip%3A2222222222(a)172.16.213.38>>.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 1 INVITE. Max-Forwards: 69. Subject: Performance Test. Content-Type: multipart/mixed;boundary=uniqueBoundary. Content-Length: 788. Contact: <sip:btpsh-58470879-6c61-1@172.16.213.38>. . --uniqueBoundary. Content-Type: application/sdp. . v=0. o=user1 53655765 2353687637 IN IP4 172.16.213.38. s=-. c=IN IP4 172.16.213.38. t=0 0. m=audio 40236 RTP/AVP 8. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-11,16. a=sendrecv. a=rtcp:40237. a=ice-ufrag:QNCzXhUr. a=ice-pwd:Ci90BRpdZH51Hx5BaPgGMrGCeh. a=candidate:P1djl8LFNb5kexbG 1 UDP 2130706431 172.16.213.38 40236 typ host. a=candidate:P1djl8LFNb5kexbG 2 UDP 2130706430 172.16.213.38 40237 typ host. . --uniqueBoundary. Content-Type: application/gtd. Content-Disposition: signal;handling=optional. . IAM,. CGN,04,y,1,y,4,1143617400. CIC,0000000573. CPC,09. CPN,02,y,1,52381660. FCI,n,n,n,n,y,n,n,u. GCI,f7140cc78a611601838a002128d7e512. NOC,0,n,1,n. PRN,q761*,AR*,oper2,1993. TMR,02. . --uniqueBoundary--. ................ # U 2016/12/06 15:52:13.879441 172.16.213.31:5060 -> 172.16.213.38:5060 SIP/2.0 180 Ringing. Via: SIP/2.0/UDP 172.16.213.38;branch=z9hG4bKabaa.840cc83114975a34a37b7af020d37b65.1. *From: 1111111111 <sip:111111111@172.16.213.38 <sip%3A111111111(a)172.16.213.38>>;tag=1.* *To: 2222222222 <sip:2222222222@172.16.213.38 <sip%3A2222222222(a)172.16.213.38>>;tag=2.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 1 INVITE. Contact: <sip:172.16.213.31:5060;transport=UDP>. Content-Type: application/sdp. Content-Length: 137. . v=0. o=user1 53655765 2353687637 IN IP4 172.16.213.31. s=-. c=IN IP4 172.16.213.31. t=0 0. m=audio 6000 RTP/AVP 0. a=rtpmap:0 PCMU/8000. ................ # U 2016/12/06 15:52:13.936565 172.16.213.38:5060 -> 172.16.213.21:5060 SIP/2.0 180 Ringing. *From: sipp <sip:sipp@172.16.213.21:5060 <http://sip:sipp@172.16.213.21:5060>>;tag=1.* *To: sut <sip:5555555555@172.16.213.38:5060 <http://sip:5555555555@172.16.213.38:5060>>;tag=2.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 1 INVITE. Content-Type: application/sdp. Content-Length: 316. Via: SIP/2.0/UDP 172.16.213.21:5060;branch=z9hG4bK-12775-1-0. Contact: <sip:atpsh-58470879-6c61-2@172.16.213.38>. . v=0. o=user1 53655765 2353687637 IN IP4 172.16.213.38. s=-. c=IN IP4 172.16.213.38. t=0 0. m=audio 40248 RTP/AVP 0. a=rtpmap:0 PCMU/8000. a=sendrecv. a=rtcp:40249. a=candidate:P1djl8LFNb5kexbG 1 UDP 2130706431 172.16.213.38 40248 typ host. a=candidate:P1djl8LFNb5kexbG 2 UDP 2130706430 172.16.213.38 40249 typ host. ................ # U 2016/12/06 15:52:20.882165 172.16.213.31:5060 -> 172.16.213.38:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 172.16.213.38;branch=z9hG4bKabaa.840cc83114975a34a37b7af020d37b65.1. *From: 1111111111 <sip:111111111@172.16.213.38 <sip%3A111111111(a)172.16.213.38>>;tag=1.* *To: 2222222222 <sip:2222222222@172.16.213.38 <sip%3A2222222222(a)172.16.213.38>>;tag=2.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 1 INVITE. Contact: <sip:172.16.213.31:5060;transport=UDP>. Content-Type: application/sdp. Content-Length: 213. . v=0. o=user1 53655765 2353687637 IN IP4 172.16.213.31. s=-. c=IN IP4 172.16.213.31. t=0 0. m=audio 6000 RTP/AVP 0. a=rtpmap:0 PCMU/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=ptime:20. a=sendrecv. ................ # U 2016/12/06 15:52:21.173798 172.16.213.38:5060 -> 172.16.213.21:5060 SIP/2.0 200 OK. *From: sipp <sip:sipp@172.16.213.21:5060 <http://sip:sipp@172.16.213.21:5060>>;tag=1.* *To: sut <sip:5555555555@172.16.213.38:5060 <http://sip:5555555555@172.16.213.38:5060>>;tag=2.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 1 INVITE. Content-Type: application/sdp. Content-Length: 380. Via: SIP/2.0/UDP 172.16.213.21:5060;branch=z9hG4bK-12775-1-0. Contact: <sip:atpsh-58470879-6c61-2@172.16.213.38>. . v=0. o=user1 53655765 2353687637 IN IP4 172.16.213.38. s=-. c=IN IP4 172.16.213.38. t=0 0. m=audio 40248 RTP/AVP 0. a=rtpmap:0 PCMU/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=ptime:20. a=sendrecv. a=rtcp:40249. a=candidate:P1djl8LFNb5kexbG 1 UDP 2130706431 172.16.213.38 40248 typ host. a=candidate:P1djl8LFNb5kexbG 2 UDP 2130706430 172.16.213.38 40249 typ host. ................ # U 2016/12/06 15:52:21.174390 172.16.213.21:5060 -> 172.16.213.38:5060 ACK sip:atpsh-58470879-6c61-2@172.16.213.38 SIP/2.0. Via: SIP/2.0/UDP 172.16.213.21:5060;branch=z9hG4bK-12775-1-4. *From: sipp <sip:sipp@172.16.213.21:5060 <http://sip:sipp@172.16.213.21:5060>>;tag=1.* *To: sut <sip:5555555555@172.16.213.38:5060 <http://sip:5555555555@172.16.213.38:5060>>;tag=2.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 1 ACK. Contact: sip:sipp@172.16.213.21:5060. Max-Forwards: 70. Subject: Performance Test. Content-Length: 0. . ................ # U 2016/12/06 15:52:21.248172 172.16.213.38:5060 -> 172.16.213.31:5060 ACK sip:172.16.213.31:5060;transport=UDP SIP/2.0. Via: SIP/2.0/UDP 172.16.213.38;branch=z9hG4bKabaa.98116b5795d4c30f52156187a72059c8.0. *From: sipp <sip:111111111@172.16.213.38 <sip%3A111111111(a)172.16.213.38>>;tag=1.* *To: sut <sip:2222222222@172.16.213.38 <sip%3A2222222222(a)172.16.213.38>>;tag=2.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 1 ACK. Max-Forwards: 69. Subject: Performance Test. Content-Length: 0. Contact: <sip:btpsh-58470879-6c61-1@172.16.213.38>. . ................ # U 2016/12/06 15:52:51.178826 172.16.213.21:5060 -> 172.16.213.38:5060 BYE sip:atpsh-58470879-6c61-2@172.16.213.38 SIP/2.0. Via: SIP/2.0/UDP 172.16.213.21:5060;branch=z9hG4bK-12775-1-7. *From: sipp <sip:sipp@172.16.213.21:5060 <http://sip:sipp@172.16.213.21:5060>>;tag=1.* *To: sut <sip:5555555555@172.16.213.38:5060 <http://sip:5555555555@172.16.213.38:5060>>;tag=2.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 2 BYE. Contact: sip:sipp@172.16.213.21:5060. Max-Forwards: 70. Subject: Performance Test. Content-Length: 0. . ................ # U 2016/12/06 15:52:51.468639 172.16.213.38:5060 -> 172.16.213.31:5060 BYE sip:172.16.213.31:5060;transport=UDP SIP/2.0. Via: SIP/2.0/UDP 172.16.213.38;branch=z9hG4bK7baa.3cb44935b506e759e3418501b0688b08.0. *From: sipp <sip:111111111@172.16.213.38 <sip%3A111111111(a)172.16.213.38>>;tag=1.* *To: sut <sip:2222222222@172.16.213.38 <sip%3A2222222222(a)172.16.213.38>>;tag=2.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 2 BYE. Max-Forwards: 69. Subject: Performance Test. Content-Length: 0. Contact: <sip:btpsh-58470879-6c61-1@172.16.213.38>. . ................ # U 2016/12/06 15:52:51.469153 172.16.213.31:5060 -> 172.16.213.38:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 172.16.213.38;branch=z9hG4bK7baa.3cb44935b506e759e3418501b0688b08.0. *From: sipp <sip:111111111@172.16.213.38 <sip%3A111111111(a)172.16.213.38>>;tag=1.* *To: sut <sip:2222222222@172.16.213.38 <sip%3A2222222222(a)172.16.213.38>>;tag=2.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 2 BYE. Contact: <sip:172.16.213.31:5060;transport=UDP>. Content-Length: 0. . ................ # U 2016/12/06 15:52:51.519423 172.16.213.38:5060 -> 172.16.213.21:5060 SIP/2.0 200 OK. *From: sipp <sip:sipp@172.16.213.21:5060 <http://sip:sipp@172.16.213.21:5060>>;tag=1.* *To: sut <sip:5555555555@172.16.213.38:5060 <http://sip:5555555555@172.16.213.38:5060>>;tag=2.* Call-ID: 1-12775(a)172.16.213.21. CSeq: 2 BYE. Content-Length: 0. Via: SIP/2.0/UDP 172.16.213.21:5060;branch=z9hG4bK-12775-1-7. Contact: <sip:atpsh-58470879-6c61-2@172.16.213.38>. . ................ exit 13 received, 0 dropped Sorry for my english. Thanks in advance! Diego.

2 7

Session Timers
by Duarte Rocha 30 Jan '18

30 Jan '18

Hey guys, I have two issues about Session Timers that need some clarification. 1) I have my Kamailio between my clients CPE's and my GW to the PSTN. I want to configure it in a way that i always try to make the CPE do the refreshing so I can save resources on my kamailio and in the GW. If the CPE doesn't support it, the refresh should be done by the GW. Is it possible to do this test and configuration in every call ? 2) SIP has the MIN-SE mechanic and is well documented, but is it possible to implement a MAX-SE in any way ? Thanks for the help. If you need more details about the issue, please let me know. Cheers

2 1

Re: [SR-Users] Problem to install Kameilio from Ubuntu packages
by Victor Seva 30 Jan '18

30 Jan '18

2018-01-26 17:46 GMT+01:00 Alain Bonnefoy - XOOL <a.bonnefoy(a)xool.fr>: > > > I tried to install Kameilio on Ubuntu 16.04 from what explained in the > wiki <https://www.kamailio.org/wiki/packages/debs>. > Wiki updated. Thanks

1 0

Re: [SR-Users] Problem to install Kameilio from Ubuntu packages
by Bastian Triller 30 Jan '18

30 Jan '18

There another command on http://deb.kamailio.org for people behind firewalls which block port 11371: % wget -O- http://deb.kamailio.org/kamailiodebkey.gpg | sudo apt-key add - On Jan 26, 2018 5:46 PM, "Alain Bonnefoy - XOOL" <a.bonnefoy(a)xool.fr> wrote: > Hello, > > > > I tried to install Kameilio on Ubuntu 16.04 from what explained in the > wiki <https://www.kamailio.org/wiki/packages/debs>. > > > > But when I execute the command to add your GPG key, I just get replied > that the timeout occured. > > > > What to do ? > > > > Alain > > Provenance : Courrier <https://go.microsoft.com/fwlink/?LinkId=550986> > pour Windows 10 > > > > _______________________________________________ > Kamailio (SER) - Users Mailing List > sr-users(a)lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > >

1 0

kamailio tls passthrough
by pavel＠eremina.net 30 Jan '18

30 Jan '18

Hi, All i am trying to load balancing Kamailio with TLS in passthrough mode. is it possible to do it in stateless mode?

2 1

whats happened to iptel.org
by voipspace voipspace 29 Jan '18

29 Jan '18

Anyone know whats happened to iptel.org The webiste is now a wix page iptel.org the sip uri music(a)iptel.org was a useful resource. Now the song has changed and the service is down alot Has it it changed hands or been sold?

1 0

i can not receive BYE after websocket has been closed and reconnected during the call
by Kenan Kocaerkek 29 Jan '18

29 Jan '18

Hi, I have a WebRTC softphone based on JsSIP and kamailio 4.4.7. Generally it works well but sometimes websocket connections interrupt and reconnect immediately (especially running behind proxies). If the interruption occurs during an active call, kamailio tries to send BYE message to softphone over closed websocket. gruu_enabled flag is active on registrar module and JsSIP sends proper sip.instance value. So after ws reconnects, registered contact details do not change on kamailio except Expires value. Is it possible to send BYE message via contact's last active websocket after reconnect? Jan 29 14:35:20 registrar-kenan /usr/local/sbin/kamailio[30357]: WARNING: <script>: WebSocket connection from 195.142.112.66:49086 has closed Jan 29 14:35:24 registrar-kenan /usr/local/sbin/kamailio[30323]: WARNING: <core> [msg_translator.c:2761]: via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found Jan 29 14:35:24 registrar-kenan /usr/local/sbin/kamailio[30323]: ERROR: <core> [msg_translator.c:1979]: build_req_buf_from_sip_req(): could not create Via header Jan 29 14:35:24 registrar-kenan /usr/local/sbin/kamailio[30323]: ERROR: tm [t_fwd.c:462]: prepare_new_uac(): could not build request Jan 29 14:35:24 registrar-kenan /usr/local/sbin/kamailio[30323]: ERROR: tm [t_fwd.c:1723]: t_forward_nonack(): ERROR: t_forward_nonack: failure to add branches Jan 29 14:35:24 registrar-kenan /usr/local/sbin/kamailio[30323]: ERROR: sl [sl_funcs.c:363]: sl_reply_error(): ERROR: sl_reply_error used: No error (2/SL) Regards, Kenan

1 0

Ann: Registration to Kamailio World 2018 is open!
by Daniel-Constantin Mierla 29 Jan '18

29 Jan '18

Hello, a quick note to the community forums to announce that the registration to next Kamailio World Conference (May 14-17, 2018, in Berlin, Germany) is now open! More details are available at: * https://www.kamailioworld.com/k06/registration/ In a matter of several days, we expect to publish the details about the first group of accepted speakers. Looking forward to meeting many of you in Berlin! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

1 0

New module – embedded MSRP relay
by kossivi HOLONOU 28 Jan '18

28 Jan '18

Hello,I would like to develop a project that will allow me to: - voice, video, screen sharing, etc. sessions with content communication via RTP - end to end presence – this is purely SIP routing - SIMPLE-based presence (aka, presence server or presence agent model) via presence* and pua* modules — user presence, dialog states notification (aka, blinking lamps), resource lists service (including OMA/RCS extensions), user location states notification and replication, audio/video conference mixer notifications, a.s.o. - embedded XCAP server – management of user contact lists, presence policies, user agent configuration files, a.s.o. There is also an XCAP client extension - embedded HTTP server – for admin and user interaction with the service via pure HTTP or XMLRPC requests - embedded MSRP relay – for relaying and fine controlling of the message-based content of SIP sessions - IRC-style instant messaging conference via imc module - storage of instant messages for offline users and relay to them when they become again online via msilo module I need your help to start. I went through the document a little without understanding much. Thanks for your help

1 0

Kamailio with asterisk on private lan
by Mark Boyce 28 Jan '18

28 Jan '18

Hi all I’m trying to create a relatively simple setup with Kamailio dual homed on public/private ip and asterisk on private ip only. The idea is load balance / fail over asterisk boxes. Following the real-time tutorial I have clients registering with Kamailio, Kamailio registering on clients behalf with asterisk as well as invites going through. However what I’m seeing is that when an invite occurs asterisk offers media on its private ip, as it would. However this is making its way through Kamailio all the way to the client. After a bit of searching all I can find is people trying to get it working and failing, or putting asterisk on public IP. So questions - am I doing this completely the wrong way? Should Kamailio alter the media ip of asterisk on the way through or do I need to do that by hand? Surely someone somewhere has a write up on this already :-) Thanks Mark

7 8

SEMS with sbc application
by Mojtaba 27 Jan '18

27 Jan '18

Hello, I have a problem today, It's strange for me. Suppose we have this senario: uac1------->SEMS(mo profile)------->Kamailio-------->SEMS(mt profile)---------->uac2 In above topology, we have two interfaces(intern,extern) for SEMS, and just used as SBC (sbc application). if i used port=5060 as external port, every things is right and log file is like this: [#7fed3f9f9700/32820] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 89.165.117.125:42411 vv --++-- REGISTER sip:kava.shatel.ir;transport=UDP SIP/2.0 Via: SIP/2.0/UDP 89.165.117.125:42411;branch=z9hG4bK-d8754z-021bd8b61efc7ac0-1---d8754z- Max-Forwards: 70 Contact: <sip:4000@ 89.165.117.125:42411;rinstance=79011092e56e1a09;transport=UDP> To: <sip:4000@kava.shatel.ir;transport=UDP> From: <sip:4000@kava.shatel.ir;transport=UDP>;tag=82820e1f Call-ID: Y2U4YThiYjEwNTUzMzliZTIwNWZkMDI3MTM4OTZlNWU. CSeq: 2 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri User-Agent: Z 3.3.25608 r25552 Allow-Events: presence, kpml Content-Length: 0 but when i changed port=4080 for external port, The Via header and contact header are changed to my public ip, like this: [#7fed3f9f9700/32820] [run, udp_trsp.cpp:352] DEBUG: vv M [|] u recvd msg via UDP from 89.165.117.125:42411 vv --++-- REGISTER sip:kava.shatel.ir;transport=UDP SIP/2.0 Via: SIP/2.0/UDP 172.1.1.125:42411;branch=z9hG4bK-d8754z-021bd8b61efc7ac0-1---d8754z- Max-Forwards: 70 Contact: <sip:4000@172.1.1.125:42411;rinstance=79011092e56e1a09;transport=UDP> To: <sip:4000@kava.shatel.ir;transport=UDP> From: <sip:4000@kava.shatel.ir;transport=UDP>;tag=82820e1f Call-ID: Y2U4YThiYjEwNTUzMzliZTIwNWZkMDI3MTM4OTZlNWU. CSeq: 2 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri User-Agent: Z 3.3.25608 r25552 Allow-Events: presence, kpml Content-Length: 0 Why my public ip address is there here? I just changed external port=4080 in sems server. In SDP protocol i have the same problem when i changed external ip port in sems server. Thanks. --Mojtaba Esfandiari.S

3 3

Transcoding
by Wilkins, Steve 26 Jan '18

26 Jan '18

Hello All, I am currently using Kamailio and Asterisk on Centos 7 servers and trying to enable WebRTC jsSIP clients to be able to do Audio/Video calls with Provider Phones (Purple, Z, Sorenson, etc....), however, the providers do not have vp8 codecs (which is what the WebRTC clients use for Audio) so I believe I will need a media proxy server to resolve the video issues. My question is, can rtpproxy or rtpengine perform this transcoding? If so, and if rtpengine is the way to go, should I use Ubuntu for the rtpengine since it is the only one that seems to have a working installation? Thank you, -Steve

5 5

Problem to install Kameilio from Ubuntu packages
by Alain Bonnefoy - XOOL 26 Jan '18

26 Jan '18

Hello, I tried to install Kameilio on Ubuntu 16.04 from what explained in the wiki. But when I execute the command to add your GPG key, I just get replied that the timeout occured. What to do ? Alain Provenance : Courrier pour Windows 10

1 0

Kamailio log file empty
by Ashutosh chaubey 26 Jan '18

26 Jan '18

Hi, My kamailio.log file is empty, following is my configuration: In Kamailio.cfg- log_facility=LOG_LOCAL0 #!ifdef WITH_DEBUG debug=4 log_stderror=yes #!else debug=3 log_stderror=no #!endif Inside rsyslog.conf # don't log messages with LOG_LOCAL0 in /var/log/syslog anymore *.*;auth,authpriv.none,local0.none -/var/log/syslog # # log messages with LOG_LOCAL0 in /var/log/kamailio.log local0.* -/var/log/kamailio.log User has all the privileges to write in log file. Regards, Ashutosh Chaubey

3 2

EOL of geoip module.
by Sergey Okhapkin 26 Jan '18

26 Jan '18

Maxmind just announced EOL of legacy geolite databases used by geoip module, no updates starting this April. See more at https://blog.maxmind.com/ 2018/01/02/discontinuation-of-the-geolite-legacy-databases/ If you use kamailio's geoip module, I suggest to switch to geoip2 module which uses Geolite2 databases and is a plug in replacement for geoip module.

2 1

Behavior of UAC-Redirect module
by Richard Skidmore 26 Jan '18

26 Jan '18

2 2

SIP reply reason and code in dialog
by voipspace voipspace 26 Jan '18

26 Jan '18

within event_route[dialog:end] How do I find out SIP reply reason phrase and SIP reply code $rr $rs and $T_rpl($rs) $T_rpl($rr) are null

3 4

Three core dump bug fixes IMS kamailio 5.1.0 -> Pull Requests will follow
by Valentin Christoph 25 Jan '18

25 Jan '18

Hi all, When switching from kamailio 4.4.5 to kamailio 5.1.0 with the IMS installation in our lab, we detected three bugs, that lead to core dump. We will issue three pull requests in the course of this afternoon. KR ____ Christoph VALENTIN Software Developer | R&D Core / MGW + HLR + MSC P +43 50 811 3785 | M +43 664 628 3785 christoph.valentin(a)kapsch.net<mailto:christoph.valentin@kapsch.net> Kapsch CarrierCom AG | Lehrbachgasse 11 | 1120 Vienna | Austria Company Register at: Commercial Court Vienna FN 223804 z | Registered Office Vienna | www.kapsch.net<http://www.kapsch.net/> [Kapsch Logo]<https://www.kapsch.net/> The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.

2 2

Modify Reply Created
by Duarte Rocha 25 Jan '18

25 Jan '18

Hey everyone. Right now i'm doing a redirect server and i'm trying to sinalize the redirection using a 3xx reply. In order to do that, according the RFC I need to add a Contact and Diversion header. How do i do that ? i'm creating the reply with send_reply() but i can't seem to find a way to add these parameters to the reply. Thanks for the help. Cheers

3 2

kamctl domain reload
by David Villasmil 25 Jan '18

25 Jan '18

Hello guys, This is weird, using kamctl I am able to do things from like: kamctl trusted show +----+--------------+-------+--------------+--------------+------+----------+ | id | src_ip | proto | from_pattern | ruri_pattern | tag | priority | +----+--------------+-------+--------------+--------------+------+----------+ | 1 | 1.2.3.4 | udp | | NULL | | 0 | +----+--------------+-------+--------------+--------------+------+----------+ but reloading, etc doesn't work: kamctl trusted reload { "jsonrpc": "2.0", "error": { "code": 500, "message": "Method Not Found" }, "id": 22107 } Other cases: kamctl domain showdb +----+-------------------------------------+------+---------------------+ | id | domain | did | last_modified | +----+-------------------------------------+------+---------------------+ | 1 | proxy.domain.com | NULL | 2018-01-25 00:56:24 | +----+-------------------------------------+------+---------------------+ but show: kamctl domain show { "jsonrpc": "2.0", "error": { "code": 500, "message": "Method Not Found" }, "id": 22277 } Any ideas why this might be happening? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 ᐧ

2 1

Re: [SR-Users] Modify Reply Created
by Duarte Rocha 25 Jan '18

25 Jan '18

Thanks for the reply, that works :) What about if I want to delete or overwrite an header ? I need to change to To Header. If i use append_reply() will it overwrite ? Cheers

1 0

Allow Methods and Allow events SIP Headers are missing on SIP Registrtaion
by Suresh Talasaniya 25 Jan '18

25 Jan '18

Hi All, I am facing issue while SIP REGISTER. Allow methods and Allow Event SIP Headers are the mission of 401 Unauthorized and 200 OK on Successful SIP Registered. Please find the attached document in which I mention both working and nonworking SIP Message. It would be appreciable if anyone help figures out this issue on Kamailio server. Thank you. -- Regards, Suresh Talasaniya. Contact : +91-9724264776 Skype : suresh.talsaniya

2 2

Purge htable after dialog termination
by Jean Cérien 24 Jan '18

24 Jan '18

Hello I am following up on the improper sip dialog that has been fixed by storing contact details into a htable. I am trying to delete the key at the end of the call, so the table doesnt grow exponentially. I've added a event_route[dialog:end] {} block, but I see it is processed BEFORE the BYE is processed in the request_route(). Therefore, when I delete the data in the htable, I cant relay this BYE correctly. Is there another event (or technique) I could use to purge the htable ? doing from a cron on the cmd line is not so nice, and can delete data still needed for current calls thanks J.

2 4

Question about [SIP Transaction] Handle Cancel message
by Jacek S 23 Jan '18

23 Jan '18

Hi How you finally solved the problem with "481 Call transaction does not exist"? I have the same problem. Best regards, Jacek Szyszka

1 0

Freeradius Accounting [sql] Unsupported Acct-Status-Type = 15
by Suresh Talasaniya 23 Jan '18

23 Jan '18

Hey Guys, I have faced the issue when I am trying to store answered the call to PostgreSQL database using freeradius. *Mon Jan 22 06:48:39 2018 : Info: [sql] Unsupported Acct-Status-Type = 15* For more details, find here with attached radius.log. # freeradius -v freeradius: FreeRADIUS Version 2.2.5, for host x86_64-pc-linux-gnu, built on Aug 10 2017 at 07:25:15 Copyright (C) 1999-2013 The FreeRADIUS server project and contributors. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. You may redistribute copies of FreeRADIUS under the terms of the GNU General Public License. For more information about these matters, see the file named COPYRIGHT. Can someone help me to resolve this problem? -- Regards, Suresh Talasaniya. Contact : +91-9724264776 Skype : suresh.talsaniya

1 0

Kamailio v5.1.1 Released
by Daniel-Constantin Mierla 22 Jan '18

22 Jan '18

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

1 0

Already called uac_replace for this dialog
by Евгений Голей 22 Jan '18

22 Jan '18

Tell me please. Logs periodically display messages 2018-01-22T14: 14: 46.7701 "INFO: uac [replace.c: 392]: replace_uri (): Already called uac_replace for this dialog" 2018-01-22T14: 14: 46.7704 "INFO: uac [replace.c: 401]: replace_uri (): Deleted <_uac_funew> var in dialog" The reason I know, the question is how in the dialog to overwrite the previously saved parameter, which was obtained with "uac_replace"? -- С уважением, Евгений Голей

1 0

Planning the release of v5.1.1
by Daniel-Constantin Mierla 22 Jan '18

22 Jan '18

Hello, I am considering to do the first patch release from 5.1 series at the beginning of next week (most likely on Monday or Tuesday), as usual, if there are issues you are aware of and not reported to bug tracker, do it as soon as possible in order to have a chance to be fixed: - https://github.com/kamailio/kamailio/issues Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

1 1

sip invite proxy-authorization
by Dave & Hazel 21 Jan '18

21 Jan '18

Hello, Sorry, I'm not that familiar with Kamailio. I am trying to figure out how to configure proxy-authorization for incoming sip invites. I've defined WITH_AUTH in the configuration file but I think this only applies to sip register transactions. Any insight is most appreciated. Dave

4 9

Coredump while exchanging diameter capabilities
by Tsvetan Filev 19 Jan '18

19 Jan '18

Hi. I get a coredump which is caused by bad memory handling during the diameter capability exchange process. Here is part of the log file: =================================== 2018-01-16T09:16:39.890992+02:00 linux-o12d kamailio[13298]: 87(13388) INFO: cdp [worker.c:332]: worker_process(): [0] Worker process started... 2018-01-16T09:16:40.296393+02:00 linux-o12d systemd-coredump[13196]: Process 13193 (kamailio) of user 479 dumped core. 2018-01-16T09:16:40.871483+02:00 linux-o12d kamailio[13298]: 94(13395) DEBUG: cdp [peermanager.c:263]: peer_timer(): peer_timer(): taking care of peers... 2018-01-16T09:16:40.871545+02:00 linux-o12d kamailio[13298]: 94(13395) DEBUG: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.epc.mnc019.mcc425.3gppnetwork.org State 0 2018-01-16T09:16:40.871596+02:00 linux-o12d kamailio[13298]: 94(13395) DEBUG: cdp [peerstatemachine.c:90]: sm_process(): sm_process(): Peer hss.epc.mnc019.mcc425.3gppnetwork.org State Closed Event Start 2018-01-16T09:16:40.871612+02:00 linux-o12d kamailio[13298]: 94(13395) INFO: cdp [peerstatemachine.c:525]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.epc.mnc019.mcc425.3gppnetwork.org 2018-01-16T09:16:40.871636+02:00 linux-o12d kamailio[13298]: 94(13395) INFO: cdp [receiver.c:869]: peer_connect(): peer_connect(): Trying to connect to 10.82.10.85 port 3868 2018-01-16T09:16:40.871782+02:00 linux-o12d kamailio[13298]: 94(13395) INFO: cdp [receiver.c:937]: peer_connect(): peer_connect(): Peer hss.epc.mnc019.mcc425.3gppnetwork.org:3868 connected 2018-01-16T09:16:40.871813+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [receiver.c:697]: receive_loop(): select_recv(): There is something on the fd exchange pipe 2018-01-16T09:16:40.871828+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [receiver.c:706]: receive_loop(): select_recv(): fd exchange pipe says fd [22] for peer 0x7f0626b91c98:[hss.epc.mnc019.mcc425.3gppnetwork.org] 2018-01-16T09:16:40.871910+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:90]: sm_process(): sm_process(): Peer hss.epc.mnc019.mcc425.3gppnetwork.org State Wait_Conn_Ack Event I_Rcv_Conn_Ack 2018-01-16T09:16:40.871933+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [diameter_msg.c:184]: AAANewMessage(): AAANewMessage: param session received null and it's a request!! 2018-01-16T09:16:40.872011+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [diameter_msg.c:81]: AAABuildMsgBuffer(): AAABuildMsgBuffer(): len=204 2018-01-16T09:16:40.872041+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [receiver.c:994]: peer_send_msg(): peer_send_msg(): Pipe push [0x7f0626c02548] 2018-01-16T09:16:40.872064+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [receiver.c:751]: receive_loop(): select_recv(): There is something on the send pipe 2018-01-16T09:16:40.872084+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [receiver.c:764]: receive_loop(): select_recv(): Send pipe says [0x7f0626c02548] 8 2018-01-16T09:16:40.872104+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [diameter_msg.c:410]: AAAFreeMessage(): AAAFreeMessage: Freeing message (0x7f0626c02548) 257 2018-01-16T09:16:40.872277+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [receiver.c:574]: do_receive(): receive_loop(): [hss.epc.mnc019.mcc425.3gppnetwork.org] Recv Version 1 Length 360 2018-01-16T09:16:40.872322+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [receiver.c:1088]: receive_message(): receive_message(): [hss.epc.mnc019.mcc425.3gppnetwork.org] Recv msg 257 2018-01-16T09:16:40.872345+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:90]: sm_process(): sm_process(): Peer hss.epc.mnc019.mcc425.3gppnetwork.org State Wait_I_CEA Event I_Rcv_CEA 2018-01-16T09:16:40.872372+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:692]: count_Supported_Vendor_Id_AVPS(): Found 4 Supported_Vendor AVPS92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 5535 2018-01-16T09:16:40.872389+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 10415 2018-01-16T09:16:40.872405+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 13019 2018-01-16T09:16:40.872420+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 58637 2018-01-16T09:16:40.872438+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 5535 2018-01-16T09:16:40.872453+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 10415 2018-01-16T09:16:40.872468+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 13019 2018-01-16T09:16:40.872486+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 58637 2018-01-16T09:16:40.872504+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 5535 2018-01-16T09:16:40.872523+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 10415 2018-01-16T09:16:40.872539+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 13019 2018-01-16T09:16:40.872554+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:743]: save_peer_applications(): Found Supported Vendor for Application 0: 58637 2018-01-16T09:16:40.872570+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:756]: save_peer_applications(): Found Supported Vendor for Application 1: 5535 2018-01-16T09:16:40.872586+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:756]: save_peer_applications(): Found Supported Vendor for Application 1: 10415 2018-01-16T09:16:40.872601+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:756]: save_peer_applications(): Found Supported Vendor for Application 1: 13019 2018-01-16T09:16:40.872616+02:00 linux-o12d kamailio[13298]: 92(13393) DEBUG: cdp [peerstatemachine.c:756]: save_peer_applications(): Found Supported Vendor for Application 1: 58637 2018-01-16T09:16:40.872634+02:00 linux-o12d kamailio[13298]: 92(13393) CRITICAL: <core> [core/mem/q_malloc.c:145]: qm_debug_frag(): BUG: qm: prev. fragm. tail overwritten(28af01000000, 0)[0x7f0626c038d0:0x7f0626c03908]! Memory allocator was called from cdp: diameter_avp.c:365. Fragment marked by cdp: diameter_avp.c:142. 2018-01-16T09:16:41.054292+02:00 linux-o12d kamailio[13298]: 0(13298) ALERT: <core> [main.c:746]: handle_sigs(): child process 13393 exited by a signal 6 2018-01-16T09:16:41.054403+02:00 linux-o12d kamailio[13298]: 0(13298) ALERT: <core> [main.c:749]: handle_sigs(): core was generated 2018-01-16T09:16:41.054422+02:00 linux-o12d kamailio[13298]: 0(13298) INFO: <core> [main.c:771]: handle_sigs(): terminating due to SIGCHLD 2018-01-16T09:16:41.054438+02:00 linux-o12d kamailio[13298]: 0(13298) DEBUG: <core> [main.c:773]: handle_sigs(): terminating due to SIGCHLD 2018-01-16T09:16:41.054464+02:00 linux-o12d kamailio[13298]: 2(13303) INFO: <core> [main.c:826]: sig_usr(): signal 15 received ... =================================== Attached is wireshark trace. Here is my DiameterPeer.xml: =================================== <?xml version="1.0" encoding="UTF-8"?> <DiameterPeer FQDN="ims110-scscf.epc.mnc019.mcc425.3gppnetwork.org" Realm="epc.mnc019.mcc425.3gppnetwork.org" Vendor_Id="10415" Product_Name="CDiameterPeer" AcceptUnknownPeers="1" DropUnknownOnDisconnect="1" Tc="30" Workers="4" QueueLength="8" TransactionTimeout="5" SessionsHashSize="128" DefaultAuthSessionTimeout="3600" MaxAuthSessionTimeout="3600"> <Peer FQDN="hss.epc.mnc019.mcc425.3gppnetwork.org" Realm="epc.mnc019.mcc425.3gppnetwork.org" port="3868" /> <Acceptor port="3869" bind="10.82.10.56" /> <Auth id="16777216" vendor="10415" />  <DefaultRoute FQDN="ims110-scscf.epc.mnc019.mcc425.3gppnetwork.org" metric="10" /> </DiameterPeer> =================================== It looks like buffer overflow to me but I'm not sure. kamailio version is: =================================== kamailio -v version: kamailio 5.1.0 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled on 05:30:36 Jan 15 2018 with gcc 4.8.5 =================================== OS is openSUSE Leap 42.3. Kernel: Linux linux-o12d 4.4.104-39-default #1 SMP Thu Jan 4 08:11:03 UTC 2018 (7db1912) x86_64 x86_64 x86_64 GNU/Linux Do you have any idea what might be wrong ? It could be bad config but still it should say something in the log without a crash. Regards.

3 5

Problem Proxy
by Nicolas Breuer 18 Jan '18

18 Jan '18

Hello the list, I have a problem on the proxy with the audio between two calls bridged by a UAC. When I made a normal call, no problems. My UAC is nated. UAC > Router > KAMAILIO Frames arrives with private IP in the SDP. U 2018/01/18 21:50:16.798581 217.112.180.235:1024 -> 217.112.180.10:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 217.112.180.10;branch=z9hG4bK2d06.2f2a1856bde881173a3fc413c4136b83.0. Via: SIP/2.0/UDP 84.14.241.179:5060;rport=5060;branch=z9hG4bK0dBe3143bcf7f60a70b. Record-Route: <sip:217.112.180.10;lr=on;ftag=gK0d4dfe6f;did=227.c0d2;nat=yes>. From: <sip:32XXXXXX87@ >;tag=gK0d4dfe6f. Call-ID: 940401290_111374574(a)84.14.241.179. CSeq: 29328 INVITE. Contact: <sip:32XXXXXX61@192.168.2.2:5060;transport=udp>. Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY. Supported: timer,100rel. Server: IP Office 10.1.0.0.0 build 237. Min-SE: 1800. Require: timer. Session-Expires: 1800;refresher=uas. To: <sip:32XXXXXX61@217.112.180.235>;tag=998e429e819ba686. Content-Type: application/sdp. Content-Length: 202. . v=0. o=UserA 3721571424 1025404311 IN IP4 192.168.2.2. s=Session SDP. c=IN IP4 192.168.2.2. t=0 0. m=audio 49154 RTP/AVP 9 101. a=rtpmap:9 G722/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. I don't understand why but the proxy (in case of an incoming call) succeed to determine the public IP. Jan 18 21:40:08 proxy1 rtpproxy[1314]: INFO:rxmit_packets:1fb3f1c6c8dfe738221842406be48450: caller's address filled in: 217.112.180.235:49154 (RTP) Jan 18 21:40:08 proxy1 rtpproxy[1314]: INFO:rxmit_packets:1fb3f1c6c8dfe738221842406be48450: guessing RTCP port for caller to be 49155 Jan 18 21:40:16 proxy1 rtpproxy[1314]: INFO:rxmit_packets:1fb3f1c6c8dfe738221842406be48450: caller's address latched in: 217.112.180.235:49155 (RTCP) Don't know why because the only information in SDP is 192.168.2.2 The Kamailio didn't send the information of the proxy to the UAC , but to the other end as this is an incoming call. So I have audio in this case. When I setup a bridge on the UAC to a second number, we have an issue. ( Kamailio 4.4.6 ) This is the same frames U 2018/01/18 21:51:26.607270 217.112.180.235:1024 -> 217.112.180.10:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 217.112.180.10;branch=z9hG4bK4181.bb7aab84b6fb0aea5836b4d8874406ec.0. Via: SIP/2.0/UDP 84.14.241.179:5060;rport=5060;branch=z9hG4bK0bB16ee5a3d300fee16. Record-Route: <sip:217.112.180.10;lr=on;ftag=gK0b5d7652;did=cc6.5452;nat=yes>. From: <sip:32XXXXXX87@ >;tag=gK0b5d7652. Call-ID: 940248136_13287504(a)84.14.241.179. CSeq: 21946 INVITE. Contact: <sip:32XXXXXX61@192.168.2.2:5060;transport=udp>. Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY. Supported: timer,100rel. Server: IP Office 10.1.0.0.0 build 237. Min-SE: 1800. Require: timer. Session-Expires: 1800;refresher=uas. To: <sip:32XXXXXX61@217.112.180.235>;tag=559c99f5edcab5d4. Content-Type: application/sdp. Content-Length: 202. . v=0. o=UserA 1781830446 4071482272 IN IP4 192.168.2.2. s=Session SDP. c=IN IP4 192.168.2.2. t=0 0. m=audio 49156 RTP/AVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. But in this case no audio RTCP detected but no the RTP. He took the private ip address "192.168.2.2" and this is the reason of the "no audio". Jan 18 21:51:26 proxy1 rtpproxy[1314]: INFO:rtpp_command_ul_handle:940248136_13287504@84.14.241.179: lookup on ports 11264/10446, session timer restarted Jan 18 21:51:26 proxy1 rtpproxy[1314]: INFO:rtpp_command_ul_handle:940248136_13287504@84.14.241.179: pre-filling callee's address with 192.168.2.2:49156 Jan 18 21:51:26 proxy1 rtpproxy[1314]: INFO:rxmit_packets:e1e387824e0753522b7bc55e02090784: callee's address latched in: 79.137.49.139:39176 (RTP) Jan 18 21:51:32 proxy1 rtpproxy[1314]: INFO:rxmit_packets:e1e387824e0753522b7bc55e02090784: caller's address filled in: 217.112.180.235:49155 (RTCP) Jan 18 21:51:32 proxy1 rtpproxy[1314]: INFO:rxmit_packets:940248136_13287504@84.14.241.179: callee's address filled in: 217.112.180.235:49157 (RTCP) I would like to understand why with the first call, no issues to determine the RTP IP and not in the second case,

1 0

SEMS Site?
by Mark Boyce 18 Jan '18

18 Jan '18

Hi all Could anyone tell me where the current SEMS site is? iptel seem to have lost all references and moved their site to wix. Everything search wise points me back at iptel :-( Or is the copy on github it at the moment? https://github.com/sems-server <https://github.com/sems-server> Cheers Mark

2 2

Problems with probing in dispatcher module
by Paulo Ferreira 18 Jan '18

18 Jan '18

Hi list, I'm using dispatcher module and I'm not able to figure it out how to accomplish a simple task regarding gateways availability and probings. My goal is to probe with SIP OPTIONS my three gatways every, for example, 30 seconds. When one, or more, of them respond with unexpected message or simply do not respond at all, dispatcher module put it/them as inactive automatically. I tried several conf scenarios but without success, all with gateway A off. Fore example: 1 -> I configure the three gateways (A, B and C) in conf file (sip.peers as configuration bellow) with flags 8 setted (probing destination). - When I start kamailio with probing mode equal to 1, all gateways present flags AP (using kamctl dispatcher dump) and nothing change (I only see OPTIONS sent to host B and C). - with probing mode setted to 0, all gateways start with flags AP, after 30 seconds, first OPTIONS are sent (only for B a C again), both B and C pass to AX and after more 30 seconds (ping interval defined) gateway A pass also to AX and OPTIONS stop being sent. 2-> Now I configured the gateways in conf file with flags 1 (inactive destination). - With prob mode 1, all started as IX, 30 seconds later it sends OPTIONS only for gw B and C and both change state to AP and A maintain IX. After more 30 seconds, no more OPTIONS are sent and gw A pass also to AP (hoped it remained IP or IX but not happened). I also tried other combinations of these two parameters, but only the onde I described above make me sense for my purpose. Maybe the solution is simple but I'm not getting there or maybe this it is only possible using failure or timeout routes and setting flags manually to gateways :( Can anyone point out the solution for this if it exists? module configuration used: modparam("dispatcher", "list_file", "sip.peers"); modparam("dispatcher", "flags", 2); 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_method", "OPTIONS"); modparam("dispatcher", "ds_ping_from", "sip:ping@test.tt"); modparam("dispatcher", "ds_ping_interval", 30); modparam("dispatcher", "ds_probing_threshold", 1); modparam("dispatcher", "ds_inactive_threshold", 1); modparam("dispatcher", "ds_ping_reply_codes", "class=2;class=4;class=5;class=3"); modparam("dispatcher", "ds_probing_mode", 1); Thanks in advance, Paulo -- ------------------------------------------- Paulo Ferreira VoIP@RCTS - Área de Infraestruturas Aplicacionaisz FCCN http://www.fccn.pt/ Av. do Brasil, n.º 101 1700-066 Lisboa - Portugal Telefone|Phone: +351 218440100; Fax: +351 218472167 Aviso de Confidencialidade/Disclaimer Esta mensagem é exclusivamente destinada ao seu destinatário, podendo conter informação CONFIDENCIAL, cuja divulgação está expressamente vedada nos termos da lei. Caso tenha rececionado indevidamente esta mensagem,solicitamos-lhe que nos comunique esse mesmo facto por esta via ou para o telefone +351 218440100 devendo apagar o seu conteúdo de imediato. This message is intended exclusively for its addressee. It may contain CONFIDENTIAL information protected by law. If this message has been received by error, please notify us via e-mail or by telephone +351 218440100 and delete it immediately.

1 1

Dialog KeepAlive
by Duarte Rocha 18 Jan '18

18 Jan '18

Hey! I'm trying to use the KeepAlive options avaliable in the Dialog modules. For that I use the function dlg_set_property() like this : dlg_set_property("timeout-noreset"); dlg_set_property("ka-dst"); dlg_set_property("ka-src"); However, kamailio can't seem to get the answers from "ka-src". I've tried several scenarios and different call directions and i can never get the answer from the "ka-src". Is there any known issue about this feature ? What arguments kamailio uses to build the OPTIONS request? I think i might be albe to solve the issue if i know this. I have some endpoints behind NAT, Kamailio has multiple IP's and i do number normalization so my proxy works in E.164. I've made some tests and those features don't seem to be the problem, but i cannot be sure. The "ka-dst" works all the time under all situations. Thanks in advance, Cheers

1 0

Re: [SR-Users] app_lua sr.sqlops.query exit status
by Daniel-Constantin Mierla 18 Jan '18

18 Jan '18

How did you take the backtrace, it's not the usual gdb backtrace. Cheers, Daniel On 17.01.18 13:24, jenus(a)cyberchaos.nl wrote: > Daniel, > > Just tested this on another (centos-release-6-9.el6.12.3.x86_64) > machine and here kamailio crashes as well. Not sure if it helps but it > seems to happen on different linux distro's. > > Last part of the kamailio log: > > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.exec.exec_dset(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.exec.exec_msg(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.exec.exec_avp(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1975]: > lua_sr_kemi_register_libs(): initializing kemi sub-module: KSR.exec > (exec) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.lock(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.unlock(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.trylock(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.rand_set_prob(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.rand_reset_prob(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.rand_get_prob(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.rand_event(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.abort(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.pkg_status(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.shm_status(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.pkg_summary(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.shm_summary(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.cfgutils.core_hash(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1975]: > lua_sr_kemi_register_libs(): initializing kemi sub-module: > KSR.cfgutils (cfgutils) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.statistics.update_stat(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.statistics.reset_stat(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1975]: > lua_sr_kemi_register_libs(): initializing kemi sub-module: > KSR.statistics (statistics) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.app_lua.dostring(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.app_lua.dofile(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.app_lua.runstring(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.app_lua.run(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.app_lua.run_p1(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.app_lua.run_p2(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1961]: > lua_sr_kemi_register_libs(): exporting KSR.app_lua.run_p3(...) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1975]: > lua_sr_kemi_register_libs(): initializing kemi sub-module: KSR.app_lua > (app_lua) > 0(13896) DEBUG: app_lua [app_lua_sr.c:1978]: > lua_sr_kemi_register_libs(): module 'KSR' has been initialized > *** glibc detected *** kamailio: realloc(): invalid next size: > 0x0000000001d5f080 *** > ======= Backtrace: ========= > /lib64/libc.so.6[0x30f2a75dee] > /lib64/libc.so.6[0x30f2a7bcca] > /lib64/libc.so.6(realloc+0x158)[0x30f2a7bf08] > /usr/lib64/liblua-5.1.so[0x30fae0fd2c] > /usr/lib64/liblua-5.1.so[0x30fae0bb99] > /usr/lib64/liblua-5.1.so[0x30fae10765] > /usr/lib64/liblua-5.1.so[0x30fae13331] > /usr/lib64/liblua-5.1.so[0x30fae0bcf3] > /usr/lib64/liblua-5.1.so[0x30fae0c137] > /usr/lib64/liblua-5.1.so[0x30fae0c1b2] > /usr/lib64/liblua-5.1.so[0x30fae0c282] > /usr/lib64/liblua-5.1.so(lua_load+0x43)[0x30fae07ac3] > /usr/lib64/liblua-5.1.so(luaL_loadbuffer+0x1c)[0x30fae17d4c] > /usr/lib64/kamailio/modules/app_lua.so(lua_sr_init_probe+0x339)[0x7f042b343e9a] > > /usr/lib64/kamailio/modules/app_lua.so(+0x5f7e5)[0x7f042b3957e5] > kamailio[0x5c16d3] > kamailio(init_child+0x34)[0x5c1a01] > kamailio(main_loop+0x1e19)[0x422782] > kamailio(main+0x5939)[0x42a264] > /lib64/libc.so.6(__libc_start_main+0xfd)[0x30f2a1ed1d] > kamailio[0x418039] > ======= Memory map: ======== > 00400000-00837000 r-xp 00000000 fd:01 > 160801 /usr/sbin/kamailio > 00a37000-00a42000 rw-p 00437000 fd:01 > 160801 /usr/sbin/kamailio > 00a42000-00aef000 rw-p 00000000 00:00 0 > 01c1a000-01ceb000 rw-p 00000000 00:00 0 > 01ceb000-01d8d000 rw-p 00000000 00:00 0 > 30f2200000-30f2220000 r-xp 00000000 fd:01 > 7437 /lib64/ld-2.12.so > 30f2420000-30f2421000 r--p 00020000 fd:01 > 7437 /lib64/ld-2.12.so > 30f2421000-30f2422000 rw-p 00021000 fd:01 > 7437 /lib64/ld-2.12.so > 30f2422000-30f2423000 rw-p 00000000 00:00 0 > 30f2600000-30f2602000 r-xp 00000000 fd:01 > 7533 /lib64/libdl-2.12.so > 30f2602000-30f2802000 ---p 00002000 fd:01 > 7533 /lib64/libdl-2.12.so > 30f2802000-30f2803000 r--p 00002000 fd:01 > 7533 /lib64/libdl-2.12.so > 30f2803000-30f2804000 rw-p 00003000 fd:01 > 7533 /lib64/libdl-2.12.so > 30f2a00000-30f2b8a000 r-xp 00000000 fd:01 > 7531 /lib64/libc-2.12.so > 30f2b8a000-30f2d8a000 ---p 0018a000 fd:01 > 7531 /lib64/libc-2.12.so > 30f2d8a000-30f2d8e000 r--p 0018a000 fd:01 > 7531 /lib64/libc-2.12.so > 30f2d8e000-30f2d90000 rw-p 0018e000 fd:01 > 7531 /lib64/libc-2.12.so > 30f2d90000-30f2d94000 rw-p 00000000 00:00 0 > 30f2e00000-30f2e17000 r-xp 00000000 fd:01 > 7541 /lib64/libpthread-2.12.so > 30f2e17000-30f3017000 ---p 00017000 fd:01 > 7541 /lib64/libpthread-2.12.so > 30f3017000-30f3018000 r--p 00017000 fd:01 > 7541 /lib64/libpthread-2.12.so > 30f3018000-30f3019000 rw-p 00018000 fd:01 > 7541 /lib64/libpthread-2.12.so > 30f3019000-30f301d000 rw-p 00000000 00:00 0 > 30f3200000-30f3207000 r-xp 00000000 fd:01 > 7542 /lib64/librt-2.12.so > 30f3207000-30f3406000 ---p 00007000 fd:01 > 7542 /lib64/librt-2.12.so > 30f3406000-30f3407000 r--p 00006000 fd:01 > 7542 /lib64/librt-2.12.so > 30f3407000-30f3408000 rw-p 00007000 fd:01 > 7542 /lib64/librt-2.12.so > 30f3600000-30f3615000 r-xp 00000000 fd:01 > 7538 /lib64/libz.so.1.2.3 > 30f3615000-30f3814000 ---p 00015000 fd:01 > 7538 /lib64/libz.so.1.2.3 > 30f3814000-30f3815000 r--p 00014000 fd:01 > 7538 /lib64/libz.so.1.2.3 > 30f3815000-30f3816000 rw-p 00015000 fd:01 > 7538 /lib64/libz.so.1.2.3 > 30f3a00000-30f3a83000 r-xp 00000000 fd:01 > 7539 /lib64/libm-2.12.so > 30f3a83000-30f3c82000 ---p 00083000 fd:01 > 7539 /lib64/libm-2.12.so > 30f3c82000-30f3c83000 r--p 00082000 fd:01 > 7539 /lib64/libm-2.12.so > 30f3c83000-30f3c84000 rw-p 00083000 fd:01 > 7539 /lib64/libm-2.12.so > 30f3e00000-30f3e1d000 r-xp 00000000 fd:01 > 7547 /lib64/libselinux.so.1 > 30f3e1d000-30f401c000 ---p 0001d000 fd:01 > 7547 /lib64/libselinux.so.1 > 30f401c000-30f401d000 r--p 0001c000 fd:01 > 7547 /lib64/libselinux.so.1 > 30f401d000-30f401e000 rw-p 0001d000 fd:01 > 7547 /lib64/libselinux.so.1 > 30f401e000-30f401f000 rw-p 00000000 00:00 0 > 30f4200000-30f42a1000 r-xp 00000000 fd:01 > 140158 /usr/lib64/libnetsnmp.so.20.0.0 > 30f42a1000-30f44a0000 ---p 000a1000 fd:01 > 140158 /usr/lib64/libnetsnmp.so.20.0.0 > 30f44a0000-30f44a3000 r--p 000a0000 fd:01 > 140158 /usr/lib64/libnetsnmp.so.20.0.0 > 30f44a3000-30f44a5000 rw-p 000a3000 fd:01 > 140158 /usr/lib64/libnetsnmp.so.20.0.0 > 30f44a5000-30f44db000 rw-p 00000000 00:00 0 > 30f4600000-30f4616000 r-xp 00000000 fd:01 > 7548 /lib64/libgcc_s-4.4.7-20120601.so.1 > 30f4616000-30f4815000 ---p 00016000 fd:01 > 7548 /lib64/libgcc_s-4.4.7-20120601.so.1 > 30f4815000-30f4816000 rw-p 00015000 fd:01 > 7548 /lib64/libgcc_s-4.4.7-20120601.so.1 > 30f4a00000-30f4a16000 r-xp 00000000 fd:01 > 4581 /lib64/libnsl-2.12.so > 30f4a16000-30f4c15000 ---p 00016000 fd:01 > 4581 /lib64/libnsl-2.12.so > 30f4c15000-30f4c16000 r--p 00015000 fd:01 > 4581 /lib64/libnsl-2.12.so > 30f4c16000-30f4c17000 rw-p 00016000 fd:01 > 4581 /lib64/libnsl-2.12.so > 30f4c17000-30f4c19000 rw-p 00000000 00:00 0 > 30f4e00000-30f4f3a000 r-xp 00000000 fd:01 > 161929 /usr/lib64/libnss3.so > 30f4f3a000-30f5139000 ---p 0013a000 fd:01 > 161929 /usr/lib64/libnss3.so > 30f5139000-30f513f000 r--p 00139000 fd:01 > 161929 /usr/lib64/libnss3.so > 30f513f000-30f5141000 rw-p 0013f000 fd:01 > 161929 /usr/lib64/libnss3.so > 30f5141000-30f5143000 rw-p 00000000 00:00 0 > 30f5200000-30f5226000 r-xp 00000000 fd:01 > 161928 /usr/lib64/libnssutil3.so > 30f5226000-30f5425000 ---p 00026000 fd:01 > 161928 /usr/lib64/libnssutil3.so > 30f5425000-30f542c000 r--p 00025000 fd:01 > 161928 /usr/lib64/libnssutil3.so > 30f542c000-30f542d000 rw-p 0002c000 fd:01 > 161928 /usr/lib64/libnssutil3.so > 30f5600000-30f5604000 r-xp 00000000 fd:01 > 7552 /lib64/libplc4.so > 30f5604000-30f5803000 ---p 00004000 fd:01 > 7552 /lib64/libplc4.so > 30f5803000-30f5804000 r--p 00003000 fd:01 > 7552 /lib64/libplc4.so > 30f5804000-30f5805000 rw-p 00004000 fd:01 > 7552 /lib64/libplc4.so > 30f5a00000-30f5a39000 r-xp 00000000 fd:01 > 7551 /lib64/libnspr4.so > 30f5a39000-30f5c39000 ---p 00039000 fd:01 > 7551 /lib64/libnspr4.so > 30f5c39000-30f5c3a000 r--p 00039000 fd:01 > 7551 /lib64/libnspr4.so > 30f5c3a000-30f5c3c000 rw-p 0003a000 fd:01 > 7551 /lib64/libnspr4.so > 30f5c3c000-30f5c3e000 rw-p 00000000 00:00 0 > 30f5e00000-30f5e03000 r-xp 00000000 fd:01 > 7553 /lib64/libplds4.so > 30f5e03000-30f6002000 ---p 00003000 fd:01 > 7553 /lib64/libplds4.so > 30f6002000-30f6003000 r--p 00002000 fd:01 > 7553 /lib64/libplds4.so > 30f6003000-30f6004000 rw-p 00003000 fd:01 > 7553 /lib64/libplds4.so > 30f6200000-30f6216000 r-xp 00000000 fd:01 > 7559 /lib64/libresolv-2.12.so > 30f6216000-30f6416000 ---p 00016000 fd:01 > 7559 /lib64/libresolv-2.12.so > 30f6416000-30f6417000 r--p 00016000 fd:01 > 7559 /lib64/libresolv-2.12.so > 30f6417000-30f6418000 rw-p 00017000 fd:01 > 7559 /lib64/libresolv-2.12.so > 30f6418000-30f641a000 rw-p 00000000 00:00 0 > 30f6600000-30f6604000 r-xp 00000000 fd:01 > 7555 /lib64/libattr.so.1.1.0 > 30f6604000-30f6803000 ---p 00004000 fd:01 > 7555 /lib64/libattr.so.1.1.0 > 30f6803000-30f6804000 r--p 00003000 fd:01 > 7555 /lib64/libattr.so.1.1.0 > 30f6804000-30f6805000 rw-p 00004000 fd:01 > 7555 /lib64/libattr.so.1.1.0 > 30f6a00000-30f6a08000 r-xp 00000000 fd:01 > 7540 /lib64/libpopt.so.0.0.0 > 30f6a08000-30f6c08000 ---p 00008000 fd:01 > 7540 /lib64/libpopt.so.0.0.0 > 30f6c08000-30f6c09000 rw-p 00008000 fd:01 > 7540 /lib64/libpopt.so.0.0.0 > 30f6e00000-30f6fba000 r-xp 00000000 fd:01 > 145222 /usr/lib64/libcrypto.so.1.0.1e > 30f6fba000-30f71ba000 ---p 001ba000 fd:01 > 145222 /usr/lib64/libcrypto.so.1.0.1e > 30f71ba000-30f71d5000 r--p 001ba000 fd:01 > 145222 /usr/lib64/libcrypto.so.1.0.1e > 30f71d5000-30f71e1000 rw-p 001d5000 fd:01 > 145222 /usr/lib64/libcrypto.so.1.0.1e > 30f71e1000-30f71e5000 rw-p 00000000 00:00 0 > 30f7200000-30f736f000 r-xp 00000000 fd:01 > 7558 /lib64/libdb-4.7.so > 30f736f000-30f756f000 ---p 0016f000 fd:01 > 7558 /lib64/libdb-4.7.so > 30f756f000-30f7574000 rw-p 0016f000 fd:01 > 7558 /lib64/libdb-4.7.so > 30f7574000-30f7575000 rw-p 00000000 00:00 0 > 30f7600000-30f7607000 r-xp 00000000 fd:01 > 7557 /lib64/libacl.so.1.1.0 > 30f7607000-30f7806000 ---p 00007000 fd:01 > 7557 /lib64/libacl.so.1.1.0 > 30f7806000-30f7807000 r--p 00006000 fd:01 > 7557 /lib64/libacl.so.1.1.0 > 30f7807000-30f7808000 rw-p 00007000 fd:01 > 7557 /lib64/libacl.so.1.1.0 > 30f7a00000-30f7a15000 r-xp 00000000 fd:01 > 161930 /usr/lib64/libelf-0.164.so > 30f7a15000-30f7c14000 ---p 00015000 fd:01 > 161930 /usr/lib64/libelf-0.164.so > 30f7c14000-30f7c15000 r--p 00014000 fd:01 > 161930 /usr/lib64/libelf-0.164.so > 30f7c15000-30f7c16000 rw-p 00015000 fd:01 > 161930 /usr/lib64/libelf-0.164.so > 30f7e00000-30f7e20000 r-xp 00000000 fd:01 > 161931 /usr/lib64/liblzma.so.0.0.0 > 30f7e20000-30f8020000 ---p 00020000 fd:01 > 161931 /usr/lib64/liblzma.so.0.0.0 > 30f8020000-30f8021000 rw-p 00020000 fd:01 > 161931 /usr/lib64/liblzma.so.0.0.0 > 30f8200000-30f8210000 r-xp 00000000 fd:01 > 7554 /lib64/libbz2.so.1.0.4 > 30f8210000-30f840f000 ---p 00010000 fd:01 > 7554 /lib64/libbz2.so.1.0.4 > 30f840f000-30f8411000 rw-p 0000f000 fd:01 > 7554 /lib64/libbz2.so.1.0.4 > 30f8600000-30f8607000 r-xp 00000000 fd:01 > 7535 /lib64/libcrypt-2.12.so > 30f8607000-30f8807000 ---p 00007000 fd:01 > 7535 /lib64/libcrypt-2.12.so > 30f8807000-30f8808000 r--p 00007000 fd:01 > 7535 /lib64/libcrypt-2.12.so > 30f8808000-30f8809000 rw-p 00008000 fd:01 > 7535 /lib64/libcrypt-2.12.so > 30f8809000-30f8837000 rw-p 00000000 00:00 0 > 30f8a00000-30f8a04000 r-xp 00000000 fd:01 > 7556 /lib64/libcap.so.2.16 > 30f8a04000-30f8c03000 ---p 00004000 fd:01 > 7556 /lib64/libcap.so.2.16 > 30f8c03000-30f8c04000 rw-p 00003000 fd:01 > 7556 /lib64/libcap.so.2.16 > 30f8e00000-30f8e02000 r-xp 00000000 fd:01 > 7534 /lib64/libfreebl3.so > 30f8e02000-30f9001000 ---p 00002000 fd:01 > 7534 /lib64/libfreebl3.so > 30f9001000-30f9002000 r--p 00001000 fd:01 > 7534 /lib64/libfreebl3.so > 30f9002000-30f9003000 rw-p 00002000 fd:01 > 7534 /lib64/libfreebl3.so > 30f9200000-30f9228000 r-xp 00000000 fd:01 > 161940 /usr/lib64/libsmime3.so > 30f9228000-30f9427000 ---p 00028000 fd:01 > 161940 /usr/lib64/libsmime3.so > 30f9427000-30f942b000 r--p 00027000 fd:01 > 161940 /usr/lib64/libsmime3.so > 30f942b000-30f942c000 rw-p 0002b000 fd:01 > 161940 /usr/lib64/libsmime3.so > 30f9600000-30f9603000 r-xp 00000000 fd:01 > 7568 /lib64/libcom_err.so.2.1 > 30f9603000-30f9802000 ---p 00003000 fd:01 > 7568 /lib64/libcom_err.so.2.1 > 30f9802000-30f9803000 r--p 00002000 fd:01 > 7568 /lib64/libcom_err.so.2.1 > 30f9803000-30f9804000 rw-p 00003000 fd:01 > 7568 /lib64/libcom_err.so.2.1 > 30f9a00000-30f9a47000 r-xp 00000000 fd:01 > 145913 /usr/lib64/libssl3.so > 30f9a47000-30f9c47000 ---p 00047000 fd:01 > 145913 /usr/lib64/libssl3.so > 30f9c47000-30f9c4b000 r--p 00047000 fd:01 > 145913 /usr/lib64/libssl3.so > 30f9c4b000-30f9c4c000 rw-p 0004b000 fd:01 > 145913 /usr/lib64/libssl3.so > 30f9c4c000-30f9c4d000 rw-p 00000000 00:00 0 > 30f9e00000-30f9f62000 r-xp 00000000 fd:01 > 135162 /usr/lib64/perl5/CORE/libperl.so > 30f9f62000-30fa162000 ---p 00162000 fd:01 > 135162 /usr/lib64/perl5/CORE/libperl.so > 30fa162000-30fa16b000 rw-p 00162000 fd:01 > 135162 /usr/lib64/perl5/CORE/libperl.so > 30fa200000-30fa349000 r-xp 00000000 fd:01 > 161926 /usr/lib64/libxml2.so.2.7.6 > 30fa349000-30fa548000 ---p 00149000 fd:01 > 161926 /usr/lib64/libxml2.so.2.7.6 > 30fa548000-30fa552000 rw-p 00148000 fd:01 > 161926 /usr/lib64/libxml2.so.2.7.6 > 30fa552000-30fa553000 rw-p 00000000 00:00 0 > 30fa600000-30fa664000 r-xp 00000000 fd:01 > 161934 /usr/lib64/librpm.so.1.0.0 > 30fa664000-30fa863000 ---p 00064000 fd:01 > 161934 /usr/lib64/librpm.so.1.0.0 > 30fa863000-30fa86a000 rw-p 00063000 fd:01 > 161934 /usr/lib64/librpm.so.1.0.0 > 30fa86a000-30fa86b000 rw-p 00000000 00:00 0 > 30faa00000-30faa2a000 r-xp 00000000 fd:01 > 161933 /usr/lib64/librpmio.so.1.0.0 > 30faa2a000-30fac2a000 ---p 0002a000 fd:01 > 161933 /usr/lib64/librpmio.so.1.0.0 > 30fac2a000-30fac2d000 rw-p 0002a000 fd:01 > 161933 /usr/lib64/librpmio.so.1.0.0 > 30fac2d000-30fac2f000 rw-p 00000000 00:00 0 > 30fae00000-30fae2b000 r-xp 00000000 fd:01 > 161932 /usr/lib64/liblua-5.1.so > 30fae2b000-30fb02b000 ---p 0002b000 fd:01 > 161932 /usr/lib64/liblua-5.1.so > 30fb02b000-30fb02d000 rw-p 0002b000 fd:01 > 161932 /usr/lib64/liblua-5.1.so > 30fb200000-30fb390000 r-xp 00000000 fd:01 > 161962 /usr/lib64/libnetsnmpmibs.so.20.0.0 > 30fb390000-30fb58f000 ---p 00190000 fd:01 > 161962 /usr/lib64/libnetsnmpmibs.so.20.0.0 > 30fb58f000-30fb595000 r--p 0018f000 fd:01 > 161962 /usr/lib64/libnetsnmpmibs.so.20.0.0 > 30fb595000-30fb59c000 rw-p 00195000 fd:01 > 161962 /usr/lib64/libnetsnmpmibs.so.20.0.0 > 30fb59c000-30fb6c8000 rw-p 00000000 00:00 0 > 30fb800000-30fb825000 r-xp 00000000 fd:01 > 161960 /usr/lib64/libnetsnmphelpers.so.20.0.0 > 30fb825000-30fba24000 ---p 00025000 fd:01 > 161960 /usr/lib64/libnetsnmphelpers.so.20.0.0 > 30fba24000-30fba25000 r--p 00024000 fd:01 > 161960 /usr/lib64/libnetsnmphelpers.so.20.0.0 > 30fba25000-30fba26000 rw-p 00025000 fd:01 > 161960 /usr/lib64/libnetsnmphelpers.so.20.0.0 > 30fbc00000-30fbc48000 r-xp 00000000 fd:01 > 134861 /usr/lib64/libnetsnmpagent.so.20.0.0 > 30fbc48000-30fbe48000 ---p 00048000 fd:01 > 134861 /usr/lib64/libnetsnmpagent.so.20.0.0 > 30fbe48000-30fbe4a000 r--p 00048000 fd:01 > 134861 /usr/lib64/libnetsnmpagent.so.20.0.0 > 30fbe4a000-30fbe4b000 rw-p 0004a000 fd:01 > 134861 /usr/lib64/libnetsnmpagent.so.20.0.0 > 30fbe4b000-30fbe4c000 rw-p 00000000 00:00 0 > 30fc000000-30fc00f000 r-xp 00000000 fd:01 > 161961 /usr/lib64/libsensors.so.4.2.0 > 30fc00f000-30fc20f000 ---p 0000f000 fd:01 > 161961 /usr/lib64/libsensors.so.4.2.0 > 30fc20f000-30fc210000 rw-p 0000f000 fd:01 > 161961 /usr/lib64/libsensors.so.4.2.0 > 30fca00000-30fcadc000 r-xp 00000000 fd:01 > 7569 /lib64/libkrb5.so.3.3 > 30fcadc000-30fccdb000 ---p 000dc000 fd:01 > 7569 /lib64/libkrb5.so.3.3 > 30fccdb000-30fcce5000 r--p 000db000 fd:01 > 7569 /lib64/libkrb5.so.3.3 > 30fcce5000-30fcce7000 rw-p 000e5000 fd:01 > 7569 /lib64/libkrb5.so.3.3 > 30fce00000-30fce29000 r-xp 00000000 fd:01 > 7567 /lib64/libk5crypto.so.3.1 > 30fce29000-30fd029000 ---p 00029000 fd:01 > 7567 /lib64/libk5crypto.so.3.1 > 30fd029000-30fd02a000 r--p 00029000 fd:01 > 7567 /lib64/libk5crypto.so.3.1 > 30fd02a000-30fd02b000 rw-p 0002a000 fd:01 > 7567 /lib64/libk5crypto.so.3.1 > 30fd02b000-30fd02c000 rw-p 00000000 00:00 0 > 30fd200000-30fd241000 r-xp 00000000 fd:01 > 7570 /lib64/libgssapi_krb5.so.2.2 > 30fd241000-30fd441000 ---p 00041000 fd:01 > 7570 /lib64/libgssapi_krb5.so.2.2 > 30fd441000-30fd442000 r--p 00041000 fd:01 > 7570 /lib64/libgssapi_krb5.so.2.2 > 30fd442000-30fd444000 rw-p 00042000 fd:01 > 7570 /lib64/libgssapi_krb5.so.2.2 > 30fd600000-30fd60a000 r-xp 00000000 fd:01 > 7566 /lib64/libkrb5support.so.0.1 > 30fd60a000-30fd809000 ---p 0000a000 fd:01 > 7566 /lib64/libkrb5support.so.0.1 > 30fd809000-30fd80a000 r--p 00009000 fd:01 > 7566 /lib64/libkrb5support.so.0.1 > 30fd80a000-30fd80b000 rw-p 0000a000 fd:01 > 7566 /lib64/libkrb5support.so.0.1 > 30fda00000-30fda02000 r-xp 00000000 fd:01 > 7565 /lib64/libkeyutils.so.1.3 > 30fda02000-30fdc01000 ---p 00002000 fd:01 > 7565 /lib64/libkeyutils.so.1.3 > 30fdc01000-30fdc02000 r--p 00001000 fd:01 > 7565 /lib64/libkeyutils.so.1.3 > 30fdc02000-30fdc03000 rw-p 00002000 fd:01 > 7565 /lib64/libkeyutils.so.1.3 > 30fde00000-30fde62000 r-xp 00000000 fd:01 > 161946 /usr/lib64/libssl.so.1.0.1e > 30fde62000-30fe062000 ---p 00062000 fd:01 > 161946 /usr/lib64/libssl.so.1.0.1e > 30fe062000-30fe066000 r--p 00062000 fd:01 > 161946 /usr/lib64/libssl.so.1.0.1e > 30fe066000-30fe06c000 rw-p 00066000 fd:01 > 161946 /usr/lib64/libssl.so.1.0.1e > 30fe200000-30fe232000 r-xp 00000000 fd:01 > 7562 /lib64/libidn.so.11.6.1 > 30fe232000-30fe431000 ---p 00032000 fd:01 > 7562 /lib64/libidn.so.11.6.1 > 30fe431000-30fe432000 rw-p 00031000 fd:01 > 7562 /lib64/libidn.so.11.6.1 > 30fe600000-30fe619000 r-xp 00000000 fd:01 > 145736 /usr/lib64/libsasl2.so.2.0.23 > 30fe619000-30fe818000 ---p 00019000 fd:01 > 145736 /usr/lib64/libsasl2.so.2.0.23 > 30fe818000-30fe819000 r--p 00018000 fd:01 > 145736 /usr/lib64/libsasl2.so.2.0.23 > 30fe819000-30fe81a000 rw-p 00019000 fd:01 > 145736 /usr/lib64/libsasl2.so.2.0.23 > 30fea00000-30fea4e000 r-xp 00000000 fd:01 > 7564 /lib64/libldap-2.4.so.2.10.3 > 30fea4e000-30fec4d000 ---p 0004e000 fd:01 > 7564 /lib64/libldap-2.4.so.2.10.3 > 30fec4d000-30fec4f000 r--p 0004d000 fd:01 > 7564 /lib64/libldap-2.4.so.2.10.3 > 30fec4f000-30fec51000 rw-p 0004f000 fd:01 > 7564 /lib64/libldap-2.4.so.2.10.3 > 30fee00000-30fee0e000 r-xp 00000000 fd:01 > 7563 /lib64/liblber-2.4.so.2.10.3 > 30fee0e000-30ff00d000 ---p 0000e000 fd:01 > 7563 /lib64/liblber-2.4.so.2.10.3 > 30ff00d000-30ff00e000 r--p 0000d000 fd:01 > 7563 /lib64/liblber-2.4.so.2.10.3 > 30ff00e000-30ff00f000 rw-p 0000e000 fd:01 > 7563 /lib64/liblber-2.4.so.2.10.3 > 30ff200000-30ff227000 r-xp 00000000 fd:01 > 161947 /usr/lib64/libssh2.so.1.0.1 > 30ff227000-30ff426000 ---p 00027000 fd:01 > 161947 /usr/lib64/libssh2.so.1.0.1 > 30ff426000-30ff428000 rw-p 00026000 fd:01 > 161947 /usr/lib64/libssh2.so.1.0.1 > 30ff600000-30ff653000 r-xp 00000000 fd:01 > 140998 /usr/lib64/libcurl.so.4.1.1 > 30ff653000-30ff852000 ---p 00053000 fd:01 > 140998 /usr/lib64/libcurl.so.4.1.1 > 30ff852000-30ff855000 rw-p 00052000 fd:01 > 140998 /usr/lib64/libcurl.so.4.1.1 > 3baec00000-3baec2c000 r-xp 00000000 fd:01 > 7511 /lib64/libpcre.so.0.0.1 > 3baec2c000-3baee2c000 ---p 0002c000 fd:01 > 7511 /lib64/libpcre.so.0.0.1 > 3baee2c000-3baee2d000 rw-p 0002c000 fd:01 > 7511 /lib64/libpcre.so.0.0.1 > 7f03e4000000-7f03e4021000 rw-p 00000000 00:00 0 > 7f03e4021000-7f03e8000000 ---p 00000000 00:00 0 > 7f03eaf22000-7f03eaf27000 r-xp 00000000 fd:01 > 327 /lib64/libnss_dns-2.12.so > 7f03eaf27000-7f03eb126000 ---p 00005000 fd:01 > 327 /lib64/libnss_dns-2.12.so > 7f03eb126000-7f03eb127000 r--p 00004000 fd:01 > 327 /lib64/libnss_dns-2.12.so > 7f03eb127000-7f03eb128000 rw-p 00005000 fd:01 > 327 /lib64/libnss_dns-2.12.so > 7f03eb128000-7f03eb135000 r-xp 00000000 fd:01 > 329 /lib64/libnss_files-2.12.so > 7f03eb135000-7f03eb334000 ---p 0000d000 fd:01 > 329 /lib64/libnss_files-2.12.so > 7f03eb334000-7f03eb335000 r--p 0000c000 fd:01 > 329 /lib64/libnss_files-2.12.so > 7f03eb335000-7f03eb336000 rw-p 0000d000 fd:01 > 329 /lib64/libnss_files-2.12.so > 7f03eb336000-7f042b336000 rw-s 00000000 00:04 > 30666920 /dev/zero (deleted) > 7f042b336000-7f042b3e0000 r-xp 00000000 fd:01 > 161143 /usr/lib64/kamailio/modules/app_lua.so > 7f042b3e0000-7f042b5df000 ---p 000aa000 fd:01 > 161143 /usr/lib64/kamailio/modules/app_lua.so > 7f042b5df000-7f042b5e5000 rw-p 000a9000 fd:01 > 161143 /usr/lib64/kamailio/modules/app_lua.so > 7f042b5e5000-7f042b5e7000 rw-p 00000000 00:00 0 > 7f042b5e7000-7f042b5ee000 r-xp 00000000 fd:01 > 160777 /usr/lib64/kamailio/modules/statistics.so > 7f042b5ee000-7f042b7ed000 ---p 00007000 fd:01 > 160777 /usr/lib64/kamailio/modules/statistics.so > 7f042b7ed000-7f042b7ee000 rw-p 00006000 fd:01 > 160777 /usr/lib64/kamailio/modules/statistics.so > 7f042b7ee000-7f042b7ff000 r-xp 00000000 fd:01 > 160705 /usr/lib64/kamailio/modules/cfgutils.so > 7f042b7ff000-7f042b9ff000 ---p 00011000 fd:01 > 160705 /usr/lib64/kamailio/modules/cfgutils.so > 7f042b9ff000-7f042ba00000 rw-p 00011000 fd:01 > 160705 /usr/lib64/kamailio/modules/cfgutils.so > 7f042ba00000-7f042ba15000 r-xp 00000000 fd:01 > 160722 /usr/lib64/kamailio/modules/exec.so > 7f042ba15000-7f042bc15000 ---p 00015000 fd:01 > 160722 /usr/lib64/kamailio/modules/exec.so > 7f042bc15000-7f042bc16000 rw-p 00015000 fd:01 > 160722 /usr/lib64/kamailio/modules/exec.so > 7f042bc16000-7f042bc1c000 r-xp 00000000 fd:01 > 160760 /usr/lib64/kamailio/modules/rtimer.so > 7f042bc1c000-7f042be1c000 ---p 00006000 fd:01 > 160760 /usr/lib64/kamailio/modules/rtimer.so > 7f042be1c000-7f042be1d000 rw-p 00006000 fd:01 > 160760 /usr/lib64/kamailio/modules/rtimer.so > 7f042be1d000-7f042be29000 r-xp 00000000 fd:01 > 161712 /usr/lib64/libjansson.so.4.9.0 > 7f042be29000-7f042c028000 ---p 0000c000 fd:01 > 161712 /usr/lib64/libjansson.so.4.9.0 > 7f042c028000-7f042c029000 rw-p 0000b000 fd:01 > 161712 /usr/lib64/libjansson.so.4.9.0 > 7f042c029000-7f042c038000 r-xp 00000000 fd:01 > 161110 /usr/lib64/kamailio/modules/jansson.so > 7f042c038000-7f042c237000 ---p 0000f000 fd:01 > 161110 /usr/lib64/kamailio/modules/jansson.so > 7f042c237000-7f042c238000 rw-p 0000e000 fd:01 > 161110 /usr/lib64/kamailio/modules/jansson.so > 7f042c238000-7f042c23a000 r-xp 00000000 fd:01 > 7577 /lib64/libutil-2.12.so > 7f042c23a000-7f042c439000 ---p 00002000 fd:01 > 7577 /lib64/libutil-2.12.so > 7f042c439000-7f042c43a000 r--p 00001000 fd:01 > 7577 /lib64/libutil-2.12.so > 7f042c43a000-7f042c43b000 rw-p 00002000 fd:01 > 7577 /lib64/libutil-2.12.so > 7f042c43b000-7f042c443000 r-xp 00000000 fd:01 > 3922 /lib64/libwrap.so.0.7.6 > 7f042c443000-7f042c643000 ---p 00008000 fd:01 > 3922 /lib64/libwrap.so.0.7.6 > 7f042c643000-7f042c644000 r--p 00008000 fd:01 > 3922 /lib64/libwrap.so.0.7.6 > 7f042c644000-7f042c645000 rw-p 00009000 fd:01 > 3922 /lib64/libwrap.so.0.7.6 > 7f042c645000-7f042c646000 rw-p 00000000 00:00 0 > 7f042c646000-7f042c677000 r-xp 00000000 fd:01 > 161120 /usr/lib64/kamailio/modules/snmpstats.so > 7f042c677000-7f042c876000 ---p 00031000 fd:01 > 161120 /usr/lib64/kamailio/modules/snmpstats.so > 7f042c876000-7f042c87a000 rw-p 00030000 fd:01 > 161120 /usr/lib64/kamailio/modules/snmpstats.so > 7f042c87a000-7f042c889000 r-xp 00000000 fd:01 > 160797 /usr/lib64/kamailio/modules/xhttp.so > 7f042c889000-7f042ca89000 ---p 0000f000 fd:01 > 160797 /usr/lib64/kamailio/modules/xhttp.so > 7f042ca89000-7f042ca8a000 rw-p 0000f000 fd:01 > 160797 /usr/lib64/kamailio/modules/xhttp.so > 7f042ca8a000-7f042ca8f000 r-xp 00000000 fd:01 > 145920 /usr/lib64/kamailio/libtrie.so.1.0 > 7f042ca8f000-7f042cc8e000 ---p 00005000 fd:01 > 145920 /usr/lib64/kamailio/libtrie.so.1.0 > 7f042cc8e000-7f042cc8f000 rw-p 00004000 fd:01 > 145920 /usr/lib64/kamailio/libtrie.so.1.0 > 7f042cc8f000-7f042cca1000 r-xp 00000000 fd:01 > 160795 /usr/lib64/kamailio/modules/userblacklist.so > 7f042cca1000-7f042cea1000 ---p 00012000 fd:01 > 160795 /usr/lib64/kamailio/modules/userblacklist.so > 7f042cea1000-7f042cea2000 rw-p 00012000 fd:01 > 160795 /usr/lib64/kamailio/modules/userblacklist.so > 7f042cea2000-7f042cf58000 r-xp 00000000 fd:01 > 160714 /usr/lib64/kamailio/modules/dialog.so > 7f042cf58000-7f042d157000 ---p 000b6000 fd:01 > 160714 /usr/lib64/kamailio/modules/dialog.so > 7f042d157000-7f042d15a000 rw-p 000b5000 fd:01 > 160714 /usr/lib64/kamailio/modules/dialog.so > 7f042d15a000-7f042d183000 r-xp 00000000 fd:01 > 160710 /usr/lib64/kamailio/modules/db_cluster.so > 7f042d183000-7f042d382000 ---p 00029000 fd:01 > 160710 /usr/lib64/kamailio/modules/db_cluster.so > 7f042d382000-7f042d383000 rw-p 00028000 fd:01 > 160710 /usr/lib64/kamailio/modules/db_cluster.so > 7f042d383000-7f042d38d000 r-xp 00000000 fd:01 > 160746 /usr/lib64/kamailio/modules/path.so > 7f042d38d000-7f042d58d000 ---p 0000a000 fd:01 > 160746 /usr/lib64/kamailio/modules/path.so > 7f042d58d000-7f042d58e000 rw-p 0000a000 fd:01 > 160746 /usr/lib64/kamailio/modules/path.so > 7f042d58e000-7f042d5c2000 r-xp 00000000 fd:01 > 161131 /usr/lib64/kamailio/modules/dialplan.so > 7f042d5c2000-7f042d7c2000 ---p 00034000 fd:01 > 161131 /usr/lib64/kamailio/modules/dialplan.so > 7f042d7c2000-7f042d7c3000 rw-p 00034000 fd:01 > 161131 /usr/lib64/kamailio/modules/dialplan.so > 7f042d7c3000-7f042d7df000 r-xp 00000000 fd:01 > 160775 /usr/lib64/kamailio/modules/sqlops.so > 7f042d7df000-7f042d9df000 ---p 0001c000 fd:01 > 160775 /usr/lib64/kamailio/modules/sqlops.so > 7f042d9df000-7f042d9e0000 rw-p 0001c000 fd:01 > 160775 /usr/lib64/kamailio/modules/sqlops.so > 7f042d9e0000-7f042da3a000 r-xp 00000000 fd:01 > 160787 /usr/lib64/kamailio/modules/uac.so > 7f042da3a000-7f042dc3a000 ---p 0005a000 fd:01 > 160787 /usr/lib64/kamailio/modules/uac.so > 7f042dc3a000-7f042dc3c000 rw-p 0005a000 fd:01 > 160787 /usr/lib64/kamailio/modules/uac.so > 7f042dc3c000-7f042dc47000 rw-p 00000000 00:00 0 > 7f042dc47000-7f042dc8e000 r-xp 00000000 fd:01 > 160522 /usr/lib64/kamailio/modules/avpops.so > 7f042dc8e000-7f042de8d000 ---p 00047000 fd:01 > 160522 /usr/lib64/kamailio/modules/avpops.so > 7f042de8d000-7f042de8f000 rw-p 00046000 fd:01 > 160522 /usr/lib64/kamailio/modules/avpops.so > 7f042de8f000-7f042de9c000 r-xp 00000000 fd:01 > 160794 /usr/lib64/kamailio/modules/uri_db.so > 7f042de9c000-7f042e09b000 ---p 0000d000 fd:01 > 160794 /usr/lib64/kamailio/modules/uri_db.so > 7f042e09b000-7f042e09c000 rw-p 0000c000 fd:01 > 160794 /usr/lib64/kamailio/modules/uri_db.so > 7f042e09c000-7f042e0e8000 r-xp 00000000 fd:01 > 160715 /usr/lib64/kamailio/modules/dispatcher.so > 7f042e0e8000-7f042e2e8000 ---p 0004c000 fd:01 > 160715 /usr/lib64/kamailio/modules/dispatcher.so > 7f042e2e8000-7f042e2ea000 rw-p 0004c000 fd:01 > 160715 /usr/lib64/kamailio/modules/dispatcher.so > 7f042e2ea000-7f042e303000 r-xp 00000000 fd:01 > 161139 /usr/lib64/kamailio/modules/xmlrpc.so > 7f042e303000-7f042e503000 ---p 00019000 fd:01 > 161139 /usr/lib64/kamailio/modules/xmlrpc.so > 7f042e503000-7f042e504000 rw-p 00019000 fd:01 > 161139 /usr/lib64/kamailio/modules/xmlrpc.so > 7f042e504000-7f042e505000 rw-p 00000000 00:00 0 > 7f042e505000-7f042e549000 r-xp 00000000 fd:01 > 160727 /usr/lib64/kamailio/modules/htable.so > 7f042e549000-7f042e748000 ---p 00044000 fd:01 > 160727 /usr/lib64/kamailio/modules/htable.so > 7f042e748000-7f042e74a000 rw-p 00043000 fd:01 > 160727 /usr/lib64/kamailio/modules/htable.so > 7f042e74a000-7f042e74b000 rw-p 00000000 00:00 0 > 7f042e74b000-7f042e764000 r-xp 00000000 fd:01 > 161137 /usr/lib64/kamailio/modules/dmq_usrloc.so > 7f042e764000-7f042e964000 ---p 00019000 fd:01 > 161137 /usr/lib64/kamailio/modules/dmq_usrloc.so > 7f042e964000-7f042e965000 rw-p 00019000 fd:01 > 161137 /usr/lib64/kamailio/modules/dmq_usrloc.so > 7f042e965000-7f042e998000 r-xp 00000000 fd:01 > 160717 /usr/lib64/kamailio/modules/dmq.so > 7f042e998000-7f042eb97000 ---p 00033000 fd:01 > 160717 /usr/lib64/kamailio/modules/dmq.so > 7f042eb97000-7f042eb99000 rw-p 00032000 fd:01 > 160717 /usr/lib64/kamailio/modules/dmq.so > 7f042eb99000-7f042ebd2000 r-xp 00000000 fd:01 > 160762 /usr/lib64/kamailio/modules/rtpproxy.so > 7f042ebd2000-7f042edd2000 ---p 00039000 fd:01 > 160762 /usr/lib64/kamailio/modules/rtpproxy.so > 7f042edd2000-7f042edd4000 rw-p 00039000 fd:01 > 160762 /usr/lib64/kamailio/modules/rtpproxy.so > 7f042edd4000-7f042ee07000 r-xp 00000000 fd:01 > 160743 /usr/lib64/kamailio/modules/nathelper.so > 7f042ee07000-7f042f006000 ---p 00033000 fd:01 > 160743 /usr/lib64/kamailio/modules/nathelper.so > 7f042f006000-7f042f008000 rw-p 00032000 fd:01 > 160743 /usr/lib64/kamailio/modules/nathelper.so > 7f042f008000-7f042f018000 rw-p 00000000 00:00 0 > 7f042f018000-7f042f02a000 r-xp 00000000 fd:01 > 160750 /usr/lib64/kamailio/modules/pike.so > 7f042f02a000-7f042f22a000 ---p 00012000 fd:01 > 160750 /usr/lib64/kamailio/modules/pike.so > 7f042f22a000-7f042f22b000 rw-p 00012000 fd:01 > 160750 /usr/lib64/kamailio/modules/pike.so > 7f042f22b000-7f042f241000 r-xp 00000000 fd:01 > 160718 /usr/lib64/kamailio/modules/domain.so > 7f042f241000-7f042f441000 ---p 00016000 fd:01 > 160718 /usr/lib64/kamailio/modules/domain.so > 7f042f441000-7f042f442000 rw-p 00016000 fd:01 > 160718 /usr/lib64/kamailio/modules/domain.so > 7f042f442000-7f042f482000 r-xp 00000000 fd:01 > 160749 /usr/lib64/kamailio/modules/permissions.so > 7f042f482000-7f042f681000 ---p 00040000 fd:01 > 160749 /usr/lib64/kamailio/modules/permissions.so > 7f042f681000-7f042f683000 rw-p 0003f000 fd:01 > 160749 /usr/lib64/kamailio/modules/permissions.so > 7f042f683000-7f042f684000 rw-p 00000000 00:00 0 > 7f042f684000-7f042f699000 r-xp 00000000 fd:01 > 160516 /usr/lib64/kamailio/modules/auth_db.so > 7f042f699000-7f042f899000 ---p 00015000 fd:01 > 160516 /usr/lib64/kamailio/modules/auth_db.so > 7f042f899000-7f042f89a000 rw-p 00015000 fd:01 > 160516 /usr/lib64/kamailio/modules/auth_db.so > 7f042f89a000-7f042f8c5000 r-xp 00000000 fd:01 > 160514 /usr/lib64/kamailio/modules/auth.so > 7f042f8c5000-7f042fac4000 ---p 0002b000 fd:01 > 160514 /usr/lib64/kamailio/modules/auth.so > 7f042fac4000-7f042fac6000 rw-p 0002a000 fd:01 > 160514 /usr/lib64/kamailio/modules/auth.so > 7f042fac6000-7f042fad2000 r-xp 00000000 fd:01 > 161176 /usr/lib64/libradiusclient-ng.so.2.0.0 > 7f042fad2000-7f042fcd2000 ---p 0000c000 fd:01 > 161176 /usr/lib64/libradiusclient-ng.so.2.0.0 > 7f042fcd2000-7f042fcd3000 rw-p 0000c000 fd:01 > 161176 /usr/lib64/libradiusclient-ng.so.2.0.0 > 7f042fcd3000-7f042fcdf000 r-xp 00000000 fd:01 > 161112 /usr/lib64/kamailio/modules/acc_radius.so > 7f042fcdf000-7f042fede000 ---p 0000c000 fd:01 > 161112 /usr/lib64/kamailio/modules/acc_radius.so > 7f042fede000-7f042fedf000 rw-p 0000b000 fd:01 > 161112 /usr/lib64/kamailio/modules/acc_radius.so > 7f042fedf000-7f042ff17000 r-xp 00000000 fd:01 > 145978 /usr/lib64/kamailio/modules/acc.so > 7f042ff17000-7f0430117000 ---p 00038000 fd:01 > 145978 /usr/lib64/kamailio/modules/acc.so > 7f0430117000-7f0430118000 rw-p 00038000 fd:01 > 145978 /usr/lib64/kamailio/modules/acc.so > 7f0430118000-7f043013c000 rw-p 00000000 00:00 0 > 7f043013c000-7f0430177000 r-xp 00000000 fd:01 > 161135 /usr/lib64/kamailio/modules/jsonrpcs.so > 7f0430177000-7f0430377000 ---p 0003b000 fd:01 > 161135 /usr/lib64/kamailio/modules/jsonrpcs.so > 7f0430377000-7f0430378000 rw-p 0003b000 fd:01 > 161135 /usr/lib64/kamailio/modules/jsonrpcs.so > 7f0430378000-7f043037d000 r-xp 00000000 fd:01 > 160704 /usr/lib64/kamailio/modules/cfg_rpc.so > 7f043037d000-7f043057c000 ---p 00005000 fd:01 > 160704 /usr/lib64/kamailio/modules/cfg_rpc.so > 7f043057c000-7f043057d000 rw-p 00004000 fd:01 > 160704 /usr/lib64/kamailio/modules/cfg_rpc.so > 7f043057d000-7f04305c9000 r-xp 00000000 fd:01 > 160708 /usr/lib64/kamailio/modules/ctl.so > 7f04305c9000-7f04307c9000 ---p 0004c000 fd:01 > 160708 /usr/lib64/kamailio/modules/ctl.so > 7f04307c9000-7f04307ca000 rw-p 0004c000 fd:01 > 160708 /usr/lib64/kamailio/modules/ctl.so > 7f04307ca000-7f04307db000 rw-p 00000000 00:00 0 > 7f04307db000-7f04307f2000 r-xp 00000000 fd:01 > 160763 /usr/lib64/kamailio/modules/sanity.so > 7f04307f2000-7f04309f1000 ---p 00017000 fd:01 > 160763 /usr/lib64/kamailio/modules/sanity.so > 7f04309f1000-7f04309f2000 rw-p 00016000 fd:01 > 160763 /usr/lib64/kamailio/modules/sanity.so > 7f04309f2000-7f04309fe000 r-xp 00000000 fd:01 > 160799 /usr/lib64/kamailio/modules/xlog.so > 7f04309fe000-7f0430bfe000 ---p 0000c000 fd:01 > 160799 /usr/lib64/kamailio/modules/xlog.so > 7f0430bfe000-7f0430bff000 rw-p 0000c000 fd:01 > 160799 /usr/lib64/kamailio/modules/xlog.so > 7f0430bff000-7f0430c3a000 r-xp 00000000 fd:01 > 160770 /usr/lib64/kamailio/modules/siputils.so > 7f0430c3a000-7f0430e3a000 ---p 0003b000 fd:01 > 160770 /usr/lib64/kamailio/modules/siputils.so > 7f0430e3a000-7f0430e3c000 rw-p 0003b000 fd:01 > 160770 /usr/lib64/kamailio/modules/siputils.so > 7f0430e3c000-7f0430e88000 r-xp 00000000 fd:01 > 160779 /usr/lib64/kamailio/modules/textops.so > 7f0430e88000-7f0431087000 ---p 0004c000 fd:01 > 160779 /usr/lib64/kamailio/modules/textops.so > 7f0431087000-7f043108a000 rw-p 0004b000 fd:01 > 160779 /usr/lib64/kamailio/modules/textops.so > 7f043108a000-7f04310c8000 r-xp 00000000 fd:01 > 161133 /usr/lib64/kamailio/modules/http_client.so > 7f04310c8000-7f04312c7000 ---p 0003e000 fd:01 > 161133 /usr/lib64/kamailio/modules/http_client.so > 7f04312c7000-7f04312c9000 rw-p 0003d000 fd:01 > 161133 /usr/lib64/kamailio/modules/http_client.so > 7f04312c9000-7f043130d000 r-xp 00000000 fd:01 > 139773 /usr/lib64/libevent-2.0.so.5.1.9 > 7f043130d000-7f043150d000 ---p 00044000 fd:01 > 139773 /usr/lib64/libevent-2.0.so.5.1.9 > 7f043150d000-7f043150f000 rw-p 00044000 fd:01 > 139773 /usr/lib64/libevent-2.0.so.5.1.9 > 7f043150f000-7f0431549000 r-xp 00000000 fd:01 > 160849 > /usr/lib64/kamailio/modules/http_async_client.so > 7f0431549000-7f0431748000 ---p 0003a000 fd:01 > 160849 > /usr/lib64/kamailio/modules/http_async_client.so > 7f0431748000-7f043174a000 rw-p 00039000 fd:01 > 160849 > /usr/lib64/kamailio/modules/http_async_client.so > 7f043174a000-7f0431793000 r-xp 00000000 fd:01 > 160758 /usr/lib64/kamailio/modules/registrar.so > 7f0431793000-7f0431992000 ---p 00049000 fd:01 > 160758 /usr/lib64/kamailio/modules/registrar.so > 7f0431992000-7f0431995000 rw-p 00048000 fd:01 > 160758 /usr/lib64/kamailio/modules/registrar.so > 7f0431995000-7f04319e0000 r-xp 00000000 fd:01 > 160796 /usr/lib64/kamailio/modules/usrloc.so > 7f04319e0000-7f0431be0000 ---p 0004b000 fd:01 > 160796 /usr/lib64/kamailio/modules/usrloc.so > 7f0431be0000-7f0431be2000 rw-p 0004b000 fd:01 > 160796 /usr/lib64/kamailio/modules/usrloc.so > 7f0431be2000-7f0431be8000 r-xp 00000000 fd:01 > 160735 /usr/lib64/kamailio/modules/maxfwd.so > 7f0431be8000-7f0431de8000 ---p 00006000 fd:01 > 160735 /usr/lib64/kamailio/modules/maxfwd.so > 7f0431de8000-7f0431de9000 rw-p 00006000 fd:01 > 160735 /usr/lib64/kamailio/modules/maxfwd.so > 7f0431de9000-7f0431e8c000 r-xp 00000000 fd:01 > 160755 /usr/lib64/kamailio/modules/pv.so > 7f0431e8c000-7f043208b000 ---p 000a3000 fd:01 > 160755 /usr/lib64/kamailio/modules/pv.so > 7f043208b000-7f0432090000 rw-p 000a2000 fd:01 > 160755 /usr/lib64/kamailio/modules/pv.so > 7f0432090000-7f0432091000 rw-p 00000000 00:00 0 > 7f0432091000-7f04320c1000 r-xp 00000000 fd:01 > 160759 /usr/lib64/kamailio/modules/rr.so > 7f04320c1000-7f04322c0000 ---p 00030000 fd:01 > 160759 /usr/lib64/kamailio/modules/rr.so > 7f04322c0000-7f04322c2000 rw-p 0002f000 fd:01 > 160759 /usr/lib64/kamailio/modules/rr.so > 7f04322c2000-7f04322db000 r-xp 00000000 fd:01 > 160771 /usr/lib64/kamailio/modules/sl.so > 7f04322db000-7f04324da000 ---p 00019000 fd:01 > 160771 /usr/lib64/kamailio/modules/sl.so > 7f04324da000-7f04324dc000 rw-p 00018000 fd:01 > 160771 /usr/lib64/kamailio/modules/sl.so > 7f04324dc000-7f04324f8000 r-xp 00000000 fd:01 > 160784 /usr/lib64/kamailio/modules/tmx.so > 7f04324f8000-7f04326f8000 ---p 0001c000 fd:01 > 160784 /usr/lib64/kamailio/modules/tmx.so > 7f04326f8000-7f04326fa000 rw-p 0001c000 fd:01 > 160784 /usr/lib64/kamailio/modules/tmx.so > 7f04326fa000-7f04326fb000 rw-p 00000000 00:00 0 > 7f04326fb000-7f0432829000 r-xp 00000000 fd:01 > 160782 /usr/lib64/kamailio/modules/tm.so > 7f0432829000-7f0432a29000 ---p 0012e000 fd:01 > 160782 /usr/lib64/kamailio/modules/tm.so > 7f0432a29000-7f0432a2e000 rw-p 0012e000 fd:01 > 160782 /usr/lib64/kamailio/modules/tm.so > 7f0432a2e000-7f0432a40000 rw-p 00000000 00:00 0 > 7f0432a40000-7f0432a55000 r-xp 00000000 fd:01 > 160706 /usr/lib64/kamailio/modules/corex.so > 7f0432a55000-7f0432c55000 ---p 00015000 fd:01 > 160706 /usr/lib64/kamailio/modules/corex.so > 7f0432c55000-7f0432c56000 rw-p 00015000 fd:01 > 160706 /usr/lib64/kamailio/modules/corex.so > 7f0432c56000-7f0432c65000 r-xp 00000000 fd:01 > 144207 /usr/lib64/kamailio/libsrutils.so.1.0 > 7f0432c65000-7f0432e65000 ---p 0000f000 fd:01 > 144207 /usr/lib64/kamailio/libsrutils.so.1.0 > 7f0432e65000-7f0432e66000 rw-p 0000f000 fd:01 > 144207 /usr/lib64/kamailio/libsrutils.so.1.0 > 7f0432e66000-7f0432e75000 r-xp 00000000 fd:01 > 160731 /usr/lib64/kamailio/modules/kex.so > 7f0432e75000-7f0433074000 ---p 0000f000 fd:01 > 160731 /usr/lib64/kamailio/modules/kex.so > 7f0433074000-7f0433076000 rw-p 0000e000 fd:01 > 160731 /usr/lib64/kamailio/modules/kex.so > 7f0433076000-7f04330a4000 r-xp 00000000 fd:01 > 141110 /usr/lib64/kamailio/libsrdb1.so.1.0 > 7f04330a4000-7f04332a4000 ---p 0002e000 fd:01 > 141110 /usr/lib64/kamailio/libsrdb1.so.1.0 > 7f04332a4000-7f04332a5000 rw-p 0002e000 fd:01 > 141110 /usr/lib64/kamailio/libsrdb1.so.1.0 > 7f04332a5000-7f04332b1000 r-xp 00000000 fd:01 > 141797 /usr/lib64/kamailio/libsrdb2.so.1.0 > 7f04332b1000-7f04334b0000 ---p 0000c000 fd:01 > 141797 /usr/lib64/kamailio/libsrdb2.so.1.0 > 7f04334b0000-7f04334b1000 rw-p 0000b000 fd:01 > 141797 /usr/lib64/kamailio/libsrdb2.so.1.0 > 7f04334b1000-7f04335e7000 r-xp 00000000 fd:01 > 141483 /usr/lib64/mysql/libmysqlclient.so.16.0.0 > 7f04335e7000-7f04337e6000 ---p 00136000 fd:01 > 141483 /usr/lib64/mysql/libmysqlclient.so.16.0.0 > 7f04337e6000-7f0433834000 rw-p 00135000 fd:01 > 141483 /usr/lib64/mysql/libmysqlclient.so.16.0.0 > 7f0433834000-7f0433835000 rw-p 00000000 00:00 0 > 7f043383c000-7f043386f000 r-xp 00000000 fd:01 > 137644 /usr/lib64/kamailio/modules/db_mysql.so > 7f043386f000-7f0433a6e000 ---p 00033000 fd:01 > 137644 /usr/lib64/kamailio/modules/db_mysql.so > 7f0433a6e000-7f0433a70000 rw-p 00032000 fd:01 > 137644 /usr/lib64/kamailio/modules/db_mysql.so > 7f0433a70000-7f0434274000 rw-p 00000000 00:00 0 > 7f0434278000-7f043427a000 rw-p 00000000 00:00 0 > 7f043427a000-7f043427c000 rw-p 00000000 00:00 0 > 7ffe9e90c000-7ffe9e921000 rw-p 00000000 00:00 > 0 [stack] > 7ffe9e9cc000-7ffe9e9cd000 r-xp 00000000 00:00 > 0 [vdso] > ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 > 0 [vsyscall] > > [...] -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

2 1

Kamailio 5.0.4 WebSocket failover to secondary
by James Aylett 18 Jan '18

18 Jan '18

Hello, I am testing failover scenarios between two Active/Active kamailios for Sip over WebSockets and WebRTC. In my test scenario, I have setup the call through proxy-a, then stopped the kamailio service so that the sip client reconnects to proxy-b. Dialogs and registrations are shared across both instances using MariaDB and Galera. When the SIP client reconnects to proxy-b, I send a BYE and see the following errors in the logs: Jan 18 09:12:36 webrtc-proxy-b /usr/sbin/kamailio[6975]: ERROR: <script>: Connection ID: 1 Jan 18 09:12:36 webrtc-proxy-b /usr/sbin/kamailio[6975]: ERROR: <script>: WITHINDLG Jan 18 09:12:36 webrtc-proxy-b /usr/sbin/kamailio[6975]: ERROR: <script>: RELAY Jan 18 09:12:36 webrtc-proxy-b /usr/sbin/kamailio[6975]: WARNING: <core> [core/msg_translator.c:2765]: via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found Jan 18 09:12:36 webrtc-proxy-b /usr/sbin/kamailio[6975]: ERROR: <core> [core/msg_translator.c:1980]: build_req_buf_from_sip_req(): could not create Via header Jan 18 09:12:36 webrtc-proxy-b /usr/sbin/kamailio[6975]: ERROR: tm [t_fwd.c:476]: prepare_new_uac(): could not build request Jan 18 09:12:36 webrtc-proxy-b /usr/sbin/kamailio[6975]: ERROR: tm [t_fwd.c:1732]: t_forward_nonack(): failure to add branches Jan 18 09:12:36 webrtc-proxy-b /usr/sbin/kamailio[6975]: ERROR: sl [sl_funcs.c:362]: sl_reply_error(): stateless error reply used: No error (2/SL) It seems that core/msg_translator.c is using the wrong WebSocket connection ID (0 rather than 1). Is this a bug in Kamailio or a limitation that I do not understand? I have assumed that the BYE is a new transaction for the existing dialog so t_relay() should be able to forward the message. I can provide config and any additional error logs if required. Any help is much appreciated. Thanks, James

1 0

exec warning
by voipspace voipspace 17 Jan '18

17 Jan '18

exec_msg gives the following warning. Even when no variables are used in the parameters 8(29619) WARNING: exec [exec_hf.c:464]: append_fixed_vars(): uri not parsed 8(29619) WARNING: exec [exec_hf.c:482]: append_fixed_vars(): orig URI not parsed

2 2

kamailio 5.1 from git compile error
by Abdul Basit 17 Jan '18

17 Jan '18

Hi, I am trying to compile kamailio 5.1 from git following https://kamailio.org/docs/tutorials/5.1.x/kamailio-install-guide-git/ on Debian GNU/Linux 8.10 (jessie) I also installed packages after getting dependency errors apt-get install libhiredis-dev libphonenumber6-dev libicu-dev apt-get install unicode unicode-data Kamailio compile stopped at error ..... LD (gcc) [M uid_avp_db.so] uid_avp_db.so CC (gcc) [M pdb.so] pdb.o LD (gcc) [M pdb.so] pdb.so CC (gcc) [M phonenum.so] phonenum_mod.o CC (gcc) [M phonenum.so] phonenum_pv.o Compiling cphonenumber.cpp g++ -fPIC -DPIC -g -funroll-loops -Wcast-align -m64 -minline-all-stringops -falign-loops -ftree-vectorize -fno-strict-overflow -Wall -Wno-write-strings -Wno-deprecated -Wno-unused-f unction -Wno-sign-compare -Wno-strict-aliasing -fPIC -DPIC -g -funroll-loops -Wcast-align -m64 -minline-all-stringops -falign-loops -ftree-vectorize -fno-strict-overflow -Wall -DNA ME='"kamailio"' -DVERSION='"5.1.0"' -DARCH='"x86_64"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 4.9.2"' -D__CPU_x86_64 -D__OS_linux -DSER_VER=5001000 -DCFG_DIR='"/usr/loc al/etc/kamailio/"' -DRUN_DIR='"/var/run/kamailio/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS _FAILOVER -DUSE_DST_BLACKLIST -DUSE_NAPTR -DWITH_XAVP -DMEM_JOIN_FREE -DF_MALLOC -DQ_MALLOC -DTLSF_MALLOC -DDBG_SR_MEMORY -DUSE_TLS -DTLS_HOOKS -DUSE_CORE_STATS -DSTATISTICS -DMALLO C_STATS -DWITH_AS_SUPPORT -DUSE_SCTP -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_ NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DHAVE_IP_MREQN -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DUSE_FUTEX -DHAVE_SE LECT -I/opt/local/include -DKAMAILIO_MOD_INTERFACE -DMOD_NAME='"phonenum"' -c cphonenumber.cpp -o cphonenumber.o In file included from /usr/include/phonenumbers/geocoding/phonenumber_offline_geocoder.h:26:0, from cphonenumber.cpp:24: /usr/include/phonenumbers/base/memory/scoped_ptr.h:25:45: fatal error: phonenumbers/base/template_util.h: No such file or directory #include "phonenumbers/base/template_util.h" ^ compilation terminated. Makefile:22: recipe for target 'cphonenumber.o' failed make[2]: *** [cphonenumber.o] Error 1 Makefile:511: recipe for target 'modules' failed make[1]: *** [modules] Error 1 make[1]: Leaving directory '/usr/local/src/kamailio/src' Makefile:27: recipe for target 'all' failed make: *** [all] Error 2 I googled but couldnt found any resolution or required dependency. Its look like libphonenumber is broken. Kindly suggest way out. Also i don't require libphonenumber for this server. How to get rid off. -- regards, abdul basit

3 5

send LUA logs via HEP to Homer server
by Abdul Basit 17 Jan '18

17 Jan '18

Hi K-team, I am processing incoming INVITE events in my lua script. To print the logs with kamailio syslog, i am using sr.log("info", "-- Collecting data from kamailio -- ") I am searching for a way to send selective logs for an incoming call from lua script through HEP3 towards Homer server. How can I make it work? What utility or library is helpful. *PS:* captagent is configured on the same server for SIP traces. -- regards, abdul basit

2 2

Error: no config routing engine registered
by Christian Scheid 17 Jan '18

17 Jan '18

Experts, I'm currently setting up Kamailio for the first time (yay!) and ran into an issue (DOH!!!). The install went fine and I modified a few lines in the kamailio-basic.cfg (below). I also set up two users 'bob' and 'alice' and am trying to start a simple chat session between two QjSimple clients. In the syslog I see the following error. /usr/sbin/kamailio[32998]: ERROR: <core> [core/receive.c:257]: receive_msg(): no config routing engine registered I followed the Debian installation instructions below but didn't see anything about config routing engine setup. https://www.kamailio.org/wiki/tutorials/getting-started/main#debian Can you point me in the right direction what is missing? Thanks! Chris ----------------------- #!KAMAILIO # # Kamailio (OpenSER) SIP Server v5.0 - default configuration script # - web: http://www.kamailio.org # - git: http://sip-router.org # # Direct your questions about this file to: <sr-users(a)lists.sip-router.org> # # Refer to the Core CookBook at http://www.kamailio.org/wiki/ # for an explanation of possible statements, functions and parameters. # # Several features can be enabled using '#!define WITH_FEATURE' directives: # # *** To run in debug mode: # - define WITH_DEBUG # # *** To enable mysql: # - define WITH_MYSQL # # *** To enable authentication execute: # - enable mysql # - define WITH_AUTH # - add users using 'kamctl' # # *** To enable IP authentication execute: # - enable mysql # - enable authentication # - define WITH_IPAUTH # - add IP addresses with group id '1' to 'address' table # # *** To enable persistent user location execute: # - enable mysql # - define WITH_USRLOCDB # # *** To enable nat traversal execute: # - define WITH_NAT # - install RTPProxy: http://www.rtpproxy.org # - start RTPProxy: # rtpproxy -l _your_public_ip_ -s udp:localhost:7722 # - option for NAT SIP OPTIONS keepalives: WITH_NATSIPPING # # *** To enable TLS support execute: # - adjust CFGDIR/tls.cfg as needed # - define WITH_TLS # # *** To enhance accounting execute: # - enable mysql # - define WITH_ACCDB # - add following columns to database #!ifdef ACCDB_COMMENT ALTER TABLE acc ADD COLUMN src_user VARCHAR(64) NOT NULL DEFAULT ''; ALTER TABLE acc ADD COLUMN src_domain VARCHAR(128) NOT NULL DEFAULT ''; ALTER TABLE acc ADD COLUMN src_ip varchar(64) NOT NULL default ''; ALTER TABLE acc ADD COLUMN dst_ouser VARCHAR(64) NOT NULL DEFAULT ''; ALTER TABLE acc ADD COLUMN dst_user VARCHAR(64) NOT NULL DEFAULT ''; ALTER TABLE acc ADD COLUMN dst_domain VARCHAR(128) NOT NULL DEFAULT ''; ALTER TABLE missed_calls ADD COLUMN src_user VARCHAR(64) NOT NULL DEFAULT ''; ALTER TABLE missed_calls ADD COLUMN src_domain VARCHAR(128) NOT NULL DEFAULT ''; ALTER TABLE missed_calls ADD COLUMN src_ip varchar(64) NOT NULL default ''; ALTER TABLE missed_calls ADD COLUMN dst_ouser VARCHAR(64) NOT NULL DEFAULT ''; ALTER TABLE missed_calls ADD COLUMN dst_user VARCHAR(64) NOT NULL DEFAULT ''; ALTER TABLE missed_calls ADD COLUMN dst_domain VARCHAR(128) NOT NULL DEFAULT ''; #!endif ####### Include Local Config If Exists ######### import_file "kamailio-local.cfg" # Custom Setup # #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB ####### Defined Values ######### # *** Value defines - IDs used later in config #!ifdef WITH_MYSQL # - database URL - used to connect to database server by modules such # as: auth_db, acc, usrloc, a.s.o. #!ifndef DBURL #!define DBURL "mysql://kamailio:kamailiorw@localhost/kamailio" #!endif #!endif #!define MULTIDOMAIN 0 # - flags # FLT_ - per transaction (message) flags # FLB_ - per branch flags #!define FLT_ACC 1 #!define FLT_ACCMISSED 2 #!define FLT_ACCFAILED 3 #!define FLT_NATS 5 #!define FLB_NATB 6 #!define FLB_NATSIPPING 7 ####### Global Parameters ######### ### LOG Levels: 3=DBG, 2=INFO, 1=NOTICE, 0=WARN, -1=ERR #!ifdef WITH_DEBUG debug=4 log_stderror=yes #!else debug=2 log_stderror=no #!endif memdbg=5 memlog=5 log_facility=LOG_LOCAL0 fork=yes children=4 /* uncomment the next line to disable TCP (default on) */ #disable_tcp=yes /* uncomment the next line to disable the auto discovery of local aliases * based on reverse DNS on IPs (default on) */ #auto_aliases=no /* add local domain aliases */ #alias="sip.mydomain.com" /* uncomment and configure the following line if you want Kamailio to * bind on a specific interface/port/proto (default bind on all available) */ #listen=udp:10.0.0.10:5060 /* port to listen to * - can be specified more than once if needed to listen on many ports */ port=5060 #!ifdef WITH_TLS enable_tls=yes #!endif # life time of TCP connection when there is no traffic # - a bit higher than registration expires to cope with UA behind NAT tcp_connection_lifetime=3605 ####### Modules Section ######## # set paths to location of modules (to sources or installation folders) #!ifdef WITH_SRCPATH mpath="modules" #!else mpath="/usr/lib/x86_64-linux-gnu/kamailio/modules/" #!endif #!ifdef WITH_MYSQL loadmodule "db_mysql.so" #!endif loadmodule "jsonrpcs.so" loadmodule "kex.so" loadmodule "corex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "usrloc.so" loadmodule "registrar.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "ctl.so" loadmodule "cfg_rpc.so" loadmodule "acc.so" loadmodule "counters.so" #!ifdef WITH_AUTH loadmodule "auth.so" loadmodule "auth_db.so" #!ifdef WITH_IPAUTH loadmodule "permissions.so" #!endif #!endif #!ifdef WITH_NAT loadmodule "nathelper.so" loadmodule "rtpproxy.so" #!endif #!ifdef WITH_TLS loadmodule "tls.so" #!endif #!ifdef WITH_DEBUG loadmodule "debugger.so" #!endif # ----------------- setting module-specific parameters --------------- # ----- jsonrpcs params ----- modparam("jsonrpcs", "pretty_format", 1) /* set the path to RPC fifo control file */ # modparam("jsonrpcs", "fifo_name", "/var/run/kamailio/kamailio_rpc.fifo") /* set the path to RPC unix socket control file */ # modparam("jsonrpcs", "dgram_socket", "/var/run/kamailio/kamailio_rpc.sock") # ----- ctl params ----- #modparam("ctl", "binrpc", "unix:/var/run/kamailio/kamailio_ctl") # ----- tm params ----- # auto-discard branches from previous serial forking leg modparam("tm", "failure_reply_mode", 3) # default retransmission timeout: 30sec modparam("tm", "fr_timer", 30000) # default invite retransmission timeout after 1xx: 120sec modparam("tm", "fr_inv_timer", 120000) # ----- rr params ----- # add value to ;lr param to cope with most of the UAs modparam("rr", "enable_full_lr", 1) # do not append from tag to the RR (no need for this script) modparam("rr", "append_fromtag", 0) # ----- registrar params ----- modparam("registrar", "method_filtering", 1) /* uncomment the next line to disable parallel forking via location */ # modparam("registrar", "append_branches", 0) /* uncomment the next line not to allow more than 10 contacts per AOR */ #modparam("registrar", "max_contacts", 10) # max value for expires of registrations modparam("registrar", "max_expires", 3600) # set it to 1 to enable GRUU modparam("registrar", "gruu_enabled", 0) # ----- acc params ----- /* what special events should be accounted ? */ modparam("acc", "early_media", 0) modparam("acc", "report_ack", 0) modparam("acc", "report_cancels", 0) /* by default we do not adjust the direct of the sequential requests. * if you enable this parameter, be sure the enable "append_fromtag" * in "rr" module */ modparam("acc", "detect_direction", 0) /* account triggers (flags) */ modparam("acc", "log_flag", FLT_ACC) modparam("acc", "log_missed_flag", FLT_ACCMISSED) modparam("acc", "log_extra", "src_user=$fU;src_domain=$fd;src_ip=$si;" "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd") modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) /* enhanced DB accounting */ #!ifdef WITH_ACCDB modparam("acc", "db_flag", FLT_ACC) modparam("acc", "db_missed_flag", FLT_ACCMISSED) modparam("acc", "db_url", DBURL) modparam("acc", "db_extra", "src_user=$fU;src_domain=$fd;src_ip=$si;" "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd") #!endif # ----- usrloc params ----- /* enable DB persistency for location entries */ #!ifdef WITH_USRLOCDB modparam("usrloc", "db_url", DBURL) modparam("usrloc", "db_mode", 2) modparam("usrloc", "use_domain", MULTIDOMAIN) #!endif # ----- auth_db params ----- #!ifdef WITH_AUTH modparam("auth_db", "db_url", DBURL) modparam("auth_db", "calculate_ha1", yes) modparam("auth_db", "password_column", "password") modparam("auth_db", "load_credentials", "") modparam("auth_db", "use_domain", MULTIDOMAIN) # ----- permissions params ----- #!ifdef WITH_IPAUTH modparam("permissions", "db_url", DBURL) modparam("permissions", "db_mode", 1) #!endif #!endif #!ifdef WITH_NAT # ----- rtpproxy params ----- modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722") # ----- nathelper params ----- modparam("nathelper", "natping_interval", 30) modparam("nathelper", "ping_nated_only", 1) modparam("nathelper", "sipping_bflag", FLB_NATSIPPING) modparam("nathelper", "sipping_from", "sip:pinger@kamailio.org") # params needed for NAT traversal in other modules modparam("nathelper|registrar", "received_avp", "$avp(RECEIVED)") modparam("usrloc", "nat_bflag", FLB_NATB) #!endif #!ifdef WITH_TLS # ----- tls params ----- modparam("tls", "config", "/etc/kamailio/tls.cfg") #!endif #!ifdef WITH_DEBUG # ----- debugger params ----- modparam("debugger", "cfgtrace", 1) #!endif ####### Routing Logic ######## # Main SIP request routing logic # - processing of any incoming SIP request starts with this route # - note: this is the same as route { ... } request_route { # per request initial checks route(REQINIT); # NAT detection route(NATDETECT); # CANCEL processing if (is_method("CANCEL")) { if (t_check_trans()) { route(RELAY); } exit; } # handle requests within SIP dialogs route(WITHINDLG); ### only initial requests (no To tag) # handle retransmissions if(t_precheck_trans()) { t_check_trans(); exit; } t_check_trans(); # authentication route(AUTH); # record routing for dialog forming requests (in case they are routed) # - remove preloaded route headers remove_hf("Route"); if (is_method("INVITE|SUBSCRIBE")) record_route(); # account only INVITEs if (is_method("INVITE")) { setflag(FLT_ACC); # do accounting } # dispatch requests to foreign domains route(SIPOUT); ### requests for my local domains # handle registrations route(REGISTRAR); if ($rU==$null) { # request with no Username in RURI sl_send_reply("484","Address Incomplete"); exit; } # user location service route(LOCATION); } route[RELAY] { # enable additional event routes for forwarded requests # - serial forking, RTP relaying handling, a.s.o. if (is_method("INVITE|BYE|SUBSCRIBE|UPDATE")) { if(!t_is_set("branch_route")) t_on_branch("MANAGE_BRANCH"); } if (is_method("INVITE|SUBSCRIBE|UPDATE")) { if(!t_is_set("onreply_route")) t_on_reply("MANAGE_REPLY"); } if (is_method("INVITE")) { if(!t_is_set("failure_route")) t_on_failure("MANAGE_FAILURE"); } if (!t_relay()) { sl_reply_error(); } exit; } # Per SIP request initial checks route[REQINIT] { #!ifdef WITH_ANTIFLOOD # flood dection from same IP and traffic ban for a while # be sure you exclude checking trusted peers, such as pstn gateways # - local host excluded (e.g., loop to self) if(src_ip!=myself) { if($sht(ipban=>$si)!=$null) { # ip is already blocked xdbg("request from blocked IP - $rm from $fu (IP:$si:$sp)\n"); exit; } if (!pike_check_req()) { xlog("L_ALERT","ALERT: pike blocking $rm from $fu (IP:$si:$sp)\n"); $sht(ipban=>$si) = 1; exit; } } if($ua =~ "friendly-scanner") { sl_send_reply("200", "OK"); exit; } #!endif if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; } if(is_method("OPTIONS") && uri==myself && $rU==$null) { sl_send_reply("200","Keepalive"); exit; } if(!sanity_check("1511", "7")) { xlog("Malformed SIP message from $si:$sp\n"); exit; } } # Handle requests within SIP dialogs route[WITHINDLG] { if (!has_totag()) return; # sequential request withing a dialog should # take the path determined by record-routing if (loose_route()) { route(DLGURI); if (is_method("BYE")) { setflag(FLT_ACC); # do accounting ... setflag(FLT_ACCFAILED); # ... even if the transaction fails } else if ( is_method("ACK") ) { # ACK is forwarded statelessy route(NATMANAGE); } else if ( is_method("NOTIFY") ) { # Add Record-Route for in-dialog NOTIFY as per RFC 6665. record_route(); } route(RELAY); exit; } if ( is_method("ACK") ) { if ( t_check_trans() ) { # no loose-route, but stateful ACK; # must be an ACK after a 487 # or e.g. 404 from upstream server route(RELAY); exit; } else { # ACK without matching transaction ... ignore and discard exit; } } sl_send_reply("404", "Not here"); exit; } # Handle SIP registrations route[REGISTRAR] { if (!is_method("REGISTER")) return; if(isflagset(FLT_NATS)) { setbflag(FLB_NATB); #!ifdef WITH_NATSIPPING # do SIP NAT pinging setbflag(FLB_NATSIPPING); #!endif } if (!save("location")) sl_reply_error(); exit; } # User location service route[LOCATION] { if (!lookup("location")) { $var(rc) = $rc; t_newtran(); switch ($var(rc)) { case -1: case -3: send_reply("404", "Not Found"); exit; case -2: send_reply("405", "Method Not Allowed"); exit; } } # when routing via usrloc, log the missed calls also if (is_method("INVITE")) { setflag(FLT_ACCMISSED); } route(RELAY); exit; } # IP authorization and user uthentication route[AUTH] { #!ifdef WITH_AUTH #!ifdef WITH_IPAUTH if((!is_method("REGISTER")) && allow_source_address()) { # source IP allowed return; } #!endif if (is_method("REGISTER") || from_uri==myself) { # authenticate requests if (!auth_check("$fd", "subscriber", "1")) { auth_challenge("$fd", "0"); exit; } # user authenticated - remove auth header if(!is_method("REGISTER|PUBLISH")) consume_credentials(); } # if caller is not local subscriber, then check if it calls # a local destination, otherwise deny, not an open relay here if (from_uri!=myself && uri!=myself) { sl_send_reply("403","Not relaying"); exit; } #!endif return; } # Caller NAT detection route[NATDETECT] { #!ifdef WITH_NAT force_rport(); if (nat_uac_test("19")) { if (is_method("REGISTER")) { fix_nated_register(); } else { if(is_first_hop()) set_contact_alias(); } setflag(FLT_NATS); } #!endif return; } # RTPProxy control route[NATMANAGE] { #!ifdef WITH_NAT if (is_request()) { if(has_totag()) { if(check_route_param("nat=yes")) { setbflag(FLB_NATB); } } } if (!(isflagset(FLT_NATS) || isbflagset(FLB_NATB))) return; rtpproxy_manage("co"); if (is_request()) { if (!has_totag()) { if(t_is_branch_route()) { add_rr_param(";nat=yes"); } } } if (is_reply()) { if(isbflagset(FLB_NATB)) { set_contact_alias(); } } #!endif return; } # URI update for dialog requests route[DLGURI] { #!ifdef WITH_NAT if(!isdsturiset()) { handle_ruri_alias(); } #!endif return; } # Routing to foreign domains route[SIPOUT] { if (uri==myself) return; append_hf("P-hint: outbound\r\n"); route(RELAY); exit; } # Manage outgoing branches branch_route[MANAGE_BRANCH] { xdbg("new branch [$T_branch_idx] to $ru\n"); route(NATMANAGE); } # Manage incoming replies onreply_route[MANAGE_REPLY] { xdbg("incoming reply\n"); if(status=~"[12][0-9][0-9]") route(NATMANAGE); } # Manage failure routing cases failure_route[MANAGE_FAILURE] { route(NATMANAGE); if (t_is_canceled()) { exit; } }

2 1

Re: [SR-Users] app_lua sr.sqlops.query exit status
by Daniel-Constantin Mierla 17 Jan '18

17 Jan '18

I only need time here to reproduce myself, what I have from your side is enough for the moment. Cheers, Daniel On 11.01.18 20:12, jenus(a)cyberchaos.nl wrote: > Daniel, > > Is there something else i can test on my side? Seems it crashes with a > very minimal config as wel (with no routing logic defined). Strange > thing is that if i disable any other module kamailio will start fine. > > Jan > > jenus(a)cyberchaos.nl schreef op 2018-01-10 13:46: >> Daniel, >> >> I have attached a stripped version of the config. With this config it >> crashes on my machine (debian 8.10). If i disable any other module >> kamailio starts and keeps running. Looks like it does not matter what >> module i disable. >> >> Jan >> >> >> >> Daniel-Constantin Mierla schreef op 2018-01-10 13:02: >>> I have master (which should be more or less like latest 5.1) running >>> with app_lua, but on debian 9.0. From backtrace, no obvious issue. >>> >>> Wondering if you can get a stripped down version of you config with as >>> less loaded modules as possible and minimal routing blocks that expose >>> the issue, so I can try it here. Try to load only the app_lua and the >>> modules it binds to and see if crashes ... if not, it could be a side >>> effect from other place. >>> >>> Cheers, >>> Daniel >>> >>> >>> On 10.01.18 12:44, jenus(a)cyberchaos.nl wrote: >>>> Daniel, >>>> >>>> (gdb) frame 5 >>>> #5 0x00007fd3b2684870 in lua_sr_kemi_register_libs (L=0xeffdb0) at >>>> app_lua_sr.c:1973 >>>> 1973 app_lua_sr.c: No such file or directory. >>>> (gdb) list >>>> 1968 in app_lua_sr.c >>>> (gdb) info locals >>>> _sr_crt_KSRMethods = 0xf0cf80 >>>> emods = 0xa59a00 <_sr_kemi_modules> >>>> emods_size = 37 >>>> i = 3 >>>> k = 35 >>>> n = 346 >>>> mname = >>>> "KSR.uac_redirect\000\000\000\000\000\000\000\000\256\240B\262\323\177\000\000й\360\000\000\000\000\000\004\000\000\000\323\177\000\000 >>>> >>>> ˏ\262\323\177\000\000\000\362\066\000\234\324\302Ͱ\375\357", '\000' >>>> <repeats 21 times>, >>>> "\065\246C\262\323\177\000\000@\265\225\356\376\177\000\000\000\000\000\000\377\377\377\377\000\000\000\000\000\000\000\000\177\241m\262\323\177\000" >>>> >>>> __FUNCTION__ = "lua_sr_kemi_register_libs" >>>> >>>> (gdb) frame 6 >>>> #6 0x00007fd3b26cf107 in lua_sr_openlibs (L=0xeffdb0) at >>>> app_lua_api.c:185 >>>> 185 app_lua_api.c: No such file or directory. >>>> (gdb) list >>>> 180 in app_lua_api.c >>>> (gdb) info locals >>>> No locals. >>>> >>>> >>>> Jan >>>> >>>> >>>> Daniel-Constantin Mierla schreef op 2018-01-10 12:40: >>>>> Now the backtrace is different, gram the output for info locals in >>>>> frame >>>>> 5 and 6. >>>>> >>>>> Cheers, >>>>> Daniel >>>>> >>>>> >>>>> On 10.01.18 11:26, jenus(a)cyberchaos.nl wrote: >>>>>> I have overwritten the core file b y accident. I did a new >>>>>> backtrace: >>>>>> >>>>>> (gdb) backtrace >>>>>> #0 0x00007fd3b24365a0 in ?? () from >>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>> #1 0x00007fd3b2437b62 in ?? () from >>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>> #2 0x00007fd3b242a040 in lua_settable () from >>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>> #3 0x00007fd3b243a412 in luaL_findtable () from >>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>> #4 0x00007fd3b243a581 in luaL_openlib () from >>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>> #5 0x00007fd3b2684870 in lua_sr_kemi_register_libs (L=0xeffdb0) at >>>>>> app_lua_sr.c:1973 >>>>>> #6 0x00007fd3b26cf107 in lua_sr_openlibs (L=0xeffdb0) at >>>>>> app_lua_api.c:185 >>>>>> #7 0x00007fd3b26cf7c1 in lua_sr_init_probe () at app_lua_api.c:225 >>>>>> #8 0x00007fd3b265b97d in child_init (rank=-127) at >>>>>> app_lua_mod.c:197 >>>>>> #9 0x0000000000549944 in init_mod_child (m=0x7fd3bc82cc70, >>>>>> rank=-127) >>>>>> at core/sr_module.c:938 >>>>>> #10 0x0000000000549c72 in init_child (rank=-127) at >>>>>> core/sr_module.c:964 >>>>>> #11 0x0000000000422c1c in main_loop () at main.c:1576 >>>>>> #12 0x000000000042aab9 in main (argc=3, argv=0x7ffeee95b548) at >>>>>> main.c:2646 >>>>>> >>>>>> (gdb) frame 7 >>>>>> #7 0x00007fd3b26cf7c1 in lua_sr_init_probe () at app_lua_api.c:225 >>>>>> 225 app_lua_api.c: No such file or directory. >>>>>> (gdb) list >>>>>> 220 in app_lua_api.c >>>>>> (gdb) info locals >>>>>> L = 0xeffdb0 >>>>>> txt = 0x7fd3bd00dce7 <__fprintf+135> "H\201\304", <incomplete >>>>>> sequence >>>>>> \330> >>>>>> li = 0x0 >>>>>> sbuf = {st_dev = 0, st_ino = 206158430256, st_nlink = >>>>>> 140732901208248, >>>>>> st_mode = 4002787296, st_uid = 32766, st_gid = 4002787464, __pad0 = >>>>>> 14, st_rdev = 140728898420739, st_size = 0, >>>>>> st_blksize = 30795, st_blocks = 7970120, st_atim = {tv_sec = >>>>>> 7929944, tv_nsec = 0}, st_mtim = {tv_sec = 0, tv_nsec = >>>>>> 140732901208128}, st_ctim = {tv_sec = 140547210663782, >>>>>> tv_nsec = 7938688}, __glibc_reserved = {-541165879423, >>>>>> 140732901208240, 5544260}} >>>>>> __FUNCTION__ = "lua_sr_init_probe" >>>>>> >>>>>> I assume that in this case i need to do a "frame 7". >>>>>> >>>>>> >>>>>> Jan >>>>>> >>>>>> Daniel-Constantin Mierla schreef op 2018-01-10 11:18: >>>>>>> Few more things to grab from core file with gdb -- take the >>>>>>> output for >>>>>>> the next commands: >>>>>>> >>>>>>> frame 16 >>>>>>> >>>>>>> list >>>>>>> >>>>>>> info locals >>>>>>> >>>>>>> Cheers, >>>>>>> Daniel >>>>>>> >>>>>>> >>>>>>> On 10.01.18 11:08, jenus(a)cyberchaos.nl wrote: >>>>>>>> Daniel, >>>>>>>> >>>>>>>> Here are the app_lua settings: >>>>>>>> >>>>>>>> # ----- app_lua params ----- >>>>>>>> modparam("app_lua", "load", >>>>>>>> "/etc/kamailio/kamailio_functions.lua") >>>>>>>> modparam("app_lua", "register", "sqlops") >>>>>>>> modparam("app_lua", "register", "siputils") >>>>>>>> modparam("app_lua", "register", "xhttp") >>>>>>>> >>>>>>>> >>>>>>>> Jan >>>>>>>> >>>>>>>> >>>>>>>> Daniel-Constantin Mierla schreef op 2018-01-10 11:03: >>>>>>>>> Can you give here the parameters you set for app_lua module? >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> Daniel >>>>>>>>> >>>>>>>>> >>>>>>>>> On 09.01.18 22:27, jenus(a)cyberchaos.nl wrote: >>>>>>>>>> Daniel, >>>>>>>>>> >>>>>>>>>> Here is the backtrace. >>>>>>>>>> >>>>>>>>>> (gdb) backtrace >>>>>>>>>> #0 0x00007fe41140e067 in __GI_raise (sig=sig@entry=6) at >>>>>>>>>> ../nptl/sysdeps/unix/sysv/linux/raise.c:56 >>>>>>>>>> #1 0x00007fe41140f448 in __GI_abort () at abort.c:89 >>>>>>>>>> #2 0x00007fe41144c1b4 in __libc_message >>>>>>>>>> (do_abort=do_abort@entry=1, >>>>>>>>>> fmt=fmt@entry=0x7fe411541210 "*** Error in `%s': %s: 0x%s >>>>>>>>>> ***\n") at >>>>>>>>>> ../sysdeps/posix/libc_fatal.c:175 >>>>>>>>>> #3 0x00007fe41145198e in malloc_printerr (action=1, >>>>>>>>>> str=0x7fe41153d42a "realloc(): invalid next size", >>>>>>>>>> ptr=<optimized >>>>>>>>>> out>) at malloc.c:4996 >>>>>>>>>> #4 0x00007fe41145476b in _int_realloc >>>>>>>>>> (av=av@entry=0x7fe41177e620 >>>>>>>>>> <main_arena>, oldp=oldp@entry=0x21789c0, >>>>>>>>>> oldsize=oldsize@entry=736, >>>>>>>>>> nb=nb@entry=1552) at malloc.c:4234 >>>>>>>>>> #5 0x00007fe411455769 in __GI___libc_realloc (oldmem=0x21789d0, >>>>>>>>>> bytes=1536) at malloc.c:3029 >>>>>>>>>> #6 0x00007fe40c460cae in ?? () from >>>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>>> #7 0x00007fe40c45c9aa in ?? () from >>>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>>> #8 0x00007fe40c46166d in ?? () from >>>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>>> #9 0x00007fe40c4640b3 in ?? () from >>>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>>> #10 0x00007fe40c45ccd1 in ?? () from >>>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>>> #11 0x00007fe40c45c92e in ?? () from >>>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>>> #12 0x00007fe40c45d7bb in ?? () from >>>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>>> #13 0x00007fe40c45d8c2 in ?? () from >>>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>>> #14 0x00007fe40c459528 in lua_load () from >>>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>>> #15 0x00007fe40c469d8c in luaL_loadbuffer () from >>>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>>> #16 0x00007fe40c6fe7d7 in lua_sr_init_probe () at >>>>>>>>>> app_lua_api.c:228 >>>>>>>>>> #17 0x00007fe40c68a97d in child_init (rank=-127) at >>>>>>>>>> app_lua_mod.c:197 >>>>>>>>>> #18 0x0000000000549944 in init_mod_child (m=0x7fe410c3b998, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:938 >>>>>>>>>> #19 0x0000000000549662 in init_mod_child (m=0x7fe410c3bec0, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #20 0x0000000000549662 in init_mod_child (m=0x7fe410c3c708, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #21 0x0000000000549662 in init_mod_child (m=0x7fe410c3cd78, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #22 0x0000000000549662 in init_mod_child (m=0x7fe410c3d360, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #23 0x0000000000549662 in init_mod_child (m=0x7fe410c3e1e8, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #24 0x0000000000549662 in init_mod_child (m=0x7fe410c3e938, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #25 0x0000000000549662 in init_mod_child (m=0x7fe410c3f4c8, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #26 0x0000000000549662 in init_mod_child (m=0x7fe410c3fca0, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #27 0x0000000000549662 in init_mod_child (m=0x7fe410c40118, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #28 0x0000000000549662 in init_mod_child (m=0x7fe410c40780, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #29 0x0000000000549662 in init_mod_child (m=0x7fe410c422f8, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #30 0x0000000000549662 in init_mod_child (m=0x7fe410c42968, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #31 0x0000000000549662 in init_mod_child (m=0x7fe410c42e50, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #32 0x0000000000549662 in init_mod_child (m=0x7fe410c43b48, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #33 0x0000000000549662 in init_mod_child (m=0x7fe410c43f20, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #34 0x0000000000549662 in init_mod_child (m=0x7fe410c446e0, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #35 0x0000000000549662 in init_mod_child (m=0x7fe410c44bd0, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #36 0x0000000000549662 in init_mod_child (m=0x7fe410c44ec8, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #37 0x0000000000549662 in init_mod_child (m=0x7fe410c45378, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #38 0x0000000000549662 in init_mod_child (m=0x7fe410c458f0, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #39 0x0000000000549662 in init_mod_child (m=0x7fe410c45e48, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #40 0x0000000000549662 in init_mod_child (m=0x7fe410c464e8, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #41 0x0000000000549662 in init_mod_child (m=0x7fe410c47278, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #42 0x0000000000549662 in init_mod_child (m=0x7fe410c476f0, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #43 0x0000000000549662 in init_mod_child (m=0x7fe410c47b68, >>>>>>>>>> rank=-127) >>>>>>>>>> at core/sr_module.c:935 >>>>>>>>>> #44 0x0000000000549c72 in init_child (rank=-127) at >>>>>>>>>> core/sr_module.c:964 >>>>>>>>>> #45 0x0000000000422c1c in main_loop () at main.c:1576 >>>>>>>>>> #46 0x000000000042aab9 in main (argc=3, argv=0x7ffe17f0e788) at >>>>>>>>>> main.c:2646 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Jan >>>>>>>>>> >>>>>>>>>> Daniel-Constantin Mierla schreef op 2018-01-09 22:21: >>>>>>>>>>> Can you install the debug symbols for kamailio as well? There >>>>>>>>>>> should be >>>>>>>>>>> a kamailio-dbg package or so ... >>>>>>>>>>> >>>>>>>>>>> Then take again the backtrace, it should provide more >>>>>>>>>>> information -- >>>>>>>>>>> file and line for each frame, ... >>>>>>>>>>> >>>>>>>>>>> Cheers, >>>>>>>>>>> Daniel >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 09.01.18 21:21, jenus(a)cyberchaos.nl wrote: >>>>>>>>>>>> Daniel, >>>>>>>>>>>> >>>>>>>>>>>> Just upgraded to 5.1 but kamailio now generates a core >>>>>>>>>>>> file. I'm >>>>>>>>>>>> running debian 8.10. It seems to crash on liblua5.1.so.0 : >>>>>>>>>>>> >>>>>>>>>>>> Using host libthread_db library >>>>>>>>>>>> "/lib/x86_64-linux-gnu/libthread_db.so.1". >>>>>>>>>>>> Core was generated by `kamailio -m 1500'. >>>>>>>>>>>> Program terminated with signal SIGSEGV, Segmentation fault. >>>>>>>>>>>> #0 0x00007f30c17f25a0 in ?? () from >>>>>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>>>>> (gdb) backtrace >>>>>>>>>>>> #0 0x00007f30c17f25a0 in ?? () from >>>>>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>>>>> #1 0x00007f30c17f3b62 in ?? () from >>>>>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>>>>> #2 0x00007f30c17e6040 in lua_settable () from >>>>>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>>>>> #3 0x00007f30c17f6412 in luaL_findtable () from >>>>>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>>>>> #4 0x00007f30c17f6581 in luaL_openlib () from >>>>>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>>>>> #5 0x00007f30c1a40870 in lua_sr_kemi_register_libs () from >>>>>>>>>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>>>>>>>>> #6 0x00007f30c1a8b107 in lua_sr_openlibs () from >>>>>>>>>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>>>>>>>>> #7 0x00007f30c1a8b7c1 in lua_sr_init_probe () from >>>>>>>>>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>>>>>>>>> #8 0x00007f30c1a1797d in ?? () from >>>>>>>>>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>>>>>>>>> #9 0x0000000000549944 in ?? () >>>>>>>>>>>> #10 0x0000000000549c72 in init_child () >>>>>>>>>>>> #11 0x0000000000421498 in main_loop () >>>>>>>>>>>> #12 0x000000000042aab9 in main () >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Thanks, >>>>>>>>>>>> >>>>>>>>>>>> Jan >>>>>>>>>>>> >>>>>>>>>>>> jenus(a)cyberchaos.nl schreef op 2018-01-09 20:53: >>>>>>>>>>>>> Daniel, >>>>>>>>>>>>> >>>>>>>>>>>>> Currently running kamailio 5.0.5. >>>>>>>>>>>>> >>>>>>>>>>>>> Jan >>>>>>>>>>>>> >>>>>>>>>>>>> Daniel-Constantin Mierla schreef op 2018-01-09 13:27: >>>>>>>>>>>>>> Hello, >>>>>>>>>>>>>> >>>>>>>>>>>>>> what version of kamailio are you using? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>> Daniel >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On 07.01.18 22:14, jenus(a)cyberchaos.nl wrote: >>>>>>>>>>>>>>> Hello, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I'm doing some tests with a lua script and app_lua. I'm >>>>>>>>>>>>>>> using >>>>>>>>>>>>>>> sr.sqlops.query to insert records into the database but >>>>>>>>>>>>>>> would >>>>>>>>>>>>>>> like to >>>>>>>>>>>>>>> test the exit status of the sql query. In kamailio i can >>>>>>>>>>>>>>> do: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> if(!sql_query("kamailio", "INSERT INTO subscriber ...")) >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Is there some kind of exit status for the lua function >>>>>>>>>>>>>>> sr.sqlops.query >>>>>>>>>>>>>>> in order to do the same check in lua? In other words, is it >>>>>>>>>>>>>>> possible >>>>>>>>>>>>>>> to check if a sql query was successful in lua? The result >>>>>>>>>>>>>>> seems >>>>>>>>>>>>>>> to be >>>>>>>>>>>>>>> nill in all cases for a INSERT in lua using >>>>>>>>>>>>>>> sr.sqlops.query. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Jan Hazenberg >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> Kamailio (SER) - Users Mailing List >>>>>>>>>>>>>>> sr-users(a)lists.kamailio.org >>>>>>>>>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Kamailio (SER) - Users Mailing List >>>>>>>>>>>>> sr-users(a)lists.kamailio.org >>>>>>>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>>>>>>>>>> >>>>>>>>>> >>>>>>>> >>>>>> >>>> >> >> _______________________________________________ >> Kamailio (SER) - Users Mailing List >> sr-users(a)lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

2 2

Re: [SR-Users] Fosdem dinner
by Federico Cabiddu 16 Jan '18

16 Jan '18

Hi Daniel, I will be at Fosdem and I'd like to join the dinner. See you there. Federico On 15 Jan 2018 09:29, "Daniel-Constantin Mierla" <miconda(a)gmail.com> wrote: Hello, in the past 10 years or so, many of us met at Fosdem conference in Brussels (the edition this year happens during February 3-4) and had a dinner on Saturday evening. I know already couple of people from community that will go there, so the question is if there is any interest to organize again such event. If yes, it will be again on Saturday, on the evening of the 3rd of February. At the past editions, it turned into an all-RTC dinner, but we can consider to have it alone again (eventually with few other invited friends), if there are too many or people want a smaller meeting. Reply this week if you want to join, so we can estimate how many seats we need and have enough time to find a place that can accommodate us. More about Fosdem can be found at: - https://fosdem.org There is a devroom on Sunday with topics covering real time communications. I will have a presentation there. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

1 0

Re: [SR-Users] Process transactions after server crash?
by Malcolm O'Hare 16 Jan '18

16 Jan '18

The situation is an INVITE sent and forked to multiple branches to send to multiple devices. After forwarding the AP goes down before either the 180 or final response from any branch. In the case with multiple branches going stateless wouldn't work because the caller would potentially receive multiple final responses? And sending cancels to the other branches after a final response wouldn't work since we wouldn't know about them. I was envisioning something like what you said, serializing the transaction info and saving it (and updating it on branch replies) and then having other hosts able to read it if they end up getting a message for which they werent in the original route.

1 0

Blind Transfer WS Error
by Alessio Miranda 16 Jan '18

16 Jan '18

Hi, I have a problem with the blind transfer via WebSocket, debugging from the browser we see that in some cases when the REFER is done and the sip message "202 Accepted" arrives, the message "180 Ringing" arrives first and then the "100 Trying" and the transfer goes in error with "500 JsSIP Internal Error" I have an architecture with Kamailio in frontend and asterisk in backend on the same network, the sip dialogue between FE and BE is in SIP / UDP. The WebRTC client connects to WebSocket at Kamailio's public address. We have verified that the sip messages exchanged between kamailio and asterisk are always correct. Kamailio Ver. 4.4.4 Asterisk Ver. 13.18.3 PJSIP Ver. 2.6 JSSIP Ver. 3.2.2 Thanks Alessio

1 0

im_auth: IMS AKA re-synchronization failure
by Jason Weijian Chen 16 Jan '18

16 Jan '18

Hello all, I am testing VoLTE between Kamailio and several smart phones. The phones requested re-synchronization from time to time. However, I found the one phone could not re-syn while the other phones could. The main difference is that this phone send "auts" with no "response", and other phone requested re-sync with a "response". Here is the comparison of two typical Authorization attribute: 1, no response: Authorization: Authentication Scheme: Digest Nonce Value: "ruyNeVizArzCYHL7P8RARxEImZpylYAAzrS+UZA9LS4=" Username: "460000123456005(a)ims.mnc000.mcc460.3gppnetwork.org" Authentication URI: "sip:ims.mnc000.mcc460.3gppnetwork.org" Realm: "ims.mnc000.mcc460.3gppnetwork.org" Algorithm: AKAv1-MD5,response="" QOP: auth,cnonce="86340c0486340c24" Nonce Count: 00000001,auts="UNjSbCZ9C8A7gHq2ngE=" 2, no response: Authorization: Authentication Scheme: Digest Username: "460000123456006(a)ims.mnc000.mcc460.3gppnetwork.org" Realm: "ims.mnc000.mcc460.3gppnetwork.org" Nonce Value: "XA2hWJsI0H1ElQORsxX9KjaGlvSLNIAAqUhXhX7iIgw=" Algorithm: AKAv1-MD5,uri="sip:ims.mnc000.mcc460.3gppnetwork.org" Digest Authentication Response: "6ebd7700739d5e6d4f8d3c7009147fa3" QOP: auth,nc=00000001,cnonce="dsf232sun603405704xyx" Authentication Token: "F3k9aD3/Zd7ijAeKiWw=" I think the problem lies in module ims_auth. On line 784 of kamailio/src/modules/ims_auth/authorize.c: if (!get_nonce_response(msg, &username, realm, &nonce, &response16, &qop, &qop_str, &nc, &cnonce, &uri, is_proxy_auth) || !nonce.len || !response16.len) { LM_DBG("Nonce or response missing: nonce len [%i], response16 len[%i]\n", nonce.len, response16.len); return AUTH_ERROR; } Basically the code skip re-sync request and return auth failure when "response" is empty. So the IMS server doesn't update SQN with UE and it responds 401 challenge with a old SQN. Re-synchronization can never succeed then. By deleting the existence cheek of response, re-sync passed on my setup。 if (!get_nonce_response(msg, &username, realm, &nonce, &response16, &qop, &qop_str, &nc, &cnonce, &uri, is_proxy_auth) || !nonce.len ) { I hope I didn't miss anything else and won't cause other problem. Regards, Wei-Jian Chen

1 0

Does Kamailio support Cx interface Diameter over SCTP ?
by Tsvetan Filev 16 Jan '18

16 Jan '18

Hi all. This question has already been asked in the past: https://lists.kamailio.org/pipermail/sr-users/2015-July/089083.html But I don't see any answer if this is supported. Can you tell me if it is possible to enable the IMS to talk to HSS using Cx (diameter) over SCTP ? In the source code (kamailio/src/modules/cdp/configparser.c) I can see only these parameters for Peer node: - FQDN - Realm - port - src_addr but there is no protocol parameter. I tried with the example VM here: https://www.kamailio.org/w/2016/02/kamailio-ims-getting-started-box/ I started all services and dumped the traffic with wireshark. The transport is TCP. This VM uses an older version of kamailio: ==================================================== kamailio -v version: kamailio 4.3.4 (x86_64/linux) 583dc0 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, 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 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 583dc0 compiled on 21:01:04 Dec 1 2015 with gcc 4.9.2 ==================================================== So I installed the latest stable but it seems it also uses TCP. Regards.

2 2

Process transactions after server crash?
by Malcolm O'Hare 16 Jan '18

16 Jan '18

Is there any module in kamailio that enables proxies to handle transactions that weren’t created by that proxy? Anything which stores the transaction state in the database? Did a bit of looking but I didn’t see anything that looked like it did that and nothing in the FAQ.

2 1

How much is too much logging
by voipspace voipspace 15 Jan '18

15 Jan '18

Hi I set my logging like this to rsyslog to write to local file log_facility=LOG_LOCAL0 "local0.* -/var/log/kamailio.log" >> /etc/rsyslog.conf The entries I have logging is quite detailed and can even be used to in place of acc info. For each call it writes 50 lines. Would this be considered to many writes and impact performance?

3 4

Configuration Help
by Alexandre Cardoso 15 Jan '18

15 Jan '18

Hi, I’m new in Kamailio and Asterisk world (only 1 week), I’ve installed Kamailio for the 1st time with Siremis GUI. I’m having a problem when adding subscriber on Kamailio, it gives me an error: From Siremis GUI: [2018-01-15 09:54:34 (GMT)] An exception occurred while executing this script: Error message: #0, Error in query:: SELECT T0.id, T0.username, T0.domain, T0.contact, T0.received, T0.path, T0.expires, T0.q, T0.callid, T0.cseq, T0.last_modified, T0.flags, T0.cflags, T0.user_agent, T0.socket, T0.methods, T0.ruid, T0.instance, T0.reg_id, T0.server_id, T0.connection_id, T0.keepalive, T0.partition FROM `location` T0 LIMIT 10. SQLSTATE[42S22]: Column not found: 1054 Unknown column 'T0.server_id' in 'field list' Script name and line number of error: /var/www/html/openbiz/bin/data/BizDataObj_Lite.php:447 function: _run_search ( Array(2) ) @ /var/www/html/openbiz/bin/data/BizDataObj_Lite.php 243 function: fetch ( ) @ /var/www/html/openbiz/bin/easy/EasyForm.php 690 function: fetchDataSet ( ) @ /var/www/html/openbiz/bin/easy/FormRenderer.php 69 function: renderSmarty ( Object(EasyForm), "/var/www/html/siremis/modules/ser/template/grid.tpl" ) @ /var/www/html/openbiz/bin/easy/FormRenderer.php 45 function: render ( Object(EasyForm) ) @ /var/www/html/openbiz/bin/easy/EasyForm.php 1648 function: renderHTML ( ) @ /var/www/html/openbiz/bin/easy/EasyForm.php 1538 function: render ( ) @ /var/www/html/openbiz/bin/easy/ViewRenderer.php 83 function: renderSmarty ( Object(EasyView), "/var/www/html/siremis/modules/ser/template/view_tabs.tpl" ) @ /var/www/html/openbiz/bin/easy/ViewRenderer.php 40 function: render ( Object(EasyView) ) @ /var/www/html/openbiz/bin/easy/EasyView.php 274 function: _render ( ) @ /var/www/html/openbiz/bin/easy/EasyView.php 237 function: render ( ) @ /var/www/html/openbiz/bin/BizController.php 221 function: renderView ( "ser.view.SubscriberListView", "", "", Null, "" ) @ /var/www/html/openbiz/bin/BizController.php 107 function: dispatchRequest ( ) @ /var/www/html/openbiz/bin/BizController.php 32 function: include_once ( "/var/www/html/openbiz/bin/BizController.php" ) @ /var/www/html/siremis/bin/controller.php 6 function: include ( "/var/www/html/siremis/bin/controller.php" ) @ /var/www/html/siremis/bin/_forward.php 102 function: include ( "/var/www/html/siremis/bin/_forward.php" ) @ /var/www/html/siremis/index.php 3 and via kamcli commands [root@localhost html]# kamctl add test1(a)192.168.1.204 test which: no gdb in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/) MySQL password for user 'kamailio@localhost': ERROR 1045 (28000): Access denied for user 'kamailio'@'localhost' (using password: YES) ERROR: introducing the new user 'test1(a)192.168.1.204' to the database failed The password Is correct I can add Domain but not an subscriber or Location list. How can I overcome this issue? Also can you support on how I can do authentication on Kamailio using Asterisk database? Thanks Alex

2 3

Re: [SR-Users] Registration Failure - IMS
by champa wijesooriya 15 Jan '18

15 Jan '18

Sent from my Windows Phone

1 0

IMS Proxy URI translate
by Amar Tinawi 15 Jan '18

15 Jan '18

Hello Dears Recently i'm trying to call B user as a tel:"number" from a registered ims A user i'm facing a strange behavior when the proxy is translating tel:"number" to sip:"number"@mydomain i don't want this kind of translation to be done on the proxy, but to be forwarded to the serving node as it is. is there any place in which i should modify PCSCF configuration ? Regards

1 0

two Kamailio instances suddenly stopped handling packets
by Sebastian Damm 15 Jan '18

15 Jan '18

Hi, this morning, two Kamailio servers suddenly stopped working after having worked without a problem for months. Both are running 5.0.2 on Debian Jessie. Those systems only analyze mirrored traffic and write some information to a RabbitMQ. I tried restarting, but after a few seconds they get stuck the same way as before. Then I attached a gdb to some of the UDP listeners, and they all look pretty much the same. ===========8< process 1 ================= (gdb) bt #0 0x00007f404ca435b9 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007f4049f41260 in futex_get (lock=0x7f4041bccd00) at ../../core/parser/../mem/../futexlock.h:108 #2 0x00007f4049f477d7 in cfg_lock_helper (lkey=0x7fff3c048650, mode=0) at cfgutils.c:667 #3 0x00007f4049f481ed in w_cfg_lock_wrapper (msg=0x7f404ba17f18, key=0x7f404ba15488, mode=0) at cfgutils.c:712 #4 0x00007f4049f4823c in w_cfg_lock (msg=0x7f404ba17f18, key=0x7f404ba15488 "\210a\241K@\177", s2=0x0) at cfgutils.c:717 #5 0x000000000045cd85 in do_action (h=0x7fff3c049410, a=0x7f404b9d5170, msg=0x7f404ba17f18) at core/action.c:1060 #6 0x0000000000469afa in run_actions (h=0x7fff3c049410, a=0x7f404b9d5170, msg=0x7f404ba17f18) at core/action.c:1552 #7 0x000000000045958d in do_action (h=0x7fff3c049410, a=0x7f404b9ce558, msg=0x7f404ba17f18) at core/action.c:678 #8 0x0000000000469afa in run_actions (h=0x7fff3c049410, a=0x7f404b9cdf70, msg=0x7f404ba17f18) at core/action.c:1552 #9 0x000000000046a2bd in run_top_route (a=0x7f404b9cdf70, msg=0x7f404ba17f18, c=0x0) at core/action.c:1641 #10 0x0000000000580033 in receive_msg ( buf=0xa393f9 <buf+121> "REGISTER sip:domain SIP/2.0\r\nVia: SIP/2.0/UDP 1.2.3.4;branch=z9hG4bKfc98.c762d7151f110c7eb71fc7d4e0648f1f.0\r\nVia: SIP/2.0/UDP 192.168.0.3:5060 ;rport=38020;received=62.30.8.128;branch=z9hG4"..., len=799, rcv_info=0x7fff3c049810) at core/receive.c:264 #11 0x00007f40483efcdf in parsing_hepv3_message (buf=0xa39380 <buf> "HEP3\003\230", len=920) at hep.c:499 #12 0x00007f40483ee264 in hepv3_received (buf=0xa39380 <buf> "HEP3\003\230", len=920, ri=0x7fff3c049a50) at hep.c:231 #13 0x00007f40483ec9cb in hep_msg_received (data=0x7fff3c049a30) at hep.c:85 #14 0x000000000049e4e1 in sr_event_exec (type=7, data=0x7fff3c049a30) at core/events.c:263 #15 0x000000000048731a in udp_rcv_loop () at core/udp_server.c:466 #16 0x0000000000422d08 in main_loop () at main.c:1623 #17 0x000000000042a408 in main (argc=13, argv=0x7fff3c049ef8) at main.c:2643 (gdb) quit ===========8< process 1 ================= ===========8< process 2 ================= (gdb) bt #0 0x00007f404ca435b9 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007f4049f41260 in futex_get (lock=0x7f4041bccd00) at ../../core/parser/../mem/../futexlock.h:108 #2 0x00007f4049f477d7 in cfg_lock_helper (lkey=0x7fff3c048650, mode=0) at cfgutils.c:667 #3 0x00007f4049f481ed in w_cfg_lock_wrapper (msg=0x7f404ba17f18, key=0x7f404ba15488, mode=0) at cfgutils.c:712 #4 0x00007f4049f4823c in w_cfg_lock (msg=0x7f404ba17f18, key=0x7f404ba15488 "\210a\241K@\177", s2=0x0) at cfgutils.c:717 #5 0x000000000045cd85 in do_action (h=0x7fff3c049600, a=0x7f404b9d5170, msg=0x7f404ba17f18) at core/action.c:1060 #6 0x0000000000469afa in run_actions (h=0x7fff3c049600, a=0x7f404b9d5170, msg=0x7f404ba17f18) at core/action.c:1552 #7 0x000000000045958d in do_action (h=0x7fff3c049600, a=0x7f404b9cf920, msg=0x7f404ba17f18) at core/action.c:678 #8 0x0000000000469afa in run_actions (h=0x7fff3c049600, a=0x7f404b9ce9c0, msg=0x7f404ba17f18) at core/action.c:1552 #9 0x000000000046a2bd in run_top_route (a=0x7f404b9ce9c0, msg=0x7f404ba17f18, c=0x7fff3c049600) at core/action.c:1641 #10 0x0000000000580a69 in receive_msg ( buf=0xa393f9 <buf+121> "SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP 172.20.40.8;branch=z9hG4bKa69c.5cca5a54c4d270c515eeb4bbb5e0bb44.0\r\nVia: SIP/2.0/UDP 2.3.4.5:5060\r\nContact: <sip:1234567@9.8.7.6:59669;transport=UDP>\r\nTo: "..., len=506, rcv_info=0x7fff3c049810) at core/receive.c:327 #11 0x00007f40483efcdf in parsing_hepv3_message (buf=0xa39380 <buf> "HEP3\002s", len=627) at hep.c:499 #12 0x00007f40483ee264 in hepv3_received (buf=0xa39380 <buf> "HEP3\002s", len=627, ri=0x7fff3c049a50) at hep.c:231 #13 0x00007f40483ec9cb in hep_msg_received (data=0x7fff3c049a30) at hep.c:85 #14 0x000000000049e4e1 in sr_event_exec (type=7, data=0x7fff3c049a30) at core/events.c:263 #15 0x000000000048731a in udp_rcv_loop () at core/udp_server.c:466 #16 0x0000000000422d08 in main_loop () at main.c:1623 #17 0x000000000042a408 in main (argc=13, argv=0x7fff3c049ef8) at main.c:2643 (gdb) quit ===========8< process 2 ================= Looks to me as if Kamailio gets stuck trying to get a lock for this packet. The config file when handling those packets looks like this: request_route { route(initialize_variables); route(foo); } onreply_route { route(initialize_variables); route(foo); } route[initialize_variables] { $vn(bar) = $null; $vn(baz) = $null; $vn(barbaz) = $null; $vn(foobar) = $null; } route[foo] { lock("$ci"); xlog("L_DBG", "Obtained lock, calling lua...\n"); if(!lua_run("handle_packet")) { xlog("L_ERR", "SCRIPT: failed to execute lua function!\n"); } if ($vn(bar) != $null) { route(mediaIpToRedis); } if ($vn(baz) != $null) { route(channelInfoToRedis); } if ($vn(barbaz) != $null) { route(sendToQueue); } xlog("L_DBG", "All finished, releasing lock...\n"); unlock("$ci"); xlog("L_DBG", "Released lock...\n"); # update stats if ($vn(foobar) != $null) { update_stat("$vn(foobar)", "+1"); } drop; exit; } Is there any race condition I am missing? Until this morning, it ran without problems and only every 2 minutes or so, 4 packets were sent to the RabbitMQ. So the system throws away nearly 100% of the traffic (which is around 20 Mbit). In the log file, there are no errors at all, no aborted lua scripts or whatsoever. Does anybody have a hint for me? Thanks in advance. Regards Sebastian

3 5

New Install Homer, No call data stored in DB
by Trent 15 Jan '18

15 Jan '18

Hello. I installed Homer a couple of days ago on new Debian 8 minimal install with HEP configured on Asterisk 14 on another machine. I installed Homer with the quick install script available on Git Hub. As the subject line states, no information is being stored in the daily database tables being created. I have confirmed with tcpdump, the Asterisk 14 machine is sending out data on port 9060. On the Homer side, Kamailio is confirmed listening on port 9060, and tcpdump confirms it is receiving that Asterisk 14 SIP data to port 9060. When starting up Kamailio: In /var/log/messages this is all which is listed (even during calls): Jan 12 11:31:06 Qbox-Homer homer[5815]: INFO: <core> [main.c:810]: sig_usr(): signal 15 received Jan 12 11:31:06 Qbox-Homer homer[5813]: INFO: <core> [main.c:810]: sig_usr(): signal 15 received Jan 12 11:31:06 Qbox-Homer homer[5811]: INFO: <core> [main.c:810]: sig_usr(): signal 15 received Jan 12 11:31:06 Qbox-Homer homer[5801]: INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Jan 12 11:31:07 Qbox-Homer kamailio: INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Jan 12 11:31:07 Qbox-Homer kamailio: WARNING: <core> [socket_info.c:1303]: fix_hostname(): could not rev. resolve 0.0.0.0 Jan 12 11:31:07 Qbox-Homer kamailio: INFO: <core> [tcp_main.c:4665]: init_tcp(): using epoll_lt as the io watch method (auto detected) Jan 12 11:31:07 Qbox-Homer homer[20228]: INFO: sipcapture [sipcapture.c:437]: parse_table_names(): INFO: table name:sip_capture Jan 12 11:31:08 Qbox-Homer homer[20228]: INFO: <core> [udp_server.c:150]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Jan 12 11:31:08 Qbox-Homer homer[20228]: INFO: <core> [udp_server.c:200]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 And here is Kamailio starting at debug level 2 in /var/log/syslog Jan 12 11:44:29 Qbox-Homer systemd[1]: Starting Kamailio (OpenSER) - the Open Source SIP Server... Jan 12 11:44:29 Qbox-Homer kamailio: INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Jan 12 11:44:29 Qbox-Homer kamailio: WARNING: <core> [socket_info.c:1303]: fix_hostname(): could not rev. resolve 0.0.0.0 Jan 12 11:44:29 Qbox-Homer kamailio: INFO: <core> [tcp_main.c:4665]: init_tcp(): using epoll_lt as the io watch method (auto detected) Jan 12 11:44:29 Qbox-Homer kamailio[23757]: Listening on Jan 12 11:44:29 Qbox-Homer kamailio[23757]: udp: 0.0.0.0:9060 Jan 12 11:44:29 Qbox-Homer kamailio[23757]: Aliases: Jan 12 11:44:29 Qbox-Homer homer[23759]: INFO: sipcapture [sipcapture.c:437]: parse_table_names(): INFO: table name:sip_capture Jan 12 11:44:29 Qbox-Homer homer[23759]: INFO: <core> [udp_server.c:150]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Jan 12 11:44:29 Qbox-Homer homer[23759]: INFO: <core> [udp_server.c:200]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Jan 12 11:44:29 Qbox-Homer systemd[1]: Started Kamailio (OpenSER) - the Open Source SIP Server. No more messages appear during, or after a call is terminated. Any more suggestions? Thanks!

3 7

check auth_check return code
by David Villasmil 15 Jan '18

15 Jan '18

Is this possible? I'm trying with: if (auth_check("$fd", "subscriber", "1")==-2) { log something } i'm trying to find out if the username actually exists in the db, but the password provided was wrong... Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 ᐧ

2 1

send_data keeps connection open
by voipspace voipspace 15 Jan '18

15 Jan '18

Hi I tried send_data it transmits the data however the socket connect remains open. Is it possibe to just send. I dont want the other end to need to close the connect or reply. thanks

2 1

kamailio 4.4.1 DROUTING module memory leak ?
by Uri Shacked 14 Jan '18

14 Jan '18

Hi, I have some kind of memory growth (leak?). kamailio 4.4.1. started with 64M for shmem, had a crash after 5 days of traffic. increased shmem to 128, but still memory grows everyday. when traffic load decrease, the memory growth stops but memory stays on the same level. when traffic increase again,used memory continue to grows again. I started kamailio now with the "-x qm" option to debug shmem. every half hour i dump the status of it. there are several modules that the memory size is increasing (some of them are obvious). but, one is very strange.... DROUTING I am using drouting module for each call on my kamailio. the DB tables are very small, and there is no reloads. only one time used in my script : .. ... subst_user('/(.*)/$avp(xxx)/'); if(!do_routing("$avp(yyyy)")){ xlog...somthing; return(-1) } .. .... the shmem that is rapidly growing and does not make sense is: "from drouting: dr_time.c: ac_get_maxval(219)" seems that when i used mem_join =1, the growth was smaller, but still significant. now i use mem_join = 0, it seems rapidly increasing... I have more information from the logs, will send it if necessary (it is just a lot...) any ideas ? cheers, Uri

2 9

how to check $ua
by David Villasmil 14 Jan '18

14 Jan '18

I'm trying to verify the auth username begins with, i.e. "32", but i'm using in AUTH route: if( !($au=~"32") ){ do something } and that's not working, and i don't get why? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 ᐧ

3 2

T_precheck_trans
by Abdelmuhaimen Seaudi 12 Jan '18

12 Jan '18

Hi. In the below part from kamailio.cfg, why didn't we just exit if t_precheck_trans returns true ? Why did we run t_check_trans, although there might be another process already running the other t_check_trans ? # handle retransmissions if (!is_method("ACK")) { if(t_precheck_trans()) { t_check_trans(); exit; } t_check_trans(); }

2 1

Free size of shared memory falls to near zero during the load testing
by Andrey Deykunov 12 Jan '18

12 Jan '18

Hi, We use kamailio as a router in our PBX server. The test below causes significant decreasing of free shared memory and many "out of memory" errors in kamailio log: Preconditions: kamailio server with 256Mb of shared memory allocated. Test actions: run two load testing scripts at the same time: 1) 10000 register operations; 2) 20000 calls (about 300 per sec); Results: 1) memory consumption in peak values: - shmem.free_size: 1.8Mb - core: 120Mb: - build_req_buf_from_sip_req: 12.5Mb - msg_lump_cloner: 23.6Mb - sip_msg_shm_clone: 84Mb - tm module: 118Mb 2) shmem.free_size parameter back to normal after the test, so it could be concluded that we don't have any memory leaks. Is it normal behavior or it's possible to do something to increase performance? PS: the same behaviour occurs for various values of shared memory defined at the start of kamailio server (128Mb, 256Mb, 512Mb etc.). Thank you, Andrey

3 5

Re: [SR-Users] app_lua sr.sqlops.query exit status
by Daniel-Constantin Mierla 11 Jan '18

11 Jan '18

I have master (which should be more or less like latest 5.1) running with app_lua, but on debian 9.0. From backtrace, no obvious issue. Wondering if you can get a stripped down version of you config with as less loaded modules as possible and minimal routing blocks that expose the issue, so I can try it here. Try to load only the app_lua and the modules it binds to and see if crashes ... if not, it could be a side effect from other place. Cheers, Daniel On 10.01.18 12:44, jenus(a)cyberchaos.nl wrote: > Daniel, > > (gdb) frame 5 > #5 0x00007fd3b2684870 in lua_sr_kemi_register_libs (L=0xeffdb0) at > app_lua_sr.c:1973 > 1973 app_lua_sr.c: No such file or directory. > (gdb) list > 1968 in app_lua_sr.c > (gdb) info locals > _sr_crt_KSRMethods = 0xf0cf80 > emods = 0xa59a00 <_sr_kemi_modules> > emods_size = 37 > i = 3 > k = 35 > n = 346 > mname = > "KSR.uac_redirect\000\000\000\000\000\000\000\000\256\240B\262\323\177\000\000й\360\000\000\000\000\000\004\000\000\000\323\177\000\000 > ˏ\262\323\177\000\000\000\362\066\000\234\324\302Ͱ\375\357", '\000' > <repeats 21 times>, > "\065\246C\262\323\177\000\000@\265\225\356\376\177\000\000\000\000\000\000\377\377\377\377\000\000\000\000\000\000\000\000\177\241m\262\323\177\000" > __FUNCTION__ = "lua_sr_kemi_register_libs" > > (gdb) frame 6 > #6 0x00007fd3b26cf107 in lua_sr_openlibs (L=0xeffdb0) at > app_lua_api.c:185 > 185 app_lua_api.c: No such file or directory. > (gdb) list > 180 in app_lua_api.c > (gdb) info locals > No locals. > > > Jan > > > Daniel-Constantin Mierla schreef op 2018-01-10 12:40: >> Now the backtrace is different, gram the output for info locals in frame >> 5 and 6. >> >> Cheers, >> Daniel >> >> >> On 10.01.18 11:26, jenus(a)cyberchaos.nl wrote: >>> I have overwritten the core file b y accident. I did a new backtrace: >>> >>> (gdb) backtrace >>> #0 0x00007fd3b24365a0 in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #1 0x00007fd3b2437b62 in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #2 0x00007fd3b242a040 in lua_settable () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #3 0x00007fd3b243a412 in luaL_findtable () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #4 0x00007fd3b243a581 in luaL_openlib () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #5 0x00007fd3b2684870 in lua_sr_kemi_register_libs (L=0xeffdb0) at >>> app_lua_sr.c:1973 >>> #6 0x00007fd3b26cf107 in lua_sr_openlibs (L=0xeffdb0) at >>> app_lua_api.c:185 >>> #7 0x00007fd3b26cf7c1 in lua_sr_init_probe () at app_lua_api.c:225 >>> #8 0x00007fd3b265b97d in child_init (rank=-127) at app_lua_mod.c:197 >>> #9 0x0000000000549944 in init_mod_child (m=0x7fd3bc82cc70, rank=-127) >>> at core/sr_module.c:938 >>> #10 0x0000000000549c72 in init_child (rank=-127) at >>> core/sr_module.c:964 >>> #11 0x0000000000422c1c in main_loop () at main.c:1576 >>> #12 0x000000000042aab9 in main (argc=3, argv=0x7ffeee95b548) at >>> main.c:2646 >>> >>> (gdb) frame 7 >>> #7 0x00007fd3b26cf7c1 in lua_sr_init_probe () at app_lua_api.c:225 >>> 225 app_lua_api.c: No such file or directory. >>> (gdb) list >>> 220 in app_lua_api.c >>> (gdb) info locals >>> L = 0xeffdb0 >>> txt = 0x7fd3bd00dce7 <__fprintf+135> "H\201\304", <incomplete sequence >>> \330> >>> li = 0x0 >>> sbuf = {st_dev = 0, st_ino = 206158430256, st_nlink = 140732901208248, >>> st_mode = 4002787296, st_uid = 32766, st_gid = 4002787464, __pad0 = >>> 14, st_rdev = 140728898420739, st_size = 0, >>> st_blksize = 30795, st_blocks = 7970120, st_atim = {tv_sec = >>> 7929944, tv_nsec = 0}, st_mtim = {tv_sec = 0, tv_nsec = >>> 140732901208128}, st_ctim = {tv_sec = 140547210663782, >>> tv_nsec = 7938688}, __glibc_reserved = {-541165879423, >>> 140732901208240, 5544260}} >>> __FUNCTION__ = "lua_sr_init_probe" >>> >>> I assume that in this case i need to do a "frame 7". >>> >>> >>> Jan >>> >>> Daniel-Constantin Mierla schreef op 2018-01-10 11:18: >>>> Few more things to grab from core file with gdb -- take the output for >>>> the next commands: >>>> >>>> frame 16 >>>> >>>> list >>>> >>>> info locals >>>> >>>> Cheers, >>>> Daniel >>>> >>>> >>>> On 10.01.18 11:08, jenus(a)cyberchaos.nl wrote: >>>>> Daniel, >>>>> >>>>> Here are the app_lua settings: >>>>> >>>>> # ----- app_lua params ----- >>>>> modparam("app_lua", "load", "/etc/kamailio/kamailio_functions.lua") >>>>> modparam("app_lua", "register", "sqlops") >>>>> modparam("app_lua", "register", "siputils") >>>>> modparam("app_lua", "register", "xhttp") >>>>> >>>>> >>>>> Jan >>>>> >>>>> >>>>> Daniel-Constantin Mierla schreef op 2018-01-10 11:03: >>>>>> Can you give here the parameters you set for app_lua module? >>>>>> >>>>>> Cheers, >>>>>> Daniel >>>>>> >>>>>> >>>>>> On 09.01.18 22:27, jenus(a)cyberchaos.nl wrote: >>>>>>> Daniel, >>>>>>> >>>>>>> Here is the backtrace. >>>>>>> >>>>>>> (gdb) backtrace >>>>>>> #0 0x00007fe41140e067 in __GI_raise (sig=sig@entry=6) at >>>>>>> ../nptl/sysdeps/unix/sysv/linux/raise.c:56 >>>>>>> #1 0x00007fe41140f448 in __GI_abort () at abort.c:89 >>>>>>> #2 0x00007fe41144c1b4 in __libc_message >>>>>>> (do_abort=do_abort@entry=1, >>>>>>> fmt=fmt@entry=0x7fe411541210 "*** Error in `%s': %s: 0x%s >>>>>>> ***\n") at >>>>>>> ../sysdeps/posix/libc_fatal.c:175 >>>>>>> #3 0x00007fe41145198e in malloc_printerr (action=1, >>>>>>> str=0x7fe41153d42a "realloc(): invalid next size", ptr=<optimized >>>>>>> out>) at malloc.c:4996 >>>>>>> #4 0x00007fe41145476b in _int_realloc (av=av@entry=0x7fe41177e620 >>>>>>> <main_arena>, oldp=oldp@entry=0x21789c0, oldsize=oldsize@entry=736, >>>>>>> nb=nb@entry=1552) at malloc.c:4234 >>>>>>> #5 0x00007fe411455769 in __GI___libc_realloc (oldmem=0x21789d0, >>>>>>> bytes=1536) at malloc.c:3029 >>>>>>> #6 0x00007fe40c460cae in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #7 0x00007fe40c45c9aa in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #8 0x00007fe40c46166d in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #9 0x00007fe40c4640b3 in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #10 0x00007fe40c45ccd1 in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #11 0x00007fe40c45c92e in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #12 0x00007fe40c45d7bb in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #13 0x00007fe40c45d8c2 in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #14 0x00007fe40c459528 in lua_load () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #15 0x00007fe40c469d8c in luaL_loadbuffer () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #16 0x00007fe40c6fe7d7 in lua_sr_init_probe () at app_lua_api.c:228 >>>>>>> #17 0x00007fe40c68a97d in child_init (rank=-127) at >>>>>>> app_lua_mod.c:197 >>>>>>> #18 0x0000000000549944 in init_mod_child (m=0x7fe410c3b998, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:938 >>>>>>> #19 0x0000000000549662 in init_mod_child (m=0x7fe410c3bec0, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #20 0x0000000000549662 in init_mod_child (m=0x7fe410c3c708, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #21 0x0000000000549662 in init_mod_child (m=0x7fe410c3cd78, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #22 0x0000000000549662 in init_mod_child (m=0x7fe410c3d360, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #23 0x0000000000549662 in init_mod_child (m=0x7fe410c3e1e8, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #24 0x0000000000549662 in init_mod_child (m=0x7fe410c3e938, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #25 0x0000000000549662 in init_mod_child (m=0x7fe410c3f4c8, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #26 0x0000000000549662 in init_mod_child (m=0x7fe410c3fca0, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #27 0x0000000000549662 in init_mod_child (m=0x7fe410c40118, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #28 0x0000000000549662 in init_mod_child (m=0x7fe410c40780, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #29 0x0000000000549662 in init_mod_child (m=0x7fe410c422f8, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #30 0x0000000000549662 in init_mod_child (m=0x7fe410c42968, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #31 0x0000000000549662 in init_mod_child (m=0x7fe410c42e50, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #32 0x0000000000549662 in init_mod_child (m=0x7fe410c43b48, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #33 0x0000000000549662 in init_mod_child (m=0x7fe410c43f20, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #34 0x0000000000549662 in init_mod_child (m=0x7fe410c446e0, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #35 0x0000000000549662 in init_mod_child (m=0x7fe410c44bd0, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #36 0x0000000000549662 in init_mod_child (m=0x7fe410c44ec8, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #37 0x0000000000549662 in init_mod_child (m=0x7fe410c45378, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #38 0x0000000000549662 in init_mod_child (m=0x7fe410c458f0, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #39 0x0000000000549662 in init_mod_child (m=0x7fe410c45e48, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #40 0x0000000000549662 in init_mod_child (m=0x7fe410c464e8, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #41 0x0000000000549662 in init_mod_child (m=0x7fe410c47278, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #42 0x0000000000549662 in init_mod_child (m=0x7fe410c476f0, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #43 0x0000000000549662 in init_mod_child (m=0x7fe410c47b68, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #44 0x0000000000549c72 in init_child (rank=-127) at >>>>>>> core/sr_module.c:964 >>>>>>> #45 0x0000000000422c1c in main_loop () at main.c:1576 >>>>>>> #46 0x000000000042aab9 in main (argc=3, argv=0x7ffe17f0e788) at >>>>>>> main.c:2646 >>>>>>> >>>>>>> >>>>>>> Jan >>>>>>> >>>>>>> Daniel-Constantin Mierla schreef op 2018-01-09 22:21: >>>>>>>> Can you install the debug symbols for kamailio as well? There >>>>>>>> should be >>>>>>>> a kamailio-dbg package or so ... >>>>>>>> >>>>>>>> Then take again the backtrace, it should provide more >>>>>>>> information -- >>>>>>>> file and line for each frame, ... >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Daniel >>>>>>>> >>>>>>>> >>>>>>>> On 09.01.18 21:21, jenus(a)cyberchaos.nl wrote: >>>>>>>>> Daniel, >>>>>>>>> >>>>>>>>> Just upgraded to 5.1 but kamailio now generates a core file. I'm >>>>>>>>> running debian 8.10. It seems to crash on liblua5.1.so.0 : >>>>>>>>> >>>>>>>>> Using host libthread_db library >>>>>>>>> "/lib/x86_64-linux-gnu/libthread_db.so.1". >>>>>>>>> Core was generated by `kamailio -m 1500'. >>>>>>>>> Program terminated with signal SIGSEGV, Segmentation fault. >>>>>>>>> #0 0x00007f30c17f25a0 in ?? () from >>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>> (gdb) backtrace >>>>>>>>> #0 0x00007f30c17f25a0 in ?? () from >>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>> #1 0x00007f30c17f3b62 in ?? () from >>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>> #2 0x00007f30c17e6040 in lua_settable () from >>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>> #3 0x00007f30c17f6412 in luaL_findtable () from >>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>> #4 0x00007f30c17f6581 in luaL_openlib () from >>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>> #5 0x00007f30c1a40870 in lua_sr_kemi_register_libs () from >>>>>>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>>>>>> #6 0x00007f30c1a8b107 in lua_sr_openlibs () from >>>>>>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>>>>>> #7 0x00007f30c1a8b7c1 in lua_sr_init_probe () from >>>>>>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>>>>>> #8 0x00007f30c1a1797d in ?? () from >>>>>>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>>>>>> #9 0x0000000000549944 in ?? () >>>>>>>>> #10 0x0000000000549c72 in init_child () >>>>>>>>> #11 0x0000000000421498 in main_loop () >>>>>>>>> #12 0x000000000042aab9 in main () >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> >>>>>>>>> Jan >>>>>>>>> >>>>>>>>> jenus(a)cyberchaos.nl schreef op 2018-01-09 20:53: >>>>>>>>>> Daniel, >>>>>>>>>> >>>>>>>>>> Currently running kamailio 5.0.5. >>>>>>>>>> >>>>>>>>>> Jan >>>>>>>>>> >>>>>>>>>> Daniel-Constantin Mierla schreef op 2018-01-09 13:27: >>>>>>>>>>> Hello, >>>>>>>>>>> >>>>>>>>>>> what version of kamailio are you using? >>>>>>>>>>> >>>>>>>>>>> Cheers, >>>>>>>>>>> Daniel >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 07.01.18 22:14, jenus(a)cyberchaos.nl wrote: >>>>>>>>>>>> Hello, >>>>>>>>>>>> >>>>>>>>>>>> I'm doing some tests with a lua script and app_lua. I'm using >>>>>>>>>>>> sr.sqlops.query to insert records into the database but would >>>>>>>>>>>> like to >>>>>>>>>>>> test the exit status of the sql query. In kamailio i can do: >>>>>>>>>>>> >>>>>>>>>>>> if(!sql_query("kamailio", "INSERT INTO subscriber ...")) >>>>>>>>>>>> >>>>>>>>>>>> Is there some kind of exit status for the lua function >>>>>>>>>>>> sr.sqlops.query >>>>>>>>>>>> in order to do the same check in lua? In other words, is it >>>>>>>>>>>> possible >>>>>>>>>>>> to check if a sql query was successful in lua? The result >>>>>>>>>>>> seems >>>>>>>>>>>> to be >>>>>>>>>>>> nill in all cases for a INSERT in lua using sr.sqlops.query. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Thanks, >>>>>>>>>>>> >>>>>>>>>>>> Jan Hazenberg >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Kamailio (SER) - Users Mailing List >>>>>>>>>>>> sr-users(a)lists.kamailio.org >>>>>>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Kamailio (SER) - Users Mailing List >>>>>>>>>> sr-users(a)lists.kamailio.org >>>>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>>>>>>> >>>>>>> >>>>> >>> > -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

2 3

Siremis Subscriber List
by Alexandre Cardoso 11 Jan '18

11 Jan '18

Hi Guys, I’m a new guy working with Kamailio and sirens, could you help on a issue that I’ve found? I just installed Kamailio and Siremis and went to the Siremis GUI. I want to add subscriber to subscriber list and I’m facing the following error: [2018-01-11 11:22:18 (GMT)] An exception occurred while executing this script: Error message: #0, Error in query:: SELECT T0.id, T0.username, T0.domain, T0.contact, T0.received, T0.path, T0.expires, T0.q, T0.callid, T0.cseq, T0.last_modified, T0.flags, T0.cflags, T0.user_agent, T0.socket, T0.methods, T0.ruid, T0.instance, T0.reg_id, T0.server_id, T0.connection_id, T0.keepalive, T0.partition FROM `location` T0 LIMIT 10. SQLSTATE[42S22]: Column not found: 1054 Unknown column 'T0.server_id' in 'field list' Script name and line number of error: : function: _run_search ( Array(2) ) @ /var/www/html/openbiz/bin/data/BizDataObj_Lite.php 243 function: fetch ( ) @ /var/www/html/openbiz/bin/easy/EasyForm.php 690 function: fetchDataSet ( ) @ /var/www/html/openbiz/bin/easy/FormRenderer.php 69 function: renderSmarty ( Object(EasyForm), "/var/www/html/siremis/modules/ser/template/grid.tpl" ) @ /var/www/html/openbiz/bin/easy/FormRenderer.php 45 function: render ( Object(EasyForm) ) @ /var/www/html/openbiz/bin/easy/EasyForm.php 1648 function: renderHTML ( ) @ /var/www/html/openbiz/bin/easy/EasyForm.php 1538 function: render ( ) @ /var/www/html/openbiz/bin/easy/ViewRenderer.php 83 function: renderSmarty ( Object(EasyView), "/var/www/html/siremis/modules/ser/template/view_tabs.tpl" ) @ /var/www/html/openbiz/bin/easy/ViewRenderer.php 40 function: render ( Object(EasyView) ) @ /var/www/html/openbiz/bin/easy/EasyView.php 274 function: _render ( ) @ /var/www/html/openbiz/bin/easy/EasyView.php 237 function: render ( ) @ /var/www/html/openbiz/bin/BizController.php 221 function: renderView ( "ser.view.SubscriberListView", "", "", Null, "" ) @ /var/www/html/openbiz/bin/BizController.php 107 function: dispatchRequest ( ) @ /var/www/html/openbiz/bin/BizController.php 32 function: include_once ( "/var/www/html/openbiz/bin/BizController.php" ) @ /var/www/html/siremis/bin/controller.php 6 function: include ( "/var/www/html/siremis/bin/controller.php" ) @ /var/www/html/siremis/bin/_forward.php 102 function: include ( "/var/www/html/siremis/bin/_forward.php" ) @ /var/www/html/siremis/index.php 3 Please ask system administrator for help… Have you faced already a similar issue? Or do you know how I can add those subscribers via command line? Thanks in advance for your help Alex

1 0

kamailio-5.0.5 active/passive pcs/cluster with rtpengine - how to fix calls after failover
by Karsten Horsmann 11 Jan '18

11 Jan '18

Hello List, and also an happy new year to everyone. I use CentOS 7.4.x with kamailio 5.0.5 and rtpengine on a pacemaker/corosync cluster in front of an internal kamailio siprouter and media-services. If i did an "pcs node standby" to failover my frontend-kamailio (udp/tcp 5060, udp/tcp 5061-tls and tcp websocket-secure) i noticed the following scenarios: 1) Plain RTP: just stocks a few seconds and flows. Everything fine. 2) SDES/RTP: silence - but REINVITE manually in my client brings audio back. Need improvement. 3) DTLS/RTP WebRTC: silence - all clients shows an active call. I know that there is NO way to recover this call - because of the temporay DTLS certificate due the rtpengine start-up. So i thought - for scenario1) i dont need anything to do. Works nice. For scenario2) i need something to "remember its SDES/RTP calls and send them an REINVITE" And for scenario3) i should just hangup all WebRTC calls - IMHO the best for that. How can i fire-up these tasks to get an "clean-up" or "reinvite" after an failover? scenario legend: 1) unencrypted call 2) TLS/SDES encrypted call 3) DTÖS WebRTC encrypted call -- Kind Regards *Karsten Horsmann*

2 8

XML-RPC htable.reload
by Martin Nyström 11 Jan '18

11 Jan '18

Hi, I am trying to use XML-RPC for issuing a htable.reload but fails to get it working properly. In this scenario I am trying to reload the htable “foobar”. My XML doc looks as follows: <?xml version="1.0"?> <methodCall> <methodName>htable.reload foobar</methodName> <params></params> </methodCall> The returned response is: <?xml version="1.0"?> <methodResponse> <fault> <value> <struct> <member> <name>faultCode</name> <value><int>500</int></value> </member> <member> <name>faultString</name> <value><string>Method Not Found</string></value> </member> </struct> </value> </fault> </methodResponse> So my question is really how I can use XML-RPC to reload a htable. I am probaly missing a field here or anything like that. kamailio 4.4.5 (x86_64/linux) Regards

1 0

Error linking contact to IMPU on SCSCF
by Rafi A. 11 Jan '18

11 Jan '18

Hi there, I need some help here to understand why the query in [usrloc_db.c:1084] is empty. This causes the linking of contact to IMPU to fail. I'm using Kamailio 5.0.4. 10(13882) DEBUG: ims_usrloc_scscf [impurecord.c:1284]: unref_subscription_unsafe(): un-reffing subscription [rafi(a)mnc001.mcc001.3gppnetwork.org] - was [3] 10(13882) DEBUG: ims_registrar_scscf [save.c:519]: update_contacts_helper(): updating the contacts for IMPU <sip:rafi@mnc001.mcc001.3gppnetwork.org> 10(13882) DEBUG: ims_registrar_scscf [save.c:137]: calc_contact_expires(): Calculated expires for contact is 600000 10(13882) DEBUG: ims_registrar_scscf [save.c:548]: update_contacts_helper(): Need to update contact: <sip:rafi@192.168.10.48:57230;transport=udp>: q_value [-1],sos: [0],expires [600000] 10(13882) DEBUG: ims_registrar_scscf [save.c:550]: update_contacts_helper(): packing contact information 10(13882) DEBUG: ims_registrar_scscf [save.c:556]: update_contacts_helper(): adding/updating contact based on prior existence 10(13882) DEBUG: ims_usrloc_scscf [impurecord.c:748]: get_scontact(): looking for contact [sip:rafi@192.168.10.48:57230;transport=udp] in slot 300 10(13882) DEBUG: ims_registrar_scscf [save.c:562]: update_contacts_helper(): inserting new contact 10(13882) DEBUG: ims_usrloc_scscf [impurecord.c:562]: insert_scontact(): INSERTing ucontact in usrloc module 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [+g.3gpp.cs-voice] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [+g.3gpp.icsi-ref] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [audio] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [+g.oma.sip-im.large-message] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [+g.3gpp.smsip] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [language] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [+g.oma.sip-im] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [expires] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:173]: new_ucontact(): generating hash based on [sip:rafi@192.168.10.48:57230;transport=udp] 10(13882) DEBUG: ims_usrloc_scscf [impurecord.c:280]: mem_insert_scontact(): Created new contact in memory with AOR: [sip:rafi@192.168.10.48:57230;transport=udp] and hash [300] 10(13882) DEBUG: ims_usrloc_scscf [usrloc_db.c:289]: db_insert_ucontact(): DB: inserting ucontact [sip:rafi@192.168.10.48:57230;transport=udp] 10(13882) DEBUG: ims_usrloc_scscf [usrloc_db.c:311]: db_insert_ucontact(): Converted params to string to insert into db: [+g.3gpp.cs-voice;+g.3gpp.icsi-ref=urn%3Aurn-7%3A3gpp-application.ims.iari.g sma-vs;audio;+g.oma.sip-im.large-message;+g.3gpp.smsip;language=en,fr;+g.oma .sip-im;expires=600000] 10(13882) DEBUG: ims_usrloc_scscf [udomain.c:843]: ref_contact_unsafe(): incrementing ref count on contact [sip:rafi@192.168.10.48:57230;transport=udp], was 1 10(13882) DEBUG: ims_usrloc_scscf [impurecord.c:1225]: link_contact_to_impu(): number of contacts for IMPU [sip:rafi@mnc001.mcc001.3gppnetwork.org] is 1 10(13882) DEBUG: ims_usrloc_scscf [usrloc_db.c:1065]: db_link_contact_to_impu(): DB: linking contact to IMPU 10(13882) DEBUG: ims_usrloc_scscf [usrloc_db.c:1084]: db_link_contact_to_impu(): QUERY IS [] and len is 0 10(13882) ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Query was empty (1065) 10(13882) ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query 10(13882) ERROR: ims_usrloc_scscf [usrloc_db.c:1086]: db_link_contact_to_impu(): Unable to link impu-contact in DB - impu [ <sip:rafi@mnc001.mcc001.3gppnetwork.org> sip:rafi@mnc001.mcc001.3gppnetwork.org], contact [ <sip:rafi@192.168.10.48:57230;transport=udp> sip:rafi@192.168.10.48:57230;transport=udp] 10(13882) ERROR: ims_usrloc_scscf [impurecord.c:1227]: link_contact_to_impu(): Failed to update DB linking contact [ <sip:rafi@192.168.10.48:57230;transport=udp> sip:rafi@192.168.10.48:57230;transport=udp] to IMPU [ <sip:rafi@mnc001.mcc001.3gppnetwork.org> sip:rafi@mnc001.mcc001.3gppnetwork.org]...continuing but db will be out of sync! 10(13882) DEBUG: ims_usrloc_scscf [udomain.c:852]: unref_contact_unsafe(): decrementing ref count on contact [sip:rafi@192.168.10.48:57230;transport=udp], was 2 Best Regards, Rafael A.

1 0

Re: [SR-Users] TLS cipher suites
by Steve 10 Jan '18

10 Jan '18

Hello, Thank you both for your responses to my query about TLS cipher suites supported by Kamailio 4.3.4. When I used a self-signed certificate generated from an RSA key, the server selected the RSA-AES256-GCM-SHA384 cipher suite for the connection. When I used a self-signed certificate generated from an EC key, the server selected the ECDH-ECDSA-AES256-GCM-SHA384 cipher suite for the connection. This was confirmed using the OpenSSL /s_client/ command and with Wireshark. In short, I am still unable to establish an ECDHE ephemeral key exchange even though the OpenSSL version 1.0.2g on Lubuntu 16.4.3 supports it. So I must not have the correct configuration of the TLS module for Kamailio 4.3.4 or else need to generate some other kind of key/certificate. I'm using the Kamailio and TLS config files that came with the package downloads, minimally modified to enable TLS and specify the file location of the key and certificate. I googled "ephemeral key exchange" and came across a posting on Stack Exchange talking about commands such as /SSL_CTX_set_temp_ecdh_callback/ that enable ephemeral key exchange. This command is not listed as a configuration setting in the TLS module man-page so I assume it is a coding command used within the module. In any case, I'd appreciate any further suggestions. Thanks, Steve --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 2

Anyone successfully run Fortify on Kamailio?
by Malcolm O'Hare 10 Jan '18

10 Jan '18

I've been trying to run Fortify Static Code Analyzer on the Kamailio build but all the ways its suggested to hook the build aren't working. I'm curious if anyone has tried to run it and been successful, and if they saved / remember what they did.

1 0

usrloc rpc command ul add
by Евгений Голей 10 Jan '18

10 Jan '18

Hello! Tell me how, when using the "kamcmd ul.add location username@domain sip:contact_username@contact_ip:contact_port 0 1.0 ??? 0 0 0" command, specify parameters that are not used, for example path ? -- С уважением, Евгений Голей

2 2

Re: [SR-Users] app_lua sr.sqlops.query exit status
by Daniel-Constantin Mierla 10 Jan '18

10 Jan '18

Now the backtrace is different, gram the output for info locals in frame 5 and 6. Cheers, Daniel On 10.01.18 11:26, jenus(a)cyberchaos.nl wrote: > I have overwritten the core file b y accident. I did a new backtrace: > > (gdb) backtrace > #0 0x00007fd3b24365a0 in ?? () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #1 0x00007fd3b2437b62 in ?? () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #2 0x00007fd3b242a040 in lua_settable () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #3 0x00007fd3b243a412 in luaL_findtable () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #4 0x00007fd3b243a581 in luaL_openlib () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #5 0x00007fd3b2684870 in lua_sr_kemi_register_libs (L=0xeffdb0) at > app_lua_sr.c:1973 > #6 0x00007fd3b26cf107 in lua_sr_openlibs (L=0xeffdb0) at > app_lua_api.c:185 > #7 0x00007fd3b26cf7c1 in lua_sr_init_probe () at app_lua_api.c:225 > #8 0x00007fd3b265b97d in child_init (rank=-127) at app_lua_mod.c:197 > #9 0x0000000000549944 in init_mod_child (m=0x7fd3bc82cc70, rank=-127) > at core/sr_module.c:938 > #10 0x0000000000549c72 in init_child (rank=-127) at core/sr_module.c:964 > #11 0x0000000000422c1c in main_loop () at main.c:1576 > #12 0x000000000042aab9 in main (argc=3, argv=0x7ffeee95b548) at > main.c:2646 > > (gdb) frame 7 > #7 0x00007fd3b26cf7c1 in lua_sr_init_probe () at app_lua_api.c:225 > 225 app_lua_api.c: No such file or directory. > (gdb) list > 220 in app_lua_api.c > (gdb) info locals > L = 0xeffdb0 > txt = 0x7fd3bd00dce7 <__fprintf+135> "H\201\304", <incomplete sequence > \330> > li = 0x0 > sbuf = {st_dev = 0, st_ino = 206158430256, st_nlink = 140732901208248, > st_mode = 4002787296, st_uid = 32766, st_gid = 4002787464, __pad0 = > 14, st_rdev = 140728898420739, st_size = 0, > st_blksize = 30795, st_blocks = 7970120, st_atim = {tv_sec = > 7929944, tv_nsec = 0}, st_mtim = {tv_sec = 0, tv_nsec = > 140732901208128}, st_ctim = {tv_sec = 140547210663782, > tv_nsec = 7938688}, __glibc_reserved = {-541165879423, > 140732901208240, 5544260}} > __FUNCTION__ = "lua_sr_init_probe" > > I assume that in this case i need to do a "frame 7". > > > Jan > > Daniel-Constantin Mierla schreef op 2018-01-10 11:18: >> Few more things to grab from core file with gdb -- take the output for >> the next commands: >> >> frame 16 >> >> list >> >> info locals >> >> Cheers, >> Daniel >> >> >> On 10.01.18 11:08, jenus(a)cyberchaos.nl wrote: >>> Daniel, >>> >>> Here are the app_lua settings: >>> >>> # ----- app_lua params ----- >>> modparam("app_lua", "load", "/etc/kamailio/kamailio_functions.lua") >>> modparam("app_lua", "register", "sqlops") >>> modparam("app_lua", "register", "siputils") >>> modparam("app_lua", "register", "xhttp") >>> >>> >>> Jan >>> >>> >>> Daniel-Constantin Mierla schreef op 2018-01-10 11:03: >>>> Can you give here the parameters you set for app_lua module? >>>> >>>> Cheers, >>>> Daniel >>>> >>>> >>>> On 09.01.18 22:27, jenus(a)cyberchaos.nl wrote: >>>>> Daniel, >>>>> >>>>> Here is the backtrace. >>>>> >>>>> (gdb) backtrace >>>>> #0 0x00007fe41140e067 in __GI_raise (sig=sig@entry=6) at >>>>> ../nptl/sysdeps/unix/sysv/linux/raise.c:56 >>>>> #1 0x00007fe41140f448 in __GI_abort () at abort.c:89 >>>>> #2 0x00007fe41144c1b4 in __libc_message (do_abort=do_abort@entry=1, >>>>> fmt=fmt@entry=0x7fe411541210 "*** Error in `%s': %s: 0x%s ***\n") at >>>>> ../sysdeps/posix/libc_fatal.c:175 >>>>> #3 0x00007fe41145198e in malloc_printerr (action=1, >>>>> str=0x7fe41153d42a "realloc(): invalid next size", ptr=<optimized >>>>> out>) at malloc.c:4996 >>>>> #4 0x00007fe41145476b in _int_realloc (av=av@entry=0x7fe41177e620 >>>>> <main_arena>, oldp=oldp@entry=0x21789c0, oldsize=oldsize@entry=736, >>>>> nb=nb@entry=1552) at malloc.c:4234 >>>>> #5 0x00007fe411455769 in __GI___libc_realloc (oldmem=0x21789d0, >>>>> bytes=1536) at malloc.c:3029 >>>>> #6 0x00007fe40c460cae in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #7 0x00007fe40c45c9aa in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #8 0x00007fe40c46166d in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #9 0x00007fe40c4640b3 in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #10 0x00007fe40c45ccd1 in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #11 0x00007fe40c45c92e in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #12 0x00007fe40c45d7bb in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #13 0x00007fe40c45d8c2 in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #14 0x00007fe40c459528 in lua_load () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #15 0x00007fe40c469d8c in luaL_loadbuffer () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #16 0x00007fe40c6fe7d7 in lua_sr_init_probe () at app_lua_api.c:228 >>>>> #17 0x00007fe40c68a97d in child_init (rank=-127) at app_lua_mod.c:197 >>>>> #18 0x0000000000549944 in init_mod_child (m=0x7fe410c3b998, >>>>> rank=-127) >>>>> at core/sr_module.c:938 >>>>> #19 0x0000000000549662 in init_mod_child (m=0x7fe410c3bec0, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #20 0x0000000000549662 in init_mod_child (m=0x7fe410c3c708, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #21 0x0000000000549662 in init_mod_child (m=0x7fe410c3cd78, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #22 0x0000000000549662 in init_mod_child (m=0x7fe410c3d360, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #23 0x0000000000549662 in init_mod_child (m=0x7fe410c3e1e8, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #24 0x0000000000549662 in init_mod_child (m=0x7fe410c3e938, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #25 0x0000000000549662 in init_mod_child (m=0x7fe410c3f4c8, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #26 0x0000000000549662 in init_mod_child (m=0x7fe410c3fca0, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #27 0x0000000000549662 in init_mod_child (m=0x7fe410c40118, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #28 0x0000000000549662 in init_mod_child (m=0x7fe410c40780, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #29 0x0000000000549662 in init_mod_child (m=0x7fe410c422f8, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #30 0x0000000000549662 in init_mod_child (m=0x7fe410c42968, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #31 0x0000000000549662 in init_mod_child (m=0x7fe410c42e50, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #32 0x0000000000549662 in init_mod_child (m=0x7fe410c43b48, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #33 0x0000000000549662 in init_mod_child (m=0x7fe410c43f20, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #34 0x0000000000549662 in init_mod_child (m=0x7fe410c446e0, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #35 0x0000000000549662 in init_mod_child (m=0x7fe410c44bd0, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #36 0x0000000000549662 in init_mod_child (m=0x7fe410c44ec8, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #37 0x0000000000549662 in init_mod_child (m=0x7fe410c45378, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #38 0x0000000000549662 in init_mod_child (m=0x7fe410c458f0, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #39 0x0000000000549662 in init_mod_child (m=0x7fe410c45e48, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #40 0x0000000000549662 in init_mod_child (m=0x7fe410c464e8, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #41 0x0000000000549662 in init_mod_child (m=0x7fe410c47278, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #42 0x0000000000549662 in init_mod_child (m=0x7fe410c476f0, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #43 0x0000000000549662 in init_mod_child (m=0x7fe410c47b68, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #44 0x0000000000549c72 in init_child (rank=-127) at >>>>> core/sr_module.c:964 >>>>> #45 0x0000000000422c1c in main_loop () at main.c:1576 >>>>> #46 0x000000000042aab9 in main (argc=3, argv=0x7ffe17f0e788) at >>>>> main.c:2646 >>>>> >>>>> >>>>> Jan >>>>> >>>>> Daniel-Constantin Mierla schreef op 2018-01-09 22:21: >>>>>> Can you install the debug symbols for kamailio as well? There >>>>>> should be >>>>>> a kamailio-dbg package or so ... >>>>>> >>>>>> Then take again the backtrace, it should provide more information -- >>>>>> file and line for each frame, ... >>>>>> >>>>>> Cheers, >>>>>> Daniel >>>>>> >>>>>> >>>>>> On 09.01.18 21:21, jenus(a)cyberchaos.nl wrote: >>>>>>> Daniel, >>>>>>> >>>>>>> Just upgraded to 5.1 but kamailio now generates a core file. I'm >>>>>>> running debian 8.10. It seems to crash on liblua5.1.so.0 : >>>>>>> >>>>>>> Using host libthread_db library >>>>>>> "/lib/x86_64-linux-gnu/libthread_db.so.1". >>>>>>> Core was generated by `kamailio -m 1500'. >>>>>>> Program terminated with signal SIGSEGV, Segmentation fault. >>>>>>> #0 0x00007f30c17f25a0 in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> (gdb) backtrace >>>>>>> #0 0x00007f30c17f25a0 in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #1 0x00007f30c17f3b62 in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #2 0x00007f30c17e6040 in lua_settable () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #3 0x00007f30c17f6412 in luaL_findtable () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #4 0x00007f30c17f6581 in luaL_openlib () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #5 0x00007f30c1a40870 in lua_sr_kemi_register_libs () from >>>>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>>>> #6 0x00007f30c1a8b107 in lua_sr_openlibs () from >>>>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>>>> #7 0x00007f30c1a8b7c1 in lua_sr_init_probe () from >>>>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>>>> #8 0x00007f30c1a1797d in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>>>> #9 0x0000000000549944 in ?? () >>>>>>> #10 0x0000000000549c72 in init_child () >>>>>>> #11 0x0000000000421498 in main_loop () >>>>>>> #12 0x000000000042aab9 in main () >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> Jan >>>>>>> >>>>>>> jenus(a)cyberchaos.nl schreef op 2018-01-09 20:53: >>>>>>>> Daniel, >>>>>>>> >>>>>>>> Currently running kamailio 5.0.5. >>>>>>>> >>>>>>>> Jan >>>>>>>> >>>>>>>> Daniel-Constantin Mierla schreef op 2018-01-09 13:27: >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>> what version of kamailio are you using? >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> Daniel >>>>>>>>> >>>>>>>>> >>>>>>>>> On 07.01.18 22:14, jenus(a)cyberchaos.nl wrote: >>>>>>>>>> Hello, >>>>>>>>>> >>>>>>>>>> I'm doing some tests with a lua script and app_lua. I'm using >>>>>>>>>> sr.sqlops.query to insert records into the database but would >>>>>>>>>> like to >>>>>>>>>> test the exit status of the sql query. In kamailio i can do: >>>>>>>>>> >>>>>>>>>> if(!sql_query("kamailio", "INSERT INTO subscriber ...")) >>>>>>>>>> >>>>>>>>>> Is there some kind of exit status for the lua function >>>>>>>>>> sr.sqlops.query >>>>>>>>>> in order to do the same check in lua? In other words, is it >>>>>>>>>> possible >>>>>>>>>> to check if a sql query was successful in lua? The result seems >>>>>>>>>> to be >>>>>>>>>> nill in all cases for a INSERT in lua using sr.sqlops.query. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> >>>>>>>>>> Jan Hazenberg >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Kamailio (SER) - Users Mailing List >>>>>>>>>> sr-users(a)lists.kamailio.org >>>>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Kamailio (SER) - Users Mailing List >>>>>>>> sr-users(a)lists.kamailio.org >>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>>>>> >>>>> >>> > -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

2 1

Re: [SR-Users] app_lua sr.sqlops.query exit status
by Daniel-Constantin Mierla 10 Jan '18

10 Jan '18

Few more things to grab from core file with gdb -- take the output for the next commands: frame 16 list info locals Cheers, Daniel On 10.01.18 11:08, jenus(a)cyberchaos.nl wrote: > Daniel, > > Here are the app_lua settings: > > # ----- app_lua params ----- > modparam("app_lua", "load", "/etc/kamailio/kamailio_functions.lua") > modparam("app_lua", "register", "sqlops") > modparam("app_lua", "register", "siputils") > modparam("app_lua", "register", "xhttp") > > > Jan > > > Daniel-Constantin Mierla schreef op 2018-01-10 11:03: >> Can you give here the parameters you set for app_lua module? >> >> Cheers, >> Daniel >> >> >> On 09.01.18 22:27, jenus(a)cyberchaos.nl wrote: >>> Daniel, >>> >>> Here is the backtrace. >>> >>> (gdb) backtrace >>> #0 0x00007fe41140e067 in __GI_raise (sig=sig@entry=6) at >>> ../nptl/sysdeps/unix/sysv/linux/raise.c:56 >>> #1 0x00007fe41140f448 in __GI_abort () at abort.c:89 >>> #2 0x00007fe41144c1b4 in __libc_message (do_abort=do_abort@entry=1, >>> fmt=fmt@entry=0x7fe411541210 "*** Error in `%s': %s: 0x%s ***\n") at >>> ../sysdeps/posix/libc_fatal.c:175 >>> #3 0x00007fe41145198e in malloc_printerr (action=1, >>> str=0x7fe41153d42a "realloc(): invalid next size", ptr=<optimized >>> out>) at malloc.c:4996 >>> #4 0x00007fe41145476b in _int_realloc (av=av@entry=0x7fe41177e620 >>> <main_arena>, oldp=oldp@entry=0x21789c0, oldsize=oldsize@entry=736, >>> nb=nb@entry=1552) at malloc.c:4234 >>> #5 0x00007fe411455769 in __GI___libc_realloc (oldmem=0x21789d0, >>> bytes=1536) at malloc.c:3029 >>> #6 0x00007fe40c460cae in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #7 0x00007fe40c45c9aa in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #8 0x00007fe40c46166d in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #9 0x00007fe40c4640b3 in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #10 0x00007fe40c45ccd1 in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #11 0x00007fe40c45c92e in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #12 0x00007fe40c45d7bb in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #13 0x00007fe40c45d8c2 in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #14 0x00007fe40c459528 in lua_load () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #15 0x00007fe40c469d8c in luaL_loadbuffer () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #16 0x00007fe40c6fe7d7 in lua_sr_init_probe () at app_lua_api.c:228 >>> #17 0x00007fe40c68a97d in child_init (rank=-127) at app_lua_mod.c:197 >>> #18 0x0000000000549944 in init_mod_child (m=0x7fe410c3b998, rank=-127) >>> at core/sr_module.c:938 >>> #19 0x0000000000549662 in init_mod_child (m=0x7fe410c3bec0, rank=-127) >>> at core/sr_module.c:935 >>> #20 0x0000000000549662 in init_mod_child (m=0x7fe410c3c708, rank=-127) >>> at core/sr_module.c:935 >>> #21 0x0000000000549662 in init_mod_child (m=0x7fe410c3cd78, rank=-127) >>> at core/sr_module.c:935 >>> #22 0x0000000000549662 in init_mod_child (m=0x7fe410c3d360, rank=-127) >>> at core/sr_module.c:935 >>> #23 0x0000000000549662 in init_mod_child (m=0x7fe410c3e1e8, rank=-127) >>> at core/sr_module.c:935 >>> #24 0x0000000000549662 in init_mod_child (m=0x7fe410c3e938, rank=-127) >>> at core/sr_module.c:935 >>> #25 0x0000000000549662 in init_mod_child (m=0x7fe410c3f4c8, rank=-127) >>> at core/sr_module.c:935 >>> #26 0x0000000000549662 in init_mod_child (m=0x7fe410c3fca0, rank=-127) >>> at core/sr_module.c:935 >>> #27 0x0000000000549662 in init_mod_child (m=0x7fe410c40118, rank=-127) >>> at core/sr_module.c:935 >>> #28 0x0000000000549662 in init_mod_child (m=0x7fe410c40780, rank=-127) >>> at core/sr_module.c:935 >>> #29 0x0000000000549662 in init_mod_child (m=0x7fe410c422f8, rank=-127) >>> at core/sr_module.c:935 >>> #30 0x0000000000549662 in init_mod_child (m=0x7fe410c42968, rank=-127) >>> at core/sr_module.c:935 >>> #31 0x0000000000549662 in init_mod_child (m=0x7fe410c42e50, rank=-127) >>> at core/sr_module.c:935 >>> #32 0x0000000000549662 in init_mod_child (m=0x7fe410c43b48, rank=-127) >>> at core/sr_module.c:935 >>> #33 0x0000000000549662 in init_mod_child (m=0x7fe410c43f20, rank=-127) >>> at core/sr_module.c:935 >>> #34 0x0000000000549662 in init_mod_child (m=0x7fe410c446e0, rank=-127) >>> at core/sr_module.c:935 >>> #35 0x0000000000549662 in init_mod_child (m=0x7fe410c44bd0, rank=-127) >>> at core/sr_module.c:935 >>> #36 0x0000000000549662 in init_mod_child (m=0x7fe410c44ec8, rank=-127) >>> at core/sr_module.c:935 >>> #37 0x0000000000549662 in init_mod_child (m=0x7fe410c45378, rank=-127) >>> at core/sr_module.c:935 >>> #38 0x0000000000549662 in init_mod_child (m=0x7fe410c458f0, rank=-127) >>> at core/sr_module.c:935 >>> #39 0x0000000000549662 in init_mod_child (m=0x7fe410c45e48, rank=-127) >>> at core/sr_module.c:935 >>> #40 0x0000000000549662 in init_mod_child (m=0x7fe410c464e8, rank=-127) >>> at core/sr_module.c:935 >>> #41 0x0000000000549662 in init_mod_child (m=0x7fe410c47278, rank=-127) >>> at core/sr_module.c:935 >>> #42 0x0000000000549662 in init_mod_child (m=0x7fe410c476f0, rank=-127) >>> at core/sr_module.c:935 >>> #43 0x0000000000549662 in init_mod_child (m=0x7fe410c47b68, rank=-127) >>> at core/sr_module.c:935 >>> #44 0x0000000000549c72 in init_child (rank=-127) at >>> core/sr_module.c:964 >>> #45 0x0000000000422c1c in main_loop () at main.c:1576 >>> #46 0x000000000042aab9 in main (argc=3, argv=0x7ffe17f0e788) at >>> main.c:2646 >>> >>> >>> Jan >>> >>> Daniel-Constantin Mierla schreef op 2018-01-09 22:21: >>>> Can you install the debug symbols for kamailio as well? There >>>> should be >>>> a kamailio-dbg package or so ... >>>> >>>> Then take again the backtrace, it should provide more information -- >>>> file and line for each frame, ... >>>> >>>> Cheers, >>>> Daniel >>>> >>>> >>>> On 09.01.18 21:21, jenus(a)cyberchaos.nl wrote: >>>>> Daniel, >>>>> >>>>> Just upgraded to 5.1 but kamailio now generates a core file. I'm >>>>> running debian 8.10. It seems to crash on liblua5.1.so.0 : >>>>> >>>>> Using host libthread_db library >>>>> "/lib/x86_64-linux-gnu/libthread_db.so.1". >>>>> Core was generated by `kamailio -m 1500'. >>>>> Program terminated with signal SIGSEGV, Segmentation fault. >>>>> #0 0x00007f30c17f25a0 in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> (gdb) backtrace >>>>> #0 0x00007f30c17f25a0 in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #1 0x00007f30c17f3b62 in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #2 0x00007f30c17e6040 in lua_settable () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #3 0x00007f30c17f6412 in luaL_findtable () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #4 0x00007f30c17f6581 in luaL_openlib () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #5 0x00007f30c1a40870 in lua_sr_kemi_register_libs () from >>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>> #6 0x00007f30c1a8b107 in lua_sr_openlibs () from >>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>> #7 0x00007f30c1a8b7c1 in lua_sr_init_probe () from >>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>> #8 0x00007f30c1a1797d in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>> #9 0x0000000000549944 in ?? () >>>>> #10 0x0000000000549c72 in init_child () >>>>> #11 0x0000000000421498 in main_loop () >>>>> #12 0x000000000042aab9 in main () >>>>> >>>>> >>>>> >>>>> Thanks, >>>>> >>>>> Jan >>>>> >>>>> jenus(a)cyberchaos.nl schreef op 2018-01-09 20:53: >>>>>> Daniel, >>>>>> >>>>>> Currently running kamailio 5.0.5. >>>>>> >>>>>> Jan >>>>>> >>>>>> Daniel-Constantin Mierla schreef op 2018-01-09 13:27: >>>>>>> Hello, >>>>>>> >>>>>>> what version of kamailio are you using? >>>>>>> >>>>>>> Cheers, >>>>>>> Daniel >>>>>>> >>>>>>> >>>>>>> On 07.01.18 22:14, jenus(a)cyberchaos.nl wrote: >>>>>>>> Hello, >>>>>>>> >>>>>>>> I'm doing some tests with a lua script and app_lua. I'm using >>>>>>>> sr.sqlops.query to insert records into the database but would >>>>>>>> like to >>>>>>>> test the exit status of the sql query. In kamailio i can do: >>>>>>>> >>>>>>>> if(!sql_query("kamailio", "INSERT INTO subscriber ...")) >>>>>>>> >>>>>>>> Is there some kind of exit status for the lua function >>>>>>>> sr.sqlops.query >>>>>>>> in order to do the same check in lua? In other words, is it >>>>>>>> possible >>>>>>>> to check if a sql query was successful in lua? The result seems >>>>>>>> to be >>>>>>>> nill in all cases for a INSERT in lua using sr.sqlops.query. >>>>>>>> >>>>>>>> >>>>>>>> Thanks, >>>>>>>> >>>>>>>> Jan Hazenberg >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Kamailio (SER) - Users Mailing List >>>>>>>> sr-users(a)lists.kamailio.org >>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Kamailio (SER) - Users Mailing List >>>>>> sr-users(a)lists.kamailio.org >>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>>> >>> > -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

2 1

Re: [SR-Users] app_lua sr.sqlops.query exit status
by Daniel-Constantin Mierla 10 Jan '18

10 Jan '18

Can you give here the parameters you set for app_lua module? Cheers, Daniel On 09.01.18 22:27, jenus(a)cyberchaos.nl wrote: > Daniel, > > Here is the backtrace. > > (gdb) backtrace > #0 0x00007fe41140e067 in __GI_raise (sig=sig@entry=6) at > ../nptl/sysdeps/unix/sysv/linux/raise.c:56 > #1 0x00007fe41140f448 in __GI_abort () at abort.c:89 > #2 0x00007fe41144c1b4 in __libc_message (do_abort=do_abort@entry=1, > fmt=fmt@entry=0x7fe411541210 "*** Error in `%s': %s: 0x%s ***\n") at > ../sysdeps/posix/libc_fatal.c:175 > #3 0x00007fe41145198e in malloc_printerr (action=1, > str=0x7fe41153d42a "realloc(): invalid next size", ptr=<optimized > out>) at malloc.c:4996 > #4 0x00007fe41145476b in _int_realloc (av=av@entry=0x7fe41177e620 > <main_arena>, oldp=oldp@entry=0x21789c0, oldsize=oldsize@entry=736, > nb=nb@entry=1552) at malloc.c:4234 > #5 0x00007fe411455769 in __GI___libc_realloc (oldmem=0x21789d0, > bytes=1536) at malloc.c:3029 > #6 0x00007fe40c460cae in ?? () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #7 0x00007fe40c45c9aa in ?? () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #8 0x00007fe40c46166d in ?? () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #9 0x00007fe40c4640b3 in ?? () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #10 0x00007fe40c45ccd1 in ?? () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #11 0x00007fe40c45c92e in ?? () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #12 0x00007fe40c45d7bb in ?? () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #13 0x00007fe40c45d8c2 in ?? () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #14 0x00007fe40c459528 in lua_load () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #15 0x00007fe40c469d8c in luaL_loadbuffer () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #16 0x00007fe40c6fe7d7 in lua_sr_init_probe () at app_lua_api.c:228 > #17 0x00007fe40c68a97d in child_init (rank=-127) at app_lua_mod.c:197 > #18 0x0000000000549944 in init_mod_child (m=0x7fe410c3b998, rank=-127) > at core/sr_module.c:938 > #19 0x0000000000549662 in init_mod_child (m=0x7fe410c3bec0, rank=-127) > at core/sr_module.c:935 > #20 0x0000000000549662 in init_mod_child (m=0x7fe410c3c708, rank=-127) > at core/sr_module.c:935 > #21 0x0000000000549662 in init_mod_child (m=0x7fe410c3cd78, rank=-127) > at core/sr_module.c:935 > #22 0x0000000000549662 in init_mod_child (m=0x7fe410c3d360, rank=-127) > at core/sr_module.c:935 > #23 0x0000000000549662 in init_mod_child (m=0x7fe410c3e1e8, rank=-127) > at core/sr_module.c:935 > #24 0x0000000000549662 in init_mod_child (m=0x7fe410c3e938, rank=-127) > at core/sr_module.c:935 > #25 0x0000000000549662 in init_mod_child (m=0x7fe410c3f4c8, rank=-127) > at core/sr_module.c:935 > #26 0x0000000000549662 in init_mod_child (m=0x7fe410c3fca0, rank=-127) > at core/sr_module.c:935 > #27 0x0000000000549662 in init_mod_child (m=0x7fe410c40118, rank=-127) > at core/sr_module.c:935 > #28 0x0000000000549662 in init_mod_child (m=0x7fe410c40780, rank=-127) > at core/sr_module.c:935 > #29 0x0000000000549662 in init_mod_child (m=0x7fe410c422f8, rank=-127) > at core/sr_module.c:935 > #30 0x0000000000549662 in init_mod_child (m=0x7fe410c42968, rank=-127) > at core/sr_module.c:935 > #31 0x0000000000549662 in init_mod_child (m=0x7fe410c42e50, rank=-127) > at core/sr_module.c:935 > #32 0x0000000000549662 in init_mod_child (m=0x7fe410c43b48, rank=-127) > at core/sr_module.c:935 > #33 0x0000000000549662 in init_mod_child (m=0x7fe410c43f20, rank=-127) > at core/sr_module.c:935 > #34 0x0000000000549662 in init_mod_child (m=0x7fe410c446e0, rank=-127) > at core/sr_module.c:935 > #35 0x0000000000549662 in init_mod_child (m=0x7fe410c44bd0, rank=-127) > at core/sr_module.c:935 > #36 0x0000000000549662 in init_mod_child (m=0x7fe410c44ec8, rank=-127) > at core/sr_module.c:935 > #37 0x0000000000549662 in init_mod_child (m=0x7fe410c45378, rank=-127) > at core/sr_module.c:935 > #38 0x0000000000549662 in init_mod_child (m=0x7fe410c458f0, rank=-127) > at core/sr_module.c:935 > #39 0x0000000000549662 in init_mod_child (m=0x7fe410c45e48, rank=-127) > at core/sr_module.c:935 > #40 0x0000000000549662 in init_mod_child (m=0x7fe410c464e8, rank=-127) > at core/sr_module.c:935 > #41 0x0000000000549662 in init_mod_child (m=0x7fe410c47278, rank=-127) > at core/sr_module.c:935 > #42 0x0000000000549662 in init_mod_child (m=0x7fe410c476f0, rank=-127) > at core/sr_module.c:935 > #43 0x0000000000549662 in init_mod_child (m=0x7fe410c47b68, rank=-127) > at core/sr_module.c:935 > #44 0x0000000000549c72 in init_child (rank=-127) at core/sr_module.c:964 > #45 0x0000000000422c1c in main_loop () at main.c:1576 > #46 0x000000000042aab9 in main (argc=3, argv=0x7ffe17f0e788) at > main.c:2646 > > > Jan > > Daniel-Constantin Mierla schreef op 2018-01-09 22:21: >> Can you install the debug symbols for kamailio as well? There should be >> a kamailio-dbg package or so ... >> >> Then take again the backtrace, it should provide more information -- >> file and line for each frame, ... >> >> Cheers, >> Daniel >> >> >> On 09.01.18 21:21, jenus(a)cyberchaos.nl wrote: >>> Daniel, >>> >>> Just upgraded to 5.1 but kamailio now generates a core file. I'm >>> running debian 8.10. It seems to crash on liblua5.1.so.0 : >>> >>> Using host libthread_db library >>> "/lib/x86_64-linux-gnu/libthread_db.so.1". >>> Core was generated by `kamailio -m 1500'. >>> Program terminated with signal SIGSEGV, Segmentation fault. >>> #0 0x00007f30c17f25a0 in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> (gdb) backtrace >>> #0 0x00007f30c17f25a0 in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #1 0x00007f30c17f3b62 in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #2 0x00007f30c17e6040 in lua_settable () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #3 0x00007f30c17f6412 in luaL_findtable () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #4 0x00007f30c17f6581 in luaL_openlib () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #5 0x00007f30c1a40870 in lua_sr_kemi_register_libs () from >>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>> #6 0x00007f30c1a8b107 in lua_sr_openlibs () from >>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>> #7 0x00007f30c1a8b7c1 in lua_sr_init_probe () from >>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>> #8 0x00007f30c1a1797d in ?? () from >>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>> #9 0x0000000000549944 in ?? () >>> #10 0x0000000000549c72 in init_child () >>> #11 0x0000000000421498 in main_loop () >>> #12 0x000000000042aab9 in main () >>> >>> >>> >>> Thanks, >>> >>> Jan >>> >>> jenus(a)cyberchaos.nl schreef op 2018-01-09 20:53: >>>> Daniel, >>>> >>>> Currently running kamailio 5.0.5. >>>> >>>> Jan >>>> >>>> Daniel-Constantin Mierla schreef op 2018-01-09 13:27: >>>>> Hello, >>>>> >>>>> what version of kamailio are you using? >>>>> >>>>> Cheers, >>>>> Daniel >>>>> >>>>> >>>>> On 07.01.18 22:14, jenus(a)cyberchaos.nl wrote: >>>>>> Hello, >>>>>> >>>>>> I'm doing some tests with a lua script and app_lua. I'm using >>>>>> sr.sqlops.query to insert records into the database but would >>>>>> like to >>>>>> test the exit status of the sql query. In kamailio i can do: >>>>>> >>>>>> if(!sql_query("kamailio", "INSERT INTO subscriber ...")) >>>>>> >>>>>> Is there some kind of exit status for the lua function >>>>>> sr.sqlops.query >>>>>> in order to do the same check in lua? In other words, is it possible >>>>>> to check if a sql query was successful in lua? The result seems >>>>>> to be >>>>>> nill in all cases for a INSERT in lua using sr.sqlops.query. >>>>>> >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Jan Hazenberg >>>>>> >>>>>> _______________________________________________ >>>>>> Kamailio (SER) - Users Mailing List >>>>>> sr-users(a)lists.kamailio.org >>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>> >>>> >>>> _______________________________________________ >>>> Kamailio (SER) - Users Mailing List >>>> sr-users(a)lists.kamailio.org >>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> > -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

2 1

Re: [SR-Users] app_lua sr.sqlops.query exit status
by Daniel-Constantin Mierla 09 Jan '18

09 Jan '18

Can you install the debug symbols for kamailio as well? There should be a kamailio-dbg package or so ... Then take again the backtrace, it should provide more information -- file and line for each frame, ... Cheers, Daniel On 09.01.18 21:21, jenus(a)cyberchaos.nl wrote: > Daniel, > > Just upgraded to 5.1 but kamailio now generates a core file. I'm > running debian 8.10. It seems to crash on liblua5.1.so.0 : > > Using host libthread_db library > "/lib/x86_64-linux-gnu/libthread_db.so.1". > Core was generated by `kamailio -m 1500'. > Program terminated with signal SIGSEGV, Segmentation fault. > #0 0x00007f30c17f25a0 in ?? () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > (gdb) backtrace > #0 0x00007f30c17f25a0 in ?? () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #1 0x00007f30c17f3b62 in ?? () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #2 0x00007f30c17e6040 in lua_settable () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #3 0x00007f30c17f6412 in luaL_findtable () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #4 0x00007f30c17f6581 in luaL_openlib () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #5 0x00007f30c1a40870 in lua_sr_kemi_register_libs () from > /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so > #6 0x00007f30c1a8b107 in lua_sr_openlibs () from > /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so > #7 0x00007f30c1a8b7c1 in lua_sr_init_probe () from > /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so > #8 0x00007f30c1a1797d in ?? () from > /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so > #9 0x0000000000549944 in ?? () > #10 0x0000000000549c72 in init_child () > #11 0x0000000000421498 in main_loop () > #12 0x000000000042aab9 in main () > > > > Thanks, > > Jan > > jenus(a)cyberchaos.nl schreef op 2018-01-09 20:53: >> Daniel, >> >> Currently running kamailio 5.0.5. >> >> Jan >> >> Daniel-Constantin Mierla schreef op 2018-01-09 13:27: >>> Hello, >>> >>> what version of kamailio are you using? >>> >>> Cheers, >>> Daniel >>> >>> >>> On 07.01.18 22:14, jenus(a)cyberchaos.nl wrote: >>>> Hello, >>>> >>>> I'm doing some tests with a lua script and app_lua. I'm using >>>> sr.sqlops.query to insert records into the database but would like to >>>> test the exit status of the sql query. In kamailio i can do: >>>> >>>> if(!sql_query("kamailio", "INSERT INTO subscriber ...")) >>>> >>>> Is there some kind of exit status for the lua function sr.sqlops.query >>>> in order to do the same check in lua? In other words, is it possible >>>> to check if a sql query was successful in lua? The result seems to be >>>> nill in all cases for a INSERT in lua using sr.sqlops.query. >>>> >>>> >>>> Thanks, >>>> >>>> Jan Hazenberg >>>> >>>> _______________________________________________ >>>> Kamailio (SER) - Users Mailing List >>>> sr-users(a)lists.kamailio.org >>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> >> >> _______________________________________________ >> Kamailio (SER) - Users Mailing List >> sr-users(a)lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

2 1

Re: [SR-Users] app_lua sr.sqlops.query exit status
by Daniel-Constantin Mierla 09 Jan '18

09 Jan '18

Hello, I needed to know in order to suggest use of "KSR" package or not, instead of "sr". The "sr" package likely to be obsoleted soon, as KSR has lot more exported functions and it is part of the kemi framework. See: http://kamailio.org/docs/tutorials/devel/kamailio-kemi-framework/ http://kamailio.org/docs/tutorials/devel/kamailio-kemi-framework/modules/#s… However, 5.0 doesn't have so many KSR exports as 5.1, and not sure if KSR has the sqlops exports in that version -- too late to check more in the code now... Looking at the code, sr.sqlops.query() should return -1 in case of error and 0 if ok. Cheers, Daniel On 09.01.18 20:53, jenus(a)cyberchaos.nl wrote: > Daniel, > > Currently running kamailio 5.0.5. > > Jan > > Daniel-Constantin Mierla schreef op 2018-01-09 13:27: >> Hello, >> >> what version of kamailio are you using? >> >> Cheers, >> Daniel >> >> >> On 07.01.18 22:14, jenus(a)cyberchaos.nl wrote: >>> Hello, >>> >>> I'm doing some tests with a lua script and app_lua. I'm using >>> sr.sqlops.query to insert records into the database but would like to >>> test the exit status of the sql query. In kamailio i can do: >>> >>> if(!sql_query("kamailio", "INSERT INTO subscriber ...")) >>> >>> Is there some kind of exit status for the lua function sr.sqlops.query >>> in order to do the same check in lua? In other words, is it possible >>> to check if a sql query was successful in lua? The result seems to be >>> nill in all cases for a INSERT in lua using sr.sqlops.query. >>> >>> >>> Thanks, >>> >>> Jan Hazenberg >>> >>> _______________________________________________ >>> Kamailio (SER) - Users Mailing List >>> sr-users(a)lists.kamailio.org >>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

1 0

app_lua sr.sqlops.query exit status
by jenus＠cyberchaos.nl 09 Jan '18

09 Jan '18

Hello, I'm doing some tests with a lua script and app_lua. I'm using sr.sqlops.query to insert records into the database but would like to test the exit status of the sql query. In kamailio i can do: if(!sql_query("kamailio", "INSERT INTO subscriber ...")) Is there some kind of exit status for the lua function sr.sqlops.query in order to do the same check in lua? In other words, is it possible to check if a sql query was successful in lua? The result seems to be nill in all cases for a INSERT in lua using sr.sqlops.query. Thanks, Jan Hazenberg

2 4

t_relay dying ?
by Jean Cérien 09 Jan '18

09 Jan '18

Hello I am using kamailio 5.0.2, on a debian 9 system. Everything was running fine, until one of our voip provider changed his switch. Our kamailio is relaying between several voip providers and several asterisk (only the signalisation, no rtp). When we get an invite from this new switch, we select an asterisk and relay it correctly to this box. However, the OK is relayed back. But when the voip providers sends an ACK for this OK, the t_relay function does not return at all, it just dies with no action and no error. Here is the snippet from route(relay) xlog("L_INFO","route(relay) @@ $rm - Source: $si:$sp, fu:$fu, tu:$tu\n" ); $var(restrelay)=t_relay(); xlog("L_INFO","route(relay) @@ $rm - t_relay result: $var(restrelay)" ); if (!$var(restrelay)) { When processing the initial invite, I do get both INFO messages. When the ACK is processed, I only get one INFO message, and no ACK is relayed - so it seems execution dies in the t_relay What could be wrong ??? J. Details of the ACK: ACK sip:dialednumber@kamailioIP:5060 SIP/2.0 Via: SIP/2.0/UDP VOIPPROVIDERIP:5060;branch=z9hG4bKjq16fi00d85uee181ic0.1 To: <sip:kamailioIP:5060>;tag=as7f10ed48 From: <sip:sourcenumber@orange-multimedia.fr >;tag=SD8u3ob01-7dd8efde-0002-00d5-0000-0000 Call-ID: SD8u3ob01-688d41f5e2164ceeafe76f40b82b3f97-v300g00030 CSeq: 1 ACK Max-Forwards: 66 Content-Length: 0 Route: <sip:kamailioIP;lr=on;ftag=SD8u3ob01-7dd8efde-0002-00d5-0000-0000;did=a0b.49d> (should you have enough width; the diagram will look ok) VOIP PROVIDER KAMAILIO ASTERISK 21:38:54.685149 │ ──────────────────────────> │ │ ▒ +0.000451 │ 100 trying -- your call is │ │ ▒ 21:38:54.685600 │ <────────────────────────── │ │ ▒ +0.000084 │ │ INVITE (SDP) │ ▒ 21:38:54.685684 │ │ ──────────────────────────> │ ▒ +0.000831 │ │ 100 Trying │ ▒ 21:38:54.686515 │ │ <────────────────────────── │ ▒ +0.000471 │ │ 200 OK (SDP) │ ▒ 21:38:54.686986 │ │ <────────────────────────── │ ▒ +0.000394 │ 200 OK (SDP) │ │ ▒ 21:38:54.687380 │ <────────────────────────── │ │ ▒ +0.038694 │ ACK │ │ ▒ 21:38:54.726074 │ ──────────────────────────> │ │ ▒ +0.060155 │ │ 200 OK (SDP) │ ▒ 21:38:54.786229 │ │ <<<──────────────────────── │ ▒ +0.000138 │ 200 OK (SDP) │ │ ▒ 21:38:54.786367 │ <<<──────────────────────── │ │ ▒ +0.005721 │ ACK │ │

10 25

WebRTC proxy for legacy systems
by paul＠kristianpaul.org 09 Jan '18

09 Jan '18

Hi, I'm looking to use kamailio as a webrtc proxy for legacy sip system that doesnt have this capability, is there a example or blueprint i can follow to get started with this? I'm RTFMing the docs but still need a while to understand kamailio internals :-)

3 4

Kamailio fail to start with db_mongodb and ndb_mongodb modules
by Abdul Basit 09 Jan '18

09 Jan '18

Hi Daniel & K-Team, I setup kamailio 5.0.5 from git on vanilla Debian GNU/Linux 8.3 (jessie) # kamailio -v version: kamailio 5.0.5 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled on 16:53:42 Jan 5 2018 with gcc 4.9.2 Installed mongodb from debian repo # dpkg -l | grep mongodb ii mongodb 1:3.2.17-1 amd64 object/document-oriented database (metapackage) ii mongodb-clients 1:3.2.17-1 amd64 object/document-oriented database (client apps) ii mongodb-dev 1:2.4.10-5+deb8u1 amd64 object/document-oriented database (development) ii mongodb-server 1:3.2.17-1 amd64 object/document-oriented database (server package) # mongo --version MongoDB shell version: 3.2.17 Will try sometime with mongodb latest version 3.6 as well as I will get time. Installed libmongoc driver through sid repo "deb http://ftp.de.debian.org/debian sid main" # dpkg -l | grep libmongoc ii libmongoc-1.0-0 1.9.0+dfsg-1 amd64 MongoDB C client library - runtime files ii libmongoc-dev 1.9.0+dfsg-1 amd64 MongoDB C client library - dev files Kamailio compiled with # make cfg include_modules="utils app_lua json evapi db_mongodb ndb_mongodb" Created version collection in mongodb # cat /usr/local/src/kamailio/utils/kamctl/mongodb/kamailio/version-create.mongo | mongo Setup kamailio.cfg as per https://telerain.com/kamailio This time kamailio started successfully without any crash :) --------- Now its time to use mongodb for kamailio backend database. Used default kamailio configuration and defined mongodb connection as #!define DBURL "mongodb://localhost/kamailio" I enabled WITH_USRLOCDB [#!define WITH_USRLOCDB], kamailio refuse to start with errors. Jan 5 19:16:05 kmaongo kamailio: CRITICAL: <core> [core/cfg.y:3411]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 365, column 30-34: syntax error Jan 5 19:16:05 kmaongo kamailio: CRITICAL: <core> [core/cfg.y:3411]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 365, column 30-34: Invalid arguments Jan 5 19:16:05 kmaongo kamailio: CRITICAL: <core> [core/cfg.y:3414]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 365, column 35: Jan 5 19:16:05 kmaongo kamailio[28067]: ERROR: bad config file (3 errors) Jan 5 19:16:05 kmaongo kamailio: WARNING: <core> [core/ppcfg.c:221]: pp_ifdef_level_check(): different number of preprocessor directives: N(#!IF[N]DEF) - N(#!ENDIF) = 1 Jan 5 19:16:05 kmaongo kamailio: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Jan 5 19:16:05 kmaongo systemd[1]: kamailio.service: control process exited, code=exited status=255 [FAILJan 5 19:16:05 kmaongo systemd[1]: Failed to start Kamailio (OpenSER) - the Open Source SIP Server. Jan 5 19:16:05 kmaongo systemd[1]: Unit kamailio.service entered failed state. failed! Default userloc params in kamailio.cfg states line 365 as # ----- usrloc params ----- /* enable DB persistency for location entries */ #!ifdef WITH_USRLOCDB modparam("usrloc", "db_url", DBURL) [ << line 365 ] modparam("usrloc", "db_mode", 2) modparam("usrloc", "use_domain", MULTIDOMAIN) modparam("usrloc", "db_insert_null", 1) #!endif I created location collection as well but it didn't help. I experienced same error when I enable WITH_ACCDB or any other section that use DBURL. 1. Whats the syntax error here? 2. Is there any special configuration required to work with mongodb? 3. How can we create collections using 'kamdbctl create' ? What else should I share for resolving the issue? -- regards, abdul basit On 4 January 2018 at 12:50, Abdul Basit <basit.engg(a)gmail.com> wrote: > Hi Daniel, > > Thank you for your reply. > > I tested libmongoc with debian package available with repo. Then I moved > to compile from source. result was same. > > But i will try it again with fresh installation and will post here. > > -- > regards, > > abdul basit > > On 2 January 2018 at 16:38, Daniel-Constantin Mierla <miconda(a)gmail.com> > wrote: > >> Hello, >> >> the issue happens inside mongoc library. Have you tried with the default >> one from Debian, without compiling it from sources? >> >> Cheers, >> Daniel >> >> On 01.01.18 16:51, Abdul Basit wrote: >> >> Hi, >> >> My last email was help for admin review. >> >> Sharing logs through pastebin https://pastebin.com/6HhdYLJK >> >> Interesting part will start from line 983 where it start initializing >> ndb_mongodb. >> >> >> >> On 1 January 2018 at 20:32, Abdul Basit <basit.engg(a)gmail.com> wrote: >> >>> Hi, >>> >>> I enabled but kamailio didn't generate any dump file >>> To enable code dump followed https://www.kamailio.org/dokuw >>> iki/doku.php/troubleshooting:corefiles >>> >>> I also un-commented lines in /etc/init.d/kamailio script >>> >>> if test "$DUMP_CORE" = "yes" ; then >>> # set proper ulimit >>> ulimit -c unlimited >>> >>> # directory for the core dump files >>> COREDIR=/tmp/corefiles >>> [ -d $COREDIR ] || mkdir -p $COREDIR >>> chmod 777 $COREDIR >>> echo "$COREDIR/core.%e.sig%s.%p" > /proc/sys/kernel/core_pattern >>> fi >>> >>> >>> I think reason is that kamailio process didn't exit after crash and keep >>> on restarting. each time with new PID. >>> >>> However, debug file is attached. I hope this will help. >>> -- >>> regards, >>> >>> abdul basit >>> >>> On 29 December 2017 at 20:11, M S <shaheryarkh(a)gmail.com> wrote: >>> >>>> Hi, >>>> >>>> Enable core dump and provide backtrace of sigfault. See this for more >>>> info, >>>> >>>> https://sourceware.org/gdb/onlinedocs/gdb/Backtrace.html >>>> >>>> Thank you. >>>> >>>> On Fri, Dec 29, 2017 at 12:25 PM, Abdul Basit <basit.engg(a)gmail.com> >>>> wrote: >>>> >>>>> Adding further from https://stackoverflow.com/ques >>>>> tions/2549214/interpreting-segfault-messages >>>>> >>>>> error 6 means, fault is >>>>> >>>>> * bit 2 == 1 means kernel, 1 means user-mode >>>>> * bit 4 == 1 means fault was an instruction fetch >>>>> >>>>> >>>>> That looks like kamailio is trying to invoke for db connection where >>>>> libmongo-c don't like to be. >>>>> -- >>>>> regards, >>>>> >>>>> abdul basit >>>>> >>>>> On 29 December 2017 at 15:39, Abdul Basit <basit.engg(a)gmail.com> >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I am trying to setup mongo db as database engine for kamailio as >>>>>> described at >>>>>> <http://www.kamailio.org/wiki/tutorials/kamailio-and-mongodb> >>>>>> http://www.kamailio.org/wiki/tutorials/kamailio-and-mongodb >>>>>> and >>>>>> https://telerain.com/kamailio >>>>>> >>>>>> OS: Debian GNU/Linux 8.10 (jessie) >>>>>> MongoDB server version: 3.4.10 >>>>>> mongo-c-driver-1.9.0.tar.gz compiled with >>>>>> ./configure --disable-static --disable-silent-rules >>>>>> --enable-debug-symbols --enable-ssl=no --enable-sasl=yes >>>>>> --with-libbson=bundled --enable-optimizations --disable-automatic-init-and-c >>>>>> leanup >>>>>> >>>>>> version: kamailio 5.0.4 (x86_64/linux) >>>>>> flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, >>>>>> DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, >>>>>> Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, >>>>>> FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, >>>>>> USE_DST_BLACKLIST, HAVE_RESOLV_RES >>>>>> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, >>>>>> MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB >>>>>> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. >>>>>> id: unknown >>>>>> compiled on 20:45:44 Dec 27 2017 with gcc 4.9.2 >>>>>> >>>>>> include_modules= utils app_lua db_postgres json evapi db_mongodb >>>>>> ndb_mongodb >>>>>> >>>>>> Kamailio is crashing with segfault as soon as it try to load >>>>>> libmongo-c >>>>>> >>>>>> Dec 28 04:44:14 sipserver systemd[1]: Starting Kamailio (OpenSER) - >>>>>> the Open Source SIP Server... >>>>>> Dec 28 04:44:14 sipserver kamailio: INFO: <core> >>>>>> [core/sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if >>>>>> you want to use it, load sctp module >>>>>> Dec 28 04:44:14 sipserver kamailio: INFO: <core> >>>>>> [core/tcp_main.c:4671]: init_tcp(): using epoll_lt as the io watch method >>>>>> (auto detected) >>>>>> Dec 28 04:44:14 sipserver kamailio[11685]: Listening on >>>>>> Dec 28 04:44:14 sipserver kamailio[11685]: udp: 127.0.0.1:5060 >>>>>> Dec 28 04:44:14 sipserver kamailio[11685]: udp: 192.168.10.20:5060 >>>>>> Dec 28 04:44:14 sipserver kamailio[11685]: tcp: 127.0.0.1:5060 >>>>>> Dec 28 04:44:14 sipserver kamailio[11685]: tcp: 192.168.10.20:5060 >>>>>> Dec 28 04:44:14 sipserver kamailio[11685]: Aliases: >>>>>> Dec 28 04:44:14 sipserver kamailio[11685]: tcp: localhost:5060 >>>>>> Dec 28 04:44:14 sipserver kamailio[11685]: udp: localhost:5060 >>>>>> Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: INFO: rr >>>>>> [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe >>>>>> module is not loaded >>>>>> ..... >>>>>> Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: INFO: >>>>>> <core> [core/udp_server.c:203]: probe_max_receive_buffer(): SO_RCVBUF is >>>>>> finally 425984 >>>>>> Dec 28 04:44:14 sipserver systemd[1]: Started Kamailio (OpenSER) - >>>>>> the Open Source SIP Server. >>>>>> Dec 28 04:44:14 sipserver kernel: [53109.390171] show_signal_msg: 20 >>>>>> callbacks suppressed >>>>>> Dec 28 04:44:14 sipserver kernel: [53109.390176] kamailio[11696] >>>>>> segfault at 78 ip 00007f690c0e6e98 sp 00007ffcde1a4770 error 6 in >>>>>> libmongoc-1.0.so.0.0.0[7f690c0ca000+6e000] >>>>>> Dec 28 04:44:14 sipserver kernel: [53109.390753] kamailio[11694] >>>>>> segfault at 78 ip 00007f690c0e6e98 sp 00007ffcde1a4770 error 6 in >>>>>> libmongoc-1.0.so.0.0.0[7f690c0ca000+6e000] >>>>>> Dec 28 04:44:14 sipserver kernel: [53109.393147] kamailio[11699] >>>>>> segfault at 38 ip 00007f690c0e6e98 sp 00007ffcde1a4770 error 6 in >>>>>> libmongoc-1.0.so.0.0.0[7f690c0ca000+6e000] >>>>>> Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: >>>>>> <core> [main.c:743]: handle_sigs(): child process 11689 exited by a signal >>>>>> 11 >>>>>> Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: >>>>>> <core> [main.c:746]: handle_sigs(): core was not generated >>>>>> Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: >>>>>> <core> [main.c:743]: handle_sigs(): child process 11688 exited by a signal >>>>>> 11 >>>>>> ....... >>>>>> Dec 28 04:44:14 sipserver systemd[1]: kamailio.service: main process >>>>>> exited, code=exited, status=1/FAILURE >>>>>> Dec 28 04:44:14 sipserver systemd[1]: Unit kamailio.service entered >>>>>> failed state. >>>>>> >>>>>> >>>>>> As I tried googling the issue and found few issues with tls >>>>>> connection. >>>>>> I set in default kamailio.cfg but still facing the saem issue. >>>>>> >>>>>> enable_tls=no >>>>>> ... >>>>>> loadmodule "ndb_mongodb.so" >>>>>> modparam("ndb_mongodb", "server", "name=cgr91rc8;uri='mongodb:// >>>>>> localhost/kamailio'") >>>>>> >>>>>> Its mongodb default installation and its accessible without any auth >>>>>> yet. >>>>>> >>>>>> Please suggest the way farward. >>>>>> >>>>>> -- >>>>>> regards, >>>>>> >>>>>> abdul basit >>>>>> >>>>>

3 3

cdr processing questions
by voipspace voipspace 09 Jan '18

09 Jan '18

A few question; Firstly With mod acc and acc_cdr i see the default fields logged is only start_time, end_time, duration. This is an actual entry logged. start_time, end_time, duration 1515353126, 1515353135, 9.660000 Why is the duration 9.660000? It seems wrong because it is more then the difference in time 1515353135 - 1515353126 = 9 Secondly What is a reliable way to capture and log start time, answer time, and end time. How do I get the duration info. a) start time to end time. b) answer to end time. Is there an built in variable that store this info? Thirdly dialog events listed as: event_route[dialog:start] event_route[dialog:end] event_route[dialog:failed] There does not seems to be a event for answer so then how to be notified when a dialog is answered? Regards

2 1

parsing of SIP message failed
by Suresh Talasaniya 08 Jan '18

08 Jan '18

Hi, *I consistently receive the following 3 errors (see below) over and over when a call is being collected.* ERROR: <core> [core/parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 22) ERROR: <core> [core/parser/msg_parser.c:671]: parse_msg(): ERROR: parse_msg: message=<HTTP/1.1 101 Switching Protocols#015#012Sia: SIP/2.0/TLS x.x.x.x:42173#015#012Sec-WebSocket-Protocol: sip#015#012Upgrade: websocket#015#012Connection: upgrade#015#012Sec-WebSocket-Accept: qrLTSNMA7oAO8YXGaUhf3Ru26X0=#015#012Content-Length: 0#015#012#015#012> Any assistance would be appreciated. Thank you. -- Regards, Suresh Talasaniya. Contact : +91-9724264776 Skype : suresh.talsaniya

2 6

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users January 2018