[Serusers] SER and MSN Configuration Help
Chris Bookholt
cgbookho at ncsu.edu
Fri Mar 26 18:33:59 CET 2004
Thanks! Your advice to enforce authentication was very helpful! Now MSN prompts for a password.
However, I'm still having issues with one buddy not seeing the other as online. Hmm... As I wrote that last sentence the missing buddy just became visible. However, it took on the order of 5+ minutes to appear. That's not going to be within acceptable limits.
The delay confuses me because once the buddies can see each other in their buddy lists, status updates (away, busy, brb, etc.) happen almost instantaneously. What's causing this delay for sign on?
Again, thanks in advance!
-Chris B.
Daniel-Constantin Mierla wrote:
> Hello,
>
> On 03/25/04 23:58, Chris Bookholt wrote:
>
>> Greetings,
>>
>> I'm a new SER user trying to set up a very basic SER configuration
>> with a proxy server and two SIP clients. I'm running SER on RedHat
>> Linux 7.3 and a pair of MSN 4.6 clients.
>> I have set up SER with MySQL and digest authentication support (see of
>> of message for ser.cfg) and added a handful of normal users to the ser
>> MySQL db using serctl.
>> The two clients can sign on and communicate with each other. However,
>> the weirdness started after I added each client to the other's buddy
>> list. Even though both users are online and could IM each other, only
>> one of the users were shown as online on the other user's buddy list.
>> The factor that determines which client is visible in a buddy list
>> seems to be the order in which the users sign on.
>>
> you might need some time until both MSNs refresh the status of buddy
> list. If doesn't work, then watch the network traffic between then and
> see what happens with the SIP requests between them (you can use
> ethereal or ngrep).
>
>>
>>
>> Another issues is that a non-existent user can login. That is, a user
>> that does not have any entry in the ser MySQL database can still login
>> and communicate with other users online. How do you enforce
>> authentication?
>>
> You have to call www_authorize() for each REGISTER request. Better
> change if (uri=~"team3") to if (uri == myself) and put alias="team3" in
> the global configuration parameters.
>
>> I'd also be happy to learn of any alternatives to MSN that run on
>> either Windows of GNU/Linux.
>>
> Linux: KPhone (audio and instant messaging/presence)
> Windows: Xten (audio)
>
> .Daniel
>
>> Any help you can provide would be appreciated. Thanks in advance.
>>
>> Best Regards,
>>
>> Chris B.
>>
>> P.S. - I did search the serusers archive using Google and it seemed
>> that a similar question had been brought up in the past, but I found
>> no answer. My apologies if I was too hasty in my search of the
>> archives.
>> --- ser.cfg ---
>>
>> #
>> # $Id: ser.cfg,v 1.21.4.1 2003/11/10 15:35:15 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 debug=7
>> 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/lib/ser/modules/mysql.so"
>>
>> loadmodule "/usr/lib/ser/modules/sl.so"
>> loadmodule "/usr/lib/ser/modules/tm.so"
>> loadmodule "/usr/lib/ser/modules/rr.so"
>> loadmodule "/usr/lib/ser/modules/maxfwd.so"
>> loadmodule "/usr/lib/ser/modules/usrloc.so"
>> loadmodule "/usr/lib/ser/modules/registrar.so"
>>
>> # Uncomment this if you want digest authentication
>> # mysql.so must be loaded !
>> loadmodule "/usr/lib/ser/modules/auth.so"
>> loadmodule "/usr/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)
>>
>> # -- 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 > 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
>> record_route();
>> # loose-route processing
>> if (loose_route()) {
>> t_relay();
>> 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=~"team3") {
>>
>> if (method=="REGISTER") {
>>
>> # Uncomment this if you want to use digest authentication
>> if (!www_authorize("team3", "subscriber")) {
>> www_challenge("team3", "0");
>> break;
>> };
>>
>> save("location");
>> break;
>> };
>>
>> # native SIP destinations are handled using our USRLOC DB
>> if (!lookup("location")) {
>> sl_send_reply("404", "Not Found");
>> break;
>> };
>> };
>> # 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();
>> };
>>
>> }
>>
>> _______________________________________________
>> Serusers mailing list
>> serusers at lists.iptel.org
>> http://lists.iptel.org/mailman/listinfo/serusers
>>
>>
>>
More information about the sr-users
mailing list