sr-users

sr-users@lists.kamailio.org

42 participants
37517 discussions

Using dispatcher's algorithm 12
by George Diamantopoulos 04 Dec '17

04 Dec '17

Hello all, I've been trying to use dispatcher's algorithm "12" to fork REGISTER messages constructed with uac module to all destinations within a set. However, the request is routed to only one destination. Is anything else needed in addition to calling ds_select_dst("0", "12") in the configuration script? Thanks. BR, George

3 5

bash script to install siremis&kamailio
by Atux Atux 04 Dec '17

04 Dec '17

Hi. i would like to ask if someone has found any bash script that could install all at once for Kamailio and Siremis in ubuntu/debian or even in centos.

2 1

dmq issues
by Aidar Kamalov 03 Dec '17

03 Dec '17

Hello. I have 4 kamailio nodes with same config: modparam("dmq", "server_address", "sip:LOCALIP:5050") modparam("dmq", "notification_address", "sip:192.168.8.213:5050") modparam("dmq", "notification_address", "sip:192.168.10.54:5050") modparam("dmq", "notification_address", "sip:192.168.107.195:5050") modparam("dmq", "notification_address", "sip:192.168.150.225:5050") modparam("dmq", "num_workers", 6) modparam("dmq_usrloc", "enable", 1) modparam("dmq_usrloc", "sync", 1) modparam("dmq_usrloc", "batch_size", 2000) modparam("dmq_usrloc", "batch_usleep", 1000) regularly (don't know why) I've got issues - replication is broken, for example now at all nodes I have: # kamcmd dmq.list_nodes { host: 192.168.8.213 port: 5050 resolved_ip: 192.168.8.213 status: 2 last_notification: 0 local: 0 } { host: 192.168.10.54 port: 5050 resolved_ip: 192.168.10.54 status: 2 last_notification: 0 local: 0 } { host: 192.168.150.225 port: 5050 resolved_ip: 192.168.150.225 status: 8 last_notification: 0 local: 0 } { host: 192.168.107.195 port: 5050 resolved_ip: 192.168.107.195 status: 2 last_notification: 0 local: 1 } but at node 192.168.150.225: # kamcmd dmq.list_nodes { host: 192.168.150.225 port: 5050 resolved_ip: 192.168.150.225 status: 2 last_notification: 0 local: 0 } { host: 192.168.150.225 port: 5050 resolved_ip: 192.168.150.225 status: 2 last_notification: 0 local: 1 } nodes restart doesn't help. but if i exec systemctl stop kamailio && sleep 15 && systemctl start kamailio it is partially solve my issue - dmq.list_nodes show all nodes, but at 192.168.150.225 i see not all user locations: they are added gradually There is no errors in logs Dec 1 08:28:37 sipufa /usr/sbin/kamailio[18252]: NOTICE: <script>: ROOT: KDMQ notification_peer [15f3edf9258014d1-7114(a)192.168.8.213] Dec 1 08:28:38 sipufa /usr/sbin/kamailio[18271]: NOTICE: <script>: ROOT: KDMQ notification_peer [7acb9eae627482f8-87828(a)192.168.10.54] Dec 1 08:28:39 sipufa /usr/sbin/kamailio[18250]: NOTICE: <script>: ROOT: KDMQ notification_peer [621ad9f474b335e2-18272(a)192.168.150.225] Dec 1 08:28:40 sipufa /usr/sbin/kamailio[18252]: NOTICE: <script>: ROOT: KDMQ notification_peer [7b817f6a6244f923-8872(a)192.168.107.195] Dec 1 08:28:47 sipufa /usr/sbin/kamailio[18271]: NOTICE: <script>: ROOT: KDMQ usrloc [7acb9eae627482f2-87794(a)192.168.10.54] Dec 1 08:29:20 sipufa /usr/sbin/kamailio[18251]: NOTICE: <script>: ROOT: KDMQ usrloc [7acb9eae627482ef-87790(a)192.168.10.54] -- Aydar A. Kamalov

3 8

kamailio as application server
by eyas barhouk 01 Dec '17

01 Dec '17

Hello if i need to use kamailio as an application server like mmtel for example how could i do that and what is the features that kamailio have if i want to use it as application server in another word what is the type of application server it could be act like (mmtel - presence) ? and thanks for help

2 1

In need of a simple, stateless 302 redirect for INVITE
by Robert 01 Dec '17

01 Dec '17

Hello again, I am not a SIP expert, and I’m new to Kamailio, really enjoying learning it, but I’ve hit a blocker and I’m pretty sure I’ve missed something really simple. I’m looking to implement the Redirect Server from here: https://tools.ietf.org/html/rfc3665#section-3.6 <https://tools.ietf.org/html/rfc3665#section-3.6> (the Avaya Session Manager being Alice), Kamailio as the Redirect Server. My configuration is working fine, and I can see the 302 going back (to Avaya SM), I then get the ACK I’m expecting. The incoming SIP request contains a number of fields, including a Contact header, which I’m told SM needs on the return. But the send_reply() or sl_send_reply() doesn’t return the Contact header, and I am unable to manually set it, or any other header, using any of the append_hf(), append_to_reply() etc. mechanisms. I’m executing a msg_apply_changes() which succeeds, but no Contact header is returned. I’ve tried an sl_send_reply(“100”, “Trying”) before any other processing, and Wireshark confirms that the SIP response is basically identical to the 302 response sent after processing… The goal is to run this stateless, I’m assuming this is possible - it certainly feels like it should be. I’ve re-read the intros & tutorials, and other reading material such as this http://kamailio.org/docs/ser-getting-started/SER-GettingStarted.pdf <http://kamailio.org/docs/ser-getting-started/SER-GettingStarted.pdf> but, this, even my best Google-fu has left me utterly stumped… The sl_send_reply documentation https://kamailio.org/docs/modules/5.2.x/modules/sl.html#sl_send_reply <https://kamailio.org/docs/modules/5.2.x/modules/sl.html#sl_send_reply> states “If the code is in the range 300-399 (redirect reply), the current destination set is appended to the reply as Contact headers” but the Contact header is definitely not being set when I use this. Apologies in advance if eyes are rolling and this is really obvious, or (and?) that my lack of SIP knowledge is shining through - any tips or guidance would be appreciated. I certainly feel overwhelmed by the number of modules and the interplay between them. If the answers to this, and other things along these lines are contained in the admin book, that’s fab, I’ve just filled the form out :) Cheers - Robert...

3 3

DBURL password in clear
by Robert 01 Dec '17

01 Dec '17

Hello, I’m working for a UK high street bank and our Kamailio implementation has been challenged because we’ve got database passwords held in clear in the configuration file. I am unable to find any examples of where this has been worked around, there doesn’t seem to be any module or configuration means of supplying a variable in the modparam() entry that is expanded a startup. The security tutorials only seem to relate to the SIP level of security, not Kamailio as a platform. My requirement is simple, I need to be able to supply a password via means such as loading a variable from a run-once script at start up, or a module. The ideal would be to be able to read in a Docker secret :) I am by no means a Kamailio expert, so apologies in advance if this is a mindblowingly basic thing to achieve, but I do feel I’ve exhausted the Kamailio documentation, wiki etc. and all the goodness Google usually has to offer and drawn a blank. Sincere thanks in advance for any assistance. Cheers - Robert...

