- sr-users - kamailio.org

no transaction found so that cant step into route-block
by fran.interpla.56906 26 Aug '21

26 Aug '21

1 0

no transaction found so that cant step into route-block
by fran.interpla.56906 26 Aug '21

26 Aug '21

1 0

Kamailio v5.5.2 Released
by Daniel-Constantin Mierla 25 Aug '21

25 Aug '21

Hello, Kamailio SIP Server v5.5.2 stable release is out. This is a maintenance release of the latest stable branch, 5.5, that includes fixes since the release of v5.5.1. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.5.x. Deployments running previous v5.5.x versions are strongly recommended to be upgraded to v5.5.2. For more details about version 5.5.2 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2021/08/kamailio-v5-5-2-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.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

3 2

MS Teams outbound calls. Called number normalization
by Володимир Іванець 25 Aug '21

25 Aug '21

Hello all! I'm testing integration with MS Teams. I treat calls from Teams to the phone system the same way as calls from phones. And would like to ask if someone has already dealt with this. My test account location is set to the United States. When I make a call to "200", an INVITE request from Teams to Kamailio will have "+1200" in the To URI user. I could just strip "+1" but when I make a call to "100", Teams sends "+100". So in this case I need to strip only one character. The problem is that I don't know when I need to remove one or two characters. And it gets more complicated when I change my test account location. For some countries, Teams prepend 3 characters. What do to make sure phone numbers are consistent? I thought this behavior could be disabled in Teams but could not find anything related yet. Thank you! Regards, Volodymyr Ivanets

1 0

Releasing Kamailio v5.5.2
by Daniel-Constantin Mierla 25 Aug '21

25 Aug '21

Hello, I am considering to release Kamailio v5.5.2 sometime next week, likely on Wednesday (August 25, 2021). This is the usual heads up notification to see if anyone is aware of issues not yet reported to bug tracker and if yes, do it as soon as possible to give them a chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

2 2

[VoLTE] 401 unauthorized error
by 오택경 24 Aug '21

24 Aug '21

Hi. I am implementing the VoLTE setup with the dockerized project (https://github.com/herlesupreeth/docker_open5gs https://github.com/herlesupreeth/docker_open5gs). I have almost done to run the VoLTE service, but 401 unauthorized error in sip and auth-pending error in fhoss have occured. How can I fix this problem? I will share the discussion note in which I tried to solve some problems including the above one. : https://github.com/herlesupreeth/docker_open5gs/issues/55 https://github.com/herlesupreeth/docker_open5gs/issues/55 Very thanks, Taekkyung Oh.

3 7

Race conditions upon quick reinvite
by David VILLAUME 24 Aug '21

24 Aug '21

Hello, We encounter sometimes reinvite from some provider really quickly after 200 OK ACK so sometime there a race conditions where the re-invite exits Kamailio before the ACK leading to some Freeswitch “500 Overlapping Requests”. [cid:image001.png@01D798FA.6F5B9D80] I tried to catch the 500 on failure-route unsuccessfully as transaction is already established. Do you have any idea on how I could deal with this behavour ? Running 5.3.6 with 8 childs modules used :(tm + dialog) No costly action performed on ack that can explain slowliness. Regards, David

3 3

kazoo error
by 崔群 24 Aug '21

24 Aug '21

Dear sir: I have some problems。the kamailio version is 5.3.0. My linux version is centos 7. the kamailio log: ERROR: kazoo [kz_amqp.c:2238]: kz_amqp_send_ex(): Failed to publish -9 : a socket error occurred ERROR: kazoo [kz_amqp.c:2707]: kz_amqp_publisher_send(): error sending publish to zone : local , connection id : 1, uri : amqp://admin The connection between kamailio and rabbitmq was interrupted, which caused the queue of MQ to be blocked and the message could not be consumed。

2 1

Some questions about drouting module
by Андрей Яри н 23 Aug '21

23 Aug '21

Hello! I test module on Centos 7, kamailio version 5.5 and found some strange things: 1) Definition of table dr_gateways at https://kamailio.org/docs/modules/5.5.x/modules/drouting.html#idm98 - in DB there is field 'attrs' and only notice about it is module param 3.8. attrs_avp but it doesnt describe table field. In OpenSIPS docs i found description * attributes (not used by DR engine, but only pushed to script level when routing to this GW) In kamailio this field is deprecated or its only docs misses param? 2) Previous moment was found when i try to resolve: WARNING: drouting [dr_load.c:529]: dr_load_routing_info(): route <1> does not exist "Definition of dr_rules table" says that field has type of integer, but realy in database its varchar and i think its old docs. But i use KEMI question is - how i can tell module that it must be called in KEMI, not in native? 3) Every time when i call 'kamcmd drouting.reload' i get message CRITICAL: <core> [core/mem/q_malloc.c:502]: qm_free(): BUG: bad pointer 0x7f3e4cea04c0 (out of memory block!) called from core: core/utils/tmrec.c: tmrec_free(393) - ignoring I rollback to 5.4 and still get this error. As i understand its old module and its can be internal error - how critical this error can be? 4) Also planned commands like drouting.dump gws|gw_lists|rules? -- С уважением, Ярин Андрей Анатольевич инженер, группы управления телефонией Группа компаний «Интерсвязь» e-mail: yarin-aa(a)intersvyaz.net

