sr-users August 2010

sr-users@lists.kamailio.org

47 participants
71 discussions

Freezing for 3.1 on Monday, Aug 16
by Daniel-Constantin Mierla 17 Aug '10

17 Aug '10

Hello, as I could spot, there was some intense activity from Andrei in the last days with a new internal statistics API. To allow some time for it as well as for others (like me) to get some work done that is good to be in 3.1, I propose next Monday (Aug 16) as timeline to freeze the repo for new features. Probably during the freeze we can still merge some modules (in the way of moving one version to modules and removing the other as long as remaining version includes the features of the other) -- thinking of pdt, ratelimit, sms, ... Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com/

3 6

Re: [SR-Users] Kamailio 3.0 cann't access the RTPProxy
by JinKevin 17 Aug '10

17 Aug '10

Guys, Anyone has some feedback on this? Thanks, Kevin Hi All, I have the kamailio configed as below on Solaris 10 (Sparc): # ----- nathelper ----- #!ifdef WITH_NAT modparam("nathelper", "rtpproxy_sock", "udp:127.0.0.1:7722") modparam("nathelper", "natping_interval", 30) modparam("nathelper", "ping_nated_only", 1) modparam("nathelper", "sipping_bflag", 7) modparam("nathelper", "sipping_from", "sip:pinger@kamailio.org") modparam("registrar|nathelper", "received_avp", "$avp(i:80)") modparam("usrloc", "nat_bflag", 6) #!endif and rtpproxy is started as AppSer01:ipunity@/opt/ipunity$ ps -ef |grep rtp ipunity 4687 1 0 12:58:20 ? 0:00 /usr/local/bin/rtpproxy -l 210.xx.xx.xx -s udp:localhost:7722 AppSer01:ipunity@/opt/ipunity$ netstat -an |grep 7722 127.0.0.1.7722 Idle 127.0.0.1.41509 127.0.0.1.7722 Connected 127.0.0.1.41510 127.0.0.1.7722 Connected 127.0.0.1.41511 127.0.0.1.7722 Connected 127.0.0.1.41512 127.0.0.1.7722 Connected 127.0.0.1.41513 127.0.0.1.7722 Connected 127.0.0.1.41514 127.0.0.1.7722 Connected 127.0.0.1.41515 127.0.0.1.7722 Connected 127.0.0.1.41516 127.0.0.1.7722 Connected 127.0.0.1.41517 127.0.0.1.7722 Connected 127.0.0.1.41518 127.0.0.1.7722 Connected 127.0.0.1.41519 127.0.0.1.7722 Connected However, kamailio is not able to connect the rtpporxy, Jul 24 12:58:59 AppSer01 /usr/local/kamailio-3.0/sbin/kamailio[22867]: [ID 788202 local0.error] ERROR: nathelper [nathelper.c:2457]: can't send command to a RTP proxy Jul 24 12:58:59 AppSer01 /usr/local/kamailio-3.0/sbin/kamailio[22867]: [ID 844113 local0.error] ERROR: nathelper [nathelper.c:2492]: proxy <udp:127.0.0.1:7722> does not respond, disable it Jul 24 12:58:59 AppSer01 /usr/local/kamailio-3.0/sbin/kamailio[22867]: [ID 582370 local0.error] ERROR: nathelper [nathelper.c:3144]: no available proxies Jul 24 12:58:59 AppSer01 /usr/local/kamailio-3.0/sbin/kamailio[22867]: [ID 788202 local0.error] ERROR: nathelper [nathelper.c:2457]: can't send command to a RTP proxy Jul 24 12:58:59 AppSer01 /usr/local/kamailio-3.0/sbin/kamailio[22867]: [ID 844113 local0.error] ERROR: nathelper [nathelper.c:2492]: proxy <udp:127.0.0.1:7722> does not respond, disable it Jul 24 12:58:59 AppSer01 /usr/local/kamailio-3.0/sbin/kamailio[22867]: [ID 582370 local0.error] ERROR: nathelper [nathelper.c:3144]: no available proxies Jul 24 12:59:04 AppSer01 /usr/local/kamailio-3.0/sbin/kamailio[22870]: [ID 582370 local0.error] ERROR: nathelper [nathelper.c:2627]: no available proxies Jul 24 12:59:04 AppSer01 /usr/local/kamailio-3.0/sbin/kamailio[22870]: [ID 582370 local0.error] ERROR: nathelper [nathelper.c:2627]: no available proxies Any helps are appreciated. Thanks, Kevin 聊天+搜索+邮箱想要轻松出游,手机MSN帮你搞定! 立刻下载！ _________________________________________________________________ MSN十年回馈，每位用户可免费获得价值25元的卡巴斯基反病毒软件2010激活码，快来领取！ http://kaba.msn.com.cn/?k=1

