April 2017 - sr-users - kamailio.org

Kamailio 5.0 doesn't forward Authorization (Digest username) to Asterisk
by Marko Tirs 11 Apr '17

11 Apr '17

Hello all, I am trying to use Kamailio 5.0 with Asterisk (separate IP addresses, both port 5060), but Asterisk doesn't register the SIP clients which comes through Kamailio.If I register the same user directly to the Asterisk then it works! 1st REGISTER is also without Authorization (Digest name) but in the 2nd REGISTER it exists and registration goes OK. How to use Kamailio with Asterisk in the way the SIP client is registered on both of them?Thank youMarko SIP-CLIENT DIRECTLY TO ASTERISK:----------------------------------------------------------- 1 2017-04-01 15:20:48.331806 192.168.0.12 192.168.0.2 SIP 544 Request: REGISTER sip:192.168.0.2 (1 binding) | 2 2017-04-01 15:20:48.332998 192.168.0.2 192.168.0.12 SIP 626 Status: 401 Unauthorized | 3 2017-04-01 15:20:48.333814 192.168.0.12 192.168.0.2 SIP 700 Request: REGISTER sip:192.168.0.2 (1 binding) | 4 2017-04-01 15:20:48.335975 192.168.0.2 192.168.0.12 SIP 647 Status: 200 OK (1 binding) | Frame 3: 700 bytes on wire (5600 bits), 700 bytes captured (5600 bits) on interface 0 Ethernet II, Src: AsrockIn_0a:0b:46 (70:85:c2:0a:0b:46), Dst: Raspberr_a1:fd:f7 (b8:27:eb:a1:fd:f7) Internet Protocol Version 4, Src: 192.168.0.12, Dst: 192.168.0.2 User Datagram Protocol, Src Port: 64369, Dst Port: 5060 Session Initiation Protocol (REGISTER) Request-Line: REGISTER sip:192.168.0.2 SIP/2.0 Message Header Via: SIP/2.0/UDP 192.168.0.12:64369;rport;branch=z9hG4bKPj9f8759c0537b4834bb411358d0b0a2ff Max-Forwards: 70 From: "33" <sip:33@192.168.0.2>;tag=4c586be1fcf842359e7d429abcb0b213 To: "33" <sip:33@192.168.0.2> Contact: <sip:74081936@192.168.0.12:64369>;+sip.instance="<urn:uuid:b408367e-d06b-4780-a9a0-291eb99ec83c>" Call-ID: d3c240808c934b77a9bbcb8bd4c1bd8c CSeq: 2 REGISTER Expires: 600 Supported: gruu User-Agent: Blink 3.0.0 (Windows) Authorization: Digest username="33", realm="asterisk", nonce="76ca37d8", uri="sip:192.168.0.2", response="19fc1a634abc72c41dcb516470c34fc2", algorithm=MD5 Authentication Scheme: Digest Username: "33" Realm: "asterisk" Nonce Value: "76ca37d8" Authentication URI: "sip:192.168.0.2" Digest Authentication Response: "19fc1a634abc72c41dcb516470c34fc2" Algorithm: MD5 Content-Length: 0 SIP-CLIENT TO KAMAILIO WITH FORWARD TO ASTERISK:---------------------------------------------------------------------------------------------- 11 2017-04-01 15:21:06.806347 192.168.0.13 192.168.0.2 SIP 459 Request: REGISTER sip:192.168.0.2:5060 (1 binding) | 12 2017-04-01 15:21:06.807514 192.168.0.2 192.168.0.13 SIP 608 Status: 401 Unauthorized | 13 2017-04-01 15:21:06.814819 192.168.0.13 192.168.0.2 SIP 456 Request: REGISTER sip:192.168.0.2:5060 (remove 1 binding) | 14 2017-04-01 15:21:06.815712 192.168.0.2 192.168.0.13 SIP 608 Status: 401 Unauthorized | 15 2017-04-01 15:21:06.821125 192.168.0.13 192.168.0.2 SIP 459 Request: REGISTER sip:192.168.0.2:5060 (1 binding) | 16 2017-04-01 15:21:06.821910 192.168.0.2 192.168.0.13 SIP 608 Status: 401 Unauthorized | Frame 15: 459 bytes on wire (3672 bits), 459 bytes captured (3672 bits) on interface 0 Ethernet II, Src: Micro-St_de:b2:3a (00:24:21:de:b2:3a), Dst: Raspberr_a1:fd:f7 (b8:27:eb:a1:fd:f7) Internet Protocol Version 4, Src: 192.168.0.13, Dst: 192.168.0.2 User Datagram Protocol, Src Port: 5060, Dst Port: 5060 Session Initiation Protocol (REGISTER) Request-Line: REGISTER sip:192.168.0.2:5060 SIP/2.0 Message Header Via: SIP/2.0/UDP 192.168.0.13;branch=z9hG4bKd101.0ad599b6000000000000000000000000.0 To: <sip:32@192.168.0.2> SIP to address: sip:32@192.168.0.2 From: <sip:32@192.168.0.2>;tag=533cb9e91f4b999cf76861cbb9ed54ed-85c4 SIP from address: sip:32@192.168.0.2 SIP from tag: 533cb9e91f4b999cf76861cbb9ed54ed-85c4 CSeq: 10 REGISTER Call-ID: 41df282f10fdc7b6-2773(a)127.0.0.1 Max-Forwards: 70 Content-Length: 0 User-Agent: kamailio (5.0.0 (x86_64/linux)) Contact: <sip:32@192.168.0.13:5060> Contact URI: sip:32@192.168.0.13:5060 Expires: 3600 kamailio.cfg:-------------------- #!define WITH_DEBUG #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB #!define WITH_ASTERISK ... #!ifdef WITH_ASTERISK asterisk.bindip = "192.168.0.2" desc "Asterisk IP Address" asterisk.bindport = "5060" desc "Asterisk Port" kamailio.bindip = "192.168.0.13" desc "Kamailio IP Address" kamailio.bindport = "5060" desc "Kamailio Port" #!endif ... # Forward REGISTER to Asterisk route[REGFWD] { if(!is_method("REGISTER")) { return; } $var(rip) = $sel(cfg_get.asterisk.bindip); $uac_req(method)="REGISTER"; $uac_req(ruri)="sip:" + $var(rip) + ":" + $sel(cfg_get.asterisk.bindport); #$uac_req(ruri)="sip:" + $au + "@" + $var(rip) + ":" + $sel(cfg_get.asterisk.bindport); $uac_req(furi)="sip:" + $au + "@" + $var(rip); $uac_req(turi)="sip:" + $au + "@" + $var(rip); $uac_req(hdrs)="Contact: <sip:" + $au + "@" + $sel(cfg_get.kamailio.bindip) + ":" + $sel(cfg_get.kamailio.bindport) + ">\r\n"; if($sel(contact.expires) != $null) $uac_req(hdrs)= $uac_req(hdrs) + "Expires: " + $sel(contact.expires) + "\r\n"; else $uac_req(hdrs)= $uac_req(hdrs) + "Expires: " + $hdr(Expires) + "\r\n"; uac_req_send(); }

