sr-users June 2005

sr-users@lists.kamailio.org

241 participants
595 discussions

by Ryan Pagquil

Hi guys, I have a problem with SER... whenever I register using X-lite i never get logged in.... X-lite always prompts me that the connection timed out.... in my SER machine I run tcpdump -i gem0 | grep 5060 and i only see the request comming from my firewall and the SER machine is not responding on the request. here is the diagnostic of x-lite: SEND TIME: 3530347 SEND >> 202.84.24.107:5060 REGISTER sip:philonline.com SIP/2.0 Via: SIP/2.0/UDP 202.84.24.126:5060;rport;branch=z9hG4bK1165436EDDDD11D9BFB500E04CAB4AB4 From: Ryan Pagquil <sip:rpagquil@philonline.com>;tag=2916895101 To: Ryan Pagquil <sip:rpagquil@philonline.com> Contact: "Ryan Pagquil" <sip:rpagquil@202.84.24.126:5060> Call-ID: 11654266DDDD11D9BFB500E04CAB4AB4(a)philonline.com CSeq: 53597 REGISTER Expires: 1800 Max-Forwards: 70 User-Agent: X-Lite release 1103m Content-Length: 0 here is my ser.cfg: #debug=4 # debug level (cmd line: -dddddddddd) #fork=no #log_stderror=yes # (cmd line: -E) # Uncomment these lines to enter debugging mode #debug=3 #fork=yes #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 ---------------------------------- 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" modparam("usrloc", "db_mode", 2) modparam("auth_db", "calculate_ha1", yes) modparam("auth_db", "password_column", "password") modparam("rr", "enable_full_lr", 1) # ------------------------- request routing logic ------------------- # main routing logic route{ if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); break; }; if (len_gt( max_len )) { sl_send_reply("513", "Message too big"); break; }; record_route(); if (loose_route()) { t_relay(); break; }; if (uri==mysql) { if (method=="REGISTER") { if (!www_authorize("philonline.com", "subscriber")) { www_challenge("philonline.com", "0"); break; }; save("location"); break; }; if (!lookup("location")) { sl_send_reply("404", "Not Found"); break; }; }; if (!t_relay()) { sl_reply_error(); }; } my ser.cfg contains the default configuration and i just edited and uncommented some parts of it. Thanks, -- Ryan Pagquil Infodyne Inc. - PhilOnline.com 3603 Antel Global Corporate Center Doña Julia Vargas Ave. Ortigas Center Pasig City Tel: 687-0715 Web: www.philonline.com

19 years

[Serusers] How to execute failure_route block on tcp connect failure.

by Dmitry Isakbayev

Hello, I am having a problem executing a failure_route block when t_relay fails to establish a tcp connection. Everything works as expected when t_relay connects to a proxy and receives back an error like 501. Is there a way to configure t_relay to execute a failure_route block an a tcp connection error? Thank You in advance. Dmitry Here are the logs from connection failure - Jun 15 20:52:14 localhost ser[21870]: ERROR: tcp_blocking_connect: SO_ERROR (111) Connection refused Jun 15 20:52:14 localhost ser[21870]: ERROR: tcpconn_connect: tcp_blocking_connect failed Jun 15 20:52:14 localhost ser[21870]: ERROR: tcp_send: connect failed Jun 15 20:52:14 localhost ser[21870]: msg_send: ERROR: tcp_send failed Jun 15 20:52:14 localhost ser[21870]: ERROR: t_forward_nonack: sending request failed

19 years

[Users] RE: [Serusers] OpenSER release

by info＠beeplove.com

