sr-users

sr-users@lists.kamailio.org

7 participants
37522 discussions

kamailio setup
by roman＠dmytriv.com 10 Mar '11

10 Mar '11

Hello there! I'm in the process of setting my first kamailio server and run into dead end. I was following your instructions very closely at http://www.kamailio.org/dokuwiki/doku.php/install:kamailio-3.1.x-from-git I'm using Centos 5.5 i386. Everything vent pretty much fine until step 7 were I had to create MySQL database. When I run /usr/local/kamailio-3.1/etc/kamailio/kamctlrc it gives me "Permission denied" error. I was able to access kamctlrc with a text editor and uncommented DBENGINE=MYSQL. Now when I run /usr/local/kamailio-3.1/sbin/kamdbctl create I have ERROR 2002. Please take a look at the attachment. Please help. Roman

4 3

Question about LCR
by Geoffrey Mina 10 Mar '11

10 Mar '11

Hello, I have a question about LCR which I have been unable to solve. I have 4 upstream carrier gateways owned by 2 carriers. Each carrier provides a primary and secondary gateway for load balancing purposes. On a 5XX error I am trying to send the same call to the other carrier. If both carriers reject the call with 5XX, I allow the response to go downstream to my asterisk server. The issue I am running into is that in a scenario where both my carriers respond with a 5XX, I end up presenting the same call to all 4 gateways. I would like to present the call to one gateway on each carrier and not try the same carriers second gateway for the same call. Here is what is happening now: ASTERISK --> INVITE --> KAMAILIO INVITE --> CARRIER A/GATEWAY 1 <-- 5XX Error INVITE --> CARRIER A/GATEWAY 2 <-- 5XX Error INVITE --> CARRIER B/GATEWAY 1 <-- 5XX Error INVITE --> CARRIER B/GATEWAY 2 <-- 5XX Error KAMAILIO --> 5XX Error --> ASTERISK OR any combination of the above... i.e. ASTERISK --> INVITE --> KAMAILIO INVITE --> CARRIER A/GATEWAY 1 <-- 5XX Error INVITE --> CARRIER B/GATEWAY 2 <-- 5XX Error INVITE --> CARRIER B/GATEWAY 1 <-- 5XX Error INVITE --> CARRIER A/GATEWAY 2 <-- 5XX Error KAMAILIO --> 5XX Error --> ASTERISK What I want to happen is: ASTERISK --> INVITE --> KAMAILIO INVITE --> CARRIER A/GATEWAY 1 or 2 <-- 5XX Error INVITE --> CARRIER B/GATEWAY 1 or 2 <-- 5XX Error KAMAILIO --> 5XX Error --> ASTERISK I tried dealing with the issue using some flags on the gateway, but i couldn't get the logic to work properly. Here is the path I was heading down, but my plan fell apart after some testing. CARRIER A has a gateway flag of "1" CARRIER B has a gateway flag of "2" failure_route[1]{ $var(gw_flag) = $avp(i:712); while(next_gw()){ if($var(gw_flag) != $avp(i:712)){ xlog("L_INFO","Found an LCR destination which is different than current, routing. ($ci)"); t_on_reply("1"); t_on_failure("1"); t_relay(); exit; }else{ xlog("L_INFO","The next destination in LCR has the same AVP flag, skipping. ($ci)"); } } # let the reply go upstram - it is the default action xlog("L_ERR", "No Next Gateway - M=$rm RURI=$ru F=$fu T=$tu IP=$si ID=$ci\n"); exit; } Any help would be greatly appreciated. Thanks, Geoff

4 6

kamailio setup
by roman＠dmytriv.com 09 Mar '11

09 Mar '11

1 0

Does Kamailio support RFC5626 as Edge Proxy(or outbound proxy)
by Derrick Ding 09 Mar '11

09 Mar '11

Dear All, I wonder if Kamailio supports RFC5626 as edge proxy or outbound proxy. That is, Edge Proxy adds a Path header with a flow token and includes the "ob" parameter when Processing Register Requests. Eg: Path: <sip:VskztcQ/S8p4WPbOnHbuyh5iJvJIW3ib@ep1.example.com;lr;ob> If does, how can I config it in kamailio.cfg. At present, Kamailio can only forward register msg to sip server and reply 200 OK to SIP UA with "require: outbound" when register accepted. No "Path" and "ob" added in the msg forwarded to SIP server. You answer is appreciated!! Sincerely, Derrick

3 3

#!define and #!subst problem
by Klaus Darilion 09 Mar '11

09 Mar '11

Hi! I tried #!subst "/IPADDRESS_VIRTUAL/83.136.32.161/" listen=udp:IPADDRESS_VIRTUAL:5060 and #!define IPADDRESS_VIRTUAL 83.136.32.161 listen=udp:IPADDRESS_VIRTUAL:5060 Both do not work - am I doing something wrong or is this a known limitation with "listen" statements? Thanks Klaus

2 2

dispatcher confusion
by Klaus Darilion 07 Mar '11

07 Mar '11

Hi! Every time I use the dispatcher(k) module I am confused again. Sometimes it seems that "probing" is a dedicated state, sometimes it seems that "probing" is done also in "active" state, but never in "inactive" state. IMO "probing" should only be a flag which indicates if OPTIONS should sent or not. If probing is successful, then the state should be "active". If probing is unsuccessful, then the state should be "inactive". Current behavior is very strange (ds_probing_mode(0)): --> startup state: A --> no probing kamctl fifo ds_set_state i 1 sip:.... --> state: I --> no probing kamctl fifo ds_set_state a 1 sip:.... --> state: A --> no probing calling 3 times ds_mark_dst("p") --> state: P --> probing (and dst is still loaded as last value into the dst_avp, why?) kamctl fifo ds_set_state i 1 sip:.... --> state: I --> still probing kamctl fifo ds_set_state a 1 sip:.... --> state: P (???) --> probing Thus, "ds_set_state a ..." does not set active, but probing if it was probing before. Strange. And as "inactive" does not stop probing when dst was in probing mode, the destination becomes automatically "active" if the probing succeeds. And why is a destination in probing mode loaded into the dst_avp? Very weird. Is there a reason for this behavior? Thanks Klaus