2 2

Info: mailing lists use lists.kamailio.org
by Daniel-Constantin Mierla 11 Apr '17

11 Apr '17

Hello, all the mailing lists related to the Kamailio project are using now lists.kamailio.org as primary domain, including sr-dev and sr-users. >From now on, the emails should be addressed to: - sr-dev(a)lists.kamailio.org - sr-users(a)lists.kamailio.org The previous domain (lists.sip-router.org) should still work, so existing discussions can go on as usual. If anyone is encountering any problems or notices some information on kamailio.org that needs to be updated, do not hesitate to reply here or contact me. In addition, URLs should use now https, browsing the archive with plain http is redirected to https urls. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - May 22-24 (USA) - www.asipto.com Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com

2 3

Disable DNS
by Diego Nadares 11 Apr '17

11 Apr '17

Hi Guys, Is it possible to disable using of dns in kamailio? The thing is that not all INVITES that arrives to the proxy comes with ip 172.16.205.25/PUB_IP in the ruri. Some gateways sends a string in ruri -> @myproxysip and others sends @other.domain.com Request-Line: INVITE sip:1111111@myproxysip:5060;user=phone SIP/2.0 Request-Line: INVITE sip:1111111@other.domain.com:5060;user=phone SIP/2.0 Sometimes, myproxysip is from a public ip and sometimes is from a private ip. So, it's difficult to know to which of kamailio's interfaces (pub or priv) is. ERROR: <core> [resolve.c:1694]: sip_hostport2su(): could not resolve hostn ame. Reconfigure those gw it's not possible. There are a lot of them and a lot of people that won't like that idea. Is possible to disable it? or What do you recommend me to do? Maybe using /etc/hosts? Any suggestion will be very appreciated. Diego.

