- sr-users - kamailio.org

Configure(children=x) didn't work
by sgy 31 May '17

31 May '17

HI All, I try to change the value of children in kamailio.cfg, but it didn't work, could you give me some advice, thank you -- Best Regards, Shengy

2 5

dispatcher & failover
by Jean Cérien 31 May '17

31 May '17

Hello I am working with Kamailio 5.0 dispatcher module. I am aiming at having two or more gateways receiving the traffic with load balancing, and when one fails, that the traffic is distributed among others. Currently, testing with 2 gw. I see the options message going out (and not being answered). When I monitor with kamctl dispatcher dump, I never see the faulty gw going inactive (flags remain AP), and calls are still tried to the faulty gw. "Best" result so far is with ds_probing_mode=1, the flags start at AX with both gateway up, then AP once they've replied to an OPTIONS, and even if I stop one, and OPTIONS is no longer replied, it stays at AP. when a call comes through, it is tried on this GW (3 invites), and then fails onto the other one. I was expecting that the gw would not be tried if inactive. Am I missing something ? J. modparam("dispatcher", "db_url", DBURL) modparam("dispatcher", "table_name", "dispatcher") 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:probe@probe") modparam("dispatcher", "ds_ping_reply_codes", "class=2;class=3;class=4;class=5") modparam("dispatcher", "ds_ping_interval", 30) modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_probing_threshold", 3) modparam("dispatcher", "ds_timer_mode", 1)

2 3

How to get modified SDP by RTPProxy
by Albert Petit 31 May '17

31 May '17

Hi list, We are using RTPProxy as media proxy. When doing a SIPcall we would need to know the final ports used by RTPProxy. Hence I would need to access the rewritten SDP of the 200 OK send by our application server. Unfortunately we are not achieving to get that rewritten SDP. I tried calling sdp_print("1") using module sdpops just after calling rtpproxy_offer or rtpproxy_answer in kamailio script. (According the doc those methods do: "Rewrites SDP body to ensure that media is passed through an RTP proxy. To be invoked on INVITE for the cases the SDPs are in INVITE and 200 OK and on 200 OK when SDPs are in 200 OK and ACK".) However the sdp we print just after calling that is still having the original ports set by the AS but not the ports used in the rtpproxy or that we will send to the client in the rewritten SDP What are we doing wrong? Any hint how we can get the rewritten SDP in the 200 OK answer we send to caller side?

2 1

Should a proxy change Contact or From domains?
by Phil Lavin 31 May '17

31 May '17

Hi all, Theoretical question about the role of a Kamailio proxy which is also a registration server for UAs. Assuming a B2BUA on IP 1.2.3.4 behind the Kamailio proxy. Kamailio receives an INVITE from this B2BUA with From and Contact as something like sip:4321@1.2.3.4 When Kamailio routes the INVITE to that UA, is it Kamailio’s responsibility to change the domain part of the From and/or Contact to itself (e.g. sip:4321@proxy.mytld.com)? The question has arisen from Polycom missed call “call back” behaviour. When issuing a call back from a Polycom, following a missed call, it sends the call directly to the full URI in the INVITE’s From (or maybe Contact… I’ve not fully tested yet). As such the call is sent to the B2BUA, which UAs do not have access to, and thus times out. I suspect here the answer is “no”, and the Polycom must be configured to force all outbound calls through the proxy… but thoughts welcome. Cheers Phil

2 1

Is it possible to replace Request-URI in the REGISTERs with the result of dispatcher?
by 刘鲲 31 May '17

31 May '17

Hello, I build three kamailioes, one acts as a pass-through proxy as well as load-balancing, the two registrars. The kamailio_1 decides to which registrar the REGISTER should forward by a dispatcher based on db_text. ----->kamailio_2(IP2, registrar) SoftPhone--->kamailio_1(IP1, pass-through proxy)--| | ----->kamailio_3(IP3, registrar) | dispatcher(db_text) I expect the kamailio_1 forward the REGISTERs to kamailio_2/kamailio_3, and kamailio_2/kamailio_3 respond with 200 OK. But in fact, the registrars send the REGISTER back to kamailio_1. I think the reason is that the host part of Request-URI in REGISTER from SoftPhone is IP1, and kamailio_1 does not rewrite it as a pass-through proxy, so kamailio_2/kamailio_3 will find the host in Request-URI is not mine, thus route the REGISTER back to kamailio_1 according Request-URI. The setting of SoftPhone cannot be changed, so is it possible to : 1) replace host part of Request-URI in the REGISTERs with the result of dispatcher in kamailio_1 , or 2) force kamailio_2/kamailio_3 to respond rather than forward? Thanks!

