sr-users

sr-users@lists.kamailio.org

20 participants
37471 discussions

[Kamailio-Users] About Kamailio-1.4.0-notls.
by Sunil Teli 12 Jan '09

12 Jan '09

Hi, I want to know that Kamailio-1.4.0-notls supports Dialog Event Package, If yes what configuration I have to do. If no the which version of the kamailio/OpenSER/OpenSIPS I have to use for the Dialog Event package support. Please go through the below call flow I have a problem. I am using kamailio-1.4.0-notls and trying to use dialog event package. The above call flow is as follows. 1) B an x-lite phone is Registered(B@kamailio) then C another x-lite phone is registered(c@kamailio) 2) Now from my application I am registering A and got registered(A@kamailio). 3) Now A is subscribing to B for the dialog event, so I am sending SUBSCRIBE message to kamailio server, that is I am sending SUBSCRIBE message from A@application to B@kamailio with the Event header. 4) Now I got 202 for the SUBSCRIBE. 5) Server Kamailio sends NOTIFY and then my application A sends 200 OK. 6) Now I will establish call between two x-lite phones B and C. Now My Question? When I establish call between B and C, I(Application A) have to get NOTIFY from kamailio server about the dialog event, I am not getting the NOTIFY for the dialog event since I have Subscribed to B for the Dialog event Package. Finally I(A application) want to know that dialog changes in the B Any help is appreciated to solve my problem. Advance thanks for the help. Thank You Regards, Sunil ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at <a href="http://www.techmahindra.com/Disclaimer.html">http://www.techmahindra.com/Disclaimer.html</a> externally and <a href="http://tim.techmahindra.com/Disclaimer.html">http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech Mahindra. ============================================================================================================================

2 1

[Kamailio-Users] Kamailio (OpenSER) 1.5.0 Freezing on Jan 26, 2009
by Daniel-Constantin Mierla 12 Jan '09

12 Jan '09

Hello, we approach the time for a new stable version: http://www.kamailio.org/dokuwiki/doku.php/development:release-policy Proposed date to freeze the code is: Mon, Jan 26, 2009. It will follow about one month of testing and the the new version will be out. There is a lot of new development since last major release 1.4.0, check a summary at: http://www.kamailio.org/dokuwiki/doku.php/features:new-in-1.5.x AFAIK, before release, 2-4 new more module are going to be introduced and couple of existing modules extended. This is a notification for all users and developers (existing or upcoming) to finish the work before the freezing data if they want to get their code in Kamailio (OpenSER) 1.5.0. The 1.5.x series will be the last to use the current core. Next releases will be based on SIP Router project: http://sip-router.org/ Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com

1 0

[Kamailio-Users] textops: regexp-based search/remove headers
by Daniel-Constantin Mierla 12 Jan '09

12 Jan '09

Hello, the textops module has two new functions that help to search and remove headers based on regular expressions: - is_present_hf_re(regexp) http://kamailio.org/docs/modules/devel/textops.html#id2506553 - remove_hf_re(regexp) http://kamailio.org/docs/modules/devel/textops.html#id2506863 Particularly the second is useful to remove a bunch of headers in one step. For example, if you have several proxyes in your platform and you exchange information between them via X-Something headers, then you can remove all with: remove_hf_re("^X-"); Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com

1 0

Re: [Kamailio-Users] [OpenSIPS-Users] WARNING:core:send2child: no free tcp receiver
by Ali Jawad 12 Jan '09

12 Jan '09

As an update I have retrieved this [root@sero ~]# /usr/local/sbin/openserctl ps Process:: ID=0 PID=30033 Type=attendant Process:: ID=1 PID=30036 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=2 PID=30037 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=3 PID=30038 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=4 PID=30039 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=5 PID=30041 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=6 PID=30042 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=7 PID=30043 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=8 PID=30044 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=9 PID=30045 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=10 PID=30046 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=11 PID=30047 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=12 PID=30048 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=13 PID=30049 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=14 PID=30050 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=15 PID=30051 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=16 PID=30052 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=17 PID=30053 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=18 PID=30054 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=19 PID=30055 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=20 PID=30056 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=21 PID=30057 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=22 PID=30060 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=23 PID=30062 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=24 PID=30064 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=25 PID=30065 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=26 PID=30066 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=27 PID=30067 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=28 PID=30068 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=29 PID=30069 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=30 PID=30070 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=31 PID=30071 Type=timer Process:: ID=32 PID=30072 Type=timer Process:: ID=33 PID=30073 Type=MI FIFO Process:: ID=34 PID=30074 Type=TCP receiver Process:: ID=35 PID=30075 Type=TCP receiver Process:: ID=36 PID=30076 Type=TCP receiver Process:: ID=37 PID=30077 Type=TCP receiver Process:: ID=38 PID=30079 Type=TCP receiver Process:: ID=39 PID=30080 Type=TCP receiver Process:: ID=40 PID=30081 Type=TCP receiver Process:: ID=41 PID=30082 Type=TCP receiver Process:: ID=42 PID=30084 Type=TCP receiver Process:: ID=43 PID=30085 Type=TCP receiver Process:: ID=44 PID=30086 Type=TCP receiver Process:: ID=45 PID=30087 Type=TCP receiver Process:: ID=46 PID=30090 Type=TCP receiver Process:: ID=47 PID=30091 Type=TCP receiver Process:: ID=48 PID=30092 Type=TCP receiver Process:: ID=49 PID=30094 Type=TCP receiver Process:: ID=50 PID=30095 Type=TCP receiver Process:: ID=51 PID=30096 Type=TCP receiver Process:: ID=52 PID=30097 Type=TCP receiver Process:: ID=53 PID=30098 Type=TCP receiver Process:: ID=54 PID=30099 Type=TCP receiver Process:: ID=55 PID=30100 Type=TCP receiver Process:: ID=56 PID=30101 Type=TCP receiver Process:: ID=57 PID=30102 Type=TCP receiver Process:: ID=58 PID=30103 Type=TCP receiver Process:: ID=59 PID=30104 Type=TCP receiver Process:: ID=60 PID=30105 Type=TCP receiver Process:: ID=61 PID=30107 Type=TCP receiver Process:: ID=62 PID=30109 Type=TCP receiver Process:: ID=63 PID=30110 Type=TCP receiver Process:: ID=64 PID=30111 Type=TCP main With Regards Ali Jawad System Administrator Splendor Telecom (www.splendor.net <outbind://206/www.splendor.net> ) Beirut, Lebanon Phone: +961 1 373725 Fax: + 961 1 375554 ________________________________ From: users-bounces(a)lists.opensips.org [mailto:users-bounces@lists.opensips.org] On Behalf Of Ali Jawad Sent: 2009-01-12 02:31 To: users(a)lists.opensips.org Cc: users(a)lists.kamailio.org Subject: [OpenSIPS-Users] WARNING:core:send2child: no free tcp receiver Hi All I am getting a lot of WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (7) I tried setting children to 20 that did not help, these warning start being displayed right after I start openser. Users frequently get service unavailable errors randomly when they try to connect, but I dont know if this is related to this warning message or not. As for the server there is plenty of CPU and RAM left, users range from 140 to 250 online all using tls. As for server limits I have set them to the following : You have new mail in /var/spool/mail/root [root@sero openser]# ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited file size (blocks, -f) unlimited pending signals (-i) 1024 max locked memory (kbytes, -l) 32 max memory size (kbytes, -m) unlimited open files (-n) 101024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 stack size (kbytes, -s) 10240 cpu time (seconds, -t) unlimited max user processes (-u) 16382 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited Is this warning message related to the serice unavailable problem, what does the warning message mean in more depth and how to get rid of it ? Thanks Getting alot of Jan 12 00:00:32 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (7) Jan 12 00:00:32 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (7) Jan 12 00:00:32 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (7) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (8) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (8) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (8) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (8) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (9) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (9) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (9) Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (9) Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (10) Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (10) Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (10) Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (10) Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (10) Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (10)

