sr-users April 2021

sr-users@lists.kamailio.org

43 participants
61 discussions

by Dong Ming (董明)

Thank you for your reply！ It's the first time to learn ims, I am very sorry for lack of knowledge and inaccurate description of this problem. I sincerely hope that you can give me some advice how to deal with this problem. thank you！发件人: Mojtaba <mespio(a)gmail.com> 发送时间: 2021年4月8日 17:02 收件人: Dong Ming (董明) <dongming(a)twsz.com> 抄送: Daniel-Constantin Mierla <miconda(a)gmail.com>; Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> 主题: Re: [SR-Users] sip registration fail Just be notic, being behind nat, cause your request to pcscf is rejected and the same issue (No private identity specified) is appeared in lon info. The public identity (IMPU) and private identity (IMPI) are created with the same pattern by default as shown in your attachment, but the title of the issue is confusing. On Thu, Apr 8, 2021 at 1:08 PM Dong Ming (董明) <dongming(a)twsz.com<mailto:dongming@twsz.com>> wrote: Hello According to the debug information, ================================================ 12(4516) DEBUG: <core> [core/parser/msg_parser.c:610]: parse_msg(): SIP Request: 12(4516) DEBUG: <core> [core/parser/msg_parser.c:612]: parse_msg(): method: <REGISTER> 12(4516) DEBUG: <core> [core/parser/msg_parser.c:614]: parse_msg(): uri: <sip:scscf.ims.mnc001.mcc460.3gppnetwork.org:6060<http://scscf.ims.mnc001.mcc460.3gppnetwork.org:6060>> 12(4516) DEBUG: <core> [core/parser/msg_parser.c:616]: parse_msg(): version: <SIP/2.0> 12(4516) DEBUG: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=10 12(4516) DEBUG: <core> [core/parser/msg_parser.c:171]: get_hdr_field(): <To> [57]; uri=[sip:460010000000001@ims.mnc001.mcc460.3gppnetwork.org<mailto:sip%3A460010000000001@ims.mnc001.mcc460.3gppnetwork.org>] 12(4516) DEBUG: <core> [core/parser/msg_parser.c:174]: get_hdr_field(): to body [<sip:460010000000001@ims.mnc001.mcc460.3gppnetwork.org<mailto:sip%3A460010000000001@ims.mnc001.mcc460.3gppnetwork.org>> ], to tag [] 12(4516) DEBUG: <core> [core/parser/msg_parser.c:152]: get_hdr_field(): cseq <CSeq>: <2> <REGISTER> 12(4516) DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK11a4.1097491452b96d42664a6b234646cc60.0>; state=6 12(4516) DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 236, <i> = <1>; state=16 12(4516) DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 12(4516) DEBUG: <core> [core/parser/msg_parser.c:498]: parse_headers(): Via found, flags=2 12(4516) DEBUG: <core> [core/parser/msg_parser.c:500]: parse_headers(): this is the first via 12(4516) INFO: ims_auth [cxdx_avp.c:137]: cxdx_get_avp(): cxdx_get_user_name: Failed finding avp (avp_code = 1, vendor_id = 0) 12(4516) ERROR: ims_auth [cxdx_mar.c:151]: async_cdp_callback(): No private identity specified (Authorization: username) ================================================ The above content is found in the log of s-cscf,It seems that the authentication failed. May I ask how to configure this part, or if this part of the code is deleted, will it affect the subsequent process? Thank you very much！发件人: Mojtaba <mespio(a)gmail.com<mailto:mespio@gmail.com>> 发送时间: 2021年4月8日 15:48 收件人: Daniel-Constantin Mierla <miconda(a)gmail.com<mailto:miconda@gmail.com>>; Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> 抄送: Dong Ming (董明) <dongming(a)twsz.com<mailto:dongming@twsz.com>> 主题: Re: [SR-Users] sip registration fail It seems the issue is related to some default configuration in IMS nodes in(pcscf, icscf and scscf). In pcap file, just pcscf node is appeared. please send full signaling flow in whole nodes. Thanks On Thu, Apr 8, 2021 at 11:06 AM Daniel-Constantin Mierla <miconda(a)gmail.com<mailto:miconda@gmail.com>> wrote: Hello, On 07.04.21 10:40, Dong Ming (董明) wrote: Hello I have a problem about volte(401 Unauthorized). P-CSCF: 4(4467) INFO: rr [rr_mod.c:515]: pv_get_route_uri_f(): No route header present. 4(4467) INFO: ims_registrar_pcscf [sec_agree.c:296]: cscf_get_security_verify(): No sec urity-verify parameters found Can you help me see where the problem is？ Tips：About SQN, the SQN is the same at the beginning of the test (Open5GS, FOHSS), but when it is found that the sip registration fails, the SQN is inconsistent. If this situation is normal? If it is not normal, how to solve it? I am not familiar with the IMS extensions, if nobody else comes with other suggestions, I recommend to set debug=3 in your kamailio configuration file and then look at the syslog, there should be a lot of DEBUG messages that may give more hints about what happens. Also, when sending Kamailio logs, do not make screen shots, just copy and paste them, it is easier to read as well as search in the source code for them by copy&paste. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com<http://www.asipto.com> www.twitter.com/miconda<http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda> Kamailio Advanced Training - Online May 17-20, 2021 (Europe Timezone) - June 7-10, 2021 (America Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/ _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- --Mojtaba Esfandiari.S 本电子邮件（包括任何的附件）为本公司保密文件。本文件仅仅可为以上指定的收件人或公司使用，如果阁下非电子邮件所指定之收件人，那么阁下对该邮件部分或全部的泄漏、阅览、复印、变更、散布或对邮件内容的使用都是被严格禁止的。如果阁下接收了该错误传送的电子邮件，敬请阁下通过回复该邮件的方式立即通知寄件人，同时删除你所接收到的文本。 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. -- --Mojtaba Esfandiari.S 本电子邮件（包括任何的附件）为本公司保密文件。本文件仅仅可为以上指定的收件人或公司使用，如果阁下非电子邮件所指定之收件人，那么阁下对该邮件部分或全部的泄漏、阅览、复印、变更、散布或对邮件内容的使用都是被严格禁止的。如果阁下接收了该错误传送的电子邮件，敬请阁下通过回复该邮件的方式立即通知寄件人，同时删除你所接收到的文本。 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