5 14

Dispatcher latency stats monitoring with statsd
by Julien Chavanton 01 Dec '17

01 Dec '17

Not sure if anyone is using "latency measurement" feature in Kamailio dispatcher module, I thought I could share a very simple Python script that I am using to monitor remote gateway using this. Sample Script is attached, it will post data to statsd and is working in cron The feature can be enabled : 3.27. ds_ping_latency_stats (int) Enable latency measurement when pinging nodes If set to 0, disable latency measurement. If set to 1, enable latency measurement https://www.kamailio.org/docs/modules/devel/modules/dispatcher.html#dispatc… This is one use case of this feature, another one will be to load balance based on congestion detected on latency, I am planning to share a lab experiment in a little while. Regards

2 1

[CFP] FOSDEM 2018, RTC devroom, speakers, volunteers neeeded
by FOSDEM RTC Team 30 Nov '17

30 Nov '17

FOSDEM is one of the world's premier meetings of free software developers, with over five thousand people attending each year. FOSDEM 2018 takes place 3-4 February 2018 in Brussels, Belgium. https://fosdem.org This email contains information about: - Real-Time Communications dev-room and lounge, - speaking opportunities, - volunteering in the dev-room and lounge, - related events around FOSDEM, including the XMPP summit, - social events (the legendary FOSDEM Beer Night and Saturday night dinners provide endless networking opportunities), - the Planet aggregation sites for RTC blogs Call for participation - Real Time Communications (RTC) ======================================================= The Real-Time dev-room and Real-Time lounge is about all things involving real-time communication, including: XMPP, SIP, WebRTC, telephony, mobile VoIP, codecs, peer-to-peer, privacy and encryption. The dev-room is a successor to the previous XMPP and telephony dev-rooms. We are looking for speakers for the dev-room and volunteers and participants for the tables in the Real-Time lounge. The dev-room is only on Sunday, 4th of February 2018. The lounge will be present for both days. To discuss the dev-room and lounge, please join the FSFE-sponsored Free RTC mailing list: https://lists.fsfe.org/mailman/listinfo/free-rtc To be kept aware of major developments in Free RTC, without being on the discussion list, please join the Free-RTC Announce list: http://lists.freertc.org/mailman/listinfo/announce Speaking opportunities ---------------------- Note: if you used FOSDEM Pentabarf before, please use the same account/username Real-Time Communications dev-room: deadline 23:59 UTC on 30th of November. Please use the Pentabarf system to submit a talk proposal for the dev-room. On the "General" tab, please look for the "Track" option and choose "Real Time Communications devroom". https://penta.fosdem.org/submission/FOSDEM18/ Other dev-rooms and lightning talks: some speakers may find their topic is in the scope of more than one dev-room. It is encouraged to apply to more than one dev-room and also consider proposing a lightning talk, but please be kind enough to tell us if you do this by filling out the notes in the form. You can find the full list of dev-rooms at https://www.fosdem.org/2018/schedule/tracks/ and apply for a lightning talk at https://fosdem.org/submit Main track: the deadline for main track presentations is 23:59 UTC 3rd of November. Leading developers in the Real-Time Communications field are encouraged to consider submitting a presentation to the main track at https://fosdem.org/submit First-time speaking? -------------------- FOSDEM dev-rooms are a welcoming environment for people who have never given a talk before. Please feel free to contact the dev-room administrators personally if you would like to ask any questions about it. Submission guidelines --------------------- The Pentabarf system will ask for many of the essential details. Please remember to re-use your account from previous years if you have one. In the "Submission notes", please tell us about: - the purpose of your talk - any other talk applications (dev-rooms, lightning talks, main track) - availability constraints and special needs You can use HTML and links in your bio, abstract and description. If you maintain a blog, please consider providing us with the URL of a feed with posts tagged for your RTC-related work. We will be looking for relevance to the conference and dev-room themes, presentations aimed at developers of free and open source software about RTC-related topics. Please feel free to suggest a duration between 20 minutes and 55 minutes but note that the final decision on talk durations will be made by the dev-room administrators based on the number of received proposals. As the two previous dev-rooms have been combined into one, we may decide to give shorter slots than in previous years so that more speakers can participate. Please note FOSDEM aims to record and live-stream all talks. The CC-BY license is used. Volunteers needed ================= To make the dev-room and lounge run successfully, we are looking for volunteers: - FOSDEM provides video recording equipment and live streaming, volunteers are needed to assist in this - organizing one or more restaurant bookings (dependending upon number of participants) for the evening of Saturday, 3rd of February - participation in the Real-Time lounge - helping attract sponsorship funds for the dev-room to pay for the Saturday night dinner and any other expenses - circulating this Call for Participation to other mailing lists Related events - XMPP and RTC summits ===================================== The XMPP Standards Foundation (XSF) has traditionally held a summit in the days before FOSDEM. There is discussion about a similar summit taking place on the 2nd of February 2018 http://wiki.xmpp.org/web/Summit_22 - please join the mailing list for details: http://mail.jabber.org/mailman/listinfo/summit Social events and dinners ========================= The traditional FOSDEM beer night occurs on Friday, 2nd of February. On Saturday night, there are usually dinners associated with each of the dev-rooms. Most restaurants in Brussels are not so large so these dinners have space constraints and reservations are essential. Please subscribe to the Free-RTC mailing list for further details about the Saturday night dinner options and how you can register for a seat: https://lists.fsfe.org/mailman/listinfo/free-rtc Spread the word and discuss =========================== If you know of any mailing lists where this CfP would be relevant, please forward this email. If this dev-room excites you, please blog or microblog about it, especially if you are submitting a talk. If you regularly blog about RTC topics, please send details about your blog to the planet site administrators: All projects http://planet.freertc.org planet(a)freertc.org XMPP http://planet.jabber.org ralphm(a)ik.nu SIP http://planet.sip5060.net planet(a)sip5060.net (Español) http://planet.sip5060.net/es/ planet(a)sip5060.net Please also link to the Planet sites from your own blog or web site as this helps everybody in the free real-time communications community. Contact ======= For any private queries, contact us directly using the address fosdem-rtc-admin(a)freertc.org and for any other queries please ask on the Free-RTC mailing list: https://lists.fsfe.org/mailman/listinfo/free-rtc The dev-room administration team: Saúl Ibarra Corretgé <saghul(a)gmail.com> Iain R. Learmonth <irl(a)debian.org> Ralph Meijer <ralphm(a)ik.nu> Daniel-Constantin Mierla <miconda(a)gmail.com> Daniel Pocock <daniel(a)pocock.pro>