3 16

Re: [SR-Users] Kamailio doesn't start
by Ernest Mavrel 17 Aug '10

17 Aug '10

2 4

please help me with domainpolicy module.
by truong ngoc THANH 15 Aug '10

15 Aug '10

hi all, I try to configure domainpolicy but it does not work. =========== my scenarios is : 1: i configure multi domain with kamailio, and i set two domain example.com and kamailio.com which have the same ip(192.168.1.40). 2:the sip client can register and make call in local domain . 3: i try to make policy in domain example.com to call to kamailio.com. my config as : ============ i add some line in kamailio.cfg loadmodule "domainpolicy.so" #---------------------domainpolicy---------------------------- modparam("domainpolicy", "db_url", "mysql://openser:openserrw@localhost/kamailio") modparam("domainpolicy", "dp_table", "supportedpolicies") modparam("domainpolicy", "dp_col_rule", "rules") modparam("domainpolicy", "dp_col_type", "type") modparam("domainpolicy", "dp_col_att", "att") modparam("domainpolicy", "dp_col_val", "val") modparam("domainpolicy", "port_override_avp", "portoverride") modparam("domainpolicy", "transport_override_avp", "transportoverride") modparam("domainpolicy", "domain_replacement_avp", "domainreplacement") modparam("domainpolicy", "domain_prefix_avp", "domainprefix") modparam("domainpolicy", "domain_suffix_avp", "domainsuffix") modparam("domainpolicy", "send_socket_avp", "sendsocket") if (is_method("INVITE")) { setflag(1); # do accounting dp_can_connect();#< i add dp_apply_policy();#< i add in mysql i create table : and add rules as : mysql> select * from supportedpolicies; +----+--------------+------+-------------------+--------------+--------------+-------------------+-------------------+--------------+--------------+-------------+ | id | rules | type | att | val | portoverride | transportoverride | domainreplacement | domainprefix | domainsuffix | description | +----+--------------+------+-------------------+--------------+--------------+-------------------+-------------------+--------------+--------------+-------------+ | 5 | kamailio.com | dom | domainreplacement | kamailio.com | 5060 | udp | kamailio.com | NULL | NULL | | | 6 | example.com | dom | domainreplacement | kamailio.com | NULL | NULL | kamailio | NULL | NULL | | +----+--------------+------+-------------------+--------------+--------------+-------------------+-------------------+--------------+--------------+-------------+ 2 rows in set (0.00 sec) the log when i make call from 1(a)example.com to 3(a)kamailio.com Aug 14 10:16:41 appliance /usr/local/sbin/kamailio[2140]: INFO: domainpolicy [domainpolicy.c:547]: looking up Domain itself: example.com Aug 14 10:16:41 appliance /usr/local/sbin/kamailio[2140]: INFO: domainpolicy [domainpolicy.c:429]: checking for 'example.com'. Aug 14 10:16:41 appliance /usr/local/sbin/kamailio[2140]: INFO: domainpolicy [domainpolicy.c:473]: querying database OK Aug 14 10:16:41 appliance /usr/local/sbin/kamailio[2140]: INFO: domainpolicy [domainpolicy.c:506]: DB returned domainreplacement/kamailio.com Aug 14 10:16:41 appliance /usr/local/sbin/kamailio[2140]: INFO: domainpolicy [domainpolicy.c:551]: found a match on domain itself Please help me to correct config to use domainpolicy thanks for help.peter_green

2 1

Issue using subst
by Uriel Rozenbaum 15 Aug '10

15 Aug '10

