sr-users

sr-users@lists.kamailio.org

42 participants
37519 discussions

TOS value in configuration
by Olle E. Johansson 04 Mar '12

04 Mar '12

I've set tos=IPTOS_RELIABILITY in my configuration, which follows https://www.kamailio.org/wiki/cookbooks/3.2.x/core#tos which has the following examples: tos=IPTOS_LOWDELAY tos=0x10 tos=IPTOS_RELIABILITY but I get a configuration error: 0(45338) : <core> [cfg.y:3501]: parse error in config file /usr/local/etc/kamailio/kam-global.inc, line 29, column 5-21: syntax error 0(45338) : <core> [cfg.y:3501]: parse error in config file /usr/local/etc/kamailio/kam-global.inc, line 29, column 5-21: number expected Has this option been deprecated or is it a small bug? /O

2 1

Facebook page for Kamailio
by Olle E. Johansson 04 Mar '12

04 Mar '12

Just to make sure we're in the flow, I've started a Facebook page for Kamailio. http://www.facebook.com/kamailio Feel free to like it if you're a Facebook user. There's also a Google+ page. If you have news to share, you're welcome to add it on these pages. /O

2 1

Building Up a Kamailio Server
by Faisal Rehman 03 Mar '12

03 Mar '12

Hi Everyone, I am totally new to Kamailio & going to build up Kamailio server as an XMPP server with the following wanted functionalities: -Have XMPP client to register to my kamailio server - The XMPP clients should all be able to see each others presence - The XMPP clients should be able to IM other XMPP clients - The registered sip client will be able to just dial any other sip client. No need for any gateway or trunk for now I have a good previous background with SIP but its my first time to work with XMPP & Kamailio & that's why I am in need of a bit help & assistance. I have installed Kamailio on my CentOS box & now going to start to configure it in order to complete the above requirements, so any links or any refferals will be highly appreciated. Regards, Faisal Rehman

2 5

XMPP module not passing subscribes coming from xmpp side
by Dan-Cristian Bogos 02 Mar '12

02 Mar '12

Hey Guys, I was wondering if anyone having experience with using xmpp module as presence gateway between SIP and XMPP. I started evaluating it and till now got some weird results, not sure if it is just my setup which does not match the one widely used or the module is incomplete. Regarding my setup, I use OpenFIRE 3.7.1 on one side and Kamailio 3.2.0 out of debian packages on the other. The issue I got right now is that the subscribe coming from XMPP side produces no action/reply on SIP side. Bellow you can see the packet coming from OpenFIRE: # T 2012/03/02 09:49:57.743750 127.0.0.1:5275 -> 127.0.0.1:49965 [AP] <presence id="4h8F6-19" to="dan4(a)gw.mydomain.com" type="subscribe" from="dan(a)mydomain.com"><c xmlns="http://jabber.org/protocol/caps" ext="voice-v1 video-v1 camera-v1 " hash="sha-1" node="http://jitsi.org" ver="ohjz8WKq0ZQRiNWRNcapX4BBHLk="/></presence> """ Anyone here got this working somehow? Ta, DanB

2 1

iOS push notification using Kamailio
by Krishna Kurapati 02 Mar '12

02 Mar '12

Hi, I have been looking at the usrloc module's source code to see how the uuid that is sent in +sip.instance parameter in the Contact header. Apparently, the module ensures that only one contact per uuid exists. However the uuid is not stored in the database. The reason I need the uuid in the database is to access it when the iOS device is offline inorder to send a push notification. I am using pjsip which supports sending the uuid of the device ( w/ rfc 5626 support) in the REGISTER message. Has anyone implemented push notification using this or other methods using Kamailio? Thanks Krish Kura

2 1

automatically switch to TCP
by Klaus Darilion 01 Mar '12

01 Mar '12

Hi! Is there a feature somewhere (core, tm) to automatically switch from UDP to TCP? It may be useful with bodies > 64K. regards Klaus

2 1

Kamailio error code 500 (6/SL)
by Pavel Klochan 01 Mar '12

01 Mar '12

Hi. I'm a newbie to Kamailio (so do not judge strictly). I have experience only with Asterisk and now I'm trying to configure Kamailio. With default config all is working as expected, but I'm trying to configure it from zero with minimal functions, but using parts from default config (those parts that I figured out). With my present config local calls are working great, but I can't make outbound calls. I've attached config file, sip-trace and debug log. I think there is a route loop somewhere but I can't figure out where. I would be grateful if you pointed out to me where exactly my mistake or just point me in the right direction =) Thanks in advance

