- sr-users - kamailio.org

Websockets, set_contact_alias(), & IPv6
by Anthony Messina 08 Apr '15

08 Apr '15

I've been working on Kamailio websocket integration and I believe I'm having issues with the IPv6 address representation in the Contact header's alias parameter. After Googling, it appears after https://github.com/kamailio/kamailio/commit/814c08f3 the IPv6 contact is represented in brackets []. However, it when using websockets, and the alias= parameter uses brackets [] around and IPv6 address, there are message parsing issues. With a header such as the following Contact: <sip:wstest1@example.com;gr=urn:uuid:26140e27-0ab7-4e65-98e3-3d0909b1434e;alias=[2001:db8:0:1]~48768~6> Asterisk 13.2.0 will give the following error: pjsip:0 <?>: sip_transport. Error processing 1855 bytes packet from UDP 10.77.79.3:5060 : PJSIP syntax error exception when parsing 'Request Line' header on line 12 col 129: And when sipjs, or jssip are used with either Firefox or Chrome, they send garbage in the ACK request URI: Kamailio logs something like the following and the ACK cannot be processed: WARNING: sanity [sanity.c:236]: check_ruri_scheme(): failed to parse request uri [�a�{1me▒s�na@50�9��1.�8:�2v0;i��a��=11>7�n7x>10O�2v0~1] Is it proper to have [] brackets around the IPv6 alias address in the Contact header? Does the value need to be quoted? If I force the browser to use IPv4, without changing anything else, both jssip and sipjs work perfectly in Firefox and Chrome. -- Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery 8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E

2 5

Re: [SR-Users] [RTPproxy] Re: [OpenSIPS-Users] Announcing rtpproxy v2.0.0
by Maxim Sobolev 08 Apr '15

08 Apr '15

Pull requests are welcome, guys. We are hitting 30k rtp sessions on one of our largest clusters. Lot of changes are coming into git repo soon to make rtp_cluster component run smoothly under such conditions. On Mar 16, 2015 8:56 PM, "John Mathew" <john.mathew(a)divoxmedia.com> wrote: > Yes > > On Tuesday, 17 March 2015, Zheng Frank <zhengyumingapple(a)gmail.com> wrote: > >> Do you mean ROHC ? >> >> 2015-03-14 12:39 GMT+08:00 Maxim Sobolev <sobomax(a)sippysoft.com>: >> >>> Do you have any particular RFC in mind? >>> On Mar 12, 2015 10:28 AM, "John Mathew" <john.mathew(a)divoxmedia.com> >>> wrote: >>> >>>> Hi, >>>> >>>> Maxim, >>>> Is there any plans for rtp header compression in future. I can't see >>>> anything in the change log for 2.0.0 >>>> >>>> >>>> On Tuesday, 10 March 2015, Maxim Sobolev <sobomax(a)sippysoft.com> wrote: >>>> >>>>> Hi All, >>>>> >>>>> I'm happy to announce that we have released rtpproxy v2.0.0. >>>>> >>>>> You can review the release notes here: >>>>> https://github.com/sippy/rtpproxy/releases/tag/v2.0.0 >>>>> >>>>> -sobomax >>>>> >>>>> >>>> >>>> -- >>>> Sent from iPhone 6 >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "rtpproxy" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to rtpproxy+unsubscribe(a)googlegroups.com. >>>> To post to this group, send email to rtpproxy(a)googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/rtpproxy/CA%2BSkwpUhu9fpwmqpRFiaXsQo9_%2B… >>>> <https://groups.google.com/d/msgid/rtpproxy/CA%2BSkwpUhu9fpwmqpRFiaXsQo9_%2B…> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> _______________________________________________ >>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >>> sr-users(a)lists.sip-router.org >>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >>> >>> >> > > -- > Sent from iPhone 6 > > -- > You received this message because you are subscribed to the Google Groups > "rtpproxy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to rtpproxy+unsubscribe(a)googlegroups.com. > To post to this group, send email to rtpproxy(a)googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/rtpproxy/CA%2BSkwpWvmaQnE8qM8ibb10d%3DNj9… > <https://groups.google.com/d/msgid/rtpproxy/CA%2BSkwpWvmaQnE8qM8ibb10d%3DNj9…> > . > For more options, visit https://groups.google.com/d/optout. >

1 0

Reg. invalid cseq error.
by Badri Ranganathan 07 Apr '15

07 Apr '15

Hi all, I make calls towards the Kamailio from my call generator and I get a message saying "invalid cseq error" sometimes at the 1005th registration or sometimes at the 1013thregistration, but the cseq number seems to be fine. Any idea about why this would happen? Thanks, Badri.

3 2

Upgrade from Sip Express Router 0.9.6
by Andres 07 Apr '15

07 Apr '15

How would one even approach the daunting task of upgrading a fully operational Sip Express Router 0.9.6 installation with thousands of users that has been running unmodified for over 10 years. I would like some pointers on how to approach the mysql database migration from the old schema to the Kamailio 4.2 schema. I sure hope I don't have to start from scratch. Maybe somebody has already done an upgrade script? Regarding the config file, I will certainly have to rewrite it but I was wondering if there was a list of deprecated commands or syntaxes that would no longer be valid and their equivalent replacement. Thanks, -- Technical Support http://www.cellroute.net

3 6

Problem unsubcribing list
by JIvars 07 Apr '15

07 Apr '15

Hello i want to unsubscribe from sr-users(a)lists.sip-router.org but it is impossible, i have tried with: http://lists.sip-router.org/cgi-bin/mailman/options/sr-users But the email never arrives, could you help me please Best regards.

3 2

Regarding multi user chat in Kamailio IMS server
by MadhuManjushaAripirala 07 Apr '15

07 Apr '15

Hello all, I have RCS based client. I would like to implement MUC(multi chat user) in existing Kamailio IMS Server. Please help me to input the procedure.Is it really possible to do it ? Please share me URL for any existing "C" source code which I can directly imbibe into Kamailio IMS serve -- View this message in context: http://sip-router.1086192.n5.nabble.com/Regarding-multi-user-chat-in-Kamail… Sent from the Users mailing list archive at Nabble.com.

2 4

flag f in search_hf() is not working for me
by schwatzi＠web.de 07 Apr '15

07 Apr '15

Hi. I think there is a bug in function search_hf_f() in textops.c Here is what I do if ( method == SUBSCRIBE ) { if ( !search_hf("Event", "call-completion", "f") ) { sl_send_reply("489","Bad Event"); exit; } } But here is a SUBSCRIBE that do pass the proxy. SUBSCRIBE sip:101@192.168.1.50 SIP/2.0 Via: SIP/2.0/UDP 77.10.66.72:59793;branch=z9hG4bKPj.O5IXVtDsImPNfCGnDkvj91INsEfvZsm Max-Forwards: 70 From: <sip:101@192.168.1.50>;tag=8-cXkrmwx5WGSIAYgYaXW0oTTsEAEM1S To: <sip:101@192.168.1.50> Contact: <sip:101@192.168.1.8:59793;ob> Call-ID: O12dPIx7Wiih2b.o36UFmMdXr6RE-8Jl CSeq: 24359 SUBSCRIBE Route: <sip:192.168.1.50;transport=udp;lr> Event: message-summary Expires: 3600 Supported: replaces, 100rel, timer, norefersub Accept: application/simple-message-summary Allow-Events: presence, message-summary, refer User-Agent: CSipSimple_mako-21/r2457 Content-Length: 0 As you can see the Event header doesn't contain "call-completition". Looking at function search_hf_f() i saw that if nothing is found value -1 will be returned. if there is the match then 1 is returned. (see line 2779 and 2797) But in line 2782 the function will return 1 instead of -1 index 50a6f07..a945937 100644 --- a/modules/textops/textops.c +++ b/modules/textops/textops.c @@ -2779,7 +2779,7 @@ static int search_hf_f(struct sip_msg* msg, char* str_hf, char* re, char *flags) return 1; } else { if(flags!=NULL && *flags=='f') - return 1; + return -1; } } else { hfl = hf; I am no programmer so it's possible that I misunderstood something. greetz Paolo

