sr-users October 2018

sr-users@lists.kamailio.org

81 participants
124 discussions

Kamailio topoh and t_check_trans not working.
by José Seabra 17 Oct '18

17 Oct '18

Hi all, I noticed that using the module TOPOH with the parameter mask call id enabled and the t_check_trans together isn't working correctly. When i receive the BYE message my script call the function t_check_trans() in order to check if a message belongs or is related to a transaction. This function always returns false when used with the topoh mask call id enabled, once that the BYE belongs to an existing dialog it must return true. In the logs it says something like transaction doesn't match dialog using the RFC3261. If the TOPOH mask call id option is disabled everything works perfectly. Anyone here already faced this behavior? Thanks Regards -- José Seabra

2 3

Missing documentation
by Pan Christensen 16 Oct '18

16 Oct '18

Hello. The documentation for the ims_usrloc_scscf module seems to be missing: Not Found The requested URL /docs/modules/stable/modules/ims_usrloc_scscf.html was not found on this server. ________________________________ Apache/2.4.10 (Debian) Server at www.kamailio.org Port 443 Pan B. Christensen Utvikler Phonect AS Mail: pan.christensen(a)phonect.no<mailto:pan.christensen@phonect.no> + 47 41 88 88 00 [mail_footer]

4 5

Re: [SR-Users] Problem with callid as htable key
by Daniel-Constantin Mierla 16 Oct '18

16 Oct '18

If no operator is matched in the first two characters of expression part for $shtcn(...), then regexp is used. That's because initially the $shtcn() was doing only regexp matching, later it was added support for additional operators. Yes, == is the operator for equal. Cheers, Daniel On 16.10.18 11:53, jenus(a)cyberchaos.nl wrote: > Daniel, > > Ok so if i'm correct i can prefix the callid with for example 1234 to > avoid matching the eq. In other words eq will only match the regex > code if the callid string starts with it? > > And by mathing on equal you mean: $shtcn(ht_test=>==$var(htid)) ? > > Thanks, > > Jan > > Daniel-Constantin Mierla schreef op 2018-10-16 10:16: >> Just to add that regexp matching when using keys from the sip message >> such as call-id is exposed further to some issues -- for example, it is >> common to have . (dot) in call-id, which for a regexp is matching any >> char, so a call id having 123.456 is matching 123x456. So depending on >> what you want to count, might be better to match by equal or prefix >> rules. >> >> Cheers, >> Daniel >> >> On 16.10.18 10:03, jenus(a)cyberchaos.nl wrote: >>> Daniel, >>> >>> Thanks for the quick response, that indeed solves my problem. >>> >>> >>> Jan >>> >>> Daniel-Constantin Mierla schreef op 2018-10-16 09:55: >>>> Hello, >>>> >>>> the expression in the $shtcn(table=>exp) can have some operators at >>>> the >>>> beginning, see: >>>> >>>> - >>>> https://www.kamailio.org/wiki/cookbooks/devel/pseudovariables#shtcn_htable_… >>>> >>>> >>>> >>>> So, eq is one of them, the safest is to explicitly set the operator if >>>> you cannot predict what is the key, like in this case. If the operator >>>> is missing, then the exp is matched as regular expression, so you can >>>> do: >>>> >>>> $shtcn(ht_test=>~~$var(htid)) >>>> >>>> Cheers, >>>> Daniel >>>> >>>> >>>> On 16.10.18 09:47, jenus(a)cyberchaos.nl wrote: >>>>> Hello, >>>>> >>>>> I'm running kamailio 5.1.4 and running into a issue with htable. I >>>>> use >>>>> it to store some dialog data so i can use it in a http route. When i >>>>> use the callid as a key it creates a issue for callid's starting with >>>>> eq. Here some example code that i use to reproduce the issue: >>>>> >>>>> >>>>> modparam("htable", "htable", "ht_test=>size=16;autoexpire=10") >>>>> >>>>> $var(htable-val) = $_s($dlg(h_entry)) + "::" + $_s($dlg(h_id)) + "::" >>>>> + $Ts; >>>>> xlog("L_WARN", "HT_TEST: Adding $var(htable-val) to ht_test with key >>>>> eq1234"); >>>>> $var(htid) = "eq1234"; >>>>> $sht(ht_test=>$var(htid)) = $var(htable-val); >>>>> $var(htable-val) = $null; >>>>> >>>>> if ($shtcn(ht_test=>$var(htid)) > 0) >>>>> { >>>>> xlog("L_WARN", "HT_TEST: Key eq1234 found!"); >>>>> } else { >>>>> xlog("L_WARN", "HT_TEST: Key eq1234 NOT found!"); >>>>> } >>>>> $var(htid) = $null; >>>>> >>>>> Results in : >>>>> >>>>> Oct 16 09:36:31 sip03 /usr/sbin/kamailio[22344]: WARNING: <script>: >>>>> HT_TEST: Adding 531::926::1539675391 to ht_test with key eq1234 >>>>> Oct 16 09:36:31 sip03 /usr/sbin/kamailio[22344]: WARNING: <script>: >>>>> HT_TEST: Key eq1234 NOT found! >>>>> >>>>> >>>>> When i prefix eq with a 1 it works fine: >>>>> >>>>> modparam("htable", "htable", "ht_test=>size=16;autoexpire=10") >>>>> >>>>> $var(htable-val) = $_s($dlg(h_entry)) + "::" + $_s($dlg(h_id)) + "::" >>>>> + $Ts; >>>>> xlog("L_WARN", "HT_TEST: Adding $var(htable-val) to ht_test with key >>>>> eq1234"); >>>>> $var(htid) = "1eq1234"; >>>>> $sht(ht_test=>$var(htid)) = $var(htable-val); >>>>> $var(htable-val) = $null; >>>>> >>>>> if ($shtcn(ht_test=>$var(htid)) > 0) >>>>> { >>>>> xlog("L_WARN", "HT_TEST: Key eq1234 found!"); >>>>> } else { >>>>> xlog("L_WARN", "HT_TEST: Key eq1234 NOT found!"); >>>>> } >>>>> $var(htid) = $null; >>>>> >>>>> Results in: >>>>> >>>>> Oct 16 09:37:25 sip03 /usr/sbin/kamailio[22555]: WARNING: <script>: >>>>> HT_TEST: Adding 3050::1098::1539675445 to ht_test with key eq1234 >>>>> Oct 16 09:37:25 sip03 /usr/sbin/kamailio[22555]: WARNING: <script>: >>>>> HT_TEST: Key eq1234 found! >>>>> >>>>> >>>>> Am i running into a bug? Or are there some restrictions on the >>>>> key's i >>>>> can use? I'm still going trough the logs to check if there are more >>>>> callid's that have a issue with matching. >>>>> >>>>> >>>>> Thanks, >>>>> >>>>> Jan Hazenberg >>>>> >>>>> _______________________________________________ >>>>> 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 Kamailio World Conference -- www.kamailioworld.com Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

