sr-users October 2018

sr-users@lists.kamailio.org

81 participants
124 discussions

UPDATE relayed from wrong socket
by Sergiu Pojoga 15 Oct '18

15 Oct '18

Hi ppl, I have this problem with call transfer, may be someone can help. The phone to the far right is registered with the Registrar to the far left using two PATH headers (trespassing two proxy ports, 5070 then 5060). As you can see in the graph below, after receiving the UPDATE request, Kamailio relays it further from port 5060, I expect it to be from 5070 just like the dialog forming INVITE and the CANCEL afterwards. [image: image.png] The UPDATE has a to-tag, but unlike the original INVITE - it has no Route header!??? route[*WITHINDLG*] { if (!has_totag()) return; if (loose_route()) { route(DLGURI); if (is_method("BYE")) { ... } else if ( is_method("ACK") ) { route(NATMANAGE); } else if ( is_method("NOTIFY") ) { record_route(); } route(RELAY); exit; } if ( is_method("ACK") ) { ... } # handle UPDATE method for in-dialog requests if (is_method("*UPDATE*")) { route(DLGURI); record_route(); route(RELAY); } } Thanks in advance.

2 7

Distorted uri / Route header replaces the uri
by Abdulaziz Alghosh 15 Oct '18

15 Oct '18

Greetings, in order to upgrade kamailio server from 3.0.3 to 5.1.4 version, I am conducting test calls and it is not completelly successful. The main components I have are: 1- Media Gateway (Asterisk) : 192.168.226.133 2- Signalling Gateway (Kamailio 5.1.4) 192.168.226.132 3- Global Dispatcher (Kamailio 3.0.3 in front of the Signalling Gateway.) : 192.168.226.130 Both caller and callee have the dispatcher's IP as a proxy and their registration requests is passed to be registered at the Signalling Gateway (Kamailio 5.1.4) and saved on the MySQL server. The caller reaches the callee properly, who in its turn answeres the call and sends the OK msg to the caller who gets it. Unfortunately, when the caller sends the ACK for this INVITE to the callee, the ACK does not reach the callee because it is trapped by the dispatcher at the last stage because the uri was dropped and the Route header was used instead. This behaviour is abnormal since as I know the Route header should be converted into a Via header and the uri stays untouchable. The ACK was looped into the dispatcher itself .i.e. the dispatcher sent it to itself adding always the via header ""Via: SIP/2.0/UDP 192.168.226.130;branch=0"" endlessly. Once again, here is an example of the ACK before the dispatcher and how the dispatcher forwards the ACK afterwards. the supposed path is as following: caller --> GDP--> SGW --> MGW--> SGW --> GDP --> callee Although the GDP (before the calle after the SGW) received the uri well from SGW inside the ACK as it appears below: ACK sip:yyyyyyyyyyyy@192.168.226.130:5060;rinstance=1608f7c153f40093;transport=UDP SIP/2.0 Record-Route: <sip:192.168.226.132;lr=on;ftag=as3b989c5f> Via: SIP/2.0/UDP 192.168.226.132;branch=z9hG4bK136f.1e8349c235fff01ee1849f3456f8868a.0 Via: SIP/2.0/UDP 192.168.226.133:5060;rport=5060;branch=z9hG4bK34871fe9 Route: <sip:192.168.226.130;lr;ftag=as3b989c5f;did=d5b.87890dc6> Max-Forwards: 69 From: "xxxxxxxxxxxxxx" <sip:xxxxxxxxxxxx@domain.com>;tag=as3b989c5f To: <sip:yyyyyyyyyyyyy@192.168.226.132:5060>;tag=1af2c424 Contact: <sip:xxxxxxxxx@192.168.226.133:5060> Call-ID: 7ed2ab533d4c43086746d0e620bdff06(a)domain.com CSeq: 102 ACK User-Agent: MGW Content-Length: 0 The global dipstacher (GDP) has used the Route header (which has no R-URI yyyyyyyyy) instead of the uri: ACK sip:192.168.226.130;lr;ftag=as3b989c5f;did=d5b.87890dc6 SIP/2.0 Record-Route: <sip:192.168.226.132;lr=on;ftag=as3b989c5f> Via: SIP/2.0/UDP 192.168.226.130;branch=0 Via: SIP/2.0/UDP 192.168.226.132;rport=5060;branch=z9hG4bK136f.1e8349c235fff01ee1849f3456f8868a.0 Via: SIP/2.0/UDP 192.168.226.133:5060;rport=5060;branch=z9hG4bK34871fe9 Max-Forwards: 68 From: "xxxxxxxxxx" <sip:xxxxxxxxxxx@domain.com>;tag=as3b989c5f To: <sip:yyyyyyyyy@192.168.226.132:5060>;tag=1af2c424 Contact: <sip:xxxxxxx@192.168.226.132:5060> Call-ID: 7ed2ab533d4c43086746d0e620bdff06(a)domain.com CSeq: 102 ACK User-Agent: MGW Content-Length: 0 Thanks in advance for your contribution Abdulaziz

2 1

DIALPLAN Module: doubts about regular expression usage
by Stefano Bertuola 15 Oct '18

15 Oct '18

Hi Experts. I did some tests with DIALPLAN module and I have some doubts about how to define the regular expressions in the database. For example, using the start character '^' (beginning of the string), it looks not working: kamcmd> dialplan.dump 1 { DPID: 1 ENTRIES: { ENTRY: { PRIO: 1 MATCHOP: 2 MATCHEXP: ^(\+39)(.*)$ MATCHLEN: 0 SUBSTEXP: ^(\+39)(.*)$ REPLEXP: \2 ATTRS: 1 } } } kamcmd> dialplan.translate 1 "+39123456" error: 500 - No translation Removing it, it works... but not as desired: kamcmd> dialplan.dump 1 { DPID: 1 ENTRIES: { ENTRY: { PRIO: 1 MATCHOP: 1 MATCHEXP: (\+39)(.*)$ MATCHLEN: 0 SUBSTEXP: (\+39)(.*)$ REPLEXP: \2 ATTRS: 1 } } } kamcmd> dialplan.translate 1 "+39123456" { Output: 123456" Attributes: 1 } kamcmd> dialplan.translate 1 "xxxxxxx+39123456" { Output: 123456" Attributes: 1 } Can someone help me understand how the regular expression should be used in DIALPLAN, please? Br. Stefano

4 8

DIALPLAN Module: how to get/use the Attributes value
by Stefano Bertuola 14 Oct '18

14 Oct '18

Hi experts. I intended ATTRIBUTES is a value that is returned by dialplan's dp_translate as the result as shown by kamcmd command: kamcmd> dialplan.translate 2 s:+3912345 { Output: 3912345 Attributes: test } Is my understanding correct? I tried many ways, including using AVP and XAVP for the result, but no success: dp_translate("2", "$rU/$xavp(dp_result)"); pv_xavp_print(); DEBUG: dialplan [dialplan.c:222]: dp_get_ivalue(): dpid is 2 from constant argument DEBUG: dialplan [dialplan.c:243]: dp_get_svalue(): searching 7 DEBUG: dialplan [dialplan.c:331]: dp_translate_f(): input is +3912345 DEBUG: dialplan [dp_repl.c:592]: translate(): regex operator testing over [+3912345] DEBUG: dialplan [dp_repl.c:662]: translate(): found a matching rule 0x7f56aef690d8: pr 1, match_exp ^\+39..... DEBUG: dialplan [dp_repl.c:481]: rule_translate(): copying match <3912345> token size 2 DEBUG: dialplan [dialplan.c:340]: dp_translate_f(): input +3912345 with dpid 2 => output 3912345 INFO: <core> [xavp.c:494]: xavp_print_list_content(): +++++ start XAVP list: 0x7f56aeffaaa8 (level=0) INFO: <core> [xavp.c:498]: xavp_print_list_content(): *** XAVP name: dp_result INFO: <core> [xavp.c:499]: xavp_print_list_content(): XAVP id: 3539756229 INFO: <core> [xavp.c:500]: xavp_print_list_content(): XAVP value type: 2 INFO: <core> [xavp.c:509]: xavp_print_list_content(): XAVP value: 3912345 INFO: <core> [xavp.c:531]: xavp_print_list_content(): ----- end XAVP list: 0x7f56aeffaaa8 (level=0) If possible, how can I get both OUTPUT and ATTRIBUTES as result? Stefano

2 1

db_mysql when compiling Kamailio
by Wilkins, Steve 12 Oct '18

12 Oct '18

Hello All, When db_mysql is selected in the make, the make looks for -lmariadb. However, I want MySQL, not mariadb. Is there a way to let the make know that MySQL is preferred ov mariadb? Thank you

2 1

registrar timer and database modes
by eyas barhouk 11 Oct '18

11 Oct '18

hello dears , i'm using kamailio 5.0.1 as IMS platform and have the following issues : * for Module "ims_usrloc_scscf" there is no documentation and i can't find a way to set database mode =2 and define the tables . * for Module "ims_registrar_scscf"when the user Unregistered it takes about 1~2 minutes to remove it from the memory on database mode 0 . so is there a way to minimize the timer when the user Unregistered and remove it immediately from the memory . thanks in advance & best regards.

2 1

Kamailio with Asterisk as Media Relay
by Benjamin Marty 11 Oct '18

11 Oct '18

Hello Ok, that sounds perfect. Is there a sample kamailio configuration file of how to achieve such a thing?

3 2

Addition of a code of conduct to the Kamailio repository
by Henning Westerholt 11 Oct '18

11 Oct '18

Hello, with commit a213d9d1 I introduced a Code of Conduct to the Kamailio repository [1]. This topic was initially discussed during the Kamailio development workshop, started from Daniel. During the development workshop we came to the conclusion that this is a policy decision and needs broader discussion in the Kamailio Management board and also the Kamailio Admin-Team. This discussion started last Friday, and after several days of discussion we decided to choose an existing Code of Conduct. We adapted the CoC of the Debian Project [2] and did a few changes for readability and also to adapt it to the (smaller) scope of our project. This CoC is in my opinion a good, generic and pragmatic document. Many people in our community are already in one way or the other involved in the Debian project. I am aware that this is (especially right now) a hot topic for some people. My personal opinion is that we managed to get a great fit to the existing Kamailio community culture. The history of this project shows that we are an open project and welcome contributions from anybody. So I don't expect any impact because of this change. We also ensured that the CoC only applies inside the Kamailio project, and that the Kamailio Management board is the authoritative instance in any conflicts about this topic. I don't want to start a classical "bike-shedding" discussion on this list about this topic.. But if you have any questions about this, lets us know. You can also contact the Kamailio Management Board, if you want to keep it private. Best regards, Henning Westerholt [1] https://github.com/kamailio/kamailio/blob/master/CODE_OF_CONDUCT.md [2] https://www.debian.org/code_of_conduct

1 0

Websocket configuration for kamailio 5.1.6
by Priyaranjan Nayak 09 Oct '18

09 Oct '18

Hi All, I have compiled the kamailio v5.1.6 source code with tls and websocket module enabled in ubuntu 18.04 LTS. Now I am able to start the kamailio in UDP and TCP port 5060. I wanted to run the kamailio in WS, WSS and TLS port as well. I have generated the private_key, certificate and ca_list and provided the absolute file path in tls.cfg file. I observed tls.so and websocket.so is present in the module path after compile and installation of code. I have used below command to compile and install. 1. make proper 2. make PREFIX="/usr/local/kamailio-5.1" include_modules="db_mysql tls websocket" cfg 3. make all 4. make install I have attached the kamailio.cfg and tls.cfg. Could you please suggest the modification in configuration file to run in WS, WSS and TLS port ? Thanks Priyaranjan

2 1

Kamailio 5.1.6 Debian Package -> SEGFAULT
by Floimair Florian 09 Oct '18

09 Oct '18

Hi! I just upgrade from 5.1.5 to 5.1.6 on my machine and I see Kamailio segfaulting (SIGSEGV). Unfortunately the systemd service is also not restarted in this case. I will generate coredumps and look into the backtrace and provide you with any insights I can gather.

1 0

← Newer
1
...
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