3 years, 3 months

sip registration fail

by Dong Ming (董明)

Hello I have a problem about volte(401 Unauthorized). P-CSCF: 4(4467) INFO: rr [rr_mod.c:515]: pv_get_route_uri_f(): No route header present. 4(4467) INFO: ims_registrar_pcscf [sec_agree.c:296]: cscf_get_security_verify(): No sec urity-verify parameters found Can you help me see where the problem is？ Tips：About SQN, the SQN is the same at the beginning of the test (Open5GS, FOHSS), but when it is found that the sip registration fails, the SQN is inconsistent. If this situation is normal? If it is not normal, how to solve it? open5gs：v2.2.3 kamailio：5.3 Thanks! 本电子邮件（包括任何的附件）为本公司保密文件。本文件仅仅可为以上指定的收件人或公司使用，如果阁下非电子邮件所指定之收件人，那么阁下对该邮件部分或全部的泄漏、阅览、复印、变更、散布或对邮件内容的使用都是被严格禁止的。如果阁下接收了该错误传送的电子邮件，敬请阁下通过回复该邮件的方式立即通知寄件人，同时删除你所接收到的文本。 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

3 years, 3 months

SSL handshake failed : X509 - Certificate verification failed, e.g. CRL, CA or signature check failed

by amitsharma＠coraltele.com