1 0

Re: [SR-Users] Problem with callid as htable key
by Daniel-Constantin Mierla 16 Oct '18

16 Oct '18

Just to add that regexp matching when using keys from the sip message such as call-id is exposed further to some issues -- for example, it is common to have . (dot) in call-id, which for a regexp is matching any char, so a call id having 123.456 is matching 123x456. So depending on what you want to count, might be better to match by equal or prefix rules. Cheers, Daniel On 16.10.18 10:03, jenus(a)cyberchaos.nl wrote: > Daniel, > > Thanks for the quick response, that indeed solves my problem. > > > Jan > > Daniel-Constantin Mierla schreef op 2018-10-16 09:55: >> Hello, >> >> the expression in the $shtcn(table=>exp) can have some operators at the >> beginning, see: >> >> - >> https://www.kamailio.org/wiki/cookbooks/devel/pseudovariables#shtcn_htable_… >> >> >> So, eq is one of them, the safest is to explicitly set the operator if >> you cannot predict what is the key, like in this case. If the operator >> is missing, then the exp is matched as regular expression, so you can >> do: >> >> $shtcn(ht_test=>~~$var(htid)) >> >> Cheers, >> Daniel >> >> >> On 16.10.18 09:47, jenus(a)cyberchaos.nl wrote: >>> Hello, >>> >>> I'm running kamailio 5.1.4 and running into a issue with htable. I use >>> it to store some dialog data so i can use it in a http route. When i >>> use the callid as a key it creates a issue for callid's starting with >>> eq. Here some example code that i use to reproduce the issue: >>> >>> >>> modparam("htable", "htable", "ht_test=>size=16;autoexpire=10") >>> >>> $var(htable-val) = $_s($dlg(h_entry)) + "::" + $_s($dlg(h_id)) + "::" >>> + $Ts; >>> xlog("L_WARN", "HT_TEST: Adding $var(htable-val) to ht_test with key >>> eq1234"); >>> $var(htid) = "eq1234"; >>> $sht(ht_test=>$var(htid)) = $var(htable-val); >>> $var(htable-val) = $null; >>> >>> if ($shtcn(ht_test=>$var(htid)) > 0) >>> { >>> xlog("L_WARN", "HT_TEST: Key eq1234 found!"); >>> } else { >>> xlog("L_WARN", "HT_TEST: Key eq1234 NOT found!"); >>> } >>> $var(htid) = $null; >>> >>> Results in : >>> >>> Oct 16 09:36:31 sip03 /usr/sbin/kamailio[22344]: WARNING: <script>: >>> HT_TEST: Adding 531::926::1539675391 to ht_test with key eq1234 >>> Oct 16 09:36:31 sip03 /usr/sbin/kamailio[22344]: WARNING: <script>: >>> HT_TEST: Key eq1234 NOT found! >>> >>> >>> When i prefix eq with a 1 it works fine: >>> >>> modparam("htable", "htable", "ht_test=>size=16;autoexpire=10") >>> >>> $var(htable-val) = $_s($dlg(h_entry)) + "::" + $_s($dlg(h_id)) + "::" >>> + $Ts; >>> xlog("L_WARN", "HT_TEST: Adding $var(htable-val) to ht_test with key >>> eq1234"); >>> $var(htid) = "1eq1234"; >>> $sht(ht_test=>$var(htid)) = $var(htable-val); >>> $var(htable-val) = $null; >>> >>> if ($shtcn(ht_test=>$var(htid)) > 0) >>> { >>> xlog("L_WARN", "HT_TEST: Key eq1234 found!"); >>> } else { >>> xlog("L_WARN", "HT_TEST: Key eq1234 NOT found!"); >>> } >>> $var(htid) = $null; >>> >>> Results in: >>> >>> Oct 16 09:37:25 sip03 /usr/sbin/kamailio[22555]: WARNING: <script>: >>> HT_TEST: Adding 3050::1098::1539675445 to ht_test with key eq1234 >>> Oct 16 09:37:25 sip03 /usr/sbin/kamailio[22555]: WARNING: <script>: >>> HT_TEST: Key eq1234 found! >>> >>> >>> Am i running into a bug? Or are there some restrictions on the key's i >>> can use? I'm still going trough the logs to check if there are more >>> callid's that have a issue with matching. >>> >>> >>> Thanks, >>> >>> Jan Hazenberg >>> >>> _______________________________________________ >>> 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 Kamailio World Conference -- www.kamailioworld.com Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

