sr-users February 2007

sr-users@lists.kamailio.org

158 participants
285 discussions

by zahra bahar

could we see the processes that ser has when receives each massage? is there any log file for ser in about this? --------------------------------- Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit.

17 years, 9 months

[Users] DB tables for presence module

by Reinhold Buchinger

Hello, Can you explain me the difference between the information stored in the "watchers" table and "active-watchers" table? When is a watcher insert in which table? Thanks a lot! Best regards, Reinhold --

17 years, 9 months

[Users] MEDIAPROXY - Cannot detect inactive rtp sessions, any other BYE fix method?

by Dan-Cristian Bogos

Hi Guys, I know that this is not the support channel of mediaproxy, but just hoping that somebody from ag-projects is monitoring this list as well. I found out that, in my case, the SIP-BYE issue is still persistent even by using mediaproxy . If I will stop sending rtp through mediaproxy (eg by killing my client from task manager, or loosing the internet), mediaproxy will still find the session active, like nothing happened and therefore the bill will be inaquarate. I am using the version 1.7.2, and as read in the change log, 1.8.0 didn't change anything on this chapter. Is there any other solution or workarround available? Thxs, Dan

17 years, 9 months

[Serusers] Patch for MySQL 5.0.19 and above in SER 0.9.x

by sip

I've attached a patch file for people to use (it really only adds 3 lines) to patch the my_con.c file in the mysql module for SER 0.9.x I've tested it for a week with inactivity, restarts of mysql, etc, and it holds up rather well, but of course I would be remiss if I didn't add a 'use at your own risk' disclaimer. ;) The basic problem is that, after MySQL 5.0.3, they changed the default behaviour of the mysql connection socket to NOT reconnect in the case of a timeout or a restart of the server. If you had SER up and running for a while, or if there were a glitch with your mysql, the connection would time out/disconnect, and SER would no longer be able to hit the database (requiring a restart of SER). The MySQL coders added an option to enable the reconnect ability of the mysql connection, but it didn't work until 5.0.19. SO... if you're using mysql 5.0.19 or above with SER 0.9.x (there may only be 3 of us doing this ;) ), here's a patch file for you to apply to my_con.c in your modules/mysql directory. I'd recommend backing up your my_con.c file before patching. N.

17 years, 9 months

[Users] ?opsr? - setup

by Michel Bensoussan

Hello I have some setup problems. I compiled and install as following: /prompt$ make mode=debug all prompt$ su prompt# make install /To run openSer I tried: /prompt# /usr/local/sbin/openser / and /prompt# /usr/local/sbin/openser D E / in both case there is the following output: / 127.0.0.1 [127.0.0.1]:5060 192.168.1.86 [192.168.1.86]:5060 192.169.4.86 [192.169.4.86]:5060 192.168.13.86 [192.168.13.86]:5060 127.0.0.1 [127.0.0.1]:5060 192.168.1.86 [192.168.1.86]:5060 192.169.4.86 [192.169.4.86]:5060 192.168.13.86 [192.168.13.86]:5060 Listening on udp: 127.0.0.1 [127.0.0.1]:5060 udp: 192.168.1.86 [192.168.1.86]:5060 udp: 192.169.4.86 [192.169.4.86]:5060 udp: 192.168.13.86 [192.168.13.86]:5060 tcp: 127.0.0.1 [127.0.0.1]:5060 tcp: 192.168.1.86 [192.168.1.86]:5060 tcp: 192.169.4.86 [192.169.4.86]:5060 tcp: 192.168.13.86 [192.168.13.86]:5060 Aliases: tcp: michel:5060 tcp: michel.local:5060 tcp: localhost:5060 udp: michel:5060 udp: michel.local:5060 udp: localhost:5060 //prompt# /Attached my config file ( /etc/openser/openser.cfg). On this config file, I set listen=192.168.13.86 so I expected the openSER to listen only 192.168.13.86. Actually I don't understand from where the application takes the openser.cfg file? I removed /etc/openser/openser.cfg but the application is still running. / /Regards, Michel. / / # # $Id: openser.cfg,v 1.6.2.1 2006/07/17 15:51:03 klaus_darilion Exp $ # # simple quick-start config script # # ----------- global configuration parameters ------------------------ debug=3 # 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) listen=192.168.13.86 port=5060 children=4 fifo="/tmp/openser_fifo" # # uncomment the following lines for TLS support #disable_tls = 0 #listen = tls:your_IP:5061 #tls_verify_server = 1 #tls_verify_client = 1 #tls_require_client_certificate = 0 #tls_method = TLSv1 #tls_certificate = "/usr/local/etc/openser/tls/user/user-cert.pem" #tls_private_key = "/usr/local/etc/openser/tls/user/user-privkey.pem" #tls_ca_list = "/usr/local/etc/openser/tls/user/user-calist.pem" # ------------------ module loading ---------------------------------- # Uncomment this if you want to use SQL database #loadmodule "/usr/local/lib/openser/modules/mysql.so" loadmodule "/usr/local/lib/openser/modules/sl.so" loadmodule "/usr/local/lib/openser/modules/tm.so" loadmodule "/usr/local/lib/openser/modules/rr.so" loadmodule "/usr/local/lib/openser/modules/maxfwd.so" loadmodule "/usr/local/lib/openser/modules/usrloc.so" loadmodule "/usr/local/lib/openser/modules/registrar.so" loadmodule "/usr/local/lib/openser/modules/textops.so" # Uncomment this if you want digest authentication # mysql.so must be loaded ! #loadmodule "/usr/local/lib/openser/modules/auth.so" #loadmodule "/usr/local/lib/openser/modules/auth_db.so" # ----------------- setting module-specific parameters --------------- # -- usrloc params -- modparam("usrloc", "db_mode", 0) # 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) # ------------------------- request routing logic ------------------- # main routing logic route{ # initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); exit; }; # we record-route all messages -- to make sure that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol if (!method=="REGISTER") record_route(); # subsequent messages withing a dialog should take the # path determined by record-routing if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); }; if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); # if you have some interdomain connections via TLS #if(uri=~"@tls_domain1.net") { # t_relay("tls:domain1.net"); # exit; #} else if(uri=~"@tls_domain2.net") { # t_relay("tls:domain2.net"); # exit; #} route(1); }; # if the request is for other domain use UsrLoc # (in case, it does not work, use the following command # with proper names and addresses in it) if (uri==myself) { if (method=="REGISTER") { # Uncomment this if you want to use digest authentication #if (!www_authorize("openser.org", "subscriber")) { # www_challenge("openser.org", "0"); # exit; #}; save("location"); exit; }; lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); exit; }; append_hf("P-hint: usrloc applied\r\n"); }; route(1); } route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; exit; }