Hello Team, I am using Linphone with Kamailio and facing *SSL handshake failed : X509 - Certificate verification failed, e.g. CRL, CA or signature check failed* error over *TLS*. Following error is coming Apr 7 15:54:36 irisivdxcloud /usr/sbin/kamailio[9089]: ERROR: tls [tls_server.c:1290]: tls_h_read_f(): destination IP: 172.105.49.156 Apr 7 15:54:36 irisivdxcloud /usr/sbin/kamailio[9089]: ERROR: <core> [core/tcp_read.c:1500]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f2c7f85a2e0 r: 0x7f2c7f85a408 (-1) Apr 7 15:54:36 irisivdxcloud /usr/sbin/kamailio[9036]: WARNING: {1 20 REGISTER ~OkQyvT70a} sanity [sanity.c:612]: check_cl(): content length header missing in request Apr 7 15:54:40 irisivdxcloud /usr/sbin/kamailio[9040]: WARNING: {1 20 REGISTER ~OkQyvT70a} sanity [sanity.c:612]: check_cl(): content length header missing in request Apr 7 15:54:43 irisivdxcloud /usr/sbin/kamailio[9071]: ERROR: tls [tls_server.c:1283]: tls_h_read_f(): protocol level error Apr 7 15:54:43 irisivdxcloud /usr/sbin/kamailio[9071]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14094418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca Apr 7 15:54:43 irisivdxcloud /usr/sbin/kamailio[9071]: ERROR: tls [tls_server.c:1287]: tls_h_read_f(): source IP: 49.36.149.254 Apr 7 15:54:43 irisivdxcloud /usr/sbin/kamailio[9071]: ERROR: tls [tls_server.c:1290]: tls_h_read_f(): destination IP: 172.105.49.156 Apr 7 15:54:43 irisivdxcloud /usr/sbin/kamailio[9071]: ERROR: <core> [core/tcp_read.c:1500]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f2c7f85a2e0 r: 0x7f2c7f85a408 (-1) Apr 7 15:54:44 irisivdxcloud /usr/sbin/kamailio[9042]: WARNING: {1 20 REGISTER ~OkQyvT70a} sanity [sanity.c:612]: check_cl(): content length header missing in request Apr 7 15:54:44 irisivdxcloud /usr/sbin/kamailio[9072]: INFO: {1 674 REGISTER 583608109(a)192.168.1.105} <script>: REGISTRATION CALLED: 740,Count: 0,Contact: sip:740@117.242.44.49:3668;transport=TCP,Domain: location Please suggest, what is this issue all about. Thanks & Regards, Amit Sharma (Sr. Team Leader) (An ISO 9001:2008 company) Mobile: <tel:9891612004> tel:9891612004 PH: +91 120 2595870 Ext.: <tel:870> tel:870 Email : <mailto:amitsharma@coraltele.com> amitsharma(a)coraltele.com Web : <blocked::http://www.coraltele.com> www.coraltele.com

3 years, 3 months

fix_nated_sdp function

by Ilie Soltanici

