Hi,
I would like to report an issue which crashes kamailio quite often.
I am running kamailio on Debian 10:
*version: kamailio 5.4.3 (x86_64/linux) 06bd17-dirtyflags: USE_TCP,
USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST,
DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC,
DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE,
USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES,
TLS_PTHREAD_MUTEX_SHAREDADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE
262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MBpoll method
support: poll, epoll_lt, epoll_et, sigio_rt, select.id: 06bd17
-dirtycompiled on 13:03:02 Mar 2 2021 with gcc 8.3.0*
A crash message with an error from syslog. (see attachment)
Thank you for your help.
Hello,
I am considering to release Kamailio v5.4.5 sometime next week, likely
on Thursday, April 15, 2020. 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.comwww.twitter.com/miconda -- 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/
Hello guys !!!
i'm a beginner in kamailio technology and i want to use kamailio http_client module to get data from API, but
i got :
Access error : Unauthorized
Access Denied Wrong Password
My user IDs are correct. API's encryption is MD5 (digest Auth ).
So i use:
modparam("http_client", "authmethod", 2)
...
modparam("http_client", "cipher_suites", "ecdhe_ecdsa_aes_128_gcm_sha_256, rsa_aes_128_gcm_sha_256")
then
modparam("http_client", "cipher_suites", "rc4-md5")
Can someone help me please ?
Test topology using K 5.4 where topos module is loaded in Proxy1:
A - Proxy1 - Proxy2 - Proxy1 - B
A sends INVITE, B responds with 183 Session Progress, and A sends PRACK.
The result is that PRACK starts to loop in second Proxy1 instance
instead of being forwarded to B.
If topos module is not loaded in Proxy1, it forwards PRACK to B as it
should.
Also, if Proxy1 loads topos module, but A does not send PRACK, other
in-dialog requests (e.g. BYE) work fine.
-- Juha
Hello,
We have been using the kamailio-python plugin with kamailio, running on
CentOS 7. The RPM for the kamailio-python plugin has a requirement on the
python36 package. I'm curious if it's possible to run kamailio with
the kamailio-python plugin with python 3.7 or if python 3.6 is required. If
it is possible to use the kamailio-python plugin with python 3.7, would we
need to create our own RPM with a requirement on python37 or is there
another way we could set it up?
Thank you very much for your feedback,
Aaron
Aaron Lucia | Software Engineer
100 High Street, 7th Floor, Boston, MA 02110 USA
www.cogitocorp.com | Cogito on LinkedIn
<https://www.linkedin.com/company/cogito-corp-/> | Office: 617.580.3101
Confidentiality Notice : This email is the property of Cogito Corporation.
This message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential and/or privileged
information. Any unauthorized review, use, disclosure or distribution is
prohibited. If you are not the intended recipient, please contact the
sender by reply email and destroy all copies of the original message.
Hi all,
I'm trying in KEMI & Python to set a Pseudo Variable to the value of
another PV (simple enough) but the value of the PV is not a string or an
integer,
For example the SMSops
<https://github.com/kamailio/kamailio/tree/master/src/modules/smsops>
module has a PV called $smsbody which I need to set the message body to
equal in UAC, but I'm not able to load it to set it as the message body,
In my Python file I have:
smsbody = KSR.pv.get("$smsbody")
Which leads to:
kamailio[226069]: UnicodeDecodeError: 'utf-8' codec can't decode byte 0x91
in position 7: invalid start byte
kamailio[226069]: 2(226069) DEBUG: app_python3 [apy_kemi.c:112]:
sr_kemi_config_engine_python(): execution of route type 1 with no name
returned -1
*Is there a way to set a PV in Kemi without actually interpreting it?*
*Is there a way to run an arbitrary line of native Kamailio config from
Kemi like KSR.x.modf? *
In reality all I need to do is:
$uac_req(body) = $smsbody;
Would work fine in the native config, but the equivalent in Kemi tries to
parse the contents and fails, so can't set the body.
Cheers,
Nick
Does anyone know how to connect my kamailio server on the other side with metaswitch?
I need to configure Kamailio IMS for cross-domain SIP calls.
Thanks
Gustavo
Legal Disclaimer :
The information contained in this message may be privileged and confidential.
It is intended to be read only by the individual or entity to whom it is addressed
or by their designee. If the reader of this message is not the intended recipient,
you are on notice that any distribution of this message, in any form,
is strictly prohibited. If you have received this message in error,
please immediately notify the sender and delete or destroy any copy of this message!
Hi
I am using the dispatcher module with Kamailio as a front-end
Registrar/LB in front of a cluster of Asterisk boxes. I have come across
an issue with SUBSCRIBE messages not getting routed to the correct
server in the event that the phone endpoint's dispatch set is changed.
It will still go to the old server until such time as the phone is rebooted.
The reason this is happening is because the 200 OK in the response from
the Asterisk server has Contact set to its own IP:port and subsequent
in-dialog reSUBSCRIBE are sent with the original Asterisk ip:port in the
RURI. When Kamailio receives these reSUBSCRIBE it does not change the
RURI even though ds_select_dst is being called in the [WITHIN_DIALOG] route.
My feeling is I have two choices - either alter the Contact in the reply
from Asterisk, or, change the RURI manually on receipt of an in-dialog
SUBSCRIBE.
Has anyone else come across this, or have advice on the best way to
handle this?
Thanks
--
-Barry
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.
