sr-users

sr-users@lists.kamailio.org

20 participants
37472 discussions

LCR in openser 1.2 - is it possible to disable a gateway?
by Iñaki Baz Castillo 24 Apr '10

24 Apr '10

Hi, I need to add LCR support to an existing OpenSer 1.2 server (not possible to upgrade it for now). I've realized that 1.2 doesn't include gateways monitorize feature. Ok, I can do the check with an external tool, but I would like some way to dissable such gw from the LCR module, something like upgrading the gw table and performing the MI reload function. But I don't see how to set in the gw table that such gateway is disabled. Is it possible? Thanks. -- Iñaki Baz Castillo <ibc(a)aliax.net>

2 1

Solutions to missing BYEs, accounting for them
by Alex Balashov 23 Apr '10

23 Apr '10

Hi all, Please forgive the slightly long post, but if you have anything to contribute on this topic, please consider giving it a read as I could really use your input. :-) As I'm sure many others of you running proxy-based service delivery platforms of some description also, I am faced with the problem of trying to account for calls with missing BYEs in a realistic way. There is no shortage of mailing list posts over the years on this topic. Inevitably, in a platform with sufficient call volume, with some NAT'd and/or endpoint diversity and other technical causes, there will be some calls that are never officially terminated from the point of view of a proxy. The ability of the 'dialog' module to spoof bidirectional BYEs on timeout[1] goes a long way toward addressing this problem theoretically. However, there are practical obstacles to relying on it solely as a solution, mainly because there is not an acceptable timeout value to use as a trade-off. If the timeout period is set to a very low value, users will obviously complain, and in any case, depending on the destination, the worst-case scenario for maximum call billing may still be far too high. If the timeout period is set high--perhaps something like 5-8 hours--then all calls that fail to end in the normal way will be billed some excessively large amount that certainly will not sit well with users either. If either the core delivery element of the platform or the user agent is tightly controlled by the operator of the proxy from an administrative point of view, it is indeed probably possible to rely on RTP timeouts or SIP Session Timers (SSTs) on one of the endpoints. That doesn't create a satisfying resolution for those of us dealing with indeterminate call completion scenarios with a great deal of user and vendor diversity, though. For instance, I route to about 15 ITSPs and carriers; I think maybe one of them does 15-minute SSTs, and the rest are certainly not going to turn them on just for me, even if their SBCs/switches/things have the capability. The user endpoints are mostly Asterisk and do RTP timeout, of course, and in most cases I do get the resulting BYE. However, this discussion is about the minute but nontrivial percentage of cases in which I do not get the BYE, whether because of NAT statekeeping problems or network reachability or whatever underlying causes--in truth, I cannot accurately characterise these. So, it seems to me that from a theoretical point of view, there are basically two directions someone in this position can go from here: 1) Inline B2BUA in the signaling path of all calls; 1a) Make it do SSTs; or 1b) Make it relay media, too, and hang up the call (bidirectional BYE) on RTP receive timeout; 2) Couple the proxy to an RTP relay and provide some mechanism by which the proxy can be made aware, in an asynchronous fashion, that an RTP timeout was detected by the relay. It seems to me from a brief and informal survey of prior mailing list literature that #1 is the usually recommended option here. If #1 is pursued, what is the best tool to use in the Kamailio/SIP-Router-oriented ecosystem? My default instinct would say SEMS; I really like SEMS, and use it a lot for various related chores. The problem is that the pre-built modules and examples for SEMS mostly center on application-level functionality, while low-level documentation of its powerful C++ API is a bit impoverished, so this would take a lot of work. Needless to say, I am interested in the option that requires the least work but still solves the problem in an elegant way from a technical and--dare I say--aesthetic perspective. For instance, it seems clear from looking at the SEMS-1.1.1 sources that SSTs are supported in principle in core/plug-in/session_timer. But unless I am missing something, I cannot find anywhere in the sources or examples where it is actually used. So, I suppose one option is to figure out how to make this stuff work in SEMS, and make it work. But for some reason who is not attune to the universe of its C++ API, it is a rather formidable chore. I think the same would hold true of making it observe bidirectional RTP timeout. Turning attention to option #2, I have looked at rtpproxy (my preferred default), iptrtpproxy, and mediaproxy modules but have not found any evidence that the control protocols Kamailio/SR uses to engage them support any notion of backward asynchronous feedback in case of RTP timeout. It would be really nice if one of these stream control protocols was augmented to kick back a packet to Kamailio that can be caught in a special event_route, like event_route[nathelper:rtp-stream-timeout], but that is clearly not the case today. To be honest, I would not use MediaProxy even if it had this feature, because, well, let's be bluntly honest and acknowledge what the more politically aware presumably already conjecture: in light of AG Projects' zealous OpenSIPS partnership, it's difficult to muster confidence in future compatibility of MediaProxy with Kamailio. The module is there, it works, and I'm sure its maintainers are dedicated to doing whatever it takes to reverse engineer and keep it working, lift patches from OpenSIPS as necessary, etc., but who wants to be on the wrong side of the project ecosystem fence? Not I. That leaves iptrtpproxy, whose 'switchboard' concept I do not fully comprehend due to lack of experience with it, but which holds a potentially viable, if slightly kludgy/Rube Goldbergian answer. Of the three RTP proxies, it is the only one that provides a ready means of exporting a list of media streams it is currently tracking, together with statistics on how many packets have been received, etc. It is not inconceivable to cook up an external process that will frequently check this 'switchboard', as it were, and incite Kamailio/SR to do dlg_bye() via MI if it appears that the media stream has disappeared from either side; the dialog module helpfully exports the MI command dlg_end_dlg. Still, this does not seem nearly as parsimonious and reliable a solution as simply building some kind of RTP stream leg timeout notification into the control socket. After all, the control socket is open persistently, right, not on-demand? The various RTP proxies all seem to have some kind of dead peer detection internally in order to have some means of gracefully expiring resources allocated to media streams that have gone away, so it would just be a matter of passing a control frame up the socket to Kamailio/SR and wiring that to a custom event_route or a more static callback in the code. By the way, I should mention that I am aware of and historically very sympathetic to the perspective that this kind of call control is alien to the nature of a proxy, and an appropriate job for UAs and not proxies at all. However, we all have to make pragmatic concessions to the realities of real-world operation, which I assume is the motivation for dialog timeouts, dlg_bye(), and other perversions from the point of view of a purist. :-) I welcome your thoughts and suggestions about the easiest and most technically meritorious approach. Thanks, -- Alex [1] Enabled via $dlg_ctx(timeout_bye) = 1 -- Alex Balashov - Principal Evariste Systems LLC 1170 Peachtree Street 12th Floor, Suite 1200 Atlanta, GA 30309 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/

