[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sr-dev
Subject:    [OpenSER-Devel] no matching sunbscription errors/warnings
From:       jh () tutpro ! com (Juha Heinanen)
Date:       2007-08-31 8:07:17
Message-ID: 18135.45517.568509.662563 () harjus ! tutpro ! com
[Download RAW message or body]

a user had an ongoing subscription while i was testing various presence
related things and in that process cleared presence tables and restarted
openser.

when this user now sends an in-dialog subscribe to an existing, but now
gone subscription, i get the following to syslog:

Aug 31 08:58:26 tutpro /usr/sbin/openser[13320]: Handling in-dialog SUBSCRIBE to \
                <sip:192.98.101.10:5090>
Aug 31 08:58:26 tutpro /usr/sbin/openser[13320]: PRESENCE:get_database_info:ERROR No \
                matching subscription dialog found in database
Aug 31 08:58:26 tutpro /usr/sbin/openser[13320]: PRESENCE:handle_subscribe:ERROR \
                getting stored info
Aug 31 08:58:26 tutpro /usr/sbin/openser[13320]: WARNING: script writer didn't \
release transaction

perhaps an ALERT would be better description of this situation than
ERROR.  

my main point, however, is, why is the release transaction warning
printed, because my script DOES release the transaction:

	if (method == "SUBSCRIBE") {
	    if (! t_newtran()) {
		xlog("L_ERR", "Could not create new transaction for <$rm> to <$ru>\n");
		sl_send_reply("500","Could not create new transaction");
	        exit;
	    };
  	    xlog("L_INFO", "Handling in-dialog SUBSCRIBE to <$ru>\n");
		if (!handle_subscribe()) {
		    xlog("L_ERR", "SUBSCRIBE to <$ru> failed\n");
		    t_reply("500", "SUBSCRIBE failed");
		};
		t_release();
		exit;
	} ...

or is the warning printed already by t_reply and i should release the
transaction before calling t_reply?

-- juha


[prev in list] [next in list] [prev in thread] [next in thread]