sr-users June 2019

sr-users@lists.kamailio.org

63 participants
92 discussions

Re: [SR-Users] ICSCF mysql error
by Henning Westerholt 07 Jun '19

07 Jun '19

Hello, not an expert on this particular module, but this is the internal error path from the module that probably caused this error reply: - case RC_IMS_DIAMETER_ERROR_USER_UNKNOWN, will send message with: - #define MSG_604_USER_UNKNOWN "Does not exist anywhere - HSS User Unknown" The status comes probably from the CDP module: diameter_epc_code_result.h 57: RC_EPC_DIAMETER_ERROR_USER_UNKNOWN = 5001, Maybe this helps. Henning Am 03.06.19 um 06:43 schrieb Trinh, Jenny: Hi, I’m getting the error 604 when ICSCF did a query to mysql and failed with an INVITE. Please see my attached pcap. Would appreciate any feedbacks on what might the issue. We’re using BOGHE client to register and make call with Kamailio IMS 5.2.2 May 22 09:15:10 imskamailio /usr/local/sbin/kamailio[22167]: DEBUG: <core> [core/msg_translator.c:2305]: generate_res_buf_from_sip_res(): copied size: orig:143, new: 56, rest: 630 msg=#012SIP/2.0 604 Does not exist anywhere - HSS User Unknown#015#012Via: SIP/2.0/UDP 0.0.0.0:4060;received=10.0.20.1;branch=z9hG4bK3c92.7402885f6124cf2862bde6f9458080b5.0#015#012Via: SIP/2.0/UDP 10.141.161.85:56962;received=10.141.161.85;branch=z9hG4bK594030036;rport=56962#015#012From: <sip:bob@ims522.irisims.org><mailto:sip:bob@ims522.irisims.org>;tag=594048364#015#012To: <sip:alice@ims522.irisims.org><mailto:sip:alice@ims522.irisims.org>;tag=077cecf844e3c5622044f0dc84818fc7-09fb#015#012Call-ID: 25759faf-6f50-5607-c8f9-162abbbff8cb#015#012CSeq: 19622 INVITE#015#012Server: Kamailio I-CSCF#015#012Content-Length: 0#015#012Warning: 392 10.0.20.1:5060 "Noisy feedback tells: pid=22149 req_src_ip=10.0.20.1 req_src_port=6060 in_uri=sip:alice@ims522.irisims.org<mailto:in_uri=sip:alice@ims522.irisims.org> out_uri=sip:+alice@ims522.ir<mailto:out_uri=sip:+alice@ims522.ir> Thank you _______________________________________________ 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 -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services

2 1

Using DNS in Dispatcher for SRV Clarification
by JR Richardson 07 Jun '19

07 Jun '19

Hey All, I'm in the lab testing kamailio 5.2 with DNS SRV records. The scenario is simple, using dispatcher with hard coded IP URIs [sip:10.10.10.10:5060] and also a DNS name URI [sip:sip.domain.com]. There are 2 SRV servers. The DNS SRV records are setup and resolving OK, during startup, kamailio list the DNS name in the dispatcher list. During a call scenario, when the dispatcher selects the DNS name URI for the next destination, the TM module takes over, resolves the _sip._udp.sip.domain.com for both SRV records OK and sends the call to the first SRV server in the list. But if I take the first SRV server offline, make another call, the TM module does not route to the second SRV server until the DNS record timeout is reached, in my lab was set for 300 seconds. I decreased the DNS SRV record TTL down to 5 seconds with same results above, but 5 seconds lapse when TM routes call to next SRV server. I think this is working as expected but not sure if this is by design so my question is, should the TM module route to another SRV server in the list in the event of a no response timeout or send the transaction back to the dispatcher to select another target? Should I play around with the TM Module parameter "max_noninv_lifetime" to get quicker results or it is better to have DNS SRV record TTL set really low? Thanks. JR -- JR Richardson Engineering for the Masses Chasing the Azeotrope

2 1

Re: [SR-Users] ICSCF mysql error
by Daniel-Constantin Mierla 06 Jun '19

06 Jun '19

