sr-users November 2005

sr-users@lists.kamailio.org

245 participants
570 discussions

[Users] Setting t_relay() timeout in lcr

by Douglas Garstang

How can I set the t_relay() INVITE timeout in the lcr module? Setting fr_inv_timer and fr_inv_timer_next with modparam seems to have no effect. What's the significance of fr_inv_timer_avp? Do I need to set that instead? And just what is an 'rpid'??? I can't find this documented anywhere. Thanks

19 years

[Serusers] NAT again

by bosinclar＠laposte.net

I need to add some functions in my ser.cfg for nat support. I use my open(ser) as outbound proxy with two interfaces ppp0 and eth0. sip agents send requests to eth0. I want my packets passing through the register and invite blocks by fixing contact with a public ip. All packets from private network must be sent to eth0. Any suggestions Bob Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,34/mn) ; tél : 08 92 68 13 50 (0,34/mn)

19 years

[Users] writing URI lists from headers into AVPs

by JF

Hi, Is there a way (from the script) to write a URI list from a SIP header (like the ones in Route or Record-Route headers) into one or more AVPs? Thanks in advance! JF

19 years

RE: [Users] Multiple IP in one box

by Fernando Rodriguez

Iqbal, Actualy the conection between the atas is made the problem is that only one side can hear the other so the voice is not going tru. Of I run ser/openser with out forking I see it listening to all the ip addresses, I think is more an issue of using media proxy or rtpproxy. The 10.xx and 192.169.xx networks can ping and do anything to the internet the problem is from the internet to the inside .. -----Mensaje original----- De: Iqbal [mailto:iqbal@gigo.co.uk] Enviado el: Martes, 22 de Noviembre de 2005 10:38 a.m. Para: Fernando Rodriguez Asunto: Re: [Users] Multiple IP in one box Hi You have 3 IP to which you want ser to listen to, to allow ATA to make calls, why not just tell the ATA the sip proxy addess, instead and let it deal with the NAT issue and henceonly listen to one IP address, I mean can your ATA on the 10.254 network see the public IP address vis NA translation. If not get SER to listen to all the IP address, by using the listen command iqbal Fernando Rodriguez wrote: > Im trying to use openser as a Proxy for different interfaces in one > box I have tried almos averithing to make it work properly but for > some reason I cant. > > > > Here is my setup and I hope someone can helpme or guide me in the > right way. > > > > > > > > > > One Linux-OpenSer box with 4 netcards > > > > 1 Has a public ip > > 2 Has a 192.168.23.10 ip > > 3 Has a 10.254.10.240 ip > > 4 Is not being used > > > > I want to be able to make calls from the ATAs in all the different > networks, but the fact is that as it is now I cant, I want to know if > I have to set up multiple media proxies or rtpproxy if I have to use a > proxy dispatcher or not. > > > > This is my configuration file > > > > > > > > > > # ----------- global configuration parameters ------------------------ > > > > #debug=9 # debug level (cmd line: -dddddddddd) > > fork=yes > > log_stderror=no # (cmd line: -E) > > > > /* Uncomment these lines to enter debugging mode > > #fork=no > > #log_stderror=yes > > */ > > > > check_via=no # (cmd. line: -v) > > dns=no # (cmd. line: -r) > > rev_dns=no # (cmd. line: -R) > > #port=5060 > > children=4 > > fifo="/tmp/openser_fifo" > > fifo_db_url="mysql://openser:openserrw@localhost/openser" > > > > alias="test.net" > > # ------------------ module loading ---------------------------------- > > > > #loadmodule "/usr/lib/openser/modules/acc.so" > > loadmodule "/usr/lib/openser/modules/mysql.so" > > loadmodule "/usr/lib/openser/modules/sl.so" > > loadmodule "/usr/lib/openser/modules/tm.so" > > loadmodule "/usr/lib/openser/modules/rr.so" > > loadmodule "/usr/lib/openser/modules/maxfwd.so" > > loadmodule "/usr/lib/openser/modules/usrloc.so" > > loadmodule "/usr/lib/openser/modules/registrar.so" > > loadmodule "/usr/lib/openser/modules/auth.so" > > loadmodule "/usr/lib/openser/modules/auth_db.so" > > loadmodule "/usr/lib/openser/modules/uri.so" > > loadmodule "/usr/lib/openser/modules/uri_db.so" > > loadmodule "/usr/lib/openser/modules/domain.so" > > loadmodule "/usr/lib/openser/modules/mediaproxy.so" > > loadmodule "/usr/lib/openser/modules/nathelper.so" > > loadmodule "/usr/lib/openser/modules/textops.so" > > > > > > # ----------------- setting module-specific parameters --------------- > > # -- usrloc params -- > > > > modparam("usrloc", "db_mode", 2) > > modparam("usrloc", "timer_interval", 10) > > modparam("usrloc", "db_url", > "mysql://openser:openserrw@localhost/openser") > > > > # -- auth params -- > > modparam("auth_db", "db_url", > "mysql://openser:openserrw@localhost/openser") > > modparam("auth_db", "calculate_ha1", yes) > > modparam("auth_db", "password_column", "password") > > > > # -- rr params -- > > # add value to ;lr param to make some broken UAs happy > > modparam("rr", "enable_full_lr", 1) > > > > > > # -- tm Params -- > > modparam("tm", "fr_inv_timer", 45 ) > > modparam("tm", "fr_timer", 12 ) > > > > modparam("registrar", "nat_flag", 6) > > > > > > modparam("nathelper", "rtpproxy_disable", 1) > > #modparam("nathelper", "natping_interval", 30) > > #modparam("nathelper", "sipping_from", "sip:ping@sipserver.net") > > > > > > #modparam("mediaproxy", "ping_nated_only", 0) # Ping only clients > behind NAT > > modparam("mediaproxy", "natping_interval", 20) > > modparam("mediaproxy", "mediaproxy_socket", "/var/run/mediaproxy.sock") > > > > modparam("registrar", "nat_flag", 6) > > > > > > # ------------------------- request routing logic ------------------- > > > > # main routing logic > > > > route { > > > > # > ----------------------------------------------------------------- > > # Procesos de Limpieza > > # > ----------------------------------------------------------------- > > if (!mf_process_maxfwd_header("10")) { > > sl_send_reply("483", "Too Many Hops"); > > break; > > }; > > > > if (msg:len > max_len) { > > sl_send_reply("513", "Message Overflow"); > > break; > > }; > > > > # > ----------------------------------------------------------------- > > # Registro > > # > ----------------------------------------------------------------- > > if (method!="REGISTER") { > > log(1, "Area de Registro\n"); > > > > record_route(); > > }; > > > > > > # > ----------------------------------------------------------------- > > # Call Tear Down Section > > # > ----------------------------------------------------------------- > > if (method=="BYE" || method=="CANCEL") { > > log(1, "Proceso de fin de llamada\n"); > > end_media_session(); > > }; > > # > ----------------------------------------------------------------- > > # Loose Route Section > > # > ----------------------------------------------------------------- > > if (loose_route()) { > > > > if (has_totag() && (method=="INVITE" || method=="ACK")) { > > > > if (client_nat_test("3") || > search("^Route:.*;nat=yes")) { > > setflag(6); > > use_media_proxy(); > > }; > > }; > > > > route(1); > > break; > > }; > > > > # > ----------------------------------------------------------------- > > # Call Type Processing Section > > # > ----------------------------------------------------------------- > > > > if (uri!=myself) { > > route(1); > > break; > > }; > > > > if (uri==myself) { > > > > if (method=="CANCEL") { > > route(3); > > break; > > } else if (method=="INVITE") { > > route(3); > > break; > > } else if (method=="REGISTER") { > > route(2); > > break; > > }; > > > > lookup("aliases"); > > if (uri!=myself) { > > route(1); > > break; > > }; > > > > if (!lookup("location")) { > > sl_send_reply("404", "User Not Found"); > > break; > > }; > > }; > > > > route(1); > > } > > > > route[1] { > > > > # > ----------------------------------------------------------------- > > # Default Message Handler > > # > ----------------------------------------------------------------- > > > > t_on_reply("1"); > > > > if (!t_relay()) { > > > > if (method=="INVITE" || method=="ACK") { > > end_media_session(); > > }; > > > > sl_reply_error(); > > }; > > } > > > > route[2] { > > > > # > ----------------------------------------------------------------- > > # REGISTER Message Handler > > # ---------------------------------------------------------------- > > > > sl_send_reply("100", "Trying"); > > > > # if(dst_ip==192.168.1.1) { > > # log("message received on loopback interface\n"); > > # setflag(7); > > # fix_nated_register(); > > # force_rport(); > > # }; > > # if(dst_ip==192.168.108.253) { > > # log("message received on loopback interface\n"); > > # setflag(6); > > # fix_nated_register(); > > # force_rport(); > > # }; > > > > if (!www_authorize("test.net","subscriber")) { > > www_challenge("test.net","0"); > > break; > > }; > > > > if (!check_to()) { > > sl_send_reply("401", "Unauthorized"); > > break; > > }; > > > > consume_credentials(); > > > > if (!save("location")) { > > sl_reply_error(); > > }; > > fix_nated_register(); > > } > > > > route[3] { > > > > # > ----------------------------------------------------------------- > > # CANCEL and INVITE Message Handler > > # > ----------------------------------------------------------------- > > > > lookup("aliases"); > > if (uri!=myself) { > > route(1); > > break; > > }; > > > > if (!lookup("location")) { > > sl_send_reply("404", "User Not Found"); > > break; > > }; > > > > if (method=="CANCEL") { > > route(1); > > break; > > }; > > > > if (!proxy_authorize("","subscriber")) { > > proxy_challenge("","0"); > > break; > > } else if (!check_from()) { > > sl_send_reply("403", "Use From=ID"); > > break; > > }; > > > > consume_credentials(); > > > > # > ------------------------------------------------------------------------ > > # Reglas de LLamada > > # > ------------------------------------------------------------------------ > > > > if(uri=~"(^sip:1[0-9]*@.*)" && > from_uri=~"(^sip:2[0-9]*@.*)") { > > log(1, "Llamada de extenciones 1xxx a 2xxx\n"); > > use_media_proxy(); > > }; > > > > if(uri=~"(^sip:1[0-9]*@.*)" && > from_uri=~"(^sip:3[0-9]*@.*)") { > > log(1, "Llamada de extenciones 1xxx a 3xxx\n"); > > fix_contact(); > > use_media_proxy(); > > }; > > > > if(uri=~"(^sip:1[0-9]*@.*)" && > from_uri=~"(^sip:4[0-9]*@.*)") { > > log(1, "Llamada de extenciones 1xxx a 4xxx\n"); > > fix_contact(); > > use_media_proxy(); > > }; > > > > if(uri=~"(^sip:2[0-9]*@.*)" && > from_uri=~"(^sip:1[0-9]*@.*)") { > > log(1, "Llamada de extenciones 2xxx a 1xxx\n"); > > fix_contact(); > > use_media_proxy(); > > }; > > > > if(uri=~"(^sip:2[0-9]*@.*)" && > from_uri=~"(^sip:3[0-9]*@.*)") { > > log(1, "Llamada de extenciones 2xxx a 3xxx\n"); > > fix_contact(); > > use_media_proxy(); > > }; > > > > if(uri=~"(^sip:2[0-9]*@.*)" && > from_uri=~"(^sip:4[0-9]*@.*)") { > > log(1, "Llamada de extenciones 2xxx a 4xxx\n"); > > fix_contact(); > > use_media_proxy(); > > }; > > > > if(uri=~"(^sip:3[0-9]*@.*)" && > from_uri=~"(^sip:1[0-9]*@.*)") { > > log(1, "Llamada de extenciones 3xxx a 1xxx\n"); > > fix_contact(); > > use_media_proxy(); > > }; > > > > if(uri=~"(^sip:3[0-9]*@.*)" && > from_uri=~"(^sip:2[0-9]*@.*)") { > > log(1, "Llamada de extenciones 3xxx a 2xxx\n"); > > fix_contact(); > > use_media_proxy(); > > }; > > > > if(uri=~"(^sip:3[0-9]*@.*)" && > from_uri=~"(^sip:4[0-9]*@.*)") { > > log(1, "Llamada de extenciones 3xxx a 4xxx\n"); > > fix_contact(); > > use_media_proxy(); > > }; > > > > if(uri=~"(^sip:4[0-9]*@.*)" && > from_uri=~"(^sip:1[0-9]*@.*)") { > > log(1, "Llamada de extenciones 4xxx a 1xxx\n"); > > fix_contact(); > > use_media_proxy(); > > }; > > > > if(uri=~"(^sip:4[0-9]*@.*)" && > from_uri=~"(^sip:2[0-9]*@.*)") { > > log(1, "Llamada de extenciones 4xxx a 2xxx\n"); > > fix_contact(); > > use_media_proxy(); > > }; > > > > if(uri=~"(^sip:4[0-9]*@.*)" && > from_uri=~"(^sip:3[0-9]*@.*)") { > > log(1, "Llamada de extenciones 4xxx a 3xxx\n"); > > fix_contact(); > > use_media_proxy(); > > }; > > > > route(1); > > } > > > > onreply_route[1] { > > > > #if ((isflagset(6) || isflagset(7)) && > (status=~"(180)|(183)|2[0-9][0-9]")) { > > > > # if (!search("^Content-Length:\ +0")) { > > log(1, "Mensaje de prueba en reply route\n"); > > fix_contact(); > > use_media_proxy(); > > # }; > > # }; > > > > } > > > > > > As you can see I use different starting numbers for the ATA for each > of the interfaces, I tested using only one mediaproxy listening to > 127.0.0.1 but I have tried a lot of configurations, all the clients > register perfectly but cant seem to call one another exept the ones > that are on the same interface. > > > > Im using fedora core 3 with openser 0.95 mediaproxy 1.42 > > > > Hope any one can help me or point me the way to do this of if its not > viable or cant be done. > > > > Thanks a lot for your kind help > > > > Yours truly > > > > > > Fernando Rodriguez V. > > frod(a)aitelecom.net <mailto:frod@aitelecom.net> > > AITelecom S.A. de C.V. > > http://www.aitelecom.net > > > > > > > >------------------------------------------------------------------------ > >_______________________________________________ >Users mailing list >Users(a)openser.org >http://openser.org/cgi-bin/mailman/listinfo/users > >