I agree with you. We should have proper bug tracking system, including feature request. MOhammad Original Message: ----------------- From: Giudice, Salvatore Salvatore.Giudice(a)FMR.COM Date: Wed, 15 Jun 2005 14:12:15 -0400 To: daniel(a)voice-system.ro, andrei(a)iptel.org, serdev(a)iptel.org, serusers(a)iptel.org, devel(a)openser.org, users(a)openser.org Subject: RE: [Serusers] OpenSER release I am not an advocate for either ser or openser, but I would like to comment. Is openser going to be equipped with a forum/ticket system where people can document bugs, feature requests, etc (non-configuration issues)? This is just my observation and you may not agree, but I believe this project could be much better maintained if it used a more structured ticketing style system to manage development issues instead of the current mailing lists. In my experience, mailing lists like this foster a terrible user experience where many development issues can go on without response. Ideally, if there was a mailing list to address user issues and ticketing system like the one Digium uses to manage Asterisk, I think everyone would benefit by being better informed and ser would ultimately be a better product for it. How many people out there feel that their issues have fallen through the cracks in the past couple years? -----Original Message----- From: Daniel-Constantin Mierla [mailto:daniel@voice-system.ro] Sent: Wednesday, June 15, 2005 4:28 AM To: Andrei Pelinescu-Onciul Cc: SER developer mailing list; serusers; users(a)openser.org; devel(a)openser.org Subject: Re: [Serusers] OpenSER release On 06/14/05 23:21, Andrei Pelinescu-Onciul wrote: >On Jun 14, 2005 at 22:48, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote: > >[...] > > >>It is your opinion, but I repeat myself, that the SER code maintained by >>us will go further -- I don't think that someone can claim that we >>didn't do the job for our code (the only discrepancy is some last-minute >>adds in xlog (to print avps) - will be committed on unstable very soon >>with the new color patch). The cvs was created just to ease the >>maintainance. The patches would be a nightmare. >> >> > >Maybe I've misunderstood you: is this only a parallel "stabilized" >version + some features or is it a full fork (do you intend to fork >unstable also)? > > It is fork for the code that we changed (acc module, usrloc module ...), in the future may be other that they do not find the path in SER. We will maintain and upgrade our part of code from SER continuously. >I have no problem with another stable version, what worries me is >fragmenting the development for unstable (which is the place where major >changes are made). > > I see no fragmenting there -- the situation is the same for SER as it was before. For example, there is no fragment for acc module, it will be maintained by who did it till now, adding what he considers necessary there. But we came to meet a lot of requests of why the acc patch is not included in the CVS (it was fully backward compatible and had new features requested by many SER users) and we want to promote _more open_ approach to contributions to all parts of code. The acc patch was sent on November 1, 2004. No real response (neither negative, nor positive) from maintainer to the submission since then ... are you aware of a good reason?!?! ... should we wait just about (or more) half an year for each contribution?!? I will not do that anymore!!! Daniel > >Andrei > > > _______________________________________________ Serusers mailing list Serusers(a)iptel.org http://mail.iptel.org/mailman/listinfo/serusers _______________________________________________ Serusers mailing list Serusers(a)iptel.org http://mail.iptel.org/mailman/listinfo/serusers -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ .

19 years

RE: [Serusers] DNS Resolution of SDP-"Connection Address" at SER

by Gerhard Zweimüller

