sr-users January 2005

sr-users@lists.kamailio.org

199 participants
399 discussions

by sanjaydhadda

>A-Z route over sip is available. > >1) several backup routes per one destination >2) availability of test >3) technical support > > >Plz contact me offlist for rate and further informations > > >MSN:dhadda@hotmail.com >Mohammad > > > > >

20 years, 1 month

[Serusers] NOTIFY missing Contact Header

by Don_Gilletti＠logitech.com

Greetings, I seem to be having some trouble with the pa module on SER 0.10.99-dev0 running on Fedora 3. I can REGISTER fine, and issuing a SUBSCRIBE results in a 200 OK response (and NOTIFYs being generated by the server). However, both the 200 OK response to the SUBSCRIBE and the NOTIFY messages are all missing a Contact header field. Here's the messages: ====================================================== Session Initiation Protocol Request-Line: SUBSCRIBE sip:dontest@172.17.76.25 SIP/2.0 Method: SUBSCRIBE Resent Packet: False Message Header To: <sip:dontest@172.17.76.25> From: <sip:don@172.17.76.25>;tag=b029225f Via: SIP/2.0/UDP 172.17.84.29:5060;branch=z9hG4bK-d87543-671970329-1--d87543-;rport Call-ID: 7f37841cd1635a0b CSeq: 1 SUBSCRIBE Contact: <sip:don@172.17.84.29:5060> Expires: 600 Max-Forwards: 70 Accept: application/pidf+xml Event: presence Content-Length: 0 Session Initiation Protocol Status-Line: SIP/2.0 200 OK Status-Code: 200 Resent Packet: False Message Header To: <sip:dontest@172.17.76.25>;tag=44274c5ba0cc60268b6a1c7eb3de8672-9325 From: <sip:don@172.17.76.25>;tag=b029225f Via: SIP/2.0/UDP 172.17.84.29:5060;branch=z9hG4bK-d87543-671970329-1--d87543-;rport=5060 Call-ID: 7f37841cd1635a0b CSeq: 1 SUBSCRIBE Server: Sip EXpress router (0.10.99-dev0 (i386/linux)) Content-Length: 0 Session Initiation Protocol Request-Line: NOTIFY sip:don@172.17.84.29:5060 SIP/2.0 Method: NOTIFY Resent Packet: False Message Header Via: SIP/2.0/UDP 172.17.76.25;branch=z9hG4bKaebf.9fd37101.0 To: <sip:don@172.17.76.25>;tag=855dae7f From: <sip:dontest@172.17.76.25>;tag=44274c5ba0cc60268b6a1c7eb3de8672-0ddd CSeq: 3 NOTIFY Call-ID: b063ea763c2f6d3d Content-Length: 245 User-Agent: Sip EXpress router(0.10.99-dev0 (i386/linux)) Event: presence Content-Type: application/pidf+xml Subscription-State: active;expires=594 Message body ====================================================== I've been looking at all the documentation I can find, and I can't seem to find out why these are being omitted. Is there something wrong w/my configuration? (see below) Any suggestions why this might be ocurring? don_g ====================================================== ser.cfg file: ====================================================== #--------------------------------------------------------------------- # global configuration parameters #--------------------------------------------------------------------- #debug=7 #fork=no #log_stderror=no listen="172.17.76.25" alias="localhost.localdomain" alias="172.17.76.25" alias="localhost.mycompany.com" dns=no rev_dns=no port=5060 check_via=no sip_warning=no fifo="/tmp/ser_fifo" fifo_db_url="mysql://ser:heslo@localhost/ser" #--------------------------------------------------------------------- # module loading #--------------------------------------------------------------------- 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.so" loadmodule "/usr/local/lib/ser/modules/auth_db.so" loadmodule "/usr/local/lib/ser/modules/exec.so" loadmodule "/usr/local/lib/ser/modules/group.so" loadmodule "/usr/local/lib/ser/modules/print.so" loadmodule "/usr/local/lib/ser/modules/uri.so" loadmodule "/usr/local/lib/ser/modules/uri_db.so" loadmodule "/usr/local/lib/ser/modules/domain.so" loadmodule "/usr/local/lib/ser/modules/xlog.so" loadmodule "/usr/local/lib/ser/modules/options.so" loadmodule "/usr/local/lib/ser/modules/textops.so" loadmodule "/usr/local/lib/ser/modules/pa.so" #--------------------------------------------------------------------- # setting module-specific parameters #--------------------------------------------------------------------- #--------------------------------------------------------------------- # tm module parameters #--------------------------------------------------------------------- modparam("tm", "fr_inv_timer", 40) modparam("tm", "wt_timer", 5) modparam("tm", "fr_timer", 20) #--------------------------------------------------------------------- # rr module parameters #--------------------------------------------------------------------- modparam("rr", "enable_full_lr", 1) #--------------------------------------------------------------------- # userloc module parameters #--------------------------------------------------------------------- modparam("usrloc", "db_url", "mysql://ser:heslo@localhost/ser") modparam("usrloc", "timer_interval", 60) modparam("usrloc", "db_mode", 2) modparam("usrloc", "use_domain", 1) modparam("usrloc", "desc_time_order", 1) #--------------------------------------------------------------------- # registrar module parameters #--------------------------------------------------------------------- modparam("registrar", "default_expires", 3600) modparam("registrar", "min_expires", 60) modparam("registrar", "max_expires", 86400) modparam("registrar", "append_branches", 1) modparam("registrar", "use_domain", 1) modparam("registrar", "desc_time_order", 1) #--------------------------------------------------------------------- # pa module parameters #--------------------------------------------------------------------- modparam("pa", "default_expires", 3600) modparam("pa", "default_priority_percentage", 50) modparam("pa", "db_url", "mysql://ser:heslo@localhost/ser") modparam("pa", "pa_domain", "172.17.76.25") modparam("pa", "use_db", 1) #--------------------------------------------------------------------- # auth_db module parameters #--------------------------------------------------------------------- modparam("auth_db", "db_url", "mysql://ser:heslo@localhost/ser") modparam("auth_db", "password_column", "password") modparam("auth_db", "calculate_ha1", yes) modparam("auth_db", "use_domain", 1) #--------------------------------------------------------------------- # exec module parameters #--------------------------------------------------------------------- modparam("exec", "setvars", 1) modparam("exec", "time_to_kill", 10) #--------------------------------------------------------------------- # group module parameters #--------------------------------------------------------------------- modparam("group", "db_url", "mysql://ser:heslo@localhost/ser") modparam("group", "use_domain", 1) #--------------------------------------------------------------------- # uri_db module parameters #--------------------------------------------------------------------- modparam("uri_db", "db_url", "mysql://ser:heslo@localhost/ser") modparam("uri_db", "use_domain", 1) #--------------------------------------------------------------------- # domain module parameters #--------------------------------------------------------------------- modparam("domain", "db_url", "mysql://ser:heslo@localhost/ser") modparam("domain", "db_mode", 1) #--------------------------------------------------------------------- # xlog module parameters #--------------------------------------------------------------------- modparam("xlog", "buf_size", 8192) #--------------------------------------------------------------------- # 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"); break; }; if (msg:len >= max_len) { sl_send_reply("513", "Message too big"); break; }; #------------------------------------------------------ # 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 within 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); break; }; if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); route(1); break; }; if (uri==myself) { if (method=="REGISTER") { if (!www_authorize("172.17.76.25", "subscriber")) { www_challenge("172.17.76.25", "1"); break; }; save("location"); break; }; lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); break; }; #------------------------------------------------------ # native SIP destinations are handled using our USRLOC DB #------------------------------------------------------ if (!lookup("location")) { sl_send_reply("404", "Not Found"); break; }; if (method=="SUBSCRIBE") { if (!t_newtran()) { log(1, "newtran error\n"); sl_reply_error(); }; handle_subscription("registrar"); break; }; if (method=="PUBLISH") { if (!t_newtran()) { log(1, "newtran error\n"); sl_reply_error(); }; handle_publish("registrar"); break; }; }; append_hf("P-hint: userloc applied\r\n"); route(1); } #--------------------------------------------------------------------- # Route Section [1] #--------------------------------------------------------------------- route[1] { #------------------------------------------------------ # forward to current uri now; use stateful forwarding; that # works reliably even if we forward from TCP to UDP #------------------------------------------------------ if (!t_relay()) { sl_reply_error(); }; }