19 years

[Serusers] Noisy feedback tells & radius_authorize_sterman(): Failure

by Kamran Ahmad

Hi all I am using SER-0.9.3 with radiusclient-ng-0.5.1 but unable to get thrrough radius Digest Authentication i am getting Noisy feedback tells and no request to Radius ---------------------------------------------------- 192.168.0.1:10411 -> 192.168.0.3:5060 REGISTER sip:192.168.0.3 SIP/2.0..To: 2000<sip:2000@192.168.0.3>..From: 2000<sip:2000@212. 36.71.78>;tag=68a232bb..Via: SIP/2.0/UDP 192.168.1.236:10411;branch=z9hG4bK-d87543-788469354 -1--d87543-;rport..Call-ID: 726b328158a24912..CSeq: 2 REGISTER..Contact: <sip:2000@192.168.1 .236:10411>..Expires: 60..Max-Forwards: 70..Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO..User-Agent: eyeBeam release 3005x stamp 17288..Authorizat ion: Digest username="2000",realm="192.168.0.3",nonce="438142b95bb202f9f7b35267264fa3cdf240 c34c",uri="sip:192.168.0.3",response="587553ab1fdd8979c16dd5619ea1f3f1",algorithm=MD5..Cont ent-Length: 0.... # U 192.168.0.3:5060 -> 192.168.0.1:10411 SIP/2.0 100 Trying..To: 2000<sip:2000@192.168.0.3>..From: 2000<sip:2000@192.168.0.3>;tag=6 8a232bb..Via: SIP/2.0/UDP 192.168.1.236:10411;branch=z9hG4bK-d87543-788469354-1--d87543-;rpo rt=10411;received=192.168.0.1..Call-ID: 726b328158a24912..CSeq: 2 REGISTER..Server: OpenSer (0.9.5 (i386/linux))..Content-Length: 0..Warning: 392 192.168.0.3:5060 "Noisy feedback tel ls: pid=27853 req_src_ip=192.168.0.1 req_src_port=10411 in_uri=sip:192.168.0.3 out_uri=si p:192.168.0.3 via_cnt==1".... # U 192.168.0.3:5060 -> 192.168.0.1:10411 SIP/2.0 401 Unauthorized..To: 2000<sip:2000@192.168.0.3>;tag=236419814c1d6cbca250c821be3316 c3.97c8..From: 2000<sip:2000@192.168.0.3>;tag=68a232bb..Via: SIP/2.0/UDP 192.168.1.236:1041 1;branch=z9hG4bK-d87543-788469354-1--d87543-;rport=10411;received=192.168.0.1..Call-ID: 726 b328158a24912..CSeq: 2 REGISTER..WWW-Authenticate: Digest realm="192.168.0.3", nonce="7264fa3cdf240c34c"..Server: OpenSer (0.9.5 (i386/linux))..Content-Length: 0..Warning: 392 192.168.0.3:5060 "Noisy feedback tells: pid=27853 req_src_ip=192.168.0.1 req_src_port=10411 in_uri=sip:192.168.0.3 out_uri=sip:192.168.0.3 via_cnt==1".... ------------------------------------------------------------------------ why i am getting these ------------------------------------------------------- 0(27853) radius_authorize_sterman(): Failure 0(27853) build_auth_hf(): 'WWW-Authenticate: Digest realm="192.168.0.3, nonce="43814271015d7812e9f068467d0c352ceb679d70" ' 0(27853) parse_headers: flags=-1 0(27853) check_via_address(192.168.0.1, 192.168.0.1, 0) 0(27853) DEBUG:destroy_avp_list: destroying list 0x4043dee0 0(27853) receive_msg: cleaning up ser.cfg ----------------------- loadmodule "/usr/local/lib/ser/modules/mysql.so" loadmodule "/usr/local/lib/ser/modules/sl.so" loadmodule "/usr/local/lib/ser/modules/tm.so" loadmodule "/usr/local/lib/ser/modules/rr.so" loadmodule "/usr/local/lib/ser/modules/maxfwd.so" loadmodule "/usr/local/lib/ser/modules/usrloc.so" loadmodule "/usr/local/lib/ser/modules/registrar.so" loadmodule "/usr/local/lib/ser/modules/auth_radius.so" loadmodule "/usr/local/lib/ser/modules/textops.so" loadmodule "/usr/local/lib/ser/modules/nathelper.so" loadmodule "/usr/local/lib/ser/modules/uri.so" # Uncomment this if you want digest authentication # mysql.so must be loaded ! loadmodule "/usr/local/lib/ser/modules/auth.so" modparam("usrloc", "db_mode", 0) modparam("auth_radius","radius_config","/usr/local/etc/radiusclient-ng/radiusclient.conf") modparam("auth_radius","service_type",15) # Uncomment this if you want to use SQL database # for persistent storage and comment the previous line #modparam("usrloc", "db_mode", 2) # -- auth params -- # Uncomment if you are using auth module # #modparam("auth_db", "calculate_ha1", yes) # # If you set "calculate_ha1" parameter to yes (which true in this config), # uncomment also the following parameter) # #modparam("auth_db", "password_column", "password") # -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1) modparam("nathelper", "natping_interval", 30) modparam("nathelper", "ping_nated_only", 1) modparam("nathelper", "rtpproxy_sock", "unix:/var/run/rtpproxy.sock") #modparam("usrloc", "db_mode", 2) modparam("registrar", "nat_flag", 6) modparam("rr", "enable_full_lr", 1) ############################################################################# modparam("tm", "fr_timer", 40) modparam("tm", "fr_inv_timer", 35) modparam("tm", "wt_timer", 5) modparam("tm", "fr_inv_timer_avp", "inv_timeout") ########################################################################### # ------------------------- request routing logic ------------------- # main routing logic route{ # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); break; }; if (msg:len >= max_len ) { sl_send_reply("513", "Message too big"); break; }; if (!method=="REGISTER") { record_route(); } if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); break; }; if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); route(1); break; }; if (method=="BYE" || method=="CANCEL") { unforce_rtp_proxy(); } if (loose_route()) { if (has_totag() && (method=="INVITE" || method=="ACK")) { if (nat_uac_test("19")) { setflag(6); force_rport(); fix_nated_contact(); }; # force_rtp_proxy("l"); force_rtp_proxy(); }; route(1); break; }; # if the request is for other domain use UsrLoc # (in case, it does not work, use the following command if (uri==myself) { if (method=="INVITE") { route(3); break; }; }; append_hf("P-hint: usrloc applied\r\n"); route(1); } route[1] { # ----------------------------------------------------------------- # Default Message Handler # ----------------------------------------------------------------- t_on_reply("1"); if (!t_relay()) { if (method=="INVITE" && isflagset(6)) { unforce_rtp_proxy(); }; sl_reply_error(); }; } route[2] { # ----------------------------------------------------------------- # REGISTER Message Handler # ---------------------------------------------------------------- if (!search("^Contact:\ +\*") && nat_uac_test("19")) { setflag(6); fix_nated_register(); force_rport(); }; sl_send_reply("100", "Trying"); if (!radius_www_authorize("")) { www_challenge("","0"); break; }; consume_credentials(); if (!save("location")) { sl_reply_error(); }; } __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