Hello, check you kamailio configuration file, the 604 reply is likely to be generated there -- although I haven't written any of the ims modules, typically the reply generated by kamailio are from configuration file, not hardcoded in the source. Cheers, Daniel On 03.06.19 06:43, Trinh, Jenny wrote: > > Hi, > > I’m getting the error 604 when ICSCF did a query to mysql and failed > with an INVITE. Please see my attached pcap. Would appreciate any > feedbacks on what might the issue. > > > > We’re using BOGHE client to register and make call with Kamailio IMS 5.2.2 > > > > May 22 09:15:10 imskamailio /usr/local/sbin/kamailio[22167]: DEBUG: > <core> [core/msg_translator.c:2305]: generate_res_buf_from_sip_res(): > copied size: orig:143, new: 56, rest: 630 msg=#012SIP/2.0 604 Does not > exist anywhere - HSS User Unknown#015#012Via: SIP/2.0/UDP > 0.0.0.0:4060;received=10.0.20.1;branch=z9hG4bK3c92.7402885f6124cf2862bde6f9458080b5.0#015#012Via: > SIP/2.0/UDP > 10.141.161.85:56962;received=10.141.161.85;branch=z9hG4bK594030036;rport=56962#015#012From: > <sip:bob@ims522.irisims.org>;tag=594048364#015#012To: > <sip:alice@ims522.irisims.org>;tag=077cecf844e3c5622044f0dc84818fc7-09fb#015#012Call-ID: > 25759faf-6f50-5607-c8f9-162abbbff8cb#015#012CSeq: 19622 > INVITE#015#012Server: Kamailio I-CSCF#015#012Content-Length: > 0#015#012Warning: 392 10.0.20.1:5060 "Noisy feedback tells: pid=22149 > req_src_ip=10.0.20.1 req_src_port=6060 > in_uri=sip:alice@ims522.irisims.org out_uri=sip:+alice@ims522.ir > > > > Thank you > > > _______________________________________________ > Kamailio (SER) - Users Mailing List > sr-users(a)lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

Use dmq module with private and public IP addresses
by Markus Bönke 05 Jun '19

05 Jun '19

Hello NG, I have a question regarding the dmq / dmq_userloc module. In my test setup have 2 Kamailio servers in 2 different data centers. The data centers are interconnected by a crosslink. Each Kamailio server has configured an internal (private) and an external (public) IP address. The internal IPs are routed to use the crosslink. The external IPs are routed through the public internet by different ISPs. The requirement is that the replication should primarily be routed via the crosslink, only if the crosslink is down it should be routed via public internet. As I understand the „server_address“ parameter can have only one IP address. If I configure the public IPs on both sides and one ISP connection gets disconnected, packets will NOT be routed automatically via the crosslink. And the other way around, if I configure the private IPs on both sides and the crosslink gets disconnected, packets will NOT be routed automatically via public internet. Is there any way to setup and use dmq for such a scenario ? Thanks and regards Markus

2 3

IMS - change the transport layer protocol for Diameter based interfaces (especially Rx)
by "björn bauer" 04 Jun '19

04 Jun '19

3 2

RTPEngine and dialog moving.
by Igor Olhovskiy 04 Jun '19

04 Jun '19

Hi! Wanted to clarify some info about rtpengine working within HA-environment. Idea is we have multiple rtpengines under same setid. So, when I'm calling rtpengine_offer() I really don't care which is selected. But than might happen situation, where this call(dialog) is moved to other Kamailio instance (via dlg_db_load_callid()) and from there called rtpengine_delete(). So, my question is, how I can be sure, that delete request will go to same rtpengine instance that was selected in rtpengine_offer() on different server. And where this info is stored, within dialog or within TM module (which is not replicated in any way) Regards, Igor

3 4

Info: app_lua_sr module - old Lua sr library
by Daniel-Constantin Mierla 04 Jun '19

04 Jun '19

Hello, several days ago I split the app_lua module, relocating the code related to old Lua sr library to app_lua_sr module, keeping in this way app_lua smaller and focused to the KEMI code. Over the time, app_lua_sr should be deprecated and removed, as we are sure the functions in Lua sr have an equivalent in Lua KSR. Therefore, if you are using in Lua scripts functions from 'sr' library, consider migrating to KSR as soon as possible. The intermediary solution for a quick upgrade to master version (to be release as v5.3.x) is to load app_lua_sr and update some modparams, like: loadmodule "app_lua.so" loadmodule "app_lua_sr.so" modparam("app_lua_sr", "register", "sl") If you find a function from Lua sr not available in Lua KSR, then report it via mailing lists or bug tracker. An article about this topic was published at: * https://www.kamailio.org/w/2019/05/new-module-app_lua_sr/ Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

Multiple definitions with OR or AND in "ifdef" in kamailio script
by Maxim M 04 Jun '19

04 Jun '19

Is it possible to do something like this in kamailio script?: !!ifdef DEF1 || DEF2 .... !!endif

2 1

empty action lists in route block
by Maryam Baghdadi 04 Jun '19

04 Jun '19

Hello everyone! I tried to use from Lua scripting language in kamailio configuration and rewrite all routes in Lua script. and I export many functions in ims_auth in KEMI and recompile ims_auth module. I have a problem with www_ims_challenge function calling in Lua script. when I define and call a function (REG_MAR_ROUTE) in www_ims_challenge as a route black, I get this error " empty action lists in route block" . why this happens and what's the solution ? thanks in advance

3 2

Removal of Dispatcher
by Colin, Andrew 04 Jun '19

04 Jun '19

I am using the API to remove dispatchers with a simple curl command, is there a way i can make kamailio check that there are sufficient dispatchers available before removing them when the command is run? Example: i am removing asterisk1 out of kamailio dispatcher list, but kamailio needs to ensure that there is atleast 2 or 3 other asterisk servers active in the list before it allows it to be removed. any ideas how i can achieve this?

2 3

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

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