Hello, Can someone point me to what is wrong with this SDP: ``` v=0 o=- 3826710256 3826710256 IN IP4 100.113.232.22 s=pjmedia b=AS:386 t=0 0 a=X-nat:0 m=audio 4012 RTP/SAVP 96 8 120 121 c=IN IP4 100.113.232.22 b=TIAS:96000 a=rtcp:4013 IN IP4 100.113.232.22 a=sendrecv a=rtpmap:96 opus/48000/2 a=fmtp:96 useinbandfec=1 a=rtpmap:8 PCMA/8000 a=rtpmap:120 telephone-event/48000 a=fmtp:120 0-16 a=rtpmap:121 telephone-event/8000 a=fmtp:121 0-16 a=ssrc:886437437 cname:61141a4c6ecaa55e a=crypto:1 AES_256_CM_HMAC_SHA1_80 inline:J9gds2sgq3OQccZ4fQoy3Oh9P2sWAXGHpLx+v/Ykh3gFQtAcaD8u5zpygEw2Dw== a=crypto:2 AES_256_CM_HMAC_SHA1_32 inline:yVCi20viRSxW+7hkUDjDBfXX4eAsuNrGj96ByTpDejOww8A0+BwSDjO40U1u3A== a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:9vWxWlHSBcLYv0p+qYTviva7Bc6tUb+fKblHaQ1D a=crypto:4 AES_CM_128_HMAC_SHA1_32 inline:UlLlQR2NB1owPDx7fFyGqnq09AVFVOLB50I3f/FC ``` I'm trying to apply function "fix_nated_sdp" to it, but getting back this error: <no `IP[4|6]' in `a=rtcp' field> By looking at the source code, seems that the nextissip value is 0, and that's why it fails (nextissip value:0/len:14) Any idea why?

3 years, 3 months

SNMP counter doesn't increase in stateful proxy

by Marat Gareev

Hello, I'm trying to get the total number of SIP request messages sent out by the proxy with *kamailioSIPSummaryOutRequest* scalar. But the value doesn't increase if I use t_relay() (with forward() counter works). Related thread <https://opensips.org/pipermail/users/2012-December/024045.html>. Is there another SNMP counter which contains a total number of OUT requests? Marat

3 years, 3 months

ERROR: connect_unix_sock: connect(/var/run/kamailio//kamailio_ctl): No such file or directory [2]

by Fadi Hamdan

Hi there, When I try to run: kazoo-kamailio status I'm getting this error: ERROR: connect_unix_sock: connect(/var/run/kamailio//kamailio_ctl): No such file or directory [2] Any solution for this error? Cheers, Hamdan, Fadi 24B Carrick Glen Avenue, Flat Bush, Auckland 2019 New Zealand fadi.h(a)msn.com<mailto:%20fadi.h@msn.com> M +64 21 066 0088

3 years, 3 months

SDP Change

by Nick Meyjes

Hi, I am trying to send calls to a provider that is switching to Nokia SBCs. They dont like seeing any IP other than our kamailio SBC in the messaging, I changed the contact but I cant find a way to change the owner line in the SDP I have try mangler and SDPOPS to change but neither seem to work on changing or removing the owner line Any ideas? Nick

3 years, 3 months

How to handle SIP-I(ISUP) with Kamailio

by Waseem Zaidi

Hi All: I am new to the list, I am struggling to find out Kamailio's capabilities with SIP-I/ISUP. I see that there is SIP-T module in kamailio and ss7ops module, but I need to get a hold on how to start. I would appreciate if someone could guide me. previously, I tried to use OpenSIPS SIP-I to extract ISUP from incoming calls, i was able to extract ISUP parameters in SDP body as xlog("Called Number: $isup_param_str(Called Party Number|Address signal)\r\n"); xlog("Calling Number: $isup_param_str(Calling Party Number|Address signal)\r\n"); xlog("Location is: $isup_param_str(Location Number)\r\n"); Location parameter is appearing as 0x04971400330268 which is wrongly interpreted. its proper interpretation should appear as 4100332086. I also tried below: xlog("Location is: $isup_param_str(Location Number|Address signal)\r\n"); but this subfield is not present. The transformation didn't make any difference: xlog("Location NUM: $(var(isup_body){isup.param, Location Number} Help pleeez ?

3 years, 3 months

Phase III clinical trials of Kamailio DMQ

by Alex Balashov

For immediate release: GAINESVILLE, Florida (1 April 2021)--Evariste Systems, in partnership with Posner | Palner Pharmaceuticals, are pleased to announce the eagerly anticipated start of Phase III clinical trials of Kamailio DMQ module replication. In this stage of the investigation of the promising replication scheme, which was developed in record time, DMQ will be tested in a rigourous, double-blind, controlled CI/CD process for large-scale efficacy and continually monitored for safety in shorter and longer terms. The now-concluded second phase established basic safety and Phase 2b entailed a dose-finding study for the optimal number of batched `dmq_usrloc` contacts per kilogram of cloud computing resource. The main cohort of the main sequence of the Phase III trial will enroll 380 randomly selected, statistically representative Floridian SIP registrars and 5700 SIP dialogs, also in the state of Florida. When asked about the disparity in the number of registrars versus dialogs, Alex Balashov of Evariste said, "It is reflective of the small number of SIP registrars in Florida; not to be indelicate, but consider the median age of the population." As previously remarked upon in proceedings of the World SIP Organisation (WSO), the choice of Florida as a venue attracted some questions. We asked Fred Posner of Posner | Palner about the clinical background informing this choice of replication study cohort: "Florida is a good place to find eventual consistency failures; the open climate and reluctance to accept traditional data integrity science would have sealed the deal, but when people started to drink bleach here, I saw an opportunity." Evariste and Posner | Palner are aiming for a US Food & Drug Administration EUA (Emergency Use Authorisation) for DMQ replication as a prophylactic data redundancy and failover measure to ward off the development of moderate to severe viral Sonus Haemorrhagic Fever symptoms. Phase II studies have painted a promising a picture of the DMQ architecture's ability to reduce moderate to severe symptoms and associated 28-day mortality by more than 90%, albeit over a small sample size and in enterprise patients with known pre-existing comorbidities such as Session Border Controller and BroadSoft Multi-System Inflammatory Syndrome. Phase III trials seek to bolster quantums of broader efficacy, including efficacy for localised outbreaks of small to medium business softswitch. Of the control group, Balashov said, "They will receive a standard pipe-to-/dev/null placebo protocol, but with identical '200 OK' confirmation messages. We proudly developed this approach in early 2020 in consultation with the highest levels of the Trump presidential administration; it is called TENP, or 'The Emperor's New Potion.' It is a successor to that administration's previous approved placebo protocol, SHTI - Small Hands, Tremendous Initiatives." Despite speculative autism and packet fragmentation claims by Florida Governor Ron DeSantis, Balashov was quick to provide reassurance about side effects from DMQ in the Phase III trial. "The incidence of severe allergies to plain-text UDP was within standard deviation over the mean for all insecure replication, and there's support for other transports on the way. Anyway, we have a robust adverse effects reporting system in our issue tracker and solid surveillance. Don't let partisan politics dissuade you from allowing request lines with the KDMQ method." Other industry sources have reported that DMQ is not the only replication investigation undertaken by Evariste and Posner | Palner, although it is the only prophylactic suitable for the early infection development and inflammatory phases of a broad class of SBC-complex syndromes typically afflicting service providers. A recent IETF preprint by the same authors has shown high-quality preliminary data suggesting statistically significant improvement in morbidity outcomes from Perimeta and Nokia via a later-stage therapeutic intervention with a monoclonal, monorepo Github cocktail administered intravenously. -- 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/

3 years, 3 months

Kamailio + Websocket issues

by Vinicius Kwiecien Ruoso

Hi! I'm using Kamaio in front of multiple Asterisk instances. At this moment it works as a SIP over Websocket proxy, with rtpengine, for browser clients to connect to Asterisk using WebRTC. I do not use the registration module of Kamailio, as each backend Asterisk is independent and handles its own registrations. Everything works great when making calls from the browser, and the routing is correctly executed by Kamailio based on the request SIP domain. We have an internal routing API that it calls to discover which backend Asterisk to route the calls. The issue I have is when a call initiates from that backend Asterisk, trying to reach a contact that is connected in Kamailio via the websocket. The Asterisk sends the message to the proxy, and Kamailio must route it to the corresponding websocket. I've tried a few approaches: - using add_contact_alias + handle_ruri_alias: I have the alias with alias=<ip>~<port>~ws in the contact registration, but for some reason handle_ruri_alias cannot use it - using the Path module on Asterisk, so when registering, the path is recorded and sent back from Asterisk, Kamailio is also not respecting that - Using contact_param_encode and contact_param_encode and contact_param_decode_ruri, but the encoded sip address is always the invalid websocket, like sip:58c0ktrg@5hp0nn5hqqv9.invalid;transport=ws None with success. Any hints on that can be wrong? I can share more detailed information. Greetings, Vinicius

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