sr-users February 2020

sr-users@lists.kamailio.org

57 participants
71 discussions

by Dovid Bender

Hi, We are fighting with a vendor and trying to explain to them that call routing should be based on the RURI on the INVITE and *not* the To header. I went through RFC 3261 and while there are many "indicators" and it seems like its screaming that we should be using the RURI, is anyone aware of any specific text (that I may have missed) where it says specifically call routing should be done based on the RURI and *NOT* the to header? TIA. Dovid https://tools.ietf.org/html/rfc3261#page-78 1) 8.1.1.1 Request-URI *The initial Request-URI of the message SHOULD be set to the value of the URI in the To field.* - Note that it says SHOULD but is NOT mandatory. Also this is for the *INITIAL* request. *This may or may not be the ultimate recipient of the request.* - Again this is the To field. The RURI is what we are supposed to follow when we want to know where the call should be delivered to. 2) 8.1.2 Sending the Request -Usage of the URI from the *To and From fields in the original request within subsequent requests is done for backwards compatibility with RFC 2543*, which used the URI for dialog identification. *In this specification, only the tags are used for dialog identification*. It is expected that mandatory reflection of the original To and From URI in mid-dialog requests will be deprecated in a subsequent revision of this specification. - While this is for subsequent requests (and not an original one) you see that the only point of the To field is to identify the dialog. 3) 8.2.2.1 To and Request-URI The To header field identifies the *original recipient of the request* designated by the user identified in the From field. - Note that the TO field identifies the ORIGINAL recipient, this **CAN** change. This is basically telling you that you *can't* rely on the To header for routing. *However, the Request-URI identifies the UAS that is to process the request*. - As you can see the Request-RU and *NOT* the TO header tells you where the request should go. 5) 12.2.1.1 Generating the Request a. The UAC uses the *remote target* and route set to build the *Request-URI and Route header field of the request*. - This is self explanatory. it shows that the RURI is using for routing and *NOT* the to header. b. The procedures in Section 8.1.2 will normally result in the request being *sent to the address* indicated by the topmost Route header field value or the *Request-URI* if no Route header field is present. Subject to certain restrictions, they allow the request to be sent to an alternate address (such as a default outbound proxy not represented in the route set). Again self explanatory. 6) 16.5 Determining Request Targets Each target in the set is *represented as a URI*. - This clearly shows that how we route is based on the RURI and *NOT* the to header. 7) 26.5 Privacy Thus it MAY be desirable for privacy reasons to create a To header field that differs from the Request-URI. - Again this shows that the to may not match up the RURI. Think of the To header as the contact in someones phone and the RURI as where we are calling. The to header may be bob(a)1.1.1.1 but the URI is where we are actually calling which is 12346(a)1.1.1.1 or bob_smith(a)1.1.1.1.1

4 years, 2 months

Kamailio presence when account not equal extension

by Zhan Bazarov

Hello, I'm using presence and pua modules, it works perfectly when username is equal to extension... But now I have case when username is not equal to the extension.. Like: extension: 1111 username: aythnbghhgt How I can implement this? Any ideas? -- Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html

4 years, 2 months

CentOS 8 RPMs missing from OBS

by Anthony Alba

The 5.3.2-4 builds for CentOS 8 are not available here: https://download.opensuse.org/repositories/home:/kamailio:/v5.3.x-rpms/Cent… Is https://rpm.kamailio.org/centos/8/5.3/5.3.2/x86_64/ aka Pulp the official release location now? (With -0 builds) For CentOS 7 Pulp has 5.3.2-0 and OBS has 5.3.2-4. The version mismatch is confusing. Cheers Anthony

4 years, 2 months

Kamailio presence when account not equal extension

by Zhan Bazarov

4 years, 2 months

acc_radius

by volga629

4 years, 2 months

Understanding some usrloc modparams

by Joel Serrano

Hello, I have an installation using usrloc + db_mode=1. If I want on db_mode=1 or db_mode=2 the expired contacts to be cleaned up I have to enable the modparam db_timer_clean: https://www.kamailio.org/docs/modules/devel/modules/usrloc.html#usrloc.p.db… The docs say: "*Enable (1) or disable (0) cleaning of expired db records on timer basis for db_mode WRITE-BACK and WRITE-THROUGH. It uses the secondary timer process.*" I have the following doubts: 1- What does the reference "it uses *the* secondary timer process" mean? Is there a specific secondary timer just for this purpose? 2- Is #1 related to the modparam timer_procs? (so it uses one of those when enabled?) 3- Why/When would you need a timer_proces modparam with a value higher than "1"? Thanks, Joel.

4 years, 2 months

Active-Active Registrar setup with users behind NAT persistence in event of server failure

by Jonathan Hunter

Hi Guys, I have a quick question wondered if anyone could provide some suggestions please?! We have a setup of two registrars in EC2 (kamailio 4.4 running on debian VMs) which act in an active/active fashion with a number of devices behind NAT where we use the DMQ dmq_t_replicate function to send the registration details between each server and append the PATH parameter so the registrar the device registered with is always associated with the client device. This all works fine, the only issue is persistency should we have a failure of one of the registrars, be it process or server and recovering the correct PATH detail so the end device can still be reached. I have tried this with separate databases with each registrar, which works when using cache and db but I ideally want the same database for the two servers and not change the architecture at this time unless it is a necessary. I have also tested with dmq_usrloc but this again provides the usrlocation details of the notification servers in the group(not path), again which I understand but I wondered if there is anything else I could try or its just a question of in the event of a failure half the registrations will be effected until it recovers and they re-register again if I dont want to have separate databases (location tables) or I add more network elements into the flow, such as HA pair or load balancer but just want to make sure I have exhausted all options or consider the risk before I look to do this. Many thanks! Jon

4 years, 2 months

IMS Third party Register issue

by Lanvin ADON

Hi All, I'm facing an issue with the third party registration in the ISC interface between the SCSCF and the AS. The AS is triggered for deregistration but not for registration. Attached are logs for a register that not works and a deregister that works Regards Lanvin ADON

4 years, 2 months

Documentation Broken Link

by Sam Ware

On the http://www.kamailio.org/w/documentation/ page, the Docbook tutorials <http://sip-router.org/docbook/sip-router/branch/master/> link is broken. -- Sam D Ware

4 years, 2 months

xlog() format change from 5.3 to 5.4-nightly

by Joel Serrano

Hello, I've noticed that the output format of xlog() changes from 5.3 to 5.4-nightly. v5.3 xlog(): Feb 13 11:56:35 csbc01 csbc[27333]: NOTICE: {1 24727 REGISTER b1d374f6-9b8c53ff(a)A.B.C.D} <script>: [log] auth successful v5.4-nightly xlog(): Feb 13 11:56:35 csbc01 csbc[27333]: NOTICE: {1 24727 REGISTER b1d374f6-9b8c53ff(a)A.B.C.D} <script>: xlog_helper(): [log] auth successful Is there a way to avoid adding the extra "*xlog_helper():*" string? We have a lot of scripts that parse the K logs for different reasons and I would like to avoid having to update them all to match the new format. I've tried adding *modparam("xlog", "prefix", "")* but it only affects the "<script>:" part and not the "xlog_helper():" part. Thanks, Joel.

4 years, 2 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 February 2020