2 1

Problem with callid as htable key
by jenus＠cyberchaos.nl 16 Oct '18

16 Oct '18

Hello, I'm running kamailio 5.1.4 and running into a issue with htable. I use it to store some dialog data so i can use it in a http route. When i use the callid as a key it creates a issue for callid's starting with eq. Here some example code that i use to reproduce the issue: modparam("htable", "htable", "ht_test=>size=16;autoexpire=10") $var(htable-val) = $_s($dlg(h_entry)) + "::" + $_s($dlg(h_id)) + "::" + $Ts; xlog("L_WARN", "HT_TEST: Adding $var(htable-val) to ht_test with key eq1234"); $var(htid) = "eq1234"; $sht(ht_test=>$var(htid)) = $var(htable-val); $var(htable-val) = $null; if ($shtcn(ht_test=>$var(htid)) > 0) { xlog("L_WARN", "HT_TEST: Key eq1234 found!"); } else { xlog("L_WARN", "HT_TEST: Key eq1234 NOT found!"); } $var(htid) = $null; Results in : Oct 16 09:36:31 sip03 /usr/sbin/kamailio[22344]: WARNING: <script>: HT_TEST: Adding 531::926::1539675391 to ht_test with key eq1234 Oct 16 09:36:31 sip03 /usr/sbin/kamailio[22344]: WARNING: <script>: HT_TEST: Key eq1234 NOT found! When i prefix eq with a 1 it works fine: modparam("htable", "htable", "ht_test=>size=16;autoexpire=10") $var(htable-val) = $_s($dlg(h_entry)) + "::" + $_s($dlg(h_id)) + "::" + $Ts; xlog("L_WARN", "HT_TEST: Adding $var(htable-val) to ht_test with key eq1234"); $var(htid) = "1eq1234"; $sht(ht_test=>$var(htid)) = $var(htable-val); $var(htable-val) = $null; if ($shtcn(ht_test=>$var(htid)) > 0) { xlog("L_WARN", "HT_TEST: Key eq1234 found!"); } else { xlog("L_WARN", "HT_TEST: Key eq1234 NOT found!"); } $var(htid) = $null; Results in: Oct 16 09:37:25 sip03 /usr/sbin/kamailio[22555]: WARNING: <script>: HT_TEST: Adding 3050::1098::1539675445 to ht_test with key eq1234 Oct 16 09:37:25 sip03 /usr/sbin/kamailio[22555]: WARNING: <script>: HT_TEST: Key eq1234 found! Am i running into a bug? Or are there some restrictions on the key's i can use? I'm still going trough the logs to check if there are more callid's that have a issue with matching. Thanks, Jan Hazenberg