2 3

Kamailio as basic dispatcher for load balancing
by Philipp Trenz 23 Aug '21

23 Aug '21

Hey there, I’m Philipp, an IT Systems Engineer from Potsdam, Germany and want to deepen my knowledge in SIP communication on scale. Currently, my setup is quite simple: A single stateless Asterisk instance, fully managed via ARI, which registers to multiple VoIP providers, only processes incoming calls to play audio files (no outgoing or conference calls). Now, with growing load on the single Asterisk instance, I would like to have one or two Kamailio instances, which will balance the load of incoming calls to multiple Asterisk instances. On which Asterisk instance they end up is irrelevant for me, as the calls can be processed on every instance. I looked into some Kamailio and Astricon conference speeches and checked out some tutorials. But still I’m not quite sure where to start. So here are some basic questions which would really help me out to get going: As I don’t want to have registrations of all my Asterisk instances at the VoIP providers, I should use the UAC module to let Kamailio do the registering to the VoIP providers and register my Asterisk instances to Kamailio, right? Will Kamailio automatically apply new outbound registrations when added to the database or do I have to trigger that manually? Should I use one or two instances of Kamailio, how hard is it to configure them fail-safe? For writing my first config file, should I start blank or from the standard config, what’s best practice? Thanks in advance, looking forward to your replies! Philipp

3 5

How tell if rtp packets are being relayed through rtpengine in kamailio
by Faiz Fazaluddin 23 Aug '21

23 Aug '21

Hi, I want to see if rtp packets are being relayed through kamailio. I am attmepting to connect rtpengine with kamailio, but am not sure if it is working, how can I tell? I have the kamailio server on a different VM than the clients. In wireshark, no rtp packets show on the server VM and rtp packets only seem to be going directly through the client VM. Rtp engine mentions being unable to find hashtables when attempting to implement a delete_node command. Thank you very much for your help, Faiz

3 2

Register Forwarding
by Thomas Grande 21 Aug '21

21 Aug '21

Hi there! I bumped into this post to perform forwarding of REGISTER requests and then saving a local cache on 2xx replies from main Registrar: https://lists.kamailio.org/pipermail/sr-users/2020-October/110779.html I think I understand all the steps described, but some features I need are missing: - How to change the Via headers to perform topology hiding? I understand TOPOS and TOPOH do not work on these types of messages. - Change contact header so that registrar responses traverse the Kamailio box. (Use textops I suppose?) - Besides, is this approach still the best in comparison to OpenSIPs mid-registrar module? Thanks in advance, -- *Thomás Alimena Del Grande* Engenharia - Aligera Tel. 51 3500-0121

3 2

record_route() from websocket UA to tls UA
by Juha Heinanen 20 Aug '21

20 Aug '21

