Hi, I am using the last version of the SER server (0.9.6), and have a problem with the presence management. I want a user (805) to subscribe to the presence of another user (806), but when 805 sends a SUBSCRIBE to the SER, it responses a NOTIFY with "closed-offline", while both users had sent previously a successful REGISTER to the SER. Both users are added (serctl) to the server, and are displayed in "subscriber" table of the "ser" DB. Once registered, they are also in the "location" table. But the ser does not add "open" to the NOTIFY.. Any

Once the user 805 is successfully subscribed to the presence of user 806, when 806 modifies its presence (sends a PUBLISH to the SER, with

and <note>"Away"</note> in the xml, for instance), the SER is suppposed to send a NOTIFY with the same xml to user 805 (subscriber),

"pa" module is added, but in this moment I don't need authentication. U can see the ser.cfg file bellow: Thanks in advance // ******************************** # # $Id: ser.cfg,v 1.25.2.1 2005/02/18 14:30:44 andrei 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) #port=5060 #children=4 fifo="/tmp/ser_fifo" # ------------------ module loading ---------------------------------- # Uncomment this if you want to use SQL database 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/textops.so" loadmodule "/usr/local/lib/ser/modules/pa.so" # Uncomment this if you want digest authentication # mysql.so must be loaded ! #loadmodule "/usr/local/lib/ser/modules/auth.so" #loadmodule "/usr/local/lib/ser/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) modparam("pa","db_url","mysql://ser:heslo@localhost/ser") # -- 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"); break; }; if (msg:len >= 2048 ) { 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 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); break; }; if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); route(1); break; }; # 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=="PUBLISH"){ if(t_newtran()){ handle_publish("registrar"); break; } } if (method=="SUBSCRIBE") { if (!t_newtran()) { log(1, "newtran error\n"); sl_reply_error(); }; handle_subscription("registrar"); break; }; if (method=="REGISTER") { # Uncomment this if you want to use digest authentication # if (!www_authorize("192.168.1.118", "subscriber")) { # www_challenge("192.168.1.118", "0"); # 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; }; }; 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(); }; } // ******************************** -----Mensaje original----- De: Vaclav Kubart [mailto:vaclav.kubart@iptel.org] Enviado el: miércoles, 18 de octubre de 2006 6:21 Para: Diego Do?ate CC: serusers(a)iptel.org Asunto: Re: [Serdev] pa module: presence "substatus" Hi, notes are quite often used for this. Can you send your config here? What SER version do you use? And if you try register your users via sending REGISTER messages it is still the

> > Both users are added with serctl, but it seems the SER does not