2 1

GSM SMS service
by Raj Roy Ghandhi 07 Apr '15

07 Apr '15

Hi Friends, I need to send text to GSM phones from SIP client. SIPSimple text -> GSM SMS Does anybody know good SMS gateway service that I can use for this purpose. Best Regards, Roy Gandhi.

2 1

Regarding IMS/RCS complaint clients for Kamailio IMS/RCS server
by MadhuManjushaAripirala 07 Apr '15

07 Apr '15

Hello, Please let me know 1.What are the IMS and RCS based clients available to test on Kamailio IMS/RCS server? 2.On browsing for Kamailio Installation,I found below 3 different links,please suggest me which one to be followed. https://loadmultiplier.com/node/76 http://www.kamailio.org/wiki/tutorials/ims/installation-howto http://kamailio.org/wiki/install/4.2.x/git 3.From the first link above,I see there are separate steps mentioned to install CSCF nodes and HSS but where I find no information for setting up RCS AS(application server) module.Please let me know on this. Thanks & Regards, Manjusha. -- View this message in context: http://sip-router.1086192.n5.nabble.com/Regarding-IMS-RCS-complaint-clients… Sent from the Users mailing list archive at Nabble.com.

3 6

Fwd: INVITE routing issue when using Private IP (RFC1918) network
by pslack14 06 Apr '15

06 Apr '15

Hello, I have a Kamailio IMS instance setup, using different hosts for each IMS function (P-CSCF,S-CSCF,I-CSCF etc) and am able to register clients successfully. However, when Client-A tries to call Client-B (both registered to the same S-CSCF), the call is failing with the "403 Forbidden - You must register first with a S-CSCF" error. . All hosts & clients are running on the same subnet using RFC1918 IP addresses, there is no NAT involved. I've seen the same issue on both 4.2 and Master branches. I have the nathelper 'nat_uac_test' parameter set to 18. Looking at the debug prints and SIP traces, I can see that the 403 Error is being generated by the P-CSCF when it receives the INVITE from the S-CSCF (for forwarding to Client-B). Digging deeper into the debug logs, it looks like this is a result of a failed contact match - I've experimented with different values for "hashing_type", which do change the routing logic but still I see the 403 Error. Here's 2 excerpts from the debug prints for different values of hashing_type : *modparam("ims_usrloc_pcscf", ""hashing_type",hashing_type", 0) :* 2(19636) DEBUG: ims_registrar_pcscf [service_routes.c:183]: getContactP(): > Searching in usrloc for 10.133.202.17:5060 (Proto 1) 2(19636) DEBUG: ims_usrloc_pcscf [udomain.c:618]: get_pcontact_by_src(): > Trying to find contact by src with URI: [sip:*@10.133.202.17:5060] 2(19636) DEBUG: ims_usrloc_pcscf [udomain.c:465]: get_pcontact(): > Searching for contact in P-CSCF usrloc [sip:*@10.133.202.17:5060] 2(19636) DEBUG: ims_usrloc_pcscf [usrloc.c:187]: get_aor_hash(): Returning > hash slot: [1670705485] 2(19636) DEBUG: ims_registrar_pcscf [service_routes.c:186]: getContactP(): > No entry in usrloc for 10.133.202.17:5060 (Proto 1) found! 2(19636) DEBUG: ims_usrloc_pcscf [udomain.c:465]: get_pcontact(): > Searching for contact in P-CSCF usrloc [sip:john@10.133.202.61:64019 > ;transport=udp] 2(19636) DEBUG: ims_usrloc_pcscf [usrloc.c:187]: get_aor_hash(): Returning > hash slot: [397265208] 2(19636) DEBUG: ims_registrar_pcscf [service_routes.c:119]: > checkcontact(): Port 64019 (search 5060), Proto 1 (search 1), reg_state > registered (search registered) 2(19636) ERROR: *** cfgtrace:request_route=[Orig_Initial] > c=[/etc/kamailio/kamailio.cfg] l=926 a=26 n=send_reply *modparam("ims_usrloc_pcscf", ""hashing_type",hashing_type", 2) :* 1(19401) DEBUG: ims_registrar_pcscf [service_routes.c:183]: getContactP(): >> Searching in usrloc for 10.133.202.17:5060 (Proto 1) > > 1(19401) DEBUG: ims_usrloc_pcscf [udomain.c:618]: get_pcontact_by_src(): >> Trying to find contact by src with URI: [sip:*@10.133.202.17:5060] > > 1(19401) DEBUG: ims_usrloc_pcscf [udomain.c:465]: get_pcontact(): >> Searching for contact in P-CSCF usrloc [sip:*@10.133.202.17:5060] > > 1(19401) DEBUG: ims_usrloc_pcscf [usrloc.c:97]: >> get_alias_host_from_contact(): no params > > 1(19401) DEBUG: ims_usrloc_pcscf [usrloc.c:183]: get_aor_hash(): using >> host for hash [10.133.202.17] > > 1(19401) DEBUG: ims_usrloc_pcscf [usrloc.c:187]: get_aor_hash(): >> Returning hash slot: [-1564914093] > > 1(19401) DEBUG: ims_registrar_pcscf [service_routes.c:186]: >> getContactP(): No entry in usrloc for 10.133.202.17:5060 (Proto 1) found! > > 1(19401) DEBUG: ims_usrloc_pcscf [udomain.c:465]: get_pcontact(): >> Searching for contact in P-CSCF usrloc [sip:john@10.133.202.61:64013 >> ;transport=udp] > > 1(19401) DEBUG: ims_usrloc_pcscf [usrloc.c:176]: get_aor_hash(): Looks >> like this contact is natted - contact URI: [10.133.202.61] but came from >> received_host: [10.133.202.17] so will use received_host for hash > > 1(19401) DEBUG: ims_usrloc_pcscf [usrloc.c:187]: get_aor_hash(): >> Returning hash slot: [-1564914093] > > 1(19401) ERROR: *** cfgtrace:request_route=[Orig_Initial] >> c=[/etc/kamailio/kamailio.cfg] l=926 a=26 n=send_reply > > Can anyone offer any hints as to how to resolve this? I am attaching a SIP call flow - I can supply a complete Kamailio debug trace if needed. Thanks Phill

1 0

Ip Address
by badican c-tin 05 Apr '15

05 Apr '15

HelloI have a little project and I need to find the ip address from my SIP phone. How can I find my ip addres of the phone?Have you a command or a service whith this functions? Thanks for help !!!Best regards,Constantin

1 0

Re: [SR-Users] SIP messages over UDP with sizes over MTU
by Yufei Tao 03 Apr '15

03 Apr '15