I noticed that when jsSIP UA that has registered over wss calls another SIP UA that has registered over tls, record_route() adds only one Route URI to outgoing INVITE (example below). This causes BYE to fail. This issue may be caused by the fact that both UAs register over the same Kamailio tls listening socket. Still two Route URIs should be added in the same way as is done when one UA registers over tcp and the other over udp. -- Juha --------------------------------------------------------------------- 09:25:43.639833 wss:87.95.73.155:19458 wss:192.27.134.1:5061 INVITE sip:foo@test.tutpro.com SIP/2.0 Via: SIP/2.0/WSS jovobf9n4svm.invalid;branch=z9hG4bK2639638 Max-Forwards: 69 To: <sip:foo@test.tutpro.com> From: " Test" <sip:test@test.tutpro.com>;tag=f7lpsuo7cb Call-ID: ovhd9fu1fl1a66nec011 CSeq: 1387 INVITE Contact: <sip:test@test.tutpro.com;gr=urn:uuid:e7f92a54-2295-4772-abc8-504be07e94c5> ... 09:25:43.649462 tls:192.27.134.1:5061 tls:87.95.73.155:19461 INVITE sip:foo-0x793ee87a90@10.158.141.103:38378;transport=tls SIP/2.0 Record-Route: <sip:192.27.134.1:5061;transport=ws;sn=ext_tls;lr;n2;dtlsf=avp;pm=0;ice> Via: SIP/2.0/TLS 192.27.134.1:5061;branch=z9hG4bK637c.7e15ef5b84ea054cfc8ea3d4e860521f.0 Via: SIP/2.0/WSS jovobf9n4svm.invalid;rport=19458;received=87.95.73.155;branch=z9hG4bK2639638 Max-Forwards: 68 To: <sip:foo@test.tutpro.com> From: " Test" <sip:test@test.tutpro.com>;tag=f7lpsuo7cb Call-ID: ovhd9fu1fl1a66nec011 CSeq: 1387 INVITE Contact: <sip:test@test.tutpro.com;gr=urn:uuid:e7f92a54-2295-4772-abc8-504be07e94c5>

2 11

install latest sems-server on debian 10 buster
by Mojtaba 18 Aug '21

18 Aug '21

Hello there, Does anybody have experience installing the latest SEMS-Server (1.6.0) on debian 10 buster? I tried to install both 1.6.0. and 1.7-dev and some issues are occurred, but i installed the version 1.3.1 on debian 8 before. Any help would be appreciated. Thanks with best regards -- --Mojtaba Esfandiari.S

4 11

How to insert user=phone header INVITE TO FROM
by César Matheus 18 Aug '21

18 Aug '21

Hi list. mY provider asks me to insert user = phone in my header. because it requires to receive my INVITE with user = phone in TO and FROM However, I add the user = phone in my configuration like this: $ ru = "sip:" + $ rU + "@" + $ sel (cfg_get.pstn1.gw_ip) + ":" + $ sel (cfg_get.pstn1.gw_port) + "; user = phone"; but only the INVITE appears, not in the TO or FROM. INVITE sip: 09872323232(a)X.Y.X.K: 5060; user = phone SIP / 2.0 From: <sip: XXXXYYYYY(a)172.20.12.4: 5060>; tag = 15552444533876 To: <sip: 09872323232(a)172.20.12.2: 5060> You can help me solve it. Thanks. -- César Matheus

3 2

crash in timer
by Juha Heinanen 17 Aug '21

17 Aug '21

