sr-users June 2020

sr-users@lists.kamailio.org

71 participants
104 discussions

Presence and call queueing - Kamailio and Asterisk

by Pover A.V.

Summary: Using Kamailio to load balance between Asterisk servers. Trouble getting call queuing working because can't get device state hints to work reliably. - Hello I'd be grateful for any advice that can be offered for this problem to do with presence and call queueing. I have 3 Kamailio (v5.3.4) servers that load-balance incoming traffic from various sources: a legacy PBX, soft phone clients, and a SIP trunking service. Sitting behind the 3 Kamailio servers are 2 Asterisk (v16 LTS) servers. Kamailio acts as a registrar and user location service. Asterisk is routing calls and (should be) providing device state information for each extension. An external script builds a list of PJSIP endpoints based on the content of the Kamailio subscriber table, and deploys it to the Asterisk servers whenever a change is detected. The AOR for each record is configured to point to Kamailio. No authentication details are attached to these endpoints, as Kamailio is doing authentication before dispatching a request to Asterisk. Whenever Kamailio receives an INVITE, it passes this to an Asterisk server using the dispatcher module (round-robin algorithm '4'); asterisk then processes the request. At the moment, everything is working except for presence/device states and call queueing. I've tried to set up 'presence', 'pua', 'dialog' and '(presence/pua)_dialoginfo' modules on Kamailio with limited success. The presence state when a user toggles 'do not disturb' on their soft phone is passed to other users who are subscribed (watching), however when a user makes a call, no presence updates are seen by subscribed users (the extensions show as 'Idle' or 'Available' instead of 'In Use' or 'Busy'). Asterisk is able to report that an extension is 'Ringing' or 'InUse' when a call is made to that extension, because an INVITE to an internal extension matches a pattern in the dialplan and Asterisk routes it to a PJSIP endpoint with the same name. However, when somebody makes a call, Asterisk is unable to track the state of the extension making the call because the call is going via Kamailio so Asterisk is not seeing the caller as an internal extension. We need a way to make Asterisk think the call is coming from an internal device if the caller ID matches a PJSIP endpoint. Both Asterisk servers are configured to share device state updates with each other, and this is working. Without being able to see device state for an internal calling party, we will be unable to reliably set up call queues in Asterisk. Using the 'mohqueue' module on Kamailio is not something we want to do because of its reliance on a database, which is creating a single point of failure - if the database server is down for any reason, Kamailio refuses to start. Ideally, we would achieve some form of distributed call queueing, however the simplest option seems to be setting up a queue on one Asterisk server and having an active-passive high availability configuration, should a server go down. I'm looking for advice on how best to keep track of what is happening in a call, and for Asterisk to know the states of each extension and make these available in a dialplan hint. Or any other suggestions that might help to achieve call queueing in this setup. Thank you

3 years, 10 months

Dialog Profiles

by Ilie Soltanici

Hello, Is there any way in Kamailio to get the profile values the current dialog is part of? For example, I have one dialog with the following profiles: profiles: { { test: abcd } test: 1234 } I need in the reply route to get the values for the test dialog profile. (abcd, 1234). I know I can use get_profile_size, but that will give the number of profiles of the current dialog, but I need the values to loop through. Thanks.

3 years, 10 months

Kamailio I-CSCF not sending SIP:200 OK messages to Asterisk (to tag)

by Martin W Woscek

Hello all, SIP/UE (boghe or imsdroid) client registered to Kamailio makes call to an Asterisk registered SIP phone is successful: [UE]-Kamailio--->INVITE--->Asterisk16-[phone] [UE]-Kamailio--->200 OK with to_tag--->Asterisk16-[phone] But in reverse direction for a call, Kamailio does not return the SIP OK so no to_tag is sent so call fails to ring and complete: [phone]-Asterisk16 --->INVITE--->Kamailio Where the UE device never receives the INVITE, Asterisk never gets and 200 OK message with the to_tag from the I-CSCF, the call flow itself gets lost in Kamailio, where the P-CSCF sends final INVITE to I-CSCF and and ultimately a 604 HSS user unknown message is sent back to Asterisk from the I-CSCF. Basically Im using the default "sample" configs for both the P and the I-CSCF. Our sauce is in the S-CSCF for out going calls that originate by a registered UE. Any insight or sample Kamailio configuration that Im lacking? Has anyone done this and could share the asterisk and Kamailio script snippets that make it possible. Thanks, _Martin

3 years, 10 months

Kamailio ims video calls

by Pavithra Mohanraja