Hi guys, I'm having a weird situation when trying to modify some parts of the RPID on my config file. I'm using Kamailio 1.5.3-notls The code is the following: ... subst('/^Remote-Party-ID:(.*)sip:(.*)@(.*)$/Remote-Party-ID:\1sip:$avp(s:ANIegress)@\3/ig'); subst('/^Remote-Party-ID:(.*)"(.*)"(.*)sip:(.*)$/Remote-Party-ID:\1"$avp(s:ANIegress)"\3sip:\4/ig'); ... With the first line I'm trying, to change the user part of the SIP-URI to the value in $avp(s:ANIegress). Then i just replace the token between double quotes (if any) with the value in $avp(s:ANIegress). But when I check the captured (ngrep) results I have the following: Before: Remote-Party-ID: "60911000" <sip:541160911100@192.168.200.100>;privacy=off;screen=no. After: Remote-Party-ID: "60911000" <sip:1160911100@192.168.200.100>;privacy=off;screen=no.Remote-Party-ID: "1160911100" <sip:541160911100@192.168.200.100>;privacy=off;screen=no. Can anyone point me on the direction to solve the issue, or a better way to replace the values in RPID, PAI (and possibly From Header for some providers)? Thanks in advence! Uriel

3 6

Is this a BUG?
by dotnetdub 12 Aug '10

12 Aug '10

Hi All, I see this in every call setup.. CRITICAL: dialog [dlg_hash.c:591]: bogus event 6 in state 2 for dlg 0xaf933bd0 [3739:1530909163] with clid ' 5959362a340dfa7938cf52ae1ba4b9d7(a)my.proxy.com' and tags 'as5b636a8a' '' I am running SIP-Router 3.01 I note this thread: http://www.mail-archive.com/sr-dev@lists.sip-router.org/msg05668.html but it's inconclusive. It doesn't seem to cause any issue but I would like to get it sorted. Thanks Brian

5 9

[Kamailio-Users] kamailio and PRACK
by BERGANZ François 10 Aug '10

10 Aug '10

Hello, Does kamailio support PRACK method ? If yes, how? Thank you Cordialement, BERGANZ François P Pensez à l'Environnement, n'imprimez ce mail que si nécessaire.

5 4

Billing
by Lens Oreste 10 Aug '10

10 Aug '10

Are you looking for an affordable billing solution for Kamailio? if so SGT got you cover, we are a commercial grade billing. We offer hosted billing solution for kamailio and opensips. Our billing is radius based and fully integrated with kamailio/opensips. please send us an email at info at sgthire.com or support at sgthire dot com

2 1

time formats (specifically in db_flatstore)
by SIP Projects 10 Aug '10

10 Aug '10

Using version 1.5.2. Trying to migrate acc from db_mysql to db_flatstore to reduce io wait during heavy dialing. However, the default time format changes from normal YYYY-MM-DD hh:mm:ss to unixtime (I think) in flatstore. I tried using $TF but its format is even more non-standard. Is there a way to change time format for either the default acc time field in the db_flatstore module or $TF so I can 'LOAD DATA' into mysql as datetime? Thanks, Matt

3 5

PDT ran out of pkg memory using pdt_list
by JR Richardson 10 Aug '10

10 Aug '10

Hi All, I loaded up the PDT database with about 35K records and when I issue the commad "kamctl fifo pdt_list" I get: 3(3018) ERROR: <core> [tree.c:139]: no more pkg mem 3(3018) ERROR: mi_fifo [fifo_fnc.c:509]: command (pdt_list) processing failed Searching around I found the http://www.kamailio.org/dokuwiki/doku.php/troubleshooting:memory which suggest I adjust the pkg mem size in config.h. In config.h, I found: /*used only if PKG_MALLOC is defined*/ #define PKG_MEM_POOL_SIZE 4*1024*1024 So is this what I am supposed to adjust? Maybe try: #define PKG_MEM_POOL_SIZE 4*2048*2048 or #define PKG_MEM_POOL_SIZE 8*1024*1024 Which one would be a logical adjustment? Also, is there a correlation between pkg mem and database record size as related to pdt_list? The idea is to have a few 100K records loaded in kamailio and be able to perform "kamctl fifo pdt_list | grep 512345" to show this prefix route. But without enough memory, doesn't work. Thanks. JR -- JR Richardson Engineering for the Masses

8 29

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 August 2010