Any idea what could cause the crash shown in the bt below? This is with Kamailio 5.5. -- Juha [New LWP 12061] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". bt Core was generated by `/usr/bin/sip-proxy -f /etc/sip-proxy/sip-proxy.cfg -P /run/sip-proxy/sip-proxy.'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0000563d3b390c5d in timer_list_expire (t=1584008014, h=0x7f7a1e76bb40, slow_l=0x7f7a1e76d680, slow_mark=63909) at core/timer.c:846 846 core/timer.c: No such file or directory. (gdb) bt full #0 0x0000563d3b390c5d in timer_list_expire (t=1584008014, h=0x7f7a1e76bb40, slow_l=0x7f7a1e76d680, slow_mark=63909) at core/timer.c:846 tl = 0x7f7a226ecbd8 ret = 0 #1 0x0000563d3b391219 in timer_handler () at core/timer.c:922 saved_ticks = 1584008014 run_slow_timer = 0 i = 421 __func__ = "timer_handler" #2 0x0000563d3b391742 in timer_main () at core/timer.c:961 No locals. #3 0x0000563d3b2c94de in main_loop () at main.c:1839 i = 8 pid = 0 si = 0x0 si_desc = "udp receiver child=7 sock=46.182.160.20:5060\000\000\000\000\003\000\000\000 \000\000\000\000\071CU\356xL\375\000\000\000\000\000\000\000\000\210\300m;=V\000\000\000\000\000\000\000\000\000\000\260\334\371Jz\177\000\000\263\331r;=V\000\000\000\000\000 \000\000\000\000\340\b3;\374\177\000\000\t\365U;=V\000" nrprocs = 8 woneinit = 1 __func__ = "main_loop" #4 0x0000563d3b2d44aa in main (argc=17, argv=0x7ffc3b330e28) at main.c:3053 cfg_stream = 0x563d3b9ea290 c = -1 r = 0 tmp = 0x7ffc3b331f3f "" tmp_len = 1260628273 port = 32634 proto = 0 ahost = 0x0 aport = 0 --Type <RET> for more, q to quit, c to continue without paging--c options = 0x563d3b6dece0 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 1970794883 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x0 p = 0xffff00001f80 <error: Cannot access memory at address 0xffff00001f80> st = {st_dev = 21, st_ino = 21649, st_nlink = 2, st_mode = 16832, st_uid = 109, st_gid = 115, __pad0 = 0, st_rdev = 0, st_size = 40, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1620846563, tv_nsec = 71986646}, st_mtim = {tv_sec = 1628122861, tv_nsec = 116913769}, st_ctim = {tv_sec = 1628122861, tv_nsec = 616909103}, __glibc_reserved = {0, 0, 0}} tbuf = "\000\000\000\000\000\000\000\000\b\000\000\000\000\000\000\000\060\067&Kz\177\000\000\000\000\000\000\000\000\000\000\240\241>;\374\177\000\000\364:$Kz\177\000\000\b\000\000\000\000\000\000\000\230\242>;\374\177\000\000\060\067&Kz\177\000\000\310\v3;\374\177\000\000\304\v3;\374\177", '\000' <repeats 18 times>, "\230\242>;\374\177\000\000\250\241>;\374\177\000\000'\256\002Kz\177\000\000&\260be\000\000\000\000\060\r3;\374\177\000\000\300\212\225\001\000\000\000\000\220\f3;\374\177\000\000\200\f3;\374\177\000\000\310\v3;\374\177\000\000X7&Kz\177\000\000\001", '\000' <repeats 31 times>... option_index = 0 long_options = {{name = 0x563d3b6e0f3f "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x563d3b6dc4e1 "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0x563d3b6e0f44 "alias", has_arg = 1, flag = 0x0, val = 1024}, {name = 0x563d3b6e0f4a "subst", has_arg = 1, flag = 0x0, val = 1025}, {name = 0x563d3b6e0f50 "substdef", has_arg = 1, flag = 0x0, val = 1026}, {name = 0x563d3b6e0f59 "substdefs", has_arg = 1, flag = 0x0, val = 1027}, {name = 0x563d3b6e0f63 "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 0x563d3b6e0f6d "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, {name = 0x563d3b6e0f78 "modparam", has_arg = 1, flag = 0x0, val = 1030}, {name = 0x563d3b6e0f81 "log-engine", has_arg = 1, flag = 0x0, val = 1031}, {name = 0x563d3b6e0f8c "debug", has_arg = 1, flag = 0x0, val = 1032}, {name = 0x563d3b6e0f92 "cfg-print", has_arg = 0, flag = 0x0, val = 1033}, {name = 0x563d3b6e0f9c "atexit", has_arg = 1, flag = 0x0, val = 1034}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} __func__ = "main"

1 0

Info: First group of presentations at Kamailio World Online 2021
by Daniel-Constantin Mierla 17 Aug '21

17 Aug '21

Hello, the first group of presentations selected for the next Kamailio World Online, September 1-2, 2021, has been published, aiming to provide a good knowledge base of using Kamailio for different deployment types: segregation of networks with an SBC-like role, controlling robots, RTP streams management with RTPEngine, configuration variables or transformations, SIP attacks handling and asynchronous SIP routing. You can find more details at: * https://kamailioworld.com/k09-online/ The schedule will be completed during the next days, with another group of interesting sessions and open discussion panels. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

No docker hub automated builds
by Sergey Safarov 14 Aug '21

14 Aug '21

I found that not more automated builds available on docker hub https://www.docker.com/blog/changes-to-docker-hub-autobuilds/ Looks like we need to make some changes for the alpine docker image. Maybe use github actions for this task? https://docs.docker.com/ci-cd/github-actions/ Sergey

1 0

RTPEngine: Async connection/communication between Kamailio and RTPEngine
by Mitesh Thakkar 12 Aug '21

12 Aug '21

