sr-users August 2021

sr-users@lists.kamailio.org

49 participants
52 discussions

by Joli Martinez

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,

3 years, 3 months

Integration with multiple MS Teams instances

by Володимир Іванець

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 years, 3 months

Ringing Timeout

by Edward Romanenco

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

3 years, 3 months

help

by Said Hassani

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 years, 3 months

XCAP server with simservs support

by H Yavari

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

3 years, 3 months

no debug trace of incoming request

by Juha Heinanen

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 years, 3 months

Issues with TOPOS when not relaying an in-dialog request

by Marrold

Hi, I am currently using TOPOS to make Kamailio behave more like a B2BUA from the clients perspective. It's working well, however I have discovered a scenario where it fails. To aid with some interoperability I am sending (sl_send_reply) 200 OK to an in-dialog SUBSCRIBE request during a call. Once this has happened, the subsequent BYE from the B leg goes to the incorrect (Private) IP. If I disable this SUBSCRIBE, or relay it to the B leg, the BYE goes to the expected IP address. Does anyone know where I am going wrong? I have tried not calling record_route() for these messages but the result is the same. I've attached the ladder diagram of the call below. Note the subscribe is not relayed in this scenario. Thanks! [image: image.png]

3 years, 3 months

Re: [SR-Users] How to unload previously loaded destinations in the case of applying multiple ds_select_domain

by Serdar GÜÇLÜER

> Serdar, > > Have you tried to clean variables before calling new ds_select_domain(), > that are using by dispatcher module failover? > > Like > https://kamailio.org/docs/modules/5.3.x/modules/dispatcher.html#dispatcher.… <https://kamailio.org/docs/modules/5.3.x/modules/dispatcher.html#dispatcher.…> > and so on? > > But as I got, you're saying, that calling ds_select_domain() with > different setid's in a case of fail, not really fails, but using "old" > available destinations from previous attempt? > > Regards, > Igor Igor, also thanks for your interest. > Hello, > > delete the xavps based on the names you set via modparams xavp_dst and > xavp_ctx. > > Cheers, > Daniel I remove xavp value using "xavp_rm("_dsdst_")", i supposed that my problem was solved but in my other tests, i recognised that xavp_rm removed the first index of "xavp(_dsdst_)" not all previous destinations(indexes). after researching, i found a post at https://lists.kamailio.org/pipermail/sr-users/2020-May/109192.html and i removed all ellements of list as below, if(defined $xavp(_dsdst_)) { while($xavp(_dsdst_[0]) != $null) { xlog("L_INFO", "--- Loaded Dispatchers --- Grp : $xavp(_dsdst_[0]=>grp)\n"); xlog("L_INFO", "--- Loaded Dispatchers --- Uri : $xavp(_dsdst_[0]=>uri)\n"); $xavp(_dsdst_[0]) = $null; } } it worked but i am not sure it is a best solution. Is there another simple way to delete all indexes of xavp? Best regards, Serdar

3 years, 3 months

Converting Cisco SIP NOTIFY DTMF to SIP INFO (Binary operations)

by Marrold

Hi, I am using an old Cisco 2811 with an FXS card and trying to get it to convert between POTS and SIP. Mostly for "fun". For the most part it works, however there are some problems with DTMF in the call. Because the end device uses pulse dialling it seems that only the Cisco Proprietary SIP NOTIFY method of sending DTMF is supported. It sends 4 bytes in the message body that indicate the DTMF digit sent. I'd like to convert it to the more standard SIP INFO method. The docs about the encoding are here - https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/sip/configuration/1… I looked at the transformations but couldn't find anything relevant. Is it possible to extract the binary from the body and decode it? Thanks Matthew

3 years, 3 months

which is better for B2BUA

by Mojtaba

Hello there, According to , https://lists.kamailio.org/pipermail/sr-users/2016-March/092058.html, which talked about B2BUA (just signalling) in Kamailio. As i have experienced working with SEMS, freeswitch and Kamailio while using B2BUA feature, Each of them have pros and cons: 1- The sems is a light sip engine server with several applications (like as sbc) for using b2bua. All incoming and outgoing calls could go to sems server for doing b2bua like this: Incoming<=======>Kamailio<========>Sems<========>Kamailio<=======>outgoing 2- In sems, you could disable rtp realying. It forces sems to work just as b2bua without anchoring RTP 3- Easy to use different active profiles in routing. Just a couple of things there are in SEMS. For example, the sems adds itself (local IP) in Via header, and it couldn't be common in b2bua. like this: . . . INVITE sip:200@cloud.domain.com;transport=UDP SIP/2.0 Via: SIP/2.0/UDP 10.10.10.200;branch=z9hG4bK2f53.07a3fd9edaa8c8d609ab2ac6b01a087f.0 *================================>Kamailio public IP* *Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;branch=z9hG4bKsPRMNast;rport=5080 ===============================>private loopback sems ip* From: <sip:100@cloud.domain.com ;transport=UDP>;tag=6FFDB493-60EABB3600016ECD-379F9700 To: <sip:200@cloud.domain.com;transport=UDP> CSeq: 10 INVITE Call-ID: Y2M1ODQxNTZmMjdkZWZjN2U5MmMyYjBmN2Y2OGY1ODQ._leg2 Route: <sip:mo@127.0.0.1:5060;lr> Max-Forwards: 69 Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE User-Agent: Z 3.3.25608 r25552 Content-Type: application/sdp Contact: <sip:127.0.0.1:5080;transport=udp> Content-Length: 246 . . . For this reason, Is there a way to avoid this issue? I know it is possible to do this by using other modules like textops and retransformation ? And why in Kamailio, there is no b2bua module to perform all b2bua functionality, yet? Thanks with Best Regards. -- --Mojtaba Esfandiari.S

3 years, 3 months

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 August 2021