Hi, Could anyone please give me some idea on how video call works in IMS. Does it need rtp proxy to work? Or is it the same way how voice call works ? It would be good , if anybody share some links on video calls as well voice conferencing. Thanks, pavithra

3 years, 10 months

kamailio 5.2.2 enabling hashing_type

by Martin W Woscek

Hello, I'm revisiting some initial issues I had with P-CSCF. I could not set the hashing type in my PCSCF (kamalio 5.2.2) so I simply commented it out and moved on. But now, I may need it as the P-CSCF is not handling INVITES coming from I-CSCF that originated from external SIP server, where the endpoint (UE) is registered to the IMS but the P-CSCF sends the INVITE back to the S rather that the registered UE and fails. kamailio.cfg: modparam("ims_usrloc_pcscf", "hashing_type", 1) So with that, when I set the hashing_type to 1,1 or 2 I get the following starting the pcscf: Starting the P-CSCF: Jun 17 08:25:30 ubuntu kamailio_pcscf[5753]: * Not starting Kamailio IMS P-CSCF: invalid configuration file! Jun 17 08:25:30 ubuntu kamailio_pcscf[5753]: * Jun 17 08:25:30 ubuntu kamailio_pcscf[5753]: * 0(5766) ERROR: <core> [core/modparam.c:140]: set_mod_param_regex(): parameter <hashing_type> of type <2> not found in module <ims_usrloc_pcscf> Jun 17 08:25:30 ubuntu kamailio_pcscf[5753]: 0(5766) CRITICAL: <core> [core/cfg.y:3510]: yyerror_at(): parse error in config file /etc/kamailio/pcscf/kamailio.cfg, line 364, column 47: Can't set module parameter Am I missing some module that I did not include at compile time? According to the docs, it has no additional dependencies other than the ims_usrloc_pcscf.so https://kamailio.org/docs/modules/5.0.x/modules/ims_usrloc_pcscf.html#idp35… Any help is appreciated. Thanks, _Martin

3 years, 10 months

kamailio5.2.2 calling t_relay(host, port)

by Martin W Woscek

Hello all, Im trying to call t_relay() with host and port as documented in: https://www.kamailio.org/docs/modules/5.2.x/modules/tm.html However, I get a subst_str(): no match on P-CSCF start and therefore fails. Is t_relay(host, port) supported as documented? Am I missing something? Thanks, _Martin

3 years, 10 months

Expired transaction

by Marat Gareev

Hello! I'm trying to manually reproduce expired transactions which couldn't be cleared. I had one idea, but it was unsuccessful. I tried to send SIGSTOP to a group of Kamailio processes while the transaction is live. The idea is to freeze processes for a while, then continue to work, so that by this time the transaction deletion time was missed. But after a few seconds, the transaction is still cleared. Do you have any ideas for reproduction? P.S. I'm sorry If you received my incoherent mails. These were attempts to reply to the thread, seems to be my mail client or sr-users mailing list doesn't support In-Reply-To header.

3 years, 10 months

ERROR: pua [send_publish.c:304]: publ_cback_func(): No Expires header found

by Denys Pozniak