Thanks for your answer. The funny thing is: I am trying quite hard to convince the vendor (actually a well-known VoIP-chip/module/appliance maker) that FQDN in SDP is a good (and allowed) thing. Even more funny: In the preceding firmware-release FQDN was no problem. But in the current release they apparently *removed* the FQDN-support and now they try to convince me that FQDN in SDP is not allowed :-( Although I sent them RFCs and everything to prove them wrong. But there you go. I tried your suggestion with fix_nated_sdp and so far it seems to work. Thanks for the tip! Hopefully the vendor will change its RFC-support policy soon. Kind regards, Gerhard -----Original Message----- From: Zeus Ng [mailto:zeus.ng@isquare.com.au] Sent: Sunday, June 12, 2005 8:30 AM To: Gerhard Zweimüller Cc: serusers(a)lists.iptel.org Subject: RE: [Serusers] DNS Resolution of SDP-"Connection Address" at SER Forcing SER to do stuff in order to fix problem UA implementation, I don't think this is a good approach. Using FQDN as connection information in SDP is the recommended approach in RFC 2327, though few UA do this. I would suggest you contact the vendor to fix the UA that can't work with DNS. Have a look on the fix_nated_sdp() function in nathelper. I haven't tried this before but it might work. However, there is no guarantee. Let us know if it works. > -----Original Message----- > From: Gerhard Zweimüller > Sent: Saturday, 11 June 2005 11:07 PM > To: serusers(a)lists.iptel.org > Subject: [Serusers] DNS Resolution of SDP-"Connection Address" at SER > > > Hi Serusers, > > I have a problem with DNS resolution in SIP/SDP "Connection > Information" > / "ConnectionAddress". Maybe somebody can help me: > > In the network we use SIP-UAs that are integrated into ADSL-Modems > from Allied Telesyn (AT RG 634). > The SIP-client itself works OK. But when the unit is given a > system-name in the configuration, it will always use its DNS-name > instead of its IP-addr as "Connection Address" in the "Connection > Information" in SDP in INVITE and corresponding OK messages. > > Now we want to add SIP-UAs that are NOT capable of resolving DNS-Names > in the "Connection Address" field. > Alle messages pass through SER of course and the SDP-part so far > remains unchanged. > > Now my question to the list: > Is there a simple way of forcing SER to do the DNS-resolution of in > incoming message, put in the IP-address in "Connection Address" and > forward it to the other UA? > > Thanks a lot in advance! > Gerhard > > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers > __________________________________________________________________________________ Dieses Mail wurde vom Infotech SecureMail Service ueberprueft und fuer sicher befunden. Fuer weitere Informationen zu Infotech SecureMail Service waehlen Sie bitte: www.infotech.at/securemail/ This email has been scanned by Infotech SecureMail Service and it has been classified as secure. For more information on Infotech SecureMail direct your web browser to: www.infotech.at/securemail/

19 years

[Serusers] failed to lookup for few seconds for every one hour

by Karun Chemudugunta

Hi Group, I am seeing issues where lookup() failing for every one hour for period of few seconds. ( ~ 20 to 30 seconds). Is it known issues ? Any house keeping happening for every hour ??? Version SER software: 0.8.12 Please find my attached ser.cfg Thanks in advance. Karun _______________________________________________________________________ Jun 13 12:41:14 encasip001 /usr/sbin/ser[4805]: lookup failed :SIP request from config Jun 13 12:41:14 encasip001 /usr/sbin/ser[4810]: lookup failed :SIP request from config Jun 13 13:40:44 encasip001 /usr/sbin/ser[4805]: lookup failed :SIP request from config Jun 13 13:41:15 encasip001 /usr/sbin/ser[4808]: lookup failed :SIP request from config Jun 13 13:41:15 encasip001 /usr/sbin/ser[4803]: lookup failed :SIP request from config Jun 13 13:41:17 encasip001 /usr/sbin/ser[4807]: lookup failed :SIP request from config Jun 13 13:41:17 encasip001 /usr/sbin/ser[4806]: lookup failed :SIP request from config Jun 13 13:41:17 encasip001 /usr/sbin/ser[4807]: lookup failed :SIP request from config Jun 13 13:41:17 encasip001 /usr/sbin/ser[4806]: lookup failed :SIP request from config Jun 13 13:41:17 encasip001 /usr/sbin/ser[4807]: lookup failed :SIP request from config Jun 13 13:41:18 encasip001 /usr/sbin/ser[4811]: lookup failed :SIP request from config Jun 13 13:41:18 encasip001 /usr/sbin/ser[4809]: lookup failed :SIP request from config Jun 13 13:41:18 encasip001 /usr/sbin/ser[4811]: lookup failed :SIP request from config Jun 13 13:41:19 encasip001 /usr/sbin/ser[4809]: lookup failed :SIP request from config Jun 13 13:41:19 encasip001 /usr/sbin/ser[4805]: lookup failed :SIP request from config Jun 13 13:41:19 encasip001 /usr/sbin/ser[4808]: lookup failed :SIP request from config Jun 13 13:41:20 encasip001 /usr/sbin/ser[4803]: lookup failed :SIP request from config Jun 13 14:40:57 encasip001 /usr/sbin/ser[4808]: lookup failed :SIP request from config Jun 13 14:40:57 encasip001 /usr/sbin/ser[4811]: lookup failed :SIP request from config Jun 13 14:40:57 encasip001 /usr/sbin/ser[4809]: lookup failed :SIP request from config Jun 13 14:40:58 encasip001 /usr/sbin/ser[4806]: lookup failed :SIP request from config Jun 13 14:40:58 encasip001 /usr/sbin/ser[4803]: lookup failed :SIP request from config Jun 13 14:40:59 encasip001 /usr/sbin/ser[4811]: lookup failed :SIP request from config Jun 13 14:41:00 encasip001 /usr/sbin/ser[4809]: lookup failed :SIP request from config Jun 13 15:40:35 encasip001 /usr/sbin/ser[4803]: lookup failed :SIP request from config Jun 13 15:40:35 encasip001 /usr/sbin/ser[4808]: lookup failed :SIP request from config Jun 13 15:40:36 encasip001 /usr/sbin/ser[4807]: lookup failed :SIP request from config Jun 13 15:40:36 encasip001 /usr/sbin/ser[4808]: lookup failed :SIP request from config Jun 13 15:40:36 encasip001 /usr/sbin/ser[4803]: lookup failed :SIP request from config Jun 13 15:40:36 encasip001 /usr/sbin/ser[4806]: lookup failed :SIP request from config Jun 13 15:40:36 encasip001 /usr/sbin/ser[4803]: lookup failed :SIP request from config Jun 13 15:40:37 encasip001 /usr/sbin/ser[4809]: lookup failed :SIP request from config Jun 13 15:40:37 encasip001 /usr/sbin/ser[4808]: lookup failed :SIP request from config Jun 13 15:40:39 encasip001 /usr/sbin/ser[4810]: lookup failed :SIP request from config ___________________________________________________________________________ # # $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=9 # 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) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) #port=5060 #children=4 fifo="/tmp/ser_fifo" alias=209.233.189.177 alias=voice.engca.bevocal.com # ------------------ 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" loadmodule "/usr/lib/ser/modules/exec.so" loadmodule "/usr/lib/ser/modules/textops.so" #loadmodule "/usr/lib/ser/modules/acc.so" #modparam("acc", "log_level", 2) #modparam("acc", "log_flag", 1) #modparam("acc", "report_cancels", 1) #modparam("acc", "failed_transactions", 1) # 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==myself) { if(method=="OPTIONS") { sl_send_reply("200", "Ok"); break; }; if (method=="REGISTER") { save("location"); break; }; if(method=="INVITE") { log(1,"about lookup in route zero"); if (!lookup("location","encamed")) { log(1,"lookup failed :SIP request from config"); sl_send_reply("404", "Not Found"); break; }; t_on_failure("5"); }; }; # setflag(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(); }; } failure_route[5] { revert_uri(); if (!lookup("location","encamed")) { log(1,"lookup failed :SIP request from config"); t_reply("404", "Not Found"); break; }; append_branch(); append_urihf("CC-Diversion: ", "\r\n"); t_on_failure("6"); t_relay(); } failure_route[6] { log(1,"Inside failure_route six"); exec_msg("printenv|grep '^SIP'|mail -v -s onfailure6 krcgunta(a)yahoo.com"); } _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

19 years

[Serusers] RE: CPL: serctl fifo LOAD_CPL problem

by Aisling O'Driscoll

I realise now what I've done wrong - I wasn't following the dtd file correctly (/tmp/ser-0.9.0/modules/cpl-c/cpl-06.dtd). ---- Original Message ---- From: ashling.odriscoll(a)cit.ie To: serusers(a)iptel.org Subject: RE: CPL: serctl fifo LOAD_CPL problem Date: Wed, 15 Jun 2005 15:20:52 +0100 >Hello, > >I am trying to upload a script onto SER using the "serctl fifo >UPLOAD_CPL user(a)xxx.xxx.xxx.xxx /path/to/file.xml" command.It is very >simple script to reject a call from caller 2093. Unfortunately I have >the errors seen below. I have included my simple cpl script, the >errors and the relevant part of the ser.cfg. Any help would be >greatly appreciated. > >Many Thanks, >Aisling. > >CPL SCRIPT [saved in /opt/ser/etc/ser]: > ><?xml version="1.0" encoding="UTF-8"?> ><!DOCTYPE cpl PUBLIC '-//IETF//DTD RFCxxxx CPL 1.0//EN'"cpl-06.dtd"> > <cpl> > <string-switch field="from"> > <string matches="2093(a)157.190.74.152"> > <response status="reject" reason="I dont want to"/> > </string> > </string-switch> > </cpl> > >SER.CFG: > >if (method == "INVITE"){ > if(!cpl_run_script("incoming", "is_stateless")) > { > # script execution failed > t_reply("500", "CPL script execution failed"); > }; > route(3); > break; > } else if (method == "REGISTER"){ > #handle REGISTER messages with CPL script > cpl_process_register(); > route(2); > break; > }; >} > >ERRORS: > >localhost:/opt/ser/etc/ser # :0: Element cpl content does not follow >the DTD >Expecting (ancillary? , subaction* , outgoing? , incoming?), got >(string-switch ) >:0: Element string content does not follow the DTD >Expecting (location | lookup | remove-location | address-switch | >string-switch | language-switch | time-switch | priority-switch | >proxy | redirect | reject | mail | log | sub)?, got (response ) >:0: No declaration for attribute matches of element string >:0: No declaration for element response >:0: No declaration for attribute status of element response >:0: No declaration for attribute reason of element response > 1(20171) ERROR:cpl-c:encodeCPL: CPL script doesn't respect CPL >grammar > 1(20171) ERROR: fifo_server: command (LOAD_CPL) processing failed > -------------------Legal Disclaimer--------------------------------------- The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt.

19 years

[Serusers] serweb for ser 0.9.0?

by maka

hi all, is there a working serweb for ser-0.9.0? I tried using serweb_2004-07-27 but it appears to be using the old database structure with 'perms' column in subscriber table in numerous queries. is there a working serweb for ser-0.9.0 or I would have to modify this one? cheers

19 years

[Serusers] CPL: serctl fifo LOAD_CPL problem

by Aisling O'Driscoll

Hello, I am trying to upload a script onto SER using the "serctl fifo UPLOAD_CPL user(a)xxx.xxx.xxx.xxx /path/to/file.xml" command.It is very simple script to reject a call from caller 2093. Unfortunately I have the errors seen below. I have included my simple cpl script, the errors and the relevant part of the ser.cfg. Any help would be greatly appreciated. Many Thanks, Aisling. CPL SCRIPT [saved in /opt/ser/etc/ser]: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE cpl PUBLIC '-//IETF//DTD RFCxxxx CPL 1.0//EN'"cpl-06.dtd"> <cpl> <string-switch field="from"> <string matches="2093(a)157.190.74.152"> <response status="reject" reason="I dont want to"/> </string> </string-switch> </cpl> SER.CFG: if (method == "INVITE"){ if(!cpl_run_script("incoming", "is_stateless")) { # script execution failed t_reply("500", "CPL script execution failed"); }; route(3); break; } else if (method == "REGISTER"){ #handle REGISTER messages with CPL script cpl_process_register(); route(2); break; }; } ERRORS: localhost:/opt/ser/etc/ser # :0: Element cpl content does not follow the DTD Expecting (ancillary? , subaction* , outgoing? , incoming?), got (string-switch ) :0: Element string content does not follow the DTD Expecting (location | lookup | remove-location | address-switch | string-switch | language-switch | time-switch | priority-switch | proxy | redirect | reject | mail | log | sub)?, got (response ) :0: No declaration for attribute matches of element string :0: No declaration for element response :0: No declaration for attribute status of element response :0: No declaration for attribute reason of element response 1(20171) ERROR:cpl-c:encodeCPL: CPL script doesn't respect CPL grammar 1(20171) ERROR: fifo_server: command (LOAD_CPL) processing failed -------------------Legal Disclaimer--------------------------------------- The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt.

19 years

RE: [Serusers] Ser Presence Server + Windows MSN 4.7

by PHAN, Quang-Minh

Hi, Yes, the PA module in SER does handle SUBSCRIBE, NOTIFY messages but it's not compatible with windows messenger 4.7. I don't know if someone is working on this module but at the moment it cannot be use to provide presence service. Minh > -----Message d'origine----- > De : serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] De la > part de Simith Nambiar > Envoyé : jeudi 9 juin 2005 07:47 > À : 'serusers(a)lists.iptel.org' > Objet : [Serusers] Ser Presence Server + Windows MSN 4.7 > > > Hello Serusers, > I'am new to the List , please can you give me the > below details , > > 1.) Does the Presence server in Ser do SUBSCRIBE/ NOTIFY processing and is > it compatible with Windows Messenger 4.7 ? > what i mean to say is that , does it reflect the current status of > the > logged in users, and generate appropriate Notifications ? > > Please let me know ! > > Thank You, > Cheers. > Simith > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers

19 years

Re: [Serusers] And the winner is ...

by harry gaillac

Samuel, You don't offend me. I just think all developpers should work together on the same project freely. It would be better for open community (and business) . If you want to do business don't give your work to open community (see Microsoft) . Go away SER players. Harry /////////////////////////////////////////////////////// > Business is the motivation for all SER users, I do > not > think that is > someone that do stuff with SER just because he has > no > other thing to do /////////////////////////////////////////////////////// --- Samuel Osorio Calvo <samuel.osorio(a)nl.thalesgroup.com> a écrit : > And the looser is...... > Harry! > > Samuel. > > P.D. It's nothing personal, I took you as an example > of user, I hope that it does not offend you. > > Unclassified. > >>> harry gaillac <gaillacharry(a)yahoo.fr> 06/15/05 > 12:08PM >>> > > Either voice-sistem or iptelorg.com !? > > ///////////////////////////////////////////////////////// > From: Daniel-Constantin Mierla > > Business is the motivation for all SER users, I do > not > think that is > someone that do stuff with SER just because he has > no > other thing to do > -- many work for companies that use SER, others do > studies and use ser > for projects... So the business behind is the engine > for development. > //////////////////////////////////////////////////////// > > Harry > > > > > > > ___________________________________________________________________________ > > Appel audio GRATUIT partout dans le monde avec le > nouveau Yahoo! Messenger > Téléchargez cette version sur > http://fr.messenger.yahoo.com > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers > > ___________________________________________________________________________ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com

19 years

← Newer
1
...
31
32
33
34
35
36
37
...
60
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 June 2005