20 years, 1 month

[Serusers] ser-0.9.0 and PA clients

by Helge Waastad

Hello, I've started to use the 0.9.0 release and to me it seems to work as a charm :-) However does anybody know which SIP clients which is compliant for the PA? I'm using kphone and it works fine, but I would like to try out some for use on Microsoft? Messenger 5.0 does not work. Mvh, Helge Waastad

20 years, 1 month

RE: [Serusers] Dynamic Routes with SER.

by Ricardo Martinez

Hello. Regarding to this subject. I followed some instructions for the AVPOPS module and i have created the next lines in mysql database. This is the description of my usr_preferences table: +-----------+---------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +-----------+---------------+------+-----+---------+-------+ | uuid | varchar(64) | | | | | | username | varchar(100) | | PRI | | | | domain | varchar(128) | | PRI | | | | attribute | varchar(32) | | PRI | | | | value | varchar(128) | | PRI | | | | type | int(11) | | | 0 | | | modified | timestamp(14) | YES | | NULL | | +-----------+---------------+------+-----+---------+-------+ I inserted the next data in the table: +------+----------+--------+-----------+---------------+------+------------- ---+ | uuid | username | domain | attribute | value | type | modified | +------+----------+--------+-----------+---------------+------+------------- ---+ | | | | 00562 | 192.168.1.254 | 0 | 20050111152728 | +------+----------+--------+-----------+---------------+------+------------- ---+ So what i want to do is check the first part of the RURI in the INVITE message, for example if the INVITE is something like this INVITE sip:005621111111@sip.mydomain.com SIP/2.0 My question is how can i match the 00562111111 with the 00562 in the field "attribute" and therefore change the domain in the uri to: INVITE sip:005621111111@192.168.1.254 SIP/2.0 I guess that a simple t_relay() then would send the message to the new gateway. If this possible? Thanks in advance. Best Regards, Ricardo.- -----Mensaje original----- De: Ricardo Martinez [mailto:rmartinez@redvoiss.net] Enviado el: Lunes, 10 de Enero de 2005 18:14 Para: serusers(a)lists.iptel.org Asunto: RE: [Serusers] Dynamic Routes with SER. Thanks Samuel, I think the dispatcher module does not acomplish my requeriments for now. I more interested now in the avpops module. I read some lines about the module a few months ago for a similar problem. Is someone using this module for something like this?. In particular i want to mantain a route table for all my destinations and the respective terminating gateway. For example : Code Gateway 56 | 192.168.0.1 1 | 192.168.0.2 44 | 192.168.0.3 and so on.... This table is consulted for all the incoming request and then SER answer with a Redirect for the particular GW. Can someone provide me and example on how the AVPOPS module can handle this? I will really appreciate.... Thanks in advance Best Regards. Ricardo.- -----Mensaje original----- De: Samuel Osorio Calvo [mailto:samuel.osorio@nl.thalesgroup.com] Enviado el: Lunes, 10 de Enero de 2005 12:30 Para: dnay(a)ionosphere.net; serusers(a)lists.iptel.org; rmartinez(a)redvoiss.net Asunto: RE: [Serusers] Dynamic Routes with SER. Hi, There are a couple of modules in version 0.9 which can be used for dynamic routing depending on the desired functinality. One is called dispatcher, and is meant to be a load balancer without fair distribution. I think that you define a list of possible servers in a database and the dispatcher module forwards message to one of them (together with all within-dialog future responses and requests). The other option is to use avpops module which provides an attribute-value functionallity. You can use them to select the next hop depending on the incoming SIP message parameters and the values present in a database. I would advise you to take a look at the documentation of both modules to see if they suit your requirements before using the exec commands, which are not 100% reliable and increases the memory requirements as you have mentioned. From the exec module's readme: 1.5. Known Issues There is currently no guarantee that scripts ever return and stop blocking SIP server. (There is kill.c but it is not used along with the current mechanisms based on popen. Besides that kill.c is ugly). Enjoy SER, Samuel. Unclassified. >>> Ricardo Martinez <rmartinez(a)redvoiss.net> 01/10/05 05:22PM >>> Darren: Thanks for your quick answer. I was thinking in a similar solution, using a external program, in fact i use the exec_dset() functionality for something similar. I was thinking add to this solution a Redirect Server?. Maybe the call to the dynamic route proccess is in the Redirect Server, calling the exec_dset() function, so all the extra resource needed to perform these tasks are used in the redirect server and no in my Proxy-Registrar Server. Is just an idea.. IS this scalable maybe? Is this posible? Thanks in advance Best Regards, Ricardo Martinez.- -----Mensaje original----- De: Darren Nay [mailto:dnay@ionosphere.net] Enviado el: Lunes, 10 de Enero de 2005 11:06 Para: Ricardo Martinez; 'serusers(a)lists.iptel.org' Asunto: Re: [Serusers] Dynamic Routes with SER. Take a look in the SER Admin guide at "Executing an External Program". You can write an application with perl, C, etc.. Which will process the call info and return a destination set. This functionality is available using the exec_dset function in SERs exec module. I use this feature in our SER deployment and it works great. The only problem I've found so far is that it definitely does increases the resources required per call, and hurts your scalability. Especially if you use perl. Try to use C if at all possible, or persistent perl at the very least. Darren Nay On 1/10/05 11:01 AM, "Ricardo Martinez" <rmartinez(a)redvoiss.net> wrote: > Hello List. > I have a question on how to handle dynamic routes in SER. For what > i know, SER by himself is not the best way to handle dynamic routes, since > every change in a route implies a change in the ser.cfg file and then a > restart of the service. So i'm thinking how to solve this problem and a was > hoping that someone could give some advice on this issue. > Any idea is welcome. > > Thanks in advance. > BEst Regards. > > Ricardo Martinez.- > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