Hello! Could someone point me to the possible source of the problem? Jun 16 09:51:06 proxy-edge /usr/sbin/kamailio[9645]: ERROR: pua [send_publish.c:304]: publ_cback_func(): No Expires header found Jun 16 09:51:07 proxy-edge /usr/sbin/kamailio[9640]: ERROR: pua [send_publish.c:304]: publ_cback_func(): No Expires header found Jun 16 09:51:07 proxy-edge /usr/sbin/kamailio[9600]: ERROR: pua [send_publish.c:304]: publ_cback_func(): No Expires header found Jun 16 09:51:07 proxy-edge /usr/sbin/kamailio[9660]: ERROR: pua [send_publish.c:304]: publ_cback_func(): No Expires header found Modules settings: *loadmodule "pua.so"* *loadmodule "pua_dialoginfo"* *loadmodule "dialog.so" * *modparam("pua", "default_expires", 1200)* *modparam("pua", "outbound_proxy", LOCAL_IP_ADDR)* *modparam("pua_dialoginfo", "include_callid", 1)* *modparam("pua_dialoginfo", "include_localremote", 1)* *modparam("pua_dialoginfo", "include_tags", 1)* *modparam("pua_dialoginfo", "send_publish_flag", 8)* *modparam("dialog", "dlg_flag", 4)modparam("dialog", "db_mode", 0)modparam("dialog", "enable_stats", 1)modparam("dialog", "dlg_match_mode", 1)modparam("dialog", "default_timeout", 7200) modparam("dialog", "hash_size", 8192)* *request_route{* *...* *setflag(8);* *...* *}* Generated SIP PUBLISH: *PUBLISH sip:extension@sip.company.com <sip%3Aextension(a)sip.company.com> SIP/2.0* *Via: SIP/2.0/UDP 8.8.8.8;branch=z9hG4bK3e55.afdce977000000000000000000000000.0* *To: <sip:extension@sip.company.com <sip%3Aextension(a)sip.company.com>>* *From: <sip:extension@sip.company.com <sip%3Aextension(a)sip.company.com>>;tag=e98d9fc94bada9746d67946ab287a76f-ba77* *CSeq: 10 PUBLISH* *Call-ID: 72ef85f374c8e703-9659(a)10.10.10.10 <72ef85f374c8e703-9659(a)10.10.10.10>* *Content-Length: 578* *User-Agent: proxy* *Max-Forwards: 70* *Event: dialog* *Expires: 7201* *Content-Type: application/dialog-info+xml* *<?xml version="1.0"?>* *<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" entity="sip:extension@sip.company.com <sip%3Aextension(a)sip.company.com>">* * <dialog id="162092997-5060-464(a)BJC.BGI.CA.BBI" call-id="162092997-5060-464(a)BJC.BGI.CA.BBI" direction="initiator">* * <state>Trying</state>* * <remote>* * <identity>sip:1234567890@sip.company.com <sip%3A1234567890(a)sip.company.com></identity>* * <target uri="sip:1234567890@sip.company.com <sip%3A1234567890(a)sip.company.com>"/>* * </remote>* * <local>* * <identity>sip:extension@sip.company.com <sip%3Aextension(a)sip.company.com></identity>* * <target uri="sip:extension@sip.company.com <sip%3Aextension(a)sip.company.com>"/>* * </local>* * </dialog>* *</dialog-info>* -- BR, Denys Pozniak

3 years, 10 months

icscf start error

by Pavithra Mohanraja

Hi, I have installed kamailio - 5.3.4 version where i am facing below issues in icscf while starting kamailio. db_mysql is loaded but .. what could be the issue? icscf : Aliases: *: ims.sip.example.com:* 0(789) INFO: <core> [core/tcp_main.c:5042]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(791) INFO: pike [pike.c:97]: pike_init(): PIKE - initializing 0(791) INFO: pike [ip_tree.c:81]: init_lock_set(): probing 256 set size *0(791) ERROR: <core> [db.c:204]: db_bind_mod(): Module db_con1=>mysql not found. Missing loadmodule? 0(791) ERROR: ims_icscf [db.c:83]: ims_icscf_db_bind(): ims_icscf_db_bind: cannot bind to database module! Did you forget to load a database module ? 0(791) ERROR: ims_icscf [ims_icscf_mod.c:270]: mod_init(): Failed to initialise ims_icscf module 0(791) ERROR: <core> [core/sr_module.c:849]: init_mod(): Error while initializing module ims_icscf (/usr/lib/x86_64-linux-gnu/kamailio/modules/ims_icscf.so)* ERROR: error while initializing modules 0(791) INFO: cdp [cdp_mod.c:255]: cdp_exit(): CDiameterPeer child stopping ... 0(791) INFO: cdp [diameter_peer.c:367]: diameter_peer_destroy(): destroy_diameter_peer(): Terminating all children... 0(791) INFO: cdp [diameter_peer.c:386]: diameter_peer_destroy(): destroy_diameter_peer(): All processes terminated. Cleaning up. 0(791) INFO: cdp [worker.c:139]: worker_destroy(): Unlocking workers waiting on empty queue... 0(791) INFO: cdp [worker.c:142]: worker_destroy(): Unlocking workers waiting on full queue... 0(791) CRITICAL: cdp [diameter_peer.c:426]: diameter_peer_destroy(): destroy_diameter_peer(): Bye Bye from C Diameter Peer test 0(791) INFO: cdp [cdp_mod.c:257]: cdp_exit(): ... CDiameterPeer child stopped 0(791) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized

3 years, 10 months

Kamailio v5.3.5 Released

by Daniel-Constantin Mierla

Hello, Kamailio SIP Server v5.3.5 stable release is out. This is a maintenance release of the latest stable branch, 5.3, that includes fixes since the release of v5.3.4. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.3.x. Deployments running previous v5.3.x versions are strongly recommended to be upgraded to v5.3.5. For more details about version 5.3.5 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2020/06/kamailio-v5-3-5-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 years, 10 months

← Newer
1
2
3
4
5
6
7
8
...
11
Older →

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 June 2020