Hi, Couple of week before I have posted feature request - https://github.com/kamailio/kamailio/issues/2807 As suggested, I am trying to figure out how I can achieve it with async or sworker modules. Can someone help me to understand how to use those modules to achieve async connectivity? Regards, Miteshkumar Thakkar

3 3

auth challenge freeswitch with Zopier
by Joli Martinez 10 Aug '21

10 Aug '21

Hello, I am using dsiprouter as a public facing server for pass through registrations to a fusion pbx box. This setup works great and has for a long time now. The issue I am having is that we are switching soft phone clients to copier. Zopier uses a push server. When an incoming call comes into the freeswitch server, it fires off an invite to the Zopier registered client. For some reason ONLY in this scenario Kamailio is doing an auth challenge to Freeswitch preventing to call to be sent to the soft phone. How can I stop this from happening? Other soft phones and hard phones work great with inbound calls except for Zopier. thanks,

2 1

Integration with multiple MS Teams instances
by Володимир Іванець 10 Aug '21

10 Aug '21

Hello all! I was able to connect Kamailio with MS Teams and now trying to add one more Teams instance. It looks like I have some misconfiguration or there is a bug. My test server has 2 domain records pointing at it (kamailio.domain1.com and kamailio.domain2.com). My tls.cfg configuration file looks like this. As you can see the Default section is configured with a kamailio.domain1.com sertificate: *[server:default]* *method = TLSv1.0+* *require_certificate = no* *verify_certificate = no* *private_key = /var/kamailio/certificates/kamailio.domain1.com/server/key.pem <http://kamailio.domain1.com/server/key.pem>* *certificate = /var/kamailio/certificates/kamailio.domain1.com/server/cert.pem <http://kamailio.domain1.com/server/cert.pem>* *ca_list = /var/kamailio/certificates/kamailio.domain1.com/CA/cert.pem <http://kamailio.domain1.com/CA/cert.pem>* *[client:default]* *method = TLSv1.0+* *require_certificate = no* *verify_certificate = no* *private_key = /var/kamailio/certificates/kamailio.domain1.com/server/key.pem <http://kamailio.domain1.com/server/key.pem>* *certificate = /var/kamailio/certificates/kamailio.domain1.com/server/cert.pem <http://kamailio.domain1.com/server/cert.pem>* *ca_list = /var/kamailio/certificates/kamailio.domain1.com/CA/cert.pem <http://kamailio.domain1.com/CA/cert.pem>* *[server:172.16.30.206:5062 <http://172.16.30.206:5062>]* *method = TLSv1.0+* *require_certificate = no* *verify_certificate = no* *private_key = /var/kamailio/certificates/kamailio.domain1.com/server/key.pem <http://kamailio.domain1.com/server/key.pem>* *certificate = /var/kamailio/certificates/kamailio.domain1.com/server/cert.pem <http://kamailio.domain1.com/server/cert.pem>* *ca_list = /var/kamailio/certificates/kamailio.domain1.com/CA/cert.pem <http://kamailio.domain1.com/CA/cert.pem>* *server_name = "kamailio.domain1.com <http://kamailio.domain1.com>"* *server_id = "**"kamailio.domain1.com <http://kamailio.domain1.com>"* *[client:172.16.30.206:5062 <http://172.16.30.206:5062>]* *method = TLSv1.0+* *require_certificate = no* *verify_certificate = no* *private_key = /var/kamailio/certificates/kamailio.domain1.com/server/key.pem <http://kamailio.domain1.com/server/key.pem>* *certificate = /var/kamailio/certificates/kamailio.domain1.com/server/cert.pem <http://kamailio.domain1.com/server/cert.pem>* *ca_list = /var/kamailio/certificates/kamailio.domain1.com/CA/cert.pem <http://kamailio.domain1.com/CA/cert.pem>* *[server:172.16.30.206:5063 <http://172.16.30.206:5063>]* *method = TLSv1.0+* *require_certificate = no* *verify_certificate = no* *private_key = /var/kamailio/certificates/kamailio.domain2.com/server/key.pem <http://kamailio.domain2.com/server/key.pem>* *certificate = /var/kamailio/certificates/kamailio.domain2.com/server/cert.pem <http://kamailio.domain2.com/server/cert.pem>* *ca_list = /var/kamailio/certificates/kamailio.domain2.com/CA/cert.pem <http://kamailio.domain2.com/CA/cert.pem>* *server_name = "kamailio.domain2.com <http://kamailio.domain2.com>"* *server_id = "**"kamailio.domain2.com <http://kamailio.domain2.com>"* *[client:172.16.30.206:5063 <http://172.16.30.206:5063>]* *method = TLSv1.0+* *require_certificate = no* *verify_certificate = no* *private_key = /var/kamailio/certificates/kamailio.domain2.com/server/key.pem <http://kamailio.domain2.com/server/key.pem>* *certificate = /var/kamailio/certificates/kamailio.domain2.com/server/cert.pem <http://kamailio.domain2.com/server/cert.pem>* *ca_list = /var/kamailio/certificates/kamailio.domain2.com/CA/cert.pem <http://kamailio.domain2.com/CA/cert.pem>* The dispatcher configuration table looks like this: +----+-------+----------------------------------------------+-------+----------+--------------------------------------------------------------------+-------------+ | id | setid | destination | flags | priority | attrs | description | +----+-------+----------------------------------------------+-------+----------+--------------------------------------------------------------------+-------------+ | 1 | 1 | sip:sip.pstnhub.microsoft.com;transport=tls | 0 | 3 | socket=tls:172.16.30.206:5062;ping_from=sip:kamailio.domain1.com | MS Teams 1 | | 2 | 2 | sip:sip.pstnhub.microsoft.com;transport=tls | 0 | 3 | socket=tls:172.16.30.206:5063;ping_from=sip:kamailio.domain2.com | MS Teams 2 | +----+-------+----------------------------------------------+-------+----------+--------------------------------------------------------------------+-------------+ When Kamailio is started only connection with the first trunk is established: *# kamcmd tls.list* *{* * id: 1* * timeout: 0* * src_ip: 52.114.75.24* * src_port: 5061* * dst_ip: 172.16.30.206* * dst_port: 0* * cipher: ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH Au=RSA Enc=AESGCM(256) Mac=AEAD* * ct_wq_size: 0* * enc_rd_buf: 0* * flags: 2* * state: established* *}* *{* * id: 2* * timeout: 0* * src_ip: 52.114.75.24* * src_port: 7810* * dst_ip: 172.16.30.206* * dst_port: 5062* * cipher: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD* * ct_wq_size: 0* * enc_rd_buf: 0* * flags: 2* * state: established* *}* *{* * id: 3* * timeout: 596* * src_ip: 52.114.75.24* * src_port: 7811* * dst_ip: 172.16.30.206* * dst_port: 5062* * cipher: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD* * ct_wq_size: 0* * enc_rd_buf: 0* * flags: 2* * state: established* *}* Here is what I can see in Kamailio log file when it sends an OPTIONS request to the second trunk. Kamailio uses Default tls configuration and MS Teams don't accept it: *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: ALERT: <script>: == TRACE. tm:local-request. fs is tls:172.16.30.206:5063 <http://172.16.30.206:5063>* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: tm [uac.c:352]: t_run_local_req(): apply new updates without Via to sip msg* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/msg_translator.c:1796]: check_boundaries(): no multi-part body* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/msg_parser.c:610]: parse_msg(): SIP Request:* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/msg_parser.c:612]: parse_msg(): method: <OPTIONS>* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/msg_parser.c:614]: parse_msg(): uri: <sip:sip.pstnhub.microsoft.com <http://sip.pstnhub.microsoft.com>;transport=tls>* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/msg_parser.c:616]: parse_msg(): version: <SIP/2.0>* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK169b.6411b4c3000000000000000000000000.0>; state=16* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/msg_parser.c:498]: parse_headers(): Via found, flags=2* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/msg_parser.c:500]: parse_headers(): this is the first via* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=10* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/msg_parser.c:171]: get_hdr_field(): <To> [47]; uri=[sip:sip.pstnhub.microsoft.com <http://sip.pstnhub.microsoft.com>;transport=tls]* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/msg_parser.c:174]: get_hdr_field(): to body (47)[<sip:sip.pstnhub.microsoft.com <http://sip.pstnhub.microsoft.com>;transport=tls>^M* *], to tag (0)[]* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/msg_parser.c:152]: get_hdr_field(): cseq <CSeq>: <10> <OPTIONS>* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/msg_parser.c:185]: get_hdr_field(): content_length=0* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/msg_parser.c:89]: get_hdr_field(): found end of header* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/msg_parser.c:610]: parse_msg(): SIP Request:* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/msg_parser.c:612]: parse_msg(): method: <OPTIONS>* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/msg_parser.c:614]: parse_msg(): uri: <sip:sip.pstnhub.microsoft.com <http://sip.pstnhub.microsoft.com>;transport=tls>* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/msg_parser.c:616]: parse_msg(): version: <SIP/2.0>* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK169b.6411b4c3000000000000000000000000.0>; state=16* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/msg_parser.c:498]: parse_headers(): Via found, flags=2* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/msg_parser.c:500]: parse_headers(): this is the first via* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=10* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/msg_parser.c:171]: get_hdr_field(): <To> [47]; uri=[sip:sip.pstnhub.microsoft.com <http://sip.pstnhub.microsoft.com>;transport=tls]* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/msg_parser.c:174]: get_hdr_field(): to body (47)[<sip:sip.pstnhub.microsoft.com <http://sip.pstnhub.microsoft.com>;transport=tls>^M* *], to tag (0)[]* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/parser/msg_parser.c:152]: get_hdr_field(): cseq <CSeq>: <10> <OPTIONS>* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: tm [uac.c:189]: uac_refresh_hdr_shortcuts(): cseq: [CSeq: 10]* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/tcp_main.c:1993]: tcp_send(): no open tcp connection found, opening new one* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/ip_addr.c:229]: print_ip(): tcpconn_new: new tcp connection: 52.114.75.24* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/tcp_main.c:1175]: tcpconn_new(): on port 5061, type 3, socket -1* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: <core> [core/tcp_main.c:1498]: tcpconn_add(): hashes: 2831:67:0, 1* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: tls [tls_server.c:199]: tls_complete_init(): completing tls connection initialization* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: tls [tls_server.c:162]: tls_get_connect_server_name(): xavp with outbound server name not found* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: tls [tls_server.c:142]: tls_get_connect_server_id(): xavp with outbound server id not found* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: tls [tls_server.c:228]: tls_complete_init(): Using initial TLS domain TLSc<default> (dom 0x7f35509da688 ctx 0x7f3550b7a568 sn [])* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: tls [tls_domain.c:1177]: tls_lookup_private_key(): Private key lookup for SSL_CTX-0x7f3550b7a568: (nil)* *Jul 29 16:46:14 kamailio /usr/sbin/kamailio[11809]: DEBUG: tls [tls_domain.c:747]: sr_ssl_ctx_info_callback(): SSL handshake started* *...* If I change the Default configuration to use kamailio.domain2.com certificate, the second trunk will connect but the first one will fail. I tried to set "$xavp(tls=>server_name)" and "$xavp(tls[0]=>server_id)" variables to the event_route[tm:local-request] section but log still stated that server Name and ID were not found. Can someone please point me in the right direction, how can I make Kamailio use the correct certificates when establishing multiple TLS connections? Thanks a lot! Regards, Volodymyr Ivanets