2 2

Problem with Kamailio 4.2.0
by José Antonio Gutiérrez Delgado 16 Oct '18

16 Oct '18

Hi, I'm using Kamailio 4.2.0 and I'm developing a SIP-based application. Today I made a test connecting two devices directly to an S7 sharing the Internet, I usually use a VPN even if they are both connected to the same network because in the future they will be in different networks.Without the VPN calls were not received. This has never happened to me, I have repeated tests and in an S6 it has also happened to me. So I have checked my Kamailio server and I have detected that when executing: kamctl ul show, the received field did not appear: With VPN: Contact:: sip:pruebaT@47.60.42.40:10924;transport=udp Q= Expires:: 1992 Callid:: iwNoYb~QR- Cseq:: 21 User-agent:: Unknown (belle-sip/1.6.1) Received:: sip:47.60.42.40:10924 State:: CS_NEW Flags:: 0 Cflag:: 64 Socket:: udp:10.0.0.4:5060 Methods:: 4294967295 Ruid:: uloc-5a9d9097-9fa-431c Instance:: <urn:uuid:8b50dde3-d07f-4752-9a24-7b8ddf219a99> Reg-Id:: 0 Last-Keepalive:: 1539614732 Last-Modified:: 1539614732 Without VPN: Contact:: sip:pruebaT@37.10.156.189:51163;transport=udp Q= Expires:: 1996 Callid:: webjvHycBs Cseq:: 21 User-agent:: Unknown (belle-sip/1.6.1) State:: CS_NEW Flags:: 0 Cflag:: 0 Socket:: udp:10.0.0.4:5060 Methods:: 4294967295 Ruid:: uloc-5a9d9097-9fc-1feb Instance:: <urn:uuid:89306a81-e2d1-4b7a-8206-107e3cbc0688> Reg-Id:: 0 Last-Keepalive:: 1539614531 Last-Modified:: 1539614531 Would someone know why it happened? Thanks -- José Antonio Gutiérrez Delgado Responsable técnico Oficina: (+34) 923040031 <http://www.arsoft-company.com/> *Este mensaje se dirige exclusivamente a su destinatario/s y puede contener información privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.* *Antes de imprimir, piensa si es necesario. Cuidar el medioambiente es tarea de todos.*

3 2

Hi guys,
by shailendra kumar 15 Oct '18

15 Oct '18

I am fresher and want to learn about Kamailio Soft switch, Anyone can provide me link or document from where i can learn. I will be thankful for such help, Thanks & Regards, Shailendra Kumar

2 1

Subscription from asterisk
by willy 15 Oct '18

15 Oct '18

Hello all. I'm trying to share states and presence from kamailio between asterisks. Is there a way to do this in kamailio? Thank you, willy d

2 1

SDP in fifth 200 OK is not the same as in first four
by Roman Romanchenko 15 Oct '18

15 Oct '18

Hi all, I have an issue with SDP from Kamailio side in the following scenario: simple call from A to B. When B answers a call and sends '200 OK' to A, A delays ACK for a while, so '200 OK' re-transmission happens. After the fourth try to re-send '200 OK' towards A, Kamailio changes SDP (specifically connection information 'c', IP address become address of A instead of proxy IP as it was in the previous attempts). At some point A sends ACK and call is established, but last received '200 OK' has invalid SDP and it prevents successful media establishment. I wonder if there any re-transmission counter or whatever what can affect this scenario and change SDP? Roman Romanchenko VoIP devel Sipwise GmbH

2 1

Dialog variables and persistence
by Alex Balashov 15 Oct '18

15 Oct '18

Hi, I forget, can $dlg_var(...) variables nowadays be reconstituted, along with dialog state in general, using database backing? What about profile membership? Last time I brushed with this topic was probably in 4.x days, and as I remember the general idea was that dialog state could be recovered on restart, but without dialog variables or profile counts. Is this accurate? Is it still true? Or has the amount of state serialised into database persistence increased since then? Thanks much! -- Alex -- 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/

2 1

← Newer
1
...
5
6
7
8
9
10
11
12
13
Older →

2026

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 October 2018