3 2

blf in kamailio dmq cluster
by Aidar Kamalov 30 Nov '17

30 Nov '17

Hello, I have two(or more) kamailio servers with dmq module and dmq_usrloc - sip1.example.com and sip2.example.com publish and subcribe replication works too. BLF works fine if clients connected to the same kamailio server, because in active_watchers table stored with same domain sip1.example.com But what to do when call going from one server to second? Is there any configuration to ignore domain in pusblish, subscribe, notify, etc? -- Aydar A. Kamalov

3 7

OpenSIPS-devel not starting (TCP Error)
by SamyGo 29 Nov '17

29 Nov '17

Hi, I just installed the head version from git. version: opensips 2.4.0-dev (x86_64/linux) flags: STATS: On, SHM_EXTRA_STATS, EXTRA_DEBUG, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, QM_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535 poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. git revision: d1a4419 main.c compiled on 19:53:20 Nov 28 2017 with gcc 4.8 It was compiled with EXTRA_DEBUG and DBG_TCPCON flags; While starting opensips with the residential vanilla script it gives following error: Nov 28 20:05:52 [30899] ERROR:core:tcp_init: oom con hist Nov 28 20:05:52 [30899] CRITICAL:core:main: could not initialize tcp Nov 28 20:05:52 [30899] INFO:core:cleanup: cleanup Nov 28 20:05:52 [30899] DBG:core:shm_mem_destroy: destroying the shared memory lock Nov 28 20:05:52 [30899] NOTICE:core:main: Exiting.... already running Even if I remove the proto_tcp, and tcp related things this still gives error and doesn't start. Kindly help. Regards, Sammy

2 3

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