3 12

Ringing Timeout
by Edward Romanenco 09 Aug '21

09 Aug '21

Hey all, I'm trying to find the best way for settings a timeout for the 'ringing' stage of a call - meaning - I would like to wait for 20 seconds between receiving status 180 / 183 / early media from the remote end and 200, if I fail to receive the expected response in this timeframe - call should be dropped. Most of the documented timeouts I saw count between the first invite to any of the aforementioned stages - but I'm actually looking for the opposite. Edward

2 1

help
by Said Hassani 08 Aug '21

08 Aug '21

Dear Team, I would like to know how to link Kamailio with openIMSCore?I would like to use Kamailio as an Application server.Please guide me or if there is someone who has worked on this subject, I would like to benefit from his help.

3 4

XCAP server with simservs support
by H Yavari 05 Aug '21

05 Aug '21

Hi to all, As I found there isn't any support for this AUID : simservs.ngn.etsi.org in Kamailio.Anyone can confirm that we can't use Kamailio as mmtel for IMS with the current xcap_server module?!!Thank you. Regards,Hossein

2 2

no debug trace of incoming request
by Juha Heinanen 05 Aug '21

05 Aug '21

Is it somehow possible that ngrep shows incoming INVITE arriving over TCP to Kamailio's listening address and port, but there is no debug trace of the request (e.g. receive_msg(): --- received sip message ...) in syslog? -- Juha

3 3

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