Hello,
short note to mark the freezing of development for Kamailio v5.2 series.
For few weeks, please do not push new features in the master branch.
Once the branch 5.2 is created (expected to happen in 3-4 weeks from
now), the master branch becomes again open for new feature. Meanwhile
the focus has to be on testing current code.
Work on related tools (e.g., kamctl) or documentation can still be done
as well as getting the new modules in 5.2 in good shape, plus adding
exports to kemi interface (which should not interfere with old code).
The entire testing phase is expected to be 4 to 6 weeks, then the
release of v5.2.0 will be out.
Cheers,
Daniel
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - www.asipto.com
Kamailio World Conference - www.kamailioworld.com
Hi again,
When acting as an intermediary proxy for a non-colocated Registrar, the
REGISTER request coming in on one port and going out on another, shouldn't
the *add_path[received]()* generate *two* nodes in the Path header?
Otherwise, how are the subsequent requests supposed to be routed back to
the UAC?
Scenario with Kamailio proxy on IP 1.1.1.1 with dual port listeners
UAC => proxy:5070 <=> proxy:5060 => Registrar:5060
Path: <sip:1.1.1.1;lr;received=sip:123.123.123.123:59593>
I would expect it to be something like:
Path: <sip:1.1.1.1;lr>,<sip:1.1.1.1:5070;lr;received=sip:
123.123.123.123:59593>
modparam("rr", "enable_double_rr", 1)
modparam("path", "use_received", 1)
Merci!
Using "Kamailio in a mobile world" as a base, I have the following routes to store information about the current transaction, however, if the transaction is already cancelled registrations for the user will still trigger `ts_append`, raising an error as the htable hasn't expired yet.
Is there anyway to remove the htable entry when the original transaction cancels? Or something else that I'm missing?
Hello,
Kamailio SIP Server v5.1.6 stable release is out.
This is a maintenance release of the latest stable branch, 5.1, that
includes fixes since the release of v5.1.5. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.1.x. Deployments running previous v5.1.x
versions are strongly recommended to be upgraded to v5.1.6.
For more details about version 5.1.6 (including links and guidelines to
download the tarball or from GIT repository), visit:
* https://www.kamailio.org/w/2018/10/kamailio-v5-1-6-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Many thanks to all contributing and using Kamailio!
Cheers,
Daniel
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - www.asipto.com
Kamailio World Conference - www.kamailioworld.com
Hello,
as it was discussed during our last IRC devel meeting before the summer,
the time to release a new major version should be this autumn.
With the Kamailio Developers Meeting planned for September 27-28, 2018,
I think it is better to freeze the code couple of days after that event.
So I propose the following milestones:
* on Thursday, October 4, 2018 - last development day, code for 5.2.0
will be frozen at the end of the day
* 4 to 6 weeks of testing
* release sometime in November, to be decided more precisely after the
first weeks of testing, some rough candidates being within the weeks of
Nov 5 or Nov 19
If anyone has something to add or adjust, let's discuss on sr-users
mailing list.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com
Hello,
a matter of the schedule to be agreed in the morning and the
availability during the Kamailio Developers Meeting, we may do a new
stable release from branch 5.1.6 on Thursday, Sep 27, 2018, in the
afternoon. Given that several of us will be in the same room, the
special goal would be to try to automate the process as much as possible.
If the time doesn't allow it, then the release will be done next week, a
specific day to be decided by the end of this week.
Anyhow, this is the informal notification to report as soon as possible
any issues you are aware of and not yet in bug tracker, so they get a
chance to be fixed.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com
Hi guys!
We have four a scripts that sends dlg.list command to kamailio through
xmlrpc. They are not executed simultaneously. Sometimes, we are getting
the following errors:
fm_search_defrag(): fm_search_defrag(0x7f212c25a000, 5273984); Free
fragment not found!2017-05-26T13:54:20.438736-03:00 drwsip02
/usr/local/sbin/kamailio[19833]: ERROR: <core> [mem/f_malloc.c:498]:
fm_malloc(): fm_malloc(0x7f212c25a000, 5273984) called from core:
tcp_main.c: tcpconn_new(957), module: core; Free fragment not
found!2017-05-26T13:54:20.439101-03:00 drwsip02
/usr/local/sbin/kamailio[19833]: ERROR: <core> [tcp_main.c:959]:
tcpconn_new(): mem. allocation failure2017-05-26T13:54:20.439344-03:00
drwsip02 /usr/local/sbin/kamailio[19833]: ERROR: <core> [tcp_main.c:3985]:
handle_new_connect(): tcpconn_new failed, closing socket
I all ready increased this two variables:
tcp_conn_wq_max=30000000
tcp_rd_buf_size=5273226
How can I see how much memory xmlrpc is using?
Any advice will be appreciated.
Thanks in advance!
Diego
Hi ppl,
If I add a FQDN advertise address to the listen statement, *is_first_hop()
<https://kamailio.org/docs/modules/4.3.x/modules/siputils.html#siputils.f.is…>*
seems to return FALSE no matter how I play with the listen and alias
settings.
listen=udp:1.1.1.1:5060 advertise sip.mydomain.net:5060
alias="sip.mydomain.net:5060"
This statement doesn't get executed in the *onreply_route*
*onreply_route[MANAGE_REPLY] {*
*if(is_first_hop())*
*set_contact_alias(); # contact alias doesn't get set?*
*}*
*is_first_hop()*
*"The function returns true if the proxy is first hop after the original
sender. For incoming SIP replies, it means that top Record-Route URI is
'myself' and source address is not matching it"*
*This is the reply.*
2018/10/03 17:03:38.276846 2.2.2.2:62033 -> 1.1.1.1:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP sip.mydomain.net:5060
;branch=z9hG4bK49b3.bfbe15.0;received=1.1.1.1
Via: SIP/2.0/UDP 10.10.10.10:5060;rport=5060;branch=z9hG4bK1af96136
*Record-Route*: <sip:sip.mydomain.net;lr=on;did=4cc.734>
Contact: <sip:888@10.17.0.35:62033>
Suggestions?
Thanks.
Hi!
I am working successfully with Kamailio in my lab setup where Kamailio is
the SBC for Asterisk.
The network layout is looking like this:
SIP-Phone <== PUBLIC NET ==> Kamailio (SBC) <== PRIVATE NET ==> Asterisk
<== PUBLIC NET ==> Carrier
Each public network is reachable from the internet and has a local firewall
with IP whitelists.
The internal SIP transactions are UDP-only but for external phones I would
like to also listen for TCP/TLS.
For this layout to work with rtpproxy (before we move on to RTPengine), we
have to enable mhomed in Kamailio.
We also have some routing issues with packets leaving with the wrong IP via
rtpproxy (when call between carrier and external phone needs to be bridged).
Most examples show that Asterisk is deployed on the same network as the
external interface of Kamailio (-> Asterisk exposed to the public network).
In our tests, this works much better but I have great security concerns
because this Asterisk instance itself does not need to be reachable from
external.
How do other users deploy Kamailio in front of Asterisk or similar as SBC
to secure internals?
There is lot of docs for Kamailio's config but IMHO less for the setup as
DMZ (SBC) proxy.
Thank you very much.
Kind regards
Kevin