Hi Daniel We don't have pike module enabled. When the problem occurred on an VIP, we observed these: * Kamailio stopped responding to any messages that were sent to the VIP, not just OPTIONS * The OPTIONS messages are not big. But the other SIP messages, e.g. some of the INVITE/OK that came from some SBCs can be big * netstat showed the Recv-Q on that VIP had a lot of bytes accumulated, while Kamailio was not seeing/reading them * Kamailio responded fine on its real IP, when I sent OPTIONS pings to it using sipsak * After restarting Kamailio it started working. But after 1 week or so the same problem happened again Since this only happened after running for 1 week or so, we didn't have any traces to show what exactly happened at the particular time when it happened. It is possible some SIP messages may have come in fragmented and some are just too big, depending on the route they came from etc. So I was wonder if it was possible that the UDP receive buffer was filled somehow with messed-up messages. Is there anyway to check this? Any suggestions where I should start looking please? Or is it generally a bad idea to use UDP when there are messages that may be too big, either fragmented or not? Since the it is running in the production environment, I'd like to get some confidence that a Kamailio upgrade will fix the problem first before I change anything there. Cheers, Yufei Date: Wed, 01 Apr 2015 16:27:44 +0200 From: Daniel-Constantin Mierla <miconda(a)gmail.com> To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.sip-router.org > Subject: Re: [SR-Users] SIP messages over UDP with sizes over MTU Message-ID: <551C0060.3010002(a)gmail.com> Content-Type: text/plain; charset="windows-1252" Hello, first, not related to the topic you reported, I would recommend at least upgrading to latest 4.0.x, there were many fixes from v4.0.0 and there are no changes to be done to config or database -- simply deploy latest 4.0.x and restart. Back to this topic. Is all the other traffic handled apart of big OPTIONS? Do you have pike module enabled? If yes, can you double check and be sure that the SBC is not blacklisted (traffic from it should not be handled via pike_check_req()). Cheers, Daniel On 01/04/15 15:42, Yufei Tao wrote: > Hi > > We've got Kamailio (v4.0.0) connected to some SBC, which sends SIP > traffic and periodic OPTIONS pings to Kamailio's VIP. Kamailio > responds to the OPTIONS pings with OK, i.e. in the main route block: > if (is_method("OPTIONS")) > { > sl_send_reply("200","OK"); > exit; > } > > All works fine for a week or so, then Kamailio stopped responding to > the OPTIONS pings on the VIP it listens to. But it still respond to > OPTIONS pings that are sent to its real IP. The real IP is not used > for receiving/sending any traffic while only the VIP is. So it seems > that Kamailio is still working, but maybe having problems with the > receiving buffer for the VIP? > > We do see that some SIP messages sent to Kamailio's VIP are too big > (sometimes over 1500 bytes). My question is, in this case, what would > be expected to happen? Is it possible somehow the receiving buffer for > the VIP got messed up by the big UDP messages? Any one seen similar > problems? What is the suggested solution? > > We're considering moving to TCP. But since this is production > environment, I want to get some confidence that the problem we saw was > likely to have been caused by the UDP message being too large. > > Cheers, > Yufei

2 1

Kamailio v4.2.4 Released
by Daniel-Constantin Mierla 02 Apr '15

02 Apr '15

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

1 0

Kamailio coredump when "INVITE" enter in failure route
by José Seabra 02 Apr '15

02 Apr '15

Hi there, I have noticed that my kamailio proxy, version 4.2.2 is originating core dumps. This happens when Kamailio receives an INVITE in failure route, then execute the function async_sleep(3), after that changes request uri, then it stops with following error message shown below: <core> [mem/f_malloc.c:586]: fm_free(): BUG: fm_free: bad pointer 0x7f8d26605ed8 (out of memory block!), called from <core>: parser/msg_parser.c: set_path_vector(822) - aborting Please see the attachment that contains the " gdb bt full" from core.dump originated Thank you for your attention Best Regards -- Cumprimentos José Seabra

2 4

rtpengine documentation error for forced rtpproxying?
by Daniel Tryba 02 Apr '15

02 Apr '15

I'm looking to replace rtpproxy with rtpengine. All calls have to be forced thru rtpengine and according to the documentation the equivalent of rtpproxy_manage("f"); is rtpengine_manage("force"); But rtpenginge doesn't recognize it as a valid flag. Using the legacy rtpproxy mod it still works though. Is it a documentation failure or is a specific version of rtpengine required for forced? Apr 1 17:54:28 pisco rtpengine[3432]: Got valid command from 127.0.0.1:43193: offer - { "sdp": "v=0#015#012o=tryba 8000 8001 I N IP4 10.0.3.169#015#012s=SIP Call#015#012c=IN IP4 10.0.3.169#015#012t=0 0#015#012m=audio 5016 RTP/AVP 8 0 9 2 3 18 4 99 101 13 #015#012a=sendrecv#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:9 G722/8000#015#012a=rtpmap:2 G726-3 2/8000#015#012a=rtpmap:3 GSM/8000#015#012a=rtpmap:18 G729/8000#015#012a=rtpmap:4 G723/8000#015#012a=rtpmap:99 iLBC/8000#015#012 a=fmtp:99 mode=20#015#012a=ptime:20#015#012a=rtpmap:101 telephone- event/8000#015#012a=fmtp:101 0-11#015#012", "flags": [ "force " ], "call-id": "5 ... Apr 1 17:54:28 pisco rtpengine[3432]: ... f13ffb48e98404a(a)10.0.3.169", "received-from": [ "IP4", "109.235.34.226" ], "from-tag ": "3819edfdf2df044a", "command": "offer" } Apr 1 17:54:28 pisco rtpengine[3432]: Unknown flag encountered: 'force' -- Telefoon: 088 0100 700 Sales: sales(a)pocos.nl | Service: servicedesk(a)pocos.nl http://www.pocos.nl/ | Croy 9c, 5653 LC Eindhoven | Kamer van Koophandel 17097024

2 4

Planning to release Kamailio v4.2.4
by Daniel-Constantin Mierla 02 Apr '15

02 Apr '15

Hello, I am considering to release a new maintenance version from latest stable branch - to be v4.2.4 - next week, most likely on Thursday, April 2. If there is anything important to get in and not discussed yet, bring the topic on development mailing list. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com

1 1

Recommendation for toggling MSILO m_store auto-notification reply on/off
by Anthony Messina 02 Apr '15

02 Apr '15

Using Kamailio 4.2-dev and MSILO, is it possible to "toggle" the auto- notification reply MESSAGE using something similar to the following where "$var(msilo_reply)" is emtpy at startup (or are there suggestions for a better method): modparam("msilo", "from_address", "$var(msilo_reply)") ... if(CONDITION WHERE I WANT THE AUTO-REPLY RETURNS POSITIVE) { $var(msilo_reply)="$rU(a)example.net"; } m_store($rU) ... My use case is that I would like the auto-notification reply to occur in some instances, but not others. I also do not want to create a loop where the auto-notification replies are also stored. I was originally using a simple test: if(src_ip!=myself), but I have begun to use the IMC module as well as the EXEC module and these MESSAGEs appear to originate from "myself." Looking at the MSILO documentation I see there is "extra_hdrs(string)," but this appears to be designed to add headers to dumped MESSAGEs. I was hoping there would be a way to add a custom header to the auto-notification, on which I could filter/drop generated replies earlier in the route, but it doesn't appear that this exists. My preference for the best-case scenario would be to control the generation of the auto-notification reply in the first place rather than having to add a control to detect the reply and drop it. Thanks in advance for any recommendations. -- Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery 8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E

2 3

SIP messages over UDP with sizes over MTU
by Yufei Tao 01 Apr '15

01 Apr '15

Hi We've got Kamailio (v4.0.0) connected to some SBC, which sends SIP traffic and periodic OPTIONS pings to Kamailio's VIP. Kamailio responds to the OPTIONS pings with OK, i.e. in the main route block: if (is_method("OPTIONS")) { sl_send_reply("200","OK"); exit; } All works fine for a week or so, then Kamailio stopped responding to the OPTIONS pings on the VIP it listens to. But it still respond to OPTIONS pings that are sent to its real IP. The real IP is not used for receiving/sending any traffic while only the VIP is. So it seems that Kamailio is still working, but maybe having problems with the receiving buffer for the VIP? We do see that some SIP messages sent to Kamailio's VIP are too big (sometimes over 1500 bytes). My question is, in this case, what would be expected to happen? Is it possible somehow the receiving buffer for the VIP got messed up by the big UDP messages? Any one seen similar problems? What is the suggested solution? We're considering moving to TCP. But since this is production environment, I want to get some confidence that the problem we saw was likely to have been caused by the UDP message being too large. Cheers, Yufei

