[Devel] Re: [Users] t_newtran in BYE

openser-devel at list.coretech.ro openser-devel at list.coretech.ro
Fri Aug 4 20:38:05 CEST 2006


hello,

I have the same problem but in different scenario, I do not know if they 
are related.

I use the uac module.
the problem manifests only with retransmissions, and only if the "from" 
header was rewritten.
from what I can see it appears with any sip message, not just BYE

I have included a small scenario, maybe it helps, or maybe I misuse the 
uac module.

thanks,
Razvan Radu


openser-1.1.0-notls from source

===openser.cfg===
debug=2
fork=yes
log_stderror=no
log_facility=LOG_LOCAL5
 
port=5060
children=8
listen=192.168.2.1
 
mpath="/usr/local/lib/openser/modules"
loadmodule "sl.so"
loadmodule "tm.so"
loadmodule "rr.so"
loadmodule "uac.so"
 
alias="192.168.2.1"
 
route {
        loose_route();
        log(1, "T_RELAY EXEC\n");
        if(!t_relay()) {
                log(1, "T_RELAY EXECUTION FAILED\n");
                sl_reply_error();
        }
        exit;
}
===openser.cfg===

===sip-msg===
BYE sip:99903 at 192.168.0.102:5060 SIP/2.0
Via: SIP/2.0/UDP 
192.168.0.102:27234;branch=z9hG4bK-d87543-d62bf124e540b40a-1--d87543-;rport
Max-Forwards: 70
Route: 
<sip:192.168.2.1;lr;ftag=9735324217235;vsf=Y3NzYyklKCYzVCs+MjVsNiQwU11C>
Contact: <sip:99904 at 192.168.0.102:27234>
To: <sip:my-sip-proxy.com>;tag=9735324217235
From: <sip:99904 at 192.168.2.1>;tag=4b196b44
Call-ID: 3DBD8C6C-410E-4232-B237-2F3BE7BF00F1 at 192.168.0.102
CSeq: 2 BYE
User-Agent: X-Lite release 1003l stamp 30942
Reason: SIP;description="User Hung Up"
Content-Length: 0
 
===sip-msg===

===simulate===
twice in less than 15secs
cat sip-msg | nc -u -w 1 192.168.2.1 5060
===simulate===

===logs===
21:38:46 /usr/local/sbin/openser[20789]: T_RELAY EXEC
21:38:50 /usr/local/sbin/openser[20785]: T_RELAY EXEC
21:38:50 /usr/local/sbin/openser[20785]: ERROR: t_newtran: transaction 
already in process 0x2aaaab42a790
21:38:50 /usr/local/sbin/openser[20785]: T_RELAY EXECUTION FAILED
===logs===



