sr-users

sr-users@lists.kamailio.org

56 participants
37562 discussions

Fwd: configuration
by neili ma 12 Sep '11

12 Sep '11

Hello sr-users, I'm new using kamailio open source, and I would like to ask for help. My version is 3.1.4 and I am trying to configure 3 servers, one with proxy, one with registrar and one with location server. My problem is when I try to send a register message it returns an error "401 Unauthorized", I know the error is in the fuction www_authorize("10.254.239.7", "subscriber") but I don't know how to solve it, for me it seems correct the parameters. Below I have attatched the proxy and registrar relevant route code for my problem, and the IPs for proxy an registrar are: 10.254.239.7-----------10.254.239.8 If someone can help me, I will be gratefull. Thanks in advance. ####REGISTRAR CODE route{ # initial sanity checks -- too long messages if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); exit; }; if (!uri==myself) { sl_send_reply("400", "Bad destination, only register messages de$ exit; }; # the only valid message for the registrar is the register message # other messages are answered with an error message if (uri==myself) { if (method=="REGISTER") { sl_send_reply("100", "Trying"); if (!www_authorize("10.254.239.7", "subscriber")) { www_challenge("10.254.239.7", "1"); exit; }; if (!check_to()) { sl_send_reply("401", "Unauthorized"); exit; }; consume_credentials(); if(!save("location")) { sl_reply_error(); }; exit; } else { sl_send_reply("403", "Forbidden"); exit; }; }; } #########PROXY CODE if (method=="ACK") { route(1); exit; } if (method=="INVITE") { route(3); exit; } else if (method=="REGISTER") { route(2); exit; }; lookup("aliases"); if (!uri==myself) { route(1); }; route[2] { #rewrinting the host allows the registrar to know that the message is de$ rewritehost("10.254.239.8"); if(!t_relay()) { sl_reply_error(); }; exit; }

2 1

Re: [SR-Users] Kamailio 3.0.4 is crashed
by Daniel-Constantin Mierla 12 Sep '11

12 Sep '11