2 1

SIP Authentication Best Practices
by Grant Bagdasarian 01 Apr '15

01 Apr '15

Hello, I'm implementing basic authentication using the auth and auth_db module, and I was wondering which domain to use when calling the auth_check function? Should I use the From domain or the To domain? Or both? The default configuration file deployed with kamailio uses $fd, but a code sample in the htable module page uses $td (dictionary attack sample). Aren't both the From and To header spoofable and not really used in SIP message routing?

1 0

jsonrpc_exec crashes kamailio
by Grant Bagdasarian 01 Apr '15

01 Apr '15

Hello, Kamailio crashes when I try to execute the following jsonrpc_exec functions: jsonrpc_exec('{"jsonrpc": "2.0", "method": "domain.reload", "id": 0}'); #domain module jsonrpc_exec('{"jsonrpc": "2.0", "method": "addressReload", "id": 0}'); #permissions module This one works fine: jsonrpc_exec('{"jsonrpc": "2.0", "method": "htable.reload", "params": ["tablename"], "id": 0}'); Any ideas? Running on Debian 7.8 and Kamailio 4.2.3. Backtrace: *** glibc detected *** /usr/local/sbin/kamailio: double free or corruption (fasttop): 0x0000000001f1ff00 *** ======= Backtrace: ========= /lib/x86_64-linux-gnu/libc.so.6(+0x75be6)[0x7f7009d50be6] /lib/x86_64-linux-gnu/libc.so.6(cfree+0x6c)[0x7f7009d5598c] /usr/local/lib64/kamailio/modules/jsonrpc-s.so(+0x2834)[0x7f7003e12834] /usr/local/lib64/kamailio/modules/jsonrpc-s.so(+0xb59a)[0x7f7003e1b59a] /usr/local/sbin/kamailio(do_action+0x749a)[0x41fc24] /usr/local/sbin/kamailio(run_actions+0x643)[0x42bc9a] /usr/local/sbin/kamailio(do_action+0x737e)[0x41fb08] /usr/local/sbin/kamailio(run_actions+0x643)[0x42bc9a] /usr/local/sbin/kamailio(do_action+0x10073)[0x4287fd] /usr/local/sbin/kamailio(run_actions+0x643)[0x42bc9a] /usr/local/sbin/kamailio(do_action+0x737e)[0x41fb08] /usr/local/sbin/kamailio(run_actions+0x643)[0x42bc9a] /usr/local/sbin/kamailio(do_action+0x737e)[0x41fb08] /usr/local/sbin/kamailio(run_actions+0x643)[0x42bc9a] /usr/local/sbin/kamailio(do_action+0x408d)[0x41c817] /usr/local/sbin/kamailio(run_actions+0x643)[0x42bc9a] /usr/local/sbin/kamailio(run_top_route+0x98)[0x42c3dd] /usr/local/sbin/kamailio(receive_msg+0x12fc)[0x50acec] /usr/local/sbin/kamailio(receive_tcp_msg+0x47a)[0x5f356a] /usr/local/sbin/kamailio(tcp_read_req+0x1798)[0x5f4d09] /usr/local/sbin/kamailio[0x5f7d19] /usr/local/sbin/kamailio[0x5eb830] /usr/local/sbin/kamailio(tcp_receive_loop+0x362)[0x5f8d6d] /usr/local/sbin/kamailio(tcp_init_children+0x7e2)[0x5e2453] /usr/local/sbin/kamailio(main_loop+0x390b)[0x4a8e33] /usr/local/sbin/kamailio(main+0x47cc)[0x4ae0fb] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)[0x7f7009cf9ead] /usr/local/sbin/kamailio[0x417db9] ======= Memory map: ======== 00400000-007c3000 r-xp 00000000 08:01 803340 /usr/local/sbin/kamailio 009c2000-009cc000 rw-p 003c2000 08:01 803340 /usr/local/sbin/kamailio 009cc000-00a89000 rw-p 00000000 00:00 0 01e84000-01f0a000 rw-p 00000000 00:00 0 [heap] 01f0a000-01f47000 rw-p 00000000 00:00 0 [heap] 01f47000-01f6d000 rw-p 00000000 00:00 0 [heap] 7f6ff8000000-7f6ff8021000 rw-p 00000000 00:00 0 7f6ff8021000-7f6ffc000000 ---p 00000000 00:00 0 7f6ffdbc6000-7f6ffdbdb000 r-xp 00000000 08:01 913924 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f6ffdbdb000-7f6ffdddb000 ---p 00015000 08:01 913924 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f6ffdddb000-7f6ffdddc000 rw-p 00015000 08:01 913924 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f6ffdddc000-7f6ffddde000 r-xp 00000000 08:01 784463 /usr/lib/x86_64-linux-gnu/gconv/CP1252.so 7f6ffddde000-7f6ffdfdd000 ---p 00002000 08:01 784463 /usr/lib/x86_64-linux-gnu/gconv/CP1252.so 7f6ffdfdd000-7f6ffdfde000 r--p 00001000 08:01 784463 /usr/lib/x86_64-linux-gnu/gconv/CP1252.so 7f6ffdfde000-7f6ffdfdf000 rw-p 00002000 08:01 784463 /usr/lib/x86_64-linux-gnu/gconv/CP1252.so 7f6ffdfdf000-7f6ffdfe2000 r-xp 00000000 08:01 914284 /lib/x86_64-linux-gnu/libgpg-error.so.0.8.0 7f6ffdfe2000-7f6ffe1e1000 ---p 00003000 08:01 914284 /lib/x86_64-linux-gnu/libgpg-error.so.0.8.0 7f6ffe1e1000-7f6ffe1e2000 rw-p 00002000 08:01 914284 /lib/x86_64-linux-gnu/libgpg-error.so.0.8.0 7f6ffe1e2000-7f6ffe1f3000 r-xp 00000000 08:01 787833 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.0.0 7f6ffe1f3000-7f6ffe3f2000 ---p 00011000 08:01 787833 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.0.0 7f6ffe3f2000-7f6ffe3f3000 r--p 00010000 08:01 787833 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.0.0 7f6ffe3f3000-7f6ffe3f4000 rw-p 00011000 08:01 787833 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.0.0 7f6ffe3f4000-7f6ffe40a000 r-xp 00000000 08:01 914012 /lib/x86_64-linux-gnu/libz.so.1.2.7 7f6ffe40a000-7f6ffe609000 ---p 00016000 08:01 914012 /lib/x86_64-linux-gnu/libz.so.1.2.7 7f6ffe609000-7f6ffe60a000 r--p 00015000 08:01 914012 /lib/x86_64-linux-gnu/libz.so.1.2.7 7f6ffe60a000-7f6ffe60b000 rw-p 00016000 08:01 914012 /lib/x86_64-linux-gnu/libz.so.1.2.7 7f6ffe60b000-7f6ffe686000 r-xp 00000000 08:01 913957 /lib/x86_64-linux-gnu/libgcrypt.so.11.7.0 7f6ffe686000-7f6ffe886000 ---p 0007b000 08:01 913957 /lib/x86_64-linux-gnu/libgcrypt.so.11.7.0 7f6ffe886000-7f6ffe887000 r--p 0007b000 08:01 913957 /lib/x86_64-linux-gnu/libgcrypt.so.11.7.0 7f6ffe887000-7f6ffe88a000 rw-p 0007c000 08:01 913957 /lib/x86_64-linux-gnu/libgcrypt.so.11.7.0 7f6ffe88a000-7f6ffe89a000 r-xp 00000000 08:01 787835 /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.16 7f6ffe89a000-7f6ffea99000 ---p 00010000 08:01 787835 /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.16 7f6ffea99000-7f6ffea9a000 r--p 0000f000 08:01 787835 /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.16 7f6ffea9a000-7f6ffea9b000 rw-p 00010000 08:01 787835 /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.16 7f6ffea9b000-7f6ffeaa2000 r-xp 00000000 08:01 918716 /lib/x86_64-linux-gnu/librt-2.13.so 7f6ffeaa2000-7f6ffeca1000 ---p 00007000 08:01 918716 /lib/x86_64-linux-gnu/librt-2.13.so 7f6ffeca1000-7f6ffeca2000 r--p 00006000 08:01 918716 /lib/x86_64-linux-gnu/librt-2.13.so 7f6ffeca2000-7f6ffeca3000 rw-p 00007000 08:01 918716 /lib/x86_64-linux-gnu/librt-2.13.so 7f6ffeca3000-7f6ffed5c000 r-xp 00000000 08:01 784529 /usr/lib/x86_64-linux-gnu/libgnutls.so.26.22.4 7f6ffed5c000-7f6ffef5b000 ---p 000b9000 08:01 784529 /usr/lib/x86_64-linux-gnu/libgnutls.so.26.22.4 7f6ffef5b000-7f6ffef61000 r--p 000b8000 08:01 784529 /usr/lib/x86_64-linux-gnu/libgnutls.so.26.22.4 7f6ffef61000-7f6ffef63000 rw-p 000be000 08:01 784529 /usr/lib/x86_64-linux-gnu/libgnutls.so.26.22.4 7f6ffef63000-7f6ffef74000 r-xp 00000000 08:01 801540 /usr/lib/x86_64-linux-gnu/libodbcinst.so.1.0.0 7f6ffef74000-7f6fff174000 ---p 00011000 08:01 801540 /usr/lib/x86_64-linux-gnu/libodbcinst.so.1.0.0 7f6fff174000-7f6fff175000 rw-p 00011000 08:01 801540 /usr/lib/x86_64-linux-gnu/libodbcinst.so.1.0.0 7f6fff175000-7f6fff1d2000 r-xp 00000000 08:01 803365 /usr/lib/x86_64-linux-gnu/odbc/libtdsodbc.so 7f6fff1d2000-7f6fff3d2000 ---p 0005d000 08:01 803365 /usr/lib/x86_64-linux-gnu/odbc/libtdsodbc.so 7f6fff3d2000-7f6fff3d5000 r--p 0005d000 08:01 803365 /usr/lib/x86_64-linux-gnu/odbc/libtdsodbc.so 7f6fff3d5000-7f6fff3d6000 rw-p 00060000 08:01 803365 /usr/lib/x86_64-linux-gnu/odbc/libtdsodbc.so 7f6fff3d6000-7f6fff3d8000 r-xp 00000000 08:01 784470 /usr/lib/x86_64-linux-gnu/gconv/ISO8859-1.so 7f6fff3d8000-7f6fff5d7000 ---p 00002000 08:01 784470 /usr/lib/x86_64-linux-gnu/gconv/ISO8859-1.so 7f6fff5d7000-7f6fff5d8000 r--p 00001000 08:01 784470 /usr/lib/x86_64-linux-gnu/gconv/ISO8859-1.so 7f6fff5d8000-7f6fff5d9000 rw-p 00002000 08:01 784470 /usr/lib/x86_64-linux-gnu/gconv/ISO8859-1.so 7f6fff5d9000-7f70035d9000 rw-s 00000000 00:04 574933 /dev/zero (deleted) 7f70035d9000-7f70035e4000 r-xp 00000000 08:01 918697 /lib/x86_64-linux-gnu/libnss_files-2.13.so 7f70035e4000-7f70037e3000 ---p 0000b000 08:01 918697 /lib/x86_64-linux-gnu/libnss_files-2.13.so 7f70037e3000-7f70037e4000 r--p 0000a000 08:01 918697 /lib/x86_64-linux-gnu/libnss_files-2.13.so 7f70037e4000-7f70037e5000 rw-p 0000b000 08:01 918697 /lib/x86_64-linux-gnu/libnss_files-2.13.so 7f70037e5000-7f70037ef000 r-xp 00000000 08:01 918707 /lib/x86_64-linux-gnu/libnss_nis-2.13.so 7f70037ef000-7f70039ee000 ---p 0000a000 08:01 918707 /lib/x86_64-linux-gnu/libnss_nis-2.13.so 7f70039ee000-7f70039ef000 r--p 00009000 08:01 918707 /lib/x86_64-linux-gnu/libnss_nis-2.13.so 7f70039ef000-7f70039f0000 rw-p 0000a000 08:01 918707 /lib/x86_64-linux-gnu/libnss_nis-2.13.so 7f70039f0000-7f7003a05000 r-xp 00000000 08:01 918699 /lib/x86_64-linux-gnu/libnsl-2.13.so 7f7003a05000-7f7003c04000 ---p 00015000 08:01 918699 /lib/x86_64-linux-gnu/libnsl-2.13.so 7f7003c04000-7f7003c05000 r--p 00014000 08:01 918699 /lib/x86_64-linux-gnu/libnsl-2.13.so 7f7003c05000-7f7003c06000 rw-p 00015000 08:01 918699 /lib/x86_64-linux-gnu/libnsl-2.13.so 7f7003c06000-7f7003c08000 rw-p 00000000 00:00 0 7f7003c08000-7f7003c0f000 r-xp 00000000 08:01 918711 /lib/x86_64-linux-gnu/libnss_compat-2.13.so 7f7003c0f000-7f7003e0e000 ---p 00007000 08:01 918711 /lib/x86_64-linux-gnu/libnss_compat-2.13.so 7f7003e0e000-7f7003e0f000 r--p 00006000 08:01 918711 /lib/x86_64-linux-gnu/libnss_compat-2.13.so 7f7003e0f000-7f7003e10000 rw-p 00007000 08:01 918711 /lib/x86_64-linux-gnu/libnss_compat-2.13.so 7f7003e10000-7f7003e21000 r-xp 00000000 08:01 923664 /usr/local/lib64/kamailio/modules/jsonrpc-s.so 7f7003e21000-7f7004021000 ---p 00011000 08:01 923664 /usr/local/lib64/kamailio/modules/jsonrpc-s.so 7f7004021000-7f7004022000 rw-p 00011000 08:01 923664 /usr/local/lib64/kamailio/modules/jsonrpc-s.so 7f7004022000-7f700402f000 r-xp 00000000 08:01 923743 /usr/local/lib64/kamailio/modules/xhttp.so 7f700402f000-7f700422f000 ---p 0000d000 08:01 923743 /usr/local/lib64/kamailio/modules/xhttp.so 7f700422f000-7f7004230000 rw-p 0000d000 08:01 923743 /usr/local/lib64/kamailio/modules/xhttp.so 7f7004230000-7f700426f000 r-xp 00000000 08:01 923652 /usr/local/lib64/kamailio/modules/dispatcher.so 7f700426f000-7f700446f000 ---p 0003f000 08:01 923652 /usr/local/lib64/kamailio/modules/dispatcher.so 7f700446f000-7f7004471000 rw-p 0003f000 08:01 923652 /usr/local/lib64/kamailio/modules/dispatcher.so 7f7004471000-7f70044af000 r-xp 00000000 08:01 923689 /usr/local/lib64/kamailio/modules/permissions.so 7f70044af000-7f70046af000 ---p 0003e000 08:01 923689 /usr/local/lib64/kamailio/modules/permissions.so 7f70046af000-7f70046b1000 rw-p 0003e000 08:01 923689 /usr/local/lib64/kamailio/modules/permissions.so 7f70046b1000-7f70046b2000 rw-p 00000000 00:00 0 7f70046b2000-7f70046bf000 r-xp 00000000 08:01 923660 /usr/local/lib64/kamailio/modules/group.so 7f70046bf000-7f70048bf000 ---p 0000d000 08:01 923660 /usr/local/lib64/kamailio/modules/group.so 7f70048bf000-7f70048c0000 rw-p 0000d000 08:01 923660 /usr/local/lib64/kamailio/modules/group.so 7f70048c0000-7f70048d7000 r-xp 00000000 08:01 923655 /usr/local/lib64/kamailio/modules/domain.so 7f70048d7000-7f7004ad6000 ---p 00017000 08:01 923655 /usr/local/lib64/kamailio/modules/domain.so 7f7004ad6000-7f7004ad7000 rw-p 00016000 08:01 923655 /usr/local/lib64/kamailio/modules/domain.so 7f7004ad7000-7f7004aea000 r-xp 00000000 08:01 923540 /usr/local/lib64/kamailio/modules/auth_db.so 7f7004aea000-7f7004cea000 ---p 00013000 08:01 923540 /usr/local/lib64/kamailio/modules/auth_db.so 7f7004cea000-7f7004ceb000 rw-p 00013000 08:01 923540 /usr/local/lib64/kamailio/modules/auth_db.so 7f7004ceb000-7f7004d13000 r-xp 00000000 08:01 923539 /usr/local/lib64/kamailio/modules/auth.so 7f7004d13000-7f7004f13000 ---p 00028000 08:01 923539 /usr/local/lib64/kamailio/modules/auth.so 7f7004f13000-7f7004f14000 rw-p 00028000 08:01 923539 /usr/local/lib64/kamailio/modules/auth.so 7f7004f14000-7f7004f28000 r-xp 00000000 08:01 923690 /usr/local/lib64/kamailio/modules/pike.so 7f7004f28000-7f7005128000 ---p 00014000 08:01 923690 /usr/local/lib64/kamailio/modules/pike.so 7f7005128000-7f7005129000 rw-p 00014000 08:01 923690 /usr/local/lib64/kamailio/modules/pike.so 7f7005129000-7f7005163000 r-xp 00000000 08:01 923661 /usr/local/lib64/kamailio/modules/htable.so 7f7005163000-7f7005362000 ---p 0003a000 08:01 923661 /usr/local/lib64/kamailio/modules/htable.so 7f7005362000-7f7005364000 rw-p 00039000 08:01 923661 /usr/local/lib64/kamailio/modules/htable.so 7f7005364000-7f700537b000 r-xp 00000000 08:01 918717 /lib/x86_64-linux-gnu/libpthread-2.13.so 7f700537b000-7f700557a000 ---p 00017000 08:01 918717 /lib/x86_64-linux-gnu/libpthread-2.13.so 7f700557a000-7f700557b000 r--p 00016000 08:01 918717 /lib/x86_64-linux-gnu/libpthread-2.13.so 7f700557b000-7f700557c000 rw-p 00017000 08:01 918717 /lib/x86_64-linux-gnu/libpthread-2.13.so 7f700557c000-7f7005580000 rw-p 00000000 00:00 0 7f7005580000-7f7005589000 r-xp 00000000 08:01 801498 /usr/lib/x86_64-linux-gnu/libltdl.so.7.3.0 7f7005589000-7f7005788000 ---p 00009000 08:01 801498 /usr/lib/x86_64-linux-gnu/libltdl.so.7.3.0 7f7005788000-7f7005789000 rw-p 00008000 08:01 801498 /usr/lib/x86_64-linux-gnu/libltdl.so.7.3.0 7f7005789000-7f70057e9000 r-xp 00000000 08:01 801505 /usr/lib/x86_64-linux-gnu/libodbc.so.1.0.0 7f70057e9000-7f70059e8000 ---p 00060000 08:01 801505 /usr/lib/x86_64-linux-gnu/libodbc.so.1.0.0 7f70059e8000-7f70059f0000 rw-p 0005f000 08:01 801505 /usr/lib/x86_64-linux-gnu/libodbc.so.1.0.0 7f70059f0000-7f70059f1000 rw-p 00000000 00:00 0 7f70059f1000-7f7005a0d000 r-xp 00000000 08:01 923645 /usr/local/lib64/kamailio/modules/db_unixodbc.so 7f7005a0d000-7f7005c0c000 ---p 0001c000 08:01 923645 /usr/local/lib64/kamailio/modules/db_unixodbc.so 7f7005c0c000-7f7005c0d000 rw-p 0001b000 08:01 923645 /usr/local/lib64/kamailio/modules/db_unixodbc.so 7f7005c0d000-7f7005c17000 r-xp 00000000 08:01 923745 /usr/local/lib64/kamailio/modules/xlog.so 7f7005c17000-7f7005e16000 ---p 0000a000 08:01 923745 /usr/local/lib64/kamailio/modules/xlog.so 7f7005e16000-7f7005e17000 rw-p 00009000 08:01 923745 /usr/local/lib64/kamailio/modules/xlog.so 7f7005e17000-7f7005e37000 r-xp 00000000 08:01 923729 /usr/local/lib64/kamailio/modules/tmx.so 7f7005e37000-7f7006037000 ---p 00020000 08:01 923729 /usr/local/lib64/kamailio/modules/tmx.so 7f7006037000-7f7006038000 rw-p 00020000 08:01 923729 /usr/local/lib64/kamailio/modules/tmx.so 7f7006038000-7f700603a000 rw-p 00000000 00:00 0 7f700603a000-7f7006050000 r-xp 00000000 08:01 923723 /usr/local/lib64/kamailio/modules/textopsx.so 7f7006050000-7f7006250000 ---p 00016000 08:01 923723 /usr/local/lib64/kamailio/modules/textopsx.so 7f7006250000-7f7006251000 rw-p 00016000 08:01 923723 /usr/local/lib64/kamailio/modules/textopsx.so 7f7006251000-7f700628b000 r-xp 00000000 08:01 923722 /usr/local/lib64/kamailio/modules/textops.so 7f700628b000-7f700648b000 ---p 0003a000 08:01 923722 /usr/local/lib64/kamailio/modules/textops.so 7f700648b000-7f700648c000 rw-p 0003a000 08:01 923722 /usr/local/lib64/kamailio/modules/textops.so 7f700648c000-7f700648d000 rw-p 00000000 00:00 0 7f700648d000-7f70064a7000 r-xp 00000000 08:01 923718 /usr/local/lib64/kamailio/modules/sqlops.so 7f70064a7000-7f70066a6000 ---p 0001a000 08:01 923718 /usr/local/lib64/kamailio/modules/sqlops.so 7f70066a6000-7f70066a8000 rw-p 00019000 08:01 923718 /usr/local/lib64/kamailio/modules/sqlops.so 7f70066a8000-7f70066be000 r-xp 00000000 08:01 923715 /usr/local/lib64/kamailio/modules/sl.so 7f70066be000-7f70068be000 ---p 00016000 08:01 923715 /usr/local/lib64/kamailio/modules/sl.so 7f70068be000-7f70068bf000 rw-p 00016000 08:01 923715 /usr/local/lib64/kamailio/modules/sl.so 7f70068bf000-7f70068ef000 r-xp 00000000 08:01 923714 /usr/local/lib64/kamailio/modules/siputils.so 7f70068ef000-7f7006aef000 ---p 00030000 08:01 923714 /usr/local/lib64/kamailio/modules/siputils.so 7f7006aef000-7f7006af0000 rw-p 00030000 08:01 923714 /usr/local/lib64/kamailio/modules/siputils.so 7f7006af0000-7f7006b09000 r-xp 00000000 08:01 923707 /usr/local/lib64/kamailio/modules/sanity.so 7f7006b09000-7f7006d08000 ---p 00019000 08:01 923707 /usr/local/lib64/kamailio/modules/sanity.so 7f7006d08000-7f7006d09000 rw-p 00018000 08:01 923707 /usr/local/lib64/kamailio/modules/sanity.so 7f7006d09000-7f7006d32000 r-xp 00000000 08:01 923703 /usr/local/lib64/kamailio/modules/rr.so 7f7006d32000-7f7006f32000 ---p 00029000 08:01 923703 /usr/local/lib64/kamailio/modules/rr.so 7f7006f32000-7f7006f33000 rw-p 00029000 08:01 923703 /usr/local/lib64/kamailio/modules/rr.so 7f7006f33000-7f7006fbe000 r-xp 00000000 08:01 923699 /usr/local/lib64/kamailio/modules/pv.so 7f7006fbe000-7f70071be000 ---p 0008b000 08:01 923699 /usr/local/lib64/kamailio/modules/pv.so 7f70071be000-7f70071c2000 rw-p 0008b000 08:01 923699 /usr/local/lib64/kamailio/modules/pv.so 7f70071c2000-7f70071c9000 r-xp 00000000 08:01 923674 /usr/local/lib64/kamailio/libbinrpc.so.0.1 7f70071c9000-7f70073c9000 ---p 00007000 08:01 923674 /usr/local/lib64/kamailio/libbinrpc.so.0.1 7f70073c9000-7f70073ca000 rw-p 00007000 08:01 923674 /usr/local/lib64/kamailio/libbinrpc.so.0.1 7f70073ca000-7f70073d1000 r-xp 00000000 08:01 923677 /usr/local/lib64/kamailio/modules/mi_rpc.so 7f70073d1000-7f70075d1000 ---p 00007000 08:01 923677 /usr/local/lib64/kamailio/modules/mi_rpc.so 7f70075d1000-7f70075d2000 rw-p 00007000 08:01 923677 /usr/local/lib64/kamailio/modules/mi_rpc.so 7f70075d2000-7f70075ed000 r-xp 00000000 08:01 923673 /usr/local/lib64/kamailio/modules/mi_fifo.so 7f70075ed000-7f70077ed000 ---p 0001b000 08:01 923673 /usr/local/lib64/kamailio/modules/mi_fifo.so 7f70077ed000-7f70077ee000 rw-p 0001b000 08:01 923673 /usr/local/lib64/kamailio/modules/mi_fifo.so 7f70077ee000-7f70077f4000 r-xp 00000000 08:01 923670 /usr/local/lib64/kamailio/modules/maxfwd.so 7f70077f4000-7f70079f4000 ---p 00006000 08:01 923670 /usr/local/lib64/kamailio/modules/maxfwd.so 7f70079f4000-7f70079f5000 rw-p 00006000 08:01 923670 /usr/local/lib64/kamailio/modules/maxfwd.so 7f70079f5000-7f7007a76000 r-xp 00000000 08:01 918696 /lib/x86_64-linux-gnu/libm-2.13.so 7f7007a76000-7f7007c75000 ---p 00081000 08:01 918696 /lib/x86_64-linux-gnu/libm-2.13.so 7f7007c75000-7f7007c76000 r--p 00080000 08:01 918696 /lib/x86_64-linux-gnu/libm-2.13.so 7f7007c76000-7f7007c77000 rw-p 00081000 08:01 918696 /lib/x86_64-linux-gnu/libm-2.13.so 7f7007c77000-7f7007c87000 r-xp 00000000 08:01 923646 /usr/local/lib64/kamailio/libsrutils.so.1.0 7f7007c87000-7f7007e86000 ---p 00010000 08:01 923646 /usr/local/lib64/kamailio/libsrutils.so.1.0 7f7007e86000-7f7007e87000 rw-p 0000f000 08:01 923646 /usr/local/lib64/kamailio/libsrutils.so.1.0 7f7007e87000-7f7007e99000 r-xp 00000000 08:01 923665 /usr/local/lib64/kamailio/modules/kex.so 7f7007e99000-7f7008098000 ---p 00012000 08:01 923665 /usr/local/lib64/kamailio/modules/kex.so 7f7008098000-7f700809a000 rw-p 00011000 08:01 923665 /usr/local/lib64/kamailio/modules/kex.so 7f700809a000-7f70080e3000 r-xp 00000000 08:01 923565 /usr/local/lib64/kamailio/modules/ctl.so 7f70080e3000-7f70082e2000 ---p 00049000 08:01 923565 /usr/local/lib64/kamailio/modules/ctl.so 7f70082e2000-7f70082e3000 rw-p 00048000 08:01 923565 /usr/local/lib64/kamailio/modules/ctl.so 7f70082e3000-7f70082f4000 rw-p 00000000 00:00 0 7f70082f4000-7f7008303000 r-xp 00000000 08:01 923561 /usr/local/lib64/kamailio/modules/corex.so 7f7008303000-7f7008503000 ---p 0000f000 08:01 923561 /usr/local/lib64/kamailio/modules/corex.so 7f7008503000-7f7008504000 rw-p 0000f000 08:01 923561 /usr/local/lib64/kamailio/modules/corex.so 7f7008504000-7f700850c000 r-xp 00000000 08:01 923544 /usr/local/lib64/kamailio/libkmi.so.1.0 7f700850c000-7f700870b000 ---p 00008000 08:01 923544 /usr/local/lib64/kamailio/libkmi.so.1.0 7f700870b000-7f700870c000 rw-p 00007000 08:01 923544 /usr/local/lib64/kamailio/libkmi.so.1.0 7f700870c000-7f700871b000 r-xp 00000000 08:01 923559 /usr/local/lib64/kamailio/modules/cfgutils.so 7f700871b000-7f700891a000 ---p 0000f000 08:01 923559 /usr/local/lib64/kamailio/modules/cfgutils.so 7f700891a000-7f700891b000 rw-p 0000e000 08:01 923559 /usr/local/lib64/kamailio/modules/cfgutils.so 7f700891b000-7f7008928000 r-xp 00000000 08:01 923533 /usr/local/lib64/kamailio/libkcore.so.1.0 7f7008928000-7f7008b27000 ---p 0000d000 08:01 923533 /usr/local/lib64/kamailio/libkcore.so.1.0 7f7008b27000-7f7008b28000 rw-p 0000c000 08:01 923533 /usr/local/lib64/kamailio/libkcore.so.1.0 7f7008b28000-7f7008b54000 r-xp 00000000 08:01 923529 /usr/local/lib64/kamailio/libsrdb1.so.1.0 7f7008b54000-7f7008d53000 ---p 0002c000 08:01 923529 /usr/local/lib64/kamailio/libsrdb1.so.1.0 7f7008d53000-7f7008d54000 rw-p 0002b000 08:01 923529 /usr/local/lib64/kamailio/libsrdb1.so.1.0 7f7008d54000-7f7008d97000 r-xp 00000000 08:01 923543 /usr/local/lib64/kamailio/modules/avpops.so 7f7008d97000-7f7008f97000 ---p 00043000 08:01 923543 /usr/local/lib64/kamailio/modules/avpops.so 7f7008f97000-7f7008f98000 rw-p 00043000 08:01 923543 /usr/local/lib64/kamailio/modules/avpops.so 7f7008f98000-7f7008f99000 rw-p 00000000 00:00 0 7f7008f99000-7f7008fb6000 r-xp 00000000 08:01 923542 /usr/local/lib64/kamailio/modules/avp.so 7f7008fb6000-7f70091b5000 ---p 0001d000 08:01 923542 /usr/local/lib64/kamailio/modules/avp.so 7f70091b5000-7f70091b6000 rw-p 0001c000 08:01 923542 /usr/local/lib64/kamailio/modules/avp.so 7f70091b6000-7f70092c4000 r-xp 00000000 08:01 923727 /usr/local/lib64/kamailio/modules/tm.so 7f70092c4000-7f70094c3000 ---p 0010e000 08:01 923727 /usr/local/lib64/kamailio/modules/tm.so 7f70094c3000-7f70094c7000 rw-p 0010d000 08:01 923727 /usr/local/lib64/kamailio/modules/tm.so 7f70094c7000-7f7009cdb000 rw-p 00000000 00:00 0 7f7009cdb000-7f7009e5c000 r-xp 00000000 08:01 918702 /lib/x86_64-linux-gnu/libc-2.13.so 7f7009e5c000-7f700a05c000 ---p 00181000 08:01 918702 /lib/x86_64-linux-gnu/libc-2.13.so 7f700a05c000-7f700a060000 r--p 00181000 08:01 918702 /lib/x86_64-linux-gnu/libc-2.13.so 7f700a060000-7f700a061000 rw-p 00185000 08:01 918702 /lib/x86_64-linux-gnu/libc-2.13.so 7f700a061000-7f700a066000 rw-p 00000000 00:00 0 7f700a066000-7f700a079000 r-xp 00000000 08:01 918715 /lib/x86_64-linux-gnu/libresolv-2.13.so 7f700a079000-7f700a278000 ---p 00013000 08:01 918715 /lib/x86_64-linux-gnu/libresolv-2.13.so 7f700a278000-7f700a279000 r--p 00012000 08:01 918715 /lib/x86_64-linux-gnu/libresolv-2.13.so 7f700a279000-7f700a27a000 rw-p 00013000 08:01 918715 /lib/x86_64-linux-gnu/libresolv-2.13.so 7f700a27a000-7f700a27c000 rw-p 00000000 00:00 0 7f700a27c000-7f700a27e000 r-xp 00000000 08:01 918708 /lib/x86_64-linux-gnu/libdl-2.13.so 7f700a27e000-7f700a47e000 ---p 00002000 08:01 918708 /lib/x86_64-linux-gnu/libdl-2.13.so 7f700a47e000-7f700a47f000 r--p 00002000 08:01 918708 /lib/x86_64-linux-gnu/libdl-2.13.so 7f700a47f000-7f700a480000 rw-p 00003000 08:01 918708 /lib/x86_64-linux-gnu/libdl-2.13.so 7f700a480000-7f700a4a0000 r-xp 00000000 08:01 918714 /lib/x86_64-linux-gnu/ld-2.13.so 7f700a68b000-7f700a68c000 rw-s 00000000 00:04 0 /SYSV790116c2 (deleted) 7f700a68c000-7f700a68d000 rw-s 00000000 00:04 0 /SYSV790116c2 (deleted) 7f700a68d000-7f700a68e000 rw-s 00000000 00:04 0 /SYSV790116c2 (deleted) 7f700a68e000-7f700a695000 r--s 00000000 08:01 784486 /usr/lib/x86_64-linux-gnu/gconv/gconv-modules.cache 7f700a695000-7f700a698000 rw-p 00000000 00:00 0 7f700a698000-7f700a699000 rw-s 00000000 00:04 0 /SYSV790116c2 (deleted) 7f700a699000-7f700a69a000 rw-s 00000000 00:04 0 /SYSV790116c2 (deleted) 7f700a69a000-7f700a69b000 rw-s 00000000 00:04 0 /SYSV790116c2 (deleted) 7f700a69b000-7f700a69c000 rw-s 00000000 00:04 0 /SYSV790116c2 (deleted) 7f700a69c000-7f700a69f000 rw-p 00000000 00:00 0 7f700a69f000-7f700a6a0000 r--p 0001f000 08:01 918714 /lib/x86_64-linux-gnu/ld-2.13.so 7f700a6a0000-7f700a6a1000 rw-p 00020000 08:01 918714 /lib/x86_64-linux-gnu/ld-2.13.so 7f700a6a1000-7f700a6a2000 rw-p 00000000 00:00 0 7ffe7071f000-7ffe70740000 rw-p 00000000 00:00 0 [stack] 7ffe707bb000-7ffe707bc000 r-xp 00000000 00:00 0 [vdso] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall] 13(9728) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 16 0(9715) ALERT: <core> [main.c:784]: handle_sigs(): child process 9724 exited by a signal 6 0(9715) ALERT: <core> [main.c:787]: handle_sigs(): core was not generated 0(9715) INFO: <core> [main.c:799]: handle_sigs(): terminating due to SIGCHLD 12(9727) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 8(9723) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 4(9719) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 7(9722) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 3(9718) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 10(9725) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 2(9717) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 5(9720) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 1(9716) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 13(9728) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 6(9721) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 11(9726) INFO: <core> [main.c:850]: sig_usr(): signal 15 received 0(9715) ERROR: ctl [ctl.c:382]: mod_destroy(): ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: Operation not permitted (1)