2 2

loose_route() with pre-loaded Route in ACK
by Andreas Granig 01 Mar '12

01 Mar '12

Hi, I ran into an interesting scenario when experimenting with kamailio 3.1 as a stateless proxy (no tm module used): There is an initial INVITE without to-tag and with pre-loaded Route header pointing to the external address of the lb. When I call loose_route for that, it returns false and the Route header is removed. That's what I expected, and it's documented in http://www.kamailio.org/docs/modules/3.1.x/modules_k/rr.html#loose-route-id. However if a 407 is relayed back from the registrar via the lb to the UA, it sends an ACK, again with pre-loaded Route header like in the initial INVITE, this time with to-tag. In that case, loose_route() returns true, but the $du is $null and the R-URI is still the same. So the Route is consumed, but the URI is not used. Since it's a stateless proxy, this hop-by-hop ACK needs to be routed the same way as the initial INVITE, so what I'm doing is something like that: if(loose_route()) { if($du == $null && $ru == $ou) { # skip loose-routing for such a request } } Is this how it's supposed to work? And is there some documentation of how loose_route() detects whether Route points to itself or not? I'm not using auto_aliases, nor do I set any aliases manually. Does it determine internally whether the Route points to its local ip and port? If not, how come the $du is not set although loose_route returns true? Andreas

2 9

DRouting cause Kamailio 3.2 to stop
by Fatima Chahrour~Vanrise Support 01 Mar '12

01 Mar '12

Hi, I am newly experiencing kamailio 3.2. I have installed kamailio and MySQL and tried the test call from 1 PC(x-lite) to another PC(x-lite) and ended successfully. Now moving further, I have configured dynamic routing module and applied needed parameters and scripts to finally be able to start kamailio without any issue. Also I set a testing scenario in the related database tables BUT my problem is that whenever am trying to call the predefined prefix (961) from x-lite am getting a 'calling' message on it and then request timeout where I find that kamailio has stopped running. I kamctrl start again and call 961 then get calling so I wait and kamailio stps again. Below is the script used in the routing logic and database record. Any help to achieve a successful call is highly appreciated. dr_gatways: 3, 1, '192.168.111.15', 0, '', '', 2, 'PC1' dr_groups: 2, '.*', '.*', 0, 'Anyone' dr_gw_lists: 2, '3', 'Test Call' dr_rules: 2, '0', '961', '', 0, '1', '#2', 'Lebanon Fix' ####### Routing Logic ######## # main request routing logic route{ if (is_method("INVITE")) { setflag(1); # do accounting route(4); # Call our dynamic route. } } .. .. .. route[4] { if (!do_routing("0")) { send_reply("503", "No Rules matching the URI"); exit; } if (is_method("INVITE")) { t_on_failure("4"); } route(RELAY); } .. .. .. failure_route[4] { if (use_next_gw()) { t_relay(); exit; } else { t_reply ("503", "Service not available"); exit; } } Thanks in Advance, F.Chahrour

4 8

memory allocation failure
by Robert R 29 Feb '12

29 Feb '12

Hi, The openser service died on my servers after "memory allocation failure". This issue has been occurred a couple of times on two different servers within the last two months. Feb 29 08:31:59 /usr/sbin/openser[7115]: ERROR:core:do_action: memory allocation failure Feb 29 08:31:59 /usr/sbin/openser[7115]: ERROR:core:pv_set_ruri_user: do action failed Feb 29 08:31:59 /usr/sbin/openser[7115]: ERROR:core:do_assign: setting PV failed .... Feb 29 08:31:59 /usr/sbin/openser[7115]: ERROR:core:insert_cond_lump_after: out of pkg memory Feb 29 08:31:59 /usr/sbin/openser[7115]: ERROR:rr:build_rr: failed to insert lumps Feb 29 08:31:59 /usr/sbin/openser[7115]: ERROR:rr:record_route: failed to insert inbound Record-Route Feb 29 08:31:59 kernel: [8806798.263792] openser[7115] general protection rip:7f6e17eae69c rsp:7fff21dac5b0 error:0 Feb 29 08:31:59 /usr/sbin/openser[7164]: CRITICAL:core:receive_fd: EOF on 22 It seems increasing memory size in /etc/default/openser to 1024 didn't fix the issue. # Amount of memory to allocate for the running OpenSER server (in Mb) MEMORY=1024 Any advice would be appreciated. Thanks, R

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