Hello, try to keep the mailing list cc-ed -- others may be able to help you faster or this discussion will be helpful for different people. The username_spec and password_spec were removed indeed, the first was useless since the username was taken from auth header and the second became parameter to pv_www_authenticate, see: http://kamailio.org/docs/modules/3.1.x/modules/auth.html#pv_www_authenticate You simply have to use something like: if (!pv_www_authenticate("$td", "$var(password)", "0")) { www_challenge("$td", "0"); exit; } Cheers, Daniel On 9/10/11 12:51 PM, Khoa Phuong Viet Ngo wrote: > Hi Daniel, > > Thanks Daniel for your answer. > > It's very helpful for me :). > > Actually i tried with using kamailio 3.1.4 (lastest kamailio) but i > got the problem with auth module and parameter with auth module. > Because some parameters at auth module have changed. > http://kamailio.org/docs/modules/stable/modules/auth.html [3.1.4] > > But in 3.0.4 kamailio, i am using auth module with these parameter and > it had error with new kamailio (3.1.4) . :( > > kamailio.cfg > > ######################################################## > loadmodule auth.so > > # ----- auth params ----- > modparam("auth", "username_spec", "$var(username)") > modparam("auth", "password_spec", "$var(password)") > modparam("auth", "calculate_ha1", 1) > > route[AUTH] { > $var(utype) = 0; > #!ifdef WITH_AUTH > if (is_method("REGISTER")) > { > if(is_present_hf("Authorization")) > { > # authenticate the REGISTER requests (uncomment to enable > auth) > if(!route(GETPASSWD)) > { > www_challenge("", "0"); > exit; > } > if(!pv_www_authorize("")) > { > www_challenge(""/*realm*/,"0"/*qop*/); > exit; > } > } else { > www_challenge("", "0"); > exit; > } > } else { > $var(srcgrp) = allow_source_address_group(); > if ($var(srcgrp) > 0) { > # src ip allowed > $var(utype) = 1; > if($var(srcgrp)!=100) > { > $rd = $Ri; > $fs = "udp:" + $Ri + ":5062"; > } > return 1; > } > # authenticate if from local subscriber (uncomment to enable auth) > if (from_uri==myself) > { > if(is_present_hf("Proxy-Authorization")) > { > # authenticate the non-REGISTER requests (uncomment to > enable auth) > if(!route(GETPASSWD)) > { > proxy_challenge("", "0"); > exit; > } > if(!pv_proxy_authorize("")) > { > proxy_challenge(""/*realm*/,"0"/*qop*/); > exit; > } > } else { > proxy_challenge("", "0"); > exit; > } > $var(utype) = 2; > consume_credentials(); > # caller authenticated > } > } > #!endif > return; > } > > ##################################################### > > Error logs: > > Sep 6 19:37:01 CorePBX kamailio: ERROR: <core> [modparam.c:150]: > set_mod_param_regex: parameter <username_spec> not found in module <auth> > Sep 6 19:37:01 CorePBX kamailio: : <core> [cfg.y:3419]: parse error > in config file /usr/local/etc/kamailio/kamailio.cfg, line 260, column > 51: Can't set module parameter > Sep 6 19:37:01 CorePBX kamailio: ERROR: <core> [modparam.c:150]: > set_mod_param_regex: parameter <password_spec> not found in module <auth> > Sep 6 19:37:01 CorePBX kamailio: : <core> [cfg.y:3419]: parse error > in config file /usr/local/etc/kamailio/kamailio.cfg, line 261, column > 51: Can't set module parameter > Sep 6 19:37:01 CorePBX kamailio: ERROR: <core> [modparam.c:150]: > set_mod_param_regex: parameter <calculate_ha1> not found in module <auth> > Sep 6 19:37:01 CorePBX kamailio: : <core> [cfg.y:3419]: parse error > in config file /usr/local/etc/kamailio/kamailio.cfg, line 262, column > 36: Can't set module parameter > Sep 6 19:37:01 CorePBX kamailio: : <core> [cfg.y:3419]: parse error > in config file /usr/local/etc/kamailio/kamailio.cfg, line 562, column > 27: unknown command, missing loadmodule? > Sep 6 19:37:01 CorePBX kamailio: : <core> [cfg.y:3419]: parse error > in config file /usr/local/etc/kamailio/kamailio.cfg, line 594, column > 30: unknown command, missing loadmodule? > Sep 6 19:37:39 CorePBX kamailio: ERROR: <core> [modparam.c:150]: > set_mod_param_regex: parameter <username_spec> not found in module <auth> > Sep 6 19:37:39 CorePBX kamailio: : <core> [cfg.y:3419]: parse error > in config file /usr/local/etc/kamailio/kamailio.cfg, line 260, column > 51: Can't set module parameter > Sep 6 19:37:39 CorePBX kamailio: ERROR: <core> [modparam.c:150]: > set_mod_param_regex: parameter <password_spec> not found in module <auth> > Sep 6 19:37:39 CorePBX kamailio: : <core> [cfg.y:3419]: parse error > in config file /usr/local/etc/kamailio/kamailio.cfg, line 261, column > 51: Can't set module parameter > Sep 6 19:37:39 CorePBX kamailio: ERROR: <core> [modparam.c:150]: > set_mod_param_regex: parameter <calculate_ha1> not found in module <auth> > > ######################################################## > > I appreciate all your help on this case. > > Thanks Daniel, > KhoaNVP > > > > > On Sat, Sep 10, 2011 at 1:58 PM, Daniel-Constantin Mierla > <miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote: > > Hello, > > it seems like a buffer overflow happened previously, since the > crash is in malloc. Do you get any error messages is syslog? Can > you recompile with QM_DBG_MALLOC like explained in the next link > and try again watching the syslog messages? > http://www.kamailio.org/dokuwiki/doku.php/troubleshooting:memory > > On another hand, 3.0.4 is quite old, why are not using 3.1.4, it > is far more updated than 3.0 series -- we are just to release > first in 3.2 series. Upgrading from 3.0 to 3.1 is rather trivial. > > Cheers, > Daniel > > > On 9/9/11 8:38 PM, KhoaNVP wrote: > > Hi everyone, > > I hope you can help me with this issues. > I'm working with kamailio 3.0.4 and when i implement the call > via kamailio > after 1-->3 mins , kamailio is crashed. > > It's my debug from core log. > > Core was generated by `kamailio -E -ddd'. > Program terminated with signal 11, Segmentation fault. > #0 fm_malloc (qm=0x88c860, size=<value optimized out>) at > mem/f_malloc.c:382 > 382 *f=frag->u.nxt_free; > (gdb) qt > Undefined command: "qt". Try "help". > (gdb) bt > #0 fm_malloc (qm=0x88c860, size=<value optimized out>) at > mem/f_malloc.c:382 > #1 0x000000000041fd27 in dup_lump_list_r (l=0x9275f8, > dir=LD_AFTER, > error=0x7fff23bd661c) at data_lump.c:453 > #2 0x000000000041ffa9 in dup_lump_list_r (l=0x927640, > dir=LD_AFTER, > error=0x7fff23bd666c) at data_lump.c:476 > #3 0x000000000041ff6d in dup_lump_list_r (l=0x926db0, > dir=<value optimized > out>, error=0x7fff23bd66b4) at data_lump.c:465 > #4 0x0000000000420058 in dup_lump_list (l=0x88c860) at > data_lump.c:508 > #5 0x00002b8b2efb858d in prepare_new_uac (t=0x2b8b3218ffa8, > i_req=0x926ef0, > branch=0, uri=0x927150, path=0x9274d0, next_hop=<value > optimized out>, > fsocket=0x0, snd_flags=0 '\000', fproto=0, flags=0) at > t_fwd.c:242 > #6 0x00002b8b2efb94c7 in add_uac (t=0x2b8b3218ffa8, > request=0x926ef0, > uri=0x927150, next_hop=0x7, path=0x9274d0, proxy=0x0, fsocket=0x0, > snd_flags=0 '\000', proto=0, flags=0) at t_fwd.c:679 > #7 0x00002b8b2efbce7a in t_forward_nonack (t=0x2b8b3218ffa8, > p_msg=0x926ef0, proxy=0x0, proto=0) at t_fwd.c:1340 > #8 0x00002b8b2efb4996 in t_relay_to (p_msg=0x926ef0, > proxy=0x0, proto=0, > replicate=0) at t_funcs.c:358 > #9 0x0000000000413489 in do_action (h=0x7fff23bd71e0, a=0x8be788, > msg=0x926ef0) at action.c:860 > #10 0x0000000000415e03 in run_actions (h=0x7fff23bd71e0, > a=0x8be788, > msg=0x926ef0) at action.c:1315 > #11 0x00000000004161e7 in run_actions_safe (h=0x7fff23bd8bb0, > a=0x38, > msg=0x88ca08) at action.c:1370 > #12 0x000000000049696b in rval_get_int (h=0x7fff23bd8bb0, > msg=0x88ca08, > i=0x7fff23bd75dc, rv=0x7, cache=0x7) at rvalue.c:897 > #13 0x000000000049b7fc in rval_expr_eval_int (h=0x7fff23bd8bb0, > msg=0x926ef0, res=0x7fff23bd75dc, rve=0x8be878) at rvalue.c:1841 > #14 0x000000000049b8ad in rval_expr_eval_int (h=0x7fff23bd8bb0, > msg=0x926ef0, res=0x7fff23bd79d8, rve=0x8bef48) at rvalue.c:1848 > #15 0x0000000000411d49 in do_action (h=0x7fff23bd8bb0, a=0x8bf798, > msg=0x926ef0) at action.c:834 > #16 0x0000000000415e03 in run_actions (h=0x7fff23bd8bb0, > a=0x8be608, > msg=0x926ef0) at action.c:1315 > #17 0x0000000000413084 in do_action (h=0x7fff23bd8bb0, a=0x8f6060, > msg=0x926ef0) at action.c:479 > #18 0x0000000000415e03 in run_actions (h=0x7fff23bd8bb0, > a=0x8f6060, > msg=0x926ef0) at action.c:1315 > #19 0x0000000000411dab in do_action (h=0x7fff23bd8bb0, a=0x8f62d0, > msg=0x926ef0) at action.c:853 > #20 0x0000000000415e03 in run_actions (h=0x7fff23bd8bb0, > a=0x8f62d0, > msg=0x926ef0) at action.c:1315 > #21 0x0000000000413084 in do_action (h=0x7fff23bd8bb0, a=0x8bd698, > msg=0x926ef0) at action.c:479 > #22 0x0000000000415e03 in run_actions (h=0x7fff23bd8bb0, > a=0x8bd398, > msg=0x926ef0) at action.c:1315 > #23 0x0000000000411dab in do_action (h=0x7fff23bd8bb0, a=0x8bd788, > msg=0x926ef0) at action.c:853 > #24 0x0000000000415e03 in run_actions (h=0x7fff23bd8bb0, > a=0x8a1340, > msg=0x926ef0) at action.c:1315 > #25 0x0000000000416174 in run_top_route (a=0x8a1340, > msg=0x926ef0, c=<value > optimized out>) at action.c:1391 > #26 0x000000000048009c in receive_msg (buf=0x57e779 "DEBUG", > len=<value > optimized out>, rcv_info=0x7fff23bd8e20) at receive.c:196 > #27 0x000000000050698b in udp_rcv_loop () at udp_server.c:520 > #28 0x0000000000455e2f in main_loop () at main.c:1447 > #29 0x0000000000456f32 in main (argc=<value optimized out>, > argv=0x7fff23bd90e8) at main.c:2251 > (gdb) > > > Thanks with all the help, > Khoa > > > -- > Daniel-Constantin Mierla -- http://www.asipto.com > Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat > http://linkedin.com/in/miconda -- http://twitter.com/miconda > > -- Daniel-Constantin Mierla -- http://www.asipto.com Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat http://linkedin.com/in/miconda -- http://twitter.com/miconda