19 years

RE: [Users] Dispatcher module - Does it actually work?

by Douglas Garstang

So, will the lcr module let me timeout a gateway, and try another if it's unavailable, as someone else suggested? As soon as I call t_relay(), I hit the same problem.... it never times out and tries to reach the first gateway forever. -----Original Message----- From: Daniel-Constantin Mierla [mailto:daniel@voice-system.ro] Sent: Fri 11/25/2005 2:56 AM To: Douglas Garstang Cc: users(a)openser.org Subject: Re: [Users] Dispatcher module - Does it actually work? On 11/24/05 22:42, Douglas Garstang wrote: > Hashing over call-id may work to some degree, and I'll investigate it more, but hashing over the From: means that the same caller will always get the same Asterisk box, and your redundancy goes down the toilet. > The redundancy you talk about is only in your mind. I never said that dispatcher supports redundancy. Please read carefully the messages and have an adequate language. Besides that, the topic was not about the redundancy, but about traffic dispatching. To get the right answer put the proper question. As you said, "The request URI from the phones is always going to be the same." I suggested to use either call-id or from uri hash algorithm. Yes, for same From uri the destination will be the same, and also for same call-id the destination will be the same. Moreover, for different values, the destination can be the same, since there is hash computation and some results will overlap. Cheers, Daniel > > Actually I guess it's down the toilet anyway. The bottom line seems to be that it doesn't matter whether you use the dispatcher or SRV records to distribute load, OpenSER will never try to connect to anything else on failure and at least for us, that makes it use in a production system, not an option. > > > > -----Original Message----- > From: Daniel-Constantin Mierla [mailto:daniel@voice-system.ro] > Sent: Thu 11/24/2005 12:19 PM > To: Douglas Garstang > Cc: users(a)openser.org > Subject: Re: [Users] Dispatcher module - Does it actually work? > > > > On 11/24/05 19:53, Douglas Garstang wrote: > > The request URI from the phones is always going to be the same. Doesn't that mean that OpenSER will always just use the same Asterisk box then? > if you do hash over r-uri, then yes, all messages will go to same > destination. > > I'm trying to round-robin as evenly (as possible) and distribute call load amonst multiple Asterisk systems. > > > In this case hash over call-id or from is more indicated. > > Cheers, > Daniel > > > -----Original Message----- > > From: Daniel-Constantin Mierla [mailto:daniel@voice-system.ro] > > Sent: Thu 11/24/2005 10:25 AM > > To: Douglas Garstang > > Cc: users(a)openser.org > > Subject: Re: [Users] Dispatcher module - Does it actually work? > > > > > > > > On 11/24/05 01:37, Douglas Garstang wrote: > > > After many many fruitless hours spent on trying to get OpenSER to work with DNS SRV records (I made a post to the group earlier today on this), I stumbled across the dispatcher module, and have been trying to get it to work instead. > > > > > > The module was designed to load balance, right? It doesn't seem to have been designed very well, unless I am missing something. > > > > > If you read carefully the documentation of the module, you will see the > > scope and limitations of the module: > > http://openser.org/docs/modules/1.0.x/dispatcher.html > > > > If something is not according to the documentation, then it is a bug. > > Stateless means that the module does not keep any state, so it cannot > > select the same destination using algorithm 4 (round robin) after a > > authentication request, choose another algorithm (hashing r-uri, > > callid). Also, being stateless, it cannot try the next address if the > > selected destination fails. > > > > The module was not designed to be load balancer, but a request > > dispatcher. Load balancing is something more complex. > > > > In the last weeks I added destination failover support in dispatcher > > (serial forking within the destination set, with auto-detection of > > failed destinations). It will be on cvs very soon, I have to update the > > documentation and do some testing. > > > > Cheers, > > Daniel > > > > > > > > If you set the algorithm with ds_select_dst() to 4, round robin, it doesn't work! Here's what happens. > > > > > > 1. UA sends INVITE to OpenSER > > > 2. OpenSER forwards INVITE to the first proxy in the dispatcher list. > > > 3. Proxy sends back a digest challenge for authorisation credentials to OpenSER. > > > 4. OpenSER forwards the challenge back to the UA. > > > 5. The UA sends the INVITE again to OpenSER, this time with the requested credentials. > > > 6. OpenSER forwards the new INVITE to the _OTHER_ proxy in the dispatcher list. > > > > > > This is where things start to fall over. This proxy has not issued a challenge request yet so it _again_ sends a digest challenge back to the UA through OpenSER. The UA does not like to receive a second challenge to what it's already sent and gives up. > > > > > > If you set the algorithm to something else besides 4, say 0, to hash to the callid, then OpenSER tries to use an arbitrary proxy from the list. Given that it's hashed against the callid it doesn't switch proxies like it does above in mid call. However, if that proxy is down, it _NEVER_ tries another proxy, thus rending the dispatcher module as a load balancer completely useless. > > > > > > If this module was designed to be a load balancer, how have people gotten it to work? I find it incredibly hard to believe that the dispatcher module was not designed with the above scenarios in mind. I'm so frustrated because what I am trying to do is so simple (had issues with SRV behaving in a similar way). Send requests from OpenSER to another proxy/pbx in a redundant and load balanced fashion. If a system is down, simply go to the next! It's that simple! > > > > > > Btw, the 'proxy' that OpenSER is forwarding too is Asterisk (yeah ok so it isn't a proxy) and the UA's are Polycom 301/501/601 phones. > > > > > > Help very much appreciated! > > > > > > Thanks. > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > _______________________________________________ > > > Users mailing list > > > Users(a)openser.org > > > http://openser.org/cgi-bin/mailman/listinfo/users > > > > > > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Users mailing list > > Users(a)openser.org > > http://openser.org/cgi-bin/mailman/listinfo/users > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Users mailing list > Users(a)openser.org > http://openser.org/cgi-bin/mailman/listinfo/users >

19 years

[Serusers] NAT type detection

by Ladislav Andel

Hello, I've been using Asus WL-500G as NAT/Router device for my testing purposes with SER. I implemented MyStun server which is running on the same OS as SER on 192.168.1.50. I also have two IP addresses on the server which are 192.168.1.50-51 for MyStun functionality. When I start MyStun it listens on default ports 3478 an 3479. UA behind the NAT is Xlite so the STUN implemetation of this softphone should be ok. Question 1: Where should I be able to determine/see what type of NAT I'm behind with X-lite? I'm trying to combine NAThelper/RTPproxy with STUN and use STUN if there is no symmetric NAT. Question 2: Could you advice me what tools I should use for debugging functionality of STUN, please? Hopefully, everything is clear. Ladislav

19 years

RE: [Users] Dispatcher module - Does it actually work?

by Douglas Garstang

Correct me if I am wrong here, but the sketchy docs at openser.org seem to imply that I am going to need to have multiple rows in my mysql table 'gw' for every single user who places calls? Is that correct? Is there some way to trim this down? -----Original Message----- From: Andreas Granig [mailto:andreas.granig@inode.info] Sent: Thu 11/24/2005 5:24 PM To: Douglas Garstang Cc: users(a)openser.org Subject: Re: [Users] Dispatcher module - Does it actually work? Douglas Garstang wrote: > Andy, no. No one has suggested using the lcr module, and I wasn't even aware of it until you mentioned it just now. I took a look at the module docs, they're way beyond my current understanding. it. I'll have to do some reading. Does it allow you to try another route when one is not responding? Yes. You have to define a set of destinations which you can load in the script using load_gws(), and every call to next_gw() sets the ip/port of another destination as ruri, until no more destinations are available. You can find an example here: http://linguin.org/ser/lcr_cap/lcr_config_example.txt It's for a lcr-version which I have extended a little to be able to group destinations according to their capabilities (http://linguin.org/ser.php#lcr-cap), but you should at least get the idea on how to do it with the vanilla lcr module (just leave out the argument in load_gws()). Andy

19 years

[Serusers] MediaProxy exception (text version)

by Adrian Georgescu

Hello Patrick, The issue can be fixed by the attached patch (it will be also fixed in the next release). Alternatively use python2.3 or newer which works even with the existing code. Index: dispatcher.py =================================================================== RCS file: /home/cvs/cvsroot/mediaproxy/modules/dispatcher.py,v retrieving revision 1.28 diff -u -r1.28 dispatcher.py --- dispatcher.py 25 Jul 2005 11:18:17 -0000 1.28 +++ dispatcher.py 25 Nov 2005 05:03:47 -0000 @@ -579,7 +579,7 @@ else: self.address = MediaProxyAddress(url) # implement this def __setattr__(self, name, value): - readonly = ('address') + readonly = ('address',) if name in readonly and self.__dict__.has_key(name): raise AttributeError, "'%s' is a readonly attribute" % name self.__dict__[name] = value >>>>>>>>>> Patrick Jordan-Smith pjs at quicksilver.co.nz Fri Nov 18 02:46:18 CET 2005 Hi, When I have a outgoing INVITE my mediaproxy crashes :( See the following: Nov 18 14:29:00 sip1 proxydispatcher[23201]: command request b566cc84-cd467d92-da2c547b at 202.89.130.40 202.89.130.40:2252:audio 202.89.130.40 sip.qsi.net.nz remote eth0.1 remote PolycomSoundPointIP-SPIP_500-UA/1.5.2.0054 info=from:728728 at sip.qsi.net.nz,to:8378 at sip.qsi.net.nz,fromtag:60DCA320-5F6D23C9,totag: Nov 18 14:29:00 sip1 proxydispatcher[23201]: ---------------------------------------- Nov 18 14:29:00 sip1 proxydispatcher[23201]: Exception happened during processing of request from Nov 18 14:29:00 sip1 proxydispatcher[23201]: Traceback (most recent call last): Nov 18 14:29:00 sip1 proxydispatcher[23201]: File "/usr/lib/python2.2/SocketServer.py", line 458, in process_request_thread Nov 18 14:29:00 sip1 proxydispatcher[23201]: self.finish_request(request, client_address) Nov 18 14:29:00 sip1 proxydispatcher[23201]: File "/usr/lib/python2.2/SocketServer.py", line 253, in finish_request Nov 18 14:29:00 sip1 proxydispatcher[23201]: self.RequestHandlerClass(request, client_address, self)

19 years

[Serusers] MediaProxy exception

by Adrian Georgescu

Hello Patrick, The issue can be fixed by the attached patch (it will be also fixed in the next release). Alternatively use python2.3 or newer which works even with the existing code. >>>>>>>>>> Patrick Jordan-Smith pjs at quicksilver.co.nz Fri Nov 18 02:46:18 CET 2005 Hi, When I have a outgoing INVITE my mediaproxy crashes :( See the following: Nov 18 14:29:00 sip1 proxydispatcher[23201]: command request b566cc84-cd467d92-da2c547b at 202.89.130.40 202.89.130.40:2252:audio 202.89.130.40 sip.qsi.net.nz remote eth0.1 remote PolycomSoundPointIP-SPIP_500-UA/1.5.2.0054 info=from:728728 at sip.qsi.net.nz,to:8378 at sip.qsi.net.nz,fromtag:60DCA320-5F6D23C9,totag: Nov 18 14:29:00 sip1 proxydispatcher[23201]: ---------------------------------------- Nov 18 14:29:00 sip1 proxydispatcher[23201]: Exception happened during processing of request from Nov 18 14:29:00 sip1 proxydispatcher[23201]: Traceback (most recent call last): Nov 18 14:29:00 sip1 proxydispatcher[23201]: File "/usr/lib/python2.2/SocketServer.py", line 458, in process_request_thread Nov 18 14:29:00 sip1 proxydispatcher[23201]: self.finish_request(request, client_address) Nov 18 14:29:00 sip1 proxydispatcher[23201]: File "/usr/lib/python2.2/SocketServer.py", line 253, in finish_request Nov 18 14:29:00 sip1 proxydispatcher[23201]: self.RequestHandlerClass(request, client_address, self)

19 years

← Newer
1
...
11
12
13
14
15
16
17
...
57
Older →

Jump to page:

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 November 2005