sr-users January 2010

sr-users@lists.kamailio.org

73 participants
127 discussions

[Serusers] ReTransmission of CANCELs on 0.9.7

by rupert.organ＠bt.com

Hi All, Has anyone come up against an issue on 0.9.6 / 0.9.7 whereby a SIP App Server, delivers a CANCEL to the SER. The SER proxies the CANCELs to all the forked endpoints. At the same time it sends "200 Cancelling" back to the SIP App server...(this suppresses CANCEL retransmission from the SIP App server). If one of the CANCELs from the SER to the SIP UA gets lost....the phone keeps ringing. There is no CANCEL retransmission on the SER !!! There is CANCEL retransmission on the SIP App, but when it sends SER replies "no pending branches" Ideally want the SER do CANCEL retransmissions. I understand the timers were rewritten in 0.10.x but this is not hardened version like 0.9.6....any suggestions? Thanks in advance Rupert

14 years, 7 months

[Kamailio-Users] What is the best module for routing INVITE based on DID in R-URI?

by Geoffrey Mina

Hello, I am putting up a Kamailio server which will do nothing but route INVITE requests from my upstream carrier to individual offices on my side. The office locations will NOT be registered SIP UAs, but other Kamailio proxy servers. What I want to have is a database of DIDs associated with a forwarding IP:Port and/or SRV records. 5555551212 ==> 1.2.3.4:5060 5555551213 ==> 1.2.3.5:5060 etc. Any guidance on what the best approach to achieving my goal would be much appreciated. Thanks, Geoff

14 years, 8 months

[Kamailio-Users] ratelimit enhancements

by Daniel-Constantin Mierla

Hi Marius, since you did some updates to this module, I am opening for debate some needed enhancements I did during 3.0 testing phase and want to get opinions how to get in the code repo. Practically is a new module I named for now ratelimit2 and my last idea is to get it named pipelimit in the trunk. The reason for a new module are some major changes. The module uses the same algorithm but its core is overhaul. - definitions of pipes are loaded from database - there can be unlimited number of pipes - pipes are identified by string names - should be possible to reload pipes at runtime (iirc, not yet in) - new pipes can be added at runtime - functions accept variables to identify the pipe Since I never used queues from this module and haven't spent time to understand the concept behind, this functionality is completely missing. The old module might be good to keep in place, probably many people are using it in this form. So, proposals? What is the way to go on? Common code (algorithms) can be made lib at some point. Cheers, Daniel -- Daniel-Constantin Mierla * http://www.asipto.com/

14 years, 8 months

[Kamailio-Users] Carrierroute issue

by michel freiha

