sr-users June 2018

sr-users@lists.kamailio.org

88 participants
121 discussions

problems to parse Cseq 0 value
by David Escartin 05 Jun '18

05 Jun '18

hello all we have seen that when an OPTIONS is sent with CSep: 0 OPTIONS, message is not parsed. Jun 4 10:12:09 proxy-1-aws /usr/local/kamailio/sbin/kamailio[2205]: ERROR: <core> [core/parser/parse_cseq.c:61]: parse_cseq(): no method found Jun 4 10:12:09 proxy-1-aws /usr/local/kamailio/sbin/kamailio[2205]: ERROR: <core> [core/parser/parse_cseq.c:92]: parse_cseq(): bad cseq Jun 4 10:12:09 proxy-1-aws /usr/local/kamailio/sbin/kamailio[2205]: ERROR: <core> [core/parser/msg_parser.c:144]: get_hdr_field(): bad cseq Jun 4 10:12:09 proxy-1-aws /usr/local/kamailio/sbin/kamailio[2205]: ERROR: <core> [core/parser/msg_parser.c:331]: parse_headers(): bad header field [CSeq: 0 Jun 4 10:12:09 proxy-1-aws /usr/local/kamailio/sbin/kamailio[2205]: WARNING: <core> [core/receive.c:198]: receive_msg(): parsing relevant headers failed as far i see in rfc3261 "The sequence number value MUST be expressible as a 32-bit unsigned integer and MUST be less than 2**31." i don't know if you already discussed about this, but do you think it would be something to fix? best regards and thanks a lot david escartin

2 4

Kamailio v5.1.4 Released
by Daniel-Constantin Mierla 05 Jun '18

05 Jun '18

Hello, Kamailio SIP Server v5.1.4 stable release is out. This is a maintenance release of the latest stable branch, 5.1, that includes fixes since the release of v5.1.3. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.1.x. Deployments running previous v5.1.x versions are strongly recommended to be upgraded to v5.1.4. For more details about version 5.1.4 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2018/06/kamailio-v5-1-4-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.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com

1 0

WARNING: topos [tps_storage.c:400]: tps_storage_record(): no local address
by Minh Phan 05 Jun '18

05 Jun '18

Hi List, I have this warning message in kamailio log when Kamailio handle an OPTIONS message with topos module enabled (I am using Kamailio 5.1.2): WARNING: topos [tps_storage.c:400]: tps_storage_record(): no local address - do record routing for all initial requests In my config file, OPTIONS message is handled this way: if ( is_method("OPTIONS") ) { t_newtran(); record_route(); t_reply("200","OK"); exit; } I have found this issue on Github but it is closed and I am not sure what was the solution: #1483 <https://github.com/kamailio/kamailio/issues/1483> My server receives 4 OPTIONS messages every 10 seconds that give as many warning in my log file. What could I do to get rid of them? Thanks, Minh

3 5

Releasing Kamailio v5.1.4
by Daniel-Constantin Mierla 05 Jun '18

05 Jun '18

Hello, I am considering to release a new minor version out of branch 5.1, respectively the v5.1.4, sometime next week, likely on Tuesday, June 5, 2018. As usual, if there is any issue not yet reported on github tracker, do it as soon as possible to give it a chance to be fixed. Soon I am going to do the backports of commits with fixes in master that apply in branch 5.1, so keep a close eye and if someone is missing, let me know to push it in the stable branch. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com

3 3

Transaction flags and branch_routes
by Alex Balashov 05 Jun '18

05 Jun '18

Hi, Given: flags PROXY_MEDIA_SET : 10, SIPPING : 11, DUMMY2 : 12 And: request_route { ... route(XYZ); } route[XYZ] { setflag(PROXY_MEDIA_SET); t_on_branch("BRANCH_ROUTE"); if(!t_relay()) sl_reply_error(); } branch_route[BRANCH_ROUTE] { if(isflagset(PROXY_MEDIA_SET)) { ... } ... } Is PROXY_MEDIA_SET meant to be visible inside the branch_route? Because it doesn't seem to be. Thanks! -- 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

ACK to 200 OK without to tag
by Kjeld Flarup 04 Jun '18

04 Jun '18

We have a SIP doorstation Grandstream GDS3710. When I connect it via kamailio, it does not setup call correct. Kamailio sends a 200 OK with this to field: t: <sip:0001@192.168.1.150:5069>;tag=e33a13d3-c18c-4df1-b68f-446e42957de6 Grandstream answers with: To: <sip:0001@192.168.1.150:5069> As the code follows this example: https://kamailio.org/docs/modules/4.3.x/modules/dispatcher.html#dispatcher.…, it seems obvious that this will fail, as there is not route[WITHINDLG] { if (has_totag()) { There simply is not to tag. Is this a bug in the grandstream? If so how could that go unnoticed, or is it me who misses something? I have attached the full sip text for the 200OK and the ACK -- -------------------- Med Liberalistiske Hilsner ---------------------- Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog Sofienlundvej 6B, 7560 Hjerm, Tlf: 40 29 41 49 Den ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk

2 3

Jumping on new TCP connection during a SIP session?
by Abdoul Osséni 04 Jun '18

04 Jun '18

Hello group, The call flow is: useragent (TLS) -> Kamailio -> Sems Server. During the establishment of a call (before the 200OK or during a retransmission of the 200OK issued by Sems Server via Kamailio), if a user agent (TCP) loses its connection (the user agent is on a mobile network for example or the network is not reliable.) and sends a "register" to Kamailio (same source IP address but a different source TCP port), is it possible for Kamailio to take into account this new TCP port with the function t_relay () ? Abdoul

4 4

Module sanity - memory leaks
by Konstantin Polyakov 04 Jun '18

04 Jun '18

Hello, We had memory leak on a production server and to find it we removed optional modules one by one. As result we found that problem is in the sanity module. Unfortunately I don't have time to fix it since I am going to vacation. We used the following checks: ruri_sip_version (1), required_headers (4), cseq_method (32), cseq_value (64), cotent_length (128), expires_value (256), proxy_require (512), parse uri's (1024). So be aware that this module is not ready to use in production. Best regards, Konstantin

1 0

configuring websockts in kamilio
by vinod mn 04 Jun '18

04 Jun '18

hi configured websockets on kamilio 5.1.3 I am trying to register the client based on webrtc client ,(sip.js) the registration is fine but i am not getting the correct address if i run "*kamctl ul show"* * In the address filed I want the sip:<id>@<ip>:<port>ex: sip:12345@127.0.0.1:12345 <http://sip:12345@127.0.0.1:12345> * output shows: { "jsonrpc": "2.0", "result": { "Domains": [{ "Domain": { "Domain": "location", "Size": 1024, "AoRs": [{ "Info": { "AoR": "1xxxxxxxxx", "HashID": 1xxxxx, "Contacts": [{ "Contact": { *"Address": "sip:eg84vjhr@p6ggglrk0gsh.invalid;transport=ws"*, "Expires": 397, "Q": 1, "Call-ID": "ma4feu2i43bnu6ophe4k78", "CSeq": 86, "User-Agent": "SIP.js/0.5.0-devel BB", "Received": "sip:X.X.X.X:56087;transport=ws", "Path": "[not set]", "State": "CS_NEW", "Flags": 0, "CFlags": 192, "Socket": "tcp:X.X.X.X:8080", "Methods": 783, "Ruid": "uloc-5b116457-1dc1-03", "Instance": "<urn:uuid:0e879ebf-0a31-45a8-9fd9-6b937d3328d4>", "Reg-Id": 1, "Server-Id": 0, "Tcpconn-Id": 259, "Keepalive": 1, "Last-Keepalive": 1527876355, "Last-Modified": 1527876355 } }] } } ], "Stats": { "Records": 1, "Max-Slots": 1 } } }] }, "id": 18958 } In the address filed I want the sip:<id>@<ip>:<port> ex: sip:12345@127.0.0.1:12345 Please give me any suggestions on this, which webrtc client can i use to register to kamailio and able to receive on the client and to make outbound calls from the client. -- Thanks and regards Vinod.M.N

2 1

Kamailio Behind TCP Load Balancer
by Colin Morelli 04 Jun '18

04 Jun '18

Hey all, I'm looking to put Kamailio behind a TCP load balancer that is SIP-unaware. My application is deployed in AWS and I'm tying to place Kamailio behind an ELB. For the most part, everything is fine. For my specific implementation I'm disabling UDP as a signaling transport and using only TLS. This enables me to not have to worry about a SIP-aware LB at the edge because replies to an incoming request will be sent over the existing established TCP socket (avoiding any crazy routing requirements). However - this poses an issue with source addresses. Does Kamailio support anything like the proxy protocol ( http://www.haproxy.org/download/1.5/doc/proxy-protocol.txt) for getting TCP stream information from a load balancer? Do I need to go back to exposing it directly to the world so that I can get source addresses? Thanks, Colin

3 4

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