2 9

Nonce lifetime in RADIUS auth module
by Måns Nilsson 31 Mar '15

31 Mar '15

Hi, I have a problem with stale nonces being reused by a UA. I'd like to do two things; * Set the nonce lifetime to a lower value * Handle stale nonces in my authentication route For the first, I'm interpreting the RADIUS module documentation so that it gets such parameters from the generic auth module and, therefore, I should be good with something like: ... modparam("auth", "nonce_expire", 60) # Set nonce_expire to 60s ... For the second, I'd appreciate pointers on how to set stale=true in the 401 reply, if special handling is required. I have incomplete packet traces to work from right now, so can't tell if it is being set already. Thanks, -- Måns Nilsson primary/secondary/besserwisser/machina MN-1334-RIPE +46 705 989668 I'm wearing PAMPERS!!

1 0

htable persistation question
by Attila Megyeri 31 Mar '15

31 Mar '15

Hi, We are having problem with persisting htable. There are 4 hashtables defined in kamailio config, like: modparam("htable", "db_url", DBURL) modparam("htable", "htable", "vtp=>size=10;autoexpire=120;dbtable=htable;dbmode=1;") modparam("htable", "htable", "a=>size=6;") modparam("htable", "htable", "rpn=>size=10;autoexpire=0;dbtable=htable;dbmode=1;"); modparam("htable", "htable", "rpnn=>size=10;autoexpire=0;dbtable=htable;dbmode=1;"); The strange behavior is that if I restart kamailio, the hash table is not persisted into the database. If I change e.g. rpn's dbtable to e.g. htable_1 (which should be created in the kamailio mysql database schema upfront, then the rpn hashtable will be presisted successfully at every stop and will be reload at every start. What is wrong in my config? Kamailio version is 4.2.3 Thanks, Attila

2 2

Share location table 3.x 4.x
by Jon Bonilla (Manwe) 31 Mar '15

31 Mar '15

Hi all I'm sharing a location table between two kamailio 3.3 and kamailio 4.2 servers. Table versions are 5 and 6 but I don't know how to skip table version checking to prevent one of them from running. Any tips? thanks, Jon

2 2

keep Kamailio running
by Mihaly Zachar 31 Mar '15

31 Mar '15

Hi All, As far as I can see if a child dies due to segmentation fault Kamailio stops all the childs and it exits. Is there a possibility to change this behaviour to a kind of "respawn the child" way ? What do you think is the best way to keep Kamailio running on Ubuntu ? On RHEL ? Thanks, Misi

4 4

please help
by mail＠sathees.co.uk 31 Mar '15

31 Mar '15

Hi, I’m trying to setup kamailio as proxy to asterisk. Asterisk server running on public IP. I want to hide the asterisk behind kamailio. UAC à Kamailio à Asterisk media services à PSTN PSTN à Asterisk media services à Kamailio à UAC I like to use dispatcher or load balancer modules. I have tried Kamailio 4.0.x and Asterisk 11.3.0 Real time Integration no luck. Can some mail me working scripts or some sort of idea? Appreciate. Sathees

2 1

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