Hi Bogdan:

I did not use forward(), but I load sl module. 
And I did use sl_send_reply() to reply 
483 and 513 message and sl_reply_error().

The attached file is my openser config file.

I use this config file to run openser. 
The under RFC3665 section 3.8 condition, 
I got two Via headers as I mentioned before.

So, according to my config file,
Openser is a stateless proxy server under 
RFC3665 section 3.8's condition?

Thank you.

Best Regards,
Fangyu Ling


----- Original Message ----- 
From: "Bogdan-Andrei Iancu" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[email protected]>
Sent: Wednesday, July 04, 2007 2:53 PM
Subject: Re: [OpenSER-Users] The Via Header of CANCEL Message


> Hi Fangyu ,
> 
> My opinion is that the RFC3665 does not cover the stateless part.
> 
> OpenSER can be both a stateless ans stateful proxy, it is just a matter 
> of configuration (what functions are you using). You can get pure 
> stateless or stateful cfg, or a mixed one, depending of you.
> 
> If you use the TM function for relaying and replying you will get a pure 
> stateful proxy. For stateless functions, see the forward() or sl module.
> 
> regards,
> bogdan
> 
> fancy wrote:
>> Hi Bogdan:
>>
>> RFC3665 didn't mention any stateful or stateless 
>> within all the document.
>> So I think it is just not covering it.
>>
>> By the way, is openser a stateless proxy server?
>> I think it is a stateful proxy server!
>> Can I config it to be a pure stateless or stateful proxy server?
>>
>> Thank you.
>>
>> Best Regards,
>> Fangyu Ling
>>
>>
>>   
>>> Klaus,
>>>
>>> CANCEL is hop-by-hop only in stateful processing and in this case, yes, 
>>> it has only on VIA. But if you have stateless processing, CANCEL is 
>>> end-2-end and it will have multiple VIAs...
>>>
>>> Does 3665 obsoletes stateless SIP or it is just not covering it???
>>>
>>> regards,
>>> bogdan
>>>
>>> Klaus Darilion wrote:
>>>     
>>>> Looks like it is defined clearly and openser is not 100% standard conform.
>>>>
>>>> regards
>>>> klaus
>>>>
>>>> fancy wrote:
>>>>   
>>>>       
>>>>> Hi Klaus:
>>>>> RFC 3665 page 54 line 4:
>>>>>         
>> Sorry it's RFC 3261 page 54 line 4:
>>   
>>>>>    A CANCEL constructed by a
>>>>>    client MUST have only a single Via header field value matching the
>>>>>    top Via value in the request being cancelled.
>>>>>
>>>>> and RFC 3665 at page 53:
>>>>>         
>> Sorry it's RFC 3261 at page 53:
>>   
>>>>>    CANCEL is referred to as a "hop-by-hop" request, since it is
>>>>>    responded to at each stateful proxy hop.
>>>>>
>>>>> and RFC 3665 at page 21:
>>>>>         
>> Sorry it's RFC 3261 at page 21:
>>   
>>>>>    Client: A client is any network element that sends SIP requests
>>>>>          and receives SIP responses.  Clients may or may not interact
>>>>>          directly with a human user.  User agent clients and proxies are
>>>>>          clients.
>>>>>
>>>>> So, for my opinion, the role of proxy in this case of RFC 3665 section 
>>>>> 3.8 is a client when it sends CANCEL message to Bob.
>>>>>
>>>>> If I misunderstand any RFC meanings, please correct me.
>>>>> Thank you very much.
>>>>>
>>>>> Best Regards,
>>>>> Fangyu Ling
>>>>>
>>>>>
>>>>>     
>>>>>         
>>>>>> fancy wrote:
>>>>>>       
>>>>>>           
>>>>>>> According to RFC 3665 section 3.8 and RFC 3261 section 9,
>>>>>>> there is only one via header in CANCEL message
>>>>>>> (message F11, F13 at page 72 of RFC 3665).
>>>>>>>         
>>>>>>>             
>>>>>> Hi!
>>>>>>
>>>>>> I could find it in RFC 3665, but not in 3261. Where exactly in RFC 3261
>>>>>> is mentioned that the CANCEL has only 1 Via header?
>>>>>>
>>>>>> Further, the example has only one Via header - but I could not find any
>>>>>> definition if this is a MUST or not.
>>>>>>
>>>>>>       
>>>>>>           
>>>>>>> How can I remove the 2nd via header?
#
# $Id: openser.cfg 1827 2007-03-12 15:22:53Z bogdan_iancu $
#
# simple quick-start config script
# Please refer to the Core CookBook at http://www.openser.org/dokuwiki/doku.php
# for a explanation of possible statements, functions and parameters.
#