20 years, 1 month

[Serusers] SER won't start: can't find PID file

by Christian Thomas

Hi CJ, Sorry for disturbing you but I have the same pb than you've got regarding the serctl start with message. Starting SER: cat: /var/run/ser.pid: No such file or directory. SO for fun I touched a file with that name in that directory to see what would happen. I then get: Starting SER: PID file exists! (/var/run/ser.pid) already running? This is all obtained by running "serctl start". Prior to running I ran "ser -ddd -P /var/run/ser.pid" then I run serctrl, but am left being stuck in this situation. I'm stuck too in this situation and perhaps you have resolved this situation. Hope you can help me. best regards, Christian Thomas Diretor Executivo cthomas(a)canalwest.com <mailto:cthomas@canalwest.com> www.canalwest.com Tel +55 (48) 2107 2728 / Fax +55 (48) 333 3745 Atendimento SP (11) 5644 9889 Atendimento RJ (21) 3523 0393 Atendimento SC (48) 3027 2450

20 years, 1 month

[Serusers] q-value in location table incorrect

by Franz Edler

Hello, I just discovered, that the q-value in the location table does not reflect the q-value of the REGISTER request. Two examples: - q-value in Contact-header = 0,8 --> location table shows 0.01 - no q-value in Contact-header (default=0)--> location table shows -1.00 Any comments on this? Regards Franz

