sr-users May 2014

sr-users@lists.kamailio.org

96 participants
156 discussions

sip trunk help
by Joli Martinez 09 May '14

09 May '14

Hello, I am new to Kamailio. I need to get a SIP trunk registered to Kamailio. Can someone explain how to set this up. Thanks

3 3

issue with usr_loc db_mode
by Henry Fernandes 08 May '14

08 May '14

I'm using Kamailio 3.3 and the USRLOC module to track registrations. I have set "db_mode" to 1 because I want to store all registration info to the database and I want the database to be up to date (in case I need to restart Kamailio). Unfortunately, this doesn't work as I expect. When I query the database, it has far fewer entries in the "location" table than are registered to Kamailio (which I find with a "kamctl ul show"). Also, when I restart Kamailio, I lose some of the registrations for my phones. Am I misunderstanding the behaviour for db_mode=1? Isn't it supposed to keep the database up to date? -H

3 3

n00b question -- RADIUS authentication.
by Måns Nilsson 08 May '14

08 May '14

[first post to list] Greetings, I'm in the process of getting a Kamailio 3.3.2 installation authenticating its SIP accounts against a RADIUS database. There are -- at the moment -- no plans to do any fancy accounting nor any authorisation beyond simple authentication. I've set up and tested a FreeRadius 2.2.3_1 server on a dedicated server. After a fairly steep learning curve involving RADIUS dictionaries I've come so far that kamailio sends out a RADIUS Access-Request message that is received by FreeRadius, processed, and returned to Kamailio which promptly ignores it and continues to send 401 to the client; the SIP message exchange with the client being: (some identifing info has been redacted) > REGISTER sip:my.domain SIP/2.0 < SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 10.25.191.24:41688;branch=z9hG4bK-d8754z-eac09e6c626d4c4d-1---d8754z-;rport=41688 > REGISTER sip:my.domain SIP/2.0 Via: SIP/2.0/UDP 10.25.191.24:41688;branch=z9hG4bK-d8754z-4f25c643f4b93465-1---d8754z-;rport < SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 10.25.191.24:41688;branch=z9hG4bK-d8754z-4f25c643f4b93465-1---d8754z-;rport=41688 The RADIUS exchange: 10:07:10.861063 IP (tos 0x0, ttl 64, id 14964, offset 0, flags [none], proto UDP (17), length 270) 10.24.194.198.63712 > 10.24.194.196.1812: [udp sum ok] RADIUS, length: 242 Access Request (1), id: 0x05, Authenticator: 4215e95809551826eda76972be4106c4 Username Attribute (1), length: 18, Value: mtu-06(a)my.domain 0x0000: 6d74 752d 3036 4069 706b 2e73 722e 7365 Unknown Attribute (207), length: 10, Value: 0x0000: 0a08 6d74 752d 3036 Unknown Attribute (207), length: 13, Value: 0x0000: 010b 6970 6b2e 7372 2e73 65 Unknown Attribute (207), length: 36, Value: 0x0000: 0222 5532 6448 326c 4e6e 5271 3677 4353 0x0010: 6463 6775 5056 3050 516e 3936 324d 5635 0x0020: 6d34 Unknown Attribute (207), length: 17, Value: 0x0000: 040f 7369 703a 6970 6b2e 7372 2e73 65 Unknown Attribute (207), length: 12, Value: 0x0000: 030a 5245 4749 5354 4552 Unknown Attribute (207), length: 8, Value: 0x0000: 0506 6175 7468 Unknown Attribute (207), length: 12, Value: 0x0000: 090a 3030 3030 3030 3031 Unknown Attribute (207), length: 36, Value: 0x0000: 0822 3933 3832 3333 3333 3530 3162 3238 0x0010: 6439 3236 3739 3863 3964 3038 6539 3134 0x0020: 3733 Unknown Attribute (206), length: 34, Value: 0x0000: 3538 3665 3336 3763 3230 3163 3137 6438 0x0010: 6261 3265 3830 3533 3763 6433 3562 3761 Service Type Attribute (6), length: 6, Value: #15 0x0000: 0000 000f Unknown Attribute (208), length: 8, Value: 0x0000: 6d74 752d 3036 NAS Port Attribute (5), length: 6, Value: 5060 0x0000: 0000 13c4 NAS IP Address Attribute (4), length: 6, Value: 10.24.194.198 0x0000: c079 c2c6 10:07:10.863964 IP (tos 0x0, ttl 64, id 28916, offset 0, flags [none], proto UDP (17), length 48) 10.24.194.196.1812 > 10.24.194.198.63712: [bad udp cksum 0x06ac -> 0x44c0!] RADIUS, length: 20 Access Accept (2), id: 0x05, Authenticator: 8f07de871a066aacfbe822e20a9b96c1 The RADIUS part of the Kamailio config is: if (is_method("REGISTER") || from_uri==myself) #if (is_method("REGISTER") ) { # authenticate requests xlog("L_INFO", "authenticate [$fd]\n"); ### RADIUS ### if (!radius_www_authorize("my.domain")) { $var(ret) = $rc; xlog("L_INFO", "response code: [$var(ret)]\n"); switch ($var(ret)) { case -7: send_reply("500", "Server Internal Error"); exit; case -1: send_reply("400", "Bad Request"); exit; default: }; if (defined($avp(digest_challenge)) && ($avp(digest_challenge) != "")) { append_to_reply("$avp(digest_challenge)"); }; send_reply("401", "Unauthorized"); exit; }; # user authenticated - remove auth header if(!is_method("REGISTER|PUBLISH")) consume_credentials(); } Any clues? What is missing from my narrative? -- Måns Nilsson primary/secondary/besserwisser/machina MN-1334-RIPE +46 705 989668 Actually, what I'd like is a little toy spaceship!!