Hi all, I'm using carrierroute module and ie seems that it's not working well...Suppose I have 2 entries in carrierroute table...Entry 1 with scan prefix 00 and prob 0 and a second entry with scan prefix 00 and prob=1...As soon as i make a call, this call will be forwarded to the entry with prob 0 because i guess it appears before the one with prob 1 in the table... When starting Kamailio I got the below: Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: adding prefix 1, prob -14931260.000000 Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: domain 0 not found, add it Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_tree: tree default has 1 trees Jul 29 12:30:11 [23143] DBG:carrierroute:add_route_tree: tree 0Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: created route tree: 0, with id 0 Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: found route, now adding Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_rule: no backed up rules Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: adding prefix , prob -14931260.000000 Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: found domain 0 Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: found route, now adding Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_rule: no backed up rules Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: adding prefix 011, prob -14931260.000000 Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: found domain 0 Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: found route, now adding Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_rule: no backed up rules Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: adding prefix 00, prob -14931260.000000 Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: found domain 0 Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: found route, now adding Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_rule: no backed up rules Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: adding prefix 111, prob -14931260.000000 Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: found domain 0 Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: found route, now adding Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_rule: no backed up rules Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: adding prefix 00, prob -14931260.000000 Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: found domain 0 Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: found route, now adding Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_rule: no backed up rules Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: adding prefix , prob -14931260.000000 Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: found domain 0 Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: found route, now adding Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_rule: no backed up rules Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: adding prefix 011, prob -14931260.000000 Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: found domain 0 Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: found route, now adding Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_rule: no backed up rules Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: adding prefix 011, prob -14931260.000000 Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: found domain 0 Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: found route, now adding Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_rule: no backed up rules Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: adding prefix , prob -14931260.000000 Jul 29 12:30:11 [23143] INFO:carrierroute:get_route_tree: found domain 0 Jul 29 12:30:11 [23143] INFO:carrierroute:add_route: found route, now adding Jul 29 12:30:11 [23143] INFO:carrierroute:add_route_rule: no backed up rules It seems that kamailio is not reading probability entry in carrier route table Please find below carrierroute table structure: CREATE TABLE IF NOT EXISTS `carrierroute` ( `id` int(10) unsigned NOT NULL auto_increment, `carrier` int(10) unsigned NOT NULL default '0', `domain` varchar(64) NOT NULL default '', `scan_prefix` varchar(64) NOT NULL default '', `flags` int(11) unsigned NOT NULL default '0', `mask` int(11) unsigned NOT NULL default '0', `prob` float NOT NULL default '0', `strip` int(11) unsigned NOT NULL default '0', `rewrite_host` varchar(128) NOT NULL default '', `rewrite_prefix` varchar(64) NOT NULL default '', `rewrite_suffix` varchar(64) NOT NULL default '', `description` varchar(255) default NULL, PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=23 ; Can someone help me to find this issue? Regards

14 years, 9 months

[Kamailio-Users] isup in invite

by Eric Hiller

I have an issue where my sip endpoint is sending ISUP information in the invite. IE: sip:+1xxxxxxxxxx;npdi=yes;cic=+1-0110@xxxx:5060 and when I run the enum query I am getting: 0(24410) enum_query(): uri user is not an E164 number This is most likely due to the fact that $rU=+17794294010;npdi=yes;cic=+1-0110 Does openser not read the user properly? Is there a way to correct this? I am running openser 1.2.2 notls Thanks for any help! -Eric _________________________________________________________________ Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. http://clk.atdmt.com/GBL/go/196390709/direct/01/

14 years, 9 months

[Kamailio-Users] new feature: remote user registration

by Daniel-Constantin Mierla

Hello, if you follow the sr-dev mailing list, you may have noticed some new features added in master branch (for the 3.1.0). I will send more details about each, now: remote user registration. The uac module can register in behalf of users to remote servers. The user details (credentials, local and remote username/domain) are loaded from database. The module sends registration at start-up and then refreshes just before expiration time. If the REGISTER is challenged for authentication, uac will re-send the REGISTER with proper credentials. A typical scenario is when users have accounts to many voip providers and they want to receive calls to those accounts via your sip server (inbound traffic). Of course, the user has to give details such as username/password to you. Other use case can be dynamic interconnection/peering. you can imagine a scalable solution where you have a traffic dispatcher and worker servers. When an worker becomes active, it registers to traffic dispatcher for receiving traffic... and examples can continue. Hope will help you in various cases! Readme at: http://sip-router.org/docbook/sip-router/branch/master/modules_k/uac/uac.ht… SQL to create the mysql table is in utils/kamctl/mysql/uac-create.sql Cheers, Daniel -- Daniel-Constantin Mierla * http://www.asipto.com/

14 years, 9 months

[Kamailio-Users] kamailio 1.4 cpc

by Asim Riaz

Hi List, Is it possible to add diffrent CPC(calling party catagory) for diffrent type of the number in the INVITE before sending out to an upstream SIP server? INVITE ----> Kamailio(add CPC) -------> SIP_Proxy_2 Thanks, Asim

14 years, 9 months

[Kamailio-Users] help me to find the problem

by shaon＠opennets.net

Hello I am new with kamailio. here is my problem X-lite -->TLS-->Kamailio(TLS+RegisterForwrd)-->UDP-->RegisterServer-->PSTN/VOIPCall I am able to forward my register request to the register server, and make call. Able to talk from both side. But when i hangup the call from termination side call never hangup from origination side. I attached my config file. I got following log on my kamailio.log file ############# Jan 31 15:54:45 ser /usr/local/sbin/kamailio[7579]: DBG:tm:t_lookup_request: start searching: hash=53225, isACK=0 Jan 31 15:54:45 ser /usr/local/sbin/kamailio[7579]: DBG:tm:t_lookup_request: proceeding to pre-RFC3261 transaction matching Jan 31 15:54:45 ser /usr/local/sbin/kamailio[7579]: DBG:tm:t_lookup_request: no transaction found Jan 31 15:54:45 ser /usr/local/sbin/kamailio[7579]: DBG:tm:run_reqin_callbacks: trans=0xb61945d0, callback type 1, id 0 entered Jan 31 15:54:45 ser /usr/local/sbin/kamailio[7579]: DBG:core:mk_proxy: doing DNS lookup... Jan 31 15:54:45 ser /usr/local/sbin/kamailio[7579]: DBG:core:get_send_socket: force_send_socket of different proto (1)! Jan 31 15:54:45 ser /usr/local/sbin/kamailio[7579]: WARNING:core:get_send_socket: protocol/port mismatch Jan 31 15:54:45 ser /usr/local/sbin/kamailio[7579]: DBG:tm:set_timer: relative timeout is 500000 Jan 31 15:54:45 ser /usr/local/sbin/kamailio[7579]: DBG:tm:insert_timer_unsafe: [4]: 0xb619471c (40400000) Jan 31 15:54:45 ser /usr/local/sbin/kamailio[7579]: DBG:tm:set_timer: relative timeout is 30 Jan 31 15:54:45 ser /usr/local/sbin/kamailio[7579]: DBG:tm:insert_timer_unsafe: [0]: 0xb6194738 (69) Jan 31 15:54:45 ser /usr/local/sbin/kamailio[7579]: DBG:tm:t_relay_to: new transaction fwd'ed Jan 31 15:54:45 ser /usr/local/sbin/kamailio[7579]: DBG:tm:t_unref: UNREF_UNSAFE: after is 0 Jan 31 15:54:45 ser /usr/local/sbin/kamailio[7579]: DBG:core:destroy_avp_list: destroying list (nil) Jan 31 15:54:45 ser /usr/local/sbin/kamailio[7579]: DBG:core:receive_msg: cleaning up Jan 31 15:54:45 ser /usr/local/sbin/kamailio[7581]: DBG:tm:utimer_routine: timer routine:4,tl=0xb619471c next=(nil), timeout=40400000 Jan 31 15:54:45 ser /usr/local/sbin/kamailio[7581]: DBG:tm:retransmission_handler: retransmission_handler : request resending (t=0xb61945d0, BYE sip:9 ... ) Jan 31 15:54:45 ser /usr/local/sbin/kamailio[7581]: DBG:tm:set_timer: relative timeout is 1000000 Jan 31 15:54:45 ser /usr/local/sbin/kamailio[7581]: DBG:tm:insert_timer_unsafe: [5]: 0xb619471c (41400000) Jan 31 15:54:45 ser /usr/local/sbin/kamailio[7581]: DBG:tm:retransmission_handler: retransmission_handler : done Jan 31 15:54:46 ser /usr/local/sbin/kamailio[7581]: DBG:tm:utimer_routine: timer routine:5,tl=0xb619471c next=(nil), timeout=41400000 Jan 31 15:54:46 ser /usr/local/sbin/kamailio[7581]: DBG:tm:retransmission_handler: retransmission_handler : request resending (t=0xb61945d0, BYE sip:9 ... ) Can anybody help me to solve the issue? Shaon

14 years, 9 months

[Kamailio-Users] ERROR:tm:w_t_reply failed to send a t_reply to a message for which no transaction-ate has been established

by AnthonyD

Dear List, I am running Kamailio (1.5.3-notls (i386/linux)) with the following modules: loadmodule "db_mysql.so" loadmodule "mi_fifo.so" loadmodule "sl.so" loadmodule "tm.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "usrloc.so" loadmodule "registrar.so" loadmodule "textops.so" loadmodule "uri_db.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "acc.so" loadmodule "avpops.so" loadmodule "lcr.so" loadmodule "dialog.so" loadmodule "auth.so" loadmodule "auth_db.so" loadmodule "domain.so" I get a lot of these errors in my logs: ERROR:tm:w_t_reply failed to send a t_reply to a message for which no transaction-ate has been established Can someone give me some info on these errors and how to trouble shoot the cause? Thanks Anthony Drozdek

14 years, 9 months

[Kamailio-Users] DTLS with kamailio

by mustafa samara

Hello I want to try DTLS with kamailio, I am working on minisip it support DTLS, but what a bout the kamailio side? is there any thing to do? also i would ask about IPSec support is there any thing to do on kamailio side, or it just on the kernel level? any help please? thanks -- Eng.Mustafa Al-Samara

14 years, 9 months

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