20 years, 1 month

[Serusers] A bug in www authentication?

by 牛坤

Dear ser users, Sorry to trouble you all. I'm developing my own sip client based on the nist jain sip library. I used SJphone with my SER and it works fine. When I change to JSphone(sip-communicator),something strange happened. I read the sourcecode of JSphone. It seems that the field nonce and cnonce in the "Authentication" field are both null in JSphone. However,I can see the values in SJphone are not null. Both clients can register onto my server. I wonder if this is a bug in ser. Thank you for your reply. Sincerely, Kun

20 years, 1 month

[Serusers] radius acc

by Gustavo Villegas

Dear Ser users I was wondering if the same method to make acc in mysql, is aplicable to accounting in radius scenario. or i need to enable something in the radius.conf. Best Regards Gustavo Villegas

20 years, 1 month

[Serusers] wrong translated request-uri in accounting records

by Juha Heinanen

if a request is forwarded to another destination in failure route by appending a new branch to it like in this example from the manual: failure_route[1] { # forwarding failed -- try again at another destination append_branch("sip:nonsense@iptel.org"); log(1,"first redirection\n"); # if this alternative destination fails too, proceed to reply_route[2] t_on_failure("2"); t_relay(); } then translated request-uri (format o) of accounting record does not contain this appended new uri, since the appended branch is not checked, when o-value is selected: case 'o': if (rq->new_uri.len) val_arr[cnt]=&rq->new_uri; else val_arr[cnt]=&rq->first_line.u.request.uri; ATR(OURI); break; is there an existing solution to this problem or should the above code be fixed? -- juha

20 years, 1 month

[Serusers] how to test that request comes from a fifo?

by Juha Heinanen

i can easily test in ser.cfg that a request comes from a particular ip address, but how do i test that a request comes from a particular fifo or unix socket? -- juha

20 years, 1 month

← Newer
1
...
26
27
28
29
30
31
32
...
40
Older →

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