Bogdan-Andrei Iancu wrote:
> Hi,
>
> most probably it is a script error - the message you get says that the 
> transaction for the BYE is created more than once. Script functions 
> that create transactions are: t_newtran, t_relay.
>
> probably you have more than one t_relay...?!
>
> regards,
> bogdan
>
> Kapil Dhawan wrote:
>
>> With evey Bye i am receiving t_newtran
>> ERROR: t_newtran: transaction already in process
>> DEBUG:sl:sl_reply_error: error text is I'm terribly sorry, server 
>> error occurred (1/SL)
>>
>> #
>> # $Id: openser.cfg,v 1.6 2006/02/15 18:23:46 bogdan_iancu Exp $
>> #
>> # simple quick-start config script
>> #
>>
>> # ----------- global configuration parameters ------------------------
>>
>> debug=8            # debug level (cmd line: -dddddddddd)
>> fork=yes
>> log_stderror=yes    # (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/openser_fifo"
>> fifo_db_url="mysql://root:root@localhost/openser"
>>
>> #
>> # uncomment the following lines for TLS support
>> #disable_tls = 0
>> #listen = tls:your_IP:5061
>> #tls_verify = 1
>> #tls_require_certificate = 0
>> #tls_method = TLSv1
>> #tls_certificate = "/usr/local/etc/openser/tls/user/user-cert.pem"
>> #tls_private_key = "/usr/local/etc/openser/tls/user/user-privkey.pem"
>> #tls_ca_list = "/usr/local/etc/openser/tls/user/user-calist.pem"
>>
>> # ------------------ module loading ----------------------------------
>>
>> # Uncomment this if you want to use SQL database
>> loadmodule "/usr/local/lib/openser/modules/mysql.so"
>>
>> loadmodule "/usr/local/lib/openser/modules/sl.so"
>> loadmodule "/usr/local/lib/openser/modules/tm.so"
>> loadmodule "/usr/local/lib/openser/modules/rr.so"
>> loadmodule "/usr/local/lib/openser/modules/maxfwd.so"
>> loadmodule "/usr/local/lib/openser/modules/usrloc.so"
>> loadmodule "/usr/local/lib/openser/modules/registrar.so"
>> loadmodule "/usr/local/lib/openser/modules/textops.so"
>>
>> # Uncomment this if you want digest authentication
>> # mysql.so must be loaded !
>> loadmodule "/usr/local/lib/openser/modules/auth.so"
>> loadmodule "/usr/local/lib/openser/modules/auth_db.so"
>>
>> # !! Accounting
>> loadmodule "/usr/local/lib/openser/modules/acc.so"
>>
>> # !! Nathelper
>> loadmodule "/usr/local/lib/openser/modules/nathelper.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)
>>
>> # -- acc params --
>> # set the reporting log level
>> modparam("acc", "log_level", 3)
>> # number of flag, which will be used for accounting; if a message is
>> # labeled with this flag, its completion status will be reported
>> modparam("acc", "log_flag", 1)
>> modparam("acc", "log_missed_flag", 2)
>> modparam("acc", "failed_transaction_flag", 1)
>> modparam("acc", "report_cancels", 1)
>> modparam("acc", "db_url", "mysql://root:root@localhost/openser")
>> modparam("acc", "db_flag", 1)
>> modparam("acc", "db_missed_flag", 2)
>>
>> # !! Nathelper
>> # -- nathelper params --
>> modparam("registrar", "nat_flag", 6)
>> modparam("nathelper", "natping_interval", 30) # Ping interval 30 s
>> modparam("nathelper", "ping_nated_only", 1)   # Ping only clients 
>> behind NAT
>>
>> # -------------------------  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;
>>        };
>>
>>
>>        # !! Nathelper
>>        # Special handling for NATed clients; first, NAT test is
>>        # executed: it looks for via!=received and RFC1918 addresses
>>        # in Contact (may fail if line-folding is used); also,
>>        # the received test should, if completed, should check all
>>        # vias for presence of received
>>        if (nat_uac_test("3")) {
>>                # Allow RR-ed requests, as these may indicate that
>>                # a NAT-enabled proxy takes care of it; unless it is
>>                # a REGISTER
>>
>>                if (method == "REGISTER" || ! search("^Record-Route:")) {
>>                    log("LOG: Someone trying to register from private 
>> IP, rewriting\n");
>>
>>                    # This will work only for user agents that support 
>> symmetric
>>                    # communication. We tested quite many of them and 
>> majority is
>>                    # smart enough to be symmetric. In some phones it 
>> takes a configuration
>>                    # option. With Cisco 7960, it is called 
>> NAT_Enable=Yes, with kphone it is
>>                    # called "symmetric media" and "symmetric 
>> signalling".
>>
>>                    fix_nated_contact(); # Rewrite contact with source 
>> IP of signalling
>>                    if (method == "INVITE") {
>>                        fix_nated_sdp("1"); # Add direction=active to SDP
>>                    };
>>                    force_rport(); # Add rport parameter to topmost Via
>>                    setflag(6);    # Mark as NATed
>>                };
>>        };
>>
>>        # labeled all transaction for accounting
>> #        setflag(1);
>> #        setflag(2);
>>        # 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);
>>        };
>>
>>        if (!uri==myself) {
>>                # mark routing logic in request
>>                append_hf("P-hint: outbound\r\n");
>>                # if you have some interdomain connections via TLS
>>                #if(uri=~"@tls_domain1.net") {
>>                #       t_relay("tls:domain1.net");
>>                #       exit;
>>                #} else if(uri=~"@tls_domain2.net") {
>>                #       t_relay("tls:domain2.net");
>>                #       exit;
>>                #}
>>                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)
>>        if (uri==myself) {
>>
>>                if (method=="REGISTER") {
>>
>>                        # Uncomment this if you want to use digest 
>> authentication
>>                        if (!www_authorize("", "subscriber")) {
>>                                www_challenge("", "0");
>>                                exit;
>>                        };
>>
>>                        save("location");
>>                        exit;
>>                };
>>
>>                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")) {
>>                        rewriteport("5065");
>>                        route(1);
>> #                       sl_send_reply("404", "Not Found");
>>                        exit;
>>                };
>>                append_hf("P-hint: usrloc applied\r\n");
>>        };
>>        t_on_failure("2");
>>        route(1);
>> }
>> route[1]
>> {
>>        # !! Nathelper
>>        if (uri=~"[@:](192\.168\.|10\.|172\.(1[6-9]|2[0-9]|3[0-1])\.)" 
>> && !search("^Route:")){
>>            sl_send_reply("479", "We don't forward to private IP 
>> addresses");
>>            return;
>>        };
>>
>>        # if client or server know to be behind a NAT, enable relay
>>        if (isflagset(6)) {
>>            force_rtp_proxy();
>>        };
>>
>>        # NAT processing of replies; apply to all transactions (for 
>> example,
>>        # re-INVITEs from public to private UA are hard to identify as
>>        # NATed at the moment of request processing); look at replies
>>        t_on_reply("1");
>>
>>        # send it out now; use stateful forwarding as it works reliably
>>        # even for UDP2TCP
>>        if (!t_relay()) {
>>                sl_reply_error();
>>        };
>> }
>>
>> failure_route[2] {
>>        t_on_reply("1");
>>        append_branch();
>>        t_relay("udp:x.y.z.w:5065");
>>        exit;
>> }
>>
>> # !! Nathelper
>> onreply_route[1] {
>>    # NATed transaction ?
>>    if (isflagset(6) && status =~ "(183)|2[0-9][0-9]") {
>>        fix_nated_contact();
>>        force_rtp_proxy();
>>    # otherwise, is it a transaction behind a NAT and we did not
>>    # know at time of request processing ? (RFC1918 contacts)
>>    } else if (nat_uac_test("1")) {
>>        fix_nated_contact();
>>    };
>> }
>>
>> _________________________________________________________________
>> Shah Rukh fan? Know all about the Baadshah of Bollywood. On MSN 
>> Search http://server1.msn.co.in/profile/shahrukh.asp
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at openser.org
>> http://openser.org/cgi-bin/mailman/listinfo/users
>>
>
>
> _______________________________________________
> Devel mailing list
> Devel at openser.org
> http://openser.org/cgi-bin/mailman/listinfo/devel





More information about the Devel mailing list