3 4

Kamailio 3.0.4: dispatcher module request
by Klaus Feichtinger 07 Mar '11

07 Mar '11

Hello list, I have a question to the dispatcher module in Kamailio version 3.0.4. In my integration I use this module for distributing calls to a set of gateways (with the round robin algorithm). Sometimes a gateway does not react or send back a negative response. In that case I use the function 'ds_mark_dst("p")' in the failure_route and mark the current destination with the flag 'probing'. I have set the threshhold value for probing mode to '10'. This means that a gateway is effectively set to probing mode only when it was marked with the flag 'probing' for 10 times. However, sometimes a gateway is sending back a negative response for e.g. 5 times and is afterwards working fine - without any problems. A few hours later (e.g.) it is sending a negative reply again for one time. This means: the counter for the probing_flags is increasing every time when the function ds_mark_dst("p") is executed (in case that the process was not restarted in the meantime!). So the problem is, that the counter is reaching the threshhold value at any time and at that moment the gateway is set to probing mode. Even if the gateway has sent a negative reply for only one time (at that moment) - but according the history the proging_flag was set several times. What I miss in this module is a function to _reset_ that flag counter from a REPLY_ROUTE. Note: I have to reset the counter, because the gateway does not yet SIP OPTIONS requests and therefore it is set to 'probing' all time until it is manually set back to active via MI command or after a process restart. According the README file (and practical experience) the function ds_mark_dst() is executable only within the failure_route. However, when I want to set the flag ("a") for the current destination I will do it within a reply_route, but not in the failure_route (because I have received a positive response and not a negative one). From my point of view it does not make sense setting the 'active' flag for a destination from within a FAILURE route. Does anybody have an idea, how the 'flag-counter' could be reset (from within the script)? I do not want to use a MI command..... configuration excerpt: [...] modparam("dispatcher", "db_url", "mysql://openser:openserrw@localhost/openser") modparam("dispatcher", "table_name", "dispatcher") modparam("dispatcher", "dst_avp", "$avp(AVP_DST)") modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)") modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)") modparam("dispatcher", "ds_ping_from", "sip:proxy@192.168.37.87") modparam("dispatcher", "ds_probing_mode", 0) modparam("dispatcher", "ds_probing_threshhold", 10) modparam("dispatcher", "ds_ping_interval", 30) modparam("dispatcher", "flags", 2) modparam("dispatcher", "force_dst", 1) [...] if (!ds_select_dst("1", "4")) { sl_send_reply("404", "No destination (disp)"); exit; } t_on_failure("failureroute"); t_on_reply("replyroute"); [...] failure_route[failureroute] { [...] if (t_check_status("[45][08]0") || (t_branch_timeout() && !t_branch_replied())) { ds_mark_dst("p"); if (!ds_next_dst()) { t_reply("404", "No destination (disp)"); exit; } t_on_failure("failureroute"); t_on_reply("replyroute"); } [...] } onreply_route [replyroute] { if (t_check_status("180|200") { # nice to have...... # ds_mark_dst("a"); } } Thanks in advance! regards, Klaus

2 4

Siremis Installation - Hangs at Database Configuration Page
by Tim Nelson 07 Mar '11

07 Mar '11

Greetings- I'm attempting an installation of Siremis on a CentOS 5.5 64-bit system running Kamailio 3.1.0. Following the instructions on the wiki [1], I find that I cannot pass step 3 for the database configuration. I've triple checked all of my details are correct and verified the permissions are set appropriately on the Siremis source dir. Also, I've successfully run 'make apache-config' and 'make prepare'. After clicking 'next', I simply get the 'Loading... please wait awhile' graphic. On three different fresh installs, I've waited for 3 hours each. By now, I have to assume it shouldn't be taking this long and there is an error somewhere. The Apache logs don't indicate anything of interest other than a missing favicon. Do you have any ideas? Thank you! --Tim [1] http://kb.asipto.com/siremis:install20:main

1 0

Limit call duration
by Hans Goossens 07 Mar '11

07 Mar '11

Hi, I'm wondering if there is a easy way to limit the call duration in Kamailio ? I would like to automaticaly end the call when the max. duration (for example 12 hours) is reached. In the feature overview of Kamailio 1.5 I found: "option to send BYE when dialog expires" but i'm can't figure out how to get this working (if it's still implemented at all in the current version). Thanks in advance, Kind regards Hans

2 2

about syn_branch
by Juha Heinanen 07 Mar '11

07 Mar '11

we noticed that if sr 3.1 config does not contain syn_branch=0 then acks to 200 oks that are t_relayed by sr, contain branch=0 param in topmost via. in kamailio 1.5, via branch param has proper value even when tm param syn_branch is not set. a couple of questions: 1) according to core cookbook, syn_branch core param only affects stateless forwarding. in my config, all acks are t_relayed, i.e., syn_branch param should not have any effect, but is does. how is that possible? is there a bug in core cookbook? 2) should t_relaying of acks to 200 oks use proper (i.e.. non 0) via branch param even when syn_branch is not set to any value in config? if not why? if yes, will branch=0 be used only when ack to 200 ok does not match any invite transaction? -- juha

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