1 0

Kamailio 3.0.4 is crashed
by KhoaNVP 10 Sep '11

10 Sep '11

Hi everyone, I hope you can help me with this issues. I'm working with kamailio 3.0.4 and when i implement the call via kamailio after 1-->3 mins , kamailio is crashed. It's my debug from core log. Core was generated by `kamailio -E -ddd'. Program terminated with signal 11, Segmentation fault. #0 fm_malloc (qm=0x88c860, size=<value optimized out>) at mem/f_malloc.c:382 382 *f=frag->u.nxt_free; (gdb) qt Undefined command: "qt". Try "help". (gdb) bt #0 fm_malloc (qm=0x88c860, size=<value optimized out>) at mem/f_malloc.c:382 #1 0x000000000041fd27 in dup_lump_list_r (l=0x9275f8, dir=LD_AFTER, error=0x7fff23bd661c) at data_lump.c:453 #2 0x000000000041ffa9 in dup_lump_list_r (l=0x927640, dir=LD_AFTER, error=0x7fff23bd666c) at data_lump.c:476 #3 0x000000000041ff6d in dup_lump_list_r (l=0x926db0, dir=<value optimized out>, error=0x7fff23bd66b4) at data_lump.c:465 #4 0x0000000000420058 in dup_lump_list (l=0x88c860) at data_lump.c:508 #5 0x00002b8b2efb858d in prepare_new_uac (t=0x2b8b3218ffa8, i_req=0x926ef0, branch=0, uri=0x927150, path=0x9274d0, next_hop=<value optimized out>, fsocket=0x0, snd_flags=0 '\000', fproto=0, flags=0) at t_fwd.c:242 #6 0x00002b8b2efb94c7 in add_uac (t=0x2b8b3218ffa8, request=0x926ef0, uri=0x927150, next_hop=0x7, path=0x9274d0, proxy=0x0, fsocket=0x0, snd_flags=0 '\000', proto=0, flags=0) at t_fwd.c:679 #7 0x00002b8b2efbce7a in t_forward_nonack (t=0x2b8b3218ffa8, p_msg=0x926ef0, proxy=0x0, proto=0) at t_fwd.c:1340 #8 0x00002b8b2efb4996 in t_relay_to (p_msg=0x926ef0, proxy=0x0, proto=0, replicate=0) at t_funcs.c:358 #9 0x0000000000413489 in do_action (h=0x7fff23bd71e0, a=0x8be788, msg=0x926ef0) at action.c:860 #10 0x0000000000415e03 in run_actions (h=0x7fff23bd71e0, a=0x8be788, msg=0x926ef0) at action.c:1315 #11 0x00000000004161e7 in run_actions_safe (h=0x7fff23bd8bb0, a=0x38, msg=0x88ca08) at action.c:1370 #12 0x000000000049696b in rval_get_int (h=0x7fff23bd8bb0, msg=0x88ca08, i=0x7fff23bd75dc, rv=0x7, cache=0x7) at rvalue.c:897 #13 0x000000000049b7fc in rval_expr_eval_int (h=0x7fff23bd8bb0, msg=0x926ef0, res=0x7fff23bd75dc, rve=0x8be878) at rvalue.c:1841 #14 0x000000000049b8ad in rval_expr_eval_int (h=0x7fff23bd8bb0, msg=0x926ef0, res=0x7fff23bd79d8, rve=0x8bef48) at rvalue.c:1848 #15 0x0000000000411d49 in do_action (h=0x7fff23bd8bb0, a=0x8bf798, msg=0x926ef0) at action.c:834 #16 0x0000000000415e03 in run_actions (h=0x7fff23bd8bb0, a=0x8be608, msg=0x926ef0) at action.c:1315 #17 0x0000000000413084 in do_action (h=0x7fff23bd8bb0, a=0x8f6060, msg=0x926ef0) at action.c:479 #18 0x0000000000415e03 in run_actions (h=0x7fff23bd8bb0, a=0x8f6060, msg=0x926ef0) at action.c:1315 #19 0x0000000000411dab in do_action (h=0x7fff23bd8bb0, a=0x8f62d0, msg=0x926ef0) at action.c:853 #20 0x0000000000415e03 in run_actions (h=0x7fff23bd8bb0, a=0x8f62d0, msg=0x926ef0) at action.c:1315 #21 0x0000000000413084 in do_action (h=0x7fff23bd8bb0, a=0x8bd698, msg=0x926ef0) at action.c:479 #22 0x0000000000415e03 in run_actions (h=0x7fff23bd8bb0, a=0x8bd398, msg=0x926ef0) at action.c:1315 #23 0x0000000000411dab in do_action (h=0x7fff23bd8bb0, a=0x8bd788, msg=0x926ef0) at action.c:853 #24 0x0000000000415e03 in run_actions (h=0x7fff23bd8bb0, a=0x8a1340, msg=0x926ef0) at action.c:1315 #25 0x0000000000416174 in run_top_route (a=0x8a1340, msg=0x926ef0, c=<value optimized out>) at action.c:1391 #26 0x000000000048009c in receive_msg (buf=0x57e779 "DEBUG", len=<value optimized out>, rcv_info=0x7fff23bd8e20) at receive.c:196 #27 0x000000000050698b in udp_rcv_loop () at udp_server.c:520 #28 0x0000000000455e2f in main_loop () at main.c:1447 #29 0x0000000000456f32 in main (argc=<value optimized out>, argv=0x7fff23bd90e8) at main.c:2251 (gdb) Thanks with all the help, Khoa -- View this message in context: http://old.nabble.com/Kamailio-3.0.4-is-crashed-tp32433892p32433892.html Sent from the OpenSER Users Mailing List mailing list archive at Nabble.com.

2 1

Error reading AVP
by Carlos Ruiz Diaz 09 Sep '11

09 Sep '11

Hello. I'm currently developing an OpenSER module which does some business logic for the company I work for. For compatibility reasons we are working with openser-1.2.2-tls and we haven't been able to upgrade to newer version yet. In one block of the code I have to read an avp which is written inside the openser.cfg script using: OPENSER: avp_copy("sip:123@123.123.123:5060", "$avp(s:selectedroute)/g"); C CODE: if (is_response && is_invite_seq) { struct usr_avp* destavp = NULL; int_str destval; const str selected_route = { "selectedroute", 13 }; int attempts = 1, max_attempts = 3; for ( destavp = search_first_avp(AVP_NAME_STR | AVP_VAL_STR, (int_str) selected_route, NULL, 0); destavp != NULL; destavp = search_next_avp(destavp, NULL) ) { get_avp_val(destavp, &destval); } } The problem is that "selectedroute" avp cannot be found so I can't read its value. This happens sporadically and most of the time the code works just fine. I also checked for the list of available AVPs using get_avp_list() but it reports an empty list. Is there another way to read AVPs or is there something I'm missing which is causing this problem? Any help will be appreciated. Thanks in advance! Carlos.

2 2

10 Years SER Conference - Presentations
by Daniel-Constantin Mierla 08 Sep '11

08 Sep '11

Hello, the presentations from 10 Years SER Conference I received so far were uploaded at: * http://www.kamailio.org/events/2011-10yearsSER/ Expect the rest during the next days. The recording of the talk about Gemeinschaft 4 by Stefan Wintermeyer is available on youtube: * http://www.youtube.com/watch?v=mbGn5N_y4rw Cheers, Daniel -- Daniel-Constantin Mierla -- http://www.asipto.com Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat http://linkedin.com/in/miconda -- http://twitter.com/miconda

1 0

Re: [SR-Users] Kamailio + rtpproxy talking to multiple carrier gateways - Solution
by Sarat C. Vemuri 07 Sep '11

07 Sep '11

I think I have this working. For anyone else trying to do similar thing (or placing Kamailio behind FW/NAT), here is my cookbook. We are trying to setup the following: [UAS] <------> (PubIP)[FireWall/One-to-OneNAT]<-------->(PrivIP)[Kamailio/RTPProxy](PrivIP)<---------->(PrivIP2)[UAC] UAC/UAS cannot reach each other directly. For simplicity I am running RTPProxy on same machines as Kamailio. But this can be changed. Versions/Patches/fixes you need if you are running 3.1.2 : (Trunk/3.2 has these): a. Fixed forward.c for mhome to work properly (included in 3.1.4). b. rr module from trunk to be able to use 2 strings for record_route_preset c. Patched rtpproxy module to actually use the forced ip supplied to force_rtp_proxy. Patch at the end of this message d. rtpproxy version 1.2.1 What to do: 1. Setup FW/NAT rules to map public IP to PrivateIP and allow communications to/from UAS 2. Setup RTPProxy in "bridged" mode (e.g -F -l 10.10.5.90/10.10.5.90 -s udp:10.10.5.90:9005) listening on PrivateIP. 3. Setup the config file to: a. Setup modparams to make the above rtpproxy available. Use set_rtp_proxy_set if you have more than one instance. b. Do the following where you are processing Outbound *initial* invite (i.e. check totag) (Call from UAC to UAS) set_advertised_address("YourPublicIP "); if(!has_totag()) { record_route_preset("YourPublicIP:5060;r2=on;nat=yes","YourPrivateIp:5060;r2=on;nat=yes"); } force_rtp_proxy("ocfaei"," YourPublicIP "); c. Do the following where you are processing Inbound invite (Call from UAS to UAC) if(!has_totag()) { record_route_preset("YourPrivateIP:5060;r2=on;nat=yes", "YourPublicIp:5060;r2=on;nat=yes"); } force_rtp_proxy("ocfaei"); d. Do the following where you are processing replies (180/183/2XX) For Inbound Calls force_rtp_proxy("ocfa","YourPublicIP"); For Outbound Calls force_rtp_proxy("ocfa"); e. Unforce RTPProxy on BYE or Failures. Do not use record_route in the above scenario. If you have it now, remove it or make sure it doesn't get called for this specific case. Explanation: In #b, you are fixing the Via headers to use public IP, setting Record-Route headers so that ACK/RE-INVITE can find way back and are force fixing SDP with public IP for outbound calls. In #c, You are doing same thing except no need to fix Via and the route set is reversed. No need to force fix SDP either since it is figured out automatically. In #d, You are force fixing the SDP to use the public IP for inbound or usual for outbound so that the audio stream from UAS can be relayed. The r2=on parameter is required (as well as enabling double rr, which is default) so that the proxy can deal with the route sets properly Hope the above helps others. SV. Rtpproxy Path 2226,2233c2226 < LM_DBG("Str2 is %s\n", str2); < if(str2) { < newip.s = str2; < LM_DBG("NewIp is %s\n", newip.s); < } < else { < newip.s = (argc < 2) ? str2 : argv[1]; < } --- > newip.s = (argc < 2) ? str2 : argv[1];

1 0

Re: [SR-Users] Kamailio + rtpproxy talking to multiple carrier gateways
by Sarat C. Vemuri 07 Sep '11

07 Sep '11

Ovidiu, Thanks for your time. The "fixes" I pulled in is the latest rr module only. I didn't see anything in that diff to make this work. Could you elaborate a little? However, I was able to get "Outbound" working properly by adding ";r2=on" to the record_route_preset IPs. In going through the source code, I noticed that this is what regular record_route uses to enable double rr and it would automatically take both headers out if it sees that. That seems to have worked. Any pitfals with this? I am still working on "Inbound". For some reason my carrier GW keeps resending invites even after receiving ACK. I need to see if it is an issue with the carrier. Thanks SV. -----Original Message----- From: Ovidiu Sas [mailto:osas@voipembedded.com] Sent: Tuesday, September 06, 2011 9:50 AM To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List Subject: Re: [SR-Users] Kamailio + rtpproxy talking to multiple carrier gateways It seems that something is miss configured on your server. The fixes that I made in the trunk (and you pulled in your local 3.1 repo) were designed to handle the scenario that you are trying to implement. The ACK should be handled properly and routed to the upstream carrier (following the same path as the initial INVITE). Regards, Ovidiu Sas On Mon, Sep 5, 2011 at 5:07 PM, Sarat C. Vemuri <sarat.vemuri(a)fthco.com> wrote: > Again, I apologize for this clumsy way of replying. > > Ovidiu, > > Thanks for the pointer on set_advertised_address. I had to patch rtpproxy module (and rr module for the two parameters to request_route_preset) since I am running 3.1. > > However, I still have a problem with ACKs after following what you suggested. > > INVITE from Internal to Carrier routes properly (two Request-Route headers, one internal IP and other public IP). On 200 OK, the carrier GW properly copies the route set in to Route header. Now the route contains two entries, the public IP and the private IP of Kamailio. The Internal UAC then sends the ACK back to Kamailio. Everything is fine till this point. Now, Kamailio removes the top entry, which is the private IP and then promptly sends the ACK to the public IP of itself!. Of course, that doesn't go anywhere. > > How do I remove the "public IP" entry from the route set before forwarding the reply to Internal UAC? Is there another way to deal with this? I've tried to set an alias= core parameter with the public IP, but doesn't seem to have any effect. The public IP is not reachable from internal network. > > Thanks for your help > > SV. > ------------------------------ > > Message: 3 > Date: Sat, 3 Sep 2011 16:44:22 -0700 > From: Ovidiu Sas <osas(a)voipembedded.com> > Subject: Re: [SR-Users] Kamailio + rtpproxy talking to multiple > carrier gateways - some via Firewall/NAT > To: "SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - > Users Mailing List" <sr-users(a)lists.sip-router.org> > Message-ID: > > <CAND0Lkt_dpcTm2WKMywMhX6rdsX1ia0r=LYrzB1WfX3oN32Wrg(a)mail.gmail.com> > Content-Type: text/plain; charset=windows-1252 > > It is feasable to what you want: kamailio behind NAT proxying traffic > from/to public internet to/from private network. > You will need to properly craft the INVITE and use proper record route headers. > Use set_advertised_address when needed: > http://kamailio.org/dokuwiki/doku.php/core-cookbook:3.1.x#set_advertis > ed_address Also, use record_route_preset (note that there are two > parameters): > http://kamailio.org/docs/modules/devel/modules_k/rr.html#id2547566 > > That should do it. You don't need any patches for rtpproxy. > Just use force_rtpp_proxy (and force the IP address): > http://kamailio.org/docs/modules/devel/modules/rtpproxy.html#id2546034 > > > Note: Make sure that you understand how in-dialog requests are routed > by a proxy in order to know how to properly handle the initial INVITE. > > > Regards, > Ovidiu Sas > > On Sat, Sep 3, 2011 at 2:53 PM, Sarat C. Vemuri <sarat.vemuri(a)fthco.com> wrote: >> We are trying to configure Kamailio ?(3.1.x) as a ?boarder proxy? >> where it acts as the front for various carrier gateways so that >> internal UACs and UASs are unaware of the carrier gateways. >> >> >> >> Let me try to present a clear picture of our setup. >> >> 1.?????? Kamailio has several NICs (physical or vlan).? Each on a >> different subnet. One subnet is internal/has routes for internal.? >> Other subnets are private connections to carriers or a ?route to public Internet. >> >> 2.?????? All of these subnets are non-routable from Internet. In >> addition , the carrier private connections are not routable internally. >> >> 3.?????? Connection to public internet is via a FW/NAT (one-to-one >> NAT), which maps to one of the interfaces. >> >> 4.?????? All internal? UAC/UAS connect on the internal subnet. >> >> 5.?????? We are using RTPProxy? (at least one instance per carrier) >> to relay media between internal and carrier subnets >> >> >> >> We are able to make this setup up work great except for one >> scenario.? One of the carriers is only reachable via public >> Internet.? Due to security requirements, our Kamailio cannot have a >> public IP address and must use FW/NAT. I guess this scenario is >> ??Proxy behind NAT? and not really encouraged. But I would like to >> see if there is a way to make this work.? We cannot use the >> ?advertised_address? since it changes the IP for every ?route?. >> >> >> >> We were able to get this mostly ?working by doing the following >> >> 1.?????? mhomed=1 >> >> 2.?????? Small patch in the rtpproxy module so that ?force_rtp_proxy >> actually uses the IP address passed (public IP). >> >> 3.?????? Using request_route_preset(?publicIP?) >> >> >> >> The above ?mostly? works.? By that I mean, the INVITE transaction is >> properly passed between internal UAS and carrier SBC and the call is setup. >> However, further transactions (BYE/re-INVITE) etc do not work >> properly. So, far-end hangups are not ?working etc. >> >> >> >> I?ve searched various archives of this and other SER lists looking to >> see if anyone was able to get this scenario working, but couldn?t >> find a definitive answer.? Most of them point to using ?advertised_address?. >> >> >> >> So, and ideas on how to make ?Proxy behind NAT? work without using >> advertised_address?? Am I wasting my time? >> >> >> >> Thanks in advance for any help you can offer. >> >> >> >> SV. >> >> >> >> _______________________________________________ >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing >> list sr-users(a)lists.sip-router.org >> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >> >> > > > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing > list sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >

2 1

permanent usrloc entries in Kamailio
by Klaus Darilion 07 Sep '11

07 Sep '11

Hi! Recently I had a problem with permanent usrloc entries when upgrading a server from SER 0.9 to Kamailio 3.1. Obviously the problem was that the permanent entries had "flag=128" and now expires=0 is used, see old thread: http://old.nabble.com/usrloc-permanent-records-and-strptime-td17668417.html The strange thing is, that even setting the expiry to 2099-0...... did not worked and Kamailio deleted the "expired" entries. Only setting it to "1970-01-01 01:00:00" worked. Any ideas what could been wrong? Further I wonder why Kamailio uses 01:00:00 for the permanent entry? The server is currently running in timezon CEST (UTC+2), thus IMO 02:00:00 would be more logical. Above thread also mentions problems with day-light-saving changes. Are there really problems? How do you solve those problems? I think the best workaround is to set system time always to UTC. Thanks Klaus

2 2

Siremis User Role permissions
by Camila Troncoso 07 Sep '11

07 Sep '11

Hi, I have a question about the assignment of Role permissions to limit some Users privileges in Siremis. I defined a user , and then a Role denying some actions, but I couldn’t deny the action from de SER menu . The Role permissions only show the modules on Application Menu from Administration Tab . What if I want to deny access to some items inside SER Menu , like modifying the ACL services or /and Rounting services? Regards, *Camila Troncoso **|* Ingeniero de Desarrollo VoissNet S.A. *|*ctroncoso(a)redvoiss.net Santiago - Chile *|* +56 2 2408535 www.redvoiss.net

2 1

Check disconnected users
by Anto 06 Sep '11

06 Sep '11

Hello I want to store in a file access and disconnections to the system. To access (registrar), I thought scheduling a perl script and executed with the perl module, the problem I find with disconnections. Since the user can be disconnected for various reasons, had planned to do a script that runs an SQL table location and according to the expires field, see if disconnection has occurred or not. Would have to run this script in cron every X minutes. Is there a simpler way to check this or have Kamailio some function for it?. Thank you. Best regards

2 2

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