3 10

Use of variables for force_send_socket
by Jöran Vinzens 11 Apr '17

11 Apr '17

Hi all, i try to re-arrange my config and i try to use a variable declared in modparam pv such like: modparam("pv", "varset", "externalip=s:1.2.3.4") and use it as: force_send_socket($var(externalip)); unfortunately the kamailio does not start with this configuration and telling me bad config file like: line 109, column 36: bad argument, [proto:]host[:port] expected it seems the force_send_socket is not able to get variable. Is there any other way to have static content defined and put across the config? Reason for the question is the possibility to use ansible as deployment tool. I set all the variables i need in a separate file and include it. This file contains the entire modconfig and global vars section to adapt this part to every single machine individually. This does not work if i need to put "constant" variables on different places in my config. If anybody has ever made this, could you please help me, or give any suggestions? Many thanks! BR Jöran -- Jöran Vinzens - vinzens(a)sipgate.de sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391 www.sipgate.de - www.sipgate.co.uk

4 4

Notice: work on mailing lists server
by Daniel-Constantin Mierla 11 Apr '17

11 Apr '17

Hello, be aware that today I plan to do some maintenance on the mailing lists server, including the shifting to the lists.kamailio.org as primary domain. I expect not to have any relevant downtime, but one never knows. Maybe the archive won't be available for short time due to changes needs to be done to the web server after mailing lists server is upgraded. I will sent another notification when everything is finished. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - May 22-24 (USA) - www.asipto.com Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com

1 0

Authentication on Kamailio with MySQL
by Nicolas Pace 10 Apr '17

10 Apr '17

Hi everyone, I'm having some trouble setting up a simple Kamailio installation with user authentication. I've installed a kamailio (4.3.4) base install on an ubuntu server 16.04 (x86/64) on virtualbox, and added this lines at the beginning of the file: ``` #!KAMAILIO #! define WITH_MYSQL #! define WITH_AUTH #! define WITH_USRLOCDB ``` Also configured the db name, host, user and pass for RO and RW and run `kamdbctl create`. Everything I do was following this tutorial: http://www.kamailio.org/wiki/tutorials/getting-started/main Based on what the tutorial says, I should have a server that only allows users that have been authenticated against the DB. The thing is that now Kamailio allows me to access, no matter what credentials I gave him (replies 200 OK to my REGISTER requests, and whows the user on the `kamctl monitor` view). I've added to this gist: * My current kamailio config * the kamailio grepped syslog * the pjsua output from when I register with an unexistent user https://gist.github.com/nicopace/9d44bf813fe309df69ff4cd0affe8324 I've already checked out some of the wiki documentation, namely: * http://www.kamailio.org/wiki/tutorials/auth/auth_db * http://www.kamailio.org/wiki/tutorials/getting-started/main Am I missing something? Thanks

3 3

Introduction
by Nicolas Pace 10 Apr '17

10 Apr '17