17 years, 9 months

Re: [Users] A better way to count the length of a variable

by Tavis P

Ah efficient length counting, you're only a version away... Thanks Brandon Brandon Armstead wrote: > Tavis P wrote: >> I'm trying to find a fast way to count the length of a variable (and >> detect when the length exceeds a certain value) >> All i've come up with so far is a regex, does anyone know of a >> faster/better way to do this? >> >> >> Heres my current approach: >> !avp_check("$ci", "re/^.{1,128}$/g") >> >> >> tavis >> >> _______________________________________________ >> Users mailing list >> Users(a)openser.org >> http://openser.org/cgi-bin/mailman/listinfo/users >> >> > Hello Tavis, > > Currently that is the only method available, however keep your eye > out for the release of OpenSER version 1.2.0, it was recently froze in > CVS and hopefully will be ready pretty soon, however here are some of > the methods that will be available: > http://openser.org/dokuwiki/doku.php/transformations:devel. > > Regards, > Brandon > >

17 years, 9 months

[Users] A better way to count the length of a variable

by Tavis P

I'm trying to find a fast way to count the length of a variable (and detect when the length exceeds a certain value) All i've come up with so far is a regex, does anyone know of a faster/better way to do this? Heres my current approach: !avp_check("$ci", "re/^.{1,128}$/g") tavis

17 years, 9 months

[Serusers] Problems with Rtpproxy traffic balancing in SER 0.10.x

by Angelo Taddeo

I'm using ser 0.10.x ( CVS version). About rtpproxy traffic balancing, I don't know where I have to put rtpproxy IP address and where I have to set $node variable value. How does SER obtain rtpproxy IP address ? What the relation between rtpproxy IP address and N0, N1.....etc ? What parameters have I to put in force_rtp_proxy() function? Only rtpproxy IP address? In my framework happens : when SER receives INVITE Request and 200 OK it rewrites the body of SIP message (SDP). The problem is that it doesn't put in connection information (c) rtpproxy IP address; it puts its IP address. So clients send their RTP packet to SER instead to rtpproxy. How I can force SER to rewrite correctly SDP so that clients receive rtpproxy IP address in INVITE and 200 OK SIP message? Thanks in advance Alekos --------------------------------- L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail

17 years, 9 months

[Serusers] register with ser

by zahra bahar

Hi. I installed SER.when I want to register with xlite in ser.xlite phone sends INVITE to ser.but ser doesn't send ok or any reply. what is the wrong. wen I run ser I have: Listening on udp: 127.0.0.1 [127.0.0.1]:5060 udp: 10.10.10.138 [10.10.10.138]:5060 tcp: 127.0.0.1 [127.0.0.1]:5060 tcp: 10.10.10.138 [10.10.10.138]:5060 Aliases: tcp: Shahab2:5060 tcp: Shahab2.Sarv:5060 tcp: localhost:5060 udp: Shahab2:5060 udp: Shahab2.Sarv:5060 udp: localhost:5060 WARNING: no fork mode and more than one listen address found(will use only thethe first one) stateless - initializing 0(0) Maxfwd module- initializing textops - initializing 0(0) INFO: udp_init: SO_RCVBUF is initially 112640 0(0) INFO: udp_init: SO_RCVBUF is finally 225280 0(0)WARNING: using only the first listen address (no fork) 2(6248) INFO: fifo process starting: 6248 2(6248) SER: open_uac_fifo: fifo server up at /tmp/ser_fifo... 2(6248) WARNING: no fifo_db_url given - fifo DB commands disabled! --------------------------------- Be a PS3 game guru. Get your game face on with the latest PS3 news and previews at Yahoo! Games.

17 years, 9 months

RE: [Serusers] register with ser

by Su Kerry

17 years, 9 months

← Newer
1
...
17
18
19
20
21
22
23
...
29
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 February 2007