6 29

MI functions
by Hector.Ortiz＠swisscom.com 23 Apr '10

23 Apr '10

Hi everyone, In the page where a module is described, there is a list of dependencies that have to be met in order to use the module, the list of exported parameters that might need to be set in the configuration file and a list of exported functions which can be used in the configuration script. I've noticed as well, that there are some "Exported MI functions" but I was wondering if any of you know what the purpose of those functions is, where and how such functions could be used? Thanks Héctor

2 1

Error with Presence: no shmem
by Tristan Mahé 23 Apr '10

23 Apr '10

Hi List, I'm writing a little message because I encountered today a strange error on my Kamailio 3.0 proxy/presence server ( and can't ask on IRC there's nobody atm ;p ) I get these errors in the logs since a few hours: Apr 23 14:31:41 proxy-b /proxy/bin/kamailio/sbin/kamailio[29008]: ERROR: tm [t_msgbuilder.c:1371]: build_uac_req(): no shmem Apr 23 14:31:41 proxy-b /proxy/bin/kamailio/sbin/kamailio[29008]: ERROR: tm [uac.c:327]: t_uac: Error while building message Apr 23 14:31:41 proxy-b /proxy/bin/kamailio/sbin/kamailio[29008]: ERROR: presence [notify.c:1577]: in function tmb.t_request_within Apr 23 14:31:41 proxy-b /proxy/bin/kamailio/sbin/kamailio[29008]: ERROR: presence [notify.c:1673]: sending Notify not successful Apr 23 14:31:41 proxy-b /proxy/bin/kamailio/sbin/kamailio[29008]: ERROR: presence [notify.c:1348]: Could not send notify for dialog That prevents NOTIFYs from being sent, but I can also see sometimes NOTIFYs get sent without theses errors. The strange thing is that the error indicate no shared memory, but on the server, I'm far from being memless (16G total RAM, 4G free not even used for cache ). I have presence, presence_xml, presence_dialoginfo, pua, pua_dialoginfo and pua_bla loaded. Anyone got an idea on where to look ? Regards, Gled.

2 1

[Kamailio-Users] How can i install and configuration CDRTool + Freeradius + mediaproxy + kamailio
by RAJNIKANT VANZA 23 Apr '10

23 Apr '10

Hi All, I would like to use CDRTool for accounting and integrate with kamailio + mediaproxy + freeradius. so, please let me know about configuration or installation steps for CDRToolon centos-5.X os. I have followed this link for CDRTool configuration http://cdrtool .ag-projects.com/wiki/Install but not success and confused. I have seen above url for CDRTool that provides information for deban os. but i want to install on centos. I am installed and run kamailio and mediaproxy successful. I am confused about compile or install about CDRTool and i want to help about Freeradius integration with kamailo and CDRTool. Thanks in advance. -- Best Regards, Rajnikant