Hi Everyone! I just wanted to introduce myself, before blasting the list with questions (just kidding!). My name is Nicolás Pace, I'm a Community Networks advocate from Argentina. I'm working on a community project for Rhizomatica [0], which is an amazing organization that promotes Community Cellular Networks for underserved communities in Latin America (mainly mexican's first nations but also in Nicaragua, Colombia nad Brazil). We are working on a mobile app to connect the Community Cellular Networks (that uses 2G Cellular Networks) with the rest of the world via SIP, and we are considering using Kamailio for this. The project has been using FreeSwitch for some time and now we are thinking about using Kamailio on the cloud side, and intengrate them via SIP. On a not so distant future, if the Kamailio experience goes well, we are thinking on moving everything to Kamailio, as it seems to be much more simple and effective. For now we expect to do a prototype to connect this communities with their relatives via SMS (on the Cellular side) with SIP SIMPLE Messages (on the 'cloud' side). Awesome to meet you all, and hope to be collaborating with this community! Regards, [0] https://www.rhizomatica.org/

3 3

INFO: Shifting mailing lists to kamailio.org domain
by Daniel-Constantin Mierla 10 Apr '17

10 Apr '17

Hello, I think it is time to migrate the mailing lists under kamailio.org domain, respectively use lists.kamailio.org. The lists.sip-router.org will still work, but lists.kamailio.org is intended to become the primary domain for mailing lists. The sip-router.org was the quick solution for integrating Kamailio and SER in one project back in 2008, when kamailio.org and iptel.org still needed to be operated for a while as independent projects. For few years now, Kamailio is the only project name that is used out there and it will make operating everything a bit smoother, more coherent and also avoid eventual confusions for people new into the project. As a matter of fact, we even had a small incident few weeks ago -- due to split management of sip-router.org and DNS registration expire notifications going to an email address on a different server than kamailio.org, the domain was expired for few hours (although it was kept on hold by registrar) and mailing lists started to be unavailable. Fortunately that was discovered and fixed in time. The names will stay the same sr-users and sr-dev, just primary domain will be using kamailio.org (which should 'hopefully' work even now, as this email was addressed with mixed sr-dev(a)lists.sip-router.org and sr-users(a)lists.kamailio.org) If anyone has different opinions or suggestions, let's discuss them! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - May 22-24 (USA) - www.asipto.com Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com

1 1

Transaction Lookup Failing
by Colin Morelli 10 Apr '17

10 Apr '17

Hey all, Trying to debug an issue with canceling an invite. I have two different types of clients. On one client, canceling an invite works correctly. With the other client, it t_check_trans fails. Both clients show the same request/responses: On Client A: -> INVITE <- 183 -> PRACK <- 200 -> UPDATE (from successful STUN binding) <- 200 -> CANCEL <- 200 On Client B: -> INVITE <- 183 -> PRACK <- 200 -> UPDATE (from successful STUN binding) <- 200 -> CANCEL <- 481 (this is sent from my kamailio script when t_check_trans fails) I can't see much that's different between the leading requests/responses of each. They seem to be virtually identical (with the exception of IP addresses and tag values, of course). This makes sense, since they're both based on PJSIP (albeit different versions of PJSIP, but not off by much) Is there anything in particular I should be looking out for that might be obvious? I could provide more detailed logs and traces if required. Best, Colin

2 3

"kamdbctl create" failed
by Tim Makarios 10 Apr '17

10 Apr '17

Hi, Following http://kamailio.org/docs/tutorials/devel/kamailio-install-guide-deb/ I got to the step where I had to run kamdbctl create Unfortunately, this failed, with the following output: > INFO: test server charset > INFO: creating database kamailio ... > INFO: granting privileges to database kamailio ... > INFO: creating standard tables into kamailio ... > ERROR 1101 (42000) at line 2: BLOB/TEXT column 'body' can't have a default value > ERROR: Creating core tables failed at msilo! Searching for this error turned up http://tinyurl.com/lovr4aq , but the link in the answer is broken, and it doesn't appear that STRICT_TRANS_TABLES is relevant to my version of MySQL [1], which is 5.5.54 (running on Trisquel 7, which is based on Ubuntu Trusty). Has anyone else encountered and overcome this problem, or does anyone have any ideas about how I might proceed? Tim <>< [1] http://tinyurl.com/zmnc75c

2 8