2 1

push notification
by volga629＠networklab.ca 30 May '17

30 May '17

Hello Everyone, Trying understand how push notification works based on Daniel example in 2014 Code in question: if(lua_runstring("do_push([[$hdr(X-VxTo)]], [[$tU]], [[$hdr(X-VxFrom)]], [[$fU]], [[$ci]])")<0) { send_reply("501", "No link to destination"); exit; } I understand how string should look like, but lua give this error ERROR: app_lua [app_lua_api.c:607]: app_lua_runstring(): lua loading state not initialized (call: do_push([[<null>]], [[4310]], [[<null>]], [[4311]], [[dd4cb9b2-bf21-1235-05b5-5254003e39bb]])) Is possible clarify how this part should work ? volga629

2 5

kamctl v5 issues sending rpc raw commands
by José Seabra 30 May '17

30 May '17

Hello there, I'm trying to use the following command: *kamctl rpc get_statistics usrloc::registered_users* and i'm getting the following errors: { "jsonrpc": "2.0", "error": { "code": -32000, "message": "Execution Error" }, "id": 12006 } ERROR: jsonrpcs [jsonrpcs_mod.c:1323]: jsonrpc_exec_ex(): method callback not found [get_statistics] Question here is: This rpc raw command isn't available on new kamctl v5? or i have to call this in a different way? Thank you Regards José Seabra

3 4

How to disable proxy function of kamailio
by sgy 30 May '17

30 May '17

Hi anyone, Kamailio server receive a register packet, but IP addr of request line is not same with addr of kamailio server ,then ther server will transfer it out. Now I want kamailio server process it as it receive a register itsself. So how do I close proxy function of kamailio server. For Example: Receive packet: ======================================== REGISTER sip:113.80.5.159:9198 SIP/2.0 kamailio server: 222.222.1.2 -- Best Regards, Shengy

3 2

Kamailio start failed
by sgy 29 May '17

29 May '17

Hi anyone, I can't start kamailio, Please help me Log: 1. ~# kamctl start database engine 'MYSQL' loaded Control engine 'RPCFIFO' loaded INFO: Starting Kamailio : ERROR: PID file /var/run/kamailio/kamailio.pid does not exist -- Kamailio start failed 2. :~# kamailio -M 8 -E -e -dd 0(1685) DEBUG: <core> [core/route_struct.c:129]: mk_action(): ACTION_#24 #1/2: 3(3)/ (nil) 0(1685) DEBUG: <core> [core/sr_module.c:694]: find_mod_export_record(): find_export_record: found <t_is_canceled> in module tm [/usr/local/lib64/kamailio/modules/tm.so] 0(1685) DEBUG: <core> [core/route_struct.c:129]: mk_action(): ACTION_#2 #0/2: 3(3)/ 0x1 0(1685) DEBUG: <core> [core/route_struct.c:129]: mk_action(): ACTION_#2 #1/2: 3(3)/ 0x1 0(1685) DEBUG: <core> [core/route_struct.c:129]: mk_action(): ACTION_#16 #0/3: 22(16)/ 0x7f634f00f780 0(1685) DEBUG: <core> [core/route_struct.c:129]: mk_action(): ACTION_#16 #1/3: 8(8)/ 0x7f634f00feb0 0(1685) DEBUG: <core> [core/route_struct.c:129]: mk_action(): ACTION_#16 #2/3: 0(0)/ 0x7f6300000000 0(1685) DEBUG: <core> [core/route.c:129]: route_add(): mapping routing block (0xafc160)[MANAGE_FAILURE] to 1 ERROR: bad config file (1 errors) 0(1685) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized -- Best Regards, Shengy