3 2

possible bug with dialog module
by Kelvin Chua 23 Apr '10

23 Apr '10

currently using kamailio 3.0 with around 1000 users. Apr 21 10:19:57 kamvm-1 /usr/local/sbin/kamailio[28511]: ERROR: dialog [dlg_handlers.c:218]: bad sip message or missing Contact hdr Apr 21 10:19:57 kamvm-1 /usr/local/sbin/kamailio[28511]: ERROR: dialog [dlg_handlers.c:350]: could not add further info to the dialog Apr 21 10:19:57 kamvm-1 kernel: kamailio[28511]: segfault at 0000000000000088 rip 00002ab61b62779a rsp 00007fffec157440 error 4 Apr 21 10:19:57 kamvm-1 /usr/local/sbin/kamailio[28507]: ALERT: <core> [main.c:722]: child process 28511 exited by a signal 11 Apr 21 10:19:57 kamvm-1 /usr/local/sbin/kamailio[28507]: ALERT: <core> [main.c:725]: core was generated Kelvin Chua

4 20

new features: write access to branch attributes
by Daniel-Constantin Mierla 22 Apr '10

22 Apr '10

Hello, yesterday I committed to git new feature that allow write access to branch attributes. It is about branches kept in core before TM takes over and creates the branches for transaction. These branches are filled when you do location lookup, alias db lookup or append_branch in route block. You can update the attributes: - r-uri - outbound proxy address (dst uri) - path - q value - local socket to be used for sending - branch flags More at: http://sip-router.org/wiki/cookbooks/pseudo-variables/devel#branch_attribut… The access can be done with index, 0 is the first. Negative value of index starts counting from the last, therefore index -1 is the last branch. If the index is missing, then first branch is used. Adding a new branch can be done with km_append_branch(...) of kex module or append_branch() functions. Dropping a branch is by assigning $null to uri attribute of branch. Among benefits: - drop invalid branches before creating the transaction - you can lookup the aor from branches in location table, avoiding a loopback of a branch (e.g., for alias db case) Cheers, Daniel -- Daniel-Constantin Mierla * http://www.asipto.com/ * http://twitter.com/miconda * http://www.linkedin.com/in/danielconstantinmierla

2 1

Catching internally generated BYE event & other
by Alex Balashov 21 Apr '10

21 Apr '10

Hello, I am using the dialog module to time out excessively long calls: modparam("dialog", "default_timeout", 21600) # 6 hours modparam("dialog", "dlg_flag", 2) ... route { ... ... setflag(2); $dlg_ctx(timeout_bye) = 2; ... ... if(!t_relay()) sl_reply_error(); } I have two unrelated questions: 1) Why does $dlg_ctx(timeout_bye) work here? My understanding is that $dlg_ctx(...) is a PV namespace container that exposes some aspect of the allocated dialog tracking structure. The dialog structure is created via a TM->dialog callback triggered by t_relay(); why is it possible to access it prior to that point? 2) The spoofed BYEs that are generated by the proxy with this setting do not show up as sequential requests, nor are catchable in script at all. As a result, BYE events are not written to CDRs with 'acc' and I have no way of knowing when the call actually closed. What is the most efficient and canonical solution to this problem? I can think of two: (a) Define a $dlg_ctx(timeout_route) and have it write a BYE event artificially using acc_db_request(). (b) Loop the BYE request back to the proxy with some sort of differentiating URI parameter or similar that causes it to be dropped instead of forwarded. But this is really nasty. What is your suggestion? Thanks, -- Alex Balashov - Principal Evariste Systems LLC 1170 Peachtree Street 12th Floor, Suite 1200 Atlanta, GA 30309 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/

3 13

Appended headers are not added in serial forking
by Iñaki Baz Castillo 21 Apr '10

21 Apr '10

Hi, I receive a request, append some custom headers and use "load_gws()" (from LCR module). If the first gateway fails I do "next_gw()" and this second request to the second gateway doesn't contain the previously appended custom headers. Is it the expected behavior? -- Iñaki Baz Castillo <ibc(a)aliax.net>

3 6

SQLOps question
by Maciej Bylica 21 Apr '10

21 Apr '10

Hello, I am trying to use SQLOps Module in my kamailio 1.5 configuration. According to your explanations every result of sql_query should be freed just after using that data. So it means that there will be better to fetch for THE SAME data three times instead of just one. Am I right? But nevertheless I've been trying to query just one and free the result of the sql_query at the end of the file. Could sb tell me if the result of sql query executed in the main part of the script is remembered and could be used on failure route as well? Thanks, Maciej.

4 5

Jump to page:

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