1 0

[Kamailio-Users] WARNING:core:send2child: no free tcp receiver
by Ali Jawad 12 Jan '09

12 Jan '09

Hi All I am getting a lot of WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (7) I tried setting children to 20 that did not help, these warning start being displayed right after I start openser. Users frequently get service unavailable errors randomly when they try to connect, but I dont know if this is related to this warning message or not. As for the server there is plenty of CPU and RAM left, users range from 140 to 250 online all using tls. As for server limits I have set them to the following : You have new mail in /var/spool/mail/root [root@sero openser]# ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited file size (blocks, -f) unlimited pending signals (-i) 1024 max locked memory (kbytes, -l) 32 max memory size (kbytes, -m) unlimited open files (-n) 101024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 stack size (kbytes, -s) 10240 cpu time (seconds, -t) unlimited max user processes (-u) 16382 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited Is this warning message related to the serice unavailable problem, what does the warning message mean in more depth and how to get rid of it ? Thanks Getting alot of Jan 12 00:00:32 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (7) Jan 12 00:00:32 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (7) Jan 12 00:00:32 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (7) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (8) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (8) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (8) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (8) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (9) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (9) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (9) Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (9) Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (10) Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (10) Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (10) Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (10) Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (10) Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (10)

1 0

[Serusers] ser behind NAT
by WANG Zhenzhong 11 Jan '09

11 Jan '09

Hi every body My SER is behind NAT, so when SER forward INVITE message, the VIA must be set to the public IP How? Thank you very much. 王振中 wangzz 艾诺通信系统（苏州）有限责任公司苏州工业园区国际科技园一期203A wangzz(a)avonaco.com ============================================

4 4

[Kamailio-Users] compare uri and aor
by Daniel-Constantin Mierla 11 Jan '09

11 Jan '09

Hello, I have introduced in siputils module functions to compare SIP URI and AoR in a more RFC manner, related to: https://sourceforge.net/tracker/index.php?func=detail&aid=2047019&group_id=… Now, for URI it does comparison of: - username - password - hostname - port For AoR, it does: - username - hostname - port (if port is missing, it assumes 5060 -- for URI comparison this is not used, conform to RFC3261) The questions are: - shall the comparison for URI be extended to follow full RFC? could get complex when taking URI headers in account -- haven't seen many, but the RFC allow them. Where to stop then the rules for comparing the URI? - for AoR, I am not sure if port should be considered, but when running multiple instances on different ports, it may make the difference? What do you think? Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com

3 5

[Serusers] SER monitoring capabilities
by Martin Lane 09 Jan '09

09 Jan '09

I'm looking for some information on the ability to monitor (have an indication of activity of, not listen too) the active calls real-time with the SER/SEMS suite. Can this be done and is anyone doing that? mll

3 2

[Serusers] SER monitoring capabilities
by Martin Lane 09 Jan '09

09 Jan '09

I'm looking for some information on the ability to monitor (have an indication of activity of not listen too) the active calls real-time with the SER/SEMS suite. Can this be done and is anyone doing that? mll

1 0

[Kamailio-Users] Help!! Getting get_hdr_field: out of memory
by Krunal Patel 09 Jan '09

09 Jan '09

Hi, I am using openser 1.2.3. I have increased PKG_MEM_POOL_SIZE to 4MB. Openser worked properly for 4 days since last restart. I found get_hdr_field: out of memory for all messages. I did openser restart & the issue is fixed now. Is anybody there who have faced the same issue? Thanks in advance!! -- Krunal patel

2 15

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