3 7

Fwd: questions about FL_RPL flag in dmq_usrloc
by 张顺通 27 May '17

27 May '17

In dmq_usrloc, a ucontact_t with FL_RPL flag will not send it's modify to other kamailio. For example, I have one edge and three kamailio(for register, name A B C). And First SIP REGISTER send to edge, and edge forward to register kamailio A, then kamailio B & C have FL_RPL flag, kamailio A do not have FL_RPL flag. In this situation, If kamailio A is crash, the second SIP REGISTER(same call-id and tag) forward to kamailio B, kamailio B will not replicate reg info to C, because kamailio B have FL_RPL flag. What is the suggestion in this case? Thanks

3 6

mod.stats rpc call crashes
by Andy 26 May '17

26 May '17

Hi, I see kamailio crashing on a call to possibly (mod.stats rpc call), @function __strcmp_sse42 probably is referencing null, which is passed mname and pointer to mname. backtrace: thanks a lot. -- View this message in context: http://sip-router.1086192.n5.nabble.com/mod-stats-rpc-call-crashes-tp158967… Sent from the Users mailing list archive at Nabble.com.

2 4

question about cseq handling
by 张顺通 26 May '17

26 May '17

In urecord.c:get_ucontact_by_instance, REGISTER without instance-id will check cseq number(must be higher), REGISTER with instance-id will not check cseq number. what is the difference?why not check cseq in REGISTER with instance-id? Thanks

2 1

Some Errors
by Douglas Girard 25 May '17

25 May '17

Hello, I am using a fresh install of centos 7, homer (using install script) and kamailio (installed with homer script). After modifying kamailio.cfg file with correct DB username, password and Server IP, i am able to start and stop kamailio service. Now my issue is that I have begun to duplicate SIP messages from my PBX, but am receiving these and other errors from kamailio: May 25 12:44:20 localhost.localdomain homer[14456]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Data too long for column 'msg' at row 1 (1406) May 25 12:44:20 localhost.localdomain homer[14456]: ERROR: <core> [db_query.c:235]: db_do_insert_cmd(): error while submitting query and: May 25 12:44:42 localhost.localdomain homer[14456]: ERROR: <core> [receive.c:173]: receive_msg(): core parsing of SIP message failed ( 10.3.3.24:51553/1) May 25 12:45:12 localhost.localdomain homer[14460]: ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) Any suggestions? Thanks!

1 0

Dialog module timeout behaviours
by Alex Balashov 25 May '17

25 May '17

Hello, I'm running 4.3.5:1b0c0a and have run into two distinct, bizarre issues with the dialog module that I am unable to explain. In all cases, I am using $dlg_ctx(send_bye) = 1, and passing in a dialog timeout of 7200 sec via AVP (timeout_avp modparam). 1) Local BYEs are sent after either ~60 or ~120 sec -- This happens on a very small number of answered calls for no apparent reason. I have spent days poring through the traces trying to figure out if there's anything eccentric about how the messages, but can't find anything out of the ordinary except (a) 1 retransmission of 200 OK to INVITE due to not receiving ACK fast enough due to end-to-end latency, and (b) consequently, retransmission of ACK. My understanding is that the dialog module does not prophylactically end calls as a response to strange or improper messaging, but only (a) when the dialog timeout is reached or (b) keepalive OPTION pings (if enabled) fail. Keepalive OPTIONS pings are not enabled in these scenarios, and are not sent in the traces. (2) Local BYEs sent in response to race conditions that result in strange dialog state transitions -- There are some calls that look something like: A. Caller INVITEs callee; B. Callee sends progress; C. Callee sends 200 OK answer and immediately sends BYE (e.g. 1 ms later); D. Kamailio receives these nearly simultaneously and forwards the BYE first; E. Caller sends 487 Request Terminated response (processing BYE as if it were CANCEL); F. Kamailio forwards 200 OK back to caller, who ignores it. G. Callee retransmits 200 OK through Kamailio. A few minutes later, Kamailio sends BYE in both directions even though dialog should have been removed from state tracking long ago because of the dispositive 487 reply. ... In particular, I'm curious as to whether there have been any fixes to deal with scenarios like #2 since 4.3.5. I wasn't able to spot any obvious ones in the commit history for the module. I'm also at a complete loss to explain #1. I have traces for all of these scenarios, but would prefer to send privately. Many 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/

