Hi,
Is it reasonable to assume that the various tcp_* core parameters
(keepalive behaviour, connection limits, buffer sizes, etc.) also
regulate the behaviour of TLS connections, since TLS is encapsulated in
TCP?
--
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/
Hello,
I am looking for a module to block number based on CLID. If the module
allows REG expresions it would really make my day.
I need to block some callers and I would like to use a module and database
to avoid restarting kamailio service everytime a new number appears.
Thank you
Nelson.-
i am monitoring an issue with 5.1.2 where a cancel is not being propagated
after a 183 is received the packet dump doesn't show anything anomalous.
some notes:
1. the invite went out through t_relay(), transaction is tracked
2. cancel is handled this way
if (is_method("CANCEL")) {
xlog("CANCEL received");
if (t_check_trans()) {
route(RELAY);
}
exit;
}
3. if the UAC who is sending the call to kamailio is configured to send
invite with RURI without a port i.e. 14087654321(a)w.x.y.z instead of
14087654321@w.x.y.z:6050, then this does not happen
4. can be argued that this is not an issue, and that the client should just
be configured properly with outbound proxy and ruri without port. but i am
just being difficult here and wanted to understand what is going on with
the matching algo.
TM debug, in case it helps
2018-04-18T07:29:50.984652+00:00 pinkman /usr/sbin/kamailio[17670]: ERROR:
<script>: 100 Trying received
2018-04-18T07:29:50.984746+00:00 pinkman /usr/sbin/kamailio[17670]: DEBUG:
tm [t_reply.c:1263]: t_should_relay_response(): ->>>>>>>>> T_code=100,
new_code=100
2018-04-18T07:29:50.984752+00:00 pinkman /usr/sbin/kamailio[17670]: DEBUG:
tm [t_reply.c:1786]: relay_reply(): branch=1, save=0, relay=-1 icode=0
2018-04-18T07:29:53.564979+00:00 pinkman /usr/sbin/kamailio[17678]: DEBUG:
tm [h_table.c:129]: free_cell_helper(): freeing transaction 0x7f820b6b8a60
from timer.c:651
2018-04-18T07:29:53.752387+00:00 pinkman /usr/sbin/kamailio[17678]: DEBUG:
tm [h_table.c:129]: free_cell_helper(): freeing transaction 0x7f820b6bbcd8
from timer.c:651
2018-04-18T07:29:54.002501+00:00 pinkman /usr/sbin/kamailio[17678]: DEBUG:
tm [h_table.c:129]: free_cell_helper(): freeing transaction 0x7f820b6bf130
from timer.c:651
2018-04-18T07:29:54.184438+00:00 pinkman /usr/sbin/kamailio[17671]: DEBUG:
tm [t_lookup.c:1019]: t_check_msg(): msg (0x7f8212d77e28) id=3 global id=2
T start=0xffffffffffffffff
2018-04-18T07:29:54.184454+00:00 pinkman /usr/sbin/kamailio[17671]: DEBUG:
tm [t_lookup.c:897]: t_reply_matching(): t_reply_matching: hash 6057 label
0 branch 1
2018-04-18T07:29:54.184468+00:00 pinkman /usr/sbin/kamailio[17671]: DEBUG:
tm [t_lookup.c:951]: t_reply_matching(): reply (0x7f8212d77e28) matched an
active transaction (T=0x7f820b6cc988)!
2018-04-18T07:29:54.184474+00:00 pinkman /usr/sbin/kamailio[17671]: DEBUG:
tm [t_lookup.c:1088]: t_check_msg(): msg (0x7f8212d77e28) id=3 global id=3
T end=0x7f820b6cc988
2018-04-18T07:29:54.184485+00:00 pinkman /usr/sbin/kamailio[17671]: DEBUG:
tm [t_reply.c:2207]: reply_received(): org. status uas=100, uac[1]=100
local=0 is_invite=1)
2018-04-18T07:29:54.184544+00:00 pinkman /usr/sbin/kamailio[17671]: ERROR:
<script>: 183 Session Progress received
2018-04-18T07:29:54.184825+00:00 pinkman rtpengine[1660]: INFO:
[EqRkPDiOFOOhFg_3018V8A..]: Received command 'answer' from 127.0.0.1:41084
2018-04-18T07:29:54.184918+00:00 pinkman rtpengine[1660]: INFO:
[EqRkPDiOFOOhFg_3018V8A..]: answer time = 0.000074 sec
2018-04-18T07:29:54.184931+00:00 pinkman rtpengine[1660]: INFO:
[EqRkPDiOFOOhFg_3018V8A..]: Replying to 'answer' from 127.0.0.1:41084
2018-04-18T07:29:54.185049+00:00 pinkman /usr/sbin/kamailio[17671]: DEBUG:
tm [t_reply.c:1263]: t_should_relay_response(): ->>>>>>>>> T_code=100,
new_code=183
2018-04-18T07:29:54.185066+00:00 pinkman /usr/sbin/kamailio[17671]: DEBUG:
tm [t_reply.c:1786]: relay_reply(): branch=1, save=0, relay=1 icode=0
2018-04-18T07:29:54.252450+00:00 pinkman /usr/sbin/kamailio[17678]: DEBUG:
tm [h_table.c:129]: free_cell_helper(): freeing transaction 0x7f820b6c2540
from timer.c:651
2018-04-18T07:29:54.377492+00:00 pinkman rtpengine[1660]: WARNING:
[EqRkPDiOFOOhFg_3018V8A.. port 18598]: RTP packet with unknown payload type
95 received
2018-04-18T07:29:54.564924+00:00 pinkman /usr/sbin/kamailio[17678]: DEBUG:
tm [h_table.c:129]: free_cell_helper(): freeing transaction 0x7f820b6c57a8
from timer.c:651
2018-04-18T07:29:55.627429+00:00 pinkman /usr/sbin/kamailio[17678]: DEBUG:
tm [h_table.c:129]: free_cell_helper(): freeing transaction 0x7f820b6c8bf8
from timer.c:651
2018-04-18T07:29:55.939949+00:00 pinkman /usr/sbin/kamailio[17678]: DEBUG:
tm [h_table.c:129]: free_cell_helper(): freeing transaction 0x7f820b6cc988
from timer.c:651
2018-04-18T07:29:56.404385+00:00 pinkman /usr/sbin/kamailio[17673]: ERROR:
<script>: CANCEL received
2018-04-18T07:29:56.404411+00:00 pinkman /usr/sbin/kamailio[17673]: DEBUG:
tm [t_lookup.c:711]: t_lookupOriginalT(): searching on hash entry 6057
2018-04-18T07:29:56.404424+00:00 pinkman /usr/sbin/kamailio[17673]: DEBUG:
tm [t_lookup.c:435]: matching_3261(): RFC3261 transaction matching failed
2018-04-18T07:29:56.404429+00:00 pinkman /usr/sbin/kamailio[17673]: DEBUG:
tm [t_lookup.c:801]: t_lookupOriginalT(): no CANCEL matching found!
2018-04-18T07:29:56.404434+00:00 pinkman /usr/sbin/kamailio[17673]: DEBUG:
tm [t_lookup.c:803]: t_lookupOriginalT(): lookup completed
2018-04-18T07:29:56.404441+00:00 pinkman /usr/sbin/kamailio[17673]: DEBUG:
tm [tm.c:1096]: ki_t_lookup_cancel_flags(): lookup_original:
t_lookupOriginalT returned: (nil)
Kelvin Chua
Hello,
a while ago, I started to put together a unit testing framework for
Kamailio. It was more or less inspired from the old shell-based testing
framework added by Henning Westerholt many years ago (which still
resides in source tree path test/unit/), but now leveraging docker to
have an isolated environment for running the tests.
The new testing framework is available on github at:
* https://github.com/kamailio/kamailio-tests
Giacomo Vacca helped a bit so far, he is actually going to present more
about it at Kamailio World 2018
(https://www.kamailioworld.com/k06/schedule/).
But we want now to get more feedback from community, eventually to
adjust the framework to become something easy to use and even more
important, to be easy to contribute to.
One of the main benefits from my point of view it would be to have the
reports of the issues that can be reproduced submitted along with a unit
test. It would make it easier to troubleshoot and then after fixing it,
would be tested always before releases in order to avoid regressions.
Right now, a good help from community would represent converting the old
unit tests to the new framework, afterwards we can decommission
test/unit. The conversion should be rather easy, as we still rely on
shell and the sip tools like sipp/sipsak ... If you want to help here by
you need clarifications or get stuck somewhere, just write to mailing
list and I would be more than happy to assist. Such contributions should
be submitted as pull requests in order to be easy to review:
* https://github.com/kamailio/kamailio-tests/pulls
Looking forward to your feedback, comments or contributions!
Cheers,
Daniel
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com
Hi All,
I want to compile kamailio 5.1.2 for debian packages amd install on ubuntu
16.04.
And i have couple of queries.
1. can i compile and run kamailio 5.1.2 on ubuntu 16.04(Xenial)?
2. Im currently using kamailio 4.3.6 with polaris configuration. And the
same way can i use kamailio 5.1.2 with polaris configuration files and
scripts to bringup kamailo 5.1.2?
and if yes, please share me steps and scripts to bringup kamailio 5.1 2
with Open HSS( i need to use CX and RX interface).
Please help me out.
Thanks in advance.
Regards,
vinay
Hello
What is the correct way to handle, if a branched call reaches a 404 on
one of the branches.
Currently I discard all 404 in onreply_route, but if all branches has
404, then this is never send to the caller.
--
-------------------- Med Liberalistiske Hilsner ----------------------
Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog
Sofienlundvej 6B, 7560 Hjerm, Tlf: 40 29 41 49
Den ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk
Hey All,
I have a weird issue. I’m sending a SIP INVITE to a SIP Service that send’s me back a 433, which let’s me know that the number is invalid. I then send an INVITE to a media server (FreeSwitch) to play a message that the number can’t be called, which looks to be working. But, the final ACK from the SIP client is sent back to the SIP Service versus the media server. The following diagram below depicts this: https://snag.gy/qMWfvk.jpg. The code snippet in the failure_route for the the SIP Service has this:
if (t_check_status("403|433")) {
if ($avp(s:teleblock_media_enabled) == "1") {
# make sure media server can route back to kamailio
record_route();
revert_uri();
$ru = "sip:" + $T_reply_code + $rU + "@" + $sel(cfg_get.teleblock.media_ip) + ":" + $sel(cfg_get.teleblock.media_port);
append_branch();
t_relay();
exit;
}
Hi List,
two questions regarding Kamailio Websockets:
1. How do I send INVITE request TO the listening Websocket?
I usually used for UDP/TCP/TLS these format, but somehow this is not working for Websocket because it gets in an endless loop:
if ($rU=~"^(\+|00|0)?[1-9][0-9]{4,20}$") {
$ru = "sip:" + $rU + "@" + $sel(cfg_get.pstn.gw_ip) + ";user=phone;transport=udp";
force_send_socket(udp:MY_EXTERN_IP:MY_EXTERN_PORT);
rtpengine_offer("internal trust-address RTP AVP");
route(RELAY);
exit;
}
2. Why do I get these errors every time my Websocket Client is registering, but it still works and DB is inserted with registered location:
ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 22)
ERROR: <core> [parser/msg_parser.c:690]: parse_msg(): ERROR: parse_msg: message=<HTTP/1.1 101 Switching Protocols#015#012Sia: SIP/2.0/TCP 10.250.5.17:51283#015#012Sec-WebSocket-Protocol: sip#015#012Upgrade: websocket#015#012Connection: upgrade#015#012Sec-WebSocket-Accept: 6uLXlD/aBrzu/j3PYP3DWO7rvLE=#015#012Server: kamailio (4.3.5 (x86_64/linux))#015#012Content-Length: 0#015#012#015#012>
I am using Kamailio 4.3.5 + CentOS 7.2. I appreciate every help I can get.
Best Regards
Dimitry Nagorny
Trainee