# ----------- global configuration parameters ------------------------

#debug=3            # debug level (cmd line: -dddddddddd)
#fork=yes
#log_stderror=no    # (cmd line: -E)
#children=4

# Uncomment these lines to enter debugging mode 
#fork=no
#log_stderror=yes
#
alias="under.test.com"

listen=192.0.50.50
port=5060

advertised_address="ss.under.test.com"

# ------------------ module loading ----------------------------------

#set module path
mpath="/usr/local/lib/openser/modules/"

# Uncomment this if you want to use SQL database
loadmodule "mysql.so"

loadmodule "sl.so"
loadmodule "tm.so"
loadmodule "rr.so"
loadmodule "maxfwd.so"
loadmodule "usrloc.so"
loadmodule "registrar.so"
loadmodule "textops.so"
loadmodule "mi_fifo.so"
loadmodule "options.so" # load by fancy, 2007/06/25

# Uncomment this if you want digest authentication
# mysql.so must be loaded !
loadmodule "auth.so"
loadmodule "auth_db.so"

# ----------------- setting module-specific parameters ---------------

# -- mi_fifo params --

modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo")

# -- 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)

# added by fancy, 2007/06/25
modparam("options", "accept", "application/sdp")
modparam("options", "accept_encoding", "gzip")
modparam("options", "accept_language", "en")
modparam("options", "support", "timer")

# -------------------------  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
        
        # marked by fancy, 2007/05/31
#       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 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)
        
        # modified by fancy, 2007/05/25
        #if (uri==myself) {
        if (uri==myself || uri=~"reg.under.test.com" || 
uri=~"ss.under.test.com") {

                if (method=="OPTIONS") {
                        options_reply();
                };

                if (method=="REGISTER") {
                        route(2);
                };

                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"); 
        };

        # added by fancy, 2007/05/25
        # force server to reply 407 message when it recieved INVITE message
        ########## for one proxy test ##########
        if (!(method=="BYE") && (uri=~"under.test.com")) {
                if (!proxy_authorize("under.test.com", "subscriber")) {
                        log(1,"proxy_authorize auto realm\n");
                        proxy_challenge("under.test.com", "1");
                        exit;
                };
        };
        ########################################
        ######### for Two Proxy Test ########### 
        if (!(method=="BYE") && !(uri=~"under.test.com")) {
                if (!proxy_authorize( "","subscriber")) {
                        log(1,"proxy_authorize auto realm\n");
                        proxy_challenge( "", "1" );
                        exit;
                };
        };
        ########################################

        # added by fancy
        consume_credentials();
        route(1);
}


route[1] {
        # send it out now; use stateful forwarding as it works reliably
        # even for UDP2TCP

        # remove Proxy-Authorization from ACK
        # added by fancy, 2007/06/08
        remove_hf("Proxy-Authorization");

        if (!t_relay()) {
                sl_reply_error();
        };

        exit;
}

####################################################
# Registrar
# added by fancy, 2007/06/07
####################################################
route[2] {
        # Uncomment this if you want to use digest authentication
        #if (!www_authorize("openser.org", "subscriber")) {
        #       www_challenge("openser.org", "0");
        if (!www_authorize("under.test.com", "subscriber")) {
                www_challenge("under.test.com", "1");
                exit;
        };

        # append date
        # added by fancy, 2007/06/07
        append_time();
        save("location");
        exit;
}
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users

Reply via email to