2 4

in-dialog contact update before dialog being confirmed
by Jayesh Nambiar 25 May '17

25 May '17

Hello, In a user-user based calling on mobile apps, when the call is connected and the user moves from a Wifi to Mobile data (network change); the device sends a Re-Invite with new contact information and subsequent messages go to appropriate changed contact address. But when the dialog is in say ringing state; and the caller moves from one network to another; what would be an appropriate SIP method to trigger the contact update. My problem is generating a Re-INVITE or an UPDATE before the call is connected is very difficult. What I tried is sending an in-dialog INFO message with new contact address; which gets relayed to the called party and the response for INFO is also properly received on the new contact address. But the subsequent response of the INVITE like a 486 or 200 goes to the original contact only. What would be the best way to update the contact address of a client if I'm maintaining all the dialogs in kamailio. Thanks, - Jayesh

3 4

Dispatcher - no destination sets
by Jean Cérien 24 May '17

24 May '17

Hello I am working with Kamaiio 5.0 on the dispatcher, with the default dispatcher.cfg file ( https://github.com/kamailio/kamailio/blob/master/src/modules/dispatcher/doc… ) I've added via mysql a gateway: mysql> select * from dispatcher \G; *************************** 1. row *************************** id: 1 setid: 1 destination: 192.168.2.20 flags: 0 priority: 0 attrs: description: local gw 1 row in set (0.00 sec) Kamctl sees it correctly: kamctl dispatcher show dispatcher gateways +----+-------+--------------+-------+----------+-------+-------------+ | id | setid | destination | flags | priority | attrs | description | +----+-------+--------------+-------+----------+-------+-------------+ | 1 | 1 | 192.168.2.20 | 0 | 0 | | local gw | +----+-------+--------------+-------+----------+-------+-------------+ Here is the piece of cfg: if(ds_list_exist(1)) { xlog("L_INFO", "----------- data in set 1"); } else { xlog("L_INFO", "----------- NO data in set 1"); } if(!ds_select_dst("1", "4")) { send_reply("404", "No destination"); exit; } Yet, when an INVITE arrives, I get the following errors: DEBUG: dispatcher [dispatcher.c:876]: w_ds_list_exist(): --- Looking for dispatcher set 1 DEBUG: dispatcher [dispatch.c:1314]: ds_list_exist(): -- Looking for set 1 INFO: dispatcher [dispatch.c:1320]: ds_list_exist(): destination set [1] not found INFO: <script>: ----------- NO data in set 1 ERROR: dispatcher [dispatch.c:1679]: ds_select_dst_limit(): no destination sets same result wether I state the dataset as 1 or "1" - Mysql table column type is int(11). What could be wrong ? Thanks for the help J.

3 5

Kamailio 4.4 crashing
by Pete Kelly 24 May '17

24 May '17

Hi I have Kamailio 4.4 proxying a "normal" call and am finding that it is crashing consistently when it tries to proxy the 200OK from a BYE request when dealing with a certain endpoint. The SIP looks very normal to me and I've managed to obtain a trace, full debug logs and a core dump of the issue. I can provide full copies of the files but the interesting parts from the logfile are here: https://pastebin.com/QkwVMxJj bt output from the coredump is here: https://pastebin.com/auNRaeaU Can anyone please advise?

2 1

can kamailio+rtpproxy traversal any kind of nat
by 赵国杰 24 May '17

24 May '17

Hi everyone, Right now I'm running kamailio and rtpproxy on a server behind nat with a public ip. I enabled the advertise address. If i registered two clients via my home wifi or 3g/4g network, then everything's fine. However, if i start the two clients via my office wifi, two clients can calll each other but with no audio. Obviously, the rtp media session has trouble traversal the office LAN nat. I have no idea what went wrong. Anyone can point me the right direction? Sincerely, jesse

1 0

tsilo module enhancement
by Jayesh Nambiar 24 May '17

24 May '17

Hello, I see the tsilo module works only with registered contacts using location table. Is there a possibility that the ts_append function can actually take the destination URI as an argument and append branch to respective destination? Basically I want to avoid maintaining location table. In a typical mobile use case, where the incoming call is suspended and a push notification is generated to the called party; the called party generates a REGISTER request with expires header as 0; kamailio just extracts the contact header and sends the call. Problem comes in when the same user receives a PUSH on another device; I cannot figure a neat way to append the same call on the new device. Is there a better alternative to achieve this without looking up the location table. Thanks for any help. - Jayesh

2 2

R-URI for ACK
by David Wilson 24 May '17

24 May '17

Hello All, I’m trying to interop with a provider whose ACK during an inbound call seems to be misrouted. During the INVITE, OK, ACK handshake, my understanding (which matches the examples in RFC 3665) is that the R-URI in the ACK should be the Contact specified in the 200 OK. I have also found multiple discussions that imply that this is necessary. However, I can’t find a convincing normative reference for this... Is there a reference (ideally in RFC 3261) that makes this clear? Cheers, Dave.

1 0

Kamailio and XMLRPC commands with POST
by Olli Attila 24 May '17

24 May '17

Hi, I'm using kamailio 5.0.0 and trying to use core commands through xmlrpc interface but the requests are failing towards Kamailio. I have compiled and enabled the xmlrpc module in config and I have this on my kamailio.cfg: # XMLRPC routing #!ifdef WITH_XMLRPC route[XMLRPC] { # allow XMLRPC from localhost if ((method=="POST" || method=="GET") && (src_ip==127.0.0.1)) { # close connection only for xmlrpclib user agents (there is a bug in # xmlrpclib: it waits for EOF before interpreting the response). if ($hdr(User-Agent) =~ "xmlrpclib") set_reply_close(); set_reply_no_connect(); dispatch_rpc(); exit; } send_reply("403", "Forbidden"); exit; } #!endif I have tried to test this by using curl and calling "core.uptime" method in xml body (core.uptime works when executed through kamcmd commandline tool). The curl is called from the same machine that I have Kamailio installed on: "curl -X POST -H 'Host: 127.0.0.1:5060' -H 'User-Agent: xmlrpcclient' -H 'Content-Type: text/xml' -d '<?xml version='1.0'?><methodCall><methodName>core.uptime</methodName><params></params></methodCall>' http://127.0.0.1:5060" This fails and I only get: "curl: (7) Failed to connect to 127.0.0.1 port 5060: Connection refused" network traffic shows me this.. firewall is disabled completely when doing the test: 1 0.000000 127.0.0.1 -> 127.0.0.1 TCP 74 55630→5060 [SYN] Seq=0 Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=1347930477 TSecr=0 WS=64 2 0.000032 127.0.0.1 -> 127.0.0.1 TCP 54 5060→55630 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0 Can anyone help me to get to the right direction with this? Cheers, --Olli

5 10

rtpengine opening second RTP port
by John Petrini 23 May '17

23 May '17

Hello List, I'm having an issue with rtpengine changing the source port of the RTP stream after receiving a 183 from the carrier. Though RTP engine continues to send RTP to the proper carrier IP and port the carrier drops the inbound audio once the source port changes. Can anyone tell me what might trigger this type of behavior from rtpengine and if it's expected? Thank You, ___ John Petrini

3 3

Missing accounting events in ACC table
by Muhammad Shahzad 23 May '17

23 May '17

Hi, About 3 weeks ago i upgraded one of my production server with latest stable kamailio version 4.2.1-fad00a. Now i am getting a lot of complaints about missing CDR events in ACC table. I observe following problems, 1. There are only BYE records in acc table, no record for INVITE or ACK. 2. In kamailio logs when ACK is received against 200 OK response for INVITE, i see following errors, -- ERROR: <core> [parser/parse_from.c:113]: parse_from_uri(): failed to parse >From uri ERROR: pv [pv_core.c:434]: pv_get_xto_attr(): cannot parse From URI NOTICE: <script>: [udp:<null>@1.0.0.127:5060]: Call from 'you(a)kamailio.org' to 'you(a)kamailio.org' has been hanged up by '<null>' at '1419364717.255484' -- Of course all these errors are bogus, I have checked all headers in ACK (not just FROM header), they all seem perfectly fine and valid. 3. Then the dialog times out, -- WARNING: dialog [dlg_handlers.c:1440]: dlg_ontimeout(): timeout for dlg with CallID '6D8BD23CAC65AE3C1DE1D0B531F87B8CFEAA9CB9' and tags '1D3ECD34F5731AB845BA3064AC95BB2D' '7f55e81e0630-100007f-13c4-6009-2440a4-5fa31570-2440a4' -- 4. Any further sequential requests complain about "unable to find dialog", e.g. -- NOTICE: <script>: Sequencial 'BYE' request received from caller ERROR: uac [replace.c:591]: restore_uri(): new URI [] shorter than old URI [ sip:00xxxxxxxxxx@sip.domain.com] WARNING: dialog [dlg_handlers.c:1174]: dlg_onroute(): unable to find dialog for BYE with route param '5ae1.d595' [7845:22877] -- 5. However the acc record for BYE is written to db and log file, -- NOTICE: acc [acc.c:318]: acc_log_request(): ACC: transaction answered: timestamp=1419364760;method=BYE;from_tag=7f55e81e0630-100007f-13c4-6009-2440a4-5fa31570-2440a4;to_tag=1D3ECD34F5731AB845BA3064AC95BB2D;call_id=6D8BD23CAC65AE3C1DE1D0B531F87B8CFEAA9CB9;code=200;reason=OK;src_user=00xxxxxxxxxx;src_domain= sip.domain.com ;src_ip=xx.xx.xx.xx;dst_ouser=+1xxxxxxxxxx;dst_user=1xxxxxxxxxx;dst_domain=yy.yy.yy.yy -- The same config was working fine with older version 4.2.0-97cab8. The kamailio config i am using is pretty much standard, -- #!define FLT_ACC 1 #!define FLT_ACCMISSED 2 #!define FLT_ACCFAILED 3 #!define FLT_DLG 4 ... modparam("acc", "early_media", 1) modparam("acc", "report_ack", 1) modparam("acc", "report_cancels", 1) modparam("acc", "detect_direction", 1) modparam("acc", "log_flag", FLT_ACC) modparam("acc", "log_missed_flag", FLT_ACCMISSED) modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) # log to db modparam("acc", "db_flag", FLT_ACC) modparam("acc", "db_missed_flag", FLT_ACCMISSED) modparam("acc", "db_url", "DBURL") ... request_route { # per request initial checks route(REQINIT); # NAT detection route(NATDETECT); # handle requests within SIP dialogs route(WITHINDLG); # CANCEL processing if (is_method("CANCEL")) { if (t_check_trans()) { t_relay(); }; exit; }; #### only initial requests (no To tag) #### t_check_trans(); .... # account only INVITEs if (is_method("INVITE")) { setflag(FLT_DLG); # create dialog setflag(FLT_ACC); # do accounting setflag(FLT_ACCFAILED); # ... even if the transaction fails $avp(dlg_timeout) = 60; dlg_manage(); .... } -- Any ideas why its happening? Since it is 3 weeks old so may be problem has already been spotted and fixed by someone else. Otherwise let me know how can i provide more info to help fix this issue. Thank you.

3 11

How to make OutBound calls with kamailio
by sharad tyagi 23 May '17

23 May '17

Hi I am novice to kamailio , I have installed kamailio-4.2.0 and SIREMIS. I have add and registered two IP phones with kamailio these phone able to call each other. How can i make outbound call with that I am using a asterisk server as PSTN Gateway. i am not famalier with kamailio script. Regards Sharad Tyagi SparkTG info Pvt Ltd

4 3

Siremis v4.4.0 Released
by Daniel-Constantin Mierla 23 May '17

23 May '17

Hello, a short note to announce that Siremis v4.4.0 has been released - the web management application for Kamailio. It is supposed to mark the compatibility with Kamailio v4.x series, its future version will target Kamailio v5.0 compatibility. - http://siremis.asipto.com/2017/05/18/siremis-v4-4-0-released/ Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - May 22-24 (USA) - www.asipto.com Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com

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