2 3

kamctl online and ul show are empty!
by 5060 08 May '14

08 May '14

Hello: after i starting kamailio for while, the system shows: 3(1466) DEBUG: mi_fifo [mi_parser.c:84]: end of fifo input tree 3(1466) DEBUG: mi_fifo [fifo_fnc.c:507]: done parsing the mi tree 1(1464) DEBUG: usrloc [urecord.c:327]: Binding '102',' sip:102@192.168.1.105:5060' has expired 3(1466) DEBUG: mi_fifo [mi_parser.c:84]: end of fifo input tree 3(1466) DEBUG: mi_fifo [fifo_fnc.c:507]: done parsing the mi tree 3(1466) DEBUG: mi_fifo [mi_parser.c:84]: end of fifo input tree 3(1466) DEBUG: mi_fifo [fifo_fnc.c:507]: done parsing the mi tree ---------------------------------------------------------------------- kamctl online and ul show are empty. how can i adjust the time to resolve the problem? thanks!

2 3

Re: [SR-Users] UPDATE --- Can "presence" module handle publish reqs with several dialog entries? + Problem SOLUTION
by Klaus Feichtinger 08 May '14

08 May '14

Pls find attached the patch for version 4.1.3. The three lines of code are equal for all affected version (incl. 3.2.4, 3.3.5, 4.0.6 and 4.1.3). regards, Klaus > Daniel-Constantin Mierla <miconda(a)gmail.com> hat am 7. Mai 2014 um 15:45 > geschrieben: > > Hello, > > can you send the patch to be reviewed? > > Cheers, > Daniel > > On 07/05/14 13:15, Klaus Feichtinger wrote: > > > > Hi Daniel, > > > > I think we´ve found the reason, why this problem occurs! > > > > The problem is caused in the "agregate_xmls" function in file > > "notify_body.c" of the "presence_dialoginfo" module: > > > > /* loop over all bodies and create the aggregated body */ > > for(i=0; i<j; i++) > > { > > /* LM_DBG("[n]=%d, [i]=%d, [j]=%d xml_array[i]=%p\n", n, i, j, > > xml_array[j] ); */ > > p_root= xmlDocGetRootElement(xml_array[i]); > > if(p_root ==NULL) { > > LM_ERR("while geting the xml_tree root element\n"); > > goto error; > > } > > if (p_root->children) { > > for (node = p_root->children; node; node = node->next) { > > if (node->type == XML_ELEMENT_NODE) { > > LM_DBG("node type: Element, name: %s\n", > > node->name); > > /* we do not copy the node, but unlink it and then > > add it ot the new node > > * this destroys the original document but we do > > not need it anyway. > > * using "copy" instead of "unlink" would also copy > > the namespace which > > * would then be declared redundant (libxml > > unfortunately can not remove > > * namespaces) > > */ > > if (!force_single_dialog || (j==1)) { > > xmlUnlinkNode(node); > > if(xmlAddChild(root_node, node)== NULL) { > > LM_ERR("while adding child\n"); > > goto error; > > } > > > > It seems to be not the best idea to "unlink" the XML node (= > > "xmlUnlinkNode(node);"), as then no "node->next" is available any more. > > Therefore, this loop will _always_ stop after one dialog entry and ignore > > any additional one! > > > > But we "solved" the problem in this way that the loop will not directly > > use "node->next", but a variable, which is set within the loop. It looks > > like this: > > xmlNodePtr next_node = NULL; > > [...] > > if (p_root->children) { > > for (node = p_root->children; node; node = next_node) { > > next_node = node->next; > > if (node->type == XML_ELEMENT_NODE) { > > [...] > > > > This solution has been tested with 2 and 3 dialog entries in a single > > PUBLISH request and it is working fine. We should discuss if this is a > > problem that should be solved generally or if it is a "private" problem in > > our use case. > > > > What do you mean? > > > > regards, > > Klaus > > > > > > >

2 1

Problems this morning using Iptel.org
by swill 08 May '14

08 May '14

Hi, I use a configuration of ipkall and iptel.org, Most of the time this works out as a great incoming solution, however, today, it seems to be ending the call as i answer, I use only one softpphone at a time, but have tried it on Zoiper, 3cx, and Phonerlite, It does the same thing, call it, it rings, answer it and it immediately goes to "Call ended". I've done powercycle reboots on my HTC EVO 4G LTE, and on my PC it acts the same on all three. It registers fine on them all, I just cant determine if it is an IPKall or an Iptel problem..Is anyone else having an issue?? Are there any suggestions on what further troubleshooting I could do?? Thanks Michael

2 1

Kamailio auto restart if stopped
by JR Richardson 07 May '14

07 May '14

Hi All, Just had a strange occurrence where kamailio has been up and running fine for several months and just died with a strange error: root@sip-router3:~# kamailio -V version: kamailio 4.1.1 (x86_64/linux) ac7d55 May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2275]: : <core> [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already freed pointer (0x7faf565586d0), called from <core>: mem/shm_mem.c: sh_realloc(88), first free <core>: mem/shm_mem.c: sh_realloc(88) - aborting May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2271]: ALERT: <core> [main.c:775]: handle_sigs(): child process 2275 exited by a signal 6 May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2271]: ALERT: <core> [main.c:778]: handle_sigs(): core was not generated May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2271]: INFO: <core> [main.c:790]: handle_sigs(): INFO: terminating due to SIGCHLD May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2279]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2277]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2273]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2272]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2274]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2276]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2278]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2271]: ERROR: ctl [ctl.c:379]: mod_destroy(): ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: Operation not permitted (1) Not sure what that means, memory leak? I started started it right back up with no indication of a problem. Running Kamailio for many years, I have never had an instance of it just shut down before. So I'm wondering if there are any safe scripts that check the running process for kamailio and restart if automatically if not running? I dug around a bit but not seeing any hits for auto start kamailio scripts. And another question would be if this occurrence of shutting down should be of concern or not? Thanks. JR -- JR Richardson Engineering for the Masses

2 1

Can "presence" module handle publish reqs with several dialog entries?
by Klaus Feichtinger 07 May '14

07 May '14

Hi, during simulating scenarios in relation with the notify problem I have so far, I became unsure, if Kamilio (in principal) is supporting handling of PUBLISH requests (event "dialog") that contain _more than_ one (1) dialog entry. I know that it can generate notify requests with a message body that contains more than one dialog entry. But that´s not automatically the same as handling publish requests.... So - is Kamailio able or not? Did anybody ever use it in such a scenario? regards, Klaus

2 7

Problem initial configuration of Kamalio
by Mr.Gab 07 May '14

07 May '14

Hello everybody, i'm new to kamalio and i'm trying to install on a centos server hosted on a open-stack IaaS platform. I followed the official wiki adding the "advertise statement" and define WITH_NAT. I added 3 user as test 100 101 102 that i can see typing kamctl db show subscriber but if i try to register with Bria i get Failed. Theese are sip packets that i sniffed with tcpdump. http://pastebin.com/sa74HJqM can someone help a noob to understad how to debug this kind of problem with kamalio? i tried googling but i didn't find anything. Thank you all in advice

1 0

Routing incoming calls to Asterisk trunk
by Teleport Engineer 07 May '14

07 May '14

Hello, I'd setup a test environment where Kamailio accepts external invites and routes them to an internal Asterisk (actually working as an SBC). My dialplan works fine routing the INVITE to the internal Asterisk, but the SIP message goes into the defaul sip context (the one configured in sip general), and not in the context defined for the sip trunk between Kamailio and Asterisk. The sip trunk is configured like this: [kamailio] disallow=all host=kamailio port=5060 insecure=port,invite type=friend context=from-sip-external fromdomain=mydomain qualify=yes allow=alaw allow=g722 So I expect that all the sip invites coming from kamailio should be executed in from-sip-external context. But it doesn't work like this since each invite goes in the default context. The invite that goes to Asterisk is like this <--- SIP read from kamailio-external:5060 ---> INVITE sip:extension@asterisk:5060;transport=UDP SIP/2.0 Record-Route: <sip:kamailio-external:5060;nat=yes;ftag=905e4921;lr=on> Via: SIP/2.0/UDP kamailio-external:5060;branch=z9hG4bK277a.aea3ad87.0 Via: SIP/2.0/UDP caller:28021;rport=28019;received=caller;branch=z9hG4bK-d8754z-d11f1fa1d0fb2ab4-1---d8754z- Max-Forwards: 69 Contact: <sip:524@caller:28019;transport=UDP> To: <sip:extension@kamailio-external> From: <sip:524@caller:28007>;tag=905e4921 Call-ID: YzEzMDM1NDZhZTllMTRiMDJmY2MyZTE0ZWZjMzE5OTc. CSeq: 1 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri User-Agent: Z 3.2.21357 r21367 Allow-Events: presence, kpml Content-Type: application/sdp Content-Length: 260 What I think is that in the sip message there is no information about kamailio internal ip address but only about kamailio-external address and then Asterisk put it into the default context. If this is the reason, should I change the trunk ip address in Asterisk and should I do some manipulation on the incoming packet on kamailio? Or maybe I should use kamailio-external as fromdomain in the trunk configuration? Thanks.

2 1

Jump to page:

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 May 2014