sr-users

sr-users@lists.kamailio.org

4 participants
37456 discussions

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

Presence between different domains
by Manuel Perez 29 Feb '12

29 Feb '12

Hello, I've used kamailio 3.2.2, i have rls, simple presence and xcap support working. I've replicated this server into another one in a different domain, but presence between domains is not working. I'm using for presence presence.so, presence_xml.so and presence_mwi.so. In route[WITHINDLG] i have the following lines: ... if (is_method("SUBSCRIBE|NOTIFY") && uri==myself) route(PRESENCE); ... When NOTIFY from user B at domain B arrives to the server at domain A, the message is not forwarded to the user A, How can i achieve this? Thank you.

2 3

dialog doesn't clear calls that were re-INVITEd shortly after ACK
by Andrew Pogrebennyk 29 Feb '12

29 Feb '12

Hi, I noticed dialog module showing calls that have already been terminated with state=4. The kamailio version is 3.1.5, I'm aware of certain limitations of dialog module in this version (must use stateless replies, create dialog after 407), but this is something rather new. In kamailio config I'm using dlg_manage() for initial INVITEs and BYE/CANCEL and in-dialog requests are loose-routed, so nothing finicky. The call scenario is: A calls B, B answers the call, A immediately after sending ACK for the 200 OK issues re-INVITE. After some seconds A hangs up, and the dialog stays in memory in state=4, e.g.: dialog:: hash=3304:623200556 state:: 4 ref_count:: 2 timestart:: 1329938667 timeout:: 78590167 callid:: MGExMjRiYzMzN2Q5YWU4YjRiMjFjYTYwYWZlMGFlMzY. from_uri:: sip:sipwise-user1@67.202.62.202 from_tag:: 4207e429 caller_contact:: sip:sipwise-user1@80.108.64.151:46420 caller_cseq:: 3 caller_route_set:: <sip:127.0.0.1:5060;lr;r2=on>,<sip:67.202.62.202:5060;lr;r2=on> caller_bind_addr:: udp:127.0.0.1:5062 callee_bind_addr:: udp:127.0.0.1:5062 to_uri:: sip:43991002@67.202.62.202 to_tag:: 6C8F89E9-4F4540EA0001F575-AC557700 callee_contact:: sip:sipwise-user2@127.0.0.1:5080 callee_cseq:: 11 callee_route_set:: When I set dlg_match_mode=1 the problem goes away. I would like however to understand why the dialog fails to clear in default mode (DID_ONLY), because the dialog cookie seems to be preserved by caller in all in-dialog requests properly. There is nothing in the debug log and trace attached that catches my eye. Do you see anything wrong there? In trace file the proxy address is 127.0.0.1:5062. You may notice that the actual signaling flow is a little bit more complicated, I will gladly answer any questions about it. For this test I've used two lines in the eyeBeam softphone, when one line answers the other is automatically put on hold which is what I want. Then I un-hold the callee and clear the call. The customer is reporting multiple stale calls when re-INVITE is sent by Cirpack PSTN gw immediately after call connect, which is basically the same call flow I am talking about, it is just not practical for me to run kamailio with debug=3 there all the time. I am going to try theredlg_match_mode=1 though and see if the problem goes away. Any ideas?

1 1

Re: [SR-Users] sr-users Digest, Vol 81, Issue 95
by Yufei Tao 29 Feb '12

29 Feb '12

Hi Thanks for your reply! I already set the accounting flag like you say. And all normal BYEs are inserted into the acc table fine. Just internally generated BYEs don't get inserted in acc table. I've done a bit googling and added event_route: event_route[tm:local-request] { if (is_method("BYE")) { xlog("L_INFO", "event_route: BYE: callid=$ci, cseq=$cs - internally generated\n"); setflag(FLT_ACC); # do accounting ... setflag(FLT_ACCFAILED); # ... even if the transaction fails } } When I have two clients in a call, I disconnect the network for both clients, so no RTP either direction, which triggered mediaproxy to send dlg_bye_dlg to Kamailio, which sent BYE to both clients. I can see from the log that event_route did get executed, and BYE sent to both clients, but still BYE isn't inserted to acc table. The code inside event_route() above is copied from my route[WITHINDLG], which for client-generated BYEs operates correctly (inserts BYEs into acc table). But in event_route it didn't work. I also tried to use sql_query to insert BYE into acc table in event_route and it causes Kamailio to crash. Using sql_query to select * from acc also causes Kamailio to crash. Any idea where I've done wrong? I'm very much lost. Thank you! Yufei > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 27 Feb 2012 13:21:50 -0500 > From: Alex Balashov <abalashov(a)evaristesys.com> > Subject: Re: [SR-Users] How to do accounting for Kamailio-generated > BYEs? > To: sr-users(a)lists.sip-router.org > Message-ID: <4F4BC9BE.8000704(a)evaristesys.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 02/27/2012 12:58 PM, Yufei Tao wrote: >> Hi >> >> I've got a mediaproxy that detects no media, and sends dlg_end_dlg to >> Kamailio via mi_datagram socket. Then Kamailio sends BYE to both calling >> parties. It all works fine. But my question is, how to do accounting for >> these Kamailio-generated BYEs? They don't appear in the acc table. > In the loose_route() section of the config script, set the accounting > flag for BYEs, e.g. > > if(is_method("BYE")) > setflag(xx); > > -- Yufei Tao Red Embedded This E-mail and any attachments hereto are strictly confidential and intended solely for the addressee. If you are not the intended addressee please notify the sender by return and delete the message. You must not disclose, forward or copy this E-mail or attachments to any third party without the prior consent of the sender. Red Embedded Design, Company Number 06688253 Registered in England: The Waterfront, Salts Mill Rd, Saltaire, BD17 7EZ

1 2

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